Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

Tivoli IBM Tivoli OMEGAMON XE for WebSphere MQ

IBM

Version 3.7.0

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

SC31-6889-00

12

1

2

Tivoli IBM Tivoli OMEGAMON XE for WebSphere MQ

IBM

Version 3.7.0

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

SC31-6889-00

12

Note Before using this information and the product it supports, read the information in Notices on page 323.

1

Eighth Edition (April 2005) This edition applies to version 3.7.0 of IBM Tivoli OMEGAMON XE for WebSphere MQ (product number 5724-L34 on Windows, UNIX, OS/400, and HP NonStop Kernel; product number 5698-A57 on z/OS) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces GC32-9327-00. Copyright Sun Microsystems, Inc. 1999 Copyright International Business Machines Corporation 1996, 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

2

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Whats New in Version 3.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Chapter 1. Introducing Tivoli OMEGAMON XE for WebSphere MQ Configuration . . . . . . 17Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 OMEGAMON Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration?. . . . . . . . . . . . . . .24 Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Chapter 2.

Viewing Your Current WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . 35Creating Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Entering Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Creating a Configured System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Discovering Your Existing WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . . . .40 Reviewing Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Chapter 3.

Prototyping Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Introducing Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Using the Global Variables Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Adding, Modifying, or Deleting Global User Variables . . . . . . . . . . . . . . . . . . . . . . . . . .54 Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter 4.

Creating and Defining Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63What Are Defined Objects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Using the Configuration Search Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Creating New Queue Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Setting Access Authority for WebSphere MQ Objects. . . . . . . . . . . . . . . . . . . . . . . . . . .73 Connecting Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Creating Resource Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Contents

5

Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Using the Replicate Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Chapter 5.

Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Validating Objects in the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Controlling the Amount of Validation Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Chapter 6.

Maintaining Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Maintaining Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Viewing Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Updating the Configuration Database from Your Actual Configuration . . . . . . . . . . . . .97 Backing Up the Configuration of the Actual Environment . . . . . . . . . . . . . . . . . . . . . . .99 Updating Your Actual Configuration from Defined Objects . . . . . . . . . . . . . . . . . . . . .100 Working with Queue-Sharing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Exporting or Importing XML Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Exporting MQSC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Chapter 7.

Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111About Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Scheduling an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Scheduled Action Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116 Scheduled Action Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 Scheduled Action Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 Running a Schedule on Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Chapter 8.

Creating and Defining Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121About the Cluster Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 Clustering Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Product-Managed Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Creating a New Managed Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Chapter 9.

Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Audit Logging Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Historical Disk Space Requirements for the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . .141 Audit Log Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Chapter 10.

Backing up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Backing up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 Restoring the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Changing the Configuration Database Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Appendix A.

Remote Queue Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153What Is Remote Configuration?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Setting up Queue Managers for Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . .156 Examples of Possible WebSphere MQ Configurations . . . . . . . . . . . . . . . . . . . . . . . . .158

6

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, V3.7.0

Creating Remote Queue Manager Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

Appendix B.

Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165KMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 KCF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 KMCRCA Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 KCFCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Windows Event Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310

Appendix C.

Problem Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Problem Determination Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 The Environment File Used by this Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314

Appendix D. Appendix E. Index

Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Contents

7

8


Preface

PIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration is a component product of IBM Tivoli OMEGAMON XE for WebSphere MQ which is a component product of the IBM Tivoli OMEGAMON XE for WebSphere Business Integration package. The IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration sofware helps you simplify the time-consuming and resource-intensive tasks of defining and managing your WebSphere MQ configuration. This book describes the features and capabilities of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration and explains how to use it to quickly define and manage your WebSphere MQ configuration.

Preface

9

About This Book

About This BookWho should read this bookThis guide is intended to provide system administrators of WebSphere MQ with the processes involved in preparing IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to help you design and prototype your WebSphere MQ resources. Although step-by-step instructions are provided for each stage of the process, this book is designed to complement the online help that is provided with the product. Note: Before you can follow any of the instructions in this book, you must have OMEGAMON Platform and IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration installed and configured in your enterprise. For instructions, see the installation and configuration books on the publications CDs that accompanied this product.

Related publicationsThis section lists other useful publications in the IBM Tivoli OMEGAMON XE for WebSphere Business Integration library and in the OMEGAMON Platform library. The installation and configuration instructions in the following books are a prerequisite to the instructions in Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration:s

Windows and UNIX: Installing and Setting up OMEGAMON Platform and CandleNet Portal on Windows and UNIX , SC32-1768 Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX, SC31-6885

s

z/OS: Configuring Candle Management Server on z/OS, GC32-9414 Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS, SC31-6884

s

OS/400: Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere MQ on OS/400, SC31-6886

s

HP NonStop Kernel Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere MQ on HP NonStop Kernel, SC31-6887

These books explain how to use the other component products of IBM Tivoli OMEGAMON XE for WebSphere Business Integration:s

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, SC31-6888 Using IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers, SC31-6890

s

10


About This Book

s

Using IBM Tivoli OMEGAMON XE for WebSphere InterChange Server, SC31-6891

The following documents also provide useful information:s

Administering OMEGAMON Products: CandleNet Portal, GC32-9180, describes the support tasks and functions required for the OMEGAMON Platform, including CandleNet Portal user administration. Using OMEGAMON Products: CandleNet Portal, GC32-9182, describes the features of CandleNet Portal and how to use them with your IBM Tivoli OMEGAMON XE products. Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products, GC32-9429, describes the process of collecting historical data and either warehousing it or converting it to delimited flat files for reporting purposes. IBM Tivoli Candle Products Messages, 5 vols. SC32-9416SC32-9420, lists messages issued by the OMEGAMON Platform components.

s

s

s

The online glossary for the CandleNet Portal includes definitions for many of the technical terms related to OMEGAMON XE software. Accessing publications online Two publications CDs are shipped with IBM Tivoli OMEGAMON XE for WebSphere MQ:s

IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD OMEGAMON Platform and CandleNet Portal Documentation CD

s

The format of all publications is PDF. 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 software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address: http://www.ibm.com/software/tivoli/library/ Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the IBM Tivoli OMEGAMON XE for WebSphere Business Integration link to access the product library at the Tivoli software information center. 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 the following Web site: http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi You can also order by telephone by calling one of these numbers:s

In the United States: 800-879-2755 In Canada: 800-426-4968

s

Preface

11

About This Book

In other countries, see the following Web site for a list of telephone numbers: http://www.ibm.com/software/tivoli/order-lit

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM Tivoli Education Web site: http://www.ibm.com/software/tivoli/education

