Known Issues

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.

The following sections provide a list of Known Issues specific to every version.

List of known issues for v6.1.2.0

Functionality Known Issue Workaround
Installation Special characters cannot be used for creating database passwords. For information on the list of unsupported characters see, Unsupported Characters List. No workaround available.
Installation of IBM® Sterling B2B Integrator using Certified Container JMX Monitoring is not supported in certified container deployments. No workaround.
Apache log4j 1.x You can still find Apache log4j 1.x jars in Installed_data, uninstall, and packages folder. For more details, refer to Consideration for Third Party Jars which reference Apache log4j 1.x.
Note: This known issue is not applicable to the container images.
You should ignore these references as they are not used in runtime and thus will not cause any security threat.
myFileGateway 2.0 The swagger UI is not accessible in myFileGateway 2.0 with all DBs in an SSL-enabled mode with older versions of DB driver jars.
You must use the following drivers to access swagger UI in myFileGateway 2.0:
  • Oracle - ojdbc8.jar with v19.3 and later versions.
  • MSSQL - mssql-jdbc-8.4.1.jre8.jar Bundle-Version: 8.4.1.
  • DB2 - db2jcc4_11.5.jar Bundle-Version: 1.4.0.
    For example, install the db2jcc4_11.5.jar for DB2 v11.5 driver and replace the jdbc.url in cfgapi.properties file with the following:
    
    jdbc:db2://<DB IP>:<DB Port>/<DB Name>:sslConnection=true; 
    sslTrustStoreLocation=<truststore path>;
    sslTrustStorePassword=<truststore password>
    

List of known issues for v6.1.2.1

Functionality Known Issue Workaround
AIX Installing IBM Sterling B2B Integrator v6.1.2.1 or direct OS upgrades (new folder upgrade) from the previous JDK version on an AIX system results in Java core dumps and the installation failing. This is due to issues with the AIX JDK's JIT compiler. Install IBM Sterling B2B Integrator v6.1.2.2 using AIX JDK 8.0.7.15 from the following Fix Central link: ibm.com/support/fixcentral/
Installation of IBM Sterling B2B Integrator using Certified Container JMX Monitoring is not supported in certified container deployments. No workaround.

List of known issues for v6.1.2.2

Functionality Known Issue Workaround
AIX Installing IBM Sterling B2B Integrator v6.1.2.2 or direct OS upgrades (new folder upgrade) from the previous JDK version on an AIX system results in Java core dumps and the installation failing. This is due to issues with the AIX JDK's JIT compiler. Install IBM Sterling B2B Integrator v6.1.2.2 using AIX JDK 8.0.7.15 from the following Fix Central link: ibm.com/support/fixcentral/
AIX 7.3 Installing IBM Sterling B2B Integrator v6.1.2.2 or direct OS upgrades (new folder upgrade) from the previous JDK version on an AIX system results in Java core dumps and the installation failing. This is due to issues with the AIX JDK's JIT compiler. To install/upgrade IBM Sterling B2B Integrator from an older version to v6.1.2.2 on AIX 7.3:
    • If you are performing a fresh installation: Install v6.1.2.0 using IIM v1.9.1.
    • If you are upgrading from an older version: Perform an intermediate upgrade to v6.1.2.0 using IIM v1.9.1.
  1. Upgrade the IIM to v1.9.2.3.
  2. Install IBM Sterling B2B Integrator v6.1.2.2.
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 v1.9.2.3 limitation. Before launching IIM, ensure that the GTK package version in the OS is 3.22.30.
Installation of IBM Sterling B2B Integrator using Certified Container JMX Monitoring is not supported in certified container deployments. No workaround.
Upgrading IBM Sterling B2B Integrator from v5.2.6.3_x to 6.1.2.2. Upgrading IBM Sterling B2B Integrator from v5.2.6.3_x (or lower) to 6.1.2.2 fails due to v5.2.6.3_x running on JDK 7.
  1. Stop the Sterling B2B Integrator v5.2.6.3_x (or lower) instance.
  2. Run the command: upgradeJDK.sh <path to IBM JDK 8.0.6.20> <path to JCE policy File>.
  3. Using IIM, upgrade Sterling B2B Integrator to v6.1.2.2 by using the GUI mode or by using a response file while pointing to IBM JDK 8.0.7.15.
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.

List of known issues for v6.1.2.3

Functionality Known Issue Workaround
Cassandra node Whenever a pre-v6.1.2x system, i.e., v6.0.3.x, 6.1.0.x, or 6.1.1.x is upgraded to v6.1.2.x, there is an issue with Cassandra nodes communicating within a cluster. Since v6.1.2.x onwards, we have Cassandra version 4.x and before v6.1.2.x, we had Cassandra version 3.x. The Cassandra version 4 node is not able to communicate with the Cassandra version 3 node, resulting in a LOCAL_QUORUM Error and file transfer failures.
Once the Cassandra node is upgraded to v4.x from v3.x, before starting this node, edit the cassandra.yaml file and add the below property in the server_encryption_options section:
enable_legacy_ssl_storage_port: true
Example:
server_encryption_options:
internode_encryption: none
keystore: conf/.keystore
keystore_password: cassandra
truststore: conf/.truststore
truststore_password: cassandra
enable_legacy_ssl_storage_port: true

Once the property is added, you can start the Cassandra node.

You can repeat the same process for all the Cassandra nodes.

Installation of IBM Sterling B2B Integrator using Certified Container JMX Monitoring is not supported in certified container deployments. No workaround.

List of known issues for v6.1.2.5

Functionality Known Issue Workaround
Import/Export of EBICS resources If EBICS resources are exported prior to v6.1.2.5 upgrade and then imported into upgraded environments, the EBICS version displayed may be limited to only four characters. It is recommended to export EBICS resources after v6.1.2.5 upgrade, and then import these resources in newer environments (v6.1.2.5 or later).