IBM Support

IBM Integration Bus Version 10.0 release notes

Release Notes


Abstract

This document contains the release notes for IBM Integration Bus Version 10.0, including the tooling and runtime components.

Content

Release Notes file for: IBM Integration Bus
Product release: 10.0
Update Name: 10.0.0.17
Versions and fix packs:
* V10.0.0.0 (electronic availability: 27 March 2015)
* Fix Pack V10.0.0.1 (electronic availability 29 May 2015)
* Fix Pack V10.0.0.2 (electronic availability 25 September 2015)
* Fix Pack V10.0.0.3 (electronic availability 27 November 2015)
* Fix Pack V10.0.0.4 (electronic availability 11 March 2016)
* Fix Pack V10.0.0.5 (electronic availability 27 May 2016)
* Fix Pack V10.0.0.6 (electronic availability 26 August 2016)
* Fix Pack V10.0.0.7 (electronic availability 25 November 2016)
* Fix Pack V10.0.0.8 (electronic availability 17 March 2017)
* Fix Pack V10.0.0.9 (electronic availability 02 June 2017)
* Fix Pack V10.0.0.10 (electronic availability 08 September 2017)
* Fix Pack V10.0.0.11 (electronic availability 30 November 2017)
* Fix Pack V10.0.0.12 (electronic availability 29 March 2018)
* Fix Pack V10.0.0.13 (electronic availability 21 June 2018)
* Fix Pack V10.0.0.14 (electronic availability 28 September 2018)
* Fix Pack V10.0.0.15 (electronic availability 18 December 2018)
* Fix Pack V10.0.0.16 (electronic availability 29 March 2019)
* Fix Pack V10.0.0.17 (electronic availability 24 June 2019)


Document first published: 27 March 2015
Document last modified: 24 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.ibm.com/support/docview.wss?uid=swg27006917

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 Integration Bus Version 10.0 documentation.

System requirements
Check the IBM Integration Bus 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 Integration Bus system requirements website.

Downloading the product from the IBM Passport Advantage website:
For information about downloading IBM Integration Bus V10.0 installation images from the Passport Advantage website, see Download IBM Integration Bus V10.0 from the Passport Advantage website.


Essential information if you are migrating

If you are migrating from WebSphere Message Broker Version 7.0 or Version 8.0, or from IBM Integration Bus Version 9.0, refer to the Migrating section of the online product documentation, which provides detailed information about how to migrate.

The names of several resources and components within the product changed in IBM Integration Bus Version 9.0. For more information, see Name changes in IBM Integration Bus Version 9.0 and Version 10.0.

The contents of all applicable diagnostic messages has been updated to reflect the name change of several resources and components, which occurred in IBM Integration Bus Version 9.0. The contents of various diagnostic messages has also been updated to improve message clarity, and additional diagnostic messages have been added. For more information see Diagnostic messages.


Product documentation

The online product documentation can be found in IBM Knowledge Center. See IBM Integration Bus Version 10.0 documentation.

In IBM Integration Bus Version 10, the IBM Integration Toolkit help is now 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 Integration Toolkit to use this local source. For more information, see Downloading and installing a local IBM Integration Bus documentation feature.

The stand-alone product documentation is available for download at the following locations:


For information about using the stand-alone product information center, read the using_the_infocenter.html file that is included in the ibm_help folder in the ib_help_linux.tgz and ib_help_win.zip files.


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 Integration Bus support website.
To find information, click Troubleshooting documentation. IBM Integration Bus Technotes are displayed. The results can be filtered and searched.


Feature updates

To learn about what features have been added to IBM Integration Bus Version 10.0, see What's new in Version 10.0?

To learn about what enhancements have been added in IBM Integration Bus fix packs, see New function added in Version 10.0 fix packs.

Check periodically for updates to the IBM Integration Toolkit. Information about recommended fixes can be found on the Recommended fixes for IBM Integration Bus and WebSphere Message Broker web page.

For information about how to install fix packs, see Installing fix packs.


Known problems and their workarounds (if any)

This section outlines the known problems and their workarounds (if any) of IBM Integration Bus, by component.


Installation

  • The 'iib' command fails on Linux and UNIX if the 'iibconfig' directory exists but is empty (46098)
    Symptom:
    A single-user installation of IBM Integration Bus 10.0.0.0 on Linux and UNIX uses the directory $HOME/iibconfig as the work path to store IBM Integration Bus configuration files. If this directory exists but is empty, then the 'iib' command fails to run correctly. The following errors might be observed:
    IBM Integration Bus v10000 (utility.mqsiexplain) [Thread 1] (Msg 1/1) BIP2229W: Warning: abend file directory ($HOME/iibconfig/common/errors) open failed: errno 2. Using directory /tmp 0
    Failed to open file $HOME/iibconfig/common/log/utility.mqsiexplain.trace.bin.0 with error No such file or directory
    Failed to open file $HOME/iibconfig/common/log/utility.mqsiexplain.userTrace.bin.0 with error No such file or directory

    Solution:
    Delete the iibconfig directory in $HOME. The next time the 'iib' command is run, the directory $HOME/iibconfig is recreated with the correct contents.
    This issue is fixed in IBM Integration Bus V10.0.0.1.
  • Running 'iib make registry global' shows an error on AIX (46097)
    Symptom:
    On AIX, running either 'iib make registry global' or 'iib make registry global accept license' as root results in the following error being displayed:
    find: cannot execute :: No such file or directory
    Solution:
    This error can be safely ignored.
    This issue is fixed in IBM Integration Bus V10.0.0.1.
  • On Windows, the installation process does not prevent you from installing one V10.0 installation over the top of another V10 installation, and a subsequent uninstall of one version leaves the other unusable (48527)
    Symptom:
    When installing IBM Integration Bus V10.0.0.0 or V10.0.0.1, you manually changed the installation directory and specified the same directory as is used by an existing V10.0 installation. This appears to work until you uninstall one of the two installations, and the other one is then left unusable because some files are missing.
    Note: Installing IBM Integration Bus V10.0 over an existing deployment of IBM Integration Bus is not supported. For information on installing IBM Integration Bus on Windows, see Installing IBM Integration Bus on Windows.
    Solution:

1. Uninstall both versions of IBM Integration Bus, one at a time. This will return your system to a clean state.
2. Either reinstall only IBM Integration Bus V10.0.0.1, or, if you want to install both V10.0.0.0 and V10.0.0.1, make sure that you install each version into a different directory.
This issue is fixed in IBM Integration Bus V10.0.0.2.
 


Platforms
z/OS

  • 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 fixpack 10.0.0.16, connections will fails 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
Solaris and HP-UX

  • 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 RedHat 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 V10 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 RedHat 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 on 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 V10.0.0.1 (or later) and your integration node is V10.0.0.0, or your IBM Integration Toolkit is V10.0.0.0 and your integration node is V10.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 V10.0.0.0, you can use the Flow Exerciser only with an integration node that is V10.0.0.0. If the IBM Integration Toolkit is V10.0.0.1 (or later), you can use the Flow Exerciser only with an integration node that is V10.0.0.1 (or later).
    To check the version of an integration node within the IBM Integration Toolkit, in the Integration Nodes view click on 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 V10.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 V10.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 V10.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 V10.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 V10.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 V10.0.0.1.
  • IBM Integration Bus V10 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

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 V10.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 V10.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 V10.0.0.3.

XA

  • After applying fixpack 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 V10.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 fixpack 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 datasource 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 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 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 V10.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 2018. All rights reserved.

Original Publication Date

21 March 2016

[{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Documentation","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","Edition":""}]

Document Information

Modified date:
24 June 2019

UID

swg27045067