IBM Integration Bus Version 10.0 release notes

• Increase in bipbroker and DataFlowEngine memory footprint on Solaris and HP-UX
  Symptom:
  After upgrading from WebSphere Message Broker V8.0.0.1, bipbroker and DataFlowEngine processes that are running on Solaris or HP systems might use an additional 204 MB of memory. This is caused by an increased default value of the ReservedCodeCacheSize parameter, in the Java virtual machine (JVM) that is used by the integration node (broker) processes. This area of memory is related to the just-in-time compilation of Java classes, and was increased by the JVM supplier in response to an increase in third-party products requiring additional space in the code cache.
  Solution:
  If the increase in memory usage causes problems for your system, you can set the value of the ReservedCodeCacheSize parameter to its former value by exporting the following environment variable in the profile of your integration node before you start that integration node:
  _JAVA_OPTIONS=-XX:ReservedCodeCacheSize=64m

Linux

• The logind.conf file for RHEL 7.2 sets option RemoveIPC to yes by default which can cause IIB to crash
  Symptom:
  IIB can crash when deploying to Integration servers in a multi instance environment. See Red Hat bug report https://access.redhat.com/solutions/2062273 for platform environment details.
  When IIB crashes abend files are generated which contain diagnostic errors similar to the following:
  
  Function is semop or semtimedop
  Inserts capture errorcodes 43 or 22
  IIB function from where error raised - ImbGlobalMutexHelper::lockGlobal() or ImbNamedMutex::lock()
  
  For example:
  File: /build/S1000_slot1/S1000_P/src/CommonServices/Unix/ImbGlobalMutexHelper.cpp
  Line: 887
  Function: semop
  ---- Inserts ----
  43
  338329603
  lockGlobal
  Or
  File: /build/S1000_slot1/S1000_P/src/CommonServices/Unix/ImbNamedMutex.cpp
  Line: 912
  Function: semtimedop
  ---- Inserts ----
  -1
  22
  Relayed by ImbNamedMutex::lock
  
  Solution:
  To resolve this problem, complete the following steps:
  - On the computer where RHEL 7.2 and IIB is installed, open /etc/systemd/logind.conf in a text editor.
  - Set RemoveIPC to no.
  - Save the file.
  
  - You might need to restart RHEL 7.2 for the change to take effect.

AIX

• DataFlowEngine abend on AIX when resolving hostname
  Symptom:
  The integration server (DataFlowEngine) process running on AIX may terminate on startup or during a deploy with the following call stack in the abend/core file:
  calloc []
  getaddrinfo []
  Java_java_net_Inet6AddressImpl_lookupAllHostAddr
  
  Solution:
  Apply AIX APAR IV95824 (AIX 7.2, or equivalent for AIX 6.1 and 7.1).
  Alternatively apply one of the following workarounds:
  - Specify hosts resolution order in /etc/netsvc.conf so that IPv4 is resolved first.
  For example: hosts=local4,bind4
  - Export the following environment variable setting:
  IBM_JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true

IBM Integration Toolkit

• IBM Integration Toolkit language packs are not included by default
  Symptom:
  The IBM Integration Bus 10 installation does not include language packs for the IBM Integration Toolkit. By default, the IBM Integration Toolkit interface is displayed in English.
  Solution:
  See Installing language packs for the IBM Integration Toolkit.
• IBM Integration Toolkit on Red Hat 6.5 crashes with "JVM terminated. Exit code=160" error (46681)
  Symptom:
  When the IBM Integration Toolkit runs on Red Hat Linux 6.5, and you click the Patterns Explorer view or you use the Tutorials Gallery, the IBM Integration Toolkit can crash with a JVM terminated. Exit code=160 error.
  Red Hat Linux ships with WebKitGTK version webkitgtk.x86_64 1.2.6-5.el6 which can have problems with the Eclipse SWT browser.
  Solution:
  To work around this problem, complete one of the following steps:
• Upgrade Red Hat Enterprise Linux to 6.6 or later. Versions of Red Hat Enterprise Linux 6.6 and later ship with a version of WebKitGTK which does not exhibit the problem.
  OR
• Update the IBM Integration Toolkit eclipse.ini file to use XULRunner instead of WebKitGTK for browser support by completing the following steps:

