ITX Container Integration with Sterling B2B Integrator

Linux x64 IBM Certified Container
Certified Container image is in IBM Entitled Registry
Image Registry: cp.icr.io/cp
Image Name: ibm-itx-rs
Image Tag: 10.1.1.1.20221116
Image Digest: sha256:d6dea7cad255582d091f91c7ab226d819ce105a4146b9ac706d96262dd929afc

• Create the required PVs for ITX integration if ITX integration is required.
• Configure values.yaml to enable ITX integration flag.
• Confirm datasetup configuration is enabled for ITX in values.yaml.
• Install Sterling B2B Integrator Helm charts.
• See Integrating ITX with Sterling B2B Integrator for a complete installation guide.

1. You need two PVs, which are data and logs.

   Under Data PV, the following folders are automatically created:

   /data/maps contains compiled maps. By default, the maps must have the .lnx file extension. If a map references a file relative to the map directory, that file must reside in the directory relative to this directory. Likewise, if a map creates a file without specifying a directory, that file will be created in the map directory. If a map runs other maps, those maps must reside in the same directory and must be saved under the exact names, including file extensions, under which they are referenced in the main map. To ensure that all instances of the container have access to the same maps when those instances are running on different hosts, this location must be accessible on all hosts, for example, it can be an NFS share.
   /data/tmp contains temporary execution files.
   /data/extra contains any additional shared libraries and JAR files to make available to the running container, such as, for example, JDBC driver JARs for use with the JDBC adapter. You can also list JAR files and directories in the dtx.ini configuration file.
   Logs PV will hold the log files generated by the ITX runtime.
   /logs contains log files produced by the ITX runtime.
2. The following parameters are added in values.yaml:

   integrations:
     seasIntegration:
       isEnabled: false
       seasVersion: "1.0"
     itxIntegration:
       enabled: false
       dataSetup:
         enabled: true
       image:
         repository: "cp.icr.io/cp/ibm-itx-rs"
         tag: "10.1.1.1.20221116"
         digest: "sha256:d6dea7cad255582d091f91c7ab226d819ce105a4146b9ac706d96262dd929afc"
         pullPolicy: IfNotPresent
         pullSecret:
       dataPVC:
         name: itxdata
         useDynamicProvisioning: true  
         storageClassName: ""
         selector:
           label: "intent"
           value: "itxdata"
         accessMode: ReadWriteMany
         size: 100Mi
         preDefinedDataPVCName:
       logsPVC:
         name: itxlogs
         useDynamicProvisioning: true
         storageClassName: ""
         selector:
           label: "intent"
           value: "itxlogs"
         accessMode: ReadWriteMany
         size: 100Mi
         preDefinedLogsPVCName:
       # Logging settings
       log:
         includeHostInLogNames: true
         jniLog:
           # Supported levels are "none", "failures", "info" and "all". Default is "none".
           level: "none"
         cmgrLog:
           # Supported levels are "none", "failures", "info" and "all". Default is "none".
           level: "none"
    

3. Enable ITX integration with Sterling B2B Integrator by updating the properties below in values.yaml file in the Sterling B2B Integrator Helm charts.

   
   itxIntegration:
      enabled: true

4. Enable datasetup one time, perform Helm install or upgrade, and then set the datasetup property to false.
   Note: You need to have required service created in Sterling B2B Integrator for ITX integration i.e. ITX Map Service and this is required to function the integration properly.

   
   itxIntegration:
    enabled: true
    dataSetup:
     enabled: true
   

5. Add respective image details like repository, tag, digest, pullPolicy, and pullSecret for the itxIntegration section in values.yaml.
6. Specify PVC configuration for data and logs for ITX integration.

   
       dataPVC:
         name: itxdata
         useDynamicProvisioning: true  
         storageClassName: ""
         selector:
           label: "intent"
           value: "itxdata"
         accessMode: ReadWriteMany
         size: 100Mi
         preDefinedDataPVCName:
       logsPVC:
         name: itxlogs
         useDynamicProvisioning: true
         storageClassName: ""
         selector:
           label: "intent"
           value: "itxlogs"
         accessMode: ReadWriteMany
         size: 100Mi
         preDefinedLogsPVCName:

   Under data PV, the maps folder will be created post ASI or AC pod starts, and this is where we should copy the required set of maps used by the WTX Map service.

   The log files generated by the ITX runtime will be stored under Logs PV.

7. For ITX integration, you can configure the ITX runtime logging configuration in the below section.

   
     log:
         includeHostInLogNames: true
         jniLog:
           # Supported levels are "none", "failures", "info" and "all". Default is "none".
           level: "none"
         cmgrLog:
           # Supported levels are "none", "failures", "info" and "all". Default is "none".
           level: "none"

itxIntegration:
 enabled: false
 

1. You can find the required WTX adapters in the jars or libs folder inside the ASI and AC pods, under /ibm/integrations/itx/opt/runtime. You can add these jars to the SI classpath as follows:
   Note: From Sterling B2B Integrator v6.2.0.1 and above, you can find the required WTX adapters in the jars or libs folder inside the ASI and AC pods, under /opt/runtime.
   • Copy the /ibm/b2bi/install/properties/dynamicclasspath.cfg.in file to the persistent volume.
   • Make the necessary modifications to this copied file and place the file in the config folder in the Sterling B2B Integrator Helm charts.
   • If required, shuffle the jars and change the order in dynamicclasspath.cfg.in.
   • Perform Helm upgrade.
2. In the case of third-party Jar:
   • Use the customization UI to deploy the Jar.
   • Follow the above process if you want to change the order of the jars.

• Sterling B2B Integrator v603x with ITX 10.0.3 (IM) is upgraded to Sterling B2B Integrator 6200 with ITX 10.1.1.1 in OCP.
• Sterling B2B Integrator 601x with ITX 10.0.3 (IM) is upgraded to Sterling B2B integrator 6200 with ITX 10.1.1.1 in OCP.
• Sterling B2B Integrator 611x with ITX 10.0.3 (IM) is upgraded to Sterling B2B integrator 6200 with ITX 10.1.1.1 in OCP.