IBM Support

IBM App Connect Enterprise Version 11.0 release notes

Release Notes


Abstract

This document contains the release notes for IBM App Connect Enterprise Version 11.0, including the tooling and runtime components.

Content

Release Notes file for: IBM App Connect Enterprise
Product release: 11.0

Update name: 11.0.0.26
Document first published: 04 April 2018
Document last modified: 30 April 2024

Versions and fix packs:

* V11.0.0.0 (electronic availability 30 March 2018)

* Fix Pack V11.0.0.1 (electronic availability 14 August 2018)

* Fix Pack V11.0.0.2 (electronic availability 16 October 2018)

* Fix Pack V11.0.0.3 (electronic availability 19 December 2018)

* Fix Pack V11.0.0.4 (electronic availability 27 March 2019)

* Fix Pack V11.0.0.5 (electronic availability 28 June 2019)

* Fix Pack V11.0.0.6 (electronic availability 03 October 2019)

* Fix Pack V11.0.0.7 (electronic availability 16 December 2019)

* Fix Pack V11.0.0.8 (electronic availability 19 March 2020)

* Fix Pack V11.0.0.9 (electronic availability 28 May 2020)

* Fix Pack V11.0.0.10 (electronic availability 26 August 2020)

* Fix Pack V11.0.0.11 (electronic availability 17 December 2020)

* Fix Pack V11.0.0.12 (electronic availability 30 March 2021)

* Fix Pack V11.0.0.13 (electronic availability 08 June 2021)

* Fix Pack V11.0.0.14 (electronic availability 24 August 2021)

* Fix Pack V11.0.0.15 (electronic availability 25 October 2021)

* Fix Pack V11.0.0.16 (electronic availability 21 January 2022)

* Fix Pack V11.0.0.17 (electronic availability 18 March 2022)

* Fix Pack V11.0.0.18 (electronic availability 01 June 2022)

* Fix Pack V11.0.0.19 (electronic availability 09 September 2022)

* Fix Pack V11.0.0.20 (electronic availability 27 January 2023)

* Fix Pack V11.0.0.21 (electronic availability 18 May 2023)

* Fix Pack V11.0.0.22 (electronic availability 31 July 2023)

* Fix Pack V11.0.0.23 (electronic availability 29 September 2023)

* Fix Pack V11.0.0.24 (electronic availability 30 November 2023)

* Fix Pack V11.0.0.25 (electronic availability 14 March 2024)

* Fix Pack V11.0.0.26 (electronic availability 30 April 2024)

Contents

Accessing the latest version of the release notes

Always use the latest version of this release notes file, which is available in English only at: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006913

Translated release notes files are available at: ftp://public.dhe.ibm.com/software/integration/integrationbus/docs/

Prior to installation

Accessing the online product documentation
For information about any tasks you must complete before you install the product, refer to the IBM App Connect Enterprise Version 11.0 documentation.

System requirements
Check the IBM App Connect Enterprise system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For information about the system requirements for all of the different versions of the product, see the IBM App Connect Enterprise system requirements website.

Downloading the product from the IBM Passport Advantage website:
For information about downloading IBM App Connect Enterprise V11.0 installation images from the Passport Advantage website, see the IBM Passport Advantage website.

Before installing 11.0.0.22 and above on AIX

The minimum OS for AIX has changed to

  • AIX 7.2.TL5 SP5

The following prerequisites for AIX have changed to

  • IBM Open XL C/C++ 17.1.1.4
  • GCC 8.3

Before installing 11.0.0.14 and above

Apar IT38070.  All users must upgrade to be able to communicate with IIBSWITCH servers running IIB 10.0.0.25+, ACE 11.0.0.14+ or 12.0.2.0+ or App Connect on IBM Cloud

Description:

The switch is a component of IIB and ACE which is able to securely route data and administration commands between integration servers, an App Connect Dashboard instance, and IBM App Connect on IBM Cloud.

