Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1 Sg246768

7/31/2019 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1 Sg246768

1/338

ibm.com/redbooks

Implementing IBM TivoliOMEGAMON XE forWebSphere Business

Integration V1.1

Vasfi Gucer

Scott Wallace

Inampudi Aruna Kumar

Amina Shaheen

Jason Shamroski

Implement an end-to-end WBI

monitoring solution

Experiment with real life

scenarios

Learn troubleshooting

tips and best practices

Front cover
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/338


3/338

Implementing IBM Tivoli OMEGAMON XE forWebSphere Business Integration V1.1

July 2005

International Technical Support Organization

SG24-6768-00


4/338

Copyright International Business Machines Corporation 2005. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (July 2005)

This edition applies to OMEGAMON XE for WebSphere Business Integration V1.1.

Note: Before using this information and the product it supports, read the information inNotices on page xv.


5/338

Copyright IBM Corp. 2005. All rights reserved. iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 WebSphere MQ overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1 Queue managers and queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2 Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.3 Dead Letter Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.4 Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 WebSphere Business Integration Message Broker overview . . . . . . . . . . . 61.3 WebSphere InterChange Server overview . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 Why do I need to manage my middleware? . . . . . . . . . . . . . . . . . . . . . . . 10

1.5 OMEGAMON XE for WBI overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.6 OMEGAMON XE for WBI and ITIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.7 Our lab environment for the redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 2. OMEGAMON XE/DE Distributed Architecture . . . . . . . . . . . . . 21

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3 Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.4 Deployment scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.4.1 Simple deployment with no firewall . . . . . . . . . . . . . . . . . . . . . . . . . . 252.4.2 Simple deployment with firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.4.3 Complex deployment: CMS, RMS, and a firewall . . . . . . . . . . . . . . . 27

2.5 Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 3. Installation of the OMEGAMON infrastructure. . . . . . . . . . . . . 313.1 Planning for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1.1 Business requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1.2 Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


6/338

iv Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

3.1.3 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.1.4 Network requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2 Candle Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.2.1 Candle Management Server installation . . . . . . . . . . . . . . . . . . . . . . 37

3.2.2 CandleNet Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2.3 Modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.2.4 Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.2.5 Product prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.2.6 Starting the InstallShield Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.3 IBM Tivoli OMEGAMON DE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.3.1 Installing IBM Tivoli OMEGAMON DE . . . . . . . . . . . . . . . . . . . . . . . 54

3.4 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 4. Installation and configuration of WebSphere MQ Agents . . . 594.1 WebSphere MQ Agent installation and configuration . . . . . . . . . . . . . . . . 60

4.1.1 Installing the WebSphere MQ Agent on z/OS. . . . . . . . . . . . . . . . . . 604.1.2 Installing the WebSphere MQ Agent on UNIX . . . . . . . . . . . . . . . . . 804.1.3 Installing OMEGAMON WebSphere MQ Agent on Windows . . . . . . 864.1.4 Create additional instances of the agent. . . . . . . . . . . . . . . . . . . . . . 96

4.2 WebSphere MQ Configuration Agent configuration . . . . . . . . . . . . . . . . . 98

Chapter 5. WebSphere MQ Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 103

5.1 OMEGAMON XE for WebSphere MQ Configuration overview . . . . . . . . 1055.1.1 Centralized configuration information . . . . . . . . . . . . . . . . . . . . . . . 1055.1.2 A graphical representation of your configuration. . . . . . . . . . . . . . . 1065.1.3 Common prototype models for creating WebSphere MQ objects. . 1065.1.4 Managing resources from a business perspective . . . . . . . . . . . . . 1075.1.5 Keeping your actual and defined configurations in sync . . . . . . . . . 1075.1.6 Scheduling actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.1.7 Entering WebSphere MQ commands from the Defined View. . . . . 108

5.2 WebSphere MQ Configuration scenario . . . . . . . . . . . . . . . . . . . . . . . . . 109

5.2.1 Scheduling an action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.2.2 Connecting queue managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265.2.3 Creating resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

5.3 Audit Logging feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305.3.1 Audit Log reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.3.2 Accessing additional details reports . . . . . . . . . . . . . . . . . . . . . . . . 133

5.4 Backing up the configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . 1355.4.1 Restoring the configuration database . . . . . . . . . . . . . . . . . . . . . . . 137

Chapter 6. WebSphere MQ Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 1396.1 OMEGAMON XE for WebSphere MQ Monitoring overview . . . . . . . . . . 1406.2 WebSphere MQ Monitoring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

6.2.1 Editing WebSphere MQ Monitoring options . . . . . . . . . . . . . . . . . . 143


7/338

Contents v

6.2.2 Install WebSphere MQ Agent on z/OS . . . . . . . . . . . . . . . . . . . . . . 1446.3 Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626.4 Monitoring scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

6.4.1 WebSphere MQ queue manager monitoring . . . . . . . . . . . . . . . . . 166

6.4.2 WebSphere MQ queue monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 1746.4.3 SYSTEM.DEAD.LETTER alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826.4.4 WebSphere MQ channel monitoring . . . . . . . . . . . . . . . . . . . . . . . . 186

Chapter 7. WebSphere Integration Brokers Monitoring. . . . . . . . . . . . . . 1937.1 IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers . . . . . . 195

7.1.1 What does the agent do? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957.1.2 How does the agent work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

7.2 Planning for installation of the WebSphere Integration Brokers Monitoring

Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967.2.1 Prerequisite information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1977.2.2 Setting up the environment prior to installation . . . . . . . . . . . . . . . . 199

7.3 Installing the WebSphere Integration Brokers Monitoring Agent. . . . . . . 2007.3.1 Running the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

7.4 Installing the seed file on the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107.4.1 Seeding the CMS on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117.4.2 Seeding the CMS on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

7.5 Configuring the WebSphere Integration Brokers Monitoring Agent . . . . 214

7.5.1 Configuring the agent on Windows . . . . . . . . . . . . . . . . . . . . . . . . . 2147.5.2 Configuring the agent on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

7.6 The agents configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2227.7 Using situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2287.8 Using Take Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2317.9 Automating responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2357.10 Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2377.11 Monitoring scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2467.12 Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

7.12.1 Performance considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2507.12.2 Working with the CandleMonitor Node . . . . . . . . . . . . . . . . . . . . . 2517.12.3 Using the sample programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Chapter 8. WebSphere Interchange Server Monitoring . . . . . . . . . . . . . . 2558.1 OMEGAMON XE for WebSphere InterChange Server overview . . . . . . 256

8.1.1 What does OMEGAMON XE for WICS do? . . . . . . . . . . . . . . . . . . 2568.1.2 How does OMEGAMON XE for WICS help you? . . . . . . . . . . . . . . 256

