IBM Tivoli Monitoring for Applications: Siebel...

IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications

User’s GuideVersion 5.1.0

SC23-4819-00

��

NoteBefore using this information and the product it supports, read the information in Appendix I, “Notices” on page 131.

First Edition (September 2002)

This edition applies to version 5.1.0 of IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications and toall subsequent releases and modifications until otherwise indicated in new editions.

Contents

About this guide . . . . . . . . . . . vWho should read this guide . . . . . . . . . vWhat this guide contains . . . . . . . . . . vPublications . . . . . . . . . . . . . . v

IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications library . . . . . . . vRelated Publications . . . . . . . . . . viAccessing softcopy publications . . . . . . viiOrdering Publications . . . . . . . . . . viiProviding Feedback about Publications . . . . vii

Accessibility . . . . . . . . . . . . . . viiiContacting Customer Support . . . . . . . . viiiConventions used in this book. . . . . . . . viii

Typeface conventions . . . . . . . . . . viiiTerminology . . . . . . . . . . . . . viiiOperating system-dependent variables and paths ix

Chapter 1. Overview . . . . . . . . . 1Tivoli Administrators . . . . . . . . . . . 1Authorization Roles . . . . . . . . . . . . 1Siebel Managed Resources and Endpoints . . . . 2User Interface Options . . . . . . . . . . . 2

Chapter 2. Getting startedquick-reference guide . . . . . . . . . 3

Chapter 3. Setting Up IBM TivoliMonitoring for Applications, Version5.1.0: Siebel eBusiness Applications . . 5Starting the Tivoli environment . . . . . . . . 5Setting authorization roles . . . . . . . . . . 7Discovering Siebel eBusiness Applications resources 9Distribute resource models . . . . . . . . . 11

Chapter 4. Working with IBM TivoliMonitoring for Applications: SiebeleBusiness Applications . . . . . . . 15Checking Siebel eBusiness Applications resourcesstatus . . . . . . . . . . . . . . . . 16Viewing Siebel resource properties. . . . . . . 17Starting or stopping a resource . . . . . . . . 20Managing Siebel Logs . . . . . . . . . . . 21Managing Tivoli logs . . . . . . . . . . . 23Editing Tivoli Siebel server object parameters . . . 24Creating Siebel objects . . . . . . . . . . . 24

Chapter 5. Working with tasks and jobs 29Running tasks . . . . . . . . . . . . . 30Customizing a task . . . . . . . . . . . . 33Creating jobs . . . . . . . . . . . . . . 35Running jobs . . . . . . . . . . . . . . 38Scheduling jobs . . . . . . . . . . . . . 39

Chapter 6. Viewing resource modelresults with the IBM Tivoli MonitoringWeb Health Console . . . . . . . . . 45Understanding resource health . . . . . . . . 45Connecting the IBM Tivoli Monitoring Web HealthConsole. . . . . . . . . . . . . . . . 46

Chapter 7. Enabling Tivoli EnterpriseData Warehouse. . . . . . . . . . . 47Overview . . . . . . . . . . . . . . . 47

Control server . . . . . . . . . . . . 47Central data warehouse . . . . . . . . . 48Data marts . . . . . . . . . . . . . 48Report interface . . . . . . . . . . . . 48

Working with users and user groups . . . . . . 49About users and user groups . . . . . . . 49The Tivoli Enterprise Data Warehouse roles. . . 49

Creating an IBM Console user . . . . . . . . 50Assigning roles to a user . . . . . . . . . . 50Creating a user group . . . . . . . . . . . 51Assigning users to a user group . . . . . . . 51Assigning user groups to a data mart. . . . . . 52Managing Tivoli Enterprise Data Warehouse reports 52Running reports . . . . . . . . . . . . . 54Scheduling reports to run automatically . . . . . 55Modifying default settings for reports . . . . . 55Creating reports . . . . . . . . . . . . . 56

Appendix A. Authorization roles quickreference. . . . . . . . . . . . . . 59

Appendix B. Task quick reference . . . 61Siebel Event Tasks task library . . . . . . . . 61Siebel Operational Tasks task library . . . . . . 61Siebel Utility Tasks task library . . . . . . . . 62

Appendix C. Setting up TivoliEnterprise Console . . . . . . . . . 63Overview of Tivoli Enterprise Console . . . . . 63Configuring event server . . . . . . . . . . 64Installing logfile adapter message formats . . . . 67Listings of event classes and rules . . . . . . . 69

Siebel Server Logfile events . . . . . . . . 69Connection Broker Logfile events . . . . . . 70Resource models events . . . . . . . . . 70Siebel Tivoli Enterprise Console rules. . . . . 71

Appendix D. Integrating with TivoliBusiness Systems Manager . . . . . 73Understanding Tivoli Business Systems Manager . . 73Discovering resources for Tivoli Business SystemsManager . . . . . . . . . . . . . . . 74Working with Tivoli Business Systems Manager . . 75

iii

Uninstalling IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications integration from TivoliBusiness Systems Manager . . . . . . . . . 76

Appendix E. Using IBM TivoliMonitoring . . . . . . . . . . . . . 79Setting up IBM Tivoli Monitoring . . . . . . . 79

Creating profile managers and profiles . . . . 80Subscribing resources to profile managers . . . 82Adding default resource models to profiles . . . 83Adding custom resource models to profiles. . . 84Distributing profiles from the desktop . . . . 85Distributing profiles using MDist2 . . . . . . 87Rerunning failed profile distributions. . . . . 90

Working with IBM Tivoli Monitoring . . . . . . 91Modifying indications . . . . . . . . . . 91Adding or removing a built-in action . . . . . 93Editing a built-in action . . . . . . . . . 95Specifying tasks for an indication . . . . . . 96Sending a notice to administrators when an eventoccurs . . . . . . . . . . . . . . . 97Modifying parameters . . . . . . . . . . 99Creating scheduling rules . . . . . . . . 100Modifying the scheduling monitoring period 102Modifying data logging settings . . . . . . 103Managing profiles and resource models atendpoints . . . . . . . . . . . . . 105Managing IBM Tivoli monitoring gateways . . 106Determining which resource models are runningon endpoints . . . . . . . . . . . . 106Viewing resource model results with the IBMTivoli Web Health Console . . . . . . . . 107

Appendix F. Problem determination 109Resource models . . . . . . . . . . . . 109

A resource model fails to start but no event isreported to Tivoli Enterprise Console . . . . 109

Tasks . . . . . . . . . . . . . . . . 109The Archive_Siebel_Logs task output shows agreater log archive size than the size reportedby Windows. . . . . . . . . . . . . 109Errors occur when creating an object . . . . 109The gateway and server object icons do notchange when the Stop_Connection_Broker taskis run. . . . . . . . . . . . . . . . 110The Siebel Discovery task or job returns anexception after running the Tivoli odstatcommand. . . . . . . . . . . . . . 110

Appendix G. Messages . . . . . . . 111

Appendix H. Accessibility . . . . . . 129Using Assistive Technologies . . . . . . . . 129Magnifying What is Displayed on the Screen . . . 129Documentation in Accessible Formats . . . . . 129Using Alternative Text . . . . . . . . . . 130

Appendix I. Notices . . . . . . . . . 131Trademarks . . . . . . . . . . . . . . 133

Index . . . . . . . . . . . . . . . 135

iv IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: User’s Guide

About this guide

IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications provides theability to manage and monitor Siebel resources. The IBM Tivoli Monitoring forApplications Version 5.1.0: Siebel eBusiness Applications Reference Guide describes indetail the tasks, monitors, and commands used in the procedures in this guide.

Who should read this guideThis guide is for system administrators who monitor and manage a Siebelenvironment using IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications. This guide requires administrator-level knowledge of Tivolimanagement software, UNIX® and Windows® operating systems, databases, andSiebel products.

What this guide containsThis book contains the following chapters:v Chapter 1, “Overview” on page 1v Chapter 2, “Getting started quick-reference guide” on page 3v Chapter 3, “Setting Up IBM Tivoli Monitoring for Applications, Version 5.1.0:

Siebel eBusiness Applications” on page 5v Chapter 4, “Working with IBM Tivoli Monitoring for Applications: Siebel

eBusiness Applications” on page 15v Chapter 5, “Working with tasks and jobs” on page 29v Chapter 6, “Viewing resource model results with the IBM Tivoli Monitoring Web

Health Console” on page 45v Chapter 7, “Enabling Tivoli Enterprise Data Warehouse” on page 47v Appendix A, “Authorization roles quick reference” on page 59v Appendix B, “Task quick reference” on page 61v Appendix D, “Integrating with Tivoli Business Systems Manager” on page 73v Appendix E, “Using IBM Tivoli Monitoring” on page 79v Appendix F, “Problem determination” on page 109v Appendix G, “Messages” on page 111v Appendix H, “Accessibility” on page 129v Appendix I, “Notices” on page 131

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Applications, Version5.1.0: Siebel eBusiness Applications library and any other related documents. It alsodescribes how to access Tivoli publications online, how to order Tivolipublications, and how to submit comments on Tivoli publications.

IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications library

The following documents are available in the IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications library:

v

v IBM Tivoli Monitoring for Applications Version 5.1.0: Installation and Setup Guide,GC23-4810Describes how to install and deploy the IBM Tivoli Monitoring for Applicationsproduct.

v IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness ApplicationUser’s Guide, SC23-4819Describes how to use IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications.

v IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness ApplicationsReference Guide, SC23-4818Provides information about resource models and task libraries for the IBM TivoliMonitoring for Applications, Version 5.1.0: Siebel eBusiness Applications.

v IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness ApplicationsLimitations and Workarounds Supplement, SC23-4817Provides the latest information about known product limitations andworkarounds. To ensure that the information is the latest available, thisdocument is provided only on the Web, where it is updated on a regular basis.You can access the Limitations and Workarounds document through the IBMTivoli Monitoring for Applications: Siebel eBusiness Applications link on theTivoli Information Center Web site:

http://www.tivoli.com/support/public/Prodman/public_manuals/td/ \TD_PROD_LIST.html

v IBM Tivoli Monitoring for Applications, Version 5.1.0 Release Notes, GI11-0941Describes product features and provides information about the latest changes tothe installation requirements and procedures. The release notes also describeknown limitations related to installation and explain how to work around eachlimitation.

Related PublicationsThe following documents also provide useful information related to IBM TivoliMonitoring for Applications: Siebel eBusiness Applications:v Tivoli Framework User’s Guide

v Tivoli Framework Planning and Installation Guide

v Tivoli Framework Reference Manual

v Tivoli Enterprise Console Rule Builder’s Guide

v Tivoli Enterprise Console User’s Guide

v Tivoli Enterprise Console Reference Manual

v Tivoli Enterprise Console Event Integration Facility Guide

v Tivoli Enterprise Console Adapters Guide

v Tivoli Enterprise Data Warehouse User’s Guide

v IBM Tivoli Monitoring User’s Guide

v IBM Tivoli Monitoring Reference Guide

v Tivoli Business Systems Manager product documentation

The Tivoli Glossary includes definitions for many of the technical terms related toTivoli software. The Tivoli Glossary is available, in English only, at the followingWeb site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm

vi IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: User’s Guide

Accessing softcopy publicationsPublications in the product libraries are included in PDF or HTML formats, orboth, on the product CD. To access them publications using a Web browser, openthe infocenter.html file, which is located in the appropriate publications directoryon the product CD.

When IBM publishes an updated version of one or more online or hardcopypublications, they are posted to the Tivoli Information Center. You can accessupdated publications in the Tivoli Information Center from the following TivoliCustomer Support Web site:

http://www.tivoli.com/support/documents/

The Tivoli Information Center contains the most recent version of the books in theproduct library in PDF or HTML formats, or both. Translated documents are alsoavailable for some products.

The Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers aguide to support services (the Customer Support Handbook); frequently askedquestions (FAQs); and technical information, including release notes, user’s guides,redbooks, and white papers. You can access Tivoli publications online athttp://www.tivoli.com/support/documents/. The documentation for someproducts is available in PDF and HTML formats. Translated documents are alsoavailable for some products.

To access most of the documentation, you need an ID and a password. To obtainan ID for use on the support Web site, go tohttp://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html formore information about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” on page vii for moreinformation about obtaining Tivoli technical documentation.

Ordering Publicationspage are printed on the paper that you are using. You can order hardcopypublications online from the IBM Publications Center Website:

http://www.elink.ibmlink.ibm.c om/public/applications/publications/ \cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

See the following Web site for a list of telephone numbers in other countries:

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback about PublicationsIf you have comments or suggestions about Tivoli products and documentation,send an e-mail to [email protected] or complete the customer feedback survey atsurvey at http://www.tivoli.com/support/survey/

About this guide vii

http://www.tivoli.com/support/documents/

http://www.tivoli.com/support/

http://www.tivoli.com/support/documents

http://www.tivoli.com/support/getting/

http://www.tivoli.com/support/smb/index.html

http://www.ibm.com/shop/publications/order

http://www.ibm.com/shop/publications/order

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

AccessibilityAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate features of the graphical userinterface. See Appendix H, “Accessibility” on page 129 for additional information.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact Customer Support.See the Tivoli Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting support

Conventions used in this bookThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths.

Typeface conventionsThis book uses the following typeface conventions.

Bold Lowercase and mixed-case commands, command options, file and pathnames, and flags that appear within text appear like this, in bold type.Graphical user interface elements and names of keys also appear like this,in bold type.

Italic Variables, values you must provide, new terms, and words and phrasesthat are emphasized appear like this, in italic type.

MonospaceCommands, command options, and flags that appear on a separate line,code examples, output, and message text appear like this, in monospacetype.

Names of files and directories, text strings you must type when theyappear within text, names of Java methods and classes, and HTML andXML tags also appear like this, in monospace type.

TerminologyThis guide uses the following terminology conventions.

This guide uses theterm...

To refer to...

Distributed Non-OS390 platforms (AIX, HP-UX, Solaris, Windows NT™, andWindows™ 2000)

UNIX AIX, HP-UX, and Solaris

viii IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: User’s Guide

This guide uses theterm...

To refer to...

Windows Windows NT and Windows 2000

Siebel eBusinessApplications resources

Siebel eBusiness Applications server, gateway, or connectionbroker.

For a complete glossary of Tivoli and related terms, refer to the glossary at thefollowing Web site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm.

Operating system-dependent variables and pathsThis book uses the UNIX convention for specifying environment variables and fordirectory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

About this guide ix

x IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: User’s Guide

Chapter 1. Overview

The IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusinessApplications product provides an integration of the Tivoli Framework softwarewith the Siebel eBusiness Applications product. This integration allows centralizedmanagement of Siebel eBusiness Applications across a multi-platform network.This product provides the following features for managing Siebel eBusinessApplications:v IBM Tivoli Monitoring for Applications tasks and jobs designed specifically for

Siebel eBusiness Applicationsv IBM Tivoli Monitoring for Applications resource models designed specifically for

Siebel eBusiness Applicationsv Tivoli Enterprise Console events and rule sets customized for IBM Tivoli

Monitoring for Applications: Siebel eBusiness Applicationsv Tivoli Data Warehouse for use with IBM Tivoli Monitoring for Applications:

Siebel eBusiness Applicationsv Tivoli Business Systems Manager for use with IBM Tivoli Monitoring for

Applications: Siebel eBusiness Applications

Tivoli AdministratorsSiebel administrators are known in the Tivoli environment as Tivoli administrators.Administrators are system or Tivoli administrators who have the authorization tomanage Siebel servers in policy regions. After the product is installed, you canassign authorization roles to other administrators that define the operations theycan perform. Each administrator or group of administrators is represented by anicon on the Tivoli desktop.

IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications integratesinto Tivoli security. To perform administrative functions, administrators must haveauthorization roles for both IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications and the Tivoli management environment.

Authorization RolesTivoli authorization roles determine the range of actions an administrator canperform. You assign roles to administrators so they can perform server or Siebelmanagement tasks. A role may cover the entire Tivoli Management Region or aspecific set of resources. super, senior, admin, and user are examples ofauthorization roles provided in Tivoli software. See the Tivoli ManagementFramework User’s Guide for descriptions of these roles.

IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusiness Applicationsprovides the following roles:

siebel_seniorAuthorizes configuring the connection brokers, Siebel gateways, and Siebelservers. An administrator with the siebel_senior role can perform alloperations.

1

siebel_adminAuthorizes general management operations such as starting and stoppingthe Siebel servers, Siebel gateways, and connection brokers, or deletingdebug logs.

siebel_userAuthorizes general view of the environment.

All tasks require at least one of these roles to be assigned to the Tivoliadministrator running the task. In addition, some tasks require Tivoli authority asdefined by Tivoli management region roles. A Tivoli administrator must have therequired Tivoli authority and must have been assigned one of the IBM TivoliMonitoring for Applications: Siebel eBusiness Applications roles to successfully runthese tasks and processes. You can assign IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications authorization as Tivoli management region roles oras resource roles, depending on local authorization requirements.

Siebel Managed Resources and EndpointsA managed resource is a system or network resource that you manage with TivoliFramework. A managed resource is a specific resource that has a default policydefined in the policy region. An endpoint is a managed resource that is the targetfor distribution of a profile or the resource on which a task or job is to be run.

IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications provides thefollowing types of managed resources:v Siebel Application Serverv Siebel Gateway Name Serverv Connection Broker

User Interface OptionsIBM Tivoli Monitoring for Applications: Siebel eBusiness Applications provides thefollowing user interfaces that you can use to manage Siebel servers:v The Tivoli desktop is the traditional Tivoli graphical user interface.v The command line interface (CLI) is useful in the following circumstances:

– Accessing the Tivoli environment through a modem when you do not haveaccess to a graphical user interface.

– Grouping multiple operations inside a single shell script.– Working on a keyboard without using a mouse or other pointing device.

The following optional products provide additional interfaces that you can use tomanage Siebel servers:v Tivoli Enterprise Consolev Tivoli Business Systems Managerv Tivoli Enterprise Data Warehousev IBM Tivoli Monitoring Web Health Console

2 IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications: User’s Guide

Chapter 2. Getting started quick-reference guide

This chapter provides a quick-reference table of the installation and setupprocedures you must perform before you can use the IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications product. The table below includescross-references to places where you can find additional information about each ofthese tasks.

Table 1. Quick-reference guide for getting started with IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications

Goal Refer to

Installing the IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications product

Make sure you have the appropriate amountof disk space and memory for the software.

Release notes.

Install the software. IBM Tivoli Monitoring for Applications Version 5.1.0: Installation andSetup Guide.

Setting up administrators to use the software

Assign users authorization roles for theprocedures each must perform.Note: You must assign both Tivoli and SiebeleBusiness Applications authorization roles tousers in the policy regions that you want themto manage.

Chapter 3, “Setting Up IBM Tivoli Monitoring for Applications,Version 5.1.0: Siebel eBusiness Applications” on page 5

Appendix A, “Authorization roles quick reference” on page 59 liststhe authorization roles required for each procedure.

Setting up monitoring profiles and tasks

(Optional) Set up any customized tasks. “Customizing a task” on page 33.

(Optional) Set up and schedule jobs from tasks. “Scheduling jobs” on page 39

Also see the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide for more informationabout tasks.

Set up the resource models that you want torun:

v Set up the suggested resource models andrun them for a period of time.

v Remove any resource models that are notnecessary for your environment.

“Setting up IBM Tivoli Monitoring” on page 79.

Also see the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide for more informationabout resource models.

View daily reports in the Web Health Console

View statistics regarding your environment inthe Web Health Console.

Chapter 6, “Viewing resource model results with the IBM TivoliMonitoring Web Health Console” on page 45

(Optional) Connecting to Tivoli Enterprise Console

Set up the Tivoli Enterprise Console so youcan view activity reports for yourenvironment.

Appendix C, “Setting up Tivoli Enterprise Console” on page 63.

(Optional) Create historical reports in the Tivoli Enterprise Data Warehouse

Configure the Tivoli Enterprise DataWarehouse to view environmental data fortroubleshooting and performance tuning.

Chapter 7, “Enabling Tivoli Enterprise Data Warehouse” on page 47

(Optional) Connecting to the Tivoli Business Systems Manager

3

Table 1. Quick-reference guide for getting started with IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications (continued)

Goal Refer to

Set up Tivoli Business Systems Manager sothat you can monitor potential problems inyour environment.

Appendix D, “Integrating with Tivoli Business Systems Manager”on page 73.


Chapter 3. Setting Up IBM Tivoli Monitoring for Applications,Version 5.1.0: Siebel eBusiness Applications

This section describes how to set up IBM Tivoli Monitoring for Applications,Version 5.1.0: Siebel eBusiness Applications which involves the following sections:

Table 2.

Goal Refer to

1. Access the interfaces in the Tivolienvironment so you can use theoperations and functions of IBM TivoliMonitoring for Applications: SiebeleBusiness Applications

“Starting the Tivoli environment” on page 5

2. Assign privileges to administrators andusers so they can manage resources

“Setting authorization roles” on page 7

3. Locate Siebel servers, gateways, andbrokers so you can manage them.

“Discovering Siebel eBusiness Applicationsresources” on page 9

4. (Optional) Configuring Tivoli EnterpriseConsole to work with IBM TivoliMonitoring for Applications, Version5.1.0: Siebel eBusiness Applications soyou can work with resource model orlog file adapter events.

“Configuring event server” on page 64 inAppendix C, “Setting up Tivoli EnterpriseConsole”.

5. (Optional) Update the Logfile adapterfile so the Tivoli Logfile Adapter cangenerate events for Siebel Server logmessages or Connection Broker logmessages.

“Installing logfile adapter message formats”on page 67 in Appendix C, “Setting up TivoliEnterprise Console”.

6. Distribute the resource models so youcan monitor Siebel resources.

“Distribute resource models” on page 11

Starting the Tivoli environment

ObjectiveTo access the Tivoli environment so that you can use the operations and functionsof IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications.

Background informationYou can access the Tivoli desktop or the Tivoli command line interface in order touse the operations and functions of IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications.

The Tivoli desktop is a user interface that provides point-and-click access to IBMTivoli Monitoring for Applications: Siebel eBusiness Applications features andfunctions. The Tivoli desktop provides a central control point for you to organize,manage, and delegate system management operations.

IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications alsoprovides a command line interface (CLI) that enables you to enter commands fromthe keyboard. You can use these commands in shell scripts and with system

5

utilities such as the UNIX cron utility. For more information about usingcommands, refer to the Tivoli Management Framework Reference Manual.

Required authorization roleNone.

Before you beginNone.

When you finishNone.

ProcedureYou can perform this procedure from either the Tivoli command line or thedesktop.

Command Line: Use one of the following two methods to access the Tivolicommand line interface, depending on whether you use a Windows NT or UNIXoperating system:v Windows NT/2000

1. Log on to a Windows NT managed node or Tivoli management regionserver.

2. Select Start in the Windows task bar to open the command prompt window.3. Select Programs4. Select Command Prompt5. Enter the following command to run the environment initialization and setup

script:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env

This command enables you to perform all of Tivoli commands.v UNIX

1. Log on to a UNIX managed node or Tivoli management region server.2. Run the environment initialization and setup script.

– If you are using the Bourne, Korn, or bash shell, run the followingcommand:. /etc/Tivoli/setup_env.sh

– If you are using the C shell, run the following command:source /etc/Tivoli/setup_env.csh

Desktop: Use one of the following methods to log onto the Tivoli desktop:v Windows NT/2000

1. Click Start in the Windows task bar.2. Select Programs.3. Select Tivoli to display the Tivoli pop-up menu.4. Select Tivoli to display the Tivoli login screen.5. Type values in the following fields of the login screen:

Host MachineSpecifies the host name of the Tivoli management region serverwhere the Tivoli desktop should connect.

Log In AsSpecifies the login name to the Tivoli management region server.


PasswordSpecifies the password for the specified login name.

6. Click OK to display the Tivoli desktop.

—OR—v UNIX

Enter the tivoli command. See the Tivoli Management Framework, Version 3.7.1:Reference Manual for more information on this command.

Setting authorization roles

ObjectiveTo assign Siebel administrators and users the roles they need for managingresources in IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusinessApplications.

Background informationYou can authorize roles for the persons who use the product so that they canperform operations and access the resources that their jobs require. The followingroles are created when you install the product:v siebel_senior

v siebel_admin

v siebel_user

A Tivoli administrator must have the required Tivoli authority and be assigned oneof these roles to successfully use this product.

Required authorization rolesenior


When you finishShut down and restart desktop for changes to take effect. When you complete thisprocedure you can discover Siebel eBusiness Applications resources. See“Discovering Siebel eBusiness Applications resources” on page 9.


Command Line: Use the wsetadmin command to set or change resourceauthorization roles. See the Tivoli Management Framework Reference Manual for moreinformation.

Desktop:

Chapter 3. Setting Up IBM Tivoli Monitoring for Applications, Version 5.1.0: Siebel eBusiness Applications 7

1. Double-click the Administrators icon to display the collection to see the iconsrepresenting the defined Tivoli administrators.

2. Right-click the existing administrator whose role you want to modify to displaythe Administrators drop-down menu.

3. Select Edit Resource Roles to display the Set Resource Roles dialog box.

4. Select the Monitoring for Siebel resource for which you want to set theadministrators role from the Resources scrolling list.

5. Add or remove roles for the selected resources as follows:v Add roles

a. Select one or more Siebel roles from those shown in the Available Rolesscrolling list


b. Click the left-arrow button to move the selected roles from the AvailableRoles scrolling list to the Current Roles scrolling list.Additional Information: You can also double-click an entry to move itautomatically from one list to the other.

v Remove rolesa. Select one or more Siebel roles from those shown in the Current Roles

scrolling list.b. Click the right-arrow button to move the selected roles from the Current

Roles scrolling list to the Available Roles scrolling list.

You can also double-click an entry in the Current Roles scrolling list to moveit automatically to the Available Roles scrolling list.

Note: The list of roles can include others not listed here, depending on theparticular applications installed. You must click Change & Close orChange to add and remove the selected roles; the selected roles areonly temporarily moved to the Current Roles or Available Rolesscrolling lists.

6. If you are adding more than one role, click Change to add or remove theselected resource roles for the administrator as specified. The Set ResourceRoles dialog box remains displayed.

Note: You must click Change for each resource to which you assign roles.7. (Optional) Repeat steps 4 through 6 for each resource to which you want to

assign roles.8. Click Change & Close to add or remove the selected resource roles for the

administrator and return to the Administrators window.9. Shut down and restart desktop for changes to take effect.

Discovering Siebel eBusiness Applications resources

ObjectiveTo locate Siebel eBusiness Applications servers, gateways, and connection brokersthat you want to manage in IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications, to capture the resource configuration information, and toconfigure it as a Siebel resource object in this product.

