Set Up Adapter Container

You can set up an adapter container for node configuration.

The database should be up and running to set up an adapter container JVM as the database is updated to set up the adapter container.

Ensure that you have sufficient hardware resources before configuring container nodes. The default value of maximum heap for container node is 512 MB. You can increase this value if the container hosting the adapter is processing a large amount of data. Change this value in the Maximum Heap Size (MB) field on the Performance Tuning: JVM Parameters Container Nodes page of the performance tuning wizard. Refer to the performance management documentation for information about using the tuning wizard.

The database connection parameters are the same as that of ASI node. However, you can modify the database connection parameters by overriding them in the customer_overrides.properties file in the container node properties directory.

For more information about tuning container JVMs, see the performance management documentation.

Every ASI node and container node contains customer_overrides.properties file. You have to update the customer_overrides.properties file in the respective nodes to apply or override any changes. You should update customer_overrides.properties file depending on the order in which you set up the container node:
  • If you create or update the customer_overrides.properties file in the ASI node before the container node is set up, the properties added into the customer_overrides.properties file of the ASI node would be automatically added into the customer_overrides.properties file in the container node.
  • If you create or update the customer_overrides.properties file in the ASI node after the container node is set up, the properties added into the customer_overrides.properties file of the ASI node should be manually added into the customer_overrides.properties file in the container node.

If you update the cluster protocol, you must also update the adapter container protocol.

Set Up Adapter Container - UNIX/Linux

To set up an adapter container JVM in UNIX/Linux:
  1. Navigate to the install_dir/install/bin directory.
  2. Perform this step, which enables you to set up the adapter container independently later without shutting down the system.
    Note: Skip this step and perform step 3 if you are:
    • Running Sterling B2B Integrator in a cluster environment.

    • Migrating Sterling B2B Integrator to a cluster environment after setting up at least one adapter container.

      For more information about migrating to a cluster environment, see Sterling B2B Integrator Cluster Installation.

    • Adding additional adapter containers after setting up at least one adapter container.

    If the application server-independent (ASI) node is up, run ./hardstop.sh command to stop it.

    Run ./startCluster.sh 1 false command.

  3. Set up the adapter container by running ./setupContainer.sh containerNumber command.

    In this convention, containerNumber refers to the adapter container node number. For example, if you run ./setupContainer.sh 2 on Sterling B2B Integrator node2, then the adapter container name will be node2AC2.

  4. Run ./setupfiles.sh.
  5. Configure the adapter container for node communication.

Set Up Adapter Container - Windows

To set up an adapter container JVM and install it as a service in Windows:
  1. Navigate to the install_dir\install\bin directory.
  2. Perform this step, which enables you to set up the adapter container independently later without shutting down the system.
    Note: Skip this step and perform step 3 if you are:
    • Running Sterling B2B Integrator in a cluster environment.

    • Migrating Sterling B2B Integrator to a cluster environment after setting up at least one adapter container.

      For more information about migrating to a cluster environment, see Sterling B2B Integrator Cluster Installation.

    • Adding additional adapter containers after setting up at least one adapter container.

    If an application server-independent (ASI) node is up, run stopWindowService.cmd command to stop it.

    Run startCluster.cmd 1 false command.

  3. Set up the adapter container by running setupContainer.cmd containerNumber command.

    In this convention, containerNumber refers to the adapter container node number. For example, if you run setupContainer.cmd 2 on Sterling B2B Integrator node2, then the adapter container name will be node2AC2.

  4. Run setupfiles.cmd.
  5. Configure the adapter container for node communication.

Applying New Builds

You should stop application-server independent (ASI) nodes before applying new builds. However, container nodes can be running when you are applying new builds. You can apply new builds to the ASI nodes and container nodes separately. You can apply new builds to the container nodes after applying them on the ASI nodes.

If you intend to apply new build to both container node and ASI node together, both nodes should be stopped. For more information, see the Sterling B2B Integrator Upgrade documentation.

If you intend to apply new build to the ASI node and container node separately, ensure that you first apply the new build to the ASI node.

To apply new build to the ASI node, perform the following tasks:
  1. Stop ASI node by running one of the following commands:
    • (UNIX/Linux) ./stopASI.sh
    • (Windows) stopASIWindowsService.cmd
  2. Stop ASI ops server by running one of the following commands:
    • (UNIX/Linux) ./stopASI.sh ops
    • (Windows) stopOpsWindowsService.cmd
  3. Install the new build by running one of the following commands:
    • (UNIX/Linux) ./InstallService.sh <patch.jar>
    • (Windows) InstallService.cmd <patch.jar>
  4. (Windows only) Run the following command: setupfiles.cmd
  5. Start ASI node by running one of the following commands:
    • (UNIX/Linux) ./run.sh
    • (Windows) startASIWindowsService.cmd
To apply new build to the container node, perform the following tasks:
  1. Stop adapter container nodes by running one of the following commands:
    • (UNIX/Linux) ./stopContainer.sh
    • (Windows) stopContainerWindowsServices.cmd
  2. Install the new build by running one of the following commands:
    • (UNIX/Linux) ./patchContainerNodes.sh
    • (Windows) patchContainerNodes.cmd
  3. (Windows only) Run the following command: setupfiles.cmd
  4. Start adapter container node by running one of the following commands:
    • (UNIX/Linux) ./startContainer.sh
    • (Windows) startContainerWindowsService.cmd

You should update customer_overrides.properties.in file in each container node if you have customized bundles. For example, if you have two OSGI bundles, customer_bundle1.jar and customer_bundle2.jar, you should place them in install_dir/install/osgi/bundles (install_dir\install\osgi\bundles for Windows) directory. Additionally, you should add the following line in the customer_overrides.properties.in file in the install_dir/install/properties/node*AC* (install_dir\install\properties\node*AC* for Windows) directory:

osgi.osgi.auto.start.bundles.customer=customer_bundle1.jar, customer_bundle2.jar