8.1.3 How does OMEGAMON XE for WICS work? . . . . . . . . . . . . . . . . . 2578.1.4 OMEGAMON XE for WICS key features . . . . . . . . . . . . . . . . . . . . 2588.2 WebSphere InterChange Server configuration for monitoring . . . . . . . . 261

8.2.1 SNMP Agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262


8/338

vi Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

8.2.2 SNMP Configuration Manager configuration. . . . . . . . . . . . . . . . . . 2638.2.3 WebSphere InterChange Server Monitoring Agent configuration . . 266

8.3 Monitoring your integration systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2708.3.1 Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

8.3.2 Customizing the monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2738.3.3 Monitoring scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Chapter 9. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2839.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2849.2 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

9.2.1 Enabling trace settings for the CNPS . . . . . . . . . . . . . . . . . . . . . . . 2849.2.2 Enabling trace settings for the CMS . . . . . . . . . . . . . . . . . . . . . . . . 288

9.3 Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

9.3.1 CNPS and CNP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2899.3.2 CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2899.3.3 Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

9.4 Top issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2919.4.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2919.4.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2929.4.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

9.5 Miscellaneous tips and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2999.5.1 Changing the JRE version of the CNPS . . . . . . . . . . . . . . . . . . . . . 299

9.5.2 Using the digup tool on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3009.5.3 Mutex and shared memory cleanup . . . . . . . . . . . . . . . . . . . . . . . . 3019.5.4 WebSphere MQ Configuration problem determination . . . . . . . . . . 301

Appendix A. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

System requirements for downloading the Web material . . . . . . . . . . . . . 304How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307


9/338

Copyright IBM Corp. 2005. All rights reserved. vii

Figures

1-1 E-mail as an analogy of MQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2 MQ application to queue manager interface and message handling. . . . 31-3 MQ channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-4 MQ triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51-5 WBI message handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61-6 WBI publish and subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71-7 Relationship between WBI components . . . . . . . . . . . . . . . . . . . . . . . . . 81-8 Message Broker components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1-9 ITIL architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151-10 Our lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192-1 Simple deployment with no firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262-2 Simple deployment with firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272-3 Complex deployment: CMS, RMS and firewall . . . . . . . . . . . . . . . . . . . 283-1 CMS Welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383-2 Location menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393-3 Select features menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403-4 Confirm installation menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3-5 Setup Types menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423-6 Configure CMS menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433-7 Configure CMS communication menu . . . . . . . . . . . . . . . . . . . . . . . . . . 433-8 Configuration Defaults for Connecting to an CMS. . . . . . . . . . . . . . . . . 443-9 Configuration Defaults for Connecting to a CMS menu. . . . . . . . . . . . . 453-10 Manage Candle Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463-11 CandleNet Portal Component Installation . . . . . . . . . . . . . . . . . . . . . . . 493-12 Configure the installed products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3-13 CNP host information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513-14 CNPS data source configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523-15 CNP server configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533-16 Second CNP server configuration dialog box . . . . . . . . . . . . . . . . . . . . 543-17 Installing IBM Tivoli OMEGAMON DE . . . . . . . . . . . . . . . . . . . . . . . . . . 554-1 Creating a new dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624-2 Copy the datasets via ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634-3 Main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644-4 Set Up Work Environment menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4-5 Adding the runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664-6 Building the runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674-7 Configuring the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . . 684-8 Selecting the product component to configure. . . . . . . . . . . . . . . . . . . . 69


10/338

viii Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

4-9 Creating the runtime members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704-10 Specify the agent address space parameters . . . . . . . . . . . . . . . . . . . . 714-11 Specify TCP and NIC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724-12 Creating the runtime members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734-13 Configuration completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4-14 RUNTIME ENVIRONMENTS panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 754-15 OMEGAMON XE WBI component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774-16 Configuration setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784-17 CNP host information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794-18 Setup completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804-19 Installing CMA Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884-20 CMA Framework Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894-21 Connection to CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

4-22 Hub CMS connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904-23 Installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914-24 WebSphere MQ Agent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924-25 Configuration setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934-26 Connection to CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944-27 Hub CMS connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954-28 Installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964-29 Creating a WebSphere MQ Agent instance. . . . . . . . . . . . . . . . . . . . . . 974-30 WebSphere MQ Configuration Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 98

4-31 WebSphere MQ Configuration Agent-to-CMS communication . . . . . . . 994-32 Hub CMS connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004-33 Starting WebSphere MQ Configuration Agent . . . . . . . . . . . . . . . . . . . 1015-1 Example of Defined View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065-2 ABC company WebSphere MQ environment . . . . . . . . . . . . . . . . . . . 1105-3 Configuration Update mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125-4 Creating new Configured System Group . . . . . . . . . . . . . . . . . . . . . . . 113

5-5 Discovering existing queue managers. . . . . . . . . . . . . . . . . . . . . . . . . 114

5-6 Viewing configuration of discovered queue manager . . . . . . . . . . . . . 1155-7 Creating prototype for queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165-8 Viewing ProtoOrderEntryQ1 prototype . . . . . . . . . . . . . . . . . . . . . . . . 1175-9 Creating Resource Group prototype . . . . . . . . . . . . . . . . . . . . . . . . . . 1185-10 Linking queue resource prototypes to the resource group prototype. . 1195-11 Copying the resource group prototype to the defined queue manager 1205-12 Validate the queue manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

5-13 Update actual from define . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225-14 Scheduling an action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

5-15 Scheduling options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255-16 Connecting queue managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275-17 Creating local queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295-18 Viewing the queue object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130


11/338

Figures ix

5-19 Audit Log workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325-20 Audit log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335-21 Selecting log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345-22 Detailed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345-23 Backup configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6-1 Creating a new dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456-2 Copy the datasets via ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1466-3 Main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476-4 SET UP WORK ENVIRONMENT menu . . . . . . . . . . . . . . . . . . . . . . . 1486-5 Adding the runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496-6 Building the runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506-7 Configuring the runtime environment. . . . . . . . . . . . . . . . . . . . . . . . . . 1516-8 Selecting the product component to configure. . . . . . . . . . . . . . . . . . . 152

6-9 Specify the agent address space parameters . . . . . . . . . . . . . . . . . . . 1536-10 Specify TCP and NIC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1546-11 Creating the runtime members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556-12 Configuration completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566-13 RUNTIME ENVIRONMENTS menu. . . . . . . . . . . . . . . . . . . . . . . . . . . 1576-14 OMEGAMON XE WBI component. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1596-15 Configuration setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1606-16 CNP host information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616-17 Setup completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

