Add a Perimeter Server to Sterling B2B Integrator

You can add a perimeter server to Sterling B2B Integrator to monitor the perimeter server on the Troubleshooter page.

About this task

Before you can add a perimeter server to Sterling B2B Integrator, you must:
  • Install a perimeter server.
  • Know the host name and port number of the installed perimeter server.
  • Install a JDK version on the DMZ server that Sterling B2B Integrator supports.
    CAUTION:
    Do not use spaces in the name of the JDK installation directory.

Procedure

To add a perimeter server, complete the following steps:

  1. From the Administration menu, select Operations > Perimeter Servers.
  2. On the Perimeter Servers page, next to New Perimeter Server, click add.
  3. On the Perimeter Server Configuration page, complete the following fields and click Next.
    Field Description
    Name Name you provided of the perimeter server to connect to.
    Near End Configuration
    Note: The Near End Configuration fields are useful in environments involving firewalls with rules designed to only allow specific IP addresses, ports, or both to create outbound connections.
    Interface Or IP DNS name or IP address of the computer that you typed when you installed the perimeter server.

    Type * (wildcard) to allow Sterling B2B Integrator to establish this value.

    This interface will be used for the near end of the persistent connection to the perimeter server. Specify it only if your machine has multiple interfaces and not all are able to connect to your DMZ.

    Local Port Port number that you chose when you installed the perimeter server.

    Type 0 (zero) to allow Sterling B2B Integrator to establish this value.

    This port will be used for the near end of the persistent connection to the perimeter server.

    Specify a port other than 0 (zero) only if your firewall controls access to the DMZ based on the originating port. Specifying 0 (zero) allows Sterling B2B Integrator to choose any available port.

    Perimeter Server (far-end) is in less secure network zone Check this to enable the connection from Sterling B2B Integrator to the perimeter server. To connect in the opposite direction, clear the checkbox.
    Perimeter Server Host DNS name or TCP/IP address of the computer that the remote perimeter server is installed on. If you specified an internal interface during your perimeter server installation, use that address here.
    Perimeter Server Port Port number that the remote perimeter server monitors for connections. This is the port number you specified when installing your remote perimeter server.
    Cluster Node Node that is to be used with this perimeter server, if you are running in a clustered environment. If you are running in a clustered environment. If you are not running in a clustered environment, you must select the local node (node1) from the list.
  4. On the High/Low Watermarks page, complete the following fields and click Next.
    Field Description
    Note: You can set specific watermark parameters for each trading partner, by adding a perimeter server for each trading partner and configuring the perimeter server to match the trading volume and document size for each trading partner. This enables you to allocate more system memory to your trading partners with which you trade larger volumes and larger files. By allocating more or less memory to a trading partner, you can increase performance.
    Inbound Connection
    High Highest inbound connection buffer size. This is the high watermark.

    When a trading partner sends data faster than Sterling B2B Integrator can process it, the excess data accumulates inside perimeter services in the inbound connection buffer. When the buffer size reaches the High Inbound Connection value, perimeter services stops receiving data for that connection until enough of the excess data has been processed that the inbound connection buffer size drops to the Low Inbound Connection value.

    For example, if you set the High Inbound Connection value to 500 KB and the Low Inbound Connection value to 250 KB, perimeter services will stop receiving data when the inbound connection buffer size reaches 500 KB and will resume receiving data when the inbound connection buffer size drops to 250 KB.

    Low Lowest inbound connection buffer size. This is the low watermark.

    When a trading partner sends data faster than Sterling B2B Integrator can process it, the excess data accumulates inside perimeter services in the inbound connection buffer. When the buffer size reaches the High Inbound Connection value, perimeter services stops receiving data for that connection until enough of the excess data has been processed that the inbound connection buffer size drops to the Low Inbound Connection value.

    For example, if you set the High Inbound Connection value to 500 KB and the Low Inbound Connection value to 250 KB, perimeter services will stop receiving data when the inbound connection buffer size reaches 500 KB and will resume receiving data when the inbound connection buffer size drops to 250 KB.

    Outbound Connection
    High Highest outbound connection buffer size. This is the high watermark.

    When Sterling B2B Integrator sends data to a trading partner faster than the trading partner can receive it, the excess data accumulates inside perimeter services in the outbound connection buffer. When the buffer size reaches the High Outbound Connection value, perimeter services stops sending data through that connection until enough of the excess data has been sent that the outbound connection buffer size drops to the Low Outbound Connection value.

    For example, if you set the High Outbound Connection value to 500 KB and the Low Outbound Connection value to 250 KB, perimeter services will stop sending data when the outbound connection buffer size reaches 500 KB and will resume sending data when the outbound connection buffer size drops to 250 KB.

    Low Lowest outbound connection buffer size. This is the low watermark.

    When Sterling B2B Integrator sends data to a trading partner faster than the trading partner can receive it, the excess data accumulates inside perimeter services in the outbound connection buffer. When the buffer size reaches the High Outbound Connection value, perimeter services stops sending data through that connection until enough of the excess data has been sent that the outbound connection buffer size drops to the Low Outbound Connection value.

    For example, if you set the High Outbound Connection value to 500 KB and the Low Outbound Connection value to 250 KB, perimeter services will stop sending data when the outbound connection buffer size reaches 500 KB and will resume sending data when the outbound connection buffer size drops to 250 KB.

  5. On the Confirm page, verify your selections and click Finish.
    The perimeter server is added to Sterling B2B Integrator. You can now monitor the perimeter server using the Troubleshooter page. View the perimeter server log using the System Logs page. Monitor the remote perimeter server using the perimeter server log on the remote server.