Starting Sterling B2B Integrator in a cluster environment

After you complete the installation or run the upgrade software, you can start Sterling B2B Integrator.

Before you begin

If you are starting Sterling B2B Integrator after you upgrade the application from v5.1, change the values of the following properties in the centralops.properties file to 600. This action prevents the start command from timing out before Sterling B2B Integrator starts.

  • OpsServer.commandTimeout
  • PassPhrase.urlTimeout

For the Windows operating system, the centralops.properties file is in the <install_dir>\properties directory.

For the Unix/Linux operating system, the centralops.properties file is in the <install_dir>/properties directory.

Procedure

Complete the following steps for each node in the cluster, starting with node 1.

  1. Complete the following steps for the Windows operating system:
    1. Open the \<install_dir>\bin directory.
    2. Enter StartWindowsService.cmd.
    3. Enter your passphrase.
  2. Complete the following steps for the Linux/Unix operating system:
    1. Open the /<install_dir>/bin directory.
    2. Enter ./run.sh.
    3. Enter your passphrase.
  3. The final startup processes run, concluding with the following message:
    Open your Web browser to http://<host:port>/dashboard

    Where <host:port> is the IP address and port number where Sterling B2B Integrator is located on your system.

    Depending on system load, it might take several minutes for the UI to be ready.

  4. Record the URL address so that you can access Sterling B2B Integrator.

What to do next

To release all the locks in a cluster when all nodes are down, use the restart parameter for node 1.

Note: The restart parameter can be used on only node 1. It cannot be used on any other nodes.
For Windows, complete the following steps:
  1. For node 1, enter the following command: startWindowsService.cmd restart
  2. For node 2 and higher, enter the following command: startWindowsService.cmd
For Unix/Linux, complete the following steps:
  1. For node 1, enter the following command: ./run.sh restart
  2. For node 2 and higher, enter the following command: ./run.sh