Configuring an HTTPS connection to the Sterling B2B Integrator server

Edit online

You can configure a secure connection to the Sterling B2B Integrator server.

About this task

The Design Studio establishes a HyperText Transfer Protocol (HTTP) connection with a Sterling B2B Integrator server, which is the default connection type, using the server and Sterling B2B Integrator Dashboard port number connection properties specified in the options for IBM Transformation Extender maps.

However, to have a secure connection to the Sterling B2B Integrator server, you can use HyperText Transfer Protocol Secure (HTTPS) access through the Secure Socket Layer (SSL) with the Test Map and Check In Map services. You must configure the Map Test HTTP Server Adapter using SSL in the Sterling B2B Integrator Dashboard. To read about how to do this, see the topic about configuring the HTTP Server adapter in the IBM Sterling B2B Integrator documentation that you can access through the IBM Sterling B2B Integrator Support website (http://www.ibm.com/software/commerce/support).

There are additional options under the Connectivity section of the Sterling B2B Integrator server preferences pane in the Design Studio where you specify a secure connection.

To configure a secure connection with the Sterling B2B Integrator server using HTTPS in the Design Studio:

Procedure

  1. Enter the port number in the Dashboard port field. If you configured the Map Test HTTP Server Adapter for a secure connection, use that same port number for the Dashboard port field.
  2. Select the Secure Transport check box.
  3. To specify direct trust, select the Trust all hosts check box. At run time when the map run or deploy operations are attempting to establish a connection to a Sterling B2B Integrator server, the following results occur depending on how Trust all hosts is set:
    • If Trust all hosts is selected, the connection verification step that checks the host passes even if the machine host name does not match the host name in the certificate.
    • If Trust all hosts is cleared, the connection verification step that checks the host fails if the machine host name does not match the host name in the certificate.
  4. Click OK to save changes.