Setting up Command Line Adapter 2 (CLA2) on Certified Container deployment
The Command Line Adapter 2 (CLA2) is a second-generation adapter that enables Sterling B2B Integrator to run a program from a command line in a business process, including executable programs, scripts, or operating system (OS) commands external to Sterling B2B Integrator. For more information, refer to Command Line Adapter 2.
Deployment of CLA2 can be done both locally or remotely on a Certified Container environment.
Deployment pattern with a local CLA2 server
For local CLA2 deployment, a CLA2 server runs on each ASI node or pod and only the local CLA2 client adapter can call the CLA2 server. Business processes must be on each node that is running a CLA2 server or you can create a service group of CLA2 adapters to allow the client service to call the appropriate CLA2 server on the local ASI pod. To configure and launch a local CLA2 server on the ASI pod, refer to Configuring local Command Line Adapter 2 (CLA2) on Certified Container.
The local CLA2 server runs inside the ASI pod on the same underlying Operating System (OS) as the application which is based on RHEL Universal Base Image (UBI).
Deployment pattern with a remote CLA2 server
For remote CLA2 deployment, a CLA2 server runs on external host outside of the Kubernetes or Red Hat OpenShift cluster. The CLA2 client adapter on each ASI node or pod can be configured to invoke the remote CLA2 server using the remote host and port. You can create a service group of CLA2 adapters to allow the client service to call the appropriate remote CLA2 server. To configure and launch a remote CLA2 server, refer to Configuring remote Command Line Adapter 2 (CLA2) on Certified Container.
The external/remote host can be on any Operating System (OS), like Windows or any Unix/Linux version, and does not have to be on the same OS as the ASI pod. This allows integration options with heterogeneous environments using the CLA2 adapter along with a remote CLA2 server.
