178
Administering OMEGAMON ® Products CandleNet Portal ® Version 195 GC32-9180-00 July 2004 Candle Corporation 100 North Sepulveda Blvd. El Segundo, California 90245

Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

  • Upload
    others

  • View
    21

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Administering OMEGAMON® ProductsCandleNet Portal®

Version 195

GC32-9180-00

July 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

Page 2: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

2 Administering OMEGAMON Products: CandleNet Portal, V195

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/REMOTE, Availability Command Center, Candle, Candle CIRCUIT, Candle Command Center, Candle Direct logo, Candle eDelivery, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleLight, CandleNet, CandleNet Command Center, CandleNet eBusiness Platform, CandleNet Portal, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, DEXAN, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness at the speed of light, eBusiness Assurance, eBusiness Institute, ELX, EPILOG, ESRA, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAMON Monitoring Agents, OMEGAVIEW, OMEGAVIEW II, PQEdit, Response Time Network, Roma, SitePulse, Solutions for Networked Applications, Solutions for Networked Businesses, TMA2000, Transplex, and Volcano.Trademarks and service marks of Candle Corporation: AF/Advanced Notification, AF/PERFORMER, Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Business Services Composer, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle eSupport, Candle Insight, Candle InterFlow, Candle Managing what matters most, Candle Service Suite, Candle Technologies, CandleNet, CandleNet 2000, CandleNet Conversion, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., CandleNet eBP Administrator, CandleNet eBP Broker Access for Mercator or MQSI, 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, Candle Vision, CCC, CCP, CCR2, 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, e2e, eBA*SE, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBX, End-to-End, eNotification, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, ER+, ERPNet, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, Managing what matters most, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NC4, NetGlue, NetGlue Extra, NetMirror, NetScheduler, New Times, New Team, New Readiness, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON/e, OMEGAMON Management Center, OSM, PathWAI, PC COMPANION, Performance Pac, Powered by Roma Technology, PowerQ, PQConfiguration, PQScope, 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, Tracer, Unified Directory Services, WayPoint, and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. Multi-Win and MetaFrame are trademarks of Citrix Systems, Inc. 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 may be trademarks or registered trademarks of their respective owners.

Copyright © April 2004, 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.

Page 3: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Contents 3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

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

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 13Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . 15

What’s New in Version 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23OMEGAMON Family of Products . . . . . . . . . . . . . . . . . . . . . . . . . . . 24What is OMEGAMON XE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25What is OMEGAMON DE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29OMEGAMON Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31What is CandleNet Portal?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 2. Preparing your CandleNet Portal Environment . . . . . . . . . . . . . 39Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Browser Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Desktop Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Logon Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Defining Global Parameters and Variables . . . . . . . . . . . . . . . . . . . . . 53Adding Platforms to the Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 3. User Administration and Customization . . . . . . . . . . . . . . . . . . 67User Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Adding, Editing and Removing Users . . . . . . . . . . . . . . . . . . . . . . . . 71Assigning User Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Contents

Page 4: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

4 Administering OMEGAMON Products: CandleNet Portal, V195

User ID for Take Action Commands . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 4. Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Error Messages and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84CandleNet Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Browser Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Using the Candle Technologies Service Console . . . . . . . . . . . . . . . . 93Setting a Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Regional Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Chapter 5. CandleNet Portal Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Replicating the CandleNet Portal Server Environment. . . . . . . . . . . 100Migrating Objects from CMW to CandleNet Portal. . . . . . . . . . . . . . 106Migrating Additional Users from CMW to CandleNet Portal. . . . . . . 108Migrating New CMW Managed Objects to CandleNet Portal . . . . . . 110

Appendix A. CandleNet Portal and the CMW . . . . . . . . . . . . . . . . . . . . . . . 111Features Exclusive to CandleNet Portal . . . . . . . . . . . . . . . . . . . . . . 112Conceptual Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Functional Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116CMW and CandleNet Portal Working Together . . . . . . . . . . . . . . . . 128

Appendix B. OMEGAMON Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . 133What is OMEGAMON Web Services? . . . . . . . . . . . . . . . . . . . . . . . 134Using OMEGAMON Web Services . . . . . . . . . . . . . . . . . . . . . . . . . 135Starting the SOAP Client and Making a Request . . . . . . . . . . . . . . . 136SOAP Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Page 5: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Tables 5

Table 1. CandleNet Portal Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 2. Where Objects are Stored for CandleNet Portal and for the CMW . . 106Table 3. Comparing CMW and CandleNet Portal Functions . . . . . . . . . . . . . 116Table 4. Predefined SOAP Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Table 5. Example of CT_Get SOAP Request sent/data Received. . . . . . . . . . 155

Tables

Page 6: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

6 Administering OMEGAMON Products: CandleNet Portal, V195

Page 7: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Figures 7

Figure 1. CandleNet Portal Application Window . . . . . . . . . . . . . . . . . . . . . . . 28Figure 2. OMEGAMON DE Graphic View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 3. OMEGAMON XE Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 4. Example Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 5. Desktop Client Instances to Two CNP Servers . . . . . . . . . . . . . . . . . . 50Figure 6. Windows Local Security Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 7. CNPS Data Source Config Parameters dialog.. . . . . . . . . . . . . . . . . . 91Figure 8. Data Snapshot Chart and Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Figure 9. Data Snapshot Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Figure 10. Universal Message Console Showing Messages Received . . . . . . . . 160Figure 11. Message Log Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Figures

Page 8: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

8 Administering OMEGAMON Products: CandleNet Portal, V195

Page 9: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preface 9

Preface

This manual describes the administration of your OMEGAMON® XE and OMEGAMON® DE products using the CandleNet Portal® interface, with planning and configuration guidelines for setting up your monitoring environment.

This guide describes:

� CandleNet Portal and how it is integrated into the OMEGAMON family of products

� the administrative features of CandleNet Portal

� troubleshooting procedures for CandleNet Portal

� how CandleNet Portal is different from the previous Candle system management client, the Candle Management Workstation® (CMW™)

� procedures for migrating objects from CMW to CandleNet Portal

� procedures for migrating the presentation files (for custom workspaces) and the CNPS database from one CandleNet Portal Server to another.

This guide also describes the OMEGAMON Web Services, which is installed automatically with the Candle Management Server (CMS). This service provides you with an industry-standard open interface into Candle’s OMEGAMON XE and DE solutions.

P

Page 10: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

About This Book

10 Administering OMEGAMON Products: CandleNet Portal, V195

About This Book

Who should read this book?Anyone whose job it is to plan and customize the CandleNet Portal environment. This includes

� system administrators

� system programmers

� network administrators

� Candle Support Center and Field Systems Engineers

This manual assumes you have already installed

� the OMEGAMON Platform: Candle Management Server® (CMS™), CandleNet Portal Server, CandleNet Portal client and, optionally, the CMW.

� one or more OMEGAMON XE or OMEGAMON DE products and you are familiar with the major features. Refer to the appropriate documentation for details.

Important: This guide assumes familiarity with the major features of CandleNet Portal. It is intended for advanced users of CandleNet Portal who already know how to build workspaces, define queries and links, create situations, and, for OMEGAMON DE, construct policies and create Navigator views.

Documentation set informationUsing OMEGAMON Products: CandleNet Portal complements the online help. It has hands-on lessons and detailed instructions for all CandleNet Portal features except user administration, which is described in this guide.

Administering OMEGAMON Products: CandleNet Portal describes the support tasks and functions required for the CandleNet Portal Server and clients, including CandleNet Portal user administration.

Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center describes the process of collecting historical data and either warehousing it or converting it to delimited flat files for use in third-party data applications.

Page 11: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preface 11

Adobe Portable Document Format

Installing Candle Products on Windows provides instructions to installing and configuring the OMEGAMON Platform on Windows (Candle Management Server, CandleNet Portal Server, and CandleNet Portal browser and desktop clients), and all OMEGAMON XE monitoring agents and alert managers running on Windows.

Use of MVS terminologyThe term MVS applies to the MVS, OS/390, and z/OS operating systems, unless specifically noted in this guide.

Page 12: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

About This Book

12 Administering OMEGAMON Products: CandleNet Portal, V195

Where to look for more informationFor more information about this 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

Ordering additional documentationTo order additional Candle Documentation CDs, contact your Candle Support Services representative.

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.

Page 13: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preface 13

Adobe Portable Document Format

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.

Page 14: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

About This Book

14 Administering OMEGAMON Products: CandleNet Portal, V195

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.

Page 15: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preface 15

Adobe Portable Document Format

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 support tools that include a range of services. For example, 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 Customer Service and Satisfaction by telephone or e-mail on the Candle Web site. Go to www.candle.com support section and choose the link to Support Contacts to locate your regional support center.

Page 16: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

About This Book

16 Administering OMEGAMON Products: CandleNet Portal, V195

Page 17: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What’s New in Version 195 17

What’s New in Version 195

New features and enhancementsCandleNet Portal® version 195 provides several new features and ease-of-use enhancements for OMEGAMON XE and OMEGAMON DE.

For the administrator

Java Runtime Environment (JRE) version support

CandleNet Portal extends the JRE version support to 1.3.1_12, so the complete range is now 1.3.1_04 to 1.3.1_12.

Browser clients can run different JRE versions from one another

In earlier versions of CandleNet Portal, all browser mode users were required to run the same version of the JRE as the CandleNet Portal Server. Now you have the option to set a specific version for browser clients that may be different from the CandleNet Portal Server or to set a wildcard to enable any supported JRE version (1.3.1_04 to 1.3.1_12) to be used by browser clients. See “Edit detectplugin.html” on page 42.

Http proxy parameter

A client parameter has been added that enables you to define the name used by Candle’s integral browser to identify itself to the http server. This is necessary if users get an error when they try to access the Internet from the browser view because the web server or its proxy does not recognize the browser identity. See “http:agent” on page 53.

W

Page 18: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

18 Administering OMEGAMON Products: CandleNet Portal, V195

Resource consolidation

The files used for event sounds and graphic views (maps, background images, icons, and style sheets) are now stored on the CandleNet Portal Server. Administrators no longer need to copy such resources to more than one location to have them accessible by both browser mode and desktop mode users that log onto that server.

IBM DB2 Universal Database (UDB)

IBM’s DB2 UDB replaces the Microsoft MSDE as the default database used by CandleNet Portal. UDB has a graphical user interface for administration. (In the CandleNet Portal help, we were able to build the ODBC Custom Query Example to report which users were logged on because we could easily see the CNPS database table constructs in the UDB user interface.)

System tray offset parameter

A new client parameter has been added to take into account the Windows task bar at the bottom of the screen when CandleNet Portal displays menus and dialogs. See cnp.systemtray.offset in Table 1: CandleNet Portal Global Parameters on page 53.

OMEGAMON XE

Remove offline managed systems

When an monitoring agent becomes unavailable its Navigator item is disabled. You can now remove the dimmed icon from the Navigator Physical view through the pop-up menu, instead of having to go to the Candle Management Workstation to remove it. See the CandleNet Portal Help topic, “Remove Offline Managed Systems” for details.

User ID authority for workspace administration

The Workspace Author Mode and Workspace Administration Mode permissions have moved from the User Administration authorities to a new authority: Workspace Administration. In their place are two new permissions: Author Mode Eligible and Administration Mode Eligible. When either of these is enabled, the user can toggle the mode on or off without being required to have an administrator-level user ID. See page 77 for details.

Page 19: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What’s New in Version 195 19

Hexadecimal support in formula editors

You can now use hexadecimal notation in the Properties (Filters and Thresholds tabs), Query, and Situation editors. This new capability allows such filtering as the See if value is within a range (BETWEEN) function for tape or DASD devices.

Managed system list editor

A managed system list is a defined set of managed systems, much like a mailing list. CandleNet Portal has a new editor for creating and maintaining managed systems lists for any logical grouping and apply them to:

� distribution lists for situations

� managed system assignments for queries

Sound for open events

Sound files (.wav) can be associated with situation states. For example, when a warning situation becomes true, a sound file will play when the event indicator appears on the Navigator item. You can mute the sound from the main toolbar. The options for setting up sound enable you to specify any one of these options:

� one sound for one situation

� one sound for all situations of the same state

� one sound for all situations of the same Candle agent type

Navigator hide

The Navigator view toolbar has a Hide button that collapses the Navigator and expands the adjacent workspace views to fill the gap. The right side of the status bar shows a Navigator icon, which you can click to restore the view. You can save the workspace with the Navigator minimized.

Save maximized view

In earlier versions of CandleNet Portal, you could maximize a workspace view to fill the entire work area, but you could not save the workspace in this state. Now you can: the next time you open the workspace it opens with the view maximized.

Page 20: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

20 Administering OMEGAMON Products: CandleNet Portal, V195

Column manipulation� Maintain column width settings

In earlier versions of CandleNet Portal, you could adjust table and message log column widths by dragging their borders, but you could not save these changes with the workspaces. Now you can save the changes with the workspaces.

� Change column order

In earlier versions of CandleNet Portal, you could control the order in which table columns appeared only through the Query editor. Now you can drag and drop a column where you want it to appear. This facility works in the Query editor, the Situation editor, and in the Filters and Thresholds tabs of the Properties notebook). It also works in the table and message log views.

� Lock a column

You now have the ability to fix the first column of any table view so it remains displayed when you scroll the table left or right. You can also save the locked column setting with the workspace.

� Sort order

In previous versions of CandleNet Portal, you could change the column by which a table was sorted by clicking a column heading. However, you could not save the sort order with the workspace. Now you can save the sort order.

Page size control

In earlier releases, multiple-row table views were broken into 100-row pages. You can now control the amount of data returned per “page” for a table, a message log, a pie chart or a bar chart view.

For example, a pie chart gives you one pie for each row of data returned, so 50 rows will give you 50 pies in the view. By limiting the page size to, say, three rows, you can have three pies on a page, using PageDown to turn to the next page. The smaller page size speeds up data retrieval to the workspace because only one page is retrieved at a time rather than the entire row set.

Page 21: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What’s New in Version 195 21

Note that you can still adjust the maximum row default for these views through the cnp.databus.pageSize parameter, as described in Table 1: CandleNet Portal Global Parameters on page 53.

Multiple item selection

The ability to use Ctrl+click or Shift+click to select multiple items is now available in the situation event flyover list and in the Situation editor tree. For example, you can select multiple open events in the flyover list and acknowledge them all at once, or you can select multiple situations and associate them with the current Navigator item.

Browser view URL

You can now use a simple reference to HTML files placed on the CandleNet Portal Server machine in the candle\cnb folder or a subfolder. This is especially useful when browser mode users log on to CandleNet Portal through a firewall.

OMEGAMON DE OMEGAMON DE includes all the features of OMEGAMON XE. Here are the new features in CandleNet Portal Version 195 that are exclusive to OMEGAMON DE:

Event Console view

The enhancements for column manipulation and page size control listed above also apply to the Event Console view.

The Filter Closed tool has been removed. If you want to see closed events, create a message log view.

Two new filters have been added to the toolbar: Filter Stopped and Filter Problem.

Managed system lists

As well as the applications for managed systems lists described above, you can use them for:

� managed system assignments in custom Navigator views

� policies correlated by business application group

Page 22: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

22 Administering OMEGAMON Products: CandleNet Portal, V195

Graphic view default graphic

In earlier versions of CandleNet Portal, the default background was a georeferenced map of the world. As well, if you wanted a different default image it could only be another georeferenced .IVL image. The new default is a world map in .JPG format, and you can specify your own .JPG image as the default. See “Change the default graphic or style sheet” on page 172.

Workflow editor activities

New activities based on OMEGAMON Web Services, such as Get a Candle Report and Execute an AF/Operator Command, have been added to the Workflow editor. These activities are available only with CT400, which is awaiting release at time of printing. See “OMEGAMON Web Services” on page 133.

Page 23: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 23

Introduction

IntroductionThis chapter introduces OMEGAMON XE and its user interface, CandleNet Portal. This chapter explains the architecture of OMEGAMON XE and how it is integrated into the OMEGAMON family of products.

Chapter contentsOMEGAMON Family of Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24OMEGAMON Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31What is OMEGAMON XE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25What is OMEGAMON DE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29What is CandleNet Portal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

1

Page 24: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Family of Products

24 Administering OMEGAMON Products: CandleNet Portal, V195

OMEGAMON Family of Products

The OMEGAMON family of products consists of a suite of real-time and historical performance and availability monitors. These products are the first line of defense in detecting, analyzing and resolving problems that can threaten critical systems and applications.

This guide deals with the administration of the CandleNet Portal server and client portion of the OMEGAMON Platform supporting your OMEGAMON XE and OMEGAMON DE solutions.

For information on the OMEGAMON II® solutions that are also part of the OMEGAMON family of products, refer to the documentation for those solutions.

Page 25: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 25

What is OMEGAMON XE?

What is OMEGAMON XE?

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

OMEGAMON XE solutions have a flexible, easy-to-use Java™ based interface that transforms complicated systems data into the pure business knowledge you need to run your enterprise.

OMEGAMON XE uses the concept of presenting information in a single window comprising a navigation tree and a workspace:

� The navigation tree, or Navigator, lights up with critical, warning and informational alerts so you can instantly deal with problems as they come up.

� Each workspace can be divided into multiple segments containing reports in the form of tables and charts, TN3270 emulator views, web browsers, text boxes, graphic views and event message logs. OMEGAMON XE is a powerful tool to help keep your enterprise up and running optimally.

How you can use OMEGAMON XEYou can use OMEGAMON XE to

� create situations (conditions to test when monitoring)

� establish your own performance thresholds and raise alerts when thresholds are exceeded or values are matched

� trace the causes leading up to an alert

� create and send commands to systems in your managed enterprise by means of the Take Action feature

� create comprehensive reports about system conditions.

� define your own queries, using the attributes provided by Candle’s monitoring agents, to monitor conditions of particular interest to you.

Page 26: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is OMEGAMON XE?

26 Administering OMEGAMON Products: CandleNet Portal, V195

An additional feature package, OMEGAMON® DE, is available with OMEGAMON XE. For information about its capabilities, see “What is OMEGAMON DE?” on page 29.

OMEGAMON XE featuresThe features listed below are available with the CandleNet Portal V190 interface for OMEGAMON XE. If you are using a later version of CandleNet Portal, additional features may be available.

Customized workspaces for each information group

CandleNet Portal retrieves monitoring data at regular intervals and sends the results to the workspace in the form of charts and tables. You can start monitoring activity and system status immediately with the predefined workspaces. With just a few clicks of the mouse, you can tailor your own workspaces to look at specific conditions, display critical threshold values in red, and filter incoming data so you see only what matters.

Workspace views

CandleNet Portal offers a set of views you can use to build and customize workspaces: � Table views display data the Candle monitoring agents

have gathered. You can also display data from ODBC databases.

� Chart views—pie, bar, plot, gauge—also display data from Candle monitoring agents.

� Take action view lets you enter a command or select a predefined command, and execute it on any system in your managed network.

� Message log view shows the status of the situations running on your managed network.

� Notepad view opens a simple text editor for writing text that can be saved with the workspace.

� Terminal view starts a 3270 or 5250 session for working with OS/390 applications.

� Browser view opens the integrated browser.

Linked workspaces

If you often go from one workspace to another, you can build a link between them to speed the transition. You can also build links that originate from a table or from a bar or pie chart, and use relevant data from the source link to determine the target link.

Page 27: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 27

What is OMEGAMON XE?

Historical data You can configure CandleNet Portal to retain data samplings in history files and, if you have data warehousing, roll off to a historical database. Using chart and table views, you can then review what happened hours, days, or weeks past to find a pattern, or filter the data to see specific areas of interest.

Custom queries Every Candle agent comes with a set of predefined queries for every attribute group. These queries tell the CMS what monitoring data to retrieve from the agent for the chart or table view. You can create your own queries to specify exactly which attributes to retrieve, thus saving valuable resources. For example, you can build a filter into the query to retrieve only records whose file size is greater than 5 megabytes.

Additionally, you can write SQL queries to ODBC data sources and apply the results to any chart or table. This enables you to show Candle data and data from other sources (such as third-party databases) in a single workspace.

Interaction with systems from your console

The Take Action feature lets you enter a command or select a predefined command, and execute it on any system in your managed network.

Conditional alerts with the Situation editor

You can write comparisons with threshold values that CandleNet Portal tests against monitored data. When it finds a matching value (or one within a range), it displays an indicator to alert you and, optionally, plays a sound.

Managed system lists

You can create and maintain named lists of managed systems that can be applied to:� situation distribution lists� policies correlated by business application group � queries � custom Navigator managed system assignments

User administration

CandleNet Portal provides the user administration feature for adding new user IDs, complete with selectable permissions for the major features and specific managed systems.

Universal Agent support

Candle's OMEGAMON Universal Agent is an agent you can configure to monitor any data you collect. It lets you integrate data from virtually any platform and any source, such as custom applications, databases, systems, and subsystems. Your defined data providers are listed in the Navigator, and default workspaces are automatically created for them.

Page 28: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is OMEGAMON XE?

28 Administering OMEGAMON Products: CandleNet Portal, V195

CandleNet Portal windowThe CandleNet Portal window displays information about your enterprise. On the left is the Navigator, which shows the arrangement of your monitored network and any alerts associated with systems and applications on the network. On the right is a workspace. As you select each item in the Navigator, the workspace changes to show views for that item. Figure 1 on page 28 shows the CandleNet Portal application window.

Figure 1. CandleNet Portal Application Window

Page 29: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 29

What is OMEGAMON DE?

What is OMEGAMON DE?

What OMEGAMON DE doesOMEGAMON DE offers a dashboard view of your enterprise; a single point of control for managing the resources your business-critical applications rely on. For example, a typical IT network might have a web server running on Windows, an application server running on UNIX, a database on OS/390, and a transaction processor on CICS on the mainframe. OMEGAMON DE brings all these views together in a single window, so you can see when any component is not working as expected.

OMEGAMON DE featuresOMEGAMON DE provides all the features of CandleNet Portal included with OMEGAMON XE, plus these application integration components. If you are using a later version, additional features may be available.

Multiple applications in one workspace

In one workspace you can build a table or chart with data from one type of monitoring agent, and another table or chart with data from a different agent, showing views from as many different agent types as are included on that branch of the Navigator.

Linking between workspaces and Navigators

You can define a link from a workspace associated with one application to the workspace of another.And you can link between Navigators.

Graphic view The Graphic view lets you place icons of Navigator items on a map or other background graphic, giving you a visual orientation for quick detection of problems anywhere in your monitored enterprise. You can zoom in and you can add such graphics as floor plans and organization charts. Figure 2 on page 30 illustrates a Graphic view.

Custom Navigator views

CandleNet Portal comes with the Navigator Physical view, which organizes your managed enterprise by operating platform and agent type, and the Navigator Business view, which initially shows one Navigator item or, if you have a Candle Management Workstation® (CMW™) installation, a hierarchy of your managed objects. You can also define Navigator views for any logical hierarchy, such as a departmental or site hierarchy

Page 30: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is OMEGAMON DE?

30 Administering OMEGAMON Products: CandleNet Portal, V195

Figure 2 on page 30 shows the CandleNet Portal application window with the Graphic view feature of OMEGAMON DE.

Figure 2. OMEGAMON DE Graphic View

Event Console view

In a single view, you can see the entire list of alerts that have occurred over a certain period. The event Console view lists each alert, including such information as the age of the alert, where and when it occurred, and the situation name. The console has a toolbar for filtering the view and a pop-up menu for managing alerts.

Automation The Workflow editor enables you to design sets of automated system processes, called policies, to resolve system problems. A policy performs actions, schedules work to be performed by users, or automates manual tasks.

