configuration and customization...

Configuration and Customization GuideOMEGAMON XE® for WebSphere MQ

Configuration on OS/390 and z/OS Version 360

OMEGAMON XE for WebSphere MQMonitoring on OS/390 and z/OS

Version 360

GC32-9329-00

October 2003

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 OMEGAMON XE for WebSphere MQ Configuration and Monitoring on OS/390 and z/OS CCG

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 © October 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

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

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

Chapter 1. Start Here to Configure Your Product . . . . . . . . . . . . . . . . . . . .17Using the Checklists and Topics in this Chapter . . . . . . . . . . . . . . . . . 18Checklist: Prerequisites for Configuring Your Product . . . . . . . . . . . . 20Checklist: Starting CICAT and Accessing the Menu for Configuration 21Checklist: Configuring OMEGAMON XE for WebSphere MQ Monitoring Using CICAT . . . . . . . . . . . . . . . . . 22Checklist: Configuring OMEGAMON XE for WebSphere MQ Configuration Using CICAT . . . . . . . . . . . . . . . 25Checklist: Configuring Your Product Outside of CICAT . . . . . . . . . . . 29Checklists: Customizing Your Product Outside of CICAT . . . . . . . . . . 31Checklist: Updating Your Configuration. . . . . . . . . . . . . . . . . . . . . . . 32Using Advanced Features in CICAT. . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 2. Overview of Processes, Methods, and CICAT Modes . . . . . . . .35Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 36Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Processes for Installing, Configuring, and Maintaining Products. . . . . 38Background about CICAT Modes: Interactive and Batch . . . . . . . . . . 43

Chapter 3. Plan Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Candle Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . 46Details about the Candle Products and Components. . . . . . . . . . . . . 48Determining the Components to Install and Configure . . . . . . . . . . . 50

Contents


Requirements to Review Before Configuring Your Product . . . . . . . . 52Considerations and Requirements for OMEGAMON XE for WebSphere MQ Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4. Start CICAT and Access the Menu for Configuring . . . . . . . . . 57Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 58Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Accessing the Menu for Configuring the Product . . . . . . . . . . . . . . . . 60Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5. Completing the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . .63Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 64Copying the Procedures for the Started Task . . . . . . . . . . . . . . . . . . . 65Copying the VTAM Definition and Varying the VTAM Node Active . . 66APF-authorizing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Copying the Procedures for the Persistent Datastore . . . . . . . . . . . . . 68Seeding the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . 74Verifying the Configuration: Different Address Space. . . . . . . . . . . . . 75Verifying the Configuration: CMS on a Different Platform . . . . . . . . . 76

Chapter 6. Completing the Customization . . . . . . . . . . . . . . . . . . . . . . . . .77Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 78Granting Authorizations to the Monitoring and Configuration Agents 79Monitoring CICS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Multi-level Security: Reviewing Configuration Database Security. . . . 83Multi-level Security: Implementing Configuration Database Security . 94

Chapter 7. Managing and Updating the Configuration . . . . . . . . . . . . . . . . 97Updating and Changing the Configuration . . . . . . . . . . . . . . . . . . . . 98

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Tables 5

Table 1. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 2. Advanced Features Available in CICAT . . . . . . . . . . . . . . . . . . . . . . . 33Table 3. Installing Products and Maintenance: A Comparison . . . . . . . . . . . . . 38Table 4. Installing and Configuring: A Comparison . . . . . . . . . . . . . . . . . . . . . 39Table 5. Example Tasks for Installing, Maintaining, and Configuring . . . . . . . . 40Table 6. Locating Information for Installing and Configuring. . . . . . . . . . . . . . 41Table 7. CICAT Modes: Interactive and Batch. . . . . . . . . . . . . . . . . . . . . . . . . 43Table 8. Overview of Candle Products and Components . . . . . . . . . . . . . . . . 46Table 9. Details about the Relationships and CMS Types . . . . . . . . . . . . . . . . 48

Table 10. Products and Components You Will Need . . . . . . . . . . . . . . . . . . . . . 50Table 11. Products and Components to Configure . . . . . . . . . . . . . . . . . . . . . . 51Table 12. Guidelines for Seeding the CMS for Products on MVS . . . . . . . . . . . 70Table 13. Profile Naming Conventions for Defined Configuration Objects . . . . 87Table 14. Profile Naming Conventions for Prototype Configuration Objects . . . 90Table 15. Profile Naming Conventions for Tasks . . . . . . . . . . . . . . . . . . . . . . . . 91

Tables

Preface 7

Preface

This manual covers the configuration and customization on OS/390 and z/OS for both of the following products:

� OMEGAMON XE® for WebSphere MQ Monitoring, Version 360 (renamed from Candle Command Center for MQSeries)

� OMEGAMON XE for WebSphere MQ Configuration, Version 360 (renamed from Candle Command Center for MQSeries Configuration)

This manual contains:

� a set of checklists you can use to complete the steps required to configure and customize the products

� an overview of the process for installing and configuring all Candle products and components

� the planning information you should review before you configure the products and components

� information about using the Candle Installation and Configuration Assistance Tool (CICAT) to configure the products and components

� the step-by-step instructions to follow to complete the manual configuration outside of CICAT and manual customization outside of CICAT (if any)

� the step-by-step instructions to follow to update or change the configuration

P

About This Book


About This Book

Who should read this guideThis guide is intended for users of the OMEGAMON XE for WebSphere MQ products, including product administrators and systems programmers.

Documentation set information

How to use this guideThis guide is designed to help new and experienced customers.

If you are a new customer, you can use:

� the chapters in the order they are included in this guide (The information and tasks are listed in the order they are needed or performed.)

� the checklists in Chapter 1 to verify that you have completed the steps required to configure the product and locate specific information or procedures (if needed)

If you are an experienced customer, you can use the checklists in Chapter 1 to verify that you have completed the steps required to configure and customize the product and locate specific information or procedures (if needed)

Product You Are Configuring Product-specific Documentation Provided

OMEGAMON XE for WebSphere MQ Monitoring

� User’s Guide, MQ54-6630� Configuration and Customization Guide

on OS/390 and z/OS, MQ51-6631

OMEGAMON XE for WebSphere MQ Configuration

� User’s Guide, MC54-6710� Configuration and Customization Guide

on OS/390 and z/OS, MQ51-6631

Preface 9

About This Book

Determining the chapters to use in this guide The table shows the type of information covered in this guide and the chapters that contain the type of information.

Where to look for more informationFor more information about a Candle product, see:

� online help

� technical documentation CD-ROM (if one came with the product)

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

Chapter to Use

Type of Information You Need 1 2 3 4 5 6 7

Checklists that you can use to verify that you have completed all the steps in the broad process for configuring products and maintenance (Recommended for all new and experienced customers.)

!

Background about CICAT !

Definitions for Candle terminology !

Overview of the entire process for installing and configuring Candle products and maintenance

!

Prerequisites you must complete before configuring the product and following the procedures in this guide

!

Procedures to follow to start CICAT and access the menu to configure the product

!

Procedures to follow outside of CICAT to configure the product and to verify that the configuration is complete by starting the product and components

!

Procedures to follow outside of CICAT to customize the product for your site (In most cases, these steps are optional.)

!

Procedures to follow to update or change the configuration !

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

About This Book


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 and Monitoring on OS/390 and z/OS CCG" in the subject line.

Preface 11

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.



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 13

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 literalsIn examples of 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.

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



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 15

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

http://www.candle.com

Start Here to Configure Your Product 17

Start Here to ConfigureYour Product

IntroductionThis chapter contains a checklist or topic for each of the steps in the process for configuring products and maintenance, that you can use to:

� guide you through the steps in the process for configuring and customizing products and components

� verify that you have used all of the options in CICAT required for your specific situation

� verify that you have completed all the required steps outside of CICAT to configure and customize the products and components

� locate detailed information when you need background information or step-by-step instructions for a specific task

Chapter contentsUsing the Checklists and Topics in this Chapter. . . . . . . . . . . . . . . . . . . . . 18Checklist: Prerequisites for Configuring Your Product . . . . . . . . . . . . . . . . 20Checklist: Starting CICAT and Accessing the Menu for Configuration . . . . 21Checklist: Configuring OMEGAMON XE for WebSphere MQ Monitoring

Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Checklist: Configuring OMEGAMON XE for WebSphere MQ Configuration

Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Checklist: Configuring Your Product Outside of CICAT. . . . . . . . . . . . . . . 29Checklists: Customizing Your Product Outside of CICAT. . . . . . . . . . . . . . 31Checklist: Updating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 32Using Advanced Features in CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1

Using the Checklists and Topics in this Chapter



Determine the checklists and topics to use This chapter contains a checklist or topic for each of the steps in the process for installing, maintaining, and configuring products. In most cases, there is a checklist you can use to verify that you have completed all the tasks.

The following table shows the checklist or topic you should use for your tasks.

Task Checklists and Topics to Use in this Chapter Page #

Complete the configuration of the product or maintenance

! Checklist: Prerequisites for Configuring Your Product page 20

! Checklist: Starting CICAT and Accessing the Menu for Configuration

page 21

! Checklist: Configuring OMEGAMON XE for WebSphere MQ Monitoring Using CICAT

page 22

! Checklist: Configuring OMEGAMON XE for WebSphere MQ Configuration Using CICAT

page 25

! Checklist: Configuring Your Product Outside of CICAT page 29

! Checklists: Customizing Your Product Outside of CICAT

page 29

! Checklist: Updating Your Configuration page 32

! Using Advanced Features in CICAT page 33

Update or change the configuration for the product

! Checklist: Starting CICAT and Accessing the Menu for Configuration

page 21

! Checklist: Updating Your Configuration page 32

! Using Advanced Features in CICAT page 33



How to use the checklists The tasks in the checklists are listed in the order they are performed. You use:

� the first column with the box to track the tasks you complete

� the next column(s) to determine the task

� the last column to locate background information or step-by-step instructions in the resources provided with the product (such as the online help and this guide)

If you are not familiar with Candle, CICAT, or the processIf you are not familiar with Candle terminology, CICAT, or the process of installing, maintaining, and configuring products, see Chapter 2 in this guide.

Checklist: Prerequisites for Configuring Your Product


Checklist: Prerequisites for Configuring Your Product

Who should use this checklistUse this checklist if you are configuring and customizing:

