IBM Support

Updates to IBM App Connect Enterprise and IBM Integration Bus that have led to changes in default configuration or behaviour

Product Documentation


Some APARs and component upgrades have result in necessary changes to default configuration or behaviour in IBM App Connect Enterprise and IBM Integration Bus, which might require extra migration steps when upgrading to a later fixpack


The table specifies the minimum versions of IBM App Connect Enterprise and IBM Integration Bus, where the changes apply:

v12 v11 v10 v9
APAR IT38070. Any user of the iibswitch component on IIB or below, or ACE or below will not be able to connect to a Switch server running on IIB or above, ACE or above, or ACE or above.
Local fix: Upgrade to one IIB or above, ACE or above, or ACE or above.
See Release Notes for full details or below or below
APAR IT37741. On Linux on zSeries, must be run on a CPU that has the Message Security Assist (MSA) extension 4. There is currently no fix other than to install on a level on Linux on zSeries where the CPU contains the Message Security Assist (MSA) extension 4. N/A N/A
APAR IT35898 changes the default value of EnableLookups property in integration node listener and integration server (embedded) listener to 'false' in App Connect Enterprise V11.0. The EnableLookups property value of 'true' caused, in some systems, the DNS lookup to take more time resulting in poor performance for HTTPInput and SOAPInput node-based integration flows N/A N/A
APAR IT14173 introduced a change to prevent the use of invalid storage by intentionally increasing the lifespan of some parser elements. This change in behaviour can result in an additional memory requirement. N/A
Security vulnerabilities in WebSphere Message Broker and IBM Integration Bus that have led to changes in the default configuration N/A

Policies explicitly referenced by message flows and message flow nodes must be deployed in the default policy project for the integration server. Except when the message flow or message flow node property explicitly names the policy project that uses the "{project-name}:policy-name" syntax on the property. The default policy project name is "DefaultPolicies" and this name can be modified by using the 'policyProject' attribute in the server.conf.yaml file for an integration server. Policies created by using the mqsicreateconfigurableservice command are automatically placed into the "DefaultPolicies" policy project for the integration node. N/A N/A
Fix for security vulnerability APAR IT25079 makes a change that can impact users of CICS XA on distributed UNIX or Linux systems. As a result, the user running the MQ queue manager responsible for coordinating global transactions must be part of the mqbrkrs group. N/A adds support for ODBC CONNECTIONS TO ORACLE 12C RELEASE 2. With this fixpack, the default value for the connection property EnableNCharSupport changes from EnableNcharSupport=0 to EnableNcharSupport=1. This can result in a string truncation error when working with CLOB column data against a UTF-8 Oracle database. Data types NCHAR, NVARCHAR, NVARCHAR2, and NCLOB on Oracle are not supported and it is recommended that you explicitly disable this connection option. Instructions are supplied under APAR IT25238.
The version of Java shipped with the product on Linux (x64, Z, PPC & PPCLE), AIX & Windows is upgraded from Java 7.1 to Java 8. Java 8 is added as a supported version for z/OS. See IBM Integration Bus v10 support for Java 8 for known issues associated with the JRE upgrade. N/A N/A
Invalid characters not allowed by RFCs 7230 & 3986 are no longer permitted in an HTTP request URL received by IIB/WMB. As a result, you observe 'HTTP/1.1 400 Bad Request' errors from your client if special characters are present in the URL/query string. To recover from such failure and errors, special characters in the following list must be percentage encoded: ' ',",#,<,>,\,^,`,{,|,}. N/A changes the level of the JMS interface that is used by default from JMS 1.1 to JMS 2.0. This can result in the failure to load JMS Provider clients that are not compatible with the JMS 2.0 interface. This change in default behaviour can be reverted by setting the environment variable MQSI_JMS_INTERFACE_VERSION_1 to any non-null value prior to starting the Integration Node. N/A N/A
IT07291 / IT10385 - APARs IT10385 and IT07291 introduce changes to XA handling for JMS and JDBC that require extra migration steps when upgrading to a fixpack which includes the APARs. N/A
If the integration node function level is set to or later, or all, then the XML format REST responses to the apiv1 admin api now include namespaces. This makes responses incompatible with previous responses if they are parsed using a namespace aware XML parser. N/A N/A
IT01950 - ESQL no longer allows propagation from within FOR loop. N/A
PI17122 - FileOutput Node no longer creates files with world writeable permissions. N/A

[{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Migration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"10.0;9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Migration","Platform":[{"code":"","label":""}],"Version":"7.0;8.0","Edition":"All Editions","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"Migration","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 May 2022