Support informationIf 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:s

Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information. Obtaining fixes: You can locate the latest fixes that are already available for your product. Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support.

s

s

For more information about these three ways of resolving problems, see Support Information on page 317.

12


Documentation Conventions

Documentation ConventionsOverviewThis guide uses several conventions for special terms and actions, and operating system-dependent commands and paths.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Required blanksThe slashed-b (!) character in examples represents a required blank. The following example illustrates the location of two required blanks.!eBA*ServiceMonitor!0990221161551000

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of z/OS command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

SymbolsThe following symbols may appear in command syntax:Table 1. Symbols in Command Syntax Symbol | Usage The or symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example: YES | NO In this example, YES or NO may be specified. [] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example: APPLDEST DEST [ALTDEST] In this example, DEST is a required argument and ALTDEST is optional.

Preface

13

Documentation Conventions

Table 1. Symbols in Command Syntax Symbol {} Usage Some documents use braces to denote required arguments, or to group arguments for clarity. Example: COMPARE {workload} REPORT={SUMMARY | HISTOGRAM} The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM. _ Default values are underscored. Example: COPY infile outfile - [COMPRESS={YES | NO}] In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

14


Whats New in Version 3.7.0

WThis product has a new nameIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (formerly OMEGAMON XE for WebSphere MQ Configuration) has been renamed because it is now produced by the Tivoli Software Group of IBM. Its companion product, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring (formerly OMEGAMON XE for WebSphere MQ Monitoring) has also been renamed. These two component products together are called IBM Tivoli OMEGAMON XE for WebSphere MQ which is a component product of the IBM Tivoli OMEGAMON XE for WebSphere Business Integration package.

Configuration product enhancementsThis configuration product includes many user-requested enhancements. They are:s

Configuration database has a database type option You can use either the product-provided Internal configuration database type (as in the previous release) or you can use a DB2 Universal Database (UDB) type database as your configuration database. Setting up the configuration database is part of setting up support for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration on your hub CMS. Refer to one of these books: Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS

You can find these books on the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product. For information about the configuration database, see Backing up the Configuration Database on page 143.s

Enhanced Scheduled Action options You can manually save the data from a scheduled action report to a log file on the client machine, or optionally export the data to a specified file. The saved file may be used as input for third-party reporting utilities. A Backup configuration database scheduled action is available.

Whats New in Version 3.7.0

15

For information about scheduled actions, see Action Scheduling on page 111.s

Enhanced dialogs The enhanced Discrepancy Display dialog lets you select muliple items then perform the Update actual from defined, or Update defined from actual operation. For information about discrepancies, see Viewing Discrepancies on page 95. The enhanced Validation Display dialog lets you select an item that is in error and correct it without leaving the dialog. For information about validation, see Validating Objects in the Defined View on page 86.

s

Pop-up menu options additions and some minor changes Use the Change Fonts option to adjust the appearance of some of the text in the defined view or prototype view. These changes are in effect until you log off of the session. Use the Compare items option to compare the resource definitions of two selected objects of the same type in the defined view tree; any combination of Defined or Actual resources is allowed. For example you can compare the defined resources of queue manager QM1 to either the defined resources or the actual resources of queue manager QM2. Use the Display configured systems option to quickly view the associations between configured systems and host names. The Display configured systems option is available when you right-click on the top-level icon in the defined view tree. Use the Display resources option to quickly view the resources contained in a resource group. The Display resources option is available when you right-click on a resource group icon in the defined view tree. Use the View authorities option to view the WebSphere MQ authorities in effect for objects in the selected configured system in the defined view tree. Use the Export all option to perform a full export of the entire configuration database. The data is exported in XML format for use with third-party report generators. An XML data file created using the Export all option cannot be imported back into the configuration database. The Export all option is available when you right-click on the top-level icon in the defined or prototype view tree. In a disaster recovery situation only, use the Reset Actual Exists option for the selected configured system in the defined view tree.

The appearance of some pop-up menu options has changed so that they fit more compactly on the menu. For example: The former Update actual from defined and Update defined from actual now appear as Update > actual from defined and Update > defined from actual. The former Show resolved menu option has been renamed to View resolved.

The functional operation of these menu options has not changed. For information about menu options, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration section of the CandleNet Portal help.

16


1Introduction Chapter contents

Introducing Tivoli OMEGAMON XE for WebSphere MQ Configuration

This chapter provides an overview of this products configuration features and explains how they can help you manage your WebSphere MQ configuration. This chapter also contains a scenario designed to explain how the elements of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration work together to help you ensure a cohesive network whose interrelationships are correctly defined.

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMEGAMON Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration? . . . . . . . . . . . . . Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . .

18 21 24 28


17

Getting Started

Getting StartedIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration uses the CandleNet Portal interface and adds the Configuration navigator view and the WebSphere MQ Configuration Authorities items to the interface. These items are described below. Heres how to get started using the Configuration view: 1. Log on to CandleNet Portal and, from the List of available Navigator Views, select Configuration.

The Configuration view is present in this list after initial installation of your IBM Tivoli OMEGAMON XE for WebSphere Business Integration product package. If Configuration does not appear in your List of available Navigator Views, then your IBM Tivoli OMEGAMON XE product administrator needs to assign the view to your User ID. 2. To add the Configuration view to your list of available Navigator views: open the Administer Users dialog (or ask your IBM Tivoli OMEGAMON XE product administrator to open it for you), select your User ID, then select the Navigator Views tab and add Configuration to your list of Assigned Views.

If you move Configuration to the top of the list of Assigned Views, as shown below, it becomes your default view.

Note: If Configuration is not listed in the Administer Users dialog on the Navigator Views tab shown above, either in the list of Available Views or in the list of Assigned Views, then product support is not properly installed from the CD for IBM Tivoli OMEGAMON XE for WebSphere Business Integration. Refer to the installation

18


Getting Started

documents on the the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product package. 3. While in the Administer Users dialog, select the Permissions tab and scroll down the list of Authorities. In this list, you will see the WebSphere MQ Configuration Authorities item, as shown in the next illustration.

Note: If the WebSphere MQ Configuration Authorities item is not listed in the Administer Users dialog on the Permissions tab shown above, then product support is not properly installed from the CD for IBM Tivoli OMEGAMON XE for WebSphere Business Integration. Refer to the installation documents on the the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product package. Your User ID requires the Modify permission (Modify includes View) in order to change your sites WebSphere MQ configuration or to schedule configuration updates using this configuration product (which may include access from the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring product by means of enhanced integration using OMEGAMON DE). 4. Click OK to save and exit the Administer Users dialog.