6-18 WebSphere MQ Agent workspaces within the Navigator . . . . . . . . . . 1636-19 WebSphere queue manager problem alert . . . . . . . . . . . . . . . . . . . . . 1676-20 Alert acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1686-21 Setting alert acknowledgement timeframe. . . . . . . . . . . . . . . . . . . . . . 1696-22 Alert in Acknowledged status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706-23 Acknowledging z/OS WebSphere MQ queue manager alert . . . . . . . . 1716-24 Queue Manager Status workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

6-25 Queue Manager parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

6-26 Alert in Closed status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1746-27 WebSphere MQ queue full alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766-28 Queue Statistics workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1776-29 Queue Statistics details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786-30 Changing object attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796-31 Changing queue max depth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806-32 Queue Messages workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

6-33 Deleting messages from the queue . . . . . . . . . . . . . . . . . . . . . . . . . . . 1826-34 Alert acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

6-35 Dead Letter Queue Messages workspace. . . . . . . . . . . . . . . . . . . . . . 1846-36 Retry message delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856-37 Queue and queue manager names . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856-38 Successful completion message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186


12/338

x Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

6-39 WebSphere MQ channel stopped alert . . . . . . . . . . . . . . . . . . . . . . . . 1876-40 Channel Performance workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886-41 Channel Performance workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1896-42 Taking actions to restart the channel . . . . . . . . . . . . . . . . . . . . . . . . . . 1906-43 Restarting a channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

7-1 CandleMonitor Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1967-2 Welcome menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2017-3 Prerequisite information menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2027-4 Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2037-5 Agents to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2047-6 Agent configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2057-7 Agent connection to CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067-8 Agents CMS connection settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

7-9 Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087-10 Available operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2097-11 Agent selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2107-12 Agent Select Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117-13 Manage Candle Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2157-14 Change startup for Windows agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 2167-15 Configuring the UNIX agent from the command line . . . . . . . . . . . . . . 2197-16 Sample kqi.xml file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2237-17 Situation Editor with QI_Broker_Not_Started. . . . . . . . . . . . . . . . . . . . 230

7-18 Take Action by right-clicking the QI Broker . . . . . . . . . . . . . . . . . . . . . 2347-19 Take Action from right-clicking an Execution Group . . . . . . . . . . . . . . 2357-20 Reflex automation for QI_Broker_Not_Started situation . . . . . . . . . . . 2367-21 Agent workspaces within the Navigator . . . . . . . . . . . . . . . . . . . . . . . . 2387-22 Message Flow Statistics workspace . . . . . . . . . . . . . . . . . . . . . . . . . . 2457-23 Situation Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2478-1 WebSphere InterChange Server Monitoring architecture . . . . . . . . . . 258

8-2 SNMP Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

8-3 SNMP Configuration Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2648-4 Server Access in SNMP Configuration Manager. . . . . . . . . . . . . . . . . 2658-5 Manage Candle Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2668-6 Agent Advanced Configuration window . . . . . . . . . . . . . . . . . . . . . . . . 2678-7 Agent Advance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2678-8 Monitoring Agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2688-9 WebSphere InterChange Server Host . . . . . . . . . . . . . . . . . . . . . . . . . 268

8-10 WebSphere InterChange Server status in CNP. . . . . . . . . . . . . . . . . . 2698-11 Candle Net Portal workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

8-12 WebSphere InterChange Server workspaces in CNP . . . . . . . . . . . . . 2718-13 WebSphere InterChange Servers in CNP . . . . . . . . . . . . . . . . . . . . . . 2728-14 CNP workspace for WebSphere InterChange Server . . . . . . . . . . . . . 2738-15 CNP showing alterations in the Enterprise view . . . . . . . . . . . . . . . . . 276


13/338

Figures xi

8-16 WebSphere InterChange Server alert for MQ Connector . . . . . . . . . . 2778-17 WebSphere InterChange Server taking action on alert . . . . . . . . . . . . 2788-18 Take Action window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2798-19 Take Action window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2798-20 Edit Argument window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

8-21 Take Action window with arguments . . . . . . . . . . . . . . . . . . . . . . . . . . 2808-22 WICS Server with active connectors . . . . . . . . . . . . . . . . . . . . . . . . . . 2819-1 Accessing trace parameters for the CNPS . . . . . . . . . . . . . . . . . . . . . 2859-2 CNPS Trace Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2869-3 CT Services console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2879-4 Unable to connect to CNPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2979-5 Accessing Build CNPS Database menu . . . . . . . . . . . . . . . . . . . . . . . 2989-6 CNPS Data Source Configuration menu . . . . . . . . . . . . . . . . . . . . . . . 299


14/338

xii Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1


15/338

Copyright IBM Corp. 2005. All rights reserved. xiii

Tables

1-1 Proactive management offered by Tivoli Monitoring tools . . . . . . . . . . . 113-1 Supported operating systems and software. . . . . . . . . . . . . . . . . . . . . . 333-2 Communication protocol requirements . . . . . . . . . . . . . . . . . . . . . . . . . 343-3 Hardware requirements for CandleNet Portal Server . . . . . . . . . . . . . . 484-1 ./install.sh parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814-2 ./CandleConfig parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834-3 Prompts in response to CandleConfig execution. . . . . . . . . . . . . . . . . . 844-4 CandleAgent command parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6-1 WebSphere MQ workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1637-1 Supported operating environment for agent . . . . . . . . . . . . . . . . . . . . 1977-2 Attributes of kqi.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2247-3 Predefined alert based situations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2287-4 Take Actions provided by the product . . . . . . . . . . . . . . . . . . . . . . . . . 2317-5 Agent workspace information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2387-6 CandleMonitor node variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252


16/338

xiv Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1


17/338

Copyright IBM Corp. 2005. All rights reserved. xv

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. Consultyour 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 IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility 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 give you any license to these patents. You can send licenseinquiries, in writing, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisionsare inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS 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 disclaimerof express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto 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 atany time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements 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 onthe 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 themas 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 businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which thesample programs are written. These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming to IBM's applicationprogramming interfaces.


18/338

xvi Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

AIX 5LAIXCandle Command CenterCandle Management ServerCandle Management

WorkstationCandleCandleNet PortalCandleNetCICS

DB2 Universal DatabaseDB2EveryplaceHummingbirdIBMIMSMQIntegratorMQSeriesOMEGAMON Monitoring AgentOMEGAMON

OS/390OS/400RedbooksRedbooks (logo) TivoliWebSpherez/OSzSeries

The following terms are trademarks of other companies:

Java, J2EE, J2ME, J2SE, Solaris, Sun, Sun Microsystems, and all Java-based trademarks are trademarksof Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft Internet Explorer, Microsoft, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of IntelCorporation or its subsidiaries in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.


