OMEGAMON XE for WebSphere MQ Configഀ甀爀愀琀椀漀渀唀猀...

User’s GuideOMEGAMON® XE

for WebSphere MQ Configuration

Version 360

GC32-9327-00

December 2003

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 OMEGAMON XE for WebSphere MQ Configuration User’s Guide, V360

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleNet eBusiness Platform, CandleNet Portal, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CandleNet Command Center, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Assurance, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein are trademarks or registered trademarks of their respective companies.

Copyright © December 2003, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . 13

What’s New in Version 360 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Chapter 1. Introducing OMEGAMON XE for WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . . 17Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18What Are OMEGAMON XE and OMEGAMON DE? . . . . . . . . . . . . . 21What Is CandleNet Portal?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23What Is OMEGAMON XE for WebSphere MQ Configuration? . . . . . 24Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . 30

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

Chapter 3. Prototyping Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . 47About Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . 50Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . 53Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . 54Introducing Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Using the Global Variables Workspace. . . . . . . . . . . . . . . . . . . . . . . . 58Adding, Modifying, or Deleting Global User Variables . . . . . . . . . . . . 59Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . 61

Contents


Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . 63Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 4. Creating and Defining Objects . . . . . . . . . . . . . . . . . . . . . . . . .69What Are Defined Objects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Using the Configuration Search Facility . . . . . . . . . . . . . . . . . . . . . . . 72Creating New Queue Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Setting Access Authority for WebSphere MQ Objects. . . . . . . . . . . . . 81Connecting Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Creating Resource Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Copying and Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Using the Replicate Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 5. Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .95Validating Objects in the Defined View . . . . . . . . . . . . . . . . . . . . . . . 96Controlling the Amount of Validation Testing. . . . . . . . . . . . . . . . . . . 99

Chapter 6. Maintaining Your Configuration . . . . . . . . . . . . . . . . . . . . . . .103Maintaining Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Viewing Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Updating the Configuration Databasefrom Your Actual Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Backing Up the Configuration of the Actual Environment . . . . . . . . 109Updating Your Actual Configuration from Defined Objects . . . . . . . 110Exporting or Importing XML Data . . . . . . . . . . . . . . . . . . . . . . . . . . 112Exporting MQSC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 7. Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119About Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Scheduling an Action/Defining a Scheduled Action . . . . . . . . . . . . . 121Scheduled Action Summary Report . . . . . . . . . . . . . . . . . . . . . . . . 124Scheduled Action Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Scheduled Action Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Running a Schedule on Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Contents 5

Chapter 8. Creating and Defining Clusters . . . . . . . . . . . . . . . . . . . . . . . .129About the Cluster Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Clustering Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Product-Managed Configuration Objects . . . . . . . . . . . . . . . . . . . . . 134Creating a New Managed Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 135Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 9. Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Audit Logging Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Audit Log Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Chapter 10. Backing Up the Configuration Database . . . . . . . . . . . . . . . . .155Backing up the configuration database . . . . . . . . . . . . . . . . . . . . . . 156Restoring the configuration database. . . . . . . . . . . . . . . . . . . . . . . . 158

Appendix A. Remote Queue Manager Configuration . . . . . . . . . . . . . . . . .161What Is Remote Configuration?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Setting Up Queue Managers for Remote Configuration . . . . . . . . . . 165Examples of Possible WebSphere MQ Configurations . . . . . . . . . . . 168Creating Remote Queue Manager Objects. . . . . . . . . . . . . . . . . . . . 172

Appendix B. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181

Preface 7

Preface

Welcome to the OMEGAMON® XE for WebSphere MQ Configuration User’s Guide. This guide provides detailed information about using CandleNet Portal® to set up the OMEGAMON environment to quickly define and manage your WebSphere MQ network.

P

About This Book


About this Book

Who should read this bookThis guide is intended to provide system administrators of WebSphere MQ with the processes involved in preparing 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 guide is designed to complement the online help that is provided with the product.

Where to look for more informationFor more information related to this product and other related products, please see the

� technical documentation CD-ROM that came with your product

� technical documentation information available on the Candle Web site at www.candle.com

� online help provided with this and the other related products

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department. You can also send email to [email protected]. Please include "OMEGAMON XE for WebSphere MQ Configuration User’s Guide, V360" in the subject line.

