ibm tivoli monitoring for web infrastructure: weblogic...

IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server

User’s GuideVersion 5.1.0

GC23-4718-00

��

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

First Edition (November 2002)

This edition applies to the 5.1.0 version of IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2002. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . ixWho should read this guide . . . . . . . . . ixPublications . . . . . . . . . . . . . . ix

IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server library . . . . . . . . . ixPrerequisite publications . . . . . . . . . xAccessing softcopy publications . . . . . . . xTivoli Information Center . . . . . . . . . xOrdering publications . . . . . . . . . . xProviding feedback about publications . . . . xi

Accessibility . . . . . . . . . . . . . . xiContacting Customer Support . . . . . . . . xiConventions used in this book . . . . . . . . xi

Typeface conventions . . . . . . . . . . xi

Chapter 1. Overview of IBM TivoliMonitoring for Web Infrastructure,Version 5.1.0: WebLogic Server . . . . 1Availability management . . . . . . . . . . 1Performance management . . . . . . . . . . 2Operations management . . . . . . . . . . 2Overview of IBM Tivoli Monitoring . . . . . . 2

Understanding IBM Tivoli Monitoring terminology 3Authorization roles . . . . . . . . . . . . 9Managed resources and endpoints . . . . . . . 9User interface options . . . . . . . . . . . 10

Chapter 2. Setting up IBM TivoliMonitoring for Web Infrastructure:WebLogic Server . . . . . . . . . . 11Guidelines for setting up the product . . . . . . 11Setting authorization roles . . . . . . . . . 11Registering IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server resources . . . . 13Link to a JRE for each endpoint . . . . . . . 17Setting up the IBM Tivoli Monitoring environment 1717Distributing profiles . . . . . . . . . . . 18

Distributing profiles from the Tivoli desktop . . 18Distributing profiles using MDist2 . . . . . . 20

Chapter 3. Setting up the TivoliEnterprise Console for eventcorrelation . . . . . . . . . . . . . 23Overview of the Tivoli Enterprise Console . . . . 23Configuring the Tivoli Enterprise Console eventserver . . . . . . . . . . . . . . . . 24

Chapter 4. Integrating with TivoliBusiness Systems Manager . . . . . 29

Understanding Tivoli Business Systems Manager . . 29Prerequisites . . . . . . . . . . . . . . 30Integrating IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server with Tivoli BusinessSystems Manager . . . . . . . . . . . . 30Configuring the Tivoli Enterprise Console eventserver to work with Tivoli Business SystemsManager . . . . . . . . . . . . . . . 31Discovering resources for Tivoli Business SystemsManager . . . . . . . . . . . . . . . 32Working with Tivoli Business Systems Manager . . 33Uninstalling IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server integration fromTivoli Business Systems Manager . . . . . . . 33

Chapter 5. Working with resourcemodels. . . . . . . . . . . . . . . 35Resource model library . . . . . . . . . . 35Modifying indications . . . . . . . . . . . 36Specifying tasks for an indication . . . . . . . 38Sending a notice to administrators when an eventoccurs . . . . . . . . . . . . . . . . 39Creating scheduling rules. . . . . . . . . . 41Modifying data logging settings . . . . . . . 43Managing profiles and resource models at endpoints 45Managing IBM Tivoli Monitoring gateways. . . . 46Determining which resource models are running onendpoints . . . . . . . . . . . . . . . 46Viewing resource model results with the IBM TivoliMonitoring Web Health Console . . . . . . . 47

Understanding resource health . . . . . . . 47Connecting the IBM Tivoli Monitoring WebHealth Console . . . . . . . . . . . . 48

Chapter 6. Working with IBM TivoliMonitoring for Web Infrastructure:WebLogic Server resources. . . . . . 49Register or unregister a WebLogic Domain . . . . 49Configure WebLogic Domains . . . . . . . . 50Register or unregister WebLogic Servers . . . . . 51Configure WebLogic Servers . . . . . . . . . 53Discover the WebLogic Servers within a specificdomain . . . . . . . . . . . . . . . . 56Starting, stopping, or killing a server . . . . . . 58Validate a WebLogic Server . . . . . . . . . 60

Chapter 7. Working with tasks and jobs 63Running a task . . . . . . . . . . . . . 63Customizing a task . . . . . . . . . . . . 66Creating a job . . . . . . . . . . . . . 67Running a job . . . . . . . . . . . . . 69Scheduling a job . . . . . . . . . . . . . 70

iii

Chapter 8. Enabling Tivoli EnterpriseData Warehouse. . . . . . . . . . . 75Overview . . . . . . . . . . . . . . . 75

Control server . . . . . . . . . . . . 75Central data warehouse . . . . . . . . . 76Data marts . . . . . . . . . . . . . 76Report interface . . . . . . . . . . . . 76

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

Creating an IBM Console user . . . . . . . . 78Assigning roles to a user . . . . . . . . . . 78Creating a user group . . . . . . . . . . . 79Assigning users to a user group . . . . . . . 79Assigning user groups to a data mart. . . . . . 80Managing Tivoli Enterprise Data Warehouse reports 80

IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server star schemas, data marts, andreports . . . . . . . . . . . . . . . 81Running reports . . . . . . . . . . . . 83Scheduling reports to run automatically . . . . 84Modifying default settings for reports . . . . 85Creating reports . . . . . . . . . . . . 86

Appendix A. Task and commandauthorization roles quick reference . . 87

Appendix B. Task quick reference . . . 89

Appendix C. Setting up IBM TivoliMonitoring . . . . . . . . . . . . . 91Creating profile managers and profiles . . . . . 92Subscribing resources to profile managers . . . . 93Adding default resource models to profiles . . . . 94

Adding customized resource models to profiles . . 95Rerunning failed profile distributions . . . . . . 96

Appendix D. Creating custom resourcemodels. . . . . . . . . . . . . . . 99Creating custom resource models using the IBMTivoli Monitoring Workbench . . . . . . . . 99

Appendix E. Event classes and rules 103Event classes . . . . . . . . . . . . . 103Rules for resource models and events . . . . . 103

Appendix F. Problem determination 105Possible problems and workarounds . . . . . 105

General problem determination . . . . . . 105Tivoli Enterprise Console problemdetermination . . . . . . . . . . . . 105Tivoli Enterprise Data Warehouse problemdetermination . . . . . . . . . . . . 106Tasks problem determination . . . . . . . 107Resource models problem determination . . . 107

Appendix G. Accessibility . . . . . . 111Using assistive technologies . . . . . . . . 111Magnifying what is displayed on the screen . . . 111Documentation in accessible formats. . . . . . 111Using alternative text . . . . . . . . . . . 111

Appendix H. Notices . . . . . . . . 113Trademarks . . . . . . . . . . . . . . 114

Index . . . . . . . . . . . . . . . 117

iv IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

Figures

1. WebLogic Server resources output . . . . . 162. The WebLogic_Configure_TEC task window 273. The Policy Region: Monitoring for WebLogic

window. . . . . . . . . . . . . . 54

4. The WebLogicDomain window . . . . . . 555. The Discover Servers window . . . . . . 576. Example of a task argument window . . . . 66

v

vi IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

Tables

1. Counting occurrences . . . . . . . . . 52. Guidelines for setting up the product . . . . 113. Integrating with Tivoli Business System

Manager . . . . . . . . . . . . . 294. Working with resource models . . . . . . 355. IBM Tivoli Monitoring for Web Infrastructure:

WebLogic Server resource models . . . . . 356. Health Determination Example . . . . . . 487. Working with tasks and jobs . . . . . . . 638. Guidelines for working with Tivoli Enterprise

Data Warehouse users and user groups . . . 779. Guidelines for working with Tivoli Enterprise

Data Warehouse reports . . . . . . . . 8110. Default time filter names and values . . . . 8511. IBM Tivoli Monitoring for Web Infrastructure:

WebLogic Server task authorization roles. . . 87

12. IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server command authorization roles. 87

13. IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server tasks . . . . . . . . . 89

14. Monitoring resources and applicationsguidelines . . . . . . . . . . . . . 91

15. Guidelines for creating custom resourcemodels . . . . . . . . . . . . . . 99

16. General problems and solutions . . . . . 10517. Tivoli Enterprise Console problems and

solutions . . . . . . . . . . . . . 10518. Tivoli Enterprise Data Warehouse problems

and solutions . . . . . . . . . . . 10619. Task problems and solutions . . . . . . 10720. Resource model problems and solutions 107

vii

viii IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

About this guide

The IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebLogic Server User’sGuide provides information about setting up and using IBM® Tivoli® Monitoringfor Web Infrastructure: WebLogic® Server to manage your WebLogic Serverresources.

Who should read this guideThis guide is for administrators and system programmers who use IBM TivoliMonitoring for Web Infrastructure to manage WebLogic Server resources.

Readers should be familiar with the following:v The operating systems that the Web servers run on, such as UNIX®, Microsoft®

Windows® 2000, Windows NT®, and Linuxv Web server administrationv The Tivoli management environment

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server library and any other related documents. It also describes how toaccess Tivoli publications online, how to order Tivoli publications, and how tosubmit comments on Tivoli publications.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverlibrary

The IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server librarycontains the following publications:v IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide,

GC23-4717Provides information about installing and setting up IBM Tivoli Monitoring forWeb Infrastructure.

v IBM Tivoli Monitoring for Web Infrastructure Release Notes, GI11-0925Provides a product overview, system requirements, and additional installationinformation.

v IBM Tivoli Monitoring for Web Infrastructure Reference Guide, GC23-4720Provides detailed programming information about the IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server resource models, tasks, commands, anderror messages.

v IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server Warehouse EnablementPack Implementation Guide, SC09-7792Provides information about installing and using the IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server Warehouse Enablement Pack.This document is located on the IBM Tivoli Monitoring for Web Infrastructure,Version 5.1.0: Component Software CD in the tedw_apps_etl\gwl\pkg\v110\docdirectory.

v IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server Limitations andWorkarounds Supplement, SC09-7773

ix

Provides information about problems that might occur, as well as customerissues that have been resolved.

Prerequisite publicationsTo use the information in this book effectively, you must have some prerequisiteknowledge of IBM Tivoli Monitoring, which you can get from the following books:v IBM Tivoli Monitoring User’s Guide, SC23-4567

Provides an overview of IBM Tivoli Monitoring, especially of resource models. Italso describes how to use the user interface.

v IBM Tivoli Monitoring Workbench User’s Guide, SC23-5678Describes using the IBM Tivoli Monitoring Workbench to create and customizeresource models.

Accessing softcopy publicationsThe publications for this product are available in PDF and HTML formats throughthe following media:

IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: Documentation CD,LK3T-8515–00

The Documentation CD contains all of the English language publications for thisproduct, except for the Web-only Limitations and Workarounds supplements. Toaccess the publications, use a Web browser to open the start.html file, which islocated in the root directory of the CD.

Note: The IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server WarehouseEnablement Pack Implementation Guide is located on the product CD, not thedocumentation CD.

The NLS (national language support) Documentation CD contains both Englishand non-English language publications for this product, except for the Web-onlyLimitations and Workarounds Supplements. To access the publications, use a Webbrowser to open the start.html file, which is located in the root directory of the CD.

Tivoli Information CenterIBM posts all publications for this product, as they become available and wheneverthey are updated, to the Tivoli Information Center Web site. The Tivoli InformationCenter is located at the following Web address:

Click the IBM Tivoli Monitoring for Web Infrastructure link to access the productlibrary.

Ordering publicationsYou can order hardcopy publications online from the IBM Publications Center Website:

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

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

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

x IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

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

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

In other countries, see the following Web site for a list of telephone numbers:

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

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,complete the customer feedback survey at the following Web site:

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

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface. For more information about the accessibility features of this product, seeAppendix G, “Accessibility” on page 111.

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

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

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

you are locatedv What information you should gather before contacting support

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

Typeface conventionsThe following typeface conventions are used in this book:

Bold Lowercase and mixed-case commands, command options, andflags that appear within text appear like this, in bold type.

Graphical user interface elements and names of keys also appearlike this, in bold type.

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

Monospace Commands, command options, and flags that appear on a separateline, code examples, output, and message text appear like this, inmonospace type.

About this guide xi

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

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

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

Text strings you must type, when they appear within text, namesof Java™ methods and classes, and HTML and XML tags alsoappear like this, in monospace type.

xii IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

Chapter 1. Overview of IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebLogic Server

IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebLogic Serverprovides a centralized system management tool for WebLogic Server. The IBMTivoli Monitoring for Web Infrastructure: WebLogic Server enables you to manageWebLogic Servers.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides the abilityto manage and monitor WebLogic Server resources by providing extensions toTivoli Management Framework, IBM Tivoli Monitoring, Tivoli Enterprise Console,Tivoli Business Systems Manager, and Tivoli Enterprise Data Warehouse.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server uses IBM TivoliMonitoring resource models to manage distributed WebLogic Server resourceseffectively.

Use IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server to perform thefollowing tasks:v Monitor and interpret performance and availability data for WebLogic Server

resources across distributed environmentsv Manage performance and availability of WebLogic Server resourcesv Capture and manage historical data that is stored in a central data warehousev Forward WebLogic Server events to the Tivoli Enterprise Consolev Manage event correlation and automation using the Tivoli Business Systems

Manager

Note: Tivoli Enterprise Console and Tivoli Business Systems Manager must beinstalled for you to take advantage of event management functions. Thisguide addresses event management topics with the assumption that TivoliEnterprise Console and Tivoli Business Systems Manager are installed whererequired.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides thefollowing features:v Availability managementv Performance managementv Operations management

Availability managementIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides resourcemodels that periodically check the status of your WebLogic Server components. Forexample, the resource models monitor the servers for the following states:v Runningv Shutdown in processv Suspendedv Standbyv Unknown

1

v Down

You can configure the resource models to customize the monitoring cycle and tochange the triggering thresholds.

To ensure that you are managing all available resources, IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server provides the discover_weblogic_server taskthat finds WebLogic Servers. When the discover_weblogic_servers task locates newWebLogic Server resources, it adds them to your Tivoli configuration.

Performance managementThe IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server resourcemodels enable you to measure and report the performance of various componentsrunning on your WebLogic Server resources, such as Enterprise JavaBean (EJB)performance or database connection pool performance, both of which affect theperformance of Web applications running on your servers.

Operations managementIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server tasks enable you tomanage your WebLogic Server resources on a daily basis. You can use these tasksto do the following:v Start and stop your WebLogic Serversv Check the status and retrieve information about your WebLogic Server resources

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server event rules managethe information presented on your event console. These rules correlate and closeevents as well as remove duplicate and harmless events that are no longerrelevant. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server eventreporting functions support standard Tivoli event filtering, which you can use toreduce the number of events sent to your events server. In addition to forwardingevents to Tivoli Enterprise Console, IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server can also forward events to Tivoli Business Systems Manager.

Overview of IBM Tivoli MonitoringIBM Tivoli Monitoring 5.1.1 enables you to deploy preconfigured best practicesresource models as well as standard and customized resource models to automatethe monitoring of essential resources. In this context, a resource is anything thataffects the operation of a computer system and includes physical and logical disks,CPUs, memory, printers, the processes running, and the services, such as LanMan,Windows event log, UNIX syslogd (logging system daemon) and TCP/IP. Thisenables you to detect bottlenecks and other potential problems and defineautomatic recovery from critical situations. This ability frees system administratorsfrom manually scanning extensive performance data. The monitoring softwareintegrates with other Tivoli Availability solutions, including Tivoli Business SystemManager and Tivoli Enterprise Console.

A resource model captures and returns information, such as database status or serveravailability, about a resource or software application in the Tivoli managementenvironment. To use a resource model, you must define and distribute it to anendpoint.

Tivoli provides tools for organizing system resources on the Tivoli desktop. Serversare subscribed to profile managers. These subscriptions provide the channel through

2 IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server: User’s Guide

which resource models are distributed to servers. A profile manager also containsprofiles, which are containers for application-specific information about a particulartype of resource. Each profile contains one or more resource models. You cansubscribe resources to a profile manager. You can distribute individual profileswithin the profile manager to subscribers of the profile manager. You can groupprofile managers in a way that meets your needs. Profile managers can reflectfunctional grouping of resources, functional grouping of resource models, or anygrouping at all. Likewise, a profile can contain any combination of resourcemodels. However, you must segregate profiles according to resources: Web serversneed Web server resource models, and database servers need database serverresource models.

You can define each resource model to include information such as how often tocheck resource status and what to do when certain conditions are met. Someresource models provide predefined settings and response actions, which you canadjust. Other resource models require you to define all the settings. See the IBMTivoli Monitoring for Web Infrastructure Reference Guide for a description ofindividual settings.

Before running a resource model, you must subscribe the server resource to theprofile manager that contains the profile in which the resource model is stored.You can then distribute the profile to the resource. By default, resource models areset up to become active when you distribute them to subscribers. You can activateand deactivate resource models after they are distributed.

Understanding IBM Tivoli Monitoring terminologyThis section describes the main concepts required for understanding how to usethe IBM Tivoli Monitoring product.

Note: The definitions below apply to resource models in general. They are notspecific to the resource models provided by IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server. For information about the configuration ofthe IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server resourcemodels, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide.

ActionsYou can associate one or more recovery actions with a specific event. Theseactions are automatically triggered when the event occurs and, typically,are used for restoring satisfactory system service level. Each time an eventoccurs, the system provides a notification of the event, triggers a recoveryaction to restore satisfactory conditions and, if the action is successful,provides a notification that the action was performed. Actions areassociated with the execution of a CIM method or the execution of aprogram. Associate actions with indications when modifying an existingresource model using this software, or when creating a new resourcemodel with the IBM Tivoli Monitoring Workbench.

AttributesAttributes can be string or numeric values. When creating a new resourcemodel with the IBM Tivoli Monitoring Workbench, you can qualify anevent by specifying relevant attributes according to the information youwant the resource model to monitor. For example, an event might indicateinsufficient disk space. When you specify attributes, such as disk name, oravailable disk space, the resource model can generate a more preciseindication of the problem. For each resource model, some of the attributesare designated as keys.

Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebLogic Server 3

Cycles When a resource model is run at an endpoint, it gathers data at regularintervals, called cycles; the duration of a cycle is the cycle time, which isexpressed in seconds. A resource model with a cycle time of 60 secondsgathers data every 60 seconds. Each of the supplied resource models has adefault cycle time, which you can modify when you define the resourcemodel. At each cycle, the resource model collects data, analyzes it,generates the events and triggers specified actions. The data collected are asnapshot of the status of the resources specified in the resource model.

Gathering Historical Data componentThe Gathering Historical Data component enables IBM Tivoli Monitoringto use Tivoli Decision Support for Server Performance Prediction andTivoli Enterprise Data Warehouse.