There are four clients which interact with a switch server, depending on the type of  interaction: "AgentA "AgentC", "AgentP", and "AgentX"

  •  AgentA - Connection agent used for remote administration. This is used to allow an App Connect Dashboard instance to remotely administer an integration server (see "Configuring an integration server to connect to an IBM App Connect Dashboard" in the IBM Documentation for App Connect Enterprise)
  •  AgentC - Connection agent for cloud systems. This is used to allow remote debugging of ACE integration servers running in IBM App Connect Enterprise on IBM Cloud (see "Remote debugging hybrid integration solutions with the App Connect toolkit" in the IBM Documentation for App Connect on IBM Cloud)
  •  AgentP - Connection agent for on-premises systems. This is used to establish secure connectivity between message flows running in IBM App Connect Enterprise on IBM Cloud and on-premises systems such as SAP, databases, and IBM MQ (see "Secure connectivity between integration servers in App Connect on IBM Cloud and on-premises systems" in the IBM Documentation for App Connect on IBM Cloud)
  •  AgentX - Connection agent for remote callable flows. This is used to allow callable flows on integration servers to be called remotely from other integration servers, be they on-premises or in the cloud.

A BIP2206 message is issued by an integration server whenever one of these four agents is started

Any user of these agents on IIB 10.0.0.23 or below, or ACE 11.0.0.10 or below will not be able to connect to a Switch server running on IIB 10.0.0.25 or above, ACE 11.0.0.14 or above, or ACE 12.0.2.0 or above. Attempting to do so will result in the following error messages being seen depending on which agent is being used:
  •  AgentA - BIP6488 or BIP6489
  •  AgentC - BIP6467 or BIP6468
  •  AgentP - BIP6472 or BIP6473
  •  AgentX - BIP6453 or BIP6454

Local Fix:

Upgrade to one IIB 10.0.0.24 or above, ACE 11.0.0.11 or above, or ACE 12.0.1.0 or above.
Customers using iibswitch clients to connect to App Connect on Cloud should update as soon as possible.
The planned date when App Connect on Cloud will stop supporting older clients is 31 January 2022.

Product documentation

The online product documentation can be found in IBM Knowledge Center. See IBM App Connect Enterprise Version 11.0 documentation.

In IBM App Connect Enterprise Version 11, the IBM App Connect Enterprise Toolkit help is configured to display help topics that are hosted in the online product documentation. However, you can download a local version of the product documentation and configure the IBM App Connect Enterprise Toolkit to use this local source. For more information, see IBM App Connect Enterprise Toolkit.

Support

Defects:
This release notes file might contain references to defect numbers. These numbers refer to internal IBM problem numbers; you might find these numbers useful when discussing problems with your IBM service representative.

Technotes:
For current information about known problems and available fixes, see the IBM App Connect Enterprise support web page.

To find information, click Download, then Fixes, updates and drivers, then enter the product name. This web page provides links to the latest available maintenance for the in-service IBM App Connect Enterprise family of products.

Feature updates

To learn about the new features in IBM App Connect Enterprise V11.0, see What's new in Version 11.0?

Known problems and their workarounds (if any)

This section outlines the known problems and their workarounds (if any) in IBM App Connect Enterprise.

Description:

APAR IT46223 MEMORY LEAK FOR NODE OWNED INTEGRATION SERVERS WITH FLOW STATS, RESOURCE STATS, OR ADMIN LOG ENABLED ON 12.0.12.0 OR ABOVE. Refer to the APAR IT46223 for details of the scenarios affected. Ifixes are available from Fix Central to apply to:

Description:

Messages BIP2801E and BIP212E during Integration Server startup and shutdown

The following messages may be seen.

During integration server startup:

BIP2112E: IBM App Connect Enterprise internal error: diagnostic information 'Cannot load XAJmsJni library', 'java.lang.UnsatisfiedLinkError: XAJmsJni (Not found in java.library.path)

During integration server shutdown:

BIP2801E: Unable to load implementation file 'libXAJdbcJni.so', rc=Null pointer' during Integration Server shutdown

These messages are due to an issue in App Connect Enterprise 11.0.0.12 and later fixpacks where  libDynJMSSwitch.so, libXAJmsJni.so, libXAJdbcJni.so, and libJDBCSwitch.so are incorrectly dependent on system library libnsl.so.1.