Background informationDiscovery creates Siebel objects, including connection brokers, gateways, andservers, from a user-designated list of endpoints. When IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications discovers a server it can manage, itcreates an object and icon for it. The product subscribes each discovered object to aprofile manager. For example, if the product discovers a gateway, that gateway issubscribed to the Siebel Gateways profile manager.

This procedure requires you to run the Discover task. For more information onrunning tasks, see Chapter 5, “Working with tasks and jobs” on page 29. IBMTivoli Monitoring for Applications: Siebel eBusiness Applications sets the state ofthe new object as UP, DOWN, or WARNING.

Required authorization rolesiebel_senior


Before you beginDetermine the managed node name, Siebel server path, and the Siebel gatewaypath, in which you want to run the task and the endpoints against which youwant to run the task. The dialog in Step 3 of this procedure displays theinformation you must determine before discovering objects.

When you finishAfter you discover objects you can install logfile adapter formats, run tasks, ordistribute resource models. To receive data from a resource model, you first mustdistribute that resource model to the Siebel objects from which you want to receivedata.


Command Line: You can use the wruntask command to run the Discover task todiscover Siebel objects. See the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide for more information on running theDiscover task from the command line.

Desktop:

1. Double-click the Monitoring for Siebel icon to open the Monitoring for Siebelpolicy region window.

2. Double-click the Siebel Utility Tasks icon to display the Siebel Utility Taskstask library window.

3. Double-click the Siebel_Discover_Job icon to display the Discover dialog.

4. Click Choices to display the Endpoint Names dialog box.5. Select the endpoints against which you want to run the Discover task.6. Click Set & Close to set the endpoint names and close the Endpoint Names

dialog box.7. Specify the following attributes in the designated text boxes:

Additional Information: For a detailed description of each attribute, click TaskDescription or refer to the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide.a. Siebel Administrator User Name


b. Siebel Administrator Password – If you use a different password for eachendpoint, you must run the Discover task on each endpoint. You canchange the passwords manually via the desktop after discovering the server.

c. Siebel Server Path (UNIX platform only).d. Siebel Gateway Path (UNIX platform only).

8. Optional. Specify the managed node on which you want to create the Tivoliobjects. By default, this is the managed node currently managing the endpoint.a. Click Choices next to the words Managed Node Name to display the

Managed Node Name dialog box.b. Select a Managed Node Name from the list of options.c. Click Set & Close to set the Managed Node Name and close the Managed

Node Name dialog box.9. Click Set and Execute to run the Discover task against each of the endpoints

you selected.Additional Information: You can also save this task with the parameters that youselected. For more information on how to do this, see “Creating jobs” on page35.

Distribute resource models

ObjectiveTo distribute resource models to a list of subscribers so you can monitor SiebeleBusiness Applications resources.

Background informationWhen you create a Siebel object, it is automatically subscribed to one of thefollowing profile manager types, depending upon which type of Siebel object youcreate:v Connection Brokers profile manager contains Siebel connection broker objects.v Siebel Gateway profile manager contains Siebel gateway objects.v Siebel Servers profile manager contains Siebel server objects.

Each profile manager contains, by default, one profile to which Siebel objects aresubscribed. Each profile holds, by default, one resource model to which the profileis subscribed. However, to receive data from a resource model, you first mustdistribute that resource model to the Siebel objects from which you want to receivedata.

You can distribute resource models to subscribers after you install IBM TivoliMonitoring for Applications, Version 5.1.0: Siebel eBusiness Applications and runthe Discover task against the endpoints you want to manage .

Required authorization rolessenior

Before you beginCreate or discover objects. See “Discovering Siebel eBusiness Applicationsresources” on page 9 for more information.

When you finishNone



Command Line: You can use the wdmdistrib command to distribute resourcemodels to Siebel objects. See the IBM Tivoli Monitoring Reference Guide for moreinformation.

Desktop:

1. Open the Monitoring for Siebel policy region window.2. Double-click the icon for the profile manager that contains the profile to which

you want to distribute a resource model.

The profile manager displays.


3. Double-click the Profile icon to display the IBM Tivoli Monitoring Profilewindow.

4. Click Profile from the menu bar to display the profile drop-down menu.5. Click Distribute... from the toolbar to display the Distribute Profile dialog.

6. Select one of the following from the Distribute to box:v Next level of subscribers

–OR–v All levels of subscribers


7. Select one of the following from the Distribute Will section of the DistributeProfile dialog

8. Add or remove subscribers from the Distribute to These Subscribers: or DoNot Distribute to These Subscribers to select subscribers to which you want todistribute the resource model.

9. Click Distribute and Close to distribute the resource model and close thewindow.


Chapter 4. Working with IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications

This chapter describes how to work with the Siebel resource objects in the Tivolienvironment. Siebel servers, gateways, and brokers are represented by resourceobjects in the Tivoli environment. Table 3 provides an overview of the topicscovered in this chapter.

Table 3. Working with IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications

Goal Refer to

Check the status of a broker, gateway, orserver

“Checking Siebel eBusiness Applicationsresources status” on page 16

View broker, gateway, or server properties “Viewing Siebel resource properties” onpage 17

Start or stop a broker, gateway or server “Starting or stopping a resource” on page 20

View Siebel logs “Managing Siebel Logs” on page 21

View Tivoli logs “Managing Tivoli logs” on page 23

Edit server properties “Editing Tivoli Siebel server objectparameters” on page 24

Create Siebel objects “Creating Siebel objects” on page 24

The following displays an example of a resource object’s right-click drop-downmenu.

15

Checking Siebel eBusiness Applications resources status

ObjectiveTo check the status of the Siebel connection broker, gateway, or server.

Background informationUse this procedure to display the status of a Siebel eBusiness Applications resourcein an output window. When the status of a resource changes, the associated icon inthe policy region is updated to reflect the object’s current status. The status is oneof the following:v UP

—OR—v DOWN

—OR—v WARNING

—OR—v UNKNOWN

You can also check status with the Check_Server_Status task. See thedocumentation for this task in the IBM Tivoli Monitoring for Applications Version5.1.0: Siebel eBusiness Applications Reference Guide. For more information on runningtasks and jobs, see Chapter 5, “Working with tasks and jobs” on page 29.

Required authorization rolesiebel_user or siebel_admin or siebel_senior

Before you beginCreate either a Siebel Connection Broker, Siebel Gateway or Siebel Server object.Refer to the Discover task in the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide for more information.

When you finishClose the output display window.


Command Line: You can use the wruntask command to run theCheck_Server_Status task to check the status of a Siebel object. See thedocumentation for this task in the IBM Tivoli Monitoring for Applications Version5.1.0: Siebel eBusiness Applications Reference Guide for more information.

Desktop:

1. From the Monitoring for Siebel policy region window, right-click a Siebelconnection broker, gateway, or server object icon.


2. Select Operation to display the Operation pop-up menu.

3. Select Check Status to display the Check Status display window.

Viewing Siebel resource properties

ObjectiveTo display the values of the managed resource properties. If a task fails, you cancheck the properties to confirm that they are set correctly.

Background informationViewing Siebel object properties (broker, gateway or server) enables you to reviewsystem resources. Table 4, Table 5 on page 18, and Table 6 on page 18 list thespecific information you can view for each object type.

The Siebel Connection Broker object properties window contains informationabout the location and configuration of the Siebel Connection Broker object.

Table 4. Siebel Connection Broker properties

Property Name Property Description

Tivoli label Name of the Tivoli enterprise

Installation Path The file path where the connection broker isinstalled

Enterprise Name Name of the Siebel enterprise

Chapter 4. Working with IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications 17

Table 4. Siebel Connection Broker properties (continued)

Hostname The name of the host where the connectionbroker is installed

Managed Node The managed node where the object resides

Endpoint Name of the endpoint where the connectionbroker is located

The Siebel Gateway object properties window contains information about thelocation and configuration of the Siebel Gateway.

Table 5. Siebel Gateway object properties



Gateway Name Name of the Siebel Gateway

Gateway Version Version of the Siebel Gateway

Installation Path The file path used to install the gateway.

Enterprise Name Name of the Siebel enterprise

Hostname The name of the host where the gateway isinstalled

Managed Node The managed node where the object islocated

Endpoint Name of the endpoint where the gateway islocated

The Siebel Server object properties window contains information about thelocation and configuration of the Siebel Server.

Table 6. Siebel Server object properties



Server Name Name of the Siebel server

Enterprise Name Name of the enterprise where the Siebelserver is located

Server Version Version of the Siebel server

User Name User ID of the Siebel administrator

Installation Path The file path used to install the serverserver.

Hostname The name of the host where the Siebelserver is installed

Managed Node The managed node where the server islocated

Endpoint Name of the endpoint where the object isdefined

Required authorization rolesiebel_user, siebel_admin, or siebel_senior


Before you beginCreate a Siebel connection broker, gateway, or server object. Refer to the Discovertask in the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for more information.



Command Line: You can use the wsiebel command to view the properties of aSiebel object. See the documentation for this task in the IBM Tivoli Monitoring forApplications Version 5.1.0: Siebel eBusiness Applications Reference Guide for moreinformation.

Desktop:

1. Double-click the Monitoring for Siebel policy region to display the PolicyRegion: Monitoring for Siebel window.

2. Right-click the object icon to display a pop-up menu.3. Click Operation to display the Operation pop-up menu.


4. Click Properties to display the properties of the resource.

Starting or stopping a resource

ObjectiveTo start or stop the Siebel Connection Broker, Siebel Gateway, or Siebel Server.

Background informationYou might want to use this procedure before performing maintenance on a server.

Use this procedure to start or stop the following:v a Siebel Connection broker or Resonate Central Dispatch Agent NT Service/Unix

daemon on a node.v a Siebel Gateway NT Service/Unix daemon on a node.v a Siebel Server NT Service/Unix daemon on an node.

Starting and stopping a resource updates the server object icon.

You can use the following tasks to start Siebel resources:v Start_Connection_Brokerv Start_Siebel_Gatewayv Start_Siebel_Server

You can use the following tasks to stop Siebel resources:v Stop_Connection_Brokerv Stop_Siebel_Gatewayv Stop_Siebel_Server

See the Table 7 on page 29 and the IBM Tivoli Monitoring for Applications Version5.1.0: Siebel eBusiness Applications Reference Guide for more information.

Required authorization rolesiebel_admin or siebel_senior


Before you beginBefore you stop a server, consider the impact on your Siebel environment.



Command Line: You can use the wruntask command to run these tasks. Thesetasks are documented in the IBM Tivoli Monitoring for Applications Version 5.1.0:Siebel eBusiness Applications Reference Guide.

Desktop:

1. Double-click the Monitoring for Siebel policy region to display the PolicyRegion: Monitoring for Siebel window.

2. Right-click the object icon for the resource you want to start or stop.3. Select Operation to display the Operation pop-up menu.

4. Select Start Server to start the resource.—OR—Select Stop Server to stop the resource.

5. Click Close to close the output window.

Managing Siebel Logs

ObjectiveTo display the list of log files located on an endpoint that are specific to the SiebeleBusiness Applications and optionally delete them.

Background informationThe Log Files dialog window displays log files that are specific to the managedresource the object represents. You can use logs to analyze problems. For example,if you have a problem with the Siebel server that does not stay running, you mightlook at the Siebel server logs.

This procedure allows you to view log files to isolate and solve performanceproblems. You can delete unnecessary log files to free up disk space.



Before you beginCreate a Siebel connection broker, gateway, or server object. Refer to “DiscoveringSiebel eBusiness Applications resources” on page 9 for more information.


ProcedureYou can perform this procedure from the Tivoli desktop only.1. Double-click the Monitoring for Siebel policy region to display the Policy

Region: Monitoring for Siebel window.2. Right-click a Siebel Connection Broker, Siebel Gateway, or Siebel Server object

icon.3. Select Diagnostics to display the Diagnostics pop-up menu.4. Click the Siebel Server Logs option to display the Log Files window.

Note: The Siebel object you right-clicked in Step 2 determined the Siebel logoption available on the pop-up menu in this step. The option displayedis one of the following:v Broker Logs

v Siebel Gateway Logs

v Siebel Server Logs

5. Select one or more log files from the Log Files list.Additional information: To select more than one log file, hold the Ctrl key downon the keyboard and click multiple log files. Double-click a log file to view itscontents.


6. Click Log Files on the menu bar to display the Log Files drop-down menu.7. Select one of the following Log Files options:

v Get Log(s) to view selected logs—OR—

v Delete Log(s) to delete the selected logs—OR—

v Refresh List to refresh the log file list and display the Log Files dialog boxwith the refreshed list.

Managing Tivoli logs

ObjectiveTo display the endpoint or callback log files so you can view or delete logs.

Background informationEndpoint files are generated by the resource models and and tasks that run againstthe Siebel objects. Callback log files are generated each time you select an itemfrom an object right-click-menu.

The Log File dialog displays the specified object’s log files as well as logs that arenot associated to an object. You can use logs to analyze problems. For example, ifyou have a problem getting the properties of a Siebel object, you might look at thecallback logs. If you have trouble starting a Siebel server, you might look at theendpoint log for information on the cause of the problem.




Procedure1. Double-click the Monitoring for Siebel policy region to display the Policy

Region: Monitoring for Siebel window.2. Right-click the object icon.3. Select Diagnostics to display the Diagnostics pop-up menu.4. Select Tivoli Logs to display the Tivoli Logs pop-up menu.5. Select one of the following:

v Endpoint to display all log files for the specified object on the endpointhosting the object. The set of log files includes task logs.—OR—

v Callback to display all callback logs for the object.6. Select a log file from the Log Files list.

Additional information: To select more than one log file, hold the Ctrl key downand click multiple log files. Double-click a log to view its contents.

7. Click Log Files on the toolbar to display the Log Files drop-down menu.8. Select one of the following Log Files options:

v Get Log(s) to view output for the selected logs.—OR—


v Delete Log(s) to delete the selected logs.—OR—

v Refresh list to refresh the log file list and display the Log Files dialog boxwith the refreshed list.

Editing Tivoli Siebel server object parameters

ObjectiveTo update a Siebel Administrator user ID and password for a Siebel Server object.For example, you should update a password after you have changed it on theserver.

Background informationThe values in the object parameter are saved with the object and used by varioustasks and resource models to access data from a Siebel server.




ProcedureYou can perform this procedure from the Tivoli desktop only.1. Double-click the Monitoring for Siebel policy region to display the Policy

Region: Monitoring for Siebel window.2. Right-click a Siebel Server object icon.3. Select Change Server to display the Change Siebel Server Parameters dialog

box.

4. Specify the Siebel Administrator user id in the User ID text box. This field iscase-sensitive.

5. Specify the Siebel Administrator password in the Password textbox. This fieldis case-sensitive.

6. Click Set and Execute to commit the changes to the User ID and Password.

Creating Siebel objects

ObjectiveTo create a Siebel connection broker, gateway, or server object.

Background informationYou can create Siebel objects using one of the following:


v The Discover task or Siebel_Discover_Job task. This is the recommended methodfor creating objects because the Discover task automatically collects and verifiesattributes of the resource and the other methods do not. See “Discovering SiebeleBusiness Applications resources” on page 9 for more information.

v The Policy Region Create menu toolbar option on the Tivoli desktop. Thismethod requires you to put all the necessary attributes of the resource and doesnot verify the input. If you use this method to create objects, you can run theRun_Srvrmgr_Command task and input the Siebel List Servers command toverify the server object creation. See the Run_Srvrmgr_Command task in theIBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness ApplicationsReference Guide for more information.

v The wsiebel command from the Tivoli command line. This method requires youto put all the necessary attributes of the resource and does not verify the input.If you use this method to create objects, you can run theRun_Srvrmgr_Command task and input List Servers command to verify theserver object creation. Refer to the Discover task and the wsiebel commandchapter in the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for more information.

When you create an IBM Tivoli Monitoring for Applications, Version 5.1.0: SiebeleBusiness Applications object, it is added as a subscriber to a profile manager inthe Monitoring for Siebel policy region. For instance, Siebel Gateway objects areadded as a subscriber to the Siebel Gateways profile manager.

You can specify the managed node where you want to create the object. If you donot specify a managed node, the object is created on the managed node acting asthe Tivoli Gateway for the specified endpoint. When you select an endpoint, thegateway associated with the endpoint is filled in as the default managed node onthe dialog box.

For more information on the wsiebel command, see the section on the wsiebelcommand in the IBM Tivoli Monitoring for Applications Version 5.1.0: SiebeleBusiness Applications Reference Guide.



When you finishRun the IBM Tivoli Monitoring for Applications: Siebel eBusiness ApplicationsRun_Srvrmgr_Command task and input the List Servers command to verify thecreation of server objects. This verifies that the object you have created is afunctional object. To verify a connection broker or gateway object, right-click on theobject, select Diagnostics from the drop menu, and select Siebel Gateway Logs fora Gateway, or Siebel Broker Logs, for a broker. If you get an error, the object is notfunctional.

After you verify that you created functional objects, you can distribute resourcemodels and run tasks.



Command Line: For information on how to create objects from the command line,see the section on the wsiebel command in the IBM Tivoli Monitoring forApplications Version 5.1.0: Siebel eBusiness Applications Reference Guide.

See Chapter 5, “Working with tasks and jobs” on page 29 for step-by-stepinstructions on running tasks.

Desktop: There is a Create menu on the Monitoring for Siebel policy regionwindow menu bar. If you select this menu item, you see options to create aSIEBELBroker, SIEBELGateway, and SIEBELServer. After you select one of theoptions, a dialog box prompts for several values displays.

Follow these steps to create a Siebel object from the Tivoli desktop:1. Double-click the Monitoring for Siebel policy region to display the Policy

Region: Monitoring for Siebel window.2. Select Create to display the Create drop-down menu.3. Select one of the following object types:

v SIEBELBroker... to display the Create Connection Broker dialog box andperform the following steps.

a. Select an endpoint from the Select an endpoint list.b. Select a Siebel Enterprise Name.c. Optional: Specify a managed node.d. Specify a Connection Broker.e. Click Set and Execute to create the Broker Object and close the dialog

box.

—OR—


v SIEBELGateway...to display the Create Siebel Gateway dialog box andperform the following steps:

a. Select an endpoint from the Select an Endpoint list.b. Select a Siebel Gateway Version.c. Select a Siebel Enterprise Name.d. Optional: Specify a Managed Node.e. Specify a Siebel Gateway Path.f. Click Set and Execute to create the Gateway object and close the dialog

box.

—OR—


v SIEBELServer... to display the Create Siebel Server dialog box andcomplete the following steps:

v where:a. Select an endpoint from the Select an Endpoint list.b. Specify a Siebel Server Name.c. Specify a Siebel Enterprise Name.d. Specify a Siebel Server Version.e. Specify a Siebel Administrator User Namef. Specify a Siebel Administrator password.g. Specify a Siebel Gateway name.h. Optional: Specify a managed node.i. Specify a Siebel Server Path.j. Click Set and Execute to create the server object and close the dialog

box.


Chapter 5. Working with tasks and jobs

A task is a Siebel eBusiness Applications operation, such as starting a server. IBMTivoli Monitoring for Applications, Version 5.1.0: Siebel eBusiness Applicationsprovides task libraries that contains standard tasks. Standard tasks run on anymachine without consideration to platform type. Tasks can be run routinely onendpoints to maintain your managed environment.

A customized task is a standard task with defined arguments that are saved under aunique task name. For example, you can customize a task to save task outputresults to a file after each execution. Because customized task arguments are saved,the Tivoli environment does not display argument dialogs when you run the taskfrom the desktop. However, if you run a customized task from the command line,you still must specify the task arguments. Running a customized task requiresadditional information before it runs, such as the target of the execution.

A job is a task with pre-defined output destination and execution targets that canbe executed many times on specific managed resources. You can create jobs fromboth standard and customized tasks in the product task library. Like tasks, jobs arestored in task libraries, so you can reuse them. After you create a job, you can runit immediately using the procedure described in “Running jobs” on page 38. Youcan schedule jobs to run repeatedly in the Scheduler, as described in “Schedulingjobs” on page 39.

Table 7 shows the options to manage tasks and jobs.

Table 7. Working with tasks and jobs

Goal Refer to

1. Running a task to perform a specificoperation.

“Running tasks” on page 30

2. Defining a standard task with specificarguments to customize the task.

“Customizing a task” on page 33

3. Creating a job from a task so that it can bescheduled to run.

“Creating jobs” on page 35

4. Running a job with predefined arguments. “Running jobs” on page 38

5. Scheduling jobs to run at specified times. “Scheduling jobs” on page 39

The installation process installs several task libraries in the Monitoring for Siebelpolicy region. We recommend that you do not remove the task libraries from thispolicy region. The task libraries contain default policies that affect how the tasklibraries work.

The policy region containing the task libraries defines task and job policies. Defaultpolicies set profile manager options and endpoints for tasks. Validation policiescontrol the creation and execution of tasks.

29

Running tasks

ObjectiveTo execute, or run, a standard or customized task on one or more specified targetsso you can perform a Siebel eBusiness Applications operation.

Background InformationFor an understanding of tasks, see the introduction of this chapter.

Required Authorization RolesThe required authorization role is task-specific. See the Appendix A,“Authorization roles quick reference” on page 59 to determine which authorizationrole to use for specific tasks.

Before You BeginNone.

When You FinishNone.


Command Line: Use the wruntask command to run a task. The documentationfor the wruntask command does not provide information for specific tasks. See the“command line interface (CLI) Syntax” and “CLI Example” sections in the productreference guide. The “CLI Example” section provides an example of how to enterthe wruntask command and the task arguments at the command line.

For more information about the wruntask command, see the Tivoli FrameworkReference Manual.

Desktop:

1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the Monitoring for Siebel policy region icon to display the

policy region.c. Double-click the product task icon to display the product task library

window.


2. Double-click the task icon that you want to run to display the Execute Taskdialog box.

Additional Information: The Execute Task dialog box is a generic dialog box ofexecution parameters for all tasks.

3. Click one of the following check boxes in the Execution Mode group box:v Parallel runs the task simultaneously on all targets. Parallel is typically the

fastest method of execution.—OR—

v Serial runs the task sequentially on all targets in alphabetical order.—OR—

v Staged runs the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you are running the taskon a large number of endpoints. Specify the Staging Count (number oftargets to run against per stage) and the Staging Interval (number of secondsbetween each set).

4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional Information: The Timeout value does not stop the task. This valuespecifies the number of seconds the desktop waits for the task to completebefore it issues an error. The task continues to execute on the endpoint withoutdisplay of output results. Setting an early timeout enables your desktop tobecome available again if the task takes a long time to execute. The default is

Chapter 5. Working with tasks and jobs 31

60 seconds. If the task takes longer to complete than the specified Timeout andis running in Serial or Staged mode, the product moves on to other endpointsafter this time expires.

5. Click one or more of the following check boxes in the Output Format groupbox to choose the output types that the task returns:

HeaderIncludes a descriptive header for each record, such as the task nameand target.

Return CodeIncludes the programming codes produced when the task executes.

Standard ErrorIncludes all error messages encountered when the task executes.

Standard OutputIncludes all information that results from the task execution.

6. Select one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Desktop to display the task output on the desktop.

Additional Information: If you choose Display to Desktop, you have an optionto save the information to a file as an option inside the output displaywindow.—OR—

v Click Save to File to save the output to a file.

To save the task output to a file, do the following:a. Click the Save to File check box in the Output Destination group box to

display the Destination for Task Output dialog box.b. Type the name of the managed node on which to save the output in the On

Host text box.Additional Information: The endpoint must be a Tivoli client.

c. Type the absolute pathname for the output file in the Output File text box.Additional Information: Example: /tmp/mytask.out

d. Click Set & Close to set your choices and return to the Execute Task dialogbox.

7. Choose the Siebel objects on which you want to run the task by doing one ofthe following:v Run the task on specific endpoints by doing the following:

a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the Selected

Task Endpoints list.

—OR—v Run the task on all subscribers of the specified profile managers by doing the

following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.8. Click Execute to display the task argument dialog box.

Additional Information: For more information on the fields in the dialog box,refer to the task description in the product reference guide or click Task


Description to display the online help. The following tasks do not display atask argument dialog when you click Execute:v Check_Server_Statusv Start_Connection_Brokerv Start_Siebel_Gatewayv Start_Siebel_Serverv TBSM_Discover

9. Click Set & Execute to run the task.

Customizing a task

ObjectiveTo customize one of the standard tasks in the task library so you can save definedarguments for future executions.

Background InformationFor an understanding of tasks, see the introduction of this chapter.



When You FinishYou can run a task by following the procedure in “Running tasks” on page 30.When you run a customized task, the Tivoli desktop does not display the taskargument dialog.

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Open the task library window by doing the following:

a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the Task library icon to display the task library window.

2. Double-click a task icon to display the Execute Task window for that task.Additional Information: The Execute Task window is a generic dialog box withexecution parameters for all tasks. Complete this dialog box to run the task asdescribed in “Running tasks” on page 30.

3. Click Execute to display the task argument dialog box.Additional Information: The following tasks do not display a task argumentdialog when you click Execute:v Check_Server_Statusv Start_Connection_Brokerv Start_Siebel_Gatewayv Start_Siebel_Serverv TBSM_Discover

4. Type the appropriate values for this customized task.Additional Information: Most standard tasks have an argument dialog box. Forinformation about each field in these dialog boxes, see the task description in


the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide, or click Task Description to display the onlinehelp.

5. Click Save to display the Save Argument dialog box.

6. Type the following information to define the customized task:a. Type a name for the task in the Name text box.

Additional Information: This name appears in the Library Contents field soyou can view the customized tasks that are based on the parent task.Example: Discover

b. Type an identifier for this task.Additional Information: An identifier is the name of the task icon in the TaskLibrary window. A customized task identifier has two parts. The first partis the standard task name (such as Discover). The second part isdescriptive information that makes sense to you. For example, you couldtype SYS. The resulting task name would be Discover_SYS.The software generates a unique default name (such asControl_Logfile_Adapter_aaa) if no identifier is entered.

c. Type a description of this task in the Description text box.d. Optional: Select the Show by Identifier check box to change the Library

Contents list to use the task identifier instead of the task name.e. Optional: Click Parent Description to display information about the parent

task from which you are creating a customized task.Additional Information: The task information appears under the headingDescription.

f. Click Save & Close to return to the task argument dialog box.7. Click Cancel in the task argument dialog box.8. Click Close in the Execute Task dialog to return to the Task Library window.9. Click View to display the View drop-down menu.

10. Click Refresh from the View drop-down menu to display the new customizedtask.


Creating jobs

ObjectiveTo create a job by defining execution parameters so you can specify a targetenabling you to schedule it to run repeatedly in the Scheduler.

Background InformationFor an understanding of jobs, see the introduction of this chapter.

