Tivoli Manager for Siebel eBusiness...

Tivoli Manager for Siebel eBusinessApplicationsUser’s Guide Version 1.1.0

Tivoli Manager for Siebel eBusiness Applications User’s Guide

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No partof this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language,in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior writtenpermission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of anymachine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyrightnotice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is notintended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorporation.

Trademarks

IBM, Tivoli, the Tivoli logo, AIX, Tivoli Enterprise, Tivoli Enterprise Console, and TME are trademarks or registered trademarks ofInternational Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, othercountries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Accessing the Files on the Product CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Accessing the Files on the Tivoli Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . x

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Installing Tivoli Manager for SiebeleBusiness Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installing from the Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Uninstalling Tivoli Manager for Siebel eBusiness Applications. . . . . . . . . . . . 6

Uninstalling from an Endpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Uninstalling from a Tivoli Management Region . . . . . . . . . . . . . . . . . . . 6

Tivoli Inventory Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Getting started with the Tivoli Manager forSiebel eBusiness Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Assigning Tivoli Manager for Siebel eBusiness Applications Authorization. . . 9

Assigning Tivoli Management Region Roles to a Tivoli Administrator . . . . . 10

iiiTivoli Manager for Siebel eBusiness Applications

Assigning Resource Roles to a Tivoli Administrator . . . . . . . . . . . . . . . . . . . 10

Subscribing Servers to a Profile Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Starting the Tivoli Manager for Siebel eBusiness Applications . . . . . . . . . . . 12

Chapter 3. Subscription Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Subscribing Siebel Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4. Tivoli Manager for Siebel eBusinessApplications Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Task Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Tivoli Manager for Siebel eBusiness Applications Tasks. . . . . . . . . . . . . . . . 18

Configure_Siebel_Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configure_Siebel_Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Display_Siebel_Servers_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 20

List_Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Offline_Component_Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Online_Component_Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Remove_Tivoli_Manager_for_Siebel_Files . . . . . . . . . . . . . . . . . . . . . . 21

Restart_Gateway_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Restart_Resonate_Connection_Broker . . . . . . . . . . . . . . . . . . . . . . . . . 23

Restart_Siebel_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Run_Srvrmgr_Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Start_Connection_Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Start_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Start_Siebel_Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Start_Siebel_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Stop_Connection_Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Stop_Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Stop_Siebel_Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Stop_Siebel_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

iv User’s Guide Version 1.1.0

Running a Siebel Job and Saving the Output . . . . . . . . . . . . . . . . . . . . . . . . 27

Modifying a Siebel Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Modifying for All Future Executions of the Job . . . . . . . . . . . . . . . . . . 27

Modifying for a Single Execution of the Job . . . . . . . . . . . . . . . . . . . . 28

Chapter 5. Resource Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . 31Using Tivoli Manager for Siebel eBusiness Applications Monitors . . . . . . . . 31

Viewing the Status of Monitored Resources . . . . . . . . . . . . . . . . . . . . . . . . . 33

Siebel Resource Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SiebelServerStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SiebelProcesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ActiveSiebelTasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

ConnectionBrokerStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

GatewayNameServerStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 6. Enterprise Event Management . . . . . . . . . . . . . . 37Configuration Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Creating a New Rule Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Adding an Existing Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring the Logfile Adapter for Siebel . . . . . . . . . . . . . . . . . . . . . . . . . 40

Events and Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Siebel Logfile Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Resonate (Connection Broker) Logfile Events . . . . . . . . . . . . . . . . . . . . . . . 41

Tivoli Distributed Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Rules for Tivoli Manager for Siebel eBusiness Applications Events . . . . . . . 43

Chapter 7. Troubleshooting the Tivoli Manager forSiebel eBusiness Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 45

vTivoli Manager for Siebel eBusiness Applications

Installation Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Questions on Running Tasks from the Desktop . . . . . . . . . . . . . . . . . . . . . . 47

Questions on Using Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Questions on Using the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . 49

Appendix A. Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

vi User’s Guide Version 1.1.0

Preface

The Tivoli Manager for Siebel eBusiness Applications User’s Guideprovides information about integrating the Tivoli Framework withthe Siebel eBusiness Applications product. This guide provides thetasks and troubleshooting for this module.

Who Should Read This GuideThis guide is for system administrators who monitor and manageTivoli Framework components. This guide requires knowledge ofTivoli management software, UNIX and Windows operating systems,databases, and Siebel products.

Prerequisite and Related DocumentsThe following documents also provide useful information related toTivoli Manager for Siebel eBusiness Applications:

¶ Tivoli Framework User’s Guide

¶ Tivoli Framework Planning and Installation Guide

¶ Tivoli Framework Reference Manual

¶ Tivoli Enterprise Console Rule Builder’s Guide

¶ Tivoli Enterprise Console User’s Guide

¶ Tivoli Enterprise Console Reference Manual

¶ Tivoli Enterprise Console Event Integration Facility Guide

¶ Tivoli Enterprise Console Adapters Guide

¶ Tivoli Distributed Monitoring User’s Guide

What This Guide ContainsThis User’s Guide contains the following chapters:

¶ “Installing Tivoli Manager for Siebel eBusiness Applications” onpage 1

viiTivoli Manager for Siebel eBusiness Applications

Describes the basic features and functions of Tivoli Manager forSiebel eBusiness Applications .

¶ “Getting started with the Tivoli Manager for Siebel eBusinessApplications” on page 9

Shows how to launch the module in your Tivoli Manager forSiebel eBusiness Applications collection.

¶ “Subscription Lists” on page 15

Describes the subscription lists for Siebel servers and how yousubscribe the endpoints to them.

¶ “Tivoli Manager for Siebel eBusiness Applications Tasks” onpage 17

Describes the tasks that the Tivoli Manager for Siebel eBusinessApplications provides.

¶ “Resource Monitoring” on page 31

Describes the monitoring capabilities of Tivoli Manager forSiebel eBusiness Applications.

¶ “Enterprise Event Management” on page 37

Explains the events that affect Siebel or the system on whichSiebel is running and how Tivoli Manager for Siebel eBusinessApplications responds to these events.

¶ “Troubleshooting the Tivoli Manager for Siebel eBusinessApplications” on page 45

Describes the logging facilities in Tivoli Manager for SiebeleBusiness Applications.

¶ “Messages” on page 51

Contains a list of the messages produced by Tivoli Manager forSiebel eBusiness Applications.

Conventions Used in This GuideThe guide uses several typeface conventions for special terms andactions. These conventions have the following meanings:

Bold Commands, keywords, file names, authorizationroles, URLs, or other information that you must use

viii User’s Guide Version 1.1.0

appear in bold. Names of windows, dialogs, andother controls also appear in bold.

Italics Variables and values that you must provide appear initalics. Words and phrases that are emphasized alsoappear in italics.

Monospace Code examples, output, and system messages appearin a monospace font.

This guide uses the UNIX convention for specifying environmentvariables and for directory notation. When using the Windows NTcommand line, replace $variable with %variable% for environmentvariables and replace each forward slash (/) with a backslash (\) indirectory paths.

Note: When using the bash shell on a Windows NT system, you canuse the UNIX conventions.