The Gathering Historical Data component uses data collected by specificIBM Tivoli Monitoring resource models to populate a database on theTivoli server where the Gathering Historical Data component is installed.The collected data is aggregated every 24 hours and added to the IBMTivoli Monitoring database, from where it can be used in analyses thathelp plan network growth using key system metrics.

For more information about Tivoli Enterprise Data Warehouse, see thefollowing publications:v Tivoli Distributed Monitoring Warehouse Enablement Pack: Implementation

Guide

v Enabling an Application for Tivoli Enterprise Data Warehouse

Heartbeat functionIBM Tivoli Monitoring operates a heartbeat function, which monitors thebasic system status at endpoints attached to the gateway at which it isenabled. Events can be sent to the Tivoli Business Systems Manager(provided that the Tivoli Business Systems Manager Adapter component isinstalled at the gateway), the Tivoli Enterprise Console®, and the IBM TivoliMonitoring Notice Group.

Indications and EventsAn indication is generated when the state of a given resource meetsdefined criteria. By itself, an indication does not trigger any specific action.When indications are aggregated, the resource model generates an event.When you define an event, you must specify under what conditions acertain number of indications are aggregated into an event. You alsospecify whether these indications must be consecutive, or whether thesequence may be interrupted by one or more monitoring cycles that do notregister any indication. The cycles during which no indication is generatedare called holes. An event can notify that there is a problem in the resourcestate, trigger an action and, if enabled, send a notification to the TivoliEnterprise Console server or to Tivoli Business Systems Manager.

IndicationsEach resource model generates an indication when thresholds youdefine are exceeded in a given cycle. A single occurrence of anindication does not always represent a problem, however thepersistence of indications might. The resource model measures thepersistence of the indications and aggregates them according toyour specifications, or how you define settings for occurrences andholes. If the persistence of an indication meets the specified


number of occurrences, the resource model generates an event.Indications can be generated in any one of the followingcircumstances:v When a single threshold is exceededv When a combination of two or more thresholds are exceededv When a combination of other factors change

Occurrences and holesOccurrences and holes record whether or not an indication occursduring a cycle for a specific resource model. An occurrence is acycle during which at least one threshold is exceeded and anindication occurs for a given resource model. A hole is a cycleduring which an indication does not occur for a given resourcemodel. A hole means none of the conditions that generate anindication were met.

EventsAn event is an aggregation of a defined number of consecutiveoccurrences during which there can be a defined number ofconsecutive holes. An event is generated only when theaggregation algorithm detects the number of consecutiveoccurrences defined in the indication with which the event isassociated. An event verifies the persistence of an indication byeliminating unrepresentative peaks and troughs over a period ofcycles. An indication that persists over several cycles is more likelyto be a problem. Thus, an event defines that a number ofoccurrences over a period of cycles has occurred.

When you define an event, you can specify how many consecutiveholes in the sequence of consecutive occurrences are permitted.Specifying how many consecutive holes are permitted during theaccumulation of the consecutive occurrences enables you tocontinue the counting of consecutive occurrences if one or twocycles fall below the threshold.

The following examples illustrate what happens if you define anevent as three occurrences and two holes. 1 represents anoccurrence and 0 represents a hole.v 0 1 0 1 0 0 1

Because fewer than three holes exist between each of the threeoccurrences, the three occurrences are consecutive. Therefore, thesequence represents an event.

v 1 0 0 1 0 0 1If each occurrence is followed by the maximum specified holeswithin seven cycles, an event is triggered.

v 1 0 0 1 0 0 0If the algorithm counts two consecutive occurrences and thenobserves three consecutive holes (more holes than that allowedin the definition of an event for this example) it sets the count ofoccurrences to zero. See Table 1.

Table 1. Counting occurrences

Sequence Count of occurrences

1 0 0 1

1 0 0 1 2


Table 1. Counting occurrences (continued)

Sequence Count of occurrences

1 0 0 1 0 2

1 0 0 1 0 0 2

1 0 0 1 0 0 0 0

While defining an event, you can also indicate if you want thesystem to notify the Tivoli Enterprise Console server, or the TivoliBusiness Systems Manager, that an event was generated. The TivoliMonitoring operator can change these selections later, when theresource model is included in a Tivoli Monitoring profile. You canalso define the degree of severity and the message that will specifythe notification of the event.

Clearing EventsA clearing event is a resource model function that, ifenabled, allows IBM Tivoli Monitoring to close an eventwhen the circumstances that caused the event are nolonger present. Clearing events can be processed by theTivoli Enterprise Console server and by Tivoli BusinessSystems Manager. Clearing events have a severity ofharmless, regardless of the severity of the original event, buthave the same event ID as the original event.

For example, a service stops and the Tivoli EnterpriseConsole server receives an event notifying it of thisproblem. Until the service restarts, the problem is stillpresent on the endpoint, but IBM Tivoli Monitoring doesnot send any further event notifications to the TivoliEnterprise Console server. If the Clearing Event function isenabled, as soon as the service restarts, a clearing event issent to the Tivoli Enterprise Console server, thereby closingthe original event. The Clearing Event itself does notnormally appear on the server, because its only function isto clear the original error event.

Note: Correlated events cannot be cleared.

Monitoring of events and indicationsEvents can be sent to the Tivoli Enterprise Console server, the WebHealth Console, and Tivoli Business Systems Manager.

Tivoli Enterprise Console serverEvents can be viewed by a Tivoli Enterprise Console serverand contain a set of properties that can help to identifyproblems.

Clearing events can also be processed by the TivoliEnterprise Console server. If the default procedure is usedto enable the monitoring of events, the Tivoli EnterpriseConsole server uses the clearing event to close theassociated error event. However, if you choose not toinstall the clearing events rule incorporated in theabove-mentioned default procedure, the clearing event isdisplayed as a separate entity with the same ID as theoriginal error event.


Web Health ConsoleThe Web Health Console, an optional part of IBM TivoliMonitoring, displays the health of each resource model fora selected endpoint as a numeric value between 100(perfect health) and zero (with zero meaning that an eventhas been triggered). Intermediate values show thepercentage of occurrences currently registered with respectto the total number of occurrences needed to trigger anevent.

Tivoli Business Systems ManagerEvents and clearing events can also be sent to the TivoliBusiness Systems Manager, provided that the TivoliBusiness Systems Manager Adapter component has beeninstalled on the gateways of the endpoints that are to bemonitored. A full description of Tivoli Business SystemsManager can be found in the Tivoli Business SystemsManager documentation.

Clearing events can also be processed by the TivoliBusiness Systems Manager, which uses the clearing eventto close the associated error event.

LoggingFor any endpoint, you can log the data collected by a resource model in alocal database. Then you can view it through the History View of the WebHealth Console. You can choose to store raw or aggregated data. You canalso log data to the Tivoli Enterprise Data Warehouse.

ParametersWhile thresholds can be only numeric values, parameters can be lists ofnumbers or strings. Using parameters enables you to customize yourresource model. You can define different parameters, as required. For eachparameter you can specify a value, which can, for example, represent theinstances you want to monitor, or a limit you do not want your resource toexceed, depending on how you use this setting in your script. The lists willthen be displayed in the IBM Tivoli Monitoring dialogs, and depending onthe type of list you select in the IBM Tivoli Monitoring Workbench, thelists will appear in different forms on IBM Tivoli Monitoring. Within theIBM Tivoli Monitoring Workbench, you can define default values and thenlet the operator customize the settings in IBM Tivoli Monitoring. You canchoose one among the following kinds of lists when you specify theparameters:v Boolean Listv Choice Listv String Listv Numeric List

Some resource models have one or more parameters.

ProfilesIBM Tivoli Monitoring is a profile-based application that runs in a Tivolienvironment. Different profiles can be defined containing differentselections of resource models. All aspects of existing profiles can bemodified, including the addition, deletion and customization of resourcemodels. You can distribute multiple profiles to each endpoint.


Recovery ActionsFor any event, recovery actions can be run automatically, such as built-inactions (for Windows) or Tivoli Framework tasks. The actions can takepositive steps to remedy the situation, or can ensure that information aboutthe event is distributed to the appropriate authorities or entities.

Built-In ActionsCertain events can have one or more built-in actions predefined forthem. An action can be either the execution of a common informationmodel (CIM) class method or the execution of a program. Both typeof actions can be implemented only through the Workbench. Forexample, an event that detects the failure of a service could havethe restart of that service as its built-in action. Thus, without anyhuman intervention, IBM Tivoli Monitoring detects the failure of aservice and automatically restarts it. Built-in actions are defined bydefault as part of an event, but can be removed. They have thesame event ID as the event that they are designed to correct.

Note: The events for the IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebLogic Server resourcemodels do not have built-in actions. You can add built-inactions to a custom resource model.

Tivoli Framework tasksFor each event you can select one or more Tivoli Framework tasksto be performed when the event is triggered. The tasks that aretriggered by a IBM Tivoli Monitoring event can access the eventname and event thresholds by accessing the environment variables.

Resource modelsIBM Tivoli Monitoring products provide predefined resource models thataccess specific performance data from the system at runtime. The resourcemodels process the data they collect using an algorithm that determineswhether or not the system is performing to expectations. You can eitheruse a resource model’s default values to collect performance data orcustomize the resource models to match specific requirements in yourenvironment. Distributing resource models using default values enablesyou to begin monitoring immediately to obtain useful data concerningyour enterprise. When you become more familiar with the monitoringprocess and feedback, you may choose to customize the resource modelinformation.

SchedulingIBM Tivoli Monitoring contains a scheduling feature that enables you todetermine a period within which monitoring takes place and specificscheduling rules.

The monitoring period is determined by defining a from and a to date.

The scheduling rules enable you to define time periods on specific daysduring which monitoring takes place. Any number of rules can be defined,allowing you to set up a complex pattern of resource monitoring for aprofile, covering the time periods important to you.

The scheduled times are always interpreted as local times, enabling you toset up a single rule that monitors the same local time period in differenttime zones. For example, if your region covers several time zones, but youwant to monitor morning activities in each time zone, a single rule


defining the monitoring period of between 08:00 and 13:00 is interpretedlocally in each of the time zones, so that you monitor the same relativeperiod.

You should note also that all times of events or activities reported fromendpoints or gateways are logged in the local time of the system fromwhere they originated.

ThresholdsEach resource model defines one or more thresholds. Each threshold has adefault numeric value that you can change when you define the resourcemodel or edit it. The following are examples of how a resource model canuse thresholds:v A threshold value might represent a limit that, if not met, indicates an

unsatisfactory resource state. For example, if you want the system tonotify you when disk space drops under 70%, set the threshold value to70 to generate an indication each time your disk space is less than 70%.

v Some threshold values control the scope of what the resource modelmonitors.

You can add a description in the IBM Tivoli Workbench for each thresholdin the Threshold dialog explaining what each value measures and how itis used within the monitoring algorithm.

Authorization rolesWebLogic Server administrators are known in the Tivoli environment as Tivoliadministrators. Administrators are system or Tivoli administrators who have theauthorization to manage WebLogic Server objects. After the product is installed,you can assign authorization roles to administrators that define the operations theycan perform. Each administrator or group of administrators is represented by anicon on the Tivoli desktop.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server fully integratesinto Tivoli security. To perform administration functions, administrators must haveauthorization roles for both IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server and the Tivoli management environment.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server uses the followingauthorization roles:v weblogic_super

v weblogic_admin

v weblogic_user

Managed resources and endpointsA managed resource is a system or network resource that you manage with TivoliManagement Framework. A managed resource is a specific resource that has adefault policy defined in a policy region. An endpoint is a managed resource thatis the target for distribution of a profile or the resource on which a task or job is tobe run. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server usesendpoint objects to represent WebLogic Servers. To manage WebLogic Serverresources, the Tivoli endpoint must be installed on each node represented by aWebLogic Server object.


Note: In the Tivoli environment, the term node is used to refer to any managedresource with Tivoli Management Framework installed. In the WebLogicenvironment, the term node is used to refer to the WebLogic Server. In thisdocument, unless specifically indicated, the Tivoli environment definition ofnode is used.

User interface optionsYou can use the following user interfaces when working with IBM TivoliMonitoring for Web Infrastructure: WebLogic Server:v The Tivoli desktop, which is the traditional Tivoli graphical user interface (GUI)v The command line interface (CLI) for viewing and operational management of

resourcesv IBM Tivoli Monitoring Web Health Console to work with resource modelsv Tivoli Enterprise Console to work with event managementv Tivoli Business Systems Manager to work with event management and to run

some tasksv Tivoli Enterprise Data Warehouse to gather data about your resources


Chapter 2. Setting up IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server

This chapter describes how to configure IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server.

Guidelines for setting up the productThe following table describes the steps required to set up IBM Tivoli Monitoringfor Web Infrastructure: WebLogic Server, as well as links to where to find moreinformation.

Table 2. Guidelines for setting up the product

Goal Where to find information

Assign the IBM Tivoli Monitoring for WebInfrastructure: WebLogic Serverauthorization to one or more Tivoliadministrators

“Setting authorization roles”

Register IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server resources.

“Registering IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server resources”on page 13

Link to a JRE for each endpoint. “Link to a JRE for each endpoint” onpage 17

Set up the IBM Tivoli Monitoringenvironment so that you can run commands.

“Setting up the IBM Tivoli Monitoringenvironment” on page 17

Distribute profiles either from the Tivolidesktop or using MDist2.

“Distributing profiles” on page 18

Set up Tivoli Enterprise Console for eventcorrelation (optional).

“Configuring the Tivoli Enterprise Consoleevent server” on page 24

Set up Tivoli Business Systems Manager(optional).

“Integrating IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server with TivoliBusiness Systems Manager” on page 30

During installation, IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverperforms several tasks that help to set up your IBM Tivoli Monitoringenvironment, including creating the WebLogic Monitoring profile manager, addingresources to the profiles, and adding resource models to profiles.

If you want to create additional profile managers or customize the subscribers orresource models assigned to your profile manager, the procedures are documentedin Appendix C, “Setting up IBM Tivoli Monitoring” on page 91.

Setting authorization roles

ObjectiveTo assign the IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverauthorization roles for managing resources to administrators and users.

11

Background informationWhen you install IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server,the following three roles are created:v weblogic_super

v weblogic_admin

v weblogic_user

All tasks require that you assign at least one of these roles to the Tivoliadministrator who is running the task. In addition, some tasks require Tivoliauthorities as defined by Tivoli management region roles. To run tasks andprocesses, the Tivoli administrator must have the required Tivoli authority andmust be assigned one of the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server authorization roles. You can assign IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server authorization as Tivoli management regionroles or as resource roles, depending on local authorization requirements.

Required authorization rolesenior

Before you beginBefore setting authorization roles, you must have installed IBM Tivoli Monitoringfor Web Infrastructure: WebLogic Server. See the IBM Tivoli Monitoring for WebInfrastructure Installation and Setup Guide for information on installation.

When you finishAdd managed resources to a policy region.

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

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

Tivoli desktop: Follow these steps to perform this procedure from the Tivolidesktop:1. Open the Administrators collection to see the icons representing the defined

Tivoli administrators.2. Right-click the existing administrator whose role you want to modify to access

the pop-up menu.3. Select Edit Resource Roles to access the Set Resource Roles window.4. Select a resource for which you want to set the administrator’s role from the

Resources scrolling list.5. Add or remove roles for the selected resources as follows:

v To add roles for the selected resources, select one or more roles from thoseshown in the Available Roles scrolling list and click the left-arrow button.The selected roles are moved from the Available Roles scrolling list to theCurrent Roles scrolling list. You can also double-click an entry in theAvailable Roles scrolling list to move it automatically to the Current Rolesscrolling list.

v To remove roles for the selected resources, select one or more roles fromthose shown in the Current Roles scrolling list and click the right-arrowbutton. The selected roles are moved from the Current Roles scrolling list to


the Available Roles scrolling list. You can also double-click an entry in theCurrent Roles scrolling list to move it automatically to the Available Rolesscrolling list.

6. You must click Change & Close or Change to add and remove the selectedroles and save your changes.

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

assign roles.8. Click Change & Close to return to the Administrators window.

The administrator must restart the Tivoli desktop before this change takes effect.

Registering IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer resources

ObjectiveTo register IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server objectsthat represent your WebLogic Server components.

Background informationThe first step in managing WebLogic Server components is to create IBM TivoliMonitoring for Web Infrastructure: WebLogic Server objects to represent thecomponents that you want to manage.

You can register these objects in one of three ways:v Using the Tivoli desktopv Using the command linev Using the weblogic_server_discover task

When registering a WebLogic Server, the server is validated using the STRONGvalue.

Required authorization roleweblogic_admin or weblogic_super for the Tivoli desktop

weblogic_super for the weblogic_server_discover task

Before you beginAny systems that you want to manage with IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server must have a supported version of WebLogic Serveror higher installed and must be configured as Tivoli endpoints. See the TivoliManagement Framework Reference Manual for information about configuring Tivoliendpoints.

Note: All of the WebLogic Servers in any specific WebLogic Domain should be thesame version of BEA WebLogic Server. This is a general expectation of theBEA WebLogic Server product.

Ensure that the WebLogic Server is running.

Once you have registered a WebLogic Domain, it is recommended that the firstserver you register be the WebLogic Administration Server. The domain wideconfig.xml file resides on this server.

Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server 13

When you finishSubscribe servers to profile managers, if needed. Distribute resource models to thenew IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server objects so thatyou can monitor their status and performance.

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

Note: If you experience problems performing this procedure, see Appendix F,“Problem determination” on page 105 for information about log files andcommon problems that might occur. You can also see the IBM TivoliMonitoring for Web Infrastructure Reference Guide for information aboutmessages.

Command line: Use the wweblogic -RegisterDomain command to register aWebLogic Domain. Use the wweblogic -RegisterServer command to register aWebLogic Server. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Tivoli desktop: Follow these steps to register objects from the Tivoli desktop:1. To register a WebLogic Domain, from the Create menu inside the Monitoring

for WebLogic policy region or a sub-region, select WebLogicDomain.2. Complete the following fields on the Register Domain window:

Label Unique identifier for the WebLogic Domain.

Domain NameName of the WebLogic Domain as specified in the configuration file onthe WebLogic Administration Server.

Maximum Days UnvalidatedMaximum number of days to allow the WebLogic Domain to beunvalidated. If a WebLogicServer remains unvalidated for more daysthan this setting, it will be removed the next time a DiscoverServersmethod is run against this WebLogicDomain.

System UserLogin ID of the administrator of the WebLogicDomain. This ID is usedto connect to the underlying WebLogic Domain.

System PasswordSystem password to use for domain operations.

Confirm System PasswordConfirmed system password to use for domain operations.

TEC ServerUnique identifier for the Tivoli Event Console server. To determine thevalue for the TEC Server option, perform the wlookup -ar EventServercommand and use the resulting value. This value is optional.

3. Click Execute & Close.4. To register a WebLogic Server, from the WebLogic Domain in which you want

to register the server, click theWebLogicDomain menu and then select RegisterServer.

