Configuring local Command Line Adapter 2 (CLA2) on Certified Container

On a Certified Container deployment, the CLA2 server is not launched in the ASI pod by default. To setup and launch a local CLA2 server inside each ASI node or pod, you must perform certain additional configuration changes during the Certified Container deployment.

Launch the CLA2 Server

For Sterling B2B Integrator v6.2.0.0, to launch the CLA2 server on the ASI pod, you should add the below configuration to your Certified Container helm values configuration override file. The configuration needs to be added at the end of the setupCfg section in the helm values configuration override file followed by helm upgrade.

setupCfg:
...
...
  SANDBOX_LAUNCH_CLA2_SERVER: true

For Sterling B2B Integrator v6.2.0.1 and above, to launch the CLA2 server on the ASI pod, you should enable the launchClaServer configuration in your Certified Container helm values configuration override file. The configuration is available under the setupCfg section of the helm values override file followed by helm upgrade.

setupCfg:
...
...
#CLA2 configurations
launchClaServer: true

Map external scripts or files for CLA2 server

External scripts or files required to be executed by the CLA2 server can be made available to the local CLA2 server either through the resources volume, if enabled and configured, or through the resources or extra init container configured for the ASI pod.

If resources volume is enabled and configured as part of the Certified Container deployment, the scripts or files to be executed by the local CLA2 server can be placed in the external mapped resources path location. While configuring the CLA2 Adapter, set the working directory to /ibm/resources.

Alternatively, you can bundle the scripts and other files required by the local CLA2 server in an image by using one of the below options:

If resources init container option is enabled, extend the resources init image by adding the required scripts and files to the location /ibm/resources. For more details, refer to Building Custom Init Container Image. Configure the extended image for the resourcesInit section in the helm values configuration override file.
Note: While configuring the CLA2 Adapter, the working directory needs to be set to /ibm/resources.
Build an entirely new image to bundle the scripts and files required by the local CLA2 server and copy the artifacts to a directory location. For more details, refer to Building Custom Init Container Image. Make sure the Docker file is updated to copy the required files as needed. Then, the new image should be configured as an extra init container for the ASI pod in the helm configuration override file. For example:
```
asi:
…
  extraInitContainers: 
    - name: cla2server
      image: “image-registry.openshift-image-registry.svc:5000/b2bi-       
      cla2:1.0"
      imagePullPolicy: IfNotPresent
      command:
      shareVolume: true
      localMountPath: /b2bi/cla2/
      appMountPath: /ibm/cla2/
```
Note: While configuring the CLA2 Adapter, the working directory needs to be set to appMountPath from the above extra init configuration example viz. /ibm/cla2.

Note: In Sterling B2B Integrator v6.2.0.0, only the resources init image option is available for mounting CLA2 scripts/resources.

Note: From Sterling B2B Integrator v6.2.0.1 onwards, the extraInitContainer configurations is available to mount a local path to an application mount path.

CLA2 adapter configurations

Set the following configurations while configuring the CLA2 adapter to connect to a local CLA2 server:

Set the Remote Name to either localhost or 127.0.0.1.
Tip: It is recommended to set the Remote Name to either localhost or the localhost loopback IP 127.0.0.1. Setting it to the local pod IP is not recommended as it may change when the pod restarts or upgrades.
Set the Remote Port to the configured base port + 52.
Note: Base port value is configured in the setupCfg section (setupCfg.basePort) of the helm configuration values override file.
Set the working directory to the mapped resources or init container location viz. /ibm/resources or appMountPath-/ibm/cla2 - from the extra init container configuration.

For rest of the CLA2 adapter configurations, refer to Configuring CLA2.

Note: In Sterling B2B Integrator v6.2.0.0, authentication and SSL are not supported currently for the local CLA2 server. To disable authentication, set PROPERTY_cla2server_enableAuthentication to false in the values.yaml file.

From Sterling B2B Integrator v6.2.0.1 onwards, authentication and SSL are supported for the local CLA2 server. To enable authentication and SSL for the local CLA2 server, add the following configurations to the helm configuration override file in the setupCfg:

PROPERTY_cla2server_enableAuthentication: true/false
PROPERTY_cla2server_SSLRequired: "Yes/No"

Note: The value Yes or No for the parameter PROPERTY_cla2server_SSLRequired should be enclosed within quotes as shown above.

To enable authentication and SSL for the CLA2 adapter, select the System Authentication Certificate as cla2auth and SSL Public CA Certificate as cla2ssl on the Adapter configuration.

CLA2 TLS Configurations

To configure CLA2 to use TLS 1.2 or TLS 1.3 protocols, ensure the following properties are added to the setup.Cfg section of values.yaml:

PROPERTY_cla2server_CLA2TLSVersion: TLSv1.3, or
PROPERTY_cla2server_CLA2TLSVersion: TLSv1.2

Once configured, proceed with a Helm install/upgrade.