19

Getting Started

5. Close the interface then log on to CandleNet Portal again to update the List of Available Navigator Views and select (or default to) the Configuration view.

The Configuration view is the usual way to access IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. (It can also be accessed by means of enhanced integration with IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring using OMEGAMON DE.) This guide describes what you can do in the Configuration view.

20


OMEGAMON Platform

OMEGAMON PlatformIBM Tivoli OMEGAMON XE for WebSphere MQ is one of a suite of IBM products that assist you in monitoring your mainframe and distributed systems and applications. IBM Tivoli OMEGAMON XE products share a common agent-server-client architecture.(see Figure 1).

OMEGAMON XE agentsOMEGAMON XE monitoring agents collect system or application data from monitored, or managed, systems. The IBM Tivoli OMEGAMON XE for WebSphere MQ monitoring agents, for example, let you easily collect and analyze WebSphere MQ-specific data for all your remote and local queue managers from a single vantage point. The data are passed to the Candle Management Server, and displayed in the CandleNet Portal client.Figure 1. OMEGAMON XE AgentServerClient ArchitectureCandle Management Server

CandleNet Portal Clients

Monitoring Agents

CandleNet Portal Server

OMEGAMON XE 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 CandleNet Portal clients by the Candle Management Server. OMEGAMON configuration agents can create and configure objects. The configuration agents associated with IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration can configure objects such as WebSphere MQ queue managers and all their components (queues, channels, processes, and so on).

Candle Management ServerThe Candle Management Server (CMS) gathers data from the OMEGAMON XE agents and acts as a collection and control point for alerts received from the agents. The CMS


21

OMEGAMON Platform

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

CandleNet Portal clientsCandleNet Portal is the Java-based interface to the data monitoring and management resources of OMEGAMON Platform. Depending on how it is installed, CandleNet Portal can be used as either a desktop or browser-based client. CandleNet Portal has its own server, the CandleNet Portal Server. The CandleNet Portal Server performs common CandleNet Portal functions and serves to lighten the CandleNet Portal client.

Candle Management WorkstationThe Candle Management Workstation (CMW) is used for certain administrative functions that CandleNet Portal does not support. If you want to define and manage work groups and work lists, you must use the CMW.

IBM Tivoli OMEGAMON DEThe IBM Tivoli OMEGAMON DE feature package for CandleNet Portal offers a process-driven view of your enterprise. It enables you to pull together information from disparate sources, including a range of operating systems, servers, databases, mainframes, and network and Web components, in a single workspace and provides a single point of control from which you can manage all the resources your business-critical applications rely on. IBM Tivoli OMEGAMON DE extends the capabilities of OMEGAMON XE to include:s

Enterprise-specific Navigator views The Navigator physical view shows the hierarchy of your managed enterprise by operating platform and type of IBM Tivoli OMEGAMON XE agent. The Navigator business view offered by IBM Tivoli OMEGAMON DE shows the hierarchy of any managed objects. You can also define Navigator views for any logical grouping, such as a business process or a departmental hierarchy.

s

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 type of monitoring agent, and another table or chart with data from a different agent. Within that workspace, you can show views from as many different agent types as are included on that branch of the Navigator.

s

Linking application workspaces You can define a link from a workspace associated with one type of monitoring agent to a workspace associated with another type of agent.

22


OMEGAMON Platform

Policy ManagementThe CandleNet Portal Policy Management solution incorporates all the features of IBM Tivoli OMEGAMON DE and adds automation capabilities by means of the Workflow editor. The Workflow editor enables you to design sets of automated system processes, called policies, to resolve system problems. A policy performs actions, schedules work to be performed by users, or automates manual tasks.

Where to find more informationFor more information about OMEGAMON Platform, see the CandleNet Portal online help and the books on the OMEGAMON Platform and CandleNet Portal Documentation CD.


23

What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration?

What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration?What IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration doesBuilding a network for your WebSphere MQ messaging middleware can be a slow and difficult task. As your network grows and queue managers span dozens of systems running on a variety of operating systems, it becomes even more difficult to determine where and how to configure new queue managers and their resources. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration simplifies the time-consuming and resource-intensive tasks of defining your configuration. You can use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to:s

Manage your WebSphere MQ network, including local or remote nodes, from a single point of control See how your WebSphere MQ queue managers and resources are related by viewing a graphical representation of your entire network Manipulate WebSphere MQ objects across one or more networks of queue managers from a single workstation Base configurations on prototype models so you can implement global updates with the click of a mouse Save time and resources by performing many difficult development tasks automatically Group related WebSphere MQ resources together in ways that reflect the business-oriented relationships between them and the logical structure of your enterprise

s

s

s

s

s

This guide provides information on the features and tools that IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration offers to help you manage your WebSphere MQ configuration.

Centralized configuration informationIn a highly distributed network, WebSphere MQ may run on a wide variety of platforms, which compounds the complexity of configuring and maintaining hundreds or even thousands of nodes. No matter where your resources lie, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides simplification by offering a single repository for all your WebSphere MQ configuration data, called the configuration database. The configuration database is stored at the hub CMS and includes a default set of objects to help you start using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

A graphical representation of your configurationIt is difficult to get a sense of your configuration structure when your view of it consists only of configuration definitions. To help you understand the structure of your configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides a

24



representation of your WebSphere MQ configuration called the Defined View. Defined objects in this view represent current or potential WebSphere MQ resourcesqueue managers, channels, queues, processes, namelists, and so on, all under the management of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

You can use the Discover feature to quickly and easily build defined objects that represent your actual WebSphere MQ configuration. You can also use the Defined View to safely validate changes to your configuration before applying them to your actual WebSphere MQ configuration.

Common prototype models for creating WebSphere MQ objectsThe prototype feature enables you to create blueprints for queue managers, resource groups, and resources that you can use as templates for defining configurations. Once you create a prototype object, you can drag and drop it from the Prototype View into the Defined View as needed to build or update your configuration. Any object created from a prototype inherits the characteristics of the prototype unless you specifically override them. If you update a prototype, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration updates all objects based on that prototype automatically. Using prototypes makes maintaining your WebSphere MQ configuration much easier, because instead of having to update many defined objects, you can update just the prototype on which they are based. You can decrease your maintenance costs even further by using variables in your prototypes. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration includes a Global Variables workspace that enables you to quickly and easily change variable values that are inherited by subordinate objects.