Required Authorization Rolesadmin, senior, or super




Command Line: Use the wcrtjob command to create jobs from the command line.The syntax is as follows:

wcrtjob –j job_name –l library_name –t task_name –M mode

[–s interval –n number] –m timeout –o output_format

[–D|–d mannode_name –f file_name] [–h mannode_name]

[–p prof_manager_name]

where:

–j job_nameThe name of the job being created. Job names can include anyalphanumeric character, an underscore (_), a dash (–), a period (.), and aspace.

–l library_nameSpecifies the task library containing the task to be included in the job.

–t task_nameSpecifies the name of the task to include in the job.

–M modeSpecifies the mode in which the job runs. Valid options are as follows:

parallelRuns the job on all specified endpoints and any subscriberssimultaneously.

serial Runs the job on one endpoint at a time.

staged Runs the job on a set number of endpoints at specified intervals.

Desktop:

1. Access the task library window by doing the following:a. Open the Tivoli desktop.


b. Double-click the policy region icon to display the policy region.c. Double-click the task library icon to display the task library window.

2. Click Create to display the Create drop-down menu.3. Click Job from the Create drop-down menu to display the Create Job dialog

box.

4. Type a descriptive job name in the Job Name text box.Additional Information: The job name identifies the icon on the desktop. Thename can include any alphanumeric character, an underscore (_), dash (–),period (.), or blank space.

5. Select the task on which the job is based from the Task Name list.6. In the Execution Mode group box, select one of the following check boxes:


ParallelRuns the task simultaneously on all targets. Parallel is typically thefastest method of execution.

—OR—

Serial Runs the task sequentially on all targets in alphabetical order.

—OR—

StagedRuns the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you are running thetask on a large number of endpoints. Complete Step 8 to specify theStaging Count (number of targets to run against per stage) and theStaging Interval (number of seconds between each set).

7. In the Execution Parameters group box, type the timeout value (in seconds)for the task in the Timeout text box.Additional Information: This value specifies the number of seconds the productwaits for the task or job to complete before it issues an error. The default is 60seconds. If the task takes longer to complete than the specified Timeout and isrunning in Serial or Staged mode, the product moves on to other endpointsafter this time expires. The task continues to execute on the endpoint, eventhough the product has stopped waiting for it to end.

8. Optional: If you selected Staged in Step 6, specify the number of endpoints toinclude in each staged set in the Staging Count text box and the number ofseconds between each set’s start-up time in the Staging Interval text box.

9. Click one or more of the following check boxes to choose the output type inthe Output Format group box:

HeaderIncludes a descriptive header for each record.

Return CodeIncludes the programming codes produced when the job executes.

Standard ErrorIncludes all error messages encountered when the job executes.

Standard OutputIncludes all information that results from the job execution.

10. Select one of the following in the Output Destination group box to choose anoutput destination:v Display on Desktop to display the job output on the desktop. Go to Step

12.Additional Information: If you choose Display to Desktop, you have anoption to save the information to a file as an option inside the outputdisplay window.—OR—

v Save to File to save the output to a file and display the Destination forTask Output dialog box. Go to Step 11.

11. Do the following in the Destination for Task Output dialog box to save thejob output to a file:a. Type a Tivoli client endpoint name on which to save the output in the On

Host text box.b. Type the absolute pathname for the output file in the Output File text box.

Additional Information: Example: /tmp/myjob.out


c. Click Set & Close to set your choices and return to the Create Job dialogbox.

12. Do one of the following to choose the endpoints on which to run the job:v Run the job on specific endpoints by doing the following:

a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the

Selected Task Endpoints list.–OR–

v Run the job on all subscribers of the specified profile managers by doingthe following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.13. Click Create & Close to create the job and return to the Task Library window.

Additional Information: The new job icon appears in the Task Library window.

Running jobs

ObjectiveTo execute a job on specific endpoints immediately so you can perform a SiebeleBusiness Applications operation.

Background InformationBefore you can run a job, you must create it, as described in “Creating jobs” onpage 35.

If you created a job from a standard task, the Tivoli desktop displays the taskargument dialog so that you can fill in any required information.

Jobs created from customized tasks run without further input because all requiredinformation is specified. (See “Customizing a task” on page 33 for informationabout how to create a customized task.)



When You FinishYou can choose to schedule a job to run regularly as described in “Schedulingjobs” on page 39.


Command Line: Use the wrunjob command to run jobs from the command line.For more information about this command, see the Tivoli Framework ReferenceManual.

Desktop:


1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the task icon to display the task library window.

2. Do one of the following:v Double-click the job icon created from a customized task to begin executing

the job.–OR–

v Double-click the job icon created from a standard task. Go to Step 3.

3. Type the values in the task dialog box.Additional Information: For information about specific fields, see the taskdescription in the product reference guide or click Task Description to displaythe online help. The product runs the job and displays the output on thedesktop or sends it to a file in accordance with the job specification.

Scheduling jobs

ObjectiveTo schedule jobs to occur regularly so you can routinely perform Siebel eBusinessApplications operations.

Background InformationThe product utilizes Scheduler to schedule jobs. To schedule a job, you must firstcreate it (see “Creating jobs” on page 35).

Required Authorization Rolesadmin, senior, or super





Command Line: Use the wschedjob command to schedule a job in the TaskLibrary from the command line. You can only schedule jobs that already exist inthe task library from the command line. For more information, see the TivoliFramework Reference Manual.

Desktop:

1. Open the product task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the product policy region icon to display the policy region.c. Double-click the product task library icon to display the task library

window.2. Drag the job icon that you want to schedule onto the Scheduler icon located

on the Tivoli desktop.3. Optional: Do the following if a task argument dialog box displays:

a. Type the appropriate information for each field in the dialog.Additional Information: Refer to the task description in the product referenceguide or click Task Description to display the online help for this task.


b. Click Set & Execute to set the task arguments and open the AddScheduled Job dialog box.

4. Type a label for the job icon in the Job Label text box of the Add ScheduledJob dialog box.Additional Information: The label identifies the icon on the desktop. The joblabel can include alphanumeric characters, underscores (_), dashes (–), periods(.), and blanks. If you do not specify a label, the job name is used.

5. Do one of the following:v Select the Disable the Job check box to stop a scheduled job from running.

—OR—v Deselect the Disable the Job check box to continue running a scheduled

job.

Additional Information: For more information on job disabling, see the TivoliEnvironment Framework User’s Guide.


6. Optional: Type a job description to uniquely identify the job in the Descriptionfield.

7. Set the date and time to begin scheduling in the Schedule Job For group box:a. Type a date in the Month, Day, and Year text boxes.b. Enter the time using the Hour and Minute drop-down lists and the AM

and PM radio buttons.8. Optional: Repeat the job by doing the following in the Repeat the Job group

box:a. Do one of the following:

v Select the Repeat the job indefinitely check box to repeat the jobindefinitely.–OR–

v Repeat the job a finite number of times by doing the following:1) Select the Repeat the job check box.2) Type the number of times you want the job to run.

b. Set the interval between start times for the job in the The job should startevery field.

9. Click any of the following check boxes in the When Job Completes group boxto send job completion notification:v Send a notice to a specific group by doing the following:

a. Click the Post Tivoli Notice check box.b. Click Available Groups to display the Available Groups dialog box.c. Select a group from the list of notice groups.d. Click Set to set your group and return to the Add Scheduled Job dialog

box.

Additional Information: You can read notices from the Tivoli desktop byclicking on the Notices icon.

v Send a notice to your desktop by doing the following:a. Click the Post Status Dialog on Desktop check box.b. Type the message you want displayed in the text box next to the check

box.v Send an email to a specified user by doing the following:

a. Click the Send e-mail to check box.b. Type the complete e-mail address in the text box next to the check box.

v Log the job completion status to a file by doing the following:a. Click the Log to File check box.b. Enter the file destination by doing one of the following:

– Type the file destination in the Host and File text boxes.–OR–

– Browse for the file destination by doing the following:1) Click File Browser to display the File Browser dialog.2) Double-click on a host name to display the directories and files

for that host.3) Select a directory and file from the Directories and Files lists.4) Click Set File & Close to return to the Add Scheduled Job dialog

box.


10. Optional: Set retry, cancel, or restriction options by doing the following:a. Click Set Retry/Cancel/Restriction Options to display the Set

Retry/Cancel Restrictions Options dialog box.b. Choose one of the following cancel job options:

v Deselect the Cancel job check box to have the Scheduler continue tryingthe job indefinitely.—OR—

v Set the Scheduler to cancel a job in a specified time frame by doing thefollowing:1) Select the Cancel job check box.2) Type the time frame for the Scheduler to wait before canceling a job

that has not started.c. Click one of the following retry options:

v Click Retry the job until success to retry the job until it runssuccessfully.—OR—

v Specify the number of times a job attempts to run by doing thefollowing:1) Click the Retry the job check box.2) Type the number of attempts to start the job in the text box.3) Type the amount of time the Scheduler waits before retrying in the

The job should retry every field.d. Click any of the following check boxes in the Restrictions group box to

specify the job run times:

During the daySet the beginning and ending hour of day for the job to run.

At nightSet the beginning and ending hour of night for the job to run.

During the weekSet the beginning and ending day of the week for the job to run.

On weekendsSet the beginning and ending day of the weekend for the job torun.

e. Click Set to set the options and return to the Add Scheduled Job dialogbox.

11. Click Schedule Job & Close to schedule the job and return to the Tivolidesktop.


Chapter 6. Viewing resource model results with the IBM TivoliMonitoring Web Health Console

This chapter provides an overview of the IBM Tivoli Monitoring Web HealthConsole. For complete information on installing and working with the IBM TivoliMonitoring Web Health Console see the latest version of the IBM Tivoli MonitoringUser’s Guide. The IBM Tivoli Monitoring Web Health Console runs on Netscape 6.xand Internet Explorer 6.x browsers. You can use the IBM Tivoli Monitoring WebHealth Console for the following purposes:v Checking, displaying, and analyzing the status and health of endpoints that

have distributed resource monitorsv Displaying an endpoint’s real-time and historical data logged to the IBM Tivoli

Monitoring databasev Viewing online and historical data on endpoints as a follow-up to specific

problemsv Starting and stopping the IBM Tivoli Monitoring engine and individual resource

models on selected endpointv Removing a profile from the selected endpoint

You can use the IBM Tivoli Monitoring Web Health Console to check, display, andanalyze the status and health of any endpoint with profiles and resource models.Status reflects the state of the endpoint displayed on the IBM Tivoli MonitoringWeb Health Console, such as running or stopped. Health is a numeric valuedetermined by resource model settings. You can also use the Web Health Consoleto work with real-time or historical data from an endpoint that is logged to theIBM Tivoli Monitoring database.

You can use the diagnostic and monitoring capabilities of the IBM TivoliMonitoring Web Health Console to perform targeted analysis of problemsassociated with individual endpoints when an event is sent to the Tivoli EnterpriseConsole. Use the online and historical data to follow up specific problems withsingle endpoints.

Understanding resource healthThe IBM Tivoli Monitoring Web Health Console obtains events and indicationsfrom endpoints. The IBM Tivoli Monitoring Web Health Console displays thehealth of each potential problem as a numeric value between 100 (perfect health)and zero (with zero meaning that the conditions for the corresponding event aremet). Intermediate values show the percentage of occurrences currently registeredwith respect to the total number of occurrences needed to trigger an event. SeeTable 8 on page 46

45

Table 8. Health determination example

Cycle 1 2 3 4 5

CPU% 55 73 54 63 68

Occurrences or Holes H O H O O

Occurrence Count 0 1 1 2 3

Health % 100 75 75 50 25

Table 8 displays the health percentage changes in steps of 25% because 4occurrences were required to trigger an event; if the indication required 5occurrences, the health percentage would have changed by steps of 20%. Resourcehealth is determined at the indication level and passed up to the endpoint. Thelowest health of any indication in a resource model is shown as the health of thatresource model and the lowest health of any resource model installed on anendpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is installed on an endpoint has a health of zero, the healthof the endpoint is shown as zero. The required occurrences, cycle times, thresholds,and parameters for indications are defined when the resource model is created inthe IBM Tivoli Monitoring Workbench.

Connecting the IBM Tivoli Monitoring Web Health ConsoleYou can connect the IBM Tivoli Monitoring Web Health Console to any Tivolimanagement region server or managed node and configure it to monitor any or allof the endpoints that are found in that region. The IBM Tivoli Monitoring WebHealth Console does not have to be within the region itself, although it could be.To connect to the IBM Tivoli Monitoring Web Health Console you need access tothe server on which the IBM Tivoli Monitoring Web Health Console server isinstalled and the IBM Tivoli Managed Region on which you want to monitorhealth. All user management and security is handled through the IBM Tivolimanagement environment. This includes creating users and passwords as well asassigning authority.


Chapter 7. Enabling Tivoli Enterprise Data Warehouse

This chapter provides information on enabling IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications for Tivoli Enterprise Data Warehouse.

OverviewTivoli Enterprise Data Warehouse enables you to access application reports fromvarious Tivoli and customer applications. The infrastructure provides a set ofextract, transform and load (ETL) utilities that you use to extract and move datafrom Tivoli application data stores to a central data warehouse database.

Tivoli Enterprise Data Warehouse provides the following capabilities:v An open architecture for storing, aggregating, and correlating historical data. In

addition to the data collected by IBM Tivoli software, Tivoli Enterprise DataWarehouse has the flexibility and extensibility to enable you to integrate yourown application data.

v Database optimizations for the efficient storage of large amounts of historicaldata and for fast access to data for analysis and report generation.

v The infrastructure and tools necessary for maintaining and viewing the collecteddata. These include the Tivoli Enterprise Data Warehouse application, IBM DB2Universal Database™ Enterprise Edition, the Data Warehouse Center, DB2Warehouse Manager, and a user interface for creating and viewing reports.

v The ability to use your choice of data analysis tools to examine your historicaldata. In addition to the report interface, you can analyze your data using otherproducts such as online analytical processing (OLAP), planning, trending,analysis, accounting, and data mining tools.

v The ability to control access to your historical data. You can keep data aboutmultiple customers and data centers in one central data warehouse, but restrictaccess so that customers can see and work with data and reports based only ontheir data and not any other customer’s data. You can also restrict an individualuser’s ability to access data.

v A zero-footprint client. Users can access Tivoli Enterprise Data Warehousereports from any system by using a Web browser. No special software isrequired on the user’s system.

v Internationalization support. Not only is the report interface localized,application programmers can localize the data stored in the central datawarehouse.

Tivoli Enterprise Data Warehouse consists of the following components:v Control serverv Central data warehousev Data martsv Report interface

Control serverThe control server contains the control database for Tivoli Enterprise DataWarehouse from which you manage your data warehouse.

47

The control server has these subcomponents:v A server that controls communication between the control server, the central

data warehouse server, the data mart server, and the report server.v The control database, which contains metadata for Tivoli Enterprise Data

Warehouse.

The control server uses the following parts of the IBM DB2 product, which youmust install manually before installing the control server. These parts are allautomatically installed when you install IBM DB2 Universal Database EnterpriseEdition on a Microsoft Windows system.v DB2 Serverv The Data Warehouse Center, a component that automates data warehouse

processing. You can use the Data Warehouse Center to define the ETL processesthat move and transform data into the central data warehouse and the starschemas used by the data marts. Then, you can use the Data Warehouse Centerto schedule, maintain, and monitor these processes.

v The warehouse agent, part of DB2 Warehouse Manager.

Central data warehouseThe central data warehouse is a DB2 database that contains the historical data foryour enterprise. The system that hosts the central data warehouse is called thecentral data warehouse server. The central data warehouse component uses IBM DB2Universal Database Enterprise Edition, which you must install manually beforeinstalling the control server.

Data martsA separate DB2 database contains the data mart for your enterprise. The data martcomponent requires IBM DB2 Universal Database Enterprise Edition, which youmust install manually before installing the control server. The data mart contains asubset of the historical data from the central data warehouse to satisfy the analysisand reporting needs of a specific department, team, customer, or application. Thesystem that hosts this DB2 database is called the data mart server. Although you canhave many data marts, you can have only one data mart server. IBM TivoliMonitoring for Applications: Siebel eBusiness Applications provides the GMSMonitoring for Siebel data mart.

The warehouse pack for IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications creates the GMS Monitoring for Siebel data mart with the extract,transform, and load (ETL) process, called a data mart ETL. The GMS Monitoringfor Siebel data mart’s structure is suitable for the report interface. After creating it,the warehouse pack loads the data mart with data from the central datawarehouse.

You can modify the GMS Monitoring for Siebel data mart or create new data martswith different data to address a specific reporting needs. You must be familiar withdatabase ETL processes and the internal representation of a data mart as starschemas in the Tivoli Enterprise Data Warehouse databases to modify or create adata mart. Refer to the Enabling an Application for Tivoli Enterprise Data Warehousefor information about database ETL processes and star schemas.

Report interfaceThe Tivoli Enterprise Data Warehouse report interface (RPI) provides tools and agraphical user interface that other Tivoli software products use to create and


display reports. You can use Tivoli Enterprise Data Warehouse to customize reportsprovided with other Tivoli software and to create new reports. You also use thereport interface to control access to data marts and to the reports associated with adata mart. The system on which you install the report interface is called the reportserver.

Use the Work with Reports task group in the report interface to manage users,groups, and data marts for Tivoli Enterprise Data Warehouse or to run, create, andview Tivoli Enterprise Data Warehouse reports. The following sections describehow to do the following tasks:v Working with usersv Working with roles and groupsv Working with data martsv Working with reports

Working with users and user groupsThis section describes tasks associated with managing user groups for TivoliEnterprise Data Warehouse. It includes the following topics:v An overview of users and user groupsv Creating an IBM Console userv An overview of the Tivoli Enterprise Data Warehouse rolesv Assigning roles to a userv Creating a user groupv Assigning users to a user group

About users and user groupsYou control access to data in Tivoli Enterprise Data Warehouse data marts byspecifying which user groups (collections of users) can run the reports that accessthe data in each data mart. Each user in a user group is given access to all reportsthat access the data in the data marts to which that user group has access.

By default, Tivoli Enterprise Data Warehouse provides the TWHAdmin user group,which contains a single user: superadmin. You can customize the TWHAdmin usergroup for the needs of your enterprise.

A user can be assigned to more than one user group.

The Tivoli Enterprise Data Warehouse rolesThe following Tivoli Enterprise Data Warehouse roles control access to tasks andactivities in the Work with Reports task group:v Warehouse Security Administrator

With this role, a user can create and manage groups and data marts. A user withthis role controls access to data marts by assigning users to groups and bygiving groups access to specific data marts. In effect, this role controls access tothe Tivoli Enterprise Data Warehouse data using user groups and data marts.

v Report roles control a user’s ability to create and modify reports for the datamarts his user groups can access. Assign only one of the following roles to eachuser:– Advanced Report Author

Chapter 7. Enabling Tivoli Enterprise Data Warehouse 49

With this role, a user can create, modify, run, and delete public and their ownpersonal reports, and save the output of reports, both public and personal.

– Report AuthorWith this role, a user can run and save the output of public reports and createand modify their own personal reports. They can run public and personalreports, and create, modify, and delete personal reports.

– Report ReaderWith this role, a user can run public reports and view the saved output ofpublic reports.

Creating an IBM Console user

ObjectiveTo create an IBM Console user.

Background informationTivoli Enterprise Data Warehouse is displayed using the IBM Console, which isalso used by other Tivoli software products. A user is given access to tasks in theIBM Console based on the roles that are assigned to that user. One user can haveroles for diverse tasks including administering IBM Console users, managing TivoliEnterprise Data Warehouse user groups and data marts, running and viewing theoutput of Tivoli Enterprise Data Warehouse reports, and performing tasksassociated with other Tivoli software products.

Required authorization rolesuperadmin


When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.

ProcedureTo create an IBM Console user, complete the following steps:1. From the IBM Console, select Administer Users and then Create a User.2. Open the Task Assistant and follow the instructions provided in the online help

to create a user.

Assigning roles to a user

ObjectiveTo assign roles to a user.

Background informationNone.

Required authorization rolesuperuser



When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.

ProcedureTo assign a role to a user, complete the following steps:1. From the IBM Console, select Administer Users and Roles and then Manage

Users.2. From the table of users, click the context menu icon of a user and select

Properties.3. Follow the instructions in the Task Assistant about assigning roles to the user.

Creating a user group

ObjectiveTo create a user group.


Required authorization roleAdministration Authorizations


When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding users to a user group, and deleting a usergroup.

ProcedureTo create a user group, complete the following steps:1. From the IBM console, select Work with Reports and then Manage User

Groups.2. In the Manage User Groups window, click the context menu of Root and select

Create.3. Follow the instructions in the Task Assistant about creating user groups.

Assigning users to a user group

ObjectiveTo assign users to user groups.





When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding or removing users from a user group, anddeleting a user group.

ProcedureTo assign one or more users to a user group, perform the following steps:1. From the IBM Console, select Work with Reports and then Manage User

Groups.2. In the Manage User Groups window, click the context menu icon of a group

and select Properties.3. Follow the instructions in the Task Assistant about assigning users to user

groups.

Assigning user groups to a data mart

ObjectiveTo assign user groups to a data mart.

Background informationGrant access to only those user groups whose users need the data mart to performtasks.



When you finishThe Tivoli Enterprise Data Warehouse online help can guide you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, removing users from a user group, and removing datamart access from a user group.

ProcedureTo assign user groups to a data mart, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Data

Marts.2. In the Manage Data Marts window, in the Data Mart view, click the context

menu icon for the data mart that you want to change and click Properties.3. Select the User Groups tab.

Managing Tivoli Enterprise Data Warehouse reportsTivoli Enterprise Data Warehouse reports display a static view of the data in a datamart. Reports are provided by the warehouse pack for IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications, along with the data marts required tocollect the data used in the report.

This section describes the following tasks:v Running a report manuallyv Automatically running reportsv Modifying default settings for report creation


v Creating a report

For more information about working with reports, see the Tivoli Enterprise DataWarehouse online help.

Tivoli software products using the Tivoli Enterprise Data Warehouse can provideprepackaged reports that enable you to access specific information about yourbusiness environment. All of these reports are listed in the Manage Reports andReport Output task of the Work with Reports task group in the IBM Console. Thisincludes reports from all Tivoli software products that use the Tivoli EnterpriseData Warehouse report interface. Tivoli software products can also provide adifferent reporting interface.

A Tivoli Enterprise Data Warehouse report uses data from a single data mart.

If you have the appropriate role, you can also create additional reports or modifyexisting reports. Before you can create a new report or modify an existing report,you must understand the structure of the underlying warehouse data and of theoperational data that is the source of that data. For information about the structureof data in the data mart and in the central data warehouse, see Enabling anApplication for Tivoli Enterprise Data Warehouse.

The following list includes the name and description of each report provided bythe GMS Monitoring for Siebel data mart.

Daily CPU Usage Health Check for Siebel ServersA health check report that displays the daily CPU usage for each Siebelserver. The report displays minimum, maximum and average of memoryusage in megabytes.

Daily CPU Usage Health Check for Siebel TasksA health check report that displays the daily CPU usage for each Siebeltask. The report displays minimum, maximum and average percentage ofCPU usage.

Daily Memory Usage Health Check for Siebel TasksA health check report that displays the daily memory usage for each Siebeltask. The report displays minimum, maximum and average of memoryusage in megabytes.

Daily CPU Usage for Siebel ServersA daily average report that displays the Siebel servers with highest percentof CPU usage. The report displays CPU usage on the y-axis and theservers on the x-axis.

Daily Memory Usage for Siebel ServersA daily average report that displays the Siebel servers with highestmemory usage. The report displays memory usage in bytes on the y-axisand the servers on the x-axis.

Daily Memory Usage Health Check for Siebel ServersA health check report displays the daily memory usage for each Siebelserver. The report displays minimum, maximum and average percentage ofCPU usage.

Hourly CPU Usage for Siebel ServersAn hourly extreme report that displays the Siebel servers with highestpercent of CPU usage. The report displays CPU usage displays on they-axis and servers on the x-axis.


Monthly CPU Usage for Siebel ServersA monthly average report that displays the Siebel servers with highestCPU. The report displays CPU usage on the y-axis and the servers on thex-axis.

Summary of Daily Status for Siebel ServersA summary report that shows the daily status for each Siebel server. Thisreport displays the status as a percentage of time the server was in each ofthe following states:v Upv Downv Warningv Unknown

Summary of Daily Memory Usage for Siebel ServersThis summary report shows the daily memory usage for each server aswell as aggregated across all servers. It displays minimum, maximum andaverage memory usage in megabytes.

Summary of Daily Memory Usage for Siebel TasksThis summary report that shows the daily memory usage for each task aswell as aggregated across all tasks. It displays minimum, maximum andaverage memory usage in megabytes.

Summary of Daily Status for Siebel GatewaysThis summary report shows the daily status for each Siebel gateway. Itdisplays the status in terms of the percentage of time the gateway was ineach of the following states:v Upv Down

Summary of Daily CPU Usage for Siebel TasksA summary report that displays the daily CPU usage for each task andaggregated usage for all tasks. The report displays minimum, maximumand average percentage of CPU usage.

Summary of Daily Status for Connection BrokerA summary report that displays the daily status for the connection broker.The report displays the status as a percentage of time the connectionbroker was in each of the following states:v Upv Down

Summary of Daily CPU Usage for Siebel ServersA summary report that displays the daily CPU usage for each server andaggregated usage for all servers. The report displays minimum, maximumand average CPU usage in terms of percent CPU utilization.

Weekly CPU Usage for Siebel ServersA weekly average report that displays the Siebel servers with highest CPUusage. The report displays CPU usage on the y-axis and the servers on thex-axis.

Running reports

ObjectiveTo run a report using the report interface.



Required authorization roleAdvRepAuthRole, RepAuthRole, or RepReaderRole


When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as displaying the properties of a report anddeleting a report.

ProcedureTo run a report using the report interface, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Reports

and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

the context menu icon of a report and select Run.

Scheduling reports to run automatically

ObjectiveTo automatically run reports.

Background informationUsing the Tivoli Enterprise Data Warehouse report interface, you can schedule areport to run automatically when the associated data mart is updated. This ensuresthat when you examine the output of the report, it displays the most recent data inthe warehouse.

Required authorization roleAdvRepAuthRole


When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureTo schedule a report to run automatically when the associated data mart isupdated, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Reports

and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

Reports.3. Click the context menu icon of a report and select Properties.

Modifying default settings for reports

ObjectiveTo modify default settings for report creation.


Background informationWhen you create or modify a report, you select predetermined values for the timeframe of the report. The predetermined values of Peak Hours and Weekdaysspecified under Filtering in the Time page of report properties can be modified. Dothis by modifying the information in the control database on the control server.