1. Download XULRunner 10.0.4 ESR 64-bit from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/10.0.4esr/runtimes/xulrunner-10.0.4esr.en-US.linux-x86_64.tar.bz2
2. Expand the compressed file into a convenient directory (such as /usr/lib/xulrunner_new).
3. Add the following lines to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
-Dorg.eclipse.swt.browser.XULRunnerPath=<location of unzipped download file>/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
For example:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
4. Restart the IBM Integration Toolkit.

• Internal web browser in IBM Integration Toolkit does not work on Red Hat 7.1 (55502)
  Symptom:
  When the IBM Integration Toolkit runs on Red Hat Linux 7.1 and you use any of the views that require an internal web browser, you might see one or more of the following error messages:
• In the Pattern Specification editor:
  No internal web browser can be resolved. Pattern specifications is opened in default system web browser.
• In the Tutorials Gallery view:
  No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
• In the XML View tab in the DFDL Test - Logical Instance view:
  The default browser installed on your system is not compatible or environment variables need to be specified.
  Consult the Welcome screen (Help and Welcome in the menu) for information about configuring your system.

Solution:
To work around this problem, update the IBM Integration Toolkit eclipse.ini file to use XULRunner instead of WebKitGTK for browser support by completing the following steps:
1. Download XULRunner 10.0.4 ESR 64-bit from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/10.0.4esr/runtimes/xulrunner-10.0.4esr.en-US.linux-x86_64.tar.bz2
2. Expand the compressed file into a convenient directory (such as /usr/lib/xulrunner_new).
3. Add the following lines to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
-Dorg.eclipse.swt.browser.XULRunnerPath=<location of unzipped download file>/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
For example:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
4. Restart the IBM Integration Toolkit.
5. If the IBM Integration Toolkit crashes with a JVM terminated. Exit code=160 error, run the following command before launching the toolkit in the same terminal window:
export LD_LIBRARY_PATH=<location of unzipped download file>/xulrunner:$LD_LIBRARY_PATH
For example:
export LD_LIBRARY_PATH=/usr/lib/xulrunner_new/xulrunner:$LD_LIBRARY_PATH

• The Flow Exerciser displays an error message when injecting saved messages into MQ nodes (52673)
  Symptom:
  When using the Flow Exerciser to resend a recorded message into a message flow with an MQInput node, the following error message is displayed:
  BIP2087E: Integration node 'node_name' was unable to process the internal configuration message.
  In particular, you see this when your MQInput node is configured to read from IBM MQ over a client connection.
  Solution:
  This is a current limitation. A workaround in a test environment is to adjust the MQInput node configuration to use a local queue manager.
• An error message is displayed when you start the Flow Exerciser (48133)
  Symptom:
  Either your IBM Integration Toolkit is 10.0.0.1 (or later) and your integration node is 10.0.0.0, or your IBM Integration Toolkit is 10.0.0.0 and your integration node is 10.0.0.1 (or later). You open a message flow in the message flow editor and start the Flow Exerciser. The flow deploys correctly, but the progress window displays a failure message. The error contains the following text:
  BIP2210E: Invalid configuration message: attribute name 'testRecordMode' not valid for target object 'object_name'
  Solution:
  If the IBM Integration Toolkit is 10.0.0.0, you can use the Flow Exerciser only with an integration node that is 10.0.0.0. If the IBM Integration Toolkit is 10.0.0.1 (or later), you can use the Flow Exerciser only with an integration node that is 10.0.0.1 (or later).
  To check the version of an integration node within the IBM Integration Toolkit, in the Integration Nodes view click the integration node, and then look in the Properties view.
  For more information about installing fix packs and upgrading integration nodes to use the fix pack code, see Installing fix packs.
• In IBM Integration Toolkit 10.0.0.1, or later, after you uninstall a pattern and then start working with another pattern, an error message is displayed in the Pattern Configuration editor (48036)
  Symptom:
  In IBM Integration Toolkit 10.0.0.1, or later, after you uninstall a pattern and then start working with another pattern within the same IBM Integration Toolkit session, an error occurs.
• When you attempt to create a pattern instance you see the error message: Failed to create the part's controls.
• When you attempt to generate a pattern you see the error message: Could not find transformation with id {pattern_id}.

Solution:
After uninstalling a pattern, restart your IBM Integration Toolkit before continuing to work with other patterns.
This issue is fixed in IBM Integration Bus 10.0.0.4.