� OMEGAMON XE for WebSphere MQ Configuration

� OMEGAMON XE for WebSphere MQ Monitoring

Checklist: Prerequisites for configuring products The checklist contains the prerequisite actions you must have completed before you can begin to configure the product.

✓ Prerequisite Location of Information

! If you have not already done so, verify for the product you want to configure that:

! you have the required software

! you have the required DASD space

! the product versions can exist in the same CSI

Installation & Configuration of Candle Products on OS/390 and z/OS

! You must have installed the product and components using CICAT.

� Installation & Configuration of Candle Products on OS/390 and z/OS

� the online help in CICAT ! You must have created a runtime environment (RTE)

using CICAT.

! You must have completed the configuration for a Candle Management Server® (CMS).

� Candle Management Server Configuration and Customization Guide

� the online help in CICAT

! If this is the first time you have used Candle products or you are not familiar with the terminology, CICAT, or the process, review an overview.

Chapter 2 in this guide

! If this is the first time you have used Candle products or you do not know the configuration you want, review the background, planning information, and migration information (if any).



Checklist: Starting CICAT and Accessing the Menu for Configuration

Checklist: Starting CICAT and Accessing the Menu for Configuration




Checklist: Start CICAT and access the configuration menuThe checklist contains the steps you perform to start CICAT and access the configuration menu.

✓ TaskLocation of Information

! Using TSO, start CICAT by executing shilev.INSTLIB. Chapter 4 in this guide

! On the CICAT Main Menu, select Configure products and complete the following options on the menu.

! If this is the first time you have used CICAT V300 to configure a Candle product, use Set up configuration environment to specify values that CICAT will use to build the JCL that allocates the runtime data sets for all the products you are configuring.

! Use Select product to configure to display a list of the products available and to select the product you want to configure using the S (Select product) select.

! On the Runtime Environments (RTEs) panel, either:

– if you want to configure an existing RTE, type C (Configure) in the Action field for the RTE

– if you want to create a new RTE, type A (Add) in the Action field and specify the values for the new RTE

! If you are configuring a product that communicates with the CMS, on the Product Configuration Selection Menu enter the selection number of the product or component.


Checklist: Configuring OMEGAMON XE for WebSphere MQ Monitoring Using CICAT



Who should use this checklistUse this checklist if you are configuring OMEGAMON XE for WebSphere MQ Monitoring.

Checklist: Configure OMEGAMON XE for WebSphere MQ Monitoring using CICAT

The following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE for WebSphere MQ Monitoring.

✓ Location in CICAT

Configuration Step to Perform in CICAT

Location of Information

! Configure OMEGAMON XE for WebSphere MQ Monitoring Menu

Use Register with local CMS to enable the OMEGAMON XE for WebSphere MQ Monitoring product, by registering it to the local CMS.

Online help in CICAT


Use Specify configuration parameters to specify� your WebSphere MQ authorized load

library and language library� monitoring characteristics for the

DEFAULT monitoring groupNote: Retain the default values until you verify the installation and configuration.





If you are defining an agent to run in an agent address space, use Specify Agent address space parameters to provide information required to create the address space and communicate with the CMS.

! If this is a new agent to be configured in the agent address space:

– Specify the configuration values for the agent address space.

– Specify advanced agent configuration values, by using the Advanced key (F5).

– Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent address space to support.

! If this is the second or third agent to be configured in the agent address space, on the Agent Address Space Selection panel:

– To share an existing agent address space, type S (Select) next to the address space name and then use Create runtime members to generate the job that updates the runtime members for the agent address space.

– To add a new agent address space, type A (Add) in the Action field and use the steps for configuring a new agent in the agent address space.

Note: If the agent is already configured to share an agent address space, a message showing the agent address space owner appears in the upper right corner of the Configure panel.


and

“Requirements to Review Before Configuring Your Product” on page 52


If you are defining an agent to run in an agent address space, use Create runtime members to generate the job that creates the runtime members for the agent address space.







Determine what to do nextSee “Checklist: Configuring Your Product Outside of CICAT” on page 29.


If you are defining an agent to run in an agent address space, use Configure persistent datastore to specify values for allocating and managing a persistent data store for the agent address space.

This option is required if you:� will be enabling historical data collection

on CandleNet Portal.� configured the CT/PDS for a previous

version of the WebSphere MQ Monitoring product in this RTE.



If you are defining an agent to run in the CMS address space, use Install Agent into local CMS to generate the job that installs the agent into the specified CMS.



If you are defining an agent to run in the CMS address space, use Configure persistent datastore to specify values for allocating and managing a persistent data store for the CMS address space.



Use Complete the Configuration to display a set of instructions for completing the configuration outside of CICAT. (The instructions are also covered in this guide.)


and

“Completing the Configuration” on page 63

! Runtime Environments (RTEs) panel

Use L (Load libs after SMP/E) to load all the libraries used by the RTE.






Checklist: Configuring OMEGAMON XE for WebSphere MQ Configuration Using CICAT


Who should use this checklistUse this checklist if you are configuring OMEGAMON XE for WebSphere MQ Configuration.

Checklist: Configure OMEGAMON XE for WebSphere MQ Configuration using CICAT

The following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE for WebSphere MQ Monitoring.




! Configure OMEGAMON XE for WebSphere MQ Configuration Menu

Use Register with local CMS to enable the OMEGAMON XE for WebSphere MQ Configuration product, by registering it to the local CMS.



Use Configure persistent datastore to specify values for allocating and managing a persistent data store for the CMS address space.





Use Specify configuration parameters to specify� your WebSphere MQ authorized load

library and language library� whether you want to collect enhanced

audit log information� the nodename the agent will use to connect

to the CMS (default is KMC_DEFAULT)

! If you change the MC agent nodename, you must use Register with local CMS to re-register the product to the local CMS.

! If you are connecting an agent to a remote CMS or a CMS in another RTE, and you change the MC agent nodename:

– Use Specify configuration parameters to specify the MC agent nodename on the remote CMS or CMS on the other RTE.

– Use Register with local CMS to re-register the product to the local CMS.








If you are defining an agent to run in an agent address space, use Specify Agent address space parameters to provide information required to create the address space and communicate with the CMS.

! If this is a new agent to be configured in the agent address space:

– Specify the configuration values for the agent address space.

– Specify advanced agent configuration values, by using the Advanced key (F5).

– Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent address space to support.

! If this is the second or third agent to be configured in the agent address space, on the Agent Address Space Selection panel:

– To share an existing agent address space, type S (Select) next to the address space name and then use Create runtime members to generate the job that updates the runtime members for the agent address space.

– To add a new agent address space, type A (Add) in the Action field and use the steps for configuring a new agent in the agent address space.

Note: If the agent is already configured to share an agent address space, a message showing the agent address space owner appears in the upper right corner of the Configure panel.


and

“Requirements to Review Before Configuring Your Product” on page 52


If you are defining an agent to run in an agent address space, use Create runtime members to generate the job that creates the runtime members for the agent address space.







Determine what to do nextSee “Checklist: Configuring Your Product Outside of CICAT” on page 29.


If you are defining an agent to run in the CMS address space, use Install Agent into local CMS to generate the job that installs the agent into the specified CMS.



Use Complete the Configuration to display a set of instructions for completing the configuration outside of CICAT. (The instructions are also covered in this guide.)


and

“Completing the Configuration” on page 63

! Runtime Environments (RTEs) panel

Use L (Load libs after SMP/E) to load all the libraries used by the RTE.






Checklist: Configuring Your Product Outside of CICAT





Reminder about the information availableIn addition to the detailed information provided in the online help in CICAT, CICAT contains a summary of the information contained in this guide.

The Complete the configuration option on the Configure menu also displays some of the manual steps you perform outside of CICAT to complete the configuration.

Checklist: Configure product outside CICATThe following checklist contains the manual steps you perform outside of CICAT to complete the configuration of your OMEGAMON XE product.

✓ Configuration Steps to Perform Outside CICAT Location of Information You Will Need

! Copy the started task procedures from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

“Copying the Procedures for the Started Task” on page 65

! Copy VTAM definitions and vary the major node active:

! Copy VTAM definitions from rhilev.midlev.RKANSAM to your VTAM list library (VTAMLST).

! Vary the VTAM major node in VTAMLST active.

“Copying the VTAM Definition and Varying the VTAM Node Active” on page 66

! APF-authorize the RKANMODn runtime load libraries. “APF-authorizing Libraries” on page 67

! If you configured the Persistent Data Store (CT/PDS), copy the CT/PDS maintenance procedures from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

“Copying the Procedures for the Persistent Datastore” on page 68



! Seed the CMS, if required. “Seeding the CMS” on page 69

! Verify the configuration:

! If your OMEGAMON XE for WebSphere MQ product and the CMS are installed and configured in the same address space:

– vary the CMS VTAM major node active – start the started task for the CMS

! If your OMEGAMON XE for WebSphere MQ product and the CMS are installed in different address spaces and the CMS is a local CMS:

– vary the CMS VTAM major node active– start the started task for the CMS– start the started tasks for the agent

! If your OMEGAMON XE for WebSphere MQ product and the CMS are installed in different address spaces and the CMS is a non-local CMS:

– start the CMS on the platform where it is installed– start the started task for the agent

“Verifying the Configuration: Same Address Space” on page 74

“Verifying the Configuration: Different Address Space” on page 75

“Verifying the Configuration: CMS on a Different Platform” on page 76

✓ Configuration Steps to Perform Outside CICAT Location of Information You Will Need


Checklists: Customizing Your Product Outside of CICAT

Checklists: Customizing Your Product Outside of CICAT

Who should use this checklistUse this checklist if you are customizing:



Reminder about the information availableIn addition to the detailed information provided in the online help in CICAT, CICAT contains a summary of the information contained in this guide.

Checklist: Configure product outside CICATThe following checklist contains the manual steps you perform outside of CICAT to customize your OMEGAMON XE product.

✓ Customization Steps to Perform Outside CICAT Location of the Information You Will

Need

! Authorize your external security program to permit the monitoring agent to access your queue managers.

“Granting Authorizations to the Monitoring and Configuration Agents” on page 79! Authorize your external security program to permit the

configuration agent to configure your queue managers.

! Enable monitoring of CICS channels. “Monitoring CICS Channels” on page 82

! Implement multi-level security for your MVS-based configuration database.

