Configuring an HTTP server

Use this task to configure an HTTP transport server that can be used by an exchange profile. A transport server must be configured before you can configure an exchange profile.

Before you begin

You must have Master Account Administrator permissions to create an HTTP server.

You also can import a server configuration as a resource from another installation of B2B Advanced Communications. For more information, see ../com.ibm.help.meg.reference.doc/meg_resource_commands.html.

About this task

The HTTP server does not use the SSL certificate for security. To use SSL with the HTTP transport protocol, you must configure an HTTPS server.
Important: If the communications component receives a notification (critical event) about low grid memory, the HTTP server stops accepting the incoming messages for processing. The messages that are already accepted are processed. After the memory clears and rises higher than the low watermark, another notification is sent to the communications component. Thereafter, the HTTP server starts accepting the messages.

Procedure

  1. Log in to B2B Advanced Communications.
  2. Click Systems Management > Servers.
  3. On the Servers page, click New and select HTTP.
  4. On the Create HTTP Server page, specify values for the following fields:
    Associated organization
    Click Select and select the owner organization with which the HTTP server is associated. Type a unique name for the HTTP server.
    Name
    Type a unique name for the HTTP server.
    Description
    Optional: Type a description for the HTTP server.
    Port
    Type the port number for the HTTP server.

    Generally, the port number specifies the service available on the HTTP server. When you are assigning a port number to the HTTP server, ensure that the port number does not conflict with the default port number of a service that is available on the HTTP server. Valid range for a port number is 0 - 65535.

    External URL for this server
    Type the URL of the HTTP server. The URL is shared with the trading partners. The trading partners configure the URL in their exchange profile.
    Perimeter server
    Optional: Select the Enable perimeter server check box to enable a perimeter server.

    Enabling the perimeter server option allows the HTTP server and perimeter server to communicate with each other. Perimeter server must be configured at the member level. If a perimeter server is configured and if it is enabled in the HTTP server configuration, messages pass through the perimeter server based on the configuration of the perimeter server - less secure or more secure network.

    Note: For more information on how to set up Perimeter server, see ../com.ibm.help.meg.planning.doc/meg_plan_install_work_perimeter_servers.html#WorkingWithPerimeterServers.
    Thread pool
    Select a thread pool (a collection of threads). A thread pool manages the threads in the pool to process the tasks. To handle large volumes of files or large files, you can create a thread pool with more number of threads and associate the thread pool to the HTTP server.
    Basic authentication
    Optional: Select the Enable basic authentication check box to enable basic user authentication.

    Basic authentication is used to determine the identity of the client (sender), through a username and password (organization credentials) when a transaction is initiated.

  5. Click Save to save the HTTP server configuration. The HTTP server is automatically started when you save the configuration.