Page 31: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 31

OMEGAMON Platform

OMEGAMON Platform

The OMEGAMON Platform provides the infrastructure for your OMEGAMON XE and OMEGAMON DE products.

Client-server-agentThe client-server-agent implementation includes:

� a client, CandleNet Portal, with a Java-based user interface for viewing and monitoring your enterprise. See “What is CandleNet Portal?” on page 34.

� a CandleNet Portal server that performs common functions such as retrieving, manipulating, and analyzing data from the Candle agents in your enterprise.

� a Candle Management Server® (CMS™), which acts as a collection and control point for alerts received from the agents, and collects performance and availability data from those agents.

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

Additional componentsAdditional components used are described below.

Integrated Web Server

The Candle integral web server is installed and configured automatically when you install the CandleNet Portal Server. This enables you to start CandleNet Portal browser mode as soon as you have a user ID and the URL for the Candle web server.

IBM DB2 Universal Database (UDB)

IBM’s DB2 Universal Database is the default database used by CandleNet Portal. It is included as part of your OMEGAMON product package, and you install it from an IBM-provided CD-ROM on the machine where the CandleNet Portal Server will be installed or upgraded to version 195. The DB2 UDB has a graphical user interface for administration. In CT400, which

Page 32: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Platform

32 Administering OMEGAMON Products: CandleNet Portal, V195

is awaiting release at time of printing, DB2 UDB can be used to configure a Candle Data Warehouse for historical reporting.

The CandleNet Portal Server (CNPS) uses UDB as a database repository. DB2 UDB provides upgrade flexibility as we continue to add new features to CandleNet Portal. UDB is a true client/server database that provides enterprise-class reliability capable of supporting business-critical requirements.

If you have Microsoft SQL Server version 7.0 or 2000 installed, you can choose to use it instead of DB2 UDB as the CNPS database repository, although we encourage migration to DB2 UDB.

Candle Management Workstation (CMW)

Although the CandleNet Portal client replaces the Candle Management Workstation as the user interface for your Candle monitored environment, you will need the CMW for one maintenance task: removing from the Navigator view any managed systems no longer in use.

The CMW also has some features not available in CandleNet Portal, such as the Universal Message Console and the Policy Microscope. See “Functional Comparison” on page 116.

Data flow among componentsFigure 1 shows the data flow among the components. The CMS is connected to the Candle monitoring agents, to the CandleNet Portal Server, and to the CMW. The CandleNet Portal client connects to the CandleNet Portal Server. Figure 1 shows two possible CandleNet Portal configurations: one for desktop mode and the other for browser mode.

� For browser mode, the browser client framework is installed on the same machine as the CNP Server. Users start the product in their browsers by entering the URL for the web server. First-time startup involves downloading the client software. This ensures fast operation and automatic version updates through the browser.

� For desktop mode, the desktop client is installed on each user’s desktop. Users start the product as they would any other application.

Click an item in the Navigator to open its default workspace. If the workspace has any chart or table views, the CMS immediately takes a data sampling at the Candle agent (or agents) and sends the values back to the workspace by way of the CandleNet Portal Server.

Page 33: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 33

OMEGAMON Platform

Similarly, the CMS runs situations and policies at the Candle agents. When the conditions of a situation have been met, the CMS posts an alert on the Navigator by way of the CandleNet Portal Server.

Figure 3. OMEGAMON XE Data Flow

managed systemshub CMS

CMW

CandleNet Portal CandleNet Portal Server

desktop mode

browser modebrowser client frameworkCandle web server

CNPSDatabase

and/or remote CMSsclient

Page 34: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is CandleNet Portal?

34 Administering OMEGAMON Products: CandleNet Portal, V195

What is CandleNet Portal?

What CandleNet Portal doesCandleNet Portal is the interface for your OMEGAMON XE products. In the same way you use your browser home page as a starting point for navigating the Internet, you use CandleNet Portal to get a high level overview of your network environment. One section of the window displays the Navigator, a tree-like view of your monitored network, from the top level ( ENTERPRISE) down to individual groupings of information collected by Candle monitoring agents. The rest of the window is filled with views pertinent to the chosen item in the Navigator tree. From the top level or from your home workspace, you can navigate to specific locations to check activity and investigate problems.

Figure 4 on page 35 shows a workspace for the item chosen in the tree. This workspace was designed with bar charts and a table containing critical, warning, and informational thresholds. You can create and customize additional workspaces for every item in the tree.

The event indicators that appear in the tree, or Navigator, are the results of tests, called situations, that run on your monitored systems. When the condition described in the situation is true, a critical icon, warning icon, or information icon overlays the affected items in the tree. You use the Situation editor to set up conditional alerts that monitor your environment automatically.

You use the Workflow editor to set up policies to automate your environment.

Page 35: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 35

What is CandleNet Portal?

Figure 4. Example Workspace

Modes of operationCandleNet Portal offers two modes of operation:

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

� browser mode, in which the thin client software is downloaded from the CandleNet Portal Server to your machine the first time you log on to CandleNet Portal from your browser, and thereafter when there are software updates.

Page 36: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is CandleNet Portal?

36 Administering OMEGAMON Products: CandleNet Portal, V195

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

Historical Data CollectionIn addition to the real-time reports offered by CandleNet Portal workspaces, you can set up historical data collection to store and save the data being collected by your monitoring agents. You can specify

� attribute groups for historical data collection

� data collection intervals

� data warehousing interval (if you choose to write your data to a data warehouse)

� storage location for the collected data. Historical data can be stored either at the location of the monitoring agent or on the Candle Management Server (CMS).

To ensure that data samplings are saved to populate your predefined historical workspaces, you must first configure and start historical data collection. This requirement does not apply to workspaces using attributes groups that are historical in nature and show all their entries without your starting data collection separately.

See the topic on configuring historical data collection in the CandleNet Portal help or user’s guide. See also the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center.

Platforms supportedCandleNet Portal is supported on the following platforms:

� Windows XP Professional Edition with Service Pac 1 or higher

� Windows 2000 with Service Pac 3 or higher

Page 37: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Introduction 37

What is CandleNet Portal?

What does a system administrator do?A system administrator has the highest level of authority and can access all OMEGAMON features.

This list represents the types of tasks a system administrator might perform:

� grants access to other users� sets thresholds for the attributes provided by a product� creates situations using the visual programming facilities of CandleNet

Portal� sets the severity of a situation and what, if any, sound should play when

the situation is true and an event opens� decides which situations apply to which managed systems, a process

called distribution� creates graphical views and places icons in them for monitoring� provides expert advice to display when certain situations evaluate true� creates policies, which are actions to take when situations evaluate true

What’s nextAfter the OMEGAMON product components have been properly installed and the servers started, you can perform the administrative tasks necessary to complete the setup and customization of your CandleNet Portal environment.

Page 38: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is CandleNet Portal?

38 Administering OMEGAMON Products: CandleNet Portal, V195

Page 39: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 39

Preparing yourCandleNet Portal

Environment

IntroductionThis chapter covers the necessary tasks to prepare the monitoring environment. It also describes the global parameters and variables you can set for the browser client (or each desktop client).

Chapter contentsOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Browser Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Logon Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Defining Global Parameters and Variables . . . . . . . . . . . . . . . . . . . . . . . . 53Adding Platforms to the Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2

Page 40: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Overview

40 Administering OMEGAMON Products: CandleNet Portal, V195

Overview

After installing and configuring the OMEGAMON Platform components, you need to perform some administrative tasks to prepare the environment.

JRE versions 1.3.1_04 to 1.3.1_11When users log on to CandleNet Portal through Internet Explorer, they will be prompted to install the JRE (Java Runtime Environment) if it is not on the machine. They can choose to download and install from the internet or from the intranet. If your site allows only intranet access, you need to provide the JRE setup files in the CNPS directory.

Desktop mode users are also required to have one of the supported JRE versions installed.

Logon ID� Your OMEGAMON Platform installation comes with a sysadmin user ID so

you can start CandleNet Portal and add more user IDs.

� If the Candle Management Server (CMS) has been set to Validate User, the user ID for CandleNet Portal must also be added to the network domain user accounts or to the operating system where the CMS is installed, including password.

Browser mode� Systems where users will start CandleNet Portal from their browsers

require adequate space for the downloaded program files.

� The Internet Explorer settings may need some adjustment.

� The settings for User groups on Windows 2000 need to be changed.

� You can personalize the CandleNet Portal banner to show your company logo and provide a link to your web site.

Add platforms to the Navigator The Navigator Physical view in CandleNet Portal shows the operating platform below the enterprise level. The operating platform name is followed by the word “Systems”, as in “Linux Systems” or “OS/390 Systems”. Some

Page 41: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 41

Overview

operating platforms can be broken down further. If your environment has such platforms and you would like each to have its own Navigator item, with all systems of that type contained there, you can edit the osnames file to add them.

Defining global parametersCandleNet Portal has default settings for parameters that apply to all users connected to the same CNP Server. You can adjust these global settings, such as the default hostname for the terminal emulator, through Manage Candle Services.

Page 42: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Browser Client

42 Administering OMEGAMON Products: CandleNet Portal, V195

Browser Client

OverviewWhen the CandleNet Portal Server is installed, so too is Candle’s proprietary web server. Users start browser mode by entering the URL for the machine’s web server.

The advantages of browser mode are:

� Easy deployment. The browser mode client is installed the first time users log on to the URL for the CandleNet Portal Server.

� Software upgrades are automatic. When users log on, the browser mode client is checked against the one at the CandleNet Portal Server and downloads a newer version from the Server if one is detected.

� Global parameter settings are set once for all users connected to the same CNP Server.

� Workspaces have identifying URLs, which can be emailed as links to other users or saved with your Internet Explorer Favorites.

Java Runtime EnvironmentThe CandleNet Portal Server, desktop client and browser client run Java-based software. Each of these components must have a version of the Sun Microsystems JRE installed: any version from 1.3.1_04 to 1.3.1_11 (subject to change).