• IBM Integration Toolkit on Linux becomes unresponsive after opening a DFDL file or an XSD file (49065/60518)
  Symptom:
  When the IBM Integration Toolkit runs on Linux, for example Red Hat Linux 6.x or 7.x, and you open a DFDL schema in the DFDL schema editor, or you open an XSD file in the XML schema editor, the IBM Integration Toolkit can become unresponsive and might not shut down properly. Killing the javaw process manually closes the IBM Integration Toolkit, and might result in a javacore file with the main thread in the following method:
  org/eclipse/swt/internal/gtk/OS._gtk_enumerate_printers(Native Method)
  Solution:
  This issue is caused by Eclipse Bug 153936 - Eclipse freezes when opening an editor; see https://bugs.eclipse.org/bugs/show_bug.cgi?id=153936.
  Complete one of the following steps to resolve the problem:
• Add the following line to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
  -Dorg.eclipse.swt.internal.gtk.disablePrinting
• Install the GTK2 32-bit drivers by running the following command from the command line:
  sudo yum install gtk2.i686

• NullPointerException seen when closing the message flow editor (58626)
  Symptom:
  You are using the IBM Integration Toolkit and you have been editing a subflow in the message flow editor. When you close the editor, you see an error message that contains the following text:
  java.lang.NullPointerException
  at com.ibm.etools.mft.testmode.FCBTestModeHelperDelegate.exitRecordingMode(FCBTestModeHelperDelegate.java:445)
  at com.ibm.etools.fcb.plugin.FCBGraphicalEditorPart$ActivationListener.partClosed(FCBGraphicalEditorPart.java:346)
  Solution:
  This error can be safely ignored.
  This issue is fixed in IBM Integration Bus 10.0.0.5.

Web user interface

• Webui: Unable to load BAR file in web user interface if the integration server is on z/OS (44517)
  Symptom:
  From the web user interface, you select an integration server that is on z/OS, click Deploy, and then select a BAR file. The BAR file is not loaded into the web user interface dialog.
  Solution:
  Cancel the Deploy dialog. You cannot deploy BAR files to an integration server that is on z/OS by using the web user interface. Instead you must use the mqsideploy command or deploy the BAR file by using the Integration Toolkit.
  This issue is fixed in IBM Integration Bus 10.0.0.1.

Nodes

• SCAAsyncRequest and SCAAsyncResponse nodes report BIP2628W and BIP3829E messages (42124)
  Symptom:
  IBM Integration Bus Version 10.0.0.0 reports internal timeout trace messages related to the asynchronous SCA nodes, as the following BIP warnings and errors:
  BIP2628W: Exception condition detected on input node 'FLOW NAME.SCA Asynchronous Response'.
  BIP3829E: SCARequest node 'SCA Asynchronous Request', which is using an MQ SCA binding, did not receive a response message within the timeout period.
  Solution:
  These messages can be safely ignored.
  This issue is fixed in IBM Integration Bus 10.0.0.1.
• IBM Integration Bus 10 contains APAR IT01950, so if you are migrating, you might see a new BIP2503 message generated by message flows that use ESQL
  Symptom:
  If a message flow uses ESQL containing a FOR statement that iterates over a SHARED ROW variable containing a PROPAGATE statement within the FOR block, then any attempt to write to that shared variable will result in the exception BIP2503 "Propagate with a SHARED variable lock held by FOR statement" being thrown. The reason for this is that while iterating over a SHARED ROW variable, a lock is held on the variable. This lock is also obtained when writing to the variable in downstream nodes and the exact timing of these operations could result in a deadlock occurring. It is not valid to modify the SHARED ROW variable being iterated over in downstream nodes because it might invalidate the loop. Therefore the behavior has been changed to throw an exception instead of deadlocking.
  Solution:
  Some flows which were at risk of deadlocking now throw an exception. The recommended action is to modify the flows so that they do not use the invalid pattern. If this is not possible, then the previous behavior can be restored by setting the following environment variable, and then restarting the integration node:
  MQSI_ALLOW_PROPAGATE_WITH_SHARED_LOCK_HELD=1
