CLA2 Background

Before you can understand the impact that upgrading to the new Command Line Adapter 2 (CLA2) version will have on your system, you should first review what the CLA2 does.

The CLA2 enables Sterling B2B Integrator to run executable programs, scripts, or operating system commands from a business process.

When the CLA2 runs a command, the java Run Time.exec() method is called to fork the JVM and runs the command. The fork call works by making a complete copy of the running process before it runs the new command. Running this inside of the ASI JVM would require a large amount of memory. For this reason, CLA2 is a separate JVM with a small memory footprint. The CLA2 server accepts commands, runs them, and returns the results.

The CLA2 server can be deployed locally or remotely.

The following diagram illustrates how the ASI JVM can be deployed locally, on the same host as the CLA2 server.

This diagram shows a large box that represents the ASI JVM. There is an arrow from the CLA2 adapter box to another box, outside of the large ASI JVM box, that represents the CLA2 JVM. From there, an arrow points from the CLA2 JVM, by way of a program fork, to a box representing a custom script.

The following diagram illustrates how the ASI JVM can be deployed remotely, on a different host from the CLA2 server.

This diagram shows a large box that represents the ASI JVM as Host 1. There is an arrow from the CLA2 adapter box to another box, outside of the large ASI JVM box, that represents Host 2. This is where the CLA2 JVM is located. From there, an arrow points from the CLA2 server, by way of a program fork, to a small box representing a custom script, all within Host 2.