The default value for Peak Hours is 9:00 am through 5:00 PM, or 0900 to 1700. Thisvalue can be modified to reflect different peak hours if necessary.

The default value for Weekdays is Monday through Friday. This value can also bemodified.

The RPI.TimeFilters table contains the following filters and default filter values.

Table 9. Default time filter names and values

TIME_FILTER_NAME TIME_FILTER_VALUES

Peak hours hour(meas_hour) in (9,10,11,12,13,14,15,16,17)

Weekdays dayofweek(meas_date) between 2 and 6

Required authorization roleAdvRepAuthRole


When you finishFor additional information on the properties of the RPI.TimeFilters table, seeEnabling an Application for Tivoli Enterprise Data Warehouse.

ProcedureTo change the values displayed in the report interface, perform the following steps:1. Connect to the control database (TWH_MD).2. Use an SQL statement similar to the following to modify the values for Peak

Hours or Weekdays in the RPI.TimeFilters table. The following example sets theWeekdays filter to represent Sunday through Thursday:

Update RPI.TimeFilters set TIME_FILTER_VALUES =dayofweek(meas_date) between 1 and 5where TIME_FILTER_NAME =Weekdays

After doing this, when a user selects a Weekdays filter for a report in the reportinterface, the data returned is for Sunday through Thursday.

Note: There is no error-checking for the values inserted into the tables for PeakHours and Weekdays. Therefore, ensure that the information you insert intothe tables is correct. You can save a report that contains incorrect values forthese parameters without receiving an error message. The message is notgenerated until the report is run.

Creating reports

ObjectiveTo create a report.

Background informationYou can receive a message that the name you specified is already in use, even ifyou do not have access to the report with that name.


Required authorization roleAdvRepAuthRole or RepAuthRole

Before you beginEnsure that you use descriptive and meaningful names for the reports you create.Report names are unique across all users of Tivoli Enterprise Data Warehouse.

When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureTo create a report, from the IBM Console, select Work with Reports and thenCreate a Report.


Appendix A. Authorization roles quick reference

Each IBM Tivoli Monitoring for Applications: Siebel eBusiness Applicationsprocedure has a required authorization role. The following table summarizes theseactivities and roles and tells you where to find additional information in thismanual:

Activity Context Required Role For Additional Information

Assign privileges toadministrators and users

Administratorscollection

senior andsiebel_senior

“Setting authorization roles” onpage 7

Discover objects Task library siebel_senior “Discovering Siebel eBusinessApplications resources” onpage 9

Configure Event Server Task library siebel_senior “Configuring event server” onpage 64

Install Logfile Adapter messageformats

Task library siebel_senior “Installing logfile adaptermessage formats” on page 67

Distribute Resource Models Policy region senior “Distribute resource models” onpage 11

View events in the TivoliEnterprise Console

Event console admin Tivoli Enterprise Console Version3.7 documentation

Check the status of a Broker,Server, or Gateway

Policy region siebel_user orsiebel_admin orsiebel_senior

“Checking Siebel eBusinessApplications resources status” onpage 16

View Object properties Policy region siebel_user orsiebel_admin orsiebel_senior

“Viewing Siebel resourceproperties” on page 17

Start or stop a Broker, Gateway,or Server

Task library siebel_admin orsiebel_senior

“Starting or stopping a resource”on page 20

Manage Siebel logs Task library siebel_admin orsiebel_senior

“Managing Siebel Logs” onpage 21

Manage Tivoli logs Task library siebel_admin orsiebel_senior

“Managing Tivoli logs” onpage 23

Edit Tivoli Siebel server objectparameters

Task library siebel_senior “Editing Tivoli Siebel serverobject parameters” on page 24

Create Siebel objects Task library siebel_senior “Creating Siebel objects” onpage 24

Run a task Task library siebel_user orsiebel_admin orsiebel_senior (variesaccording to task)

“Running tasks” on page 30

Customize and save a copy of atask

Task library Admin or Senior orSuper

“Customizing a task” on page 33

Create a job Task library Admin or Senior orSuper

“Creating jobs” on page 35

Run a job Task library siebel_user orsiebel_admin orsiebel_senior (variesaccording to task)

“Running jobs” on page 38

59

Activity Context Required Role For Additional Information

Schedule a job Task library Admin or Senior orSuper

“Scheduling jobs” on page 39

Add a profile manager andprofile

Profile manager Senior or Super “Creating profile managers andprofiles” on page 80

Add a resource model Distributed Monitoringprofile

Senior or Super “Adding default resource modelsto profiles” on page 83

Customize a resource model Distributed Monitoringprofile

Senior or Super “Adding custom resource modelsto profiles” on page 84

Edit a resource model Distributed Monitoringprofile

Senior or Super “Modifying indications” onpage 91

Subscribe endpoints to a profilemanager

Profile manager’spolicy region andsubscriber’s policyregion(s)

Admin or Senior orSuper

“Subscribing resources to profilemanagers” on page 82

Install integration on the TivoliBusiness Systems Manager server

None Administratorauthorization onTBSM server

IBM Tivoli Monitoring forApplications Version 5.1.0:Installation and Setup Guide

Configure Tivoli EnterpriseConsole event system to forwardevents to Tivoli Business SystemsManager

Task Library siebel_senior “Configuring event server” onpage 64

Discover resources for TivoliBusiness Systems Manager

Task Library siebel_senior “Discovering resources for TivoliBusiness Systems Manager” onpage 74


Appendix B. Task quick reference

The IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications tasklibraries are collections of predefined management tasks, such as starting andstopping Siebel servers.

The tasks are grouped into three libraries based on function:v “Siebel Event Tasks task library” on page 61v “Siebel Operational Tasks task library” on page 61v “Siebel Utility Tasks task library” on page 62

For a detailed description of each task, see the task chapters in the IBM TivoliMonitoring for Applications Version 5.1.0: Siebel eBusiness Applications Reference Guide.

Siebel Event Tasks task libraryThe following table provides a list of all the tasks in the Siebel Event Tasks libraryand a brief description of what each does.

Task Description

Configure_Event_Server Adds the class and rule set definitions ofthe selected configuration option to avalid rule base, if the class and rule setdefinitions are not already defined in thespecified rule base.

Configure_Logfile_Broker_Message Formats Installs and uninstalls message formatsin the Tivoli Enterprise Console LogfileAdapter format file for the Siebel broker.

Control_Logfile_Adapter Starts, stops or returns the status of theTivoli Logfile Adapter on an endpoint.

Configure_Logfile_Server_Message Formats Installs and uninstalls message formatsin the Tivoli Enterprise Console LogfileAdapter format file for the Siebel server.

TBSM_Discover Sends a DISCOVER event to TivoliBusiness Systems Manager for eachSiebel administration server andapplication server that IBM TivoliMonitoring for Applications: SiebeleBusiness Applications discovered (or iscurrently managing).

Siebel Operational Tasks task libraryThe following table provides a list of all the tasks in the Siebel Operational Taskslibrary and a brief description of what each does.

Task Description

Archive_Siebel_Logs Enables administrators to view a listing ofthe archived Siebel Server log directoriesand tar, compress, and remove old Siebellog archive directories.

61

Task Description

Check_Server_Status Returns the status of the Siebel Server,Gateway Server, or Siebel ConnectionBroker.

Control_Component_Groups Allows you to bring a component grouponline or take one offline.

Control_Siebel_Tasks Starts, stops, pauses and resumes a Siebeltask.

Run_List_Command Lists current data for components,component groups, or Siebel tasks for aSiebel server.

Run_Srvrmgr_Command Runs any valid srvrmgr command, suchas list servers and enable compgrpcomponent_group, from Siebel commandline interface on a Siebel Applicationserver.

Start_Connection_Broker Starts the specified Siebel ConnectionBroker and updates the server object icon.

Start_Siebel_Gateway Starts the specified Siebel Gateway andupdates the server object icon.

Start_Siebel_Server Starts the specified Siebel Server on anendpoint and updates the server objecticon.

Stop_Connection_Broker Stops the specified Siebel ConnectionBroker and updates the server object icon.

Stop_Siebel_Gateway Stops the specified Siebel Gateway andupdates the server object icon.

Stop_Siebel_Server Stops the specified Siebel Server andupdates the server object icon.

Siebel Utility Tasks task libraryThe following table provides a list of all the tasks in the Siebel Utility Taskslibrary and a brief description of what each does.

Task Description

Discover Locates Siebel servers, gateways, andconnection brokers that you want tomanage in IBM Tivoli Monitoring forApplications: Siebel eBusinessApplications, captures the serverconfiguration information, and configuresit as an object in this product.

Delete Endpoint Utilities Removes the Siebel dependencies and logfiles placed on the endpoint by the IBMTivoli Monitoring for Applications,version 5.1.0: Siebel eBusinessApplications product.


Appendix C. Setting up Tivoli Enterprise Console

This chapter provides information about setting up the Tivoli Enterprise Consolefor use with the IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications. You can skip this chapter if you do not have Tivoli EnterpriseConsole installed or do not want to have the IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications product send events to TivoliEnterprise Console.

Table 10. Setting up the Tivoli Enterprise Console guidelines

Goal Refer to

1. Overview of Tivoli Enterprise Console “Overview of Tivoli Enterprise Console” on page63

2. Configuring Tivoli Enterprise Console to work with IBMTivoli Monitoring for Applications, Version 5.1.0: SiebeleBusiness Applications

“Configuring event server” on page 64

3. Install logfile adapter message formats “Installing logfile adapter message formats” onpage 67

4. Listings of event classes and rules “Listings of event classes and rules” on page 69

Overview of Tivoli Enterprise ConsoleIn distributed computing environments, it is essential to address events andconditions that can lead to problems in a timely and efficient manner. TivoliEnterprise Console provides the tools for the following functions:v Receiving events from various sourcesv Processing events using rulesv Grouping events and delegating the groups selectively to administratorsv Responding to events automaticallyv Viewing events at a console

The following list explains basic concepts of event management. For moreinformation about Tivoli Enterprise Console, refer to the Tivoli Enterprise ConsoleUser’s Guide.

EventsAn event is a structured piece of information. It carries information aboutitself, including the event class, event identity, severity, location (hostwhere the event originated), and description.

Sources of eventsThe Tivoli Enterprise Console accepts events from many sources. Typically,Tivoli software is set up so that events are sent in response to changes inan application or system resource. For example, you can configure resourcemodels to send events as well as to report in other ways.

Event processingThe Tivoli Enterprise Console uses rules to process events. A rule is madeup of a set of logic statements. The rule makes decisions on what to dowith the event based on information provided in the event, such as theevent class, event name, severity, location, and description.

63

A rule’s logic provides one or more responses to the event: it can dropinsignificant events, escalate important events, create new events, orrespond to defined relationships of multiple events (event correlation). Itcan also close an old event when a new event indicates that the originalcondition is resolved.

Event grouping

The Tivoli Enterprise Console can filter events into event groups. Theseevent groups are typically organized by function but can also be organizedby other criteria, such as location or organizational jurisdiction.

Event groups are especially useful for subdividing all Tivoli EnterpriseConsole events into manageable chunks. Administrators can be assigned toone or more event groups.

Viewing events

The Tivoli Enterprise Console includes a console where administrators canwatch for incoming events and respond to them. The event console is auseful tool for managing by exception. The Tivoli Enterprise Console canfilter out normal events, respond automatically to anticipated problems,and forward only those events that require human intervention.

Responses to eventsThe Tivoli Enterprise Console normally can provide automatic responses tomany common events, either by executing response programs or byexecuting Tivoli tasks. For example, you can set a response to respond tothe event that is received when a server becomes unavailable. The specificresponse can be to inform an administrator or to attempt automatic restartsof the server, or a combination of both.

The automatic response mechanism does not work with this product.However, you can write Tivoli Enterprise Console rules that accomplish thesame thing.

Configuring event server

ObjectiveTo configure Tivoli Enterprise Console so you can access and view IBM TivoliMonitoring for Applications: Siebel eBusiness Applications events.

Background informationYou can send the following events to Tivoli Enterprise Console:

Resource model eventsAll resource models provided by IBM Tivoli Monitoring for Applications,Version 5.1.0: Siebel eBusiness Applications provide the option to sendevents to Tivoli Enterprise Console. For example, the Siebel ComponentAvailability resource model can be configured to send an event when acomponent listed in the Running Components parameter is not Running orwhen a component listed in the Online Components parameter is notOnline.

Log file eventsYou can configure the Tivoli Logfile Adapter to send logfile messages fromthe Siebel server and Connection Broker.

You can also configure the event server to use a rule base to forward the events toTivoli Business Systems Manager.


You can configure Tivoli Enterprise Console in any of the following ways:v Use the Configure_Event_Server task from the Tivoli desktopv Use the Configure_Event_Server task from the command line

Using the Configure_Event_Server task is recommended. It performs all TivoliEnterprise Console configuration in a single step. It provides options forconfiguring Tivoli Enterprise Console to accept events from resource models andlog file adapters.

The task does all of the following:v Creates the specified rule base, if it does not already exist.v Copies an existing rule base into a newly created rule base, if you select the

option to do so.v Configures the rule base for the selected option(s) by importing the appropriate

class and rule set files.v Compiles the rule base.v Loads the rule base.v Restarts the event server, if you select the option to do so.

Refer to the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for additional information about this task.

For information on viewing events in the Tivoli Enterprise Console, refer to theTivoli Enterprise Console Version 3.7 documentation.

Required authorization rolesenior

Before you beginThe Tivoli Enterprise Console event server must be installed before you begin thisprocedure. Install Tivoli Event Enablement on each Tivoli Enterprise Console eventserver that you want to forward events to the Tivoli Business Systems Manager.After you install Tivoli Event Enablement on the event server, theConfigure_Event_Server task recognizes it and compiles the rule base thatforwards events to Tivoli Business Systems Manager. See the Tivoli Business SystemsManager Installation and Configuration Guide for more information on installing theTivoli Event Enablement.

When you finishIf you configure the event server to send events to Tivoli Business SystemsManager, define your IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications objects to Tivoli Business Systems Manager with the TBSM_Discovertask, as described in “Discovering resources for Tivoli Business Systems Manager”on page 74.

ProcedureYou can perform this procedure from either the Tivoli command line, Tivolidesktop, or by using Tivoli Enterprise Console commands.

Command Line: See the IBM Tivoli Monitoring for Applications Version 5.1.0: SiebeleBusiness Applications Reference Guide for Configure_Event_Server command lineinformation.

Desktop:

1. Open the Monitoring for Siebel policy region window.

Appendix C. Setting up Tivoli Enterprise Console 65

2. Double-click on the Siebel Event Tasks library icon to display the Siebel EventTasks task library window.

3. Double-click the Siebel_Configure_Event_Server_Job icon to display theConfigure_Event_Server dialog box.

Note: Using the Siebel_Configure_Event_Server_Job is recommended. If yourun the Configure_Event_Server task you must run it against the TivoliEnterprise Console server managed node and increase the timeoutbeyond the default of 60 seconds to either 0 or 300 seconds.

4. Select one of the following options:v Update Existing Rule Base.

—OR—v Create New Rule Base from Existing

—OR—v Create New Rule Base

Additional Information: For a detailed explanation of each option, click the Helpbutton or refer to the IBM Tivoli Monitoring for Applications Version 5.1.0: SiebeleBusiness Applications Reference Guide.

5. Type the name of a new rule base in the New Rule Base Name field. If youtype the name of an existing rule base, this task issues a message and does notupdate the existing rule base.

6. Type the path in the New Rule Base Path field in which the new rule base is tobe created. The task appends the name of the new rule base, as typed in theNew Rule Base Name field, to this field value to determine the complete pathof the new rule base.

7. In the Rule Base Activation window pane, select one of the following options:


v Compile Rule Base Only.—OR—

v Compile and Load Rule Base Only

—OR—v Compile, Load Rule Base, and Restart Server

8. Click the Set and Execute button to run the task and configure the event server.

Installing logfile adapter message formats

ObjectiveTo update the Logfile Adapter Format file with Siebel Server message formats andConnection Broker message formats.

Note: This is an optional procedure

Background informationBefore the Tivoli Logfile Adapter can generate events for Siebel Server logmessages or Connection Broker log messages, you must update the LogfileAdapter Format file to include the Siebel Server message formats and theConnection Broker message formats.

After installing or uninstalling the messages, the Tivoli logfile adapter does thefollowing:v compiles the format file for the adapter.v updates the adapter configuration file with the name of the logfile to be

monitored.v stops and restarts the adapter if it is currently running.

Required authorization rolessiebel_senior

Before you beginThe following software must be installed:v Tivoli Enterprise Console Event Serverv Tivoli Enterprise Console Configuration Facility Adapter

You must push a log file adapter profile to the endpoint before performing thisprocedure.



This procedure consists of two tasks, both in the Siebel Event Tasks task library:v Configure_Logfile_Broker_Message_Formatsv Configure_Logfile_Server_Message_Formats

Before you can monitor log files for servers or connection brokers, you need toupdate the logfile adapter by running at least one of these tasks.

Note: If you decide you are no longer interested in monitoring logfile events, youcan uninstall message formats by selecting the Uninstall option.


Command Line: You can use the wruntask command to run theConfigure_Logfile_Broker_Message_Formats or theConfigure_Logfile_Server_Message_Formats task. See the documentation for thistask in the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for more information.

Desktop: Follow these steps to perform theConfigure_Logfile_Broker_Message_Formats procedure from the Tivoli desktop:1. Open the Monitoring for Siebel policy region window2. Double-click the Siebel Event Tasks library icon to open the task library

window.3. Double-click the Configure_Logfile_Broker_Message_Formats icon to display

the Execute Task window.4. Select an output destination from the Execute Task dialog.5. Select execution targets from the Available Task Endpoints list in the Execute

Task dialog.6. Click Execute to display the Configure_Logfile_Broker_Message_Formats

dialog box.

7. Select one of the following options:v Install Message Formats to install the message formats.

—OR—v Uninstall Message Formats to uninstall the message formats.

8. Click Set and Execute.

Use the following steps to perform the Configure_Logfile_Server_Message_Formatsprocedure from the Tivoli desktop:1. Open the Monitoring for Siebel policy region window.2. Double-click the Siebel Event Tasks library icon to open the task library

window.3. Double-click the Configure_Logfile_Server_Message_Formats icon to display

the Execute Task window.4. Select an output destination from the Execute Task dialog.5. Select execution targets from the Available Task Endpoints list in the Execute

Task dialog.


6. Click Execute to display the Configure_Logfile_Server_Message_Formatsdialog box.

7. Select one of the following options:v Install Message Formats to install the message formats.

—OR—v Uninstall Message Formats to uninstall the message formats.

8. Click Set and Execute.

Listings of event classes and rulesIBM Tivoli Monitoring for Applications: Siebel eBusiness Applications configuresthe Tivoli Enterprise Console to receive events from Siebel server logs, connectionbroker logs and IBM Tivoli Monitoring. The Tivoli Enterprise Console classifies theevents and then matches them against the rule base to determine if the event has apredefined rule (automated response). This section lists the event classes and rulesprovided with IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications.

Siebel Server Logfile eventsThe following events are defined in the Siebel.baroc file for events received fromthe Tivoli Logfile Adapter when monitoring the Siebel server log. For each eventlisted, the corresponding message which is defined in the siebel.fmt file is listedalong with the default severity for the event.

Event Logfile Message Severity

Siebel_Server_Started Startup HARMLESS

Siebel_Server_Stopped Shutting down due toservice stop command

CRITICAL

Siebel_Server_Stopped ServerShutdown CRITICAL

Siebel_Component_Started ProcessCreate HARMLESS

Siebel_Component_Started Created multithreadedserver process

HARMLESS

Siebel_Component_Started Created server process HARMLESS

Siebel_Component_Completed Process was terminated HARMLESS

Siebel_Component_Completed Process completedSuccessfully

HARMLESS



Siebel_Component_Exit_with_Error exited with error code MINOR

Siebel_Component_Exit_with_Error Process exited with error MINOR

Siebel_Component_Exit_Unknown exited with exception MINOR

Connection Broker Logfile eventsThe following events are defined in the Siebel.baroc file for events received fromthe Tivoli Logfile Adapter when monitoring the Connection Broker (Resonate) log.For each event listed, the corresponding message which is defined in the siebel.fmtfile is listed along with the default severity for the event.


Siebel_Connection_Broker_Started Agent started HARMLESS

Siebel_Connection_Broker_Stopped Agent terminated CRITICAL

Siebel_Connection_Broker_Logfile_Event <severity=2> WARNING

Siebel_Connection_Broker_Logfile_Event <severity=1> MINOR

Siebel_Connection_Broker_Logfile_Event <severity=0> CRITICAL

Resource models eventsThe following events are defined in the Siebel_monitors.baroc file for events sentfrom IBM Tivoli Monitoring for Applications: Siebel eBusiness Applicationsresource models. The resource model name, event class, and default severity arelisted.

Resource Model Event Class Severity

Siebel ServerAvailability

Siebel_Server_State_Down CRITICAL


Siebel_Server_State_Warning MINOR

Siebel GatewayAvailability

Siebel_Gateway_Down CRITICAL

Siebel ConnectionBroker Availability

Siebel_ConnectionBroker_Down CRITICAL

Siebel ComponentAvailability

Siebel_Component_RunState_invalid MINOR


Siebel_Server_State_Down CRITICAL


Siebel_Server_State_Warning MINOR

Siebel GatewayAvailability

Siebel_Gateway_Down CRITICAL

Siebel ConnectionBroker Availability

Siebel_ConnectionBroker_Down CRITICAL

Siebel ComponentAvailability

Siebel_Component_RunState_invalid MINOR

Siebel ComponentTask Count

SiebelComponent_RunningTasks_Too_High WARNING


Resource Model Event Class Severity

Siebel ComponentTask Count

SiebelComponent_RunningTasks_Too_Low WARNING

Siebel ComponentTasks Resource Use

Siebel_TaskMemoryHigh WARNING

Siebel ComponentTasks Resource Use

Siebel_TaskCPUHigh WARNING

Siebel Server FileSystem DirectorySize

Siebel_Server_LogFileSystemSize_too_high WARNING

Siebel Server LogFile Directory Size

Siebel_Server_FileSystemSize_too_high WARNING

Siebel ServerResource Use

Siebel_Server_CPU WARNING

Siebel ServerResource Use

Siebel_Server_ProcessSize WARNING

Siebel Tivoli Enterprise Console rulesThe Tivoli Enterprise Console includes a rules engine that processes eventsaccording to a set of rules provided by applications or added by users. IBM TivoliMonitoring for Applications: Siebel eBusiness Applications supplies a set of rulesthat provide correlation of related events. You can edit the existing rules or writenew rules customized for your installation. See the Tivoli Enterprise Console RuleBuilders Guide for more information on how to use the Tivoli Enterprise Consolegraphical rule editor. The following list describes the rules provided by IBM TivoliMonitoring for Applications: Siebel eBusiness Applications.

siebel_broker_close_stoppedCloses the associated Siebel_Connection_Broker_Stopped event when aSiebel_Connection_Broker_Started event is received from the log fileadapter.

siebel_dup_monitorsRemoves duplicate Siebel Resource Model events. A duplicate event isdefined as an event received at the event server within a day of theprevious event. When a duplicate event occurs with the same severity andvalue, the new event is dropped and the repeat_count for the originalevent is incremented by one.

siebel_dup_logfileRemoves duplicate Siebel logfile events. A duplicate event is defined as anevent received at the event server that has the same slot values for thehostname and event class.

If the event is a Siebel Server event, the enterprisename and servernameslots must also match to be considered a duplicate. If the event is aConnection Broker event, the facility, subfacility, and msg slots must matchto be considered a duplicated.

When a duplicate occurs the new event is dropped and the repeat_countfor the original event is incremented by one.

siebel_timeharmlessSets a timer on each Siebel harmless event to 15 minutes. A timer rulecloses the event when the timer expires.


siebel_closeharmlessCloses harmless events after 15 minutes, as set by thetimeharmless_monitor_was rule.

siebel_server_close_startedCloses the associated Siebel_Server_Started event when aSiebel_Server_Stopped event is received from the logfile adapter. It alsocloses the associated Siebel_Server_State_Warning resource model event forthe server, if it exists.

siebel_server_close_stoppedCloses the associated Siebel_Server_Stopped event when aSiebel_Server_Started event is received from the logfile adapter.

It also closes the associated Siebel_Server_State_Down orSiebel_Server_State_Warning resource model event for the server, if itexists.

siebel_component_close_startedCloses the associated Siebel_Component_Started event when aSiebel_Component_Completed, Siebel_Component_Exit_with_Error, orSiebel_Component_Exit_Unknown event is received from the logfileadapter.

siebel_broker_close_startedCloses the associated Siebel_Connection_Broker_Started event when aSiebel_Connection_Broker_Stopped event is received from the logfileadapter.

siebel_rm_server_downCloses the associated Siebel_Server_Started or Siebel_Server_Stoppedlogfile event when a resource model Siebel_Server_State_Down event isreceived.

siebel_rm_server_warningThis rule closes the associated Siebel_Server_Started orSiebel_Server_Stopped logfile event when a resource modelSiebel_Server_State_Warning event is received.

siebel_tmw_clearingCloses the original Siebel resource model event when a TMW_Clearing isreceived. If the clearing event is for the Siebel Server Availability, then thisrule will also close out the associated Siebel_Server_Started orSiebel_Server_Stopped logfile event.


Appendix D. Integrating with Tivoli Business SystemsManager

This chapter provides information on using Tivoli Business Systems Manager tomanage IBM Tivoli Monitoring for Applications: Siebel eBusiness Applicationsresources and events.

Integrating IBM Tivoli Monitoring for Applications: Siebel eBusiness Applicationsinto Tivoli Business Systems Manager includes the following steps:

Goal Refer to

1. Install the IBM Tivoli Monitoring forApplications: Siebel eBusinessApplications integration on the TivoliBusiness Systems Manager server

IBM Tivoli Monitoring for ApplicationsVersion 5.1.0: Installation and Setup Guide

2. Configure your Tivoli EnterpriseConsole event server to forward eventsto Tivoli Business Systems Manager

“Configuring event server” on page 64

3. Define the specific IBM TivoliMonitoring for Applications: SiebeleBusiness Applications objects to TivoliBusiness Systems Manager using adiscovery task.

“Discovering resources for Tivoli BusinessSystems Manager” on page 74

This chapter also provides a list of the IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications tasks that you can run from Tivoli Business SystemsManager and information about uninstalling the IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications integration from Tivoli BusinessSystems Manager.

Understanding Tivoli Business Systems ManagerTivoli Business Systems Manager is a business systems management tool thatenables you to graphically monitor and control interconnected businesscomponents and operating system resources. A business resource and its resourcesare referred to as a Line of Business (LOB).