All topics beginning with Multi-level Security in the chapter

“Completing the Customization” on page 77

! If you want to replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT.

page 33

Checklist: Updating Your Configuration


Checklist: Updating Your Configuration

Update and change the configuration In some cases, you will need to update the configuration for a product.

The following checklist contains the steps you perform inside and outside of CICAT to update the configuration.

✓ Step Location of the Information You

Will Need

! Make the changes you want to the configuration in CICAT and

! use L (Load libs after SMP/E) on the Runtime Environments (RTEs) panel in CICAT to load all the libraries used by the RTE

! perform the manual steps required to complete the configuration outside of CICAT (if any)

“Updating and Changing the Configuration” on page 98

! If you want to replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT.

page 33


Using Advanced Features in CICAT


Determine the advanced feature to use Use the following advanced features if you

� have completed the appropriate checklist for configuring products

� have completed the appropriate checklist for verifying that the configuration is complete

Table 2. Advanced Features Available in CICAT

TaskAdvanced

FeatureLocation of Information

Port an existing RTE to one or more MVS images, without reconfiguring the RTE for those MVS images

System Variable Support


Replicate and transport an RTE to one or more MVS images

Batch Mode Processing


Overview of Processes, Methods, and CICAT Modes 35

Overview of Processes,Methods, and CICAT

Modes

IntroductionReview this chapter only if you are not familiar with Candle or the process of installing and configuring Candle products.

Chapter ContentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 36Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Processes for Installing, Configuring, and Maintaining Products . . . . . . . . 38Background about CICAT Modes: Interactive and Batch . . . . . . . . . . . . . 43

2

Determining the Topics to Use in this Chapter



This chapter provides background information about Candle terminology, process, and the Candle Installation and Configuration Assistance Tool (CICAT).

If you are not familiar with the content, review all of the topics. These topics include:

� Candle terminology

� the process for installing products and the process for installing maintenance (including the similarities and differences between the two processes)

� the process for installing and configuring products and maintenance, and where the steps in the process are performed (including examples of the tasks performed during each of the steps in the process and where to locate the information you will need)

� modes available for working in CICAT and the tasks they are used to complete (Interactive Mode and Batch Mode)


Candle Terminology

Candle Terminology

Terminology

The following list contains some of the terms used in this guide and defines those terms.

Candle Installation and Configuration Assistance Tool (CICAT)

Tool used to: � install new products or new versions of products� install maintenance for existing products� begin the configuration of products or maintenance

(if required for that particular maintenance)

Component Product or feature provided by Candle that is a separate started task

Configuring Making a product operational by completing the configuration of the product inside CICAT and completing the manual steps required outside of CICAT

Cumulative Maintenance

Maintenance through a given date that is customer approved

Customizing Modifying the defaults for options and settings and other changes that reflect the needs of your site

Installing Loading the contents of the Candle product and maintenance and installing a product

Migrating Preserving the customized data so that you can use it in a newer version of the product

Preventive Maintenance

Maintenance through a given date that is customer approved, but not yet included in Cumulative Maintenance

Runtime Environments (RTEs)

A group of runtime libraries that execute Candle products on an MVS image

Runtime libraries Libraries in the RTE that are used by the product when the product is started

Target libraries SMP/E controlled libraries that contain the source from the distribution media

Processes for Installing, Configuring, and Maintaining Products



Processes for installing products and maintenance: a comparison

The following illustration shows the steps in the process and compares the steps you perform when:

� installing new products or new versions of existing products

� installing maintenance for existing products

Table 3. Installing Products and Maintenance: A Comparison

Step in the ProcessRequired to Install

Products?Required to Install

Maintenance?

Prepare to install products and maintenance X X

Load and start CICAT X X

Install products and components X

Install maintenance (if any) X X

Begin to configure the products and components

X X

Complete the configuration of products and components by performing the manual steps required to make the product operational

X

Once configured, complete the manual steps to customize the product for your site (if any)

X

If you want to replicate Candle products or use Candle products on other MVS images, use some of the advanced features in CICAT designed to make this implementation easier

X X



Processes for installing and configuring products: a comparison

The following illustration shows the steps in the process and compares the steps you perform when:

� installing new products or new versions of existing products

� installing maintenance for existing products

Table 4. Installing and Configuring: A Comparison

Step in the ProcessPerformed in

CICAT?Performed Outside

of CICAT?

Prepare to install products and maintenance X

Load and start CICAT V300 X (if CICAT has been previously installed)

X (if you are installing CICAT for the first

time)

Install products and components X

Install maintenance (if any) X

Begin to configure the products and components

X


X


X

If you want to replicate Candle products or use Candle products on other MVS images, use some of the advanced features in CICAT designed to make this implementation easier

X



Example tasks in the process The table shows some examples of tasks you perform.

Table 5. Example Tasks for Installing, Maintaining, and Configuring

Step in the Broad Process Examples of Tasks

Prepare to install products and maintenance

� Review the software and space requirements for CICAT and the products and components you want to install

� Perform optional steps to prepare, such as backup your existing data sets

Load and start CICAT � Review the available files and the information in the DOCFILE

� If you are using CICAT for the first time and do not have an earlier version of CICAT installed, load CICAT from the distribution media

Install products and components

� Specify the high-level qualifiers for the product libraries � Allocate the product libraries � Receive and apply product components

Install maintenance (if any) � Review information about the PTFs provided in the DOCFILE

� Receive and apply product maintenance

Begin to configure the product and components

� Inside CICAT, create or select the RTE that will contain the product you want to configure

� Inside CICAT, specify basic configuration values for the product


� Outside of CICAT, manually copy members and libraries required by the product

� Outside of CICAT, verify the configuration by starting the product and displaying data in the user interface


� For some products, specify the security settings� For some products, specify the monitoring options

specific to your site



Where to find the information you will need The table shows the steps in the process and where to locate the information you will need.

If you want to replicate or use Candle products on other images, use some of the advanced features in CICAT

� Use Batch Mode to replicate and transport RTEs � Port an existing RTE to one or more MVS images

without reconfiguring the RTE for those MVS images

Table 6. Locating Information for Installing and Configuring

Step in the Broad Process Where to Locate Information about Procedures

Where to Locate Information about

Specific Values

Outside of CICAT, prepare to install products and maintenance



If you are: � migrating from CICAT

V200, load and start CICAT V300 using CICAT V200

� installing CICAT V300 for the first time, load and start CICAT outside of CICAT



Using CICAT, install products and components



Using CICAT, install maintenance (if any)



Table 5. Example Tasks for Installing, Maintaining, and Configuring

Step in the Broad Process Examples of Tasks



Using CICAT, begin to configure the products and components



Outside of CICAT, complete the configuration of products and components by performing the manual steps required to make the product operational

This guide

The Complete the configuration option on the Configure OMEGAMON XE Menu


Outside of CICAT, complete the manual steps to customize the product for your site (if any)

This guide Online help in CICAT

If you want to replicate Candle products or use products on other images, use some of the advanced features in CICAT



Table 6. Locating Information for Installing and Configuring

Step in the Broad Process Where to Locate Information about Procedures

Where to Locate Information about

Specific Values


Background about CICAT Modes: Interactive and Batch


Modes provided in CICAT

CICAT has two modes:

� Interactive Mode

� Batch Mode

The following table provides a description for each of the two modes.

Table 7. CICAT Modes: Interactive and Batch

Mode Description

Interactive ISPF panel-driven facility that assists you in specifying parameters and tailoring jobs for � installing and configuring new products � installing and configuring new versions of products � installing maintenance

Batch Facility that creates a single batch job that you can use to build, configure, and load an RTE. This single job performs all of the same RTE processing as the interactive CICAT.

Batch Mode is a simple and useful way of replicating RTEs to other MVS systems.

Plan Your Configuration 45

Plan Your Configuration

Introduction This chapter contains information that you should review before configuring products and maintenance. This chapter:

� contains background about the products and components

� helps you determine the components to configure

Chapter contentsCandle Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Details about the Candle Products and Components . . . . . . . . . . . . . . . . 48Determining the Components to Install and Configure . . . . . . . . . . . . . . . 50Requirements to Review Before Configuring Your Product . . . . . . . . . . . . 52Considerations and Requirements for OMEGAMON XE for WebSphere MQ Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3

Candle Products and Components



Background about how CICAT installs products and components CICAT automatically installs all the required and optional products and components.

In most cases, you must also configure the components to make them available.

Background about Candle products and components The following table shows all the product and components available with the Candle products. The products and components are listed in the order they should be installed and configured (if configuration is required).

Table 8. Overview of Candle Products and Components

Component Name or Category Purpose

Platform(s) for Product or Component

Candle Management Server (CMS)

Component that: � consolidates the data collected by the agent and

distributes the data to the CandleNet Portal™ (CNP) interface

� stores historical data and prototypes for configuration in the form of seed data

Note: If you have a distributed environment, you can use a CMS on the different platforms in that environment.

� Windows (Intel-based)XP/NT/2000

� MVS � UNIX

Persistent Data Store (CT/PDS)

Component that records and stores historical data that you can access using an OMEGAMON XE interface.

In some cases you can configure the CT/PDS with the agent or OMEGAMON XE product. If you decide not to configure the CT/PDS with the CMS, configure the CT/PDS when you configure the agent.

MVS



Agents and OMEGAMON XE products

Component that monitors systems, subsystems, and applications on the system where they are installed.

Agents: � collect data and monitor performance � provide data and performance information to the

CMS � receive instructions from the CMS � issue commands to the system or application you

are monitoring Agents can be: � OMEGAMON XE, which collect performance and

analysis data.� Alert Managers, which monitor alerts and relay

the information from console or message logs, network management products, and system management product.

� Alert Emitters, which monitor events or exceptions in products running under the control of the CMS and relay them back for corrective action (if applicable).

� Gateways, which communicate events to a management application running on a supported platform using a network service.

Platform appropriate for the system or software being monitored

OMEGAMON XE platform

Component that is the graphical user interface (GUI) you use to display and work with data provided by the Java based GUI CandleNet Portal™ (CNP) that communicates with the CMS and CNP server.

(This interface can be run in desktop or browser mode.)

� Windows (Intel-based)XP/NT/2000

Table 8. Overview of Candle Products and Components

Component Name or Category Purpose

Platform(s) for Product or Component

Details about the Candle Products and Components



