Resolved issues

This topic provides information about the issues that are resolved in Sterling B2B Integrator.

Table 1. Resolved Issues
APAR Description
IT24560

SOA outbound security service creates a corrupted Subjectkeyidentifier entry for short subject keys.

IT24323

Add aes-ctr support that is FIPS compliant in IBM Sterling B2B Integrator.

IT19818 XSS vulnerability in the queuewatcher.
IT25571 Perimeter Server should allow the user to set keepalive values.
IT25347

The tuning.properties are overwritten with the default values.

IT24202

Cannot use "ws" in the host name of the IBM Sterling B2B Integrator Cluster environment.

IT24502

The workflowlauncher.sh/cmd returns invalid wfstatus = -1 when the wf_id exceeds 2152047493.

IT24548

The Alert service fails when the workflow id is greater than 2147483648.

IT20159

The column in table used for Connect:Direct Server Adapter is set to small for large workflows (over 10 digits)).

IT19004

Upgrade to V5261 fails but the logs do not provide any information about the failure.

IT19018

IBM Sterling B2B Integrator gets installed to <installlocation>\install when using IIM.

IT17399

Sap suite 3 idoc metadata builder allows passwords only with a maximum of 8 alphanumeric characters and upper case letters.

IT19020

When installing IBM Sterling B2B Integrator using IIM, a temporary silent installation file containing clear text passwords is created.

IT20158

Connect:Direct Server session sets workflow ID incorrectly in the session record when the workflow ID has 10 or more digits.

IT16890

Run .sh reports "gdha_start_script: not found" after installing the IBM® B2B Advanced Communications module.