IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup

Tivoli OMEGAMON XE for Messaging
®
Version 7.0
Installation and Setup Guide
GI11-8074-01
Tivoli OMEGAMON XE for Messaging
®
Version 7.0
Installation and Setup Guide
GI11-8074-01
Note
Before using this information and the product it supports, read the information in “Notices” on page 151.
Revised Edition (February, 2009)
This edition applies to version 7.0 of IBM Tivoli OMEGAMON XE for Messaging (product number 5724-N13) and
to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces GI11–8074–00.
© Copyright International Business Machines Corporation 2005, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . vii
Figures . . . . . . . . . . . . . . . ix
About this publication . . . . . . . . xi
Intended audience . . . . . . . . . .
Publications . . . . . . . . . . . .
IBM Tivoli OMEGAMON XE for Messaging
library . . . . . . . . . . . . .
Related publications . . . . . . . .
Accessing terminology online . . . . .
Accessing publications online . . . . .
Ordering publications. . . . . . . .
Accessibility . . . . . . . . . . . .
Tivoli technical training . . . . . . . .
Support for problem solving . . . . . .
Conventions used in this publication . . .
Typeface conventions . . . . . . . .
.
.
. xi
. xi
.
. xi
. xii
. xii
. xiii
. xiii
. xiii
. xiii
. xiii
. xiv
. xiv
.
.
.
.
.
.
.
.
.
Part 1. Preparing for installation of
IBM Tivoli OMEGAMON XE for
Messaging . . . . . . . . . . . . . 1
Chapter 1. Introducing IBM Tivoli
OMEGAMON XE for Messaging. . . . . 3
IBM Tivoli OMEGAMON XE for Messaging .
IBM Tivoli Monitoring . . . . . . .
Chapter 2. Installation roadmap
.
.
.
.
. 3
. 3
. . . . 7
Installing IBM Tivoli OMEGAMON XE for
Messaging on Windows system . . . . .
Installing IBM Tivoli OMEGAMON XE for
Messaging on UNIX or Linux system . . .
Installing IBM Tivoli OMEGAMON XE for
Messaging on i5/OS system . . . . . .
Installing IBM Tivoli OMEGAMON XE for
Messaging on a z/OS system . . . . . .
Uninstalling IBM Tivoli OMEGAMON XE for
Messaging . . . . . . . . . . . .
.
.
. 7
.
.
. 7
.
.
. 8
.
.
. 8
.
.
. 9
Chapter 3. Preparing for installation . . 11
Upgrading from a previous installation . .
General guidelines . . . . . . . . .
Collecting information for Tivoli Enterprise
Monitoring Server . . . . . . . . .
UNIX system considerations . . . . . .
Using fully qualified path names . . .
Multiple Network Interface Cards . . .
Hardware and software prerequisites . . .
Windows system prerequisites . . . .
UNIX and Linux system prerequisites .
i5/OS system prerequisites . . . . .
© Copyright IBM Corp. 2005, 2009
.
.
.
.
. 11
. 11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12
12
12
13
13
13
15
19
Part 2. Installing IBM Tivoli
OMEGAMON XE for Messaging . . . 21
Chapter 4. Installing application
support . . . . . . . . . . . . . . 23
Installing application support at the Tivoli
Enterprise Monitoring Server . . . . . . . .
Installing application support at a Tivoli
Enterprise Monitoring Server on Windows
system . . . . . . . . . . . . . . .
Installing application support at a Tivoli
Enterprise Monitoring Server on UNIX or Linux
system . . . . . . . . . . . . . . .
Installing application support at a hub Tivoli
Enterprise Monitoring Server on a z/OS system .
Installing application support at the Tivoli
Enterprise Portal Server . . . . . . . . . .
Installing application support at a Tivoli
Enterprise Portal Server on Windows system . .
Installing application support at a Tivoli
Enterprise Portal Server on UNIX or Linux
system . . . . . . . . . . . . . . .
Configuring the Tivoli Enterprise Portal Server
on UNIX or Linux system . . . . . . . .
Installing application support at the Tivoli
Enterprise Portal desktop client. . . . . . . .
Installing application support at a Tivoli
Enterprise Portal desktop client on Windows
system . . . . . . . . . . . . . . .
Installing application support at a Tivoli
Enterprise Portal desktop client on Linux system .
Configuring the Tivoli Enterprise Portal desktop
client . . . . . . . . . . . . . . .
23
23
29
30
34
34
36
37
42
42
43
44
Chapter 5. Setting up the WebSphere
MQ configuration database . . . . . . 45
Setting up the configuration database on Windows
systems. . . . . . . . . . . . . . . . 45
Setting up the configuration database on UNIX and
Linux systems . . . . . . . . . . . . . 46
Chapter 6. Installing the language
packs . . . . . . . . . . . . . . . 51
Installing a language pack on Windows system .
Installing a language pack on UNIX or Linux
system . . . . . . . . . . . . . . .
. 51
. 52
Chapter 7. Installing IBM Tivoli
OMEGAMON XE for Messaging on
Windows system . . . . . . . . . . 53
Pre-installation tasks . . . . .
Installing and initializing agents .
InstallShield Wizard installation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
. 53
. 53
iii
Silent Installation
.
.
.
.
.
.
.
.
.
.
. 57
Chapter 8. Installing IBM Tivoli
OMEGAMON XE for Messaging on
UNIX and Linux systems . . . . . . . 61
Installing from the command line . . . .
Performing a silent installation . . . . .
Installing components with a response file
Configuring to connect an agent to the Tivoli
Enterprise Monitoring Server . . . . .
.
.
.
.
.
.
. 61
. 62
. 63
.
.
. 65
Chapter 9. Installing IBM Tivoli
OMEGAMON XE for Messaging on
i5/OS systems . . . . . . . . . . . 67
Pre-installation tasks . . . . . . . . .
Verifying TCP/IP configuration. . . . .
Updating IBM Tivoli Monitoring OS agent .
Deleting old versions of agents . . . . .
Preparing your WebSphere MQ environment
Checking the authority level of the user ID .
Compiling information about your i5/OS
systems. . . . . . . . . . . . .
Configuring IBM Tivoli OMEGAMON XE for
Messaging across a firewall . . . . . .
Installing IBM Tivoli OMEGAMON XE for
Messaging . . . . . . . . . . . . .
Installing from a PC CD-ROM . . . . .
Installing from an i5/OS system CD-ROM
(command line) . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
67
67
68
68
68
69
.
. 70
.
. 71
.
.
. 73
. 73
.
. 75
Part 3. Configuring IBM Tivoli
OMEGAMON XE for Messaging . . . 79
Chapter 10. Configuring IBM Tivoli
OMEGAMON XE for Messaging on
Windows system . . . . . . . . . . 81
Before Configuring IBM Tivoli OMEGAMON XE for
Messaging . . . . . . . . . . . . . . .
Configuring WebSphere Message Broker Monitoring
Authorizing the agent . . . . . . . . . .
Configuring the WebSphere Message Broker
Monitoring agent . . . . . . . . . . .
Creating multiple instances of the WebSphere
Message Broker Monitoring agent (optional) . .
Installing the CandleMonitor node in broker
environments (optional) . . . . . . . . .
Configuring WebSphere MQ Configuration . . . .
Configuring the WebSphere MQ Configuration
agent . . . . . . . . . . . . . . .
Creating multiple instances of the WebSphere
MQ Configuration agent (optional) . . . . .
Configuring WebSphere MQ Monitoring. . . . .
Creating default objects . . . . . . . . .
Authorizing user IDs . . . . . . . . . .
Configuring the monitoring agent . . . . . .
Creating multiple instances of the WebSphere
MQ Monitoring agent (optional) . . . . . .
iv
81
81
81
82
82
83
84
84
85
85
85
86
86
Starting and Stopping the components
OMEGAMON XE for Messaging . .
Starting the components . . . .
Stopping the components. . . .
of IBM Tivoli
. . . . . 87
. . . . . 87
. . . . . 88
Chapter 11. Configuring IBM Tivoli
OMEGAMON XE for Messaging on
UNIX and Linux system . . . . . . . 89
Configuring WebSphere Message Broker Monitoring
Creating library links to start the agent (Linux
systems only). . . . . . . . . . . . .
Creating a link to the DB2 library . . . . . .
Authorizing the agent . . . . . . . . . .
Defining the required environment variable
(Linux zSeries only) . . . . . . . . . .
Configuring the agent using Manage Tivoli
Enterprise Monitoring Services . . . . . . .
Configuring the agent from the command line. .
Starting or stopping multiple agents using the
itmcmd agent command . . . . . . . . .
Customizing parameters . . . . . . . . .
Creating multiple instances of the WebSphere
Message Broker Monitoring agent (optional) . .
Installing the CandleMonitor node (optional) . .
Configuring WebSphere MQ Configuration . . . .
Creating multiple instances of the WebSphere
MQ Configuration agent (optional) . . . . .
Configuring WebSphere MQ Monitoring. . . . .
Assigning the agent to a user group . . . . .
Creating default objects . . . . . . . . .
Creating multiple instances of the WebSphere
MQ Monitoring agent (optional) . . . . . .
Customizing monitoring options (optional) . . .
Starting or stopping the agents . . . . . . . .
Changing the file permissions for agents . . .
Starting an agent from the Manage Tivoli
Enterprise Monitoring Services . . . . . . .
Stopping an agent from the Manage Tivoli
Enterprise Monitoring Services . . . . . . .
Starting an agent from the command line . . .
Stopping an agent from the command line . . .
89
89
90
90
91
92
92
92
92
93
93
94
95
95
95
95
96
96
97
97
97
98
98
98
Chapter 12. Configuring IBM Tivoli
OMEGAMON XE for Messaging on
i5/OS system . . . . . . . . . . . 101
Configuring WebSphere MQ Configuration . . .
Procedure . . . . . . . . . . . . .
Verifying installation and configuration. . . .
Configuring WebSphere MQ Monitoring . . . .
Configuring WebSphere MQ Monitoring . . .
Verifying installation and configuration. . . .
Starting or stopping the agent from a command
line . . . . . . . . . . . . . . . .
Customizing monitoring options (optional) . .
Creating multiple instances of the WebSphere
MQ Monitoring agent (optional) . . . . . .
86
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
101
101
103
104
104
106
107
107
109
Part 4. Deploying monitoring
across your environment from a
central location . . . . . . . . . . 111
Chapter 13. Deploying monitoring
across your environment from a
central location . . . . . . . . . . 113
Populating your agent depot . . . . . . . .
Populating the agent depot from the installation
image . . . . . . . . . . . . . . .
Populating the agent depot with the tacmd
addBundles command . . . . . . . . .
Changing the agent depot location . . . . .
Sharing an agent depot across your environment
Deploying agents . . . . . . . . . . . .
Deploying through Tivoli Enterprise Portal . .
Deploying through the command line . . . .
UNIX and Linux systems: deploying through
the command line . . . . . . . . . . .
Windows systems: deploying through the
command line . . . . . . . . . . . .
113
114
116
117
117
118
118
119
119
120
Part 5. Uninstalling IBM Tivoli
OMEGAMON XE for Messaging . . 121
Chapter 14. Uninstalling the
components of IBM Tivoli
OMEGAMON XE for Messaging. . . . 123
Uninstalling components on Windows system . .
Silent uninstallation . . . . . . . . . .
Uninstalling components on UNIX or Linux system
Silent uninstallation . . . . . . . . . .
Uninstalling components on i5/OS system . . .
Uninstalling remote deployment files (all systems)
123
124
125
126
126
127
Appendix A. Product codes . . . . . 131
Appendix B. Language codes . . . . 133
Appendix C. Architecture codes . . . 135
Appendix D. Supported operating
systems. . . . . . . . . . . . . . 137
Appendix E. Operating systems
supported for Tivoli Enterprise
Monitoring Server, Tivoli Enterprise
Portal Server, and Tivoli Enterprise
Portal client . . . . . . . . . . . . 141
Appendix F. UNIX Multi-Platform
installation program configuration
files . . . . . . . . . . . . . . . 145
Configuration File Types . .
User-Input type . . . .
Template type . . . . .
Custom-Configuration type.
Additional configuration file
. . .
. . .
. . .
. . .
support
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
145
145
145
146
146
Appendix G. Accessibility . . . . . . 149
Navigating the interface using the keyboard .
Magnifying what is displayed on the screen .
.
.
. 149
. 149
Notices . . . . . . . . . . . . . . 151
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 152
Index . . . . . . . . . . . . . . . 155
Part 6. Appendixes . . . . . . . . 129
Contents
v
vi
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
Worksheet for installation . . . . . . . . . . . . . . . . . . . . .
Windows system installation requirements for each component . . . . . . . .
Operating system patches required for GSKit . . . . . . . . . . . . . .
UNIX system installation requirements for each component . . . . . . . . .
Communications protocol for Tivoli Enterprise Monitoring Server . . . . . . .
Database configuration parameters . . . . . . . . . . . . . . . . . .
Tivoli Enterprise Monitoring Server protocols and values on UNIX or Linux system .
Parameters in a response file . . . . . . . . . . . . . . . . . . . .
Communication protocol settings . . . . . . . . . . . . . . . . . .
Parameters for the configure TEMA (CFGOMAMC) Dialog . . . . . . . . .
Parameters for The configure TEMA(CFGOMAMQ) Dialog . . . . . . . . .
Parameters for The configure TEMA(CFGOMAMQ) Dialog . . . . . . . . .
Product codes . . . . . . . . . . . . . . . . . . . . . . . .
Language codes for the supported languages . . . . . . . . . . . . . .
Operating system architecture abbreviations . . . . . . . . . . . . . .
Supported Windows operating systems . . . . . . . . . . . . . . . .
Supported UNIX, i5/OS and z/OS operating systems . . . . . . . . . . .
Supported Linux operating systems . . . . . . . . . . . . . . . . .
Supported Windows operating systems . . . . . . . . . . . . . . . .
Supported UNIX, i5/OS, and z/OS operating systems . . . . . . . . . . .
Supported Linux operating systems . . . . . . . . . . . . . . . . .
Additional configuration files supported . . . . . . . . . . . . . . .
© Copyright IBM Corp. 2005, 2009
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 12
. 14
. 16
. 17
. 27
. 28
. 38
. 63
. 65
. 101
. 104
. 109
. 131
. 133
. 135
. 137
. 138
. 138
. 141
. 142
. 142
. 146
vii
viii
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Agent–Server–Client Architecture . . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard welcome window during the installation of the application support at a Tivoli
Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for prerequisites installation during the installation of the application
support at a Tivoli Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for feature selection during the installation of the application support at a
Tivoli Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for agent deployment during the installation of the application support at
a Tivoli Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for setup type selection during the installation of the application support
at a Tivoli Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard welcome window during the installation of the application support at a Tivoli
Enterprise Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for prerequisites installation during the installation of the application
support at a Tivoli Enterprise Portal Server . . . . . . . . . . . . . . . . . . . . . .
Configuring Tivoli Enterprise Portal Server . . . . . . . . . . . . . . . . . . . . . .
Configuring Tivoli Enterprise Monitoring Server connections . . . . . . . . . . . . . . . .
Configuring agent parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard welcome window during the installation of the monitoring agents . . . . .
The InstallShield Wizard window for prerequisites installation during the installation of the monitoring
agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The InstallShield Wizard window for feature selection during the installation of the monitoring agents
The InstallShield Wizard window for agent deployment during the installation of the monitoring agents
© Copyright IBM Corp. 2005, 2009
. 4
. 24
. 25
. 26
. 26
. 27
. 34
.
.
.
.
.
35
38
38
39
54
. 55
56
56
ix
x
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
About this publication
IBM Tivoli OMEGAMON XE for Messaging (OMEGAMON for Messaging) helps
you monitor, analyze, and manage your IBM® business integration systems. It
consists of the following components:
v WebSphere MQ Monitoring agent
v WebSphere MQ Configuration agent
v WebSphere Message Broker Monitoring agent
Note: Before you can follow any of the instructions in this book, IBM Tivoli
Monitoring 6.2 FP1 or above must have been installed in your environment.
See the installation and configuration books listed in Publications section
for detailed instructions.
This guide explains how to install IBM Tivoli OMEGAMON XE for Messaging on
Windows® system, UNIX® system, Linux® system and i5/OS® system. See the
Program Directory of IBM Tivoli OMEGAMON XE for Messaging for information
about how to install it on z/OS® systems.
Intended audience
This publication is designed for those who are responsible for installing IBM Tivoli
OMEGAMON XE for Messaging, which include the following:
v System administrators
v System programmers
v Network administrators
v IBM Support and Field Systems Engineers
Before you can follow any of the instructions in this book, the following
components of IBM Tivoli Monitoring 6.2 FP1 or above must have been installed in
your environment:
v
v
v
v
Tivoli Enterprise Monitoring Server (monitoring server)
Tivoli Enterprise Portal Server (portal server)
Tivoli Enterprise Portal (portal) desktop client
Warehouse Proxy (if you intend to use historical reporting or save historical data
to a database for reference)
See the installation and configuration books listed in Publications for detailed
instructions.
Publications
This section lists publications in the IBM Tivoli® OMEGAMON® XE for Messaging
library and related documents. The section also describes how to access Tivoli
publications online and how to order Tivoli publications.
IBM Tivoli OMEGAMON XE for Messaging library
This following documents provide information about IBM Tivoli OMEGAMON XE
for Messaging:
© Copyright IBM Corp. 2005, 2009
xi
v IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide, GI11-8074
Describes how to install IBM Tivoli OMEGAMON XE for Messaging on
Windows, UNIX, Linux and i5/OS systems.
v Upgrading to IBM Tivoli OMEGAMON XE for Messaging 7.0
Provides information about how to upgrade or migration from previous versions
to IBM Tivoli OMEGAMON XE for Messaging 7.0.
v IBM Tivoli OMEGAMON XE for Messaging on z/OS: Configuration Guide,
SC23-7951
Provides information about installing and setting up IBM Tivoli OMEGAMON
XE for Messaging and upgrading from a previous installation.
v IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ Monitoring User's
Guide, SC23-7952
Provides instructions for using the features of WebSphere® MQ Monitoring.
v IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ Configuration User's
Guide, SC23-7953
Provides instructions for using the features of WebSphere MQ Configuration.
v IBM Tivoli OMEGAMON XE for Messaging: WebSphere Message Broker Monitoring
User's Guide, SC23-7954
Provides instructions for using the features of WebSphere Message Broker
Monitoring.
v IBM Tivoli OMEGAMON XE for Messaging: Problem Determination Guide,
GI11–8075
Provides problem determination and resolution information for the issues most
commonly encountered with IBM Tivoli OMEGAMON XE for Messaging.
v IBM Tivoli OMEGAMON XE for Messaging: WebSphere InterChange Server
Monitoring User's Guide, SC23-7950
Provides instructions for using the features of WebSphere InterChange Server
Monitoring.
Related publications
The following documents also provide useful information:
v IBM Tivoli Monitoring Administrator’s Guide, SC32-9408
Describes the support tasks and functions required for the Tivoli Enterprise
Portal Server and clients, including Tivoli Enterprise Portal user administration.
v IBM Tivoli Monitoring User’s Guide, SC32-9409
Provides hands-on lessons and detailed instructions for all Tivoli Enterprise
Portal features.
v IBM Tivoli Monitoring Problem Determination Guide, GC32-9458.
Provides information and messages to assist users with troubleshooting
problems with IBM Tivoli Monitoring.
Accessing terminology online
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. This glossary is available at http://
publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm.
The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at
http://www.ibm.com/software/globalization/terminology.
xii
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Accessing publications online
The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both. Refer to the readme file on
the CD for instructions on how to access the documentation.
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli Information Center Web
site at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/
com.ibm.itm.doc/welcome.htm.
Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.
Ordering publications
You can order many Tivoli publications online at http://
www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.
You can also order by telephone by calling one of these numbers:
v In the United States: 800-879-2755
v In Canada: 800-426-4968
In other countries, contact your software account representative to order Tivoli
publications. To locate the telephone number of your local representative, perform
the following steps:
1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.
2. Select your country from the list and click Go.
3. Click About this site in the main panel to see an information page that
includes the telephone number of your local representative.
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.
For additional information, see Appendix G, “Accessibility,” on page 149.
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site at http://www.ibm.com/software/tivoli/education.
Support for problem solving
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
Online
Go to the IBM Software Support site at http://www.ibm.com/software/
support/probsub.html and follow the instructions.
About this publication
xiii
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability
workbench that helps you resolve questions and problems with IBM
software products. The ISA provides quick access to support-related
information and serviceability tools for problem determination. To install
the ISA software, go to http://www.ibm.com/software/support/isa.
Problem determination information
For more information about resolving problems, see the problem
determination information for this product.
Conventions used in this publication
This document uses several conventions for special terms and actions, and for
operating-system-dependent commands and paths.
Typeface conventions
This publication uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
Italic
v Citations (examples: titles of publications, diskettes, and CDs
v Words defined in text (example: a nonswitched line is called a
point-to-point line)
v Emphasis of words and letters (words as words example: "Use the word
that to introduce a restrictive clause."; letters as letters example: "The
LUN address must start with the letter L.")
v New terms in text (except in a definition list): a view is a frame in a
workspace that contains data.
v Variables and values you must provide.
Monospace
v Examples and code examples
v Message text and prompts addressed to the user
v Text that the user must type
xiv
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 1. Preparing for installation of IBM Tivoli OMEGAMON XE
for Messaging
This part introduces IBM Tivoli OMEGAMON XE for Messaging and describes
tasks that you need to perform before installing the product.
© Copyright IBM Corp. 2005, 2009
1
2
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 1. Introducing IBM Tivoli OMEGAMON XE for
Messaging
This chapter gives a brief description of IBM Tivoli OMEGAMON XE for
Messaging and its relationship with IBM Tivoli Monitoring. It also provides a
roadmap that directs you to different chapters of the book depending on the
operating system on which you are installing IBM Tivoli OMEGAMON XE for
Messaging.
IBM Tivoli OMEGAMON XE for Messaging
IBM Tivoli OMEGAMON XE for Messaging is designed to:
v Provide stable, comprehensive, and proactive monitoring and management
capabilities with robust security features for IBM WebSphere MQ and IBM
WebSphere Message Broker on a variety of platforms.
v Deliver rapid time-to-value and greater ease-of-use analyses and solutions
through a powerful set of utility tools that leverage common IBM Tivoli
Monitoring technology.
IBM Tivoli OMEGAMON XE for Messaging helps:
v Monitor the critical performance data related to WebSphere MQ and WebSphere
Message Broker.
v Provide real-time status on the availability and performance of WebSphere MQ
and WebSphere Message Broker components.
v Collect monitoring data for use in historical reporting, performance analysis,
trend prediction, and enterprise-wide business impact analysis.
v Configure all WebSphere MQ resources from a central repository that allows you
to verify all configurations prior to deployment, schedule deployment of all
WebSphere MQ objects, and provide for backup of WebSphere MQ resources.
v Identify problems in real time and deliver quick problem resolution through
local correlation, root cause analysis, and corrective actions.
IBM Tivoli Monitoring
IBM Tivoli Monitoring manages system and network applications on a variety of
platforms and keeps track of the availability and performance of all parts of your
enterprise. IBM Tivoli Monitoring provides IBM Tivoli OMEGAMON XE for
Messaging with the following facilities:
v Visualize real-time monitoring data from your environment.
v Monitor resources in your environment for certain conditions.
v Establish performance thresholds and raise alerts when thresholds are exceeded
or values are matched.
v Trace the causes leading up to an alert.
v Create and send commands to systems in your managed enterprise by means of
the Take Action feature.
v Use integrating reporting to create comprehensive reports about system
conditions.
v Monitor conditions of particular interest by defining custom queries using the
attributes from an installed agent or from an ODBC-compliant data source.
v Agent deployment and configuration
© Copyright IBM Corp. 2005, 2009
3
v Tivoli Data Warehouse with summarization and pruning capabilities.
IBM Tivoli Monitoring provides IBM Tivoli OMEGAMON XE with a common
agent-server-client architecture:
Tivoli Enterprise Monitoring Server
Tivoli Enterprise
Portal Clients
Monitoring Agents
Tivoli Enterprise Portal Server
Figure 1. Agent–Server–Client Architecture
Tivoli Enterprise Monitoring Server
Tivoli Enterprise Monitoring Server gathers data from the Tivoli Enterprise
Monitoring agents and acts as a collection and control point for alerts received
from the agents. The Tivoli Enterprise Monitoring Server sends the data it receives
from the agents to Tivoli Enterprise Portal clients, where it is displayed in tabular
or graphic views in a set of predefined or customized workspaces. The Tivoli
Enterprise Monitoring Server also accepts requests for information or action from
Tivoli Enterprise Portal clients and distributes them to the agents for execution.
Tivoli Enterprise Portal
Tivoli Enterprise Portal is the Java-based interface to the data monitoring and
management resources of IBM Tivoli Monitoring. Depending on how it is installed,
Tivoli Enterprise Portal can be used as either a desktop or browser-based client.
Tivoli Enterprise Portal has its own server, Tivoli Enterprise Portal Server. Tivoli
Enterprise Portal Server performs common Tivoli Enterprise Portal functions and
serves to lighten the Tivoli Enterprise Portal client.
Tivoli Enterprise Monitoring agents
Tivoli Enterprise Monitoring agents collect system or application data from
monitored, or managed, systems. The WebSphere Message Broker Monitoring
agents, for example, monitor WebSphere Message Brokers and their message flows.
The data are passed to the Tivoli Enterprise Monitoring Server, and displayed in
the Tivoli Enterprise Portal client.
Tivoli Enterprise Monitoring agents can also compare the current values of
monitored properties against a set of defined conditions, and trigger alerts or
actions when conditions warrant. They can accept and execute requested actions
relayed to them from Tivoli Enterprise Portal clients by the Tivoli Enterprise
Monitoring Server.
4
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Where to find more information
For more information about IBM Tivoli Monitoring, see the Tivoli Enterprise Portal
online help and the IBM Tivoli Monitoring documentation which is available in the
online Tivoli software information center.
Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Messaging
5
6
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 2. Installation roadmap
Depending on the operating system on which you are installing the agents of IBM
Tivoli OMEGAMON XE for Messaging, you need to focus on different chapters.
Installing IBM Tivoli OMEGAMON XE for Messaging on Windows
system
If you are installing IBM Tivoli OMEGAMON XE for Messaging on Windows
system, perform the following tasks:
1. Install application support on Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal desktop client. See
Chapter 4, “Installing application support,” on page 23 for information about
how to install application support.
2. Optional: If you want IBM Tivoli OMEGAMON XE for Messaging information
displayed in Tivoli Enterprise Portal to be displayed in a language other than
English, install the language packs. See Chapter 6, “Installing the language
packs,” on page 51 for instructions.
3. Install the agents of IBM Tivoli OMEGAMON XE for Messaging on Windows
system. See Chapter 7, “Installing IBM Tivoli OMEGAMON XE for Messaging
on Windows system,” on page 53 for information about how to install the
agents on Windows system.
4. Configure the agents of IBM Tivoli OMEGAMON XE for Messaging on
Windows system. See Chapter 10, “Configuring IBM Tivoli OMEGAMON XE
for Messaging on Windows system,” on page 81 for information about how to
configure the agents on Windows system.
5. If you have installed the WebSphere MQ Configuration agent in your
environment, you must set up the configuration database. See Chapter 5,
“Setting up the WebSphere MQ configuration database,” on page 45 for
instructions.
You can start using IBM Tivoli OMEGAMON XE for Messaging after completing
these tasks.
Installing IBM Tivoli OMEGAMON XE for Messaging on UNIX or Linux
system
If you are installing the agents of IBM Tivoli OMEGAMON XE for Messaging on
UNIX or Linux system, perform the following tasks:
1. Install application support on Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal desktop client. See
Chapter 4, “Installing application support,” on page 23 for information about
how to install application support.
2. Optional: If you want IBM Tivoli OMEGAMON XE for Messaging information
displayed in Tivoli Enterprise Portal to be displayed in a language other than
English, install the language packs. See Chapter 6, “Installing the language
packs,” on page 51 for instructions.
3. Install the agents of IBM Tivoli OMEGAMON XE for Messaging on UNIX or
Linux system. See Chapter 8, “Installing IBM Tivoli OMEGAMON XE for
© Copyright IBM Corp. 2005, 2009
7
Messaging on UNIX and Linux systems,” on page 61 for information about
how to install the agents on UNIX or Linux system.
4. Configure the agents of IBM Tivoli OMEGAMON XE for Messaging on UNIX
or Linux system. See Chapter 11, “Configuring IBM Tivoli OMEGAMON XE for
Messaging on UNIX and Linux system,” on page 89 for information about how
to configure the agents on UNIX or Linux system.
5. If you have installed the WebSphere MQ Configuration agent in your
environment, you must set up the configuration database. See Chapter 5,
“Setting up the WebSphere MQ configuration database,” on page 45 for
instructions.
You can start using IBM Tivoli OMEGAMON XE for Messaging after completing
these tasks.
Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS system
If you are installing the agents of IBM Tivoli OMEGAMON XE for Messaging on
i5/OS system, perform the following tasks:
1. Install application support on Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal desktop client. See
Chapter 4, “Installing application support,” on page 23 for information about
how to install application support.
2. Optional: If you want IBM Tivoli OMEGAMON XE for Messaging information
displayed in Tivoli Enterprise Portal to be displayed in a language other than
English, install the language packs. See Chapter 6, “Installing the language
packs,” on page 51 for instructions.
3. Install the agents of IBM Tivoli OMEGAMON XE for Messaging on i5/OS
system. See Chapter 9, “Installing IBM Tivoli OMEGAMON XE for Messaging
on i5/OS systems,” on page 67 for information about how to install the agents
of IBM Tivoli OMEGAMON XE for Messaging on i5/OS system.
4. Configure the agents of IBM Tivoli OMEGAMON XE for Messaging on i5/OS
system. See Chapter 12, “Configuring IBM Tivoli OMEGAMON XE for
Messaging on i5/OS system,” on page 101 for information about how to
configure the agents of IBM Tivoli OMEGAMON XE for Messaging on i5/OS
system.
5. If you have installed the WebSphere MQ Configuration agent in your
environment, you must set up the configuration database. See Chapter 5,
“Setting up the WebSphere MQ configuration database,” on page 45 for
instructions.
You can start using IBM Tivoli OMEGAMON XE for Messaging after completing
these tasks.
Installing IBM Tivoli OMEGAMON XE for Messaging on a z/OS system
For information about installing IBM Tivoli OMEGAMON XE for Messaging on a
z/OS system, see IBM Tivoli OMEGAMON XE for Messaging on z/OS: Configuration
Guide.
8
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Uninstalling IBM Tivoli OMEGAMON XE for Messaging
If you plan to uninstall one or more of IBM Tivoli OMEGAMON XE for Messaging
components, see Chapter 14, “Uninstalling the components of IBM Tivoli
OMEGAMON XE for Messaging,” on page 123 for information about how to
uninstall its components from Windows system , UNIX or Linux system and i5/OS
system .
Chapter 2. Installation roadmap
9
10
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 3. Preparing for installation
This chapter explains a series of steps that must be performed before installing
IBM Tivoli OMEGAMON XE for Messaging. The information in this chapter
applies to both users who are upgrading from a previous version of IBM Tivoli
OMEGAMON XE for Messaging and those who are installing the software for the
first time, unless specifically stated otherwise.
Upgrading from a previous installation
If you are upgrading from a previous version, read Upgrading to IBM Tivoli
OMEGAMON XE for Messaging 7.0 for instructions about how to upgrade from a
previous version to IBM Tivoli OMEGAMON XE for Messaging 7.0.
General guidelines
Before starting to install IBM Tivoli OMEGAMON XE for Messaging, consider the
following points to ensure that your environment is suitable for installation.
1. Ensure that all IBM Tivoli Monitoring components required by IBM Tivoli
OMEGAMON XE for Messaging have been installed.
Before installing IBM Tivoli OMEGAMON XE for Messaging, the following
IBM Tivoli Monitoring 6.2 FP1 components must be installed and running
correctly:
v Tivoli Enterprise Monitoring Server
v Tivoli Enterprise Portal Server
v Tivoli Enterprise Portal desktop client
v The Warehouse Proxy. This component is optional and only required if you
intend to use historical reporting or save historical data to a database for
reference purposes.
If your system is running a version of IBM Tivoli Monitoring prior to IBM
Tivoli Monitoring 6.2 FP1, you must first upgrade this to IBM Tivoli Monitoring
6.2 FP1 or higher. For upgrading instructions, see IBM Tivoli Monitoring
Installation and Setup Guide.
2. Identify where the systems or applications are running.
In general, you can install and configure an IBM Tivoli OMEGAMON XE for
Messaging agent on every operation system where the queue manager or
message broker you want to monitor is running.
3. Identify the communications protocols that are available in your environment.
Use TCP/IP (IP.UDP on Windows system and IP on UNIX and Linux system) ,
IP.PIPE, or SNA for communication between the monitoring agent and the IBM
Tivoli Monitoring components.
4. Install the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal or Tivoli
Enterprise Portal Server before using the z/OS data CD to install corresponding
application support for the ITM components that you installed.
5. Ensure that the operating system of the computer on which you plan to install
IBM Tivoli OMEGAMON XE for Messaging is listed in Appendix D,
“Supported operating systems,” on page 137. If the operating system you are
using is not listed in this section, you might still be able to use WebSphere MQ
Monitoring and WebSphere MQ Configuration remote monitoring and
© Copyright IBM Corp. 2005, 2009
11
configuration features to monitor and configure WebSphere MQ components
remotely. For more information see the following documentation:
v WebSphere MQ Monitoring: Monitoring events on non-supported platforms
in IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ Monitoring
User’s Guide.
v WebSphere MQ Configuration: Configuring a remote queue manager in IBM
Tivoli OMEGAMON XE for Messaging: WebSphere MQ Configuration User’s
Guide.
6. If your environment is protected by a firewall, read the section regarding
firewalls in IBM Tivoli Monitoring: Installation and Setup Guide.
7. If you plan to use the agent remote deployment feature, ensure that the IBM
Tivoli Monitoring OS agent is running on the target computer where you plan
to deploy an agent before installing IBM Tivoli OMEGAMON XE for
Messaging. See Chapter 13, “Deploying monitoring across your environment
from a central location,” on page 113 for information about how to deploy
agent remotely.
Collecting information for Tivoli Enterprise Monitoring Server
Use the following worksheet to gather information for the installation. You will be
required to enter these information during installation:
Table 1. Worksheet for installation
Name of the Tivoli Enterprise Monitoring
Server that the agents will connect to
Host name of the computer on which the
Tivoli Enterprise Monitoring Server that the
agents will connect to is running
IP address of the computer on which the
Tivoli Enterprise Monitoring Server that the
agents will connect to is running
Encryption key for the hub Tivoli Enterprise
Monitoring Server
Agent product code or codes
Communications protocol details of the
Tivoli Enterprise Monitoring Server that the
agents will connect to
Root user password (UNIX or Linux system)
UNIX system considerations
This section provides information that you need to know before installing IBM
Tivoli OMEGAMON XE for Messaging on UNIX system.
Using fully qualified path names
Because there are a large number of different versions of UNIX system and
possible user environments, it is good form to use fully qualified path names,
without pattern-matching characters, when specifying a directory during the
installation process. IBM scripts use the Korn shell, and when a new process or
shell is invoked, use of symbolic links, environment variables, or aliases can cause
unexpected results.
12
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Multiple Network Interface Cards
If the computer on which Tivoli Enterprise Monitoring Server is installed has more
than one Network Interface Card (NIC), you must identify which NIC to use when
specifying the Tivoli Enterprise Monitoring Server name and host name during the
installation. It is possible that the host name of the system might not match the
interface name, even when only one NIC exists. In either of these situations, for
IBM Tivoli OMEGAMON XE for Messaging monitoring agents to be able to
connect to the Tivoli Enterprise Monitoring Server, you need to specify an
additional variable when configuring the Tivoli Enterprise Monitoring Server or
the monitoring agents. This variable is listed under the Optional Primary Network
Name in the configuration dialogs or during the command line installation.
Hardware and software prerequisites
See the following sections for information about the software and hardware
prerequisites of different operating systems:
v “Windows system prerequisites” on page 13
v “UNIX and Linux system prerequisites” on page 15
v “i5/OS system prerequisites” on page 19
Windows system prerequisites
This section lists the hardware and software prerequisites for installing IBM Tivoli
OMEGAMON XE for Messaging on Windows system.
Software Requirements
Windows Service Packs:
v Windows 2000 Professional: Service Pack 3 or above
v Windows XP Professional: Service Pack 1 or above
Communications among components: TCP/IP communications:
v One of the following must be installed:
– Microsoft® Winsock (version 1.1 or higher)
– Microsoft TCP/IP protocol stack
v TCP/IP network services (such as NIS, DNS and the HOSTS file) must be
configured to return the fully qualified host name.
SNA communications: A 32-bit version of one of the following SNA Server or
Client products must be installed:
v IBM PCOMM (version 4.11 or higher). Fix IC19970 is required on Windows 2000
Server or Workstation.
v IBM Communications Server (version 5.0 or higher). Fixes JR10466 and JR10368
are required for SNA Server version 5.0.
v Microsoft SNA Server (version 3 or higher). Service Pack 1 is required for SNA
Server version 4.0.
v Attachmate EXTRA! (version 6.2, 6.3, or 6.4). Fix for case number 1221139 is
required for versions 6.2 and 6.3. Fix for case number 1274151 is required for
version 6.4.
v Walldata RUMBA (version 5.1 or higher). Walldata PTF OPK52002 is required for
versions 5.2A or lower.
Chapter 3. Preparing for installation
13
Hardware Requirements
Disk space: Before installing IBM Tivoli OMEGAMON XE for Messaging, ensure
that the system on which you are installing meets the following disk space
requirements:
v
v
v
v
650 MB free disk space on the installation drive
10 MB free disk space on the system user drive
250 MB temporary free disk space for installation files
Additional free disk space for log file growth
Memory: Before installing IBM Tivoli OMEGAMON XE for Messaging, ensure
that the system on which you are installing meets the following memory
requirements:
v Minimum: 512 MB
v Recommended: 1 GB
CPU: Before installing IBM Tivoli OMEGAMON XE for Messaging, ensure that
the system on which you are installing meets the following CPU requirements:
RISC architectures:
v Minimum: 1 GHz
Intel architectures:
v Minimum: 1 GHz
v Recommended: 2 GHz
Requirements for individual components
This table lists the individual requirements for installing each IBM Tivoli
OMEGAMON XE for Messaging component.
Table 2. Windows system installation requirements for each component
Component name
WebSphere Message
Broker Monitoring
Windows system version
v Windows 2000 Server
or Advanced Server
v Windows 2003 Server
(32 bit)
v Windows XP
Professional Edition
with service pack 1 or
higher
14
Hardware
v 18 MB disk space
Other requirements
One of the following IBM broker
products:
v Additional 210 MB
v IBM WebSphere Business
disk space for remote
Integration Event Broker 5
deployment support, if
v IBM WebSphere Business
enabled
Integration Message Broker 5
v Additional 150 MB
v IBM WebSphere Business
Integration Message Broker
with Rules and Formatter
Extension 5
v Additional 70 MB disk
v IBM WebSphere Event Broker 6
space for the Global
Security Toolkit and
v IBM WebSphere Message Broker
IBM Java™ Virtual
6
Machine.
v IBM WebSphere Message Broker
v Additional disk space
6.1
for historical data
v IBM WebSphere Message Broker
storage, if historical
with Rules and Formatter
data collection is
Extension 6
enabled
disk space for Tivoli
Enterprise Monitoring
Agent Framework
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Table 2. Windows system installation requirements for each component (continued)
Component name
WebSphere MQ
Monitoring
Windows system version
v Windows 2000 Server
or Advanced Server
v Windows 2003 Server
v Windows XP
Professional Edition
with service pack 1 or
higher
v Windows 2008 Server
Hardware
Other requirements
v IBM WebSphere MQ 6.0 or 7.0
v 4 MB disk space
v Additional 210 MB
disk space for remote
deployment support, if
enabled
v Additional 150 MB
disk space for Tivoli
Enterprise Monitoring
Agent Framework
v Additional 70 MB disk
space for the Global
Security Toolkit and
IBM Java Virtual
Machine.
v Additional disk space
for historical data
storage, if historical
data collection is
enabled
WebSphere MQ
Configuration
v Windows 2000 Server
or Advanced Server
v Windows 2003 Server
v Windows XP
Professional Edition
with service pack 1 or
higher
v Windows 2008 Server
v 4 MB disk space
v IBM WebSphere MQ 6.0 or 7.0
v Additional 210 MB
disk space for remote
deployment support, if
enabled
The WebSphere MQ configuration
agent requires one of the
following databases to store
configuration information:
v Additional 150 MB
disk space for Tivoli
Enterprise Monitoring
Agent Framework
v The WebSphere MQ
configuration internal
configuration database, which is
installed automatically as part
of Tivoli Enterprise Monitoring
v Additional 70 MB disk
Server.
space for the Global
Security Toolkit and
v DB2 Universal Database (UDB)
IBM Java Virtual
Workgroup Server Edition 8.1
Machine.
or above, which must be
v Additional disk space
is required for storing
the WebSphere MQ
configuration database
on the system where
the hub Tivoli
Enterprise Monitoring
Server is installed.
installed on the same server as
the hub Tivoli Enterprise
Monitoring Server. If the Tivoli
Enterprise Monitoring Server is
installed on a z/OS system and
you want to use the DB2®
configuration database, DB2 8.1
or higher is required. If DB2 is
not already installed on the
z/OS system that hosts the
Tivoli Enterprise Monitoring
Server, it must be purchased
and installed separately.
UNIX and Linux system prerequisites
This section lists the hardware and software prerequisites for installing IBM Tivoli
OMEGAMON XE for Messaging on UNIX or Linux system.
Chapter 3. Preparing for installation
15
Software Requirements
The software prerequisites for installing IBM Tivoli OMEGAMON XE for
Messaging on UNIX or Linux system are as follows:
Shell: Korn shell command interpreter.
GSKit: GSKit, which is used to provide security between monitoring components.
The following table lists the operating system patches required for GSKit:
Table 3. Operating system patches required for GSKit
Operating system
Patches required
Solaris V8
108434-14, 111327-05, 108991, 108993-31,
108528-29, 113648-03, 116602-01, 111317-05,
111023-03, 115827-01
Solaris V9
111711-08
Solaris V10
125100-10
HP-UX V11i
PHSS_26946, PHSS_33033
®
AIX V5.x
RedHat Enterprise Linux 4 Intel
xlC.aix50.rte.6.0.0.3 or later
®
v compat-gcc-32-c++-3.2.3-46.1.i386.rpm
v compat-gcc-32-3.2.3-46.1.i386.rpm
v compat-libstdc++-33-3.2.3-47.3.i386.rpm
SUSE Linux Enterprise Server 8 Intel
none
SUSE Linux Enterprise Server 9 Intel
none
Communications:
v Communications between components can use the TCP/IP, SNA, or IP.PIPE
protocols.
For TCP/IP communication, and TCP/IP network service can be used (such as
NIS, DNS or the /etc/hosts file). These must be configured to return the fully
qualified host name, not an abbreviated name. For example, HostName.ibm.com
v Ethernet or token ring LAN connection
Hardware Requirements
Disk space:
v 450 MB free disk space on installation drive
v 10 MB free disk space on system user drive
v 650 MB temporary free disk space for installation files
v Additional disk space for log file growth
Memory: Before installing IBM Tivoli OMEGAMON XE for Messaging, ensure
that the system on which you are installing meets the following memory
requirements:
v Minimum: 512 MB
v Recommended: 1 GB
Additional Solaris requirements
On Solaris platforms, X Window System Version 11 (X11) support is required. If
X11 support has not been installed, you must add these two modules to your
configuration:
16
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
v LIBX11.SO.4
v LIBXEXT.SO.4
Additional AIX requirements
Supported AIX systems must be at the required maintenance level for IBM Java
1.5. Refer to the following Web site for the Java 5 AIX maintenance level matrix:
http://www-128.ibm.com/developerworks/java/jdk/aix/service.html. Component
xlC.aix50.rte must be at 8.0.0.4. See the following Web site for installation
instructions: http://www-1.ibm.com/support/docview.wss?uid=swg1IY84212. The
AIX C++ compiler must be at version 8. For the Tivoli Enterprise Portal Server,
AIX 5.3 must be at TL5.
Requirements for individual components
This table lists the individual requirements for installing each IBM Tivoli
OMEGAMON XE for Messaging component.
Table 4. UNIX system installation requirements for each component
Component name
WebSphere Message Broker
Monitoring
Operating system
Hardware
Other requirements
v AIX V5.2, V5.3, or V6.1 (32/64 v 10 MB disk
space
bit)
One of the following IBM
broker products:
v Solaris V8, V9, or V10 (32/64
bit)
v HP-UX V11.i (32/64 bit) with
the following Goldpacks
installed:
v Additional 210 v IBM WebSphere Business
Integration Event Broker V5
MB for remote
v IBM WebSphere Business
deployment
Integration Message Broker
support, if
V5
enabled
v Additional 230
MB for Tivoli
Enterprise
– GOLDAPPS11i,
Monitoring
r=B.11.11.0712.475
Agent
Framework,
Remember: For HP-UX
Global Security
V11.11, make sure that the
Toolkit, and
PHSS_30970 patch is installed.
IBM Java
®
v Linux on zSeries or Intel
Virtual
architectures:
Machine.
– SUSE Enterprise Server 8
v
Additional
(2.4.x kernel level), 9 (2.6.x
disk
space for
kernel level), or 10
historical data
– Red Hat Enterprise Linux 3
storage, if
(2.4.x kernel level), 4 (2.6.x
historical data
kernel level), or 5
collection is
v Linux on iSeries® and
enabled.
pSeries®:
– GOLDBASE11i,
r=B.11.11.0712.475
v IBM WebSphere Business
Integration Message Broker
with Rules and Formatter
Extension V5
v IBM WebSphere Event
Broker V6
v IBM WebSphere Message
Broker V6
v IBM WebSphere Message
Broker V6.1
v IBM WebSphere Message
Broker with Rules and
Formatter Extension V6
– SUSE Enterprise Server 9 or
10
– Red Hat Enterprise Linux 4
or 5
Chapter 3. Preparing for installation
17
Table 4. UNIX system installation requirements for each component (continued)
Component name
WebSphere MQ Monitoring
Operating system
Hardware
v AIX V5.2, V5.3, or V6.1(32/64
bit)
v 35 MB disk
space
v Solaris V8, V9, or V10 (32/64
bit)
v Additional 210
MB for remote
deployment
support, if
enabled
v HP-UX V11.i (32/64 bit) with
the following Goldpacks
installed:
v Additional 230
– GOLDBASE11i,
MB for Tivoli
r=B.11.11.0712.475 or a later
Enterprise
version
Monitoring
– GOLDAPPS11i,
Agent
r=B.11.11.0712.475 or a later
Framework,
version
Global Security
Toolkit, and
Remember: For HP-UX
IBM Java
V11.11, make sure that the
Virtual
PHSS_30970 patch is installed.
Machine.
v Linux on zSeries or Intel
v Additional
architectures:
disk space for
– SUSE Enterprise Server 8
historical data
(2.4.x kernel level), 9 (2.6.x
storage, if
kernel level), or 10
historical data
– Red Hat Enterprise Linux 3
collection is
(2.4.x kernel level), 4 (2.6.x
enabled.
kernel level), or 5
v Linux on iSeries and pSeries:
– SUSE Enterprise Server 9 or
10
– Red Hat Enterprise Linux 4
or 5
18
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Other requirements
v IBM WebSphere MQ 6.0 or
7.0
Table 4. UNIX system installation requirements for each component (continued)
Component name
WebSphere MQ
Configuration
Operating system
Hardware
Other requirements
v IBM WebSphere MQ 6.0 or
7.0
v AIX V5.2, V5.3, or V6.1 (32/64 v 35 MB disk
space
bit)
v Solaris V8, V9, or V10 (32/64
bit)
v HP-UX V11.i (32/64 bit) with
the following Goldpacks
installed:
v Additional 210
MB for remote
deployment
support, if
enabled
The WebSphere MQ
configuration agent requires
one of the following databases
to store configuration
information:
v Additional 230 v The WebSphere MQ
MB for Tivoli
configuration internal
Enterprise
configuration database,
– GOLDAPPS11i,
Monitoring
which is installed
r=B.11.11.0712.475
Agent
automatically as part of
Framework,
Remember: For HP-UX
Tivoli Enterprise Monitoring
Global Security
V11.11, make sure that the
Server.
Toolkit, and
PHSS_30970 patch is installed.
v DB2 Universal Database
IBM Java
v Linux on zSeries and Intel
(UDB) Workgroup Server
Virtual
architectures:
Edition v8.1 or higher, which
Machine.
must be installed on the
– SUSE Enterprise Server 8
same server as the hub Tivoli
(2.4.x kernel level), 9 (2.6.x v Additional
disk space is
Enterprise Monitoring Server.
kernel level) or 10
required for
If the Tivoli Enterprise
– Red Hat Enterprise Linux 3
storing the
Monitoring Server is
(2.4.x kernel level), 4 (2.6.x
WebSphere
installed on a z/OS system
kernel level), or 5
MQ
and you want to use the DB2
v Linux on iSeries and pSeries:
configuration
configuration database, DB2
database on
– SUSE Enterprise Server 9 or
v8.1 or higher is required. If
the system
10
DB2 is not already installed
where the hub
on the z/OS system that
– Red Hat Enterprise Linux 4
Tivoli
hosts the Tivoli Enterprise
or 5
Enterprise
Monitoring Server, it must be
Monitoring
purchased and installed
Server is
separately.
installed.
– GOLDBASE11i,
r=B.11.11.0712.475
i5/OS system prerequisites
This section lists the hardware and software prerequisites for installing the
WebSphere MQ Monitoring and WebSphere MQ Configuration agents on i5/OS
systems. The WebSphere Message Broker Monitoring agent is not supported on
i5/OS systems.
Software requirements
v i5/OS 5.3, 5.4, or 6.1.
v WebSphere MQ 6.0 or 7.0.
v If you are using i5/OS 5.3, ensure that PTF SI12116 - OSP-UNPRED System
agent support for i5/OS systems is installed on your system.
v TCP/IP Communication Utilities.
Tip: For information about how to check if TCP/IP Communications Utilities are
installed, see “Compiling information about your i5/OS systems” on page 70.
Hardware requirements
v RISC system
Chapter 3. Preparing for installation
19
v 5250 non-programmable workstation or any workstation running 5250 emulation
connected to an i5/OS system
v 150 MB free disk space for program files
v 50 MB temporary free disk space for running the software
20
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 2. Installing IBM Tivoli OMEGAMON XE for Messaging
This part contains instructions about how to install IBM Tivoli OMEGAMON XE
for Messaging on Windows system, Linux system, UNIX system and i5/OS system.
© Copyright IBM Corp. 2005, 2009
21
22
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 4. Installing application support
All agents require that application support files that contain agent-specific
information be installed on the Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal desktop client that the agents
will connect to. Install application support before starting to install IBM Tivoli
OMEGAMON XE for Messaging agents.
Follows the instructions in the following sections to install application support:
v “Installing application support at the Tivoli Enterprise Monitoring Server”
v “Installing application support at the Tivoli Enterprise Portal Server” on page 34
v “Installing application support at the Tivoli Enterprise Portal desktop client” on
page 42
Installing application support at the Tivoli Enterprise Monitoring Server
Depending on the operating system on which the Tivoli Enterprise Monitoring
Server is installed, follow the instructions in the following sections to install
application support on each Tivoli Enterprise Monitoring Server in your
environment:
v “Installing application support at a Tivoli Enterprise Monitoring Server on
Windows system”
v “Installing application support at a Tivoli Enterprise Monitoring Server on UNIX
or Linux system” on page 29
v “Installing application support at a hub Tivoli Enterprise Monitoring Server on a
z/OS system” on page 30
Installing application support at a Tivoli Enterprise Monitoring
Server on Windows system
Use the following steps to install required application support on a Windows
system Tivoli Enterprise Monitoring Server:
Remember: The Tivoli Enterprise Monitoring Server is stopped during the process.
1. Log on to Windows system using a user ID with Administrator authority.
2. Close any running applications.
3. Insert the IBM Tivoli OMEGAMON XE for Messaging CD-ROM for Windows
system into your CD-ROM drive. Installation begins automatically. If the
InstallShield Wizard does not start automatically, use My Computer to open
your CD-ROM drive and double-click the setup.exe file in the /WINDOWS
subdirectory to launch the installation. If the setup.exe file still fails to run, you
do not have enough disk space to decompress the installation files. Clear some
disk space before starting the installation process again.
The InstallShield Wizard window displays a message welcoming you to the
setup process. This window also contains information about what IBM Tivoli
products you currently have installed and the name and version of the
product contained on the installation CD.
© Copyright IBM Corp. 2005, 2009
23
Figure 2. The InstallShield Wizard welcome window during the installation of the application
support at a Tivoli Enterprise Monitoring Server
4. Click Next on the Welcome window.
Remember: If you already have the OMEGAMON XE for Messaging agent or
application support files installed on this computer, select Modify
on the Welcome window to indicate that you are updating an
existing installation, and then click Next. Then skip to Step 8 on
page 25.
5. The Prerequisites window, containing information about prerequisite software
that must be installed before continuing with the OMEGAMON XE for
Messaging installation is displayed. The prerequisites tested for are the IBM
Global Security Toolkit and IBM Java. The version number of each of these
products already installed on the host system is displayed, along with the
number of the version required by IBM Tivoli OMEGAMON XE for
Messaging. If the Current Version field is empty, then either the version
number of the installed product could not be obtained, or the product was not
detected on the host system. If the version number of either of the installed
products is less than stated in the Required Version field, the required version
of the prerequisite software will be installed automatically. In the Choose
common installation drive for both field enter the drive on which to install
the software, then click Next to proceed with the installation process.
24
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Figure 3. The InstallShield Wizard window for prerequisites installation during the installation
of the application support at a Tivoli Enterprise Monitoring Server
6. If the version number of prerequisite software is less than the required
version, the required version is installed automatically. Once installation of the
prerequisite software is complete, you will be automatically returned to the
OMEGAMON XE for Messaging InstallShield Wizard.
7. Click Accept on the software license.
8. The Select Features window is displayed. Select Tivoli Enterprise Monitoring
Server and click Next.
Remember:
a. If you have other components installed on the same computer, such as
Tivoli Enterprise Portal desktop client, you can also select these
components to install the component-specific application support.
b. If you are updating an existing installation (you selected Modify on the
Welcome window), the Add or Remove Features window is displayed. All
check boxes on this window reflect your choices during the initial
installation. Clearing a check box has the effect of uninstalling the
component. Clear a box only if you want to remove a component.
Chapter 4. Installing application support
25
Figure 4. The InstallShield Wizard window for feature selection during the installation of the
application support at a Tivoli Enterprise Monitoring Server
9. The Agent Deployment window is displayed. If you want to add one or more
agents to the deployment depot, select them and click Next.
Figure 5. The InstallShield Wizard window for agent deployment during the installation of the
application support at a Tivoli Enterprise Monitoring Server
10. Review the installation summary details. Click Next to start the installation. A
message is displayed stating that you will not be able to cancel the installation
or upgrade after this point. Click Yes to continue.
11. Select Install application support files for a Local/Remote Tivoli Enterprise
Monitoring Server and click Next on the Setup Type window.
26
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Figure 6. The InstallShield Wizard window for setup type selection during the installation of
the application support at a Tivoli Enterprise Monitoring Server
12. Specify the default values for any monitoring agents to use when they
communicate with the Tivoli Enterprise Monitoring Server and click OK.
Table 5. Communications protocol for Tivoli Enterprise Monitoring Server
Option or field
Description
TEMS Type
Specify the type of the Tivoli Enterprise
Monitoring Server - hub or remote.
Configuration Auditing
Select if you want auditing to be configured.
Security: Validate User
Select if you want users to be required to
enter their user name and password when
logging onto the system.
Address Translation
Select this option if the firewall shielding the
Tivoli Enterprise Monitoring Server uses
address translation.
Tivoli Event Integration Facility
Select this option if you want to forward
situation events to IBM Tivoli Enterprise
Console®.
Disable Workflow Policy/Tivoli Emitter
Agent Event Forwarding
TEMS name
Enter the name of the Tivoli Enterprise
Monitoring Server.
Protocol for this TEMS
You can enter up to three protocols to be
used when connecting to the Tivoli
Enterprise Monitoring Server. The protocol
specified in the Protocol 1 field will be used
by default. If connection to Tivoli Enterprise
Monitoring Server using this protocol fails,
the protocol specified in the Protocol 2 field
will be used, and if connection still fails, the
protocol specified in the Protocol 3 field is
used. Available protocols are IP.PIPE,
IP.SPIPE, SNA and IP.UDP.
Chapter 4. Installing application support
27
Table 5. Communications protocol for Tivoli Enterprise Monitoring Server (continued)
Option or field
Description
Configure Hot Standby TEMS
Select this option to specify a back-up Tivoli
Enterprise Monitoring Server to be used in
the event of the default Tivoli Enterprise
Monitoring Server failing. Use the options in
this section to select the protocols to use
when connecting to the standby Tivoli
Enterprise Monitoring Server, as with the
Protocol for Tivoli Enterprise Monitoring
Server options mentioned previously.
Once you have finished configuring the Tivoli Enterprise Monitoring Server,
click OK to accept the settings.
13. Specify the host name (or IP address) and port number of the Tivoli
Enterprise Monitoring Server. Click OK to continue.
The next configuration step is to install application support at the Tivoli
Enterprise Monitoring Server.
14. The WMQ Configurator Data Source Parameters window is displayed,
perform the following steps to configure the database used by OMEGAMON
XE for Messaging.
a. Enter the database configuration parameters as show in Table 6:
Table 6. Database configuration parameters
Option
Description
Database Type
Select whether to use OMEGAMON XE for
Messaging’s internal database or an external
DB2 database, accessed using ODBC. The
other options listed in this table are only
applicable to DB2 so if you select the
internal database they cannot be modified.
Data source name
Enter the name of the DB2 data source.
Database Administrator ID
Enter the ID and password of the DB2
database administrator.
WebSphere MQ Configurator Database User
ID
Enter the ID and password of the
WebSphere MQ Configurator database.
b. Click OK to accept the settings entered.
c. If a message is displayed stating that configuration was completed
successfully, click OK, otherwise, if configuration failed, you will be given
the option to return to the configuration window and re-enter the database
settings.
15. Specify the location of the Tivoli Enterprise Monitoring Server on which you
want to enable application support. Select On this computer and click OK.
16. Select which components for which you want to enable application support.
By default, all available application support is selected. Click OK.
17. Click Next on the message that provides information about installing
application support.
18. Click Finish to close the installation wizard.
You have now finished installing application support to the Tivoli Enterprise
Monitoring Server. If you have other monitoring servers in your environment,
install application support on them as well. Once all monitoring servers have been
28
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
upgraded, go to “Installing application support at the Tivoli Enterprise Portal
Server” on page 34 to continue with the installation process.
Installing application support at a Tivoli Enterprise Monitoring
Server on UNIX or Linux system
Use the following steps to install application support on a UNIX or Linux system
Tivoli Enterprise Monitoring Server:
1. Stop the Tivoli Enterprise Monitoring Server by running the following
commands:
cd install_dir/bin
./itmcmd server stop tems_name
where install_dir is the directory where the Tivoli Enterprise Monitoring Server
is installed. The default is /opt/IBM/ITM.
Tip: If you do not know the name of the Tivoli Enterprise Monitoring Server,
view the contents of the install_dir/tables directory. The Tivoli Enterprise
Monitoring Server name is displayed there.
2. Run the following command to create a temporary directory on the computer
where the Tivoli Enterprise Monitoring Server is installed. Make sure that the
full path of the directory does not contain any spaces:
mkdir dir_name
3. Mount the installation CD for UNIX or Linux system to the temporary
directory you just created.
4. Run the following commands:
cd dir_name
./install.sh
where dir_name is the temporary directory you just created.
5. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path of the installation
directory. If a message is displayed stating that the directory already exists
and asking whether to use it, enter 1 (yes) and press enter.
6. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding.
4) Exit install.
Please enter a valid number:
Type 1 to start the installation and press Enter.
7. The first part of the software license agreement is displayed. Press Enter to
view latter parts of the agreement. Once you have finished viewing the
agreement, enter 1 to accept it or 2 to reject it and press Enter. You must
accept the agreement to continue with the installation process.
8. A numbered list of available operating systems and installation components is
displayed. Type the number that corresponds to Tivoli Enterprise
Monitoring Server support and press Enter.
9. Type 1 (yes) to confirm and press Enter. A list of the components for which
you can install application support is displayed.
10. Type the number that corresponds to all of the above and press Enter.
Chapter 4. Installing application support
29
11. Type 1 (yes) to confirm that your selection is correct. The installation process
begins.
12. After all of the components are installed, you are asked whether you want to
install additional products or produce support packages. Type 2 (no) and
press Enter to exit the installation program.
13. Start the Tivoli Enterprise Monitoring Server by running the following
commands:
cd install_dir/bin
./itmcmd server start tems_name
where install_dir is the directory where the Tivoli Enterprise Monitoring Server
is installed.
14. Run the following command to activate application support on the Tivoli
Enterprise Monitoring Server. You must run the command once for each
component, using the component's specific product code. See Appendix A,
“Product codes,” on page 131 for a list of product codes.
./itmcmd support -t tems_name pc
where tems_name is the name of the Tivoli Enterprise Monitoring Server and
pc is the product code of the agent.
15. Stop and restart the Tivoli Enterprise Monitoring Server by running the
following commands:
./itmcmd server stop tems_name
./itmcmd server start tems_name
You have now finished installing application support to the Tivoli Enterprise
Monitoring Server. If you have other monitoring servers in your environment,
install application support on them as well. Once all monitoring servers have been
upgraded, go to “Installing application support at the Tivoli Enterprise Portal
Server” on page 34 to continue with the installation process.
Installing application support at a hub Tivoli Enterprise
Monitoring Server on a z/OS system
If your hub Tivoli Enterprise Monitoring Server is running on a z/OS system, you
must install application support remotely from a Windows system, UNIX system,
or Linux system that hosts either a hub Tivoli Enterprise Portal Server or a hub
Tivoli Enterprise Monitoring Server.
Remember:
1. The hub Tivoli Enterprise Monitoring Server running on a z/OS system must
be started when you add application support to it.
2. Before you do this, make sure you have registered the IBM Tivoli
OMEGAMON XE for Messaging agents to the hub Tivoli Enterprise Monitoring
Server. For more information about registering the monitoring agents with the
hub Tivoli Enterprise Monitoring Server, see IBM Tivoli OMEGAMON XE for
Messaging on a z/OS system: Configuration Guide.
Using Windows system
If the Tivoli Enterprise Portal Server is running on a Windows system, use Manage
Tivoli Enterprise Monitoring Services to install application support on the z/OS
system Tivoli Enterprise Monitoring Server:
1. On the system where the Tivoli Enterprise Portal Server is installed, open
Manage Tivoli Enterprise Monitoring Services by selecting Start → Programs →
IBM Tivoli Monitoring → Manage Tivoli Monitoring Services.
30
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
2. In the Manage Tivoli Enterprise Monitoring Services window, right-click the
name of the Tivoli Enterprise Portal Server. From the menu, select Advanced →
Add TEMS application support. The Add Application Support to the TEMS
window is displayed.
3. Select On a different computer and click OK. A reminder that the Tivoli
Enterprise Monitoring Server running on a z/OS system must be started is
displayed.
4. If the Tivoli Enterprise Monitoring Server is not started, start it and then click
OK to continue. The Non-resident TEMS Connection window is displayed.
5. Enter the name of the Tivoli Enterprise Monitoring Server and select the
communications protocol. The Tivoli Enterprise Monitoring Server name must
be the same as the CMS_NODEID parameter in the KDSENV member in
&rhilev.&rtename.RKANPARU on the z/OS system where the Tivoli Enterprise
Monitoring Server is installed.
Important: The communications protocol you select must be the protocol that
your Tivoli Enterprise Monitoring Server is configured to use.
6. The Non-resident TEMS Connection settings window is displayed. Enter the
following information and click OK to proceed:
v Hostname or IP Address: The fully qualified host name or the IP address of
the system on which your Tivoli Enterprise Monitoring Server is running.
v Port # and/or Port Pools: The port number that the Tivoli Enterprise Portal
Server uses to communicate with the Tivoli Enterprise Monitoring Server on
a z/OS system. The default is 1918.
v Entry Options: Select Convert to upper case (Tivoli Enterprise Monitoring
Server require all information to be in upper case).
7. In the Select the Application Support to Add to the TEMS window, select the
agents for which you want to install application support and then click OK.
Available options are:
v WebSphere MQ Configuration: Configuration Management Support (kcf.sql)
v WebSphere MQ Monitoring: WebSphere MQ Monitoring Agent Support
(kmq.sql)
v WebSphere Message Broker Monitoring: WebSphere Message Broker Support
(kqi.sql)
Tip: Alternative versions of these files with file names ending in _upg can also
be selected. For example, kqi_upg.sql. If you are upgrading from an earlier
version of OMEGAMON XE for Messaging, select the _upg versions of
application support files. If you are not upgrading from an earlier version,
select the standard versions of the files.
8. Recycle the Tivoli Enterprise Monitoring Server. Changes to application support
do not take effect until the Tivoli Enterprise Monitoring Server is restarted.
You have now finished installing application support to the Tivoli Enterprise
Monitoring Server. If you have other monitoring servers in your environment,
install application support on these as well. Once all monitoring servers have been
upgraded, go to “Installing application support at the Tivoli Enterprise Portal
Server” on page 34 to continue with the installation process.
Using UNIX or Linux system
As a prerequisite, you must install a monitoring server, a portal server or a
monitoring agent on the local Linux or UNIX computer. This step is necessary to
make the Manage Tivoli Monitoring Services available on the local computer. If
Chapter 4. Installing application support
31
you do not have a monitoring server, you must install the support files on the local
computer using the procedure described in Installing application support files on a
computer with no Tivoli Enterprise Monitoring Server.
Gather the following information about the Tivoli Enterprise Monitoring Server on
the remote computer:
v The host name or IP address.
v The protocol and port number that was specified when the monitoring server
was configured.
The monitoring server on the remote computer must be configured to use the
IP.UDP, IP.PIPE, or IP.SPIPE communications protocol. This procedure does not
support a monitoring server that was configured to use SNA.
In these instructions, install_dir specifies the IBM Tivoli Monitoring installation
directory. You can enter either $CANDLEHOME or the name of the directory. The
default installation directory on Linux and UNIX system is /opt/IBM/ITM.
Perform the following steps to add application support SQL files to a hub Tivoli
Enterprise Monitoring Server on a non-local system.
1. Enable the GUI interface. Your Linux or UNIX system must have a GUI
interface. Otherwise, perform the following tasks to enable it:
a. Enable X11.
b. Make sure you have access to a native X-term monitor or an X-Window
emulator.
c. If using an X-Window emulator, enable X11 access to the X-Window server
(command example: xhost +).
d. If using an X-Window emulator, set the display environment variable to
point to the X-Window server:
export DISPLAY=pc_ip_address:0
2. Ensure that the hub monitoring server is running.
3. To start Manage Tivoli Monitoring Services, go to the $CANDLEHOME bin
directory (example: /opt/IBM/ITM/bin ) and run this command:
./itmcmd manage &
A GUI window opens for Manage Tivoli Monitoring Services.
4. Select Actions → Install product support.
5. On the Add Application Support to the TEMS window, select On a different
computer and click OK.
6. When you are prompted to ensure that the hub monitoring server is
configured and running, click OK.
7. On the Non-Resident TEMS Connection window, provide the hub monitoring
server TEMS name (node ID) and select the communication protocol to use in
sending the application support SQL files to the hub monitoring server.
8. Select the appropriate communications protocol and click OK.
9. On the next window, supply any values required by the selected
communication protocol and click OK.
10. On the Install Product Support window, select the monitoring agents for
which you want to add application support to the hub monitoring server, and
click Install.
11. In Manage Tivoli Monitoring Services, look for this message:
32
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Remote seeding complete!
12. Stop and restart the hub monitoring server.
You have now finished installing application support to the Tivoli Enterprise
Monitoring Server. If you have other monitoring servers in your environment,
install application support on these as well. Once all monitoring servers have been
upgraded, go to “Installing application support at the Tivoli Enterprise Portal
Server” on page 34 to continue with the installation process.
Installing application support files on a computer with no Tivoli Enterprise
Monitoring Server
You can install application support files for a Tivoli Enterprise Monitoring Server
on a UNIX or Linux system where no monitoring server is installed and then use
the files to configure support on a non-local monitoring server. Use the following
procedure to install application support files on computer on which no monitoring
server is installed for use on a monitoring server on another computer:
1. Run the following command from the installation media, either the IBM Tivoli
Monitoring base media, the agent product CD for distributed agent products or
the data files CD for a z/OS system agent products:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default directory (/opt/IBM/ITM) or enter the full path to the
installation directory you used. The following prompt is displayed:
Select one of the following:
1)
2)
3)
4)
Install products to the local host.
Install products to depot for remote deployment (requires TEMS).
Install TEMS support for remote seeding
Exit install.
Please enter a valid number:
3. Type 3 and press Enter. The software license agreement is displayed.
4. Read through the software license agreement, then type 1 and press Enter to
accept the agreement. The installer presents a list of currently installed
products, the operating systems for which product packages are available, and
component support categories.
5. Type the 32-character encryption key to use and press Enter, or just press enter
to use the default. This key must be the same key as that used during the
installation of the Tivoli Enterprise Portal Server to which the client will
connect. The installer presents a list of products for which support packages are
available.
6. Enter the numbers of the monitoring agents that you want to install or enter
the number that corresponds to all of the above. Enter more than one number
on the same line separated by spaces or commas (,). A list of the monitoring
agents to be installed is displayed.
7. Confirm the selection by pressing Enter. The installer asks if you want to install
additional products or support packages.
8. Type 2 and press Enter. The support packages are installed. When installation is
complete, you will see the message:
... finished postprocessing.
Installation step complete.
Chapter 4. Installing application support
33
Installing application support at the Tivoli Enterprise Portal Server
Depending on the operating system on which Tivoli Enterprise Portal Server is
installed, follow the instructions in the following sections to install application
support on your Tivoli Enterprise Portal Server:
v “Installing application support at a Tivoli Enterprise Portal Server on Windows
system”
v “Installing application support at a Tivoli Enterprise Portal Server on UNIX or
Linux system” on page 36
Installing application support at a Tivoli Enterprise Portal
Server on Windows system
Perform the following steps to install application support on a Windows system
Tivoli Enterprise Portal Server:
1. Log on to Windows system using a user ID with Administrator authority.
2. Close any running applications.
3. Select Start → Programs → IBM Tivoli Monitoring → Manage Tivoli
Monitoring Services to open the Manage Tivoli Enterprise Monitoring
Services window.
4. Stop the Tivoli Enterprise Portal Server by right-clicking it and selecting Stop.
5. Insert the IBM Tivoli OMEGAMON XE for Messaging CD-ROM for Windows
system into your CD-ROM drive.
6. In the /WINDOWS subdirectory on the installation media, double-click the
setup.exe file to launch the installation.
Figure 7. The InstallShield Wizard welcome window during the installation of the application
support at a Tivoli Enterprise Portal Server
7. Click Next on the Welcome window.
Remember: If you already have the OMEGAMON XE for Messaging agent or
application support files installed on this computer, click Modify
34
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
on the Welcome window to indicate that you are updating an
existing installation, and then click Next. Then skip to Step 10.
8. The Prerequisites window, containing information about prerequisite software
that must be installed before continuing with the OMEGAMON XE for
Messaging installation is displayed. The prerequisites tested for are the IBM
Global Security Toolkit and IBM Java. The version number of each of these
products already installed on the host system is displayed, along with the
number of the version required by IBM Tivoli OMEGAMON XE for
Messaging. If the Current Version field is empty, then either the version
number of the installed product could not be obtained, or the prerequisite
software was not detected on the host system. If the version number of either
of the installed products is less than stated in the Required Version field, the
prerequisite software is installed later automatically. In the Choose common
installation drive for both field, enter the drive on which to install the
software, then click Next to proceed with the installation process.
Figure 8. The InstallShield Wizard window for prerequisites installation during the installation
of the application support at a Tivoli Enterprise Portal Server
9. Click Accept on the software license agreement.
10. Select Tivoli Enterprise Portal Server and click Next.
Remember:
a. If you have other components installed on the same computer, such as
Tivoli Enterprise Portal desktop client, you can also select these
components to install the component-specific application support.
b. If you are updating an existing installation (you selected Modify on the
Welcome window), the Add or Remove Features window is displayed. All
check boxes on this window reflect your choices during the initial
installation. Clearing a check box has the effect of uninstalling the
component. Clear a box only if you want to remove a component.
11. Ensure that no agents are selected in the Agent Deployment window and click
Next.
12. Review the installation summary details. Click Next to start the installation.
Chapter 4. Installing application support
35
13. A message is displayed stating that you will not be able to cancel the
installation or upgrade after this point. Click Yes to continue.
14. The Setup Type window is displayed. Select Configure Tivoli Enterprise
Portal and click Next.
15. Type the host name of the server where the Tivoli Enterprise Portal Server is
in the Tivoli Enterprise Portal Server Hostname window and click Next.
16. Click Finish to complete the installation.
17. Restart the Tivoli Enterprise Portal Server by right-clicking it in the Manage
Tivoli Enterprise Monitoring Services window and selecting Start.
Installation of application support on the Tivoli Enterprise Portal Server is now
complete. Go to “Installing application support at the Tivoli Enterprise Portal
desktop client” on page 42 to continue with the installation process.
Installing application support at a Tivoli Enterprise Portal
Server on UNIX or Linux system
Use the following steps to install application support on a UNIX or Linux system
Tivoli Enterprise Portal Server:
1. Stop the Tivoli Enterprise Portal Server if it is running the following
commands:
cd install_dir/bin
./CandleAgent stop cq
2. Run the following command to create a temporary directory on the computer
where the Tivoli Enterprise Portal Server is installed. Make sure that the full
path of the directory does not contain any spaces:
mkdir dir_name
3. Mount the installation CD for UNIX or Linux system to the temporary
directory you just created.
4. Run the following commands:
cd dir_name
./install.sh
where dir_name is the temporary directory you just created.
5. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory. If a message is displayed stating that the directory already exists
and asking whether to use it, enter 1 (yes) and press Enter.
6. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding.
4) Exit install.
Please enter a valid number:
Type 1 to start the installation and press Enter.
7. The first part of the software license agreement is displayed. Press Enter to
view latter parts of the agreement. Once you have finished viewing the
agreement, enter 1 to accept it or 2 to reject it and press Enter. You must
accept the agreement to continue with the installation process.
8. A numbered list of available operating systems and installation components is
displayed. Type the number that corresponds to Tivoli Enterprise Portal
Browser Client support and press Enter.
36
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
9. Type 1 (yes) to confirm and press Enter. A list of the components to install is
displayed.
10. Type the number that corresponds to all of the above and press Enter.
11. Type 1 (yes) to confirm the installation. The installation begins.
12. When you are asked whether you want to install additional products or
product support packages for a different operating system, type y and press
Enter.
13. Type the number that corresponds to Tivoli Enterprise Portal Server
support and press Enter.
14. Type 1 (yes) to confirm and press Enter. A list of the components to install is
displayed.
15. Type the number that corresponds to all of the above and press Enter.
16. Type 1 (yes) to confirm the installation. The installation begins.
17. After all of the components are installed, you are asked whether you want to
install components for a different operating system. Type 2 (no) and press
Enter.
Application support for Tivoli Enterprise Portal Server is installed. Next step is
“Configuring the Tivoli Enterprise Portal Server on UNIX or Linux system.”
Configuring the Tivoli Enterprise Portal Server on UNIX or
Linux system
You have two options to configure the Tivoli Enterprise Portal Server on UNIX or
Linux system:
v “Configuring the Tivoli Enterprise Portal Server using the GUI”
v “Configuring the Tivoli Enterprise Portal Server using the command line” on
page 40
Configuring the Tivoli Enterprise Portal Server using the GUI
Perform the following steps to configure the Tivoli Enterprise Portal Server using
the GUI on UNIX or Linux system:
1. Navigate to the install_dir/bin directory, where install_dir is the directory where
IBM Tivoli Monitoring is installed. The default is /opt/IBM/ITM.
2. Open the Manage Tivoli Enterprise Monitoring Services window by running
the following command:
./itmcmd manage
The Manage Tivoli Enterprise Monitoring Services window is displayed.
3. From the Manage Tivoli Enterprise Monitoring Services window, select Tivoli
Enterprise Portal Server, right-click and select Configure from the menu, as
shown in Figure 9 on page 38.
Chapter 4. Installing application support
37
Figure 9. Configuring Tivoli Enterprise Portal Server
4. On the Common Event Console Configuration window click OK.
5. The Configure Tivoli Enterprise Portal Server window is displayed, as shown
in Figure 10.
On the TEMS Connection tab, perform the following steps:
Figure 10. Configuring Tivoli Enterprise Monitoring Server connections
a. In the TEMS Hostname field, enter the host name of the hub Tivoli
Enterprise Monitoring Server.
b. In the Protocol 1 tab, select the protocol that you want to use to
communicate with the hub Tivoli Enterprise Monitoring Server. You have
four choices: TCP/IP, SNA, IP.PIPE and IP.SPIPE. Depending on the
protocol you select, provide the following information:
Table 7. Tivoli Enterprise Monitoring Server protocols and values on UNIX or Linux system
38
Protocol
Value
Definition
TCP/IP
IP port number
The port number of the
Tivoli Enterprise Monitoring
Server. The default is 1918.
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Table 7. Tivoli Enterprise Monitoring Server protocols and values on UNIX or Linux
system (continued)
Protocol
Value
Definition
SNA
Net name
The SNA network identifier
for your location.
LU name
The LU name of the Tivoli
Enterprise Monitoring Server.
This LU name corresponds
to the Local LU Alias in your
SNA communications
software.
Log mode
The name of the LU6.2
LOGMODE. The default
value is CANCTDCS.
IP.PIPE port number
The port number for the
Tivoli Enterprise Monitoring
Server. The default is 1918.
KDC Partition
The KDC partition. The
default value is null.
IP.SPIPE port number
The port number for the
Tivoli Enterprise Monitoring
Server. The default is 3660.
IP.PIPE
IP.SPIPE
c. If you want to set up a backup protocol, select the protocol in the Protocol 2
tab. See Table 7 on page 38 for information about how to fill in the fields.
You can specify a second backup protocol in the Protocol 3 tab.
6. The Agent Parameters tab is displayed, as shown in Figure 11.
Perform the following steps:
Figure 11. Configuring agent parameters
a. Enter the DB2 instance name. The default value is db2inst1.
b. Enter the DB2 administrator ID. The default is db2inst1.
c. Enter the password for the DB2 administrator ID.
d. Confirm the password for the DB2 administrator ID by typing it again.
Chapter 4. Installing application support
39
e. Enter the name of the DB2 database for the Tivoli Enterprise Portal Server.
The default is TEPS.
f. Enter the name of the database user ID that the Tivoli Enterprise Portal
Server will use to access the database. The default is itmuser.
g. Enter the password for the database user.
h. Confirm the password for the database user by entering it again.
i. Select Create Tivoli Enterprise Portal Server DB user ID if not found.
j. Select DB2 if you are using DB2 to warehouse data. Select Oracle(JDBC) if
you are using Oracle to warehouse data.
k. Enter the name of the database that the Tivoli Data Warehouse will use. The
default is WAREHOUS.
l. Enter the name of the database user that the Tivoli Data Warehouse will use.
The default is itmuser.
m. Enter the password for the Warehouse user ID.
n. Confirm the password for the Warehouse user by typing it again.
o. Click Save to save your changes.
7. In the Manage Tivoli Enterprise Monitoring Services window, stop the Tivoli
Enterprise Portal Server, if it is started, by right-clicking the Tivoli Enterprise
Portal Server item and click Stop Service.
8. In the Manage Tivoli Enterprise Monitoring Services window, Restart the Tivoli
Enterprise Portal Server by right-clicking the Tivoli Enterprise Portal Server
item and click Start Service.
Installation and configuration of application support on the Tivoli Enterprise Portal
Server is now complete. Go to “Installing application support at the Tivoli
Enterprise Portal desktop client” on page 42 to continue with the installation
process.
Configuring the Tivoli Enterprise Portal Server using the
command line
Perform the following steps to configure the Tivoli Enterprise Portal Server on
UNIX or Linux system using the command line:
1. Navigate to the install_dir/bin directory, where install_dir is the directory where
IBM Tivoli Monitoring is installed. The default is /opt/IBM/ITM.
2. Run the following command:
./itmcmd config -A cq
3. When asked if you want to edit commen event console for IBM Tivoli
Monitoring settings, enter 2 (no) and press Enter.
4. Enter 1 (yes) when you are asked if the agent connects to a Tivoli Enterprise
Monitoring Server.
5. Enter the host name of the hub Tivoli Enterprise Monitoring Server and press
Enter.
6. Enter the protocol that you want to use to communicate with your hub Tivoli
Enterprise Monitoring Server. You have four choices: ip, sna, ip.pipe, or
ip.spipe.
7. If you want to set up a backup protocol, enter the name of the protocol and
press Enter. If you do not want to use a backup protocol type 0 and press
Enter.
8. Depending on the protocols you specified, provide the information in Table 7
on page 38 when prompted.
40
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
9. Press Enter to accept the default value (none) for the Optional Primary
Network Name.
10. Press Enter to accept the default setting for SSL between the portal server and
clients (N). By default, SSL is disabled. To enable SSL, type 1 (yes) and press
Enter.
11. Type the DB2 instance name. The default value is db2inst1. Press Enter.
12. Type the DB2 administrator ID. The default is db2inst1. Press Enter.
13. Type the password for the DB2 administrator ID and press Enter.
14. Confirm the password for the DB2 administrator ID by typing it again. Press
Enter.
15. Type the name of the database used by the Tivoli Enterprise Portal Server. The
default is TEPS. Press Enter.
16. Type the name of the database user that the Tivoli Enterprise Portal Server
will use to access the database. The default is itmuser. Press Enter.
17. Type the password for the database user and press Enter.
18. Confirm the password for the database user by typing it again. Press Enter.
19. You are asked if it is OK to create the DB2 login user if it does not exist. Type
1 (yes) and press Enter.
20. You are asked whether you are using DB2 or Oracle (JDBC) for data
warehousing. Enter the number corresponding to the database you want to
use.
21. Type the name of the database that the Tivoli Data Warehouse will use. The
default is WAREHOUS. If you select the DB2 database, this database must be
cataloged locally if the warehouse database is on a remote computer. Press
Enter.
Remember: If you are using a remote node and database, you must manually
configure (catalog) the remote node and the remote database
from the Linux system DB2 command line. Run the following
commands:
db2 catalog tcpip node <node_name> remote <host_name> server
<port>
db2 catalog db <db_name> as <dbalias> at node <node_name>
22. Type the name of the database user ID that the Tivoli Data Warehouse will
use. The default is itmuser. Press Enter.
23. Type the password for the Warehouse user ID and press Enter.
24. Confirm the password for the Warehouse user by typing it again. Press Enter.
25. If you selected the Oracle database in step 20, enter the following information
when prompted:
a. JDBC driver class path
b. JDBC driver name
c. JDBC driver URL
d. User-defined attributes
26. You are asked whether you want to validate user with LDAP. Press Enter to
accept the default value for the LDAP security.
Installation and configuration of application support on the Tivoli Enterprise Portal
Server is now complete. Go to “Installing application support at the Tivoli
Enterprise Portal desktop client” on page 42 to continue with the installation
process.
Chapter 4. Installing application support
41
Installing application support at the Tivoli Enterprise Portal desktop
client
Depending on the operating system on which Tivoli Enterprise Portal desktop
client is installed, follow the instructions in the following sections to install
application support on each computer where you are running the Tivoli Enterprise
Portal desktop client:
v “Installing application support at a Tivoli Enterprise Portal desktop client on
Windows system”
v “Installing application support at a Tivoli Enterprise Portal desktop client on
Linux system” on page 43
Installing application support at a Tivoli Enterprise Portal
desktop client on Windows system
Use the following steps to install application support on a Windows portal desktop
client:
Remember: Stop the Tivoli Enterprise Portal desktop client before performing this
procedure.
1. Insert the IBM Tivoli OMEGAMON XE for Messaging CD-ROM for Windows
system into your CD-ROM drive.
2. In the /WINDOWS subdirectory on the installation media, double-click the
setup.exe file to launch the installation.
3. Click Next on the Welcome window.
Remember: If you already have the OMEGAMON XE for Messaging agent or
application support files installed on this computer, select Modify
on the Welcome window to indicate that you are updating an
existing installation, and then click Next. Then skip to Step 7.
4. The Prerequisites window, containing information about prerequisite software
that must be installed before continuing with the OMEGAMON XE for
Messaging installation, is displayed. The prerequisites tested for are the IBM
Global Security Toolkit and IBM Java. The version number of each of these
products already installed on the host system is displayed, along with the
number of the version required by IBM Tivoli OMEGAMON XE for
Messaging. If the Current Version field is empty, then either the version
number of the installed product could not be obtained, or the product was not
detected on the host system. If the version number of either of the installed
products is less than stated in the Required Version field, the required version
of the prerequisite software will be installed automatically. In the Choose
common installation drive for both field enter the drive on which to install
the software, then click Next to proceed with the installation process.
5. Click Accept on the software license.
6. If you see a message regarding installed versions being newer than the agent
installation, click OK to ignore this message.
7. Select Tivoli Enterprise Portal Desktop Client and click Next.
Remember: If you are updating an existing installation (you selected Modify
on the Welcome window), the Add or Remove Features window
is displayed. All check boxes on this window reflect your choices
42
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
during the initial installation. Clearing a check box has the effect
of uninstalling the component. Clear a box only if you want to
remove a component.
8. The Agent Deployment window is displayed. Make sure that no agent is
selected. Click Next.
9. Review the installation summary details. Click Next to start the installation.
10. A message is displayed stating that you will not be able to cancel the
installation or upgrade after this point. Click Yes to continue.
11. The Setup Type window is displayed. Select Configure Tivoli Enterprise
Portal and click Next.
12. The Tivoli Enterprise Portal Server Hostname window is displayed. Type the
host name of the server where Tivoli Enterprise Portal Server is and click
Next. The Tivoli Enterprise Portal Server hostname must be the name of the
Tivoli Enterprise Portal Server that this Tivoli Enterprise Portal connects to, it
doesn't change even you change the hostname during the configuration.
13. Click Finish to complete the installation wizard.
Installing application support on the Windows portal desktop client is complete.
Go back to the Chapter 2, “Installation roadmap,” on page 7 to continue with other
installation tasks.
Installing application support at a Tivoli Enterprise Portal
desktop client on Linux system
Perform the following steps to install application support on a Linux portal
desktop client:
Remember: Stop the desktop client before performing this procedure.
1. Run the following command to create a temporary directory on the computer
where the Tivoli Enterprise Portal desktop client is installed. Make sure that
the full path of the directory does not contain any spaces:
mkdir dir_name
2. Mount the installation CD for Linux system to the temporary directory you
just created.
3. Run the following commands:
cd dir_name
./install.sh
where dir_name is the temporary directory you just created.
4. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory. If a message is displayed stating that the directory already exists
and asking whether to use it, enter 1 (yes) and press Enter.
5. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding.
4) Exit install.
Please enter a valid number:
Type 1 (yes) to start the installation and press Enter.
6. The first part of the software license agreement is displayed. Press Enter to
view latter parts of the agreement. Once you have finished viewing the
Chapter 4. Installing application support
43
7.
8.
9.
10.
11.
agreement, enter 1 to accept it or 2 to reject it and press Enter. You must
accept the agreement to continue with the installation process.
A numbered list of available operating systems and installation components is
displayed. Type the number that corresponds to Tivoli Enterprise Portal
Desktop Client support and press Enter.
Type 1 (yes) to confirm and press Enter. A list of the application support
components that can be installed is displayed.
Type the number that corresponds to all of the above and press Enter.
Type 1 (yes) to confirm the installation. The installation begins.
After all of the components are installed, you are asked whether you want to
install additional products or product support packages. Type 2 (no) and press
Enter.
Application support for Tivoli Enterprise Portal desktop client is now installed. Go
to “Configuring the Tivoli Enterprise Portal desktop client” to configure the client.
Configuring the Tivoli Enterprise Portal desktop client
Perform the following steps to configure the Tivoli Enterprise Portal desktop client
on UNIX or Linux system:
1. Go to the install_dir/bin directory, where install_dir is the directory where IBM
Tivoli Monitoring is installed. The default is /opt/IBM/ITM.
2. Run the following command:
./itmcmd config -A cj
3. Press Enter to accept the default instance name when prompted.
4. Type the host name of the Tivoli Enterprise Portal Server and press Enter.
5. Type the path of your Web browser when prompted and press Enter.
6. Press Enter when you are asked if you want to use HTTP Proxy support. The
default value is no.
Installing application support on the Tivoli Enterprise Portal desktop client is
complete. Go back to the Chapter 2, “Installation roadmap,” on page 7 to continue
with the installation process.
44
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 5. Setting up the WebSphere MQ configuration
database
If you have installed the WebSphere MQ Configuration agent, you must configure
the WebSphere MQ configuration database, which stores information about
WebSphere MQ objects you define. A single instance of the WebSphere MQ
configuration database stores definition information from all WebSphere MQ
Configuration agents and is located at the hub Tivoli Enterprise Monitoring Server.
Before you configure the WebSphere MQ configuration database, you must install
application support for WebSphere MQ Configuration. Configure the WebSphere
MQ configuration database by following the instructions in the following sections,
depending on which operating system your hub Tivoli Enterprise Monitoring
Server is running on:
v “Setting up the configuration database on Windows systems”
v “Setting up the configuration database on UNIX and Linux systems” on page 46
Setting up the configuration database on Windows systems
When you install WebSphere MQ Configuration, it provides a single repository
called the configuration database for all your WebSphere MQ configuration data.
The configuration database is stored at the hub Tivoli Enterprise Monitoring
Server. WebSphere MQ Configuration supports two types of database :
v The product-provided internal database, which is installed automatically during
Tivoli Enterprise Monitoring Server installation. Under most circumstances,
using the internal database with IBM Tivoli OMEGAMON XE for Messaging
provides better performance than using DB2® Universal Database™.
v The DB2 Universal Database, which can be installed on the Windows system,
UNIX or Linux system from the DB2 UDB ESE V9.1 CD. If the hub Tivoli
Enterprise Monitoring Server is installed on a z/OS system and you want to use
a DB2 database, DB2 version 8.1 or later is required. If DB2 is not already
installed on the z/OS system that hosts the Tivoli Enterprise Monitoring Server,
you can purchase and install it separately. Alternatively, you can use the internal
database.
The DB2 Universal Database is included in the DB2 UDB ESE V9.1 for Windows
system installation CD. See your DB2 documentation for installation instructions.
Perform the following steps to set up the configuration database:
Remember: If you want to use the DB2 Universal Database, you must have
already installed DB2 Universal Database Workgroup Server Edition
8.1 or later.
1. Open the WebSphere MQ Configuration Data Source Parameters window by
double-clicking the KCFDatasource.exe file in install_dir\CMS, where install_dir is
the installation directory of IBM Tivoli OMEGAMON XE for Messaging.
2. Select the database type as either Internal or ODBC (DB2 UDB).
3. If you selected the ODBC (DB2 UDB) database, complete the fields in the
displayed window as follows:
a. In the Admin User ID and Admin Password fields, enter the user ID and
password of a user with DB2 administrator authority.
© Copyright IBM Corp. 2005, 2009
45
b. In the Database User ID and Database Password fields, either accept the
default user ID and password (by default both the user ID and password
are WMQCFG) or type the user ID (maximum 8 characters) and password
that you want to use for accessing the configuration database.
The data source name for the configuration database is RKCFAPLT. You do not
change it.
4. Click OK to save your settings and close the dialog.
The WebSphere MQ configuration database is now set up. Go back to the
Chapter 2, “Installation roadmap,” on page 7 to continue with the installation
process.
Setting up the configuration database on UNIX and Linux systems
When you install WebSphere MQ Configuration, it provides a single repository
called the configuration database for all your WebSphere MQ configuration data.
The configuration database is stored at the hub Tivoli Enterprise Monitoring
Server. WebSphere MQ Configuration supports two types of database:
v The product-provided internal database, which is installed automatically during
Tivoli Enterprise Monitoring Server installation. Under most circumstances,
using the internal database provides better performance than using the DB2
Universal Database.
v
The DB2 Universal Database, which can be installed on Windows system, UNIX
or Linux system from the DB2 UDB ESE V9.1 CD. If the hub Tivoli Enterprise
Monitoring Server is installed on a z/OS system and you want to use a DB2
database, DB2 version 8.1 or later is required. If DB2 is not already installed on
the z/OS system that hosts the Tivoli Enterprise Monitoring Server, you can
purchase and install it separately. Alternatively, use the internal database.
UNIX and Linux versions of the DB2 Universal Database is included in the DB2
UDB ESE V9.1 installation CDs. See your DB2 documentation for installation
instructions.
If you want to use the DB2 Universal Database, before setting up the configuration
database, the DB2 instance owner must have created a database and granted
permissions to the user ID that will be used to run the Tivoli Enterprise
Monitoring Server. If this has not yet been done, perform the following steps to
create the user ID and grant permissions:
1. Log on to DB2 with the user ID of the DB2 instance owner.
2. Start the DB2 Command Line Processor.
3. Run the following commands to create the database and grant permissions to
the user ID that will be used to run the Tivoli Enterprise Monitoring Server:
Important: If you are using a 64-bit version of DB2 version 8, you must create
a 32-bit database instance for the configuration database. 64-bit
instances are supported from DB2 version 9 onwards. See your DB2
documentation for more information.
CREATE DATABASE RKCFAPLT
CONNECT TO RKCFAPLT
GRANT CONNECT ON DATABASE TO USER <user>
GRANT CREATETAB ON DATABASE TO USER <user>
Perform the following steps to set up the configuration database:
1. Go to the ITM_install_dir/bin directory, where ITM_install_dir is the directory
where IBM Tivoli Monitoring is installed. The default is /opt/IBM/ITM.
46
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
2. Run the following command to stop the Tivoli Enterprise Monitoring Server:
./itmcmd server stop tems_name
Where tems_name is the name of the Tivoli Enterprise Monitoring Server.
3. Run the following command to configure the Tivoli Enterprise Monitoring
Server:
./itmcmd config -S -t tems_name
Where tems_name is the name of the Tivoli Enterprise Monitoring Server.
Tip: For more information about the itmcmd config command, see IBM Tivoli
Monitoring Command Reference.
4. Press Enter to indicate that this is a hub monitoring server (indicated by the
*LOCAL default).
Remember: The configuration is only installed at the hub Tivoli Enterprise
Monitoring Server, do not try to install it on a remote Tivoli
Enterprise Monitoring Server.
5. Accept the defaults or enter the correct values for your environment at each
prompt until you see the prompt:
User database [1=Internal, 2=DB2] (Default is: 1):
Specify which type of database you want to use by entering the appropriate
number and pressing Enter.
6. If you are using the DB2 Universal Database, perform the following steps:
a. You are prompted to enter the following information about the DB2
instance that you want to use:
1) DB2 Instance(Default is: none):
Where none might be replaced by a default DB2 instance name. If none
is shown as the default DB2 instance name, you must manually enter
the name of the DB2 instance that you want to use and press Enter,
because none is not a valid DB2 instance name. Press Enter to accept
the default if it is a valid DB2 instance name.
2) DB2 Home Directory(Default is: none):
Where none might be replaced by a default DB2 home directory such
as /home/db2inst1/sqllib. If none or an invalid DB2 library directory is
given, you must enter the full path of the directory where the DB2
library is located and press Enter. Press Enter to accept the default if it
is a valid DB2 home directory.
b. Use the UNIX system DB2 database configuration tool to write the
encrypted database password to the system files and confirm that the
database connection is enabled. Run the following commands:
v AIX:
export KEYFILE_DIR=[install_dir]/keyfiles
export ICCRTE_DIR=[install_dir]/[arch]/ms/lib/gskit
export KBBENV_HOME=[install_dir]/tables/[tems_name]
export LIBPATH=$LIBPATH:[install_dir]/[arch]/ui/lib
. /[DB2_Instance_Home]/sqllib/db2profile
[install_dir]/[arch]/ms/bin/KCFDataSourceU -d [database-name]
-u [user-id] -p [password] –t (Y|N) -c (Y|N)
v Solaris and Linux:
Chapter 5. Setting up the WebSphere MQ configuration database
47
export KEYFILE_DIR=[install_dir]/keyfiles
export ICCRTE_DIR=[install_dir]/[arch]/ms/lib/gskit
export KBBENV_HOME=[install_dir]/tables/[tems_name]
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:[install_dir]/[arch]/ui/lib
. /[DB2_Instance_Home]/sqllib/db2profile
[install_dir]/[arch]/ms/bin/KCFDataSourceU -d [database-name]
-u [user-id] -p [password] –t (Y|N) -c (Y|N)
where
v [install_dir] is the directory where IBM Tivoli OMEGAMON XE for
Messaging is installed
v [arch] is the IBM Tivoli architecture code (See Appendix C, “Architecture
codes,” on page 135 for details)
v [database-name] is the configuration database name
v [tems_name] is the name of the Tivoli Enterprise Monitoring Server
v [DB2_Instance_Home] is the name of the DB2 instance
v [user-id] is the user ID that is used to access the database
v [password] is the password that is used to access the database
v the –t option specifies whether the user ID and password will be
checked when connecting to the database. Y indicates yes and N
indicates no.
v the -c option specifies whether the password is encrypted. Y indicates
yes and N indicates no.
Important: The data source name of the configuration database is
RKCFAPLT. You cannot change it.
7. Accept the default or enter the correct values for your environment at each
prompt until the configuration program exits.
8. Open the ms.ini file and the Tivoli Enterprise Monitoring Server configuration
file in the ITM_install_dir/config directory, where ITM_install_dir is the
directory in which IBM Tivoli Monitoring is installed. Edit the following
environment variables to ensure that $DB2HOME$/lib appears before
$CANDLEHOME$/$BINARCH$/$PRODUCTCODE$/lib in the string of parameters
following each variable name:
v LD_LIBRARY_PATH
v LIBPATH
v SHLIB_PATH
Tip: The Tivoli Enterprise Monitoring Server configuration file is named as
<host_name>_ms_<tems_ID>.config, where <host_name> is the host name of
the Tivoli Enterprise Monitoring Server, and <tems_ID> is the ID of the
Tivoli Enterprise Monitoring Server.
9. If you are using a 64-bit version of DB2 and can not create a 32-bit database
instance for the configuration database, perform the following steps:
a. Ensure that $DB2HOME$/lib32 is included in the string of parameters
following the environment variables that are listed below in the ms.ini file
in the ITM_install_dir/config directory, where ITM_install_dir is the
directory in which IBM Tivoli Monitoring is installed:
v LD_LIBRARY_PATH
v LIBPATH
v SHLIB_PATH
b. If you are using the Linux operating system, skip this step and continue
with the next step below; otherwise, navigate to the <ITM_HOME>\
48
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
<BinArch>\ms\lib\ directory and do one of the following procedures,
depending on which operating system you are using:
v AIX: create a copy of the libkcfdummydb2.a file and name it libdb2.a
v HP: create a copy of the libkcfdummydb2.sl file and name it libdb2.sl
v Solaris: create a copy of the libkcfdummydb2.so file, name it libdb2.so,
create a second copy of libkcfdummydb2.so, and name it libdb2.so.1
10. Run the following command to restart the Tivoli Enterprise Monitoring Server:
./itmcmd server start <tems_name>
The WebSphere MQ configuration database is now set up. Go back to the
Chapter 2, “Installation roadmap,” on page 7 to continue with the installation
process.
Chapter 5. Setting up the WebSphere MQ configuration database
49
50
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 6. Installing the language packs
By default, IBM Tivoli OMEGAMON XE for Messaging is enabled for the English
language. If you want to use it in another supported language, you must install the
translated language pack on the computers where the Tivoli Enterprise Portal and
Tivoli Enterprise Portal Server are installed. The language packs are available on
the IBM Tivoli OMEGAMON XE for Messaging Language Pack CD.
IBM Tivoli OMEGAMON XE for Messaging provides language packs in the
following languages:
v French
v German
v Italian
v Japanese
v Korean
v Portuguese (Brazilian)
v Simplified Chinese
v Spanish
v Traditional Chinese
Remember: Before you can install a language pack, you must install IBM Tivoli
OMEGAMON XE for Messaging in English.
Installing a language pack on Windows system
To install a language pack, first make sure that you have already installed the
product in English, then perform the follow steps:
1. Double-click the lpinstaller.exe file in the language pack CD to launch the
installation program
2. Select the installer language which you prefer and click OK.
3. Click Next on the Introduction panel.
4. Click Add/Update and then click Next.
5. Select the folder where the National Language Support package (NLSPackgae)
files are located.
Tip: The NLSPackage files are usually located in the same directory with the
installer executable.
6. Select the language support of the agent and click Next.
7.
8.
9.
10.
Tip: You can use the Ctrl key for multiple selection.
Select the language (or languages) for which you want to install and click
Next to examine the installation summary.
Click Next to start the installation of the language pack.
When the installation completes, click Finish to exit the installer.
Restart the Tivoli Enterprise Portal (if on the Tivoli Enterprise Portal Server) or
restart the Tivoli Enterprise Portal Server (if on the Tivoli Enterprise Portal
Server component).
© Copyright IBM Corp. 2005, 2009
51
The language packs are now installed. Go back to the Chapter 2, “Installation
roadmap,” on page 7 to continue with the installation process.
Installing a language pack on UNIX or Linux system
To install a language pack on UNIX or Linux system, first make sure that you have
already installed IBM Tivoli OMEGAMON XE for Messaging in English, then
perform the following steps:
1. Run the following command to create a temporary directory on the computer.
Make sure that the full path of the directory does not contain any spaces:
mkdir dir_name
2. Mount the language pack CD to the temporary directory you just created.
3. Run the following command to start the installation program:
cd dir_name
lpinstaller.bin
where dir_name is the directory you just created.
4. Select the installer language which you prefer and click OK.
5. Click Next on the Introduction panel.
6. Click Add/Update and then click Next.
7. Select the folder where the National Language Support package (NLSPackgae)
files are located.
Tip: The NLSPackage files are usually located in the same directory with the
installer executable.
8. Select the language support of the agent and click Next.
9.
10.
11.
12.
Tip: You can use the Ctrl key for multiple selection.
Select the language(s) for which you want to install and click Next to examine
the installation summary.
Click Next to start the installation of the language pack.
When the installation completes, click Finish to exit the installer.
Restart the Tivoli Enterprise Portal (if on the Tivoli Enterprise Portal Server) or
restart the Tivoli Enterprise Portal Server (if on the Tivoli Enterprise Portal
Server component).
The language packs are now installed. Go back to the Chapter 2, “Installation
roadmap,” on page 7 to continue with the installation process.
52
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 7. Installing IBM Tivoli OMEGAMON XE for Messaging
on Windows system
This chapter contains step-by-step instructions for installing the agents of IBM
Tivoli OMEGAMON XE for Messaging on an Intel PC workstation running
Windows system. The following procedure is for users installing agents on a
system with no previous version installed. If a previous version is already installed
on the system, see Upgrading to IBM Tivoli OMEGAMON XE for Messaging 7.0 for
information about how to migrate or upgrade to IBM Tivoli OMEGAMON XE for
Messaging 7.0 before proceeding.
Pre-installation tasks
The following tasks must be performed before proceeding with the installation of
any agents.
1. Ensure that your Windows system user ID has Administrator authority.
Your Windows system user ID must be a member of the Administrators user
group for you to be able to install agents of IBM Tivoli OMEGAMON XE for
Messaging. If you do not have administrator access, contact your system
administrator.
2. Stop the Lotus® Notes® server.
If a Lotus Notes server is running on the operation system on which you are
installing agents of IBM Tivoli OMEGAMON XE for Messaging, stop the Lotus
Notes server before proceeding with the installation. Individual Lotus Notes
applications can continue to run.
3. Check the HOSTS file.
IBM Tivoli OMEGAMON XE for Messaging agents do not require a DNS
server. If your Windows systems are running without a DNS, make sure the
HOSTS file of the local server is up to date.
Installing and initializing agents
There are two methods of installing agents of OMEGAMON XE for Messaging on
Windows system. Installation can be performed interactively using the InstallShield
Wizard to guide you through the process, or using a silent installation where all
installation parameters are specified in a response file before the process begins.
For detailed instructions on using either of these methods, see the following
sections:
v “InstallShield Wizard installation”
v “Silent Installation” on page 57
InstallShield Wizard installation
Use the following steps to install and initialize agents of OMEGAMON XE for
Messaging with the InstallShield Wizard.
1. Log on to Windows system using a user ID with Administrator authority.
2. Close any running applications.
3. Insert the IBM Tivoli OMEGAMON XE for Messaging CD-ROM into your
CD-ROM drive. Installation begins automatically. If the InstallShield Wizard
does not start automatically, use My Computer to open your CD-ROM drive
© Copyright IBM Corp. 2005, 2009
53
and run the setup.exe file. If the setup.exe file still fails to run, you do not have
enough disk space to decompress the setup files. Clear some disk space before
starting the installation process again.
The InstallShield wizard window displays a message welcoming you to the
setup process. This window also contains information about what IBM Tivoli
products you currently have installed and the name and version of the
product contained on the installation CD.
Figure 12. The InstallShield Wizard welcome window during the installation of the monitoring
agents
Exception: If you are running Windows 2003 or Windows XP system and
have security set to check the software publisher of applications,
you might receive an error stating that the setup.exe file is from an
unknown publisher. Click Run to disregard this error message and
continue with the installation process.
4. Click Next on the Welcome window.
Remember: If you already have the OMEGAMON XE for Messaging agent or
application support files installed on this computer, select Modify
on the Welcome window to indicate that you are updating an
existing installation, and then click Next. Then skip to Step 8 on
page 55.
5. The Prerequisites window, containing information about prerequisite software
that must be installed before continuing with the OMEGAMON XE for
Messaging installation is displayed. The prerequisites tested for are the IBM
Global Security Toolkit and IBM Java Virtual Machine (JVM). The version
number of each of these products already installed on the host system is
displayed, along with the number of the version required by IBM Tivoli
OMEGAMON XE for Messaging. If the Current Version field is empty, then
either the version number of the installed product could not be obtained, or
the product was not detected on the host system. If the version number of
either of the installed products is less than stated in the Required Version
field, the required version of the prerequisite software will be installed
automatically. In the Choose common installation drive for both field, enter
the drive on which to install the software, then click Next to proceed with the
54
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
installation process.
Figure 13. The InstallShield Wizard window for prerequisites installation during the installation
of the monitoring agents
6. If the version number of prerequisite software is less than the required
version, the required version is installed automatically. Once installation of the
prerequisite software is complete, you will be automatically returned to the
OMEGAMON XE for Messaging InstallShield Wizard.
7. License agreement information is displayed. If you accept the terms of the
license agreement, click Accept to continue, otherwise click Decline to stop
the installation process. You muse accept the terms of the license agreement to
install OMEGAMON XE for Messaging.
8. The Select Features window is displayed. Select the features that you want to
install from the list provided by clicking the check box next to the features’
name. To view more detailed information about a particular feature, click the
feature name. Information about the feature is displayed in the Description
panel next to the list of features. When you have selected all the features that
you want to install, click Next to continue.
Remember: If you are updating an existing installation (you selected Modify
on the Welcome window), the Add or Remove Features window
is displayed. All check boxes on this window reflect your choices
during the initial installation. Clearing a check box has the effect
of removing the component. Clear a box only if you want to
remove a component.
Chapter 7. Installing IBM Tivoli OMEGAMON XE for Messaging on Windows system
55
Figure 14. The InstallShield Wizard window for feature selection during the installation of the
monitoring agents
9. The Agent Deployment window is displayed. Select the agents that you want
to configure for remote deployment and click Next to continue. An agent can
only be deployed on a remote host if it has been configured for remote
deployment during installation.
Figure 15. The InstallShield Wizard window for agent deployment during the installation of the
monitoring agents
10. The Start Copying Files window, summarizing the components that you have
selected to install, is displayed. Click Next to begin installing the listed
components.
56
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
11. A message is displayed stating that you will not be able to cancel the
installation or upgrade after this point. Click Yes to continue. Files are now
copied to your computer. This might take several minutes.
12. The Setup Type window is displayed. Select Configure agents default
connection to TEMS and click Next.
13. On the Configuration Defaults for Connecting to a TEMS window:
a. Select Connection must pass through firewall if the agent must cross a
firewall to access the Tivoli Enterprise Monitoring Server.
b. Select Address Translation Used if the firewall shielding the Tivoli
Enterprise Monitoring Server uses address translation.
c. Select one or more protocols to be used when connecting to the Tivoli
Enterprise Monitoring Server and click Next. You can select up to three
protocols. The protocol specified in the Protocol 1 field will be used by
default. If connection to the Tivoli Enterprise Monitoring Server using this
protocol fails, the protocol specified in the Protocol 2 field will be used,
and if connection still fails, the protocol specified in the Protocol 3 field is
used. Available protocols are IP.PIPE, IP.SPIPE, SNA and IP.UDP.
d. Refer to the fields in Table 9 on page 65 to define the communications
between the agents and the Tivoli Enterprise Monitoring Server.
14. The InstallShield Wizard Complete window is displayed. Select the Display
the README file option if you want to review the readme file after
installation is complete and click Finish to exit the installation wizard.
Installation is now complete.
Installing OMEGAMON for Messaging agents is now completed. Go back to
Chapter 2, “Installation roadmap,” on page 7 to continue with other installation
tasks.
Silent Installation
Use the silent installation feature to install OMEGAMON XE for Messaging using
installation parameters specified in a response file, instead of entering parameters
interactively during the installation process. This feature is particularly useful if
you want to install OMEGAMON XE for Messaging on a large number of
computers with similar configurations, as the administrator is required to specify
installation parameters only once, in the response file, instead of entering them
repeatedly for every operation system on which installation is performed.
To perform silent installation, you need to perform the following steps:
1. “Creating the response file”
2. “Installing OMEGAMON XE for Messaging” on page 59
3. “Configuring the agents' default connection to Tivoli Enterprise Monitoring
Server” on page 59
Creating the response file
To create a response file specifying installation parameters for your environment,
perform the following steps:
1. Copy the silent.txt file from the OMEGAMON XE for Messaging CD to a
temporary directory (for example, c:\temp).
2. Edit the silent.txt file as follows. Note that the following rules apply to this file:
v Comment lines begin with a semicolon (;), which must be placed in the first
column of the commented line.
v Blank lines are ignored.
Chapter 7. Installing IBM Tivoli OMEGAMON XE for Messaging on Windows system
57
v Parameter lines are PARAMETER=value. Do not use a space before the
parameter; you can use a space before or after an equal sign (=).
v Do not use any of the following characters in any parameter value:
– Dollar sign ($)
– Equals sign (=)
– Pipe sign (|)
Modify the following parameters as appropriate for your environment:
a. Uncomment the line containing the License Agreement parameter. By doing
this you agree to the terms of the license agreement.
Remember: You must agree to the license agreement and uncomment this
parameter to be able to proceed with the installation procedure.
b. Uncomment the Install Directory parameter and specify the directory in
which you want to install OMEGAMON XE for Messaging. To simplify the
management of Tivoli Monitoring products on Windows systems, install
Tivoli Monitoring products to the same directory on each component in
your environment. If you install to different directories on each component,
you will not be able to use the remote features provided by several product
configuration dialogs.
If you are installing OMEGAMON XE for Messaging on a system where
IBM Tivoli Monitoring is already installed, OMEGAMON XE for Messaging
will be installed to the installation directory of IBM Tivoli Monitoring,
regardless of this parameter.
c. If you do not want the OMEGAMON XE for Messaging program group to
be given the default name specified by the Install Folder parameter,
uncomment the parameter and enter a new name.
d. Uncomment the EncryptionKey parameter and enter a key with which to
encrypt your local passwords and user IDs. The encryption key must be 32
characters in length. If the key specified by this parameter is less than 32
characters, it will be padded with 9s.
e. In the [FEATURES] section, uncomment the parameters representing the
features that you want to install. The names of features are displayed
directly after the equals sign (=) of the parameter, with the component
which the feature belongs to displayed in brackets. The component code is
displayed before the equals sign.
Remember: If you want to install one or more agents on this system, make
sure that you uncomment the following line in addition to the
lines that represent the agents that you want to install:
KGLWICMA=Tivoli Enterprise Monitoring Agent Framework
For example, uncomment the following lines if you want to install the
WebSphere MQ Monitoring agent:
KGLWICMA=Tivoli Enterprise Monitoring Agent Framework
KMQWICMA=WebSphere MQ Monitoring Agent
Uncomment the following line if you want to install the WebSphere MQ
Monitoring agent application support on the Tivoli Enterprise Monitoring
Server:
KMQWICMS=WebSphere MQ Monitoring Agent Support (TEMS)
Uncomment the following line if you want to install the WebSphere MQ
Monitoring agent application support on the Tivoli Enterprise Portal Server:
58
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
KMQWICNS=WebSphere MQ Monitoring Agent Support (TEPS)
Uncomment the following line if you want to install the WebSphere MQ
Monitoring agent application support on the Tivoli Enterprise Portal client:
KMQWIXEW=WebSphere MQ Monitoring Agent Support (TEP Workstation)
f. In the [DEPLOY FEATURES] section, uncomment the parameters
representing the agents that you want to be configured for remote
deployment later. For example, uncomment the following line if you want
the WebSphere MQ Monitoring agent to be configured for remote
deployment later:
KMQWICMA=WebSphere MQ Monitoring Agent
3. Save the file and close the editor.
Remember: Do not use a long file name if you want to rename the response
file. Make sure that the length of the response file name is no
longer than eight and its file extension is no longer than three. Use
of a long file name might result in a failed installation.
Installing OMEGAMON XE for Messaging
To directly install OMEGAMON XE for Messaging using a silent installation,
perform the following steps:
1. Open a DOS Command prompt window.
2. Navigate to the directory that contains the OMEGAMON XE for Messaging
installation files (where the setup.exe file is).
3. Run the following command, you must specify the parameters in the same
order as listed below:
start /wait setup /z"/sfresponse_file_name" /s /f2"installation_log_file_name"
Where
response_file_name
Specifies the full path of the response file containing the parameters of
the installation (by default this file is named silent.txt). This parameter
cannot be omitted.
/s
Specifies that this is a silent install. This causes no responses to be
displayed during installation on the installed target workstation.
installation_log_file_name
The full path of the file to which log information will be written during
the installation process. This file is created during installation, and any
existing file with the same name is overwritten. If this parameter is not
specified, the Setup.log file in the same directory as the setup.iss file is
used to write log information.
For example, if the response file is located in C:\temp\SILENT.TXT and you
want the InstallShield log to be written to C:\temp\silent_setup.log, enter the
following command to start the silent installation:
start /wait setup /z"/sfC:\temp\SILENT.TXT" /s /f2"C:\temp\silent_setup.log"
Configuring the agents' default connection to Tivoli Enterprise
Monitoring Server
1. Open Manage Tivoli Enterprise Monitoring Services by selecting Start →
Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring Services.
2. Click Actions on the menu bar, and then select Set Defaults for All Agents
from the Actions menu.
3. On the Configuration Defaults for Connecting to a TEMS dialog:
Chapter 7. Installing IBM Tivoli OMEGAMON XE for Messaging on Windows system
59
v If the agent must cross a firewall to access the Tivoli Enterprise Monitoring
Server, select Connection must pass through firewall.
v Identify the type of protocol that the agent uses to communicate with the
Tivoli Enterprise Monitoring Server.
v Refer to the fields in Table 9 on page 65 to define the communications
between the agents and the Tivoli Enterprise Monitoring Server.
Installation of OMEGAMON XE for Messaging agents is now complete. Go back to
Chapter 2, “Installation roadmap,” on page 7 and continue with other installation
tasks.
60
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 8. Installing IBM Tivoli OMEGAMON XE for Messaging
on UNIX and Linux systems
This chapter contains step-by-step instructions for installing IBM Tivoli
OMEGAMON XE for Messaging on a UNIX or Linux system, using the command
line or the silent installation mode.
Important: If a previous version of IBM Tivoli OMEGAMON XE for Messaging
exists in your environment, see Upgrading to IBM Tivoli OMEGAMON
XE for Messaging 7.0 before proceeding.
You have the following two options to install IBM Tivoli OMEGAMON XE for
Messaging on a UNIX or Linux system:
v “Installing from the command line”
v “Performing a silent installation” on page 62
Installing from the command line
Instructions for installing IBM Tivoli OMEGAMON XE for Messaging on a UNIX
or Linux system computer are as follows:
Tip: If you are upgrading a WebSphere MQ Configuration agent from version 6.0
or 6.0.1, the existing configuration files, mc.cfg and mc.ini, are overwritten. If
you want to keep your existing configuration files, create a backup before
proceeding.
1. You can install the IBM Tivoli Monitoring software as the root user, but you
do not have to. If you do not install as a root user, you must following the
steps outlined in “Changing the file permissions for agents” on page 97 after
you install any monitoring agents.
2. Run the following command to create a temporary directory on the computer
on which you plan to install IBM Tivoli OMEGAMON XE for Messaging.
Make sure that the full path of the directory does not contain any spaces:
mkdir dir_name
3. Mount the installation CD for UNIX or Linux system to the temporary
directory you just created.
4. Run the following commands:
cd dir_name
./install.sh
where dir_name is the temporary directory you just created.
5. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory. If a message is displayed stating that the directory already exists
and asking whether to use it, enter 1 (yes) and press Enter.
6. If a message containing a list of running processes and warning you that
running products will be restarted during installation is displayed, to continue
with installation enter 1 (yes) and press Enter.
7. The following prompt is displayed:
© Copyright IBM Corp. 2005, 2009
61
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding.
4) Exit install.
Please enter a valid number:
Type 1 (yes) to start the installation and press Enter.
8. The first part of the software license agreement is displayed. Press Enter to
view latter parts of the agreement. Once you have finished viewing the
agreement, enter 1 to accept it or 2 to reject it and press Enter. You must
accept the agreement to continue with the installation process.
9. Enter a 32-character encryption key, or just press Enter to use the default.
10. A numbered list of available operating systems is displayed. Type the number
for the operating system that you are installing on and press Enter. The
default value is your current operating system.
Tips:
v If you are installing IBM Tivoli OMEGAMON XE for Messaging on
an EMT64 or AMD64 computer that is running SUSE Linux
Enterprise Server or Red Hat Enterprise Linux, select the Linux
AMD64 R2.6 (64 bit) item in the list.
11.
12.
13.
14.
v If you are installing IBM Tivoli OMEGAMON XE for Messaging on
the AIX version 6.1 operating system, AIX R5.3 (64 bit) is the default
value for the current operating system. You can accept the default
value and proceed with the next step.
Type 1 (yes) to confirm that the selected operating system is correct and press
Enter.
A numbered list of available components is displayed. Type the number that
corresponds to the component that you want to install on this computer. If
you want to install more than one component, use a comma (,) or space to
separate the numbers for each component, then press Enter.
A list of the components to install is displayed. Type 1 (yes) to confirm the
selection and start the installation process. Installation begins.
After all of the components are installed, you are asked whether you want to
install additional products or product support packages. Type 2 (no) and press
Enter to exit the installation process.
Remember: All of the installed agents of IBM Tivoli OMEGAMON XE for
Messaging are 32-bit regardless of whether your operating system is
32-bit or 64-bit.
Installation is complete. The next step is to “Configuring to connect an agent to the
Tivoli Enterprise Monitoring Server” on page 65
Performing a silent installation
Silent installation uses a response file to define what components you want to
install. A sample response file is shipped with IBM Tivoli OMEGAMON XE for
Messaging. The file name is silent_install.txt.
Before editing any of the response files, note the following syntax rules:
v Comment lines begin with a pound sign (#).
v Blank lines are ignored.
62
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
v Parameter lines are PARAMETER=value. Do not use a space before the
parameter; you can use a space before or after an equal sign (=).
v Do not use any of the following characters in any parameter value:
– Dollar sign ($)
– Equal sign (=)
– Pipe sign (|)
Installing components with a response file
The silent_install.txt file defines the installation parameters of IBM Tivoli
OMEGAMON XE for Messaging.
Tip: If you are upgrading a WebSphere MQ Configuration agent from version 6.0
or 6.0.1, the existing configuration files, mc.cfg and mc.ini, are overwritten. If
you want to keep your existing configuration files, create a backup before
proceeding.
Perform the following steps to run a silent installation:
1. You can install the IBM Tivoli Monitoring software as the root user, but you do
not have to. If you do not install as a root user, you must following the steps
outlined in “Changing the file permissions for agents” on page 97 after you
install any monitoring agents.
2. Run the following command to create a temporary directory on the computer
on which you plan to install IBM Tivoli OMEGAMON XE for Messaging. Make
sure that the full path of the directory does not contain any spaces:
mkdir dir_name
3. Mount the installation CD for the UNIX or Linux system to the temporary
directory you just created.
4. Run the following command:
cd dir_name
Where dir_name is the directory where the installation CD is mounted.
5. Edit the silent_install.txt file to set the parameters described in Table 8 to
appropriate values for your environment and save the changes:
Table 8. Parameters in a response file
Parameter
Description
INSTALL_ENCRYPTION_KEY
The data encryption key used to encrypt
data sent between systems. This key must be
the same as the key that is entered during
the installation of IBM Tivoli Monitoring.
Chapter 8. Installing IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux systems
63
Table 8. Parameters in a response file (continued)
Parameter
Description
INSTALL_FOR_PLATFORM
Use this parameter to install different agents
and application support for different
components silently. Specify the
INSTALL_FOR_PLATFORM parameter as
follows, depending on which component
you want to install application support for:
v To install an agent:
INSTALL_FOR_PLATFORM=<architecture
code>, where <architecture code> is the
code for the platform on which you are
installing the agent. For example, aix513
or sol283. For a complete list of
architecture codes, see Appendix C,
“Architecture codes,” on page 135.
v To install application support for Tivoli
Enterprise Monitoring Server:
INSTALL_FOR_PLATFORM=tms.
v To install application support for Tivoli
Enterprise Portal Server:
INSTALL_FOR_PLATFORM=tps.
v To install application support for Tivoli
Enterprise Portal desktop client:
INSTALL_FOR_PLATFORM=tpd (This applies to
Linux system only because desktop client
is not supported on UNIX system.)
v To install application support for Tivoli
Enterprise Portal browser client:
INSTALL_FOR_PLATFORM=tpw.
INSTALL_PRODUCT
The product code of the component that you
want to install. You can specify all to install
all the components of IBM Tivoli
OMEGAMON XE for Messaging. To install
multiple components but not all, repeat this
parameter for each component that you
want to install. For example, if you want to
install two components whose product codes
are pc1 and pc2, use:
INSTALL_PRODUCT=pc1
INSTALL_PRODUCT=pc2
Remember: The INSTALL_FOR_PLATFORM parameter can be specified only
once in the response file. If it is specified many times in the
response file, only the last value is valid.
6. Run the following command to start silent installation:
./install.sh -q -h install_dir -p silent_response_file_path
where
v install_dir is the IBM Tivoli OMEGAMON XE for Messaging home directory.
The default location is /opt/IBM/ITM.
v silent_response_file_path is the path of the response file that you use to specify
the installation parameters.
64
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Remember: You must specify the full path of this file, not just the file name.
Installation is complete. The next step is to “Configuring to connect an agent to the
Tivoli Enterprise Monitoring Server”
Configuring to connect an agent to the Tivoli Enterprise Monitoring
Server
Use the following procedure to connect an agent to the Tivoli Enterprise
Monitoring Server:
1. Go to the install_dir/bin directory, where install_dir is the directory where IBM
Tivoli Monitoring is installed. The default is /opt/IBM/ITM.
2. Run the following command from the directory:
./itmcmd config -A pc
where pc is a two-character product code. See Appendix A, “Product codes,”
on page 131. For example, if you are configuring WebSphere MQ Monitoring
agent, the command must be:
./itmcmd config -A mq
3. Press Enter when you are asked if the agent connects to a Tivoli Enterprise
Monitoring Server.
4. Type the name of the host system on which the Tivoli Enterprise Monitoring
Server that you want the agent to connect to is installed and press Enter.
5. Type the protocol that you want to use to communicate with the Tivoli
Enterprise Monitoring Server. You have four choices: ip, sna, ip.pipe, or
ip.spipe and press Enter.
6. If you want to set up a backup protocol, enter that protocol and press Enter. If
you do not want to use a backup protocol, press Enter without specifying a
protocol.
7. Depending on the type of protocol you specified, provide the following
information when prompted:
Table 9. Communication protocol settings
Field
Description
IP
Port number
The listening port number of the Tivoli
Enterprise Monitoring Server. The default
value is 1918.
IP.PIPE settings
Port number
The listening port of the Tivoli Enterprise
Monitoring Server. The default value is 1918.
KDC Partition
The KDC partition. The default value is null.
IP.SPIPE settings
Port number
The listening port of the Tivoli Enterprise
Monitoring Server. The default value is 3660.
SNA settings
Network Name
The SNA network identifier of your location.
Chapter 8. Installing IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux systems
65
LU Name
The LU name of the Tivoli Enterprise
Monitoring Server. This LU name
corresponds to the Local LU Alias in your
SNA communications software.
Log Mode
The name of the LU6.2 LOGMODE. The
default value is CANCTDCS.
8. When asked if you want to configure a secondary Tivoli Enterprise
Monitoring Server, type 2 (no) and press Enter.
9. When asked to enter an optional primary network name, type 0 and press
Enter.
10. Restart the agent by running the following command from the install_dir/bin
directory:
./itmcmd agent start pc
where pc is a two-character product code and install_dir is the IBM Tivoli
OMEGAMON XE for Messaging installation directory.
Tivoli Enterprise Monitoring Server connection configuration is now complete.
Installation of OMEGAMON XE for Messaging agents is now complete. Go back to
Chapter 2, “Installation roadmap,” on page 7 and continue with other installation
tasks.
66
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging
on i5/OS systems
Of the IBM Tivoli OMEGAMON XE for Messaging components, only WebSphere
MQ Monitoring and WebSphere MQ Configuration are currently supported on
i5/OS systems. This chapter contains instructions for installing these two agents.
Before you begin, verify that your site is in compliance with the agents’ hardware
and software prerequisites listed in “i5/OS system prerequisites” on page 19.
Remember: Be sure that QMQMADM authority is given to the KMQ User Profile
as the default setting.
Pre-installation tasks
Perform the following tasks before you install the IBM Tivoli OMEGAMON XE for
Messaging on i5/OS systems.
Verifying TCP/IP configuration
This step ensures that your TCP/IP network services are configured to return the
fully qualified host name of the Tivoli Enterprise Monitoring Server and the agents
(for example: #HostName.ibm.com). This configuration is necessary to minimize
the risk of inconsistent values being returned for the host name.
If your site uses SNA for network communications, you do not need to complete
this step; skip to “Deleting old versions of agents” on page 68.
Procedure
1. If your site uses DNS, verify that it is configured to return the fully qualified
host name of the Tivoli Enterprise Monitoring Server and the agents (for
example: “#hostName.ibm.com”).
2. Confirm that you have configured TCP/IP with the correct parameters, as
follows:
a. From an i5/OS system command line, enter
CFGTCP
b. Select Work with TCP/IP host tables entries.
c. Confirm that the first entry in the Host Name column is the fully qualified
host name associated with the IP address of the i5/OS system where you
will install the Tivoli Enterprise Monitoring Server or agent (for example:
“#hostName.ibm.com”). If it is not, change it now to the fully qualified host
name.
d. Return to the Configure TCP/IP menu and select “Change TCP/IP domain
information”.
e. Confirm that a host name and domain name are provided and that they
match the entry you just confirmed in the TCP/IP Host Table.
f. Confirm that the first entry for “Host name search priority” is “*LOCAL”.
© Copyright IBM Corp. 2005, 2009
67
Updating IBM Tivoli Monitoring OS agent
If the i5/OS system is installed with the i5/OS Agent 0KA4610 or earlier, update it
to IBM Tivoli Monitoring 6.2 fix pack 1 (5724C04) or later.
Deleting old versions of agents
You must complete this step if you are currently running any agents and want to
replace them with the version supplied at this release. For example, if you are
currently running a previous version of the monitoring agent for WebSphere MQ,
you must delete it before you install WebSphere MQ Monitoring. Or, if you are
currently running a previous version of the configuration agent for WebSphere
MQ, you must delete it before you install WebSphere MQ Configuration.
If you are a new customer and are not running any agents, skip to “Preparing your
WebSphere MQ environment” on page 68.
This step deletes from your system any versions of agents prior to the version
supplied with this release. This step is necessary due to architectural changes in
the new agents.
Procedure
1. Verify that the earlier version of the agent is not running. From an i5/OS
system command line, enter:
ENDOMA
If any WebSphere MQ Monitoring agent is running, from an i5/OS system
command line, enter:
WRKOMAMQ
Press F15 to stop all WebSphere MQ Monitoring agents.
If any WebSphere MQ Configuration agent is running, from an i5/OS system
command line, enter:
GO OMAMC
Select 3 from the menu to stop the WebSphere MQ Monitoring agent.
2. Delete the agent. From an i5/OS system command line, enter:
DLTLICPGM LICPGM(0Kppvvv)
where:
pp is:
v MQ for WebSphere MQ Monitoring.
v MC for WebSphere MQ Configuration.
vvv is:
the earlier version (for example, 430).
Preparing your WebSphere MQ environment
This step ensures that your site has a correctly configured WebSphere MQ
environment before proceeding with the installation of WebSphere MQ Monitoring
and WebSphere MQ Configuration agents.
Procedure
Verify that you are in compliance with the prerequisites below:
68
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
v WebSphere MQ Monitoring and WebSphere MQ Configuration agents use a
WebSphere MQ license. Verify that your site has enough licenses to install the
agents.
v The instructions in this guide assume that WebSphere MQ default objects, such
as SYSTEM.DEFAULT.MODEL.QUEUE, exist. If they do not currently exist in
your environment, you must create them before attempting to start the agent.
v If you want to monitor WebSphere MQ events, ensure that the following
WebSphere MQ parameters are enabled (refer to your WebSphere MQ
documentation if necessary):
–
–
–
–
–
INHIBTEV
LOCALEV
PERFMEV
REMOTEEV
STRSTPEV
Checking the authority level of the user ID
This step ensures that the user that will install and configure WebSphere MQ
Monitoring and WebSphere MQ Configuration agents has the proper authority.
There are two internal user profiles in Tivoli OMEGAMON XE for Messaging,
KMQ and KMC. By default, these internal user profiles have all the required
authorities.
Remember: Only the minimum authority requirements are described in this
section.
v To install IBM Tivoli OMEGAMON XE for Messaging components, verify the
following requirement is fulfilled:
– The user has the Security Officer (*SECOFR) authority on the i5/OS system
where the installation will take place.
v To configure, start, or stop the WebSphere MQ Configuration agent, verify the
following requirements are fulfilled:
– The user has the Job Control (*JOBCTL) authority to the user.
– The user has the *USE authority for the KMC user profile.
– The user has the *ALL authority for the KMCLIB and KMCTMP libraries.
– The KMC user profile has the Job Control (*JOBCTL) authority.
– The KMC user profile has the *ALL authority for the KMCLIB and KMCTMP
libraries.
v To configure, start, or stop the WebSphere MQ Monitoring agent, verify the
following requirements are fulfilled:
– The user has the Job Control (*JOBCTL) authority to the user.
– The user has the *USE authority for the KMQ user profile.
– The user has the *ALL authority for the KMQLIB and KMQTMP libraries.
– The KMQ user profile has the Job Control (*JOBCTL) authority.
– The KMQ user profile has the *ALL authority for the KMQLIB and KMQTMP
libraries.
– If the user want to issue the Take Action command on Tivoli Enterprise
Portal, the KMQ user profile should have the *SPLCTL, *AUDIT, *SAVSYS,
*SERVICE authorities.
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS systems
69
Tip: Use the same user ID as that you used to install WebSphere MQ when you
install IBM Tivoli OMEGAMON XE for Messaging components. Otherwise,
there might be potential errors existing. For example, the error log file of
WebSphere MQ cannot be read.
Compiling information about your i5/OS systems
This step provides information that is needed before or during the installation and
configuration of WebSphere MQ Monitoring and WebSphere MQ Configuration
agents.
Procedure
Review each section below and complete the steps to obtain the information.
Verifying that the IBM OMEGAMON/400 agent is not installed: WebSphere MQ
Monitoring and WebSphere MQ Configuration agents cannot be installed on the
same system with the IBM OMEGAMON/400 agent.
Before installing WebSphere MQ Monitoring and WebSphere MQ Configuration
agents, you must check for the existence of the IBM OMEGAMON/400 agent and
delete it if it is present using the steps below.
1. Access an i5/OS system command line and enter the following command:
GO LICPGM
2. At the Work with Licensed Programs, enter
12
(Delete licensed programs).
3. Check in the Licensed Program column for entry 57xxES1 (the IBM
OMEGAMON/400 agent).
4. If the entry exists, enter
4
in the Option column next to it to delete.
Verifying which version of i5/OS system you are running:
1. Access an i5/OS system command line and enter the following command:
DSPSFWRSC
2. Press F11 to display software resources.
3. In the Resource ID column, look for 57xx999.
4. Check the corresponding Release column for the version number; for example,
V5R3M0.
Verifying that the TCP/IP Utilities is installed, if necessary: If the installation
requires the TCP/IP Utilities, check for its presence as follows:
1. Access an i5/OS system command line, and enter the following command:
GO LICPGM
2. At the Work with Licensed Programs enter
10
(Display installed licensed programs).
3. Look for the following entry:
*COMPATIBLE TCP/IP Connectivity Utilities for AS/400 system
4. If the TCP/IP Utilities is not installed, you must install it. It is supplied as part
of the operating system
70
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Verifying the primary language of your i5/OS system: During installation you
will be required to know whether or not the primary language of your i5/OS
system is English. To determine this, complete the steps below:
1. Access an i5/OS system command line and enter the following command:
GO LICPGM
2. Enter
20
(Display installed secondary languages).
The Display Installed Secondary Languages dialog is displayed.
3. Note the primary language and description displayed in the upper left corner.
An English system is primary language ″2924″, description ″English″.
4. Press Enter to continue.
Configuring IBM Tivoli OMEGAMON XE for Messaging across
a firewall
This section provides an overview of IBM’s implementation of firewall support. It
explains basic concepts and gives sample scenarios of various configurations. This
section does not include specific steps for configuring IBM Tivoli OMEGAMON XE
for Messaging across a firewall; those steps can be found either in the installation
chapters of this guide or in the other platform-specific installation guides,
depending upon which operating systems you are configuring on.
Basic implementation
At this release, IBM Tivoli OMEGAMON XE for Messaging supports most
common firewall configurations, including those that use address translation
(application proxy firewall is a notable exception). To enable this support, IBM uses
the IP.PIPE socket address family, a TCP-based protocol that opens a single port on
the firewall for communication by IBM Tivoli OMEGAMON XE for Messaging
components. If your target IBM Tivoli OMEGAMON XE for Messaging
environment includes a firewall between any components, you must specify
IP.PIPE as your communication protocol during configuration. No other special
configuration is needed unless your firewall also uses address translation.
Implementation with address translation
Address translation is an enhanced security feature of some firewall configurations.
With this feature, components that must be reached across the firewall have two
unique, but corresponding addresses: the external address (valid for components
outside the firewall) and the internal address (valid for components inside the
firewall).
With regard to IBM Tivoli Monitoring, the component that typically must be
reached for connection is the Tivoli Enterprise Monitoring Server. However, the
Warehouse Proxy, which runs on Windows system as a server-type application,
must also be accessible to clients and would also require an external and internal
address. A component on either side of the firewall only knows about the address
that is valid for its side (its “partition”).
To accommodate sites with address translation, IBM uses a partition-naming
strategy. This strategy requires two steps:
v The creation of a text file called a partition file as part of the configuration of a
hub or remote Tivoli Enterprise Monitoring Server (or Warehouse Proxy). The
partition file contains an entry that defines that component’s address in the
other partition.
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS systems
71
v The specification of a partition name (any alphanumeric string up to 32
characters), as part of the configuration of any agent, a hub or remote Tivoli
Enterprise Monitoring Server, or Warehouse Proxy. A partition name must be
specified for each component regardless of which side of the firewall it is in.
Sample scenarios
Assuming that your site has one firewall, there would be two partitions: one
outside the firewall, one inside the firewall. In the sample scenarios that follow we
will specify the names OUTSIDE and INSIDE, respectively, for these partitions. (If
your site’s configuration includes more than one firewall, IBM Suggests that you
contact IBM Software Support for assistance in configuring IBM Tivoli
OMEGAMON XE for Messaging.)
Remember: Whatever the operating system, the command-line examples in the
following scenarios adhere to the UNIX and Windows system text
formatting conventions for literals and variables.
Scenario 1: hub Tivoli Enterprise Monitoring Server INSIDE, agents OUTSIDE:
As part of the configuration of the hub Tivoli Enterprise Monitoring Server, we
specify the name of the partition that it is in INSIDE. We also create a partition file
names parthub.txt, containing the following entry:
OUTSIDE ip.pipe:hub's_external_address
OUTSIDE is the partition name outside the firewall and hub’s_external_address is the
address of the hub Tivoli Enterprise Monitoring Server that is valid for the agents.
As part of the configuration of each agent, we specify the name of the partition
that each is in OUTSIDE.
When an agent starts, the parthub.txt file is searched for an entry that matches the
partition name OUTSIDE and sees the Tivoli Enterprise Monitoring Server address
that is valid for the agents (the external address).
Scenario 2: hub and remote Tivoli Enterprise Monitoring Servers INSIDE, agents
OUTSIDE:
Remember: In Scenarios 2 and 3, it is assumed that all agents report to the remote
Tivoli Enterprise Monitoring Server.
As part of the configuration of the hub Tivoli Enterprise Monitoring Server, we
specify the name of the partition that it is in INSIDE. No partition file is needed
because the only component that reports to the remote Tivoli Enterprise
Monitoring Server is also inside the firewall.
As part of the configuration of the remote Tivoli Enterprise Monitoring Server, we
specify the name of the partition that it is in INSIDE. A partition file named
partremote.txt must also be created at the remote Tivoli Enterprise Monitoring
Server. It contains the following entries:
OUTSIDE ip.pipe:remote's_external_address
When configuring the agents (all of which are outside the firewall, reporting to the
remote Tivoli Enterprise Monitoring Server), we specify the name of the partition
that they are in OUTSIDE. When the agents start, the partremote.txt file is searched
for an entry that matches the partition name OUTSIDE and sees the remote Tivoli
Enterprise Monitoring Server address that is valid for them (the external address).
72
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Scenario 3: hub Tivoli Enterprise Monitoring Server INSIDE, remote Tivoli
Enterprise Monitoring Server and agents OUTSIDE: As part of the configuration
of the hub Tivoli Enterprise Monitoring Server, we specify the name of the
partition that it is in INSIDE. We also create a partition file named parthub.txt,
containing the following entry:
OUTSIDE ip.pipe:hub's_external_address
OUTSIDE is the partition name outside the firewall and hub’s_external_address is the
address of the hub Tivoli Enterprise Monitoring Server that is valid for the remote
Tivoli Enterprise Monitoring Server.
As part of the configuration of both the agents and the remote Tivoli Enterprise
Monitoring Server, we specify the name of the partition they are in OUTSIDE.
A partition file named partremote.txt also must be created at the remote Tivoli
Enterprise Monitoring Server. It contains the following entry:
INSIDE ip.pipe:remote's_internal_address
If the hub Tivoli Enterprise Monitoring Server needs to communicate with the
remote Tivoli Enterprise Monitoring Server (for example, to issue a report request
from an agent that is connected to the remote Tivoli Enterprise Monitoring Server),
the partremote.txt file is searched for an entry that matches the partition name
INSIDE and sees the remote Tivoli Enterprise Monitoring Server address that is
valid for it (the internal address).
Installing IBM Tivoli OMEGAMON XE for Messaging
Purpose of this step:
This step loads the software for WebSphere MQ Monitoring and WebSphere MQ
Configuration agents from the IBM Tivoli OMEGAMON XE for Messaging Product
CD and uses the Restore Licensed Program RSTLICPGM command to complete its
installation.
Two procedures are provided:
v “Installing from a PC CD-ROM”
v “Installing from an i5/OS system CD-ROM (command line)” on page 75
Use one of the two procedures, whichever is most convenient for you or your site.
These procedures assume that you have completed the steps in Chapter 3,
“Preparing for installation,” on page 11.
Important: The same user ID must be used when you install IBM Tivoli
OMEGAMON XE for Messaging components as that you used to
install WebSphere MQ. Otherwise, there may be potential errors
existing. For example, the attribute file can not be read.
Installing from a PC CD-ROM
1. Access an i5/OS system command line.
2. Check that the system value QALWOBJRST is set to “*ALL”.
a. Enter this command:
WRKSYSVAL QALWOBJRST
b. Select “5” (Display), and verify that the value is set to “*ALL”. If it is set
to any other value(s), record those value(s) below:
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS systems
73
QALWOBJRST _____________________________________________
3. Press Enter to continue.
4. If QALWOBJRST was set to “*ALL”, continue with the next step below;
otherwise, do the following:
a. On the Work with System Values dialog, enter 2 to change the values.
b. On the Change System Value dialog, change the existing values to *ALL.
c. Press Enter to save your change.
d. Press F3 to return.
5. At the i5/OS system command line, create an i5/OS system library for
installation:
CRTLIB KMQ_TMPLIB TEXT('MQ INSTALL LIBRARY')
6. Create two save files in the KMQ_TMPLIB library:
CRTSAVF KMQ_TMPLIB/MQ700CMA TEXT('KMQ INSTALL PRODUCT')
CRTSAVF KMQ_TMPLIB/MC700CMA TEXT('KMC INSTALL PRODUCT')
7. Insert the IBM Tivoli OMEGAMON XE for Messaging Product CD into the
CD-ROM drive.
8. From a DOS prompt, start an FTP session:
FTP machinename
where machinename is the name of the target i5/OS system.
9. When prompted, enter your i5/OS system user ID and password.
10. Change the FTP type to binary:
BINARY
11. Transfer the software for WebSphere MQ Monitoring and WebSphere MQ
Configuration agents from the CD-ROM to the i5/OS system:
PUT e:\OS400\MQ700CMA KMQ_TMPLIB/MQ700CMA
PUT e:\OS400\MC700CMA KMQ_TMPLIB/MC700CMA
where e is your PC CD-ROM drive.
12. End your ftp session:
QUIT
13. Install the software for WebSphere MQ Monitoring and WebSphere MQ
Configuration agents (do one of the following ):
v If you are installing IBM Tivoli OMEGAMON XE for Messaging on a
system that is English upper and lower case (language ID 2924), do one of
the following:
a. If you want to install WebSphere MQ Monitoring, enter the following
command:
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) SAVF(KMQ_TMPLIB/MQ700CMA)
and proceed to step 14 on page 75 below.
b. If you want to install WebSphere MQ Configuration, enter the following
command:
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) SAVF(KMQ_TMPLIB/MC700CMA)
and proceed to step 14 on page 75 below.
v If you are installing on a non-language ID 2924 system, do one of the
following:
a. If you want to install WebSphere MQ Monitoring, check for the
existence of the KMQLNG work library.
1) If the library exists, clear it:
CLRLIB KMQLNG
74
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
2) If the library does not exist, create it:
CRTLIB KMQLNG
3) Enter the following commands:
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) RSTOBJ(*PGM) LNG(2924)
- SAVF(KMQ_TMPLIB/MQ700CMA)
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) RSTOBJ(*LNG) LNG(2924)
- SAVF(KMQ_TMPLIB/MQ700CMA) LNGLIB(KMQLNG)
This creates or recreates a library named KMQLIB containing all the
file transfer utilities components and definitions required to run the
software for WebSphere MQ Monitoring.
b. If you want to install WebSphere MQ Configuration, check for the
existence of the KMCLNG work libraries.
1) If the library exists, clear it:
CLRLIB KMCLNG
2) If the library does not exist, create it:
CRTLIB KMCLNG
3) Enter the following commands:
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) RSTOBJ(*PGM) LNG(2924)
- SAVF(KMQ_TMPLIB/MC700CMA)
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) RSTOBJ(*LNG) LNG(2924)
- SAVF(KMQ_TMPLIB/MC700CMA) LNGLIB(KMCLNG)
This creates or recreates a library named KMCLIB containing all the
file transfer utilities components and definitions required to run the
software for WebSphere MQ Configuration.
14. If you intend to install another agent, leave the QALWOBJRST value set to
“*ALL” until you are finished; otherwise, change it back to the value(s) you
recorded earlier.
15. If you will install the agent on another i5/OS system, use ftp or another file
transfer program to copy the save file to it.
16. Delete the installation library, which is no longer needed:
DLTLIB KMQ_TMPLIB
Installation of the software for WebSphere MQ Monitoring and WebSphere
MQ Configuration agents is complete.
17. If you are installing the WebSphere MQ Monitoring agent, perform the
following procedure:
a. From an i5/OS system command line, enter:
QSH
b. Run the following command:
mkdir /home/kmq
Installation of OMEGAMON XE for Messaging agents is now complete. Go back to
Chapter 2, “Installation roadmap,” on page 7 and continue with other installation
tasks.
Installing from an i5/OS system CD-ROM (command line)
1. Access an i5/OS system command line.
2. Check that the system value QALWOBJRST is set to “*ALL.“
3. Enter this command:
WRKSYSVAL QALWOBJRST
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS systems
75
4. Select “5” (Display), and verify that the value is set to “*ALL”. If it is set to
any other value(s), record those value(s) below:
QALWOBJRST _____________________________________________
5. Press Enter to continue.
6. If QALWOBJRST was set to “*ALL”, continue with the next step; otherwise,
do the following:
a. On the Work with System Values dialog, enter 2 to change the values.
b. On the Change System Value dialog, change the existing values to *ALL.
c. Press Enter to save your change.
d. Press F3 to return.
7. Create an i5/OS system library for installation:
CRTLIB KMQ_TMPLIB TEXT('MQ INSTALL LIBRARY')
8. Create a work folder.
a. Enroll your user ID to system distribution directory with the following
command:
ADDDIRE USRID(USER WBIUSER) USRD('WBI USER') USER(USER)
b. Enter this command:
WRKFLR
c. Select “1” (Create Folder), then specify
MQFLR
for the folder name.
9. Insert the IBM Tivoli OMEGAMON XE for Messaging Product CD into the
CD-ROM drive and enter:
WRKLNK QOPT
The Work with Object Links screen displays the qopt object link.
10. Select “5” (Next Level) at the qopt object link to select the next object link, the
volume ID (volid) of the CD-ROM.
Record this value for use during installation:
VOL ID _____________________________________________________
11. Continue to select “5” for each link level until the following path is displayed:
/QOPT/volid/AS400
where volid is the volume ID of the CD-ROM.
12. Look for file MC700CMA.SAVF and MQ700CMA.SAVF.
13. Enter the following commands:
CPYFRMSTMF FROMSTMF('/QOPT/volid/AS400/MC700CMA.SAVF')
- TOMBR('/qsys.lib/kmq_TMPLib.lib/MC700CMA.file')
CPYFRMSTMF FROMSTMF('/QOPT/volid/AS400/MQ700CMA.SAVF')
- TOMBR('/qsys.lib/kmq_TMPLib.lib/MQ700CMA.file')
14. Install the software for WebSphere MQ Monitoring and WebSphere MQ
Configuration (do one of the following procedures):
v If you are installing IBM Tivoli OMEGAMON XE for Messaging on a
system that is English upper and lower case (language ID 2924), do one of
the following:
a. If you want to install WebSphere MQ Monitoring, enter the following
command:
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) SAVF(KMQ_TMPLIB/MQ700CMA)
and proceed to step 14 on page 75 below.
76
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
b. If you want to install WebSphere MQ Configuration, enter the following
command:
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) SAVF(KMQ_TMPLIB/MC700CMA)
and proceed to step 14 on page 75 below.
v If you are installing on a non-language ID 2924 system, do one of the
following:
a. If you want to install WebSphere MQ Monitoring, check for the
existence of the KMQLNG work library.
1) If the library exists, clear it:
CLRLIB KMQLNG
2) If the library does not exist, create it:
CRTLIB KMQLNG
3) Enter the following commands:
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) RSTOBJ(*PGM) LNG(2924)
- SAVF(KMQ_TMPLIB/MQ700CMA)
RSTLICPGM LICPGM(0KMQ450) DEV(*SAVF) RSTOBJ(*LNG) LNG(2924)
- SAVF(KMQ_TMPLIB/MQ700CMA) LNGLIB(KMQLNG)
This creates or recreates a library named KMQLIB containing all the
file transfer utilities components and definitions required to run the
software for WebSphere MQ Monitoring.
b. If you want to install WebSphere MQ Configuration, check for the
existence of the KMCLNG work library.
1) If the library exists, clear it:
CLRLIB KMCLNG
2) If the library does not exist, create it:
CRTLIB KMCLNG
3) Enter the following commands:
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) RSTOBJ(*PGM) LNG(2924)
- SAVF(KMQ_TMPLIB/MC700CMA)
RSTLICPGM LICPGM(0KMC450) DEV(*SAVF) RSTOBJ(*LNG) LNG(2924)
- SAVF(KMQ_TMPLIB/MC700CMA) LNGLIB(KMCLNG)
This creates or recreates a library named KMCLIB containing all the
file transfer utilities components and definitions required to run the
software for WebSphere MQ Configuration.
15. If you intend to install another agent, leave the QALWOBJRST value set to
“*ALL” until you are finished; otherwise, change it back to the values you
recorded earlier.
16. Delete the installation objects that are no longer needed
a. Enter this command:
DLTLIB KMQ_TMPLIB
b. Delete MC700CMA.SAVF and MQ700CMA.SAVF from your folder:
v Enter this command:
WRKDOC FLR(MQFLR)
v Select 4 for MC700CMA.SAVF and MQ700CMA.SAVF.
v Press Enter to delete.
c. Press F3 to return to the command line.
Installation of the software for WebSphere MQ Monitoring and WebSphere
MQ Configuration agents is complete.
Chapter 9. Installing IBM Tivoli OMEGAMON XE for Messaging on i5/OS systems
77
17. If you are installing the WebSphere MQ Monitoring agent, perform the
following procedure:
a. From an i5/OS system command line, enter:
QSH
b. Run the following command:
mkdir /home/kmq
Installation of OMEGAMON XE for Messaging agents is now complete. Go back to
Chapter 2, “Installation roadmap,” on page 7 and continue with other installation
tasks.
78
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 3. Configuring IBM Tivoli OMEGAMON XE for Messaging
This part contains instructions for configuring each component of IBM Tivoli
OMEGAMON XE for Messaging on Windows system, Linux system, UNIX system
and i5/OS system. It also explains how to start or stop the components of IBM
Tivoli OMEGAMON XE for Messaging on Windows system, Linux system, UNIX
system and i5/OS system.
© Copyright IBM Corp. 2005, 2009
79
80
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 10. Configuring IBM Tivoli OMEGAMON XE for
Messaging on Windows system
This chapter contains instructions for configuring each component in IBM Tivoli
OMEGAMON XE for Messaging. Do not attempt to start these components before
completing the steps in this chapter.
Before Configuring IBM Tivoli OMEGAMON XE for Messaging
Before configuring IBM Tivoli OMEGAMON XE for Messaging, make sure that all
installation steps have been completed for IBM Tivoli OMEGAMON XE for
Messaging.
The rest of this chapter gives instructions for configuring each component of IBM
Tivoli OMEGAMON XE for Messaging. Do not attempt to start these components
before completing the steps in this chapter.
Configuring WebSphere Message Broker Monitoring
This section contains instructions for setting up WebSphere Message Broker
Monitoring before you start the component.
Authorizing the agent
By default, the account of each monitoring agent is set to LocalSystem in the
Manage Tivoli Enterprise Monitoring Services window. Before you start the
WebSphere Message Broker Monitoring, its account must be changed as explained
below. The agent’s user ID can be the same one that is used for starting the broker,
or you can create a new one.
To start and stop the WebSphere Message Broker Monitoring and to receive broker
data, the user ID used for running the monitoring agent must be a member of
groups mqm, mqbrkrs, and Administrators.
Follow these steps to authorize the agent’s user ID:
1. Log on to Windows system as a system administrator.
2. Create a user ID for the agent, if necessary. The agent’s user ID must:
v Have authority to subscribe to broker event publications.
v Belong to the groups, mqm (this must be the primary group), mqbrkrs, and
Administrators. The exact procedure for adding the user ID to a group
depends on the version of Windows system.
3. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
4. In the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere Message Broker Monitoring Agent and select Change Startup.
5. In the Log on As section, change from the system account to the user ID and
password for the account that you created above.
Depending on your site’s ACL entries, you might be required to authorize the
agent to receive broker event publications in the Message Brokers Toolkit. You
do not need to perform this step if your site uses the IBM defaults. However, if
© Copyright IBM Corp. 2005, 2009
81
ACL entries in the Topics tab of the Message Brokers Toolkit have been
modified such that Subscribe access to topics beginning with $SYS/Broker has
been restricted, this step is required.
An ACL entry for topics beginning with $SYS/Broker must be added to set
Subscribe access to Allow for the user ID of the agent. The principal for the
ACL entry must give the user ID of the agent, or it can give a group to which
the agent’s user ID belongs, such as mqbrkrs. The ACL entry must be deployed
to all brokers to be monitored by WebSphere Message Broker Monitoring. This
change allows the agent to receive the broker event publications. If the agent is
restricted from receiving these publications, much data in WebSphere Message
Broker Monitoring reports will be missing or inaccurate. (Specifically, the
Broker Events workspace will display no data.)
Tip: The simplest way to make sure that the user ID of the agent is fully
authorized for all the features of WebSphere Message Broker Monitoring is
to use the broker service user ID (the one that is used to start the broker)
for starting the agent.
Configuring the WebSphere Message Broker Monitoring agent
If you have configured the WebSphere Message Broker Monitoring agent during
installation, you do not need to reconfigure it for a second time. Otherwise, you
must configure the agent now by performing the following steps:
1. Select Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere Message Broker Monitoring Agent and select Configure using
defaults (or Reconfigure if the agent has already been configured).
3. (Reconfiguration only) To accept existing communications settings, click OK on
the two configuration windows that appear; or make any desired changes on
these windows, and then click OK.
4. You are prompted to edit the kqi.xml parameter file.
v If you want to accept the default parameters and monitor all brokers on your
system, you do not need to edit the kqi.xml file. Click No.
v If you want to change the parameters or monitor only certain brokers:
a. Click Yes.
The kqi.xml file is opened in Notepad.
b. Edit the parameters as desired, and then save the file in UTF-8 coding
and close the file.
For information about the parameters, see IBM Tivoli OMEGAMON XE
for Messaging: WebSphere Message Broker Monitoring User’s Guide.
c. Click Yes to configure the agent.
You are returned to the Manage Tivoli Enterprise Monitoring Services
window.
This completes initial configuration, and the agent is ready to start. See “Starting
and Stopping the components of IBM Tivoli OMEGAMON XE for Messaging” on
page 87 for information about how to start the agents on Windows system.
Creating multiple instances of the WebSphere Message Broker
Monitoring agent (optional)
Perform the following steps to create a secondary instance of the WebSphere
Message Broker Monitoring agent:
82
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere Message Broker Monitoring Agent and select Create Instance.
3. Enter a name for the instance when prompted and click OK. The new agent
instance is created and appears in the Manage Tivoli Enterprise Monitoring
Services window.
4. Right-click the newly created agent instance in the Manage Tivoli Enterprise
Monitoring Services window and select Configure Using Defaults.
5. A message is displayed asking if you want to update the configuration file of
the agent instance prior to configuring the WebSphere Message Broker
Monitoring agent. Click Yes.
6. A message is displayed stating that configuration will wait for you to close
your default text editor before continuing. Click OK. The configuration file is
opened in your default text editor.
7. Edit the configuration file as follows:
a. Ensure that the value of the agentId parameter is different to all other
instances of the agent running on the same system.
b. Use the MonitorBroker tag to specify which brokers the agent will monitor.
If this tag is not set, then all brokers on the system will be monitored. For
further information about the MonitorBroker tag, see IBM Tivoli
OMEGAMON XE for Messaging: WebSphere Message Broker Monitoring User’s
Guide.
8. Save and close the file
9. A message is displayed stating that the configuration file edit session is
complete. Click Yes to configure the agent.
The secondary agent instance is now configured and ready to start. Once you have
finished creating secondary instances of the WebSphere Message Broker
Monitoring agent, see “Starting and Stopping the components of IBM Tivoli
OMEGAMON XE for Messaging” on page 87 for information about how to start
the agents on Windows systems.
Installing the CandleMonitor node in broker environments
(optional)
The CandleMonitor node is an optional component that collects statistics on
message flow performance in a broker and provides a mechanism for generating
user-defined events within a message flow.
Before the CandleMonitor node can be used to monitor message flows, it must be
installed into your broker environments, as described below for Windows system
environments. For broker environments on UNIX system, see Chapter 11,
“Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux
system,” on page 89. For broker environments on a z/OS system, see IBM Tivoli
OMEGAMON XE for Messaging on z/OS: Configuration Guide.
After the CandleMonitor node is installed, it must be made available in the
Message Brokers Toolkit (V5, V5.1, V6, or V6.1). For instructions, see IBM Tivoli
OMEGAMON XE for Messaging: WebSphere Message Broker Monitoring User’s Guide.
Installing the CandleMonitor node
To install the CandleMonitor node into a broker environment on Windows system:
Chapter 10. Configuring IBM Tivoli OMEGAMON XE for Messaging on Windows system
83
1. Verify that the kqipnode.lil file was copied to the appropriate directory during
the installation of IBM Tivoli OMEGAMON XE for Messaging.
You can find the file in the broker bin directory. This is an example of a typical
bin location:
C:\Program Files\IBM\MQSI\6.0\bin
If the file was not copied to the broker bin directory during installation, do it
now by performing the following steps:
a. Shut down the broker.
b. Copy the kqipnode.lil file from the <install_dir>\TMAITM6 directory to the
broker bin directory.
2. Verify that the kqipnode.lil file in the broker's bin directory exactly matches (in
size and in date and time last modified) the one that is in the
<install_dir>\TMAITM6 directory. A mismatch of the release-level of these
files will cause a failure of the broker’s statistics and message flow events
reporting.
3. Restart the broker.
4. Repeat step 1 to step 3 for each Windows system with a broker to be
monitored.
Before you can use the CandleMonitor node in monitor message flows, it must also
be made available in the Message Brokers Toolkit (V5, V5.1, V6 or V6.1). For
instructions, see IBM Tivoli OMEGAMON XE for Messaging: WebSphere Message
Broker Monitoring User’s Guide.
The CandleMonitor node is now installed in your broker environment. See
“Starting and Stopping the components of IBM Tivoli OMEGAMON XE for
Messaging” on page 87 for information about how to start the agents on Windows
system
Configuring WebSphere MQ Configuration
This section contains instructions for setting up WebSphere MQ Configuration
before you start the component.
Configuring the WebSphere MQ Configuration agent
If you have configured the agent, you do not need to reconfigure it for a second
time, otherwise, you need to perform the following procedure to configure the
WebSphere MQ Configuration agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Configuration Agent and select Configure using defaults (or
Reconfigure if the agent has already been configured).
3. To accept existing communications settings, click OK on the two configuration
windows that appear; or make any desired changes on these windows, and
then click OK.
This completes initial configuration, and the agent is ready to start. See “Starting
and Stopping the components of IBM Tivoli OMEGAMON XE for Messaging” on
page 87 for information about how to start the agents on Windows system.
84
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Creating multiple instances of the WebSphere MQ
Configuration agent (optional)
By default a single WebSphere MQ Configuration agent instance is created during
installation, which is called the primary WebSphere MQ Configuration agent.
Under normal circumstances, you can use the primary agent to perform all your
configuration tasks. However, if the queue managers that you want to configure
are running in a Microsoft Cluster Services (MSCS) or High Availability Cluster
Multi Processing (HACMP™) cluster environment, you might need to create a
secondary agent instance. Perform the following steps to create a secondary agent
instance on Windows systems:
Perform the following steps to create a non-primary instance of the WebSphere MQ
Configuration agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Configuration Agent and select Create Instance.
3. Enter a name for the instance when prompted and click OK. The new agent
instance is created and listed in the Manage Tivoli Enterprise Monitoring
Services window.
4. Right-click the newly created agent instance in the Manage Tivoli Enterprise
Monitoring Services window and select Configure Using Defaults.
5. A message is displayed asking if you want to update the configuration file of
the agent instance prior to configuration of WebSphere MQ Configuration
agent. Click Yes.
6. A message is displayed stating that configuration will wait for you to close the
Notepad edit session before continuing. Click OK.
7. Set the KMC_CLUSTERNAME and KMC_QUEUEMGRS parameters. The
KMC_CLUSTERNAME parameter is the host name of the cluster node on
which the agent runs. The KMC_QUEUEMGRS parameter is the name of one
or more queue managers on the cluster node that you want the agent instance
to configure. Separate different queue manager names with a comma (,).
8. A message is displayed stating that the configuration file edit session is
complete. Click Yes to configure the agent.
A secondary instance of the WebSphere MQ Configuration agent is now created
and ready to start.
Once you have finished creating secondary instances of the WebSphere MQ
Configuration agent, see “Starting and Stopping the components of IBM Tivoli
OMEGAMON XE for Messaging” on page 87 for information about how to start
the agents on Windows systems.
Configuring WebSphere MQ Monitoring
This section contains instructions for setting up WebSphere MQ Monitoring before
you start the component.
Creating default objects
Before starting the WebSphere MQ Monitoring, WebSphere MQ default objects
such as SYSTEM.DEFAULT.MODEL.QUEUE must exist. If they do not exist in
your environment, create them before starting the agent. See your WebSphere MQ
documentation for information about how to create these default objects.
Chapter 10. Configuring IBM Tivoli OMEGAMON XE for Messaging on Windows system
85
Authorizing user IDs
By default, the account of each monitoring agent is set to LocalSystem in the
Manage Tivoli Enterprise Monitoring Services window. If you want to run the
monitoring agent under a user ID rather than under the system account, you must
first authorize the user ID. Only user IDs that are members of the mqm group are
authorized to start and stop the monitoring agent.
1. Log on to Windows system as a System Administrator.
2. Add the user ID that is to be used for running the agent to the mqm group.
The exact procedure depends on the version of Windows system.
3. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
4. In the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Monitoring Agent and select Change Startup.
5. In the Log on As section, change from the system account to the user ID and
password for the user account.
Configuring the monitoring agent
If you have configured the agent, you do not need to reconfigure it for a second
time, otherwise, you need to perform the following procedure to configure the
WebSphere MQ Monitoring agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Monitoring Agent and select Configure using defaults (or
Reconfigure if the agent has already been configured).
3. To accept existing communications settings, click OK on the two configuration
windows that appear; or make any desired changes on these windows, and
then click OK.
4. You are prompted to edit the agent .cfg file. (The primary agent’s configuration
file is named mq.cfg.)
v If your site has a specified default queue manager and you want the agent to
monitor the default queue manager, the agent’s default .cfg file will operate
successfully with no modifications. Click No. The agent will be configured
using defaults. If necessary, you can customize this file later.
v If your site does not have a default queue manager specified, or if you want
to configure this agent to monitor a queue manager other than the default,
click Yes. A Notepad session opens. Supply the queue manager name in the
MANAGER NAME() and MGRNAME() parameters of the .cfg file, then save
and close the Notepad session. Click Yes at the next prompt to continue.
You are returned to the Manage Tivoli Enterprise Monitoring Services window.
This completes initial configuration, and the agent is ready to start. Go to “Starting
and Stopping the components of IBM Tivoli OMEGAMON XE for Messaging” on
page 87 for information about how to start the agents on Windows system.
Creating multiple instances of the WebSphere MQ Monitoring
agent (optional)
By default the WebSphere MQ Monitoring agent monitors a single queue manager.
If you want to monitor multiple queue managers on one computer, you need to
create multiple instances.
86
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
The first instance of the agent, which is created during installation, is called the
primary agent. Any other agents that you create on the same host are secondary
agents.
Remember:
1. You cannot use the following process to create multiple instances of WebSphere
MQ Monitoring agent if the agent is deployed remotely instead of being
installed locally.
2. Names of different instances of WebSphere MQ Monitoring agent are
case-insensitive, while names of WebSphere MQ queue manager are
case-sensitive. Therefore, avoid using the case-sensitive Websphere MQ queue
managers names.
To create multiple instances of the WebSphere MQ Monitoring agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services to open the Manage Tivoli Enterprise Monitoring Services window.
2. From the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Monitoring Agent and select Create Multi-Instance.
A dialog is displayed with the queue managers that are not monitored by
WebSphere MQ Monitoring agent displayed in the Available Instances list. You
can use Instance Filter to specify criteria for filtering queue managers in the
Available Instances list. The filter can only be used to filter queue managers
starting with a specific string. The wild characters '*' and '?' are not supported
by the filter.
3. Select the queue managers that you want to monitor from Available Instances,
and click >> to add them to Selected Instances. Click OK.
New agent instances are created and listed on the Manage Tivoli Enterprise
Monitoring Services window. The agents have already been configured and are
ready to start.
Once you have finished creating secondary instances of the WebSphere MQ
Monitoring agent, see “Starting and Stopping the components of IBM Tivoli
OMEGAMON XE for Messaging” for information about how to start the agents on
Windows system.
Starting and Stopping the components of IBM Tivoli OMEGAMON XE
for Messaging
The components of IBM Tivoli OMEGAMON XE for Messaging run as Windows
system services. Use the Manage Tivoli Enterprise Monitoring Services window
to start the IBM Tivoli services installed on this system. Some services will start
automatically if they are configured for auto-start; however, you might need to
start other services manually.
Starting the components
1. When you have completed configuring IBM Tivoli OMEGAMON XE for
Messaging, you may reboot the system.
2. Open the Manage Tivoli Enterprise Monitoring Services window by clicking
Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services.
3. Start the services in this order:
a. Tivoli Enterprise Monitoring Server
b. Agents
Chapter 10. Configuring IBM Tivoli OMEGAMON XE for Messaging on Windows system
87
c. Tivoli Enterprise Portal Server
To start each service, right-click the service name in the Manage Tivoli
Enterprise Monitoring Services window and select Start.
4. Wait for the Status column to display Started.
Stopping the components
1. Open the Manage Tivoli Enterprise Monitoring Services window by selecting
Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services.
2. Stop the services in this order:
a. Tivoli Enterprise Portal Server
b. Agents
c. Tivoli Enterprise Monitoring Server
To stop each service, right-click the service name in the Manage Tivoli
Enterprise Monitoring Services window and select Stop.
3. Wait for the Status column to show Stopped.
IBM Tivoli OMEGAMON XE for Messaging agent configuration is now complete.
Go back to the Chapter 2, “Installation roadmap,” on page 7 to continue with the
installation process.
88
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for
Messaging on UNIX and Linux system
This chapter provides instructions for configuring each component of IBM Tivoli
OMEGAMON XE for Messaging on UNIX and Linux system computers. Do not
attempt to start the agents before completing the tasks in this chapter.
Configuring WebSphere Message Broker Monitoring
This section contains instructions for configuring WebSphere Message Broker
Monitoring before you can start to use the component. Perform the following tasks:
1. “Creating library links to start the agent (Linux systems only)”
2. “Creating a link to the DB2 library” on page 90
3. “Authorizing the agent” on page 90
4. “Configuring the agent using Manage Tivoli Enterprise Monitoring Services” on
page 92
5. “Configuring the agent from the command line” on page 92
6. “Starting or stopping multiple agents using the itmcmd agent command” on
page 92
7. “Customizing parameters” on page 92
8. “Installing the CandleMonitor node (optional)” on page 93
9. “Defining the required environment variable (Linux zSeries only)” on page 91
Creating library links to start the agent (Linux systems only)
This section is applicable to Linux systems only. UNIX system users can proceed
directly to the next section.
Before the WebSphere Message Broker Monitoring agent will function correctly on
Linux systems, links need to be created so that library names can be resolved
correctly.
Perform the following procedure:
1. Check whether the following links point to the correct libraries. If not, define
the links again:
v For WebSphere Message Broker Monitoring 6.0, in the /opt/mqm/lib directory
point to the 3.2 GNU-compiler-built versions of libraries provided by IBM. If
these links point to other GNU versions of libraries, redefine the links as
follows:
ln -sf /opt/mqm/lib/3.2/libimqb23gl_r.so /opt/mqm/lib/libimqb23gl_r.so
ln -sf /opt/mqm/lib/3.2/libimqb23gl.so /opt/mqm/lib/libimqb23gl.so
v For WebSphere Message Broker Monitoring 7.0, in the /opt/mqm/lib directory
point to the 3.3 GNU-compiler-built versions of libraries provided by IBM. If
these links point to other GNU versions of libraries, redefine the links as
follows:
ln -sf /opt/mqm/lib/3.3/libimqb23gl_r.so /opt/mqm/lib/libimqb23gl_r.so
ln -sf /opt/mqm/lib/3.3/libimqb23gl.so /opt/mqm/lib/libimqb23gl.so
Remember: The root authority is required to define these links.
© Copyright IBM Corp. 2005, 2009
89
2. Check whether the libstdc++-libc6.1-2.so.3 file exists in the /usr/lib directory. If
not, define the following link:
ln -s /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so /usr/lib/libstdc++-libc6.1-2.so.3
Tip: You might need to substitute libstdc++-3-libc6.2-2-2.10.0.so for another
library name available in your /usr/lib directory.
Remember: If these links are incorrect or not created, the agent will fail to start,
and the following message is displayed in the agent log:
.../kqiagent : error while loading shared libraries: <library name>:
cannot open shared object file: No such file or directory
Creating a link to the DB2 library
You must create a link to the DB2 library before you can issue Take Action
commands (such as QI StartBroker) on UNIX or Linux systems.
To create this link, open the qi.ini file in install_dir/config/, where install_dir is the
directory in which IBM Tivoli OMEGAMON XE for Messaging is installed, and
perform one of the following operations depending on your operating system:
v
– For 64-bit AIX systems, append the following path to the line that contains
the $LIBPATH parameter:
:<DB2_install_dir>/lib64:<DB2_install_dir>/lib32
where <DB2_install_dir> is the DB2 installation directory.
– For 64-bit HP-UX, 64-bit Solaris, and 64-bit Linux systems, append the
following path to the line that contains the $LD_LIBRARY_PATH parameter:
<DB2_install_dir>/lib64:<DB2_install_dir>/lib32
where <DB2_install_dir> is the DB2 installation directory.
– For other UNIX or Linux systems, append the following path to the line that
contains the $LD_LIBRARY_PATH parameter:
:<DB2_install_dir>/lib
where <DB2_install_dir> is the DB2 installation directory.
Authorizing the agent
If you choose to use the broker’s user ID (the user ID that is used to start the
broker) to start the agent, you can skip this step because this user ID is fully
authorized to use all the features of WebSphere Message Broker Monitoring. This
step is required if you choose to use a different user ID.
Notes:
1. Do not start the agent with a user ID that has a higher authority than the
broker’s user ID.
2. Do not start the agent with a user ID that has root authority unless the broker’s
user ID has root authority.
Perform the following steps to authorize the agent to receive broker data if you
choose not to user the broker’s user ID to start the agent:
1. Create a user ID which belongs to the mqm (the primary group) and mqbrkrs
groups.
90
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Remember: To support WebSphere Message Integration Broker V5 or earlier
versions, the user ID that is used to start the agent must use the
profile located in the broker samples directory
(/opt/mqsi/sample/profiles or /usr/opt/mqsi/sample/profiles on AIX
systems).
2. Make sure that the user ID has the right to create and update the files in the
following directories:
v install_dir/logs
v install_dir/config
v install_dir/arch/qi/hist
where install_dir is the installation directory of IBM Tivoli OMEGAMON XE for
Messaging and arch is the architecture code for your operating system. (See
Appendix C, “Architecture codes,” on page 135 for a complete list of
architecture codes)
3. If ACL entries in the Topics tab of the Message Brokers Toolkit show that
subscription access to topics beginning with $SYS/Broker is restricted, perform
the following steps:
a. Add an ACL entry for topics beginning with $SYS/Broker to set Subscribe
access to Allow for the user ID of the agent. The principal for the ACL
entry must contain the user ID of the agent, or the group to which the
agent’s user ID belongs, such as mqbrkrs
b. Deploy the ACL entry to all the brokers which will be monitored by
WebSphere Message Broker Monitoring. This change allows the agent to
receive the broker event publications. If the agent is restricted from
receiving these publications, much data in WebSphere Message Broker
Monitoring reports will be missing or inaccurate. (Specifically, the Broker
Events workspace will display no data.)
Defining the required environment variable (Linux zSeries
only)
This section is applicable to Linux zSeries systems only.
After you have created the soft links, before you restart the broker on Linux
zSeries systems, you need to define an environment variable. If the variable is not
set correctly, the broker will fail to load the kqipnode.lil file and produce the
following error message:
undefined symbol: read__7istreamPcl
To define the environment variable on Linux zSeries systems, perform the
following steps:
1. Open the profile of the user ID that is used to start the broker. By default it is
located in the following file depending on the version of your WebSphere
Message Broker:
v For WebSphere Message Broker V5: /opt/mqsi/sample/profiles/profile.lnx
v For WebSphere Message Broker V6: /opt/ibm/mqsi/6.0/bin/mqsiprofile
v For WebSphere Message Broker V6.1: /opt/ibm/mqsi/6.1/bin/mqsiprofile
If you are using a profile other than the default one, open that profile.
2. Append the following lines to the file and save it:
MQSI_PRELOAD=/opt/gcc295/lib/libstdc++-libc6.2-2.so.3
export MQSI_PRELOAD
3. Run the profile of the user ID that is used to start the broker.
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux system
91
4. Run the DB2 profile by executing the following command:
DB2_Instance_Home/sqllib/db2profile
where DB2_Instance_Home is the home directory of the DB2 instance.
5. Restart the broker.
Configuring the agent using Manage Tivoli Enterprise
Monitoring Services
Configure the connection between the Tivoli Enterprise Monitoring Server and the
WebSphere Message Broker Monitoring from the Manage Tivoli Enterprise
Monitoring Services window. See IBM Tivoli Monitoring Installation and Setup Guide.
Configuring the agent from the command line
To configure the agent from a command line, use the itmcmd config script. The
itmcmd config command is in the install_dir/bin directory. Run the itmcmd config
command as follows:
cd install_dir/bin
./itmcmd config -A [-h install_dir] [-a arch] qi
where install_dir is the installation directory for IBM Tivoli OMEGAMON XE for
Messaging; arch is the IBM Tivoli architecture code for the operating system on
which you installed the agent. (See Appendix C, “Architecture codes,” on page 135)
For more information about the itmcmd config command, see IBM Tivoli
Monitoring Command Reference.
Starting or stopping multiple agents using the itmcmd agent
command
When using itmcmd agent from the command line, optionally specify the broker
name. Use the -o option to specify an agent ID (4 or fewer characters) and the -p
option to give a broker name, so that use multiple WebSphere Message Broker
Monitoring agents on the same system, to monitor different brokers.
Example:
./itmcmd agent -o agentID -p brokername start|stop qi
or
./itmcmd agent -o agentID start|stop qi
The Hostname_qi_brokername_##_agentID.xml file is created automatically when
using this option, where Hostname is the name of the host where the agent is
running, brokername is the name of the broker that is monitored by the new agent
instance, and agentID is the ID of the new agent instance.
To run a single monitoring agent on the system, using the default monitoring
parameters in the kqi.xml file, run itmcmd agent as follows:
./itmcmd agent start|stop qi
Customizing parameters
The parameters that determine the operational and monitoring characteristics of
WebSphere Message Broker Monitoring are in an XML file created during product
installation. If desired, customize these parameters. For information and
instructions, see the IBM Tivoli OMEGAMON XE for Messaging: WebSphere Message
Broker Monitoring User’s Guide book.
92
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
This completes initial configuration, and the agent is ready to start. See “Starting or
stopping the agents” on page 97 for information about how to start the agent.
Creating multiple instances of the WebSphere Message Broker
Monitoring agent (optional)
Perform the following steps to create a secondary instance of the WebSphere
Message Broker Monitoring agent:
1. Log on to the UNIX or Linux system where the agent is installed.
2. Navigate to the install_dir/bin directory, where install_dir is the IBM Tivoli
OMEGAMON XE for Messaging installation directory.
3. Run the following command to create a secondary instance of the WebSphere
Message Broker Monitoring agent:
./itmcmd agent -o [agent_Id] -p [broker_name] start qi
where [agent_Id] is a unique 4-digit alphanumeric agent ID different from all
other agent instances running on the same system, and [broker_name] is name of
the monitored broker.
The secondary agent instance is now configured and ready to start.
Installing the CandleMonitor node (optional)
In the following circumstances, the CandleMonitor node will be configured
automatically during installation and there is no need to read this section.
v Your broker is installed in the default location.
v You have the single version of broker installed.
v You did not install the WebSphere Message Broker Monitoring agent using
remote deployment.
The CandleMonitor node is an optional component of WebSphere Message Broker
Monitoring that collects statistics on message flow performance in a broker and
provides a mechanism for generating user-defined events within a message flow. If
your broker is installed in a different location rather than the default one or you
installed the agent using remote deployment, you must create links to it; if you
have different versions of broker installed, installer will only create soft links for
the latest version of broker during installation and you must create links for the
older version.
Remember: With V5, V6 and V6.1 brokers, IBM provides message flow accounting
and statistics that partially overlap with the statistics provided by the
CandleMonitor node and can be monitored in Tivoli Enterprise Portal
without including the CandleMonitor node in message flows.
However, the CandleMonitor node provides additional statistics, as
well as the ability to monitor sub-flows and define message flow
events. Message flows without a CandleMonitor node are not
represented in Statistics workspaces. The CandleMonitor node does
not function with WebSphere MQ Event Broker v2.1.
Important: You must use a user ID with root authority when installing the
CandleMonitor node.
To install the CandleMonitor node in a broker running on UNIX or Linux systems,
perform the following steps:
1. Navigate to the /user/bin directory.
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux system
93
2. Run the following commands to create a set of soft links:
ln -sf <install_dir>/<arch>/qi/bin/kqipnode.lil
/<broker_dir>/lil/kqipnode.lil
ln -sf <install_dir>/<arch>/qi/bin/kqipnode.cfg
/<<broker_dir>/lil/kqipnode.cfg
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/<broker_dir>/messages/<langcode>/CandleMonitorNode.cat
Where, <install_dir> is the full path of the OMEGAMON XE for Messaging
installation directory, <langcode> is the code for the installed IBM Tivoli
OMEGAMON XE for Messaging language pack, <broker_dir> is the full path of
the broker installation directory, and <arch> is the platform architecture code.
See Appendix B, “Language codes,” on page 133 for a list of language codes
and Appendix C, “Architecture codes,” on page 135 for a list of architecture
codes.
Create another link by running one of the commands below depending on
which operating system you are using:
v On AIX:
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/usr/lib/nls/msg/<langcode>/CandleMonitorNode.cat
v On Solaris:
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/usr/lib/locale/C/LC_MESSAGES/CandleMonitorNode.cat
v On HP-11:
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/usr/lib/nls/msg/C/CandleMonitorNode.cat
v On Intel-based Linux:
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/usr/share/locale/C/LC_MESSAGES/CandleMonitorNode.cat
v On Linux for zSeries:
ln -sf <install_dir>/<arch>/qi/bin/<langcode>/CandleMonitorNode.cat
/usr/share/locale/C/LC_MESSAGES/CandleMonitorNode.cat
3. To take full advantage of 64-bit architectures, if you are running the
CandleMonitor node on a 64-bit AIX, Solaris or HP-UX (PA-RISC, not Itanium®)
system you must also create links to an additional 64-bit version of the
CandleMonitor node file. To do this, repeat step 2, replacing the kqipnode.lil
filename with kqipnode64.lil.
4. If you are running Linux on zSeries systems, you need to define the required
environment variable, as described in “Defining the required environment
variable (Linux zSeries only)” on page 91.
5. Restart the broker.
Remember: After the CandleMonitor node is installed, it must be made available
in the Message Brokers Toolkit (V5, V5.1, V6 or V6.1). For information
about how to make the CandleMonitor node available in the Message
Brokers Toolkit, see the Customizing the CandleMonitor Node chapter
in IBM Tivoli OMEGAMON XE for Messaging: WebSphere Message Broker
Monitoring User’s Guide.
Configuring WebSphere MQ Configuration
This section contains instructions for setting up WebSphere MQ Configuration
before you start the component.
94
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Creating multiple instances of the WebSphere MQ
Configuration agent (optional)
By default a single WebSphere MQ Configuration agent instance is created during
installation, which is called the primary WebSphere MQ Configuration agent.
Under normal circumstances, you can use the primary agent to perform all your
configuration tasks. However, if the queue managers that you want to configure
are running in a Microsoft Cluster Services (MSCS) or High Availability Cluster
Multi Processing (HACMP) cluster environment, you might need to create a
secondary agent instance. Perform the following steps to create a secondary agent
instance on UNIX and Linux systems:
1. Log on to the UNIX or Linux system as root.
2. Navigate to the following directory:
install_dir/bin
Where install_dir is the IBM Tivoli OMEGAMON XE for Messaging installation
directory.
3. Run the following command to create a secondary instance of the WebSphere
MQ Configuration agent:
./itmcmd agent -o [instance name] start mc
Where [instance name] is the name of the new agent instance.
4. Navigate to the following directory:
install_dir/config
Where install_dir is the IBM Tivoli OMEGAMON XE for Messaging installation
directory.
5. Open the configuration file of the newly created agent instance in a text editor.
The filename is in the following format:
hostname_mc_InstanceName.cfgWhere, [hostname] is the name of the host where
the agent is running on; [instance name] is the name of the new agent instance.
6. Set the KMC_CLUSTERNAME and KMC_QUEUEMGRS parameters and close
Notepad. KMC_CLUSTERNAME is the host name of the cluster node on which
the agent runs. KMC_QUEUEMGRS is the name of one or more queue
managers on the cluster node that you want the agent instance to configure.
Separate different queue manager names with a comma (,).
7. Edit any other parameters as necessary then save and close the file.
The secondary agent instance is now configured and ready to start.
Configuring WebSphere MQ Monitoring
This section contains instructions for setting up WebSphere MQ Monitoring before
you start the component.
Assigning the agent to a user group
The user ID which is used to start the agent must be a member of the mqm group.
Creating default objects
Before starting the WebSphere MQ Monitoring agent, WebSphere MQ default
objects such as SYSTEM.DEFAULT.MODEL.QUEUE must already exist. If they do
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux system
95
not exist in your environment, create them before starting the agent. See
WebSphere MQ documentation for information about how to create these default
objects.
Creating multiple instances of the WebSphere MQ Monitoring
agent (optional)
A WebSphere MQ Monitoring agent monitors a single WebSphere MQ queue
manager by default. You can create multiple instances of WebSphere MQ
Monitoring agent to monitor multiple queue managers on the same computer.
The first instance of the agent, which is created during installation, is called the
primary agent. Any other agents you create on the same host are secondary agents.
Important: You cannot use the following process to create multiple instances of
WebSphere MQ Monitoring agent if the agent is deployed remotely
instead of installed locally.
Perform the following steps to create secondary instances of the WebSphere MQ
Monitoring agent:
1. Run the following commands to open the Manage Tivoli Enterprise Monitoring
Services window:
cd install_dir/bin
./itmcmd manage
where install_dir is the installation directory of IBM Tivoli OMEGAMON XE for
Messaging. The default is /opt/IBM/ITM.
2. In the Manage Tivoli Enterprise Monitoring Services window, right-click
WebSphere MQ Monitoring Agent, and then click Create MultiInstance. The
Create MultiInstance window is displayed.
The queue managers that are not monitored by a WebSphere MQ Monitoring
agent are displayed in the Available Instances list. You can use Instance Filter
to specify criteria for filtering queue managers in the Available Instances list.
The filter can only be used to filter queue managers starting with a specific
string. The wild characters '*' and '?' are not supported by the filter.
3. Select the queue manager in the Available Instances list, which you want to
monitor, and then click Add. Or select the queue manager in the Selected
Instances list, and click Remove.
4. Click OK. Configuration files are created for each queue manager using the
default configuration. The configuration files are in the install_dir/config
directory.
The secondary agent instance is now configured and ready to start.
Customizing monitoring options (optional)
You can change the monitoring options for WebSphere MQ Monitoring at any time
by editing the agent’s .cfg file. For example, if you want to collect historical
monitoring data, you need to set the HISTORY parameter to YES in the PERFORM
STARTMON statement in the agent’s .cfg file.
The configuration file for an instance of the WebSphere MQ Monitoring agent has
the following naming convention:
[hostname]_mq_[queue_manager_name].cfg
96
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
v For information on historical data collection, see IBM Tivoli OMEGAMON XE for
Messaging: WebSphere MQ Monitoring User’s Guide.
v For information on monitoring options and commands, see IBM Tivoli
OMEGAMON XE for Messaging: WebSphere MQ Monitoring User’s Guide.
Starting or stopping the agents
This section contains instructions about how to start or stop the agents and how to
change the file permissions for agents so that you can use non-root user IDs to run
the agents on a UNIX or Linux system computer.
Changing the file permissions for agents
If you plan to use non-root users to run the agents on a UNIX or Linux system
computer, perform the following steps to change the file permissions of agent files
to ensure that the non-root user IDs can run the agents successfully:
1. Log on to the computer as root, or become the root user by running the su
command.
2. Create a new group (such as itmusers) to own all of the files in the
OMEGAMON XE for Messaging installation directory (The default is
/opt/IBM/ITM). For Linux system, Solaris, and HP-UX computers, run the
following command:
groupadd itmusers
For an AIX computer, run the following command:
mkgroup itmusers
3. Navigate to the Messaging installation directory.
4. Run the following commands:
chgrp -R itmusers .
chmod -R o-rwx .
chmod -R g+rwx .
5. Run the following command to change the ownership of additional agent files:
bin/SetPerm
6. If you want to run the agent as a particular user, add the user to the itmusers
group. To do this, edit the /etc/group file and ensure that the user is in the list of
users for the itmusers group. For example, if you want to run the agent as user
test1, ensure that the following line is in the /etc/group file:
itmusers:x:504:test1
7. Run the su command to switch to the user that you want to run the agent as or
log on as that user.
Now you can use non-root user IDs in the itmusers group to start, run, and stop
agents.
Tip: Step 3 to Step 5 in this procedure can also be performed by the following
command:
secureMain -g itmusers lock
Starting an agent from the Manage Tivoli Enterprise
Monitoring Services
1. Go to the install_dir/bin directory, where install_dir is the installation directory of
IBM Tivoli OMEGAMON XE for Messaging.
2. Enter the following command:
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux system
97
./itmcmd manage
The Manage Tivoli Enterprise Monitoring Services window is displayed.
3. Right-click the agent that you want to start and click Start Service from the
menu.
4. If the agent that you want to start is the WebSphere MQ Monitoring agent, you
are prompted to specify the instances for which you want to start monitoring.
Perform the following steps:
a. Select existing monitoring instances to start or add new instance to start in
the dialog.
b. Click Start.
You can also start an agent from the command line. See “Starting an agent from
the command line” for information about how to start or stop an agent from the
command line.
Stopping an agent from the Manage Tivoli Enterprise
Monitoring Services
1. Go to the install_dir/bin directory, where install_dir is the installation directory of
IBM Tivoli OMEGAMON XE for Messaging.
2. Enter the following command:
./itmcmd manage
The Manage Tivoli Enterprise Monitoring Services window is displayed.
3. Right-click the agent that you want to stop and click Stop Service.
4. If the agent that you want to stop is the WebSphere MQ Monitoring agent, you
are prompted to specify the instances for which you want to stop monitoring.
Perform the following steps:
a. Select existing monitoring instances to stop or add new instance to stop in
the dialog.
b. Click Stop.
You can also stop an agent from the command line. See “Stopping an agent from
the command line” for information about how to start or stop an agent from the
command line.
Starting an agent from the command line
1. Go to the install_dir/bin directory, where install_dir is the installation directory of
IBM Tivoli OMEGAMON XE for Messaging.
2. Enter the following command to start an agent:
./itmcmd agent start pc
where pc is a two-character product code. See Appendix A, “Product codes,” on
page 131.
For additional information about the itmcmd agent command, see IBM Tivoli
Monitoring: Installation and Setup Guide.
Stopping an agent from the command line
1. Go to the install_dir/bin directory, where install_dir is the installation directory of
IBM Tivoli OMEGAMON XE for Messaging.
2. Enter the following command to stop an agent:
./itmcmd agent stop pc
98
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
where pc is the two-character product code. See Appendix A, “Product codes,”
on page 131.
Tip: See the configuration instructions for each component for additional itmcmd
agent command parameters that might apply to that component. For
additional information about the itmcmd agent command, see IBM Tivoli
Monitoring Command Reference.
Chapter 11. Configuring IBM Tivoli OMEGAMON XE for Messaging on UNIX and Linux system
99
100
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 12. Configuring IBM Tivoli OMEGAMON XE for
Messaging on i5/OS system
This chapter contains step-by-step instructions for verifying installation and
configuration of WebSphere MQ Monitoring and WebSphere MQ Configuration
agents on i5/OS systems.
Configuring WebSphere MQ Configuration
This step establishes the necessary network connections between WebSphere MQ
Configuration and the Tivoli Enterprise Monitoring Server to which it will report.
Online Help is available by pressing F1.
Procedure
1. From an i5/OS system command line, enter this command
GO OMAMC
2. Enter 4 to select OMEGAMON Configuration Agent for MQSeries®.
The configure TEMA (CFGOMAMC) dialog is displayed.
3. Enter your site’s values for the displayed parameters using the guidelines
below.
If your site is using a firewall through which component of any IBM Tivoli
packages will communicate, be sure to read “Configuring IBM Tivoli
OMEGAMON XE for Messaging across a firewall” on page 71 before you begin
this step.
Table 10. Parameters for the configure TEMA (CFGOMAMC) Dialog
Parameter
Description
TEMS SNA location
The SNA location of the Tivoli Enterprise Monitoring Server that
this agent will report to. If you will not use SNA, enter “*NONE”.
If the correct SNA location was previously defined, enter “*SAME“
to retrieve it. If you need to define a new SNA location (which can
be the Control Point Name or the remote location name) enter its
name (for example: S10B6322).
TEMS TCP/IP
address
The TCP/IP address. If you will not use TCP/IP, enter “*NONE”.
If the correct TCP/IP address was previously defined, enter
“*SAME” to retrieve it. If you need to define a different TCP/IP
address, enter it (for example: 129.0.132.45).
TEMS IP.PIPE
Address
If IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration
must connect to the Tivoli Enterprise Monitoring Server through a
firewall, you must use IP.PIPE. Specify the IP.PIPE address. If you
will not use IP.PIPE, enter “*NONE”.
Secondary TEMS SNA The SNA location of a secondary Tivoli Enterprise Monitoring
location
Server that this agent will report to if it cannot communicate with
the primary Tivoli Enterprise Monitoring Server at startup.
Secondary TEMS IP
address
© Copyright IBM Corp. 2005, 2009
The TCP/IP address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
101
Table 10. Parameters for the configure TEMA (CFGOMAMC) Dialog (continued)
Parameter
Description
Secondary TEMS
IP.PIPE Address
The IP.PIPE address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
Partition Name
(Required only by sites with firewalls that use address translation.)
The name of the partition that this instance of IBM Tivoli
OMEGAMON XE for WebSphere MQ Configuration is in (up to 32
alphanumeric characters).
Firewall in use
If IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration
must connect to the Tivoli Enterprise Monitoring Server through a
firewall, enter “*YES”. If not, retain the default of “*NO”.
TEMS TCP/IP port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses SNA or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter “*SAME”.to retrieve it. If you need to specify a
different Tivoli Enterprise Monitoring Server port address, enter it
(up to six numeric characters).
TEMS SNA port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter “*SAME” to retrieve it. If you need to specify a
different Tivoli Enterprise Monitoring Server port address, enter it
(up to six numeric characters).
TEMS IP.PIPE port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
SNA, ignore this field. If you need to specify a different Tivoli
Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
Action user profile
The user authority under which user action must be administered.
Retain the default value of QAUTOMON to grant user system
operator authority.
SNA transaction
program
This prompt is displayed only if you entered a value (or “*SAME”)
for Tivoli Enterprise Monitoring Server SNA location. The name of
the SNA transaction program. IBM Suggests retaining the default
value of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or “*SAME”)
for SNA location. The name of the SNA transaction program
library. IBM Suggests retaining the default value of KMSCMS.
Transaction program
(backup)
This prompt is displayed only if you entered a value (or “*SAME”)
for Secondary Tivoli Enterprise Monitoring Server SNA location.
The name of the SNA transaction program. IBM Suggests retaining
the default value of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or “*SAME”)
for Secondary Tivoli Enterprise Monitoring Server SNA location.
The name of the SNA transaction program library. IBM Suggests
retaining the default value of KMSCMS.
If you are reconfiguring the agent, the changes will take effect the next time the
agent is started.
Configuration of WebSphere MQ Configuration is complete.
4. Proceed to “Verifying installation and configuration” on page 103.
102
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Verifying installation and configuration
This step starts (and optionally stops) IBM Tivoli OMEGAMON XE for WebSphere
MQ Configuration, verifying that it has been installed and configured correctly.
Procedure
Starting the agent:
1. Verify that the Tivoli Enterprise Monitoring Server that the agent connects to is
started.
2. From an i5/OS system command line, enter this command:
GO OMAMC
3. Verify that the WebSphere MQ command server is started. If not, enter the
following command to start it:
STRMQMCSVR MQMNAME(QMgr_Name)
where QMgr_Name is the name of the queue manager.
4. Enter 2 to select OMEGAMON Configuration Agent for MQSeries.
5. Verify that the following messages are displayed:
Tivoli Enterprise Management Agent startup in progress
Tivoli Enterprise Monitoring Server located
Tip: It might be several minutes before the “Online” status is displayed in the
Tivoli Enterprise Portal Managed System Status workspace (log on to
Tivoli Enterprise Portal, right-click the Enterprise icon, and then click
Workspace → Managed System Status from the menu).
6. Repeat the above steps on each system where you want to start IBM Tivoli
OMEGAMON XE for WebSphere MQ Configuration.
Stopping the agent (optional): To stop WebSphere MQ Configuration, use the
following procedure:
1. From an i5/OS system command line enter this command:
GO OMAMC
2. Enter 3 to select End OMEGAMON Configuration Agent for MQSeries.
3. Press F4 to see options for ending the agent, and specify one of the following:
v “*IMMED” to shut down immediately
v “*CNTRLD” for a controlled shutdown. With a controlled shutdown, also
specify the following options:
– “Delay time”, in seconds. Shutdown is delayed for the time interval that
you specify, allowing the agent to complete operations.
– “Allow abnormal end if needed (YES, NO)”. If you enter “YES”, any jobs
that have not ended normally after 10 minutes will shut down abnormally.
4. Look for a message that states that Tivoli Enterprise Management Agent ended.
Verification of the installation and configuration of IBM Tivoli OMEGAMON
XE for WebSphere MQ Configuration is complete.
Starting or stopping the agent from the command Line
You can use this procedure to start or stop WebSphere MQ Configuration agent
from an i5/OS system command line.
Starting WebSphere MQ Configuration agent: To start your agent from an i5/OS
system command line, type this command:
STROMAMC
Chapter 12. Configuring IBM Tivoli OMEGAMON XE for Messaging on i5/OS system
103
Stopping WebSphere MQ Configuration agent: To stop your agent from an
i5/OS system command line, type this command:
ENDOMAMC
Configuring WebSphere MQ Monitoring
This part contains step-by-step instructions for configuring and verifying
installation and configuration of WebSphere MQ Monitoring.
Configuring WebSphere MQ Monitoring
Purpose of this step:
This step establishes the necessary network connections between WebSphere MQ
Monitoring and the Tivoli Enterprise Monitoring Server to which it will report.
Online Help is available by pressing F1.
Procedure
1. From an i5/OS system command line enter this command
WRKOMAMQ
The Add OMEGAMON Agent for WebSphere MQ dialog displays.
(If this is not the first access, a different dialog displays; press F6 to display the
Add OMEGAMON Agent for WebSphere MQ dialog.)
2. Enter the name of the Queue Manager that this agent will monitor, along with
a text description, and press Enter.
The configure TEMA (CFGOMAMQ) dialog is displayed.
3. Enter your site’s values for the displayed parameters using the guidelines
below.
If your site is using a firewall through which components of any IBM Tivoli
package will communicate, be sure to read “Configuring IBM Tivoli
OMEGAMON XE for Messaging across a firewall” on page 71 before you begin
this step.
Table 11. Parameters for The configure TEMA(CFGOMAMQ) Dialog
Parameter
Description
TEMS SNA location
The SNA location of the Tivoli Enterprise Monitoring Server that
this agent will report to. If you will not use SNA, enter *NONE. If
the correct SNA location was previously defined, enter *SAME to
retrieve it. If you need to define a new SNA location (which can be
the Control Point Name or the remote location name) enter its
name (for example: S10B6322).
TEMS TCP/IP
address
The TCP/IP address. If you will not use TCP/IP, enter *NONE. If the
correct TCP/IP address was previously defined, enter *SAME to
retrieve it. If you need to define a different TCP/IP address, enter
it (for example: 129.0.132.45).
TEMS IP.PIPE
Address
If IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
must connect to the Tivoli Enterprise Monitoring Server through a
firewall, you must use IP.PIPE. Specify the IP.PIPE address. If you
will not use IP.PIPE, enter *NONE.
Secondary TEMS SNA The SNA location of a secondary Tivoli Enterprise Monitoring
location
Server that this agent will report to if it cannot communicate with
the primary Tivoli Enterprise Monitoring Server at startup.
104
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Table 11. Parameters for The configure TEMA(CFGOMAMQ) Dialog (continued)
Parameter
Description
Secondary TEMS IP
address
The TCP/IP address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
Secondary TEMS
IP.PIPE Address
The IP.PIPE address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
Partition Name
(Required only by sites with firewalls that use address translation.)
The name of the partition that this instance of WebSphere MQ
Monitoring agent is in (up to 32 alphanumeric characters).
Firewall in use
If WebSphere MQ Monitoring must connect to the Tivoli Enterprise
Monitoring Server through a firewall, enter *YES. If not, retain the
default of *NO.
TEMS TCP/IP port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses SNA or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter *SAME to retrieve it. If you need to specify a different
Tivoli Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
TEMS SNA port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter *SAME to retrieve it. If you need to specify a different
Tivoli Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
TEMS IP.PIPE port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
SNA, ignore this field. If you need to specify a different Tivoli
Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
Action user profile
The user authority under which user action must be administered.
Retain the default value of QAUTOMON to grant user system
operator authority.
SNA transaction
program
This prompt is displayed only if you entered a value (or *SAME) for
Tivoli Enterprise Monitoring Server SNA location. The name of the
SNA transaction program. IBM Suggests retaining the default value
of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or *SAME) for
SNA location. The name of the SNA transaction program library.
IBM Suggests retaining the default value of KMSCMS.
Transaction program
(backup)
This prompt is displayed only if you entered a value (or *SAME) for
Secondary Tivoli Enterprise Monitoring Server SNA location. The
name of the SNA transaction program. IBM Suggests retaining the
default value of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or *SAME) for
Secondary Tivoli Enterprise Monitoring Server SNA location. The
name of the SNA transaction program library. IBM Suggests
retaining the default value of KMSCMS.
4. Read the Options choices and Function Key choices available for each dialog to
determine which keys to press to save and exit the dialog.
Chapter 12. Configuring IBM Tivoli OMEGAMON XE for Messaging on i5/OS system
105
If you are reconfiguring the agent, the changes will take effect the next time the
agent is started.
5. If you are configuring multiple instances of WebSphere MQ Monitoring, repeat
these steps. The first instance Added is automatically assigned suffix 00001, the
second instance Added is automatically assigned suffix 00002, and so on.
Configuration of WebSphere MQ Monitoring is complete.
6. For monitoring the WebSphere MQ V6, the account used to login to the Tivoli
Enterprise Portal must be created on i5/OS system. Meantime, appropriate
authority such as BROWSE must be assigned to the dead letter queue object.
For example, you need to assign SYSADMIN with BROWSE authority if you
want SYSADMIN to have right to browse DLQ messages. To check whether
you have authority to access the DLQ object, enter following command from an
i5/OS system command line:
QSYS/DSPMQMAUT OBJ(DLQ_Name) OBJTYPE(*Q) USER(SYSADMIN) MQMNAME(QM_Name)
where DLQ_Name is the DLQ name; SYSADMIN is your account used to login
to the Tivoli Enterprise Portal; QM_Name is the Queue Manager name.
7. Proceed to “Verifying installation and configuration” on page 106.
Verifying installation and configuration
This step starts (and optionally stops) WebSphere MQ Monitoring, verifying that it
has been installed and configured correctly.
Procedure
Starting the agent:
1. Verify that the Tivoli Enterprise Monitoring Server that the agent connects to is
started.
2. From an i5/OS system command line, enter this command:
WRKOMAMQ
The Work with Tivoli Monitoring Agent for WebSphere MQ dialog displays.
3. Enter 14 in the Option column next to the agent that you want to start.
The Status column indicates when the agent is started.
4. Enter 5 in the Option column next to the agent to display its log. Verify that the
following message is displayed (Scroll up to the top of the log to see it):
Tivoli Enterprise Monitoring Server located
Tip: It might be several minutes before the “Online” status is displayed in the
Tivoli Enterprise Portal Managed System Status workspace (log on to
Tivoli Enterprise Portal, right-click the Enterprise icon, and then click
Workspace → Managed System Status from the menu).
5. Repeat these steps on each system where you want to start WebSphere MQ
Monitoring.
Stopping the agent (optional):
1. From an i5/OS system command line, enter this command:
WRKOMAMQ
The Work with Tivoli Monitoring Agent for WebSphere MQ dialog displays.
2. Enter 15 in the Option column next to the agent that you want to stop (end).
The End Tivoli Enterprise Management Agent dialog displays.
3. Suggested default values are supplied in the dialog. Here are options for
ending the agent:
106
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
v “*CNTRLD” for a controlled shutdown. With a controlled shutdown, also
specify the following options:
– “Delay time”, in seconds. Shutdown is delayed for the time interval that
you specify, allowing the agent to complete operations.
– “Allow abnormal end if needed (YES, NO)”. If you enter “YES”, any jobs
that have not ended normally after 10 minutes will shut down abnormally.
Press Enter to proceed.
4. The Work with Tivoli Monitoring Agent for WebSphere MQ dialog displays.
The Status column indicates the agent is “Ending...” then, eventually, “Not
Started”.
5. Enter 5 in the Option column next to the agent to display its log.
Look for a message that states that job KMQnnnnn completed normally.
Verification of the installation and configuration of IBM Tivoli OMEGAMON
XE for WebSphere MQ Monitoring is complete.
6. Proceed to “Customizing monitoring options (optional)” on page 107.
Starting or stopping the agent from a command line
You can use this procedure to start or stop WebSphere MQ Monitoring agent from
an i5/OS system command line.
Starting WebSphere MQ Monitoring agent:
To start your agent from an i5/OS system command line, type this command:
STROMAMQA SUFFIX(xxxxx)
where xxxxx is a unique number, starting with 00001, to identify each WebSphere
MQ Queue Manager.
Tip: If you do not know the suffix associated with this instance of the WebSphere
MQ Queue Manager, type this command at an i5/OS system command line:
WRKOMAMQ
In the dialog that displays, the suffix will appear to the right of the associated
instance that is listed.
Stopping WebSphere MQ Monitoring agent:
To stop your agent from an i5/OS system command line, type this command:
ENDOMAMQA SUFFIX(xxxxx)
where xxxxx is a unique number, starting with 00001, to identify each WebSphere
MQ Queue Manager.
Tip: If you do not know the suffix associated with this instance of the WebSphere
MQ Queue Manager, type this command at an i5/OS system command line:
WRKOMAMQ
In the dialog that displays, the suffix will appear to the right of the associated
instance that is listed.
Customizing monitoring options (optional)
You can use this step to customize monitoring options for a single queue manager.
Default monitoring options are set at installation; however, change the defaults by
Chapter 12. Configuring IBM Tivoli OMEGAMON XE for Messaging on i5/OS system
107
using the agent management program to specify options in the KMQLIB/MQnnnnn
monitoring file associated with the agent. This file is read when WebSphere MQ
Monitoring is started.
Procedure
To edit the monitoring file, follow these steps.
1. If you are unfamiliar with the various monitoring options and the commands
to enable them, refer to IBM Tivoli OMEGAMON XE for Messaging: WebSphere
MQ Monitoring User’s Guide.
If you want to collect historical data, you must set the HISTORY option to
“YES” on the PERFORM STARTMON statement in the monitoring file. See IBM
Tivoli Monitoring Administrator’s Guide for additional instructions related to
historical data collection.
2. When you are ready to customize the monitoring file, from an i5/OS system
command line enter the following command:
WRKOMAMQ
The main dialog for working with WebSphere MQ Monitoring displays
Work with Tivoli Monitoring Agent for WebSphere MQ System MYSYSTEM
Type Option, press Enter
2=Change, 4=Delete, 5=Display TEMA Log, 14=Start, 15=End
Option
Agent for MQ Manager...
MYSYSTEM
MQITMISDE1
Suffix
Status
00001 Not Started
00002 Started
On this dialog, multiple instances of WebSphere MQ Monitoring can be listed.
These instances on an i5/OS system are differentiated by a unique 5-character
numeric suffix. The first instance Added is automatically assigned suffix 00001,
the second instance Added is automatically assigned suffix 00002, and so on.
The files associated with each instance are also automatically suffixed. For
example, the monitoring file for each instance is named in the form: MQnnnnn
where nnnnn is the automatically assigned 5-character numeric suffix.
3. Type 2 in the Option column next to the instance whose monitoring file you
want to change.
The dialog for changing WebSphere MQ Monitoring Agent displays.
4. Press F8 to change the monitoring file associated with the agent. An editing
dialog opens.
5. Insert, delete, or modify monitoring option commands, as your site requires.
Adhere to these editing rules:
v To continue a command onto the next line, end the current line with a
hyphen (“-”).
v Parameters you set when grouping objects are effective for all the objects in
the group.
v override parameters for an object in a group by explicitly defining
parameters for that object.
6. When you have finished customizing the monitoring file, press F3 to save your
changes and exit. Press F3 twice more to exit the interface.
7. Verify that the queue manager and its command server are running.
8. Restart the agent for your changes to take effect.
Customization of WebSphere MQ Monitoring is complete.
108
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Creating multiple instances of the WebSphere MQ Monitoring
agent (optional)
If you are configuring multiple instances of WebSphere MQ Monitoring, perform
the following steps. The first instance is automatically assigned suffix 00001, the
second instance is automatically assigned suffix 00002, and so on.
1. From an i5/OS system command line enter this command
WRKOMAMQ
The Add OMEGAMON Agent for WebSphere MQ dialog is displayed.
(If this is not the first access, a different dialog is displayed; press F6 to display
the Add OMEGAMON Agent for WebSphere MQ dialog.)
2. Enter the name of the Queue Manager that this agent will monitor, along with
a text description, and press “Enter”.
The configure TEMA (CFGOMAMQ) dialog is displayed.
3. Enter your site’s values for the displayed parameters using the guidelines
below.
Table 12. Parameters for The configure TEMA(CFGOMAMQ) Dialog
Parameter
Description
TEMS SNA location
The SNA location of the Tivoli Enterprise Monitoring Server that
this agent will report to. If you will not use SNA, enter *NONE. If
the correct SNA location was previously defined, enter *SAME to
retrieve it. If you need to define a new SNA location (which can be
the Control Point Name or the remote location name) enter its
name (for example: S10B6322).
TEMS TCP/IP
address
The TCP/IP address. If you will not use TCP/IP, enter *NONE. If the
correct TCP/IP address was previously defined, enter *SAME to
retrieve it. If you need to define a different TCP/IP address, enter
it (for example: 129.0.132.45).
TEMS IP.PIPE
Address
If IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
must connect to the Tivoli Enterprise Monitoring Server through a
firewall, you must use IP.PIPE. Specify the IP.PIPE address. If you
will not use IP.PIPE, enter *NONE.
Secondary TEMS SNA The SNA location of a secondary Tivoli Enterprise Monitoring
location
Server that this agent will report to if it cannot communicate with
the primary Tivoli Enterprise Monitoring Server at startup.
Secondary TEMS IP
address
The TCP/IP address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
Secondary TEMS
IP.PIPE Address
The IP.PIPE address of the system where a secondary Tivoli
Enterprise Monitoring Server is. The agent will report to this Tivoli
Enterprise Monitoring Server if it cannot communicate with the
primary Tivoli Enterprise Monitoring Server at startup.
Partition Name
(Required only by sites with firewalls that use address translation.)
The name of the partition that this instance of WebSphere MQ
Monitoring agent is in (up to 32 alphanumeric characters).
Firewall in use
If WebSphere MQ Monitoring must connect to the Tivoli Enterprise
Monitoring Server through a firewall, enter *YES. If not, retain the
default of *NO.
Chapter 12. Configuring IBM Tivoli OMEGAMON XE for Messaging on i5/OS system
109
Table 12. Parameters for The configure TEMA(CFGOMAMQ) Dialog (continued)
Parameter
Description
TEMS TCP/IP port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses SNA or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter *SAME to retrieve it. If you need to specify a different
Tivoli Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
TEMS SNA port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
IP.PIPE, ignore this field. If the correct port address was previously
defined, enter *SAME to retrieve it. If you need to specify a different
Tivoli Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
TEMS IP.PIPE port
address
The listening port of the Tivoli Enterprise Monitoring Server that
this agent will report to (usually 1918). If your site uses TCP/IP or
SNA, ignore this field. If you need to specify a different Tivoli
Enterprise Monitoring Server port address, enter it (up to six
numeric characters).
Action user profile
The user authority under which user action must be administered.
Retain the default value of QAUTOMON to grant user system
operator authority.
SNA transaction
program
This prompt is displayed only if you entered a value (or *SAME) for
Tivoli Enterprise Monitoring Server SNA location. The name of the
SNA transaction program. IBM Suggests retaining the default value
of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or *SAME) for
SNA location. The name of the SNA transaction program library.
IBM Suggests retaining the default value of KMSCMS.
Transaction program
(backup)
This prompt is displayed only if you entered a value (or *SAME) for
Secondary Tivoli Enterprise Monitoring Server SNA location. The
name of the SNA transaction program. IBM Suggests retaining the
default value of KDTMSNAP.
Library
This prompt is displayed only if you entered a value (or *SAME) for
Secondary Tivoli Enterprise Monitoring Server SNA location. The
name of the SNA transaction program library. IBM Suggests
retaining the default value of KMSCMS.
4. Read the Options choices and Function Key choices available for each dialog to
determine which keys to press to save and exit the dialog.
If you are reconfiguring the agent, the changes will take effect the next time the
agent is started.
110
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 4. Deploying monitoring across your environment from a
central location
This part explains how to deploy monitoring agents from a central location, the
Tivoli Enterprise Monitoring Server.
© Copyright IBM Corp. 2005, 2009
111
112
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 13. Deploying monitoring across your environment
from a central location
With IBM Tivoli OMEGAMON XE for Messaging, you can deploy the following
agents remotely from a central location, the Tivoli Enterprise Monitoring Server:
v WebSphere MQ Monitoring agent
v WebSphere MQ Configuration agent
v WebSphere Message Broker Monitoring agent
Before you can remotely deploy IBM Tivoli OMEGAMON XE for Messaging
agents, identify the operating system where you want to deploy the agents and
ensure that the following requirements are filled in your monitoring environment:
v An OS agent is installed or deployed on the computer where you want to
remotely deploy the agents. For example, if you want to deploy the agents on
the computer where the Windows operating system is running, you must have
the monitoring agent for Windows OS installed on that computer. For
information about how to install the OS agent, see IBM Tivoli Monitoring:
Installation and Setup Guide.
v The agent depot is populated on the Tivoli Enterprise Monitoring Server from
which you deploy agents and maintenance packages across your environment.
For example, if you want to deploy the WebSphere MQ Configuration agent,
you must have the agent depot for WebSphere MQ Configuration populated on
the Tivoli Enterprise Monitoring Server. For detailed information about how to
populate the agent depot, see “Populating your agent depot.”
Tip: If your monitoring environment includes multiple Tivoli Enterprise
Monitoring Servers (a hub Tivoli Enterprise Monitoring Server and multiple
remote Tivoli Enterprise Monitoring Servers), you can put your agent depot
in a central location, such as a shared file system, and access the depot from
all of the Tivoli Enterprise Monitoring Servers. For information about how to
use one agent depot for all the Tivoli Enterprise Monitoring Servers in your
monitoring environment, see “Sharing an agent depot across your
environment” on page 117.
Populating your agent depot
The agent depot is an installation directory on the Tivoli Enterprise Monitoring
Server from which you deploy agents and maintenance packages across your
environment. Before you can deploy any agents from a Tivoli Enterprise
Monitoring Server, you must first populate the agent depot with bundles. A bundle
is the agent installation image and any prerequisites.
When you add a bundle to the agent depot, you need to add the bundle that
supports the operating system to which you want to deploy the agent. Because
IBM Tivoli OMEGAMON XE for Messaging provides different CDs for each
platform type (for example, Windows, AIX and Solaris, HP-UX, Linux systems),
you need to add the bundle from the specific platform CD. For example, if you
want to deploy a WebSphere MQ Monitoring agent to a computer running HP-UX,
add the HP-UX-specific agent bundle to the depot. If your depot directory is on a
© Copyright IBM Corp. 2005, 2009
113
Windows system and you want to deploy a WebSphere MQ Monitoring agent to
HP-UX, load the HP-UX bundle from the IBM Tivoli OMEGAMON XE for
Messaging installation CD for HP-UX.
You can have an agent depot on each Tivoli Enterprise Monitoring Server in your
environment or share an agent depot, as described in “Sharing an agent depot
across your environment” on page 117. If you choose to have an agent depot for
each Tivoli Enterprise Monitoring Server, you can customize the agent depot based
on the types of agents that you want to deploy and manage from that Tivoli
Enterprise Monitoring Server. For example, if you have a Tivoli Enterprise
Monitoring Server that is dedicated to monitoring the WebSphere MQ Monitoring
agents in your environment, populate the agent depot with bundles for WebSphere
MQ Monitoring agents.
Exception: Agent depots cannot be populated on the Tivoli Enterprise Monitoring
Server that is running on z/OS or i5/OS systems.
There are two ways to populate the agent depot:
v If you are populating your agent depot with bundles for the same operating
system as the Tivoli Enterprise Monitoring Server, you can use the installation
image of IBM Tivoli OMEGAMON XE for Messaging to populate your agent
depot. For example, you can use the installation image for Windows to add the
bundle for a Windows agent to a Tivoli Enterprise Monitoring Server running on
a Windows system, but you cannot use the installation image for Linux to add
the bundle for a Linux agent to a Tivoli Enterprise Monitoring Server running
on a Windows system. For instructions about how to use the installation image
to populate the agent depot, see “Populating the agent depot from the
installation image”
v If you want to add agent bundles for an operating system that is different from
the one on which the Tivoli Enterprise Monitoring Server is running, use the
tacmd addBundles command. For instructions about how to use the use the
tacmd addBundles command to populate the agent depot, see “Populating the
agent depot with the tacmd addBundles command” on page 116
By default, the agent depot is located in the install_dir\CMS\depot directory on
Windows systems and install_dir/tables/tems_name/depot directory on UNIX and
Linux systems, where install_dir is the installation directory for IBM Tivoli
Monitoring, and tems_name is the name of the Tivoli Enterprise Monitoring Server.
The tacmd addBundles command puts the agent bundle in that location unless
another location is defined in the configuration file of Tivoli Enterprise Monitoring
Server for the DEPOTHOME variable. You can also change this location before
populating the agent depot, see “Changing the agent depot location” on page 117.
Populating the agent depot from the installation image
Use the following instructions to populate your agent depot from the installation
image:
v “Windows systems: Populating the agent depot during installation” on page 115
v “UNIX and Linux systems: Populating the agent depot during installation” on
page 115
You can use the installation image to populate your agent depot only when you
are populating your agent depot with bundles for the same operating system as
the Tivoli Enterprise Monitoring Server. For example, you can use the Windows
installation image to add the bundle for a Windows agent to a Tivoli Enterprise
114
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Monitoring Server running on a Windows system, but you cannot use the Linux
installation image to add the bundle for a Linux agent to a Tivoli Enterprise
Monitoring Server running on a Windows system. If you want to add agent
bundles for an operating system that is different from the one on which the Tivoli
Enterprise Monitoring Server is running, use the tacmd addBundles command, as
described in “Populating the agent depot with the tacmd addBundles command”
on page 116.
Windows systems: Populating the agent depot during installation
Perform the following steps to populate the agent depot from the Windows
installation image:
1. Double-click the setup.exe file in the \Windows subdirectory of the installation
image.
2. Select Modify on the Welcome window and click Next. The following message
is displayed:
The features you have installed on the system are selected in the following
panel.
Select a new item to install it.
Clear an item to remove it.
3. Click OK.
4. Click Next on the Add or Remove Features window without making any
changes. (Do not clear any selected items because this removes them from the
computer.)
5. On the Agent Deployment window, select the agents whose bundles you want
to add to the depot and click Next.
6. Review the installation summary and Click Next to begin the installation. A
message is displayed stating that you will not be able to cancel the installation
or upgrade after this point.
7. Click OK to continue. After the bundles of the agents are added to the agent
depot, a configuration window called the Setup Type window is displayed.
8. Clear all selected components. You have already configured all components on
this computer and do not need to reconfigure any now. Click Next.
9. Click Finish to complete the installation.
UNIX and Linux systems: Populating the agent depot during
installation
Perform the following steps to populate the agent depot from the UNIX or Linux
installation image:
1. Run the following command to create a temporary directory on the computer.
Make sure that the full path of the directory does not contain any spaces:
mkdir dir_name
2. Mount the installation CD for UNIX or Linux systems to the temporary
directory you just created.
3. Run the following commands:
cd dir_name
./install.sh
where dir_name is the temporary directory you just created.
4. When prompted for the IBM Tivoli Monitoring installation directory, press
Enter to accept the default (/opt/IBM/ITM). If the Tivoli Enterprise Monitoring
Server is installed in a different directory, type the full path to that directory
and press Enter.
Chapter 13. Deploying monitoring across your environment from a central location
115
5. If the directory you specified already exists, you are asked whether to use it.
Type 1 and press Enter.
6. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Exit install.
Type 2 and press Enter to start installation. The end user license agreement is
displayed.
7. Press Enter to read through the agreement.
8. Type 1 to accept the agreement and press Enter.
9. Type the number that corresponds to the agent or agents whose bundles you
want to add to the agent depot and press Enter. If you want to add more than
one agent, use a comma (,) to separate the numbers. To select all available
agents, type all.
You can select multiple agents with consecutive corresponding numbers by
typing the first and last numbers for the agents, separated by a hyphen (-).
For example, to add all of the agents between 8 and 12, type 8-12.
10. After specifying all the agents whose bundles you want to add to the agent
depot, type E and press Enter to exit.
Populating the agent depot with the tacmd addBundles
command
To populate the agent depot using the tacmd addBundles command, run the
following command:
tacmd addBundles [-i IMAGE_PATH]
[-t PRODUCT_CODE]
[-p OPERATING_SYSTEM]
[-v VERSION]
[-n]
[-f]
Remember: Before you issue the tacmd addBundles command, you must log into
the Tivoli Enterprise Monitoring Server where you will populate the
agent depot with the tacmd login command. The following command
logs into the Tivoli Enterprise Monitoring Server of which the host
name is L3D8296 with the user ID, administrator, the password,
mypassword, and a login expiration time of 1440 minutes.
tacmd login -s L3D8296 -u administrator -p mypassword -t 1440
For further information about this command, including parameter descriptions, see
IBM Tivoli Monitoring Installation and Setup Guide and IBM Tivoli Monitoring
Command Reference.
The following example copies every agent bundle, including its prerequisites into
the agent depot on a UNIX system computer from the installation media (cd
image) located at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix
The following example copies the agent bundle for the WebSphere MQ Monitoring
agent into the agent depot on a UNIX computer from the installation media (cd
image) located at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t mq
116
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
The following example copies the agent bundle for the WebSphere MQ Monitoring
agent into the agent depot on a Windows computer from the installation media (cd
image) located at D:\WINDOWS\Deploy:
tacmd addbundles -i D:\WINDOWS\Deploy -t mq
The following example copies the agent bundle for the WebSphere MQ Monitoring
agent that runs on the AIX version 5.1.3 into the agent depot on a UNIX computer
from the installation media (cd image) located at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t mq -p aix513
Changing the agent depot location
If you want to change the location of agent depot, perform the following steps
before you run the tacmd addBundles command:
1. Open the KBBENV Tivoli Enterprise Monitoring Server configuration file
located in the install_dir/CMS directory on Windows systems and the
install_dir/tables/tems_name directory on UNIX and Linux systems.
2. Locate the DEPOTHOME variable. If it does not exist, add it to the file.
3. Type the path to the directory that you want to use for the agent depot.
4. Save and close the file.
5. (UNIX and Linux systems only) Add the same variable and location to the
kbbenv.ini file located in install_dir/config directory.
Remember: If you do not add the variable to the kbbenv.ini file, it is deleted
from the KBBENV file the next time the Tivoli Enterprise
Monitoring Server is reconfigured.
Sharing an agent depot across your environment
If your monitoring environment includes multiple Tivoli Enterprise Monitoring
Servers (a hub Tivoli Enterprise Monitoring Server and remote Tivoli Enterprise
Monitoring Servers), you can put your agent depot in a central location, such as a
shared file system, and access the depot from all of the Tivoli Enterprise
Monitoring Servers.
After populating your agent depot with either of the methods described in
“Populating your agent depot” on page 113, perform the following steps to share
the agent depot:
1. Open the KBBENV configuration file located in the install_dir\CMS directory
on Windows systems and the install_dir/tables/tems_name directory on UNIX and
Linux systems.
2. Locate the DEPOTHOME variable. If it does not exist, add it to the file.
3. Type the path to the directory that you want to use for the agent depot.
4. Save and close the file.
5. (UNIX and Linux systems only) Add the same variable and location to the
kbbenv.ini file located in install_dir/config directory.
Remember: If you do not add the variable to the kbbenv.ini file, it is deleted
from the KBBENV file the next time the Tivoli Enterprise
Monitoring Server is reconfigured.
If you are using a Windows monitoring server connecting to a depot on another
Windows computer, you must set the service ID for the Windows monitoring
Chapter 13. Deploying monitoring across your environment from a central location
117
server to Administrator. Also, instead of specifying a mapped drive letter for the
path to the depot directory, use the UNC path (such as \\server\share).
Perform the following steps to change the service ID:
1. From the Control Panel, double-click Administrative Tools.
2. Double-click Services.
3. Right-click Tivoli Enterprise Monitoring Svcs and select Properties from the
menu.
4. On the Log On tab, select This Account.
5. Type Administrator in the This Account field.
6. Type the password for the administrator in the Password field. Confirm the
password by typing it again in the Confirm password field.
7. Click Enable.
Remember: If the Administrator user does not have Logon as a service right, you
are prompted to add it.
Deploying agents
You can deploy agents through the Tivoli Enterprise Portal or from the command
line. Before you attempt to deploy the agents of IBM Tivoli OMEGAMON XE for
Messaging on a computer, you must have already installed or deployed an OS
agent on that computer, and the OS agent must be running when you deploy the
agents on the computer.
Deploying through Tivoli Enterprise Portal
Perform the following steps to deploy an agent through the Tivoli Enterprise
Portal:
Important: Before you attempt to deploy the agents of IBM Tivoli OMEGAMON
XE for Messaging on a computer, you must have already installed or
deployed an OS agent on that computer, and the OS agent must be
running when you deploy the agents on the computer.
1. Log into the Tivoli Enterprise Portal.
2. In the Navigator view, navigate to the computer where you want to deploy the
agent.
Right-click the computer and click Add Managed System.
Select the agent that you want to deploy and click OK.
Complete the configuration fields required for the agent.
Click Finish.
If the computer where you are deploying the agent already has a version of
that agent installed, you can stop the deployment, add a new instance of the
agent, if possible, or reconfigure the existing agent.
8. If the agent is being deployed to a Windows system, restart the system to
which you are deploying it.
3.
4.
5.
6.
7.
After the agent has been deployed, it connects to the Tivoli Enterprise Monitoring
Server and then displayed in the Tivoli Enterprise Portal.
Remember: If you deployed the WebSphere Message Broker Monitoring agent on
UNIX or Linux system and want to use the CandleMonitor node, you
118
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
must create the required links manually. See “Installing the
CandleMonitor node (optional)” on page 93 for instructions.
Deploying through the command line
Use the following instructions to deploy a monitoring agent through the command
line:
v “UNIX and Linux systems: deploying through the command line”
v “Windows systems: deploying through the command line” on page 120
UNIX and Linux systems: deploying through the command
line
To deploy IBM Tivoli OMEGAMON XE for Messaging agents from a UNIX or
Linux computer using command line, perform the following steps:
1. Go to the install_dir/bin directory, where install_dir is the installation directory of
IBM Tivoli Monitoring (the default is /opt/IBM/ITM)
2. Run the following command to log into the Tivoli Enterprise Monitoring
Server:
./tacmd login -s hostname -u username -p password -t timeout
where hostname is the name of the host which hosts the Tivoli Enterprise
Monitoring Server, username is the name of the user to authenticate, password is
the password of the user to authenticate, and timeout is the maximum number
of minutes between invocations of tacmd before the user is denied access. For
example, the following command logs into the Tivoli Enterprise Monitoring
Server on pebble.ibm.com with the user ID, administrator, the password,
mypassword, and a login expiration time of 1440 minutes.
./tacmd login -s pebble.ibm.com -u administrator -p mypassword -t 1440
3. Run the following command to view a list of available computers to which you
can deploy agents:
./tacmd listSystems -t UX NT LZ
4. Run the following command to deploy a monitoring agent to a computer in
your environment:
./tacmd addsystem -t pc -n managed-os
where pc is the product code of the monitoring agent and managed-os is the
name of the computer where the OS agent is installed and the product code for
the OS agent. For example, stone.ibm.com:LZ is the name of the node on
computer stone.ibm.com, which has a Linux OS agent installed. section specifies
the name of the section containing the key value pair, name specifies the name
of the configuration property, and value specifies the property value.
Tip: Each agent bundle has its own unique configuration properties that you
need to provide in the tacmd addSystem command (using the -p option).
You can view the configuration parameters by running the tacmd
describeSystemType command. The following example shows the options
that are available to use with the tacmd addSystem command for the
WebSphere Message Broker Monitoring (product code qi) to be installed
on a remote Windows system (platform WINNT):
tacmd describeSystemType -t qi -p WINNT
After the agent is deployed on the computer, a message is displayed stating that
the product type on the computer is being managed.
Chapter 13. Deploying monitoring across your environment from a central location
119
Remember: If you are deploying the WebSphere Message Broker Monitoring agent
to a UNIX or Linux system and want to use the CandleMonitor node,
you must create the required links manually. See “Installing the
CandleMonitor node (optional)” on page 93 for instructions.
Tip: The status of the monitoring agent might be stopped after deployment. If that
is the case, start it manually.
Windows systems: deploying through the command line
To deploy IBM Tivoli OMEGAMON XE for Messaging agents from a Windows
computer using command line, perform the following steps:
1. Go to the install_dir\bin directory, where install_dir is the installation directory
of IBM Tivoli Monitoring (the default is C:\IBM\ITM)
2. Open a command prompt and run the following command to log into the
Tivoli Enterprise Monitoring Server:
tacmd login -s hostname -u username -p password -t timeout
where hostname is the name of the host which hosts the Tivoli Enterprise
Monitoring Server, username is the name of the user to authenticate, password is
the password of the user to authenticate, and timeout is the maximum number
of minutes between invocations of tacmd before the user is denied access. For
example, the following command logs into the Tivoli Enterprise Monitoring
Server on pebble.ibm.com with the user ID, administrator, the password,
mypassword, and a login expiration time of 1440 minutes.
tacmd login -s pebble.ibm.com -u administrator -p mypassword -t 1440
3. Run the following command to view a list of available computers to which you
can deploy agents:
tacmd listSystems
4. Run the following command to deploy a monitoring agent to a computer in
your environment:
tacmd addsystem -t pc -n managed-os -p section.name=value
where pc is the product code of the monitoring agent, managed-os is the name of
the computer where the OS agent is installed and the product code for the OS
agent (for example, stone.ibm.com:LZ is the name of the node on computer
stone.ibm.com, which has a Linux OS agent installed),section specifies the name
of the section containing the key value pair, name specifies the name of the
configuration property, and value specifies the property value.
Tip: Each agent bundle has its own unique configuration properties that you
need to provide in the tacmd addSystem command (using the -p option).
You can view the configuration parameters by running the tacmd
describeSystemType command. The following example shows the options
that are available to use with the tacmd addSystem command for the
WebSphere Message Broker Monitoring (product code qi) to be installed
on a remote Windows system (platform WINNT):
tacmd describeSystemType -t qi -p WINNT
Tip: The status of the monitoring agent might be stopped after deployment. If that
is the case, start it manually.
120
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 5. Uninstalling IBM Tivoli OMEGAMON XE for Messaging
This part explains how to uninstall IBM Tivoli OMEGAMON XE for Messaging
from Windows system, Linux system, UNIX system and i5/OS system.
© Copyright IBM Corp. 2005, 2009
121
122
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Chapter 14. Uninstalling the components of IBM Tivoli
OMEGAMON XE for Messaging
Follow the instructions in the following sections to uninstall the components of
IBM Tivoli OMEGAMON XE for Messaging:
v “Uninstalling components on Windows system”
v “Uninstalling components on UNIX or Linux system” on page 125
v “Uninstalling components on i5/OS system” on page 126
v “Uninstalling remote deployment files (all systems)” on page 127
Uninstalling components on Windows system
If you want to uninstall a component from a Windows system, perform the
following steps.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Click Start → Settings → Control Panel.
Click Add or Remove Programs.
Select IBM Tivoli OMEGAMON XE for Messaging.
Click Change/Remove.
The Welcome window is displayed to let you modify or remove the program.
If you want to completely remove IBM Tivoli OMEGAMON XE for Messaging
and all of its features, select Remove. If you want to remove some of its
features, select Modify. Click Next.
If you selected Remove in step 5, you will be asked if you want to completely
remove the selected application and all of its features. Click OK. The
uninstallation process will start and remove IBM Tivoli OMEGAMON XE for
Messaging and all of its features. You do not need to perform the following
steps.
If you selected Modify in step 5, a message is displayed stating that on the
following panel, items that you have already installed are pre-selected,
selecting a new item installs that item, and deselecting an item uninstalls that
item. Click OK to proceed.
On the Add or Remove Features window, click the plus sign (+) next to each
main feature to expand the tree.
Clear the check boxes next to the names of components that you want to
uninstall, and click Next.
On the Agent Deployment window, clear the check boxes next to the agents to
remove the files for remote deployment.
11. On the Start Copying Files window, review the list of features or types of
support that will be removed. Click Back if you want to go back and change
any of the selections. When you are ready, click Next to begin uninstall.
12. A message is displayed stating that you will not be able to cancel the
installation or upgrade after this point. Click Yes to continue.
13. On the Setup Type window, clear the check boxes and click Next.
14. On the InstallShield Wizard Complete window, click Finish.
15. The Maintenance Complete window is displayed stating that InstallShield
Wizard has finished performing maintenance operations on IBM Tivoli
OMEGAMON XE for Messaging and reboot can be done at your earliest
convenience. Click Finish.
© Copyright IBM Corp. 2005, 2009
123
Now the uninstallation is complete.
Remember: If you are using DB2 as the WebSphere MQ configuration database,
then when you uninstall WebSphere MQ Configuration agent support
at the Tivoli Enterprise Monitoring Server, the database is not
removed. If you want to remove it, you must delete the RKCFAPLT
database manually (see your DB2 documentation for information
about deleting a database).
Silent uninstallation
For silent uninstallation, perform the following steps to remove IBM Tivoli
OMEGAMON XE for Messaging and all its components from a Windows system
computer :
1. Copy the silent.txt file from the OMEGAMON for Messaging CD to a
temporary directory (for example, c:\temp).
2. Uncomment the following lines in the silent.txt file to uninstall:
[ACTION TYPE]
UNINSTALLALL=Yes
[FEATURES]
KGLWICMA=Tivoli Enterprise Monitoring Agent Framework
KMCWICMS=WebSphere
KMCWIXEW=WebSphere
KMCWICNS=WebSphere
KMCWICMA=WebSphere
MQ
MQ
MQ
MQ
Configuration
Configuration
Configuration
Configuration
KMQWICMS=WebSphere
KMQWIXEW=WebSphere
KMQWICNS=WebSphere
KMQWICMA=WebSphere
MQ
MQ
MQ
MQ
Monitoring
Monitoring
Monitoring
Monitoring
KQIWICMS=WebSphere
KQIWIXEW=WebSphere
KQIWICNS=WebSphere
KQIWICMA=WebSphere
Message
Message
Message
Message
Agent Support
Agent Support
Agent Support
Agent
Broker
Broker
Broker
Broker
Agent Support
Agent Support
Agent Support
Agent
Monitoring
Monitoring
Monitoring
Monitoring
Agent Support
Agent Support
Agent Support
Agent
You can specify the products to uninstall in the [FEATURES] section.
For example, uncomment the following lines if you want to uninstall the
WebSphere MQ Monitoring agent:
[ACTION TYPE]
UNINSTALLALL=Yes
[FEATURES]
KMQWICMS=WebSphere
KMQWIXEW=WebSphere
KMQWICNS=WebSphere
KMQWICMA=WebSphere
MQ
MQ
MQ
MQ
Monitoring
Monitoring
Monitoring
Monitoring
Agent Support
Agent Support
Agent Support
Agent
3. Open a DOS command prompt window.
4. Navigate to the directory that contains the OMEGAMON for Messaging
installation files (where the setup.exe file is).
5. Run the following command. You must specify the parameters in the same
order as listed below:
start /wait setup /z"/sfresponse_file_name" /s /f2"uninstallation_log_file_name"
Where
response_file_name
Specifies the full path of the response file (by default this file is named
silent.txt). This parameter cannot be omitted.
124
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
/s
Specifies that this is a silent uninstall. This causes no responses to be
displayed during uninstallation.
uninstallation_log_file_name
The full path of the file to which log information will be written during
the uninstallation process. This file will be created during
uninstallation, and any existing file with the same name is overwritten.
If this parameter is not specified, the Setup.log file in the same directory
as setup.iss will be used to write log information.
For example, if the response file is located in C:\temp\SILENT.TXT and you
want the log information to be written to the C:\temp\silent_setup.log directory,
enter the following command to start the silent uninstallation:
start /wait setup /z"/sfC:\temp\SILENT.TXT" /s /f2"C:\temp\silent_setup.log"
Now the silent uninstallation is complete and IBM Tivoli OMEGAMON XE for
Messaging and all its components are removed from the Windows system
computer.
Uninstalling components on UNIX or Linux system
Perform the following steps to uninstall a component from a UNIX or Linux
system computer:
1. If Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli
Enterprise Portal desktop client or any monitoring agents are running on the
computer where the component you want to uninstall is located, stop them.
2. From a command prompt, run the following command to change to the
appropriate /bin directory:
cd install_dir/bin
where install_dir is the installation directory for IBM Tivoli OMEGAMON XE
for Messaging.
3. Run the following command:
./uninstall.sh
A numbered list of product codes, architecture codes, version and release
numbers, and product titles is displayed for all installed products.
4. For each component that you want to uninstall, perform the following
procedure:
a. Type the number that represents the agent or component that you want to
uninstall and press Enter.
b. Type 1 (yes) when prompted to confirm your selection. The component is
removed.
5. If you do not want to uninstall any more components, type 99 and press Enter
to exit the uninstall program.
6. Navigate to the install_dir/config directory and delete the following files,
depending on which agent you are uninstalling:
v WebSphere MQ Monitoring: *mq*.cfg and mq.ini, where * represents any
combination of alphanumeric characters.
v WebSphere MQ Configuration: *mc*.cfg and mc.ini, where * represents any
combination of alphanumeric characters.
v WebSphere Message Broker Monitoring: *kqi*.xml and kqi.ini, where *
represents any combination of alphanumeric characters.
Chapter 14. Uninstalling the components of IBM Tivoli OMEGAMON XE for Messaging
125
When the uninstallation is complete, the results are written to uninstall-process.trc
that is located in the install_dir/logs directory, where install_dir is the IBM Tivoli
OMEGAMON XE for Messaging installation directory.
Important: If any processes belonging to the component being uninstalled are still
running during the uninstallation process, the uninstallation program
ends without removing the component. However, it is possible to
override this by using the -i option. In this case the component is
removed even while its process is still running. You can then stop these
processes manually.
Silent uninstallation
For silent uninstallation, run the following command to remove IBM Tivoli
OMEGAMON XE for Messaging and all its components from a UNIX or Linux
system, where product_code is a two-letter code for the product to be uninstalled,
and arch_code is the architecture code (such as aix513, sol286, hp11) for the product.
. /uninstall.sh [-f] [-i] [-h candle_directory] [product_code arch_code]
v The -f option forces delete, suppressing confirmation messages and prompts.
v The -i option ignores all running processes.
For example, the following command removes WebSphere MQ Configuration from
the Linux system:
./uninstall.sh mc li6263
Uninstalling components on i5/OS system
The following section explains how to uninstall the components from i5/OS
system.
Complete the following steps for each instance of the agent that you want to
uninstall.
1. Press F3 to exit from the menu to release the object lock.
2. From an i5/OS system command line, enter
DSPSFWRSC
3. Scroll down until you see the name of WebSphere MQ Monitoring/
Configuration in the Description column.
4. Record the licensed program ID for the component, which is on the left under
the column for Resource ID.
Licensed program ID __________________________________________
5. Press Enter to continue.
6. From an i5/OS system command line, enter the following command:
DLTLICPGM LICPGM(licpgm)
where licpgm is the licensed program ID that you recorded in step 4.
7. Optional: If you are uninstalling the WebSphere MQ Monitoring agent, perform
the following additional steps:
a. From an i5/OS system command line, enter the following command:
QSH
b. In QSHELL environment, run the following command:
rm -fr /home/kmq
Now the uninstallation is complete.
126
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Uninstalling remote deployment files (all systems)
Files that are required for using remote deployment features are installed at the
Tivoli Enterprise Monitoring Server when IBM Tivoli OMEGAMON XE for
Messaging application support is installed. To remove these files, run the tacmd
removeBundles command . See appendix E of the IBM Tivoli Monitoring:
Installation and Setup Guide for more information.
Chapter 14. Uninstalling the components of IBM Tivoli OMEGAMON XE for Messaging
127
128
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Part 6. Appendixes
© Copyright IBM Corp. 2005, 2009
129
130
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix A. Product codes
The following table lists product codes that identify the IBM Tivoli OMEGAMON
XE for Messaging components. Use these codes when running commands
Table 13. Product codes
Product
Code
WebSphere Message Broker Monitoring
qi
WebSphere MQ Configuration
mc
WebSphere MQ Monitoring
mq
© Copyright IBM Corp. 2005, 2009
131
132
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix B. Language codes
Table 14 lists the languages supported by the IBM Tivoli OMEGAMON XE for
Messaging, and their corresponding language codes.
Table 14. Language codes for the supported languages
Language
code
English
en_US
German
de_DE
Spanish
es_ES
French
fr_FR
Italian
it_IT
Japanese
ja_JP
Korean
ko_KR
Portuguese (Brazilian)
pt_BR
Simplified Chinese
zh_CN
Traditional Chinese
zh_TW
© Copyright IBM Corp. 2005, 2009
133
134
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix C. Architecture codes
IBM Tivoli uses abbreviations to represent the various operating system
architectures. The table below shows the most current listing of these
abbreviations.
This information can also be found in the following file on UNIX:
install_dir/registry/archdsc.tbl.
Table 15. Operating system architecture abbreviations
Abbreviation
OS Architecture
aix513
AIX v5.1 (32 bit)
aix516
AIX v5.1 (64 bit)
aix523
AIX v5.2 (32 bit)
aix526
AIX v5.2 (64 bit)
aix533
AIX v5.3 (32 bit)
aix536
AIX v5.3 (64 bit)
citrix
Citrix Metaframe
hp10
HP-UX v10.01/10.10
hp102
HP-UX v10.20
hp11
HP-UX v11
hp116
HP-UX v11 (64 bit)
li622
Linux Intel v2.2
li6223
Linux Intel v2.2 (32 bit)
li624
Linux Intel v2.4
li6242
Linux Intel v2.4 GCC 2.9.5 (32 bit)
li6243
Linux Intel v2.4 (32 bit)
li6245
Linux Intel v2.4 GCC 2.9.5 (64 bit)
li6246
Linux Intel v2.4 (64 bit)
li6262
Linux Intel v2.6 GCC 2.9.5 (32 bit)
li6263
Linux Intel v2.6 (32 bit)
li6265
Linux Intel v2.6 GCC 2.9.5 (64 bit)
li6266
Linux Intel v2.6 (64 bit)
ls322
Linux zSeries, 2.2 kernel
ls3223
Linux zSeries, v2.2 (32 bit)
ls3226
Linux zSeries, v2.2 (64 bit)
ls324
Linux zSeries, v2.4
ls3243
Linux zSeries, v2.4 (32 bit)
ls3246
Linux zSeries, v2.4 (64 bit)
ls3262
Linux S390 v2.6 GCC 2.9.5 (32 bit)
ls3263
Linux S390 v2.6 (32 bit)
ls3265
Linux S390 v2.6 GCC 2.9.5 (64 bit)
© Copyright IBM Corp. 2005, 2009
135
Table 15. Operating system architecture abbreviations (continued)
Abbreviation
136
OS Architecture
ls3266
Linux S390 v2.6 (64 bit)
osf1
Digital UNIX (prior to V5.0)
os390
OS/390® or z/OS
os400
OS/400® system
sol24
Solaris v2.4
sol25
Solaris v2.5
sol26
Solaris v2.6
sol273
Solaris v7 (32 bit)
sol276
Solaris v7 (64 bit)
sol283
Solaris v8 (32 bit)
sol286
Solaris v8 (64 bit)
sol293
Solaris v9 (32 bit)
sol296
Solaris v9 (64 bit)
sol503
Solaris v10 (32 bit)
sol506
Solaris v10 (64 bit)
sol603
Solaris v10 Opteron (32 bit)
sol606
Solaris v10 Opteron (64 bit)
tsf50
Tru64 v5.0
unix
UNIX
winnt
Windows 2000 and Windows 2003 Server
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix D. Supported operating systems
The following tables show which operating systems are supported for different
components of IBM Tivoli OMEGAMON XE for Messaging: WebSphere MQ
Monitoring, WebSphere MQ Configuration, and WebSphere Message Broker
Monitoring.
Table 16 shows the support for IBM Tivoli OMEGAMON XE for Messaging
components on Windows system computers.
Table 16. Supported Windows operating systems
Operating System
WebSphere MQ
Monitoring
WebSphere MQ
Configuration
WebSphere Message
Broker Monitoring
Windows 2000 Server
X
X
X
Windows 2000
Advanced Server
X
X
X
Windows XP
Professional (32 bit)1
X
X
X
Windows Server 2003
SE (32 bit)2
X
X
X
Windows Server 2003
EE (32 bit)2
X
X
X
Windows 2003 R2 SE
(32 bit)
X
X
X
Windows 2003 R2 EE
(32 bit)
X
X
X
Windows Server 2003
SE (64 bit)
X
X
Windows Server 2003
EE (64 bit)
X
X
Windows 2003 R2 SE
(64 bit)
X
X
Windows 2003 R2 EE
(64 bit)
X
X
Windows Server 2008
(Longhorn) (32 bit)
X
X
Windows Server 2008
(Longhorn) (64 bit)
X
X
Notes:
1. For the Windows XP operating systems, the Microsoft End User License
Agreement (EULA) does not license these operating systems to function as a
server. Tivoli products that function as a server on these operating systems are
supported for demonstration purposes only.
2. For Windows Server 2003: If you do not plan to deploy Service Pack 1 in your
environment at this time, you must download and install Microsoft Installer 3.1
(KB893803), which is available from the Microsoft Download Web site
(www.microsoft.com/downloads).
© Copyright IBM Corp. 2005, 2009
137
Table 17 shows the support for IBM Tivoli OMEGAMON XE for Messaging
components on UNIX system (non-Linux system), i5/OS, and z/OS system
computers.
Table 17. Supported UNIX, i5/OS and z/OS operating systems
Operating System
WebSphere MQ
Monitoring
WebSphere MQ
Configuration
WebSphere Message
Broker Monitoring
AIX V5.2 (32/64 bit)
X
X
X
AIX V5.3 (32/64 bit)
X
X
X
AIX V6.1 (32/64 bit)
X
X
X
Solaris V8 (SPARC)
X
X
X
Solaris V9 (SPARC)
X
X
X
Solaris V10 (SPARC)
X
X
X
Solaris V10 (x86-64)
X
X
X
HP-UX 11i v1
(B.11.11) on PA-RISC
X
X
X
HP-UX 11i v2
(B.11.23) (32/64 bit)
on PA-RISC
X
X
X
HP-UX 11i v2
(B.11.23) on Integrity
(Itanium)
X
X
X
HP-UX 11i v3 on
PA-RISC
X
X
X
HP-UX 11i v3 on
IA64 (Itanium)
X
X
X
i5/OS 5.3
X
X
i5/OS 5.4
X
X
i5/OS 6.1
X
X
z/OS 1.6
X
X
X
z/OS 1.7
X
X
X
z/OS 1.8
X
X
X
z/OS 1.9
X
X
X
Notes:
1. For information about installing IBM Tivoli OMEGAMON XE for Messaging on
a z/OS system, see the Program Directory that comes with it.
2. Remote deployment is not supported for HP-UX 11i v2 (B.11.23) on Integrity
(IA64).
Table 18 shows support for IBM Tivoli OMEGAMON XE for Messaging
components on Linux system computers.
Table 18. Supported Linux operating systems
Operating System
RedHat Enterprise
Linux 3 on Intel
32-bit
138
WebSphere MQ
Monitoring
WebSphere MQ
Configuration
X
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
X
WebSphere Message
Broker Monitoring
X
Table 18. Supported Linux operating systems (continued)
Operating System
WebSphere MQ
Monitoring
WebSphere MQ
Configuration
WebSphere Message
Broker Monitoring
RedHat Enterprise
Linux 3 on zSeries
X
X
X
RedHat Enterprise
Linux 4 on Intel
32-bit
X
X
X
RedHat Enterprise
Linux 4 on
AMD64/EM64T
64-bit
X
X
X
RedHat Enterprise
Linux 4 on zSeries
X
X
X
RedHat Enterprise
Linux 4 on iSeries
and pSeries
X
X
X
RedHat Enterprise
Linux 5 on Intel
32-bit
X
X
X
RedHat Enterprise
Linux 5 on
AMD64/EM64T
64-bit
X
X
X
RedHat Enterprise
Linux 5 on zSeries
X
X
X
RedHat Enterprise
Linux 5 on iSeries
and pSeries
X
X
X
SUSE Linux
Enterprise Server 8
Intel 32-bit
X
X
X
SUSE Linux
Enterprise Server 8
for zSeries
X
X
X
SUSE Linux
Enterprise Server 9
Intel 32-bit
X
X
X
SUSE Linux
Enterprise Server 9
on AMD64/EM64T
X
X
X
SUSE Linux
Enterprise Server 9
for zSeries
X
X
X
SUSE Linux
Enterprise Server 9
for iSeries and
pSeries
X
X
X
SUSE Linux
Enterprise Server 10
Intel 32-bit
X
X
X
Appendix D. Supported operating systems
139
Table 18. Supported Linux operating systems (continued)
Operating System
WebSphere MQ
Monitoring
WebSphere MQ
Configuration
WebSphere Message
Broker Monitoring
SUSE Linux
Enterprise Server 10
on AMD64/EM64T
X
X
X
SUSE Linux
Enterprise Server 10
for zSeries
X
X
X
SUSE Linux
Enterprise Server 10
for iSeries and
pSeries
X
X
X
Notes:
1. For RedHat Enterprise Linux 4 on AMD64/EM64T, you must install the
following libraries:
libstdc++.so.5
libstdc++.so.5(CXXABI_1.2)
libstdc++.so.5(GLIBCPP_3.2)
libstdc++-3.4.3-9.EL4
libgcc-3.4.4-2.i386.rpm
libstdc++-3.4.4-2.i386.rpm
compat-libstdc++-33-3.2.3-47.3.i386.rpm
compat-libstdc++-296-2.96-132.7.2.i386.rpm
2. For SUSE Linux Enterprise Server 9 on AMD64/EM64T, you must install the
compat-libstdc++-lsb-4.0.2_20050901-0.4.x86_64.rpm library. This library is
available in the SUSE Linux Enterprise Server 9 for AMD64 and Intel EM64T
Service Pack 3.
3. See Technote 1247529 for minor known problems and workarounds for SUSE
Linux Enterprise Server 10 on 64-bit operating systems.
4. Red Hat Linux 5 is supported only when operating system settings for SELinux
Security and Firewall Security are set to disabled.
5. If you are running WebSphere Message Broker Monitoring on RedHat
Enterprise Linux 5 for 32-bit Intel architectures, for best performance use
RedHat Enterprise Linux 5 Update 2.
140
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix E. Operating systems supported for Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server,
and Tivoli Enterprise Portal client
The following tables show which operating systems are supported for the IBM
Tivoli Monitoring components in IBM Tivoli Monitoring 6.2 FP1: Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
client.
Table 19 shows the support for Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal client on Windows system
computers.
Table 19. Supported Windows operating systems
Operating system
Tivoli Enterprise
Monitoring Server
Tivoli Enterprise
Portal Server
Tivoli Enterprise
Portal client1
Windows 2000 Server
X
X
X
Windows 2000
Advanced Server
X
X
X
Windows XP (32 bit)2
X
Windows Server 2003
SE (32 bit)3
X
X
X
Windows Server 2003
EE (32 bit)3
X
X
X
Windows 2003 R2 SE
(32 bit)
X
X
X
Windows 2003 R2 EE
(32 bit)
X
X
X
Windows Vista (32
bit)2
X
Windows Vista (64
bit)2
X
Notes:
1. The Tivoli Enterprise Portal desktop client is supported on marked platforms. However,
the browser client can be accessed only from Windows system computers running
Internet Explorer 6 or 7.
2. For the Windows XP, and Windows Vista operating systems, the Microsoft End User
License Agreement (EULA) does not license these operating systems to function as a
server. Tivoli products that function as a server on these operating systems are
supported for demonstration purposes only.
3. For Windows Server 2003: If you do not plan to deploy Service Pack 1 in your
environment at this time, you must download and install Microsoft Installer 3.1
(KB893803), which is available from the Microsoft Download Web site
(www.microsoft.com/downloads).
Table 20 on page 142 shows the support for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal client on UNIX system
(non-Linux system), i5/OS, and a z/OS system computers.
© Copyright IBM Corp. 2005, 2009
141
Table 20. Supported UNIX, i5/OS, and z/OS operating systems
Operating system
Tivoli Enterprise
Monitoring Server
Tivoli Enterprise
Portal Server
AIX V5.2 (32/64 bit)
X
AIX V5.3 (32/64 bit)
X
X
AIX V6.1 (32/64 bit)
X
X
Solaris V9 (SPARC)
(32/64 bit)
X
Solaris V10 (SPARC)
(32/64 bit)
X
Solaris V10 (x86-64)
(64 bit)
X
HP-UX 11i v2
(B.11.23) on Integrity
(IA64)
X
HP-UX 11i v3
(B.11.31) on Integrity
(IA64)
X
z/OS 1.6
X
z/OS 1.7
X
z/OS 1.8
X
z/OS 1.9
X
Tivoli Enterprise
Portal Client
Table 21 shows the support for Tivoli Enterprise Monitoring Server, Tivoli
Enterprise Portal Server, and Tivoli Enterprise Portal client on Linux system
computers.
Table 21. Supported Linux operating systems
Tivoli Enterprise
Monitoring Server
Tivoli Enterprise
Portal Server
Tivoli Enterprise
Portal Client
Asianux 2.0 for Intel
X
X
X
Red Flag 4.1 for Intel
X
X
X
Red Flag 5.1 for Intel
X
X
X
RedHat Enterprise
Linux 4 Intel 32-bit
X
X
X
RedHat Enterprise
Linux 4 on
AMD64/EM64T
64-bit
X
RedHat Enterprise
Linux 4 on z/Series
X
X
RedHat Enterprise
Linux 5 Intel 32-bit
X
X
RedHat Enterprise
Linux 5 on
AMD64/EM64T
X
RedHat Enterprise
Linux 5 on z/Series
X
Operating system
142
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
X
X
Table 21. Supported Linux operating systems (continued)
Tivoli Enterprise
Monitoring Server
Tivoli Enterprise
Portal Server
Tivoli Enterprise
Portal Client
SUSE Linux
Enterprise Server 9
Intel 32-bit
X
X
X
SUSE Linux
Enterprise Server 9
for z/Series
X
X
SUSE Linux
Enterprise Server 10
Intel 32-bit
X
X
SUSE Linux
Enterprise Server 10
for z/Series 64-bit
X
X
Operating system
X
Appendix E. Operating systems supported for TEMS, TEPS, and TEP client
143
144
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix F. UNIX Multi-Platform installation program
configuration files
This appendix discusses the configuration files used by the UNIX multi-platform
installation program. The configuration files can be modified to customize your
installation.
The UNIX system installer stores the information in external files that are logically
linked. With the linking of files, both basic and complex environments are
supported. A basic or default agent to Tivoli Enterprise Monitoring Server
configuration is presented when the agent configuration process is started. An
advanced configuration tab is available to configure more complex environments.
Configuration information is generated from and stored in the following file types:
v User-Input
v Template
v Custom-Configuration
Configuration File Types
This section provides the configuration file type information.
User-Input type
A User-Input file is generated automatically from information entered by the user,
whether in dialogs or at the command line. The user-input data is stored in a
database for reconfiguration. User-Input files are named according to the format:
kxxenv
where xx is the 2-letter product code; for example,
kmqenv
for WebSphere MQ Monitoring
For a list of codes for the components included in the IBM Tivoli OMEGAMON XE
for Messaging package, see Appendix A, “Product codes,” on page 131.
Template type
Template files are shipped in the ./config directory and installed in the
install_dir/config directory. These files contain all of the possible environment
variables for a product. Template files are edited manually, only when a variable
needs to be added permanently to the environment. Each variable value (for
example, install_dir), that will be replaced from the user-input file, needs to be
surrounded by the $ character. These variable values keywords are not reserved
words, but rather must match the keyword in the user-input file.
Template files are named according to the format:
{2-letter product code}.ini
Example: mq.ini for WebSphere MQ Monitoring
© Copyright IBM Corp. 2005, 2009
145
For a list of codes for the components included in the IBM Tivoli OMEGAMON XE
for Messaging package, see Appendix A, “Product codes,” on page 131.
The Template and User-Input files are used to generate a Custom-Configuration
file for a product.
Remember: Any customization done to the INI files is overwritten when the
components are upgraded or reinstalled. You must keep a backup of
any INI files you customize.
Custom-Configuration type
All variables (those surrounded by the dollar sign ($) ) in the Template file are
replaced with their values from the User-Input file to create a CustomConfiguration file. This file is generated automatically if it doesn’t already exist
during the configuration of an agent or Tivoli Enterprise Monitoring Server.
Custom-Configuration files can be edited by the user using the Advanced option in
the installer. These files are named according to the format:
Agent
{2-letter product code}.config
Example: mq.config for WebSphere MQ Monitoring
For a list of codes for the components included in the IBM Tivoli OMEGAMON XE
for Messaging package, see Appendix A, “Product codes,” on page 131.
Tivoli Enterprise Monitoring Server
Host_ms_cmsname.config
Additional configuration file support
To maintain configuration flexibility as implemented in the current installer, the
following files are also supported:
Table 22. Additional configuration files supported
File Name
146
Description
host_pc.config
Read by a specific product on a
specific system (host)
host_pc_opt.config
Read by a specific product on a
specific system using a specific
option (opt)
env.config
A configuration file that is used to
store any environment variables
applicable to all agents and the
Tivoli Enterprise Monitoring Server.
File is located in the
install_dir/config directory.
mq.cfg
Contains a default set of
monitoring options for WebSphere
MQ Monitoring.
kqi.xml
Default configuration file for
WebSphere Message Broker
Monitoring.
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Table 22. Additional configuration files supported (continued)
File Name
Description
<host_name>_mq_<opt>.cfg
Read by the WebSphere MQ
Monitoring on a specific system
using a specific set of monitoring
options (<opt>). If this file does not
already exist, it is created
automatically from mq.cfg when
running the itmcmd agent
command.
<host_name>_qi_<broker_name>_##_<agent_id>.xml
or <host_name>_qi_<agent_id>.xml
Read by the WebSphere Message
Broker Monitoring on a specific
system with a specific broker agent.
If this file does not already exist, it
is created automatically from
kqi.xml when running the itmcmd
agent command.
The order in which the files are read is from the most general to the most specific.
The pc.config is created during agent configuration and the Host_ms_cmsname.config
file is created during Tivoli Enterprise Monitoring Server configuration. The other
.config files can be created and edited manually.
Appendix F. UNIX Multi-Platform installation program configuration files
147
148
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Appendix G. Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. With the major
accessibility features in this product, users can do the following:
v Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.
In addition, the product documentation was modified to include the following
features to aid accessibility:
v All documentation is available in both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.
Navigating the interface using the keyboard
Standard shortcut and accelerator keys are used by the product and are
documented by the operating system. Refer to the documentation provided by
your operating system for more information.
Magnifying what is displayed on the screen
You can enlarge information on the product windows using facilities provided by
the operating systems on which the product is run. For example, in a Microsoft
Windows system environment, you can lower the resolution of the screen to
enlarge the font sizes of the text on the screen. Refer to the documentation
provided by your operating system for more information.
© Copyright IBM Corp. 2005, 2009
149
150
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Notices
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 document 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 document. The furnishing of this document does not grant 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 (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–0032, 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 might 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 publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication 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.
© Copyright IBM Corp. 2005, 2009
151
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 Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
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 document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program 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 contains 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.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at ″Copyright and trademark information″ at http://www.ibm.com/legal/
copytrade.shtml.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
152
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.
Other company, product, and service names may be trademarks or service marks
of others.
Notices
153
154
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Index
A
access control list (ACL) authorization 81, 91
accessibility xiii, 149
address translation 71
agent depot
populating 113
tacmd addBundles command 116
UNIX and Linux system 115
Windows system 115
sharing across your environment 117
agents 146
deleting old versions 68
deploying 118
initializing 53
installing 53
prerequisites 15
starting 97
starting and stopping 97, 98
stopping 97
agents’ default connection to Tivoli Enterprise Monitoring
Server
configuring 59
AIX
versions supported 17
application support
installing 23
installing at the Tivoli Enterprise Monitoring Server 23
UNIX or Linux 29
Windows 23
z/OS 30
installing at the Tivoli Enterprise Portal desktop client 42
Linux 43
Windows 42
installing at the Tivoli Enterprise Portal Server 34
UNIX or Linux 36
Windows 34
authorization
access control list (ACL) 81, 91
WebSphere Message Broker Monitoring 81
WebSphere Message Broker Monitoring agent 90
WebSphere MQ agent account 86, 95
B
books
see publications
xiii
C
CandleMonitor node
installation 83
installing 93
soft links 93
codes
architecture 135
language 133
product 131
command line
configuring the agent
starting an agent 98
command line (continued)
starting or stopping the agent 103, 107
stopping an agent 98
command-line installation 61
communications
prerequisites 13, 16
protocols 11
compiling
information about i5/OS system 70
components
starting 87
starting and stopping 97, 98
stopping 88
uninstalling
Windows 123
configuration database
DB2 15, 19
internal 15, 19
requirements 15
setting up
UNIX and Linux 46
windows 45
configuration file support
additional 146
configuration files
multi-platform 145
types 145
configuring 94, 101
agent from the command line 92
agent using Manage Tivoli Enterprise Monitoring
Services 92
agents’ default connection to Tivoli Enterprise Monitoring
Server 59
IBM Tivoli OMEGAMON XE for Messaging 79
i5/OS 101
UNIX and Linux 89
Windows 81
monitoring agent 86
WebSphere Message Broker Monitoring 81, 89
WebSphere Message Broker Monitoring agent 82
WebSphere MQ Configuration 84, 94
WebSphere MQ Configuration agent 84
WebSphere MQ Monitoring 85, 95, 104
connecting an agent to the Tivoli Enterprise Monitoring Server
configuring 65
conventions
typeface xiv
CPU prerequisite 14
custom-configuration
types 146
customizing
WebSphere MQ Monitoring 107
D
92
© Copyright IBM Corp. 2005, 2009
database, configuration
DB2 15, 19
internal 15, 19
requirements 15
Windows 45
155
DB2
configuration database 15, 19
link on Linux Intel 90
version required 15
Windows 45
default objects
creating 85, 95
deleting
old versions of agents 68
deploying
agents 118
monitoring across your environment from a central
location 111
through Tivoli Enterprise Portal 118
disk space prerequisite 14, 16
DNS 67
E
education
see Tivoli technical training
env.config file 146
environment variable
defining 91
environment variables
env.config file 146
template files 145
xiii
F
file permissions for agents
changing 97
firewall
address translation 71
application proxy 71
IP.PIPE 71
partition-naming strategy 71
sample scenarios 72
support for 71
Warehouse Proxy 71
fully qualified hostname 67
G
guidelines
11
H
hardware and software
prerequisites 13
HOSTS file 53
HP-UX
versions supported 17
I
i5/OS system
uninstalling components 126
i5/OS system CD-ROM
installing from 75
IBM OMEGAMON/400 agent
verifying not installed 70
IBM Tivoli Monitoring 3
IBM Tivoli OMEGAMON XE for Messaging
configuring 79
156
IBM Tivoli OMEGAMON XE for Messaging (continued)
i5/OS system 101
Windows 81, 89
configuring across a firewall 71
installing 73
i5/OS system 67
UNIX and Linux 61
Windows 7
uninstalling 121
IBM Tivoli OMEGAMON XE for Messaging components
starting 87
stopping 87
IBM Tivoli OMEGAMON XE for WebSphere MQ
Configuration
starting 103
verifying
installation and configuration 103
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
verifying
installation and configuration 106
information about i5/OS system
compiling 70
installation
application support 23
CandleMonitor node 83, 93
i5/OS 8
IBM Tivoli OMEGAMON XE for Messaging 73
i5/OS system 67
UNIX and Linux system 61
Windows 7, 53
InstallShield Wizard 53
language packs 51
UNIX or Linux 52
Windows 51
OMEGAMON XE for Messaging 59
planning 11
preparing 1, 11
roadmap 7
silent 57
UNIX or Linux 7
UNIX system 61
UNIX system command line 61
Windows 53
z/OS 8
installation on UNIX system 61
installer program
multi-platform configuration files 145
Windows 53
installing from i5/OS system CD-ROM 75
installing from PC CD-ROM 73
InstallShield Wizard
installing 53
interface
navigating using the keyboard 149
Internal database
UNIX system 19
Windows 15
IP.PIPE
firewall 71
itmcmd agent command 98
starting or stopping multiple agents 92
itmcmd manage command 98
K
Korn shell
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
16
L
language
primary
i5/OS 71
language packs
installing 51
UNIX or Linux 52
Windows 51
link to DB2 library
creating 90
Linux Intel
DB2 link 90
Lotus Notes server 53
M
Manage Tivoli Monitoring Services 82
starting and stopping components from 88, 97, 98
manuals
see publications xiii
memory prerequisite 14, 16
monitoring across your environment from a central location
deploying 111
monitoring agent
configuring 86
monitoring options
customizing 96
multi-platform configuration files 145
multiple agents
starting or stopping using the itmcmd agent command 92
multiple instances of the WebSphere MQ Configuration agent
creating 95
multiple instances of the WebSphere MQ Monitoring agent
creating 86, 96, 109
R
N
Network Interface Card
multiple 13
O
ODBC 15, 19
OMEGAMON XE for Messaging
installing 59
online publications
accessing xiii
operating systems
supported 137
supported for TEMS, TEPS, and TEP client
ordering publications xiii
P
parameters
customizing 92
partition-naming strategy
path names
qualified 12
PC CD-ROM
installing from 73
planning
installation 11
populating
agent depot 113
populating (continued)
tacmd addBundles command 116
UNIX and Linux system 115
Windows system 115
pre-installation tasks 53, 67
prerequisites
agents 15
communications 13, 16
CPU 14
disk space 14, 16
GSKit 16
i5/OS system 19
Korn shell command interpreter 16
memory 14, 16
TCP/IP 67
TCP/IP communications 13
UNIX system 12, 15
WebSphere Message Broker Monitoring 14, 17
WebSphere MQ agents 15, 18
Windows Service Packs 13
Windows system 13
procedure
compiling information about i5/OS system 70
configuring WebSphere MQ Configuration 101
configuring WebSphere MQ Monitoring 104
deleting old versions of agents 68
preparing WebSphere MQ environment 68
verifying installation and configuration 103, 106
verifying TCP/IP configuration 67
protocols, communications 11
publications
accessing online xiii
ordering xiii
related xi
71
141
requirements
AIX 17
configuration database 15
hardware
i5/OS system 19
UNIX and Linux 16
windows 14
i5/OS system 19
individual components 14, 17
software
i5/OS system 19
UNIX and Linux 16
windows 13
Solaris 16
UNIX system 12
Windows system 13
response file
creating 57
UNIX system 63
RKCFAPLT data source name 46
S
silent installation 57
creating response file 57
UNIX system 62
silent uninstallation
UNIX or Linux system 126
Windows 124
Index
157
SNA communications 13
soft links
CandleMonitor node 93
Solaris
versions supported 17
X11 support required 16
starting
from command line
WebSphere MQ Configuration 103
WebSphere MQ Monitoring 107
IBM Tivoli OMEGAMON XE for WebSphere MQ
Configuration 103
WebSphere MQ Monitoring 106
starting agents 97, 98
stopping
agents 97, 98
from command line
WebSphere MQ Configuration 104
WebSphere MQ Monitoring 107
Lotus Notes server 53
WebSphere MQ Configuration 103
T
TCP/IP
prerequisites 67
verifying
utilities installed 70
TCP/IP configuration
verifying 67
TCP/IP network services 13, 16
template files 145
Tivoli Enterprise Monitoring agents 4
Tivoli Enterprise Monitoring Server 4, 146
collecting information 12
fully qualified hostname 67
Tivoli Enterprise Portal 4
Tivoli Enterprise Portal desktop client
configuring 44
Tivoli Enterprise Portal Server 4
configuring on UNIX or Linux system 37
configuring using the command line 40
configuring using the GUI 37
Tivoli Information Center xiii
Tivoli technical training xiii
training, Tivoli technical xiii
typeface conventions xiv
U
UDB 15, 19
uninstallation 9
components on i5/OS 126
components on UNIX or Linux system 125
components on Windows system 123
silent
UNIX or Linux system 126
Windows 124
uninstalling
components
i5/OS 126
UNIX or Linux 125
Windows 123
IBM Tivoli OMEGAMON XE for Messaging 121
remote deployment files
all platforms 127
158
UNIX and Linux system
authorizing agents 90
CandleMonitor node installation 93
configuring IBM Tivoli OMEGAMON XE for
Messaging 89
configuring WebSphere Message Broker Monitoring
configuring WebSphere MQ Monitoring 95
UNIX or Linux system
uninstalling components 125
using 31
UNIX system
command-line installation procedure 61
installation procedure 61
prerequisites 12, 15
updating
IBM Tivoli Monitoring OS agent 68
updating IBM Tivoli Monitoring OS agent 68
upgrading 11
user authority level
checking 69
user IDs 81
authorizing 86
user-input
types 145
V
verifying
IBM OMEGAMON/400 agent, not installed 70
installation and configuration
IBM Tivoli OMEGAMON XE for WebSphere MQ
Configuration 103
IBM Tivoli OMEGAMON XE for WebSphere MQ
Monitoring 106
primary language of your i5/OS system 71
TCP/IP utilities installed 70
version of i5/OS system 70
version of i5/OS system
verifying 70
versions
AIX 17
HP-UX 17
Solaris 17
WebSphere MQ 15
Windows 14
W
Warehouse Proxy
firewall 71
WebSphere Message Broker Monitoring
authorization 81
configuring on UNIX and Linux system 89
configuring on Windows system 81
creating library links 89
prerequisites 14, 17
WebSphere Message Broker Monitoring agent
authorization 90
configuring 82
creating multiple instance 82
creating multiple instances 93
WebSphere MQ
events 69
WebSphere MQ agents, prerequisites 15, 18
WebSphere MQ Configuration 94, 101
configuring 101
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
89
WebSphere MQ Configuration (continued)
configuring on Windows systems 84
starting
from command line 103
stopping 103
from command line 104
WebSphere MQ Configuration agent
configuring 84
creating multiple instances 85, 95
WebSphere MQ Configuration Data Source Parameters
dialog 28
WebSphere MQ configuration database
setting up 45
WebSphere MQ environment
preparing 68
WebSphere MQ Monitoring
configuring 95, 104
UNIX and Linux system 95
configuring on Window systems 85
customizing 107
starting 106
from command line 107
stopping
from command line 107
WebSphere MQ Monitoring agent
creating multiple instances 86, 96, 109
WebSphere MQ, versions supported 15
what is displayed on the screen
magnifying 149
Windows
configuration database 45
installation procedure 53
Service Packs required 13
Windows system
authorizing agents 81
CandleMonitor node installation 83
configuring IBM Tivoli OMEGAMON XE for
Messaging 81
configuring WebSphere Message Broker Monitoring
configuring WebSphere MQ Configuration 84
configuring WebSphere MQ Monitoring 85
uninstalling components 123
user ID 81
using 30
versions supported 14
81
Index
159
160
IBM Tivoli OMEGAMON XE for Messaging: Installation and Setup Guide
Printed in USA
GI11-8074-01