19/338

Copyright IBM Corp. 2005. All rights reserved. xvii

Preface

IBM Tivoli OMEGAMON XE for WebSphere Business Integration is a newproduct in Tivoli portfolio that manages WebSphere MQ, Message Broker, andInterChange Server environments from a single console. IBM TivoliOMEGAMON XE for WebSphere Business Integration supports distributed andmainframe systems and provides an end-to-end view across all systems. Itanalyzes application performance and identifies slowdowns and monitorsmessage rates, brokers, message flows, and sub-flows.

This IBM redbook covers the installation, configuration, and troubleshooting of

IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows,AIX, Linux, and z/OS platforms, with real life scenarios. OMEGAMONFramework architecture is also covered with typical deployment scenarios, bestpractices, and scalability considerations.

This redbook is an essential reading for IT Specialists who will implement IBMTivoli OMEGAMON XE for WebSphere Business Integration, or in generalOMEGAMON Framework in a customer environment.

The team that wrote this redbook

This redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization, Austin Center.

Vasfi Gucer is an IBM Certified Consultant IT Specialist working at the ITSOAustin Center. He worked with IBM Turkey for 10 years, and has been with theITSO since January 1999. He has more than 12 years of experience in systems

management, networking hardware, and distributed platform software. He hasworked on various Tivoli customer projects as a Systems Architect in Turkey andthe U.S. Vasfi is also a Certified Tivoli Consultant.

Scott Wallace is a Senior Software Engineer working in IBM Tivoli CustomerSupport at the Research Triangle Park, NC. He joined IBM in 1995 and has beenwith IBM Tivoli since 1998. He has over 13 years experience in systemsmanagement and distributed platform software. Scott is an IBM Tivoli CertifiedProfessional and is certified in ITIL.

Inampudi Aruna Kumar is a technical manager working in IBM India SoftwareLabs in Bangalore since 1999. He has more than eight years of experience intesting and management. He has his master's degree in Computer Science. He


20/338

xviii Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

is, in his current role, the leading WebSphere MQ Everyplace test and L3 teamtest strategist. He is a certified MQ specialist. His areas of expertise includeMessaging Middlewares, J2EE, J2ME, EAI, Testing, and distributedcomputing. He enjoys developing test automation solutions for distributed andpervasive systems.

Amina Shaheen is a Systems Management specialist working in IBM GlobalServices Division, Southbury, CT. She is an IBM Tivoli Certified Professional andhas extensive experience in IBM Tivoli Monitoring for WebSphere BusinessIntegration, including WebSphere MQ, WebSphere MQ Integrator, andWebSphere MQ InterChange Server. She has been leading Tivoli projects formonitoring for IBM Global and other Tivoli Commercial accounts. Her areas ofexpertise include Tivoli Framework, Distributed Monitoring, ITMFBI, and IBMTivoli Monitoring V5.1.2 and its PACs.

Jason Shamroski is Certified Tivoli Consultant working for Gulf BreezeSoftware. He has worked with IBM Tivoli and other Enterprise SystemsManagement products for almost nine years. He has co-authored two other IBMRedbooks: IBM Tivoli Monitoring Version 5.1: Advanced Resource Monitoring,SG24-5519 and IBM WebSphere Everyplace Server Service Provider andEnable Offerings: Enterprise Wireless Applications, SG24-6519. He has heldvarious team lead and consultant positions through his career, all of themfocused on systems management.

Thanks to the following people for their contributions to this project:

Budi Darmawan, Arzu Gucer, Wade WallaceInternational Technical Support Organization, Austin Center

Robert HaimowitzInternational Technical Support Organization, Raleigh Center

Bryan Anslow, Arun Biligir i, Arun Desai, Lisa Dycus, David Jackson, Anna

Grishchenko, Girish Kulkarni, Kay Maggi, Brian Petrini, Rebecca Poole, FergusStewart, Mark Verplaetse, Wendy Tung, Robin WileyIBM USA

Michael HoodIBM Australia

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbookdealing with specific products or solutions, while getting hands-on experience


21/338

Preface xix

with leading-edge technologies. You'll team with IBM technical professionals,Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. Asa bonus, you'll develop a network of contacts in IBM development labs, and

increase your productivity and marketability.

Find out more about the residency program, browse the residency index, andapply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your commentsabout this or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an e-mail to:

[email protected] Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. JN9B Building 90511501 Burnet RoadAustin, Texas 78758-3493
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


22/338

xx Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1


23/338

Copyright IBM Corp. 2005. All rights reserved. 1

Chapter 1. Introduction

In this chapter, we first provide a high-level technical overview of the WebSphereMessage Queuing (WMQ), WebSphere Business Integration Message Broker

(WBI), WebSphere InterChange Server (WICS), and IBM Tivoli OMEGAMON XEfor WebSphere Business Integration (also referred as OMEGAMON XE for WBI)products. Next, we discuss the benefits of managing your WMQ environment.Finally, we cover IBM Tivoli OMEGAMON XE for WebSphere BusinessIntegrations relationship to ITIL.

This chapter discusses the following:

1.1, WebSphere MQ overview on page 2

1.2, WebSphere Business Integration Message Broker overview on page 6

1.3, WebSphere InterChange Server overview on page 9

1.4, Why do I need to manage my middleware? on page 10

1.5, OMEGAMON XE for WBI overview on page 13

1.6, OMEGAMON XE for WBI and ITIL on page 13

1.7, Our lab environment for the redbook on page 17

1


24/338

2 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

1.1 WebSphere MQ overview

WebSphere MQ (MQ) is essentially a transport mechanism. It is a courier servicefor inter-application messages that does not require the communicatingapplications to be running at the same time, does not require them to be aware ofeach other's operating environment, and is communication protocol neutral.1

Consider this analogy: An e-mail system allows two people to send and receivemessages between different systems without the need for each person to besitting at their computer waiting for the message. It differs from a phone call (orIM) in that it is asynchronous; it uses astore and forwardmechanism, as shownin Figure 1-1.

Figure 1-1 E-mail as an analogy of MQ

In Figure 1-1, the person using the e-mail client attached to system A sends amessage that is stored by the e-mail server on their local system until it canestablish communication with the e-mail server on system B. Then the message

is forwarded and stored by the e-mail server on system B. When the user runningthe e-mail client attached to system B requests the message, it is retrieved fromthe storage on system B.

1.1.1 Queue managers and queues

Unlike point-to-point, application-to-application communication mechanisms(such as the Advanced Program to Program Communication Interface (APPC)),MQ uses queues to store messages temporarily as they are being passed from

