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.5
Document first published: 04 April 2018
Document last modified: 28 June 2019

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)

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.


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.

  • 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

  • IIB / ACE fails to start when classloader trace is enabled (#73807)

You can configure ACE to turn on Java classloader trace using IBM_JAVA_OPTIONS=-Dibm.cl.verbose=* but on server start up you will receive a BIP2116E internal error. You can work around this problem by also setting MQSI_DISABLE_MB_PRINTSTREAM=true which will enable the server to start and also enable the gathering of Java classloader trace.

  • 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.

  • 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)

  • 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.


Copyright and trademark information


For full details, see the IBM Copyright and trademark information web page.

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may 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 may 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 Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

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 World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information 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 may 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 wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM United Kingdom Laboratories
Mail Point 151
Hursley Park
Winchester
Hampshire
England
SO21 2JN

Such information may 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 has not tested those products and can not confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed 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 may 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 the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, can not guarantee or imply reliability, serviceability, or function of these programs. You may 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, developerWorks, IBM, Informix, Passport Advantage, WebSphere, z/OS.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates in the United States, other countries, or both

Microsoft and Windows 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.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

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 2018. All rights reserved.

Original Publication Date

04 April 2018

[{"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Documentation","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"11.0","Edition":""}]

Document Information

Modified date:
28 June 2019

UID

swg27050926