To avoid issues related to the use of these libraries customers should ensure that libnsl.so.1 is available on their machine as described in How to install libnsl.so.1 in Red Hat Enterprise Linux 8.1

The dependency on this system library will be removed in a future fix pack

  • BIP2801E Null pointer is displaying when stopping Integration Server (#86297)

Description:

  • The original release of IBM App Connect Enterprise 11.0.0.4 for Microsoft Windows on x86-64 which was released on 27th March 2019 and available until 15th May 2019 did not include cryptographic signatures in the executables and libraries used by the ACE runtime (APAR IT29077)
This means that it is not possible to verify whether that the installed product on disk has been tampered with. This may have knock on effects with virus scanning programs reporting warnings or quarantining the executables and libraries included in ACE 11.0.0.4.
A new version of ACE 11.0.0.4 has been published to Fix Central and Passport Advantage which has been cryptographically signed correctly.
  • There is an issue with encryption on HTTPS communication that might require a fix for specific customer scenarios

Description:
If you are using IBM App Connect Enterprise V11.0  in an application that depends on FIPS-140 certified encryption for HTTPS communications, contact your IBM sales or client representative or raise a PMR for further advice.

  • Using an incorrect value for an environment variable will cause integration server start up to fail (#70235)

Description:
In the past, IBM Integration Bus v10 used the definition of environment variables (typically named MQSI_*) to dictate that the product exhibits legacy behaviors in situations where areas of default product behavior have changed over time, or for behaviors outside the normal use case. These variables are not typically documented and are usually provided during an IBM Service request. If a user tries to use an unsupported environment variable name (or makes a mistake while typing the name), integration servers will fail to start.

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • MQHeader node: Error in parser 'MQMD' while writing the field named 'PutDate' to the bit stream (#70295)

Description:
In some circumstances, message flows that contain the MQHeader node can generate exceptions BIP5912W and BIP2133E, and fail to update the MQMD fields correctly. Known workarounds are available by using other methods in a message flow (such as a Compute node).

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • MQHeader node: Error in parser 'MQMD' while writing the field named 'MsgId' to the bit stream (#70728)

Description:
In some circumstances, message flows that contain the MQHeader node can generate exceptions BIP5912W and BIP6106E, and fail to update the MQMD fields correctly. Known workarounds are available by using other methods in a message flow (such as a Compute node).

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • Problem with the mqsicreateexecutiongroup command when using an integration node with admin security enabled (#72907)

Description:
App Connect Enterprise v11.0.0.1 enables users to create integration nodes by using the mqsicreatebroker command. With such a node that has admin security enabled for Basic Authentication, and a web userid defined (by using the mqsiwebuseradmin command), if you execute the mqsicreateexecutiongroup command without sufficient privileges, the generic exception BIP8081E is returned rather than a specific authorization exception being reported.

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • HTTP and SOAP input nodes in flows that are deployed to the same server cannot mix and match between HTTP listeners that are embedded and node-wide (#73269)

Description:
App Connect Enterprise v11.0.0.1 enables users to create integration servers that are associated with an integration node. You can also specify the use of a node-wide HTTP listener. Having done this, if you deploy two message flows to the same integration server, one that uses an HTTPInput node using the embedded HTTP listener, and one that uses a SOAPInput node using the node-wide HTTP listener, whichever is started later will fail to register its URL and will not start.

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • Problem with the mqsideleteexecutiongroup command when using an integration node (#73290)

Description:
App Connect Enterprise v11.0.0.1 enables users to create integration servers that are associated with an integration node. When deleting such servers by using the mqsideleteexecutiongroup command, the delete operation takes 60 seconds and reports a timeout (BIP8081E) despite successfully deleting the server.

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

  • Starting an integration node with an admin REST API port that is already in use causes repeated failure to start (#73304)

If you try to start an integration node whose admin REST API port cannot be opened (for instance, if the port is already in use), the bipbroker process will issue the exception BIP3144 and terminate. Rather than starting successfully without the listener port started (for example, in order to allow administration across local named comms), the bipservice process will attempt to restart bipbroker, which (assuming the port is still unavailable) will repeatedly fail again.

This issue is fixed in IBM App Connect Enterprise v11.0.0.2

 
  • IIBv10 messages recorded using the flow exerciser need editing to inject successfully into ACEv11 (#74132)

If you have saved messages which were recorded using the IIBv10 Toolkit which you wish to inject using ACEv11 Toolkit, you can edit them to change the reference to the input node injection point which will be similar to FlowName#FCMComposite_1_1 to use the label of the input node.

This issue is fixed in IBM App Connect Enterprise v11.0.0.4

  • Toolkit problem deleting multiple applications at once from an integration node owned server (#74134)

From the ACE Toolkit Integration Explorer view, if you select two or more applications for deletion, a confirmation message is displayed which can be accepted, but the resources will not be deleted. To workaround this problem, delete the applications individually.

This issue is fixed in IBM App Connect Enterprise v11.0.0.3

  • Toolkit flow exerciser fails to send a message to a flow when using the integration node wide listener (#74218)

In cases where you are using the flow exerciser with an integration node with a default queue manager, HTTP message flow nodes will default to using the integration node wide HTTP listener on port 7080 and the flow exerciser will be unable to send them data. To work around this problem, use an alternate HTTP testing client (such as curl for example). You can still use the recording feature to then save the recorded message for re-injection using the flow exerciser in the Toolkit.

This issue is fixed in IBM App Connect Enterprise v11.0.0.4

  • Toolkit flow exerciser cannot send a message to an MQInput deployed to an integration node owned server (#74224)

In cases where you are using the flow exerciser with an integration node with a default queue manager, you will not be able to send messages to MQInput message flow nodes. To work around this problem, use an alternate MQ testing client (such as RFHUtil for example). You can still use the recording feature to then save the recorded message for re-injection using the flow exerciser in the Toolkit.

This issue is fixed in IBM App Connect Enterprise v11.0.0.3

  • The Toolkit Flow Exerciser fails to record messages for a message flow inside a static library under an application (#74983)

It is possible to deploy and run a message flow which is located within a static library which is referenced from an application, but when attempting to record messages using the Flow Exerciser you may receive an exception stating "com.ibm.etools.mft.broker.runtime.model.LibraryModel incompatible with com.ibm.etools.mft.broker.runtime.model.ApplicationModel".

This issue is fixed in IBM App Connect Enterprise v11.0.0.4

  • The mqsistop -i command does not always kill DataFlowEngine (#74997)

In some circumstances, the forced (immediate) stop variant of the mqsistop command ("mqsistop integrationNodeName -i") will not be successful in killing a DataFlowEngine process. If required, you can work around this issue by utilising the Operating System kill command force the DataFlowEngine process to stop.

This issue is fixed in IBM App Connect Enterprise v11.0.0.7

  • Message Flow level Statistics and Monitoring override states are not restored on restart / redeploy (#76467)

Message flow statistics and monitoring state which have been set at an individual message flow level, rather than at Application or Server level, are not being restored. This affects settings made via the command line (mqsichangeflowstats and mqsichangeflowmonitoring with the --flow parameter), via the Toolkit Monitoring and Statistics context menu and via the ACE administrative REST API (PATCH verb on an individual message flow resource)

This issue is fixed in IBM App Connect Enterprise v11.0.0.5

  • Unexpected shutdown when reading cross platform pre-generated BAR (#76082)

If you compile a BAR file on a Little Endian machine, such as using the Toolkit on a Windows platform, and then deploy it to the ACE runtime on a Big Endian zLinux machine, this can cause an unexpected shutdown of the integration server. This problem can be avoided by compiling the BAR file on the same runtime platform on which it is deployed.

This issue is fixed in IBM App Connect Enterprise v11.0.0.6

  • The SalesforceRequest node update operation has a problem with multiple records (#78565)
When updating Salesforce records using the SalesforceRequest message flow node, you are only able to update one record at a time. Therefore, an exception will be thrown by the SalesforceRequest node in the following situations:
1. User chooses "Update" on SalesforceRequest node and supplies a WHERE clause in the LocalEnvironment which resolves to multiple records.
2. User chooses "Update" on SalesforceRequest node and does not supply a Salesforce Id in the LocalEnvironment.
These capabilities are still available in earlier ACE fixpacks, and a fix is being worked upon for later ACE fixpacks. If you need this capability in ACEv11.0.0.6 please either change your message flow design to avoid the two situations documented above, or contact IBM Support for the latest information on this problem.
This issue is fixed in IBM App Connect Enterprise v11.0.0.8
  • User-Defined Properties (UDPs) on migrated message flows are not included in the administrative REST API responses (#78650)
ACEv11 supports users migrating message flows deployed to previous versions of IIB using the mqsiextractcomponents command. Message flows with UDPs defined, will run in ACEv11 as they did in previous versions. However, when using the administrative REST API to GET information about the deployed message flow, these UDPs will not be reported in the response sections named "userDefinedProperties" and "active"->"userDefinedProperties".  New UDP values which are updated using the "apply-global-udp-override" action are correctly reported.
  • An Integration Node fails to stop or stops immediately when requested using mqsistop from an earlier fixpack (#79754)
If a user tries to stop an Integration Node, which was started using 11.0.0.7 or later, but uses the mqsistop command from an 11.0.0.6 or earlier installation, then it is reported that the node has stopped, but it will actually likely still be running. To avoid this issue, simply use mqsistop from the same installation as was used to start the integration node.
 
The behavior described here will remain. Message improvements have been made to minimise the effect of this issue.

Copyright and trademark information


For more information about this topic, see the IBM Copyright and trademark information web page.

This information was developed for products and services offered in the US.

IBM might not offer the products, services, or features discussed in this information in other countries. For more information about the products and services currently available in your area, Consult your local IBM representative. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service can be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right can be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM might have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Corporation
1 New Orchard Road
Armonk
New York
10504-1722
United States

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM Japan Ltd
IP Licensing
19 - 21 Nihonbashi Hakozaki-cho
Chuo-ku 
Tokyo 103-8510
Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This statement might not apply to you because some states do not allow disclaimer of express or implied warranties in certain transactions.

This information might include technical inaccuracies or typographical errors. Changes are periodically made to this information; these changes are incorporated in new editions of the information. IBM can make improvements to the products and programs described in this information, changes in the products and programs described in this information, or both, at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM can use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for enabling: (i) the exchange of information between independently created programs and other programs (including this program) and (ii) the mutual use of the information that is exchanged, can contact:

IBM App Connect
IBM United Kingdom Laboratories
Hursley Park
Winchester
Hampshire
England
SO21 2JN

Such information might be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM did not test those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Address any questions on the capabilities of non-IBM products to the suppliers of those products.

This information includes examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Copyright license:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You can copy, modify, and distribute these sample programs in any form without payment to IBM in the following circumstances: For the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples are not thoroughly tested under all conditions. Therefore, IBM cannot guarantee or imply reliability, serviceability, or function of these programs. You can copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

Db2, IBM, Passport Advantage, WebSphere, z/OS.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle, its affiliates, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

The registered trademark Linux® is used in accordance with a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world­wide basis.

Other company, product, or service names might be trademarks or service marks of others.

Useful websites

IBM App Connect Enterprise page
http://www.ibm.com/software/products/en/ibm-integration-bus

IBM App Connect Enterprise
https://developer.ibm.com/integration/

IBM App Connect Enterprise V11.0 online product documentation https://www.ibm.com/support/knowledgecenter/SSTTDS_11.0.0

IBM App Connect Enterprise Requirements
http://www.ibm.com/software/integration/wbimessagebroker/requirements/

DB2 Fix Packs
http://www.ibm.com/software/data/db2/udb/support.html

© Copyright IBM Corporation 2023. All rights reserved.

[{"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Documentation","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
31 May 2024

UID

swg27050926

Page Feedback