one place to another. Each system that supports MQ has a queue manager1 Some of the material in this chapter is based on a white paper called IBM Tivoli OMEGAMON XE

for WebSphere Business Integration, written by Robin Wiley, and an OMEGAMON XE for WBIpresentation created by Mark Verplaetse.

A B

EMAIL SYSTEM

Store

RetrieveSendForward

Store


25/338

Chapter 1. Introduction 3

running, which handles the interface to the application program as well as theinterface with other queue managers in order to propagate messagessuccessfully. It is possible to have a network of several queue managers allcommunicating with each other and passing messages, from one to another, thatare destined for delivery to applications attached to other queue managers

elsewhere in the network. Figure 1-2 illustrates this concept.

Figure 1-2 MQ application to queue manager interface and message handling

In Figure 1-2, application A sends two messages: the first to queue X, and theother to queue Y. It does this by communicating with the queue manager on itslocal system (Queue Manager 1) using a mechanism called theMessage QueueInterface (MQI). There are MQI stubs available for most programming languageson most operating environments.

In this example, Queue Manager 1 passes both messages to Queue Manager 2,who recognizes the first message as being addressed to queue X, which is underits control and stores it there. Queue Manager 2 then resolves the address of thesecond message and routes it to Queue Manager 3, which stores it on queue Y.

Sometime later, applications B and C ask their respective queue managers toretrieve the messages from queues X and Y. In any MQ environment, the phrasesometime latercould mean milliseconds, minutes, hours, or days.

Note: MQ delivers messages to destination queues promptly, but theapplication may pick up the message whenever it is ready to do so.

Application

A

Application

C

Queue Manager1

Application

B

Queue X Queue Y

MQI MQI MQI

Queue Manager2

Queue Manager3


26/338


1.1.2 Channels

The way the queue managers communicate with each other is via channels,which are uni-directional communication links between systems. This isillustrated in Figure 1-3.

Figure 1-3 MQ channels

In Figure 1-3, queue manager QMA has some messages it has stored that isready to send to queue manager QMB. These messages are stored in a specialqueue called a Transmission Queue. A dedicated application called a SenderMessage Channel Agent (MCA) monitors the Transmission Queue and, when itfinds messages ready to be sent, initiates a communication session with a

partner Receiver MCA on the destination system.

Once the communication link is established, the Sender MCA reads themessages from the Transmission Queue and sends them via the communicationlink to the Receiver MCA, which stores the messages on the appropriateapplication queues and are ready for the receiving applications to get andprocess them.

1.1.3 Dead Letter Queue

In the above illustration, if the Receiver MCA was unable to successfully deliverthe message to the nominated application queue, it would place the messageinstead into aDead Letter Queue (DLQ). A DLQ is a special local queue set

QMA QMB

M

CA

M

CA

Application

Queues

Transmission

Queue

SENDER RECEIVER

Session

Initiation

APOLLO GEMINI


27/338


aside to receive undeliverable messages. The reasons why a message may notbe delivered include: The queue name is spelled incorrectly, the queue is full, themessage is too big for queue, and so on.

1.1.4 TriggeringWithin MQ, there is a mechanism that allows an application to be triggered whena message arrives on a nominated queue. The mechanism is illustrated inFigure 1-4.

Figure 1-4 MQ triggering

A sending application places a message onto a specific application queue thathas been defined as having trigger parameters. When this happens, the queue

manager constructs a separate trigger message that is placed on a separate,dedicatedInitiation Queue. A dedicated system application called a TriggerMonitoris watching the Initiation Queue and reads the Trigger Message, whichcontains the name of the application to be triggered, along with some parametersto be passed to the triggered application. The Trigger Monitor starts the triggeredapplication running, which in turn opens the original application queue and readsthe message from it that caused the trigger to occur.

Note: For more information on WebSphere MQ, you can refer to MQSeries

Primer, REDP-0021.

Queue

Manager

QM

Parameters

Application

Trigger

Monitor

TriggeredApplication

App Queue

Initiation Queue

MQ GET


28/338


1.2 WebSphere Business Integration Message Brokeroverview

At its simplest level, WebSphere Business Integration Message Brokerprocesses messages on MQ queues and provides the following functions:

Message transformation: This is the main purpose for which most people useWebSphere Business Integration Message Broker. It can restructure amessage from practically any format to any other. For example, you may havea COBOL application that sends messages with fixed-length fields and haveWebSphere Business Integration Message Broker reformat it into XML thatwill be processed by a Java application.

Content-based message routing: This feature allows WebSphere BusinessIntegration Message Broker to examine the contents of messages and make

decisions as to which queues to send them to.

Message transformation and content-based message routing functions aredescribed in Figure 1-5.

Figure 1-5 WBI message handling

Publish and subscribe: This is a message distribution architecture thatuncouples the sending and receiving applications. Essentially,Publisherapplications send messages with an attached Topic to WebSphere BusinessIntegration Message Broker, which then automatically distributes them to

Subscriber applications, which have previously advertised their interest incertain topics. The publish and subscribemechanism is described inFigure1-6 on page 7.

MQ: Message Delivery

Business Integrator: MessageManipulation

Translation, Calculation,Substitution, Reformatting

Business Integrator: MessageRouting

Content-Based Delivery,Exception Handling

Application

Application

Application

Application


29/338


Figure 1-6 WBI publish and subscribe

The WebSphere Business Integration Message Broker system is implementedas a series of Message Brokers running on different platforms. A group of relatedMessage Brokers are collectively called aDomain and are controlled by a singleConfiguration Manager, which maintains parameters and configuration status forall Brokers under its control. End users and administrators interface with the

Configuration Manager via a desktop Toolkit provided by Eclipse running on aWindows PC, as shown in Figure 1-7 on page 8.

MQ: Message Delivery

Business Integrator:

Publish/Subscribe Broker

Business Integrator:

Publish/Subscribe Broker

Publisher

Subscriber

Subscriber

Subscriber

Publisher


30/338


Figure 1-7 Relationship between WBI components

Functions to be performed by the Broker are coded asMessage Flows bydevelopers using the Eclipse Toolkit, then transferred to the ConfigurationManager, which in turn downloads the parameters to the Broker for execution.Message Flows are assigned to an Execution Group, which controls theallocation of resources to each Message Flow. The Broker interfaces with MQ toget and put messages from and to queues as required by the Message Flows.This is illustrated in Figure 1-8 on page 9.

BrokerDatabase

Broker

InputQueue

OutputQueue(s)

Config.Database

Configuration

Manager

Toolkit

(Eclipse)

Windows 2000/XPWindows 2000/XP

z/OS, Solaris, AIX, HP-UX,Windows 2000/XP, Linux,

LocalDataFiles


31/338


Figure 1-8 Message Broker components