Tivoli Business Systems Manager consists of the following components:

Tivoli Business Systems Manager management serverThe Tivoli Business Systems Manager management server processes all theavailability data that is collected from various sources. Availability data is insertedin the Tivoli Business Systems Manager database, where intelligent agents providealerts on monitored objects and then broadcast those alerts to Tivoli BusinessSystems Manager workstations. The management server processes all user requeststhat originate from the workstation and includes a database server that is builtaround a Microsoft SQL Server database.

Tivoli Business Systems Manager workstationThe Tivoli Business Systems Manager workstation displays objects in customizedviews, called Line of Business Views. Objects are presented in a hierarchical Tree

73

View so that users can see the relationship between objects. Alerts are overlaid onthe objects when the availability of the object is threatened.

Tivoli Event EnablementTivoli Event Enablement is installed on the Tivoli Enterprise Console event serverand enables the event server to forward events to Tivoli Business SystemsManager. Tivoli Event Enablement defines event classes and rules for handlingevents related to Tivoli Business Systems Manager.

Task serverThe Tivoli Business Systems Manager task server is installed on the TivoliEnterprise Console event server with Tivoli Event Enablement. It receives taskrequests from the Tivoli Business Systems Manager workstation, runs the tasks onthe Tivoli server on which it is installed, and returns the output to Tivoli BusinessSystems Manager.

Discovering resources for Tivoli Business Systems Manager

ObjectiveTo define the specific IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications objects to Tivoli Business Systems Manager

Background informationDuring installation of The IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications integration, you defined the specifics types of objects that you wantTivoli Business Systems Manager to manage. After you define the object types, youmust define the specific objects. You can do this with the TBSM_Discover task. Thistask searches a managed node for objects and sends a DISCOVER event to TivoliBusiness Systems Manager for each object. The TBSM_Discover task also maintainsa list of the objects that have been discovered and alerts Tivoli Business SystemsManager when they have been deleted by sending Tivoli Business SystemsManager a GONE event for each object that no longer exists on the managed node.

You can perform this procedure using the pre-defined Siebel_TBSM_Discover_Jobfor the or the TBSM_Discover task. The recommended method is using theSiebel_TBSM_Discover_Job because it is pre-configured to run against the TivoliEnterprise Console event server. If you use the TBSM_Discover task, you mustconfigure it to run against the Tivoli Enterprise Console event server.


Before you beginDiscover Siebel objects as described in “Discovering Siebel eBusiness Applicationsresources” on page 9.

Install the Tivoli Business Systems Manager integration for IBM Tivoli Monitoringfor Applications: Siebel eBusiness Applications. See the IBM Tivoli Monitoring forApplications Installation and Setup Guide for more information.

Configure your Tivoli Enterprise Console event server, as described in“Configuring event server” on page 64.

When you finishUse Tivoli Business Systems Manager to view and manage your IBM TivoliMonitoring for Applications: Siebel eBusiness Applications objects. For informationon using Tivoli Business Systems Manager, see the Tivoli Business Systems Manager


User’s Guide. For information on the IBM Tivoli Monitoring for Applications: SiebeleBusiness Applications tasks that you can run from Tivoli Business SystemsManager, see “Working with Tivoli Business Systems Manager”.

When the task completes successfully, you receive a list of the DISCOVER andGONE events that were sent to Tivoli Business Systems Manager and the followingtrace log is generated on the Tivoli Enterprise Console server:

$DBDIR/GMS/log/trace_Siebel_tbsm_discover.log

ProcedureYou can perform this procedure from the command line or the Tivoli desktop.

Command line: Use the wruntask command to run the TBSM_Discover task fromthe command line. For information on the CLI syntax for this task, see the IBMTivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness Applications ReferenceGuide Reference Guide.

Desktop: Use the following steps to run this procedure as a job:1. In the Siebel Event Tasks task library, double-click the

Siebel_TBSM_Discover_Job icon.

Working with Tivoli Business Systems ManagerIn addition to using Tivoli Business Systems Manager to monitor the state of yourresources, you can also run tasks on the objects. IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications tasks are loaded into Tivoli BusinessSystems Manager when you install the IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications integration. These tasks appear on the SiebelOperational Tasks menus for the different object types (SIEBELServer,SIEBELBroker, and SIEBELGateway). This Siebel Operational Tasks menu isdisplayed when you right-click an object.

You can perform the following Siebel server operational tasks from Tivoli BusinessSystems Manager:v Archive_Siebel_Logsv Check_Server_Statusv Control_Component_Groupsv Control_Siebel_Tasksv Run_List_Commandv Run_Srvrmgr_Commandv Start_Siebel_Serverv Stop_Siebel_Server

You can perform the following Siebel gateway operational tasks from TivoliBusiness Systems Manager:v Start_Siebel_Gatewayv Stop_Siebel_Gateway

You can perform the following connection broker operational tasks from TivoliBusiness Systems Manager:v Start_Connection_Brokerv Stop_Connection

Appendix D. Integrating with Tivoli Business Systems Manager 75

Tivoli Business Systems Manager also monitors the status of resource models.Events generated by the resource models are forwarded from Tivoli EnterpriseConsole to Tivoli Business Systems Manager.

For more information about these tasks and resource models, see the IBM TivoliMonitoring for Applications Version 5.1.0: Siebel eBusiness Applications Reference Guide.

Uninstalling IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications integration from Tivoli Business Systems Manager

ObjectiveTo remove the IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications integration from Tivoli Business Systems Manager.

Background informationUninstalling the IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications integration removes the IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications object definitions and objects from Tivoli BusinessSystems Manager.

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerdatabase server.

Before you beginNot applicable

When you finishCheck the following log file to verify IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications was uninstalled from Tivoli Business SystemsManage:

c:\temp\GMS\trace_siebel_tbsm_uninstall.log

ProcedureUse the following steps to perform this procedure:1. On the Tivoli Business Systems Manager server, from a command prompt,

navigate to the directory where you installed the IBM Tivoli Monitoring forApplications: Siebel eBusiness Applications integration. The default directory isC:\tivoli\siebel.

2. Type uninstall to start the uninstallation wizard.3. Click Next on the welcome screen.4. The installation location for the Tivoli Business Systems Manager integration is

displayed. Click Next to continue.5. Provide the following Microsoft SQL Server information and click Next to start

the uninstallation:

SQL ServerThe name of the SQL server with which this Tivoli Business SystemsManager server is associated

SQL UseridThe SQL user ID.

SQL PasswordThe password for the user ID defined above.


6. Click Finish to exit the installation wizard.

Appendix D. Integrating with Tivoli Business Systems Manager 77

Appendix E. Using IBM Tivoli Monitoring

This appendix provides information about setting up and using IBM TivoliMonitoring.

Setting up IBM Tivoli MonitoringIBM Tivoli Monitoring provides the monitoring tools, like resource models, youneed to manage your Siebel eBusiness Applications resources. The followingsections describe setting up IBM Tivoli Monitoring.

Table 11 provides guidelines for the order in which you set up monitoringinformation and the required procedures for setting up IBM Tivoli Monitoring.When you become more familiar with IBM Tivoli Monitoring, you will discoveradditional ways of working with resource models that meet the needs of yourenvironment.

Note: For additional or advanced information on IBM Tivoli Monitoring in theTivoli environment, see the IBM Tivoli Monitoring User’s Guide.

Table 11. Monitoring resources and applications guidelines

Goal See

1. Set up profile managers and profiles toorganize your resource models. This makesthe distribution of resource models moreefficient. You might need to set up multipleprofile managers and profiles within theprofile managers to meet the needs of yourenvironment.

“Creating profile managers andprofiles” on page 80

2. Subscribe endpoints to the profile manager.This determines which resources receive aprofile when the profile is distributed.Profiles contain resource models to runagainst the endpoints (see Step 3).

“Subscribing resources to profilemanagers” on page 82

3. Populate each profile manager/profile withresource models for the resource that youwant to monitor. Include resource modelswith the default values or customize thedefault values to meet the needs of yourenvironment.

You must specify the following informationif you customize your resource models:

v Platform type

v Cycle time

v Threshold values

“Adding default resource modelsto profiles” on page 83

“Adding custom resource modelsto profiles” on page 84

79

Table 11. Monitoring resources and applications guidelines (continued)

Goal See

4. For each resource model in your profile, dothe following:

v Determine how the resource modelgenerates an event by specifyingthresholds for each indication for thatresource model.

v Specify if you want a recovery actionwhen a specific event occurs.

v Specify if you want corrective or reportingtasks for an event.

v Specify if you want to receive informationon a specific event through a notice.

v Specify if you want to customize theresource model parameters to optimize themonitoring process.

v Specify when the monitoring occurs.

v Specify if you want the monitoring tooccur at specific time periods on selecteddays.

v Specify if you want the collected log datawritten to a local database.

“Modifying indications” on page91

“Editing a built-in action” on page95

“Specifying tasks for an indication”on page 96

“Sending a notice to administratorswhen an event occurs” on page 97

“Modifying parameters” on page99

“Creating scheduling rules” onpage 100

“Modifying the schedulingmonitoring period” on page 102

“Modifying data logging settings”on page 103

5. For each profile in your profile manager, dothe following:

v Specify the subscribers that you want todistribute the monitoring profile to anddistribute the profile.

v Specify the subscribers that you want todistribute the monitoring profile to whileusing MDist2.

“Distributing profiles from thedesktop” on page 85

“Distributing profiles usingMDist2” on page 87

Creating profile managers and profiles

ObjectiveTo create profile managers and profiles so you can organize and distribute yourresource models more efficiently.

Background InformationA monitoring profile is a group of defined resource models that you can distribute(download or push) to a subscribed (marked to receive) managed resource in aprofile manager.

In addition to activating default resource models, profile managers and profiles cangroup resources to enable simultaneous monitoring of multiple resources. You canorganize the profile managers hierarchically. The profile manager is the top level ofthe organization and contains specific profiles that contain specific resourcemodels. Instances are then subscribed to the profile managers, which enable themonitoring information to be channeled to those resources.


You can create an unlimited number of profile managers, but it is recommendedthat they reflect some logical or functional grouping of resources or the business’sorganizational structure. For example, profile managers could be labeled Sales andMarketing, Administration and Finance, and Operations to reflect a businessorganization.

You can create a dataless profile manager that distributes profiles without regard tothe existence of an instance on its subscribers. A dataless profile managerdistributes to the system files on endpoints and other managed resources that havea profile database. However, it bypasses the profile database on these systems.Therefore, profiles are available only with database profile managers. A profilemanager (database or dataless) cannot subscribe to a dataless profile manager.Likewise, dataless profile managers cannot distribute to other profile managersbecause they require profiles to be written to a profile database.

Required Authorization Roleadmin

Before You BeginSet up the Tmw2kProfile managed resource types. Refer to the IBM TivoliMonitoring User’s Guide for information.

When You FinishAdd resource models to the profile. See “Adding default resource models toprofiles” on page 83 or “Adding custom resource models to profiles” on page 84.


Command Line:

1. Use the wcrtprfmgr command to create a profile manager. For example, tocreate a profile manager called ProfMgr2 in the TestRegion policy region, enterthe following command:wcrtprfmgr @PolicyRegion:TestRegion ProfMgr2

2. Optional: Use the wsetpm command to make the policy manager operate indataless mode. For example, to make the profile manager ProfMgr2 dataless,enter the following command:wsetpm -d @ProfileManager:ProfMgr2

where:

-d Specifies that the profile manager operates in a dataless mode.3. Use the wcrtprf command to create a profile. For example, to create a profile

called MarketingProf2 in the ProfMgr2 profile manager, enter the followingcommand:wcrtprf @ProfileManager:ProfMgr2 MarketingProfile MarketingProf2

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual.

Desktop:

1. Open the Policy Region dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.

Appendix E. Using IBM Tivoli Monitoring 81

2. Select Create → Profile Manager to open the Create Profile Manager dialogbox.

3. Type a unique name in the Name/Icon Label text box.4. Optional : Select the Dataless Endpoint Mode check box to create the profile

manager in dataless mode.5. Click the Create & Close button to close the Create Profile Manager dialog

box.Additional Information: In the following example, the policy region contains twoprofile manager icons, Manufacturing and Operations. The Manufacturingprofile manager is defined as dataless (the feathers under the Manufacturingprofile manager indicates that it is a dataless profile manager).

6. Double-click the profile manager icon to open the Profile Manager window.7. Select Create → Profile to open the Create Profile dialog box.8. Type a unique name for the profile in the Name/Icon text box.9. Select the Tmw2kProfile resource from the Type list.

10. Click the Create & Close button. An icon for the new profile is displayed inthe Profiles area of the Profile Manager window.

Subscribing resources to profile managers

ObjectiveTo add managed resources to a monitoring profile so administrators can definewhich resource to monitor.

Background informationSubscribing resources to a profile manager determines which resources receive aprofile when the profile is distributed. IBM Tivoli Monitoring uses the list ofsubscribers to determine which systems are monitored. To add a subscriber to adistributed monitoring profile, you must add the subscriber to the profile manager.

Note: Resources can also be subscribed to profiles from the IBM Tivoli MonitoringProfile dialog. See “Distributing profiles from the desktop” on page 85.

Required authorization roleadmin

Before you beginCreate a monitoring profile with monitoring sources. See “Creating profilemanagers and profiles” on page 80 for information.


When you finishDistribute the monitoring profile to the subscribed resource. See “Distributingprofiles from the desktop” on page 85 for information.


Command Line: Use the wsub command to add subscribers to the profilemanager.

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual .

Desktop:

1. Open the Policy Region dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.

2. Double-click a profile manager icon to open the Profile Manager dialog box.3. Select Profile Manager → Subscribers to open the Subscribers dialog box.4. Select the subscribers to receive the profile distribution from the Available to

become Subscribers scrolling list.5. Click the left-arrow button to move the selected subscribers to the Current

Subscribers scrolling list.6. Click the Set Subscriptions & Close button to add the subscribers. Subscribers

are displayed in the Subscribers field of the Profile Manager dialog box.

Adding default resource models to profiles

ObjectiveTo add a resource model to a profile using its default values so you can run theresource model immediately.

Background informationA resource model captures and returns information about a resource or application.You set up resource models and distribute them to endpoints. Each resource modelmonitors multiple resources. Choose the resource models to add to a profile basedon the resources you want to monitor. Adding one or more of these resourcemodels to a profile allows you to begin monitoring resources immediately.

We recommend that you put all of the resource models that you are going todistribute to the same endpoint in a single profile because the distribution occurson a per-profile basis.


Before you beginv Create a profile manager and profile. See “Creating profile managers and

profiles” on page 80 for information.v Add subscribers to a profile manager. See “Subscribing resources to profile

managers” on page 82 for information.v See the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness

Applications Reference Guide for detailed information about each resource model.


When you finishDistribute the profile. See “Distributing profiles from the desktop” on page 85.


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon to open the profile manager.d. Double-click the profile icon to which you want to add a customized

resource model.2. Click Add With Defaults to open the Add Resource Models to Profile dialog

box.3. Select the resource model category from the Category drop-down list.4. Select the resource model you want from the Resource Model drop-down list.5. Click Add & Close. The resource model is added to the IBM Tivoli

Monitoring Profile.

Adding custom resource models to profiles

ObjectiveTo specify the platform, cycle time, and threshold values that customize a resourcemodel to meet the needs of your environment and add the resource model to aprofile.

Background informationA resource model captures and returns information about a resource or application.You set up resource models and distributed them to endpoints. A number ofpredefined resource models are installed with the product. To customize basicsettings of a resource model, specify the platform type, cycle time, and thresholdvalues appropriate for your environment. Each resource model monitors a differentresource. Choose the resource models to add to a profile based on the resourcesyou want to monitor. Adding one or more of these resource models to a profileenables you to begin monitoring resources immediately.

We recommend that you put all of the resource monitors that you want todistribute to the same endpoint in a single profile because the distribution occursat the individual profile level.




managers” on page 82 for information.


v See the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for detailed information about each resource model.

When you finishDistribute the profile. See “Distributing profiles from the desktop”.


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon to open the Profile Manager dialog

box.d. Double-click the profile icon to which you want to add a customized

resource model.2. Click Add to open the Add Resource Models to Profile dialog box.3. Select the resource model category from the Category drop-down list.4. Select the desired resource model from the Resource Model drop-down list.5. Set the frequency with which the resource model monitors the data in the

Cycle Time text box. Enter a time in seconds.6. Use the following steps to change any of the threshold values:

a. Select the Threshold Name that you want to change.Additional Information: The description box displays a description of thethreshold that you selected. A dialog box above the description displays thecurrently assigned threshold value. For the default threshold values see theIBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide.

b. Change the currently assigned threshold value to a value appropriate toyour requirements.

c. Click Apply to set and display the new value in the Threshold Value dialogbox.

7. Optional: Click Indications or Parameters to make required modifications toindications and parameters and click Schedule to add schedule information.Additional information: If you do not perform this step, the indications andparameters use the default values shipped with the resource models. See“Modifying indications” on page 91, “Modifying parameters” on page 99, and“Modifying the scheduling monitoring period” on page 102 for information.

8. Optional. Turn on logging necessary for the IBM Tivoli Monitoring Web HealthConsole and Tivoli Enterprise Data Warehouse.

9. Click Add & Close to save your changes. The IBM Tivoli Monitoring Profiledialog box now shows the customized resource model.

Distributing profiles from the desktop

ObjectiveTo distribute profiles to specified subscribers.


Background informationYou can distribute profiles to the following groups:

Next level of subscribersDistributes the profile only to the subscribers named in the Distribute toThese Subscribers: scrolling list of the Distribute Profile dialog box. Thisoption does not distribute to subscribers at lower levels of the hierarchy.Perform the distribution process from profile managers at more than onelevel to reach all the profile endpoints if a profile manager with subscribersresides at the next lower level.

All levels of subscribersDistributes the profile to all subscribers in the hierarchy. Consider thefollowing example. You have a profile in which a dataless profile manageris subscribed to a profile manager , and the dataless profile manager has asubscribed endpoint. If you distribute to the next level of subscribers, theprofile manager distributes the profile only to the dataless profile manager.If you distribute to all levels of subscribers, the profile manager distributesthe profile to the dataless profile manager and to the endpoint.

Select this option if you want to distribute a profile in which your resourceis the only subscriber.




managers” on page 82 for information.v Add a resource model to a profile. See “Adding default resource models to

profiles” on page 83 and“Adding custom resource models to profiles” on page 84for information.


When you finish

ProcedureYou can perform this procedure from the Tivoli desktop only.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon you want to open the Profile

Manager dialog box.d. Double-click the profile you want to distribute to open the IBM Tivoli

Monitoring Profile dialog box.2. Click Profile → Distribute. The Distribute Profile dialog box opens.3. Select one of the Distribute To options based on the following descriptions:

Next level of subscribersDistributes the profile only to the subscribers named in the Distributeto These Subscribers: scrolling list of the Distribute Profile dialog box.


This selection does not distribute to subscribers at lower levels of thehierarchy. Perform the distribution process from profile managers atmore than one level to reach all the profile endpoints if a profilemanager with subscribers resides at the next lower level.

All levels of subscribersDistributes the profile to all subscribers in the hierarchy. Consider thefollowing example. You have a profile in which a dataless profilemanager is subscribed to a profile manager , and the dataless profilemanager has a subscribed endpoint. If you distribute to the next levelof subscribers, the profile manager distributes the profile only to thedataless profile manager. If you distribute to all levels of subscribers,the profile manager distributes the profile to the dataless profilemanager and to the endpoint.

Select this option if you want to distribute a profile in which yourresource is the only subscriber.

4. Select Make each subscriber’s profile an EXACT COPY of this profile fromthe Distribution Will options.Additional Information: This option overwrites the subscriber’s profile with anexact copy of the profile that you are distributing.

Note: Always select the Make each subscriber’s profile an EXACT COPY ofthis profile option when you distribute a profile to a Tivoli EnterpriseConsole endpoint. Do not select the Preserve modifications insubscriber’s copies of the profile option.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profile dialogbox, saves the settings you made, and returns to the IBM TivoliMonitoring Profile dialog box.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile dialog box open.

ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide.

Distributing profiles using MDist2

ObjectiveTo circulate copies of the monitoring profile to subscribers while using MDist2 sothat administrators and users can activate the monitoring process.


Background informationIBM Tivoli Monitoring uses Multiplexed Distribution (MDist2) to performasynchronous profile data transfers through a hierarchy of repeaters. MDist2returns a sequence of responses containing the distribution status from eachendpoint to the application initiating the distribution. These responses are sentback to IBM Tivoli Monitoring in a log file, on the MDist2 command line, orthrough the MDist2 GUI.

IBM Tivoli Monitoring uses the following MDist2 functions:

Asynchronous deliveryIBM Tivoli Monitoring submits a distribution request and immediatelyreceives a distribution identifier and confirmation that the distribution is inprogress. MDist2 uses the callback function to send the final distributionstatus for each endpoint when it completes each endpoint distributioninstead of waiting until all endpoints are distributed.

Assured deliveryAssures that distributed profiles are delivered to the endpoints when thereare network interruptions, computer shutdowns, or disconnectedendpoints. Assured delivery tries to reestablish the connections until it iseither successful or the distribution time expires. The distribution begins atthe point where it was interrupted.

Check-point and restartAssures that an interrupted data stream resumes from the last successfulcheckpoint. You do not have to re-send all the IBM Tivoli MonitoringProfile data when the distribution resumes, but only the data that was notsent when the interruption occurred.

Data depotingStores segments of the profile at a depot close to the endpoint so theendpoints can retrieve the data from the depot instead of from the sourcehost. This reduces network traffic and speeds up the distribution.





profiles” on page 83 and“Adding custom resource models to profiles” on page 84for information.


When you finishNone


Command Line: Use the wdistrib command to distribute the profile to thesubscribers of the profile manager.


This command updates subscriber databases and configuration files. If nosubscriber is specified, wdistrib updates all subscribers. The syntax variesdepending on the version of Tivoli management region that you installed. Refer tothe Tivoli Management Framework Reference Manual for more information about thewdistrib command.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon you want to open the Profile

Manager dialog box.d. Double-click the profile you want to distribute to open the IBM Tivoli

Monitoring Profile dialog box.2. Select Profile → Distribute to display the Distribute Profile dialog box.3. Select one of the Distribute To options based on the following descriptions:

v Next Level of Subscribers Distributes the profile only to the subscribersnamed in the Distribute to These Subscribers: scrolling list of the DistributeProfile dialog box. This selection does not distribute to subscribers at lowerlevels of the hierarchy. Perform the distribution process from profilemanagers at more than one level to reach all the profile endpoints if a profilemanager with subscribers resides at the next lower level.

v All Levels of Subscribers Distributes the profile to all subscribers in thehierarchy. Consider the following example. You have a profile in which adataless profile manager is subscribed to a profile manager , and the datalessprofile manager has a subscribed endpoint. If you distribute to the next levelof subscribers, the profile manager distributes the profile only to the datalessprofile manager. If you distribute to all levels of subscribers, the profilemanager distributes the profile to the dataless profile manager and to theendpoint.Select this option if you want to distribute a profile in which your resource isthe only subscriber.

4. Select one of the Distribution Will options based on the following descriptions:v Preserve modifications in subscribers’ copy of the profile retains changes to

existing monitors in each copy of the profile. If you edit the configuration ofa monitor in the subscriber’s copy, those changes are written to every copy ofthat profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed.

5. Verify that the Distribute To These Subscribers list includes only thosesubscribers to receive the profile. Use the left and right arrows to move selectedsubscribers between lists.

6. Click the Distribute & Close button to begin the distribution and close theDistribute Profile window.

7. Optional : Schedule when the distribution will occur by completing thefollowing steps:a. Click the Schedule button to display the Add Scheduled Job dialog box.b. Set the job options as needed or See “Modifying the scheduling monitoring

period” on page 102 for more information.c. Click the Schedule Job & Close button to set the schedule.


8. Click the Distribute & Close button to begin the distribution and close theDistribute Profile dialog box.

9. Select Profile → Close to close the IBM Tivoli Monitoring Profile dialog box.

Rerunning failed profile distributions

ObjectiveTo verify that the distribution to an endpoint failed so that you can rerun thedistribution for the failed endpoint.

Background informationWhen a distribution fails, IBM Tivoli Monitoring creates a profile manager thatcontains the endpoint subscribers that failed.

When you successfully redistribute profiles, the software deletes the profilemanager that it created for the failed distribution. A wholly or partiallyunsuccessful redistribution retains the profile manager containing only thesubscribers that were unsuccessful in the redistribution. Continue the process ofcorrecting the errors and retrying the distribution until the profile is successfullydistributed to all endpoints.


Before you beginNone

When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.

2. Select View → Refresh from the Policy Region dialog box to see the new profilemanagers.

3. Review the new profile manager names to determine and correct the cause ofthe failure. The following profile manager names are derived from a faileddistribution:v The failed distribution creates the following profile manager name due to a

Bad_Interpreter error:OriginalProfileName_Push_Failed_Bad_Interpreter

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

The AMW089E error message is displayed at this point, indicatingthat the resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX-T endpoint.


v The failed distribution creates the following profile manager name due toany other error:OriginalProfileName_Distribution_Failed

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

4. Subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile.

Note: This can be done only if the profile manager used for the originaldistribution was not a dataless endpoint.

5. Distribute the original profile to the failed endpoints by selecting these profilemanagers as the target for the distribution. You can also edit the profilemanagers to delete an endpoint from a group of failed endpoints beforeretrying the distribution.

Working with IBM Tivoli MonitoringThis section provides information about using the resource models that areincluded in IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications.You can customize various management aspects of the resource models so thatthey have the appropriate settings for your monitoring environment. Customizinga resource model involves the following steps:v “Modifying indications”v “Adding or removing a built-in action” on page 93v “Editing a built-in action” on page 95v “Specifying tasks for an indication” on page 96v “Sending a notice to administrators when an event occurs” on page 97v “Modifying parameters” on page 99v “Creating scheduling rules” on page 100v “Modifying the scheduling monitoring period” on page 102v “Modifying data logging settings” on page 103v “Managing profiles and resource models at endpoints” on page 105v “Managing IBM Tivoli monitoring gateways” on page 106v “Determining which resource models are running on endpoints” on page 106v “Viewing resource model results with the IBM Tivoli Web Health Console” on

page 107

Modifying indications

ObjectiveTo modify indication rules so that resources are monitored and events aregenerated relevant to your environment.

Background informationEach resource model triggers an indication if certain conditions defined by theresource model’s thresholds are not satisfied during the monitoring cycle. Eachresource model has predefined thresholds that meet the business needs of mostcustomers; however, you might have specific requirements for which thesethresholds are not appropriate; therefore, you can adjust these values as needed.