Details about the relationships and CMS types The following table shows the CMS types, the relationship for the type, and a description of the relationship.

Table 9. Details about the Relationships and CMS Types

Relationship Candle Term

Description

CMS to CMS relationship

Hub CMS that:� receives data from agents and one or more remote CMS

in the environment � communicates data to and receives commands from an

interface

Remote CMS that: � receives data from agents � communicates data to the hub CMS only (It does not

communicate directly with an interface.)

CMS to agent relationship

Local CMS that is installed in the same RTE as the agent

Non-local CMS that is installed on: � MVS, but is not installed and configured in the same RTE

as the agent. � MVS, but is not installed and configured in the same CSI

as the agent. (For example, the CMS is installed using a different INSTLIB.)

� a platform other than MVS (such as UNIX or NT)



Details about OMEGAMON XE for WebSphere MQ ConfigurationOMEGAMON XE for WebSphere MQ Configuration enables you to create, configure, and manage WebSphere MQ queue managers across your network.

The data collected by OMEGAMON XE for WebSphere MQ Configuration can then be displayed using CandleNet Portal™.

Details about OMEGAMON XE for WebSphere MQ MonitoringOMEGAMON XE for WebSphere MQ Monitoring lets you easily collect and analyze WebSphere MQ data for all your remote and local queue managers from a single vantage point.

The data collected by OMEGAMON XE for WebSphere MQ Monitoring can then be displayed using CandleNet Portal.

You can use OMEGAMON XE for WebSphere MQ Monitoring to monitor the performance of each WebSphere MQ managed system, helping you to identify system bottlenecks and evaluate tuning decisions.

Determining the Components to Install and Configure



Components that can be shared by more than one productIn some cases, a product or component can be shared by more than one product. If you have already installed and configured these types of components, you can use the existing component.

For example, you can use the Candle Management Server (CMS) with more than one Candle product.

If you are going to use an existing component, the component must be current. You must have installed and configured the component for another Candle product at the same level.

Determine the products and components you will needTable 10 shows the components available with the products, listed in the order they are configured. The table also indicates:

� whether or not the components are required (R) or optional (O)

� whether or not the component can be shared

� additional information that might help you decide whether or not you want to configure the component (if any)

Table 10. Products and Components You Will Need

Component Name or Category

OM

EG

AM

ON

XE

for

Web

Sp

her

e M

Q

Co

nfi

gu

rati

on

OM

EG

AM

ON

XE

for

Web

Sp

her

e M

Q

Mo

nit

ori

ng

Can be Shared?

Additional Information (If Any)

Candle Management Server (CMS)

R R Y

Agent/OMEGAMON XE product

R R Y



Determine whether or not you have to configure the products and components

The following table shows the components, listed in the order they are configured, and indicates whether or not you must:

� configure the component using CICAT to make the component available to the product

� perform manual steps outside of CICAT to configure the component to make it available to the product

Persistent Datastore (CT/PDS)

O O N � For OMEGAMON XE for WebSphere MQ Monitoring, you can configure the CT/PDS with the CMS and/or the agent.

� For OMEGAMON XE for WebSphere MQ Configuration, the CT/PDS must be configured with the CMS.

Table 11. Products and Components to Configure

Component Name or Category Configure Using CICAT?

Requires Manual Steps Outside of

CICAT?

Candle Management Server (CMS) Y Y

Agent/OMEGAMON XE product Y Y

Persistent Datastore (CT/PDS) Y Y

Table 10. Products and Components You Will Need

Component Name or Category

OM

EG

AM

ON

XE

for

Web

Sp

her

e M

Q

Co

nfi

gu

rati

on

OM

EG

AM

ON

XE

for

Web

Sp

her

e M

Q

Mo

nit

ori

ng

Can be Shared?

Additional Information (If Any)

Requirements to Review Before Configuring Your Product



Reviewing communication protocol requirementsBefore specifying the communication protocols (SNA, IP, IP.PIPE) you want the agent address space to support, review the following requirements.

� If IP is one of the protocols that the agent address space will support, and you are running multiple TCP/IP interfaces or network adapters on the same MVS image, specify the network interface card.

� If IP.PIPE is one of the protocols that the agent address space will support, specify values for address translation and partition name.

� For the SNA protocol, specify the VTAM applids and network ID.

Using TCP/IP or IP.PIPEIf your site is using TCP/IP, be aware that network services such as NIS, DNS, and the /etc/hosts file should be configured to return the fully qualified hostname of the CMS and the product. For example:

#HostName.candle.com

This minimizes the risk of inconsistent values being returned for the hostname.

Note: When the installers reference the TCP/IP protocol suite, this means the Candle component will use UDP (User Datagram Protocol) for connection.

If your site is using IP.PIPE, be aware of the following limitations.

� There can be at most 16 IP.PIPE processes per host.

� IP.PIPE uses one, and only one, physical port per process. Port numbers are allocated using a well-known port allocation algorithm. The first process for a host is assigned port 1918, which is the default.

� KDC_PORTS is not supported for IP.PIPE.

Note: When the installers reference IP.PIPE, this means the Candle component will use IP (Internet Protocol).



Specifying multiple network interface cards (NIC)If you are running multiple TCP/IP interfaces or network adapters on the same MVS image, you must specify the network interface card that you want your Candle application to use. This allows you to direct the Candle application to connect to a specific TCP/IP local interface.

Note: Candle applications that can have network interface cards include the CMS and all stand-alone agents.

You will set the network interface card parameter while specifying the IP and IP.PIPE communication values for the Candle application. During configuration, CICAT will then add the KDCB0_HOSTNAME= parameter in the KppENV member (pp is the product code) of the RTE’s RKANPAR library. For example, the CMS member name is KDSENV.

Note: If you are using Interlink’s TCPACCESS, you cannot use this variable.

Using the Inter-user Communication Vehicle (IUCV) interfaceIf you are using the Inter-user Communication Vehicle (IUCV) interface, you will indicate this while specifying your TCP (IP and IP.PIPE) communication values for the Candle application. During configuration, CICAT adds the IUCV keyword in the KLXINTCP member of the RTE’s RKANPAR library.

KLXINTCP is the CT/Engine initialization member for:

� IBM’s High Performance Native Sockets (HPNS) TCP/IP protocol support

� IUCV interface support

� Interlink V5.2 HPNS TCP/IP protocol support

Note: When using IBM’s HPNS TCP/IP protocol support, do not specify Y.

Considerations and Requirements for OMEGAMON XE for WebSphere MQ Products



Reviewing considerations and requirementsBefore configuring the WebSphere MQ products, review the following.

� To execute OMEGAMON XE for WebSphere MQ Configuration and OMEGAMON XE for WebSphere MQ Monitoring, you must have installed WebSphere MQ on every node where you plan to run the monitoring or configuration agents.

� Before starting the OMEGAMON XE for WebSphere MQ Monitoring agent, the WebSphere MQ default objects, such as SYSTEM.DEFAULT.MODEL.QUEUE, must exist. If they do not exist in your environment, you must create them prior to starting the agent.

� The OMEGAMON XE for WebSphere MQ Monitoring agent requires read access to SYS1.PARMLIB(IEFSSNxx) to find the WebSphere MQ subsystems defined.

� You must have created all queue managers; the MVS-based OMEGAMON XE for WebSphere MQ Configuration agent cannot create or start a queue manager.

� You must prepare queue managers for monitoring as follows:

– Edit the distributed WebSphere MQ source for initialization parameters. By default, these reside in:

mqqual.SCSQPROC(CSQ4ZPRM)

where mqqual is the WebSphere MQ subsystem high-level qualifier.

– In the CSQ6SYSP macro, change the default setting on SMFSTAT to:

SMFSTAT=YES

– Assemble and link-edit CSQ6SYSP to create a new load module in the mqqual.SCSAUTH library.

– To monitor WebSphere MQ events, use the ALT QMGR command to ensure that the following WebSphere MQ parameters are enabled:

INHIBTEV REMOTEEV PERFMEV LOCALE STRSTPEV



Setting up component trace for the OMEGAMON XE for WebSphere MQ Monitoring product

Setting up the MVS component trace environment for OMEGAMON XE for WebSphere MQ Monitoring provides the capability to generate diagnostic information that Candle Customer Service and Satisfaction may require at a later date. Candle recommends that you perform this step now so the MVS component trace members will be in place when and if you need them.

Copy the KMQATRSS module from thilev.RKANMOD to the link pack area (LPA). Member KMQATRSS controls starting and stopping of the MVS component trace for OMEGAMON XE for WebSphere MQ Monitoring.

As shipped, the OMEGAMON XE for WebSphere MQ Monitoring is inactive. Do not modify member CTKMQ00 in the rhilev.midlev.RKANSAM library unless requested to do so by Candle Customer Service and Satisfaction. This member contains MVS component trace parameters for OMEGAMON XE for WebSphere MQ Monitoring.

Deciding whether to configure WebSphere MQ agents in their own agent address space

Candle recommends that you configure the WebSphere MQ agents in their own agent address space.

An agent address space can contain one or more WebSphere MQ agents, but does not contain a CMS. Configuring an agent in an agent address space enables it to report to either a CMS on a distributed platform or to an MVS-based CMS.

You can optionally configure these agents to share an agent address space. You can then start and stop the agents with a single started task name. The first agent configured becomes the owner of the agent address space and the values you specify for it are shared by all agents configured in that address space. There is no situation where there should be more than one agent of each type on an MVS image.

Note: If an agent shares its address space with the CMS, the agent’s historical data will not be viewable from the CMW.

Warning: OMEGAMON XE for WebSphere MQ Configuration does not support the secondary CMS feature. Do not configure the MQ Configuration agent in an agent address space that reports to a secondary CMS.

Start CICAT and Access the Menu for Configuring 57

Start CICAT and Access theMenu for Configuring

IntroductionThis chapter provides detailed information about

� starting CICAT

� accessing the menu in CICAT for configuring the product

� using CICAT defaults and restrictions, and some of the commands available to assist while using CICAT to install products and maintenance

Chapter ContentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 58Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Accessing the Menu for Configuring the Product. . . . . . . . . . . . . . . . . . . . 60Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4




Relationship of the topics in this chapter and the checklistsThis chapter contains topics that correspond to the tasks in Checklist: Starting CICAT and Accessing the Menu for Configuration in Chapter 1.