1.3 WebSphere InterChange Server overviewInterChange Server provides a distributed infrastructure for solvingcross-application problems, including the capability to:

Move business information among diverse sources to perform businessexchanges across the Internet

Process and route business information among disparate applications in theenterprise environment

The IBM WebSphere InterChange Server system uses a central infrastructure(InterChange Server) and modular components in a hub-and-spoke design, asfollows:

Business-process logic resides in InterChange Server collaborations at thehub. InterChange Server collaborations are software modules that containlogic that describes a distributed business process. There are differentcollaborations for different fundamental business processes, for example, aContactManager collaboration or an InventoryMovement collaboration.

Collaborations coordinate the functionality of business processes fordisparate applications and enable data exchange between them.Collaborations are the hub; through them, data is exchanged in the form ofbusiness objects.

BrokerDatabase(Deployed)

Broker

Execution Group

Execution Group

Execution Group

MessageFlow

Message Dictionary

Queue Manager

ODBCConnection

InputQueue

OutputQueue(s)


32/338


Data is exchanged between the hub and the spokes in the form of businessobjects. Business objects are the messages used by the IBM WebSphereInterChange Server system for exchanging data.Data handlers are used totransform serial application data into business objects, and maps are usedbetween a business object that is structured for the data model of a specific

application and a business object that is generically structured for use bycollaborations at the hub.

Application and technology connectors supply connectivity to applications (orto Web servers or other programmatic entities) at the spokes. Connectors canbe configured to interact either within a network, or across the Internet andbeyond firewalls. Each connector consists of two parts: the connectorcontrollerand the connector agent. The connector controller interacts directlywith WebSphere InterChange Server collaboration objects and resides on aserver that has implemented the IBM WebSphere InterChange Server system

(the hub in a hub-and-spoke relationship). The connector agent interactsdirectly with an application, and can reside with that application on any server.A remote agent technology can be used to implement communicationbetween a connector controller at a hub site and an agent that resides atanother site across the Internet. Some connectors are designed to interactwith specific applications. Other connectors (such as the XML connector) aredesigned for interactions that conform to specific technology standards.

The Server Access Interface makes it possible for remote spoke sites that do

not implement WebSphere InterChange Server to use access clients, whichmake calls over the Internet to a hub site that does have InterChange Server.The Server Access Interface is a CORBA-compliant API that acceptssynchronous data transfers from either internally networked or externalsources. The data is then transformed into business objects that can bemanipulated by a collaboration. The Server Access Interface makes itpossible to receive calls from external entities, for example, from Webbrowsers at remote customer sites, that do not come through connectoragents, but instead come through Web servlets into the Server Access

Interface.

1.4 Why do I need to manage my middleware?

Given the increased complexity of e-business infrastructures, intelligentperformance and availability management tools are essential for proactiveidentification and resolution of IT problems before they impact businessperformance. These tools enable companies to cost effectively monitor individual

resource performance while simultaneously ensuring availability acrossheterogeneous operating environments. Ensuring peak performance andavailability helps companies meet and exceed both internal and external servicelevel agreements and reduce total cost of ownership.

B i i i l d d t lti ti it


33/338


Business processes are increasingly dependent on multi-tier compositeapplications that use business logic and data from multiple resources: Webservers, J2EE application servers, integration middleware, and existing systems.As we build new applications and connect to existing applications, transport andmediation across multiple systems must be monitored, configured, and managed

to ensure the best possible performing applications. These must be activelymanaged to support the On Demand Business. Using traditional tools, theseproblems are often not even identified until a customer complains.

As transactions move from the synchronous nature of the customer facingapplication to the asynchronous world of messaging and workflow, trackingbusiness transactions across these composite applications and managing thembecome even more difficult.

IBM Tivoli Intelligent Management software has simple goals to provide softwarethat runs your IT infrastructure so you have more time to run your business,deliver optimal ROI, and generate revenue. With Tivoli Software, IT expensesbecome IT investment.

We shall examine a simple scenario on how Tivoli Monitoring tools help inmanaging your middleware. Consider Table 1-1 a business infrastructure you aremanaging, and problem management with and without Tivoli Monitoring tools.

Table 1-1 Proactive management offered by Tivoli Monitoring tools

Process

step

How it typically works IT organization What Tivoli monitoring

solutions enable a client to do

Sense The help desk is bombardedwith calls that purchased itemsare not shipped after 30 days. ITstaff members are paged andemergency meetings are called.

Help Desk Monitoring tools proactivelyidentify the middleware hitches orslowdown in message flow, androute the problem to the correctsupport person.

Isolate In a meeting, the availablerepresentatives from thedifferent silos work to determinewhich assets are causing theproblem

IT operations team The support person uses resourceand transaction-level tools toidentify the asset where theproblem is occurring.


34/338


The proactive management of your business infrastructure helps in:

Minimizing down time of your business services

Efficient utilization of resources

Capacity planning for the on demand business environments, and theinventory of your business infrastructure.

Problem determination and isolation in a short amount of time

Develop, test, and deploy your middleware infrastructure

Diagnose The appropriate silo experts testthe specific assets that cause

the problem to determine whichsilo is responsible, (if theproblem falls in between silos,this step becomes moredifficult.). The isolate anddiagnose steps are repeateduntil the root cause is found

Network operationscenter

Databaseadministrators

Application serveradministrator

Applicationdevelopment team

Using interoperable tools anddetailed analysis capabilities, the

support person drills downseamlessly to pinpoint the rootcause.

Takeaction

The responsible silo expertdetermines, plans, andimplements a course of action toresolve the problem

Applicationdevelopment team

Serveradministrator

Still using the same console, thesupport person triggers anotherseamlessly integrated tool to takean automated, best practiceaction. Changes might includecreating more threads orprovisioning, configuring, anddeploying more server capacity. Ifthe support person lacks the skillsto resolve the problem, tools route

the problem to a domain expertand enable that expert to work onthe problem in the exact contextwhere the support person left off.

Evaluate If the problem does not go awayor if a new problem arises, thewhole process must berepeated.

IT operations team Integrated monitoring tools allowthe domain expert to instantly seehow well the results of the changesupport the companys businesspriorities. The expert can also

immediately drill down into andresolve other problems that arise.

Process

step

How it typically works IT organization What Tivoli monitoring

solutions enable a client to do

Monitoring and alerting options that can be customized to suite your needs


35/338


Monitoring and alerting options that can be customized to suite your needs

Do not forget that you cannot manage what you do not measure.