profiles” on page 83 for information.

When you finishDistribute the profile to which the resource model belongs. See “Distributingprofiles from the desktop” on page 85.

Optional: Continue customizing the resource model:v Specify if you want a recovery action when a specific event occurs. See “Editing

a built-in action” on page 95v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 96v Specify if you want to receive information on a specific event through a notice.

See “Sending a notice to administrators when an event occurs” on page 97v Specify if you want to customize your parameters to optimize the monitoring

process. See “Modifying parameters” on page 99v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules” on page 100v Determine when the monitoring of resource models takes place. See “Modifying

the scheduling monitoring period” on page 102v Specify if you want the log data collected by a resource model written to a local

database. See “Modifying data logging settings” on page 103

ProcedureYou can perform this procedure from either the command line or the Tivolidesktop.

Command line: Use the wdmeditprf command to customize a resource model fora profile.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize from the IBM Tivoli

Monitoring Profile window.3. Click Edit to open the Edit Resource Model dialog.4. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.5. Select the indication for which you want to customize the values of the event

associated with that indication.


6. Apply the changes to the values that are appropriate to your requirements. Seethe IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for the default resource model settings.You can customize the following fields. For more information about thesefields, see the IBM Tivoli Monitoring documentation.

Number of occurrencesSpecifies the number of consecutive times the problem occurs beforethe software generates an indication. You can change this value tospecify the number of times a problem occurs before an indication isgenerated.

Number of holesDetermines how many cycles that do not produce an indication canoccur between cycles that do produce an indication. This determines ifthe occurrences of an indication are consecutive.

Use the value for the Number of Holes in conjunction with theNumber of Occurrences parameter and the Cycle Time to define atime window for the generation of an event.

Send TEC EventsSelect this check box to send an event to the Tivoli Enterprise Console.You must have Tivoli Enterprise Console installed and configured.

Send to TBSMSends events to Tivoli Business Systems Manager. You do not need toselect this box. If you have Tivoli Business Systems Manager installedand configured, Tivoli Enterprise Console automatically forwardsevents to Tivoli Business Systems Manager.

7. Click Apply Changes & Close to save your changes to the indication.

Adding or removing a built-in action

ObjectiveTo add a built-in action so administrators and users can reinstate an event’srecovery actions or to remove a built-in action so administrators and users canclear an event’s recovery actions.

Background informationA built-in action is a recovery action for an event. The actions take positive steps toremedy the situation, or ensures distribution of information about the event to theappropriate authorities or entities.

The Tivoli software has predefined actions for certain events. An action is eitherthe execution of a common information model (CIM) class method, or theexecution of a program. For example, an event that detects the failure of a servicehas the restart of that service as its built-in action. IBM Tivoli Monitoring detectsthe failure of a service and automatically restarts it. Built-in actions are defined bydefault as part of an event when the resource model is created in the IBM TivoliMonitoring Workbench. See the IBM Tivoli Monitoring documentation for moreinformation.



Before you beginv You must have previously removed a built-in action to activate the Built-In

option for adding a built-in action. Use this procedure to reinstate the previouslyremoved built-in action.

v Create a profile manager and profile. See “Creating profile managers andprofiles” on page 80 for information.

v Add subscribers to a profile manager. See “Subscribing resources to profilemanagers” on page 82 for information.

v Add a resource model to a profile. See “Adding default resource models toprofiles” on page 83 for information.


Optional: Continue customizing the resource model:v Specify if you want a recovery action when a specific event occurs. See “Editing








ProcedureYou can perform this procedure from the Tivoli desktop.1. Select a resource model from the IBM Tivoli Monitoring Profile window and

click Edit to open the Edit Resource Model window.2. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.3. Select the indication that has the associated events you want to add or remove.4. Select the action from the Action List panel of the Indications and Actions

window.5. Click Remove to remove the action from the list.

— or —Click Built-in to open the Add Action window.a. Select the action you want to run when an event occurs.b. Enter the number of times you want the action to perform when an

indication generates an event in the Retry field.Additional information: If you set the Retry field to zero, the productcontinually tries to perform the action until the action is successful.

c. Click one of the following options:


Add Adds the selected action with the values specified and keeps theAdd Action window open.

Add & CloseAdds the selected action and closes the Add Action window.

6.

Click one of the following buttons:

Apply ChangesSaves the changes made to the built-in actions and leaves theIndications and Actions window open.

Apply Changes and CloseCloses the Indications and Actions window and saves the changesmade to the built-in actions.

Editing a built-in action

ObjectiveTo edit a default (built-in) action that takes recovery events for an event.








Optional: Continue customizing the resource model:v Specify if you want to customize your thresholds and events to optimize the

monitoring process. See “Modifying indications” on page 91v Specify if you want corrective or reporting tasks for an event. See “Specifying








ProcedureYou can perform this procedure from the Tivoli desktop.1. Select a resource model from the IBM Tivoli Monitoring Profile window and

click Edit to open the Edit Resource Model window.2. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.3. Select the indication that has the associated events you want to customize.4. Select the action to edit from the Action List panel of the Indications and

Actions window.5. Click Edit to open the Edit Current Action window.6. Enter the number of times you want the action to perform when an indication

generates an event in the Retry field.Additional information: If you set the Retry field to zero, the product continuallytries to perform the action until the action is successful.

7. Click Apply next to the Retry field to apply the changes.8. Click one of the following options:

Close Closes the Edit Current Action window and saves the original retryvalue.

Modify & CloseCloses the Edit Current Action window and saves the modified retryvalue.

Specifying tasks for an indication

ObjectiveTo specify a task so administrators and users can determine corrective or reportingtasks for an event.

Background informationYou can select one or more task to perform when an indication generates an event.You can select one or more task for each event. These tasks can access the IBMTivoli Monitoring event name and thresholds by accessing the environmentvariables.





profiles” on page 83 and for information.



monitoring process. See “Modifying indications” on page 91


v Specify if you want a recovery action when a specific event occurs. See “Editinga built-in action” on page 95

v Specify if you want to receive information on a specific event through a notice.See “Sending a notice to administrators when an event occurs”

v Specify if you want to customize your parameters to optimize the monitoringprocess. See “Modifying parameters” on page 99

v Specify if you want the monitoring of resource models to take place on specifictime periods of selected days. See “Creating scheduling rules” on page 100

v Determine when the monitoring of resource models takes place. See “Modifyingthe scheduling monitoring period” on page 102

v Specify if you want the log data collected by a resource model written to a localdatabase. See “Modifying data logging settings” on page 103



Tivoli desktop:

1. Select a resource model from the IBM Tivoli Monitoring Profile window andclick Edit to open the Edit Resource Model window.

2. Click Indications. The Indications and Actions window opens and displays theindications appropriate to the selected resource model.

3. Select the indication that you want to generate a task from the Indications andActions window.

4. Click Tasks in the Action List window. The Tasks window opens.5. Double-click the appropriate task library from the scroll list of the Libraries

panel. The tasks contained in the library are displayed in the Tasks panel.6. Double-click the appropriate task in the Tasks panel.7. Specify the appropriate parameters in the Configure Task window.

Additional Information: Run the wlsnotif -g command to see the available NoticeGroups.

8. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.

Sending a notice to administrators when an event occurs

ObjectiveTo send a notice in response to an event so administrators can take the appropriateactions or responses.

Background informationYou can select the IBM Tivoli Monitoring Utility task to send notices in response toan event.







You must create an administrator before you can subscribe the administrator to anotice group. For information about creating administrators, see the TivoliManagement Framework, Version 3.7.1: Reference Manual.



monitoring process. See “Modifying indications” on page 91v Specify if you want a recovery action when a specific event occurs. See “Editing


tasks for an indication” on page 96v Specify if you want to customize your parameters to optimize the monitoring







Tivoli desktop:


2. Click Indications. The Indications and Actions window opens and displays theindications appropriate to the selected resource model.

3. Select the indication that you want to generate a task from the Indications andActions window.

4. Click Tasks in the Action List window. The Tasks window opens.5. Double-click the IBM Tivoli Monitoring Utility Tasks library in the scroll list

of the Libraries panel. The tasks contained in the IBM Tivoli Monitoring UtilityTasks library are displayed in the Tasks panel.

6. Double-click dm_mn_send_notice in the Tasks panel. The Configure Taskwindow opens.

7. Specify the appropriate parameters in the Configure Task window.Additional Information: Run the wlsnotif -g command to see the available NoticeGroups.


8. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.

Modifying parameters

ObjectiveTo customize the parameters of a resource model so administrators and users canoptimize the monitoring process.

Background informationSome resource models have one or more parameters. Each parameter can take theform of a list of strings, a list of numeric values, a Boolean list of predeterminedvalues from which you can make any combination of selections, or a choice list ofmutually exclusive alternatives.











See “Sending a notice to administrators when an event occurs” on page 97v Specify if you want the monitoring of resource models to take place on specific






Tivoli desktop:



2. Click Parameters.3. Select the type of parameter from the Name drop-down list in the Parameters

window.4. Add or delete the parameter values as desired by selecting or clearing the

check boxes.5. Click Apply Changes and Close to save your changes.

Creating scheduling rules

ObjectiveTo create schedule rules so administrators and users can determine the timeperiods on selected days when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to determinea period when monitoring takes place and specific scheduling rules. You candivide the overall collection period into active and inactive intervals by applyingone or more schedule rules.

The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules whichallows you set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If the profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that monitors the same local time period in different time zones. Alltimes of events or activities reported from endpoints or gateways are also loggedin the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesManages time intervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.













process. See “Modifying parameters” on page 99v Determine when the monitoring of resource models takes place. See “Modifying





Tivoli desktop:


2. Click Schedule to open the Scheduling window.3. Select Always in the Schedule panel.4. Click New Rule in the Schedule Rules panel.5. Type a name for the rule in the Rule Name text box of the Rule Editor panel.6. Select one or more items in the weekday list to specify the day or days on

which you want the collections active during the collection period.Additional information: Use the Shift or Ctrl key as necessary to select more thanone day from the list.

7. Set the Start Time and Stop Time for the collection activity or select the AllDay check box.Additional information: Times are always interpreted as local time where theendpoint engine runs. Setting a time interval of 08:00 to 13:00 ensures thatmonitoring takes place between those times in all time zones to which youdistribute the profile.

8. Click Set Rule. Your new rule appears in the Schedule Rules list.Additional information: To display the details of any rule, select the rule in theSchedule Rules list. Its settings are displayed in the Rule Editor group box.


9. Click Modify & Close to save your rule and close the Scheduling window.

Modifying the scheduling monitoring period

ObjectiveTo customize the scheduling monitoring period of a resource model soadministrators and users can determine when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to determinea period when monitoring takes place and specific scheduling rules.

The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules whichenables you set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If a profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that monitors the same local time period in different time zones. Alltimes of events or activities reported from endpoints or gateways are also loggedin the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesManages time intervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.





profiles” on page 83 for information.v Create the schedule rules. See “Creating scheduling rules” on page 100 for more

details.









time periods of selected days. See “Creating scheduling rules” on page 100v Specify if you want the log data collected by a resource model written to a local

database. See “Modifying data logging settings”



Tivoli desktop:


2. Click Schedule to open the Scheduling window.3. Clear the Always check box in the Schedule panel.4. Set a Start Date and Stop Date to define the monitoring period.5. Optional: Add one or more schedule rules that determine time periods on the

selected dates that monitoring takes place.6. Click Modify & Close to save your changes.

Modifying data logging settings

ObjectiveTo modify data logging information so administrators and users can log datacollected by a resource model and write it in a local database.

Background InformationYou can view the log data through the IBM Tivoli Monitoring Web Health Consoleafter you write it in a local database. You can store one of the following types ofdata in the database:

Raw dataData written exactly as the resource model collects it. All the monitoredvalues are collected and copied in the database.

Aggregated dataData collected and aggregated at fixed intervals that you define


(Aggregation Period). Only the aggregated values are written in thedatabase. The aggregated data is calculated on the basis of one or more ofthe following options:v Maximumv Minimumv Average

Tivoli Enterprise Data Warehouse data loggingData collected is logged to Tivoli Enterprise Data Warehouse.

Note: To enable Tivoli Enterprise Data Warehouse data logging, you mustdisable aggregated data logging.


Before You Beginv Create a profile manager and profile.v Add subscribers to a profile manager.v Add a resource model to a profile.

When You FinishDistribute the profile to which the resource model belongs. See “Distributingprofiles from the desktop” on page 85.








the scheduling monitoring period” on page 102



See the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusinessApplications Reference Guide for examples.

Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Open the Tivoli desktop.


b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model dialog box.4. Click Logging to open the Logging dialog box.5. Select the Enable Data Logging check box in the Data Logging Settings panel.

This enables logging of all raw data collected by the resource model to adatabase.

6. Perform the following steps to specify the aggregation rule applied to the databefore it is written to the database:a. Set Hours and Minutes of the Aggregation Period to the required values.b. Select one or more of the following functions to perform on the numerical

data collected during the aggregation period before it is written to thedatabase:

MaximumCalculates and logs the peak value in each aggregation period.

MinimumCalculates and logs the lowest value in each aggregation period.

AverageCalculates and logs the average of all values in each aggregationperiod.

Note: To enable Tivoli Enterprise Data Warehouse data logging, selectTivoli Enterprise Data Warehouse data logging and clearAggregated data.

7. Set Hours and Minutes of the Historical Period to the required values.8. Click Apply Changes and Close to save your changes and close the Logging

dialog box.

Managing profiles and resource models at endpoints

ObjectiveTo manage profiles and resource models after they are distributed to endpoints soadministrators and users can maintain monitoring processes on those endpoints.

Background InformationNone


Before You Beginv Create a profile manager and profile.v Add subscribers to a profile manager.v Add a resource model to a profile.v Distribute the profile. See “Distributing profiles from the desktop” on page 85 for

information.v See the IBM Tivoli Monitoring for Applications Version 5.1.0: Siebel eBusiness



When You FinishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command line: Use the wdmcmd command to stop or restart IBM TivoliMonitoring on one or more endpoints from a gateway or server.

Use the wdmdistrib command to distribute a profile to one or more subscribers.

Use the wdmeng command to stop or start profiles or resource models atendpoints or to delete profiles at endpoints.

Use the wdmlseng command to return a list and the status of all resource modelsthat have been distributed on a specified endpoint.

Use the wdmtrceng command to set the trace parameters of the IBM TivoliMonitoring engine at the endpoint.

Managing IBM Tivoli monitoring gateways

ObjectiveTo manage IBM Tivoli Monitoring on gateways so administrators and users canrun monitoring processes on those gateways.

Background InformationNone.





When You FinishNone


Command line: Use the wdmmn command to stop or start selected IBM TivoliMonitoring processes on one or all gateways.

Determining which resource models are running on endpoints

ObjectiveTo determine which resource models are running on an endpoint.


Background InformationUse the Tivoli command line to determine which monitors are running on anendpoint.





When You FinishNone


Command line: Use the wdmlseng command to determine which monitors arerunning on an endpoint. For example, to view the list of monitors on an endpoint,enter the following command.wdmlseng -e <endpoint>

Refer to the IBM Tivoli Monitoring User’s Guide for more information.

Viewing resource model results with the IBM Tivoli WebHealth Console

This chapter provides an overview of the IBM Tivoli Monitoring Web HealthConsole. For complete information on installing and working with the IBM TivoliMonitoring Web Health Console see the latest version of the IBM Tivoli MonitoringUser’s Guide. The IBM Tivoli Monitoring Web Health Console runs on Netscape 6.xand Internet Explorer 6.x. You can use the IBM Tivoli Monitoring Web HealthConsole for the following purposes:v Checking, displaying, and analyzing the status and health of endpoints that

have distributed resource monitorsv Displaying an endpoint’s real-time and historical data logged to the IBM Tivoli

Monitoring databasev Viewing online and historical data on endpoints as a follow-up to specific

problemsv Starting and stopping the IBM Tivoli Monitoring engine and individual resource

models on selected endpointv Removing a profile from the selected endpoint

You can use the IBM Tivoli Monitoring Web Health Console to check, display, andanalyze the status and health of any endpoint with profiles and resource models.Status reflects the state of the endpoint displayed on the IBM Tivoli MonitoringWeb Health Console, such as running or stopped. Health is a numeric valuedetermined by resource model settings. You can also use the Web Health Consoleto work with real-time or historical data from an endpoint that is logged to theIBM Tivoli Monitoring database.


You can use the diagnostic and monitoring capabilities of the IBM TivoliMonitoring Web Health Console to perform targeted analysis of problemsassociated with individual endpoints when an event is sent to the Tivoli EnterpriseConsole. Use the online and historical data to follow up specific problems withsingle endpoints.

Understanding resource healthThe IBM Tivoli Monitoring Web Health Console obtains events and indicationsfrom endpoints. The IBM Tivoli Monitoring Web Health Console displays thehealth of each potential problem as a numeric value between 100 (perfect health)and zero (with zero meaning that the conditions for the corresponding event aremet). Intermediate values show the percentage of occurrences currently registeredwith respect to the total number of occurrences needed to trigger an event. SeeTable 12

Table 12. Health Determination Example

Cycle 1 2 3 4 5

CPU% 55 73 54 63 68

Occurrences or Holes H O H O O

Occurrence Count 0 1 1 2 3

Health % 100 75 75 50 25

Table 8 on page 46 displays the health percentage changes in steps of 25% because4 occurrences were required to trigger an event; if the indication required 5occurrences, the health percentage would have changed by steps of 20%. Resourcehealth is determined at the indication level and passed up to the endpoint. Thelowest health of any indication in a resource model is shown as the health of thatresource model and the lowest health of any resource model installed on anendpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is installed on an endpoint has a health of zero, the healthof the endpoint is shown as zero. The required occurrences, cycle times, thresholds,and parameters for indications are defined when the resource model is created inthe IBM Tivoli Monitoring Workbench.

Connecting the IBM Tivoli Monitoring Web Health ConsoleYou can connect the IBM Tivoli Monitoring Web Health Console to any Tivolimanagement region server or managed node and configure it to monitor any or allof the endpoints that are found in that region. The IBM Tivoli Monitoring WebHealth Console does not have to be within the region itself, although it could be.To connect to the IBM Tivoli Monitoring Web Health Console you need access tothe server on which the IBM Tivoli Monitoring Web Health Console server isinstalled and the IBM Tivoli Managed Region on which you want to monitorhealth. All user management and security is handled through the IBM Tivolimanagement environment. This includes creating users and passwords as well asassigning authority.


Appendix F. Problem determination

This appendix provides information about resolving problems that might occurwhen you run IBM Tivoli Monitoring for Applications: Siebel eBusinessApplications. The following types of problems might occur:v Machine or server availabilityv Operating system environmentv IBM Siebel eBusiness Applications Server installationv IBM Tivoli Monitoring for Applications: Siebel eBusiness Applications

configuration

Resource models

A resource model fails to start but no event is reported toTivoli Enterprise Console

Tivoli Enterprise Console events are not generated when a resource model fails tostart; they are generated when there is a problem or change in a resource beingmonitored. Problems that occur with the resource model itself are reported in theIBM Tivoli Monitoring Web Health Console. See the IBM Tivoli Monitoring User’sGuide for more information on the IBM Tivoli Monitoring Web Health Console.

Tasks

The Archive_Siebel_Logs task output shows a greater logarchive size than the size reported by Windows.

After you run the Archive_Siebel_Logs task against a Windows endpoint, the totalsize of the log archive directory reported in the task output might be different thanthe size of that Windows reports when you right-click the directory. TheArchive_Siebel_Logs task uses the du command to calculate the kilobytes used bya directory hierarchy. Because the du command incorporates additionalinformation when calculating the size of the log directory, it reports a slightlylarger value than the value reported by Windows.

Errors occur when creating an objectIf the managed node on which you are trying to create the object does not haveenough free memory, errors similar to the following might occur:v FRW0G0017E method fork failedv GMS0201E An error occurred while attempting to display output

You might also notice errors in the log files that indicate a command was unable toallocate memory. You can resolve the error and create your objects if you do thefollowing:1. Make sure your managed nodes meet the minimum requirements for Tivoli.

See the IBM Tivoli Monitoring for Applications Version 5.1.0: Installation and SetupGuide for System Requirements.

2. Execute tasks against a managed node that has sufficient available memory.3. Stop any unnecessary processes on the managed node you were trying to create

objects.

109

The gateway and server object icons do not change when theStop_Connection_Broker task is run.

If a connection broker, gateway, and server are running on a single NT machineand you run the Stop_Connection_Broker task, all three resources stop. When theStop_Connection_Broker task competes successfully, the task output reflects thestatus change for all. However, the only object icon that reflects the status changeis the Connection Broker object icon. You can also do the following to confirm aresource status change:v Run the Siebel Gateway Availability and Siebel Server Availability resource

models. The gateway and server object icons are updated when the availabilityresource models run after the Stop_Connection_Broker task completes.—OR—

v Check the resource status from the Monitoring for Siebel policy region.1. Right-click the resource icon to display the resource icon drop-down menu.2. Click Operation to display the Operation drop-down menu.3. Select Check Status to display the status in the output window.4. Click Close to the close the output window.

The Siebel Discovery task or job returns an exception afterrunning the Tivoli odstat command

When you bring up the dialog to run the Siebel Discovery task or job and run theTivoli odstat command, the output might include the following exception:* 2024 O+hdoq 1-2018 done 506 0 09:55:19 e=12 1657725682.1.26 lookup

This exception does not indicate an error and does not affect discovery.


Appendix G. Messages

GMS0002I The Siebel Server %1$s is running.

Explanation: No additional information is availablefor this message.

GMS0005I Starting Siebel Server - Enterprise name%1$s, Server name %2$s


GMS0006I The Siebel server started successfully.


GMS0007E The Siebel Server did not start.

Explanation: The attempt to start the Siebel serverfailed. Check the Start Siebel Server log file for reasonswhy the server did not start. Resolve the errors and tryto restart the server.

GMS0008E The Siebel Server file%1$s/bin/start_server was not found.

Explanation: The command used to start the SiebelServer was not found. Verify that the Siebel Server isconfigured correctly. The start_server command mustbe in the bin directory of the Siebel Server installationdirectory.

GMS0009I The Connection Broker is alreadyrunning.


GMS0010I The Connection Broker service wasstarted.


GMS0011E The Connection Broker did not start.

Explanation: An attempt to start the Resonate CentralDispatch Agent failed. Start the agent manually. If youcannot start the agent manually, check the log file forResonate Central Dispatch Agent information.

GMS0012E The Connection Broker’s control script%1$s was not found.

Explanation: Control script %1$s is needed to stopand start the Resonate Central Dispatch Agent and wasnot found. Locate the script and restore it to the correctdirectory where the Resonate Central Dispatch Agentcan find it.

GMS0016I The Siebel Gateway Server is alreadyrunning.


GMS0017I The Siebel Gateway Server was started.


GMS0018E The Siebel Gateway service did notstart.

Explanation: The Siebel Gateway Server’s processfailed to start. Look in the task log file and theGateway’s log file for information indicating why thegateway process failed to start. Resolve any errors andrestart the server.

GMS0019E The Siebel Gateway file%1$s/bin/start_ns was not found.

Explanation: On UNIX systems, theStart_Siebel_Gateway task needs the start_ns commandto start the Siebel Gateway. If the command is notfound in the specified location, the task cannot start theSiebel Gateway. Check the specified path to thecommand and do one of the following:

v If the specified path to the command is incorrect,correct the specified path to the start_ns commandand run the Start_Siebel_Gateway task again.

--OR--

v If the path is correct but the task cannot start thegateway, the start_ns command is missing from yourSiebel Gateway installation. Restore the start_nscommand and run the Start_Siebel_Gateway taskagain.

GMS0020I The Connection Broker is not running.


111

GMS0021I The Connection Broker was stoppedsuccessfully.


GMS0022E The Connection Broker was notstopped.

Explanation: The Resonate Central Dispatch Agentcannot be stopped if a Siebel Server or Gateway isrunning. Stop the running Siebel Servers or Gatewaysand run the Stop_Connection_Broker task again.

GMS0023I The Siebel Gateway is not running.

Explanation: The Stop_Siebel_Gateway_Server taskfailed because the Siebel Gateway Server is notrunning.

GMS0024I The Siebel Gateway was stoppedsuccessfully.


GMS0025E The Stop_Siebel_Gateway_Server taskfailed.

Explanation: Check the Stop_Siebel_Gateway task andSiebel Gateway Server log files for informationindicating why the process failed. Resolve the errorsand stop the Siebel Gateway Server again.

GMS0026E The Siebel Gateway file%1$s/bin/stop_ns was not found.

Explanation: The Stop_Siebel_Gateway task requiresthe stop_ns command to stop the Siebel Gateway. If thecommand is not found in the specified location, thetask cannot stop the Siebel Gateway. Check thespecified path to the command and do one of thefollowing:

v If the specified path to the command is incorrect,correct the specified path to the stop_ns commandand run the Stop_Siebel Gateway task again.

--OR--

v If the path is correct but the task cannot stop thegateway, the stop_ns command is missing from yourSiebel Gateway installation. Restore the stop_nscommand and run the Stop_Siebel_Gateway taskagain.

GMS0027I The Siebel Server %1$s was notrunning.

Explanation: You attempted an operation on a SiebelServer that was not running. Start the Siebel Server andrun the operation again.

GMS0028I Stopping Siebel Server: %1$s Enterprise,%2$s server


GMS0029I The Siebel Server was stopped.


GMS0030E The Siebel Server was not stopped.

Explanation: The Stop_Siebel_Gateway_Server taskfailed. Check the Stop_Siebel_Server tasks log file andthe Siebel Servers log file for information indicatingwhy the server did not stop. Resolve errors and trystopping the server again.

GMS0031E The Siebel Server file%1$s/bin/stop_server was not found.

Explanation: The stop_server command failed becausethe files needed to stop the Siebel Server on UNIXsystems were not found. Verify that the file exists andthe specified path to %1$s/bin/stop_server file iscorrect. Restore the file or correct the specified path tothe file and run the Stop Siebel Server task again.

GMS0032E Siebel Component Group must bespecified.

Explanation: The Control_Component_Groups taskfailed because the Component Group was not specified.Run the task again, specifying the Component Group

GMS0033I Component Group %1$s is offline.


GMS0034E Component Group %1$s was not takenoffline.

Explanation: The command to take the componentgroup offline failed. The component group either wentinto a state other than offline or the command timedout before the component group went offline. Executethe Run_List_Command task to list the componentgroups and determine the current state of thecomponent group.

GMS0035I Component Group %1$s is online.


GMS0021I • GMS0035I


GMS0036E Component Group %1$s was notbrought online.

Explanation: The Control_Component_Groups taskfailed. Run the Run_List_Command task to list thecomponent groups and determine the current state ofcomponent group %1$s.

