HTTP (embedded) trading configuration

A community can use an embedded HTTP server to receive messages from partners.

When you use the exchange wizard add an HTTP transport for a community using an embedded server, you begin by selecting one of the following options:

  • Use the system’s global embedded HTTP server – If you select this option, the wizard uses the default routing ID for the community as the last string in the URL. You can accept or change the string. No other configuration is required.
  • Use staged HTTP web servlet – If you select this option, you must install and configure a web servlet application in addition to using the delivery exchange wizard to add the transport. For details see Staged HTTP.
  • Use a previously defined embedded HTTP server (if available) – If you choose to use the system’s global embedded HTTP server, the wizard uses the default routing ID for the community as the last string in the URL. You can accept or change the string. No other configuration is required.
  • Define a new embedded HTTP server – If you choose to use a previously defined embedded HTTP server, the wizard prompts for the server name and a community routing ID to append to the URL. No other configuration is required.
    • If you choose to define a new embedded HTTP server, the wizard prompts for a server name, port number and whether clients must use SSL to connect to the server.
    • If you choose to define a community-level embedded HTTPS server, you must add an SSL certificate for the server. After setting up the server in the exchange wizard, go to the community summary page and click Change an embedded transport server near the bottom of the page. Click the name of the server to open the maintenance page. If the server needs a certificate, you are prompted to click Add an SSL server certificate. This action opens the wizard for adding a certificate.

Except for the global embedded server, embedded HTTP servers can be designated as HTTPS.

See Embedded transport servers for information about changing the configurations of embedded servers.

See HTTP security solutions for security guidelines for the embedded HTTP server.

When you use the exchange wizard to add an AS2 embedded HTTP trading pickup, you use the following fields:

  • Name – Type a name for the new embedded HTTP server. This can be any name you want. You can select this sever when setting up additional embedded HTTP delivery exchanges later.
  • Port – The port number that listens for incoming HTTP connections. The default is 4080.
  • Clients must use SSL to connect to this server – Select this to set up an HTTPS delivery exchange. A clear box indicates HTTP. When you select this check box, the following sub-field displays.
    • This server requires client authentication – If you selected SSL, select this check box to require your partners to submit a certificate to verify their identity before the delivery exchange allows the connection. Clear this box to use non-authenticated HTTPS. If you select this, you must add an authentication certificate for the partner.

Click Next to continue the configuration.

  • URL – The wizard displays the URL for the transport. This is the URL your partner uses to send messages to the community. The last item in the URL is the community routing ID. This is a suggested value. You can accept it or type another string.

Click Next if you want to name the exchange. Otherwise, click Finish.

Related Links