5. Complete the following fields on the Register Server window:

Endpoint LabelName or IP address of the machine where the WebLogic Server runs.


This name should not be confused with the label of the endpoint objectthat points to that machine. A valid IP address contains less than fouroctets, assuming subnet masks are set up correctly. For example, 255,255.255, 255.255.255, and 255.255.255.255 are all valid IP addresses.

Label Label you want to use for the Tivoli object. Must be unique within theTivoli management region. If left blank, this label will default to a closematch of the server name.

Server NameName of the WebLogic Server, according to the WebLogic configurationfile, config.xml.

Version6.1 or 7.0.

Listen AddressIP address on which the WebLogic Server listens to requests, accordingto the WebLogic configuration file, config.xml. A valid IP addresscontains less than four octets, assuming subnet masks are set upcorrectly. For example, 255, 255.255, 255.255.255, and 255.255.255.255 areall valid IP addresses. If left blank, this attribute defaults to 127.0.0.1.

Listen PortPort on which the WebLogic Server listens to requests, according to theWebLogic configuration file, config.xml. If left blank, this attributedefaults to 7001.

JRE DirectoryThe full path to the directory of the Java Runtime Environment (JRE). Avalid java executable should exist under JRE directory/bin.

Root DirectoryThe full path to the top level directory of the WebLogic installation towhich the WebLogic Server belongs.

Class PathJava class path used by the WebLogic Server. weblogic.jar should beincluded in this ClassPath.

Log FileThe full path to the logfile for this Server. You may leave blank if theversion of the server is less than 7.0.

Start CommandThe command to use to start the WebLogic Server when it is operatingas a managed server (not operating as an administration server).Include the full path to the command plus any flags the commandmight require. For more information, see “Starting, stopping, or killinga server” on page 58.

Start Command AdminThe command to use to start the WebLogic Server when it is operatingas the administration server. Include the full path to the command plusany flags the command might require.

Administration ServerTRUE or FALSE. If TRUE is selected, this WebLogic Server is theAdministration Server for the domain in which it resides. Only onesingle server acts in this capacity. In the event that you register a serveras the Administration Server and then register a second server in thesame domain as the Administration Server, the original Administration


Server will no longer be the Administration Server for that domain.Only the last WebLogic Server that is configured or registered as anAdministration Server will have that status for a domain.

Validation LevelSets the level of validation for the configuration of the WebLogicServer.WEAK validation verifies directories and paths specified in attributesexisting on the endpoint. STRONG validation attempts to connect tothe underlying WebLogic Server after configuration. The default valueis STRONG.

6. Click Set & Execute.

Task: Follow these steps to perform this procedure using a task:1. From the Tivoli desktop, double-click the Monitoring for WebLogic policy

region.2. Double-click the WebLogic Control Tasks icon.3. Double-click the discover_weblogic_servers task icon and complete the Execute

Task window. Select the WebLogic Domain object on which you want to runthe weblogic_server_discover task.

4. Select Display on Desktop to display the output of the task on the desktop.

Figure 1. WebLogic Server resources output


5. Increase the timeout value because the weblogic_server_discover task takes aconsiderable amount of time to finish.

6. Click Execute or Execute and Dismiss.

For more information on the weblogic_server_discover task, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Link to a JRE for each endpointBefore you can monitor your resources, you must link to a JRE for each endpoint.For more information on this subject, see the IBM Tivoli Monitoring for WebInfrastructure Installation and Setup Guide.

Setting up the IBM Tivoli Monitoring environment

ObjectiveTo set up the environment required to run IBM Tivoli Monitoring commands.

Background informationIn order to issue IBM Tivoli Monitoring commands such as wdmcmd andwdmlseng in a command window, you first need to source in the Tivolienvironment.

Required authorization roleOn UNIX, the user must have root privileges; on Windows, the user must havemembership in the Administrators group.

Before you beginBefore you can monitor your resources, you must link to a JRE for each endpoint.For more information on this subject, see “Link to a JRE for each endpoint” onpage 17.

When you finishNone

ProcedureYou can perform this procedure from the command line.

To set up the environment, enter one of the following commands at the commandprompt:v On a UNIX managed node, enter one of the following commands:

– For non-C shells:. /etc/Tivoli/setup_env.sh

– For C shell:source /etc/Tivoli/setup_env.csh

v On a UNIX endpoint, enter one of the following commands:– For non-C shells:

. /<lcf.install_dir>/dat/<x>/lcf_env.sh.cshetc/Tivoli/lcf/x/lcf_env.sh

– For C shell:source /<lcf.install_dir>/dat/<x>/lcf_env.sh.cshetc/Tivoli/lcf/x/lcf_env.sh

where x is the number of the endpoint installed on the machine.v On a Windows managed node, enter:

%SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd


v On a Windows endpoint, enter:%SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd

where x is the number of the endpoint installed on the machine.

Distributing profilesYou can distribute profiles from either the Tivoli desktop or by using MDist2.

Distributing profiles from the Tivoli desktop

ObjectiveTo distribute profiles to specified subscribers.

Background informationYou can distribute profiles to the following groups:

All levels of subscribersDistributes the profile to all subscribers in the hierarchy.

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

Consider the following example. You have a profile in which a dataless profilemanager is subscribed to a profile manager, and the dataless profile manager has asubscribed endpoint. If you distribute to the next level of subscribers, the profilemanager distributes the profile only to the dataless profile manager. If youdistribute to all levels of subscribers, the profile manager distributes the profile tothe dataless profile manager and to the endpoint.

Required authorization roleadmin

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

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

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

profiles” on page 94 and“Adding customized resource models to profiles” onpage 95 for information.

You can also use the predefined profile managers and profiles created duringinstallation.

See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailedinformation about each resource model.

When you finishNone


ProcedureYou can perform this procedure from the Tivoli desktop only.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the Monitoring for WebLogic Server policy region icon to

display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon containing the resource model you want to

distribute.2. Click Profile → Distribute. The Distribute Profile window opens.3. Select one of the Distribute To options. These options are explained in the

Background information section. You have the following choices:v Next level of subscribers

v All levels of subscribers

These options are explained in “Background information” on page 18.4. Select one of the Distribute Will options based on the following descriptions:

v Preserve modifications in subscribers’ copy of the profile retains changes toexisting resource models in each copy of the profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed. If youedit the configuration of a resource model in the subscriber’s copy, thosechanges are written to every copy of that profile.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profilewindow, saves the settings you made, and returns to the IBM TivoliMonitoring Profile window.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile window open.

ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide. You can also see “Scheduling a job” on page 70for more information.

7. Click Profile → Close to close the IBM Tivoli Monitoring Profile window.


Distributing profiles using MDist2

ObjectiveTo circulate copies of the monitoring profile to subscribers while using MDist2 sothat administrators and users can activate the monitoring process.

Background informationIBM Tivoli Monitoring uses Multiplexed Distribution (MDist2) to performasynchronous profile data transfers through a hierarchy of repeaters. MDist2returns a sequence of responses containing the distribution status from eachendpoint to the application initiating the distribution. These responses are sentback to IBM Tivoli Monitoring in a log file, on the MDist2 command line, orthrough the MDist2 GUI.

IBM Tivoli Monitoring uses the following MDist2 functions:

Asynchronous deliveryIBM Tivoli Monitoring submits a distribution request and immediatelyreceives a distribution identifier and confirmation that the distribution is inprogress. MDist2 uses the callback function to send the final distributionstatus for each endpoint when it completes each endpoint distributioninstead of waiting until all endpoints are distributed.

Assured deliveryAssures that distributed profiles are delivered to the endpoints when thereare network interruptions, computer shutdowns, or disconnectedendpoints. Assured delivery tries to reestablish the connections until it iseither successful or the distribution time expires.

Check-point and restartAssures that an interrupted data stream resumes from the last successfulcheckpoint. You do not have to resend all the IBM Tivoli MonitoringProfile data when the distribution resumes, but only the data that was notsent when the interruption occurred.

Data depotingStores segments of the profile at a depot close to the endpoint so theendpoints can retrieve the data from the depot instead of from the sourcehost. This reduces network traffic and speeds up the distribution.





profiles” on page 94 and“Adding customized resource models to profiles” onpage 95 for information.


See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailedinformation about each resource model.


When you finishNone

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

Command Line: Use the wdistrib command to distribute the profile to thesubscribers of the profile manager. This command updates subscriber databasesand configuration files. If no subscriber is specified, wdistrib updates allsubscribers. Refer to the Tivoli Management Framework Reference Manual for moreinformation about the wdistrib command.

Tivoli desktop:


display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon containing the resource model you want to

distribute.2. Click Profile → Distribute to display the Distribute Profile window.3. Select one of the Distribute To options. These options are explained in the

Background information section. You have the following choices:v Next level of subscribers

v All levels of subscribers

These options are explained in “Background information” on page 18.4. Select one of the Distribute Will options based on the following descriptions:

v Preserve modifications in subscribers’ copy of the profile retains changes toexisting resource models in each copy of the profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed. If youedit the configuration of a resource model in the subscriber’s copy, thosechanges are written to every copy of that profile.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profilewindow, saves the settings you made, and returns to the IBM TivoliMonitoring Profile window.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile window open.


ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide. You can also see “Scheduling a job” on page 70for more information.

7. Click Profile → Close to close the IBM Tivoli Monitoring Profile window.


Chapter 3. Setting up the Tivoli Enterprise Console for eventcorrelation

This chapter provides information on setting up the Tivoli Enterprise Console forevent correlation. Setting up event correlation requires the configuration of theTivoli Enterprise Console event server.

For information about the event classes and rules included with IBM TivoliMonitoring for Web Infrastructure: WebLogic Server, see Appendix E, “Eventclasses and rules” on page 103.

For information about using Tivoli Enterprise Console, see the Tivoli EnterpriseConsole User’s Guide.

If you experience problems using the procedures in this chapter, see Appendix F,“Problem determination” on page 105. You can also see the IBM Tivoli Monitoringfor Web Infrastructure Reference Guide for information about any messages that youreceive.

Overview of the Tivoli Enterprise ConsoleThe Tivoli Enterprise Console provides the following functions:v Receiving events from various sourcesv Processing events using rulesv Grouping events and delegating the groups selectively to administratorsv Responding to events automaticallyv Viewing events at a console

In the Tivoli Enterprise Console, rules (.rls) files contain the logic for correlation ofevents. BAROC (.baroc, Basic Recorder of Objects in C) files contain the definedevent classes.

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

EventsAn event is a structured piece of information. It carries information aboutitself, including the event class, event identity, severity, location (hostwhere the event originated), and description. IBM Tivoli Monitoring usesevents with resource models to verify the persistence of an indication overa period of cycles.

Sources of EventsThe Tivoli Enterprise Console accepts events from many sources. Forexample, you can configure resource models to send events. Typically,Tivoli software is set up so that events are sent in response to changes inan application or system resource.

Event ProcessingThe Tivoli Enterprise Console uses rules to process events. A rule is madeup of a set of logic statements. The rule determines what to do with the

23

event based on information provided in the event, such as the event class,event name, severity, location, and description.

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

Event Grouping

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

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

Viewing EventsThe Tivoli Enterprise Console includes a console where administrators canwatch for incoming events and respond to them. The Tivoli EnterpriseConsole can filter out normal events, respond automatically to anticipatedproblems, and forward only those events that require human intervention.

Responses to EventsThe Tivoli Enterprise Console normally provides automatic responses tomany common events, either by executing response programs or byexecuting Tivoli tasks. For example, you can set up a response to the eventthat is received when a server becomes unavailable. The specific responsecan inform an administrator or attempt automatic restarts of the server, ora combination of both.

You cannot use the Tivoli Enterprise Console automatic responsemechanism with this product. However, you can write Tivoli EnterpriseConsole rules that accomplish the same thing.

Configuring the Tivoli Enterprise Console event server

ObjectiveTo set up your Tivoli Enterprise Console event server to process WebLogic Serverevents.

Background informationYou must set up the event server before events can be sent to Tivoli EnterpriseConsole. Use the WebLogic_Configure_TEC task to set up the Tivoli EnterpriseConsole event server.

The WebLogic_Configure_TEC task performs the following actions:v Imports the IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server

event classes and rule setv Imports the IBM Tivoli Monitoring event classes (if they are not already present)v Imports the Tivoli Business Systems Manager rule set, if appropriatev Compiles the rule base to incorporate new classes and rulesv Loads the new rule base (optional)v Optionally stops and restarts the event server


You can configure only one Tivoli Enterprise Console event server for each Tivolimanagement region. When you have interconnected Tivoli management regions,run the Configure Event Server task against each Tivoli management region thatcontains a Tivoli Enterprise Console event server.

If your Tivoli Enterprise Console event server is in a separate Tivoli managementregion from the one that contains IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server, you must run the WebLogic_Send_Files_To_TEC task beforerunning the Weblogic_Configure_TEC task. The .baroc and .rls files used toconfigure the Tivoli Enterprise Console event server must be present in the Tivolimanagement region before configuration.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server includes thefollowing sets of event classes and rules specific to WebLogic Server:v ITMWLS_Eventsv Events for each resource model, such as the WebLogic_Server_Down event

Required authorization roleweblogic_senior

Before you beginEnsure that you have the Tivoli Enterprise Console server installed in the sameTivoli management region where you have IBM Tivoli Monitoring and IBM TivoliMonitoring for Web Infrastructure: WebLogic Server installed. If you have theTivoli Enterprise Console server installed on a different Tivoli management region,you have the option of making a two-way connection between the Tivolimanagement regions. See the Tivoli Management Framework User’s Guide for detailson properly connecting two Tivoli management regions.

Ensure that you have taken the following steps to properly connect the two Tivolimanagement regions:v Run the wconnect command as a two-way connection.v Install the Tivoli Enterprise Console ACF product on the Tivoli management

region that has IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverinstalled but not Tivoli Enterprise Console by completing the following steps:1. From the Tivoli desktop menu, select Install.2. Select Install Product.3. Select the Tivoli Enterprise Console ACF product from the Product Install

window.4. Click Install & Close.

v Ensure that you update the following Tivoli managed resources:– Register each of the Tivoli management regions in the ManagedNode

property of the other Tivoli management region.

Note: Use the wlookup command to ensure that you have a validregistration. If your registration is not accurate, use the wupdatecommand to properly register the Tivoli management region on amanaged node.

– Register the Tivoli management region where Tivoli Enterprise Consoleresides on the EventServer managed resource in the Tivoli managementregion where IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverresides.

Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 25

Note: Use the wlookup and wregister commands to ensure that you have avalid registration. If your registration is not accurate, use the wupdatecommand to properly register the Tivoli management region in theevent server.

– Register the WebLogicServer managed resource in the Tivoli managementregion where Tivoli Enterprise Console resides.

Note: Use the wlookup and wregister commands to ensure that you have avalid registration. If your registration is not accurate, use the wupdatecommand to properly register the IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server managed resources.

See the Tivoli Management Framework Reference Manual for details on the wconnect,wlookup, wregister, and wupdate commands.

If you choose to make a two-way connection between the Tivoli managementregion where Tivoli Enterprise Console resides and the Tivoli management regionwhere IBM Tivoli Monitoring and IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server reside, run the WebLogic_Send_Files_To_TEC task afterconnecting the two Tivoli management regions in order to place the required fileson the remote Tivoli management region. See the IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server Reference Guide for details on running theWebLogic_Send_Files_To_TEC task.

When you finishNone

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

Command line: Use the wruntask command to run the WebLogic_Configure_TECtask. For the CLI syntax for this task, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Tivoli desktop: Follow these steps to perform this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the WebLogic Monitoring policy region.2. Double-click the WebLogic Event Tasks icon.3. Double-click the WebLogic_Configure_TEC task icon and complete the Execute

Task window. Select the managed node on which you want configure the eventserver.

4. Select Display on Desktop to display the output of the task on the desktop.5. Increase the timeout value because the WebLogic_Configure_TEC task can take

a considerable amount of time to finish.6. Click Execute & Dismiss to display the Configure Event Server window.


Complete the following fields:

Rule Base ConfigurationSpecify the way that the rule base is created:

Rule Base NameSpecify the rule base name here. You must select a rule basethat does not exist. If you want to reuse a rule base name, youmust delete the old rule base first. See the Tivoli EnterpriseConsole User’s Guide for details.

Copy Base NameIf you select this option, you must type the name of the newrule base in the Rule Base Name field.

Event Group NameThis is supplied for compatibility with Tivoli EnterpriseConsole 3.6 servers. For Tivoli Enterprise Console 3.7.1, anyvalue you put here is ignored.

Restart Event Server?Select Yes if you want this rule base to be used afterconfiguration is complete.

7. Click Set and Execute to start the task. The Configure Event Server Outputwindow displays the job status after the task is completed.

Figure 2. The WebLogic_Configure_TEC task window

Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 27

Chapter 4. Integrating with Tivoli Business Systems Manager

This chapter provides information on using Tivoli Business Systems Manager tomanage WebLogic Server resources and events.

Integrating IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server intoTivoli Business Systems Manager includes the following steps:

Table 3. Integrating with Tivoli Business System Manager

Goal Refer to

Install the IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server integrationprogram on the Tivoli Business SystemsManager server.

“Integrating IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server with TivoliBusiness Systems Manager” on page 30

Configure your Tivoli Enterprise Consoleevent server to forward events to TivoliBusiness Systems Manager.

“Configuring the Tivoli Enterprise Consoleevent server to work with Tivoli BusinessSystems Manager” on page 31

Define the specific IBM Tivoli Monitoringfor Web Infrastructure: WebLogic Serverobjects for Tivoli Business Systems Managerusing a discovery task.

“Discovering resources for Tivoli BusinessSystems Manager” on page 32

This chapter also provides a list of the IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server tasks that you can run from Tivoli BusinessSystems Manager and information about uninstalling the IBM Tivoli Monitoringfor Web Infrastructure: WebLogic Server integration from Tivoli Business SystemsManager.

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

Tivoli Business Systems Manager consists of the following components:

Tivoli Business Systems Manager management serverThe Tivoli Business Systems Manager management server processes all theavailability data that is collected from various sources. Availability data isinserted in the Tivoli Business Systems Manager database, where intelligentagents provide alerts on monitored objects and then broadcast those alertsto Tivoli Business Systems Manager workstations. The management serverprocesses all user requests that originate from the workstations andincludes a database server that is built around a Microsoft SQL Serverdatabase.

Tivoli Business Systems Manager workstationThe Tivoli Business Systems Manager workstation displays objects incustomized views, called Line of Business Views. Objects are presented in ahierarchical TreeView so that users can see the relationship betweenobjects. Alerts are overlaid on the objects when the availability of the objectis threatened.

29

Tivoli Event EnablementTivoli Event Enablement is installed on the Tivoli Enterprise Console eventserver and enables the event server to forward events to Tivoli BusinessSystems Manager. Tivoli Event Enablement defines event classes and rulesfor handling events related to Tivoli Business Systems Manager.