This chapter also contains a topic that covers some additional information about using CICAT (such as CICAT defaults and commands).

Determine the topics to use in this chapter

If you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter. The R indicates that the topic is required. The O indicates the topic is optional.

Page Numbers for Topics

page59

page60

page61

Start CICAT R

Access the menu for configuring the product in CICAT R

Review information about restrictions, defaults, commands, and functions

O


Starting CICAT

Starting CICAT

Start CICAT

Follow these steps to start CICAT.

1. Log onto a TSO session.

2. Invoke ISPF.

3. Go to a TSO command line. (In most cases, this is option 6 on the ISPF Primary Option Menu.)

4. Enter the following command:

EX ‘shilev.INSTLIB’

(where shilev is the high-level qualifier you specified for CICAT)

Result: CICAT first displays the copyright panel and then the CICAT Main Menu. (Both the copyright panel and the CICAT Main Menu display the version and release of CICAT.)

Accessing the Menu for Configuring the Product


Accessing the Menu for Configuring the Product

Select the product to configure and access the menu

Follow these steps to access the Configure OMEGAMON XE Menu.

1. If this is the first time you have used CICAT V300 to configure a product, from the CICAT Main Menu select Configure products > Set up configuration environment.

2. From the CICAT Main Menu, select Configure products > Select product to configure.(Only those packages that are eligible to be configured are listed on this panel.)

3. On the Product Selection Menu, specify S to select a product to be configured. You can only select one product at a time for configuration.Result: CICAT displays the Runtime Environments (RTEs) panel.

4. On the Runtime Environments (RTEs) panel, specify: � to use an existing RTE, the C (Configure) select

� to create a new RTE, the A (Add), B (Build libraries), and C (Configure) selects

Result: CICAT displays the Product Configuration Selection Menu.

5. On the Product Configuration Selection Menu, select the component you want to configure.Result: CICAT displays the Configure OMEGAMON XE Menu.


Using CICAT

Using CICAT

Defaults provided with CICAT

Whenever possible, CICAT provides defaults for fields and options. These defaults

� when provided, should be sufficient to complete the installation of products and maintenance

� can be changed to values specific to your site

Assistance provided in CICAT

Whenever possible, CICAT checks the values you specify and verifies that you have specified the required values. If CICAT detects an error or omission, it displays a short message.

Display requirements in ISPF

If you are using a 3270 Model 2 (24 x 80) display, you must turn off the pre-defined function (PF) keys so that the CICAT panels are not truncated.

To turn off the pre-defined function keys, type PFSHOW on any command line and press Enter until the function keys no longer appear.

Restrictions

The length of the high-level qualifier for the runtime libraries must be 26 characters or less.

You cannot use

� the ampersand character (&) as input data in CICAT interactive or batch mode

� the ISPF feature for edit recovery

(If the ISPF RECOVERY ON command is entered, edits will produce a recovery error message. Enter the RECOVERY OFF command to suppress the error messages.)

Using CICAT


Commands and functions

The following list shows some of the commands and functions available in CICAT, that you can use for navigation and to display information.

Advanced key On some panels for configuring products, displays panels where you can specify specialized values (such as values for the Persistent Datastore for a CMS).

End key Returns to the previous panel.

Enter key Accepts the values you have specified and displays the next panel in the process.

HELP command Displays information about a panel or the extended description for a message.

README command Displays the README for the current version of CICAT.

README APP command Displays information about default applids for started tasks and VTAM, and how CICAT processes VTAM applids.

README ERR command Displays a list of CLIST error codes and descriptions (for both interactive and batch mode).

README SYS command Displays a information about system variable support.

UTIL command Displays the Installation Services and Utilities menu.

Completing the Configuration 63

Completing the Configuration

IntroductionThis chapter contains:

� the manual steps you must perform outside of CICAT to complete the configuration of your OMEGAMON XE product

� the procedure to follow to verify the configuration of your OMEGAMON XE product

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 64Copying the Procedures for the Started Task. . . . . . . . . . . . . . . . . . . . . . . 65Copying the VTAM Definition and Varying the VTAM Node Active . . . . . 66APF-authorizing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Copying the Procedures for the Persistent Datastore . . . . . . . . . . . . . . . . . 68Seeding the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . . . . 74Verifying the Configuration: Different Address Space . . . . . . . . . . . . . . . . 75Verifying the Configuration: CMS on a Different Platform. . . . . . . . . . . . . 76

5




Relationship of the topics in this chapter and the checklists

This chapter contains topics that correspond to the tasks in Checklist: Configuring Your Product Outside of CICAT in Chapter 1.

Determine the topics to use in this chapter for the OMEGAMON XE for WebSphere MQ products

If you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter.

In some cases, a task does not need to be completed if a component is not configured using CICAT. The R indicates that you must review the topic to determine whether or not it is required.


page65

page66

page67

page68

page72

page74

page75

page76

OMEGAMON XE for WebSphere MQ product and the CMS are installed and configured in the same address space

R R R R R R

OMEGAMON XE for WebSphere MQ product and the CMS are installed in different address spaces and the CMS is a local CMS

R R R R R R

OMEGAMON XE for WebSphere MQ product and the CMS are installed in different address spaces and the CMS is a non-local CMS

R R R R R


Copying the Procedures for the Started Task

Copying the Procedures for the Started Task

Background about the started tasks When you use CICAT to install and configure a product or component, CICAT creates the started task procedures.

You must copy the started task procedures to your procedure library (PROCLIB) to complete the configuration.

Copy the procedures for the started tasks to your procedure library You must copy the started task procedures for the product from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

Copying the VTAM Definition and Varying the VTAM Node Active


Copying the VTAM Definition and Varying the VTAM Node Active

Background about the VTAM definitions and the VTAM major nodeIf you configured OMEGAMON XE to use SNA as the communication protocol, CICAT created VTAM definitions.

To complete the configuration, you must:

� copy the VTAM definition to VTAMLST

� vary the VTAM major node active

Copy VTAM definitions and vary the VTAM major node activeFollow this procedure to complete the configuration for the SNA communication protocol.

1. Copy the VTAM definition from rhilev.midlev.RKANSAM to VTAMLST. The VTAM definition in rhilev.midlev.RKANSAM has the same name you specified using CICAT for either:

� the VTAM major node

� the Candle global VTAM major node (The default is KCANDLE1.)

2. Vary the VTAM major node active using the following command. V NET,ACT,ID=ccccccccc

The ccccccccc indicates the name for the VTAM major node you specified using CICAT for either:

� the VTAM major node

� the Candle global VTAM major node


APF-authorizing Libraries

APF-authorizing Libraries

Background about APF-authorization The load libraries must be APF-authorized or some of the functions in the product may not be available.

You APF-authorize the load libraries by adding them to your list of APF-authorized libraries.

APF-authorize the libraries If the RTE is sharing with SMP/E, APF-authorize the target load libraries:

� thilev.midlev.TKANMOD

� thilev.midlev.TKANMODL

For all other RTEs, APF-authorize the runtime load libraries:

� rhilev.midlev.RKANMOD

� rhilev.midlev.RKANMODL

If one library in a steplib or joblib concatenation requires APF-authorization, all the libraries in the concatenation require APF-authorization.

Note: Any runtime libraries concatenated in the STEPLIB DDNAME and in the RKANMODL DDNAME of the started task must be APF-authorized.

Copying the Procedures for the Persistent Datastore


Copying the Procedures for the Persistent Datastore

Background about the procedures for the persistent data storeThe persistent data store (CT/PDS) is used to store the data for historical collection.

When you install and configure the CT/PDS using CICAT, CICAT creates the procedures for the CT/PDS.

If you decided to configure the CT/PDS, you must copy these procedures to your procedure library (PROCLIB) to complete the configuration.

Copy the procedures to your procedure library If you configured the CT/PDS, you must copy the following procedures from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

� pdsmprefix1

� pdsmprefix2

The value for pdsmprefix is the unique prefix you specified for the maintenance procedure using CICAT. The default is KPDPROC.


Seeding the CMS

Seeding the CMS

Background about seeding the CMS When you seed the CMS, you provide the CMS with product-specific information that the CMS uses:

� for product-provided solutions (such as predefined situations and policies)

� to build reports and the Topology view

Background about the guidelines for seeding the CMS The guidelines you follow to seed the CMS depend on the platform for the product. These platforms include:

� distributed platforms (such as UNIX and Windows)

� MVS

Guidelines for seeding the CMS for products on distributed platformsFollow these guidelines when seeding the Candle Management Servers for products on distributed platforms.

� Seed all the Candle Management Servers the product communicates with in your environment using Manage Candle Services.

� If the product is on UNIX, seed the CMS using Manage Candle Services as well as the seeding process provided on UNIX when you install the product.

� If the product communicates with remote Candle Management Servers, seed the hub Candle Management Server the remote Candle Management Servers communicate with in your environment using Manage Candle Services.

� If the product communicates with a CMS on MVS, you must also install product-specific solutions in the CMS using CICAT.

Seeding the CMS


Guidelines for seeding the CMS for products on MVS The guidelines for seeding the CMS for products on MVS vary depending on the product.

Review the following table to determine the guidelines to follow for your product(s). The table has the following organization.

� The first column contains the guideline.

� The second column contains the products and the versions of the products that follow the guideline.

� The third column contains additional information (if any).

If your product or the version of your product is not listed in the second column, do not follow the guideline.

Table 12. Guidelines for Seeding the CMS for Products on MVS

Guideline Products and Product Versions That Follow the Guideline Additional Information

Seed the remote Candle Management Servers and the hub Candle Management Server on MVS using Manage Candle Services

OMEGAMON XE for CICS V100

OMEGAMON XE for CICSplex V220

OMEGAMON XE for DB2 V100

OMEGAMON XE for DB2plex V220

OMEGAMON XE for IMS V100

OMEGAMON XE for OS/390 V120 or higher

OMEGAMON XE for Mainframe Networks V100

OMEGAMON XE for Storage V100

OMEGAMON XE for WebSphere MQ Monitoring V360

The products not included in this list are seeded automatically by CICAT when the product is registered with the CMS during configuration.

Seed the hub Candle Management Server on distributed platforms using Manage Candle Services

All products and versions of products


Seeding the CMS

Seed the remote Candle Management Servers on distributed platforms using Manage Candle Services

