IBM Support

IBM Tivoli Composite Application Manager for Applications 6.2.4 ITCAM Agents for WebSphere Messaging Version 7.0.1 Fix Pack 2 Readme

Fix Readme


Abstract

xxx

Content

Readme file for: IBM Tivoli Composite Application Manager for Applications: ITCAM Agents for WebSphere Messaging Version 7.0.1 Fix Pack 2
Product/Component Release: 6.2.4
Update Name: ITCAM Agents for WebSphere Messaging Version 7.0.1 Fix Pack 2
Fix ID: 7.0.1-TIV-XEforMsg-FP0002
Publication Date: 2012-02-24
Last modified date: 2012-02-24

Download location

You can download this fix pack from Passport Advantage at the link below. The part number of installation image is CI5W8EN.
http://www-306.ibm.com/software/howtobuy/passportadvantage/index.html


You can also download the multi-language readme files which include Brazilian Portuguese, French, German, Japanese, Spanish, Simplified Chinese and Traditional Chinese versions in PDF format at this link below.
http://download4.boulder.ibm.com/sar/CMA/TIA/030hp/3/Tivoli-ITCAM_Agents_for_Messaging_701-fixpack-2.readmeML.zip

Prerequisites and co-requisites


Before you install this fix pack, make sure that the software installed in your environment is compatible with this fix pack.
Supported WebSphere MQ
* WebSphere MQ 6.0
* WebSphere MQ 7.0
* WebSphere MQ 7.0.1
* WebSphere MQ 7.1 (toleration support)
Supported IBM broker products:
* WebSphere Event Broker V6
* WebSphere Message Broker V6
* WebSphere Message Broker with Rules and Formatter Extension V6
* WebSphere Message Broker V6.1
* WebSphere Message Broker V7.0
* WebSphere Message Broker V8.0 (toleration support)
Supported IBM Tivoli Monitoring
* IBM Tivoli Monitoring 6.2.2 at the minimum

Toleration support means new features introduced to WebSphere MQ 7.1 and WebSphere Message Broker 8.0 are not supported by this fix pack.
In particular, the new Applications and Libraries features of WebSphere Message Broker 8.0 are not supported in this fix pack. Message flows that you deploy with applications and libraries in the WebSphere Message Broker Toolkit will not be monitored by the agent yet in this fix pack release.

Important: To use this fix pack with WebSphere Message Broker 8.0 before you install this fix pack, you must apply one fix of WebSphere Message Broker 8.0 APAR IC80285. This fix will be delivered with WebSphere Message Broker 8.0 Fix Pack 1. For more information about fix packs of WebSphere Message Broker, see: WebSphere Message Broker planned maintenance release dates

To acquire this APAR IC80285 fix prior to availability of WebSphere Message Broker 8.0 Fix Pack 1, contact IBM Support for WebSphere Message Broker product.

Summary of APAR IC80285:
An execution group can publish change and status notification messages on topics that should be the name of that execution group.
The problem is that the name "ImbDataFlowNotifications" appears as part of the topic string instead of the execution group name.

Besides the above prerequisites, refer to the following information centers to get a complete set of hardware and software prerequisites

Distributed systems: http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.omegamon.mes.doc_7.0.1/t_prepare_isntall.html
z/OS systems: http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.mes.doc_7.0.1/welcome.htm

Known issues

None

Known limitations


Queue managers of different WebSphere MQ versions cannot be discovered simultaneously on Windows systems.
If you have two different versions of WebSphere MQ installed on the same Windows system, the discovery function might not be able to discover queue managers and their resources for both versions at the same time. Do not run the discovery process for two agent instances at the same time.

Message Flows deployed using the new WebSphere Message Broker 8 Application and Library features are not supported.
Message flows that are deployed using the previous methods in WebSphere Message Broker 7 can be monitored by agent, but the message flows deployed with the WebSphere Message Broker 8 toolkit applications and libraries cannot be monitored.

Installation information

Prior to installation

None

Installing


The installation instructions for this fix pack are the same as those for GA version 7.0.1.
Refer to the Installation and Setup Guide (GI11-8074-02) to install agents on distributed systems, and the Program Directory (GI11-8923-01) to install agents on z/OS systems.
Information center for distributed systems:
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.mes.doc_7.0.1/welcome.htm

Information center for z/OS systems:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.3/welcome_itcam.htm


Note: When you install agents on i5/OS systems, four digits in the image file name indicate the level of the agent.
For example, MQ7012CMA is the file name for WebSphere MQ Monitoring agent of version 7.0.1 fix pack 2. To install the agents of this fix pack, use MQ7012CMA for WebSphere MQ Monitoring agent, and MC7012CMA for WebSphere MQ Configuration agent.

Performing the necessary tasks after installation


Important: To users of WebSphere MQ 7.1, you must read this section and perform the required procedures to apply this fix pack to your environment.

After the basic installation is complete, some agent-specific configurations are required to support WebSphere MQ 7.1.

WebSphere MQ Configuration agent
1. Specifying the library path for WebSphere MQ 7.1

Windows
Add the installation path of WebSphere MQ 7.1 to the the beginning of the PATH environment variable and restart the system before you start the agent.
For example, if the installation path of WebSphere MQ 7.1 is C:\IBM\WMQ71, add C:\IBM\WMQ71\bin to the beginning of the PATH variable.