Managing resources from a business perspectiveInstead of locking you into a systems perspective of your WebSphere MQ configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration frees you to organize WebSphere MQ resources into groups according to their business purpose. Configured system groups let you organize queue managers into groups of your own choosing. For example, you can group and manage all resources related to a particular application. This allows you to create a configuration that closely matches the logical structure of your


25


enterprise. At a lower level, Resource groups make it easy to organize queue manager resources (such as channels, queues, processes, namelists, and so on) by the business purpose they serve.

Keeping your actual and defined configurations in syncOnce you develop and test the Defined View, you will want to implement your changes in your actual WebSphere MQ configuration. Or you may want to change your actual configuration manually and update the Defined View accordingly. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides update features that enable you to keep your actual configuration and defined configuration in sync. It is a good practice to reconcile differences between the Defined View and your actual WebSphere MQ configuration before attempting any type of update operation. The View discrepancies action lets you resolve specific differences either in favor of the configuration database or in favor of the actual configuration. When you choose to Update actual from defined, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration first validates your Defined View to prevent errors from being implemented in your actual configuration, then updates your actual configuration to match the configuration database. Another way to keep your actual configuration and defined configuration in sync is to choose to Update defined from actual, which changes the configuration database to match your actual WebSphere MQ configuration. Note both the Update actual from defined and Update defined from actual operations may delete objects from the configuration that is being updated (thus it is important to View discrepancies before you perform either Update action to ensure you know what changes will be implemented).

Scheduling actionsYou can either perform the Update actual from defined, Update defined from actual, or View discrepancies actions as you update your configurations, or you can schedule these actions to run at specific intervals. For more information see Action Scheduling on page 111. You have options available for how to perform long-running tasks. Based on how you have the product option set, you can select whether to always run in the foreground, always run in the background, or be prompted each time. Actions that you can perform in the background include:s

Update defined from actual Update actual from defined View discrepancies Delete (defined, actual, or both actual and defined) Validate Discover new resources

s

s

s

s

s

26



s

Backup configuration database

For example, if you have the product option set to prompt each time, when you select Update actual from defined you are prompted as to whether the update should run in the background. If you reply yes, the product creates an internal scheduled action to perform the update.

Monitoring network performance with the monitoring productA sibling product of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, enables you to easily collect WebSphere MQ data from all your remote and local queue managers and analyze it from a single vantage point. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration and IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can be used independently of one another. However, when used together, one product enhances the other. CandleNet Portal integrates the monitoring functions provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring with the configuration functions provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, thereby enabling a single WebSphere MQ administrator to address both needs from a single workstation. In addition, the monitoring and performance information provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can help you configure your WebSphere MQ network for maximum efficiency. For example, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can help you determine if there are any bottlenecks in your configuration and you can then use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to resolve bottlenecks by moving or adding queues or by reconfiguring queues and channels.

Viewing monitoring product statistics from the configuration productWhen you perform a View actual request against a queue manager, a local queue, or a channel, the configuration product queries the appropriate OMEGAMON Monitoring Agent for WebSphere MQ to pick up the most current monitoring statistics. The statistics collected are presented in the Statistics section of the settings list for the object. The Statistics section is only included in the settings list if you perform the View Actual request (it is not present for a normal settings list open). If the monitoring agent is not available, the message "Statistics unavailable - WebSphere MQ monitoring agent not running" is displayed.

Entering WebSphere MQ commands from the defined viewWhen you select the Submit MQ Command option (for example: in the Defined View select a channel, right-click and, from the pop-up menu, select Action > Submit MQ command..) a dialog appears which allows you to enter a free-form WebSphere MQ operator command. The resulting return code is displayed at the client. For other action command options see Using the Action menu option for queue managers or channels on page 71.


27

Putting All the Pieces Together: A Typical Scenario

Putting All the Pieces Together: A Typical ScenarioThis section presents a scenario that may help you understand how the features of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration work together to help you build your WebSphere MQ network. At this point, you wont need to know exactly how each task is performedsubsequent chapters describe these tasks in detail. Instead, note how the company in the scenario uses the power of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to minimize the effort involved in the rollout and maintenance of a new application to many sites.

The XYZ CompanyThe XYZ Company has only recently begun to use WebSphere MQ for application-to-application integration. The company expects their WebSphere MQ configuration to grow rapidly in size and complexity. As systems administrator, you suggest they purchase IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to help them manage an increasingly challenging environment. One of their first uses of WebSphere MQ is to integrate two applications:s

An order processing application that currently runs on a central z/OS system at company headquarters. An order entry application that will run on AIX systems located at each of the seven branch offices. The application will be rolled out to the seven offices over the next two weeks.

s

BackgroundBefore you installed IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you created a queue manager and supporting queues on the central z/OS system for the order processing application. You also created queue managers on each of the remote AIX systems in anticipation of the order entry application rollout. Each AIX queue manager requires four queues. Because each group of four queues supports the same application, the WebSphere MQ administrator expects to configure each group the same way. Now that you have installed IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you want to use its features to minimize the cost of:s

Designing and testing your planned configuration of the four queues supporting the order entry application on each AIX system. Deploying the planned configuration on the seven remote AIX systems. Maintaining the configuration of the queues over the life of the application.

s

s

StrategyAfter reviewing the goals and the tools provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you work out the following strategy for designing, testing, and deploying the planned configuration.

28



Because the planned configuration will comprise sets of four queues on each of the seven systems, you decide to create prototypes of the four queues. You also decide to create a resource group prototype to hold the four queue prototypes. This strategy simplifies the work required to build the initial configuration, because once you are satisfied with the configuration of the queue prototypes, you can use them as needed to quickly create queues for the new application. All you have to do is drag an instance of the resource group prototype to the queue manager on each system in the defined view. Using prototypes also greatly minimizes the effort required to maintain the queues supporting the order entry application. If changes to the application require additional queues or changes to the existing queues, you can change the prototypes directly instead of manually changing each copy. After copying the resource group prototype to a queue manager in the defined view, you use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to test the defined configuration. Once you are satisfied with the results, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to update the actual WebSphere MQ configuration with a few clicks of the mouse.


29


ExecutionTo implement this strategy, you take the following steps: 1. Discover and view your existing WebSphere MQ configuration. You use the Discover feature to upload your existing WebSphere MQ configuration so that you can view a representation of it in the Defined View (this is explained in detail in the next chapter). Now that you can see and manipulate the structure of your existing configuration, you can easily make configuration decisions.