Alert Adapter for OMEGACENTER Gateway V150

OMEGAMON XE for CICS V100

OMEGAMON XE for CICSplex V220

OMEGAMON XE for DB2 V100

OMEGAMON XE for DB2plex V220

OMEGAMON XE for IBM Cryptographic Coprocessors V100

OMEGAMON XE for Mainframe Networks V100

OMEGAMON XE for OS/390 V120 or higher

OMEGAMON XE for Storage V100

OMEGAMON XE for Unix System Services V220

OMEGAMON XE for WebSphere Application Server V110

OMEGAMON XE for WebSphere MQ Configuration V360

OMEGAMON XE for WebSphere MQ Integrator V110 or higher

OMEGAMON XE for WebSphere MQ Monitoring V360

The products not included in this list are seeded automatically by CICAT when the product is registered with the CMS during configuration.

Table 12. Guidelines for Seeding the CMS for Products on MVS

Guideline Products and Product Versions That Follow the Guideline Additional Information

Seeding the CMS


Locating the information you will need The following table lists the tasks for seeding the CMS and the locations where you can find detailed information about seeding the CMS.

Prerequisites for seeding the CMS for products on MVSBefore seeding the CMS, verify that:

� the MVS products are installed and available with CandleNet Portal

� the same versions of the MVS products are installed and available with CandleNet Portal

Also verify that the image you used to install CandleNet Portal is compatible with the products you installed and configured using tape or Candle eDelivery.

For example, if you received a product package containing tapes and a CD image, verify that an older or newer CD image of CandleNet Portal has not been installed on the workstation you will be using to seed the CMS. If you have any question about whether or not they are compatible, contact Candle Customer Service and Satisfaction.

Task You Want to Perform Location of the Information You Will Need

For Candle Management Servers on distributed platforms, seeding the CMS

The topics on seeding the CMS in the Installation Guide for that platform

For Candle Management Servers on MVS, seeding the CMS on MVS

The topics on seeding the CMS in the:product-specific Configuration and Customization Guide (if applicable) Candle Management Server on OS/390 and z/OS Configuration and Customization Guide

For distributed products that communicate with a CMS on MVS, installing product-specific solutions

The topics on registering distributed products in the Candle Management Server on OS/390 and z/OS Configuration and Customization Guide


Seeding the CMS

Seeding the CMS using Manage Candle Services Follow these steps to seed the CMS using Manage Candle Services:

1. On the workstation where you installed the CandleNet Portal Server, select Start > Programs > Candle OMEGAMON® XE >Manage Candle Services.

2. In the Manage Candle Services window, select Actions >Advanced > Seed CMS.

3. On the Seed CMS dialog, select On a different computer and click OK.Result: The Manage Candle Services dialog appears. Confirm that the CMS to be seeded is running and click OK.

4. On the Non-resident CMS Connection dialog(s), specify the appropriate values and click the OK button.

5. On the Select Product to Seed dialog, select the products you have installed and click the OK button. Result: Manage Candle Services seeds the CMS and displays the Seed Data Operation Complete dialog box indicating whether or not the seeding completed successfully.

Verifying the Configuration: Same Address Space


Verifying the Configuration: Same Address Space

Prerequisites for verifying the configurationIn addition to completing the configuration for the product, you must also have:

� completed the configuration of the interface you want to use

� completed the configuration of the CMS on the appropriate platform (including seeding the CMS using the interface)

Process to follow to verify the configuration Follow this process to verify the configuration by starting the product. Follow this process only if:

� the CMS is installed on MVS

� the product and the CMS are installed in the same address space

Figure 1. Process for Verifying the Configuration: Same Address Space

If the Candle Management Server (CMS) is not already running, vary the CMS VTAM major node active.

.

If the CMS is not already running, start the started task for the CMS.

Using the appropriate CandleNet Portal interface, connect to the Hub CMS and use theinterface to verify that the data for the product is being displayed.


Verifying the Configuration: Different Address Space

Verifying the Configuration: Different Address Space

Prerequisites for verifying the configurationIn addition to completing the configuration for the product, you must also have completed the configuration of the:

� interface you want to use

� CMS on the appropriate platform (including seeding the CMS)

Process to follow to verify the configuration Follow this process to verify the configuration by starting the product. Follow this process only if:

� the CMS is installed on MVS

� the agent and CMS are in different address spaces

Figure 2. Process for Verifying the Configuration: Different Address Space

If you selected SNA as the communication protocol for the agent instead of TCP/IP and the CMS is not already running, vary the CMS VTAM major nodeactive.

If the CMS is not already running, start the started task for the CMS.

Start the started task for the product and components you configured.

Using the appropriate CandleNet Portal interface, connect to the Hub CMSand use the interface to verify that the data for the product is being displayed.

Verifying the Configuration: CMS on a Different Platform


Verifying the Configuration: CMS on a Different Platform

Prerequisites for verifying the configuration

In addition to completing the configuration for the product, you must also have:

completed the configuration of the interface you want to use

completed the configuration of the CMS on the appropriate platform (including seeding the CMS using the interface)

Process to follow to verify the configuration

Follow this process to verify the configuration by starting the product. Follow this process only if:

you installed the agent on MVS

the CMS in installed on a different platform

Process for Verifying the Configuration: CMS on a Different Platform

.

If the CMS is not already running, start CMS on the platform where it is installed.(For information about using a CMS on a different platform, see the InstallationGuide for that platform.)

Start the started task for the product and components you configured.

Using the appropriate CandleNet Portal interface, connect to the Hub CMSand use the interface to verify that the data for the product is being displayed.

Completing the Customization 77

Completing the Customization

IntroductionThis chapter contains information about the manual steps you must perform outside of CICAT to complete the customization.

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 78Granting Authorizations to the Monitoring and Configuration Agents . . . . 79Monitoring CICS Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Multi-level Security: Reviewing Configuration Database Security . . . . . . . 83Multi-level Security: Implementing Configuration Database Security. . . . . 94

6




Relationship of the topics in this chapter and the checklists

This chapter contains topics that correspond to the tasks in Checklists: Customizing Your Product Outside of CICAT in Chapter 1.

Determine the topics to use in this chapter

If you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter.

The table contains only steps you perform to customize the product for your site and are not required to make the product operational. All of the topics in this chapter are optional (O)


page79

page82

page83

page94

Grant authorizations to monitoring or configuration agents O

Enable CICS channel monitoring O

Review multi-level security feature for configuration databases O

Implement multi-level security for configuration databases O


Granting Authorizations to the Monitoring and Configuration Agents


Background about granting authorizationsThis section provides guidelines for authorizing your external security program (for example, RACF) to permit the

� monitoring agent to access your queue managers� configuration agent to configure your queue managersAuthorization can be granted to agents that run either in the CMS address space or in their own address space.

How you set these authorizations depends upon your external security program and the OMEGAMON XE for WebSphere MQ Monitoring parameters that you specify. Refer to the RACF and CA-TOP SECRET examples below. Also, refer to the OMEGAMON XE for WebSphere MQ Monitoring User’s Guide and consult the documentation for your external security program.

If the type of agent is... the required authorizations are to...

monitoring, � read or browse WebSphere MQ event queues. The agent or CMS identifier must also be granted authority to alter the QDPMAXEV parameter on monitored queues.

� get messages from and put messages to monitored queues.

� browse the WebSphere MQ queue SYSTEM.CHANNEL.SEQNO for CICS channel support.

configuration, � connect to the WebSphere MQ queue manager (MQCONN).

� issue system commands to WebSphere MQ and receive responses.

� get messages from and put messages to Candle queues starting with KMC (the default) or the high-level qualifier for your site (hlq).



RACF exampleThis is an example of authorization using RACF. If you use another security manager, see the required authorizations listed above.

1. For each subsystem that you plan to monitor, issue the following WebSphere MQ command:

DISPLAY SECURITY SWITCHES

The current security switch profiles settings for the specified subsystem display.

2. If the following message displays: CSQH001I CSQHPDTC SUBSYSTEM SECURITY SWITCH SET OFF,

then you do not need to grant RACF authorizations for the specified subsystem. Skip the remaining steps in this procedure.

If the above message does not display, proceed to the next step in this procedure.

3. If a RESLEVEL profile has not been defined in RACF class MQADMIN for this WebSphere MQ subsystem, then define one by issuing the RACF command:

RDEFINE MQADMIN ssid.RESLEVEL UACC(NONE) AUDIT(ALL),

where ssid is the WebSphere MQ subsystem. You have defined the RESLEVEL profile in RACF security class MQADMIN for WebSphere MQ subsystem ssid.

4. Issue this RACF command:PERMIT ssid.RESLEVEL CLASS(MQADMIN) ID(auser) ACCESS(CONTROL)

where auser is the userid for the agent’s started task. You have granted the userid for the agent’s started task access to all WebSphere MQ resources.

5. Issue this RACF command:RDEFINE MQCMDS ssid.** UACC(NONE)

You have defined the profile in RACF security class MQCMDS.

6. Issue this RACF command:PERMIT ssid.DISPLAY.** CLASS(MQCMDS) ID(auser) ACCESS(READ)

You have granted the userid for the agent’s started task the ability to issue all WebSphere MQ commands.



CA-TOP SECRET exampleThis is an example of authorization using CA-TOP SECRET® security. It is intended as a guide only; you will need to adapt these notes to conform to your release and configuration of the security product. See the required authorizations listed above.

1. If necessary, make the MQM facility resident:TSS MODIFY(FAC(MQM=RES))

2. Provide access to WebSphere MQ facilities for the ACID (the userid for the agent’s started task):

TSS ADD(auser) MQADMIN(csq1.)TSS ADD(auser) MQCMDS(csq1.)TSS ADD(auser) MQQUEUE(csq1.)

TSS PER(auser) MQADMIN(csq1.RESLEVEL)TSS PER(auser) MQCMDS(csq1.*) ACCESS(ALL)TSS PER(auser) MQQUEUE(csq1.*) ACCESS(ALL)

In this example, auser is the ACID (the userid for the agent’s started task) and csq1 is the queue manager name.

3. Refresh the WebSphere MQ security for the queue manager by issuing this command from MVS:

xxxx REVERIFY SECURITY(auser)

In this example, xxxx is the command prefix for the csq1 queue manager and auser is the ACID (the userid for the agent’s started task).

Monitoring CICS Channels