For more information about Tivoli Business System Manager, see the TivoliBusiness System Manager documentation.

PrerequisitesBefore you integrate IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer into Tivoli Business Systems Manager, perform the following prerequisitesteps:v Install Tivoli Business Systems Manager, as described in the Tivoli Business

Systems Manager Installation and Configuration Guide. You must install TivoliBusiness Systems Manager Version 1.5 with patch 35.

v Install and configure the Tivoli Event Enablement (with patch 38) on all TivoliEnterprise Console event servers that receive events that you want to forward toTivoli Business Systems Manager. See the Tivoli Business Systems ManagerInstallation and Configuration Guide for more information.

v Configure Tivoli Business Systems Manager to communicate with each TivoliEvent Enablement installed in the previous step. See the Tivoli Business SystemsManager Installation and Configuration Guide for more information.

Integrating IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer with Tivoli Business Systems Manager

ObjectiveTo integrate IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server withTivoli Business Systems Manager so you can receive WebLogic Server events onthe Tivoli Business Systems Manager.

Background informationTo enable Tivoli Business Systems Manager to manage WebLogic Server events,you must install an IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverintegration program on the Tivoli Business Systems Manager server. Thisintegration program performs the following steps:v Defines the WebLogic Server objects in Tivoli Business Systems Managerv Adds IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server tasks to

the object types in Tivoli Business Systems Managerv Defines a line of business for WebLogic Server resources

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

Before you beginMake sure that your Tivoli Business Systems Manager environment is configuredcorrectly and that you have Tivoli Event Enablement installed on each TivoliEnterprise Console event server that you want to forward events. For moreinformation, see the Tivoli Business Systems Manager Installation and ConfigurationGuide.


When you finishConfigure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager. See “Configuring the Tivoli Enterprise Console eventserver to work with Tivoli Business Systems Manager” for more information.

ProcedureUse the following steps to install the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server integration program:1. On the Tivoli Business Systems Manager server, insert the IBM Tivoli Monitoring

for Web Infrastructure: WebLogic Server CD and, from a command prompt,navigate to the \TBSM directory.

2. Type install to start the installation wizard.3. Click Next on the welcome screen.4. Specify an installation location for the Tivoli Business Systems Manager

integration program. The default location is C:\tivoli\itmwls. Click Browse toselect a different installation location.Click Next to continue.

5. Provide the following Microsoft SQL Server information and click Next to startthe installation.

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

SQL UseridThe SQL user ID

SQL PasswordThe password for the user ID defined above

A progress bar is displayed to show the progress of the installation. Wheninstallation is complete, a message is displayed.

6. Click Finish to exit the installation wizard.

Configuring the Tivoli Enterprise Console event server to work withTivoli Business Systems Manager

ObjectiveTo configure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager.

Background informationBefore Tivoli Enterprise Console event servers can forward events to TivoliBusiness Systems Manager, you must configure them to use a rule base.

Required authorization rolesenior

Before you beginInstall the Tivoli Event Enablement on each Tivoli Enterprise Console event serverthat you want to forward events to Tivoli Business Systems Manager. For moreinformation, see the Tivoli Business Systems Manager Installation and ConfigurationGuide for more information.

Chapter 4. Integrating with Tivoli Business Systems Manager 31

When you finishDefine your WebLogic Server objects for Tivoli Business Systems Manager with theWebLogic_TBSM_Discovery task, as described in “Discovering resources for TivoliBusiness Systems Manager”.

ProcedureUse the WebLogic_Configure_TEC task to configure (or reconfigure) each eventserver. If you installed the Tivoli Event Enablement on the event server, this taskrecognizes that and compiles the rule base that forwards events to Tivoli BusinessSystems Manager. For information on running this task, see “Configuring theTivoli Enterprise Console event server” on page 24.

Discovering resources for Tivoli Business Systems Manager

ObjectiveTo discover the specific IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer objects for Tivoli Business Systems Manager.

Background informationThe IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server integrationprogram that you installed in “Integrating IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server with Tivoli Business Systems Manager” on page 30defined the types of objects that you want Tivoli Business Systems Manager tomanage. After you define the object types, you must discover the specific objects.You can do this with the WebLogic_TBSM_Discovery task. This task searches amanaged node for objects and sends a DISCOVER event to Tivoli Business SystemsManager for each object. The WebLogic_TBSM_Discovery task also maintains a listof the objects that have been discovered and alerts Tivoli Business SystemsManager when they have been deleted by sending Tivoli Business SystemsManager a GONE event for each object that no longer exists on the managed node.

Required authorization roleweblogic_admin, weblogic_super

Before you beginConfigure your Tivoli Enterprise Console event server, as described in“Configuring the Tivoli Enterprise Console event server to work with TivoliBusiness Systems Manager” on page 31.

When you finishUse Tivoli Business Systems Manager to view and manage your WebLogic Serverobjects. For information on using Tivoli Business Systems Manager, see the TivoliBusiness Systems Manager User’s Guide. For information on the IBM TivoliMonitoring for Web Infrastructure: WebLogic Server tasks that you can run fromTivoli Business Systems Manager, see “Working with Tivoli Business SystemsManager” on page 33.


Command line: Use the wruntask command to run theWebLogic_TBSM_Discovery task from the command line. For information on theCLI syntax for this task, see the IBM Tivoli Monitoring for Web InfrastructureReference Guide.

Tivoli desktop: Use the following steps to run this procedure as a task:1. Open the task library window by performing the following steps:


a. Open the Tivoli desktop.b. Double-click the Monitoring for WebLogic Server policy region icon to

display the policy region.2. In the WebLogic Server task library, double-click the

WebLogic_TBSM_Discovery task.3. Select the managed node on which you want to search for objects.

Note: This task must be run on the Tivoli Enterprise Console server machine inthe managed node. If your Tivoli Enterprise Console server is in anotherTivoli management region that has been connected to the Tivolimanagement region containing IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server, run the task on the Tivoli EnterpriseConsole server in the connected Tivoli management region.

4. Select Display on Desktop to display the output on the desktop.5. Increase the timeout value if you selected more than one managed node

because this can cause the task to take longer to display output.6. Click Execute.

If the task completes successfully, you receive a return code of 0.

Working with Tivoli Business Systems ManagerIn addition to using Tivoli Business Systems Manager to monitor the state of yourresources, you can also run tasks on the objects. IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server tasks are loaded into Tivoli Business SystemsManager when you install the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server integration program. These tasks appear on the Operation Tasksmenus for the WebLogic objects. The Operation Tasks menu is displayed whenyou right-click an object.

You can perform the following WebLogic Server tasks from Tivoli Business SystemsManager:v Start_Serverv Stop_Serverv Kill_Server

Tivoli Business Systems Manager also monitors the status of resource models.Events generated by the Tivoli Enterprise Console adapter or resource models areforwarded from Tivoli Enterprise Console to Tivoli Business Systems Manager.

For more information about these tasks and resource models, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Uninstalling IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer integration from Tivoli Business Systems Manager

ObjectiveTo remove the IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverintegration program from Tivoli Business Systems Manager.

Chapter 4. Integrating with Tivoli Business Systems Manager 33

Background informationUninstalling the IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverintegration program removes the WebLogic Server object definitions and objectsfrom Tivoli Business Systems Manager.

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

Before you beginNone

When you finishNone

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

navigate to the directory where you installed the IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server integration program. The default directoryis C:\tivoli\itmwls.

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

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

the uninstallation:

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

SQL UseridThe SQL user ID

SQL PasswordThe password for the user ID defined above

6. Click Finish to exit the installation wizard.


Chapter 5. Working with resource models

This chapter provides information about using the resource models that areincluded in IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server. Youcan customize various management aspects of the resource models so that theyhave the appropriate settings for your monitoring environment. Customizing aresource model includes the following steps:

Table 4. Working with resource models

Goal Refer to

Modify indications. “Modifying indications” on page 36

Specify tasks for indications. “Specifying tasks for an indication” onpage 38

Send notices to administrators. “Sending a notice to administrators when anevent occurs” on page 39

Create scheduling rules. “Creating scheduling rules” on page 41

Modify data logging settings. “Modifying data logging settings” onpage 43

Manage profiles and resource models atendpoints.

“Managing profiles and resource models atendpoints” on page 45

Manage gateways. “Managing IBM Tivoli Monitoringgateways” on page 46

Determine which resource models arerunning.

“Determining which resource models arerunning on endpoints” on page 46

View resource model results. “Viewing resource model results with theIBM Tivoli Monitoring Web Health Console”on page 47

Resource model libraryIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides thefollowing resource models.

Table 5. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server resource models

Resource model Description

Connector Connection Pools Monitors the WebLogic Server’s connectorconnection pools (JCA), connection load, andconnections rejected rate.

DB Connection Pools Monitors the WebLogic Server’s DBconnection pools.

Enterprise Java Beans Monitors the WebLogic Server’s EnterpriseJava Bean (EJB) transactions.

Execution Queue Monitors the number of pending requests inthe WebLogic Server’s execution queue.

HTTP Sessions Monitors the WebLogic Server HTTP Sessionthroughput and load.

JVM Monitors the performance of the Java VirtualMachine (JVM) runtime memory.

35

Table 5. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server resourcemodels (continued)

Resource model Description

Messaging Monitors the WebLogic Server messaging(JMS) server and the destination load andthroughput.

Server State Monitors the availability of WebLogicServers.

Transactions Monitors WebLogic Server transactions.

Web Applications Servlets and JSPs Monitors the WebLogic Server’s Servlet andJava server pages (JSP) throughput andresponse time.

For information about the default configuration of these resource models, see theIBM Tivoli Monitoring for Web Infrastructure Reference Guide.

Modifying indications

ObjectiveTo modify indication rules so that resources are monitored and events aregenerated relevant to your environment.

Background informationEach resource model triggers an indication if certain conditions defined by theresource model’s thresholds are not satisfied during the monitoring cycle.





profiles” on page 94 for information.


When you finishDistribute the profile to which the resource model belongs. See “Distributingprofiles from the Tivoli desktop” on page 18.

– OR –

Optional: Continue customizing the resource model:v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 38.v Specify if you want to receive information on a specific event through a notice.

See “Sending a notice to administrators when an event occurs” on page 39.v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules” on page 41.


v Specify if you want the log data collected by a resource model written to a localdatabase. See “Modifying data logging settings” on page 43.

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

Command Line: Use the wdmeditprf command to customize a resource modelfor a profile. See the IBM Tivoli Monitoring Reference Guide for more information.

Tivoli desktop:


display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize from the IBM Tivoli

Monitoring Profile window.3. Click Edit to open the Edit Resource Model dialog.4. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.5. Select the indication that contains the values you want to modify.6. Apply the changes to the values that are appropriate to your requirements. See

the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for the defaultresource model settings.You can customize the following fields. For more information about thesefields, see the IBM Tivoli Monitoring documentation.

Number of occurrencesSpecifies the number of consecutive times the problem occurs beforethe software generates an indication. You can change this value tospecify the number of times a problem occurs before an indication isgenerated.

Number of holesDetermines how many cycles that do not produce an indication canoccur between cycles that do produce an indication.

Use the value for the Number of Holes in conjunction with theNumber of Occurrences parameter and the Cycle Time to define atime window for the generation of an event.

Send TEC EventsSelect this check box to send an event to the Tivoli Enterprise Console.You must have Tivoli Enterprise Console installed and configured.

Send to TBSMSends events to Tivoli Business Systems Manager. You do not need toselect this box. If you have Tivoli Business Systems Manager installedand configured, Tivoli Enterprise Console automatically forwardsevents to Tivoli Business Systems Manager.

7. Specify the severity of the indication in the Severity pull-down list. You havethe following options:v FATAL

Chapter 5. Working with resource models 37

v CRITICALv WARNINGv HARMLESSv MINOR

8. Click one of the following buttons:

Apply ChangesSaves the changes and leaves the Indications and Actions windowopen.

Apply Changes and CloseCloses the Indications and Actions window and saves the changes.

Specifying tasks for an indication

ObjectiveTo specify a task so administrators and users can determine corrective or reportingtasks for an event.

Background informationYou can select one or more task to run automatically when an event occurs. Thesetasks can access the IBM Tivoli Monitoring event name and thresholds byaccessing the environment variables.





profiles” on page 94 and for information.



– OR –

Optional: Continue customizing the resource model:v Specify if you want to customize your thresholds and events to optimize the

monitoring process. See “Modifying indications” on page 36.v Specify if you want to receive information on a specific event through a notice.


time periods of selected days. See “Creating scheduling rules” on page 41.v Specify if you want the log data collected by a resource model written to a local

database. See “Modifying data logging settings” on page 43.




Tivoli desktop:



model.2. Select a resource model from the IBM Tivoli Monitoring Profile window and

click Edit to open the Edit Resource Model window.3. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.4. Select the indication for which you want to specify a task.5. Click Tasks in the Action List window. The Tasks window opens.6. Double-click the appropriate task library from the scroll list of the Libraries

panel. The tasks contained in the library are displayed in the Tasks panel.7. Double-click the appropriate task in the Tasks panel. You can also click Select

Task.8. Specify the appropriate parameters in the Configure Task window.

Additional information: This only applies to tasks that require input parameters.9. Click Change & Close to add the task to the Action List panel in the

Indications and Actions window.

Repeat these steps for each task you want to add.

Sending a notice to administrators when an event occurs

ObjectiveTo send a notice in response to an event so administrators can take the appropriateactions or responses.

Background informationYou can select the IBM Tivoli Monitoring Utility task to send notices in response toan event.








You must create an administrator before you can subscribe the administrator to anotice group. For information about creating administrators, see the TivoliManagement Framework, Version 3.7.1: Reference Manual.


– OR –


monitoring process. See “Modifying indications” on page 36.v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 38.v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules” on page 41.v Specify if you want the log data collected by a resource model written to a local




Tivoli desktop:




click Edit to open the Edit Resource Model window.3. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.4. Select the indication for which you want to generate notices.5. Click Tasks in the Action List window. The Tasks window opens.6. Double-click the IBM Tivoli Monitoring Utility Tasks library in the scroll list

of the Libraries panel. The tasks contained in the IBM Tivoli Monitoring UtilityTasks library are displayed in the Tasks panel.

7. Double-click dm_mn_send_notice in the Tasks panel. The Configure Taskwindow opens.

8. Specify the appropriate parameters in the Configure Task window.Additional information: Run the wlsnotif -g command to see the available NoticeGroups. See the IBM Tivoli Monitoring Reference Guide for more information.


9. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.

Creating scheduling rules

ObjectiveTo create schedule rules so administrators and users can determine the timeperiods on selected days when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to createspecific scheduling rules that determine a period when monitoring takes place. Youcan divide the overall collection period into active and inactive intervals byapplying one or more schedule rules.

The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules thatenable you to set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If the profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that monitors the same local time period in different time zones. Alltimes of events or activities reported from endpoints or gateways are also loggedin the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesContains a list of the defined scheduling rules, which manage the timeintervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.









– OR –




See “Sending a notice to administrators when an event occurs” on page 39.v Specify if you want the log data collected by a resource model written to a local




Tivoli desktop:




click Edit to open the Edit Resource Model window.3. Click Schedule to open the Scheduling window.4. To use the default monitoring period, select Always in the Schedule panel.5. To customize the monitoring period, perform the following steps:

a. Set a Start Date and Stop Date to customize the monitoring period.b. Click New Rule in the Schedule Rules panel.c. Type a name for the rule in the Rule Name text box of the Rule Editor

panel.d. Select one or more items in the weekday list to specify the day or days on

which you want the collections active during the collection period.Additional information: Use the Shift or Ctrl key as necessary to select morethan one day from the list.

e. Set the Start Time and Stop Time for the collection activity or select the AllDay check box.


Additional information: Times are always interpreted as local time where theendpoint engine runs. Setting a time interval of 08:00 to 13:00 ensures thatmonitoring takes place between those times in all time zones to which youdistribute the profile.

f. Click Set Rule. Your new rule appears in the Schedule Rules list.Additional information: To display the details of any rule, select the rule in theSchedule Rules list. Its settings are displayed in the Rule Editor group box.

6. Click Modify & Close to save your rule and close the Scheduling window.

Repeat these steps for each scheduling rule that you want to create.

Modifying data logging settings

ObjectiveTo modify data logging information so administrators and users can log datacollected by a resource model and write it in a local database.

Background informationYou can view the log data through the IBM Tivoli Monitoring Web Health Consoleafter you write it in a local database. You can store one of the following types ofdata in the database:

Raw dataData written exactly as the resource model collects it. All the monitoredvalues are collected and copied in the database.

Aggregated dataData collected and aggregated at fixed intervals that you define(Aggregation Period). Only the aggregated values are written in thedatabase. The aggregated data is calculated on the basis of one or more ofthe following options:v Maximumv Minimumv Average

Tivoli Enterprise Data Warehouse data loggingData collected is logged to the Tivoli Enterprise Data Warehouse.

Note: To enable Tivoli Enterprise Data Warehouse data logging, you mustdisable aggregated data logging.









– OR –





time periods of selected days. See “Creating scheduling rules” on page 41.



Tivoli desktop:




click Edit to open the Edit Resource Model window.3. Click Logging to open the Logging window.4. Select Enable Data Logging in the Data Logging Settings panel. To enable raw

data logging, select Raw Data.5. To enable logging aggregated data, perform the following steps to specify the

aggregation rule applied to the data before it is written to the database:a. Set Hours and Minutes of the Aggregation Period to the required values.b. Select one or more of the following functions to perform on the numerical

data collected during the aggregation period before it is written to thedatabase:

MaximumCalculates and logs the peak value in each aggregation period.

MinimumCalculates and logs the lowest value in each aggregation period.

AverageCalculates and logs the average of all values in each aggregationperiod.

6. To enable Tivoli Enterprise Data Warehouse data logging, clear Aggregateddata and select TEDW data.


7. Set Hours and Minutes of the Historical Period to the required values.8. Click Apply Changes and Close to save your changes and close the Logging

window.

Managing profiles and resource models at endpoints

ObjectiveTo manage profiles and resource models after they are distributed to endpoints soadministrators and users can maintain monitoring processes on those endpoints.

Background informationNone





profiles” on page 94 for information.v Distribute the profile. See “Distributing profiles from the Tivoli desktop” on

page 18 for information.


When you finishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command Line: Use the wdmcmd command to stop or restart IBM TivoliMonitoring on one or more endpoints from a gateway or server.

Use the wdmdistrib command to distribute a profile to one or more subscribers.

Use the wdmeng command to stop or start profiles or resource models atendpoints or to delete profiles at endpoints.

Use the wdmlseng command to return a list and the status of all resource modelsthat have been distributed on a specified endpoint.

Use the wdmtrceng command to set the trace parameters of the IBM TivoliMonitoring engine at the endpoint.