GMS0037E A Siebel Gateway was not found.

Explanation: The Discover task did not find theinstallation path for the Gateway Server. Theinstallation path is either incorrect or missing. Restorethe installation path if you are running an NT Systemor specify the correct Siebel Gateway path on theDiscover dialog if you are running a UNIX system. Runthe task again after you specify or restore theinstallation path.

GMS0039E IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications supportsWindows NT, Windows 2000, SolarisOperating Environment and AIX only.

Explanation: The Siebel Gateway or Siebel Server onwhich you ran the Discover task exists on anunsupported platform. Discover the Siebel Server orGateway running on Windows NT, Windows 2000,Solaris Operating Environment, or AIX. See the IBMTivoli Monitoring for Applications Version 5.1.0: Installationand Setup Guide for supported platforms.

GMS0053E Run the task against a managed node.

Explanation: The task you attempted to run failedbecause it was not run against a managed node. Runthe task against a managed node.

GMS0054I The Tivoli logfile adapter is starting.


GMS0060I The Tivoli logfile adapter is stopping.


GMS0064I Poll Interval was already set


GMS0065I PollInterval line was added to %1$s


GMS0068I Executing %2$s command on %1$sserver.

Explanation: The Run List Command and RunSrvrmgr Command tasks display this message toindicate the command run that is running.

GMS0069E Usage: %1$s %2$s


GMS0070E Managed nodes are not supported.

Explanation: An operation on a managed node failed.Run the operation on an endpoint.

GMS0073E The Component Group %1$s does notexist.

Explanation: The Component Group %1$s specified inthe Control_Component_Group task does not exist.Run the task again specifying the name of an existingComponent Group

GMS0074I The Component Group %1$s is alreadyonline.


GMS0075I The Component Group %1$s is alreadyoffline.


GMS0076I The task completed.


GMS0122W Some log files were not deleted fromthe endpoint.

Explanation: An operation to delete log files from theendpoint failed. Remove the log files manually.

GMS0123I The files were deleted from theendpoint.


GMS0125E The task failed.

Explanation: The task did not complete the all of itsoperations. Check the task log file for informationindicating why the task failed. Resolve errors and runthe task again.

GMS0036E • GMS0125E

Appendix G. Messages 113

GMS0152E %1$s: %2$s

Explanation: The command returned the specifiedmessage. Check the error message and log files foradditional information indicating the cause of the error.

GMS0160E Specify a Siebel command.

Explanation: A Siebel command was not specified.Run the task again and specify the command you wantto run.

GMS0161E Run the task against the SIEBELBroker,SIEBELServer, or SIEBELGateway.

Explanation: The task failed because it was runagainst an invalid target. Run the task again andspecify one of the following targets:

v SIEBELBroker

v SIEBELServer

v SIEBELGateway

GMS0162I A Connection Broker was notdiscovered.

Explanation: The Discovery task did not find aConnection Broker on this endpoint. Verify that aConnection Broker was correctly installed on theendpoint and run the Discovery task again. If theproblem persists contact Customer Support.

GMS0163E An error occurred running wruntaskwith the %1$s task of the %2$s tasklibrary.

Explanation: View the trace_siebel_discover.loglocated in the $DBDIR/GMS/logs directory for details.Resolve the error and run the task again.

GMS0164E An incorrect option was specified forthe task.

Explanation: Refer to the IBM Tivoli Monitoring forApplications Version 5.1.0: Siebel eBusiness ApplicationsReference Guide for the correct task options.

GMS0165I The task was canceled because it wasnot confirmed.

Explanation: You must include the y parameter toconfirm when you run this task using the wruntaskcommand. Specifying the ″y″ parameter is equivalent toclicking Yes on the confirmation dialog when you runthe task from the desktop.

GMS0166I You must specify an object type to findan object.

Explanation: The Discovery task did not run becausean object type was not specified. You must specify oneof the following object types you want to create whenyou create a Connection Broker, Siebel Server, or SiebelGateway:

v SIEBELBroker

v SIEBELGateway

v SIEBELServer

GMS0167E You must select at least one endpointfrom the list of endpoints.

Explanation: The task failed because you did notselect an endpoint. Select at least one endpoint and runthe task again.

GMS0168E You must select a managed node inwhich to create the Siebel Objects.

Explanation: The task failed because a managed nodewas not selected. Select a managed mode and run thetask again.

GMS0169I The message catalog files were deletedfrom the endpoint


GMS0170W An error occurred while attempting tocreate object "%1$s".

Explanation: Refer to the logfiletrace_siebel_discover_ep.log for information indicatingwhy the error occurred. Resolve the errors and trycreating the object again.

GMS0171I SIEBELBroker Object "%1$s" wascreated in policy region "%2$s".


GMS0172I SIEBELGateway Object "%1$s" wascreated in policy region "%2$s".


GMS0173I SIEBELServer Object "%1$s" wascreated in policy region "%2$s".


GMS0152E • GMS0173I


GMS0174I The Server Object Name is %1$s andthe Object Class is %2$s.


GMS0175E Select a logfile to view or delete beforeproceeding.


GMS0176I File "%1$s"was deleted.


GMS0177W An error occurred while deleting logfile"%1$s".

Explanation: Refer to the task logfile for informationindicating why the file was not deleted. Resolve theerror and try to delete the logfile again.

GMS0178I No logs available.

Explanation: Verify that there are log files in thespecified log path.

GMS0179I The output from logfile %1$s isdisplayed.

Explanation: The output from the log file is displayedfor your review.

GMS0180I The server properties are displayed.


GMS0181I Checking server status.


GMS0182I The Siebel server is starting.


GMS0183I The Siebel server is stopping.


GMS0184I The dependency files were deleted fromthe endpoint.


GMS0185E The callback request %1$s is unknown.

Explanation: The request %1$s to the callback isunknown. If the problem persists contact CustomerSupport.

GMS0186E The implementation for callback request%1$s was not found.

Explanation: If the problem persists, contact CustomerSupport.

GMS0187E The shell script %1$s was not found.

Explanation: Verify that the specified shell script %1$sexists. If the problem persists, contact CustomerSupport.

GMS0188E Searching in directory %1$s.

Explanation: Verify that the directory %1$s exists. Ifthe directory is not present contact Customer Supportfor assistance.

GMS0189E An error occurred attempting to run the%1$s task from the %2$s library.

Explanation: An error occurred running the %1$s task.Refer to the callback log file for more informationindicating why the error occurred. Resolve the errorand run the task again.

GMS0190E The object type %1$s is incorrect.

Explanation: You specified an invalid object type. Theobject type must be one of the following:

v SIEBELBroker

v SIEBELGateway

v SIEBELServer

GMS0191I Tracing is turned on for callback %1$s


GMS0192I The Class is %1$s and the Object Nameis %2$s.




GMS0193I The %1$s task is running.


GMS0194I The secondary callback %1$s is posted.


GMS0195I The %1$s arguments are passed to thecallback.


GMS0196I The %1$s dialog is posted.


GMS0197I Running %1$s task in the %2$s library.


GMS0198E An error occurred while posting dialog%1$s.

Explanation: Refer to the log file for informationindicating why the error occurred. Resolve the errorand try posting the dialog again.

GMS0199E An error occurred while thewsiebeldispout utility tried to open%1$s file.

Explanation: Verify that the listed file is available.

GMS0200I The Monitoring for Siebel log files weredeleted from the endpoint


GMS0201E An error occurred while attempting todisplay output.

Explanation: Refer to the log file for informationindicating why the error occurred. Resolve the errorand try to display the output again.

GMS0202I The files necessary for the product torun were successfully pushed to thisobject’s endpoint.

Explanation: The dependencies were successfullypushed to this object’s endpoint.

GMS0203I The Tivoli log files are displayed.


GMS0204E Specify the Siebel Administrators username

Explanation: The Siebel Administrator’s user namewas either not specified or specified incorrectly. Specifythe correct Siebel Administrator user name and retrythe operation.

GMS0205E Select a Tivoli endpoint.

Explanation: Select a Tivoli endpoint and retry theoperation.

GMS0206E Endpoint name %1$s is not a Tivoliendpoint.

Explanation: Specify a Tivoli endpoint and try again.

GMS0207E %7$s is not a managed node.

Explanation: Specify a correct managed node and tryagain.

GMS0208E The %1$s exception was raised duringcomponent creation.

Explanation: Run the odstat command to returninformation that might indicate what caused theexception. Resolve errors that that caused the exception.If you are unable to resolve the exception, contactCustomer Support.

GMS0209E %7$s is not a Tivoli managed node.

Explanation: Specify a correct managed node retry theoperation.

GMS0210I The correct format for thewsiebeldispout command iswsiebeldispout [-p preface] [-f file]

Explanation: Make sure the wsiebeldispout commandis using the correct syntax as indicated.

GMS0211E Run the wsiebeldispout command fromwithin the correct Tivoli callbackcontext.

Explanation: Do not run this command manually. It isrun only by the callback scripts and cannot run outsideof that context.

GMS0193I • GMS0211E


GMS0212I The following is the correct format forthe wsiebeldispconf command:wsiebeldispconf [-N] message.

Explanation: Make sure that you specify the correctsyntax for the wsiebeldispconf command .

GMS0213E The following is the correct format forthe wsiebeldispconf command:wsiebeldispconf [-N] message.

Explanation: Make sure that you specify the correctsyntax for the wsiebeldispconf command.

GMS0214I The following is the correct format forthe wsiebelattr command: wsiebelattr [-oowner -d dialog_name -idialog_instance] -g gadget_path -tgadget_type -a gadget_attributenew_value | -f filename

Explanation: Make sure that you specify the correctsyntax for the wsiebeldispconfcommand.

GMS0215E %7$s is not a correct policy region.

Explanation: Specify a valid policy region and try theoperation again.

GMS0216I Use the following format to create aConnection Broker: wsiebel -create %7$s-e <endpoint_name> -a <path> -s<siebel_enterprise_name> [-p<policy_region>] [-m <managed_node>]

Explanation: Specify the correct syntax as indicated tocreate a Connection Broker.

GMS0217I Use the following format to create aSiebel Gateway: wsiebel -create %7$s -e<endpoint_name> -a <gateway_path> -v<siebel_gateway_version> -s<siebel_enterprise_name> [-p<policy_region>] [-m <managed_node>]

Explanation: Specify the correct syntax as indicated tocreate a Siebel Gateway

GMS0218I Use the following format to create aSiebel server: wsiebel -create %7$s -e<endpoint_name> -a <server_path> -u<siebel_admin_user_id> -w<siebel_admin_password> -n<siebel_server_name> -v<siebel_server_version> -g<siebel_gateway_name> -s<siebel_enterprise_name> [-m<managed_node>] [-p <policy_region>]

Explanation: Specify the correct syntax as indicated tocreate a Siebel server.

GMS0219E The %7$s broker was not created in thespecified policy region.

Explanation: IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications was not found on themanaged node. Create the object on a IBM TivoliMonitoring for Applications: Siebel eBusinessApplications managed node.

GMS0220E Siebel Broker %7$s was not created.

Explanation: Refer to the exception and other outputthat generated with this message for more informationindicating why the broker was not created.

GMS0221I Use the following format to delete aSiebel object: wsiebel -delete %1$scomponent_label

Explanation: Specify the correct syntax as indicated todelete a Siebel object.

GMS0222I Use the following format to returninformation on a Siebel Object: wsiebel-get %1$s component_label

Explanation: Specify the correct syntax as indicated toretrieve information on a specific Siebel object.

GMS0223E The Siebel Gateway object was notcreated.

Explanation: See the exception and other output thatoccurred along with this message for more information.

GMS0224E The Siebel Server object was notcreated.

Explanation: Refer to the exception and other outputthat occurred along with this message for moreinformation.

GMS0225E The %7$s Siebel Gateway object wasnot created in the specified policyregion.

Explanation: Unable to create the Siebel Gateway%7$s in specified policy region. The implementation forthe Tivoli Siebel Gateway object could not be found.Verify that the SIEBELGateway class was createdsuccessfully.

GMS0226E The Siebel Server object was not createdin the specified policy region.

Explanation: The implementation for the Tivoli SiebelServer object could not be found. Verify that theSIEBELServer class was created successfully.



GMS0227I The %1$s Connection Broker wasdeleted from the Tivoli region.


GMS0228I The %1$s Siebel Gateway was deletedfrom the Tivoli region.


GMS0229I The %1$s Siebel server was deletedfrom the Tivoli region.


GMS0230I The object label %1$s was not found inthe Tivoli region.

Explanation: Specify the correct object label and trythe operation again.

GMS0231E The required %1$s Tivoli BusinessSystems Manager file was not found.

Explanation: Verify that the Tivoli Business SystemsManager product was installed on the Tivoli EnterpriseConsole server.

GMS0232I GONE event was %1$s forwarded toTivoli Business Systems Manager.

Explanation: A GONE event was forwarded for theSiebel server object listed to remove it from TivoliBusiness Systems Manager.

GMS0233I DISCOVER event %1$s was forwardedto Tivoli Business Systems Manager.

Explanation: A DISCOVER event was forwarded forthe Siebel server object listed to add it to TivoliBusiness Systems Manager.

GMS0234I Use the following format tocreate/delete/get a Siebel object: wsiebel-create <-server | -gateway | -broker> -e<endpoint>[-p <policy_region>] [-m<managed_node>] -a <component_path>-s <siebel_enterprise_name>Server and Gateway Specific Parameters-v <version>Server Specific Parameters-u <siebel_admin_user> -w<siebel_admin_password> -n<component_name> -g <gateway_name>wsiebel -delete <-server | -gateway |-broker> <component_label>

wsiebel -get <-server | -gateway |-broker> <component_label>

Explanation: Specify the correct syntax as indicated tocreate/delete/get a Siebel Object.

GMS0235E You must specify the Siebeladministrators password.

Explanation: Specify the Siebel administratorpassword to create the Siebel server object.

GMS0236E You must specify the Siebel Server Path.

Explanation: Specify the Siebel Server Path in order tocreate the Siebel Server Object.

GMS0237E You must specify the Siebel gatewaypath.

Explanation: You must specify the correct Siebelgateway path to create the Siebel Gateway Object.

GMS0239E You must specify the SiebelAdministrator user id and password.

Explanation: Specify the correct Siebel Administratorsuser id and password to update the Siebel ServerObject.

GMS0240E The Context Variable values were notupdated.

Explanation: An error occurred while attempting toupdate a Context Variable. The new values were notstored. Refer to thetrace_siebel_update_server_cb_xxx.log file todetermine what exception the idlcall commandgenerated when it called the update_context method. Ifthere is an exception, it might indicate why the idlcallcommand returned a non-zero return code. Resolve theexception and try the operation again. If the problempersists contact Customer Support.

GMS0241E The request to update the dependenciesfailed on the endpoint %1$s.

Explanation: The request to update the dependenciesfailed for the endpoint specified. Verify that thegateway for that endpoint is operating correctly andhas Tivoli Monitoring for Siebel installed on it. Retrythe operation.

GMS0242I An update to a context variablecompleted.




GMS0243E Run the task against a %1$s.

Explanation: The task was run against an incorrectobject. Run the task against a %1$s.

GMS0244E The required dependency file %1$s wasnot found.

Explanation: Verify that file %1$s is available. If theproblem persists contact Customer Support.

GMS0245I The %1$s server status is %2$s.


GMS0246E Tivoli logfile adapter %1$s format filewas not found.

Explanation: The logfile adapter task did not locatethe logfile adapter %1$s format file. Determine andcorrect the cause of the missing format file and run thelogfile adapter task again. Redistributing the adapterconfiguration profile to the endpoint will recreate thefile. If the problem persists, contact Customer Support.

GMS0247E Tivoli logfile adapter CDS file %1$s wasnot found.

Explanation: The logfile adapter task was unable tolocate the logfile adapter %1$s CDS file. Determine andcorrect the cause of the missing CDS file and run thelogfile adapter task again. Redistributing the adapterconfiguration profile to the endpoint will recreate thefile. Contact Customer Support if the problem persists.

GMS0248E Tivoli logfile adapter gencds executablewas not found.

Explanation: The logfile adapter task did not locatethe logfile adapter gencds executable program.Determine and correct the cause of the missing gencdsexecutable and run the logfile adapter task again. If theproblem persists, contact Customer Support.

GMS0249E The %1$s format file was not found.

Explanation: The logfile adapter task was unable tolocate the IBM Tivoli Monitoring for Applications:Siebel eBusiness Applications %1$s format file.

Invoke the Push Dependencies option from theDiagnostics menu for the object icon. Rerun the logfileadapter task. If the problem persists, contact CustomerSupport.

GMS0250I The logfile adapter for language %1$s isbeing configured.

Explanation: The logfile adapter task is updating thelogfile format file associated with the %1$s language.

GMS0251I The CDS files in directory %1$s will beupdated.


GMS0252I The format files in directory %1$s willbe updated.


GMS0253I Logfile message formats were alreadyinstalled in file %1$s.

Explanation: The request to install existing Siebellogfile message formats failed because they arecurrently already installed.

GMS0254I Logfile message formats were notinstalled in file %1$s.

Explanation: The request to install the Siebel logfilemessage formats failed because the message formatswere not found on the target. Invoke the PushDependencies option from the Diagnostics menu forthe object icon and rerun this task.

GMS0255I The logfile message formats from the%1$s file were added to the format file.

Explanation: Check subsequent messages forsuccessful regeneration of the logfile adapter CDS file.

GMS0256I The %1$s backup file already exists.

Explanation: The %1$s backup of the currentconfiguration file was discovered while a task wasupdating configuration files. The backup files wereoverwritten. Verify that you have sufficient backup filesfor the attempted changes.

GMS0257I The %1$s backup file was created.

Explanation: A %1$s backup file was created while atask was updating configuration files.

GMS0258I The %1$s format file was created.

Explanation: A logfile adapter task made changes tothe logfile adapter format file. The new format file isthe active format file for the logfile adapter.



GMS0259I The %1$s CDS file was created.

Explanation: A logfile adapter task successfully madechanges to the logfile adapter CDS file. The new CDSfile is now the active CDS file for the logfile adapter.

GMS0260I The Tivoli logfile adapter is not runningand has not been restarted.

Explanation: The operation to restart Tivoli logfileadapter failed. The adapter must be running to berestarted.

GMS0261I Tivoli logfile adapter was started.


GMS0262I Tivoli logfile adapter was stopped.


GMS0263I Tivoli logfile adapter is not running.

Explanation: Run the Control_Logfile_Adapter task inthe task libraries to start the logfile adapter.

GMS0264E The attempt to stop the Tivoli logfileadapter failed.

Explanation: Refer to the Control Logfile Adapter tasklog for errors. Resolve the errors and run the taskagain. Contact Customer Support if the problempersists.

GMS0265E The attempt to start the Tivoli logfileadapter failed.

Explanation: Refer to the Control Logfile Adapter tasklog for errors. Resolve the errors and run the taskagain. Contact Customer Support if the problempersists.

GMS0266E The logfile adapter executable %1$s wasnot found.

Explanation: The logfile adapter task did not locatethe logfile adapter executable program. Determine andcorrect the cause of the missing executable and run thelogfile adapter task again. If the problem persists,contact Customer Support.

GMS0267E An error occurred generating the logfileadapter CDS file.

Explanation: The changes made to the format filewere not applied to the logfile adapter. Refer to thetask log for errors. Correct the errors and rerun the task

again. Contact Customer Support if the problempersists.

GMS0268I Logfile message formats were alreadyremoved from the %1$s file.


GMS0269I The logfile message formats wereremoved from the %1$s file.

Explanation: The product message formats for Siebelmessages were removed from the logfile adapter formatfile. Check subsequent messages for successfulregeneration of the logfile adapter CDS file.

GMS0270E The incorrect server type %1$s wasspecified for the task. Correct values areSERVER or BROKER.

Explanation: An incorrect server type was specifiedfor the adapter task you attempted to run. Specify theSERVER or BROKER type and run the adapter taskagain.

GMS0271I LogSource already exists for %1$s in file%2$s.


GMS0272E The installation path is not configuredfor %1$s.

Explanation: A value was not set for the applicationcontext variable SIEBELMgr_Path for %1$s.

Verify that %1$s was created correctly and run the taskagain. Refer to the trace_siebel_archive_log log file toverify that environment variables starting withSIEBELMgr_ string were set. If none of theenvironment variables were set, recreate the object andtry again or contact Customer Support.

GMS0273E The enterprise %1$s or server %2$s isnot correct.

Explanation: An incorrect enterprise name or servername was associated with the object that the task ranagainst. Create a new object with the correct enterpriseand server name then run the task again.

GMS0274E The %1$s log archive directory does notexist.

Explanation: There are no files to archive because thespecified directory does not exist.



GMS0275E You must specify a filename anddirectory for the archive file.

Explanation: You did not specify a file name for thearchive file. The file is created in the log archivedirectory if you do not specify a directory with the filename. Specify a file name and directory and run thetask again.

GMS0276E You must specify an age to indicatewhich log directories to archive.

Explanation: You did not specify an age to indicatewhich log directories you would like to archive. Thisparameter is required. Every Siebel log archivedirectory that is as old or older than the age youspecify will be archived. This parameter is an integerand that you specify in days.

GMS0277E The archive age specified is not aninteger.

Explanation: An error occurred because the archiveage specified is not an integer. The archive age must bean integer that specifies the age of the newest directoryyou would like to archive. Any Siebel log directoriesthat are as old or older than the age will be archived.Rerun this task and specify a correct value for the ageparameter.

GMS0278E The archive file already exists.

Explanation: The archive file you specified alreadyexists. Specify a new file for the archive file.

GMS0279E Based on the age specified, there are nodirectories to archive at this time.

Explanation: The archive age parameter specifieswhich directories in the Siebel log archive location youwould like to archive. If you specify 10 as the age, youare requesting that the Siebel log archive directories 10days and older should be archived. In this case, youspecified an age that did not match any directories --there are no Siebel log archive directories as old orolder than the age you specified. If you set this task upto run automatically, this may not be considered anerror.

GMS0280E The %1$s archive file was not created.

Explanation: The tar command used to create thearchive failed. Verify that there is sufficient disk spaceand that you have permission to write to the directoryin which you attempted to create the archive file. If youdo not specify a directory, the archive is created in theSiebel Server’s log archive directory. Check the trace filefor more information.

GMS0281E The %1$s archive directory was notadded to the archive file. The directorywas not removed or archived.

Explanation: This error can occur for the followingreasons:

v There is not enough free space on the drive in whichyou attempted to create the archive file.

v There is an error in the trace file located in the$LCF_DATDIR/LCFNEW/GMS/logs.

v There are errors in the tar command.

Resolve the errors and try the operation again.

GMS0282I The %1$s archive file was created.


GMS0283E The archive was not compressed. Thearchive is in file %1$s.

Explanation: The archive file was created but thecompress command failed to compress the archive file.Verify that there is enough free disk space to performthe compression. If there is enough free space, refer tothe trace file located in$LCF_DATDIR/LCFNEW/GMS/logs for the error thatoccurred running the compress command.

GMS0284E %1$s is not a correct parameter for thistask.

Explanation: An attempt was made to run the taskwith an incorrect parameter. Specify the correctparameter and run the task again.

GMS0285E The %1$s directory does not exist.

Explanation: The specified directory does not exist forthis object. There is a problem with the Siebel objectthat you are running against or there is a problem onthe endpoint. Verify that the directory exists. If thespecified path is incorrect, recreate the Siebel object andtry the operation again.

GMS0286I Tivoli logfile adapter is already running.


GMS0287I Tivoli logfile adapter is running.




GMS0288E An incorrect parameter was specified forthe %1$s task. The following are theparameter options: STATUS, START,STOP, INSTALLSERVER,INSTALLBROKER, UNINSTALLSEVERor UNINSTALLBROKBER

Explanation: You specified an invalid parameter.Specify a valid parameter and re-run the task.

GMS0289E There is not enough free space to createthe archive.

Explanation: There is not enough free space to createthe archive file. Run the task again when you haveenough free space to create the archive.

GMS0290I A Siebel Gateway was not found.

Explanation: A Siebel Gateway was not found on thespecified Windows endpoint. Verify that the Gatewaywas installed correctly and try again.

GMS0291I A Siebel Server was not found.

Explanation: A Siebel Server was not found on thespecified Windows endpoint. Verify that the Server wasinstalled correctly and try again.

GMS0292I A Siebel Server was not found.

Explanation: A Siebel server was not found on thisUnix endpoint. Verify that the server was installedcorrectly and that the Siebel server path was specifiedcorrectly.

GMS0293I The %1$s LogSource file was added tothe %2$s Tivoli logfile adapterconfiguration file.


GMS0294E Invalid Siebel Gateway Path...unable tofind %1$s/admin/gtwydefs.dat

Explanation: Could not find the gtwydefs.dat file inthe SIEBEL_ROOT path specified for the SiebelGateway Path.Verify the path was entered correctly andrerun the task.

GMS0295I No %1$s objects found.

Explanation: No objects were found of the type listed(SIEBELServer, SIEBELGateway, or SIEBELBroker) to besent to Tivoli Business Systems Manager. Specify avalid object type.

GMS0296E The Broker Path could not be found.

Explanation: No Broker Path could be found for thisendpoint. Verify that the Broker is correctly installed forthis endpoint.

GMS0297E The Managed Node selected for Objectcreation does not have the IBM TivoliMonitoring Component Servicesinstalled.

Explanation: Discovery cannot proceed because theIBM Tivoli Monitoring Component Services software isnot installed on the Managed Node given.

Install the ITM Component Services software onto theManaged Node or choose another Managed Node thatalready has the ITM Component Services installed.

GMS0298I wsiebeldisplogs -c class -f filename -lcomponent -h hostname -p path -t type-i id

Explanation: The correct usage for wsiebelattr is :wsiebelattr -c class -f filename -l component -hhostname -p path -t type -i id.

Ensure that the wsiebeldisplogs command is runwithin a Tivoli callback context. This command is onlyrun from callback scripts and cannot run outside of thatcontext.

GMS0299E wsiebeldisplogs must be run within aTivoli callback context.

Explanation: The command wsiebeldisplogs must runwithin a Tivoli callback context.

Ensure that you run the wsiebeldisplogs commandwithin a Tivoli callback context. This command cannotbe run manually.

GMS0300I The following log files were deleted:%1$s

Explanation: The specified log files were deleted asrequested.

GMS0301I Siebel log archive directory: "%1$s".

Explanation: Displays the location of the Siebel logarchive directory.

GMS0302I Successfully added directory: "%1$s" tothe archive file.

Explanation: Displays the directory name of the Siebelserver archived log directory that is being moved to thearchive file created by this task.



GMS0303E Unable to get hostname for endpoint"%1$s".

Explanation: The host name of the endpoint cannot bedetermined for the endpoint specified.

