Welcome to IBM WebSphere Message Broker and IBM WebSphere Event Broker. This is the readme file for Fix Pack 3, which contains support for HP-UX (Itanium platform). This readme file relates to Version 6.0.0.3 of the Runtime component, and Version 6.0.0.2 of the Tooling component.
This readme describes known problems, and contains documentation updates that were not available in time to be included in the online information center.
Always use the latest version of this readme file, which you can find (in English only) at:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006917
Translated versions of the readme file are available from: ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0
To complete installation, refer to the WebSphere Message Broker Installation Guide or the WebSphere Event Broker Installation Guide. These books include information about tasks you must complete before you install the product. They also include information about the support for HP-UX (Itanium platform).
Access the Installation Guide online in the IBM Publications Center at:
http://publib.boulder.ibm.com/epubs/pdf/c3466213.pdf for Message Broker
http://publib.boulder.ibm.com/epubs/pdf/c3466223.pdf for Event Broker
The information center for WebSphere Message Broker and WebSphere Event Broker reflects Version 6.0.0.3 of the Runtime component, and Version 6.0.2.0 of the Tooling component.
The stand-alone information center for WebSphere Message Broker and WebSphere Event Broker is accessible from: http://www.ibm.com/software/integration/wbimessagebroker/library/
It is also available for download from:
ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/wmb_help_lin.tgz (Linux version)
and
ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/wmb_help_win.zip (Windows version).
Read the installing_and_managing.htm file, which is included in the wmb_help_lin.tgz and wmb_help_win.zip
files.
The information center will be available through the Rational Product Updater (RPU) as an integrated part of Version 6.0.2.0 of the Toolkit in December 2006. Until that time, you can access the stand-alone information center from either the WebSphere Message Broker Library Web page or the FTP site (as shown above).
Collections of information topics formatted for printing, and all documentation for Rules and
Formatter, can be found at:
ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/
Defects: Throughout this readme document there are 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,
look at:
http://www.ibm.com/software/integration/wbimessagebroker/support/
You can then find information using either of the following methods:
Versions: For the latest status on which particular versions of operating system and databases
are supported by WebSphere Message Broker and WebSphere Event Broker, consult the WebSphere MQ Family
Supported Software pages at:
http://www.ibm.com/support/docview.wss?uid=swg27007065
This section outlines the restrictions and limitations of WebSphere Message Broker and WebSphere Event Broker, by component.
If you are installing runtime components on Windows, and the process displays the following message just before completion, the required security groups have not been created:
mqsisetsecurity.exe has encountered a problem and needs to close
The probable cause of this error is that you have uninstalled the Windows component File and Printer Sharing for Microsoft Networks. The security program depends on APIs provided by this component and cannot complete successfully unless the component is installed. The component can be disabled, if it is not required.
To run the installation program successfully, complete the following steps:
On any UNIX platform, if you install the Configuration Manager component without the Broker component, and subsequently install the Broker into the same directory, several file symbolic links will be missing from the Broker's lil and lil64 directories. To avoid this problem, either:
To upgrade the Message Brokers Toolkit to Version 6.0.0.2 (from either Version 6.0 or Version 6.0.0.1), you must use the Rational Product Updater (RPU), which must be at level 6.0.1 or later. If you are currently using an earlier version of the RPU, you must upgrade it to Version 6.0.1 before upgrading the Message Brokers Toolkit. For information on ugrading the RPU, see the WebSphere Message Broker Installation Guide (Third Edition, March 2006).
You can use the RPU to install the Message Brokers Toolkit (V6.0.0.2) either directly from the Web, or from a local system. The procedure for upgrading to Version 6.0.0.2 using the RPU is the same as that documented in the WebSphere Message Broker Installation Guide for upgrading to Version 6.0.0.1.
Additional instructions for upgrading the Message Brokers Toolkit and the Rational Product Updater are available from the WebSphere Message Broker and Event Broker V6.0 Toolkit Fix Pack 6.0.0.1 support page.
If you are using the RPU to install the package from a local system (rather than directly from the Web), the package you need to download varies according to the version you are upgrading from (Version 6.0 or Version 6.0.0.1):
After you have upgraded to Version 6.0.0.2 (Fix Pack 2), you need to do the following things:
Technotes are available covering several important issues relating to the installation of Message Broker and Event Broker Toolkits with Rational Application Developer (RAD) or Rational Software Architect (RSA) products. You are strongly advised to refer to these Technotes when installing the Message Brokers Toolkit. Information on how to access these Technotes is given in the Support section of this readme.
When you use response files for silent installation, they can contain an incorrectly set flag. As a result, if you select one or more specific components to be installed (rather than the full product), the selections are ignored and the full product is installed. To overcome this problem, you need to edit the response file and modify the appropriate flag as follows:
The following line:
-W setupTypes.selectedSetupTypeId=custom
should be changed to:
-W setupTypes.selectedSetupTypeId=
(that is, set to nothing) to prevent the default typical or custom installs (which install all components) from running.
If you develop message flows that use WebSphere MQ Real-time Transport with Multicast PGM support, you must install WebSphere MQ Version 6.0 or later on each affected broker system. You also need to apply APAR IC47032 and USERMOD ANPGM01.
Message Broker is supported in the Global zone or a whole root non-global zone, and must be installed separately in each.
If you have one or more components of WebSphere Message Broker already installed on a computer, and you then try to install any additional components, InstallShield checks to see whether there is sufficient disk space to install the entire product and not just the additional components that you want to install. As a result, you might be unable to install the additional components even though there is enough space for them on the computer. If there is enough space to install the whole product, you can install the selected components successfully. However, if there is not enough space, you will need to uninstall the previously installed components and start again.
The Command Assistant Wizard cannot currently administer Configuration Manager components. A fix will be made available to rectify this situation.
If you want to install the WebSphere MQ V6 Explorer plug-ins for use with WebSphere Message Brokers Toolkit, you can use the Eclipse Update Manager. However, you must first install the V6.0.1 refresh pack for WebSphere MQ V6.
From the Eclipse toolbar, select Help > Software Updates > Find and Install. Select the New features option. Add <WebSphere MQ installation directory>/eclipse as a new local source and the Explorer features will be shown as available for installation.
As a workaround before the availability of the V6.0.1 update, you can manually copy the directories containing the WebSphere MQ Explorer features and plug-ins into the WebSphere Message Brokers Toolkit directory. After restarting the WebSphere Message Brokers Toolkit, WebSphere MQ Explorer can then be opened as a new perspective.
When you use the -options-record flag to create a response file for use during silent uninstallation, the response file contains an incorrectly set flag. As a result, if you select one or more specific components to be uninstalled (rather than the full product), the option is ignored and the full product is uninstalled.
To overcome this problem, you need to edit the response file and modify each line that specifies whether or not an individual component is to be uninstalled. This means that you need to change all instances of the following string:
-P feature.active=trueto the following:
-P feature.activeForUninstall=truewhere feature is the name of the component to be uninstalled.
You also need to change all instances of the following string:
-P feature.active=falseto the following:
-P feature.activeForUninstall=falsewhere feature is the name of the component that you do not want to uninstall.
You must ensure that one of these statements (either activeForUninstall=true or ctiveForUninstall=false) exists for every component.
However, in the generated response file there can also be activeForUninstall statements relating to components that have not been installed. If such statements exist, ensure that the activeForUninstall option for each of these components is set to true. If the activeForUninstall option is set to false for these components, the uninstallation program fails.
Any users of the following Dublin Adapter solutions should contact Dublin Adapters Support (dubadsup@ie.ibm.com) for a version of the solution that has been tested on Version 6 of the Message Broker. Do not simply migrate the Version 5 solution as this can result in some subtle differences in behavior from Version 5:
Before attempting a migration of the solution to Version 6, any users of the following Dublin Adapter solutions should contact Dublin Adapters Support (dubadsup@ie.ibm.com) to check whether a version is available that has been tested on Version 6 of the Message Broker, and whether there are any further issues:
If you are migrating a message set from WebSphere MQ Integrator Version 2.1, and the message set contains an industry standard TDS physical format such as SWIFT, and if you intend to deploy the message set to a Version 2.1 broker (or to a Version 5 broker that is at a service level prior to Fix Pack 3), you might need to complete the following steps after using the mqsimigratemsgsets command.
If you do not make this update, the following message appears when you add the message set to a bar file (CSD3 in this message refers to Fix Pack 3):
BIP0202W This dictionary requires a version 5 CSD3 or above broker. TDS Format "SWIFT" uses "Strict Numeric Checking". This option is not supported by brokers earlier than version 5 CSD 3.
You must correct this error before you can deploy the bar file successfully.
When using the Real-timeInput node with publish/subscribe applications, there is a possible memory leak in the DataFlowEngine process on all distributed platforms. The memory used by the DataFlowEngine process constantly increases, depending on the platform and the number of publish/subscribe clients.
If the DataFlowEngine process runs out of memory it stops. On Windows, an ABEND file and a dump are generated in the 'errors' folder. On other systems, an ABEND file and a core file are generated. The DataFlowEngine process then restarts.
For example, using a single message flow (with no additional instances) in one broker with one execution group, and 80 publish/subscribe clients on a 4 way - 4GB computer running Windows, the DataFlowEngine process stopped after approximately 1.5 hours.
You are likely to see errors in the system event log such as:
Java Virtual Machine OutOfMemoryError occurred. The JVM has reported an OutOfMemoryError situation.
The ABEND File might contain errors like:
File: F:\build\S000_P\src\DataFlowEngine\JavaNodeLibrary\ImbJmsIpJNIJmsIpNode.cpp Line: 417 Function: Java_com_ibm_broker_server_JmsIpNode_logFatalError AbendAction: 3
To resolve this problem, it might be necessary to stop and restart the broker, and increase the Java Virtual Machine Heap size. You can eliminate some memory issues if you use the Real-timeOptimizedFlow node instead of the Real-timeInput node.
On z/OS platforms: If you include a Trace node, with its destination property set to "User Trace", in a high throughput message flow, the owning execution group might stop (abend S2C1). Because Trace nodes are always active, they should not normally be included in production flows. But to avoid this problem, ensure that connected Trace nodes are not included in high throughput flows as, being always active, these nodes will have a high I/O overhead.
If you want to use the flow debugger, the names of a broker and execution group must be in English alphabet characters, whatever the locale of the computer.
On AIX, an XA enabled WebSphere MQ queue manager (on WebSphere MQ Version 5) fails to start cleanly if there is no link from /usr/lib to the Oracle supplied 32-bit client library 'libclntsh.a'.
To resolve this problem, issue the following command (as root):
ln -s $ORACLE_HOME/lib32/libclntsh.a /usr/lib/libclntsh.a
This allows the queue manager to start cleanly.
Note that this does not apply to WebSphere MQ Version 6.
If you have Oracle9i or Oracle10g and DB2v8 installed on the same HP-UX system you might experience a problem using the broker with an Oracle broker database.
The broker is prevented from starting and an abend file is created. In the file you see symbols from the Oracle libraries resolved in a DB2 library, giving rise to a segmentation violation.
If you want to use Oracle with the broker, and have DB2 installed on the same (HP-UX) computer, disable the <install_dir>/lib/imbdfdb2.lil file. The easiest way to do this is to rename imbdfdb2.lil to something else. This stops the broker getting DB2 libraries that the HP-UX operating system then uses to resolve the Oracle symbols.
Oracle XA is not supported with 64-bit EGs on AIX, Solaris, and HP-UX.
The manipulation of Unicode data in databases is not supported.
In addition to the restrictions described in the "Supported Databases" topic in the information center, note that only the 32-bit Informix Dynamic Server and 32-bit Client SDK are supported. There is currently no support for 64-bit Informix server or client.
The minimum required version of the Informix client is SDK V2.90 with UC4X8 fix pack; contact Informix to request this fix pack.
On Linux and Windows, some of the samples have minor usability problems. Before using them, refer to the
following Technote:
http://www.ibm.com/support/docview.wss?rs=849&context=SSKM8N&context=SSKMAB&q1=samples&uid=swg21239255&loc=en_US&cs=utf-8&lang=en
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:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
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 Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites 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:
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 cannot 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, cannot 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:
AIX, DB2, Everyplace, IBM, Universal Database, WebSphere, z/OS, zSeries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.
DB2 Fix Packs
You can obtain DB2 Fix Packs on CDROM or by downloading from the Web. Note, however, that Fix Packs might be large and therefore requesting CDROM versions will avoid lengthy downloads.
If you have a current support contract, you can order DB2 Fix Packs on CDROM by calling DB2 support.
Contact details are provided at:
http://www.ibm.com/software/data/db2/udb/support.html
You can also download from the same Web site.
WebSphere MQ Fix Packs
http://www.ibm.com/software/integration/wmq/support/
WebSphere Message Brokers Fix Packs
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006367
WebSphere Message Broker and WebSphere Event Broker Requirements
http://www.ibm.com/software/integration/wbimessagebroker/requirements/
and
http://www.ibm.com/software/integration/wbieventbroker/requirements/
WebSphere Message Broker and WebSphere
Event Broker Readme
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006917
WebSphere Message Broker and WebSphere Event Broker Stand-alone Information Center
For Linux:
ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/wmb_help_lin.zip
For Windows:
ftp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/wmb_help_win.zip
WebSphere Message Brokers V6 online Help
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp
IBM Centre for Java Technology Development Downloads
http://www.ibm.com/developerworks/java/jdk/
Web Services Description Language (WSDL) Specification
http://www.w3.org/TR/wsdl
WebSphere Message Broker Basics (Redbook)
http://www.redbooks.ibm.com/abstracts/sg247137.html
Migrating to WebSphere Message Broker V6 (Redbook)
http://www.redbooks.ibm.com/abstracts/sg247198.html