See the IBM Tivoli Monitoring Reference Guide for information about the syntax ofthese commands.


Managing IBM Tivoli Monitoring gateways

ObjectiveTo manage IBM Tivoli Monitoring on gateways so administrators and users canrun monitoring processes on those gateways.









When you finishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command Line: Use the wdmmn command to stop or start selected IBM TivoliMonitoring processes on one or all gateways. See the IBM Tivoli MonitoringReference Guide for more information.

Determining which resource models are running on endpoints

ObjectiveTo determine which resource models are running on an endpoint.










When you finishNone

ProcedureYou can perform this procedure from the command line.

You can also view the resource models distributed to endpoints with the WebHealth Console, as described in “Viewing resource model results with the IBMTivoli Monitoring Web Health Console”.

Command Line: Use the wdmlseng command to determine which resourcemodels are running on an endpoint:wdmlseng -e <endpoint>

where <endpoint> is the Tivoli endpoint label.

Refer to the IBM Tivoli Monitoring User’s Guide for more information.

Viewing resource model results with the IBM Tivoli Monitoring WebHealth Console

This section provides an overview of the Web Health Console. For completeinformation on installing and working with the Web Health Console see the latestversion of the IBM Tivoli Monitoring User’s Guide. The Web Health Console runs onNetscape 6.x and Internet Explorer 6.x. You can use the Web Health Console forthe following purposes:v Checking, displaying, and analyzing the status and health of endpoints that

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

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

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

models on selected endpointv Removing a profile from the selected endpoints

You can use the Web Health Console to check, display, and analyze the status andhealth of any endpoint with profiles and resource models. Status reflects the stateof the endpoint, such as running or stopped. Health is a numeric value determinedby resource model settings. You can also use the Web Health Console to work withreal-time or historical data from an endpoint that is logged to the IBM TivoliMonitoring database.

You can use the diagnostic and monitoring capabilities of the Web Health Consoleto perform targeted analysis of problems associated with individual endpointswhen an event is sent to the Tivoli Enterprise Console. Use the online andhistorical data to follow up specific problems with single endpoints.

Understanding resource healthThe Web Health Console obtains events and indications from endpoints. The WebHealth Console displays the health of each potential problem as a numeric value


between 100 (perfect health) and zero (with zero meaning that the conditions forthe corresponding event are met). Intermediate values show the percentage ofoccurrences currently registered with respect to the total number of occurrencesneeded to trigger an event. See Table 6

Table 6. Health Determination Example

Cycle 1 2 3 4 5

CPU% 55 73 54 63 68

Occurrences or Holes H O H O O

Occurrence Count 0 1 1 2 3

Health % 100 75 75 50 25

Table 6 displays the health percentage changes in steps of 25% because 4occurrences were required to trigger an event; if the indication required 5occurrences, the health percentage would have changed by steps of 20%. Resourcehealth is determined at the indication level and passed up to the endpoint. Thelowest health of any indication in a resource model is shown as the health of thatresource model and the lowest health of any resource model installed on anendpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is installed on an endpoint has a health of zero, the healthof the endpoint is shown as zero.

The required occurrences, cycle times, thresholds, and parameters for indicationsare defined when the resource model is created in the IBM Tivoli MonitoringWorkbench. If you use the default profile managers created during the installationof IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server, the occurrences,cycle times, thresholds, and parameters are already defined.

Connecting the IBM Tivoli Monitoring Web Health ConsoleYou can connect the IBM Tivoli Monitoring Web Health Console to any Tivolimanagement region server, managed node, or endpoint, and configure it tomonitor any or all of the endpoints that are found in that region. The IBM TivoliMonitoring Web Health Console does not have to be within the region itself,although it could be. To connect to the IBM Tivoli Monitoring Web Health Consoleyou need access to the server on which the IBM Tivoli Monitoring Web HealthConsole server is installed and the IBM Tivoli management region on which youwant to monitor health. All user management and security is handled through theIBM Tivoli management environment. This includes creating users and passwordsas well as assigning authority.

For more information, see the Web Health Console documentation in the IBMTivoli Monitoring publications library.


Chapter 6. Working with IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server resources

This chapter provides information about working with IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server resources. The following table provides anoverview of the topics covered in this chapter.


Register or unregister a WebLogic Domain. “Register or unregister a WebLogic Domain”on page 49

Configure a WebLogic Domain. “Configure WebLogic Domains” on page 50

Register or unregister a WebLogic Server. “Register or unregister WebLogic Servers”on page 51

Configure a WebLogic Server. “Configure WebLogic Servers” on page 53

Discover the WebLogic Servers within aspecific domain.

“Discover the WebLogic Servers within aspecific domain” on page 56

Start, stop, or kill a server. “Starting, stopping, or killing a server” onpage 58

Validate a WebLogic Server. “Validate a WebLogic Server” on page 60

Note: The procedures in this chapter are performed from the Tivoli desktop or thecommand line.

Register or unregister a WebLogic Domain

ObjectiveTo register or unregister a WebLogic Domain.




When you finishNone

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

Command line: Use the wweblogic -RegisterDomain command to register aWebLogic Domain. Use the wweblogic -UnregisterDomain command to unregistera WebLogic Domain. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Tivoli desktop: Complete the following steps to register a WebLogic Domainfrom the Tivoli desktop:

49

1. From the Create menu inside the Monitoring for WebLogic policy region or asub-region, select WebLogicDomain.

2. Complete the following fields on the Register Domain window:



Maximum Days UnvalidatedMaximum number of days to allow the WebLogic Domain to beunvalidated. If a WebLogic Server remains unvalidated for more daysthan this setting, it will be removed the next time a DiscoverServersmethod is run against this WebLogicDomain.

System UserLogin ID of the administrator of the WebLogicDomain. This ID is usedto connect to the underlying WebLogic Domain.




3. Click Execute & Close.

Complete the following steps to unregister a WebLogic Domain from the Tivolidesktop:1. Select the WebLogic Domain that you want to unregister.2. From the Edit menu select Delete.3. Click Yes in the confirmation window.

Configure WebLogic Domains

ObjectiveTo configure or change the properties of an existing WebLogic Domain.




When you finishNone



Command line: Use the wweblogic -ConfigureDomain command to configure aWebLogic Domain. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Tivoli desktop: Use the following steps to run this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the policy region that contains the

application server objects to display the Policy Region window.The default policy region is Monitoring for WebLogic. If you created additionalpolicy regions, open the one that contains the objects you want to work with.

2. Right-click the WebLogic Domain that you want to configure and clickConfigure.

3. Complete the following fields on the Configure Domain window:



Maximum Days UnvalidatedMaximum number of days to allow the WebLogic Domain to beunvalidated. If a WebLogic Server remains unvalidated for more daysthan this setting, it will be removed the next time a DiscoverServersmethod is run against this WebLogic Domain.

System UserLogin ID of the administrator of the WebLogic Domain. This ID is usedto connect to the underlying WebLogic Domain.




4. Click Execute & Close.

Register or unregister WebLogic Servers

ObjectiveTo register or unregister a WebLogic Server.

Background information

Note: All of the WebLogic Servers in any specific WebLogic Domain must be thesame version of BEA WebLogic Server. This is a general expectation of theBEA WebLogic Server product.

When registering a WebLogic Server, the server is validated using the STRONGvalue.


Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server resources 51

Before you beginOnce you have registered a WebLogic Domain, it is recommended that the firstserver you register be the WebLogic Administration Server. The domain wideconfig.xml file resides on this server.

When you finishNone


Command line: Use the wweblogic -RegisterServer command to register aWebLogic Server. Use the wweblogic -UnregisterServer command to unregister aWebLogic Server. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.



2. Right-click the WebLogic Domain that contains the servers you want to registerand click Register Server.

3. Complete the following fields on the Register Server window:

Endpoint LabelName or IP address of the machine where the WebLogic Server runs.Do not confuse this name with the label of the endpoint object thatpoints to that machine. A valid IP address contains less than fouroctets, assuming subnet masks are set up correctly. For example, 255,255.255, 255.255.255, and 255.255.255.255 are all valid IP addresses.

Label Label you want to use for the Tivoli object. This label must be uniquewithin the Tivoli management region. If left blank, this label willdefault to a close match of the server name.


VersionVersion of the WebLogic Server. This value is either 6.1 or 7.0.










Administration ServerTRUE or FALSE. If TRUE is selected, this WebLogic Server is theAdministration Server for the domain in which it resides. Only oneserver acts in this capacity. In the event that you register a server as theAdministration Server and then register a second server in the samedomain as the Administration Server, the original AdministrationServer is no longer the Administration Server for that domain. Only thelast WebLogic Server that is configured or registered as anAdministration Server has that status for a domain.



Use the following steps to unregister a WebLogic Server from the Tivoli desktop:1. From the Tivoli desktop, double-click the policy region that contains the server

objects to display the Policy Region window.The default policy region is Monitoring for WebLogic. If you created additionalpolicy regions, open the one that contains the objects you want to work with.

2. Double-click on the WebLogic Domain that contains the WebLogic Server youwant to work with.

3. Select the WebLogic Server and from the Edit menu select Delete.4. Click Yes in the confirmation window.

Configure WebLogic Servers

ObjectiveTo configure or change the properties of an existing WebLogic Server.


Background information

Note: All of the WebLogic Servers in any specific WebLogic Domain must be thesame version of BEA WebLogic Server. This is a general expectation of theBEA WebLogic Server product.

When configuring a WebLogic Server, the server is validated using the STRONGvalue.



When you finishNone


Command line: Use the wweblogic -ConfigureServer command to configure aWebLogic Server. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.



2. Right-click the WebLogic Domain that contains the objects you want to workwith and select Open.

3. Right-click the WebLogic Server that you want to configure and clickConfigure.

Figure 3. The Policy Region: Monitoring for WebLogic window


4. Complete or edit the following fields on the Configure Server window:

Endpoint LabelName or IP address of the machine where the WebLogic Server runs.Do not confuse this name with the label of the endpoint object thatpoints to that machine. A valid IP address contains less than fouroctets, assuming subnet masks are set up correctly. For example, 255,255.255, 255.255.255, and 255.255.255.255 are all valid IP addresses.

Label Label you want to use for the Tivoli object. This label must be uniquewithin the Tivoli management region. If left blank, this label willdefault to a close match of the server name.


Version6.1 or 7.0.






Figure 4. The WebLogicDomain window





Administration ServerTRUE or FALSE. If TRUE is selected, this WebLogic Server is theAdministration Server for the domain in which it resides. Only oneserver acts in this capacity. In the event that you register a server as theAdministration Server and then register a second server in the samedomain as the Administration Server, the original AdministrationServer is no longer the Administration Server for that domain. Only thelast WebLogic Server that is configured or registered as anAdministration Server has that status for a domain.



Discover the WebLogic Servers within a specific domain

ObjectiveTo discover the WebLogic Servers within a specific domain.


Required authorization roleweblogic_super

Before you beginAt least one WebLogic Server (preferably the WebLogic Administration Server)must be manually registered within the WebLogic Domain before you can discoverWebLogic objects.

There are several required server properties that an automated discovery processmight not be able to determine. The shell script generated by the discovery processis prefaced with several default variables that you must correct. For example, if thefile system locations of the java classes that provide the weblogic.jar file are storedin the ClassPath attribute of the ServerStart section of the WebLogic Serverconfig.xml file the WebLogic Server will run. If this section is missing from theconfig.xml file or the ClassPath attribute is not set, then the discovery processcannot determine the location of the weblogic.jar file.


It is possible for the values of the discovered properties to be set incorrectly. Youmust edit the script generated by the discovery process before executing the script.

When you finishNone

ProcedureYou can perform this procedure as a task or from the Tivoli desktop.

Task: Use the wruntask command to use the discover_ weblogic_servers task. SeeChapter 7, “Working with tasks and jobs” on page 63 for information aboutrunning tasks.



2. Right-click the WebLogic Domain that contains the objects you want to workwith and select Discover Servers to begin a read-only examination of allWebLogic Server resources known by the WebLogic Administration Server forthe current WebLogic Domain.

Figure 5. The Discover Servers window


Starting, stopping, or killing a server

ObjectiveTo start, stop, or kill a WebLogic Server.“Starting, stopping, or killing a server”

Background informationIf a WebLogic Server is down, any web applications hosted by that server are alsodown.


Before you beginTo start a server, you first must edit a script. The Start Server command (that canbe a script) specified when you create a WebLogic Server object must be anexisting file on the endpoint. It must include properly set environment variablesand code to start the WebLogic JVM. The Start Server script can be a ″wrapper″script that you write that initializes the environment and then invokes an existingscript (for example, one that has been externally provided by a vendor).Alternatively, you can specify an externally provided script as the Start Serverscript. However, you might want to customize this script to recognize environmentvariables that are passed from the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server environment. For example, if a vendor-provided script has ahard-coded password and you want to remove this from the provided script, youcan modify the script to use the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server environment variable ″WLS_SystemPassword″ instead of thehard-coded value.

Note: If you intend to use an externally provided script that expects the currentworking directory to be already set, then a ″wrapper″ script that you writeis required to set the current working directory properly. For example, someof the sample servers from BEA include start scripts that expect the currentworking directory to be the same as where the script itself is located. So,your wrapper script must cd into that directory.


Several environment variables are predefined for the script during invocation. Theyinclude the following:

WLS_DomainNameThe name for the domain in which the WebLogic Server is contained.

WLS_ServerNameThe name of the WebLogic Server.

WLS_ListenAddressThe IP address the WebLogic Server listens on.

WLS_ListenPortThe port the WebLogic Server listens on.

WLS_AdminHostThe IP address or hostname the domain administration server listens on.

WLS_AdminPortThe port the domain administration server listens on.

WLS_SystemUserA user in the WebLogic Domain with startup privileges.

WLS_SystemPasswordThe cleartext password of the above user.

WLS_RootDirectoryThe root directory of the WebLogic installation on the given endpoint. InWebLogic Server 6.1, this must be the current directory during startup. Thestartup script should change to this directory before Java is invoked.

WLS_LogFileThe path and name of the log file for the given WebLogic Server. If arelative path is used, then it is relative to the value of WLS_RootDirectory.

WLS_IsAdminServerSet to TRUE if the server being started is the administration server for thedomain.

WLS_JreDirectoryThe root directory of a valid JRE installation. Use${WLS_JreDirectory}/bin/java in a POSIX shell to invoke Java. Use%WLS_JreDirectory%\bin\java in a Windows command shell.

WLS_ClassPathA Java classpath that contains the weblogic.jar file.

ADMIN_URLDefined as http://{WLS_AdminHost}:${WLS_AdminPort}. Provided forcompatibility with prior WebLogic startup scripts.

SERVER_NAMESame as WLS_ServerName. Provided for compatibility with olderWebLogic startup scripts.

The following script typically initializes environment variables and changesdirectories to invoke a BEA-supplied startup script:## fail if any command fails or if undefined variable usedset -eu

BEA_7_0_DIR=/data/bea_7.0.1LOGFILE=/data/bvt/myStartPetstore7.logdate >>$LOGFILE


echo "Starting WebLogic Server..." >>$LOGFILE

## change directory to where config.xml is locatedcd $BEA_7_0_DIR/weblogic700/samples/server/config/petstore

## launch petstore script/bin/sh startPetStore.sh petstore; rc=$?

echo "rc($rc)" >>$LOGFILEdate >>$LOGFILEecho "startPetStore returned." >>$LOGFILEecho >>$LOGFILE

When you finishNone

ProcedureYou can perform this procedure from the command line, as a task, or from theTivoli desktop.

Command line: Use the wweblogic -StartServer command to start a WebLogicServer. Use the wweblogic -StopServer command to stop a WebLogic Server. Usethe wweblogic -KillServer command to kill a WebLogic Server. For the CLI syntaxfor these commands, see the IBM Tivoli Monitoring for Web Infrastructure ReferenceGuide.

Task: Use the wruntask command to use either the start_ weblogic_server task,the stop_ weblogic_server task, or the kill_weblogic_server task. See Chapter 7,“Working with tasks and jobs” on page 63 for information about running tasks.

Tivoli desktop: Use the following steps to run this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the policy region that contains the server



3. Right-click the WebLogic Server and click Start Server, Stop Server, or KillServer to start, stop, or kill the server.

Validate a WebLogic Server

ObjectiveTo validate a WebLogic Server.

Background informationWEAK validation checks the information provided during the registration andconfiguration processes to ensure it matches a server’s installation on a file system.For example, it makes sure that the value provided for JreDirectory is a real filesystem directory with bin/java in it. STRONG validation ensures that the specifiedserver is manageable by attempting to open a connection to it. STRONG validationfails if the server is not currently running. STRONG validation includes WEAKvalidation.




When you finishNone

ProcedureYou can perform this procedure from the command line, as a task, or from theTivoli desktop.

Command line: Use the wweblogic -ValidateServer command to validate aWebLogic Server. For the CLI syntax for these commands, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Task: Use the wruntask command to use the validate_ weblogic_server task. SeeChapter 7, “Working with tasks and jobs” on page 63 for information aboutrunning tasks.

Tivoli desktop: Use the following steps to run this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the policy region that contains the server



3. Right-click the WebLogic Server and click Validate.


Chapter 7. Working with tasks and jobs

This chapter provides information about using tasks and jobs to manage yourWebLogic Server resources.

Table 7 shows the options to manage tasks and jobs.

Table 7. Working with tasks and jobs

Goal Refer to

Run a task to perform a specific operation. “Running a task” on page 63

Define a standard task with specific arguments to customize thetask.

“Customizing a task” on page 66

Create a job from a task so that it can be scheduled to run. “Creating a job” on page 67

Run a job with predefined arguments. “Running a job” on page 69

Schedule jobs to run at specified times. “Scheduling a job” on page 70

The installation process installs the task library in the product policy region. Donot remove the task library from this policy region. The task library containsdefault policies that affect how the task library works.

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

Running a task

ObjectiveTo run one of the standard tasks in the task library.

Background informationA task is an action that must be routinely performed on selected endpoints ormanaged nodes throughout the network. A task defines the executables to be run,the authorization role required to execute the task, and the user or group nameunder which the task is run. IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server provides standard tasks in a task library. Standard tasks run onany system without consideration of platform type.

Required authorization rolesSee the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for theauthorization role required for each task.


When you finishNone


63

Command Line: Use the wruntask command to run a task. See the IBM TivoliMonitoring for Web Infrastructure Reference Guide for information about runningtasks from the command line.

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

Tivoli desktop:

1. Open the task library window by performing the following steps:a. Open the Tivoli desktop.b. Double-click the Monitoring for WebLogic Server policy region icon to

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

window.2. Double-click the task icon that you want to run to open the Execute Task

window.Additional information: The Execute Task window is a generic window thatcontains execution parameters for all tasks.

3. Select one of the following check boxes in the Execution Mode group box:

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

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

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