2. Create queue prototypes. Next you create a prototype of each of the four queues that support the order entry application. These prototypes serve as the models for queue objects you will add later to the defined view. Once the queues are added to the seven AIX systems in the defined view, you can change the queues by simply changing the original four prototypes on which they are based. When creating the four queue prototypes, you specify a name for the prototype, ProtoOrderEntryQn, and another name for defined objects based on the prototype, OrderEntryQ n on System Y, where n is a number from 14, and Y is the AIX nodename.

30



By using similar names for defined objects and for the prototypes on which they are based, you can easily keep track of related objects.

3. Create a resource group prototype. You create a resource group prototype to contain the four resources supporting the order entry application. Creating a resource group prototype makes it easy to configure each AIX system for the order entry application as it is rolled out. When creating the prototype resource group, you specify a name for the prototype, ProtoOrderEntryGroup, and another name for defined objects that will be based on the prototype, OrderEntryGroup on System Y. Again, using similar names for defined objects and for the prototypes on which they are based, makes it easier to keep track of related objects. 4. Drag an instance of the queue prototypes into the resource group prototype. You can drag an instance of the four queue prototypes into the resource group prototype. This creates references to each of the four queue prototypes. These references act as pointers that link the queue prototypes to the resource group prototype. If you make


31


changes to a queue prototype, the change is automatically reflected in the resource group prototype and in each defined object based on these prototypes.

5. Drag an instance of the resource group prototype to the defined view tree. Next, you open the Defined and Prototype view and copy the resource group prototype to the defined queue manager for the first system to support its order entry application. Dragging an instance of a prototype to the Defined View does not affect your actual WebSphere MQ configuration. Copying the resource group prototype to the Defined View creates a defined resource group called OrderEntryGroup on System Y. The defined resource group contains the

32



four queues referenced in the resource group prototype on which it is based. As defined in their prototypes, the queues are all named OrderEntryQn on System Y.

6. Validate the queue manager definition. To ensure that there are no errors in the queue manager definition or in any of its new underlying resource definitions, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to validate the queue manager with the new resource group. If you find any errors in the four new queues, edit the associated prototypes, not the object in the Defined View, then validate the queue manager again. 7. Update the WebSphere MQ configuration. Now that you are confident that the defined view you have created in support of the order entry application is valid, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to update the actual WebSphere MQ configuration automatically. Instead of implementing the changes command by command, right-click the queue manager you want to update and, from the pop-up menu, select Update actual from defined. By default, this configuration product validates the defined configuration automatically before adding the four new queues to the queue manager on the actual AIX system. Next, repeat the process as needed for each of the remaining six AIX systems as the order entry application is rolled out.

MaintenanceOne year later, an upgrade to the order entry application requires the addition of a fifth queue to each of the seven AIX systems. Because you used prototypes to build the


33


resource group and original four queues for the application, it is easy and fast to add another queue. 1. You create a fifth prototype in the same manner as you created each of the original four queue prototypes. You use the same naming convention as well: ProtoOrderEntryQ5 for the prototype name and OrderEntryQ 5 on System Y for the name of defined objects based on the prototype. 2. You add ProtoOrderEntry5 to the resource group prototype ProtoOrderEntryGroup. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration adds a reference to the fifth queue prototype to the prototype. Now that the resource group prototype has been changed, all the defined resource groups based on ProtoOrderEntryGroup get a fifth defined queue as well. 3. Because this configuration product validates updates to an actual configuration before implementing them, you can run the Update actual from defined operation on the entire configured system group without first validating the change you just made to seven AIX systems. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration looks for validation errors that may have been introduced with the fifth queue and, finding no errors, adds the fifth queue to the actual WebSphere MQ configurations on the seven AIX systems.

34



Viewing Your Current WebSphere MQ Configuration

This chapter explains how to use the configuration product to view your existing WebSphere MQ configuration. This enables you to see a graphical representation, the structure, and the contents of your configuration.

Creating Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Configured System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering Your Existing WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . . . Reviewing Your Defined View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36 37 38 40 42


35

Creating Your Defined View

Creating Your Defined ViewAbout creating a defined view of your configurationThe Defined View enables you to create a graphical representation of your WebSphere MQ configuration and provides features that help you manage your sites actual WebSphere MQ queue managers, and resources. You can initially build this representation by one of two methods:s

Using your existing WebSphere MQ configuration as the basis for your representation in the Defined view. Creating your representation in the Defined View directly within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. See What Are Defined Objects? on page 64.

s

Process summaryCreating a representation in the Defined View based on your existing WebSphere MQ configuration comprises the following tasks: 1. Entering update mode so you can make changes to the configuration database as described on page 37. 2. Creating a new configured system group, as described on page 38. 3. Using the Discover feature to populate the configuration database with defined objects representing your actual WebSphere MQ configuration, as described on page 40. 4. Reviewing the graphical representation of your WebSphere MQ configuration, as described on page 42.

36


Entering Update Mode

Entering Update ModeWhat you can do in update modeTo change the configuration database, you must first change to update mode. When you are in update mode, you can:s

Change your Defined View, including using the configuration database to update your actual configuration (as described in Maintaining Your Configuration on page 93) and using your actual configuration to populate the configuration database (as described in this chapter). Change your Prototype View. See Prototyping Your Configuration on page 43. Use the Global Variables workspace to create, delete, and change the values assigned to your sites global user variables. See Introducing Variables on page 51. Backup and restore the configuration database. See Backing up the Configuration Database on page 143

s

s

s

Before you can enter update modeTo enter update mode, your user ID must have Modify WebSphere MQ Configuration permission, and the Navigator Configuration view as an Assigned View as described in Getting Started on page 18. For detailed information about user administration, refer to the Administering OMEGAMON Products: CandleNet Portal guide.

ProcedureTo enter update mode: 1. Ensure you are viewing IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. In CandleNet Portals List of available Navigator Views, the Configuration view is selected. 2. In the configuration navigator tree, select Configuration (the root-level item). 3. The Update mode check box displays in the Configuration workspace. 4. Select the Update mode check box.


37

Creating a Configured System Group

Creating a Configured System GroupWhat is a configured system group?A configured system group is a unit of organization within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration that enables you to organize queue managers into groups of your own choosing. A configured system group has no corresponding component in an actual WebSphere MQ configuration; it is simply a collection of queue managers, which in turn contain resource groups. Resource groups contain individual resources (queues, channels, and so on). Configured system groups are the highest unit of organization within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. You may create any number of configured system groups and organize them in any way that is meaningful for your site.

ProcedureTo create a new configured system group: 1. Ensure you are in update mode. 2. Open the Defined View. 3. The defined view tree displays on the left side of the Defined View workspace. 4. Right-click on Defined View (the root-level item) and, from the pop-up menu, select Create new Configured System Group.