Monitoring CICS Channels

Enable monitoring of CICS channelsFollow these steps to enable monitoring of CICS channels.

1. Edit the CICS region JCL, as follows:A. Locate the DFHRPL DD statement.B. Add the KMQAMQCI library to the concatenation; for example:

CANDLE.CCCMQMC.TKANMOD(KMQAMQCI)

2. Using the online resource definition (transaction CEDA), define program KMQAMQCI; language is Assembler and EXECKEY is CICS.

3. Using CEDA, define a transaction that executes program KMQAMQCI; TASKDATAKEY is CICS. Candle recommends using transaction ID KMQC.

4. The default high-level qualifier for your Candle-created queues is KMQ. If you defined a different high-level qualifier, you must specify it using INITPARM in the CICS System Initialization Table (SIT) or in the SYSIN override:

INITPARM=(KMQAMQCI=’HLQ=hlq’)

where hlq is the new high-level qualifier that you defined.

5. Start transaction KMQC using one of the following methods:� Add program KMQAMQCI to the PLTPI. Use INITPARM if you want to

specify a high-level qualifier.

� Enter transaction KMQC START [HLQ=hlq] at a CICS terminal.

� Link to program KMQAMQCI, passing START [HLQ=hlq] in the common area.

� Issue an EXEC CICS START command for transaction KMQC, passing START [HLQ=hlq] as data.

6. Transaction KMQC is automatically stopped at CICS shutdown. If you wish to stop KMQC manually, use one of the following methods:� At a CICS terminal, enter this command:

KMQC STOP

� Link to program KMQAMQCI, passing STOP in the common area.

� Issue an EXEC CICS START command for transaction KMQC, passing STOP as data.


Multi-level Security: Reviewing Configuration Database Security


Multi-level security featureThe multi-level security feature for your MVS-based Configuration Database resides with the hub Candle Management Server.

Using the multi-level security feature you can restrict access to your Configuration Database at up to four increasingly resource-specific levels. Known collectively as “authorization-checking levels”, they correspond to the following object classifications in your OMEGAMON XE for WebSphere MQ Configuration environment:

� Configured System Group� Configured System� Resource Group� Resource

Implementation of this security feature involves setting one of these four authorization-checking levels for each Configured System Group that you define. It also involves the creation of Resource Access Control Facility (RACF) profiles that are associated, by naming convention, with the level you have set.

When you attempt to manipulate an object (resource) within a protected Configured System Group, the MVS System Authorization Facility (SAF) searches for the profile associated with the assigned authorization-checking level and uses its access attributes.



Authorization-checking levelsFollowing is a description of the four authorization-checking levels, including the hierarchy of resources covered by each level.

Authorization-checking Level

Hierarchy Level

Description

Configured System Group Top Implies that only one profile exists for each Configured System Group (group of queue managers) and that all resources within the group are covered by that profile.

When Configured System Group is specified as the authorization-checking level, SAF begins searching for that profile only, even if other profiles associated with lower authorization-checking levels exist. If it does not find the designated profile, it grants access.

This is the level with the least system overhead; however, if affords the least flexibility in restricting access to objects (resources).

Configured System Second (The default setting.) Implies that one profile exists for each Configured System (queue manager) and that all resources associated with that Configured System are covered by that profile.

When Configured System is specified as the authorization-checking level, SAF searches for that profile only, even if other profiles associated with lower authorization-checking levels exist. If it does not find the designated profile, it searches for a profile associated with the parent Configured System Group. If it does not find that profile either, it grants access.



Resource Group Third Implies that one profile exists for each Resource Group (group of queues, channels, namelists, etc.) and that all resources associated with that Resource Group are covered by that profile.

When Resource Group is specified as the authorization-checking level, SAF begins searching for that profile, even if other profiles associated with the lowest authorization-checking level (Resource) exist. If it does not find the designated profile, it searches for a profile associated with the parent Configured System. If it does not find that profile either, it searches for a profile associated with the parent Configured System Group. If it does not find that profile either, it grants access.

Resource Bottom Implies that one profile exists for each individual Resource.

When Resource is specified as the authorization-checking level, SAF begins searching for that profile. If it does not find the designated profile, it searches for a profile associated with the parent Resource Group. If it does not find that profile either, it searches for a profile associated with the parent Configured System, and then the parent Configured System Group. If it does not find either of those profiles, it grants access.

Authorization-checking Level

Hierarchy Level

Description



Guidelines for creating RACF profilesThis section contains rules and guidelines to help you create the necessary profiles to protect the objects in your configuration database.

When you create a profile, you will assign user IDs certain access levels to it. These following access levels define each user’s control over the objects protected by that profile.

For example, assume you want to create a profile that gives full authority to user MQADMIN for a queue manager named QMGRPROD running on system SYSPROD. All other users will have READ access only. The following commands would create that profile:

RDEFINE $KCFADMN MQ.QMGR.SYSPROD.QMGRPROD UACC(READ)PERMIT QMGR.SYSPROD.QMGRPROD CLASS($KCFADMN) ID(MQADMIN) ACCESS(ALTER)

The general types of profiles that you can create are those that cover:

� objects in defined configurations� objects in prototype configurations� special tasks

For any resource(s) that possess common access attributes, you can also create generic profiles.

All these profile types are described in the following sections. While reading these sections, recall that RACF profile names do not support lower-case characters. When an authorization-check is performed, lower-case characters are converted to uppercase. So, assuming that on SYS1 there were two queue managers, one called QMGR1 and one called qmgr1, both would be protected by the same RACF profile called MQ.QMGR.SYS1.QMGR1.

NONE User cannot even view the object’s settings list.

READ User can view the object, but not change it.

UPDATE User can make changes to the object.

CONTROL User can make changes to the object and perform “Update Actual from Defined” against the object.

ALTER User has full access to the object, including the ability to define/delete it.



Defined configurations

In defined configurations, you associate the authorization-checking level with the profile by adhering to profile-naming conventions. These naming conventions are described in the following table.

In this table, required characters in each profile name are represented as bolded, capital letters (for example, MQ.QMGR). The remainder of the string, represented by lower-case, italicized characters (for example, system-name.queue-manager-name) is your site-specific value.

Table 13. Profile Naming Conventions for Defined Configuration Objects

Level Profile Naming Convention Explanation

Configured System Group

CSG.configured-system-group-name

configured-system-group-name is the name of the particular configured system group covered by this profile.

Configured System MQ.QMGR.system-name.queue-manager-name

� system-name is the name of the host system where this configured system (queue manager) resides.

� queue-manager-name is the name of the particular configured system (queue manager) covered by this profile.



Resource Group parent-object-profile-name.RG.resource-group-name

� parent-object-profile-name is the full name of the profile for the parent of this resource group.

� resource-group-name is the name of the resource group covered by this profile.

For example, assume there is a resource group named “myresource”, existing within a queue manager named “myqmgr” on “systema”. The profile that protects this resource would be named:

MQ.QMGR.systema.myqmgr.RG.myresource

Resource

� queue MQ.QMGR.system-name.queue-manager-name.QUEUE.queue-name

� system-name is the name of the host system where the queue manager resides.

� queue-manager-name is the name of the queue manager of this queue.

� queue-name is the name of the queue covered by this profile.

� channel MQ.QMGR.system-name.queue-manager-name.CHANNEL.channel-name



� channel-name is the name of the channel covered by this profile.





� process MQ.QMGR.system-name.queue-manager-name.PROCESS.process-name



� process-name is the name of the process covered by this profile.

� namelist MQ.QMGR.system-name.queue-manager-name.NAMELIST.namelist-name



� namelist-name is the name of the namelist covered by this profile.

� storage class MQ.QMGR.system-name.queue-manager-name.STGCLASS.storage-class-name



� storage-class-name is the name of the storage class covered by this profile.

� authentication information

MQ.QMGR.system-name.queue-manager-name.AUTHINFO.authinfo-name



� authinfo-name is the name of the authentication information covered by this profile.





Prototype configurations

In prototype configurations, there is no relationship between the authorization-checking level and the profile name; SAF always searches for a prototype-specific profile. Naming conventions for prototype profiles are described in the following table.

Required characters in each profile name are represented as bolded, capital letters (for example, MQ.PROTO.QMGR). The remainder of the string, represented by lower-case, italicized characters (prototype-name), is your prototype name.

� coupling facility MQ.QMGR.system-name.queue-manager-name.CFSTRUCT.cfstruct-name



� cfstruct-name is the name of the coupling facility covered by this profile.

Table 14. Profile Naming Conventions for Prototype Configuration Objects

Prototype Profile Naming Convention Explanation

resource group PROTO.RG.resource-group-name

resource-group-name is the name of your resource group prototype.

queue manager MQ.PROTO.QMGR.prototype-name

prototype-name is the name of your queue manager prototype.

queue MQ.PROTO.QUEUE.prototype-name

prototype-name is the name of your queue prototype.

channel MQ.PROTO.CHANNEL.prototype-name

prototype-name is the name of your channel prototype.

process MQ.PROTO.PROCESS.prototype-name

prototype-name is the name of your process prototype.





Tasks

In addition to creating profiles to restrict access to objects in both defined and prototype configurations, you can create profiles to restrict users from performing certain tasks.

RACF profiles can be created to restrict users from:

� Creating, modifying, or deleting scheduled actions� Editing global variables� Viewing and manipulating the enhanced audit log

These task-oriented profiles are described in the following table. In this table, required characters in each profile name are represented as bolded, capital letters (for example, ADMIN.SCHEDUPT). The remainder of the string, represented by lower-case, italicized characters (for example, scheduled-update-name) is your site-specific value.

namelist MQ.PROTO.NAMELIST.prototype-name

prototype-name is the name of your namelist prototype.

storage class MQ.PROTO.STGCLASS.prototype-name

prototype-name is the name of your storage class prototype.

Table 15. Profile Naming Conventions for Tasks

Task Profile Naming Convention Explanation

Scheduled actions ADMIN.SCHEDUPT.scheduled-update-name

scheduled-update-name is the name of the scheduled update. The creator of a scheduled update always has access to it.

Editing of global variables

ADMIN.GLVAR Users must have UPDATE access to alter, create, or delete global variables.

Manipulation of enhanced audit log

ADMIN.AUDIT Users must have at least READ access to view the audit log.