Accessing Publications OnlineThe Tivoli Customer Support Web site(http://www.tivoli.com/support/) offers a guide to support services(the Customer Support Handbook); frequently asked questions(FAQs); and technical information, including release notes, user’sguides, redbooks, and white papers. You can access Tivolipublications online at http://www.tivoli.com/support/documents/. Thedocumentation for some products is available in PDF and HTMLformats. Translated documents are also available for some products.

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

Resellers should refer tohttp://www.tivoli.com/support/smb/index.html for more informationabout obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” on page xifor more information about obtaining Tivoli technical documentation.

ixTivoli Manager for Siebel eBusiness Applications

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

Accessing the Files on the Product CDThe .pdf and the .htm files, for the Tivoli Manager for SiebeleBusiness Applications User’s Guide are available on the TivoliManager for Siebel eBusiness Applications CD in the DOCdirectory.

Accessing the Files on the Tivoli Web SiteThe Tivoli Manager for Siebel eBusiness Applications User’s Guideand the Tivoli Manager for Siebel eBusiness Applications ReleaseNotes are available at the following location on the Tivoli Web site:http://www.tivoli.com/support/documents.

You must be a registered user to access this Web site. If you havenot registered, when the Username and Password Required prompt isdisplayed, click Cancel and follow the registration directions.

TerminologyThe following Tivoli Manager for Siebel eBusiness Applicationsterms are used throughout this document:

componentA small binary object or program that performs a specificfunction and is designed in such a way as to easily operatewith other components and applications.

siebel serverThis server supports the processes for Siebel Clients.

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

www.tivoli.com/products/documents/glossary.

The term UNIX in this document means AIX®, Solaris, and HP-UXplatforms.

The term Windows™ in this documents means Windows NT™ andWindows 2000 platforms.

x User’s Guide Version 1.1.0

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

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or bycalling one of the following telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey athttp://www.tivoli.com/support/survey/.

Contacting Customer SupportThe Tivoli Customer Support Handbook athttp://www.tivoli.com/support/handbook/ provides information aboutall aspects of Tivoli Customer Support, including the following:

¶ Registration and eligibility.

¶ How to contact support, depending on the severity of yourproblem.

¶ Telephone numbers and e-mail addresses, by country.

¶ What information you should gather before contacting support.

xiTivoli Manager for Siebel eBusiness Applications

http://www.tivoli.com/support/Prodman/html/pub_order.html

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

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

xii User’s Guide Version 1.1.0

Installing Tivoli Manager forSiebel eBusiness Applications

The Tivoli Manager for Siebel eBusiness Applications provides anintegration of the Tivoli Framework with the Siebel eBusinessApplications product. This integration allows centralizedmanagement of the Siebel application across a multi-platformnetwork. This module provides the following features for managingthe Siebel application:

¶ Siebel-specific tasks and jobs

¶ Siebel-specific monitors for Tivoli Distributed Monitoring

¶ Tivoli Enterprise Console events and rule sets customized forSiebel

¶ Subscription lists for Siebel Application and Gateway Nameservers

¶ Tivoli Inventory Software Signatures for core Siebel files

Note: The Tivoli Distributed Monitoring and Tivoli EnterpriseConsole applications must be installed and configured beforetheir corresponding Tivoli Manager for Siebel feature isoperational.

1

1Tivoli Manager for Siebel eBusiness Applications

1.In

stalling

Installation RequirementsBefore attempting to install Tivoli Manager for Siebel into the TivoliFramework, make certain you review the requirements in thissection. The following table provides the context and authorizationrole required to install this module.

Activity Context Required Role

Installing TivoliManager for SiebeleBusiness Applications

Tivoli install_product

Installing from the DesktopUse the following steps to install Tivoli Manager for SiebeleBusiness Applications from the Tivoli desktop:

1. Select the Install -> Install Product... option from the TivoliDesktop menu to display the Install Product dialog.

If the Tivoli Manager for Siebel eBusiness Applications Moduleis listed in the Select Product to Install scrolling list, skip tostep 3 on page 3. If it is not listed, proceed to step 2 on page 3.

2 User’s Guide Version 1.1.0

2. Select the Select Media... button to display the File Browserdialog.

The File Browser dialog enables you to identify or specify thepath to the installation media.

a. From the Hosts scrolling list, choose the host on which theinstall media is mounted. Choosing a host updates theDirectories scrolling list to show the directories of the hostyou chose.

b. From the Directories scrolling list, choose the directorycontaining the install media.

c. Press the Set Media & Close button to save the new mediapath and return to the Install Product dialog. The dialog nowcontains a list of products that are available for installation.

3. If this is first Plus module installed, the Plus Module Supportproduct must be installed before installing the Tivoli Manager forSiebel eBusiness Applications module. See the installationprocess in step 4 for details.


1.In

stalling

4. Select Tivoli Manager for Siebel eBusiness Applications from theSelect Product to Install list.

To specify the clients on which the module will be installed, usethe arrow keys to move machine names between the Clients toInstall On scrolling list and the Available Clients scrolling list.

By default, all Tivoli Managed Nodes in the current TivoliManagement Region are listed in the Clients to Install Onscrolling list. To move a machine name to the Available Clientslist (and thus remove from the target list), choose one or moreclients from the Clients to Install On scrolling list and press theright arrow button. The chosen clients are moved from theClients to Install On scrolling list to the Available Clientsscrolling list. Tivoli Manager for Siebel eBusiness Applicationsshould be installed on the Tivoli Management Region Server, andall endpoint gateways.

5. Press the Install & Close button to install the module and closethe Install Product dialog. - OR -


Press the Install button to install the module and keep the InstallProduct dialog open. You can then install Tivoli Manager forSiebel eBusiness Applications on another set of clients or youcan install another product.

The installation process prompts you with a Product Installdialog.

This dialog provides the list of operations that take place wheninstalling the software. This dialog also warns you of anyproblems that you may want to correct before you install theSiebel Plus for Tivoli module.

6. Press the Continue Install button to begin the installationprocess or Press the Cancel button to abort the installationprocess.

7. Press the Close button when the Product Install status dialogindicates that the installation is complete.

Installing from the Command LineUse the winstall command to install Tivoli Manager for SiebeleBusiness Applications. The following example is the syntax for thewinstall command and its parameters:winstall -c cdrom_path -s installation_server -i index_file node

where:

-c cdrom_pathSpecifies the path to the CD-ROM image.

-s installation_serverSpecifies the server on which the product is to be installed.

-i index_fileSpecifies the index file from which the product is to be installed(SIEBEL.IND for the module and LNK31_32.IND for the PlusModule Support product).

NodeSpecifies the Tivoli managed node target for the module.


1.In

stalling

Uninstalling Tivoli Manager for Siebel eBusinessApplications

A script is provided to remove Tivoli Manager for Siebel eBusinessApplications from all nodes in the Tivoli Management Region.

Back up the database and the Tivoli management region serverinstall directory before running the uninstall script.

Uninstalling from an EndpointYou can run the Remove_Tivoli_Manager_for_Siebel_Files task todelete product files from the endpoints or managed nodes. Refer to“Remove_Tivoli_Manager_for_Siebel_Files” on page 21 for moreinformation on this task.

After you have removed the product from the Tivoli managementregion, you cannot run theRemove_Tivoli_Manager_for_Siebel_Files task again until youinstall the product again.

Uninstalling from a Tivoli Management RegionThis procedure uninstalls Tivoli Manager for Siebel eBusinessApplications from the Tivoli Management Region and optionally onall endpoints and managed nodes.

Enter the following command from the command prompt:$BINDIR/../generic_unix/TME/PLUS/SIEBEL/siebel_uninstall.sh

-rmfiles -endpoints -all

where:

-rmfilesIndicates that all product files are to be removed.

-endpointsIndicates that the Remove_Tivoli_Manager_for_Siebel_Files taskwill be run on all endpoints that are a members of either theSiebel Application Server Subscribers or the Siebel GatewayName Server Subscribers profile manager.


-allIndicates that the Remove_Tivoli_Manager_for_Siebel_Files taskwill be run on all managed nodes where the Tivoli Manager forSiebel eBusiness Applications module has been installed.

Note: The log file on the Tivoli management region server is calledSIEBEL_uninstall.log and is written to the directory returnedby the wtemp command.

Note: The usage for the siebel_uninstall.sh command can beretrieved by passing in the ″-?″ or ″-help″ parameter. Theusage is as follows:siebel_uninstall.sh [-rmfiles | -r] [-endpoints | -e] [-all

| -a] [-help | -?] [managed_nodes...]

where:

-rmfilesRemoves the scripts that were installed onto the TivoliManagement Region.

-endpointsRun the task that cleans the Tivoli Manager for Siebelfiles off of the endpoints that are members of the SiebelServer and Siebel Gateway subscription lists.

-allRuns the task that cleans the managed nodes that alsohave Tivoli Manager for Siebel eBusiness Applicationsinstalled.

-helpPrints the usage statement.

managed_nodesIf -all is not specified, you can list the managed nodesthat you would like the uninstall task to run on in order toremove Tivoli Manager for Siebel. If -all is specified thenthe managed nodes specified are ignored since the


1.In

stalling

uninstall task will be run on all managed nodes that alsohave the Tivoli Manager for Siebel eBusinessApplications installed.

Tivoli Inventory SignaturesThe Tivoli Manager for Siebel eBusiness Applications includes asoftware signature file for identifying core Siebel files to the TMEInventory application. This file (Siebelsigs.ini) will be located in theTivoli Manager for Siebel directory,<Tivoli root dir>/bin/generic Unix/TME/PLUS/SIEBEL

Please refer to the Inventory User’s Guide for details of loading newsoftware signatures.


Getting started with the TivoliManager for Siebel eBusinessApplications

This section describes how to configure Tivoli Manager for SiebeleBusiness Applications which involves the following sections:

1. Assign the Tivoli Manager for Siebel eBusiness Applicationsauthorization to one or more Tivoli administrators as described in“Assigning Tivoli Manager for Siebel eBusiness ApplicationsAuthorization”.

2. Assign Siebel Servers and Siebel Gateways to a Profile Manageras described in “Subscribing Servers to a Profile Manager” onpage 12.

3. Configure Tivoli Enterprise Console event handling, as describedin “Assigning Tivoli Manager for Siebel eBusiness ApplicationsAuthorization”.

4. Configure the Siebel Server and Siebel Gateway endpoints, asdescribed in “Configure_Siebel_Servers” on page 19 and“Configure_Siebel_Gateways” on page 18.

Assigning Tivoli Manager for Siebel eBusinessApplications Authorization

When you install Tivoli Manager for Siebel eBusiness Applications,two roles, siebel_senior and siebel_admin, are created.

2


2.G

etting

Started

All tasks require at least one of these roles to be assigned to theTivoli administrator who is running the task. In addition, some tasksrequire Tivoli authority as defined by Tivoli management regionroles. A Tivoli administrator must have the required Tivoli authorityand must have been assigned one of the Tivoli Manager for SiebeleBusiness Applications roles to successfully run these tasks andprocesses. You can assign Tivoli Manager for Siebel eBusinessApplications authorization as Tivoli management region roles or asresource roles, depending on local authorization requirements.

Assigning Tivoli Management Region Roles to aTivoli Administrator

To assign Tivoli management region siebel_senior and siebel_adminroles to a Tivoli administrator, follow these steps:

1. From the desktop, double-click the Administrators icon todisplay the Administrators window.

2. Right-click the appropriate Administrator icon and select EditTMR Roles from the pop-up menu. The Set TMR Roles dialogis displayed.

3. From the Available Roles scrolling list, do the following:

a. Select either the siebel_senior or siebel_admin role, or both.

b. Move the selected roles to the Current Roles scrolling listby clicking the left-arrow button.

4. Click Change and Close.

5. Exit the desktop.

6. Start the desktop again for the new roles to take effect.

Assigning Resource Roles to a Tivoli AdministratorTo add resource roles for a specific policy region to a Tivoliadministrator:

1. From the desktop, double-click the Administrators icon todisplay the Administrators window.


2. Right-click the appropriate Administrator icon and select EditResource Roles from the pop-up menu.

3. Select Tivoli Manager for Siebel eBusiness Applications fromthe Resources scrolling list.

4. From the Available Roles scrolling list,

a. Select either the siebel_admin or siebel_senior role, or both.

b. Move the selected roles to the Current Roles scrolling list byclicking the left arrow button.

5. Click Change and Close.

6. Exit the desktop.

7. Start the desktop again for the new roles to take effect.

8. To use the new roles as resource roles instead of TMR roles, dothe following:

a. Use the following command to add the Endpoint resource tothe current resources in the Tivoli Manager for SiebeleBusiness Applications policy region:wsetpr Endpoint "Tivoli Manager for Siebel eBusiness Applications"

b. Link the endpoint to the policy region where the roles areassigned using the following command, where endpoint_labelis the name of the endpoint to be linked to the policy region:wln @Endpoint:endpoint_label @PolicyRegion:

"Tivoli Manager for Siebel eBusiness Applications"

c. Use the following command to synchronize the endpoint datathat is stored by the endpoint manager, gateways, and theendpoint:wep sync_gateways


2.G

etting

Started

Subscribing Servers to a Profile ManagerTivoli Manager for Siebel eBusiness Applications automaticallycreates profile managers to help you group servers for management.Each profile manager has a list of subscribers that enables you to runtasks and monitors against all subscribers. The following profilemanagers are initially created:

¶ Siebel Application Server Subscribers

¶ Siebel Gateway Name Server Subscribers

Follow these steps to subscribe servers to a profile manager:

1. Right-click on one of the profile managers and selectSubscribers from the pop-up menu.

2. Select the desired endpoints from the Available to BecomeSubscribers scrolling list and move them to the CurrentSubscribers list by clicking the left-arrow button.

3. Click Set Subscriptions & Close to subscribe the servers to thelist.

Starting the Tivoli Manager for Siebel eBusinessApplications

All Tivoli Manager for Siebel eBusiness Applications modules arekept in a collection under the TivoliPlus icon on the Tivoli desktop.The Siebel icon is added to this collection after installation.

Use the following steps to see the modules included in your SiebelPlus for Tivoli collection:

1. From the main Tivoli desktop, double-click on the TivoliPlusicon or select the Open... option from the TivoliPlus icon’spop-up menu to display the Tivoli Manager for Siebel eBusinessApplications window.


Here is an example of the Tivoli desktop.

2. The TivoliPlus window displays an icon for each Plus moduleinstalled. Double-click on the Tivoli Manager for SiebeleBusiness Applications icon or select the Open... option from theTivoli Manager for Siebel eBusiness Applications icon’s pop-upmenu.

Here is an example of theTivoli Manager for Siebel eBusinessApplications window.


2.G

etting

Started

This will display the icons representing the tasks and other toolsfor managing the Siebel product.


Subscription Lists

The Tivoli Manager for Siebel eBusiness Applications creates twoprofile managers to serve as subscription lists for Siebel relatedservers, Siebel Application Server Subscribers and SiebelGateway Name Server Subscribers. Subscribing Siebel nodes(endpoints) to the appropriate Tivoli Manager for Siebel eBusinessApplications subscription list will add them to the default targetslists of the custom tasks/jobs and process monitors created with themodule. While this does not initiate any action on the endpoints, itwill allow the user to execute tasks or deploy monitors to many orall Siebel endpoints at one time.

Subscribing Siebel NodesThe following steps detail the process of subscribing Siebel Nodes tothe appropriate subscription list:

1. From the Tivoli Manager for Siebel eBusiness Applicationsscreen, select the Subscribers... option from the SiebelApplication Server Subscribers icon’s pop-up menu to display theSubscribers window.

2. The Subscribers window displays Current and Availablesubscribers to this profile manager. Highlight nodes and use thearrows in the middle to move them to or from the CurrentSubscribers list; when the list is complete with all Siebel

3


3.S

ub

scriptio

nL

ists

Application Servers, press Set Subscriptions & Close.

3. Repeat this process for the Siebel Gateway Name ServerSubscribers profile manager.


Tivoli Manager for SiebeleBusiness Applications Tasks

Tivoli Manager for Siebel eBusiness Applications provides jobs thatallow you to run Siebel tasks on multiple machines and operatingsystems. These jobs are ready to be executed as soon as you haveconfigured your Tivoli Manager for Siebel eBusiness Applicationsmodule. Simply double-click on the job icon to execute the Siebeljob; by default, it will be executed on all targets in the appropriatesubscription list. You can modify the default execution characteristicsof a particular job, such as where the output of a job is displayedand on which machines the job will run.

Task AuthorizationsTasks run from the Tivoli Manager for Siebel eBusiness Applicationstasks libraries are controlled by the resource roles. The roles andtheir uses are as follows:

siebel_seniorRequired for configuring the event server, Siebel gateways,and Siebel servers.

siebel_adminRequired for starting and stopping the Siebel servers, Siebelgateways, and logging.

4


4.Tasks

Tivoli Manager for Siebel eBusiness ApplicationsTasks

The following section lists the Siebel jobs that can be customizedand executed with Tivoli Manager for Siebel. Double-click on thetask icon to run the Siebel job on all subscribers, or select the Runon selected subscribers... option from the job icon’s pop-up menuto display the Execute Task window and choose only selectedendpoints to receive the task.

Note: The Configure_Siebel_Servers and/orConfigure_Siebel_Gateways tasks are required to be runbefore most other module elements are functional. These tasksprepare the systems to run administrative tasks and distributedmonitors.

Note: Be aware that the by default target lists of these tasks areSiebel Application Server Subscribers and/or Siebel GatewayName Server Subscribers. Double-clicking on a job can haveimmediate and wide reaching effects, such as starting orstopping all Siebel Servers. The jobs can also be run againstindividual endpoints.

Configure_Siebel_GatewaysDescription:

Registers Siebel Gateway Name Server information with theendpoint on a node.

Parameters:SIEBEL_ROOT path: directory path where the bin directorycan be located for this Gateway (i.e. c:\sea621\gtwysrvr or/siebel/gtwysrvr). This path may not contain spaces; use theDOS 8.3 name for any directory as necessary.

Job Targets:Siebel Gateway Name Server Subscribers

Notes: If SIEBEL_ROOT path is consistent, the task can bedistributed to multiple Gateway machines at one time.


Configure_Siebel_ServersDescription:

Registers Siebel Application server information with theendpoint on a node. The server must be running when thisjob is executed.

Parameters:

Siebel Enterprise Name:name of the Siebel Enterprise to which this serverbelongs.

Siebel Server Name:name of the Siebel Application Server.

SIEBEL_ROOT path:directory path where the bin directory can be located forthis server (i.e. c:\sea621\siebsrvr or /siebel). This pathmay not contain spaces; use the DOS 8.3 name for anydirectory as necessary (i.e. use c:\prograx1 forc:\Program Files).

Siebel Administrator Username:User name that can be used to initiate servermanagement commands and queries through the srvrmgrcommand line interface or srvrmgr command. Thesenames are case sensitive. Be sure to enter the namesexactly as they were defined to Siebel.

Siebel Administrator Password:Password of the administrative user.

Job Targets:Siebel Application Server Subscribers

Notes: The Siebel Enterprise and Server names are only requiredwhen multiple Siebel application servers are running on asingle node. If only one server is running, these fields can beleft blank. If SIEBEL_ROOT paths and Username/Passwordsare consistent, this allows the task to be distributed to manynodes at one time, while still performing the necessarycustomization. This same method is used throughout this


4.Tasks

module. Also note that these names are case sensitive; besure to enter them as defined to Siebel.

Display_Siebel_Servers_ConfigurationDescription:

Displays the Siebel Application and Gateway Name Serverinformation that has been registered on a node.

Parameters:None

Job Targets:Siebel Application Server Subscribers and Siebel GatewayName Server Subscribers

List_ComponentsDescription:

Displays a list of the components on a Siebel Server alongwith their status.

Parameters:




Note: The Siebel Enterprise and Server names are only requiredwhen multiple Siebel Application servers are running on asingle node.

Offline_Component_GroupDescription:

Brings offline a Siebel component group on a SiebelApplication server.

Parameters:


Component Group:The alias name of a Siebel Component Group.

Siebel Enterprise Name:The name of the Siebel Enterprise to which this serverbelongs.

Siebel Server Name:The name of the Siebel Application Server.


Notes: The Siebel Enterprise and Server names are only requiredwhen multiple Siebel Application servers are running on asingle node.

Online_Component_GroupDescription:

Brings online a Siebel component group on a SiebelApplication server.

Parameters:

Component Group:Alias name of a Siebel Component Group.





Remove_Tivoli_Manager_for_Siebel_FilesDescription:

This task deletes all supporting files (such as logs and


4.Tasks

message catalogs) that the Tivoli Manager for Siebel has puton the targeted endpoints or gateways. This task alsodisables, but does not delete, any probes that weredistributed from the Siebel monitoring collections to allspecified endpoints. The monitor definitions are not disabledon the Tivoli management region.

If you do intend to use the endpoint again, you must rerunthe Configure_Siebel_Servers task and/or theConfigure_Siebel_Gateways task. The appropriate files willbe copied as needed.

If you do not intend to use this endpoint again, unsubscribeit from any Profile Managers to which it is subscribed anddelete the probes using the wdelprb command. See to theTivoli Distributed Monitoring User’s Guide for moreinformation.

If debug is on when you run this task, the associated log fileremains on the endpoint. You can rerun this task to removethe SIEBEL_delete_utils.log file.

Parameters:None.

Note: This task is not visible in the Tivoli Manager for SiebeleBusiness Applications collection. It can be run separatelyfrom the uninstall script to clean up endpoints or managednodes that no longer need Siebel files. To do this issue thefollowing command:wruntask -t Remove_Tivoli_Manager_for_Siebel_Files

-l "Hidden Tasks for Siebel" -h task_endpoint

Restart_Gateway_ServerDescription:

Restarts the Siebel Gateway Name Server NT Service/Unixdaemon after the server failed.

Parameters:none.

Notes: This task is not visible in the Tivoli Manager for Siebel


eBusiness Applications collection, because it is used only byDistributed Monitoring to initiate a restart after detecting afailure.

Restart_Resonate_Connection_BrokerDescription:

Restarts the Resonate agent NT Service/Unix daemon afterthe agent failed.

Parameters:none.

Notes: This task is not visible in the Tivoli Manager for SiebeleBusiness Applications collection, because it is used only byDistributed Monitoring to initiate a restart after detecting afailure.

Restart_Siebel_ServerDescription:

Restarts the Siebel Application server NT Service/Unixdaemon after the server failed.

Parameters:none.

Notes: This task is not visible in the Tivoli Manager for SiebeleBusiness Applications collection, because it is used only byDistributed Monitoring to initiate a restart after detecting afailure.

Run_Srvrmgr_CommandDescription:

Runs any valid srvrmgr command on a Siebel Applicationserver such as list server and enable compgrpcomponent_group

Parameters:

Server Manager Command:Any valid command string that can be executed at thesrvrmgr> prompt


4.Tasks





Start_Connection_BrokerDescription:

Starts the Resonate Central Dispatch Agent NT Service/Unixdaemon on a node.

Parameters:None

Job Targets:Siebel Application Server Subscribers and Siebel GatewayName Server Subscribers.

Notes: This task should stay in serial mode.

Start_LoggingDescription:

This task turns tracing on for all Tivoli Manager for SiebeleBusiness Applications tasks and monitors. All tasks andmonitors will create a separate log file when run in the$LCF_DATDIR/Siebel_logs.

Parameters:None.



Start_Siebel_GatewayDescription:

Starts the Siebel Gateway Name Server NT Service/Unixdaemon on a node.

Parameters:None

Job Targets:Siebel Gateway name Server Subscribers

Start_Siebel_ServerDescription:

Starts the Siebel Application server NT Service/Unix daemonon an endpoint.

Parameters:





Stop_Connection_BrokerDescription:

Stops the Resonate Central Dispatch Agent NT Service/Unixdaemon on a node.

Parameters:None



4.Tasks

Notes: This task will attempt to stop all running servers andgateways.

Stop_LoggingDescription:

This task turns tracing off for all Tivoli Manager for SiebeleBusiness Applications tasks and monitors.

Parameters:None.

Job TargetsSiebel Application Server Subscribers and Siebel GatewayName Server Subscribers.

Stop_Siebel_GatewayDescription:

Stops the Siebel Gateway Name Server NT Service/Unixdaemon on a node.

Parameters:None

Job Targets:Siebel Gateway Name Server Subscribers

Stop_Siebel_ServerDescription:

Stops the Siebel Application server NT Service/Unix daemonon a node.

Parameters:






Running a Siebel Job and Saving the OutputTo run a Siebel job with the default execution characteristics,double-click on the icon or right-click and select Run job... from theicon’s pop-up menu.

The job’s output is displayed in an output window. To save the job’soutput to a file:

1. Select the Save to File... button to display the Save Job Outputdialog box.

2. Enter the name of the machine on which to save the output filein the On Host field.

3. Enter the name of the output file that will contain the job’soutput in the Output File field.

4. Select the Save & Close button to save the output of the job tothe file you specified.

You can also use the Modify job... option of the job icon’s pop-upmenu to specify that the output be sent to a file.

Modifying a Siebel JobYou can modify the execution characteristics of a job for each timethe job is run or for only a single execution of the job.

Modifying for All Future Executions of the Job1. Select the Modify job... option from the job icon’s pop-up menu

to display the Edit Job window.


4.Tasks

Here is an example of a Edit Job dialog.

2. Make the necessary changes in the Edit Job window. Onlinehelp is available to assist you.

3. Click on the Change & Close button when finished.

Modifying for a Single Execution of the JobUse the following steps to modify a job for only a single executionof the job. The next time you run the same job, it will return to thedefault execution characteristics.


1. Select the Run on selected subscribers... option from the jobicon’s pop-up menu to display the Execute Task window.

2. Make the necessary changes in the Execute Task window tospecify the targets and options. Online help is available to assistyou.

Here is an example of an Execute Task dialog.

3. Click on the Execute & Dismiss button when finished.


4.Tasks

Resource Monitoring

Tivoli Manager for Siebel eBusiness Applications provides theability to monitor critical resources with Tivoli DistributedMonitoring. The monitors for Tivoli Distributed Monitoring arepredefined to enable you to monitor the status of the Siebel serversand different aspects of the Siebel environment. These monitorsallow you to quickly identify and respond to potential problems sothat system downtime is avoided.

Using Tivoli Manager for Siebel eBusinessApplications Monitors

The Tivoli Manager for Siebel comes with monitoring collections forApplication Server, Gateway Name Server, and Connection Broker(Resonate) processes.

These monitors check the status of Siebel Servers and run on theendpoint where Siebel services are installed. As with most of thetasks/jobs, these monitors require the Siebel Servers and Gatewaysbe registered with the Configure_Siebel_Servers orConfigure_Siebel_Gateways task before they will properly function.

Before these monitors are operational, they must be distributed totheir subscription lists. To distribute a monitor with the predefinedsettings to the default target list, simply select the Distribute...

5


5.R

esou

rceM

on

itorin

g

option from the monitor’s pop-up menu.

Then click on the Distribute Now button.

To modify the default subscription list of a particular monitor, selectthe Subscribers... option from the monitor’s pop-up menu.

Although the Tivoli Manager for Siebel eBusiness Applicationsserver monitors come already defined to monitor resources specificto Siebel, you can add monitors from the Tivoli DistributedMonitoring collection or delete monitors as you wish. You can alsoedit existing monitors to perform different actions under differentconditions.

Selecting the options on a Siebel monitor’s pop-up menu displaysthe usual Tivoli Distributed Monitoring windows. Refer to the TivoliDistributed Monitoring documentation for more detailed informationon using this window.


Viewing the Status of Monitored ResourcesUse the Indicators for Siebel Monitors icon to view the status of themonitored resources.

The thermometer on the Indicators for Siebel Monitors icon risesas the status of a monitored resource becomes more urgent. Open theApplication, Gateway Name Server, or Connection BrokerMonitors for Siebel icon to view the status of the Siebel serverresources on remote machines. For each monitored resource, themonitor only reports the most urgent status received within a recenttime frame. The monitor reports are organized so that the mosturgent status level appears at the top of the report.

For more information on viewing the status of a monitored resource,refer to the Tivoli Distributed Monitoring documentation.

Siebel Resource MonitorsBelow is a description of each of the Tivoli Manager for SiebeleBusiness Applications monitors, their required parameters, and theautomated actions included with each.

SiebelServerStatusThe SiebelServerStatus monitor checks whether the SiebelApplication Server NT service/Unix daemon is running. This monitoraccepts 2 arguments – the enterprise name and server name of theSiebel Server to monitor. As with most other Tivoli Manager forSiebel eBusiness Applications functions, these are only required if


5.R

esou

rceM

on

itorin

g

more than 1 Siebel server is running on the node to which you willdistribute the monitor; if only 1 is running, these can be left blank orset to ’default’.

This monitor is preconfigured in the Application Server Monitors forSiebel profile to do the following:

¶ Run every fifteen minutes

¶ When the service/daemon goes down, a Fatal event is sent to theTivoli Enterprise Console and the appropriate indicator icon isupdated. A task is run to restart the Siebel Server service/daemonby default.

¶ When the Siebel Server service/daemon status changes to up, aHarmless event is sent to the Tivoli Enterprise Console and theindicator icon is updated. This Harmless up event will close theopen ″down″ event.

¶ When the service/daemon is down, a Critical event is sent to theTivoli Enterprise Console and the appropriate indicator icon isupdated.

SiebelProcessesThe SiebelProcesses monitor returns the number of Siebel initiatedprocesses that are running on an endpoint.

This monitor is not preconfigured, but can be added with userspecific thresholds.

ActiveSiebelTasksThe ActiveSiebelTasks monitor returns the number of running taskswithin a Siebel server. This monitor accepts two arguments – theenterprise name and server name of the Siebel Server to monitor.Again, these are only required if more than one Siebel server isrunning on the node to which you will distribute the monitor.

This monitor is not preconfigured, but can be added with userspecific thresholds.


ConnectionBrokerStatusThe ConnectionBrokerStatus monitor checks whether the CentralDispatch Agent NT service/Unix daemon is running. This monitorneeds no arguments.

This monitor is preconfigured in the Connection Broker Monitors forSiebel profile to do the following:


¶ When the service/daemon goes down, a Fatal event is sent to theTivoli Enterprise Console and the appropriate indicator icon isupdated. A task is run to restart the Agent service/daemon.

¶ When the Agent service/daemon status changes to up, aHarmless event is sent to the Tivoli Enterprise Console and theindicator icon is updated. This harmless up event will close theopen down event.


GatewayNameServerStatusThis monitor checks whether the Siebel Gateway Name Server NTservice/Unix daemon is running.

This monitor is preconfigured in the Gateway Name Server Monitorsfor Siebel profile to do the following:


¶ When the service/daemon goes down, a Fatal event is sent to theTivoli Enterprise Console and the appropriate indicator icon isupdated. A task is run to restart the Gateway Names Serverservice/daemon.

¶ When the service/daemon status changes to up, a Harmless eventis sent to the Tivoli Enterprise Console and the indicator icon isupdated. This Harmless ″up″ event will close the open ″down″event.


5.R

esou

rceM

on

itorin

g

Enterprise Event Management

With the Tivoli Enterprise Console, the Tivoli Manager for SiebeleBusiness Applications provides a set of filters for identifying eventsand a set of predefined correlation rules to automate the task ofresponding to specific events. An event is any significant change inthe state of system resources or an application. In the case of thismodule, an event is a change in a monitored resource that affectsSiebel or the system on which Siebel is running. Examples of eventsare the starting and stopping of an Application or Gateway NameServer.

Configuration ActivityThe following describes the tasks needed to setup the TivoliEnterprise Console to be used with Tivoli Manager for SiebeleBusiness Applications. This activity takes place on the TivoliEnterprise Console and Siebel Application and Gateway Serverendpoints.

Tivoli Enterprise Console ServerThe Tivoli Enterprise Console server is set up to:

¶ Recognize and accept Siebel events.

¶ Respond to Siebel events according to the predefinedrules.

¶ Create the Siebel event source and the Tivoli Managerfor Siebel eBusiness Applications event group forgrouping events

6


6.E

nterp

riseE

vent

Man

agem

ent

¶ Display received events on the Enterprise Console.

Siebel ServersOn the endpoints where Siebel servers will be running:

¶ The Tivoli logfile adapter is configured to forwardSiebel log messages as alarms to the Tivoli EnterpriseConsole.

Configuring the Tivoli Enterprise ConsoleUse the procedures in this section to set up the Tivoli EnterpriseConsole to receive Siebel events.

To set up the Tivoli Enterprise Console:

1. Select Run job... from the Configure_Event_Server_for_Siebelicon’s pop-up menu. This action displays theConfigure_Event_Server_for_Siebel window.

From the Configure_Event_Server_for_Siebel window, there aretwo options for setting up the Tivoli Enterprise Console: creating anew rule base or adding the Tivoli Manager for Siebel specific rulesto an existing rule base.

Creating a New Rule BaseUse the following steps to set up the Tivoli Enterprise Console bycreating a new rule base:

1. Enter the name of the rule base you want to create in the RuleBase Name field.


2. Enter ″Default″ (or another existing rule base) in the Rule Baseto clone.

3. Enter path name to the directory on the Tivoli Enterprise Consoleserver in which you want to create the new rule base in the Pathto Rule Base.

4. The Name of Event Console to configure field is used todisplay Siebel related events on a particular systemadministrator’s event console. To make this assignment, enter thename that appears under the desired system administrator’s eventconsole icon. If this option is not selected, you will need tomanually assign the Siebel event group to administrator’s eventconsole.

5. Press the Set and Close button when finished.

Adding an Existing Rule BaseUse the following steps to set up the Tivoli Enterprise Console byadding the Tivoli Manager for Siebel specific rules to an existingrule base.

1. Enter the name of the existing rule base in the Rule Base Name.

2. Leave Rule Base to Clone blank.

3. Leave Path to Rule Base blank.

4. The Name of Event Console to configure field is used todisplay Siebel related events on a particular systemadministrator’s event console. To make this assignment, enter thename that appears under the desired system administrator’s eventconsole icon. If this option is not selected, you will need tomanually assign the SiebelPlus event group to administrator’sevent console.

5. Press the Set and Close button when finished.


6.E

nterp

riseE

vent

Man

agem

ent

Configuring the Logfile Adapter for SiebelSetting up the Tivoli Enterprise Console logfile adapter willcustomize the logfile adapter to monitor the Siebel Server log file(<enterprise>.<server>.log) for component Siebel messages andforward them to the Tivoli Enterprise Console Server. Also, if theResonate Central Dispatch Agent is installed for connectionbrokering, the logfile adapter will also be configured to monitor theCentral Dispatch log file (<Resonate directory/log/agent-dir.<nodename>/agent-log). So this task may be run on GatewayNames Servers when Connection Brokering is used to monitor theResonate log.

Note: The appropriate Tivoli Enterprise Console logfile adaptermust be installed and running on the node prior to performingthis customization. See the Tivoli Enterprise Consoledocumentation for detailed installation procedures of the baselogfile adapters.

To set up the Tivoli Enterprise Console logfile adapter for Siebel:

1. Select the Run job... option from theConfigure_Logfile_Adapter_for_Siebel icon’s pop-up menu toconfigure the default targets (Siebel Application ServerSubscribers), or select the Run on selected subscribers option tospecify only certain targets.

Events and RulesThe Tivoli Manager for Siebel eBusiness Applications configures theTivoli Enterprise Console to receive events from Siebel Server logs,Resonate logs and Tivoli Distributed Monitoring. The TivoliEnterprise Console classifies the events and then matches themagainst the rule base to see if the event has a predefined rule(automated response).

Siebel Logfile EventsThe following table contains the Siebel events and rules sent to theTivoli Enterprise Console by the logfile adapter.


Event Description Event Class Event Severity

Siebel Component hasbeen started

Siebel_Component_Started Harmless

Siebel batch modecomponent completed

Siebel_Component_Completed

Harmless

Siebel batch modecomponent exited witherror

Siebel_Component_Exit_with_Error

Warning

Siebel batch modecomponent exitedunexpectedly

Siebel_Component_Exit_Unknown

Warning

Siebel interactive modecomponent exited witherror


Warning

Siebel interactive modecomponent exitedunexpectedly


Warning

Siebel background modecomponent exited witherror


Warning

Siebel background modecomponent exitedunexpectedly


Warning

Resonate (Connection Broker) Logfile EventsAll Resonate log messages are in the format:Time stamp | facility | severity | sub-facility | message

The Tivoli Manager for Siebel will map all Resonate log events tothe Tivoli Enterprise Console Event Class Resonate_Logfile_Event,and will map to slots as follows:

Log Field Event Slot

Time stamp ctime

Facility facility


6.E

nterp

riseE

vent

Man

agem

ent

Log Field Event Slot

Severity severity (0=CRITICAL, 1=MINOR,2=WARNING, 3=HARMLESS)

Sub-facility subfacility

Message msg

Note that all Resonate log messages will be forwarded to the eventserver as events. In order to filter out any severity level(s), add thefollowing line to the adapter configuration file on each node:Filter:Class=Resonate_Logfile_Event;severity=<severitylevel to filter>

Tivoli Distributed Monitoring EventsThe following table describes the events and rules that the TivoliEnterprise Console uses to process events sent from TivoliDistributed Monitoring.

Event Description Event Class Event Severity

Status Change of theSiebel Server NTService/Unix daemon

Siebel_Server_Sentry_Event Up=HARMLESS,Down=CRITICALChanges toDown=Fatal

Status Change of theSiebel Gateway NTService/Unix daemon

Siebel_Gateway_Sentry_Event

Up=HARMLESS,Down=CRITICALChanges toDown=Fatal

Status Change of theResonate NTService/Unix daemon

Siebel_Connection_Broker_Event

Up=HARMLESS,Down=CRITICALChanges toDown=Fatal


Rules for Tivoli Manager for Siebel eBusinessApplications Events

The Tivoli Enterprise Console includes a rules engine that processesevents according to a set of rules that are provided by applications oradded by users. Tivoli Manager for Siebel eBusiness Applicationssupplies a set of rules that provide correlation of related events. Youcan change these rules and also write rules that are tailored for yourinstallation. See the Tivoli Enterprise Console Rule Builders Guidefor more information on how to use the Tivoli Enterprise Consolegraphical rule editor.

The rules and their functions are as follows:

siebel_dup_monitorsThis rule removes duplicate Siebel monitor events. A duplicateevent is defined as an event received at the event server within aday of the previous event that has the same slot values for themonitor, probe_arg, collection, sub_source, hostname, and info.When a duplicate event occurs with the same severity and valuethe new event is dropped and the repeat_count for the originalevent is incremented by one. When a duplicate occurs with thesame severity (but different value), the original event is closedand the newer event is kept.

siebel_dup_logfileThis rule removes duplicate Siebel logfile events. A duplicateevent is defined as an event received at the event server has thesame slot values for the hostname and component. When aduplicate occurs the new event is dropped and the repeat_countfor the original event is incremented by one.

siebel_timeharmlessThis rule sets a timer on each Siebel harmless event to 15minutes. A timer rule closes the event when the timer expires.

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


6.E

nterp

riseE

vent

Man

agem

ent

siebel_close_server_statusThis rule closes events as follows for the Siebel server statusmonitor:

¶ If an event is received indicating that the server is up, thisrule closes out the previous down event for that server.

¶ If an event is received indicating that the server is down, thisrule closes out the previous up event for that server.

siebel_close_broker_statusThis rule closes events as follows for the Component Brokerstatus monitor:



siebel_close_gateway_statusThis rule closes events as follows for the Gateway Name Serverstatus monitor:




Troubleshooting the TivoliManager for Siebel eBusinessApplications

All functions within the Tivoli Manager for Siebel eBusinessApplications are equipped with logging facilities for troubleshootingpurposes. This debugging is activated with the presence of a flag filein that directory.

To enable debugging, run the Start_Logging task.

With debugging enabled, each Tivoli Manager for Siebel script willcreate/replace a log file, in that temporary directory, namedaccording to the task or monitor that was executed.

Knowing file names, their contents, and where to look forinformation, such as task output and log files, can often be the keyto solving a problem.

The Configure_Event_Server_for_Siebel,Configure_Logfile_Adapter_for_Siebel, Configure_Siebel_Servers,and Configure_Siebel_Gateways tasks write output to a log fileregardless of whether debugging has been enabled with theStart_Logging Task. All other tasks and monitors write output to alog file only if the Start_Logging task has been run.

Log files are placed in the following locations:

7


7.Tro

ub

lesho

otin

g

-Tivoli Management RegionThe directory returned by the wtemp command. For example,the installation log is written to Siebel_install.log.

-Tivoli Enterprise Console ServerA directory returned by the wtemp command. For example, theConfigure Event Console task written to SIEBEL_config_tec.log.

-EndpointsFiles are written to the $LCF_DATDIR/Siebel_logs directory.For example, the Configure_Siebel_ Servers task writes toSIEBEL_Configure_Siebel_Servers.log

Installation QuestionsWhat should be verified prior to installation to prepare for theTivoli Manager for Siebel eBusiness Applications?

Test Distributed Monitoring and the Tivoli Enterprise Console eventserver before installing Tivoli Manager for Siebel eBusinessApplications. This is especially important if you are installing TivoliManager for Siebel eBusiness Applications in a new Tivolimanagement region. If these core applications are not working,Tivoli Manager for Siebel eBusiness Applications will not workeither. At a minimum, you should be able to do the following withthese applications:

¶ Start a simple task. If you have the Tivoli Enterprise Consoleinstalled, then start one of the tasks in the T/EC Tasks library.

¶ Deploy some distributed monitoring monitors on Tivoli Managerfor Siebel eBusiness Applications machines. Deploy monitorsthat send a pop-up dialog to the administrator. Also send a TivoliEnterprise Console event to ensure that the monitor is runningand that the event console receives distributed monitoring events.

After your basic Tivoli installation, install the Tivoli Manager forSiebel eBusiness Applications as follows:

¶ Back up your database on each machine where Tivoli Managerfor Siebel eBusiness Applications will be installed.


¶ Install Tivoli Manager for Siebel eBusiness Applications.

¶ Back up your database on each machine on which TivoliManager for Siebel eBusiness Applications was installed.

Note: After the files are loaded onto the system from the installationmedia, an installation program is run to create the TivoliManager for Siebel eBusiness Applications policy region. Theinstallation program creates a Siebel_install.log file in thedirectory returned by the wtemp command.

If the log file does not exist, correct the problem indicated inthe task output and reinstall the product from the installationmedia.

If the log file exists, review the log file to determine thecause of the problem. Then, correct the problem indicated inthe log file and reinstall the product from the installationmedia.

Questions on Running Tasks from the DesktopThe following information might help you solve problemsencountered using tasks from the desktop:

Why does a task fail with the following permissions error:endpoint_name(Endpoint): The task failed to execute.

endpoint_name(Endpoint): Insufficient roles for executing the task onendpoint_name endpoint.

1. Ensure that you assigned the resource roles siebel_senior orsiebel_admin (or both) to the administrator that runs the task.

2. After the resource roles have been assigned, stop and then startthe desktop again, so that the assigned roles will take effect.

Why are files still on the endpoint after running the DeleteEndpoint Dependencies task?

If logging is on when you run this task, the associated log filesremain on the endpoint. To remove the log files, ensure that logging


7.Tro

ub

lesho

otin

g

is off when you run the Remove_Tivoli_Manager_for_Siebel_Filestask. Run this task again to remove the SIEBEL_delete_utils.log.

Why do I get a blank window when I run a job?

Jobs are set up at installation time to create a convenient way toinvoke tasks. Most of the jobs created are set up to run against theSiebel Application Server Subscribers or Siebel Gateway NameServer Subscribers.

When you run a job and get back a totally empty window, the jobwas run against a nonexistent endpoint. The typical cause of thiserror is that a job is run against a profile manager that does not haveany subscribers. Therefore, the job is not run against any node.

What to do:

¶ Siebel servers that are to be managed should be added assubscribers to the appropriate profile manager. The typicalscenario should be to:

v Add the endpoint to the appropriate subscriber list.

v Rerun the job.

¶ Run the job on selected subscribers and specify the appropriateendpoints directly.

Questions on Using MonitorsWhy are my monitors getting a Permission Denied error?

Make sure that you have the latest Distributed Monitoring patchesinstalled. See the Tivoli Manager for Siebel eBusiness ApplicationsRelease Notes for information on patches for Distributed Monitoring.

Why are the monitors returning E.EXEC as a result?

Typically monitors return E.EXEC when the Siebel monitor is runagainst an endpoint where Siebel is not installed or the module hasnot been configured.


Questions on Using the Tivoli Enterprise ConsoleWhy am I not seeing Siebel monitor or adapter events on theTivoli Enterprise Console event console ?

If you do not see either Siebel monitor or adapter events on theevent console, check the following:

¶ Ensure that the event server is operational.

¶ Ensure that Tivoli Manager for Siebel eBusiness Applicationsclasses and rules are installed and configured on the eventserver.

1. Enter the wlscurrb command to display the name of theactive rule base

2. Run the wlsrbclass active_rulebase_name command to listthe defined event classes. Ensure that theSiebel_Monitor_Base and Siebel_Logfile_Base classes aredefined.

3. Run the wlsrbrules active_rulebase_name command to listthe defined rules. Ensure that the Siebel.rls rule base isdefined.

4. If the required Tivoli Manager for Siebel eBusinessApplications classes or rules are not defined, run theConfigure Event Server task to define the classes and therules.

¶ Check to see if the events are being received at the event server.

v Run the wtdumprl command on the event server to displaythe events in the reception log on the event server.

v If the events are not in the list, ensure that the monitors andlogfile adapter have been configured and are running.

¶ The events are being received, but have a parsing_failedmessage.

v The Configure Event Server task has not been run. This taskloads the definitions for the Tivoli Manager for SiebeleBusiness Applications events into the event server.


7.Tro

ub

lesho

otin

g

¶ The events are being received and are processed.

Check the Event Groups that have been assigned to the eventconsole. If the Siebel group is not listed, then the event consolehas not been set up to display the Siebel events. Run theConfigure_Event_Server for Siebel task to assign the eventgroup to the event console. This can also be done manually fromthe event server desktop.


Messages

This appendix contains information about Tivoli Manager for SiebeleBusiness Applications messages.

GMS0001E No Siebel environment file (.siebeltiv.<enterprise>.<server>) was found. If theSiebel application Server is installed on this node run the taskConfigure_Siebel_Servers.

Explanation: Either the Configure_Siebel_Servers task was not run for this node,or there is no Siebel Server on this node.

User Response: If the Siebel application Server is installed on this node, run theConfigure_Siebel_Servers task.

GMS0002I The Siebel Server (Siebel server) is already running.

Explanation: This is an informational message; no action is required.

User Response: None.

GMS0003E Multiple Siebel servers are configured on this node... you must supply theenterprise and server name of the Siebel server you wish to start.

Explanation: The enterprise and server names were not supplied when trying tostart the Siebel Server.

User Response: Rerun the Start_Siebel_Server task, and specify the enterprise andserver names of the server that you wish to start.

A


A.

Messag

es

GMS0004E No Siebel server is configured on this node with Enterprise nameEnterprisename and Server name Servername. Run the task’Display_Siebel_Servers_Configuration’ to see the servers on this node.

Explanation: You are either configuring a Siebel Server that is not running or aconfigured Siebel Server with the specified enterprise and server name does notexist.

User Response: Response: Verify that you specified the correct Enterprise andServer name for the task you are running. If you are configuring a Siebel Server,verify that the Siebel Server you specified is running when you execute the task.

GMS0005I Starting Siebel Server - Enterprise name Enterprisename, Server nameServername.



GMS0006I The Siebel Server has been successfully started.



GMS0007E The Siebel Server could not be started.

Explanation: The attempt to start the Siebel server failed.

User Response: Check the Start Siebel Server log file for the server for reasonswhy the server did not start.

GMS0008E The Siebel Server files (<Siebel Server Path>/bin/start_server) cannot be found.

Explanation: The command used to start the Siebel Server could not be found.

User Response: Ensure the Siebel Server is configured correctly. Make sure thestart_server command is in the bin directory of the Siebel Server installationdirectory.

GMS0009I The Siebel Connection Broker is already running.




GMS0010I The Resonate Central Dispatch Agent has been successfully started.



GMS0011E The Resonate Central Dispatch Agent could not be started.

Explanation: The attempt to start the Resonate Central Dispatch Agent failed.

User Response: Verify that you can start the agent manually. If you can not, checkthe log file for the agent.

GMS0012E The Resonate Central Dispatch Agent control script (script name) cannot befound.

Explanation: The script used to stop and start the Resonate Central DispatchAgent could not be found.

User Response: Make sure the script that is used to start and stop the agent isplaced in the correct directory.

GMS0013I The files were successfully deleted from the managed node.



GMS0014E Siebel application server not configured. Run the task’Configure_Siebel_Servers’ to configure.

Explanation: You attempted to monitor a Siebel application server on a node, butthe application server has not been configured.

User Response: Run the Configure_Siebel_Servers task to configure theapplication server.

GMS0015E Siebel environment file (.siebeltiv.gtwyns) was not found. If the Siebel Gatewayis installed on this node, run theConfigure_Siebel_Gateways task.

Explanation: You attempted to start, stop, or monitor the status of a SiebelGateway, but no configured Siebel Gateway can be found.

User Response: Run the Configure_Siebel_Gateways task to configure the Siebelgateway.


A.

Messag

es

GMS0016I The Siebel Gateway Name Server is already running.



GMS0017I The Siebel Gateway Name Server has been successfully started.



GMS0018E The Siebel Gateway Name Server could not be started.

Explanation: The Siebel Gateway Name Server failed to start.

User Response: Look in the log file for the task and the gateway’s log file for anyinformation on why the gateway’s process failed to start.

GMS0019E The Siebel Gateway files (<Siebel Gateway Directory>/bin/start_ns) cannot befound.

Explanation: The start_ns command is used on UNIX systems by theStart_Siebel_Gateway task to start the Siebel Gateway. The command was not foundin the specified location so the task cannot start the gateway.

User Response: Make sure the specified path to the start_ns command is correct.If it is not correct, your Siebel Gateway is configured incorrectly. If the path iscorrect, the start_ns command is missing from your Siebel Gateway installation.

GMS0020I The Siebel Connection Broker was not running.

Explanation: You attempted to stop the Siebel Connection Broker, but it was notrunning.


GMS0021I The Siebel Resonate Central Dispatch Agent has been successfully stopped.



GMS0022E The Siebel Resonate Central Dispatch Agent could not be stopped. You mayneed to stop any running Siebel Server or Gateway before stopping Resonate.

Explanation: You tried to stop the Siebel Resonate Central Dispatch Agent, but aSiebel Server or Gateway was still running.


User Response: Stop any running Siebel Servers or Gateways, and rerun theStop_Connection_Broker task.

GMS0023I The Siebel Gateway Name Server was not running.

Explanation: You attempted to stop or configure the Siebel Gateway Name Server,but it was not running.

User Response: If you are configuring the Siebel Gateway, start it, then rerun theConfigure_Siebel_Gateways task.

GMS0024I The Siebel Gateway Name Server was successfully stopped.



GMS0025E The Siebel Gateway Name Server could not be stopped.

Explanation: The attempt to stop the Siebel Gateway Name Server failed.

User Response: Check the Stop_Siebel_Gateway task and Siebel Gateway NameServer log files for any information on why the process could not be stopped.

GMS0026E The Siebel Gateway files (Siebel Gateway Installation Directory/bin/stop_ns)cannot be found.

Explanation: The command used to stop the Siebel Gateway could not be found.

User Response: The Siebel Gateway may be configured incorrectly or your SiebelGateway installation is missing this file. Find the stop_ns file and make sure it is inthe correct location.

GMS0027I The Siebel Server Siebel Server was not running.

Explanation: You attempted an operation on a Siebel Server, but it was notrunning.

User Response: Start the Siebel Server, and rerun the operation.

GMS0028I Stopping Siebel Server - Enterprise name EnterpriseName, Server nameServerName.




A.

Messag

es

GMS0029I The Siebel Server was successully stopped.



GMS0030E The Siebel Server could not be stopped.

Explanation: The attempt to stop the Siebel Server failed.

User Response: Check the Stop_Siebel_Server tasks log file and the SiebelServers log file for any information on why the server could not be stopped.

GMS0031E The Siebel Server files (Siebel Server Installation Directory/bin/stop_server)cannot be found.

Explanation: The command used to stop the Siebel Server on UNIX systemscould not be found.

User Response: Make sure the correct path is specified and that the stop_serverfile exists.

GMS0032E Siebel Component Group must be specified.

Explanation: You attempted to enable or disable a Component Group, but did notspecify the Component Group.

User Response: Rerun the task, specifying the Component Group.

GMS0033I Component Group Component Group was successfully taken offline.



GMS0034E Component Group name could not be taken offline.

Explanation: The command to take the component group offline was issued, butthe component group did not go offline. This can happen if the component groupdoes not go offline immediately or if the component group goes into a state otherthan Offline.

User Response: Execute the Run_Srvrmgr_Command task to list the componentgroups and determine what state the component group is currently in.


GMS0035I Component Group Component Group was successfully brought online.



GMS0036E Component Group name could not be brought online.

Explanation: The command was issued to online the component group, but thecomponent group’s state did not change to Online or Running.

User Response: Execute the Run_Srvrmgr_Command task to list the componentgroups and determine what state the component group is currently in.

GMS0037E Valid SIEBEL_ROOT path is required.

Explanation: When running the Configure_Siebel_Gateways task, theSIEBEL_ROOT parameter was not specified.

User Response: Rerun the Configure_Siebel_Gateways task, specifying theSIEBEL_ROOT parameter.

GMS0038E Invalid SIEBEL_ROOT...unable to find Siebel RootDirectory/admin/gtwydefs.dat.

Explanation: You specified an invalid SIEBEL_ROOT parameter whenconfiguring a Siebel Gateway or Siebel Server.

User Response: Rerun the task, specifying a valid SIEBEL_ROOT parameter.

GMS0039E Module supports Windows NT, Solaris and AIX only.

Explanation: You attempted to configure a Siebel Gateway or Siebel Server thatresides on an unsupported platform.

User Response: Configure the Siebel Server or Gateway running on Windows NT,Solaris or AIX. See the Tivoli Manager for Siebel eBusiness Applications ReleaseNotes for supported platforms.

GMS0040I Siebel Gateway Siebel Gateway configured on this node.




A.

Messag

es

GMS041E Valid SIEBEL_ROOT path, Username and password are required.

Explanation: An incorrect SIEBEL_ROOT path, Username or password wasspecified when running the Configure_Siebel_Servers task.

User Response: Rerun the Configure_Siebel_Servers task, specifying validparameters.

GMS0042E Invalid SIEBEL_ROOT...unable to find <Siebel Root Directory>/bin directory.

Explanation: You specified an invalid SIEBEL_ROOT parameter whenconfiguring a Siebel Server.

User Response: Rerun the Configure_Siebel_Servers task, specifying a validSIEBEL_ROOT parameter.

GMS0043E No Siebel servers found running on this node. Environment not configured.

Explanation: You attempted to run the Configure_Siebel_Servers task on a nodethat does not have any Siebel Servers. This message can also occur if there is arunning server, but you specified an invalid server name.

User Response: Rerun the Configure_Siebel_Servers task, specifying a validSiebel Server name that is currently running.

GMS0044E Dataless endpoints are not supported by this version of Tivoli.

Explanation: There are no Tivoli Gateways in your Tivoli Installation. You willneed at least one Tivoli Gateway to manage your Siebel Servers.

User Response: Install a Tivoli Gateway.

GMS0045I Adding TMA support for Siebel Subscription lists .



GMS0054I Starting the Tivoli Enterprise Console Logfile Adapter.



GMS0055E Backing out. Files = <file list>.

Explanation: The Tivoli format file is invalid or the generation of the cds filefailed. The files modified are being restored to their original state.


User Response: Verify that the original format of the Tivoli Enterprise Consoleconfiguration files are valid. Rerun the task.

GMS0056E This node does not have the Tivoli Enterpris Console logfile directory directoryinstalled.

Explanation: The logfile adapter is not installed on the endpoint.

User Response: Install the Tivoli Enterprise Console logfile adapter onto theendpoint.

GMS0057E This node does not have the Tivoli Enterprise Console logfile adapter installed.

Explanation: The Tivoli Enterprise Console logfile adapter is not installed on theendpoint.

User Response: Install the Tivoli Enterprise Console logfile adapter onto theendpoint.

GMS0058E This node does not have the Tivoli Enterprise Console logfile gencds commandinstalled.

Explanation: The gencds command could not be found.

User Response: Install the Tivoli Enterprise Console logfile adapter on theendpoint.

GMS0059E This node does not have a Tivoli Enterprise Console logfile configuration(.conf) file.

Explanation: The gencds command could not be found.

User Response: Install the Tivoli Enterprise Console logfile adapter on theendpoint.

GMS0060I Stopping the Tivoli Enterprise Console Logfile Adapter.



GMS0061E Filename is not a valid format file.

Explanation: The specified file is not valid.

User Response: Make sure the file specified has the correct formatting.


A.

Messag

es

GMS0062I Successfully generated filename file.



GMS0063I Added LogSources LogSources to Logfile configuration.



GMS0064I Poll Interval was already set.



GMS0065I Added PollInterval line to number.



GMS0066I Node configured successfully.



GMS0067E Command exited with a non-zero status [return code].

Explanation: The specified command failed to complete successfully.

User Response: See the log file for error messages indicating why the commandfailed.

GMS0070E Only Endpoints are supported.

Explanation: An operation was executed on a managed node, not an endpoint.Managed nodes are not supported for Siebel nodes.

User Response: Rerun the operation on an endpoint.

GMS0073E The Component Group Component Group does not exist.

Explanation: The Component Group specified in the Offline_Component_Groupor Online_Component_Group doesn’t exist.


User Response: Rerun the task, supplying the name of an existing ComponentGroup

GMS0074I The Component Group Component Group is already online.



GMS0075I The Component Group Component Group is already offline.



GMS0076I Task complete.



GMS0077I Log information is written to: filename.



GMS0078I EventGroupName already assigned to EventConsole.



GMS0079I Assigned EventGroupName to EventConsole.



GMS0080E Failed to assign EventGroupName to EventConsole. Ensure task is run againstthe event server.

Explanation: Task run against managed node that is not the Tivoli Event Consoleserver.

User Response: Run the task against the event server.


A.

Messag

es

GMS0081E Command Failed.

Explanation: General failure.

User Response: Check log for other messages.

GMS0082I The last few lines of the log file FileName are ...



GMS0083I Rulebase rule base already exists, will update it. Clone rule base will beignored.



GMS0084I Clone rule base Rulebase exists.



GMS085I Created Rulebase.



GMS0086I Sentry classes already installed.



GMS0087I Sentry classes have not been installed, adding them.



GMS0088I Rulebase compiles successfully.




GMS0089I Created Rulebase rule base.



GMS0090I Copied CloneRulebase rule base to Rulebase.



GMS0091I Imported ClassFile to Rulebase rule base.



GMS0092I Stopped event server.



GMS0093I Restarted event server.



GMS0094I Configuring event server.



GMS0095I Rulefile is already in (RuleBase) rule base. It will be deleted and importedagain to pick up any new rules.



GMS0097I Created EventSource event source.




A.

Messag

es

GMS0098I EventSource event source already exists.



GMS0099I Removed EventSource.



GMS0100I Loaded Rulebase rule base.



GMS0101I Creating event group.



GMS0102I The Siebel event group was created successfully.



GMS0103I The Siebel event group already exists.



GMS0104E A rule base must be defined.

Explanation: A rule base name was not entered in the Configure Event Serverdialog.

User Response: Run the task again and supply a new or existing rule base name.

GMS0105E Clone rule base must be defined.

Explanation: A new rule base was specified on the Configure Event Server dialogbut no Rule Base to Clone was entered.


User Response: Run the task again and supply an existing rule base to close orspecify an existing rule base.

GMS0106E Clone rule base (Rulebase) must already exist.

Explanation: A new Rule Base was specified, but the Rule Base to Clone doesnot exist.

User Response: Run the task again and supply an existing rule base to clone.

GMS0107E Cannot create new rule base path.

Explanation: Unable to issue mkdir command.

User Response: Check for other diagnostic messages.

GMS0108E Rulebase does not compile.

Explanation: One or more rules in the rule base failed to compile.

User Response: Check the log for the rules that did not compile, correct the rules,and rerun the task.

GMS0109E Failed to create Rulebase rule base.

Explanation: The wcrtrb command encountered a problem.

User Response: Check the log for the error, correct it, and run the task again.

GMS0110E Failed to copy CloneRulebase rule base to Rulebase.

Explanation: The wcprb command encountered a problem.


GMS0111E Failed to import Rulefile to Rulebase rule base.

Explanation: The wimprbclass command encountered a problem.


GMS0112E Failed to create EventSource event source.

Explanation: The wcrtsrc command encountered a problem.



A.

Messag

es

GMS0113E Failed to delete EventSource event source.

Explanation: The wdelsrc command encountered a problem.


GMS0114E Failed to load Rulebase into event server.

Explanation: The wloadrb command encountered a problem.


GMS0115E Failed to create event group.

Explanation: The wcrteg command encountered a problem.


GMS0116E Failed to add a filter to the event group.

Explanation: The waddegflt command encountered a problem.


GMS0117E Failed to stop event server. Event server must be restarted before installation iscomplete.

Explanation: The wstopesvr command encountered a problem.

User Response: Stop (wstopesvr) and start (wstartesvr) the event server from thecommand line.

GMS0118E This host is not an event server.

Explanation: The task was not run against the event server.

User Response: Run the task again against the event server.

GMS0119E Cannot locate baroc file.

Explanation: Cannot find the baroc files. Possible installation error or files mayhave been removed.

User Response: Check the debug log. Check installation log files and restore filesif needed. Run the task again.


GMS0120I Event group Siebel not created; command not available.

Explanation: Tivoli Enterprise Console version 3.7 does not support the wcrtegcommand.

User Response: Create the event group manually from the Tivoli EnterpriseConsole event server desktop.

GMS0121I Event group Siebel not assigned; command not available.

Explanation: Tivoli Enterprise Console version 3.7 does not support the wassignegcommand.

User Response: Assign the event group to the event console manually from theTivoli Enterprise Console event server desktop.

GMS0122W The files were not deleted from the endpoint.

Explanation: Some of the log file could not be deleted.

User Response: Remove the logfiles manually if desired.

GMS0123I The files were successfully deleted from the endpoint.



GMS0124I There were no files to be deleted on the Endpoint, so no files have been deleted.



GMS0125E The task failed.

Explanation: The task did not complete all of its operations successfully.

User Response: See other messages for which operations did not completesuccessfully.

GMS0126I argument position: ’parameter’.




A.

Messag

es

GMS0127I Attaching PreviousDependency to RootDependency.



GMS0129W Could not attach depset dependency to method method (class class does notexist).

Explanation: The specified class does not exist.


GMS0130W Could not delete dependency; still has children children!

Explanation: The dependency set can not be deleted because it has children.


GMS0131E Could not restart oserv using command ...

Explanation: An attempt was made to restart oserv, but it failed.

User Response: Check log files for error messages.

GMS0132I ### Creating dependency on class class, method method ...



GMS133E dbcheck failed for gateway gateway_name, continuing ...

Explanation: The wgateway command failed to successfully complete a dbcheckfor the specified gateway.

User Response: Check the log files for error messages indicating the problem.

GMS0134I ... deleting reference to invalid depset dependency set .



GMS0135I DEPENDENCY SET: name.




GMS0137I DEPSET_OID: oid.



GMS0138I ### ... DONE attaching dependency to dependency!



GMS0139I ### Done setting dependency set on class class, method method.



GMS0140I Executing program .



GMS0141W Exiting program with return code number.

Explanation: The specified command exited with the specified return code.

User Response: Check logs for more information..

GMS0142E Failed to delete and remove dependency from class method!

Explanation: The attempt to remove the dependency failed.

User Response: Check the log files for additional information.

GMS0143W Framework 3.6 is required for TMA configuration.

Explanation: You attempted to install the product on a version of TivoliFramework earlier than 3.6.

User Response: Check the Tivoli Manager for Siebel eBusiness ApplicationsRelease Notes for supported software and platforms.

GMS0147I METHOD: name .




A.

Messag

es

GMS0148E oserv has died, trying to restart ...

Explanation: The oserv process is not running. An attempt is being made torestart it.

User Response: Verify that the oserv process was restarted.

GMS0149I Replacing dependency with dependency on class class, method method ...



GMS0150W Unable to remove dependency, still has children!

Explanation: The specified dependency set has children and cannot be removed.


GMS0151W The files were not deleted from the managed node.

Explanation: One or more log files could not be deleted from the managed node.

User Response: Delete the log files manually if desired.

GMS0152E command: error_message .

Explanation: The command specified was run and it returned the messagespecified.

User Response: Check the error_message and if necessary look for additionalinformation in the log files.

GMS0153I Logging turned on.



GMS0154I Logging turned off.




GMS0155I Logging already turned on.



GMS0156I Logging already turned off.



GMS0157I The Siebel environment is configured as follows:

Explanation:

User Response: This is an informational message; no action is required.


GMS0158W The Resonate Central Dispatch Agent is not installed on this system.

Explanation: You attempted to check the Connection Broker status on a systemthat doesn’t have the Resonate Central Dispatch Agent installed.

User Response: Choose a system that has the Resonate Central Dispatch Agentinstalled.

GMS0159E The Server Configuration task failed. Please see the log file for details of thefailure.

Explanation: Choose a system that has the Resonate Central Dispatch Agentinstalled.

User Response: See the log file for the task.

GMS0160E Siebel command must be specified.

Explanation: A command was not specified.

User Response: Execute the task again and specify the command that you wouldlike to run.


A.

Messag

es

Index

AActiveSiebelTasks monitor 34activity

configuration 37adding an existing rule base 39applications

starting 12applications monitors

using 31authorization

Tivoli management region roles 10

Ccommands

wdelprb 22wlscurrb 49wlsrbclass 49wlsrbrules 49wruntask 22wtdumprl 49wtemp 47

configurationTivoli Enterprise Console Server 37

configuration activity 37Configure_Event_Server task 49Configure_Siebel_Gateways task 18Configure_Siebel_Server task 50Configure_Siebel_Servers task 19configuring

logfile adapter 40configuring Tivoli Enterprise Console 38Connection Broker 41ConnectionBrokerStatus monitor 35creating a rule base 38

DDisplay_Siebel_Servers_Configuration task 20Distributed Monitoring

events 42

Eenterprise event management 37environment variables

notation for ixerror messages 51event management 37events 40

Distributed Monitoring 42Resonate 41siebel logfile 40

GGatewayNameServerStatus monitor 35

Iinformational messages 51installation

hints 46


Ind

ex

Jjobs 27

modifying a single execution of 28modifying all future executions of 27running 27

LList_Components task 20lists

subscription 15logfile adapter

configuring 40

Mmanagement

enterprise event 37messages

error 51informational 51

modifying 27modifying a single execution of a job 28modifying all future executions of a job 27modifying jobs 27monitoring resources 31monitors

ActiveSiebelTasks 34applications 31ConnectionBrokerStatus 35GatewayNameServerStatus 35hints on using 48questions on using 48resource 31, 33SiebelProcesses 34SiebelServerStatus 33viewing status of 33

Nnodes

subscribing 15

OOffline_Component_Group task 20Online_Component_Group task 21

Pprofiles

Siebel Application Server 15

Qquestions

installation 46on using monitors 48Tivoli Enterprise Console, using 49

questions on running tasks 47

RRemove_Tivoli_Manager_for_Siebel_Files

task 21resource monitoring 31resource monitors 33resource roles

siebel_senior 17resources

monitoring of 31Restart_Gateway_Server task 22Restart_Siebel_Server task 23roles

siebe_senior 10siebel_admin 9, 10


roles (continued)siebel_senior 9, 10Tivoli management region roles 10

rule baseadding 39creating a 38

rules 40Distributed Monitoring 42Resonate 41Siebel Logfile 40

Run_Srvrmgr_Command task 23running jobs 27

Ssaving 27saving jobs 27siebel_admin 17siebel_admin role 9, 10Siebel Application Server profile 15Siebel Gateway Name Server 15Siebel Gateway Name Server profile 15Siebel Logfile Events 40siebel_senior role 9, 10Siebel Servers 37SiebelProcesses monitor 34SiebelServerStatus monitor 33Start_Connection_Broker task 24Start_Logging task 24Start_Siebel_Gateway task 25Start_Siebel_Server task 25starting applications 12status of moniors

viewing 33Stop_Connection_Broker task 25Stop_Logging task 26Stop_Siebel_Gateway task 26Stop_Siebel_Server task 26subscribing nodes 15subscribing servers to a profile manager 12subscription lists 15

Ttask authorizations

authorizationstask 17

tasksConfigure_Siebel_Gateways 18Configure Siebel_Servers 19description of 17Display_Siebel_Servers_Configuration 20hints, running from the desktop 47List_Components 20Offline_Component_Group 20Online_Component_Group 21question on 47Remove_Tivoli_Manager_for_Siebel_Files 21Restart_Gateway_Server 22Restart_Resonate_Connection_Broker 23Restart_Siebel_Server 23Run_Srvrmgr_Command 23Siebel event tasks

Configure_Event_Server task 49Configure_Siebel_Server task 50

Start_Connection_Broker 24Start_Logging 24Start_Siebel_Gateway 25Start_Siebel_Server 25Stop_Connection_Broker 25Stop_Logging 26Stop_Siebel_Gateway 26Stop_Siebel_Server 26

Tivoli Enterprise Consoleconfiguring 38hints on using 49questions on using 49

Tivoli management regionroles

assigning 10Tivoli management region roles 10Tivoli Manager for Siebel eBusiness Applications

subscribing 12troubleshooting 45

troubleshooting 45installation 46running tasks and jobs from the desktop 47using monitors 48


Ind

ex

troubleshooting (continued)using the Tivoli Enterprise Console 49

Vvariables

environment variablesnotation for ix

viewing status of monitors 33

Wwdelprb command 22wlscurrb command 49wlsrbclass command 49wlsrbrules command 49wruntask command 22wtdumprl command 49wtemp command 47


Part Number: 5698SBL

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0766-00

(1P)

P/N:

5698

SBL

Tivoli Manager for Siebel eBusiness...

Documents

Transcript of Tivoli Manager for Siebel eBusiness...