You are prompted to supply a name for the new object. 5. Enter an alphanumeric name for the new configured system group. Click OK. The new configured system group object is added to the defined view tree. If the default settings for the object are acceptable, you are finished creating the new configured system group. If you want to modify or view the default settings for the object, continue with the next step in this procedure.

38


Creating a Configured System Group

6. In the defined view tree, select the new configured system group. 7. The settings list for the object displays on the right side of the Defined View. 8. Complete the settings list as necessary. 9. Click Help to display information about each parameter. 10. Click Save to save your changes.


39

Discovering Your Existing WebSphere MQ Configuration

Discovering Your Existing WebSphere MQ ConfigurationWhat the discover process doesThe Discover process populates your Defined View with data from existing queue managers. When you run the Discover process, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration searches your entire WebSphere MQ network for queue managers not already defined in the configuration database and adds them to the selected configured system group. This feature is only available at the configured system group level.

ConsiderationsA few key points about the Discover feature:s

The Discover feature processes only new queue managers on systems running IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (the configuration agent, hereafter) connected to the CMS. If the configuration manager discovers a queue manager that is already defined within the database, that queue manager is ignored. All z/OS queue managers must be defined as z/OS subsystems. On non-z/OS systems, the configuration agent scans for information relating to each queue manager that has been defined using the WebSphere MQ CRTMQM command. Queue managers can be discovered if they have been created using the WebSphere MQ CRTMQM command. For the configuration agent to pick up resource information, a queue manager must be active at the time the Discover process takes place. Inactive queue managers appear in the defined view tree as a single node with no resource groups. If this occurs, you can use one of the following options to add resource information: Start the queue manager and perform an Update defined from actual. See Updating the Configuration Database from Your Actual Configuration on page 97. Go to the queue manager settings list, expand the Auto Start section, and select the Auto start check box. Then perform an Update defined from actual, see Updating the Configuration Database from Your Actual Configuration on page 97.

s

s

s

s

s

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration can automatically perform a discovery if you activate the Auto Discover product option (in the Product Options area of the Configuration workspace). By default, automatic discovery is disabled. For more details, see the online help in the Configuration workspace. Depending on the size and complexity of your existing WebSphere MQ configuration, the Discover process may take a while, and it is not interruptible once begun. If it is not practical to wait for the entire Discover process to complete, you can activate the

s

40


Discovering Your Existing WebSphere MQ Configuration

Discover Lite product option (in the Product Options area of the Configuration workspace). By default, Discover Lite is disabled. For more details, see the online help in the Configuration workspace.s

The terms Discover and Discovery describe the default Discover process of this configuration product unless specifically noted in this guide.

ProcedureWarning:Depending on your WebSphere MQ configuration, this can be a lengthy procedure and it is not interruptible once begun. To search your sites WebSphere MQ network for queue managers and add them to the current configured system group: 1. Ensure you are in update mode. 2. Open the Defined View. The defined view tree displays on the left side of the Defined View workspace. 3. Right-click on the configured system group to which you want to add the discovered queue managers and, from the pop-up menu, select Discover. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration searches your sites entire WebSphere MQ environment for unknown queue managers and adds them and all their associated resources (queues, channels, and so on) to the configured system group you selected. For each queue manager discovered, this product creates a resource group named $Default_Group, and the queue managers resources are added to that resource group. When the Discover process is complete, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration displays a report containing information about the Discovery.


41

Reviewing Your Defined View

Reviewing Your Defined ViewOverviewAfter you use the Discover feature to populate a configured system group, you can see your existing WebSphere MQ configuration in the Defined View. Your configuration is shown graphically in a tree view. In this view, different icons represent each type of object in your configurationqueue managers, queues, channels, processes, namelists, and so on. The left side of the display shows a hierarchical representation of configured system groups, configured systems (queue managers), resource groups, and resources. Click on the + or - signs to expand or contract the display. The right side of the display shows the settings list of the currently-selected object.

Resource group $Default_GroupWhen you populate a configured system group in the Defined View using the Discover feature, resources associated with each active queue manager are put into a resource group called $Default_Group. Each active queue manager you discover has its own $Default_Group of resources. After the Discover process completes, you can move resources from this pool into resource groups that you create. See page 76 for more information about resource groups.

42



Prototyping Your Configuration

This chapter discusses the Prototype View and its relationship to the Defined View. It explains prototyping and explains how to use the provided tools effectively.

About Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introducing Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Global Variables Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding, Modifying, or Deleting Global User Variables. . . . . . . . . . . . . . . . . . . . . . . . . Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44 46 48 49 51 53 54 56 58 61 62


43

About Prototypes

About PrototypesWhy use prototypes?Prototyping allows you to design and plan your WebSphere MQ configuration. Sample prototype objects are provided. You can use these samples to build objects that may eventually become part of your WebSphere MQ configuration. Any object created from a prototype inherits the characteristics of the prototype unless you specifically override them. If you update a prototype, all objects based on that prototype are automatically updated, regardless of their location. This is ideal if you have a distributed network and you want to place identical objects in different locations while ensuring they always remain in sync. For example, you may need to create several identical queue manager configurations. Once you define the queue manager prototype, you can use it to create as many Defined View objects as you need and put them in several locations. If you decide to change the queue manager configuration in all locations, simply alter the original prototype queue manager.

Creating prototypes: two methodsYou can work entirely within the Prototype View to create a new prototype, or you can use a defined object from the Defined View to create a prototype.s

Before you actually add objects to your WebSphere MQ configuration, you may want to design and create objects from scratch in the Prototype View. The advantage here is that you can design the objects to your exact specifications before you add them to your WebSphere MQ configuration. You can also take an object that you uploaded from your WebSphere MQ configuration or created in the Defined View, and copy it to the Prototype View to use as a prototype for future objects. The advantage here is that your current WebSphere MQ objects are already configured to your specifications, so you can easily create other objects based on them.

s

Introducing the prototype viewThe Prototype View, where you work with prototypes, is divided into the following organizational levels:s

Configured System Prototypes, which represent queue managers and managed clusters. Resource Group Prototypes, which allow you to gather resources into logical groups.

s

44


About Prototypes

s

Resource Prototypes, which represent channels, queues, processes, namelists, storage classes, and so on.

Creating an instance of a prototype object within the defined viewAfter you create and define prototype objects, you can drag an instance of the prototype to the Defined View to create objects that are based on the prototypes. See Dragging Prototype Objects to the Defined View on page 49.