4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional information: The Timeout value does not stop the task. This valuespecifies the number of seconds the Tivoli desktop waits for the task tocomplete before it issues an error. The task continues to execute on theendpoint without displaying the output results. Setting an early timeoutenables your Tivoli desktop to become available again if the task takes a longtime to execute. The default is 60 seconds. If the task takes longer to completethan the specified Timeout and is running in Serial or Staged mode, theproduct moves on to other endpoints after this time expires.

5. Optional: If you selected Staged in Step 3, specify the number of endpoints toinclude in each staged set in the Staging Count text box and the number ofseconds between each set’s startup time in the Staging Interval text box.

6. Select one or more of the following check boxes in the Output Format dialogto choose the output returned upon task completion:

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

Return CodeIncludes the programming codes produced when the task executes.

Standard ErrorIncludes all error messages encountered when the task executes.


Standard OutputIncludes all information that results from the task execution.

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

desktop.Additional information: If you choose Display on Desktop, you have theoption, inside the output display window, of saving the information to afile.

v Click Save to File to save the output to a file.a. Type the name of the endpoint on which to save the output in the On

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

b. Type the absolute path name for the output file in the Output File textbox.Additional information: Example: /tmp/mytask.out

c. Click Set & Close to set your choices and return to the Execute Taskwindow.

8. Choose the endpoints on which you want to run the task by doing one of thefollowing:v Run the task on specific endpoints by doing the following:

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

Selected Task Endpoints list.

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

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

Selected Profile Managers list.9. Click Execute or Execute and Dismiss. If the task requires additional input

parameters, the task argument window is displayed. Otherwise, the taskexecutes.

Chapter 7. Working with tasks and jobs 65

Additional information: For information about how to fill in the task argumentdialog, refer to the task description in the IBM Tivoli Monitoring for WebInfrastructure Reference Guide or click Task Description to display the onlinehelp.

10. Click Set & Execute to run the task.

Customizing a task

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

Note: You can only customize tasks that use additional arguments.

Background informationA customized task is a standard task with defined arguments saved in the tasklibrary with a unique name. For example, you can customize a task to save taskoutput results to a file after each execution. Because you can customize taskarguments, the Tivoli environment does not display argument dialogs when yourun the task from the Tivoli desktop. However, if you run a customized task fromthe command line, you still must specify the task arguments. Running acustomized task requires additional information before it runs, such as the target ofthe task.

Required authorization rolesweblogic_admin


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

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

Figure 6. Example of a task argument window


a. Open the Tivoli desktop.b. Double-click the Monitoring for WebLogic Server policy region icon to


window.2. Double-click a task icon to open the Execute Task window for that task.3. Click Execute to open the task argument window.4. Enter the appropriate values for this customized task.

Additional information: For information about each field in these windows, seethe task description in the IBM Tivoli Monitoring for Web Infrastructure ReferenceGuide or click Task Description to display the online help.

5. Click Save to open the Save Argument window.6. Type the following information to define the customized task:

a. Type a name for the task in the Name text box.Additional information: This name is displayed in the Library Contents fieldso you can view the customized tasks that are based on the parent task.

b. Type an identifier for this task.Additional information: An identifier is the name of the task icon that isdisplayed in the Task Library window. A customized task identifier hastwo parts. Use the standard task name in the first part. Use descriptiveinformation that makes sense to you in the second.The software generates a unique default name if no identifier is entered.To enable filtering for an identifier without the standard task name, editthe tl_def_man_nodes policy method in the task library policy object. Seethe Tivoli Framework Reference Manual for more information.

c. Type a description of this task in the Description text box.Additional information: This description is displayed when you click TaskDescription in the task argument window for this customized task.

d. Optional: Select Show by Identifier to change the Library Contents list touse the task identifier instead of the task name.

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

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

Creating a job

ObjectiveTo create a job by defining execution parameters so you can specify a target thatenables you to schedule it to run at certain times in the Scheduler.

Background informationA job is a task with defined and saved arguments that can be executed many timeson specific managed resources. You can create jobs from both standard andcustomized tasks in the product task library. Like tasks, you store jobs in tasklibraries so you can reuse them.




When you finishAfter you create a job, you can run it immediately using the procedure describedin “Running a job” on page 69. You also can schedule jobs to run at certain timesin the Scheduler, as described in “Scheduling a job” on page 70.


Command Line: Use the wcrtjob command to create jobs from the command line.See the Tivoli Management Framework Reference Manual for information about thewcrtjob command.

Tivoli desktop:



window.2. Click Create to display the Create drop-down menu.3. Select Job from the Create drop-down menu to open the Create Job window.4. Type a descriptive job name in the Job Name text box.

Additional information: The job name identifies the icon on the Tivoli desktop.The name can include any alphanumeric character, an underscore (_), dash (–),period (.), or a blank space.

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

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

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

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

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

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


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

HeaderIncludes a descriptive header for each record.

Return CodeIncludes the programming codes produced when the job executes.

Standard ErrorIncludes all error messages encountered when the job executes.

Standard OutputIncludes all information that results from the job execution.

10. Do one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Tivoli desktop to display the job output on the Tivoli

desktop. Go to Step 12.Additional information: If you choose Display to Desktop, you have anoption, inside the output display window, to save the information to a file.—OR—

v Click Save to File to save the output to a file and open the Destination forTask Output window. Go to Step 11.

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

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

box.Additional information: Example: /tmp/myjob.out

c. Click Set & Close to set your choices and return to the Create Job window.12. Do one of the following to choose the endpoints on which to run the job:

v Run the job on specific endpoints by doing the following:a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the

Selected Task Endpoints list.–OR–

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

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

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

Running a job

ObjectiveTo run a job on specific endpoints immediately so you can perform a managementoperation.


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

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


Before you beginBefore you can run a job, you must create it, as described in “Creating a job” onpage 67.

When you finishAfter you create a job, you can set it up to run on a regular schedule as describedin “Scheduling a job” on page 70.


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

Tivoli desktop:


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

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

the job.–OR–

v Double-click the job icon created from a standard task. Go to Step 3.3. Type the values in the task window.

Additional information: For information about specific fields, see the taskdescription in the IBM Tivoli Monitoring for Web Infrastructure Reference Guide orclick Task Description to display the online help. The job runs and displays theoutput on the Tivoli desktop or sends it to a file based on the job specification.

Scheduling a job

ObjectiveTo schedule jobs to occur regularly so you can routinely perform managementoperations.

Background informationThe product uses Scheduler to schedule jobs. Scheduler is a service that enablesyou to run jobs unattended. You can schedule a job to run one time or multipletimes. Scheduler notifies you by the manner you select when a job is complete.



Before you beginTo schedule a job, the job must exist in the task library. You create a job byfollowing the procedure described in “Creating a job” on page 67.

When you finishNone


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

Tivoli desktop:



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

in the Tivoli Desktop for Administrator <root_admin_name> window on theTivoli desktop.

3. Optional: Do the following if a task argument window opens:a. Type the appropriate information for each field in the dialog.

Additional information: Refer to the task description in the IBM TivoliMonitoring for Web Infrastructure Reference Guide or click Task Descriptionto display the online help for this task.

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

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

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

—OR—v Clear Disable the Job to continue running a scheduled job.

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

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

7. Set the date and time to begin scheduling in the Schedule Job For group box:a. Type a date in the Month, Day, and Year text boxes.


b. Enter the time using the Hour and Minute drop-down lists and the AMand PM radio buttons.

8. Optional: Repeat the job by doing the following in the Repeat the Job groupbox:a. Do one of the following:

v Select Repeat the job indefinitely to repeat the job indefinitely.–OR–

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

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

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

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

window.

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

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

box.v Send an e-mail to a specified user by doing the following:

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

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

– Type the file destination in the Host and File text boxes. The hostmust be a Tivoli client endpoint and the file must be a fully qualifiedpath name. For example: /tmp/mytask.out–OR–

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

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

window.10. Optional: Set retry, cancel, or restriction options by doing the following:

a. Click Set Retry/Cancel/Restriction Options to open the Set Retry/CancelRestrictions Options window.

b. Choose one of the following cancel job options:


v Clear Cancel job to have the Scheduler continue trying the jobindefinitely.—OR—

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

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

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

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

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

specify the job run times:

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

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

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

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

e. Click Set to set the options and return to the Add Scheduled Job window.11. Click Schedule Job & Close to schedule the job and return to the Tivoli

desktop.


Chapter 8. Enabling Tivoli Enterprise Data Warehouse

This chapter provides information on enabling IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server for Tivoli Enterprise Data Warehouse.

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

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

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

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

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

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

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

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

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

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

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

75

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

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

Warehouse.

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

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

v The warehouse agent, part of DB2 Warehouse Manager.

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

Data martsA separate DB2 database contains the data marts for your enterprise. Each datamart contains a subset of the historical data from the central data warehouse tosatisfy the analysis and reporting needs of a specific department, team, customer,or application. The system that hosts this DB2 database is called the data martserver. Although you can have many data marts, you can have only one data martserver.

The data mart component requires IBM DB2 Universal Database EnterpriseEdition, which you must install manually before installing the control server.

The warehouse pack for IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer creates data marts whose structure is suitable for the report interface. Theydo this by providing an extract, transform, and load (ETL) process, called a datamart ETL, that creates the data mart and loads it with data from the central datawarehouse.

You can modify an existing data mart, or create new data marts that containslightly different data, to address a reporting need specific to your situation. Tomodify or create a data mart, you must be familiar with database ETL processesand with the internal representation of a data mart as star schemas in the TivoliEnterprise Data Warehouse databases. For information about this, see Enabling anApplication for Tivoli Enterprise Data Warehouse.

Report interfaceThe Tivoli Enterprise Data Warehouse report interface (RPI) provides tools and agraphical user interface that other Tivoli software products use to create anddisplay reports. You can use Tivoli Enterprise Data Warehouse to customize reports


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

Use the Work with Reports task group in the report interface to manage users,groups, and data marts for Tivoli Enterprise Data Warehouse or to run, create, andview Tivoli Enterprise Data Warehouse reports.

Working with users and user groupsThis section describes tasks associated with managing user groups for TivoliEnterprise Data Warehouse. It includes the following topics:

Table 8. Guidelines for working with Tivoli Enterprise Data Warehouse users and usergroups


Understand users and user groups. “About users and user groups”

Understand Tivoli Enterprise DataWarehouse roles.

“The Tivoli Enterprise Data Warehouseroles”

Create an IBM Console user. “Creating an IBM Console user” on page 78

Assign roles to a user. “Assigning roles to a user” on page 78

Create a user group. “Creating a user group” on page 79

Assign users to a user group. “Assigning users to a user group” onpage 79

Assign a user group to a data mart. “Assigning user groups to a data mart” onpage 80

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

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

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

The Tivoli Enterprise Data Warehouse rolesThe following Tivoli Enterprise Data Warehouse roles control access to tasks andactivities:v Warehouse Security Administrator

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

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

Chapter 8. Enabling Tivoli Enterprise Data Warehouse 77

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

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

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

Creating an IBM Console user

ObjectiveTo create an IBM Console user.

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

Required authorization rolesuperadmin


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

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

to create a user.

Assigning roles to a user

ObjectiveTo assign roles to a user.


Required authorization rolesuperuser



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

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

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

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

Creating a user group

ObjectiveTo create a user group.


Required authorization roleAdministration Authorizations


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

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

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

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

Assigning users to a user group

ObjectiveTo assign users to user groups.





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

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

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

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

groups.

Assigning user groups to a data mart

ObjectiveTo assign user groups to a data mart.

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



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

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

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

menu icon for the data mart that you want to change and click Properties.3. Select the User Groups tab.4. Open the Task Assistant and follow the instructions provided in the online help

to assign a user group to a data mart.

Managing Tivoli Enterprise Data Warehouse reportsTivoli Enterprise Data Warehouse reports display a static view of the data in a datamart. Reports are provided by the warehouse pack for IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server, along with the data marts required to collectthe data used in the report.

Tivoli Enterprise Data Warehouse provides three types of reports, which contain astatic view of your data:


Extreme caseAn extreme case report is a ″one measurement versus many components orgroups of components″ report that displays the worst or best n cases. Thisreport displays a maximum of 25 cases.

Health checkA health check report displays status and performance for a specifiedmeasurement over a period of time. The data in a health check report isaggregated at the application server level.

SummaryA summary report displays the overall status of the resource models. Thedata in a summary report is aggregated at the application server level andis grouped by operating system, node, and application server.

This section describes the following tasks:

Table 9. Guidelines for working with Tivoli Enterprise Data Warehouse reports


Run a report “Running reports” on page 83

Schedule a report to run automatically “Scheduling reports to run automatically” onpage 84

Modify the default settings of a report “Modifying default settings for reports” onpage 85

Create a custom report “Creating reports” on page 86

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

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

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

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

For information about any problems that might occur, see the ″Troubleshooting″chapter in the Installing and Configuring Tivoli Enterprise Data Warehouse, Version 1,Release 1.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverstar schemas, data marts, and reports

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server contains thefollowing Tivoli Enterprise Data Warehouse star schemas, data marts, and reports.


For detailed information on the specific data mart, star schema, and reportmapping of IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server, see theIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server Warehouse EnablementPack Implementation Guide located in the doc directory of IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server Installation CD.

Star schemasstar schema is a set of three or more data tables.

IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides thefollowing star schemas:v GWL Server Hourly Star Schemav GWL Server Daily Star Schemav GWL Server Weekly Star Schemav GWL Server Monthly Star Schemav GWL JDBC Connection Pool Hourly Star Schemav GWL JDBC Connection Pool Daily Star Schemav GWL JDBC Connection Pool Weekly Star Schemav GWL JDBC Connection Pool Monthly Star Schemav GWL JMS Server Hourly Star Schemav GWL JMS Server Daily Star Schemav GWL JMS Server Weekly Star Schemav GWL JMS Server Monthly Star Schemav GWL Execute Queue Hourly Star Schemav GWL Execute Queue Daily Star Schemav GWL Execute Queue Weekly Star Schemav GWL Execute Queue Monthly Star Schemav GWL JTA Hourly Star Schemav GWL JTA Daily Star Schemav GWL JTA Weekly Star Schemav GWL JTA Monthly Star Schemav GWL JVM Hourly Star Schemav GWL JVM Daily Star Schemav GWL JVM Weekly Star Schemav GWL JVM Monthly Star Schemav GWL JMS Destination Hourly Star Schemav GWL JMS Destination Daily Star Schemav GWL JMS Destination Weekly Star Schemav GWL JMS Destination Monthly Star Schemav GWL JMS Server Hourly Star Schemav GWL JMS Server Daily Star Schemav GWL JMS Server Weekly Star Schemav GWL JMS Server Monthly Star Schemav GWL Connector Component Hourly Star Schemav GWL Connector Component Daily Star Schemav GWL Connector Component Weekly Star Schemav GWL Connector Component Monthly Star Schema


v GWL Web Application Component Hourly Star Schemav GWL Web Application Component Daily Star Schemav GWL Web Application Component Weekly Star Schemav GWL Web Application Component Monthly Star Schemav GWL EJB Hourly Star Schemav GWL EJB Daily Star Schemav GWL EJB Weekly Star Schemav GWL EJB Monthly Star Schemav GWL Servlet Hourly Star Schemav GWL Servlet Daily Star Schemav GWL Servlet Weekly Star Schemav GWL Servlet Monthly Star Schema

Data marts and reportsThis warehouse pack provides one data mart: WebLogic Datamart.

GWL Monitoring for WebLogic Server provides the following prepackaged reports:

WebLogic Server Availability ( Daily) - ECThis extreme case report shows the 25 worst case WebLogic Server in termsof their average percentage of time that the WebLogic Server is up andrunning for the specified time period.

WebLogic JDBC Connection Pool Statistics (Daily) - SMThis summary report lists the average rate of leaked connections and theaverage of requesters waiting for a connection for all database pools andall WebLogic servers for the specified time period.

WebLogic EJB Transactions (Daily) - HCThis health check report examines the trends of EJB Transactions in termsof average percentage of transactions timed out and average number oftransactions committed and attempted per cycle across all WebLogicEnterprise Server Beans for all WebLogic servers in the specified timeperiod.

WebLogic Servlet Performance (Daily) - ECThis extreme case report shows the 25 busiest WebLogic Servlets in termsof invocation for the specified time period.

WebLogic JMS Load ( Daily) - ECThis extreme case report shows the 25 worst case WebLogic Server JavaMessaging Services order by destination type in terms of messagesthroughput for the specified time period.

Running reports

ObjectiveTo run a report using the report interface.


Required authorization roleAdvRepAuthRole, RepAuthRole, or RepReaderRole



When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as displaying the properties of a report,modifying the settings, and deleting a report. Also see “Modifying default settingsfor reports” on page 85 for information about customizing the reports.

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

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

the context menu icon of a report and select Run.3. For more information about running reports, see the online help in the Task

Assistant. The online help can also help guide you through additional tasks forreports, such as displaying the properties of a report and deleting a report.

Scheduling reports to run automatically

ObjectiveTo automatically run reports.

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

Required authorization roleAdvRepAuthRole


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

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

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

Reports.3. Click the context menu icon of a report and select Properties.4. Select the Schedule tab.5. In the Schedule window, select Run the report when the data mart is built.6. Click OK.

For more information about automatically running reports, see the online help inthe Task Assistant. The online help can also guide you through additional tasksfor reports, such as modifying or displaying the properties of a report and deletinga report.


Modifying default settings for reports

ObjectiveTo modify default settings for report creation.

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

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

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

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

Table 10. Default time filter names and values

TIME_FILTER_NAME TIME_FILTER_VALUES

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

Weekdays dayofweek(meas_date) between 2 and 6

Required authorization roleAdvRepAuthRole


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

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

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

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

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

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


Creating reports

ObjectiveTo create a report.


Required authorization roleAdvRepAuthRole or RepAuthRole

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

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

ProcedureYou can perform this procedure from the IBM Console.1. Click Work with Reports and select Create a Report.2. Select one of the following type of reports to create: Extreme Case, Health

Check, and Summary.3. Select the data mart that contains the information from which to create the

report.4. Click OK.5. Click the General tab and enter the Name and Description for the report.6. Click the Metrics tab, and select Add to add a new metric to graph and

display the Add Metrics screen.7. Select the star schema containing the metric that you would like to graph and

to display a list of available metrics for the star schema.8. Check one or more of the metrics that you want to graph.9. Click Next.

10. Select the aggregation type that you want for each metric.11. Click Next.12. Specify the attributes to filter by, group by, or order by.13. Click the Time tab, and specify the Time frame for which you want to run the

report.Additional information: You can specify a General Time Frame, such as the Last7 days, or a Specific Time Interval, such as January 1, 2002 through January31, 2002.

14. Click the Schedule tab, and select whether the report is run when the datamart is built.

15. Click OK.


Appendix A. Task and command authorization roles quickreference