https://www.candle.com/www1/techdocs/red.html

Preface 9

Adobe Portable Document Format


Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options for� All� Current page� Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:� settings for your printer and printer driver. (The dpi settings for both your

driver and printer should be the same. A setting of 300 dpi is recommended.)

� the printer driver you are using. (You may need a different printer driver or the Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

� the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

� the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.

About This Book


Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

Adding annotations to PDF filesIf you have purchased the Adobe Acrobat application, you can add annotations to Candle documentation in .PDF format. See the Adobe product for instructions on using the Acrobat annotations tool and its features.

http://www.adobe.com

Preface 11


Documentation Conventions

IntroductionCandle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

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 literals in command syntax examplesIn examples of command syntax for the OS/390, VM, OS/400, and NonStop Kernel platforms, uppercase letters indicate actual values (literals) that the user should type; lowercase letters indicate variables that represent data supplied by the user:

LOGON APPLID (cccccccc)

However, for the Windows and UNIX platforms, variables are shown in italics:

-candle.kzy.instrument.control.file=instrumentation_control_file_name-candle.kzy.agent.parms=agent_control_file_name

Note: In ordinary text, variable names appear in italics, regardless of platform.

About This Book


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 | NOIn 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.

{ } 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.

Preface 13


Candle Customer Service and Satisfaction

BackgroundTo assist you in making effective use of our products, Candle offers a variety of easy-to-use online support resources. The Candle Web site provides direct links to a variety of support tools that include these services:

eSupport allows you to create and update service requests opened with Customer Service and Satisfaction (CSS).

eDelivery allows you to download products, documentation, and maintenance 24 hours a day, 7 days a week.

eNotification notifies you of product updates and new releases.

In addition, you can find information about training, maintenance plans, consulting and services, and other useful support resources. Refer to the Candle Web site at www.candle.com for detailed customer service information.

Candle Customer Service and Satisfaction contactsYou will find the most current information about how to contact Candle CSS by telephone or email on the Candle Web site. Go to the www.candle.com support section, and choose the link to Support Contacts to locate your regional support center.

http://www.candle.comhttp://www.candle.com

About This Book


What’s New in Version 360 15

What’s New in Version 360

This product (formerly known as Candle Command Center™ for MQSeries Configuration) has been renamed to OMEGAMON® XE for WebSphere MQ Configuration. You will see the new name in the product help and documentation.

The enhancements to OMEGAMON XE for WebSphere MQ Configuration provided by Version 360 are:

� Gives you the ability to export files from the configuration database in MQSC commands format. See “MQSC commands export” on page 116.

� Exploits the enhanced functionality and ease-of-use provided by the CandleNet Portal® user interface. Detailed procedures for using the configuration product appear throughout this guide. CandleNet Portal is described in the online Help, the Using OMEGAMON Products: CandleNet Portal guide, and the Administering OMEGAMON Products: CandleNet Portal guide.

� Enhanced integration with the OMEGAMON XE for WebSphere MQ Monitoring product. If you purchased the OMEGAMON DE feature package for CandleNet Portal®, and if you run both the Configuration Agent for WebSphere MQ and the Monitoring Agent for WebSphere MQ on the same system, then from selected workspaces in OMEGAMON XE for WebSphere MQ Monitoring you can directly configure queue managers and resources defined in OMEGAMON XE for WebSphere MQ Configuration. This allows you to quickly change the parameters of selected WebSphere MQ objects if you detect a problem. This is described in the OMEGAMON XE for WebSphere MQ Monitoring User’s Guide.

W

About This Book


Documentation changes for this release include:

� An HTML-based online help system.

� The Customization Guide, available with this product’s V350 release, is discontinued. Information about initial configuration and customization on OS/390 and z/OS only has moved to the OMEGAMON XE for WebSphere MQ Configuration and Monitoring on OS/390 and z/OS Configuration and Customization Guide shared by OMEGAMON XE for WebSphere MQ Monitoring and OMEGAMON XE for WebSphere MQ Configuration.

Introducing OMEGAMON XE for WebSphere MQ Configuration 17

Introducing OMEGAMON XEfor WebSphere MQ Configuration

IntroductionThis chapter provides an overview of this product’s 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 OMEGAMON XE for WebSphere MQ Configuration work together to help you ensure a cohesive network whose interrelationships are correctly defined.

Chapter contentsGetting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18What Are OMEGAMON XE and OMEGAMON DE? . . . . . . . . . . . . . . . . 21What Is CandleNet Portal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23What Is OMEGAMON XE for WebSphere MQ Configuration? . . . . . . . . . 24Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . . . . . 30

1

Getting Started


Getting Started

Additions to CandleNet Portal to support configurationOMEGAMON XE for WebSphere MQ Configuration uses the CandleNet Portal® interface and adds the Configuration navigator view and the WebSphere MQ Configuration Authorities item.

The very first time you log on to OMEGAMON XE for WebSphere MQ Configuration, you may need to add the Configuration view to your list of available Navigator views (and later, you may need to ensure that other users have the appropriate views assigned and have appropriate WebSphere MQ Configuration authority assignments). Here’s how:

1. Log on to CandleNet Portal and, from the List of available Navigator Views, select Configuration.

2. If Configuration does not appear in your List of available Navigator Views, proceed to Step 3.

3. Open the Administer Users dialog (or ask your system administrator to open it for you), select your User ID, then select the Navigator Views tab.


Getting Started

4. 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.

5. While in the the Administer Users dialog, select the Permissions tab and scroll down the list of Authorities. Here OMEGAMON XE for WebSphere MQ Configuration adds the WebSphere MQ Configuration Authorities item, as shown in the next illustration. Your User ID requires the Modify permission (Modify includes View) in order to change your site’s WebSphere MQ configuration or to schedule configuration updates using the configuration product (which may include access from the OMEGAMON XE for WebSphere MQ Monitoring product by means of enhanced integration as mentioned in “What’s New in Version 360” on page 15).

Getting Started


6. Click OK to save and exit the dialog.

7. 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 OMEGAMON XE for WebSphere MQ Configuration (it can also be accessed by means of enhanced integration with the monitoring product as mentioned in “What’s New in Version 360” on page 15.) This guide describes what you can do in the Configuration view.


What Are OMEGAMON XE and OMEGAMON DE?


What OMEGAMON XE doesOMEGAMON XE is a suite of Candle® products that monitor and manage system and network applications on a variety of platforms. These products keep track of the availability and performance of all parts of your enterprise from one or more designated workstations, and provide reports you can use to track trends and troubleshoot problems.

Components of the OMEGAMON XE platformThe client/server/agent implementation includes

� a client, CandleNet Portal, with a Java-based user interface for viewing and monitoring your enterprise. CandleNet Portal offers two modes of operation: desktop and browser.

� a CandleNet Portal server that retrieves, manipulates, and analyzes data from the Candle agents in your enterprise

� a CMS, which acts as a collection and control point for alerts received from the agents, and collects their performance and availability data

� Candle monitoring agents installed on the systems or subsystems you want to monitor. These agents collect and distribute data to a CMS.

� Candle configuration agents installed on the systems you want to configure. These agents create and configure objects. The configuration agent associated with OMEGAMON XE for WebSphere MQ Configuration configures objects such as WebSphere MQ queue managers and all their components (queues, channels, processes, and so on).

What OMEGAMON DE doesOMEGAMON DE offers a dashboard view of your enterprise. It gives you a single point of control for managing the resources your business-critical applications rely on, including a range of operating systems, servers, databases, mainframes, and Web components. For example, a typical IT network might have a Web server running on Windows NT, an application server running on UNIX, a database on OS/390, and a transaction processor on CICS on the mainframe. OMEGAMON DE brings all these views together



in a single window, so you can see when any component is not working as expected.

OMEGAMON DE Policy ManagementThe CandleNet Portal V195 Policy Management solution incorporates all the features of 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.


What Is CandleNet Portal?

What Is CandleNet Portal?

What CandleNet Portal doesCandleNet Portal is the interface into your OMEGAMON XE products. In the same way you use your browser home page as a starting point for navigating the Internet, you use CandleNet Portal to get a high-level overview of your network environment. One section of the window displays the Navigator, a tree-like view of your monitored network, with alert icons that appear when problems arise. The rest of the window is filled with views pertinent to the chosen item in the Navigator tree. From the top level or from your home workspace, you can navigate to specific locations to check activity and investigate problems.

Modes of operationCandleNet Portal offers two modes of operation:

� desktop mode, in which the CandleNet Portal client is installed on your workstation and runs as a desktop application.

� browser mode, in which the system administrator installs the CandleNet Portal client on the Web server, and you start CandleNet Portal from your browser. In browser mode, thin client software is downloaded to your system the first time you log on to CandleNet Portal, and thereafter only when there are software updates.

When using CandleNet Portal in browser mode, you can start it from any workstation by entering the URL for the Web server where the browser mode client is installed. Each CandleNet Portal workspace also has a URL, so that you can save the workspace to your Favorites list or specify it as your home page.

For more about CandleNet PortalYou can find detailed instructions for using CandleNet Portal in

� the CandleNet Portal online Help

� Using OMEGAMON Products: CandleNet Portal

� Administering OMEGAMON Products: CandleNet Portal

What Is OMEGAMON XE for WebSphere MQ Configuration?



Product packages that include this agentThe OMEGAMON configuration agent for WebSphere MQ is included in these Candle product packages:

� PathWAI Dashboard for WebSphere Business Integration

� PathWAI Monitor for WebSphere MQ

� PathWAI Tuning Workbench for WebSphere Business Integration

� PathWAI Dashboard for WebSphere Infrastructure (optional component)

What 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.

OMEGAMON XE for WebSphere MQ Configuration simplifies the time-consuming and resource-intensive tasks of defining your configuration. You can use OMEGAMON XE for WebSphere MQ Configuration to:

� 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



This guide provides information on the features and tools that 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, 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 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, OMEGAMON XE for WebSphere MQ Configuration provides a representation of your WebSphere MQ configuration called the Defined View. Defined objects in this view represent current or potential WebSphere MQ resources—queue managers, channels, queues, processes, namelists, and so on, all under the management of 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, 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. 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, 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 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. 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 best practise 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, 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 119.

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:

� Update defined from actual

� Update actual from defined



� View discrepancies

� Delete (defined, actual, or both actual and defined)

� Validate

� Discover new resources

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 OMEGAMON XE for WebSphere MQ Monitoring

A sibling product of OMEGAMON XE for WebSphere MQ Configuration, 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.

OMEGAMON XE for WebSphere MQ Configuration and OMEGAMON XE for WebSphere MQ Monitoring are separate products and can be used independently of one another. However, when used together, one product enhances the other. CandleNet Portal® integrates the monitoring functions provided by OMEGAMON XE for WebSphere MQ Monitoring with the configuration functions provided by 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 OMEGAMON XE for WebSphere MQ Monitoring can help you configure your WebSphere MQ network for maximum efficiency. For example, OMEGAMON XE for WebSphere MQ Monitoring can help you determine if there are any bottlenecks in your configuration and you can then use 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 80.

Putting All the Pieces Together: A Typical Scenario



OverviewThis section presents a scenario that may help you understand how the features of OMEGAMON XE for WebSphere MQ Configuration work together to help you build your WebSphere MQ network. At this point, you won’t need to know exactly how each task is performed—subsequent chapters describe these tasks in detail. Instead, note how the company in the scenario uses the power of 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 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:

� 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.

BackgroundBefore you installed 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 OMEGAMON XE for WebSphere MQ Configuration, you want to use its features to minimize the cost of:

� 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.

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

Because the planned configuration will comprise sets of four queues on each of the 7 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 OMEGAMON XE for WebSphere MQ Configuration to test the defined configuration. Once you are satisfied with the results, use OMEGAMON XE for WebSphere MQ Configuration to update the actual WebSphere MQ configuration with a few clicks of the mouse.



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, OrderEntryQn on System Y, where n is a number from 1–4, and Y is the AIX nodename. 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 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 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 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 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 select Update actual from defined from the pop-up menu.

By default, OMEGAMON XE for WebSphere MQ Configuration 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 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 OrderEntryQ5 on System Y for the name of defined objects based on the prototype.

2. You add ProtoOrderEntry5 to the resource group prototype ProtoOrderEntryGroup. 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 OMEGAMON XE for WebSphere MQ Configuration validates updates to an actual configuration before implementing them, you can run the Update actual from defined feature on the entire configured system group without first validating the change you just made to seven AIX systems.

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.

Viewing Your Current WebSphere MQ Configuration 37

Viewing Your CurrentWebSphere MQ Configuration

IntroductionThis 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.

Chapter contentsCreating Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Entering Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Creating a Configured System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Discovering Your Existing WebSphere MQ Configuration . . . . . . . . . . . . . 42Reviewing Your Defined View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2

Creating Your Defined View


Creating Your Defined View

About 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 site’s actual WebSphere MQ queue managers, and resources.

You can initially build this representation by one of two methods:

� 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 OMEGAMON XE for WebSphere MQ Configuration. See “What Are Defined Objects?” on page 70.

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 39.

2. Creating a new configured system group, as described on page 40.3. Using the Discover feature to populate the configuration database with

defined objects representing your actual WebSphere MQ configuration, as described on page 42.

4. Reviewing the graphical representation of your WebSphere MQ configuration, as described on page 45.


Entering Update Mode

Entering Update Mode

What 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:

� Change your Defined View, including using the configuration database to update your actual configuration (as described in “Maintaining Your Configuration” on page 103) 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 47.

� Use the Global Variables workspace to create, delete, and change the values assigned to your site’s global user variables. See “Introducing Variables” on page 56.

� Backup and restore the configuration database. See “Backing Up the Configuration Database” on page 155

Before you can enter update mode

To 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.

Procedure To enter update mode:

1. Ensure you are viewing OMEGAMON XE for WebSphere MQ Configuration.In CandleNet Portal’s List of available Navigator Views, the Configuration view is selected.

2. In the configuration navigator tree, select Configuration (the root-level item).The Update mode checkbox displays in the Configuration workspace.

3. Select the Update mode checkbox.

Creating a Configured System Group



What is a configured system group?A configured system group is a unit of organization within 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 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.

Procedure To create a new 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 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.



4. 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.

5. In the defined view tree, select the new configured system group.The settings list for the object displays on the right side of the Defined View.

6. Complete the settings list as necessary.Click Help to display information about each parameter.

7. Click Save to save your changes.

Discovering Your Existing WebSphere MQ Configuration



What the discover process doesThe Discover process populates your Defined View with data from existing queue managers. When you run the Discover process, 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.

Considerations A few key points about the Discover feature:

� The Discover feature processes only new queue managers on systems running an OMEGAMON Configuration Agent (OCA) 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 OCA 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 OCA 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 107.

– Go to the queue manager settings list, expand the Auto Start section, and activate the Auto start checkbox. Then perform an Update defined from actual, see “Updating the Configuration Database from Your Actual Configuration” on page 107.



� 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 OMEGAMON XE for WebSphere MQ Configuration Help.

� 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 Discover Lite product option (in the Product Options area of the Configuration workspace). By default, Discover Lite is disabled. For more details see the OMEGAMON XE for WebSphere MQ Configuration Help.

� The terms Discover and Discovery describe the default Discover process of OMEGAMON XE for WebSphere MQ Configuration unless specifically noted in this guide.

Procedure

Warning:

Depending on your WebSphere MQ configuration, this can be a lengthy procedure and it is not interruptible once begun.

To search your site’s WebSphere MQ network for queue managers and add them to the current configured system group:


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.OMEGAMON XE for WebSphere MQ Configuration searches your site’s 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, OMEGAMON XE for WebSphere MQ Configuration creates a resource group named $Default_Group, and the queue manager’s resources are added to that resource group.



When the Discover process is complete, OMEGAMON XE for WebSphere MQ Configuration displays a report containing information about the Discovery.


Reviewing Your Defined View


OverviewAfter 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 configuration–queue 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 84 for more information about resource groups.

Prototyping Your Configuration 47

Prototyping Your Configuration

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

Chapter contentsAbout Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . . . . . 50Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . . . . 53Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . . . . 54Introducing Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Using the Global Variables Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Adding, Modifying, or Deleting Global User Variables. . . . . . . . . . . . . . . . 59Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . 63Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3

About Prototypes


About Prototypes

Why use prototypes?Prototyping allows you to design and plan your WebSphere MQ configuration. Sample prototype objects are provided. You can 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.

� 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.

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


About Prototypes

� Configured System Prototypes, which represent queue managers and managed clusters.

� Resource Group Prototypes, which allow you to gather resources into logical groups.

� 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 54.

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.

Creating Prototypes in the Prototype View



OverviewYou 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, OMEGAMON XE for WebSphere MQ Configuration 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:

� 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 51.

� 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 51.

� 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: An additional pop-up menu option allows you to create resources directly within configured systems. When you drag and drop a prototype directly to a prototype aggregate, the product determines whether the resource is being copied directly to the aggregate, or whether you want to create a reference object back to the prototype being dragged. The default is to create a reference. However, if you use the right mouse button for the drag/drop, and select Copy from the resulting pop-up menu, then the prototype is copied directly to the aggregate, and no reference object is created.The use of prototype references within a prototype is still supported.

ProcedureTo create a new prototype in the Prototype View:


2. Open the Prototype View.

3. In the prototype view tree, use one of the following options:� 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.

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, OMEGAMON XE for WebSphere MQ Configuration appends the number 1 to the prototype object. If you create another prototype object with the same name again,



OMEGAMON XE for WebSphere MQ Configuration 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.



Creating Prototypes from Defined Objects

Creating Prototypes from Defined Objects

OverviewYou 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:


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. While holding down the mouse button, 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.

Dragging Prototype Objects to the Defined View



OverviewAfter 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:

� 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.



ProcedureTo create an instance of a prototype in the Defined View:


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. While holding down the mouse button, 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 110.

Introducing Variables



OverviewWhen used with prototypes, variables ensure consistency throughout your configuration and can help you quickly identify objects that may be based on the same prototype.

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 object’s 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 show resolved global variables or symbolic variables in the Defined View using the Show Resolved menu option. For more information see “Showing resolved variables” on page 66.

Product-provided global variablesOMEGAMON 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 variablesOMEGAMON 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.

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 the 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.

Using the Global Variables Workspace


Using the Global Variables Workspace

OverviewUse the Global Variables workspace to view the global user variables currently defined for your 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 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 site’s global user variables in a report-like format. The workspace lists the following for each variable:

� Variable The name of the global user variable.� Value The value that the variable resolves to.

� Description An optional text description of the variable.


Adding, Modifying, or Deleting Global User Variables


GuidelinesUse these guidelines when adding, modifying, or deleting global user variables:

� 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.

Adding a global user variableTo add a global user variable:


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.



Modifying a global user variableTo modify a global user variable:



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.


Deleting a global user variableTo delete a global user variable:



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.



Adding Global Variables to Prototypes


OverviewThis section provides an example that you can use to add global variables to prototypes.

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

� 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

� 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 to

MQ.lwallNew_Queue



Example In 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.


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


Adding Symbolic Variables to Prototypes

Adding Symbolic Variables to Prototypes

OverviewThis section provides an example that you can use to add symbolic variables to prototypes.

Guidelines Use these guidelines when adding symbolic variables to prototypes:

� 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 of the settings list.

� You can use a symbolic variable in any text field of a settings list.

� When you use a symbolic variable in the text field of a settings list, it must be preceded by an ampersand (&).

� To string variables together or add additional descriptive text, use a period to indicate the end of a variable name.

� You can override symbolic variables for a particular object if necessary after it is in the Defined View. See “Overriding assigned symbolic variables” on page 65.

Example The following example shows how to specify and use symbolic variables in prototype objects.

1. Create a queue manager prototype and name it:Satelite.Queue.Manager.Proto

Date post:	19-Feb-2021
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

OMEGAMON XE for WebSphere MQ Configഀ甀爀愀琀椀漀渀 唀猀...

Documents

OMEGAMON XE for WebSphere MQ Configഀ甀爀愀琀椀漀渀唀猀...