Global variables versus symbolic variablesWhen used with prototypes, global variables provide a powerful way to define and maintain a value in a single place and the value can be referred to symbolically in many resources. Global variables can be used with any object. Symbolic variables are variables that apply only to one prototype and can be inherited by subordinate objects within that prototype. For example, a symbolic variable that you define at the queue manager level is available to all subordinate resource groups and resources.


45

Creating Prototypes in the Prototype View

Creating Prototypes in the Prototype ViewOverviewYou create prototypes as models on which to base future objects. If you decide to change the parameters of an object, simply alter the prototype, and all objects that are based on the prototype are updated automatically. When you drag a prototype to the Defined View, you actually create an instance of the prototype.

Sample prototypesIn the Prototype View, the configuration product provides the following types of sample prototypes to help you design and create all or part of your WebSphere MQ configuration. Sample prototypes include standard, defined resources as specified in AMQSCOMA.TST:s

Configured System prototypes Use a configured system prototype sample to create queue manager or managed cluster prototypes. Queue manager prototypes consist of a set of queue manager properties and zero or more references to resource group prototypes. Managed cluster prototypes consist of a set of cluster properties and zero or more local queue objects or references to local queue objects. See the note on page 46.

s

Resource Group prototypes Use a resource group prototype sample to create resource group prototypes that refer to one or more resource prototypes. When you reference a resource prototype within a resource group, a reference object appears. References are pointers to the original prototype. See the note on page 46.

s

Resource prototypes Use a resource prototype sample to create individual resource prototypes. Resource prototypes correspond to the WebSphere MQ resource types. For example, a local queue prototype and a sender channel prototype are provided as well as other WebSphere MQ resource types.

Note: When you drag and drop a prototype directly to a higher-level prototype, the products Prototype copy semantics setting (in the Configuration view) determines whether the resource is copied directly to the higher-level prototype, or whether a reference object is created which points back to the prototype being dragged. The default setting is to create a copy. However, if the Prototype copy semantics setting is Create reference then a prototype reference object is created.

46


Creating Prototypes in the Prototype View

ProcedureTo create a new prototype in the Prototype View: 1. Ensure you are in update mode. 2. Open the Prototype View. 3. In the prototype view tree, use one of the following options:s

To prototype a new queue manager or managed cluster, right-click on Configured System Prototypes and, from the pop-up menu, select Create then select either Queue Manager or Managed Cluster. To prototype a new resource group, right-click on Resource Group Prototypes and, from the pop-up menu, select Create Resource Group. To prototype a new resource, right-click on Resource Prototypes and, from the pop-up menu, select Create then select the type of prototype object to create.

s

s

You are prompted to supply a name for the new object. 4. Enter a name for the new object and click OK. The new prototype object is added to the prototype view tree. Note: The following applies to prototype queue managers and resource groups: If the name you assign to this prototype object already exists in the configuration database, the configuration product appends the number 1 to the prototype object. If you create another prototype object with the same name again, the configuration product increments this number by one. 5. In the prototype view tree, select the new prototype. The settings list for the object displays on the right side of the Prototype View. 6. Complete the settings list as necessary. Click Help to display information about each parameter. 7. If you are creating a new queue manager prototype, add the Default.MQSeries.Resources to the new queue manager as follows: 1. In the Prototype View, expand the Resource Group Prototypes. 2. Locate the resource group named

3. Drag the Default.MQSeries.Resources icon to the appropriate queue manager icon in the prototype view tree, then release the mouse button. An instance of the default resources are added to the new queue manager prototype definition. 8. Click Save to save your changes.


47

Creating Prototypes from Defined Objects

Creating Prototypes from Defined ObjectsOverviewYou can create a prototype by dragging a defined object from the Defined View and dropping it in the Prototype View.

ProcedureTo create prototypes from defined objects: 1. Ensure you are in update mode. 2. Open the Defined and Prototype workspace. The Defined View and Prototype View are positioned and sized so you can easily drag objects between them. 3. In the defined view tree, select the object you want to use as a prototype. Note: The defined object you select cannot itself have been based on a prototype. 4. Drag the defined object from the defined view tree to the prototype view tree; then release the mouse button on the appropriate icon. A prototype is built based on the defined object. The original object remains unchanged in the Defined View and in the configuration database.

48


Dragging Prototype Objects to the Defined View

Dragging Prototype Objects to the Defined ViewOverviewAfter you create a prototype object, you will eventually want to create an instance of an object based on that prototype in the Defined View. When you drag a prototype object to the Defined View, the configuration product adds a new icon to the Defined View, creates a defined object based on the prototype, and adds its definitions to the configuration database. Any changes you make to the original prototype in the Prototype View automatically updates the instance that is now in the configuration database.

GuidelinesUse these guidelines when dragging objects:s

You must be in update mode to drag objects. You can drag instances of queue manager prototypes into defined configured system groups only. You can drag instances of resource group prototypes into defined queue managers or defined resource groups. You can drag instances of resources into defined resource groups or defined queue managers.

s

s

s


49

Dragging Prototype Objects to the Defined View

ProcedureTo create an instance of a prototype in the Defined View: 1. Ensure you are in update mode. 2. Open the Defined and Prototype workspace. The Defined View and Prototype View are positioned and sized so you can easily drag objects between them. 3. In the prototype view tree, select the prototype whose instance you want to copy to the Defined View. 4. Drag the selected prototype from the prototype view tree to the defined view tree. Hint: While dragging the selected prototype, if you hover near the top or bottom of the defined view tree, the items will scroll. This may take a moment. 5. Release the mouse button when the prototype is in the appropriate location. An instance of an object based on the prototype is added to the configuration database. Notice that the prototype icon changes to the corresponding defined icon. 6. If necessary, right-click and, from the pop-up menu, select Refresh to update the Defined View display. Even though the object is now part of the defined configuration, it is not added to your actual WebSphere MQ configuration until you use the Update actual from defined feature. See Updating Your Actual Configuration from Defined Objects on page 100.

50


Introducing Variables

Introducing VariablesOverviewWhen used with prototypes, variables ensure consistency throughout your configuration and can help you quickly identify objects that may be based on the same prototype. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides a Global Variables workspace that allows you to create your own global user variables. Global user variables are available for use by any individual object in the configuration. Symbolic variables are local to a particular defined or prototype object, and all its subordinate objects can inherit the symbolic variables. Symbolic variables are defined in the Symbolic variables field of the objects settings list (for example, in the Prototype section of a prototype object). Variables resolve only after you create an instance of the prototype in the Defined View. If necessary, you can override variables after the objects are in the Defined View. You can view resolved global variables or symbolic variables in the Defined View using the View Resolved menu option. For more information see Viewinging resolved variables on page 60.

