Known issues in Sterling B2B Integrator
Last Updated:
2025-11-12.
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.
The following sections provide a list of Known Issues specific to every version:
- 2.1.x
- 2.1.1
List of known issues for v6.2.1.x
The following list of known issues apply to Sterling B2B Integrator v6.2.1.0 and later.
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. 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. Upgrading IBM Sterling B2B Integrator from v6.0.0.8 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 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 Use the response file to install or upgrade Sterling B2B Integrator to v6.2.1.0. |
ITXA Integration | In an IIM Sterling B2B Integrator and ITXA setup, SSO will not work in Sterling B2B Integrator v6.2.0.0-ITX 10.1.1.1-ITXA 10.0.1.7 setup and prior ITXA releases. Although SSO is not working, it will not affect the E2E runtime flows | To use the ITXA UI: 1) Comment the following properties in customer.overrides.props to ensure ITXA is a run as a standalone environment: —SI-SPE Integration —HostApplication.name=SBI —HostApplication.migrationStylesheet=ie_si_to_spe_hosted —HostApplication.driverName=InvokeSIBP —HostApplication.driverClass=com.ibm.spe.core.drivers. DriverInvokeSIBusinessProcess —HostApplication.restURL=https://<hostname>:<base port+60>/restwar/restapi/v1.0 2) Restart the ITXA TPUI server. Note: To return to integration mode with Sterling B2B Integrator, uncomment the above properties and restart the ITXA TPUI server. |
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. |
myFileGateway 2.0 | 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: | |
myFileGateway 2.0 | 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. Login to myFileGateway 2.0. |
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. 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. |
Business Process as a Service (BPaaS) | Business process fails with the following error: Processing error has occurred. Please contact the system administrator and check logs for more details: java.lang.IllegalStateException: This key is no longer valid | To resolve this issue, update Sterling B2B Integrator Liberty server’s JVM options to include the required JAR file, then restart the server: 1) Stop Sterling B2B Integrator Liberty server. Use either of the following methods: —Run: kill -9 <SILibertyPID> —Run: hardstop.sh 2) Update JVM options by navigating to <SI_InstallDir>/liberty/wlp/usr/servers/SIServer and add the following line to jvm.options: -Xbootclasspath/a:/liberty/wlp/usr/servers/SIServer/apps/APIjarsLib/bcprov-jdk18on-1.78.1.jar 3) Restart Sterling B2B Integrator Liberty server. Use either of the following scripts: —startLiberty.sh —run.sh |
ASI Pod | ASI pod keeps restarting on zlinux. | To resolve the issue, perform the following steps: 1) Update the jvmOptions flag for ASI, AC, and API pods as follows: jvmOptions: -Djdk.tls.namedGroups=secp256r1,secp384r1 Perform a helm upgrade. |
List of known issues for v6.2.1.1
The following list of known issues apply to Sterling B2B Integrator v6.2.1.1:
Functionality | Known Issue | Workaround |
Certified Containers - Adapters and Business Processes (BPs) | When you edit adapters or BPs in a certified containers environment, the process may occasionally become unresponsive or freeze. | To fix this issue, perform the following steps: 1) Copy the file centralops.properties.in outside the pod or to the resources mount location. Use the following command: kubectl/oc cp <namespace>/<asi-pod>:/ibm/b2bi/install/properties/centralops.properties.in <dir location>/centralops.properties.in Note: Replace <dir location>with the desired destination path. 2) Update the property libertyJndi=false in the copied file. 3) Put the updated file in the <helm-charts>/config folder directory. Perform a Helm upgrade. |
Known Issues
Last Updated: 2025-11-12
This topic lists the known issues in Global Mailbox. Before you use Global Mailbox, you must ensure to understand the known issues that might need you to follow certain workarounds for smooth functioning.
Functionality | Known Issue | Workaround |
Installation | Starting all Global Mailbox servers simultaneously during initial setup can lead to replication failures. | Global Mailbox servers must be started one at a time during initial setup. |
Upgrade | After upgrading Sterling B2B Integrator or Global Mailbox from v6.1.0.x to 6.2.1.x, the configurations for securing Cassandra JMX will be lost. | You must reconfigure Cassandra to secure the JMX connections. For more information, see Securing Cassandra JMX. |
Initial setup | There are port conflict errors or security concerns observed for the port number 9160. It is the port number used by Thrift RPC server in Cassandra. | Cassandra doesn’t use the Thrift RPC server any longer. If you face security concerns or any other issue on the port number 9160, you can edit the cassandra.yaml from the location <cassandra install location>/conf and set start_rtc:false. |
Initial setup | When trying to start admin servers at the same time during the initial setup, a 1970 date is written into the replication_queue_ptr table in the database and files are not replicated. | Start Global Mailbox Admin servers one at a time during the initial setup (while the replication_read_ptr table is empty or after it has been truncated). After the initial setup, you can start Global Mailbox Admin servers at the same time. |
Administrator user interface | The administrator UI for Global Mailbox cannot be reached from the Sterling B2B Integrator administrator UI when all replication servers in a data center are manually suspended. Error dialogs indicate the Global Mailbox client adapter cannot be found. | Administrative activity for Global Mailbox must be performed by directly accessing the Global Mailbox administrative UI. |
ASCP | ASCP frequently generates logs about session shutdown failures. | Ignore Session shutdown failure errors. This is a normal condition. |
Standby queue manager | The Event Rule Adapter configuration shows an empty value for the Connection Name list rather than listing the active and standby queue managers.. | Configure the Global Mailbox Event Rule Adapters in Sterling B2B Integrator to use a connection list with both the active and standby queue managers in the list. You should only list queue managers in the same datacenter as the Sterling B2B Integrator node that you are configuring |
Performance | Due to limitations in the Cassandra Repair jobs, Global Mailbox can process 500,000 messages per day. The highest measured peak throughput with Global Mailbox is 70 messages per second. Each Global Mailbox server consumes 1 CPU core while idle. | If your production environment must support a higher load of messages per day, contact IBM Support. If your production environment must support a higher load of messages per day, contact IBM Support. Allocate sufficient CPU resources to all servers. |
Non-English topics | Information about firewall configuration was not translated. | Ensure that your firewalls are configured to allow connections to the ports for ZooKeeper, Cassandra, Global Mailbox Management, MQ, and Sterling B2B Integrator nodes. |
Non-English topics | Updated information about recovering from a planned or unplanned data center outage was not translated. | Use the English version of the topics Restarting Cassandra nodes after data center maintenance and Restarting the Global Mailbox management node. |
Non-English topics | Updated information for configuring advanced event processing was not translated. | Use the English version of the topic Configuring IBM MQ advanced event management. |
Upgrading Global Mailbox 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 Use the response file to install or upgrade Sterling B2B Integrator to v6.2.1.0. |