Table 11 lists the minimum required authorization roles for the WebLogic Servertasks. For information about these authorization roles, see “Setting authorizationroles” on page 11.

Table 11. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server task authorizationroles

Task name Minimum authorization role

WebLogic_Configure_TEC weblogic_senior or weblogic_super

WebLogic_Send_Files_To_TEC weblogic_senior or weblogic_super

kill_weblogic_server weblogic_super

start_weblogic_server weblogic_super

stop_weblogic_server weblogic_super

TBSM_discovery_webLogic weblogic_senior or weblogic_super

validate_weblogic_server weblogic_super

Table 12 lists the minimum required authorization roles for the commands.

Table 12. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server commandauthorization roles

Task name Minimum authorization role

wweblogic –ListDomains weblogic_admin, weblogic_super

wweblogic –RegisterDomain weblogic_admin, weblogic_super

wweblogic –UnregisterDomain weblogic_admin, weblogic_super

wweblogic –ConfigureDomain weblogic_admin, weblogic_super

wweblogic –ListServers weblogic_admin, weblogic_super

wweblogic –RegisterServer weblogic_admin, weblogic_super

wweblogic –UnregisterServer weblogic_admin, weblogic_super

wweblogic –ValidateServer weblogic_admin, weblogic_super

wweblogic –ConfigureServer weblogic_admin, weblogic_super

wweblogic –StartServer weblogic_admin, weblogic_super

wweblogic –StopServer weblogic_admin, weblogic_super

wweblogic –KillServer weblogic_admin, weblogic_super

wweblogic –ShowServerAttributes weblogic_admin, weblogic_super

wweblogic –ShowDomainAttributes weblogic_admin, weblogic_super

87

Appendix B. Task quick reference

A task is an operation or set of operations that is performed routinely. Thefollowing table lists the IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer tasks alphabetically. For more information about these tasks, see the IBMTivoli Monitoring for Web Infrastructure Reference Guide.

The IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server tasks includethe following:

Table 13. IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server tasks

Task name Description

discover_weblogic_servers Discovers the WebLogic Servers within a specificdomain.

kill_weblogic_server Kills the WebLogic Server.

start_weblogic_server Starts the WebLogic Server.

stop_weblogic_server Stops the WebLogic Server.

validate_weblogic_server Validates the WebLogic Server.

WebLogic_Configure_TEC Clones the Tivoli Enterprise Console rule basebased on the one specified, imports the WebLogicbaroc files and rules, imports the Tivoli BusinessSystems Manager rules, compiles the rule base,and loads the rule base, stopping and restartingthe Tivoli Enterprise Console server if requested.

WebLogic_Send_Files_To_TEC Sends files to Tivoli Enterprise Console.

WebLogic_TBSM_Discovery Sends a DISCOVER event to Tivoli BusinessSystem Manager for each WebLogic Server thatIBM Tivoli Monitoring for Web Infrastructure:WebLogic Server is currently managing. For anyresources that were removed since the last timethis task was run, this task sends a GONE eventto Tivoli Business System Manager.

89

Appendix C. Setting up IBM Tivoli Monitoring

During installation, IBM Tivoli Monitoring for Web Infrastructure: WebLogic Serverperforms several tasks that help set up your IBM Tivoli Monitoring environment,including creating profile managers, adding resources to the profiles, and addingresource models to profiles. The WebLogic Monitoring profile manager is createdduring installation. This appendix provides procedures to create additional profilemanagers or customize the resources and resource models assigned to your profilemanager.

Table 14 provides guidelines for the order in which you set up monitoringinformation and the required procedures for setting up IBM Tivoli Monitoring.

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

Table 14. Monitoring resources and applications guidelines

Goal See

Set up profile managers and profiles to organize yourresource models. This makes the distribution ofresource models more efficient. You might need to setup multiple profile managers and profiles within theprofile managers to meet the needs of yourenvironment.

“Creating profile managers andprofiles” on page 92

Subscribe endpoints to the profile manager. Thisdetermines which resources receive a profile when theprofile is distributed. Profiles contain resource modelsto run against the endpoints.

“Subscribing resources to profilemanagers” on page 93

Populate each profile manager/profile with resourcemodels for the resource that you want to monitor.Include resource models with the default values orcustomize the default values to meet the needs ofyour environment.

“Adding default resource modelsto profiles” on page 94

“Adding customized resourcemodels to profiles” on page 95

For each resource model in your profile, do thefollowing:

v Determine how the resource model generates anevent by specifying thresholds, occurrences, andholes for each indication for that resource model.

v Specify if you want corrective or reporting tasks foran event.

v Specify if you want to receive information on aspecific event through a notice.

v Specify when the monitoring occurs.

v Specify if you want the collected log data written toa local database.

“Modifying indications” on page36

“Specifying tasks for an indication”on page 38

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

“Creating scheduling rules” onpage 41

“Modifying data logging settings”on page 43

For each profile in your profile manager, do thefollowing:

v Specify the subscribers that you want to distributethe monitoring profile to and distribute the profile.

v Specify the subscribers that you want to distributethe monitoring profile to while using MDist2.

“Distributing profiles from theTivoli desktop” on page 18

“Distributing profiles usingMDist2” on page 20

91

Creating profile managers and profiles

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

Background informationA monitoring profile is a group of defined resource models that you can distribute toa subscribed managed resource in a profile manager.

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

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

For more information about profile managers, including the different types (suchas dataless), see the Tivoli Management Framework documentation.


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

When you finishAdd resource models to the profile. See “Adding default resource models toprofiles” on page 94 or “Adding customized resource models to profiles” onpage 95.


Command Line:

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

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

where:

-d Specifies that the profile manager operates in a dataless mode.


3. Use the wcrtprf command to create a profile. For example, to create a profilecalled ″MarketingProf2″ in the ProfMgr2 profile manager, enter the followingcommand:wcrtprf @ProfileManager:ProfMgr2 MarketingProfile MarketingProf2

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

Tivoli desktop:

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

2. Select Create → Profile Manager to open the Create Profile Manager window.3. Type a unique name in the Name/Icon Label text box.4. Click Create & Close.5. Double-click the profile manager icon to open the Profile Manager window.6. Select Create → Profile to open the Create Profile window.7. Type a unique name for the profile in the Name/Icon text box.8. Select the Tmw2kProfile resource from the Type list.9. Click Create & Close. An icon for the new profile is displayed in the Profiles

area of the Profile Manager window.

Subscribing resources to profile managers

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

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

Note: Resources can also be subscribed to profiles from the IBM Tivoli MonitoringProfile window. See “Distributing profiles from the Tivoli desktop” onpage 18.


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

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


Appendix C. Setting up IBM Tivoli Monitoring 93

Command Line: Use the wsub command to add subscribers to the profilemanager. For example, to add a database called ″Sample@bburns″ as a subscriberto the profile manager DatabaseMonitors, enter the following command:wsub @ProfileManager:DatabaseMonitors @PolicyRegionName:Sample@bburns

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

Tivoli desktop:

1. Open the Policy Region window.2. Double-click a profile manager icon to open the Profile Manager window.3. Select Profile Manager → Subscribers.4. Select the subscribers to receive the profile distribution from the Available to

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

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

displayed in the Subscribers field of the Profile Manager window.

Adding default resource models to profiles

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

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

Put all the resource models that you are going to distribute to the same endpointin a single profile because the distribution occurs on a per-profile basis.




managers” on page 93 for information.

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


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile. For more information, see the IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebLogic Server Reference Guide.


Desktop:

1. Open the IBM Tivoli Monitoring Profile window.2. Click Add With Defaults to open the Add Resource Models to Profile

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

Profile.

Adding customized resource models to profiles

ObjectiveTo add a resource model with customized settings so that administrators and userscan specify the relevant type of platform, cycle time, and threshold values thatmeet the needs of your environment and add the resource model to a profile.

Background informationResource models are set up and distributed to WebLogic Server objects. In additionto using the predefined resource models that are installed with the product, youcan customize the predefined resource models. Each resource model monitors adifferent resource. Choose the resource models that you want to customize and thesetting you want to use to monitor those resources.




managers” on page 93 for information.

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


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile. For more information, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Tivoli desktop:

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

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

a. Select the Threshold Name that you want to change.


Additional Information: The description box displays a description of thethreshold that you selected. A dialog box above the description displays thecurrently assigned threshold value. For the default threshold values, see theIBM Tivoli Monitoring for Web Infrastructure Reference Guide.

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

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

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

8. Click Add & Close to save your changes. The IBM Tivoli Monitoring Profilewindow now shows the customized resource model.

Rerunning failed profile distributions

ObjectiveTo verify that the distribution to an endpoint failed so that you can rerun thedistribution for the failed endpoint.

Background informationWhen a distribution fails, IBM Tivoli Monitoring creates a profile manager thatcontains the endpoint subscribers that failed.

When you successfully redistribute profiles, the software deletes the profilemanager that it created for the failed distribution. A wholly or partiallyunsuccessful redistribution retains the profile manager containing only thesubscribers that were unsuccessful in the redistribution. Continue correcting theerrors and retrying the distribution until the profile is successfully distributed to allendpoints.



When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.

Tivoli desktop:

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

2. Select View → Refresh from the Policy Region dialog box to see the new profilemanagers.


3. Review the new profile manager names to determine and correct the cause ofthe failure. The following profile manager names are derived from a faileddistribution:v The failed distribution creates the following profile manager name due to a

Bad_Interpreter error:OriginalProfileName_Push_Failed_Bad_Interpreter

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

The AMW089E error message is displayed at this point, indicatingthat the resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX-T endpoint.

v The failed distribution creates the following profile manager name due toany other error:OriginalProfileName_Distribution_Failed

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

4. Subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile.

Note: This can be done only if the profile manager used for the originaldistribution was not a dataless endpoint.

5. Distribute the original profile to the failed endpoints by selecting these profilemanagers as the target for the distribution. You can also edit the profilemanagers to delete an endpoint from a group of failed endpoints beforeretrying the distribution.


Appendix D. Creating custom resource models

This section describes how you can use the Resource Model Wizard to create yourown resource models using the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server common information model (CIM) classes. Refer to the IBM TivoliMonitoring Workbench documentation for more information on how to createresource models.

For information about the IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer CIM classes, see the IBM Tivoli Monitoring for Web Infrastructure ReferenceGuide.

The following topics are discussed in this section:

Table 15. Guidelines for creating custom resource models


Create a custom resource model that usesthe IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server CIM classes.

“Creating custom resource models using theIBM Tivoli Monitoring Workbench”

Creating custom resource models using the IBM Tivoli MonitoringWorkbench

ObjectiveTo create customized resource models in the IBM Tivoli Monitoring Workbenchusing IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server CIM classesand use the Resource Model Wizard to guide you through the process.

Background informationThe IBM Tivoli Monitoring Workbench is a programming tool for creating,modifying, debugging, and packaging resource models for use with IBM TivoliMonitoring products. Samples of the ″best practice″ resource models have beenprovided for use within the IBM Tivoli Monitoring Workbench. The sampleresource models are intended as working examples for creating new resourcemodels. Also, you can use the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server ″best practice″ resource models as examples.

The Tivoli Maintenance and Support Contract covers assistance with problemsrelating to the operation of the IBM Tivoli Monitoring Workbench, but does notcover assistance for new or modified resource models other than the ones that areincluded in the IBM Tivoli Monitoring Workbench.

The Resource Model Wizard guides you through the process of creating resourcemodels using IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server CIMclasses. For information about the IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server CIM classes, see the IBM Tivoli Monitoring for Web InfrastructureReference Guide.

Refer to the IBM Tivoli Monitoring Workbench documentation for moreinformation on how to create resource models.

99


Before you beginBefore you begin, you must perform the following steps:1. Install and configure Windows Management Instrumentation.

Additional Information: You can download Windows ManagementInstrumentation (WMI) from http://msdn.microsoft.com/downloads/. WMI isalready installed on Windows 2000 systems.

2. Install and configure IBM Tivoli Monitoring Workbench.3. Load each CIM class you want to use.

Additional Information: Load the classes by running the mofcomp commandfrom the WORKBENCH/w32–ix86 directory on the IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server installation CD. For more informationabout the mofcomp command, refer to the Windows ManagementInstrumentation documentation.See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guidefor more information on loading these files.

When you finishRefer to IBM Tivoli Monitoring Workbench documentation for instructions on howto build and deploy your new resource model. Resource models created to use theIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server CIM classes needto be distributed to the WebLogic Server objects.

Procedure1. From the IBM Tivoli Monitoring Workbench, click File → New.2. Select Java Script Resource Model and click OK.3. Select Resource Model Wizard and click OK.4. Select the CIM/WMI data source type.5. Select all of the available operating systems on which you want the resource

model to run.6. Click Next.7. Type ″root\CIMv2″ in the Connect to namespace field.

Additional Information: ″\root\CIMv2″ refers to the namespace in the classrepository that includes resource model information.

8. Optional: Type your password.9. Click OK to display the Select a Class window.

Additional Information: The Selected Class field displays all available CIMclasses for use in your custom resource models.

10. Select the CIM class properties to monitor from the Available Propertiesgroup box.

11. Select one or more CIM classes.Additional information: For information about the IBM Tivoli Monitoring forWeb Infrastructure: WebLogic Server CIM classes, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

12. Click Next.13. Follow the Resource Model Wizard instructions to complete your resource

model. See the IBM Tivoli Monitoring Workbench documentation for detailedinstructions.


http://msdn.microsoft.com/downloads/

14. After the wizard is complete, add the CIM classes as platform-specificdependencies to the resource model by doing the following:a. Open the IBM Tivoli Monitoring Workbench dialog box containing the

decision tree SCRIPT.b. In the tree on the left side of the window, click ″+″ to expand the tree list

for the newly created resource model.c. Click ″+″ to the left of Dependencies to expand the Dependencies tree.d. Right-click on a platform-specific dependency element to display the Add

pop-up menu.e. Click Add to display the Open dialog box.f. For the Look in field, scroll to select the IBM Tivoli Monitoring for Web

Infrastructure installation CD.g. Click one of the following directories for the operating system on which

the resource models will run:v Windows: Workbench/w32–ix86.

—OR—v Unix (including Linux-ix86, aix4–r1, HP–UX10, solaris2):

Workbench/UNIX.h. Select the appropriate .mof file and then click Open to add the classes to

the Dependencies folder.

Appendix D. Creating custom resource models 101

Appendix E. Event classes and rules

This appendix contains information about the Tivoli Enterprise Console eventclasses and rules that IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer provides. The following topics are discussed in this appendix:v “Event classes”v “Rules for resource models and events”

Event classesIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides the TivoliEnterprise Console event class, WebLogic_Event. Events for this class are generatedby the resource models.

Rules for resource models and eventsIBM Tivoli Monitoring for Web Infrastructure: WebLogic Server provides rules forevents generated by resource models. The rules are contained in theweblogic_to_TBSM.rls file. The rules and their functions are as follows:

close_events_matching_clearingCorrelates and closes the original status change event associated with thisclearing event.

forward_WebLogic_Event_to_tbsm_1Takes events the resource models generate and sends them to TivoliBusiness Services Manager.

forward_WebLogic_Event_to_tbsm_2Takes clearing events generated by IBM Tivoli Monitoring and sends themto Tivoli Business Services Manager.

103

Appendix F. Problem determination

This appendix provides information about resolving problems that might occurwhen you run IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server.Problems can be caused by the following things:v Machine or server availabilityv Operating system environmentv IBM Tivoli Monitoring for Web Infrastructure: WebLogic Server configuration

Possible problems and workaroundsThe following sections describe problems that might occur and provideworkarounds or fixes.

General problem determinationTable 16. General problems and solutions

Problem Solution

A clarification of how the Start Serverfunctionality works with the WebLogic startupscript installed on an endpoint.

1. On the endpoint, add the WebLogic server password to thevendor startup script by setting the WLS_PW variable, forexample, WLS_PW=%WLS_systempassword%.

2. Add the password to the WLS_PW variable.

3. Test the wrapper script to ensure that it is setup correctly. Foran example of a wrapper script, see “Starting, stopping, orkilling a server” on page 58.

4. On the managed node, configure the server object toreference the wrapper script.

The wdmeng -start command for an entireprofile fails on HP-UX endpoints

This command works for a single resource model. Start eachresource model separately using this command.

The winstall command always returns successeven if the command failed.

After the last script runs, you can access a .passed file in thewtemp directory. This file indicates if the winstall command wassuccessful.

When registering a server without configuringthe endpoint, you receive the following message:

FRWSL0024E A failure was detected by theoserv daemon: FRWOG0040E Transaction Error

First configure the endpoint, and then register the server.

Tivoli Enterprise Console problem determinationTable 17. Tivoli Enterprise Console problems and solutions

Problem Solution

None

105

Tivoli Enterprise Data Warehouse problem determinationTable 18. Tivoli Enterprise Data Warehouse problems and solutions

Problem Solution

No data in the reports.

In the case of summary reports, the report is empty.

This can occur in the following situations.

v Resource model logging is not enabled. See“Modifying data logging settings” on page 43 forinformation.

v You have not installed the IBM Tivoli Monitoring,Warehouse Enabling component and have notsuccessfully uploaded data to the middle layerdatabase. See the IBM Tivoli Monitoringdocumentation.

v You have not installed and run the IBM TivoliMonitoring Tivoli Enterprise Data Warehouse supporton the Tivoli management region server. See the IBMTivoli Monitoring for Web Infrastructure Installation andSetup Guide.

v You have not installed and run the IBM TivoliMonitoring for Web Infrastructure: WebLogic ServerWarehouse Enablement Pack processes. See IBM TivoliMonitoring for Web Infrastructure Installation and SetupGuide.

v You have not installed the IBM Tivoli Monitoringwarehouse enablement pack and run theAMX_ETL1_Process before installing the WebLogicServer warehouse enablement pack (GWL WEP). Ifyou ran the AMX_ETL1_Process before installing theGWL WEP, you need to reset some tables in theTWH_CDW database To do so, you can use the scriptslocated under the<TWH_TOPDIR>/amx/v511/misc/tools directory. Thereset.bat file resets the extract_control window for theIBM Tivoli Monitoring entries, deletes the permanentIBM Tivoli Monitoring tables in the central datawarehouse database and empties 4 tables in theTWH_CDW database. If you had data from a previouswarehouse enablement pack in the warehouse centraldatabase, comment the following statements beforerunning the script against the central data warehousedatabase:

– delete from TWG.COMPATTR

– delete from TWG.COMPRELN

– delete from TWG.MSMT

– delete from TWG.COMP

Once you run the reset.bat script, then you can rerun theAMX_ETL1_Process and then the GWL_ETL2_Process.


Table 18. Tivoli Enterprise Data Warehouse problems and solutions (continued)

Problem Solution

You see the following error in the TWHApp.log file:

