Known Issues

Edit online

This topic lists the known issues in Sterling B2B Integrator.

Before you use Sterling B2B Integrator, you must ensure to understand the known issues that might need you to follow certain workarounds for smooth functioning.

List of known issues for v6.2.1.0

Functionality Known Issue Workaround
Installation of IBM® Sterling B2B Integrator using IBM Installation Manager (IIM) When installing IBM Sterling B2B Integrator on RHEL 9.x OS based on x86-64 and Power 10 little endian hardware, GTK package versions greater than 3.22.30 cause some checkboxes and radio buttons to appear incorrectly. This is due to an IIM limitation. Before launching IIM, ensure that the GTK package version in the OS is 3.22.30.
SAP Suite Adapter for JCo3x When configured for adapter containers, SAP Suite Adapter for JCo3x remains disabled.
Note: This issue is applicable only for certified container images.
No workaround.
Azure SQL Database When Sterling B2B Integrator v6.2.1.0 and higher is installed with Azure SQL Database, running the dump_info.cmd script results in an error. No workaround.
Upgrading IBM Sterling B2B Integrator from v5.2.6.3_x to v6.2.1.0. Upgrading IBM Sterling B2B Integrator from v5.2.6.3_x (or lower) to v6.2.1.0 fails due to v5.2.6.3_x running on JDK 7.
  1. Stop the Sterling B2B Integrator instance v5.2.6.3_x or lower.
  2. Run the command: upgradeJDK.sh <path to IBM JDK 8.0.6.20> <path to JCE policy File>
  3. Upgrade IIM to v1.10.1.
  4. Using the upgraded IIM, upgrade Sterling B2B Integrator to v6.2.1.0. This can be done using the GUI mode or by using a response file, while specifying IBM Semeru Runtime Certified Edition 17.0.14.0 (build 17.0.14+7).
Upgrading IBM Sterling B2B Integrator with NIST enabled. Upgrading IBM Sterling B2B Integrator from v5.2.6.5_x to v6.2.1.0 fails.
  1. Disable NIST by setting NIST_MODE=off in sandbox.cfg.
  2. Run the command:

    deployer.sh or deployer.cmd

  3. Perform the upgrade to v6.2.1.0.
  4. Re-enable NIST by setting NIST_MODE=strict after completing the upgrade.
Upgrading IBM Sterling B2B Integrator from v6.0.0.8 to v6.2.1.0 fails.
Upgrading IBM Sterling B2B Integrator on AIX
  • IIM v1.10.1 and IBM Packaging Utility no longer support 32-bit architecture on AIX systems.
  • Starting with release 1.10.1, IIM requires 64-bit Version 11 Java and does not provide GUI support for AIX. Users on a 32-bit platform must transition to a 64-bit platform to install or upgrade to version 1.10.1.
For users already on a 64-bit platform, the reInstallIM command can be used to transition IIM from a 32-bit to a 64-bit architecture:
  1. To perform this upgrade, run the command: ./userinstc -reinstallIM -acceptLicense
  2. Use the response file to install or upgrade Sterling B2B Integrator to v6.2.1.0.
myFileGateway 2.0

While installing Sterling B2B Integrator using the IBM Installation Manager, if myFileGateway 2.0 is hosted on multiple HTTP Server Adapter on AC and ASI nodes, you must access the adapter configured in sandbox.cfg.

The following properties contain the information of the configured adapters in sandbox.cfg:
ASI_SERVICE_HOST = CHANGEME
ASI_SERVICE_PORT = CHANGEME
MYFG_PROTOCOL=http
Tip: Value for MYFG_PROTOCOL can be http or https.
No workaround.

While installing Sterling B2B Integrator using Certified Container, if myFileGateway 2.0 is hosted on multiple HTTP Server Adapter on AC and ASI nodes, then you must access the adapters configured in values.yaml.

The following properties contain the information of the configured adapters in values.yaml.

myFgAccess:
        myFgPort:
        myFgProtocol:
Unable to login to myFileGateway 2.0 in zLinux.
IIM:
  1. Update the JVM options in bin/tmp.sh.
  2. Modify the JAVA_FLAGS variable as follows: JAVA_FLAGS="-Djava.io.tmpdir=/B2B/IBM/SI_6210/tmp -Djdk.tls.namedGroups="secp256r1,secp384r1""
  3. Restart the server.
  4. Login to myFileGateway 2.0.

Certified Container:

To resolve the issue with HTTPS access to dashboard when the parameter useSslForRmi is set to true and the myFileGateway 2.0 login issue:
  1. Update the jvmOptions flag for ASI, AC, and API pods as follows: jvmOptions: -Djdk.tls.namedGroups=secp256r1,secp384r1
  2. Perform a helm upgrade.
  3. Login to myFileGateway 2.0.
Out-of-the-box (OOTB) Adapters When upgrading from Sterling B2B Integrator v6.1.2.x IIM to 6.2.1.0 container deployment, the OOTB adapter ports do not update according to the base port values specified in values.yaml. Manually update the REST HTTP Server Adapter port with the value: base port + 60.
SWIFTNet7 Adapter SWIFTNet7 adapter fails to restart if the connection is lost on AIX MEFG deployment.

This issue persists only on SWIFTNet 7.7.

 Manually restart the SWIFTNet7 adapter to recover from a connection loss.
FIPS 140-3 FIPS 140-3 Strict mode is unsupported. No workaround.
Hardware Security Module (HSM) The keys created on the nCipher HSM device using earlier Sterling B2B Integrator versions with the IBM PKCS11 provider do not work in version 6.2.1.0. No workaround.
Sterling B2B Integrator API Server API Server fails to load.

This issue occurs when the property noapp.retain.libertyProps.customization is set to true in customer_overrides.properties, and Sterling B2B Integrator is upgraded to v6.2.1.0.

This issue does not occur if the property is not set or set to false.

Set noapp.retain.libertyProps.customization=false in customer_overrides.properties before performing the upgrade.
Note:
  • This setting will reset the configurations in server.xml to the default values. Any customizations made to the server.xml must be manually re-applied after the upgrade.
  • Features that are unsupported in Jakarta EE Web Profile 10.0 will fail. For more information, see Jakarta EE Web Profile 10.0 documentation.
ITX/ITXA Integration ITX/ITXA Integration is unsupported in this release. No workaround.