When you install the CandleNet Portal Server or desktop client, the installer checks that you have one of these JRE versions and, if not, takes you to Sun’s Java 2 Platform, Standard Edition (J2SE) web page for downloading the latest supported Version 1.3 (http://java.sun.com/j2se/1.3/download.html). This check also takes place at the browser client when a user logs on to CandleNet Portal from Internet Explorer.

Edit detectplugin.html

Detectplugin.html is on the CNP Server machine in the candle\cnb directory. You do not normally need to change this file unless one of the following conditions is true:

Page 43: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 43

Browser Client

� You want browser clients to be able to run different supported versions of the JRE from one another. Or, you want browser clients to all run the same supported version of the JRE and that version is different from the one used by the CandleNet Portal Server machine. For example, the default is 1.3.1_04, but you want to run 1.3.1_10. (Step 3 below.)

� Your site does not allow Internet access and you have downloaded the JRE installation program for the latest version supported on CandleNet Portal from the Sun Microsystems web site to the \candle\cnb directory of your CandleNet Portal Server installation. (Step 4 below.)

Do the following to edit detectplugin.html:

1. On the drive where you installed the CandleNet Portal Server, open:candle

cnb

2. Open detectplugin.html with Notepad or other text editor.

3. To change the JRE version number required for browser clients, find var javaVersion near the top of the file and change to * or specify a version number:

var javaVersion = “*”

to enable browser clients to use any CandleNet Portal-supported JRE version: 1.3.1_04 to 1.3.1_11. That means one user could have JRE 1.3.1_07 and another JRE 1.3.1_11 and both could start CandleNet Portal successfully.

var javaVersion = “1.3.1_11”

where 1.3.1_11 is the version number of the JRE to be used by all browser clients, from 1.3.1_04 to 1.3.1_11.

If the user’s machine does not have the version of JRE that you indicate in the detectplugin.html file (or one of the supported versions if you used *), they will be prompted to install it.

4. To specify the location of the JRE installation program, find var filename near the top of the file and change “EMPTY” to the name of the Sun Java Plugin installation file name:

var filename = “j2re-1_3_1_11-windows-i586-i.exe”

The path you enter is relative to the c:\candle\cnb directory.

5. Save and close the file.

Page 44: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Browser Client

44 Administering OMEGAMON Products: CandleNet Portal, V195

Multiple versions of JRE

If you have different versions of the JRE installed locally, the different versions can coexist. At each machine where the CandleNet Portal browser client will be started, you need to check and change these settings:

� Internet Explorer setting to not specify a Java version to use

� Java Plug-in Control Panel to configure the Java Plug-in to load the supported JRE version.

Internet Explorer

If, after installing the JRE, you encounter problems with non-CandleNet Portal applets, such as IBM’s Host-on-Demand (HOD) product, do the following.

1. Start Internet Explorer and select Internet Options from the Tools menu.

2. In the Advanced tab, scroll down to the Java (Sun) section and make sure the checkbox, which corresponds to the latest version of JRE installed on this machine, is unchecked.

3. If the Internet Explorer security level is set to high, adjust the Security tab settings to run CandleNet Portal. See “Internet Explorer security settings” on page 47.

4. Restart Internet Explorer.

Java Plug-in Control Panel

When the Java Plug-in is installed on your machine, an entry is added to the Windows Control Panel. The JRE must be set to one of the supported Java versions. Otherwise, you will get an error when you try to log on to CandleNet Portal.

1. Open the Windows Control Panel.

2. Find the version of Java you want to use for CandleNet Portal and double-click the Java Plug-in 1.3.1_11 icon (or right-click and select Open).

Page 45: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 45

Browser Client

3. In the Advanced tab, scroll through the list of Java Runtime Environments, select the Candle-supported JRE version to run, and click Apply.

Troubleshooting

If you have trouble getting the CandleNet Portal Browser Client to run under Internet Explorer because of the JRE level, do the following:

� If you installed a version of the JRE that is later than one of the supported versions, skip steps 1 and 2.

� If you installed one of the supported versions of JRE listed above, but did not accept the default settings, complete all the steps.

1. Uninstall the JRE 1.3.1_04 to 1.3.1_11.

2. Reinstall the newest version of JRE supported by CandleNet Portal (1.3.1_11, subject to change) and accept the defaults.

3. In Internet Explorer, select Internet Options from the Tools menu.

4. In the Advanced tab, scroll down to the Java (Sun) section and make sure the box is unchecked.

5. Restart Internet Explorer.

First time logonThe first time users enter the URL for CandleNet Portal, the Java plug-in transfers the necessary files to their computers from the CandleNet Portal Server machine. The transfer of files goes from the candle\cnb directory to their computers.

The next time users enter the URL, the browser mode software does not need to be downloaded again, unless a new version of CandleNet Portal has been installed.

Page 46: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Browser Client

46 Administering OMEGAMON Products: CandleNet Portal, V195

The Java plug-in maintains the version levels of the files on users computers and compares them with the version levels on the web server. If it detects files that are older than the ones on the web server, it downloads the latest files.

Be sure you have some free space for the downloaded files on the drive where Windows is installed. If the disk runs out of space during the download, you will not be warned. However, when you attempt to start CandleNet Portal, no logon dialog will appear.

Starting CandleNet Portal browser mode

1. Start Internet Explorer version 6 or higher.

2. In the Address field, enter one of the following URLs for the web server, replacing hostname with the host name or IP address of the CandleNet Portal Server machine:

If your configuration requires an external web server to connect to the CandleNet Portal Server rather than the Candle integral web server, you need not do anything unless the client must pass through a NATted firewall or secondary NIC to access the web server, which requires you to create a CNP Server Interface to provide the IP address and port number. See the section for configuring the CandleNet Portal Server in the guide, Installing Candle Products on Windows.

3. When the Logon dialog opens, type your Logon ID and, if required, your password, then click OK.If this is the first time you have started browser mode on this computer and you have the correct version of the JRE installed, the client software will be downloaded. This takes a few moments.

If you do not have the required version of the JRE installed, you will be prompted to install it. After CandleNet Portal installs the proper version of the JRE onto your system. The installation of CandleNet Portal continues.

http://hostname:1920///cnp/client Candle’s integral web server

http://hostname External web server

http://hostname/?ior=internet.ior External web server with network address translation (NAT) or secondary network interface card (NIC)

Page 47: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 47

Browser Client

Internet Explorer security settingsIf you have your Internet Explorer security level set to high, you must adjust the settings to run CandleNet Portal. Otherwise, CandleNet Portal cannot run in browser mode.

Check the security settings

1. In Internet Explorer, select Internet Options from the Tools menu.

2. Select the Security tab.

3. Click Internet if you are running CandleNet Portal through the Internet; -OR- Intranet if you are running CandleNet Portal through your intranet.

4. Change your security settings to Default Level and click OK to save.

Keep current security settings

If you wish to keep your current security settings, you can add the CandleNet Portal web site to your Trusted Sites zone.

1. Start Internet Explorer.

2. Select Internet Options from the Tools menu.

3. Select the Security tab.

4. Click the Trusted Sites icon, click Sites, and enter the URL for CandleNet Portal.

5. Uncheck the box that checks for (https:) for all sites at this zone, click Add, then OK to save. Choose the medium security level or lower for all sites in the Trusted Sites zone.

Windows write and delete privilegesStarting with Windows 2000, write and delete privileges for certain folders and registry keys were removed from the Users group. These privileges are required for anyone intending to install and run CandleNet Portal in browser mode. Otherwise, users will encounter Java exception errors when attempting to start the product.

Before users can start CandleNet Portal in browser mode, the Windows administrator must assign the required permissions to individual user IDs or the Users group, or create a new group with the necessary permissions and

Page 48: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Browser Client

48 Administering OMEGAMON Products: CandleNet Portal, V195

assign users to this group in addition to the Users group. The required permissions are:

� Write and Delete permissions on the directory where Windows is installed (such as C:\WINDOWS).

� Set Value, Create Subkey, and Delete permissions on registry key HKEY_LOCAL_MACHINE\SOFTWARE.

Note: As well as CandleNet Portal browser mode, the Windows permissions scheme affects other third-party software installed through Internet Explorer.

Adding your company logo and URLCandleNet Portal in browser mode has a banner frame showing the Candle company logo, with a link to candle.com. You can personalize the CandleNet Portal browser interface by replacing the Candle logo and URL with your own.

For best results, we recommend you use a company logo image 22 pixels high. A shorter or taller image may not look as expected.

1. On the drive where you installed the CandleNet Portal Server, open:candle

cnb

2. Select bannerimage.html and open it with Notepad.

3. Edit the HREF and IMG SRC tags for your organization’s URL and logo graphic file: � Change 349 and 22 to the width and height of your image in pixels.

� Replace “http://www.candle.com/” with your organization’s URL (in both places).

� Replace “logo_bar_tiny.gif” with the name of your organization’s logo GIF or JPG file.

4. Save the file and exit Notepad.

5. Copy the logo graphic named in step 4 to the same directory as bannerimage.html (candle\cnb).Users will now see your company logo on the right-hand side of the CandleNet Portal banner the next time they start browser mode.

Page 49: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 49

Desktop Client

Desktop Client

Candle web server has been disabledIf you have disabled the integral web server, you need to install an external web server for the images and style sheets to be available for the graphic view. You also need to edit the application parameters at every desktop client to specify the correct URL for the DataBus ior. See “Desktop mode – add URL to external web server” on page 94.

Starting desktop mode on another serverWhen installing the desktop client, you designate a home CandleNet Portal Server. If your Candle environment has multiple CandleNet Portal Servers, you can define separate desktop instances to point to other servers.

Figure 5 shows two CNP Servers connecting to the same hub CMS; one CNP Server for testing and the other for production. You could also create an instance for a CNP Server that connects to a different hub CMS.

Create a CandleNet Portal instance

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click CandleNet Portal – Desktop and select Create Instance from the popup menu.If other instances of CandleNet Portal have been created, you will see more than one in the list. Create Instance is disabled for all but the original CandleNet Portal instance.

3. In the CandleNet Portal dialog, enter a name to identify the instance and click OK.

4. In the Configure Application Instance dialog, enter the host name of the CandleNet Portal Server you want to connect to.

5. Click OK.The new CandleNet Portal instance is added to the list.

Page 50: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Desktop Client

50 Administering OMEGAMON Products: CandleNet Portal, V195

Figure 5. Desktop Client Instances to Two CNP Servers

Start another CandleNet Portal instance

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Double-click the CandleNet Portal desktop instance you want to start.

Remove a CandleNet Portal instance

If you no longer want the CandleNet Portal instance in the Manage Candle Services list, remove it.

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click the instance of CandleNet Portal you want to remove.

3. Select Remove Instance from the popup menu.

managed systems

hub CMSCandleNet Portal

and/or remote CMSs

desktop client

CandleNet Portal Servers

Page 51: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 51

Logon Requirements

Logon Requirements

OverviewWhen you start CandleNet Portal, the Logon dialog comes up. This dialog supplies fields for entering your user credentials needed to establish a connection between the CandleNet Portal client and the server. For information on assigning user permissions, see “User Administration” on page 68.

Logon dialogThe fields on the logon dialog are:

Target system

Application name is the application you are logging on to, CandleNet Portal.

Application server is the host name of the system where the CandleNet Portal Server is running.

User credentials

Logon ID is a text box for typing your assigned user ID for CandleNet Portal. Use sysadmin the first time you log on after installation.

Password is a text box for typing your password for CandleNet Portal. It is required and available only if the CMS is set for user validation. See “About passwords”, next.

Your logon ID is verified by the CandleNet Portal Server. Additionally, if the CMS has been set for user validation, the user ID and password are also verified.

Page 52: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Logon Requirements

52 Administering OMEGAMON Products: CandleNet Portal, V195

About passwordsThe user ID for logging on to CandleNet Portal consists of a one-word name and may include a password. Passwords are defined to the domain or operating system where the CMS resides:

Passwords are required for CandleNet Portal logon only if the CMS is set to Validate User. When users log on to CandleNet Portal, their user IDs are

validated at the CandleNet Portal Server, then with their passwords at the domain or operating system of the CMS.

Configuring the CMS to validate users

To configure the CMS to validate a user:

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click Candle Management Server, then select Reconfigure from the pop-up menu.

3. Check Security: Validate User.

User licenseCandleNet Portal comes with an initial five-user license, so up to five users can be logged on to the CandleNet Portal Server at one time. It does not distinguish among users IDs, only the number of users logged on.

If, while attempting to log on to CandleNet Portal, you get a message saying that the license count has been exceeded, click OK. You can either ask someone to log off so you can log on, or contact Candle Customer Support to increase the number of licenses for your site. See “Candle Customer Service and Satisfaction” on page 15.

Windows Control Panel > User Accounts > Advanced tab, then click Advanced

UNIX Password file

OS/390 or z/OS Candle’s Network Access Method security feature or a third-party security package (RACF, CA-ACF2, or CA-TOP SECRET)

Page 53: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 53

Defining Global Parameters and Variables

Defining Global Parameters and Variables

CandleNet Portal client parametersCandleNet Portal enables you to change the parameters that apply to all users. The CandleNet Portal client also supports the use of an HTTP proxy server. See “Enable the HTTP Proxy Server” on page 56.

Edit global parameters

To edit the global parameters:

1. Start > Programs > Candle OMEGAMON XE > Manage Candle Services from one of the following machines:

– where the CandleNet Portal Server is installed.

– where the CandleNet Portal desktop client is installed.

2. Right-click CandleNet Portal – Desktop or CandleNet Portal – Browser, then select Reconfigure from the pop-up menu.

3. Double-click the parameter whose value you want to change.

4. In the Edit CandleNet Portal Parm dialog, type a value and check In Use.

Table 1. CandleNet Portal Global Parameters

Argument Description

http.nonproxyhosts When Enable HTTP Proxy Server Requests is checked (see next subsection), the servers in this list will bypass the proxy. Separate each server name with a vertical line (|). See “Enable the HTTP Proxy Server” on page 56.

http:agent Defines the name used by Candle’s integral browser to identify itself to the http server. Required only if your site’s web server or its proxy requires a different browser identity before it will enable the browser view to access the Internet. See step 7 on page 57.

Page 54: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Defining Global Parameters and Variables

54 Administering OMEGAMON Products: CandleNet Portal, V195

ice.browser.http.agent This is the same as http:agent and overrides that setting when defined.

ice.pilots.html4.imageAnimation Controls whether or not browser view supports animated .gif images; <true | false>. Default: true.

ice.browser.verbose Used in problem determination to gather more specific trace information related to the browser view. Default: false.

cnp.history.depth Number of workspaces to maintain in the back / forward history navigation stack. Default: 20.

cnp.databus.pageSize Number of rows to fetch in single logical page. Default: 100 rows. Although there is no limit to what you can set here, the larger the page size, the more memory required at the client and CNP Server. Keep the maximum to a practical number.

cnp.terminal.cache.entries Maximum number of active terminal emulator sessions. Default: 50.

cnp.terminal.script.entries Maximum number of user terminal emulator scripts. Default: 256.

cnp.terminal.host Default terminal emulator hostname.

cnp.terminal.port Default terminal emulator port number. Default: 23.

cnp.terminal.type Default terminal emulator type. When specifying a terminal type, enclose the terminal type within double quotes and enter one of these supported names:� IBM 3270 (24x80)� IBM 3270 (32x80)� IBM 3270 (43x80)� IBM 3270 (27x132)� IBM 5250 (24x80)

Table 1. CandleNet Portal Global Parameters (continued)

Page 55: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 55

Defining Global Parameters and Variables

cnp.encoding.codeset String encoding code set identifier.

cnp.publish.url Browser mode only: Enables URL identifiers for workspaces. Default: true.

cnp.publishurl.delay Browser mode only: When you make a workspace switch, allows the JCM event queue to settle down before the browser initializes the new applet and destroys the old applet. Default: 1 second.

Important: This parameter should only be modified in conjunction with Candle Customer Support.

cnp.heartbeat.interval Databus to Server ping interval (in seconds). Default: 30.

cnp.pipeline.factor Databus to Server Pipeline monitoring factor (in Heartbeat cycles). Default: 2.

cnp.drag.sensitivity Number of pixels the mouse must move before drag operation begins. Default: 7.

cnp.systemtray.offset CandleNet Portal factors in the Windows task bar at the bottom of the screen when sizing menus and dialogs for display. Default: true.

cnp.playsound.interval Number of seconds before the same sound file can be played again. If events open frequently, this setting provides sound pause. Default: 10 seconds.

Table 1. CandleNet Portal Global Parameters (continued)

Page 56: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Defining Global Parameters and Variables

56 Administering OMEGAMON Products: CandleNet Portal, V195

Enable the HTTP Proxy Server

If your site uses an HTTP proxy server, you need to enable it for browser view access to the Internet.

cnp.http.url.DataBus Desktop mode only: The URL for the cnps.ior file, which is required for the CNP Server to locate the graphic view images and style sheets. The default setting, which does not show, assumes the integral web server. If it has been disabled, you must enter the URL for the external web server. See “Disabling the Candle web server” on page 94.

When you set this parameter, it overrides the settings of the other cnp.http.url parameters for protocol, port, and path.

kjr.trace.mode LOCAL or REMOTE RAS1 tracing option. Default: LOCAL.

kjr.trace.file File name of RAS1 trace log if trace mode is LOCAL.

kjr.trace.params RAS1 trace options. Default: ERROR.

kjr.trace.thread Determines whether trace calls are threaded.

kjr.trace.priority Sets tracing thread priority.

kjr.trace.client_name Sets identifier used to uniquely identify client in REMOTE log.

Table 1. CandleNet Portal Global Parameters (continued)

CNP workspace HTTPwith browser view Proxy Server Internet

Page 57: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 57

Defining Global Parameters and Variables

1. Start > Programs > Candle OMEGAMON XE > Manage Candle Services from the machine where:� Browser mode – CandleNet Portal Server is installed.

� Desktop mode – CandleNet Portal desktop client is installed.

2. Right-click one of the following and select Reconfigure from the pop-up menu:� Browser mode – CandleNet Portal Browser

� Desktop mode – CandleNet Portal Desktop

3. In the Configure dialog that opens check:� Browser mode – Enable HTTP Proxy Server for Browser View

� Desktop mode – Enable HTTP Proxy Server.

4. In the PS Host field, enter the domain name system (DNS) identifier or the IP address of the proxy host to use for the HTTP protocol.

5. In the PS Port field, leave 80 as the default port number of the HTTP proxy host; -OR- if the proxy host uses another port number, enter it here.

6. If you want to bypass the proxy server for certain web sites being accessed from the CandleNet Portal browser view:

a. Double-click http.nonproxyhosts in the parameters list.

b. In the Value field, enter the server names, separated with a vertical line (|), and surround the list in double-quotes (“). For example, if you want the requests to *.candle.com and usps.gov servers to not go through the proxy, the list would read:

“*candle.com|usps.gov”

7. If your proxy server requires a different identity for the Candle integral browser before it will allow Internet access from the browser view:

a. Double-click http:agent in the parameters list.

b. Enter a one-word name for the browser.It can be any name so long as it is not rejected by the proxy server. You normally would not need to add an http name definition unless users get an error when they attempt to access the Internet through a CandleNet Portal browser view.

8. Check In Use and click OK.

Page 58: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Defining Global Parameters and Variables

58 Administering OMEGAMON Products: CandleNet Portal, V195

CandleNet Portal Server environment variablesThe CandleNet Portal Server runs two processes: KfwCMWServer and KfwServices. Because the KfwCMWServer process stops and restarts itself when the host CMS goes offline, KfwCMWServer has environment variables that affect how it detects CMS going offline and how it stops and restarts itself. The KfwServices environment variables can also be edited for certain configuration requirements. You can edit the variables through Manage Candle Services.

Edit KfwCMWServer variables

This is the CNPS helper process and may start and stop during life span of the primary KfwServices process.

1. On the machine where the CandleNet Portal Server is installed, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click CandleNet Portal Server, point to Advanced and select Edit ENV File from the list.

3. If the CandleNet Portal Server message displays, click OK to close it.

4. Select CMWENV: CandleNet Portal Server Situation Handler from the ENV file list and click OK.

5. When the CMWENV file opens in your text editor, enable (delete # at the beginning of the line) or edit any of the following variables:� #KFW_CMW_VERBOSE=Yes

This variable causes additional diagnostic information to be written to the console. You would not normally enable it unless directed by Candle Support. See also “Console mode” on page 90.

� #KFW_CMW_RECYCLE_DELAY=30

When the CMS connection is lost, the KfwCMWServer process waits the number of seconds specified here before exiting and restarting. This delay interval enables the KfwCMWServer process to conclude or shut down any active transactions before it exits. The new process instance then waits for CMS to become available before completing its initialization and making the CNP Server available for client connections again.

It is unlikely you will need to change this setting. Consider increasing the delay interval if you observe that one of the CandleNet Portal Server processes (KfwServices or KfwCMWServer) occasionally crashes when the

Page 59: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 59

Defining Global Parameters and Variables

CMS connection is lost, preventing successful reinitialization once CMS is started again. If you want to shorten the CandleNet Portal Server recycle time, consider reducing the delay interval. This reduction can be useful if the CMS frequently goes offline then is immediately brought back online again, and CandleNet Portal does not reinitialize quickly enough before the CMS goes offline again.

� #KFW_CMW_INIT_DELAY=30

When the CandleNet Portal Server restarts and detects the CMS, it waits the number of seconds specified here before starting its full initialization, allowing the CMS to fully stabilize and reduce its CPU load before handling the CandleNet Portal connection. If you observe that not all agents have come online when the server restarts, consider increasing this value. You may also want to increase the value if the CMS seems to be slow and is not ready to connect with the CandleNet Portal Server, which may cause the server to initialize incorrectly (viewed in the RAS1 log). Consider reducing the value if you want to shorten the CandleNet Portal Server recycle time, which can be useful if the CMS frequently goes offline then immediately brought back online again.

If a CMS that has been brought back online goes back offline while the CandleNet Portal Server is reinitializing, the CandleNet Portal Server may discontinue its automatic reinitialization attempts and will remain unavailable. The server writes descriptive error messages to the RAS1 logs and to the KfwServices command window if this window is enabled. Otherwise there is no visible server-side indication of this unavailable state. When the CMS is back online and stable, the CandleNet Portal Server service should be stopped and restarted using the Manage Candle Services application.

� KFW_CMW_TOPOLOGY_START_RETRIES=3

Specifies the number of retries for CandleNet Portal to compose the Navigator Physical view and the Situation editor when restarting after the CMS has been recycled.

� KFW_CMW_RUNNING_PING_INTERVAL=2

While connected to the CMS, the CandleNet Portal Server regularly tests the connection at the interval in minutes specified here. This value must not be set lower than 2 minutes. Usually, a value of 2 or 3 minutes is acceptable for a CMS running on a distributed operating platform; 5 minutes for a CMS running on a mainframe operating platform.

Page 60: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Defining Global Parameters and Variables

60 Administering OMEGAMON Products: CandleNet Portal, V195

For best response, keep the ping interval as frequent as possible, but not shorter than the time required for a CMS transaction to fail in instances when the CMS is unavailable.

Otherwise, an increasing number of failing ping transactions may accumulate, affecting the ability of CandleNet Portal to recover across a lost CMS connection.

Because the ping interval is at least 2 minutes, the CandleNet Portal Server may detect that the CMS has gone offline almost immediately, or up to 2 minutes later. It may be the case that the server detects that the CMS has gone offline even after a CMS is brought back online. In this case, the CandleNet Portal Server's KfwCMWServer process must still recycle so that it can reinitialize against the newly online CMS.

� KFW_CMW_WAITING_PING_INTERVAL=2

If the connection to the CMS is lost, the KfwCMWServer process waits for the CMS to become available again (up to a week). It performs a hub lookup at the interval specified here.

Normally, you will not need to change this value, and, if changed, it must not be set lower than 2 minutes. You may want to increase the interval if it takes an abnormally long time for the hub lookup to fail.

6. Save CMWENV and exit your text editor.The changes will take effect when you recycle the CandleNet Portal Server.

Edit KfwServices variables

This is the CNPS primary process and runs whenever CNPS is started.

1. On the machine where the CandleNet Portal Server is installed, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click CandleNet Portal Server, point to Advanced and select Edit ENV File from the list.

3. If the CandleNet Portal Server message displays, click OK to close it.

4. Select KMWENV: CandleNet Portal Server from the ENV file list and click OK.

5. When the KMWENV file opens in your text editor, enable (delete # at the beginning of the line), disable (type # at the beginning of the line) or edit any of the following variables:� KFW_MIGRATE_CMS=Y

Page 61: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 61

Defining Global Parameters and Variables

This is set to Yes to cause initial migration of managed objects and user IDs from the CMS the first time the CNP Server starts after installation.

� KFW_MIGRATE_VERBOSE=Y

This is set to Yes to record the migration activities to the migrate log file.

� KFW_SQL_VERBOSE=Y

This is set to Yes to record actions by the CNP Server in the log file.

� DSUSER1="DSN=myODBC;UID=myUsername;PWD=myPassword"

In CandleNet Portal, the Data Source area of the Create Query dialog lists the databases available for a query. The databases that appear were read from the database server on the CandleNet Portal Server machine. If you do not see the database for which you want to write a query in the list, you need to add it here. Edit the DSUSER1 entry for your data set name, username and password:

DSUSER1=”DSN=myODBC;UID=myUsername;PWD=myPassword”

And you can continue to add new lines for other data sources, from DSUSER2 up to DSUSER9.

Note that the database you reference must be in the ODBC Data Source registry on this machine. If it is not, consult your Windows system administrator.

� #KFW_REPORT_TERM_BREAK_POINT=86400

Adjust this setting to change the point where a historical request selects from short term or long term history data. The default is for short term history data to be collected “now” to 24 hours ago. Long term historical collection is set to be greater than 24 hours ago. Set to 0 to only select from long term history data.

6. Save KMWENV and exit your text editor.

7. In Manage Candle Services, right-click CandleNet Portal Server and select Recycle from the pop-up menu.

Disabling URLs for workspacesURLEnabled mode is CandleNet Portal running in browser mode with each workspace being referenced as a URL. You have the option to disable the use of URLs for opening workspaces.

Page 62: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Defining Global Parameters and Variables

62 Administering OMEGAMON Products: CandleNet Portal, V195

The applet on the integral web server includes a URLEnabled parameter, which is set to true by default. You can change the setting disable the workspace URL. Then the URL does not change when you switch workspaces and you cannot use Internet Explorer’s Favorites support of history features.

1. Start > Programs > Candle OMEGAMON XE > Manage Candle Services from the machine where the CandleNet Portal Server is installed.

2. Right-click CandleNet Portal – Browser, then select Reconfigure from the pop-up menu.

3. In the list of parameters that opens, double-click cnp.publish.url to open the Edit CandleNet Portal Browser Parm dialog.

4. Type false as the parameter value, check In Use, and click OK. Users will no longer be able to enter a URL to open a particular workspace. They will open workspaces through the Navigator pop-up menu or the View menu in CandleNet Portal.

Page 63: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 63

Adding Platforms to the Navigator

Adding Platforms to the Navigator

The Navigator Physical view in CandleNet Portal shows the operating platform below the enterprise level. The operating platform name is followed by the word “Systems”, as in “UNIX Systems” or “OS/390 Systems”.

Some operating platforms can be broken down further. For example, UNIX can be Linux. If your environment has such platforms and you would like each to have its own Navigator item, with all systems of that type contained there, you can edit the osnames file to add them.

How osnames maps the platform to the display nameThe osnames file is a text file that maps the operating platform to the item and the title that appears in the Navigator at the platform level. When a Candle monitoring agent comes online, it asks the system on which it is installed what operating platform it is running, then sends the answer (such as, “Win2K” for Windows 2000) to the CandleNet Portal Server. The server looks up the name in the osnames file and maps it to the platform item in the Navigator.

Here is a sample osnames file.

# Map vendor platform names to display names

# First section is vendor mapping.WinNT=Windows ServersWin2K=Windows ServersWinXP=Windows ServersWin03=Windows ServersSunOs=SolarisOSF1=Digital UNIXAS/400=OS/400

# Second section has optional mappings.AIX=UNIXDigital UNIX=UNIXSolaris=UNIXHP-UX=UNIX

# Third section maps to value including the word "Systems".Windows ServersNT=Windows SystemsUNIX=UNIX SystemsOS/2=OS/2 SystemsOS/400=OS/400 SystemsOS/390=OS/390 Systems

Page 64: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Adding Platforms to the Navigator

64 Administering OMEGAMON Products: CandleNet Portal, V195

Tandem=Tandem SystemsNetware=Netware Systems

To see how the names resolve to items in the Navigator, observe an agent on a Windows 2000 system. The agent asks the system what operating platform it is running and receives a reply of “Win2K”. This information is sent to the CandleNet Portal Server, which looks it up in osnames:

Win2K=Windows Servers

The server then checks the file for a Windows Servers entry:

Windows Servers=Windows Systems

Thus, the agent will be listed under the Navigator item entitled, “Windows Systems,” which will show all agents running on all varieties of Windows specified: Windows Servers, Windows 2000, Windows XP, and Windows Server 2003.

If you want a separate Navigator item for each variety of Windows, however, edit the file to remove the resolution to Windows Servers. For example,

# First section is vendor mapping.# WinNT=Windows Servers# Win2K=Windows Servers# WinXP=Windows Servers# Win03=Windows Servers

Rather than remove the entries for WinNT, Win2K, WinXP, and Win03, you can change them to comments by adding a # at the beginning of the line. That way, you can see what the original settings were in case you want to reset them.

Secondly, you can add entries for each version of Windows for which you want to have a separate Navigator item. For example,

# Third section maps to value including the word "Systems".WinNT=Windows NT SystemsWin2K=Windows 2000 SystemsWinXP=Windows XP Professional SystemsWin03=Windows Server 2003 Systems

Page 65: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Preparing your CandleNet Portal Environment 65

Adding Platforms to the Navigator

Editing the osnames file

1. Start Windows Explorer.

2. On the drive where you installed the CandleNet Portal Server, open the “cnps” directory:

candle

cnps

3. Double-click “osnames” and, in the Open With dialog, select the Notepad program.

4. Add the # symbol to the beginning of any line in the First or Second section whose operating platform you want to be given its own Navigator item.

5. Add a new line in the Third section for each operating platform to have its own Navigator item:

platform=Navigator title

where platform is the operating system and Navigator title is the display name, such as AIX=AIX Systems.

The platform name must be spelled exactly as it is shown elsewhere in the osnames file. You cannot add new platform names, only Navigator display names. The platform name comes from the Host Info attribute of the Managed Systems attribute group.

Page 66: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Adding Platforms to the Navigator

66 Administering OMEGAMON Products: CandleNet Portal, V195

Page 67: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 67

User Administrationand Customization

IntroductionThis chapter explains how to add and remove user IDs.

Chapter contentsUser Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Adding, Editing and Removing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Assigning User Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75User ID for Take Action Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3

Page 68: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration

68 Administering OMEGAMON Products: CandleNet Portal, V195

User Administration

When creating user IDs, you select which features they can use and customize, which monitoring products they can access, and which Navigator views they can open.

Workspace administration modeAny changes you make to workspaces, links, and terminal host session scripts in CandleNet Portal are available only to your user ID. The exception is while Workspace Administration Mode is enabled.

Workspace administration mode enables you to customize and to add workspaces, links, and terminal emulator scripts that are shared with—and thus available to—all users connected to the same CandleNet Portal Server.

To use this function, your user ID must have Administration Mode Eligible permission for User Administration.

To enable or to disable workspace administration mode:

1. Click Administer Users.

2. Select your user ID in the Users list.

3. In the Authorities tree, select Workspace Administration.

4. Check or uncheck Workspace Administration Mode to enable or disable it.See “Permissions tab” on page 75.

Notes:We recommend you check Do not allow modifications in the Workspace Properties whenever you create or edit a workspace in administration mode. Otherwise, if a user edits that workspace, you no longer control the workspace and cannot override their changes with any you make in administration mode.Workspaces, links, and terminal scripts created or edited while you were in workspace administration mode cannot be deleted unless the user ID is in that mode.

SYSADMIN logon IDCandleNet Portal requires your logon ID whenever you start a work session. Every ID must first have been registered on the CandleNet Portal Server. You can log onto CandleNet Portal with SYSADMIN and register other user IDs through the Administer Users dialog. The initial user ID, SYSADMIN, has full

Page 69: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 69

User Administration

access and complete administrator authority. The system administrator registers additional users and sets their access privileges and authority. See “Logon ID” on page 40.

User IDEach user ID is stored at the CandleNet Portal Server and contains:

� the user name

� job description

� authority to view or modify CandleNet Portal functions

� assigned Navigator views

� access to specific Candle applications

Default user

To use this function, your user ID must have Modify permission for User Administration.

The first user ID in the list is <Default User> and is used as the template ID for users created with Create New User. Edit this user ID if you want to change any of the default settings. The initial defaults enable all the functions listed under CNP Authorities, except User Administration Modify. Any changes you make to <Default User> ID apply to users created from this point on; they will not affect any existing user ID settings.

Granting access to a userYou set the authority privileges for each user when you create their user IDs. Giving users access to operational areas and authorable functions takes planning. Consider the job responsibilities of each user and the company security requirements when specifying authority privileges. See “Assigning User Permissions” on page 75.

Important: Anyone with permission to create custom queries obtains access to all of the ODBC data source names (DSNs) created at the CandleNet Portal Server. Add database user IDs (to be used in the DSN) to your database software, making sure to restrict user access to only those tables, columns, and so on, allowed by your organization’s security policies.

Page 70: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration

70 Administering OMEGAMON Products: CandleNet Portal, V195

Validating user accessThe CandleNet Portal Server validates user IDs whenever users log on to CandleNet Portal. If a user’s job description changes and the user requires different access to CandleNet Portal, you need to review and perhaps change the user’s permissions.

The user ID for logging on to CandleNet Portal may include a password. You do not establish passwords in CandleNet Portal. Instead, you need to define a matching user ID with password to the network domain user accounts or to the operating system where the CMS resides:

� User Accounts on Windows

� Password file on UNIX

� RACF or ACF/2 host security system on OS/390 or z/OS

As well, the CMS must be configured to Validate User. When users log on to CandleNet Portal, the CMS asks the domain or the operating system to validate the user ID and password.

If the CMS has been installed on a Windows machine, you can check if it has been configured to Validate User: Start > Programs > Candle OMEGAMON XE > Manage Candle Services. Right-click Candle Management Server, and select Reconfigure from the pop-up menu. Check Security: Validate User.

Page 71: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 71

Adding, Editing and Removing Users

Adding, Editing and Removing Users

The user administration feature enables you to:

� Add a user. See “Adding a user” on page 71.

� Edit a user. See “Editing a user” on page 72.

� Remove a user. See “Removing a user” on page 73.

� Assign user permissions. See “Assigning User Permissions” on page 75.

� Assign Navigator views. See “Assigning User Permissions” on page 75.

Adding a user You can add a new user with the default user profile or with the same profile as an existing user.

To use this feature, your user ID must have Modify permission for User Administration.

1. Click Administer Users.

2. Do one of the following:– To create a new user with the default user profile, click Create New

User.

– To create a new user from an existing one, select the profile you want for the new user from the Users list, and click Create Another User.

3. In the Create New User dialog, enter:� User ID, which is the logon name. The name can consist of up to 10

letters and numbers. The casing of the user ID depends on the operating system used by the CandleNet Portal Server. OS/390 and Windows are not case-sensitive. For these operating platforms, user IDs are converted to uppercase to prevent the duplication of IDs. Linux and UNIX are case-sensitive, so the casing is kept as it was entered.

� User Name, which is the user's name or job classification. This field can include spaces and punctuation. The user name appears in the Users area.

� Description, like the user name, appears in the Users area. The description can include spaces and punctuation.

Page 72: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Adding, Editing and Removing Users

72 Administering OMEGAMON Products: CandleNet Portal, V195

4. To change the Permissions, select a function from the Authorities tree, then check or uncheck each box as appropriate. Repeat for all functions whose permissions you want to change.For details about each permission, click Help while the dialog is open.

5. To change the available Candle applications, click the Applications tab, then select <All Applications> or the individual applications the user should see and move them to the Allowed Applications list. Tip: After selecting the first application, use Ctrl+click to select other applications or Shift+click to select all applications between the first selection and this one.

6. To assign the Navigator views, click the Navigator Views tab, then add or remove Navigator views from the Assigned Views list. Place the view you want to be the default at the top of the list. For each Navigator view, change the Assigned Root as needed.

7. When you are finished creating the user profile, save your changes with Apply if you want to keep the Administer Users dialog open; -OR- OK if you want to close it.

Note: If you want the User ID to include a password, you must define the same user ID with password, to the operating system or domain on which the CMS resides. As well, the CMS must be configured to validate the user.

Editing a userOnce a user has been added to the Users list in the Administer Users dialog, you can edit the user profile at any time.

To use this function, your user ID must have Modify permission for User Administration.

1. Click Administer Users.

2. Click the user ID whose profile you want to edit. You can click inside the Name field or the Description field to edit either of them.

3. Right-click the user profile you want to edit and select Modify User from the pop-up menu. You cannot change the one-word User ID. You must instead delete the user ID and create a new one.

Page 73: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 73

Adding, Editing and Removing Users

4. In the Permissions tab, select a function from the CNP Authorities tree. For greater detail on the permissions and applications you can specify, see “Assigning User Permissions” on page 75.

5. Enable or disable the checkboxes as needed. Repeat for any other functions whose permissions you want to change.

6. To change the available Candle applications, click the Applications tab, then select <All Applications> or select the individual applications the user should see and move them to the Allowed Applications list. Tip: After selecting the first application, you can use Ctrl+click to select other applications. You can also use Shift+click to select all applications between the first selection and this one. Note that all OMEGAMON Platform applications display, whether they are part of your managed network or not.

7. To modify the Navigator views, click the Navigator Views tab, then add or remove Navigator views from the Assigned Views list. Place the view you want to be the default at the top of the list. For each Navigator view, change the Assigned Root as needed.

8. When you are finished editing the user profile, save your changes with Apply if you want to keep the Administer Users dialog open, or OK if you want to close it.

Note: You can change your own user permissions, except View and Modify for User Administration.

Removing a userTo remove a user from the Users list:

To use this function, your user ID must have Modify permission for User Administration.

1. Click Administer Users.

2. In the Administer Users dialog, select (highlight) the user ID you want to delete.Tip: You can select additional user IDs with Ctrl+click, or Shift+click to select all user IDs between the first selection and this one.

3. Click Remove Selected User(s) to remove the User ID from the list. A message displays, asking you to confirm the deletion. The user is permanently removed from the user ID list. If the user is currently signed on,

Page 74: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Adding, Editing and Removing Users

74 Administering OMEGAMON Products: CandleNet Portal, V195

this does not affect their work session. However, they will not be able to log on again.

4. When you are finished, save your changes with Apply if you want to keep the dialog open, or OK if you want to close it.

Note: You cannot remove your own user ID (the one you logged on with) or the <Default User> ID.

Page 75: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 75

Assigning User Permissions

Assigning User Permissions

The Administer Users dialog contains tabs for setting authorities to specific features, specifying access to applications, and specifying access to Navigator views. These tabs are:

� Permissions tab

� Applications tab

� Navigator Views tab

Permissions tabIn the Authorities area of the Permissions tab, you can select the features in CandleNet Portal to which you would like to provide access. In the Permissions area, you set the specific permissions granted to each user.

Action

View allows the user to see and execute a Take Action command from the available list of commands in the Take Action view and in the pop-up menu for the Navigator item.

Modify allows the user to enter Take Action commands, and to save them.

Note that when issuing a Take Action command, you must be authorized on the relevant system for the requested command. For example, you must have a valid TSO ID to issue a TSO command. The user ID must also be defined as a valid logon ID for CandleNet Portal.

Custom Navigator Views (OMEGAMON DE only)

Modify allows the user to create new Navigator views, and to edit and delete them. With Modify unchecked, the user will not see Edit Navigator View in the Navigator toolbar.

Event

Close allows the user to manually set a true situation to false (through the pop-up menu for the situation Navigator item).

View allows the user to see event indicators in the Navigator.

Page 76: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Assigning User Permissions

76 Administering OMEGAMON Products: CandleNet Portal, V195

Acknowledge allows the user to acknowledge an event in the Event Acknowledgement dialog, accessed through the pop-up menu for the situation Navigator item (event workspace).

Feature – OMEGAMON DE

Enable is dimmed because the setting depends on your license key, which is entered during installation or, later, through Manage Candle Services. If it is checked, your site is licensed for the enhanced feature set available with OMEGAMON DE. If it is not checked, your site is licensed only for OMEGAMON XE.

History

Configure allows the user to open the History Collection Configuration dialog, configure history files and data rolloff, and start and stop data collection for different attribute groups.

Managed System List

View allows the user to access the Managed System List editor for viewing the content of each managed system list.

Modify allows the user to create, edit and delete managed system lists in the editor.

Policy (OMEGAMON DE)

View allows the user to open the Workflow Editor dialog.

Modify allows the user to create and edit policies in the Workflow Editor dialog.

Start/Stop allows the user to start and stop policies.

Query

View allows the user to access the Query editor through the Properties editor and to select a query for the selected table or chart.

Modify allows the user to create, edit and delete queries in the Query editor.

Note that anyone with permission to create custom queries obtains access to all of the ODBC data source names (DSNs) created at the CandleNet Portal Server. Add database user IDs (to be used in the DSN) to your

Page 77: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 77

Assigning User Permissions

database software, making sure to restrict user access to only those tables, columns, and so on, allowed by your organization’s security policies.

Situation

View allows the user to see situations in the Situation editor and to see acknowledgements in the Event Acknowledgement dialog.

Modify allows the user to create new situations, to edit and to delete situations in the Situation editor.

Start/Stop allows the user to start or stop a situation through the pop-up menu for the situation Navigator item (event workspace).

User Administration

Modify allows the user to edit user IDs and to remove them. If you are viewing your own user ID, you will see that View and Modify are disabled; you cannot change your User Administration permissions.

View allows the user to open the Administer Users dialog and see their user ID permissions, but not those for other users.

Author Mode Eligible allows the user to enable or disable their Author Mode permission under Authorities – Workspace Administration, but not for any one else’s user ID.

Administration Mode Eligible allows the user to enable or disable their Administration Mode permission under Authorities – Workspace Administration, but not for any one else’s user ID.

Workspace Administration

Workspace Administration Mode, when enabled, takes the changes you make to workspaces, their links, and terminal emulator scripts, and shares them with all users logged onto the same CandleNet Portal Server. When this mode is disabled, workspace changes you make are not shared with other users.

If you intend to delete any workspaces, links, or terminal scripts that were created in this mode, you must enable workspace administration mode beforehand.

If you do set the workspace properties to Do not allow modifications, any user with Author Mode permission will be able to edit the workspace. When the user saves the workspace, it becomes their private copy; any

Page 78: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Assigning User Permissions

78 Administering OMEGAMON Products: CandleNet Portal, V195

changes you make to that workspace in future will continue to be public, but not for that user.

Workspace Author Mode allows the user to create and edit CandleNet Portal workspaces, links and terminal emulator scripts. If you disable Workspace Author Mode, the user is prevented from making any of these changes, but can continue monitoring and responding to alerts; the tools can still be seen, but they are dimmed. Thus, regardless of what features are enabled for the user, they will not be available when Workspace Author Mode is disabled if there is no pop-up menu access.

WebSphere MQ Configuration Authorities

OMEGAMON XE for WebSphere MQ Configuration installations will see this folder.

View allows the user to open the Navigator Configuration view.

Modify allows the user to define and manage the WebSphere MQ network through the Configuration view.

Applications tabIn the Applications tab, you can select the applications in CandleNet Portal to which you would like to provide access for this user ID.

To change a user’s application assignments, your ID must have Modify authority for User Administration.

Allowed Applications

Shows the applications the user will be able to access from CandleNet Portal. Initially, this is set to <All Applications>.

If you want to limit the set of applications a user has access to, select the <All Applications> entry and click the right arrow to move it back to the Available Applications list. Then select the appropriate entries and click the left arrow to move them to Allowed Applications. The user will see only those Navigator items that are included in the allowed applications; all others will not appear in the Navigator view or be selectable through dialogs such as the Situation editor.

Page 79: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 79

Assigning User Permissions

Available Applications

Shows the applications available for assignment to the selected user. If <All Applications> is on the Allowed Applications list, then no other entries can be added. You need to move it back to Available Applications before you can select a subset of applications to assign.

Select the applications you want to add, or select <All Applications>, and click the left arrow. After selecting the first application, you can use Ctrl+click to select other applications or Shift+click to select all applications between the first selection and this one.

Note that all OMEGAMON platform applications display, regardless of whether or not they are part of your managed network.

Navigator Views tabTo change a user’s Navigator view assignments, your ID must have Modify

authority for User Administration.

Assigned Views

Shows the Navigator views the user will be able to see and access. The first Navigator view in this list is the default for the user; it will come up automatically whenever the user logs on. You can select any views to which you do not want the user to have access, and click the right arrow to move them to the Available Views list. Select the appropriate entries and click the left arrow to move them to Assigned Views. You can move a Navigator view to the top of the list to make it the default by clicking the up arrow.

Available Views

Shows the Navigator views not assigned to the user and available for assignment. Select the Navigator views you want to add and move them to the Assigned Views list by using the left arrow. After selecting the first view, you can use Ctrl+click to select other views or Shift+click to select all views between the first selection and this one.

Assigned Root

Shows the Navigator view chosen in Assigned Views, with the user's assigned Navigator root highlighted. The root is the top-most level of this Navigator view the user can access. The user can access this item and all items below it, but no items parallel to or above it in the Navigator.

Page 80: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Assigning User Permissions

80 Administering OMEGAMON Products: CandleNet Portal, V195

For example, you can assign UNIX Systems as the assigned root. The user will see the UNIX Systems workspaces and those below, but will not be able to see the Enterprise workspaces or anything under Windows Systems.

Page 81: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User Administration and Customization 81

User ID for Take Action Commands

User ID for Take Action Commands

OverviewWhen CandleNet Portal sends a Take Action command to a managed system the user ID may or may not be checked for authority to perform the action.

In the simplest case, the command is sent to the managed system and executed using the user ID under which the agent is running.

The CandleNet Portal user ID is sent along with the action command:

� on-demand – user ID currently logged on

� situation action – user ID of the last person to update the situation

� workflow action – user ID of the last person to update the policy

but is ignored by the managed system unless told otherwise by a command prefix.

Command prefixWhen a command prefix is present in the Take Action, the agent passes the command to the application handler rather than executing the command. The syntax of the prefix and take action command is productcode:CNPuserID:command and the agent routes it to the application for execution. The application is free to execute the command with whatever user ID is appropriate. In the case of OMEGAMON XE for WebSphere MQ, the CNP user ID is used.

If the special prefix is missing, the agent executes the command with the user ID under which the agent is running.

Most OMEGAMONs do not employ a command prefix. OMEGAMON XE for WebSphere MQ does and, in fact, prepends on-demand Take Action commands with a hidden MQ:CNPuserID: prefix, although you cannot see it.

Page 82: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

User ID for Take Action Commands

82 Administering OMEGAMON Products: CandleNet Portal, V195

Page 83: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 83

TroubleshootingProcedures

IntroductionThis chapter provides descriptions of and user responses to error messages and conditions that may occur in CandleNet Portal. Included are instructions for using traces, which generate error logs that can be used by Candle Support personnel to help determine the cause of errors you are encountering with CandleNet Portal.

See “Candle Customer Service and Satisfaction” on page 15 for information on contacting Candle Customer Support.

Chapter contentsError Messages and Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84CandleNet Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Browser Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Using the Candle Technologies Service Console . . . . . . . . . . . . . . . . . . . . 93Setting a Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Regional Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

4

Page 84: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Error Messages and Conditions

84 Administering OMEGAMON Products: CandleNet Portal, V195

Error Messages and Conditions

OverviewLogon prompts and progress messages appear in the Logon dialog status bar. You may see error messages when logging on and at other times. This section documents some of these error messages and conditions.

Failed connection to CandleNet Portal Server

1. On the machine where the CandleNet Portal Server is installed, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Optional: Right-click the CandleNet Portal Server entry and select Change Startup from the pop-up menu. In the dialog that opens, select System Account, check Allow Service to Interact with Desktop and click OK. This will open a command prompt window when the CNP Server is started and display the internal CNP Server commands.

3. Check that the CandleNet Portal Server service is started:� If it is started, Recycle the CandleNet Portal Server.

� If it is stopped, Start the CandleNet Portal Server.

4. If you are still unable to connect, review the following. If it does not apply to your situation, contact Candle Customer Support. If you are running in browser mode and going across networks to reach the CandleNet Portal Server, it is possible the host name cannot be resolved by the network system. If this is the case, do the following on the system where the CandleNet Portal Server is installed:

A. In Manage Candle Services, right-click the CandleNet Portal – Browser service and select Reconfigure from the pop-up menu.

B. In the Launch URL field, change hostname in http://hostname:1920///cnp/client to the IP address of the CandleNet Portal Server so it reads, for example, http://10.21.2.166:1920///cnp/client.

C. Click OK.D. Start CandleNet Portal browser mode using the IP address instead of

the host name.

Page 85: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 85

Error Messages and Conditions

E. If you are still unable to connect, contact Candle Customer Support.

CandleNet Portal client cannot find CandleNet Portal Server

1. Select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Check that the CandleNet Portal Server service is running and, if not, restart it.

3. If the server shows as started, review the Windows Event Log (Event Viewer) for any errors reported by the CandleNet Portal Server application.When the server starts, an “event ID 1: KFW0001 - CandleNet Portal Server (CNPS) startup complete” information entry is logged.

If you see an error entry, double-click the item to see the description. If you do not have enough information to resolve the problem, contact Candle Customer Support.

User authorization has failed -or- Unable to process logon requestIf you get either “User authorization has failed” or “Unable to process logon request” the CandleNet Portal Server did not validate the user credentials as entered. Retype the ID and, if required, the password, with the correct letter casing.

If either message appears again, do the following:

1. Check that the CMS is started. If the CMS is installed on Windows, you can check it in Manage Candle Services.

2. If the user profile has been defined in CandleNet Portal, check if the host level security was turned on for the CMS (see “Configuring the CMS to validate users” on page 52) and, if so, that the user ID has been authorized to the host environment. CandleNet Portal uses the CNPS database to locally validate users. If you are connecting to a CMS that employs a host security system, the user ID and password are also validated at the CMS.

3. Log on to CandleNet Portal with an administrator user ID and check the user profile to see if it has been defined.

4. Try logging on to CandleNet Portal with the user ID in question.

Page 86: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Error Messages and Conditions

86 Administering OMEGAMON Products: CandleNet Portal, V195

5. If you cannot log on to CandleNet Portal and the CMS is running properly, the problem might be with the CandleNet Portal Server. Try recycling the server. If you are still unable to log on, contact Candle Customer Support. These messages also come up after a retry period of several minutes (the default is 10 minutes). The status bar shows Validating User Credentials continuously. This may be a symptom that the CMS is stopped. To change the retry period, see “User Administration” on page 68.

Inability to log onIf, instead of CandleNet Portal starting, you get an error message in the status bar of the Logon dialog, recycling the CandleNet Portal Server may fix the problem.

CandleNet Portal Server status alertsCandleNet Portal monitors the connections between server and client and server and host data sources continuously. When CandleNet Portal detects a connection error, in most cases it automatically repairs the error for you and your client session can resume unaffected. To ensure the smooth recovery of the CandleNet Portal client when a connection error occurs, we recommend the actions described below.

CNP Server is still being initialized and is not ready for communications

If you attempt to start CandleNet Portal just after the CNP Server has been started, this message will appear if initialization is still in progress. The CNP Server is not ready for requests from the client until its process, kfwservices.exe, is fully started.

Keep the Logon dialog open and click OK after waiting a moment or two.

CNP Server has lost contact with the Candle Management Server and is attempting to reconnect

This message appears when the CandleNet Portal Server has lost its connection to the CMS. Usually this is because the CMS has stopped or is being recycled.

See also KFW_CMW_RECYCLE_DELAY in “CandleNet Portal Server environment variables” on page 58.

Page 87: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 87

Error Messages and Conditions

Server Unavailable

In general, when a “Server Unavailable” message displays, you should suspend further interactions until you see a “Server Available” message unless you have decided to close your CandleNet Portal session. When the CandleNet Portal Server is available again, your client session will be automatically reconnected and you can resume normal interactions. If the server is available and the client has not reconnected after three to five minutes, exit the browser, restart the browser, and restart a CandleNet Portal client session.

Reconnect Authorization FailedThis message displays after the CMS has gone down and reconnection is attempted. The CandleNet Portal client attempts to log on once again to the CandleNet Portal Server session. After a successful re-logon, the CandleNet Portal client compares the CandleNet Portal user authorities that were in effect when the original logon occurred with the current CandleNet Portal user authorities. If any single permission has changed, you must restart your client session to make sure all components are synchronized with your user permissions. Changes to user permissions include Navigator view assignment differences since the last logon.

If you want to apply new permissions for other users immediately, make all of your desired changes, then recycle the CMS. When the CMS recycle is complete, each user will be reconnected and their user ID validated. If there were changes to their profiles, users would have to restart the CandleNet Portal client session. If no changes were made to their profiles, they would not need to restart the CandleNet Portal client session.

CandleNet Portal Server is not reconnectingIf the CandleNet Portal Server is not reconnecting for some reason, recycle the CMS, then restart the CandleNet Portal Server.

Enable OMEGAMON DE OMEGAMON DE is enabled during installation. If you did not select (enable) OMEGAMON DE at that time, Workflow Editor is disabled and the following tools do not show: Event Console, Graphic View, Edit Navigator View (Navigator view toolbar).

Page 88: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Error Messages and Conditions

88 Administering OMEGAMON Products: CandleNet Portal, V195

1. On the machine where the CandleNet Portal Server is installed, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click the CandleNet Portal Server service, point to Licensing and select CandleNet Portal Server from the pop-up menu.

3. In the CandleNet Portal Service License dialog, enter the new license key if one was issued.

4. Check Enable OMEGAMON® DE (separately licensed).

5. Click OK.When you click OK, the server stops and a message in CandleNet Portal says the server is unavailable. If you do not close the client work session, after the server has been started again (next step), another message says your CandleNet Portal permissions have changed and prompts you to restart.

6. Restart the CandleNet Portal Server and, after startup is complete, restart the the CandleNet Portal client.

Page 89: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 89

CandleNet Portal Server

CandleNet Portal Server

Windows Event ViewerWhen investigating problems with CandleNet Portal, use the Windows Event Viewer to check that the CandleNet Portal Server started properly and to look for errors. Here are possible log entries for the CandleNet Portal Server.

Note: For the database server error and warning messages, the data source is CNPS if the CandleNet Portal Server uses Microsoft SQL Server, or CNPS2 if it uses DB2 UDB.

CandleNet Portal Server application messages

Information

Error

Warning

1 CandleNet Portal Server (CNPS) startup complete

The server was started or restarted successfully either manually or automatically.

2 CandleNet Portal Server (CNPS) shutdown complete

The server was stopped successfully.

3 Unable to start CNPS because of problem with database server

Be sure the database server is running and that the data source is configured.

4 CNPS lost connection with database server

Be sure the database server is running and that CNPS data source is configured.

5 CNPS regained connection with database server

For some reason, the CandleNet Portal Server lost connection with the database, but has re-established its connection.

Page 90: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Server

90 Administering OMEGAMON Products: CandleNet Portal, V195

Console modeThe CandleNet Portal Server has an option to display the tasks at the command prompt. This is used primarily with Customer Support for gathering diagnostic information.

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click Candle Management Server, then select Change Startup from the pop-up menu.

3. Check Allow Service to Interact with Desktop.

CNPS user ID The following Windows user IDs are required by DB2 UDB:

� “db2admin”, added when you install DB2 UDB and required by the Candle installer when you configure the CNPS data source.

� “CNPS”, added during installation for creating the CNPS data source.

If the Windows Local Security Settings are enabled for long or complex passwords, you must use a password of the required syntax for these IDs.

Figure 6. Windows Local Security Settings.

Page 91: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 91

CandleNet Portal Server

Additionally, if your environment requires passwords to be changed periodically, do the following to change CandleNet Portal Server database user account password.

1. On the machine where the CandleNet Portal Server is installed, be sure you are logged on to Windows with an ID having administrator authority.

2. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

3. Right-click the CandleNet Portal Server and select Advanced > Utilities > Build CNPS Database from the pop-up menu.

4. Click DB2 to open the CNPS Data Source Config Parameters dialog.

5. Enter the Admin Password. (If you accepted the defaults during installation of DB2 UDB, the password is “candle”.)

6. Enter the new Database Password for the CNPS Database User ID.

Figure 7. CNPS Data Source Config Parameters dialog.

Page 92: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Browser Mode

92 Administering OMEGAMON Products: CandleNet Portal, V195

Browser Mode

Clearing the JAR cacheIf you encounter problems, Customer Support may instruct you to uninstall and to clear the JAR cache. See “Candle Customer Service and Satisfaction” on page 15.

1. If CandleNet Portal is running, exit by closing the browser window.

2. Start the Java Plug-in. Your Windows desktop should have a shortcut to the Java Plug-in (version 1.3.1_04). You may also find it in Start > Settings > Control Panel. To start it, double-click the Java Plug-in icon.

3. In the Java(TM) Plug-in Control Panel dialog, select the Cache tab and click Clear JAR Cache.

4. When a message says the JAR cache has been cleared, click OK. If you want to start CandleNet Portal browser mode again, restart Internet Explorer and enter the URL for CandleNet Portal. The Java Extension Installation progress bar shows as each Java archive file is downloaded. Upon completion, the logon dialog opens for you to enter your user ID.

Help not displaying

Popup blocker

If the browser toolbar has a popup blocker running, the help will not open whether you select Contents and Index from the CandleNet Portal Help menu or click Help in a dialog. Turn off the popup blocker.

Shortcut keys

Some CandleNet Portal shortcut keys are also used by Internet Explorer. If you press F1 to open the CandleNet Portal help, you will get the help for Internet Explorer instead. Select Contents and Index from the CandleNet Portal Help menu.

Page 93: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 93

Using the Candle Technologies Service Console

Using the Candle Technologies Service Console

OverviewThe Service Console enables you to read logs and turn on traces for remote product diagnostics and configuration.

A CT Service Console is uniquely identified by its service point name. All CT Service Consoles for a host are linked and presented on the Candle Service Index for that host. The Candle Service Index is obtained by pointing a browser to the CT/HTTP port 1920 on a specific host (for example, http:/goby:1920).

You can perform operations on a specific CT process by selecting the Candle Technologies Service Console associated with the desired service point name.

Starting the Service Console

1. Start Internet Explorer version 5 or higher.

2. In the Address field, type the URL for the CandleNet Portal browser client installed on your web server.The URL for the Candle web server is:

http://hostname:1920

where hostname is the host name where the CandleNet Portal Server is installed. If the Candle Technologies Service Console page does not display, it may have been disabled (see page 94).

3. Click the Candle Technologies Service Console link associated with the desired process (service point name).

4. When the Logon dialog opens, click OK.In secure environments, a valid user ID and password are required to proceed. Upon successful login, the CT Service Console will open with three distinct areas:

Header

Command Results

Command Field

Page 94: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Using the Candle Technologies Service Console

94 Administering OMEGAMON Products: CandleNet Portal, V195

You can now issue CT Service Console commands in the command input area. For a list available commands, type a question mark (?) and click Submit.

Disabling the Candle web serverYour OMEGAMON Platform configuration may employ an external web server for CandleNet Portal browser mode rather than the Candle integral web server. Or your configuration may specify CandleNet Portal only in desktop mode. In either case, the integral web server is installed automatically with the CandleNet Portal Server component, and there is nothing special you need to do to ignore it.

However, you may want to prevent users from accessing the Candle Technologies (CT) Service Console that is available through the integral web server (http://machinename:1920).

To block access to the CT Service Console:

1. Start the Registry Editor: Start > Run > regedit

2. Open the CandleNet Portal Server Environment folder:HKEY_LOCAL_MACHINE

SOFTWARE

Candle

KFW

CNPS

KFWSRV

Environment

3. Find KDC_FAMILIES in the right frame, then add a space and type the following at the end of the line: http_server:n

Example: IP PORT:1918 SNA use:n IP.PIPE use:n http_server:n

Desktop mode – add URL to external web server

If you disable the integral web server, you must install a third party web server on the CNP Server machine to access the images and style sheets for the graphic view. As well, you need to edit the application parameters at every desktop client.

Do the following on each machine where you installed the CandleNet Portal desktop client:

Page 95: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 95

Using the Candle Technologies Service Console

1. From your Windows desktop, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click CandleNet Portal – Desktop and select Reconfigure from the pop-up menu.

3. In the list of parameters that opens, double-click cnp.http.url.DataBus to open the Edit CandleNet Portal Parm dialog.

4. Enter the URL to the external web server and to the cnps.ior file in the candle\cnb directory. For example, if the web server name is myweb.hostname.com and its document root was configured to be \candle\cnb, the value to enter would be:

http://myweb.hostname.com/cnps.ior

5. Check In Use, and click OK.

Page 96: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Setting a Trace

96 Administering OMEGAMON Products: CandleNet Portal, V195

Setting a Trace

OverviewWhen you encounter an error with CandleNet Portal that requires contacting Candle Customer Support, you may be asked to submit a copy of the error log. The error log is part of the Trace diagnostic tool in CandleNet Portal. It is set to log errors, and you can set other parameters for collecting specific details.

Set trace options on the CandleNet Portal clientTo set the trace options:

1. In CandleNet Portal, select Trace Options from the File menu.

2. Select a trace class from the list or as instructed by Candle Customer support (such as UNIT:Workspace ALL):ALL provides data for all classes. This setting should be used only temporarily, as it generates large amounts of data.

ERROR logs internal error conditions. This setting provides the minimum level of tracing, with little resource overhead, and ensures that program failures will be caught and detailed.

NONE turns off the error log so no data is collected.

3. Click OK to close the dialog and turn on logging.

Desktop mode log files

An error log file is created automatically the first time you start CandleNet Portal, and is named candle\cnp\logs\kcjras1.log. This log file contains all of the ras1 tracing for the CandleNet Portal client. Whenever you start a new work session, the log file is purged and written anew for the current work session. If you want to preserve the log file from the last work session, you must rename it or copy it to another directory before starting CandleNet Portal again.

Another log file, kcj.log, contains any errors that may have been generated by the Sun Java libraries that we use in the CandleNet Portal client.

Page 97: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Troubleshooting Procedures 97

Setting a Trace

Browser mode log files

These log files are generated for browser mode on Windows 2000 or Windows XP:

c:\Documents and Settings\current user\plugin131_04.trace

where current user specifies your user directory.

Set trace options on the CandleNet Portal ServerThe trace options for the CandleNet Portal Server are set through Manage Candle Services.

1. On the machine where the CandleNet Portal Server is installed, select Start > Programs > Candle OMEGAMON XE > Manage Candle Services.

2. Right-click the CandleNet Portal Server service and, in the pop-up menu, point to Advanced and select Edit Trace Parms.

3. Select one of the files as instructed by the Candle Support representative:

Depending on which trace file you selected, the trace output is written to kfwras1.log or cmwras1.log on:

candle

cnps

logs

The log file continues to grow until you either turn off the trace or recycle the CandleNet Portal Server (for kfwras1.log) or the CMS (for cmwras1.log).

Page 98: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Regional Settings

98 Administering OMEGAMON Products: CandleNet Portal, V195

Regional Settings

In Windows, the Regional and Language Options for English specify the comma (,) as the Digit grouping symbol. Thus, 9000 may also be written as 9,000. For some languages, Windows specifies no Digit grouping symbol. So 9,000 in the CandleNet Portal editor (Query, Situation, Properties - Filters, and Properties - Thresholds) would be seen as 9 because the Decimal Format parser—a Java component—stops formatting the value where it finds the invalid , character.

If your language specifies no Digit grouping symbol, set it in the Windows Control Panel > Regional and Language Options (or Regional Settings). This must be done on every machine where CandleNet Portal will be run.

Page 99: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 99

CandleNet Portal Migration

IntroductionThis chapter describes the Candle utilities and procedures for:

� Replicating your CandleNet Portal setup and customizations, which is the same procedure as moving from a test environment to a production environment and for backing up.

� Migrating objects that were created in the CMW after CandleNet Portal installation. You can import the databases associated with these objects into CandleNet Portal.

If you have a new OMEGAMON XE installation and would like to augment its capabilities with those from the CMW, see “Functional Comparison” on page 116.

Chapter contentsReplicating the CandleNet Portal Server Environment . . . . . . . . . . . . . . 100Migrating Objects from CMW to CandleNet Portal . . . . . . . . . . . . . . . . . 106Migrating Additional Users from CMW to CandleNet Portal . . . . . . . . . . 108Migrating New CMW Managed Objects to CandleNet Portal. . . . . . . . . . 110

5

Page 100: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Replicating the CandleNet Portal Server Environment

100 Administering OMEGAMON Products: CandleNet Portal, V195

Replicating the CandleNet Portal Server Environment

OverviewWith the exception of situations, policies and managed system lists, CandleNet Portal customizations are stored at the CNP Server in two databases:

� Presentation database for custom workspaces.

� CNPS database for user IDs, and for custom queries and Navigator views.

This section describes the procedure for migrating from a test to a production environment or to a second CNP Server connected to the same CMS. Also use this procedure for backing up and restoring the CNP Server, which we recommend before applying a fix pack or upgrading to a new version.

Important: All workspaces previously created in the production environment will be replaced with those created in the test environment. Any existing user changes in the production environment will also be replaced.

PrerequisitesPrior to copying the presentation database:

� The CandleNet Portal Server on the test machine must be connected to the same hub CMS as the CandleNet Portal Server on the production machine.

� The CandleNet Portal Server on both the test machine and the production machine must be version 195 and, ideally, both have been installed from the same CD image.

� The CandleNet Portal Server on both the test machine and the production machine must have been installed the same way:

– the selected applications are the same

– the same database program is used for the CNPS database. IBM DB2 UDB is recommended.

Page 101: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 101

Replicating the CandleNet Portal Server Environment

Copy the presentation databaseThe presentation database contains two files that must be copied:

� presentation.dat

� presentation.idx

To copy the above listed two files from the test machine to c:\candle\cnps to the production machine:

1. Shut down the CandleNet Portal Server on the Production machine (the machine to which you will be copying).

2. Open a Command Prompt window (Start > Run, then type CMD).

3. If your CNP Server installation is on a different drive, change to that drive:c:

where c: is the drive letter.

4. Change to the \candle\cnps directory:cd \candle\cnps

5. Remove the read-only attribute from the presentation files.attrib -r presentation.*

6. Copy the presentation files from the source machine to the target:copy <mapped drive on test machine>:\candle\cnps\presentation.idx

copy <mapped drive on test machine>:\candle\cnps\presentation.dat

where <mapped drive on test machine> stands for the drive on the test machine where these files reside. If a drive is not already defined, you will need to map a drive to the test machine from the production machine with the net use command.

Migrate the CNPS databaseThere are two ways to migrate the CNPS database from one machine to another:

� If the database program is MSSQL7, you can use MSSQL Enterprise Manager to migrate the CNPS database.

� If the database program is DB2 UDB or your site does not have MSSQL Enterprise Manager, Candle provides migrate-import and migrate-export scripts for migrating the CNPS database.

Page 102: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Replicating the CandleNet Portal Server Environment

102 Administering OMEGAMON Products: CandleNet Portal, V195

Run the migrate-export script on the source machine

1. At the test machine, ensure that the CandleNet Portal Server is running.

2. Open a Command Prompt window (Start>Run, then type CMD).

3. If your OMEGAMON XE installation is on a different drive, change to that drive:

c:

where c: is the drive letter.

4. Change the directory to \candle\cnps:cd \candle\cnps

5. Enter:migrate-export.bat

This generates saveexport.sql in the \candle\cnps\sqllib subdirectory.

6. Copy or move file saveexport.sql from the test machine to the production machine (see below).

Run the migrate-import script on the target machine

1. At the production machine, shut down the CandleNet Portal Server.

2. Copy file saveexport.sql, generated by the migrate-export.bat script, from the test machine to c:\candle\cnps\sqllib on the production machine.

copy <mapped drive on test machine>:\candle\cnps\sqllib\saveexport.sql c:\candle\cnps\sqllib

where <mapped drive on test machine> stands for the drive on the test machine where this file resides. If a drive is not already defined, you will need to map a drive to the test machine from the production machine with the net use command.

1. At the command prompt (Start > Run, then type CMD), change to the \candle\cnps directory:

cd \candle\cnps

2. If the user ID is not the same one created when you configured the CNPS data source during installation, enter the following commands where myname is correct user name and mypassword is the correct password:SET KFW_USER=mynameSET KFW_AUTH=mypassword

Page 103: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 103

Replicating the CandleNet Portal Server Environment

SET KFW_DB=CNPSIf you do not specify the correct user ID, the migration import will fail because the user ID to access the CNPS data source will be seen as invalid.

If you don’t remember your user name or want to change the password for the CNPS database, follow the steps for “CNPS user ID” on page 90.

3. Enter this command:migrate-import

4. Restart the CandleNet Portal Server.

Using MSSQL Enterprise Manager

To migrate the CNPS database from the test machine to the production machine using MSSQL Enterprise Manager, your first objective is to create a new user named cnps with a password of cnps in the receiving SQL Server:

1. Start > Programs > Microsoft SQL Server > Enterprise Manager.

2. From the Security folder, right-click Logins and select New Login from the pop-up menu to open the SQL Server Login Properties dialog.

3. In the Name field, type cnps.

4. Select SQL Server Authentication, type the password cnps, and click OK. When prompted, retype the password and click OK. The newly created cnps login displays. Your next objective is to create a new database named cnps in the receiving SQL Server.

5. From the Databases folder, right-click the database named model and select New Database to open the Database Properties dialog.

6. In the Name field, type cnps.

7. Click the Data Files tab, and change the Initial size (MB) to 50.

8. Click the Transaction Log tab, and change the Initial size (MB) to 50.After you click OK, the newly created cnps database is listed under Databases. You are now ready to grant the new cnps user access to the new cnps database.

9. From the Databases folder, expand the cnps database.

10. Right-click Users, then select New Database User from the pop-up menu.

11. In the Database User Properties - New User dialog, select cnps from the Login name list.

Page 104: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Replicating the CandleNet Portal Server Environment

104 Administering OMEGAMON Products: CandleNet Portal, V195

12. In Permit in Database Role, select public, db_owner, db_datareader and db_datawriter, then click OK. The user named cnps has been granted access to the database named cnps. Because a user can be associated with more than one database, you need to force the cnps user ID to access the cnps database by default.

13. From the Security folder, select Logins.

14. From the list of login names on the right, select cnps and click Properties.

15. In the SQL Server Login Properties dialog, select cnps from the Database list, as the default database name, and click OK. The user cnps will by default log on to the database named cnps. You are now ready to use MS SQL Server's Import/Export Wizard to copy the CNPS database named cnps to the receiving SQL Server.

16. Start > Programs > Microsoft SQL Server > Import and Export.

17. From the DTS Import/Export Wizard dialog, click Next.

18. Complete the data source information as follows, then click Next:– For the Data source, select Microsoft OLE DB Provider for SQL

Server

– In the Server field, type the host name where the sending MS SQL Server resides

– Select SQL server authentication

– In the Username field, type cnps

– In the Password field, type cnps

– In the Database field, select cnps

19. Complete the destination information as follows, then click Next:– For the Destination, select Microsoft OLE DB Provider for SQL

Server

– In the Server field, type the host name where the receiving MS SQL Server resides

– Select SQL server authentication

– In the Username field, type cnps

– In the Password field, type cnps

Page 105: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 105

Replicating the CandleNet Portal Server Environment

– In the Database field, select cnps

20. Select Copy Tables, then click Next.

21. Click Select All, then Next.

22. Check Run immediately, then click Next and Finish. The wizard executes the commands, and displays the tables within the CNPS database named cnps that were copied from source to destination.

You have completed migrating the CNPS database from the Test machine to the Production machine.

Page 106: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Migrating Objects from CMW to CandleNet Portal

106 Administering OMEGAMON Products: CandleNet Portal, V195

Migrating Objects from CMW to CandleNet Portal

OverviewSome of the CMW objects that in CandleNet Command Center are stored on the CMS are stored in data repositories on the CandleNet Portal Server:

The first time CandleNet Portal starts up, migration scripts copy CMW objects stored at the hub CMS over to the CNPS database. A log documenting the initial migration process is located in c:\candle\cnps\sqllib\migrate.log.

If your monitoring environment requires you to continue using the CMW, you can add user IDs and managed objects through the CMW and migrate them to your CandleNet Portal environment using scripts provided by Candle. Any new user IDs and managed objects created in the CMW since the last time a migration was performed will be imported into CandleNet Portal.

Migration scriptsThe migration scripts are:

� migrate-new-users-ibmdb2.bat; migrate-new-users-mssql.bat

� migrate-cmw-navigator-ibmdb2.bat; migrate-cmw-navigator-mssql.bat

With them, you can migrate sets of tables associated with entire functional areas and move the CNP Server database from Test to Production.

Table 2. Where Objects are Stored for CandleNet Portal and for the CMW

Objects CandleNet Portal CMW

Policies CMS CMS

Situations CMS CMS

Workspace view (SQL) queries CNPS database N/A

Reports (workspace definitions in CandleNet Portal)

presentation.datpresentation.idx

CMS

Managed objects (Navigator Business view items in CandleNet Portal)

CNPS database CMS

User IDs CNPS database CMS

Page 107: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 107

Migrating Objects from CMW to CandleNet Portal

Migration considerationsWhen you migrate objects from the CMW over to CandleNet Portal, consider the following:

Situations� Alerts for situations you created in the CMW will display in the Navigator

Business view of CandleNet Portal only if they were assigned to a managed object. Alerts for these situations do not appear in the Navigator Physical view unless you associate them with a Navigator item, as described in the CandleNet Portal help and user’s guide.

� If a situation was written in the CMW with a syntax not currently supported by CandleNet Portal, its formula cannot be viewed in the Situation editor and a message will display in the status bar.

� The event indicators supported in CandleNet Portal are Critical,

Warning, and Informational.

Managed Objects� Managed objects in the CMW are migrated to CandleNet Portal at

installation time, and can be seen in the Navigator Business view. Thereafter, any changes make to managed objects through the CMW will not appear in the Navigator Business view, unless you run the migrate-cmw-navigator.bat script. See “Migrating New CMW Managed Objects to CandleNet Portal” on page 110.

User IDs� During installation, user IDs defined to the CMW are migrated to the

CandleNet Portal Server. After product installation, any changes to user IDs made in the CMW are not available in CandleNet Portal unless you run the Candle-provided migrate-new-users.bat script. See “Migrating Additional Users from CMW to CandleNet Portal” on page 108.

Navigator view Alerts show for CMW user-defined situations

Alerts show for CNP predefined situations

Business yes no, unless you associate them with Navigator items

Physical no, unless you associate them with Navigator items

yes

Page 108: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Migrating Additional Users from CMW to CandleNet Portal

108 Administering OMEGAMON Products: CandleNet Portal, V195

Migrating Additional Users from CMW to CandleNet Portal

OverviewUse the migrate-new-users script to copy users defined in the CMW over to CandleNet Portal subsequent to product installation.

Although we provide the ability to migrate users from CMW, we recommend you add users through CandleNet Portal with the User Administration feature. See “User Administration” on page 68.

Run the migrate-new-users scriptTo use the migrate-new-users.bat script:

1. Ensure that the CandleNet Portal Server is running.

2. Open a Command Prompt window (select Start > Run, then type CMD).

3. If your OMEGAMON XE installation is on a different drive, change to that drive:

c:

where c: is the drive letter.

4. Change directory to \candle\cnps:cd \candle\cnps

5. From the \cnps directory, enter the appropriate command:migrate-new-users-ibmdb2.bat UDB

migrate-new-users-mssql.bat MSSQL7 or MSDE

Notes� The Navigator Physical and Business views will be assigned automatically

to the migrated user IDs. Any other custom Navigator views must be assigned manually (Administer Users dialog).

� If the User Administration dialog is being used on the CandleNet Portal client, close and re-open User Administration to refresh the user list.

Page 109: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal Migration 109

Migrating Additional Users from CMW to CandleNet Portal

� Subsequent to migrating a user ID, if you change the permission settings for that user in the CMW, you must make the same change for that user in CandleNet Portal. Additionally, if you remove a user from the CMW, the same removal operation must be performed in CandleNet Portal.

� Users with Create User authority in CMW receive permissions for all features of CandleNet Portal. For users who do not have Create User authority in CMW, we recommend that, after migration, you verify the permissions set in CandleNet Portal to ensure these users have the intended permissions. See “User IDs” on page 128.

Page 110: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Migrating New CMW Managed Objects to CandleNet Portal

110 Administering OMEGAMON Products: CandleNet Portal, V195

Migrating New CMW Managed Objects to CandleNet Portal

OverviewThe migrate-cmw-navigator script allows you to migrate managed objects from CMW to CandleNet Portal any time after initial product installation. Managed objects created in the CMW appear in the Navigator Business view of CandleNet Portal (OMEGAMON DE only) as Navigator items with the equivalent icon.

This migration script merges into the Navigator CMW Business view any CMW managed objects that were added since first-time installation of CandleNet Portal or since the script was last run.

Run the migrate-cmw-navigator scriptTo use the migrate-cmw-navigator script:

1. Stop the CandleNet Portal client(s).

2. Ensure that the CandleNet Portal Server is running.

3. Delete the Business view from the CandleNet Portal client.

4. Open a Command Prompt window (select Start>Run, then type CMD).

5. If your OMEGAMON XE installation is on a different drive, change to that drive:

c:

where c: is the drive letter.

6. Change directory to \candle\cnps:cd \candle\cnps

7. From the \cnps directory, enter the appropriate command:migrate-cmw-navigator-ibmdb2.bat UDB

migrate-cmw-navigator-mssql.bat MSSQL7 or MSDE

8. Restart the CandleNet Portal Server, then the CandleNet Portal client(s).

Page 111: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 111

CandleNet Portaland the CMW

IntroductionCandleNet Portal replaces the Candle Management Workstation (CMW) as the user interface for the OMEGAMON Platform. This appendix lists the features of CandleNet Portal, those available only in the CMW, and the features they have in common.

If you have an existing CandleNet Command Center (CCC) installation and are already using the CMW for system management, this appendix is for you.

If you have a new OMEGAMON XE installation and would like to augment its capabilities with those from the CMW, see “Functional Comparison” on page 116.

For information on migrating objects from CMW to CandleNet Portal, see “Migrating Objects from CMW to CandleNet Portal” on page 106.

Appendix contentsFeatures Exclusive to CandleNet Portal . . . . . . . . . . . . . . . . . . . . . . . . . . 112Conceptual Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Functional Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116CMW and CandleNet Portal Working Together . . . . . . . . . . . . . . . . . . . . 128What’s next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

A

Page 112: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Features Exclusive to CandleNet Portal

112 Administering OMEGAMON Products: CandleNet Portal, V195

Features Exclusive to CandleNet Portal

OverviewCandleNet Portal has many features not available in the CMW. This section lists the major new capabilities, along with references to topics you can read to learn more.

CandleNet Portal features In CandleNet Portal you can:

� View a web site in your workspace using the browser view.

� See your managed enterprise as a navigation tree and create business views to convey any logical hierarchy of your managed enterprise.

� Observe event indicators in the Navigator and in the graphic view, and hear a sound (.wav file) when an event opens.

� Keep a real-time report of events as they arrive and when the status changes in the message log view and in the event console view.

� Start a terminal session as a view within a workspace and write scripts for automated terminal sessions.

� Select from predefined workspaces and create new workspaces.

� Get data snapshots when editing table and chart properties.

� Start CandleNet Portal browser mode and open a workspace by entering its URL in your browser.

� Define your own queries for controlling what data is retrieved from managed systems or from ODBC-compliant data sources for display in data views.

For a complete list of the tasks you can perform in CandleNet Portal and of the CMW features not available in CandleNet Portal, see “Functional Comparison” on page 116.

Page 113: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 113

Conceptual Differences

Conceptual Differences

OverviewThe Candle Management Workstation user interface design follows an OS/2 and Windows model. The CandleNet Portal design follows a web model. Most functions available on the CMW are available on CandleNet Portal, but they are executed differently and more features have been added to CandleNet Portal.

This section describes the CMW features that are conceptually different or not applicable in CandleNet Portal.

CMW and CandleNet Portal

Connect objects in a situation

In the CMW, you have a graphical editor for situations, and in CandleNet Portal it is a tabular editor. Objects are not connected graphically in CandleNet Portal, but by their position in the tabular editor:

� Each attribute adds a column to the table and each expression occupies a cell.

� Boolean AND logic is applied when multiple expressions for multiple attributes are written in the same row.

� Boolean OR logic is applied when multiple expressions are written on separate rows.

� Each cell has list buttons for selecting a function and operator for the expression. See the topic on formula functions in the CandleNet Portal help or user’s guide.

Create situation templates

There is no equivalent of this feature in CandleNet Portal. In the Situation editor, you assign a state as part of the situation association with a Navigator item.

Page 114: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Conceptual Differences

114 Administering OMEGAMON Products: CandleNet Portal, V195

Managed objects

In the CMW, managed objects are created from the managed object template. The template is where you apply a state to a situation, and it enables you to create logical groupings of situations. If you have managed objects from the CMW, they will appear in the Navigator Business view of CandleNet Portal. The Navigator Business view is available in OMEGAMON DE only. See “What is OMEGAMON DE?” on page 29. You can build other Navigator views for different user requirements and for different perspectives of your managed network.

You cannot create a managed object in CandleNet Portal. Using the Situation editor, you distribute the situation to the systems where it should run, and you assign a state as part of the situation’s association with a Navigator item. When a situation becomes true, event indicators appear in the Navigator view.

Additionally, with OMEGAMON DE, you can add a Graphic view to a workspace. This is the equivalent of the Graphic view in the CMW. The Graphic view enables you to add a background image and cover it with icons. Each icon represents a Navigator item, including any event indicators.

Alert indicators

When a situation created in the CMW becomes true, its alert indicator shows up on the managed object.

In CandleNet Portal, when an event indicator appears over a Navigator item, mouseover it to see a flyover list of true situations associated with the item. Click the situation whose event you are interested in to open its event workspace. The event workspace reports the initial and current attributes, displays expert advice written for the situation, and has a take action view so you can send a command to a managed system.

Additionally, the message log view and event console view show you the alerts that have occurred on your monitored system. The event console has a toolbar for filtering the view to show only the alerts you want to see and a pop-up menu for managing alerts.

Page 115: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 115

Conceptual Differences

Enterprise

The Enterprise Events view in the CMW is a window. To see more detail, you drill down and open more windows. The application window in CandleNet Portal shows the whole structure in the Navigator, built in a tree-like hierarchy as folders. The Enterprise item is at the root of the tree.

Create custom views

A view in CandleNet Portal is a pane in a workspace. Every Candle monitoring agent comes with a set of predefined workspaces, each with its own set of views. CandleNet Portal comes with over a dozen view choices, from charts and tables to browser and terminal emulator. You can add any appropriate view to a workspace, modify its properties, then save the workspace (or save a new workspace) if you want to keep it.

Reports

In the CMW, reports are information queries. They display as columnar tables, and some have graphs to show more detail. What is called a report in the CMW is a table view in CandleNet Portal. The table view can be one of many views in a workspace, one workspace (or more) per item in the Navigator.

Page 116: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

116 Administering OMEGAMON Products: CandleNet Portal, V195

Functional Comparison

OverviewWhich tasks can you still do in the CMW? Which functions created in the CMW will be supported in CandleNet Portal? The table below offers a comparison of both applications.

Table 3. Comparing CMW and CandleNet Portal Functions

CMW Function Available in

CandleNet Portal?

Description

Running the Software for the First Time

See “Preparing your CandleNet Portal Environment” on page 39.

Change CMS Location Brokers

yes This is completed during installation. You can reconfigure this through the CandleNet Portal Server at any time after installation.

Import and export seed data

yes CandleNet Portal contains migrate-export.bat and migrate-import.bat migration scripts. These scripts migrate entire databases. See “Migrating Objects from CMW to CandleNet Portal” on page 106.

Export take action objects yes This is completed during installation.

Hot standby no In a CMW installation, you can designate a secondary CMS as a Hot Standby. Should the primary CMS become unavailable, you can switch to the Hot Standby hub, which then takes over automatically. You can name a secondary hub CMS in a CandleNet Portal installation, but if you switch to it, you must edit the global site file and recycle the CandleNet Portal Server for the change to take effect. See “User Administration” on page 68

Page 117: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 117

Functional Comparison

Trace settings yes CandleNet Portal enables users to dynamically change the trace information for troubleshooting with Candle Customer Support. See “Setting a Trace” on page 96. See also “Candle Customer Service and Satisfaction” on page 15.

User Administration See “User Administration” on page 68.

Create access and authority privileges for the first user

yes When you install OMEGAMON XE, a user ID named SYSADMIN is assigned automatically with full administrative authority. Use SYSADMIN to log onto CandleNet Portal for the first time, then add other user IDs through Administer Users.

Also during installation, user IDs defined to the CMW are migrated to the CandleNet Portal Server. After OMEGAMON XE installation, any changes to user IDs made in the CMW are not available in CandleNet Portal; the reverse is true for changes made to user IDs in CandleNet Portal. User IDs added to CMW after initial OMEGAMON XE installation can be migrated to CandleNet Portal by using the migrate-new-users.bat script. See “Migrating Additional Users from CMW to CandleNet Portal” on page 108.

Add a new user yes This is done through Administer Users.

Copy an existing user yes This is done through Administer Users.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 118: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

118 Administering OMEGAMON Products: CandleNet Portal, V195

Validate user access yes User access to CandleNet Portal is validated at the CandleNet Portal Server. However, if the CMS is configured to Validate User, the CandleNet Portal Server requests the CMS to ask the operating system for user ID and password validation when users log onto CandleNet Portal. Be sure to also define all user IDs to the operating system if you are using the Validate User option.

Set authority yes This is done through Administer Users.

Set who can switch hubs no This is done outside of CandleNet Portal. The CMS confirms the user’s authority for switching to a secondary CMS.

Situations

Modify a product-provided situation

yes Any situation that can be viewed in the CandleNet Portal Situation editor can be edited. If a situation was written in the CMW with a syntax not currently supported by CandleNet Portal, its formula cannot be viewed or edited in the Situation editor. A message will display in the status bar.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 119: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 119

Functional Comparison

Edit situations graphically no CandleNet Portal supports what is created in the CMW. Editing of situations in CandleNet Portal is done using a tabular editor, rather than graphically. If a situation was written in the CMW with a syntax not currently supported by CandleNet Portal, its formula cannot be viewed or edited in the Situation editor. A message will display in the status bar.

When a situation created in the CMW becomes true, its alert indicator may not show up in the Navigator Physical view. If this is the case, access the Situation editor starting from the system where the situation is distributed, select the situation, and click Apply or OK.

Create a situation yes Situations are created using the CandleNet Portal Situation editor.

Create a new situation with one or more expressions

yes You can build a condition (predicate) with one or more expressions using Boolean AND and OR logic.

Set the monitoring interval for a situation

yes This is done using the Condition tab of the Situation editor.

Set situation persistence yes Situation persistence is enabled in the Situation editor using Condition > Advanced > Situation Persistence. This feature enables you to set the number of sampling intervals the situation remains true before the command specified in the Action tab is invoked.

Set the threshold for a situation

yes This is done using the Condition tab of the Situation editor.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 120: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

120 Administering OMEGAMON Products: CandleNet Portal, V195

Create advice for a situation

yes Advice written for the situation appears in the Expert Advice pane of the event workspace for a situation. Note that you can add hypertext links to the text and HTML coding.

Create missing predicates yes When you add a text attribute to a situation, you can apply a Check for Missing Items function to evaluate the situation as true if the specified value is not returned.

Create wildcard predicates

no Although CandleNet Portal does not support the * (asterisk) wildcard predicate, you can use the SCAN or STR function to the same effect. See Formula Functions in the CandleNet Portal help or user’s guide.

Take action yes You can create a Take Action command from the Situation editor. You can also creation a Take Action command from the Take Action and from the Navigator pop-up menu.

Create an Until modifier yes This is done using the Until tab of the Situation editor.

Create LaunchPad entries no CandleNet Portal does not currently support this feature.

Display the Universal Message Console

no CandleNet Portal does not currently support this feature. However, if you have OMEGAMON DE, you can add a Universal Message activity to a policy. You can also use the Action tab in situations to send a message to a Universal Message console that displays on the CMW.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 121: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 121

Functional Comparison

View a display item yes Display item is an attribute you designate to further qualify a situation. This optional addition to the situation enables you to quickly distinguish situations in the Message Log view and in the Event Console view.

Delete a situation yes You can delete a situation that was created in the CMW. This may cause problems if the situation has dependencies in the CMW (such as templates and policies). We recommend that you do not delete CMW-created situations in CandleNet Portal.

Start or stop a situation yes You can start or stop a situation from several places, such as from the situation flyover list and from the Event Console view.

Activate a situation at startup

yes This is done using the Condition tab of the Situation editor.

Distribute a situation yes This is done using the Distribution tab of the Situation editor.

Create situation templates no CandleNet Portal has no logical equivalent of a situation template. You assign the state in the Situation editor when you associate a situation with a Navigator item. Event indicators appear on the affected Navigator items.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 122: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

122 Administering OMEGAMON Products: CandleNet Portal, V195

Managed objects yes (OMEGAMON DE only) Managed objects in the CMW are migrated to CandleNet Portal at installation time, and can be seen in the Navigator Business view. Thereafter, any changes made to managed objects through the CMW will not appear in the Navigator Business view, unless you run the migrate-cmw-navigator.bat script. See “Migrating New CMW Managed Objects to CandleNet Portal” on page 110.

You can edit the Business view and create other Navigator views. You can also add a Graphic view to a workspace to see the Navigator item in a graphic, such as a map or a building diagram.

Unknown state yes In the CMW, a managed object appears in this state when the CMW has lost contact with a managed system to which it is distributed. In CandleNet Portal, the Navigator view dims (grays out) any Candle agents in the unknown state.

(OMEGAMON DE only) The Navigator Business view indicates this state with the unknown icon. The situation flyover listing on this icon shows *STATUS_UNKNOWN. This is not actually a situation, but the notation for a problem on the managed system.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 123: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 123

Functional Comparison

Managed system lists yes A managed system list is a defined set of managed systems to which you can distribute a situation. Any managed system lists defined in the CMW are migrated to CandleNet Portal during installation. You can create managed systems lists and use them in situations, policies, queries and custom Navigator views.

Policies yes

Create policies yes (OMEGAMON DE) CandleNet Portal provides a single split-pane window for creating and managing policies. You use the Workflow Editor to create, modify and to manage policies. Policies created in the CMW are available in CandleNet Portal.

Policy microscope no CandleNet Portal does not currently support this feature.

Work groups and work lists

no A work group is a group of users with similar responsibilities and expertise who have access to the same work items. A work item is the request a policy sends to a work group asking for user intervention. CandleNet Portal does not currently support creating work groups, but it does support the work groups that were created in the CMW.

Monitoring Your Enterprise

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 124: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

124 Administering OMEGAMON Products: CandleNet Portal, V195

Events view yes The situation flyover list in CandleNet Portal provides the equivalent of the CMW Events view. When you see an event indicator in the Navigator or in a graphic view, move your mouse pointer over it to see a flyover list of situations categorized by their state: critical, warning or informational. Click a situation in the flyover list to open its event workspace with tables of initial and current values, expert advice, and a take action view.

Graphic view yes (OMEGAMON DE only) You can add a graphic view to a workspace and apply one of the graphics included with CandleNet Portal or apply one of your own graphics. The formats supported are .JPG, .GIF, and .PNG. If you have already used graphics in the CMW, they must be converted from .BMP to .GIF, .JPG, or .PNG to use them in a CandleNet Portal graphic view.

Review advice yes A situation can have expert advice written for it.

Use the Attribute view to obtain additional information about an event

yes Initial attributes and current attributes are shown in the event workspace.

Acknowledge an event yes When you open an event workspace, the situation appears in the Navigator. Right-click the situation name to see Acknowledge in the pop-up menu.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 125: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 125

Functional Comparison

Reset a situation yes When you open an event workspace, the situation appears in the Navigator. Right-click the situation name and select Close Event from the pop-up menu.

Take action on an event yes A Take action command can be included with a situation to run when the situation becomes true. The event workspace also has a Take Action view that you can use to enter a command.

Open a 3270 session yes You can create a terminal view in any workspace to start a 3270 or 5250 session.

OMEGAVIEW Zoom no When you investigate events in the CMW, you can start a 3270 terminal emulator session and go directly to the destination panel identified by the OMEGAVIEW Enhanced Zoom for that OMEGAMON. Although this feature is not implemented in CandleNet Portal, you can add a terminal view to the event workspace and start a 3270 or a 5270 session. You can also record your interactions with the host, then replay the script at any time. This allows you to automate navigation to a specific set of screens.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 126: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Functional Comparison

126 Administering OMEGAMON Products: CandleNet Portal, V195

Reports yes The equivalent of a CMW report in CandleNet Portal is a table view. The table view is part of the workspace.

Candle monitoring agents come with predefined workspaces for CandleNet Portal, many with the same names as their CMW report counterpart. Such workspaces will contain at least one table view, and often multiple table and chart views. You can also create and customize your own workspaces and table views in CandleNet Portal.

Collecting and Viewing Historical Data

See the topic on configuring historical data collection in the CandleNet Portal help or user’s guide. See also the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center for information on how to configure historical data collection.

Configuring historical data collection

yes You can configure historical data collection through the History Configuration program, Configure tab. Specify the attribute groups for which to collect data.

Using history bars to view prior conditions

no CandleNet Portal does not currently support this feature.

View summary states in the preceding hour

yes Historical data is available in the table, bar chart, pie chart, and plot chart views when historical collection has been configured and started for the Candle agent(s) associated with the view.

EIB Change Log no CandleNet Portal does not currently support this feature.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 127: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 127

Functional Comparison

View alerts historical data yes CandleNet Portal does not support the history logs available through the CMW Logs window, except Status History. However, the Message Log view lists the status changes in situations (such as open events and reopened events) over the last 24 hours.

The event workspace reports the initial and current values that made the situation fire and when it fired.

Table 3. Comparing CMW and CandleNet Portal Functions (continued)

CMW Function Available in

CandleNet Portal?

Description

Page 128: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CMW and CandleNet Portal Working Together

128 Administering OMEGAMON Products: CandleNet Portal, V195

CMW and CandleNet Portal Working Together

User IDsThe user IDs and authorities established in the CMW are stored at the CMS and then migrated to the CandleNet Portal Server during installation. Permissions for CandleNet Portal-only features are not applied to the user IDs that were migrated from the CMW. These are:

� Custom Navigator Views - Modify

� Query - View; Modify

� User Administration - Workspace Administration Mode

� User Administration - Workspace Author Mode

The status overview object is the highest level managed object the user can see in the CMW. This permission is kept in CandleNet Portal, so the CMW status overview object will be the top level item the user sees in the Navigator Business view.

CandleNet Portal does not use the settings that apply only to the CMW:

� Switch Hub

� Policy Microscope

� Status

� Template

� LaunchPad

� WorkGroup

� Trouble Ticket

Although we provide a migration batch file for copying CMW-created user IDs to CandleNet Portal, we recommend you create additional users in CandleNet Portal. See “Migrating Objects from CMW to CandleNet Portal” on page 106.

Reports and workspacesThe equivalent of a CMW report in CandleNet Portal is a table view. Most product-provided reports for the CMW have been consolidated into predefined workspaces in CandleNet Portal.

Page 129: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 129

CMW and CandleNet Portal Working Together

Candle agents come with predefined workspaces for CandleNet Portal, many with the same names as their product-provided report equivalent. These workspaces contain at least one table view, and often other table and chart views.

You can see the workspaces available for a particular item in the Navigator by selecting the item, then opening View > Workspace.

Business view (OMEGAMON DE only)CandleNet Portal displays all CMW-created managed objects as items in the Navigator Business view. You can create Navigator views for any hierarchy. You can also add a Graphic view to a workspace to see Navigator items on a background image, such as a map or a building diagram.

SituationsProduct-provided situations in the CMW can also be seen in CandleNet Portal. An event for a user-defined situation from the CMW appears in the Navigator Business view if the situation was associated with the Navigator item.

Editing CMW-created situations in CandleNet Portal

In CandleNet Portal, you can modify most situations written in the CMW. However, if a situation has syntactical elements that are not supported by CandleNet Portal, the situation will run properly but it cannot be viewed or edited in the Situation editor.

The following CMW functions are currently not available in the Situation editor:

� Nested (embedded) situations

� Connecting objects graphically

Page 130: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CMW and CandleNet Portal Working Together

130 Administering OMEGAMON Products: CandleNet Portal, V195

To display a CMW situation in CandleNet Portal:

1. Right-click the Navigator item and select Situations from the pop-up menu. This menu option appears only on Navigator items with managed systems assigned: In the Navigator Physical view, managed systems are preassigned to every item except those at the operating platform level (such as Windows Systems) and cannot be changed; in the Navigator Business and custom views, managed systems are assigned when you create a Navigator item or edit its properties.

The Situation editor opens. The Situation tree lists the situations for the Navigator level chosen. For example, at the agent level of the Navigator Physical view, you will see all situations written with attributes from that agent, and at the attribute level, you will see all situations written with attributes from that group (or groups).

2. If you do not see the CMW situation, click Situation Filter, check Eligible for Association, then click OK.

3. Select the situation from the tree on the left.The situation formula displays in the tabular editor of the Condition tab. If you do not see the formula, the situation is not editable in CandleNet Portal and a message appears in the Status bar.

Note: In CandleNet Portal it is possible to delete a situation that was created using CMW. This may cause problems if the situation has dependencies (such as templates and policies) in the CMW. We recommend you do not delete situations from CandleNet Portal that were created in the CMW.

A situation in error

A situation in error means the CMS cannot evaluate the condition. If you want to monitor this situation in CandleNet Portal, you need to modify it to a syntax that is acceptable.

PoliciesPolicies created in the CMW work the same way in CandleNet Portal. This release of CandleNet Portal has no facility for creating work groups, but it does support what is created in the CMW.

Note: In this release of CandleNet Portal, it is possible to delete a policy that was created using CMW. This may cause problems if the policy has

Page 131: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CandleNet Portal and the CMW 131

CMW and CandleNet Portal Working Together

dependencies (such as an embedded policy) in the CMW. We strongly recommend that you not delete policies from CandleNet Portal that were created in the CMW.

Managed system listsManaged system lists are defined lists of managed systems. Your OMEGAMON product comes with one list defined for the product, such as UNIX Systems. If you have a CMW installation, any managed systems lists you created using CMW are available in CandleNet Portal. You can create additional lists in the Manage System List editor.

Removing managed systemsCandleNet Portal indicates when a Candle agent is unavailable by dimming its Navigator item in the Navigator Physical view. If the agent has been permanently disconnected from the CMS, it will continue appear as a dimmed Navigator item. If you want to remove it from the Navigator view permanently, you must do so through the CMW’s Managed Systems Window.

Configure historical data collectionYou can configure historical data collection in CandleNet Portal. Unlike the CMW, however, you cannot configure data collection for individual attributes. If you want to exclude certain attributes from a group, you must configure collection from the CMW.

What’s nextYou have now learned about the conceptual and functional differences between CandleNet Portal and the CMW. If your site has purchased the OMEGAMON Web Services solution, see “OMEGAMON Web Services” on page 133 for information on how to use this product.

Page 132: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

CMW and CandleNet Portal Working Together

132 Administering OMEGAMON Products: CandleNet Portal, V195

Page 133: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 133

OMEGAMONWeb Services

IntroductionThis appendix describes the OMEGAMON Web Services feature.

Note: Before executing SOAP requests using Internet Explorer Version 5.0x, you must first install service pack MSXML 3.0. Otherwise, your SOAP requests will not work. Internet Explorer Version 6.0x includes this service pack.

Appendix contentsWhat is OMEGAMON Web Services? . . . . . . . . . . . . . . . . . . . . . . . . . . . 134SOAP Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

B

Page 134: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

What is OMEGAMON Web Services?

134 Administering OMEGAMON Products: CandleNet Portal, V195

What is OMEGAMON Web Services?

OverviewThe OMEGAMON Web Services solution provides you with an industry-standard open interface into Candle’s OMEGAMON XE and DE solutions. This open interface provides easy access to Candle’s performance and availability data, allowing you to use this information for advanced automation and integration capabilities.

OMEGAMON Web Services implements a client/server architecture. The client sends SOAP requests to the OMEGAMON SOAP server. The server receives and processes the SOAP requests from the client.

Predefined SOAP methods let you perform many functions within the OMEGAMON platform environment. You can begin to use Candle’s SOAP methods immediately. You can also use Candle’s SOAP methods as templates in creating your own advanced methods.

SOAP works with any programming or scripting language, any object model and any Internet wire protocol. Candle’s SOAP methods can be invoked via PERL, Javascript, VBSCRIPT, JSCRIPT, C++, and through a browser.

See the Installing Candle Products on Windows document for instructions on installing and on configuring this product on the hub CMS.

What is SOAP?Simple Object Access Protocol (SOAP) is a communications XML-based protocol that lets applications exchange information via the Internet. SOAP is platform independent and language independent. SOAP uses XML to specify a request and reply structure. It uses HTTP as the transport mechanism to drive the request and to receive a reply.

Important: Prior to using Candle’s solution, you must have a basic understanding of SOAP, of Extensible Markup Language (XML) and XML Namespaces, and of the Web Services Description Language (WSDL). To access information and tutorials on these topics, go to w3schools.com. See also w3.org/TR/SOAP.

Page 135: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 135

Using OMEGAMON Web Services

Using OMEGAMON Web Services

OverviewCandle provides numerous SOAP methods with OMEGAMON Web Services. These methods allow you to dynamically query and control OMEGAMON XE and OMEGAMON DE environments.

Using Candle’s SOAP methods, you can:

� stop or start policies and situations

� forward AF/Remote trapped messages and display them on a Universal Message console

� retrieve attribute data that you can display in charts or reports

� open and close events

� make real-time requests for data

� issue SOAP requests as system commands in CandleNet Portal or CMW

You can also use this product to test a request to ensure it works properly. You can then create a policy that submits multiple requests for processing. In addition, you can generate daily operation summaries.

You can store retrieved data in the Candle data warehouse, as described in the historical data collection guide.

Note: OMEGAMON Web Services provides XML data rows. Use Candle’s SOAP methods in combination with your own scripts to display the data in charts and tables. For help in developing scripts, contact Candle Consulting and Services personnel.

User IDsImportant: At installation and configuration time, you will be asked to supply user IDs for those who should have access to CMS data. If no user IDs are supplied, all users will be given permission to update data.

User IDs must be identical to those specified for CMS logon validation. Access is restricted to only that CMS to which a user has access.

You can also make changes at a later time to add or to remove users’ access to CMS data. See the Installing Candle Products on Windows guide for details.

Page 136: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Starting the SOAP Client and Making a Request

136 Administering OMEGAMON Products: CandleNet Portal, V195

Starting the SOAP Client and Making a Request

OverviewThere are several ways of starting Candle’s SOAP client. Two are described here:

� Using Internet Explorer

� Using the SOAP client command line utility (not available on OS/390)

When you use the SOAP client in conjunction with Internet Explorer to issue SOAP requests, you can modify, if needed, the tags or the text. In contrast, the command line utility simply displays the output of the request at the command prompt. For descriptions of SOAP requests, see “SOAP Methods” on page 140.

Note: Before you can access newly created Universal Agent objects, the hub CMS where the SOAP server is running must be recycled. See the Installing Candle Products on Windows guide for instructions on configuring the Hub CMS.

Using Internet ExplorerAfter installing Candle’s SOAP client, perform these actions:

1. Start Internet Explorer version 5 or higher.Be sure to enable the Access data sources across domains option in Internet Explorer’s security settings.

2. In the Address field, type the URL for the SOAP client: http://hostname:1920///cms/soap/kshhsoap.htm

where hostname can be used literally when accessing the SOAP server running on the same machine or changed to the proper host name or network address of a SOAP server running on a different machine. The port number for the Candle HTTP service is 1920.

Note: You can also route requests to a remote hub by replacing soap in the Address field with the alias name of the hub you want to access (HUB_hostname in the example below). The alias must have been previously defined to the SOAP server (for information on defining hub aliases, see the installation documentation). For example:

Page 137: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 137

Starting the SOAP Client and Making a Request

http://hostname:1920///cms/HUB_hostname/kshhsoap.htm

The SOAP client HTML page displays.

3. Select a SOAP method from the list in the first field. After you select a method, the other fields fill in automatically.

4. Modify, if needed, the tags or the text in the “Edit Payload (XML)” area.

5. Click Make SOAP Request. The output of the request displays in the Your SOAP Request Payload area. For examples of using Candle’s SOAP client, see “Scenarios” on page 157.

Note: When issuing a CT_Get request against a particular agent type, the CMS where the SOAP server is running must be configured and seeded for that agent type. For example, when issuing a CT_Get request for an MVS agent connected to an MVS CMS, the CMS running the SOAP server must be configured and seeded for that MVS agent.

Using the SOAP client command line utility (kshsoap)The SOAP client command line utility, kshsoap, is an http client. It issues direct SOAP requests. It does this by sending the SOAP request you specified in two text files and by displaying the output of your SOAP request at the command prompt.

Windows systems

To use kshsoap:

1. On the CMS machine where the SOAP server is installed, change to the c:\candle\cms directory.

candle

cms

2. Create a text file named “SOAPREQ.txt” and type the following SOAP request:

<CT_Get><object>ManagedSystem</object></CT_Get>

Or if security has been enabled:

<CT_Get><userid>logonid</userid><password>password</password><object>ManagedSystem</object></CT_Get>

Page 138: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Starting the SOAP Client and Making a Request

138 Administering OMEGAMON Products: CandleNet Portal, V195

3. Create another text file named “URLS.txt” containing URLs that will receive the SOAP request, such as:

http://affiliatecompanyhostname:1920///cms/soap

In this example, affiliatecompanyhostname is the name of the receiving machine and where the hub CMS is installed.

4. At the command prompt, enter:kshsoap SOAPREQ.txt URLS.txt

This utility processes the SOAPREQ file and displays the URL destination and request. It sends the SOAP request to each URL listed in the URLS file, then displays the URL and the response message received.

Systems with APPN installed

When running kshsoap on systems that have APPN installed, you may encounter an error message stating that an APPN file needs to be configured. To resolve this situation, modify the environment variable KDE_WAPPC32.

To modify this variable, from the command prompt window that you are going to run kshsoap in, enter this:

SET KDE_WAPPC32=none

UNIX systems

To invoke the SOAP command line utility in UNIX, run the CandleSOAPClient script located in the $CANDLE_HOME\bin directory. The CandleSOAPClient takes the same parameters as described above for running kshsoap.exe on Windows.

Page 139: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 139

Starting the SOAP Client and Making a Request

Issuing SOAP requests as system commandsIn CandleNet Portal or in the CMW, you can use the Take Action feature to issue SOAP requests as system commands in policies or in situations. The SOAP requests are stored in a text file.

In CandleNet Portal, you can issue a SOAP request in a situation using the Action tab of the Situation Editor, or in a policy using the Take action or Write message activity of the Workflow editor. See the user’s guide for more on the Situation editor and Workflow editor.

In the CMW, use the Action tool to issue SOAP requests as system commands in situations and policies. See the CMW help for more information.

Note: When using the soap command in a policy, the policy must be configured to run at the CMS.

The soap command is:

soap:CT_Execute,filename=SOAPREQ

where:

� CT_Execute is the name of the SOAP method that allows you to execute a SOAP request that is stored in a file

� SOAPREQ is the name of the file you created that contains the CT_EMail SOAP request.

For example, SOAPREQ might contain:

<CT_EMail><server>n-smtpmta</server><sender>[email protected]</sender><receiver>[email protected]</receiver><subject>AFDATA untouched by human hands</subject><attachmenttitle>AFData.htm</attachmenttitle><request><attach>res.pfx</attach></request><request id="XMLID" ><CT_Redirect endpoint="http://sp22.candle.com:18882"><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > <SOAP-ENV:Body> <AF_Execute> <Exec>SOAP0002</Exec> </AF_Execute> </SOAP-ENV:Body> </SOAP-ENV:Envelope></CT_Redirect></request><request><attach>res.sfx</attach></request></CT_EMail>

Page 140: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

140 Administering OMEGAMON Products: CandleNet Portal, V195

SOAP Methods

OverviewEach SOAP method provided by Candle and its supported tags is described below.

Table 4. Predefined SOAP Methods

SOAP Method Supported Tags SOAP Tag Usage Examples

CT_ActivateStart a situation or a policy running on the OMEGAMON platform.

<name> The name of the situation or policy. This is a required tag.

<type> The type of object being activated. This tag is required.<userid> The user ID to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password> The password to access the hub CMS. Required for CMS/hub logon validation.Optional:<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_Activate><hub>MVSPROD</hub><name>name_of_situation_or_policy </name>

<type> situation</type>

<userid>sysadmin</userid>

<password>xxxxxxxx</password> </CT_Activate>

Page 141: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 141

SOAP Methods

CT_AcknowledgeSend an event acknowledgement into the OMEGAMON platform.

<name>The name of the situation. This is required.

<source> The source of the event (agent name or CMS name). The acknowledge applies to all the active sources of the named alert if the source is not supplied.<data> "No data was provided" is inserted if not provided.<item>Display item. Optional:<userid> The user ID to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided.<password> The password to access the hub CMS. Required for CMS/hub logon validation.<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<expire> Expires the acknowledgement after the number of minutes entered here.

<CT_Acknowledge><hub>MVSPROD</hub> <name>situation_from_CT </name>

<source>CT_supported_system </source>

<data>Jack is taking care of this failure</data>

<item>subsystem</item>

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_Acknowledge>

<expire>60</expire>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 142: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

142 Administering OMEGAMON Products: CandleNet Portal, V195

CT_AlertSend an event into the OMEGAMON platform.

<name> The name of the situation. This is required.

<source> The source of the event (agent name or CMS name). This is a required tag.

<data> "No data was provided" is inserted if not provided or if no optional object.attribute tag provided.

<item>Display item. Optional:<userid> The user ID to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password> The password to access the hub CMS. Required for CMS/hub logon validation.<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<data><object.attribute> Returns the value of the attribute (or attributes) specified. In the CMW the value appears in the Initial Attributes View.

<CT_Alert><hub>MVSPROD</hub><name>situation_from_XXX </name>

<source>XXX_supported_system </source>

<data><NT_Logical_Disk.Disk_Name>C:</NT_Logical_Disk.Disk_Name></data><item>subsystem</item>

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_Alert>

Note: When you specify object.attribute in the data tag, leave out any non-alphanumber characters other than the underscore (_). For example, NT_System.%_Total_Processor_Time would be entered as NT_System.Total_Processor_Time.

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 143: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 143

SOAP Methods

CT_DeactivateStop a situation or policy on the OMEGAMON platform.

<name> The name of the situation or policy. This is required.

<type> The type of object (situation or policy). This is required.<userid>The user ID to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided.<password> The password to access the hub CMS. Required for CMS/hub logon validation.Optional:<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_Deactivate> <hub>MVSPROD</hub><name>name_of_situation_or_policy </name>

<type>situation</type>

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_Deactivate>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 144: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

144 Administering OMEGAMON Products: CandleNet Portal, V195

CT_EMailSend the output from another CT SOAP method, such as CT_Get, using email through an SMTP server to a defined email address. (not available on OS/390)

<server> smtp server name/network address is required.<sender> Sender’s email address is required. <receiver> Receiver’s email address is required.<subject> Email subject is optional.<message> Email message is optional.<attachmenttitle>Attachment title is optional.<request> When specifying a second-level request, such as CT_Get, each sub-request must be included within a <request> </request> tag. Optional:An id=" " element added to the <request> tag will generate a <request id=”XMLID“> element enclosing the corresponding response for that sub-request.See “Issuing second-level requests” on page 153.

<CT_EMail> <server>smtp.server</server>

<sender>[email protected]</sender><receiver>[email protected]</receiver><subject>Here's your data.</subject>

<message>Table data supplied as attachment below. It is presented in csv format to be used by MS/Excel.</message><attachmenttitle>tabledata.csv</attachmenttitle><request id=”XMLID”><CT_Get><object>NT_Process</object><target>Primary:DCSQLSERVER:NT</target><userid>sysadmin</userid><password>xxxxxxxx</password></CT_Get></request></CT_EMail>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 145: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 145

SOAP Methods

CT_ExecuteExecutes a SOAP request that is stored in a file.

<filename> is required and specifies the filename that contains the SOAP request to be executed.The file must reside in the \html directory. On MVS, it must reside in RKANDATV.

<CT_Execute><filename>execute1.xml</filename></CT_Execute>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 146: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

146 Administering OMEGAMON Products: CandleNet Portal, V195

CT_Export Send the output from another CT SOAP method, such as CT_Get, to a defined file. (not available on OS/390)

<filename> The name of the file to contain the exported data. This is a required tag.Note: When inserting the filename tag into a quoted string literal of certain programming languages, such as C++, backslashes will need to be doubled.<warehouse/> Specifies that data is to be exported to the CNP Data Warehouse via ODBC.<filename> and <warehouse/> are mutually exclusive, but one must be supplied. <request> When specifying a second-level request, such as CT_Get, each sub-request must be included within a <request> </request> tag. Optional:An id=” “ element added to the <request> tag will generate a <request id=”XMLID“> element enclosing the corresponding response for that sub-request.See “Issuing second-level requests” on page 153.

<CT_Export> <filename>g:\exchange\excel\ntprocess$yymmddhhmmss$.htm</filename>

<request><attach>prefix.xsl</attach></request><request id="XMLID"><CT_Get><object>NT_Process</object><target>Primary:DCSQLSERVER:NT</target><userid>sysadmin</userid><password>xxxxxxxx</password></CT_Get></request><request><attach>suffix.xsl</attach></request></CT_Export>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 147: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 147

SOAP Methods

CT_Export (continued)

To the <filename> tag, you can add an optional date/timestamp variable. The variable is enclosed in $’s and can contain a combination of yy/mm/dd/hh/mm/ss (for year/month/day/hours/minutes/seconds). The date/timestamp attributes can be specified in any order, except that mm must be preceded by yy or hh to identify it as either month (after year) or minutes (after hours).

<filename>g:\exchange\excel\ntprocess$yymmdd$.htm</filename>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 148: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

148 Administering OMEGAMON Products: CandleNet Portal, V195

CT_GetReceive a group of XML objects or individual XML objects from any OMEGAMON platform agent. You can use this to obtain real time data.

Important: When issuing a CT_Get request against a particular agent type, the CMS where the SOAP server is running must be configured and seeded for that agent type.

<object> The name of the object to be retrieved. Required (by default, retrieves all the public elements of an object).<userid>The user ID to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password>The password to access the hub CMS. Required for CMS/hub logon validation. Optional:<target> Name of the agent. Caution: Defaults to "*ALL". Retrieves all available targets.<history>Y retrieves historical data if available. <results>PARSE retrieves status history event attributes. Only valid for Status_History object.Multiple: more than one may be specified.<attribute>Attribute name of object. This tag may be specified multiple times. <hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_Get> <hub>MVSPROD</hub><object> NT_System</object><target> Primary:DCSQLSERVER:NT </target>

<userid>sysadmin</userid>

<password></password>

<history>Y<history>

<attribute>Server_Name</attribute><attribute>Processor_Queue_Length</attribute>Note: When you specify an attribute in the attribute tags, leave out any non-alphanumber characters other than the underscore (_). For example, %_Total_User_Time would be entered as Total_User_Time.

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 149: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 149

SOAP Methods

CT_Get (continued)

<afilter> Returns rows meeting filter criteria, such as attribute; operator; value operators: EQ, NE, GE, GT, LE, LT, LIKE.Like pattern characters:'%' matches any single character. ' * ' matches one to many characters. Only supported for character attributes. Multiple afilters are only supported as conjuncts, for example, AND'ed together.

<afilter>Write_Time;GT;1020804</afilter><afilter>Write_Time;LT;1020805</afilter></CT_Get>

CT_RedirectReroute a SOAP request to another registered SOAP method outside of the domain of the OMEGAMON platform.

<request endpoint=" "> This is a required tag.The <request endpoint= " "> value must specify the target of the redirected SOAP request. The entire XML supplied as the value of the request element is sent to that endpoint.

When CT_Redirect is specified within a second- level request, such as, CT_Export, the <endpoint=" "> attribute is specified only within the CT_Redirect method. See “Issuing second-level requests” on page 153.

<CT_Redirect><request endpoint=\"http://services.xmethods.net:80/soap/servlet/rpcrouter\"><SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\"><SOAP-ENV:Body><ns1:getTemp xmlns:ns1=\"urn:xmethods-Temperature\"SOAP-ENV:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"><zipcode>93117</zipcode></ns1:getTemp></SOAP-ENV:Body></SOAP-ENV:Envelope></request></CT_Redirect>"

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 150: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

150 Administering OMEGAMON Products: CandleNet Portal, V195

CT_ResetSend an event reset (close event) to the OMEGAMON platform.

<name> The name of the situation. This is a required tag. <source> The source of the event (agent name or CMS name). The reset applies to all the active sources of the named alert if the source is not supplied.<item>Display item. Optional:<userid>The user ID used to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password> The password used to access the hub CMS. Required for CMS/hub validation.<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_Reset><hub>MVSPROD</hub><name>situation_from_CT </name>

<source> CT_supported_system </source>

<item>subsystem</item>

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_Reset>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 151: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 151

SOAP Methods

CT_ResurfaceResurface an acknowledged event in the OMEGAMON platform.

<name> The name of the situation. This is required.<source> The source of the event (agent name or CMS name). The resurface applies to all the active sources of the named alert if the source is not supplied.<item>Display item. Optional:<userid> The user ID used to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password>The password used to access the hub CMS. Required for CMS/hub validation.<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_Resurface><hub>MVSPROD</hub><name>situation_from_CT </name>

<source> CT_supported_system </source>

<item>subsystem</item>

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_Resurface>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 152: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

152 Administering OMEGAMON Products: CandleNet Portal, V195

CT_WTOSend a Universal Message into the OMEGAMON Platform.

<data>The message to be sent. This is required.<category> This tag isoptional/blank is the default.<severity>This isoptional/blank is the default.<userid> The user ID used to access the hub CMS. "nnn.nnn.nnn.nnn" is inserted if not provided. <password> The password used to access the hub CMS. Required for CMS/hub validation.<hub> Specifies the alias name of a remote hub that has been configured in the hubs list. The SOAP request is routed to this hub.

<CT_WTO><hub>MVSPROD</hub><data> This is Universal Message </data><category>Critical Messages </category>

<severity> High Severity </severity

<userid>sysadmin</userid>

<password>xxxxxxxx</password></CT_WTO>

Table 4. Predefined SOAP Methods (continued)

SOAP Method Supported Tags SOAP Tag Usage Examples

Page 153: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 153

SOAP Methods

Issuing second-level requestsSome second-level methods perform a particular function with the data retrieved, using imbedded lower-level methods. CT_EMail and CT_Export are second-level methods that perform this function.

The lower-level methods are:

� <CT_Get>

� <CT_Redirect>

� <attach>

� <insert>

<CT_Get> and <CT_Redirect> are used as described in “Predefined SOAP Methods” on page 140. <attach> allows you to load a file. The file must reside in the \candle\cms\html directory. <insert> allows you to load the imbedded text into the retrieved (output) data stream at a point corresponding to its position in the XML request.

Example of using second-level requests

The example that follows shows how a second-level request might be used. Running this XML would result in a file, named tabledata.htm, to be written with the data from file prefix.xls. This would be followed by the imbedded data inside the <insert> tag, followed by data from the NT_System object. Since an id=attribute is included with that request, the data tag <XML id=”NTDATA”> will be wrapped around that particular request data. Following that will be the response from a redirected SOAP request, followed by the insertion of more file data.

<CT_Export> <filename>tabledata.htm</filename> <request> <attach>prefix.xsl</attach> </request> <insert> <insertelement> <insertdata>This data has been inserted complements of CT SOAP server.</insertdata> </insertelement> </insert> <request id="NTDATA"> <CT_Get>

Page 154: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

154 Administering OMEGAMON Products: CandleNet Portal, V195

<userid>sysadmin</userid> <password></password> <object>NT_System</object> <target>*ALL</target> </CT_Get> </request> <request> <CT_Redirect endpoint="http://services.xmethods.net:80/soap/servlet/rpcrouter"> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <ns1:getTemp xmlns:ns1="urn:xmethods-Temperature" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <zipcode>93117</zipcode> </ns1:getTemp> </SOAP-ENV:Body> </SOAP-ENV:Envelope> </CT_Redirect> </request> <request> <attach>suffix.xsl</attach> </request></CT_Export>

Page 155: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 155

SOAP Methods

Sample CT_Get SOAP requestThe attached table shows a sample CT_Get SOAP request submitted and the response received.

Table 5. Example of CT_Get SOAP Request sent/data Received

SOAP Request sent to SOAP Endpoint,

http://esada.candle.com:19221/SOAP

SOAP Response from SOAP Endpoint, http://esada.candle.com:19221/SOAP

<?xml.version="1.0" encoding="UTF-8" standalone="no"?><SOAP-ENV:Envelope.xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><CT_GET xmlns:m="http://candle.com/Soap" SOAP-ENV:encodingStyle=""><CT_Get><Object>NT_System</Object><Source>Primary:ESADA:NT</Source></CT_Get></SOAP-ENV:Body></SOAP-ENV:Envelope>

<?xml version="1.0" encoding="ISO-8859-1"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body><SOAP-CHK:Success xmlns:SOAP-CHK = "http://soaptest1/soaptest/"><PARMS></PARMS><TABLE name="KNT.WTSYSTEM"><OBJECT>NT_System</OBJECT><DATA><ROW><Server_Name >Primary:ESADA:NT</Server_Name><Timestamp >1011127123323391</Timestamp><User_Name >SYSTEM</User_Name><Operating_System_Type >Windows_NT</Operating_System_Type><Operating_System_Version >4.0</Operating_System_Version><Network_Address >10.21.2.154</Network_Address><Number_of_Processors dt:dt="number">1</Number_of_Processors><Processor_Type dt:dt="number">586</Processor_Type><Page_Size dt:dt="number">4096</Page_Size><_Total_Privileged_Time dt:dt="number">1</_Total_Privileged_Time><_Total_Processor_Time dt:dt="number">7</_Total_Processor_Time>

Page 156: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

SOAP Methods

156 Administering OMEGAMON Products: CandleNet Portal, V195

<_Total_User_Time dt:dt="number">6</_Total_User_Time><Context_Switches_Sec dt:dt="number">1745</Context_Switches_Sec><File_Control_Bytes_Sec dt:dt="number">4500</File_Control_Bytes_Sec><File_Control_Operations_Sec dt:dt="number">98</File_Control_Operations_Sec><File_Data_Operations_Sec dt:dt="number">28</File_Data_Operations_Sec><File_Read_Bytes_Sec dt:dt="number">800</File_Read_Bytes_Sec><File_Read_Operations_Sec dt:dt="number">27</File_Read_Operations_Sec><File_Write_Bytes_Sec dt:dt="number">9772</File_Write_Bytes_Sec><File_Write_Operations_Sec dt:dt="number">1</File_Write_Operations_Sec><Processor_Queue_Length dt:dt="number">0</Processor_Queue_Length><System_Calls_Sec dt:dt="number">2368</System_Calls_Sec><System_Up_Time dt:dt="number">956388</System_Up_Time><Total_Interrupts_Sec dt:dt="number">1076</Total_Interrupts_Sec></ROW></DATA></TABLE></SOAP-CHK:Success></SOAP-ENV:Body></SOAP-ENV:Envelope>

Table 5. Example of CT_Get SOAP Request sent/data Received (continued)

SOAP Request sent to SOAP Endpoint,

http://esada.candle.com:19221/SOAP

SOAP Response from SOAP Endpoint, http://esada.candle.com:19221/SOAP

Page 157: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 157

Scenarios

Scenarios

OverviewHere are a few examples of how you might use OMEGAMON Web Services. You can use these examples as suggestions for creating your own applications.

Note: These scenarios do not describe the actual code that was used to develop them. To produce the charts and tables shown in these examples, you will need to develop your own scripts.

Generating daily business operation summaries and charts You can retrieve data from multiple agents, using the SOAP server against a live HUB, to generate daily business operation summaries. You can use the CT_EMail SOAP method to email these summaries to management. You might want to add an <insert> tag into CT_EMail. This tag would contain instructions for the preferred format for the summaries. Management can view these summaries at their desktops using Internet Explorer, thereby removing the need to install and launch the OMEGAMON platform user interface. Summaries provide an efficient and speedy look at problems that might have occurred during the night.

In addition to the general features you might add to tables and charts (see “Report contents” on page 161), charts and tables for these summaries might contain these features:

� Transaction volumes/response times and whether they are meeting service levels can be plotted with respect to resource trends and error conditions.

� Charts can be plotted over multiple segments, making them easier to view and to print.

� The X-axis can use a variable scale to show the prime shift in greater detail.

� Multiple objects/attributes can be plotted from multiple sources and exceptions can be correlated by time, providing focus on problem areas.

� A Status map can show the status of situations.

The graphics that follow depict sample Daily Business Operation summaries.

Page 158: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Scenarios

158 Administering OMEGAMON Products: CandleNet Portal, V195

Obtaining data snapshots and offline table and chartsUsing SOAP method CT_Get against a live HUB, you can obtain a data snapshot from multiple agents to produce charts and reports. You can also create an AF REXX script that requests a snapshot of its data.

In addition to the general features you might add to tables and charts (see “Report contents” on page 161), charts and tables for this type of request might contain these features:

� The chart can be plotted over multiple segments, making it easier to view and print.

� Clicking the attribute name in the legend box could display that attribute in the Y-axis and show its threshold value.

� The threshold value, when changed, can be used as the new threshold value.

The graphics that follow show sample charts/reports generated for this type of request.

Figure 8. Data Snapshot Chart and Table

Page 159: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 159

Scenarios

Figure 9. Data Snapshot Table

Sending alerts into an OMEGAMON platformUsing SOAP method CT_Alert, you can send a new alert into an OMEGAMON platform. For example, AF/Remote detects a problem on a Tandem system and generates an alert within an OMEGAMON platform. The OMEGAMON platform then displays alert information from the Tandem platform.

Collaborative automation using AF/RemoteYou can create an AF/REMOTE REXX application that calls JSCRIPT SOAP functions to forward any AF/Remote trapped message and display it on a Universal Message console. You can use AF/Remote scripts to trap and send any log messages, console messages, and so on, to CandleNet Command Center using SOAP methods.

You can create an application that provides these benefits:

� You can monitor devices, such as Tandem, by trapping VT100 messages and raising Universal Messages.

� You can send commands to AF/Remote monitored Telnet sessions and send replies back to those commands.

Page 160: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Scenarios

160 Administering OMEGAMON Products: CandleNet Portal, V195

� Source messages can be either excluded or included, based on any criteria using powerful regular expressions.

� A local log can keep audit information on the status of messages received and messages sent.

� A local log can keep information on the source HUB connection/retry status.

The graphics that follow show a sample Telnet session, a Universal Message console showing messages received, and a sample message log.

Figure 10. Universal Message Console Showing Messages Received

Figure 11. Message Log Details

Acknowledging an event within an OMEGAMON platformYou can acknowledge an event within an OMEGAMON platform. For example,

1. AF/Operator receives a raised situation from an OMEGAMON platform.

Page 161: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

OMEGAMON Web Services 161

Scenarios

2. AF/Operator pages a responsible party who in turn, sends back an acknowledgement.

3. AF/Operator forwards the acknowledgment of the alert to the OMEGAMON platform.

To accomplish this task, you would use Candle’s CT_Acknowledge SOAP method. This method gives you the ability to control events within an OMEGAMON platform based upon information obtained and detected by Candle’s automation solutions.

Report contentsYou can design a report to contain both a table and a chart view. You might want to add a Table/Chart button that allows you to toggle between the chart and the table view.

Chart view features

Charts can have specific features. For example, you could design charts to enable you to:

� view different types of charts, depending upon the data retrieved

� choose the Y-axis by selecting additional attributes from the drop-down attribute list

� change the title and instructions for the chart

� view the flyover text containing the name and value of the attribute plotted by placing your mouse over each plotted item

Table view features

Tables can have specific features. For example, you can design tables that allow you to:

� view the flyover text containing the name and value of the attribute plotted by placing your mouse over each plotted item

� modify the table by filtering the attributes that display

� remove attributes from a table by clicking the X button next to the attribute name

Page 162: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Scenarios

162 Administering OMEGAMON Products: CandleNet Portal, V195

Page 163: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Glossary 163

Glossary

A

administration mode Same as workspace administration mode.

AF/Operator A Candle console automation solution for the OS/390 and z/OS environments, designed to support data center operations, such as managing messages.

agent Software installed on systems you want to monitor that collects data about an operating system, subsystem, or application.

alert A warning message that appears at a console to indicate an event has occurred that may require intervention.

alert monitor A Candle agent that monitors and relays alert information to CandleNet Portal. Sources of alerts include message logs, system consoles, and network and system management products.

associate The relationship between a situation and a Navigator item that enables a light to go on and a sound to play for an open event. Predefined situations are associated automatically, as are situations created or edited through the Navigator item pop-up menu. Situations created in the CMW must be associated manually.

attribute A system or application element being monitored by the

OMEGAMON agent, such as Disk Name and Disk Read/Writes Per Second. An attribute can also be a field in an ODBC-compliant database.

attribute group A set of related attributes that can be combined in a data view or a situation. When you open the view or start the situation, CandleNet Portal retrieves data samples of the selected attributes. Each type of Candle agent has a set of attribute groups.

browser client The software installed on the CandleNet Portal Server system that is downloaded to your computer when you start CandleNet Portal browser mode.

C

Candle Technologies An integrated, layered architecture consisting of data access, communication, and presentation components that enable cross-platform operation and integration of data for systems management applications.

Candle web server A proprietary web server developed by Candle that is installed and configured automatically with the CandleNet Portal Server. You enter the URL of the Candle web server to start CandleNet Portal browser mode.

Page 164: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

164 Using OMEGAMON Products: CandleNet Portal, V195

CandleNet Command Center (CCC) A client-server implementation comprising a Candle Management Server, CandleNet Portal Server, CandleNet Portal client, and Candle monitoring agents that collect and distribute data to the CMS. The CandleNet Command Center has been renamed to OMEGAMON Platform.

CandleNet Portal Server The OMEGAMON Platform server you log on to. The CandleNet Portal Server connects to the hub CMS. It enables retrieval, manipulation and analysis of data from Candle managed systems.

chart A graphical view of data returned from a Candle agent. A data point is plotted for each attribute chosen and, for bar and pie charts, a data series for each row. Types of charts include pie, bar, plot and gauge.CICS

Customer Information Control System. IBM's main on-line transaction processing subsystem that runs under MVS, VSE, OS/2, OS/400, and AIX.

CICSplex A combination of two or more CICS regions working together to form one transaction processing subsystem, regardless of the location of the CICS regions.

class file A file containing Java object code for a single Java class.

class loader A Java component that is responsible for loading Java classes.

client/server An architecture in which the client (personal computer or workstation) is the requesting machine and the server is the supplying machine. Servers can be microcomputers, minicomputers or mainframes. The client provides the user interface and may perform application processing. A database server maintains the databases and processes requests from the client to extract data from or update the database. An application server provides additional business processing for the clients.

CMS Candle Management Server is the host data management component for the OMEGAMON Platform.

CMW Candle Management Workstation is the client component of a CandleNet Command Center environment. It is being replaced by the CandleNet Portal user interface, but is required for some advanced functions.

Configure History permission Your user ID must have Configure History permission to open the History Collection Configuration dialog for setting up history files and data roll off. If you do not have this permission, you will not see the menu item or tool for historical configuration.

CORBA Common Object Request Broker Architecture is an architecture and specification that facilitates communication among program components, or objects, in a network. The CandleNet Portal Server is a CORBA implementation.

Page 165: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Glossary 165

critical state The indication that a situation associated with the Navigator item is in an unacceptable state and that you must take corrective action. The critical state is represented by the color red.

CT Service Console An interface accessible through the Candle integral web server (port 1920) that allows for remote product diagnostics and configuration using an industry-standard browser.

Custom Navigator Views permission Your user ID has a Modify checkbox for the Custom Navigator Views feature. This permission must be enabled or you will not be able to open the Navigator view editor to view and maintain Navigator views.

detailed attribute name The name CandleNet Portal uses in formulas, expert advice, take action commands, and headers and footers when referencing a Candle attribute. In the Properties and Situation editors, you click Show Formula, then check Show detailed formula to see the detailed attribute name.

display item An attribute designated to further qualify a situation. The value displays in the event workspace and in the message log and event console views. You can select a display item when building a situation with a multiple row attribute group. For example, a display item of an attribute showing the disk name enables you to see which disk made the situation true. More

importantly, even after opening the event, the situation continues to test the other rows for display item values that meet the condition.

distribution The managed systems on which the situation is running.

DLL Dynamic Link Library is a composite of one or more executable objects, bound together by a linking procedure, and loaded at run time.

DMZ Demilitarized Zone is the area of a Web application that enables the company to host Internet services without allowing unauthorized access.

DSN Data Source Name. The name is stored in the database server and enables you to retrieve information from the database through ODBC. The DSN includes such information as the database name, database driver, user ID and password.

E

EIB Enterprise Information Base is a database used by the CMW to store situations, user definitions and managed object definitions.

endcode You assign endcodes in a policy as you connect one activity to another. The encode indicates the result of this activity that will trigger the next activity.

event An action or some occurrence, such as running out of memory or

Page 166: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

166 Using OMEGAMON Products: CandleNet Portal, V195

completing a transaction, that can be detected by a situation. The event causes the situation to become true and an alert to be issued.

event indicator The colored icon that displays over a Navigator item when an event opens for a situation.

event item A Navigator item that shows when you open the event workspace for a true situation (by selecting it from the event flyover listing or from the event console popup menu).

event sound The sound file that plays when an event opens. Sound is set in the Situation editor when the situation is associated with a Navigator item and can be different for different Navigator items.

F

Filter Criteria Limits the amount of information returned to the data view in response to a query. You can apply a pre-filter to the query to collect only certain data, or apply a post-filter to the view properties to show only certain data from what was collected.

G

georeferenced map A special type of graphic that has built-in knowledge of latitude and longitude and can be zoomed into and out of quickly. CandleNet Portal uses proprietary .IVL

files generated with the map-rendering component. These files cannot be opened or saved in a graphic editor.

H

historical data management The procedures applied to short-term binary history files that perform roll off to either a data warehouse or to delimited text files (krarloff utility on UNIX or Windows; KBDXTRA on OS/390 persistent data store), and delete entries in the short-term history files over 24 hours old to make room for new entries.

hot standby A redundant Candle Management Server that, if the primary or hub CMS should fail, assumes the responsibilities of the failed CMS.

hub 1) A central host system that collects the status of situations running on your systems. 2) The CMS that has been elected to act as the focal point to which all CandleNet Portal Servers connect. A remote CMS passes its collected data to the hub to be made available to clients, creating an enterprise-wide view.

I

interval The number of seconds that have elapsed between one sample and the next. A sample is the data that the product collects for the server.

Page 167: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Glossary 167

ior Interoperable Object Reference connects clients to the CNP Server. The IOR identifies a remote object, including such information as name, capabilities and how to contact. In the URL you may have an ior reference. This is because it goes through the web server and CandleNet Portal Server uses it to tell the client which ior to fetch. Once it does that, it extracts the host and port and tells the client where to route the request.

M

managed object An icon created in the CMW from a managed object template that represents resources you monitor with situations. In OMEGAMON DE, managed objects are converted to items in the Navigator Business view.

managed system A particular operating system, subsystem, or application in your enterprise that CandleNet Portal is monitoring with a Candle agent.

managed system list A named list of managed systems of the same type. You can see and select a managed system list when you distribute a situation or policy, edit a query specification, or assign managed systems to Navigator items in custom Navigator views. Example: A list of Linux managed systems for a geographic region named LINUX_LONDON.

Managed System Lists permission If the Edit menu has no Managed System Lists item, your user ID does not

have View permission for Managed System Lists. If you can open the editor, but the tools are disabled after you select a managed system type or list, your user ID does not have Modify permission for Managed System Lists.

middleware Software that enables the exchange of information between components in a distributed computing environment. IBM WebSphere MQ is an example of middleware.

monitor interval A specified time, scalable to seconds, minutes, hours, or days, for how often the CMS checks to see if a situation has become true. The minimum monitor interval is 30 seconds; the default is 15 minutes.

MVS Multiple Virtual Storage, the operating system used on IBM mainframes since 1974. Newer versions are OS/390 and z/OS.

N

NAT Network Address Translation is a scheme used by LANs to establish an internal and external set of IP addresses. Internal IP addresses are kept private and must be translated to and from the external address(es) for outbound and inbound communications. NAT is often used in firewall configurations.

Navigator The left pane of the CandleNet Portal window. The Navigator Physical view shows your network enterprise as a physical hierarchy of systems grouped by

Page 168: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

168 Using OMEGAMON Products: CandleNet Portal, V195

platform. OMEGAMON DE users can also create other views to create logical hierarchies grouped as you specify, such as by department or function.

O

ODBC Open DataBase Connectivity, a standard for accessing different database systems. The Queries editor enables you to write custom SQL queries for creating views that retrieve data from ODBC-compliant databases.

OMEGAMON Candle monitoring agent. The agent process probes a managed system for data and sends information back to CandleNet Portal formatted into table and chart views.

OMEGAMON DE Candle OMEGAMON Dashboard Edition, which includes all the features of CandleNet Portal included with OMEGAMON XE, plus application integration components.

OMEGAMON Platform A client-server implementation comprising a Candle Management Server, an application server known as the CandleNet Portal Server, the CandleNet Portal client, and Candle monitoring agents that collect and distribute data to a CMS.

OMEGAMON Web Services An open standards-based interface to the OMEGAMON platform using SOAP requests. Any OMEGAMON XE monitor can be dynamically queried, so

performance and availability data can be processed by other applications.

OMEGAMON XE Candle OMEGAMON Extended Edition powered by CandleNet Portal. The monitoring agent is a Candle process that probes a managed system for data and sends information back to the CandleNet Portal console, which formats it into table and chart views.

OS/390 IBM's operating system for mainframe computers that has the ability to manage large amounts of memory, direct access storage, and data.

P

platform The operating system the managed system is using, such as OS/390 and Linux. The Navigator physical mapping places the platform level under the enterprise level.

policy A set of automated system processes that can perform actions, schedule work for users, or automate manual tasks. It comprises a series of automated steps, called activities, whose order of execution you control.

presentation files Installed with the CandleNet Portal Server, presentation.dat and presentation.idx store the workspace definitions, link definitions, and terminal emulator scripts.

product code The three-letter code Candle uses to identify the product

Page 169: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Glossary 169

component. For example, the product code for OMEGAMON XE for WebSphere Application Server is KWE.

Properties editor A multi-tabbed dialog for specifying the properties of the individual views that make up a workspace, as well as the general workspace properties.

pure event A pure event is one that occurs automatically, such as when a paper out condition occurs on the printer or when a new log entry is written. Situations written to notify you of pure events remain true until they are manually closed or automatically closed by an UNTIL clause.

Q

Query permissions If you do not see the Queries tool, your user ID does not have View or Modify Query permissions. If you can see the tool but it is disabled, your user ID does not have Workspace Author Mode permission. If you can open the Query editor but the tools are disabled, your user ID does not have Modify Query permission.

S

sample The data that the Candle agent collects for the server instance. The interval is the time between data samplings.

sampled event Sampled events happen when a situation becomes true. Situations sample data at regular intervals. When the situation is true, it opens an event, which gets closed automatically when the situation goes back to false (or you can close it manually).

situation A set of conditions that, when met, creates an event. A condition consists of an attribute, an operator such as greater than or equal to, and a value. It can be read as, “If - system condition - compared to - value - is true”. An example of a situation is: IF - CPU usage - GT - 90% - TRUE. The expression “CPU usage GT 90%” is the situation condition.

small icon Small icons are used in conjunction with the graphic view stylesheets. The icon image should be no taller than 16 x 16 pixels with a 2-pixel top and bottom margin, for a total of 20 x 20 pixels. The 2-pixel margins ensure that the icon does not touch the one above or below it.

SNMP Simple Network Management Protocol. A software protocol to facilitate communications between different types of networks. CandleNet Portal uses SNMP messaging to discover the devices on your network and their availability.

SOAP Single Object Access Protocol is an XML-based protocol that enables applications to converse with each other and exchange data over the Internet, regardless of platform.

Page 170: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

170 Using OMEGAMON Products: CandleNet Portal, V195

sound WAV file that plays whenever the situation becomes true for this Navigator item. Sound is assigned to the Navigator item for a situation in the same way a state is assigned.

SQL Structured Query Language is a programming language for getting information from and updating a database. The CandleNet Portal Queries editor enables you to write SQL queries to ODBC data sources for retrieval and display in table and chart views.

Start/Stop Policy permission To start or stop a policy, your user ID must have Start/Stop Policy permission. If you can see the Workflows tool, but it is disabled, your user ID does not have Workspace Author Mode permission.

state The severity of the event: critical, warning, or informational. Indicated by a colored event indicator, state is set in the Situation editor and can be different for different Navigator items.

status The true or false condition of a situation.

subnetwork A configuration whereby a single IP network address is split up so it can be used on several interconnected local networks. Subnetworking is a local configuration; outside it appears as a single IP network.

symbol Represents a variable that can be added to header or footer text for data views, expert advice text, or query specification. The detailed attribute name is enclosed in dollar signs, such as $ORGINNODE$, and resolves to the

attribute's value. For CMS queries, EQ $NODE$ specifies from which managed systems to retrieve data. For queries to be used in link target workspaces, you can create symbols for attributes using the $symbolname$ format.

T

TCP/IP Transmission Control Protocol/Internet Protocol. An open, portable communications protocol.

Telnet A terminal emulation program used on TCP/IP networks. You can start a Telnet session with another system and enter commands that execute on the other system. A valid user ID and password are required.

TSO Time Sharing Option.

UDB IBM's DB2 Universal DataBase is a relational database management system. A UDB database is installed on the same system as the CandleNet Portal Server and stores queries, user IDs and custom Navigator views.

V

Value of expression A function in a situation condition, query specification, or data view filter or threshold that uses the raw value of an attribute. A value can be a number, text string, attribute, or modified attribute. Use this function with any operator.

Page 171: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

Glossary 171

view A windowpane, or frame, in a workspace. It may contain data from an agent in a chart or table, or it may contain a terminal session or browser, for example. A view can be split into two separate, autonomous views.

View and Modify Situations permissions Your user ID must have View and Modify Situation and Workspace Author Mode permissions to open the Situation editor for creating and maintaining situations.

View Policy permission If the Workflows tool is disabled, your user ID does not have View Policy permission or Workspace Author Mode permission, or OMEGAMON DE was not enabled during installation.

W

WAV Waveform audio format for storing sound in files, developed jointly by Microsoft and IBM.

wildcard An * (asterisk) used to represent any characters that may follow or precede those entered, such as Sys* to find System and SysTray. Used in formulas with the VALUE function or MISSING function (in the Missing Task List). Used also with the SCAN function, but at the beginning of the text as in *Z to find markZ and typeZ.

workspace The viewing area of the CandleNet Portal window, excluding the Navigator. Each workspace comprises one or more views. Every Navigator

item has its own default workspace and may have multiple workspaces.

workspace administration mode Set in the Administer Users dialog, this mode automatically shares the changes you make to workspaces, links, and terminal session scripts with all users logged onto the same CandleNet Portal Server.

workspace author mode permission Your user ID requires Workspace Author Mode permission to create and maintain workspaces, including links. If the main toolbar is disabled (except New Window, Refresh, Back, Forward and Stop), as well as the split and remove tools on the view toolbar, you do not have this permission.

Page 172: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

172 Using OMEGAMON Products: CandleNet Portal, V195

Page 173: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

173

Index

Numerics1920

disable port 94

AAdminister Users dialog 75administration

mode 68, 77SYSADMIN user ID 68user 70, 71

Adobe portable document format 13AF/REMOTE REXX application 159author mode 78author mode eligible 77

Bbackup CNP server 100banner in browser mode 48batch file

CandleSOAPClient 138migrate-cmw-navigator 110migrate-export 102migrate-import 102migrate-new-users 108

browser clientcomponent diagram 33

browser mode 32, 35add company logo to banner 48clear JAR cache 92file packages and cookies 45help not displaying in 92IE security settings 47logon 46setup overview 40uninstall procedure 92Windows 2000 permissions 47workspace switch delay 55

workspace URL parameter 55browser view

animated GIF parameter 54troubleshooting parameter 54

CCandle Management Server 31Candle web server 31Candle Web site 12CandleNet Portal

browser mode 35browser mode logon 46description 34desktop mode 35logon ID 40

CandleNet Portal Serverconnect to a different 49console mode 90environment variables 58failed connection 84replicate 100status alerts 86turn on trace 97Windows event viewer 89

chart view page size 54clear JAR cache 92client

global parameters 53logon error messages 84set trace options 96using SOAP 135

CMSinitial migration variable 60ping interval variable 59

CMWalert indicators 114CNP conceptural differences 113

Page 174: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

174 Administering OMEGAMON Products: CandleNet Portal, V195

configure history 131functional comparison 116managed objects 114, 122, 129migration considerations 107migration to CandleNet Portal 106OMEGAVIEW Zoom 125policies 130policy microscope 123reports 128situations 129situations in CandleNet Portal 129user ID 128

CMWENV file 58cmwras1.log 97CNPS database

DB2 UDB component 31error messages 89migrate 101

communicationsheartbeat interval 55HTTP proxy server 53pipeline factor 55

console mode 58, 90console mode for 90cookie 45CT Service Console 93CT_* SOAP methods 140

Ddatabase 31

copy presentation 101DB2 UDB 31error messages 89migrate CNPS 101ODBC environment variable 61

DB2 UDBuser ID 90

deletemanaged systems 131user ID 73

desktop mode 32, 35connect to another CNP Server 49

databus parameter 56dialog

Administer Users - Applications 78Administer Users - Navigator Views 79Administer Users - Permissions 75CandleNet Portal Service License 88Create Query 61Edit CandleNet Portal Browser Parm 62Edit CandleNet Portal Parm 53Java(TM) Plug-in Control Panel 92Logon 51, 84Trace Options 96

differences between CandleNet Portal and CMW 112

digit grouping symbol 98documentation set information 10

EEIB Change Log 126enable OMEGAMON DE 87environment variables 58

CMS ping interval 59CNP topology start retries 59CNPS initialization delay 59CNPS log 61CNPS recycle delay 58console mode verbose 58initial migration 60migration log 61ODBC data source 61short term history break point 61

error messageCandleNet Portal client cannot find

CandleNet Portal Server 85CandleNet Portal Server is not

reconnecting 87Failed connection to CandleNet Portal

Server 84license failure 52Reconnect Authorization Failed 87Unable to process logon request 85User authorization has failed 85

Page 175: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

175

eventindicators in CMW 114user authority 75

exportCNPS database 102seed data 116

Gglobal parameters 53graphic in banner 48graphic view 114

Hhelp not displaying 92history

bars in the CMW 126configuration in the CMW 131data collection 36environment variable 61user authority 76workspace parameter 54

Host-on-Demand 42hot standby 116hub

lookup interval 60switch 118

IIBM

DB2 Universal Database 31Host-on-Demand 44

imagebrowser view animated GIFs 54

importCNPS database 102seed data 116

initialization delay variable 59integral web server

description 31disable 94

Internet ExplorerOptions - Advanced 44

Options - Security 47ior URL 56

JJava Runtime Environment

adjustments before installing 44Java Runtime Environment (JRE) 42

Kkfwras1.log 97KMWENV file 60

LLaunchPad 120license 52log

CNPS variable 61turn on client trace 96turn on CNP Server trace 97

logo 48logon

browser mode 46error messages 84license limit 52user ID 40

logon error messages 134

MManage Candle Services

create another CNP desktop instance 49global parameters 53

managed objects 107, 114, 122, 129managed system

removing from the Navigator 131unknown state 122view applications authority 78

managed system listCMW and CandleNet Portal 123, 131user authority 76

messageCandleNet Portal client cannot find... 85

Page 176: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

176 Administering OMEGAMON Products: CandleNet Portal, V195

CNP Server application 89CNP Server has lost contact... 86CNP Server is still being initialized... 86Failed connection to... 84Unable to process logon... 85User authorization has failed 85

migrate-cmw-navigator script 110migrate-export script 102migrate-new-users script 108migration, CMW

log variable 61managed objects 110to CandleNet Portal 106user IDs 108using MSSQL Enterprise Manager 103

migration, CNP Servercopy CNPS database 101copy presentation database 101prerequisites 100

modesdesktop 35

MSSQL Enterprise Manager 103

NNavigator

adding platforms 63remove managed systems from 131topology variable 59

Navigator viewsbusiness 129user assignment 79user authority 75

OODBC data source variable 61OMEGAMON DE

enable 87features 29

OMEGAMON Platformcomponent diagram 33data flow 32description 31

OMEGAMON Web Servicescommand line utility 137introduction 133predefined SOAP methods 140report contents 161sample CT_Get SOAP request 155scenarios 157second-level requests 153SOAP client 135SOAP description and URLs 134SOAP requests as system commands 139starting the client 136user IDs 135using Internet Explorer 136what is it 134

OMEGAMON XEdescription 25features 26

OMEGAVIEW Zoom 125osnames 63

Pparameter

active terminal sessions 54databus for desktop mode on an external

web server 56editing global 53encoding code set 55event sound pause 55heartbeat interval 55HTTP proxy server 53mouse drag sensitivity 55pipeline factor 55terminal emulator hostname 54terminal emulator port 54terminal emulator type 54terminal script maximum 54trace calls threaded 56trace client identifier 56trace filename 56trace local or remote 56trace option 56

Page 177: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

177

trace thread priority 56view page size 54Windows task bar 55workspace history 54workspace switch delay 55workspace URLs 55

password 40, 52, 70PDF files, adding annotations 14performing administrative tasks 67permissions, user 75ping interval 59policy

CMW and CandleNet Portal 130microscope 123SOAP requests 139user authority 76

popup blocker 92presentation database 101printing problems 13process

KfwCMWServer 58KfwServices 60send commands to a CT 93

Properties editordigit grouping symbol 98

proxyHTTP server parameter 53

Qquery

digit grouping symbol 98user authority 76

Rregional settings 98replicate CNP Server environment 100reports 128

Sscript

CandleSOAPClient 138

migrate-cmw-navigator 110migrate-export 102migrate-import 102migrate-new-users 108terminal maximum 54

securityWindows local 90

situationCMW differences 113, 129CMW migration considerations 107CMW templates 121digit grouping symbol 98editor topology variable 59SOAP requests 139sound parameter 55user authority 77

SOAPtutorial URL 134

SOAP methodCT_Acknowledge 141, 160CT_Activate 140CT_Alert 142, 159CT_Deactivate 143CT_EMail 144CT_Execute 145CT_Export 146CT_Get 148, 155CT_Redirect 149CT_Reset 150CT_Resurface 151CT_WTO 152

switch hubs 118SYSADMIN logon ID 40, 68system administrator access 23

Ttable view page size 54take action

for SOAP requests 139user authority 75

terminal viewOMEGAVIEW Zoom 125

Page 178: Administering OMEGAMON Products - IBMpublib.boulder.ibm.com/tividd/td/ITCNetPortallnk/GC32-9180-00/en_US/... · Administering OMEGAMON Products: CandleNet Portal describes the support

178 Administering OMEGAMON Products: CandleNet Portal, V195

parameters 54trace

parameters 56setting a client 96

troubleshooting 90browser mode 92browser view parameter 54CT Service Console for 93java applets 42, 44Java exception 47logon error messages 84setting a trace 96trace parameters 56variable - console mode verbose 58

UUniversal Agent 27Universal Message Console 120unknown state 122URL 45

Candle web server 94workspace parameter 55workspace, disable 61

user administration 68adding a user 71assigning permissions 75authority 77dialog 75editing a user 72removing a user 73

user IDdefault 69failed user authorization 85license failure 52migration of CMW 107, 128OMEGAMON Web Services 135password 52, 70SYSADMIN 68sysadmin 40Windows Users Group 47

Users Group priveleges 47

Vvalidate user 52, 70views

chart 26table 26

Wweb server

Candle integral 31databus parameter to specify external 56diable Candle 94

WebSphere MQ Configurationuser authority 78

what’s new 17wildcard predicates 120Windows

Local Security Settings 90regional settings 98user ID 90Users group 47versions supported 36

work groups and work lists 123Workflows

enable OMEGAMON DE 87user authority 76

workspaceadministration mode 68author mode 77, 78author mode eligible 77disable URLs 61history parameter 54