(F) CDWIC0022E Failure detected duringSQL script executionfor Database(TWH_MART).Return code was (4)Check messages in DB2 log (twh_ibm_db2_runlog.log),Removing TMP script.Exiting...

And the following error in the twh_ibm_db2_runlog.logfile:

DECLARE global temporary TABLEPrune_Mart_Control( Table_Name VARCHAR(120) NOTDB21034E THe command was processed as anSQL statement because it was not a validCommand Line Processor command.During SQL processing it returned:SQL0286N A default table space could notbe found with a page size of at least "4096"that authorization ID "DB2" is authorizedto use. SQLSTATE=42727

If you install the Tivoli Enterprise Data Warehouse Packwith one user ID (such as ″db2admin″) and the IBMTivoli Monitoring 5.1.1 Warehouse Enablement or thiswarehouse enablement pack with another user ID (suchas ″db2″), you must create a temporary tablespace for thewarehouse enablement pack installation user.

To create a temporary tablespace, on the system that isthe Tivoli Enterprise Data Warehouse Control Server,open a DB2 command window and issue the followingcommands:

db2 connect to TWH_CDW user <userID> \using <password>

db2 create user temporary tablespace usertmp2 \managed by system using (’usertmp2’)db2 connect to TWH_MART user <userID> \using <password>db2 create user temporary tablespace usertmp3 \managed by system using (’usertmp3’)

where <userID> is the warehouse enablement pack installuser and <password> is the password of that user.

General errors occur while using Tivoli Enterprise DataWarehouse

See the ″Troubleshooting″ chapter in the Installing andConfiguring Tivoli Enterprise Data Warehouse, Version 1,Release 1 guide for more information.

Tasks problem determinationThe following table lists general task problems that might occur.

Table 19. Task problems and solutions

Problem Solution

A task fails. Ensure that you assigned the resource roles to theadministrator running the task. See “Settingauthorization roles” on page 11 for more information.After you assign the resource roles, immediately stopand start the Tivoli Desktop so the assigned roles takeeffect.

Resource models problem determinationTable 20. Resource model problems and solutions

Problem Solution

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

Tivoli Enterprise Console events are not generated when aresource model fails to start; they are generated when there is aproblem or change in a resource being monitored. Problems thatoccur with the resource model itself are reported in the IBMTivoli Monitoring Web Health Console.

Appendix F. Problem determination 107

Table 20. Resource model problems and solutions (continued)

Problem Solution

Changing the password of the WebLogicDomainobject will allow validation of theWebLogicServer to succeed, but the resourcemodels have not picked up the new passwords.If the resource models attempt to connect withthe wrong password, BEA WebLogic Server willlock their user account out from the system.

Change the password on the WebLogic Domain object from theTivoli Desktop, and then stop and restart all the resource modelsthat are running.

The IBM Tivoli Monitoring engine is notavailable.

Refer to the IBM Tivoli Monitoring documentation for additionalassistance.

For Windows endpoints:

1. Open the Task Manager to see if the m12javaprovider.exeprocess is running.

2. If it is not running:

a. From a command window on the Tivoli managementregion server, source the Tivoli environment, as describedin “Setting up the IBM Tivoli Monitoring environment” onpage 17.

b. Restart the engine by executing the following command:

wdmcmd -restart -e endpoint_name

where endpoint_name is the name of the endpoint.

3. If the m12javaprovider.exe is running, use the Task Managerto end the process manually and then restart the engine asdescribed above.

For UNIX endpoints:

1. Execute the wdmlseng command to determine if the engineis running.

2. If it is not running:

From a command window on the Tivoli management regionserver, source the Tivoli environment, as described in “Settingup the IBM Tivoli Monitoring environment” on page 17.

Restart the engine by executing the following command:

wdmcmd -restart -e endpoint_name

where endpoint_name is the name of the endpoint.

3. If the engine is running:

a. Stop the it by running the following command:

wdmcmd -stop endpoint_name

b. Restart the engine as described above.



Problem Solution

You distribute a monitoring profile and it is notshowing up on the Web Health Console.

Refer to the IBM Tivoli Monitoring documentation for additionalassistance.

Determine if the distribution was interrupted by running thefollowing command:

wmdist -I repeatername

If the output shows that the distribution was interrupted, youcan clear the distribution in the following ways:

1. Stop the gateway on which the repeater resides by runningthe following command:

wgateway gateway_name stop

where gateway_name is the name of the gateway.

2. Clear the repeater by running the following command:

wmdist -B repeatername

If this is not successful, use the following commands to deletetemporary files:

cd ’/wtemp’rm ./states/*rm ./depot/*

3. Restart the gateway/repeater by running the followingcommand:

wgateway gateway_name start

where gateway_name is the name of the gateway.

4. Redistribute the profile.

Find the trace_ILT. log file in LCFNEW/GWL/logs. TheTrace_ILT.log file logs several types of messages depending onthe setting of the logging level. The default setting is ERROR. Tochange the logging level, run the witmsettrace command. Forexample, witmsettrace GWL DEBUG_MAX logs all levels ofmessages for IBM Tivoli Monitoring for Web Infrastructure:WebLogic Server. Also, the msg_ILT.log file logs any errors.

If the log file does not exist, stop the IBM Tivoli Monitoringengine and run the IBM Tivoli Monitoring task DMLinkJRE asspecified in the IBM Tivoli Monitoring for Web InfrastructureInstallation and Setup Guide. Restart the engine

If the trace_WebLogic_Ilt.log file exists, view the contents to seeif it is using the WebLogic JRE.

If it is not using the WebLogic Server JRE, stop the IBM TivoliMonitoring engine and run the IBM Tivoli Monitoring taskDMLinkJRE, specifying the WebLogic Server JRE and restartingthe engine. See the IBM Tivoli Monitoring for Web InfrastructureInstallation and Setup Guide for more information.

You see a ″Not Compiled″ status for a resourcemodel on the Web health Console.

On a Windows endpoint, this occurs when you do not haveWindows Script Host, Version 5.6, installed. Run the cscriptcommand from the command prompt to verify the version ofWindows Script Host. If it is not Version 5.6, you can downloadit from the Microsoft Web site.

Appendix F. Problem determination 109


Problem Solution

You see a ″Missed PreReq″ status for a resourcemodel on the Web health Console

You probably have not run the DMLinkJRE command. Run theDMLinkJRE command as specified in the IBM Tivoli Monitoringfor Web Infrastructure Installation and Setup Guide.

If this problem occurs after the resource model has already runsuccessfully, restart the IBM Tivoli Monitoring engine on theendpoint. You can restart the engine from the Web HealthConsole or from the command line (with the wdmcmdcommand).

A resource model fails. Restart the IBM Tivoli Monitoring engine on the endpoint. Youcan restart the engine from the Web Health Console or from thecommand line (with the wdmcdm command).

The resource models write trace messages in one of the followingfiles on the endpoint:

v For UNIX:$LCF_DATDIR/LCFNEW/AMW/log/trace_dmxengine.log

v For Windows:%LCF_DATDIR%\LCFNEW\Tmw2k\Tmw2k.log

The statements preceding the resource model aborting messagein the trace file should contain information about why theresource model failed.

For more information, refer to the IBM Tivoli Monitoring User’sGuide.

The WebLogic Server is under stress and theresource models are unable to connect to theserver. When this occurs, the resource modelsreport a Retrying state.

To determine if stress is the problem, check the following items:

v The specified port to see if it is the correct port.

v The logs to see if the server is running.

v The admin console to determine if the server is inaccessible.Note: If the server is inaccessible, the resource models will beunable to connect to the server.

The stress level that causes this behavior is BEA WebLogic Serverdependent.

Non-key attributes in the events sent to TivoliEnterprise Console do not reflect the currentvalues as displayed in the IBM Tivoli MonitoringWeb Health Console.

Because the Web Health Console displays real-time data andTivoli Enterprise Console provides a snapshot of the data at thetime the event was generated, it is possible for the information inthe events to be out of sync with the information displayed onthe Web Health Console.

The WebLogic server is running but the resourcemodel says it is down.

The wrong JRE was specified when the DMLinkJRE task wasrun.

To link the ILT to the correct JRE, first stop the engine on theendpoint. On Windows NT, make sure the m12javaprovider.exeis also stopped. Then run the DMLinkJRE task as specified in theIBM Tivoli Monitoring For Web Infrastructure Installation and SetupGuide. Specify the location of the WebLogic Server JRE. Thenrestart the engine.

For information about the resource model error codes reported in the IBM TivoliMonitoring Web Health Console, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.


Appendix G. Accessibility

Accessibility features help users who have a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer enable you to:v Use assistive technologies such as screen-reader software and a digital speech

synthesizer to hear what is displayed on the screen.v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation includes the following features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for you to apply screen-reader software.v All images are provided with alternative text so that users of the documentation

with vision impairments can understand the contents of the images.

Using assistive technologiesAssistive technology products such as screen-readers function with both thetext-based and graphical user interfaces found in IBM Tivoli Monitoring for WebInfrastructure: WebLogic Server. Consult the assistive technology productdocumentation for specific information about using it to access command-line orgraphical interfaces.

Magnifying what is displayed on the screenIn all components of IBM Tivoli Monitoring for Web Infrastructure: WebLogicServer other than the Web Health Console, you can magnify the screens of theproduct user interfaces using facilities provided by the operating systems on whichthe product is run. For example, in a Windows environment you can change thescreen settings to a lower resolution to enlarge the font sizes of the text on thescreen. Information about these facilities is provided in the relevant operatingsystem documentation.

Documentation in accessible formatsAll user documentation is provided in HTML format, which can be read directlyby assistive tools such as screen readers, or in convertible PDF format. ConvertiblePDF files are those that can be converted from PDF to HTML by the Adobe PDF toHTML converter. For information about converting PDF documents to HTML, referto the Adobe book Optimizing Adobe PDF Files for Accessibility.

Using alternative textAll documentation images are provided with an alternative text that can be readby assistive tools such as screen readers.

111

Appendix H. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents.You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:li

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

113

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksDB2, IBM, the IBM logo, Tivoli, the Tivoli logo, and Tivoli Enterprise Console aretrademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both.

Microsoft and Windows are registered trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries, or both.


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

Other company, product, and service names may be trademarks or service marksof others.

Appendix H. Notices 115

Index

Aaccessibility xi, 111actions (recovery), concept 8administrators, Tivoli 9assigning user groups in Tivoli Enterprise

Data Warehouse 80authorization roles 87

assigning 11defined 9

availability management 1

Bbooks

feedback ixonline ixordering ix

built-in actionsconcept 8

CCIM class, definition 8clearing events, concept 6commands

authorization roles 87wcrtjob 68wcrtprf 93wcrtprfmgr 92wdistrib 21wdmcmd 45wdmdistrib 45wdmeditprf 37, 39, 40, 42, 44, 94, 95wdmeng 45wdmlseng 45, 47wdmmn 46wdmtrceng 45wrunjob 70wruntask for any task 64wschedjob 71wsetadmin 12wsetpm 92wsub 94wweblogic -ConfigureDomain 51wweblogic -ConfigureServer 54wweblogic -KillServer 60wweblogic -RegisterDomain 14, 49wweblogic -RegisterServer 14, 52wweblogic -StartServer 60wweblogic -StopServer 60wweblogic -UnregisterDomain 49wweblogic -UnregisterServer 52wweblogic -ValidateServer 61

conceptsactions (recovery) 8built-in actions 8clearing events 6data logging 7event monitors 6events 5

concepts (continued)events (clearing) 6Gathering Historical Data

Warehouse 4heartbeat function 4logging (data) 7monitors 6profiles 7recovery actions 8scheduling 8tasks (Tivoli Management

Framework) 8Tivoli Management Framework

tasks 8Configure WebSphere TEC Adapter

task 24configuring

endpoints 17Tivoli Enterprise Console event

server 24, 31conventions xiCustomer Support xicycles

definition 4

Ddata logging

concept 7customizing 43

data marts 80dataless profile managers, subscribers

example 92distributed systems

defined 3domains

configuring WebLogic Domains 50discovering WebLogic Servers 56registering WebLogic Domains 49unregistering WebLogic Domains 49WebLogic, configure 50WebLogic, discover 56WebLogic, register 49WebLogic, unregister 49

Ee-mail contact xiendpoints

configuring 17dataless 92defined 9subscribing 93which resource models are

running 46ETL utilities 75event

classescategories 103

event classes and rules 103

event monitorsconcept 6Health Console 7Tivoli Business Systems Manager 7Tivoli Enterprise Console server 6

event serverTivoli Enterprise Console,

configuring 24events

concept 5events (clearing), concept 6events, Tivoli Enterprise Console

defined 23groups 24processing 23responding to 24sources 23viewing 24

Ffailed profile distributions 96feedback about publications xi

Ggateways

IBM Tivoli Monitoring, managing 46Gathering Historical Data Warehouse

concept 4groups, subscribers 18

Hhealth

example of health determination 47understanding resource 47

Health Consoleas monitor, concept 7

heartbeat functionconcept 4

HelpSee Customer Support

holesdefined 5example 37

IIBM Tivoli Monitoring

about 3gateways, managing 46logging, customizing 43notices, sending 39overview 2profiles, managing 45resource model results 47scheduling rules, creating 41setting up 91

117

IBM Tivoli Monitoring (continued)setting up the environment 17tasks, specifying 38thresholds 36Web Health Console 47, 48which resource models are

running 46indications

defined 4installation

task library 63tasks performed automatically 11Tivoli Business Systems Manager 31

interfaces, user 10

Jjobs

creating 67running 69scheduling 70

Llibrary, task 63Line of Business 29logging

customizing 43logging (data)

concept 7

Mmanaged resources

defined 3managed resources, defined 9management, availability 1management, operations 2management, performance 2manuals

feedback ixonline ixordering ix

MDist2distributing profiles using 20functions used by IBM Tivoli

Monitoring 20monitoring profiles, defined 92monitors

concepts 6Health Console 7Tivoli Business Systems Manager 7Tivoli Enterprise Console server 6

Nnotices

sending 39

Ooccurrences

defined 5operations management 2ordering publications x

overviewIBM Tivoli Monitoring 2IBM Tivoli Monitoring for Web

Infrastructure: WebLogic Server 1

Pparameters

defined 7performance management 2problem determination

dependencies issues 105failed task 107permissions errors 107

profile managerscreated during installation 11creating 92dataless 92setting up 92subscribing endpoints 93

profilesconcept 7creating 92distributing from the Tivoli

desktop 18distributing using MDist2 20managing at endpoints 45monitoring 92rerunning failed distributions 96subscribers of 18

publicationsfeedback ixonline ixordering ix

Qquick reference, task 89

Rrecovery actions, concept 8reports

Tivoli Enterprise Data Warehouse,creating 86

Tivoli Enterprise Data Warehouse,modifying default settings 85

Tivoli Enterprise Data Warehouse,modifying settings 85

Tivoli Enterprise Data Warehouse,running 83

Tivoli Enterprise Data Warehouse,scheduling to run 84

resource health, understanding 47resource models

adding customized 95adding default 94created during installation 11definition 8managing at endpoints 45organizing 94results, viewing 47running on endpoints 46scheduling rules, creating 41tasks, specifying 38thresholds, customizing 36

resourcesadded during installation 11discovering for Tivoli Business

Systems Manager 32endpoints 9managed 9

resources, manageddefined 3

results, resource models, viewing 47roles

authorization, assigning 11Tivoli Enterprise Data Warehouse 77Tivoli Enterprise Data Warehouse,

assigning 78Tivoli Enterprise Data Warehouse,

IBM Console user 78roles, authorization 9rules 103rules, Tivoli Enterprise Console

about 24

Sscheduling

concept 8for monitoring 41resource models 41

scheduling rules, example 41server objects

configuring 13locating 13registering in the Tivoli

environment 13servers

See also server objectsconfiguring WebLogic Servers 53discovering WebLogic Servers 56killing 58registering WebLogic Servers 51starting 58stopping 58unregistering WebLogic Servers 51validating 60WebLogic, configure 53WebLogic, discover 56WebLogic, register 51WebLogic, unregister 51

softcopy publications xsubscribers 18subscribing endpoints 93Support, Customer xi

Ttask argument window, example 66task library 63tasks

authorization roles 87Configure WebSphere TEC Adapter

task 24customizing 66discover_ weblogic_servers 57kill_ weblogic_server 60library 63quick reference 89running 63


tasks (continued)specifying for an event 38standard 63start_ weblogic_server 60stop_ weblogic_server 60Tivoli Business Systems Manager,

WebLogic_TBSM_Discovery task 33validate_ weblogic_server 61working with IBM Tivoli Monitoring

for Web Infrastructure: WebLogicServer resources 49

tasks (Tivoli Management Framework)concept 8

thresholdscustomizing resource models 36defined 9

Tivoli administrators 9Tivoli Business Systems Manager

as monitor, concept 7configuring Tivoli Enterprise Console

to forward events 31discovering resources 32installing 31integrating with IBM Tivoli

Monitoring for Web Infrastructure:WebLogic Server 30

prerequisites for integrating 30task, WebLogic_TBSM_Discovery

task 33understanding 29uninstalling 34WebLogic Server tasks 33WebLogic_TBSM_Discovery task 33

Tivoli Enterprise ConsoleConfigure Event Server window 26console 24event classes 103event groups, definition 24event server, configuring 24, 31events, defined 23events, processing 23events, responding to 24events, sources 23events, viewing 24overview 23rules, overview 24

Tivoli Enterprise Console serveras monitor, concept 6

Tivoli Enterprise Data Warehouseassigning user groups to a data

mart 80assigning users to user group 79capabilities 75central data warehouse 76components 75control server 75creating IBM Console user 78creating reports 86creating user groups 79data marts 76logging 43modifying report settings 85modifying report settings

example 85problem determination 106report interface 76roles 77

Tivoli Enterprise Data Warehouse(continued)

running reports 83scheduling reports to run

automatically 84user roles, assigning 78users and user groups 77

Tivoli Management Frameworktasks, concept 8

troubleshootingSee problem determination

Uuser groups

Tivoli Enterprise Data Warehouse,assigning 80

Tivoli Enterprise Data Warehouse,assigning users 79

Tivoli Enterprise Data Warehouse,creating 79

usersroles, assigning in Tivoli Enterprise

Data Warehouse 78users. creating for IBM Console 78utilities, ETL 75

Wwcrtjob command 68wcrtprf command 93wcrtprfmgr command 92wdistrib command 21wdmcmd command 45wdmdistrib command 45wdmeditprf command 37, 39, 40, 42, 44,

94, 95wdmeng command 45wdmlseng command 45, 47wdmmn command 46wdmtrceng command 45Web Health Console 47

IBM Tivoli Monitoring 48wrunjob command 70wruntask command

for any task 64wschedjob command 71wsetadmin command 12wsetpm command 92wsub command 94

Index 119

��

Printed in U.S.A.

GC23-4718-00

ibm tivoli monitoring for web infrastructure: weblogic...

Documents