• JMS CONNECTIONS TO MQ FAIL WITH BIP4648E ON Z/OS ON 10.0.0.16
  Symptom:
  When connecting to an MQ JMS provider on z/OS using fix pack 10.0.0.16, connections will fail with the following error message in the joblog: 09.41.07 STC20315 +BIP4648E (Msg 1/1) MQ20BRK EG3 45 JMSCLIENT.'Broker 'MQ20BRK'; Executi 281 on Group 'EG3'; Message Flow 'SimpleJMSFlow'; Node 'ComIbmJMSClientInputNode::JMS Input::ComIbmJMSClientInputNode' ' THE CONNECTION WITH THE JMS PROVIDER COULD NOT START, OR HAS CLOSED FOR INITIAL CONTEXT FACTORY 'com.sun.jndi.fscontext.RefFSContextFactory'. THE NODE WILL TRY TO RE-ESTABLISH THE CONNECTION. Trace shows that the root cause of the error is an MQRC 2058 (MQRC_Q_MGR_NAME_ERROR) being issued from the MQ client. The issue is caused by a z/OS only regression in the MQ JMS libraries shipped with IBM Integration Bus 10.0.0.16.
  Solution:
  Apply PH10484

Connectors

• Undefined behavior when using custom nodes implemented in the Connector API framework with non-ASCII property data (48161)
  Symptom:
  When setting node properties to values outside the ASCII code page on nodes implemented using the Connector API framework, memory corruption can occur. This can cause undefined behavior in unrelated areas of IBM Integration Bus.
  This problem does not occur when using built-in nodes or using custom nodes developed using any of the other frameworks.
  Solution:
  Apply APAR IT09058.
  This issue is fixed in IBM Integration Bus 10.0.0.2.
• Directory permission problem when deploying a connector to the /var/mqsi/connectors directory, on Linux and UNIX systems (46995)
  Symptom:
  On Linux and UNIX systems, the /var/mqsi/connectors directory is configured with root only access. This prevents non-root users from deploying connector JAR files.
  Solution:
• If the /var/mqsi/connectors directory is created by the integration node startup process, the directory will have root only access. In order for non-root users to be able to deploy connectors, the system administrator must change the directory permissions. The ownership of the directory must be changed to the owner that is running the integration node, and the user group must be set to mqbrkrs.
• If the /var/mqsi/connectors directory does not already exist, you can manually create it with the permissions specified above.

This issue is fixed in IBM Integration Bus 10.0.0.2.

Commands

• The mqsiprofile command can exit without configuring the IBM Integration Bus environment correctly, leaving the PATH environment variable corrupted (43730)
  Symptom:
  On Linux and UNIX systems, an attempt to run the install_path/server/bin/mqsiprofile script can exit without configuring the IBM Integration Bus environment correctly, as a result of commands called by the mqsiprofile command not being found on the PATH. The mqsiprofile script attempts to call the setmqenv command to configure the IBM MQ environment, and this can corrupt the PATH environment variable.
  Solution:
  Apply the fix for IBM MQ APAR IV70713.

Global cache

• BIP7166 error with text com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.io.EOFException when getting a null value from the embedded cache (51948)
  Symptom:
  The following error is seen when performing a get operation to retrieve a value from the embedded global cache:
  BIP7166E: A connectivity exception occurred while interacting with map map_name. A client attempted operation get with map map_name from grid WMB. This attempt failed for the following reason:
  Where map_name is the name of your map, and the reason information contains the error com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.io.EOFException. This is caused by an issue in the WebSphere eXtreme Scale global cache when using the XIO transport. The XIO transport is used by IBM Integration Bus 10.0.0.2 when the function level is set to 10.0.0.2 or above. If the function level set to 10.0.0.1 or lower, then the ORB transport is used.
  Solution:
  This issue is specific to retrieving a null value from the embedded WebSphere eXtreme Scale global cache in IBM Integration Bus when using the XIO transport. If you need to store null values in the cache, then set the function level to 10.0.0.1 or lower to use the ORB transport. For more information about setting the function level, see Changing the function level of your integration nodes.
  This issue is fixed in IBM Integration Bus 10.0.0.3.

XA