Verify that the hostname command works on theendpoint. See the trace file for the Get_Endpoint_Parmsin the file named trace_siebel_get_parms.log for moredetails.

GMS0304E Unable to start internal transaction.

Explanation: An attempt was made to start atransaction, but an exception was thrown.

See the exception that is displayed with this errormessage. You cannot start a new transaction. Make sureyou have sufficient disk space or consult your TivoliFramework documentation.

GMS0305E Internal transaction endedunsuccessfully.

Explanation: An attempt was made to end the currenttransaction, but an exception was thrown.

See the exception that gets displayed along with thiserror message. For some reason you cannot end thecurrent transaction. Make sure you are not out of diskspace or consult your Tivoli Frameworkdocumentation.

GMS0306E You must specify the Connection Brokerpath.

Explanation: You must specify the correct ConnectionBroker path to create the Connection Broker Object.

GMS0307I "%1$s" created.

Explanation: An object was created with the labelspecified.

GMS0308E You must specify the Siebel Gatewayname.

Explanation: You must specify the correct SiebelGateway name to create the object.

GMS0309E You must specify the Siebel Gatewayversion.

Explanation: You must specify the correct SiebelGateway version to create the Siebel Gateway object.

GMS0310E You must specify the Siebel Servername.

Explanation: You must specify the correct SiebelServer name to create the Siebel Server object.

GMS0311E You must specify the Siebel Serverenterprise name.

Explanation: You must specify the correct SiebelServer enterprise name to create the Siebel Serverobject.

GMS0312E You must specify the Siebel Serverversion.

Explanation: You must specify the correct SiebelServer version to create the Siebel Server object.

GMS0313I The Connection Broker object "%1$s"was created successfully.

Explanation: The Connection Broker object wascreated successfully.

GMS0314I The Siebel Gateway object "%1$s" wascreated successfully.

Explanation: The Siebel Gateway object was createdsuccessfully.

GMS0315I The Siebel Server object "%1$s" wascreated successfully.

Explanation: The Siebel Server object was createdsuccessfully.

GMS0316I The %1$s LogSource file was removedfrom the %2$s Tivoli logfile adapterconfiguration file.


GMS0317E The Siebel Gateway service was notstopped because the following Server(s)were running "%1$s".

Explanation: The attempt to stop the Siebel GatewayServer failed because a Siebel Server connected to thisGateway is currently running.

GMS0318E An attempt to connect to the SiebelServer failed, however the Siebel ServerObject has been created.

Explanation: The attempt to connect to the SiebelServer failed.

GMS0319E Redistribute the Adapter ConfigurationProfile to this endpoint to ensure thedependent files exist.

Explanation: One or more Tivoli Logfile Adapter filesare missing from the endpoint. To correct the problemyou can redistribute the adapter configuration profile



that should have been created and distributed to thisendpoint before you ran this task.

GMS0320E The Siebel server started successfully,but it is not currently functioningcorrectly.

Explanation: The Siebel Server was started, but thesrvrmgr command does not report that it is running.Verify that the Siebel Gateway and Connection Brokerare operating correctly and that the connection to thedatabase is working.

GMS0321E An attempt to obtain this endpointsfully qualified hostname has failed.

Explanation: If the endpoint being discovered is notconfigured with a fully qualified hostname then thediscover task will use the short name. Ensure thisendpoint has been configured with a fully qualifiedhost name, then delete the SIEBELObjects on thisendpoint and rerun the discovery task against thisendpoint.

GMS2038I The object creation results are:%1$s


GMS9001I The Configure Event Server task ispreparing the rule base.

Explanation: You are entering the phase of preparinga new rule base.

GMS9002E The Configure Event Server task cannotlocate rules file %1$s.

Explanation: The Configure Event Server task requiresa set of rules files to complete successfully. File %1 wasnot found.

Rules files are installed during IBM Tivoli Monitoringfor Applications, version 5.1.0: Siebel eBusinessApplications installation. Search the directory in whichthe product was installed to determine if the file wasmoved or deleted. Restore the file and rerun theConfigure Event Server task. Contact Customer Supportif the problem persists.

GMS9003E The Configure Event Server task cannotlocate script file %1$s.

Explanation: The Configure Event Server task requiresa set of event script files to complete successfully. File%1$s was not found. Required script files are installedduring IBM Tivoli Monitoring for Applications, version5.1.0: Siebel eBusiness Applications installation.

Search the directory in which the product was installed

to determine if the file was moved or deleted. Restorethe file and rerun the Configure Event Server task.Contact Customer Support if the problem persists.

GMS9004E Rule base %1$s does not exist.

Explanation: An attempt was made to update rulebase %1, which does not exist.

Run the wlsrb command to list the set of existing rulebases. Rerun the Configure Event Server task specifyingan existing rule base as the rule base to update.

GMS9005E Source rule base %1$s does not exist.

Explanation: An attempt was made to create a newrule base, initializing it with the contents of rule base%1$s, which does not exist.

Run the wlsrb command to determine the set ofexisting rule bases. Rerun the Configure Event Servertask specifying an existing rule base as the source fromwhich to initialize the new rule base.

GMS9006I Created path %1$s.

Explanation: The new rule base path %1 was created.

GMS9007E Error occurred creating path %1$s.

Explanation: An error occurred creating the rule basepath %1$s. Check the Configure Event Server task logfor errors. Correct errors if possible and rerun theConfigure Event Server task. Contact Customer Supportif the problem persists.

GMS9008I IBM Tivoli Monitoring classes arealready installed.

Explanation: An attempt was made to install alreadyexisting IBM Tivoli Monitoring classes.

GMS9009I IBM Tivoli Monitoring classes were notinstalled. IBM Tivoli Monitoring forApplications, version 5.1.0: SiebeleBusiness Applications is installing theclasses now.

Explanation: IBM Tivoli Monitoring for Applications,version 5.1.0: Siebel eBusiness Applications requiresIBM Tivoli Monitoring event classes. The IBM TivoliMonitoring product is not installed, so IBM TivoliMonitoring for Applications, version 5.1.0: SiebeleBusiness Applications is installing the required classes.

GMS9010I Rule base %1$s was compiledsuccessfully.

Explanation: The Configure Event Server task issuesthis message in one of the following situations:



v When it is updating or copying an existing rule base,the existing rule base is compiled to ensure that ithas no problems. No action is required if themessage applies to the validation of an existing rulebase.

--OR--

v After it adds the IBM Tivoli Monitoring forApplications, version 5.1.0: Siebel eBusinessApplications classes and rules to the rule base toensure that the rule base has a consistent set ofclasses and rules. When you are ready to activate anew or updated rule base, load the rule base intoyour event server and restart the event server.

GMS9011E The rule base %1$s did not compilesuccessfully.

Explanation: The Configure Event Server task issuesthis message in one of the following situations:

v When it discovers compilation errors in an existingrule base while updating or copying an existing rulebase. Determine the reason for compilation errors inthe rule base and resolve them. When you resolvethe errors, rerun the Configure Event Server task.

--OR--

v After adding the Siebel classes and rules to the rulebase. Save the Configure Event Server task log andcontact Customer Support.

GMS9012I The rule base %1$s was created in %2$s.


GMS9013E An error occurred creating the rule base%1$s in %2$s.

Explanation: An error occurred trying to create rulebase %1 in directory %2. Check the Configure EventServer task log for errors. Correct errors if possible andrerun the task. Contact Customer Support if theproblem persists.

GMS9014I Rule base %1$s copied to %2$s.

Explanation: Rule base %2$s is a new rule base that isinitialized with the contents of rule base %1$s.

GMS9015E An error occurred while attempting tocopy rule base %1$s to %2$s.

Explanation: An error occurred while attempting toinitialize new rule base %2$s with the contents of rulebase %1$s. Check the Configure Event Server task logfor errors. Resolve the errors and run the task again.Contact Customer Support if the problem persists.

GMS9016I Imported classes in file %1$s into rulebase %2$s.


GMS9017E An error occurred while attempting toimport classes in file %1$s into rulebase %2$s.

Explanation: An error occurred while attempting toimport the event classes in file %1$s into rule base%2$s. Check the Configure Event Server task log forerrors. Resolve the errors and run the task again.Contact Customer Support if the problem persists.

GMS9018I Replacing rules in file %1$s in rule base%2$s.

Explanation: The event rule file %1$s already exists inrule base %2$s. File %1$s is deleted from the rule baseand replaced with the version delivered with the IBMTivoli Monitoring for Applications, version 5.1.0: SiebeleBusiness Applications.

GMS9019I Event source %1$s created as %2$s.

Explanation: A new event source was added to theevent server. The event source name is %1$s. The eventsource label is %2$s.

GMS9020E An error occurred while creating eventsource %1$s.

Explanation: An error occurred while creating eventsource %1. Check the Configure Event Server task logfor errors. Resolve the errors if possible and run thetask again. Contact Customer Support if the problempersists.

GMS9021I Event source %1$s already exists.

Explanation: While the Configure Event Server taskwas updating event sources, it discovered that eventsource %1$s already exists. The current definition of theevent source is not changed.

GMS9022I Event source %1$s was deleted.

Explanation: Event source %1$s was deleted from theevent server.

GMS9023E An error occurred while attempting todelete event source %1$s.

Explanation: An error occurred while attempting todelete event source %1. Check the Configure EventServer task log for errors. Resolve errors and rerun thetask again. Contact Customer Support if the problempersists.



GMS9024I Rule base %1$s was loaded.

Explanation: The rule base %1$ was loaded into theevent server.

GMS9025E Error occurred loading rule base %1$s.

Explanation: An error occurred while attempting toload rule base %1$ into the event server. Check theConfigure Event Server task log for errors. Resolveerrors if possible and run the task again. ContactCustomer Support if the problem persists.

GMS9026I Importing rules.

Explanation: The Configure Event Server task issuesthis message to indicate that it is entering the phase ofimporting rules.

GMS9027I Installing event sources.

Explanation: The Configure Event Server task issuesthis message to indicate that it is entering the phase ofinstalling event sources.

GMS9028I Installing event processing scripts.

Explanation: The Configure Event Server task issuesthis message to indicate that it is entering the phase ofinstalling event processing scripts.

GMS9029I Loading rule base.

Explanation: The Configure Event Server task issuesthis message to indicate that it is entering the phase ofloading the rule base.

GMS9030I The event server was stopped.

Explanation: The event server was stopped andrestarted to activate a new rule base.

GMS9031I Event server started.

Explanation: The event server started so it canactivate a new rule base.

GMS9032E The event server did not start.

Explanation: An error occurred while trying to startthe event server. Check the Configure Event Server tasklog for errors. Resolve the errors and run the taskagain. Contact Customer Support if the problempersists.

GMS9033E The event server did not stop.

Explanation: An error occurred while stopping theevent server. Check the Configure Event Server task logfor errors. Resolve the errors and run the task again.Contact Customer Support if the problem persists.

GMS9034E You must run the Configure EventServer task on the event server.

Explanation: The Configure Event Server task was runon a machine that is not an event server. This task onlyruns on an event server machine. Do one of thefollowing:

v Run the Configure Event Server task, specifying anevent server as the target of the task execution.

--OR--

v Run the Configure Event Server job in the Siebel tasklibraries.

GMS9035I Configuring the event server.

Explanation: The Configure Event Server task issuesthis message to indicate that it is starting the series ofsteps to configure an event server.

GMS9036E Rule base directory %1$s does not exist.

Explanation: While the Configure Event Server taskwas updating event forwarding information, itdiscovered that the directory %1$s associated with therule base does not exist. Check the Configure EventServer task log for errors. Resolve the errors and runthe task again. Contact Customer Support if theproblem persists.

GMS9037E Incorrect parameters were used in anattempt to run the Configure EventServer task.

Explanation: An attempt was made to run theConfigure Event Server task with incorrect parameters.This error can occur if an attempt is made to run thethe Configure Event Server task with the wruntaskcommand. Rerun the task and specify the correctarguments as listed:

v CREATE|CLONE|UPDATE

v CloneRulebaseName|″″

v NewRulebaseName|″″

v NewRulebasePath|″″

v [LOADONLY|RESTART|″″]

GMS9038E Cannot locate baroc file %1$s.

Explanation: The Configure Event Server task requiresa set of baroc files to complete successfully. File %1$swas not found. Required baroc files are installed duringIBM Tivoli Monitoring for Applications, version 5.1.0:



Siebel eBusiness Applications installation. Determine ifthe file was moved or deleted. Restore the file, ifnecessary, from the product CD and run the ConfigureEvent Server task again. Contact Customer Support ifthe problem persists.

GMS9039I The Configure Event Server taskcompleted successfully.


GMS9040E Rule base %1$s already exists.

Explanation: A request was made to create an alreadyexisting rule base named %1$s.

v To create a new rule base, run the Configure EventServer task again, specifying a rule base name thatdoes not currently exist.

--OR--

v If you want to update the existing rule base %1$s,select Update.

GMS9041E The Configure Event Server taskreceived incorrect request: %1$s.

Explanation: The Configure_Event_Server taskreceived an incorrect request. This error occurs onlywhile attempting to run the task with the wruntaskcommand. Valid values are: CREATE, CLONE, andUPDATE. Rerun the task and specify a valid request.

GMS9042E Rule base path %1$s is incorrect.

Explanation: The rule base path is incorrect because itcontains blanks. Run the Configure Event Server taskagain, specifying a rule base path name without blanks.

GMS9043I Imported rules in file %1$s into rulebase %2$s.

Explanation: Event rules in file %1$s were importedinto rule base %2$s.

GMS9044E An error occurred importing rules in file%1$s into rule base %2$s.

Explanation: An error occurred importing the eventrules in file %1$s into rule base %2$s. Check theConfigure Event Server task log for errors. Resolve theerrors and run the task again. Contact CustomerSupport if the problem persists.

GMS9045I Replacing event source %1$s.

Explanation: Event source %1$s already exists. Source%1$s is replaced with a new source definition.

GMS9046I Installed rules script %1$s.


GMS9047I Importing classes.

Explanation: The Configure Event Server task issuesthis message to indicate that it is entering the phase ofimporting event classes.

GMS9048E Cannot locate icon file %1$s.

Explanation: The Configure Event Server task requiresicon files that are normally installed with IBM TivoliMonitoring for Applications, version 5.1.0: SiebeleBusiness Applications to complete successfully. Iconfile %1$s was not found. Determine if the file wasmoved or deleted. Restore the file, from the product ifnecessary, and run the Configure Event Server taskagain. Contact Customer Support if the problempersists.

GMS9049E This task must be run against the TivoliEnterprise Console Server.

Explanation: An attempt was made to run theConfigure Event Server task against a target that wasnot a Tivoli Enterprise Console Server. Run theConfigure Event Server task against the TivoliEnterprise Console Server.

GMS9050E The Default rule base is read-only andcannot be updated.

Explanation: An attempt was made to run theConfigure Event Server task and update the Defaultrule base. This rule base is read-only and cannot beupdated.

Run the wlsrb command to list the set of existing rulebases. Rerun the Rerun the Configure Event Server taskspecifying a different existing rule base as the rule baseto update.

GMS9051E New Rule Base Name was not specified.

Explanation: An attempt was made to create a newrule base but the New Rule Base Name was notspecified.

Rerun the Configure Event Server task specifying aname for the new rule base.



GMS9052I The rule base has not been loaded. Thechanges will not take effect until therule base has been loaded and the eventserver restarted.

Explanation: A rule base was created or updated butthe activation selected indicated not to load therulebase.

GMS9053I The event server has not been restarted.Changes to the rule base will not takeeffect until the event server has beenrestarted.

Explanation: A rule base was created or updated butthe activation selected indicated not to restart the eventserver.

GMS9054E New Rule Base Path was not specified.

Explanation: An attempt was made to create a newrule base but the New Rule Base Path was notspecified.

Rerun the Configure Event Server task specifying apath for the new rule base.

GMS9055E Rule Base was not specified.

Explanation: An attempt was made to update anexisting rule base or create a new rule base from anexisting one and a Rule Base was not specified.

Rerun the Configure Event Server task specifying therule base to be updated or copied.



Appendix H. Accessibility

Accessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in IBM Tivoli Monitoring for Messaging and Collaborationenable users to:v Use assistive technologies such as screen-reader software and a digital speech

synthesizer to hear what is displayed on the screenv Operate specific or equivalent features using only the keyboardv Magnify what is displayed on the screen

In addition, the product documentation has been modified to include features toaid accessibility:v All documentation available in both HTML and convertible PDF formats to give

the maximum opportunity for users to apply screen-reader software.v All images provided with alternative text so that users of the documentation

with vision impairments can understand the contents of the images.

Using Assistive TechnologiesAssistive technology products such as screen-readers, function with both thetext-based and graphical user interfaces found in IBM Tivoli Monitoring forMessaging and Collaboration. Consult the assistive technology productdocumentation for specific information about using it to access command line orgraphical interfaces.

Additional accessibility features might be included as part of the user interface of aparticular IBM Tivoli Monitoring for Messaging and Collaboration component.Check with the individual component’s documentation for any additionalinformation about accessibility.

Magnifying What is Displayed on the ScreenIn all components of IBM Tivoli Monitoring for Messaging and Collaboration otherthan the Web Health Console, users can magnify the screens used by the product’suser interfaces using facilities provided by the operating systems on which theproduct is run. For example, in a Windows® environment you can change thescreen settings to a lower resolution to enlarge the font sizes of the text on thescreen. Information about these facilities is provided in the relevant operatingsystem documentation.

Documentation in Accessible FormatsAll user documentation is provided in HTML format, which can be read directlyby assistive tools such as screen readers, or in convertible PDF format. ConvertiblePDF files are those that can be converted from PDF to HTML by the Adobe PDF toHTML converter. For information about converting PDF documents to HTML, referto the Adobe book Optimizing Adobe PDF Files for Accessibility

129

Using Alternative TextAll documentation images are provided with an alternative text that can be readby assistive tools such as screen readers.

Documentation in PDF and HTML Formats


Appendix I. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

131

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, and Tivoli Enterprise Console aretrademarks or registered trademarks of International Business MachinesCorporation in the United States or other countries, or both.

Siebel and Siebel eBusiness Applications are trademarks of Siebel Systems, Inc inthe United States, other countries, or both.

Microsoft and Windows NT are registered trademarks of Microsoft Corporation inthe United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

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

Appendix I. Notices 133

Index

Aaccessibility 129accessibility features viiiactions, built-in

See built-in actionsAdministrators, Siebel 1Administrators, Tivoli 1authorization roles 1

list of 59setting 7

Bbooks

feedback vonline vordering v

built-in actionsadding to resource models 93editing 95removing from resource models 93

Ccommand

unable to allocate memory for a 109commands

du 109odstat 110uninstall 76wcrtjob 35wcrtprf 81wcrtprfmgr 81wdistrib 88wdmcmd 106wdmdistrib 12, 106wdmeditprf 85, 92, 97, 98, 99, 101,

103, 104wdmeng 106wdmlseng 106, 107wdmmn 106wdmtrceng 106wdneditprf 84wlsnotif 97wrubjob 38wruntask 16, 21, 30, 68, 75wschedjob 40wsetadmin 7wsetpm 81wsiebel 19, 26wsub 83

creating objects 11Creating resource objects 19, 24

verification of 25Customer Support viii

Ddata logging

customizing 103data mart, Tivoli Enterprise Data

Warehouse 52granting access to 52

data, historicalcontrol access to 47examine 47

dataless profile managersicon 82subscribers 81

DB2 Universal Database 47DB2 Warehouse Manager 47discover objects 11Discover Siebel eBusiness Applications

resourcestask 9

Discover task 19, 24du command 109

Ee-mail contact viiendpoint 2endpoints

checking health of 45dataless 81display data 45maintain monitoring processes

on 105removing profiles from 45starting or stopping resource models

on 45subscribing 82

enterprise nameviewing properties of 18

eventsnot generated 109

events, Tivoli Enterprise Consoledefined 63groups 64processing 63responding to 64sources 63viewing 64

Ffeedback about publications vii

Gglossary, online vi

Hhealth

example of health determination 108

health (continued)understanding resource 108

help, Tivoli Enterprise DataWarehouse 50

holesexample 93

IIBM Tivoli management environment

security 46IBM Tivoli Monitoring

built-in actions, adding 93built-in actions, editing 95built-in actions, removing 93IBM Tivoli Monitoring Web Health

Console 107logging, customizing 103notices, sending 97parameters, customizing 99resource model results 107scheduling monitoring period 102scheduling rules, creating 100Tasks, specifying 96thresholds 91Web Health Console 108

IBM Tivoli Monitoring Web HealthConsole 107

viewing resource model results withthe 45

ID, Siebel Administrator user 24interface options 2

Jjob

creating a 35, 38command line, from the 35desktop, from the 35

definition of a 29disabling a 41running a 38

command line, from the 38desktop, from the 38on specific endpoints 38

scheduling a 38, 39command line, from the 40desktop, from the 40

working with a 29Jobs

Siebel_Discover_Job 24

LList servers 25Logfile Adapter Format file

adding Siebel message formats tothe 67

loggingcustomizing 103

135

LogsSiebel

Broker Logs 22Gateway Logs 22managing 21Server Logs 22viewing 21

Tivolicallback 23endpoint 23managing 23viewing 23

Mmanaged node

memory requirements 109managed resources 2

properties 17, 20, 24manuals

feedback vonline vordering v

messages 111monitoring profiles, defined 80

Nnotices

sending 97

Oobject parameters

editing 24objects

creating 11discovering 11

odstsat command 110online publications viiordering publications viioutput display error 109

Pparameters

customizing resource model 99processes, monitoring on gateways 106profile managers

creating 80dataless 81setting up 80subscribing endpoints 82subscribing objects 11

profilescreating 80monitoring 80

propertiesSiebel Gateway objects 18Siebel server 18

publicationsfeedback vonline vordering v

Rreports, Tivoli Enterprise Data

Warehouse 48, 52, 54resource

broker 15check status of 16gateway 15health of 45objects 15server 15starting 20stopping 20viewing properties of a 17, 19

resource health, understanding 108resource models

built-in actions, adding 93built-in actions, editing 95built-in actions, removing 93distribute 10, 11do not start 109parameters, customizing 99results, viewing 107scheduling monitoring period 102scheduling rules, creating 100Tasks, specifying 96thresholds, customizing 91viewing results of a 45

resource status 110results, resource models, viewing 107rules, Tivoli Enterprise Console

about 63

SScheduler 39scheduling

for monitoring 100jobs 89resource models 100rules 100

securityIBM Tivoli management

environment 46setup guidelines 3

quick reference table 3Siebel Connection Broker

properties 17Siebel Connection Broker properties

endpoint 18enterprise name 17host name 18installation path 17managed node 18Tivoli label 17

Siebel Discovery taskexception in output 110

Siebel eBusiness Applications resourcesdiscovering 9

Siebel Gatewayobject properties 18

Siebel Gateway object propertiesendpoint 18gateway name 18gateway version 18hostname 18installation path 18

Siebel Gateway object properties(continued)

managed node 18Tivoli label 18

Siebel Logsize 109

Siebel Logsmanaging 21viewing 21

Siebel serverobject properties 18

Siebel server propertiesendpoint 18gateway name 18hostname 18installation path 18managed node 18server name 18server version 18Tivoli label 18user name 18

Start_Connection_Broker 20Start_Siebel_Gateway 20Start_Siebel_Server 20Stop_Connection_Broker 20Stop_Connection_Broker task 110Stop_Siebel_Gateway 20Stop_Siebel_Server 20subscribing

endpoints 82objects 11

Ttask library

opening the 33, 35Tasks

customizing 33defined 29Discover 24libraries 61Run_Srvrmgr_Command 25running 30running on a specific endpoint 32running on Tivoli Business Systems

Manager objects 75Siebel Event Tasks 61

Configure_Event_Server 61Configure_Logfile_Broker_Message

Formats 61Configure_Logfile_Server_Message

Formats 61Control_Logfile_Adapter 61TBSM_Discover 61

Siebel Operational Tasks 61, 62Archive_Siebel_Logs 61Check_Server_Status 62Control_Component_Groups 62Control_Siebel_Tasks 62Run_List_Command 62Run_Srvrmgr_Command 62Start_Connection_Broker 62Start_Siebel_Gateway 62Start_Siebel_Server 62Stop_Connection_Broker 62Stop_Siebel_Gateway 62Stop_Siebel_Server 62


Tasks (continued)Siebel Utility Tasks 62

Delete Endpoint Utilities 62Discover 62

Siebel_Discover_Job 24Siebel_TBSM_Discover_Job 74specifying for an event 96Start_Connection_Broker 20Start_Siebel_Gateway 20Start_Siebel_Server 20Stop_Connection_Broker 20, 110Stop_Siebel_Gateway 20Stop_Siebel_Server 20TBSM_Discover 74working with 29

terminology conventions viiithresholds

customizing resource models 91Tivoli Business Systems Manager

components 73defining objects to manage with 74description of 73managing objects with 74removing objects from 76

Tivoli Customer Support viiiTivoli Enterprise Console 63

configuringoverview 64

console 64event class

definition files 70, 71event classes 69

Connection Broker Logfileevents 70

Logfile events 69Resource models events 70

event groupsdefinition 64

event typesresource model 64

eventsdefined 63processing 63responding to 64sources 63viewing 64

overview 63rules 69

overview 63rules, list of 71

Tivoli Enterprise Data WarehouseCentral data warehouse

component 48Control server component 47customize reports 48data logging 104Data marts component 48data marts, control access to 48enabling 47list of reports 53online help 50reports 48

creating 52default setting 56modify default setting of 52, 55running automatically 52, 55running manually 52, 54

Tivoli Enterprise Data Warehouse(continued)

roles 49users and user groups 49

Tivoli environmentsetting authorization roles 7starting

command line 5desktop 5

Tivoli Logscallback

managing 23viewing 23

endpoint 23typeface conventions viii

Uuninstall command 76

Vvariables, specifying environment ixviewing object properties with

wsiebel 19

Wwcrtjob command 35wcrtprf command 81wcrtprfmgr command 81wdistrib command 88wdmcmd command 106wdmdistrib command 12, 106wdmeditprf command 85, 92, 97, 98, 99,

101, 103, 104wdmeng command 106wdmlseng command 106, 107wdmmn command 106wdmtrceng command 106wdneditprf command 84Web Health Console

IBM Tivoli Monitoring 108viewing resource model results with

the 45wlsnotif command 97wrunjob command 38wruntask command 16, 21, 30, 68, 75wschedjob command 40wsetadmin command 7wsetpm command 81wsiebel command 19, 26wsub command 83

Index 137

��

Printed in U.S.A.

SC23-4819-00

IBM Tivoli Monitoring for Applications: Siebel...

Documents

Transcript of IBM Tivoli Monitoring for Applications: Siebel...