Product-provided global variablesIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following global variables: APPLNAME The application type (for example, "MQ") associated with the current object. CFGSYSNM The name of the "current" configured system (for example: queue manager). HOSTNAME The host name associated with the "current" configured system. You cannot add, delete, or modify these global variables. You may see them in some of the sample prototypes and you may use them in your prototypes if you want.

Dynamic variablesIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following dynamic variables. These variables are dynamic in the sense that they are likely to have a different value each time they are referenced. DATE Current local date at the CMS, in the format yymmdd. This variable can be used in dynamic resource creation where multiple resources are to be created, using the date to form part of a unique resource name. JDATE Current Julian local date at the CMS, in the format yyddd. This variable can be used in dynamic resource creation where multiple resources are to be created, using the date to form part of a unique resource name.


51

Introducing Variables

TIME Current local time at the CMS, in the format hhmmss. This variable can be used in dynamic resource creation where multiple resources are to be created, using the time to form part of a unique resource name. USERID Current logged on User ID. Note this value is displayed in the System Information Area of the Configuration workspace. This is the user ID you typed on the CandleNet Portal Logon dialog with the casing preserved exactly as typed. Dynamic variables are designed to be used in Resources in the Prototype View. When you drag a prototype that uses a dynamic variable to the Defined View, the dynamic variable references the value that is current at the time that you drag the prototype. For example, you might create a prototype resource that contains in the Description field: Created by &MYUSER on &MYDATE at &MYTIME and that contains in the Symbolic Variables field: MYDATE=&DATE,MYTIME=&TIME,MYUSER=&USERID. Dynamic variables are not appropriate to use if you are creating Resources in the Defined View without using a prototype. For example if you create a Resource in the Defined View without using a prototype and you use the variable &TIME, the dynamic variable references one value when you save the Resource, but when you perform a View discrepancies, the database version references a new value and will always cause a discrepancy.

52


Using the Global Variables Workspace

Using the Global Variables WorkspaceOverviewUse the Global Variables workspace to view the global user variables currently defined for your IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration environment. Global user variables are variables that your site creates. The values of these variables can be referenced in the settings list of any IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration object. If you are authorized to do so, you can use the Global Variables workspace to create, modify the values of, or delete your site's global user variables.

Viewing global user variablesThe Global Variables workspace displays your sites global user variables in a report-like format. The workspace lists the following for each variable:s

Variable The name of the global user variable. Value The value that the variable resolves to. Description An optional text description of the variable.

s

s


53

Adding, Modifying, or Deleting Global User Variables

Adding, Modifying, or Deleting Global User VariablesGuidelinesUse these guidelines when adding, modifying, or deleting global user variables:s

You must be in update mode to add, modify, or delete variables. You can modify a user-defined variable Value or Description, but not its Name. If you mis-name a variable, delete it and define a new one.

s

Adding a global user variableTo add a global user variable: 1. Ensure you are in update mode. 2. Open the Global Variables workspace. The list of global user variables displays. 3. Click Add new variable. The Add User Variable dialog displays.

4. In the Name field, enter the name of your new variable (from 1 to 48 case-sensitive characters); in the Value field, enter its value (from 1 to 64 case-sensitive characters), in the Description field, enter an optional text description (from 1 to 64 case-sensitive characters). 5. Click Add. The variable is added to the list of global user variables.

54


Adding, Modifying, or Deleting Global User Variables

Modifying a global user variableTo modify a global user variable: 1. Ensure you are in update mode. 2. Open the Global Variables workspace. The list of global user variables displays. 3. Double-click in the Value field or the Description field of the variable you want to modify. A blinking text cursor appears in the field; you can now edit the field. 4. Edit the variable as appropriate. 5. Click Save to save your changes.

Deleting a global user variableTo delete a global user variable: 1. Ensure you are in update mode. 2. Open the Global Variables workspace. The list of global user variables displays. 3. Select the variable you want to delete and click Delete variable. The user variable is deleted from the Global variable editor. Note: When you delete a variable, be sure to also delete any references to the deleted variable from any settings list. 4. Click Save to save your changes.


55

Adding Global Variables to Prototypes

Adding Global Variables to PrototypesOverviewThis section provides an example that you can use to add global variables to prototypes.

GuidelinesUse these guidelines when adding global variables to an objects settings list:s

You must be in update mode to add global variables. To use a global user variable, be sure that it is defined in the Global Variables workspace. You can use a global variable in any text field of a settings list. When you use a global variable in the text field of a settings list, it must be preceded by an ampersand (&). For example, to use the global variable that resolves to the application name, enter:&APPLNAME

s

s

s

s

To string variables together or add additional descriptive text, use a period to indicate the end of a variable name. For example:&APPLNAME..&HOSTNAME.New_Queue

resolves toMQ.lwallNew_Queue

56


Adding Global Variables to Prototypes

ExampleIn the following example, you create a global variable to identify your payroll system on the West Coast. You want to be able to identify that the system is WebSphere MQ in the Los Angeles office. 1. Ensure you are in update mode. 2. Open the Global Variables workspace and create a new global user variable named LAQ. 3. In the Value field, enter: Los_Angeles. 4. Create a new queue manager prototype. 5. When prompted for the name of the new queue manager (this will be the Prototype name field on the Prototype section), enter:My_New_Queue_Manager

6. Open the settings list of the new queue manager prototype. 7. Expand the Manager section, and in the Name field enter:&APPLNAME..&LAQ..Payroll_West

This is a combination of the application name product-provided global variable, the global variable you created, and additional text. 8. Complete the settings sections, click Save to save your changes. A new queue manager prototype named My_New_Queue_Manager appears in the prototype view tree. 9. When you drag an instance of the prototype to the Defined View, the following queue manager name displays based on the global variables you entered:MQ.Los_Angeles.Payroll_West


57

Adding Symbolic Variables to Prototypes

Adding Symbolic Variables to PrototypesOverviewThis section provides an example that you can use to add symbolic variables to prototypes.

GuidelinesUse these guidelines when adding symbolic variables to prototypes:s

You must be in update mode to add symbolic variables to prototypes. Before you add symbolic variables to prototypes, you must define them in the Symbolic variables field in the Prototype section o

Date post:	11-Nov-2014
Category:	Documents
Upload:	harikrishnam2008gmailcom
View:	86 times
Download:	7 times