Start Adapter Container

Depending on whether you are using UNIX/Linux, or Windows, you have a variety of commands to start an adapter container.

This topic covers the following:
  • Start Adapter Container - UNIX/Linux
  • Start Adapter Container - Windows

Start Adapter Container - UNIX/Linux

To start an adapter container JVM in UNIX/Linux, run one of the following commands from the install_dir/install/bin directory:
  • ./runAll.sh - starts Sterling B2B Integrator and all configured adapter container JVMs.
  • ./run.sh - starts noapp node.
  • ./startContainer.sh # - starts specified adapter container JVM.
Note: If you run ./runAll.sh script, it starts Sterling B2B Integrator and all configured adapter container JVMs. Similarly, startContainer.sh will start all configured adapter containers.

Start Adapter Container - Windows

To start an adapter container JVM in Windows, run one of the following commands from the install_dir\install\bin directory:
  • startWindowsService.cmd - starts Sterling B2B Integrator and all configured adapter container JVMs.
  • startContainerWindowsService.cmd - starts all configured adapter container JVMs.
  • startContainerWindowsService.cmd # - starts specified adapter container JVM.

    In this convention, # refers to the number used to configure the container JVM. For example, in the command setupContianer.cmd 2, the container JVM number is 2.

  • startASIWindowsService.cmd - starts noapp node.