Global embedded HTTP server

The global embedded HTTP server is available after a community adds an HTTP transport for receiving messages from partners. Communities can share it. You can change the server’s port and advanced options.

Note   If you have a Peer Network license, note that these settings are not clonable.

To change settings:

  1. Select System management > Manage embedded servers. Or, click Trading configuration on the toolbar.
  2. On the Communities page, click the link near the bottom of the page named Manage all embedded servers.

This server only is for HTTP. For HTTPS have a community add an embedded server (see HTTP (embedded) fields).

The following are the configuration fields for the server.

Settings tab

  • Host – The fully qualified domain name of the computer on which the embedded server runs. Interchange detects this setting; you cannot change it.
  • Port – The port on which the server listens for connection requests.

DMZ ports tab

Note   This tab displays in the user interface only if your software license enables Secure Relay DMZ nodes. The tab only applies to servers used for trading and not integration.
  • Enable DMZ port forwarding –Select this check box if you want the external firewall or load balancer to send inbound connections to Secure Relay DMZ nodes rather than directly to embedded servers in the protected network.
  • In the simplest case there is one DMZ port with the same value as the corresponding embedded server port in the protected network. If you add a machine to your cluster and return to the DMZ ports tab, another DMZ port automatically is added in sequence. This happens because every machine in the cluster that can host the embedded server must be assigned a unique corresponding port in the DMZ.
  • Click the port field to display a list of ports already in use.
  • Enable security termination in DMZ – Select this check box to have various security functions performed in the DMZ. If connections are via SSL, the secure connection is terminated at the router agent in the DMZ. For delivery exchanges that require a user name and password to connect (for example, FTP, SFTP, WebDAV), the router agent authenticates the user.
  • Enable IP address checking in DMZ – Select this check box to have Interchange check partners’ IP addresses against a whitelist of authorized IP addresses. Connections from unknown IP addresses are not allowed.
    • Match IP address against partner definition - When IP address checking is enabled, select this check box to have the router agent check whether the partner is registered to the IP address. If not selected, the agent only checks the user’s credentials. (This control is not available to all types of servers.)
  • Zone – If you want to receive messages through a Secure Relay DMZ zone, select a zone. This drop-down field is available only if zones have been set up.

See Port forwarding details for more information.

Advanced tab

  • Minimum threads – The least number of threads Interchange must dedicate to the server.
  • Maximum threads – The most threads Interchange can dedicate to the server.
  • Read timeout (seconds) – The maximum number of seconds the server waits when reading data from a partner.
  • Restartable minimum size (KB) – The minimum size of a file that triggers the system to continue the file transfer at the point interrupted before the connection was lost. The minimum size is in kilobytes. The system only resumes transfers of files that meet this minimum. The system starts over the transfer of smaller files whose processing is interrupted.
  • Temporary file lifetime (hours) – If attempt restarts is selected, how long the system retains a file whose transfer has been interrupted while waiting for the connection to be restored. This temporary file enables the system to resume the transfer at the point interrupted.

Related topics

Related Links