1.5 OMEGAMON XE for WBI overviewIBM Tivoli OMEGAMON XE for WebSphere Business Integration helps you tomanage and configure your WebSphere MQ, Message Broker, and InterChangeServer environments. These solutions provide the most comprehensive suite oftools to manage the performance, connectivity, and configuration of yourenvironment. This allows you to gain an understanding of your environment anddetermine when your applications are not performing properly. You will then beable to take corrective action to alleviate these problems.

IBM Tivoli Performance and Availability Management products provide thecentral nervous system for complicated business landscapes: they constantlygather information on hardware, software, and network devices, and, in manycases, cure problems before they actually occur. IBM Tivoli availability productsmonitor business at the component, business system, and enterprise levels. Thistechnology identifies critical problems as well as misleading symptoms, and theneither notifies support staff with the appropriate response, or automatically curesthe problems, which decreases operating costs and improves staff efficiency.

IBM Tivoli OMEGAMON XE for Business Integration monitors and manages theWebSphere MQ, WebSphere MQ Message Broker, and WebSphereInterChange Server environments. The out-of-the box capabilities of this productprovide auto-discovery and monitoring of these complex environments, providingcustomers with rapid time to value, ease of use, and improved product quality.Additionally, it identifies common problems and automates corrective actions bymonitoring key WebSphere MQ, WebSphere MQ Message Broker, andWebSphere InterChange Server metrics. It sends event notification and provides

data collection for real-time and historical data analysis, thus reducingadministration costs and maximizing return on investment with increasedefficiency of the IT staff.

1.6 OMEGAMON XE for WBI and ITIL

ITIL (IT Infrastructure Library) is the only comprehensive, non-proprietary sourceof service management best practices that is publicly available. It was originally

created by the UK Government, but has rapidly been adopted across the worldas the guidelines for best practices in the provision of IT Service.

The main focus of IT Service Management is divided into two main areas


36/338


The main focus of IT Service Management is divided into two main areas,Service Support and Service Delivery, and contains an integrated set ofwell-documented processes including, among others:

Service Support

Service Desk Incident Management

Problem Management

Change Management

Release Management

Configuration Management

Service Delivery

Service Level Management

Availability Management

Capacity Management

Financial Management for IT Services

IT Service Continuity Management

Figure 1-9 on page 15 shows the ITIL architecture.

Note: Service Desk is considered a function, not a process, in ITIL.


37/338


Figure 1-9 ITIL architecture

In recent years, it has become increasingly recognized that information is themost important strategic resource that any organization has to manage. Key tothe collection, analysis, production, and distribution of information within anorganization is the quality of the Information Communication Technology (ICT)systems and IT services provided to the business. It is essential that werecognize that ICT systems are crucial, strategic, and organizational assets and

therefore organizations must invest appropriate levels of resources into thesupport, delivery, and management of these critical IT services and the ICTsystems that underpin them. However, these aspects of IT are often overlookedor only superficially addressed within many organizations. The key issues facingmany of today's senior Business Managers and IT Managers are:

IT and business strategic planning

Integrating and aligning IT and business goals

Acquiring and retaining the right resources and skill sets

Implementing continuous improvement

Measuring IT organization effectiveness and efficiency

Reducing costs and the Total Cost of Ownership (TCO)


38/338


g p ( )

Achieving and demonstrating Value For Money (VFM) and Return onInvestment (ROI)

Demonstrating the business value of IT

Developing business and IT partnerships and relationships Improving project delivery success

Outsourcing, insourcing, and smart sourcing

Using IT to gain competitive advantage

Delivering the required, business justified IT services (that is, delivering whatis required, when required, and at an agreed cost)

Managing constant business and IT change

Following the sun and offshore operations

Demonstrating appropriate IT governance

The challenges for IT managers are to co-ordinate and work in partnership withthe business to deliver high quality IT services. This has to be achieved whilereducing the overall TCO and often increasing the frequency, complexity, andvolume of change. The main method of realizing this goal is the operation ofeffective processes and the provision of appropriate, value for money services.

To achieve this, the correct processes need to be developed and implementedwith in-built assessment and improvement mechanisms.

Tivoli OMEGAMON XE for WBI addresses specific areas in ServiceManagement. OMEGAMON for WBI address ITIL Services Management areasto help align IT with the business requirements, as shown in the followingsections.

Services Support

Tivoli OMEGAMON XE for WBI addresses can be used in the following ITILServices Support processes:

Problem Management: OMEGAMON for WBI provides for problem isolation inorder to turn incidents into known errors. The ability of OMEGAMON for WBIto provide the capabilities of high level monitoring and alerting, the ability todeep dive into specific WBI resources in order to understand where WMQand the Message Broker have problems, and the ability to automateresponses to fix issues before they become problems lead to effective

resolution of problems. Release Management: The WebSphere MQ Configuration tool that is part of

OMEGAMON for WBI will help define and deploy WebSphere MQconfigurations. The WMQ Configuration database will be able to make

changes to the Queue manager configuration, verify them, and then stage


39/338


them for deployment. The database will be backed up in case a restoration isnecessary.

Configuration Management: While not necessarily a component ofConfiguration Management, OMEGAMON for WBI can provide input to the

Configuration Management Database (CMDB) to inventory the QueueManagers and the objects associated with the Queue Managers, should thislevel of detail be required. This information will help feed information ChangeManagement.

Service DeliveryTivoli OMEGAMON XE for WBI addresses or can be used in the following ITILServices Delivery processes:

Service Level Management: It is important to retrieve information fromOMEGAMON for WBI as input into the Service Level Agreement (SLA).Information here will determine a baseline for response times and messagethroughput to help draw up the SLA.

Availability Management: It is important to understand the availability ofmessaging components and message brokers. OMEGAMON for WBIconstantly monitors the availability of these components that will feed into theAvailability Management function.

Capacity Management: When monitoring messaging components, it isimportant to understand the throughput of individual messaging components.This will help us to draw baselines for normal operations and then help planfor peak periods. Trending these results and planning growth based on thisinput will help determine capacity for the future, and plan for this capacity tobe available.

IT Service Continuity Management: OMEGAMON for WBI provides input intothe disaster planning process by creating a centrally located backup of theWMQ configuration of any Queue Manager in the enterprise. This will

facilitate in restoring service for applications affected by service outages.

1.7 Our lab environment for the redbook

For the purposes of this redbook, we installed the following products to managethrough OMEGAMON XE for WBI:

On Windows:

WebSphere MQ

WebSphere Business Integration Message Broker

WebSphere InterChange Server


40/338


On AIX:

WebSphere MQ


On Linux:

WebSphere MQ


On z/OS:

WebSphere MQ

Our OMEGAMON XE for WBI environment consist of a CMS server on a

Windows 2003 system, a CNP server on a Windows 2000 system, and severalagents on Windows, AIX, Linux, and z/OS platforms. Figure 1-10 on page 19shows our environment and various product components installed in thisenvironment.