• After applying fix pack 10.0.0.6 or later error BIP2111E or BIP2698 is received
  Symptom:
  After installing 10.0.0.6 and following the migration instructions I see a BIP2111 or BIP2698 message with the text "Couldn't locate qm.ini". XA transactions are not committed and there may be other errors in the syslog relating to bad MQ return codes during MQCMIT.
  This is because the product has not been able to determine the location of the qm.ini file, or has not understood the qm.ini file and therefore the XA listener ports have not been opened.
  Solution:
  You can override this auto detection and force the XA listener ports to be opened by specifying one of the following environment variables and restarting the broker:
  JMS: MQSI_XA_JMS_START_LISTENER=1
  JDBC: MQSI_XA_JDBC_START_LISTENER=1
  
  You can confirm that the port is open by examining netstat output for the DataFlowEngine process. Each active listener will open a single port in the range 6500-8500
  Improved in IBM Integration Bus 10.0.0.7: BIP2111 has been replaced with BIP2698 "Not starting XA listener as could not locate qm.ini".

Databases

• Truncation error when working with CLOB column data against a UTF-8 Oracle database
  Symptom:
  10.0.0.13 adds support for ODBC CONNECTIONS TO ORACLE 12C RELEASE 2. With this fix pack the default value for the connection property EnableNCharSupport has changed from EnableNcharSupport=0 to EnableNcharSupport=1 which 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.
  Solution:
  On Linux and UNIX systems, set EnableNcharSupport=0 in the odbc.ini file. The sample odbc.ini files have been updated to include this connection option setting.
  On Windows systems add "EnableNcharSupport=0;" to the Extended Options field under the Advanced tab for the Oracle data source definition using the ODBC Data Source Administrator.

Tutorials

• Tutorials Gallery does not display correctly on Linux (44344/44803/57467)
  Symptom:
  When you start the Tutorial Manager on Linux, the following message might be displayed:
  Tutorials Gallery cannot be displayed in this internal web browser.
  Solution:
  The Tutorial Manager requires an embedded browser to display the Tutorial Gallery and this requires the installation of some compatible optional Linux packages.
  On Ubuntu 12.04, 14.04, 16.04:

1. Verify that Webkit 1.0.0 is installed.
2. If Webkit 1.0.0 is not installed then install Webkit by running the following command from the command line:
sudo apt-get install libwebkitgtk-1.0-0
3. On Ubuntu 16.04 you may also need to issue 'export LIBOVERLAY_SCROLLBAR=0' from the command line.
On Red Hat Enterprise Linux 6:
1. Verify that Webkit is installed.
2. If Webkit is not installed then install Webkit by running the following command from the command line:
sudo yum install webkitgtk
On SUSE Linux Enterprise 11:
1. Verify that XULRunner 1.9.2 is installed.
2. If XULRunner 1.9.2 is not installed then install XULRunner 1.9.2 by running the following command from the command line:
sudo /sbin/yast -i mozilla-xulrunner192
On SUSE Linux Enterprise 12:
1. Verify that XULRunner 1.9.2.x is installed.
2. If XULRunner 1.9.2 is not installed then install XULRunner 1.9.2.x (64 bit) by completing the following steps:
a. Download XULRunner 1.9.2.13 (64 bit) from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2010/12/2010-12-01-03-mozilla-1.9.2/xulrunner-1.9.2.13.en-US.linux-x86_64.tar.bz2
b. Expand the compressed file into a convenient directory (such as /usr/lib/xulrunner_new).
c. Add the following lines to the end of the eclipse.ini file in the tools directory under the IBM Integration Bus installation directory:
-Dorg.eclipse.swt.browser.XULRunnerPath=<location of unzipped download file>/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
For example:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla
d. Add XULRunner to the library path by running the following command before launching the toolkit in the same terminal window:
export LD_LIBRARY_PATH=<location of unzipped download file>/xulrunner:$LD_LIBRARY_PATH
For example:
export LD_LIBRARY_PATH=/usr/lib/xulrunner_new/xulrunner:$LD_LIBRARY_PATH
e. Restart the IBM Integration Toolkit.
 

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:

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 Integration Bus product page
http://www.ibm.com/software/products/en/ibm-integration-bus

IBM Integration Community
https://developer.ibm.com/integration/

IBM Integration Bus 10.0 online product documentation
http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.msgbroker.helphome.doc/help_home_msgbroker.htm

IBM Integration Bus Requirements
https://www.ibm.com/support/docview.wss?uid=swg27045108

IBM Integration Bus Fix Packs
http://www.ibm.com/support/docview.wss?uid=swg27006041

WebSphere MQ Fix Packs
http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ

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

© Copyright IBM Corporation 2023. All rights reserved.