UNIX and Linux
Step 1: Add the library path of WebSphere MQ 7.1 for WebSphere MQ Configuration agent to configure queue managers.
To do this, add the following line to the end of the mc.ini file:
* Linux/Solaris/HP-UX:
LD_LIBRARY_PATH=$WMQ71INSTALL/lib/compat:$LD_LIBRARY_PATH
* AIX:
LIBPATH=$WMQ71INSTALL/lib:$LIBPATH
where WMQ71INSTALL is the installation path of WebSphere MQ 7.1.
Step 2: Restart the agent instance to make the changes take effect.

2. Specifying the multiple installation paths
Since WebSphere MQ 7.0.1.6, you can have multiple copies of WebSphere MQ installed to different directories on a single machine.
If you have different versions of WebSphere MQ on the same system of if you installed two copies of WebSphere MQ 7.1 to different directories, you MUST set two parameters in the agent configuration file to specify different installation directories of different versions of WebSphere MQ:
KMC_INSTALLPATH: Specify the installation path of WebSphere MQ that is to be managed by the current agent instance.
KMC_WMQ71_INSTALL_PATH: Specify the installation path of WebSphere MQ 7.1 that is installed on the same system.
If you have two copies of WebSphere MQ 7.1 installed on the same system, specify either directory in this parameter.

Note: For Windows systems, those parameter values must be embraced by double quotation marks, for example, KMC_INSTALLPATH="C:\IBM\WMQ71", KMC_WMQ71_INSTALL_PATH="C:\IBM\WMQ71".

Remember: If you have different versions of WebSphere MQ installed on the same system, you need different instances of WebSphere MQ Configuration agent for different versions of WebSphere MQ separately.
To distinguish multiple agent instances, set KMC_CLUSTERNAME parameter in the configuration file.

WebSphere MQ Monitoring agent
To support multiple WebSphere MQ installations, do the following steps to configure WebSphere MQ Monitoring agent:

Windows
Add the installation path of WebSphere MQ 7.1 to the the beginning of the PATH environment variable. And restart the operating system.
For example, if the installation path of WebSphere MQ 7.1 is C:\IBM\WMQ71, add C:\IBM\WMQ71\bin to the beginning of the PATH variable.

UNIX and Linux
Step 1: Add the library path of WebSphere MQ 7.1 for WebSphere MQ Configuration agent to configure queue managers.
To do this, add the following line to the end of the mq.ini file:
* Linux/Solaris/HP-UX:
LD_LIBRARY_PATH=$WMQ71INSTALL/lib/compat:$LD_LIBRARY_PATH
* AIX:
LIBPATH=$WMQ71INSTALL/lib:$LIBPATH
where WMQ71INSTALL is the installation path of WebSphere MQ 7.1.
Step 2: Restart the agent instance to make the changes take effect.

Troubleshooting installation problems from the Support site

None

Uninstalling if necessary

None

List of fixes

Fix Description of fix
IZ91288 SHUTDOWN OF MQ AGENT ON I5/OS PRODUCES CPF1055
IZ93836 ERROR LOG WORKSPACE RETURNS NO DATA
IZ96503 IF ERRLOGCYCLE(0) IS CODED IN CFG FILE THE MQ AGENT INSTANCE
IZ98680 MULTI-INSTANCE BROKERS NOT REPORTING CORRECTLY
IV00651 THE UPGRADED BROKER ISN'T DISCOVERED RIGHTLY.
IZ79111 MQ SITUATION NOT FIRING WHEN USING ENUM VALUE
IZ95021 NO DATA IS BEING RETURNED FOR MESSAGING AGENT WHEN ERROR OPENING ACCOUNTING OR STATISTICS QUEUE IS ENCOUNTERED.
IZ95669 BLANK SERVER NAME WITHIN DEFINED TREE
IZ99853 MQ WORKSPACES BECOME EMPTY AFTER USER LOGS OFF
IV00343 DELTA VALUES ARE WRONG FOR SOME CHANNELS
IV04704 THE AGENT CORE DUMP WHEN TAKE ACTION REFRESH BROKER DATA FREQUENTLY.
IV01591 THE STATUS OF MULTIPLE INSTANCE BROKER ISN'T RIGHT.
IV02234 WRONG MANAGEMENT OF LONG HOSTNAME IN KMC
IV09397 SITUATION USING UTF8 DESCRIPTION FIELD AND EQUAL OPERATOR DOES
IV06918 QUEUE TIME AVG(MS) COLUMN IN MQ QUEUE STATISTICS WORKSPACE
IV08032 THE MULTI-INSTANCE BROKER(THE SHARED DIRECTORIES HAVING SPACE)
IV10822 HIGH CPU PROCESSING LARGE AMOUNTS OF MONITORING EVENTS
IV11690 MQ CONFIGURATION AGENT FAILS TO CREATE QUEUE OBJECTS
IV06924 INCOMPLETE OR DUPLICATE DATA FOUND IN MQI ACCOUNTING
IV09558 TEP USERID NOT CHECKED WHEN MQ COMMAND ISSUED
OA37177 AGENT CAN'T FIND THE ENVFILE
IV03315 KCF.SQL, KMQ.SQL, KQI.SQL AND KCF_UPG.SQL FROM LCD7-3513-02.TAR CONTAIN ERRORS
IZ95536 WHEN CREATING RESOURCE IN PROTOTYPE VIEW,DEFAULT VALUES OF SOME ATTRIBUTES ARE INVALID IN TERMS OF WMQ DEFINITION.
IZ98659 Duplicate rows in Channel Performance cause false situation alert

Document change history


Date Description of change



[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 February 2012

UID

isg400001001