41/338


Figure 1-10 Our lab environment

In this redbook, we will not cover the installation of WebSphere MQ, WebSphereBusiness Integration Message Broker, and WebSphere InterChange Serverproducts, since we assume that readers are familiar with these products.

Refer to the following sections of the book for installation and configuration of thevarious OMEGAMON XE for WBI components shown in Figure 1-10:

Chapter 3, Installation of the OMEGAMON infrastructure on page 31 for theOMEGAMON Framework components.

4.1, WebSphere MQ Agent installation and configuration on page 60 for theOMEGAMON XE for WBI MQ Agents (both Monitoring and ConfigurationAgents).

7.3, Installing the WebSphere Integration Brokers Monitoring Agent onpage 200 for the OMEGAMON XE for WBI Message Broker Agents.

Candle Management Server

Windows 2003

(helsinki-3.6 GB RAM, 3.1 GHZ)

DB2Candle Portal Server

Windows 2000(nice-1.5 GB RAM, 3 GHZ)

DB2

Linux Redhat 2.1

(edinburg 1 GB RAM,1.8 GHZ)

Windows 2000

(florence-1.5 GB RAM, 3 GHZ)

z/OS

Server

(SC58)AIX 5.2

(milan-F80,1 GB RAM)

DB2 8.1 + FP2

MQ 5.3 + FP05

MQ Message Broker 5.0.1

OMEGAMON MQ monitoring agent

OMEGAMON MQ configuration agent

OMEGAMON Message Broker agent

MQ 5.3 for z/OS

OMEGAMON MQ monitor ing agent


DB2 8.1 + FP2

MQ 5.3 + FP05

MQ Message Broker 5.0.1



OMEGAMON Message Broker agent

MQ 5.3 + FP05



DB2 8.1 + FP4

MQ 5.3 + FP10

WebSphere InterChange Server 4.3 + FP01

Windows 2000 Professional

(kcyb72b 1.0 GB RAM 3 GHz)

DB2 8.1 + FP4

MQ 5.3 + FP05



WS Interchange Server, DataSource agent

ETHERNET

DB2

DB2

DB2 8.1 + FP4MQ 5.3 + FP05MQ Message Broker 5.0.1OMEGAMON MQ monitoring agentOMEGAMON MQ configuration agent

OMEGAMON Message Broker agentOMEGAMON FrameworkWS Interchange Server and agent

DB2

Windows 2000

(copenhagen1 GB,1.8 GHz)

DB2

DB2 8.1 + FP4

MQ 5.3 + FP05



8.2, WebSphere InterChange Server configuration for monitoring onpage 261 for the WebSphere InterChange Server Monitoring and SNMP


42/338


page 261 for the WebSphere InterChange Server Monitoring and SNMPAgents.

Also, Chapter 2, OMEGAMON XE/DE Distributed Architecture on page 21provides architecture and scalability information for the OMEGAMONFramework.


43/338

Copyright IBM Corp. 2005. All rights reserved. 21

Chapter 2. OMEGAMON XE/DEDistributed Architecture

This chapter discusses the deployment of an OMEGAMON XE/DE architecturein a Distributed Computing environment. It is important to know the bestpractices for deploying an OMEGAMON XE/DE architecture to successfullyimplement a IBM Tivoli OMEGAMON XE for WebSphere Business IntegrationV1.1 solution in your environment.

The following are covered in this chapter:

2.1, Overview on page 22.

2.2, Terminology on page 23

2.3, Communications on page 24

2.4, Deployment scenarios on page 25

2.5, Scalability on page 29

2

2.1 Overview


44/338


While this redbook focuses on OMEGAMON for WebSphere BusinessIntegration, we felt it necessary to include an overview of the OMEGAMONarchitecture. This chapter will discuss the deployment of an OMEGAMON XE/DE

architecture in Distributed Computing environment. We will discuss theinstallation and placement of the Candle Management Server (CMS), CandleNet Portal, database integration, Candle's built-in Web server, and how tomanage devices in DMZs through corporate firewalls.

Let us clarify one thing at this time: the OMEGAMON designations of XE and DEare simple. The OMEGAMON XE product is the base product that everyonestarts with when they install a Candle Management Server. The OMEGAMONDE allows the defining of Business views rather than just Physical views as given

in XE. It also allows more combination and linking of data provided by totallydifferent components monitored by different types of agents.

More specifically, the OMEGAMON DE extends the capabilities of OMEGAMONXE to include:

Enterprise-specific Navigator views

The Navigator physical view shows the hierarchy of your managed enterpriseby operating platform and type of IBM Tivoli OMEGAMON XE agent. The

Navigator business view offered by IBM Tivoli OMEGAMON DE shows thehierarchy of any managed objects. You can also define Navigator views forany logical grouping, such as a business process or a departmental hierarchy.

Views of data from different types of monitoring agents in one workspace

In a single workspace, you can build a table or chart with data from one typeof monitoring agent, and another table or chart with data from a differentagent. Within that workspace, you can show views from as many differentagent types as are included on that branch of the Navigator.

Linking application workspacesYou can define a link from a workspace associated with one type ofmonitoring agent to a workspace associated with another type of agent.

You will understand these additional capabilities better as you follow theexample scenarios given throughout this book.

2.2 Terminology


45/338

Chapter 2. OMEGAMON XE/DE Distributed Architecture 23

The following sections describe the OMEGAMON terminology:

Candle Management Server (CMS): CMS gathers data from theOMEGAMON XE agents and acts as a collection and control point for alerts

received from the agents. The CMS sends the data it receives from theagents to CandleNet Portal clients, where it is displayed in tabular orgraphic views in a set of predefined or customized workspaces. The CMSalso accepts requests for information or action from CandleNet Portal clientsand distributes them to the agents for execution.

Hub Candle Management Server (Hub CMS): In scalability solutions, HubCMS communicates with agents and Remote CMSs, the CNPS, andWarehouse Agent.

Remote Management Server (RMS) (also called Remote CMS): In largeenvironments to improve scalability it may be necessary to balance thenetwork loads and configure some agents to connect to RMSs rather thandirectly to a primary CMS. Too many agents directly connecting to the primaryCMS may cause network traffic congestion.

CandleNet Portal (CNP): CNP is the Java-based interface to the datamonitoring and management resources of OMEGAMON Platform. Dependingon how it is installed, CandleNet Portal can be used as either a desktop orbrowser-based client. CandleNet Portal has its own server, the CandleNetPortal Server. The CandleNet Portal Serv

Date post:	05-Apr-2018
Category:	Documents
Upload:	bupbechanh
View:	236 times
Download:	0 times

Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1 Sg246768

Documents