Table 14. Profile Naming Conventions for Prototype Configuration Objects

Prototype Profile Naming Convention Explanation



Generic profiles

Where access attributes are the same across resources (or tasks), you can save time by creating generic profiles. Generic profiles are created by using standard RACF wildcards (*, **, %). (Refer to your RACF documentation for more information on wildcards.)

Note: SAF searches for the most specific applicable profile. If you create both a resource-specific profile and a generic profile that covers that resource, the specific profile is used.

For example. assume that the authorization-checking level for a certain Configured System Group is Resource and the following two profiles exist:

� MQ.QMGR.SYSA.QMGR1.QUEUE.QUEUE1

This profile restricts access to a queue named QUEUE1 on a queue manager named QMGR1 on a system named SYSA.

� MQ.QMGR.SYSA.*.QUEUE.*

This profile restricts access to all queues on all queue managers on SYSA.

If you attempt to access QUEUE1, SAF uses the access attributes in the first profile (MQ.QMGR.SYSA.QMGR1.QUEUE.QUEUE1) to determine your authority.

Examples of generic profiles

Following are more examples of generic profiles. Refer to the tables above, if necessary, to review required characters in the naming conventions (remember that lower-case characters are converted to uppercase):

� ADMIN.*

This profile does the following:

– restricts creation, modification, and deletion of all scheduled updates– restricts editing of global variables– restricts viewing and manipulation of the enhanced audit log.

� ADMIN.SCHEDUPT.*

This profile restricts creation, modification, and deletion of all scheduled updates.



� MQ.QMGR.SYSTEM*.QMG*.PROCESS.myprocess

This profile restricts access to all processes named “myprocess” on any queue manager that begins with “qmg” on any system that begins with “system”.

� CSG.*

This profile restricts access to all configured system groups.

� Proto.Rg.*

This profile restricts access to all resource groups.

Multi-level Security: Implementing Configuration Database Security



Before implementing configuration database securityBefore you begin to implement configuration database multi-level security, you must create a new RACF class, which requires that you re-IPL MVS.

Implement security from your MVS terminalFollow these steps on your MVS system to implement security.

1. Inspect member KDSENV in the RKANPAR dataset (for example, &RHILEV.RKANPAR(KDSENV), locate the following environment variable defaults, and verify that the settings for each are as listed below:

KDS_KCF_EXT_SECURITY=YESKDS_KCF_SAFCLASS=$KCFADMNKDS_VALIDATE=YES

If you modify any of these values, you must add them to the end of the KDSENV member in the format shown above. These statements, respectively:

� Enable this product’s multi-level security feature.� Set the default name of a new RACF class for the Configuration Database

profiles (you may change the default name of $KCFADMN).� Enable user ID checking at the Candle Management Server (where the

Configuration Database resides).

2. Define the new $KCFADMN class. If necessary, refer to the sample source in member KCFRRCDE in TKANSAM.

3. Assemble and link the ICHRRCDE table.

4. Enter the new class in the RACF router table (ICHRFR01). Source for this entry can be found in TKANSAM, member KCFRFR01.

5. Re-IPL MVS.

6. Have the Security Administrator (or someone else with RACF SPECIAL authority) issue the following command to activate the new RACF class:

SETROPTS CLASSACT($KCFADMN) GENERIC($KCFADMN) RACLIST($KCFADMN)

7. From a RACF session, create profiles within $KCFADMN, using the rules and guidelines in the above sections.



Implement security from CandleNet PortalFollow these steps on CandleNet Portal to implement security.

1. Log on to OMEGAMON XE for WebSphere MQ Configuration. (From the list of available navigator views, select the Configuration view.)

2. Ensure you are in update mode.

3. Open the Defined View.

4. Select the Configured System Group that you wish to assign an authorization-checking level to (or define a new Configured System Group and select it).

5. In the Group section of the settings list, locate the Authorization Checking Level parameter. Select the level that you wish to assign to this Configured System Group, or select None.When a user attempts to access any resource in that Configured System Group, SAF will begin searching for a profile that corresponds (by naming convention) to that level. If none is found, it will search at the next higher level.

6. Click Save to save your changes.

Managing and Updating the Configuration 97

Managing and Updatingthe Configuration

IntroductionThis chapter contains information about updating and changing your configuration.

Chapter contentsUpdating and Changing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 98

7

Updating and Changing the Configuration


Updating and Changing the Configuration

Example of a change to the configuration that requires manual stepsIf the changes you make in CICAT are to configuration values that also require manual steps outside of CICAT, you must also perform the steps outside of CICAT when you update or change the values in CICAT.

For example, if you are using the persistent data store and you change the prefix for the procedure using CICAT, you must also copy the renamed procedure to your PROCLIB.

For step-by-step instructions for these tasks, see “Completing the Configuration” on page 63.

Overview of the process for updating or changing your configurationThe illustration shows the process for updating or changing your configuration.

FIGURE 3. Process for Updating and Changing Your Configuration

Using CICAT, make the changes you want to the configuration.

.

On the Runtime Environments (RTEs) panel in CICAT, use the L (Load libs after SMP/E select to load the target libraries to the runtime libraries.

If the changes are to values that require manual steps outside of CICAT to complete the configuration, perform the appropriate steps.

Index 99

Index

Aaccess control levels 86accessing

CICAT 57menu for configuring 21, 60queue managers 31your queue managers 79

address translation 52Adobe portable document format 11advanced features 33Advanced key 62agent address space 55agent running in agent address space 23agents 47alert emitters 47alert managers 47APF-authorization 67APF-authorizing load libraries 29authorization-checking levels 83authorized load library 22, 26authorizing external security program 31authorizing the external security program 79

Bbatch mode processing 33, 43

CCandle Installation and Configuration

Assistance Tool (CICAT) 37Candle Management Server 46Candle products 46Candle terminology 37Candle Web site 9CandleNet Portal 49CA-TOP SECRET

authorizing monitoring agent using 81example 81

changing the configuration 32, 97, 98checklists 17, 19CICAT

accessing the menu for configuring 60commands 62defaults 61defaults and restrictions 57definition 37displaying information in 62functions 62modes 43release 59restrictions 61starting 59version 59

CICS channels 82CMS types 48CNP server 47collect enhanced audit log information 26communication protocol requirements 52completing the configuration 24, 28, 29components 37, 46

definition of shared 46configuration database

securing 83configured system 84configured system group 84configuring

checklist for updating or changing 32definition 37detailed procedures 63OMEGAMON XE for WebSphere MQ

Configuration 25OMEGAMON XE for WebSphere MQ

Monitoring 22persistent data store 24, 25, 29products outside CICAT 29updating or changing 98

D

100 OMEGAMON XE for WebSphere MQ Configuration and Monitoring on OS/390 and z/OS

configuring agents in their own agent address space 55

configuring products 57prerequisites 20

configuring your queue managers 79Copying 68copying started task procedures 29copying VTAM definitions 29creating a new RTE 60creating scheduled actions 91CT/PDS 24, 46cumulative maintenance 37customizing

definition 37detailed procedures 77

customizing product outside CICAT 31

Ddefault monitoring group 22defaults provided with CICAT 61defined configurations 87deleting scheduled actions 91different address space 30Display 61displaying information in CICAT 62document organization 9Documentation 8documentation set information 8

Eedit recovery 61editing global variables 91enabling historical data collection 24End key 62enhanced audit log 91Enter key 62examples of generic profiles 92external security program 79

Ffunction keys 61

Ggateways 47generic profiles 92global VTAM major node 66granting authorizations to agents 79graphical user interface 47

HHELP command 61, 62HPNS TCP/IP protocol support 53hub CMS 48

Iimplementing configuration database

security 94implementing multi-level security 31implementing security

from CandleNet Portal 95from MVS 94

installingdefinition 37

installing agent into local CMS 24, 28interactive mode 43invoking ISPF 59ISPF 61

Llanguage library 22, 26load libraries 67loading libraries 24, 28local CMS 30

Mmenu for configuring 60migrating 37modes in CICAT 43modifying scheduled actions 91monitoring CICS channels 31, 82multi-level security 83, 94

Index 101

N

Nnetwork ID 52network interface card 52non-local CMS 30, 48

OOMEGAMON XE 47organization of the guide 9

Ppartition name 52PDF files, adding annotations 12persistent data store 46

copying procedures 68PFSHOW command 61planning your configuration 45pre-defined function keys 61preparing queue managers for

monitoring 54preventive maintenance

definition 37printing problems 11procedures

copying for the persistent datastore 68copying for the started tasks 65

processesconfiguring products 39installing maintenance 38installing products 38

PROCLIBpersistent datastore 68started tasks 65

product documentation 8profile types 86profile-naming conventions 87profiles you can create 86prototype configurations 90

RRACF

authorizing monitoring agent using 80

class 94example 80profiles 83, 86, 91profiles, generic 92

README APP command 62README command 62README ERR command 62README SYS command 62RECOVERY OFF command 61RECOVERY ON command 61registering with local CMS 22, 25remote CMS 48replicating products 31resource 85resource group 85restrictions in CICAT 61reviewing communication protocol

requirements 52reviewing configuration database

security 83RTE 37RTE sharing with SMP/E 67Runtime Environments (RTEs) 37runtime load libraries 67

SSAF 83, 92same address space 30secondary CMS feature 55security switch profiles settings 80seeding the CMS 69

background 69guidelines for products on distributed

platforms 69guidelines for products on MVS 70prerequisites for seeding products on

MVS 72using Manage Candle Services 73

setting up component trace 55sharing an agent address space 23, 55sharing components 50specifying

T

102 OMEGAMON XE for WebSphere MQ Configuration and Monitoring on OS/390 and z/OS

agent address space parameters 23, 27configuration parameters 26monitoring parameters 22

started taskscopying procedures 65

starting CICAT 21, 57system variable support 33

Ttarget load libraries 67TCP/IP requirements 52terminology 37

Uupdating

detailed procedures 97the configuration 32, 98

usingchecklists in this guide 19IP.PIPE 52IUCV interface 53

using an existing RTE 60using CICAT 61using multi-level security feature 83UTIL command 62

Vvarying the major node active 29verifying the configuration 30

CMS on different platform 76different address space 75same address space 74

VTAMapplids 52

VTAMLSTcopying the VTAM definition 66

WWebSphere MQ default objects 54

configuration and customization...

Documents