IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. User s Guide. Version SC

Size: px
Start display at page:

Download "IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. User s Guide. Version SC"

Transcription

1 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server User s Guide Version SC

2

3 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server User s Guide Version SC

4 Note Before using this information and the product it supports, read the information in Appendix G, Notices, on page 155. First Edition (April 2003) This edition applies to the version of IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures v Tables vii About this guide ix Who should read this guide ix Publications ix IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server Library.... ix Prerequisite publications x Accessing softcopy publications x Ordering publications x Accessibility xi Contacting Customer Support xi Conventions used in this book xi Terminology xi Typeface conventions xi Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server Availability management Performance management Operations management Overview of IBM Tivoli Monitoring Understanding IBM Tivoli Monitoring terminology 3 Authorization roles Managed resources and endpoints User interface options Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server Guidelines for setting up the product Setting authorization roles Configuring local endpoints Configure client side WebSphere security Enabling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to communicate with IBM WebSphere Application Server on a non-default port Enabling performance monitoring Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects 17 Configuring z/os proxy endpoints Configuring metric collection for z/os systems 24 Creating an authentication key for a sysplex.. 27 Setting up and starting the z/os Data Collector 28 Updating the IBM WebSphere application server environment Setting up the IBM Tivoli Monitoring environment 33 Distributing profiles Distributing profiles from the Tivoli desktop.. 34 Distributing profiles using MDist Chapter 3. Setting up the Tivoli Enterprise Console for event correlation Overview of the Tivoli Enterprise Console Configuring the Tivoli Enterprise Console event server Configuring the Tivoli Enterprise Console adapter for local systems Configuring the Tivoli Enterprise Console z/os adapter Filtering events Chapter 4. Integrating with Tivoli Business Systems Manager Understanding Tivoli Business Systems Manager.. 51 Prerequisites Working with z/os objects Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager Configuring the Tivoli Enterprise Console event server to work with Tivoli Business Systems Manager Discovering resources for Tivoli Business Systems Manager Working with Tivoli Business Systems Manager.. 56 Uninstalling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration from Tivoli Business Systems Manager. 56 Chapter 5. Working with resource models Resource model library Modifying indications Specifying tasks for an indication Sending a notice to administrators when an event occurs Creating scheduling rules Modifying data logging settings Managing profiles and resource models at endpoints 68 Managing IBM Tivoli Monitoring gateways Determining which resource models are running on endpoints Viewing resource model results with the IBM Tivoli Web Health Console Understanding resource health Connecting the IBM Tivoli Monitoring Web Health Console Stopping the monitoring of data from an endpoint 72 iii

6 Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources Checking the status of an IBM WebSphere administration or application server Starting or stopping a server Listing application servers Viewing endpoint or callback log files Chapter 7. Working with tasks and jobs 81 Running a task Customizing a task Creating a job Running a job Scheduling a job Chapter 8. Enabling Tivoli Enterprise Data Warehouse Overview Control server Central data warehouse Data marts Report interface Working with users and user groups About users and user groups The Tivoli Enterprise Data Warehouse roles Creating an IBM Console user Assigning roles to a user Creating a user group Assigning users to a user group Assigning user groups to a data mart Managing Tivoli Enterprise Data Warehouse reports 98 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server star schemas, data marts, and reports Running reports Scheduling reports to run automatically Modifying default settings for reports Creating reports Appendix A. Task quick reference Appendix B. Setting up IBM Tivoli Monitoring Creating profile managers and profiles Subscribing resources to profile managers Adding default resource models to profiles Adding customized resource models to profiles Rerunning failed profile distributions Appendix C. Creating custom resource models Creating custom resource models using the IBM Tivoli Monitoring Workbench Enabling JVMPI data reporting Appendix D. Event classes and rules 123 Event classes Rules for resource models Rules for events z/os messages Appendix E. Problem determination 127 Possible problems and workarounds General problem determination Tivoli Enterprise Console problem determination Tivoli Enterprise Data Warehouse problem determination Tasks problem determination Resource models problem determination z/os-related resource model problem determination General z/os problem determination Debugging information Log file information AutoTrace information Appendix F. Accessibility Using assistive technologies Magnifying what is displayed on the screen Documentation in accessible formats Using alternative text Appendix G. Notices Trademarks Index iv IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

7 Figures 1. The Discover_WebSphere_Resources task execution window The Enable_Metrics_Gathering task execution window The Configure Event Server task window The Configure WebSphere TEC Adapter task window The Operation menu on a IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server object The output window for the Check Status action List of application servers associated with the specified IBM WebSphere administration server The list of endpoint logs associated with the IBM WebSphere administration server Example of a task argument window v

8 vi IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

9 Tables 1. Counting occurrences Guidelines for setting up the product Guidelines for configuring local endpoints Minimum performance monitoring levels for the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models Guidelines for configuring z/os proxy endpoints Integrating with Tivoli Business System Manager Health Determination Example Working with tasks and jobs Guidelines for working with Tivoli Enterprise Data Warehouse users and user groups Guidelines for working with Tivoli Enterprise Data Warehouse reports Default time filter names and values IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server task authorization roles Monitoring resources and applications guidelines Guidelines for creating custom resource models z/os state messages monitored by Tivoli Enterprise Console z/os error exception messages monitored by Tivoli Enterprise Console General problems and solutions Tivoli Enterprise Console problems and solutions Tivoli Enterprise Data Warehouse problems and solutions Task problems and solutions Discover_WebSphere_Resources task problems and solutions Resource model problems and solutions z/os resource model problems related to the IBM WebSphere administration server z/os resource model problems related to NetView z/os resource model problems related to the IBM WebSphere application server z/os resource model problems related to the Data Collector z/os resource model problems related to the endpoint z/os systems problems and solutions Behavior related to failed z/os components 148 vii

10 viii IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

11 About this guide Who should read this guide Publications The IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server User s Guide provides information about setting up and using IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to manage your IBM WebSphere Application Server resources. This guide is for administrators and system programmers who use IBM Tivoli Monitoring for Web Infrastructure to manage IBM WebSphere Application 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, Linux, and z/os v Web server administration v The Tivoli management environment This section lists publications in the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server library and any other related documents. It also describes how to access Tivoli publications online, how to order Tivoli publications, and how to submit comments on Tivoli publications. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server Library The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server library contains the following publications: v IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide, GC Provides information about installing and setting up IBM Tivoli Monitoring for Web Infrastructure. v IBM Tivoli Monitoring for Web Infrastructure Release Notes, GI Provides a product overview, system requirements, and additional installation information. v IBM Tivoli Monitoring for Web Infrastructure Reference Guide, GC Provides detailed programming information about the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models, tasks, commands, and error messages. v IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server Warehouse Enablement Pack Implementation Guide, SC Provides information about installing and using the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application 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\izy\pkg\v110\doc directory. ix

12 v IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server Workaround and Limitations Supplement, GI Provides information about problems that might occur, as well as customer issues that have been resolved. Prerequisite publications To use the information in this book effectively, you must have some prerequisite knowledge of IBM Tivoli Monitoring, which you can get from the following books: v IBM Tivoli Monitoring User s Guide, SC Provides an overview of IBM Tivoli Monitoring, especially of resource models. It also describes how to use the user interface. v IBM Tivoli Monitoring Workbench User s Guide, SC Describes using the IBM Tivoli Monitoring Workbench to create and customize resource models. Accessing softcopy publications The publications for this product are available in PDF and HTML formats through the following media: IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: Documentation CD, LK3T The Documentation CD contains all of the English language publications for this product, except for the Web-only Limitations and Workarounds supplements. The NLV (national language support) Documentation CD contains both English and non-english language publications for this product, except for the Web-only Limitations and Workarounds Supplements. IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Information Center Web site. The Tivoli Software Information Center is located at the following Web address: Note: If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print window. This option is available when you click File Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using. Ordering publications You can order many Tivoli publications online at the following Web site: You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, see the following Web site for a list of telephone numbers: x IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

13 Accessibility Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For more information about the accessibility features of this product, see Appendix F, Accessibility, on page 153. Contacting Customer Support If you have a problem with any Tivoli product, you can contact Customer Support. See the IBM Customer Support Guide at the following Web site: The guide provides information about how to contact Customer Support, depending on the severity of your problem, and the following information: v Registration and eligibility v v Conventions used in this book Telephone numbers and addresses, depending on the country in which you are located Information you must have before contacting Customer Support This book uses several conventions for special terms and actions, operating system-dependent commands and paths, and margin graphics. Terminology The following terms are used throughout this document: local Refers to any non-z/os platform, such as Windows, AIX, or Linux. UNIX Refers to AIX, HP-UX, and Solaris platforms. Windows Refers to Microsoft Windows NT and Windows z/os Refers to z/os and IBM OS/390 platforms. Typeface conventions This guide uses the following typeface conventions: Bold v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip: and Operating system considerations:) v Column headings in a table v Keywords and parameters in text Italic v Citations (titles of books, diskettes, and CDs About this guide xi

14 v v v v v Words defined in text Emphasis New terms in text (except in a definition list) Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options xii IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

15 Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server Availability management IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server provides a centralized system management tool for IBM WebSphere Application Server Advanced Edition. The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server enables you to manage IBM WebSphere administration and application servers. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides the ability to manage and monitor IBM WebSphere Application Server resources by providing extensions to Tivoli Management Framework, IBM Tivoli Monitoring, Tivoli Enterprise Console, Tivoli Business Systems Manager, and Tivoli Enterprise Data Warehouse. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server uses IBM Tivoli Monitoring resource models to manage distributed IBM WebSphere Application Server resources effectively. Use IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to perform the following tasks: v v v v v Monitor and interpret performance and availability data for all IBM WebSphere Application Server resources across distributed environments Manage performance and availability of IBM WebSphere Application Server resources Capture and manage historical data that is stored in a central data warehouse Forward IBM WebSphere Application Server events to the Tivoli Enterprise Console Manage event correlation and automation using the Tivoli Business Systems Manager Note: Tivoli Enterprise Console, Tivoli Business Systems Manager, and Adapter Configuration Facility products must be installed for you to take advantage of event management functions. This guide addresses event management topics with the assumption that Tivoli Enterprise Console, Tivoli Business Systems Manager, and Adapter Configuration Facility products are installed where required. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides the following features: v Availability management v Performance management v Operations management IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides resource models that periodically check the status of your IBM WebSphere Application Server components. For example, the resource models monitor the administration and application servers for the following states: 1

16 Performance management Operations management v Up v Down You can configure the resource models to customize the monitoring cycle and to change the triggering thresholds. To ensure that you are managing all available resources, IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides the Discover_WebSphere_Resources task that finds IBM WebSphere administration servers and application servers. When the Discover_WebSphere_Resources task locates new IBM WebSphere Application Server resources, it adds them to your Tivoli configuration. IBM WebSphere Application Server resources report operational changes in local logs. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides event adapter functions to extract IBM WebSphere Application Server events from these logs. You can view these events on the Tivoli Enterprise Console event console, and you can write rules to automatically take action in response to these events. You can also forward events from Tivoli Enterprise Console to Tivoli Business Systems Manager. The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models enable you to measure and report the performance of various components running on your IBM WebSphere Application Server resources, such as Enterprise JavaBean (EJB) performance or database connection pool performance, both of which affect the performance of Web applications running on your servers. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks enable you to manage your IBM WebSphere Application Server resources on a daily basis. You can use these tasks to do the following: v v v Start and stop your IBM WebSphere administration and application servers, as well as the Tivoli Enterprise Console event adapter Check the status and retrieve information about your IBM WebSphere Application Server resources Retrieve and delete IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server trace log files Note: For z/os endpoints, you can only check the status and retrieve information about the resources. You cannot start and stop resources or work with trace logs on the endpoints. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server event rules manage the information presented on your event console. These rules remove duplicate and harmless events and correlate events to close events that are no longer relevant. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server event reporting functions support standard Tivoli event filtering, which you can use to reduce the number of events sent to your events server. In addition to forwarding events to Tivoli Enterprise Console, IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server can also forward events to Tivoli Business Systems Manager. 2 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

17 Note: Events for z/os systems are filtered using NetView. See Configuring the Tivoli Enterprise Console z/os adapter on page 46 for more information. Overview of IBM Tivoli Monitoring IBM Tivoli Monitoring enables you to deploy preconfigured best practices resource models as well as standard and customized resource models to automate the monitoring of essential resources. In this context, a resource is anything that affects 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. This enables you to detect bottlenecks and other potential problems and define automatic recovery from critical situations. This ability frees system administrators from manually scanning extensive performance data. The monitoring software integrates with other Tivoli Availability solutions, including Tivoli Business System Manager and Tivoli Enterprise Console. A resource model captures and returns information, such as database status or server availability, about a resource or software application in the Tivoli management environment. To use a resource model, you must define and distribute it to an endpoint. Tivoli provides tools for organizing system resources on the Tivoli desktop. Servers are subscribed to profile managers. These subscriptions provide the channel through which resource models are distributed to servers. A profile manager also contains profiles, which are containers for application-specific information about a particular type of resource. Each profile contains one or more resource models. You can subscribe resources to a profile manager. You can distribute individual profiles within the profile manager to subscribers of the profile manager. You can group profile managers in a way that meets your needs. Profile managers can reflect functional grouping of resources, functional grouping of resource models, or any grouping at all. Likewise, a profile can contain any combination of resource models. However, you must segregate profiles according to resources: Web servers need Web server resource models, and database servers need database server resource models. You can define each resource model to include information such as how often to check resource status and what to do when certain conditions are met. Some resource models provide predefined settings and response actions, which you can adjust. Other resource models require you to define all the settings. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for a description of individual settings. Before running a resource model, you must subscribe the server resource to the profile 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 are set up to become active when you distribute them to subscribers. You can activate and deactivate resource models after they are distributed. Understanding IBM Tivoli Monitoring terminology This section describes the main concepts required for understanding how to use the IBM Tivoli Monitoring product. Note: The definitions below apply to resource models in general. They are not specific to the resource models provided by IBM Tivoli Monitoring for Web Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server 3

18 Infrastructure: WebSphere Application Server. For information about the configuration of the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Actions You can associate one or more recovery actions with a specific event. These actions are automatically triggered when the event occurs and, typically, are used for restoring satisfactory system service level. Each time an event occurs, the system provides a notification of the event, triggers a recovery action to restore satisfactory conditions and, if the action is successful, provides a notification that the action was performed. Actions are associated with the execution of a CIM method or the execution of a program. Associate actions with indications when modifying an existing resource model using this software, or when creating a new resource model with the IBM Tivoli Monitoring Workbench. Attributes Attributes can be string or numeric values. When creating a new resource model with the IBM Tivoli Monitoring Workbench, you can qualify an event by specifying relevant attributes according to the information you want the resource model to monitor. For example, an event might indicate insufficient disk space. When you specify attributes, such as disk name, or available disk space, the resource model can generate a more precise indication of the problem. For each resource model, some of the attributes are designated as keys. Cycles When a resource model is run at an endpoint, it gathers data at regular intervals, called cycles; the duration of a cycle is the cycle time, which is expressed in seconds. A resource model with a cycle time of 60 seconds gathers data every 60 seconds. Each of the supplied resource models has a default cycle time, which you can modify when you define the resource model. At each cycle, the resource model collects data, analyzes it, generates the events and triggers specified actions. The data collected are a snapshot of the status of the resources specified in the resource model. Gathering Historical Data component The Gathering Historical Data component enables IBM Tivoli Monitoring to use Tivoli Decision Support for Server Performance Prediction and Tivoli Enterprise Data Warehouse. The Gathering Historical Data component uses data collected by specific IBM Tivoli Monitoring resource models to populate a database on the Tivoli server where the Gathering Historical Data component is installed. The collected data is aggregated every 24 hours and added to the IBM Tivoli Monitoring database, from where it can be used in analyses that help plan network growth using key system metrics. For more information about Tivoli Enterprise Data Warehouse, see the following publications: v Tivoli Distributed Monitoring Warehouse Enablement Pack: Implementation Guide v Enabling an Application for Tivoli Enterprise Data Warehouse Heartbeat function IBM Tivoli Monitoring operates a heartbeat function, which monitors the basic system status at endpoints attached to the gateway at which it is enabled. Events can be sent to the Tivoli Business Systems Manager 4 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

19 (provided that the Tivoli Business Systems Manager Adapter component is installed at the gateway), the Tivoli Enterprise Console, and the IBM Tivoli Monitoring Notice Group. Indications and Events An indication is generated when the state of a given resource meets defined 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 a certain number of indications are aggregated into an event. You also specify whether these indications must be consecutive, or whether the sequence may be interrupted by one or more monitoring cycles that do not register any indication. The cycles during which no indication is generated are called holes. An event can notify that there is a problem in the resource state, trigger an action and, if enabled, send a notification to the Tivoli Enterprise Console server or to Tivoli Business Systems Manager. Indications Each resource model generates an indication when thresholds you define are exceeded in a given cycle. A single occurrence of an indication does not always represent a problem, however the persistence of indications might. The resource model measures the persistence of the indications and aggregates them according to your specifications, or how you define settings for occurrences and holes. If the persistence of an indication meets the specified number of occurrences, the resource model generates and event. Indications can be generated in any one of the following circumstances: v When a single threshold is exceeded v When a combination of two or more thresholds are exceeded v When a combination of other factors change Occurrences and holes Occurrences and holes record whether or not an indication occurs during a cycle for a specific resource model. An occurrence is a cycle during which at least one threshold is exceeded and an indication occurs for a given resource model. A hole is a cycle during which an indication does not occur for a given resource model. A hole means none of the conditions that generate an indication were met. Events An event is an aggregation of a defined number of consecutive occurrences during which there can be a defined number of consecutive holes. An event is generated only when the aggregation algorithm detects the number consecutive occurrences defined in the indication with which the event is associated. An event verifies the persistence of an indication by eliminating unrepresentative peaks and troughs over a period of cycles. An indication that persists over several cycles is more likely to be a problem. Thus, an event defines that a number of occurrences over a period of cycles has occurred. When you define an event, you can specify how many consecutive holes in the sequence of consecutive occurrences are permitted. Specifying how many consecutive holes are permitted during the Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server 5

20 accumulation of the consecutive occurrences enables you to continue the counting of consecutive occurrences if one or two cycles fall below the threshold. The following examples illustrate what happens if you define an event as three occurrences and two holes. 1 represents an occurrence and 0 represents a hole. v Because fewer than three holes exist between each of the three occurrences, the three occurrences are consecutive. Therefore, the sequence represents an event. v If each occurrence is followed by the maximum specified holes within seven cycles, an event is triggered. v If the algorithm counts two consecutive occurrences and then observes three consecutive holes (more holes than that allowed in the definition of an event for this example) it sets the count of occurrences to zero. See Table 1. Table 1. Counting occurrences Sequence Count of occurrences While defining an event, you can also indicate if you want the system to notify the Tivoli Enterprise Console server, or the Tivoli Business Systems Manager, that an event was generated. The Tivoli Monitoring operator can change these selections later, when the resource model is included in a Tivoli Monitoring profile. You can also define the degree of severity and the message that will specify the notification of the event. Clearing Events A clearing event is a resource model function that, if enabled, allows IBM Tivoli Monitoring to close an event when the circumstances that caused the event are no longer present. Clearing events can be processed by the Tivoli Enterprise Console server and by Tivoli Business Systems Manager. Clearing events have a severity of harmless, regardless of the severity of the original event, but have the same event ID as the original event. For example, a service stops and the Tivoli Enterprise Console server receives an event notifying it of this problem. Until the service restarts, the problem is still present on the endpoint, but IBM Tivoli Monitoring does not send any further event notifications to the Tivoli Enterprise Console server. If the Clearing Event function is enabled, as soon as the service restarts, Tivoli Enterprise 6 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

21 Console server, thereby closing the original event. The Clearing Event itself does not normally appear on the server, because its only function is to clear the original error event. Note: Correlated events cannot be cleared. Monitoring of events and indications Events can be sent to the Tivoli Enterprise Console server, the Web Health Console, and Tivoli Business Systems Manager. Tivoli Enterprise Console server Events can be viewed by a Tivoli Enterprise Console server and contain a set of properties that can help to identify problems. Clearing events can also be processed by the Tivoli Enterprise Console server. If the default procedure is used to enable the monitoring of events, the Tivoli Enterprise Console server uses the clearing event to close the associated error event. However, if you choose not to install the clearing events rule incorporated in the above-mentioned default procedure, the clearing event is displayed as a separate entity with the same ID as the original error event. Web Health Console The Web Health Console, an optional part of IBM Tivoli Monitoring, displays the health of each resource model for a selected endpoint as a numeric value between 100 (perfect health) and zero (with zero meaning that an event has been triggered). Intermediate values show the percentage of occurrences currently registered with respect to the total number of occurrences needed to trigger an event. Tivoli Business Systems Manager Events and clearing events can also be sent to the Tivoli Business Systems Manager, provided that the Tivoli Business Systems Manager Adapter component has been installed on the gateways of the endpoints that are to be monitored. A full description of Tivoli Business Systems Manager can be found in the Tivoli Business Systems Manager documentation. Clearing events can also be processed by the Tivoli Business Systems Manager, which uses the clearing event to close the associated error event. Logging For any endpoint, you can log the data collected by a resource model in a local database. Then you can view it through the History View of the Web Health Console. You can choose to store raw or aggregated data. You can also log data to the Tivoli Enterprise Data Warehouse. Parameters While thresholds can be only numeric values, parameters can be lists of numbers or strings. Using parameters enables you to customize your resource model. You can define different parameters, as required. For each parameter you can specify a value, which can, for example, represent the Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server 7

22 instances you want to monitor, or a limit you do not want your resource to exceed, depending on how you use this setting in your script. The lists will then be displayed in the IBM Tivoli Monitoring dialogs, and depending on the type of list you select in the IBM Tivoli Monitoring Workbench, the lists will appear in different forms on IBM Tivoli Monitoring. Within the IBM Tivoli Monitoring Workbench, you can define default values and then let the operator customize the settings in IBM Tivoli Monitoring. You can choose one among the following kinds of lists when you specify the parameters: v Boolean List v Choice List v String List v Numeric List Some resource models have one or more parameters. Profiles IBM Tivoli Monitoring is a profile-based application that runs in a Tivoli environment. Different profiles can be defined containing different selections of resource models. All aspects of existing profiles can be modified, including the addition, deletion and customization of resource models. You can distribute multiple profiles to each endpoint. Recovery Actions For any event, recovery actions can be run automatically, such as built-in actions (for Windows) or Tivoli Framework tasks. The actions can take positive steps to remedy the situation, or can ensure that information about the event is distributed to the appropriate authorities or entities. Built-In Actions Certain events can have one or more built-in actions predefined for them. An action can be either the execution of a common information model (CIM) class method or the execution of a program. Both type of actions can be implemented only through the Workbench. For example, an event that detects the failure of a service could have the restart of that service as its built-in action. Thus, without any human intervention, IBM Tivoli Monitoring detects the failure of a service and automatically restarts it. Built-in actions are defined by default as part of an event, but can be removed. They have the same event ID as the event that they are designed to correct. Note: The indications for the IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server resource models do not have built-in actions. You can add built-in actions to a custom resource model. Tivoli Framework tasks For each event you can select one or more Tivoli Framework tasks to be performed when the event is triggered. The tasks that are triggered by a IBM Tivoli Monitoring event can access the event name and event thresholds by accessing the environment variables. Resource models IBM Tivoli Monitoring products provide predefined resource models that access specific performance data from the system at runtime. The resource models process the data they collect using an algorithm that determines whether or not the system is performing to expectations. You can either 8 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

23 Authorization roles use a resource model s default values to collect performance data or customize the resource models to match specific requirements in your environment. Distributing resource models using default values enables you begin monitoring immediately to obtain useful data concerning your enterprise. When you become more familiar with the monitoring process and feedback, you may choose to customize the resource model information. Scheduling IBM Tivoli Monitoring contains a scheduling feature that enables you to determine a period within which monitoring takes place and specific scheduling 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 days during which monitoring takes place. Any number of rules can be defined, allowing you to set up a complex pattern of resource monitoring for a profile, covering the time periods important to you. The scheduled times are always interpreted as local times, enabling you to set up a single rule that monitors the same local time period in different time zones. For example, if your region covers several time zones, but you want to monitor morning activities in each time zone, a single rule defining the monitoring period of between 08:00 and 13:00 is interpreted locally in each of the time zones, so that you monitor the same relative period. You should note also that all times of events or activities reported from endpoints or gateways are logged in the local time of the system from where they originated. Thresholds Each resource model defines one or more thresholds. Each threshold has a default numeric value that you can change when you define the profile. The following are examples of how a resource model can use thresholds: v v A threshold value might represent a limit that, if not met, indicates an unsatisfactory resource state. For example, if you want the system to notify you when disk space drops under 70%, set the threshold value to 70 to generate an indication each time your disk space is less than 70%. Some threshold values control the scope of what the resource model monitors. You can add a description for each threshold in the Threshold dialog explaining what each value measures and how it is used within the monitoring algorithm. IBM WebSphere Application Server administrators are known in the Tivoli environment as Tivoli administrators. Administrators are system or Tivoli administrators who have the authorization to manage IBM WebSphere Application Server servers. After the product is installed, you can assign authorization roles to administrators that define the operations they can perform. Each administrator or group of administrators is represented by an icon on the Tivoli desktop. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server fully integrates into Tivoli security. To perform administration functions, administrators Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.1: WebSphere Application Server 9

24 must have authorization roles for both IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server and the Tivoli management environment. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server uses the following authorization roles: v websphereappsvr_super v websphereappsvr_admin v websphereappsvr_user Managed resources and endpoints User interface options A managed resource is a system or network resource that you manage with Tivoli Management Framework. A managed resource is a specific resource that has a default policy defined in a policy region. An endpoint is a managed resource that is the target for distribution of a profile or the resource on which a task or job is to be run. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server uses endpoint objects to represent IBM WebSphere administration and application servers. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server uses two types of endpoints: local endpoints and proxy endpoints. A local endpoint represents an IBM WebSphere administration or application server running on a non-z/os platform, such as Windows or AIX. A proxy endpoint is a non-z/os system that communicates with an IBM WebSphere administration or application server running on a z/os system. To manage IBM WebSphere Application Server resources on local endpoints, the Tivoli endpoint must be installed on each IBM WebSphere Application Server node. For z/os systems, the proxy endpoint must be installed on a separate system from z/os. Note: In the Tivoli environment, the term node is used to refer to any managed resource with Tivoli Management Framework installed. In the WebSphere environment, the term node is used to refer to the IBM WebSphere administration server. In this document, unless specifically indicated, the Tivoli environment definition of node is used. You can use the following user interfaces when working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: v The Tivoli desktop, which is the traditional Tivoli graphical user interface (GUI) v The command line interface (CLI) v IBM Tivoli Monitoring Web Health Console to work with resource models v Tivoli Enterprise Console to work with event management v v Tivoli Business Systems Manager to work with event management and to run some tasks Tivoli Enterprise Data Warehouse to gather data about your resources 10 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

25 Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server This chapter describes how to configure IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. Guidelines for setting up the product The following table describes the steps required to set up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server, as well as links to where to find more information. Table 2. Guidelines for setting up the product Goal Assign the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server authorization to one or more Tivoli administrators Configure the local endpoints: 1. Link to a JRE for each endpoint. 2. If WebSphere security is enabled, configure client side security. 3. If you are using a non-default port for WebSphere, enable the endpoint to also use the non-default port. 4. Enable performance monitoring. 5. Enable JVMPI data reporting (optional). Create IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects to represent your IBM WebSphere Application Server components Configure z/os systems and proxy endpoints: 1. Link to a JRE for each endpoint. 2. Configure the Tivoli Enterprise Console z/os event adapter. 3. Enable the gathering of data metrics. 4. Configure port information for your proxy endpoints. 5. Start the z/os data collector. 6. Update the IBM WebSphere application server environment. Set up the IBM Tivoli Monitoring environment so that you can run commands Distribute profiles either from the Tivoli desktop or using MDist2 Set up Tivoli Enterprise Console for event correlation (optional) Where to find information Setting authorization roles on page 12 Configuring local endpoints on page 13 Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page 17 Configuring z/os proxy endpoints on page 24 Setting up the IBM Tivoli Monitoring environment on page 33 Distributing profiles on page 34 Configuring the Tivoli Enterprise Console event server on page 40 11

26 Table 2. Guidelines for setting up the product (continued) Goal Set up Tivoli Business Systems Manager (optional) Where to find information Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager on page 53 Setting authorization roles During installation, IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server performs several tasks that help to set up your IBM Tivoli Monitoring environment, including creating profile managers, adding resources to the profiles, and adding resource models to profiles. The following profile managers are created during installation: v WebSphere Administration Servers v WebSphere Application Servers v WebSphere Application Servers with EJBs v WebSphere Application Servers with Servlets If you want to create additional profile managers or customize the subscribers or resource models assigned to your profile manager, the procedures are documented in Appendix B, Setting up IBM Tivoli Monitoring, on page 111. Objective To assign the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server authorization roles for managing resources to administrators and users. Background information When you install IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server, the following three roles are created: v websphereappsvr_super v websphereappsvr_admin v websphereappsvr_user All tasks require that you assign at least one of these roles to the Tivoli administrator who is running the task. In addition, some tasks require Tivoli authorities as defined by Tivoli management region roles. To run tasks and processes, the Tivoli administrator must have the required Tivoli authority and must be assigned one of the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server authorization roles. You can assign IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server authorization as Tivoli management region roles or as resource roles, depending on local authorization requirements. Required authorization role senior Before you begin Before setting authorization roles, you must have installed IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for information on installation. 12 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

27 Configuring local endpoints When you finish Add managed resources to a policy region. Procedure You can perform this procedure from the command line or the Tivoli desktop. Command Line: Use the wsetadmin command to set or change resource authorization roles. See the Tivoli Management Framework Reference Manual for more information. Tivoli desktop: Follow these steps to perform this procedure from the Tivoli desktop: 1. Double-click the Administrators icon to display the Administrators window that shows the defined Tivoli administrators. 2. Right-click the administrator whose role you want to modify to access the pop-up menu. 3. Select Edit TMR Roles to access the Set TMR Roles window. 4. Add or remove roles for the selected resources as follows: v To add roles for the selected resources, select one or more roles from those shown in the Available Roles scrolling list and click the left-arrow button. The selected roles are moved from the Available Roles scrolling list to the Current Roles scrolling list. You can also double-click an entry in the Available Roles scrolling list to move it automatically to the Current Roles scrolling list. v To remove roles for the selected resources, select one or more roles from those shown in the Current Roles scrolling list and click the right-arrow button. 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 the Current Roles scrolling list to move it automatically to the Available Roles scrolling list. Note: The list of roles might include others not mentioned here, depending on the particular applications installed. You must click Change & Close or Change to add and remove the selected roles and save your changes; the selected roles are only temporarily moved to the Current Roles or Available Roles scrolling lists. 5. If you are adding more than one role, click Change to add or remove the selected resource roles for the administrator as specified. The Set TMR Roles window remains displayed. 6. Click Change & Close to add or remove the selected resource roles for the administrator and return to the Administrators window. The administrator must restart the Tivoli desktop before this change takes effect. Before you can monitor your resources, you must configure the local (non-z/os) WebSphere nodes to work with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. You only need to configure a node one time. Configuring the nodes includes the following steps: Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 13

28 Table 3. Guidelines for configuring local endpoints Goal Link to a JRE for each endpoint If WebSphere security is enabled, configure client side security Configuring an endpoint to use a non-default port (Optional) Enable performance monitoring Enable JVMPI data reporting (optional) Where to find information IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide Configure client side WebSphere security Enabling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to communicate with IBM WebSphere Application Server on a non-default port on page 15 Enabling performance monitoring on page 16 Enabling JVMPI data reporting on page 121 Note: These steps apply only to local endpoints. See Configuring z/os proxy endpoints on page 24 for information about configuring z/os proxy endpoints. Configure client side WebSphere security Objective To enable WebSphere security for local endpoints. Background information When client side WebSphere security is enabled for IBM WebSphere Application Server, you must perform steps to configure client side WebSphere security. Required authorization role No Tivoli role is required. The procedure below is performed on the endpoint system, not the Tivoli management region server. Administrator authority is required on the IBM WebSphere Application Server system. Before you begin None When you finish If you are using a non-default port, see Enabling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to communicate with IBM WebSphere Application Server on a non-default port on page 15. Enable performance monitoring on your IBM WebSphere administration and application servers. See Enabling performance monitoring on page 16 for more information. When you create objects or run the Discover_WebSphere_Resources task, specify the sas.wscp.props file created in this procedure. Procedure Use the following steps to configure client side WebSphere security: 1. In the properties directory where you installed IBM WebSphere Application Server, make a copy of the sas.client.props file and name it sas.wscp.props. 2. Open the new file, sas.wscp.props, and change the lines below as follows: 14 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

29 com.ibm.corba.loginsource=properties com.ibm.corba.loginuserid=<userid> com.ibm.corba.loginpassword=<password> where <userid> is the user ID for IBM WebSphere Application Server and <password> is the password for the user. Ensure that the user ID and password are in plain text and not encrypted. 3. Save and close the file. Enabling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server to communicate with IBM WebSphere Application Server on a non-default port Objective To configure local endpoints to use a non-default port when IBM WebSphere Application Server is using a non-default port. Background information If you are using a non-default port for IBM WebSphere Application Server, you must specify this port information in order to communicate with the IBM WebSphere Application Server object. You do this by changing the port setting in the sas.wscp.props or.wscprc file. You must do this whether or not WebSphere security is enabled. Required authorization role No Tivoli role is required. The procedure below is performed on the endpoint system, not the Tivoli management region server. Administrator authority is required on the IBM WebSphere Application Server system. Before you begin If WebSphere security is enabled, configure client side security, as described in Configure client side WebSphere security on page 14. When you finish Enable performance monitoring on your IBM WebSphere administration and application servers. See Enabling performance monitoring on page 16 for more information. Procedure Use one of the following procedures to change the default port used by endpoints. If you have WebSphere security enabled, use these steps. 1. Open the sas.wscp.props file in a text editor. Note: If you have not already created this file, copy the sas.client.props file to sas.wscp.props, as described in Configure client side WebSphere security on page Add the following line: wscp.hostport=<port_number> where <port_number> is the same value specified for property com.ibm.ejs.sm.adminserver.bootstrapport in $WAS_HOME/bin/admin.config. 3. Save and close the file. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 15

30 If you are not using WebSphere security, you do not need to create the sas.wscp.props file. Instead, you can create the.wscprc file in the USERHOME directory. For information about creating this file, see the WebSphere InfoCenter. 1. Open the.wscprc file in a text editor. 2. Set the port number as follows: wscp.hostport=<portnumber> where <portnumber> is the port that you want to use. 3. Save and close the file. Enabling performance monitoring Objective To enable IBM WebSphere Application Server to collect performance data Background information Before IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server can monitor performance data for your IBM WebSphere administration and application servers, you must have the IBM WebSphere Application Server collect performance data. Data is collected for the performance categories, each of which contains counters. Each performance category has an instrumentation level, which determines which counters are collected for the category. Each category has a rating (maximum, high, medium, low, or none) that indicates the impact on an application s performance if data is collected for the counters in that category. For information about WebSphere performance monitoring, see the WebSphere InfoCenter. Required authorization role No Tivoli role is required. The procedure below is performed on the endpoint system, not the Tivoli management region server. Administrator authority is required on the IBM WebSphere Application Server system. Before you begin None When you finish If you want to gather Java Virtual Machine Profiler Interface (JVMPI) metrics with a custom resource model, enable JVMPI data reporting. See Enabling JVMPI data reporting on page 121 for more information. The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models do not gather this information. You can create other resource models to gather this data. For information, see the IBM Tivoli Monitoring Workbench User s Guide. Procedure To specify or change the instrumentation level for a resource, do the following: 1. Right-click the application server in the hierarchical tree located in the left panel of the IBM WebSphere Administrator s console. 2. Click Properties in the pop-up menu. The Properties notebook is displayed. 3. Click the Services tab. 4. From the list of services, select Performance Monitoring Settings and click the Edit Properties box. The Performance Monitoring Settings panel is now displayed. 5. Select Enable performance counter monitoring. 16 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

31 6. Select a resource and choose the appropriate monitoring level. See Table 4 for the minimum monitoring levels. 7. When you are finished, click OK. You do not need to restart the application server. Notes: 1. Choosing an instrumentation level causes the same level to be applied recursively to all elements beneath the selected resource. To ensure that an instrumentation level is applied to the desired resource, expand the node and make sure that only the desired resource is selected before setting the level. 2. If you change a monitoring setting while the related resource model is running, the change is automatically picked up. You do not need to redistribute or restart the resource model. The following table lists the minimum monitoring levels for the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models. Table 4. Minimum performance monitoring levels for the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resource models Resource model Monitoring setting Minimum monitoring level Administration Server Status Not applicable Not applicable Application Server Status Not applicable Not applicable DB Pools Database Connection Pools High EJBs Enterprise Beans High HTTP Sessions Servlet Session Manager High JVM Runtime JVM Runtime Low Thread Pools Thread Pools High Transactions Transaction Manager Medium Web Applications Web Applications High Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects Objective To create IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects that represent your IBM WebSphere Application Server components. Background information The first step in managing IBM WebSphere Application Server components (administration server and application servers) is to create IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects to represent the components that you want to manage. There are two kinds of IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects: v WSAdministrationServers that represent IBM WebSphere Administration servers For z/os systems, a WSAdministrationServer represents all System Management Server Instances. v WSApplicationServers that represent IBM WebSphere application servers For z/os systems, a WSApplicationServer represents an application server instance. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 17

32 You can create these objects in one of three ways: v Using the wwebsphere c command v Using the Tivoli Framework GUI v Using the Discover_WebSphere_Resources task For z/os proxy endpoints, this task creates the authentication key for z/os systems. If you don t use this task, you have to run the Check_Administration_Server_Status task to create the key. Note: The Discover_WebSphere_Resources task creates objects based on the current IBM WebSphere Application Server configuration. The other mechanisms require you to manually enter information in the IBM WebSphere Application Server configuration. Required authorization role websphereappsvr_admin or websphereappsvr_super for the wwebsphere c command and for the Tivoli desktop websphereappsvr_super for the Discover_WebSphere_Resources task Note: If you are using NetView 1.3, the user ID that you use to run the Discover_WebSphere_Resources task must be a USS super user (UID=0). Before you begin Any local system that you want to manage with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server must have a supported version of IBM WebSphere Application Server installed and must be configured as a Tivoli endpoint. See the Tivoli Management Framework Reference Manual for information about configuring Tivoli endpoints. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for supported versions of IBM WebSphere Application Server. Ensure that the IBM WebSphere administration server is running. Carefully consider the length of the name of the policy region with which the object will be associated. Because the policy region name is used as part of the object label, a long policy region name can cause problems with your endpoint label. For example, if you integrated with Tivoli Business System Manager, a long endpoint label will be truncated in the Tivoli Business System Manager console. Additionally, you should not use the double-byte characters for the policy region name because the label will not display correctly on the Tivoli Business System Manager console. If you are going to log data in Tivoli Enterprise Data Warehouse, do not use an apostrophe ( ) in the name of your policy region. When you finish Subscribe servers to profile managers, if needed. Distribute resource models to the new IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects so that you can monitor their status and performance. Note: If you used the Discover_WebSphere_Resources task to create objects, they are automatically subscribed to profile managers. For z/os proxy endpoints, all application servers are subscribed to all profile managers, regardless of whether or not they have servlets or EJBs. 18 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

33 For z/os systems, ensure that appropriate z/os permissions are present on any directory created by the Discovery_WebSphere_Resources task. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for more information. Procedure You can perform this procedure from the command line, from the Tivoli desktop, or as a task. Note: If you experience problems performing this procedure, see Appendix E, Problem determination, on page 127 for information about log files and common problems that might occur. You can also see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for information about messages. Command Line: Use the wwebsphere command with the c parameter to create objects. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for more information. Tivoli desktop: Follow these steps to create objects from the Tivoli desktop: 1. From inside the Monitoring for WebSphere Application Server policy region or a sub-region, click Create. 2. Select the type of object you want to create: WSAdministrationServer or WSApplicationServer. 3. Click Set & Execute. 4. If you selected WSAdministrationServer, complete the following fields on the Create WSAdministrationServer window: WebSphere Application Server Location (Required) Select Local if IBM WebSphere Application Server is installed locally, on the endpoint host, or z/os if IBM WebSphere Application Server is installed on a z/os system. Node Name (Required) Type the name of the node for the IBM WebSphere administration server that this object will represent. This field is required with a local IBM WebSphere Application Server and is not used with WebSphere for z/os. Fully Qualified Host Name (Required) Type the fully qualified host name for the IBM WebSphere administration server. For example, hpx1.raleigh.tivoli.com is the fully qualified host name for the hpx1 IBM WebSphere administration server. This field is required with a local IBM WebSphere Application Server and is not used with WebSphere for z/os. WebSphere Admin Port (Optional) Type the port number used to open a communication channel with the IBM WebSphere administration server. The default value is 900. This field is not used with WebSphere for z/os. WebSphere OS Type (Optional) Type the operating system running on the endpoint, such as AIX. This field is optional. With WebSphere for z/os, the operating system type is set to zos regardless of the value of this field. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 19

34 WebSphere Security Enabled (Optional) Specify whether or not WebSphere security is enabled on the endpoint. If security is enabled, provide the name of the security properties files in the WebSphere Security Properties File field. This field is not used with WebSphere for z/os. WebSphere Security Properties File (Conditionally required) Type the name of the security properties file. If you enter only the file name, and not the full path, the file is assumed to be in the $WAS_HOME/properties directory on the endpoint. This field is required if WebSphere security is enabled. This field is not used with WebSphere for z/os. z/os Sysplex Name Type the name of the z/os sysplex as configured in WebSphere for z/os. This field is required with WebSphere for z/os and is not used with a local IBM WebSphere Application Server. z/os Fully Qualified Host Name Type the name of the z/os host where IBM WebSphere Application Server operations can be performed and information can be gathered for the entire sysplex. This host must be accessible through NetView from the z/os system where the NETCONV connection is made. This field is required with WebSphere for z/os and is not used with a local WebSphere Application Server. Fully Qualified Endpoint Host Name Type the fully qualified host name of the Tivoli endpoint. This field is required with WebSphere for z/os and is not used with a local IBM WebSphere Application Server. Endpoint Name (Required) Select the Tivoli endpoint on which the IBM WebSphere administration server is running. Managed Node Name (Optional) Type the name of the managed node where you want to create the object. By default, the object is created on the managed node currently hosting the gateway that manages the selected endpoint. Type a different managed node name to create the object on a different node. WebSphere Version (Required) Type the version of IBM WebSphere Application Server running on the endpoint. The format must be dot separated For example, if you are running IBM WebSphere Application Server version on the endpoint, type WebSphere Install Path (Required) Type the full path to the directory on the endpoint where IBM WebSphere Application Server is installed. Use UNIX style slashes for the directory. For example, use c:/websphere/appserver instead of c:\websphere\appserver. This field is required with a local IBM WebSphere Application Server and is optional with WebSphere for z/os. 20 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

35 Note: Do not use a slash (/ or \) at the end of the installation location. The default installation location for the different platforms is as follows: v Windows C:/WebSphere/AppServer v AIX /usr/websphere/appserver v Linux /usr/websphere/appserver v OS/400 /qibm/proddata/xxxxxx where xxxxxx specifies the version of IBM WebSphere Application Server running on the system v Solaris and HP /opt/websphere/appserver v z/os /usr/lpp/websphere 5. If you selected WSApplicationServer, complete the following fields: Application Server Name (Required) Type the application server name for this object. z/os Application Server Instance Name (Required) Type the application server instance name for this application server object. This is a required field with WebSphere for z/os. Leave this field blank with a local WebSphere Application Server. Administration Server Label (Required) Type the Tivoli object label for the existing IBM WebSphere administration server object with which this application server object is associated. For example, mysphere_pr@sandhill. Endpoint Name (Required) Select the Tivoli endpoint on which the IBM WebSphere application server is running. Has Web Module (Optional) Select this if the IBM WebSphere application server is using the Web Module and is capable of hosting servlets. Has EJB Module (Optional) Select this if the IBM WebSphere application server is using the Enterprise JavaBeans (EJB) module and is capable of hosting EJBs. Managed Node Name (Optional) Type the name of the managed node where you want to create the object. By default, the object is created on the managed node currently hosting the gateway that manages the selected endpoint. Type a different managed node name to create the object on a different node. z/os System Name The name of the z/os system on which this application server instance runs, as configured in WebSphere for z/os. This field is required with WebSphere for z/os. Leave this field blank with a local IBM WebSphere Application Server. 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 WebSphere Application Server policy region. 2. Double-click the WebSphere Application Server Utility Tasks icon. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 21

36 3. Double-click the Discover_WebSphere_Resources task icon and complete the Execute Task window. Select the managed node on which you want to run the Discover_WebSphere_Resources task. 4. Select Display on Desktop to display the output of the task on the desktop. 5. Increase the timeout value because the Discover_WebSphere_Resources task takes a considerable amount of time to finish. Allow 300 seconds for each endpoint on which you are running the Discover_WebSphere_Resources task. 6. Click Execute or Execute and Dismiss to display the Discover_WebSphere_Resources window. 7. Complete the following fields on the Discover_WebSphere_Resources window: Figure 1. The Discover_WebSphere_Resources task execution window Policy Region Name (Required) Enter the name of the policy region in which to create the discovered IBM WebSphere administration server objects. If this policy region does not exist, it is created. Install path of WebSphere Application Server (Conditionally required) The IBM WebSphere Application Server installation path on the endpoint. If you leave this field blank, the default WebSphere Application Server installation path is used. Note: Do not use a slash (/ or \) at the end of the installation location. Endpoints (Required) The specific endpoints on which to search for objects. Click Choices to 22 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

37 display all endpoints available to search. Select endpoints that either run IBM WebSphere Application Server 4.x.x or that connect to a z/os system that is running IBM WebSphere Application Server 4.x.x for z/os. Security Properties File (Conditionally required) If you have security enabled on your IBM WebSphere administration server, this task requires a security properties file. Enter the full path and file name of the security properties file. If you enter only the file name, the file is assumed to be in the $WAS_HOME/properties directory on the endpoint. This field does not apply to WebSphere for z/os and is ignored if z/os is selected as the location. Object destination (Managed Node Name) (Optional) Specifies where to create the objects that correspond to the resources discovered. The default destination is the managed node that hosts the gateway of the endpoint currently being discovered. This field does not apply to WebSphere for z/os and is ignored if z/os is selected as the location. WebSphere Node name if different than host name (Optional) If the endpoint host name is not the same as the IBM WebSphere node name, enter the IBM WebSphere node name for the endpoint you are selecting. This field does not apply to WebSphere for z/os and is ignored if z/os is selected as the location. WebSphere Application Server Location Indicates where the IBM WebSphere Application Server is located: on a local endpoint or a z/os system. Select Local if the IBM WebSphere Application Server is located on the local endpoint. Select z/os if the IBM WebSphere Application Server is located on a z/os system. Address type Select IP Host if you use TCP/IP to communicate between the z/os systems. Select SNA Domain if you use Systems Network Architecture (SNA) to communicate between the z/os systems. Hostname/IP address or SNA name of z/os system Indicates the specific z/os system. If you use TCP/IP, type the hostname or IP address of the z/os system. If you use Systems Network Architecture (SNA), type the SNA NetView domain name of the z/os system. 8. Click Set & Execute to run the Discover_WebSphere_Resources task. For more information on the Discover_WebSphere_Resources task, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 23

38 Configuring z/os proxy endpoints Before you can monitor your z/os resources, you must configure the proxy endpoints to work with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. Configuring the proxy endpoints includes the following steps: Table 5. Guidelines for configuring z/os proxy endpoints Goal Where to find information Link to a JRE for each endpoint. IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide Enable the gathering of data metrics. Configuring metric collection for z/os systems Configure the authentication key on a sysplex. Start the z/os data collector. Update the IBM WebSphere application server environment. Configure the Tivoli Enterprise Console z/os event adapter (optional). Creating an authentication key for a sysplex on page 27 Setting up and starting the z/os Data Collector on page 28 Updating the IBM WebSphere application server environment on page 32 Configuring the Tivoli Enterprise Console z/os adapter on page 46 Ensure that NETCONV is connecting the z/os systems to the corresponding proxy endpoints. To do this, type the following command from the NetView operator: netconv action=list opid=all You should see the endpoint listed here. Note: IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides an agent inside IBM WebSphere Application Server that monitors updates to the configuration and registry. The agent checks for changes every 5 minutes. This provides the ability to dynamically enabled or disable metrics gathering, as well as changing the logging or trace settings for the product. Configuring metric collection for z/os systems Objective To configure the metrics collected from z/os systems for performance monitoring. Background information To collect data from z/os systems, you must enable the collection of metrics by running the Enable_Metrics_Gathering task, which provides the following options: Enable resources by level Enables the collection of metrics for WebSphere Application Server performance categories. See Enabling performance monitoring on page 16 for information about these categories and their corresponding levels. Enable resource by resource model Enables the metrics required for a specific resource model. Enable resource by metric Enables specific metrics on the z/os system. Because some metrics are enabled and disabled as a group, enabling one metric might automatically enable other metrics. 24 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

39 If you are not sure if a metric is currently enabled on a system, run the Enable_Metrics_Gathering task to enable the metric. If it is already enabled, the metric remains enabled. Required authorization role websphereappsvr_admin The NetView operator ID that you use must have write permissions for the /var/itmwas directory. Before you begin Run the Discover_WebSphere_Resources task to create proxy endpoints for your z/os systems. See Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page 17 for more information. When you finish Configure the Data Collector. See Setting up and starting the z/os Data Collector on page 28 for information. Ensure that appropriate z/os permissions are present on any directory created by the Enable_Metrics_Gathering task. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for more information. Procedure Perform the following steps to enable metrics using the Enable_Metrics_Gathering task: 1. From the Tivoli desktop, double-click the Monitoring for WebSphere Application Server policy region. 2. Double-click the WebSphere Application Server Utility Tasks icon. 3. Double-click the Enable_Metrics_Gathering task icon and complete the Execute Task window. 4. Select Display on Desktop to display the output of the task on the desktop. 5. Increase the timeout value because the Enable_Metrics_Gathering task takes a considerable amount of time to finish. Allow 300 seconds for each endpoint on which you are running the task. 6. Click Execute or Execute and Dismiss to open the Enable_Metrics_Gathering window. 7. Complete the following fields in the Enable_Metrics_Gathering window: Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 25

40 Figure 2. The Enable_Metrics_Gathering task execution window z/os System Information Provide information about the specific z/os system for which you want to enable metrics gathering. z/os System Name Type the name of the z/os system. If you use TCP/IP to communicate between your z/os systems, type the fully qualified host name or IP address for the z/os system. If you use SNA, type the SNA domain name for the z/os system. Protocol Specify the communications protocol you use to communicate between your z/os systems: IP or SNA. Enable resource by level Select the WebSphere Application Server monitoring level that you want to enable: v High v Medium v Low Enable resources by resource model Select the resource model or models for which you want to enable 26 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

41 metrics gathering. For information about the specific resource models, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Note: Enabling a resource model does not disable any other resource models that are currently enabled on the system. Enable resource by metric Specify the metric or metrics that you want to enable. Because some metrics are enabled and disabled as a group, enabling one metric might automatically enable other metrics. See the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server providers appendix in the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for information about specific metrics. 8. Click Set & Execute to run the Enable_Metrics_Gathering task. You can change the configuration of metric gathering by running the Enable_Metrics_Gathering task again or you can disable metrics by running the Disable_Metrics_Gathering task. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for information about the Disable_Metrics_Gathering task. Creating an authentication key for a sysplex Objective To configure security by creating an authentication key for a sysplex. Background information As performance monitors are collected for z/os systems, they are sent to resource models on the endpoint over a TCP/IP connection. The data sent over this connection is encrypted using SSL. The z/os system must be authenticated by the endpoint before the data metrics can be accepted. The authentication mechanism uses an identical secret value, or an authentication key, known by both the endpoint and the z/os system. This authentication key is created when you run either the Discover_WebSphere_Resources task or the Check_Administration_Server_Status task. The key is stored in a file, ITMWASSSK, on both the endpoint and the z/os system. On the endpoint, the file is located in $LCF_DATDIR; on the z/os system, the file is located in /var/itmwas. If IBM WebSphere Application Server has server instances running on more than one z/os system in the sysplex, the file is written only to the z/os system that was specified when the Discovery_WebSphere_Resources task was run. You must manually copy the file to other z/os systems in the sysplex before metrics can be sent to the resource models running on the endpoint. If you need to generate a new authentication key (for instance, if the existing value is compromised), you can force the creation of a new value by deleting the ITMWASSSK file on the endpoint and the z/os system or systems and running the Check_Administration_Server_Status task. Required authorization role No Tivoli role is required. Before you begin Run the Discover_WebSphere_Resources task to create the key. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 27

42 When you finish Set up the z/os Data Collector. See Setting up and starting the z/os Data Collector for information. Procedure Copy the /var/itmwas/itmwasssk file from the z/os system in the sysplex that you specified when you ran the Discover_WebSphere_Resources task to the /var/itmwas directories on the other z/os systems in the sysplex. Setting up and starting the z/os Data Collector Objective To start the z/os Data Collector to begin gathering information from z/os systems. Background information The z/os Data Collector is a Java program that runs on the z/os system. The Data Collector uses a file, itmwas.conf, on both the proxy endpoint and the z/os system for communication between the two systems. If you used the Discover_WebSphere_Resources task to create the proxy endpoint, this file was created on the proxy endpoint and moved to the appropriate location automatically. If you used any other method to create your proxy endpoint, you must copy this file from c:\tivoli\bin\lcf_bundle.40\bin\generic_unix\tme\wsappsvr\cfg to the $LCF_DATDIR/LCFNEW/Tmw2k/Unix/Classes/WebSphereAS directory. Note: This product attaches to WebSphere for z/os through the JVM Profiler Interface (JVMPI). The interface is limited to attaching at most one product to WebSphere for z/os. For more information on JVMPI, see Required authorization role No Tivoli role is required. Before you begin Run the Enable_Metrics_Gathering task. See Configuring metric collection for z/os systems on page 24 for more information. When you finish Update the IBM WebSphere application server with information about IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks. See Updating the IBM WebSphere application server environment on page 32 for more information. Procedure Use the following steps to set up and start the Data Collector: 1. On a z/os system, copy the itmwas.conf file from /usr/lpp/itmwas/v5r1m1/etc to /var/itmwas/cfg. 2. Edit the new itmwas.conf file. 3. In the first section of the file, change the configuration of the Data Collector. You have the following options: Note: Each of these options is preceded by com.ibm.tivoli.ws IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

43 collector.hostname Specifies the host where the Collector is running. The default value is collector.port Specifies the port on which the Collector listens for connections from agents. This setting is used by both the Collector and the agents. collector.transmissioninterval Specifies the interval, in seconds, in which the collector attempts to send data to the listed endpoint. collector.logging.level Specifies the level of logging for the collector. You have the following choices: v WARN v INFO v DEBUG_MIN v DEBUG_MID v DEBUG_MAX collector.logging.logdirectory Specifies the directory to which daily log files are written. For example: com.ibm.tivoli.ws390.collector.hostname= com.ibm.tivoli.ws390.collector.port=31173 com.ibm.tivoli.ws390.transmissioninterval=30 com.ibm.tivoli.ws390.collector.logging.level=info com.ibm.tivoli.ws390.logging.logdirectory=/var/itmwas/log 4. In the second section of the file, add your proxy endpoint information as follows: com.ibm.tivoli.ws390.endpoint.hostname=<endpoint_hostname> com.ibm.tivoli.ws390.endpoint.port=<port> where <endpoint_hostname> is the host name of the proxy endpoint and <port> is the port. The default port is Note: If you use any port other than the default, you must also change the port setting in the itmwas.conf file located on the proxy endpoint. 5. Save and close the file. 6. Repeat these steps for each image in the sysplex where you are running IBM WebSphere Application Server and want to monitor it. 7. Copy the itmplugin.conf file from /usr/lpp/itmwas/v5r1m1/etc to /var/itmwas/cfg. 8. Edit the itmplugin.conf file to specify logging and trace settings. The values specified in this file apply to all server instances. Note: You can optionally put this file in /var/itmwas/cfg/<plex>/<server>/<instance>, where <plex> isa specific sysplex, <server> a specific server, and <instance> a single instance. The values in this file apply only to the specific instance. 9. In the first section of the file, configure the WebSphere plugin settings. You have the following choices: Note: Each of these options is preceded by com.ibm.tivoli.ws390.plugin. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 29

44 threadsummaryinterval Specifies the interval, in seconds, during which metrics for a particular thread are combined into a record that details the metrics for the entire server region. regionsummarymultiple Specifies the interval, in terms of number of threadsummaryintervals, during which the agent sends its data to the Collector. eventthreshold Defines the number of events that have to occur to preempt the threadsummaryinterval. logging.level Specifies the level of logging for the WebSphere plugin. You have the following choices: v WARN v INFO v DEBUG_MIN v DEBUG_MID v DEBUG_MAX The log files created are daily log/trace files that are written to /var/itmwas/log/<plex>/<server>/<instance>. For example: com.ibm.tivoli.ws390.plugin.threadsummaryinterval=5 com.ibm.tivoli.ws390.plugin.regionsummarymultiple=6 com.ibm.tivoli.ws390.plugin.eventthreshold=64000 com.ibm.tivoli.ws390.plugin.logging.level=info 10. In the second section of the file, change the configuration for trace configuration. You can specify the level of tracing to be done (for example, tracing warning conditions), as well as specific events to trace. You must set a trace level and at least one trace filter in order to perform tracing. By default, all trace filters are collected. To trace all errors, specify traceerror and all of the trace filters. You have the following choices: Trace levels: traceerror Specifies whether to trace error conditions. traceexceptionstack Specifies whether to trace exception stacks. tracewarning Specifies whether to trace warning conditions. traceinfo Specifies whether to trace informational messages. Trace filters: traceejbs Specifies whether to trace EJB events. tracetransactions Specifies whether to trace Transaction events. 30 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

45 tracedatasources Specifies whether to trace DataSource events. traceservlets Specifies whether to trace Servlet events. tracesessions Specifies whether to trace Session events. tracethreadpool Specifies whether to trace ThreadPool events. Note: Each of these options is preceded by com.ibm.tivoli.ws390.probes.. For example: com.ibm.tivoli.ws390.probes.traceerror=true com.ibm.tivoli.ws390.probes.tracewarning=true com.ibm.tivoli.ws390.probes.traceexceptionstack=true com.ibm.tivoli.ws390.probes.traceinfo=false com.ibm.tivoli.ws390.probes.traceejbs=true com.ibm.tivoli.ws390.probes.tracetransactions=true com.ibm.tivoli.ws390.probes.tracedatasources=true com.ibm.tivoli.ws390.probes.traceservlets=true com.ibm.tivoli.ws390.probes.tracesessions=true com.ibm.tivoli.ws390.probes.tracethreadpool=true 11. Save and close the file. 12. Start the Data Collector by running the collectorstart script in the /usr/lpp/itmwas/v5r1m1/scripts directory. To run this script in the background, issue the following command: collectorstart & To redirect the output and error messages from the script to a file (instead of displaying them on the screen), issue the following command: collectorstart > /var/itmwas/stdout_err 2>&1 & Output and error messages are written to a file in the /var/itmwas directory. You can also start the Data Collector as a started task. Use the following steps to create a started task: 1. Create a user ID to be used for this task and give it the necessary authority. You can use any user ID to run the z/os Data Collector. If the BPX.DAEMON facility class is defined, the user ID must have read access to this class. The default group for the user ID can be any group that permits OMVS operations. The user ID, ITDSRV, in the example that follows is a member of the OMVSGRP group and has RACF SPECIAL authority (required to run the RACF commands). ADDUSER ITDSRV DFLTGRP(OMVSGRP) OMVS(UID(1) PROGRAM ( /bin/sh ) HOME( /u/itdsrv ) ) Note: If the UID of the user ID is not zero (0), all console messages produced by the z/os Data Collector are accompanied by a BPXM023I message that identifies the user writing to the console. 2. Allocate the OMVS home directory for the user ID, or modify the sample JCL to direct stdout and stderr to another location in the HFS file system. Ensure that the user ID has read and write access to that location: PERMIT BPX.DAEMON CLASS(FACILITY) ID (ITDSRV) ACCESS(READ) Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 31

46 Note: Run this command only if you have the BPX.DAEMON class defined. 3. Define the started task. In this procedure and sample startup procedure, the started task is named ITDSRV, but you can use any name for the task. To define the started task for the user ID you just created, use the following RACF commands: RDEFINE STARTED ITDSRV.** STDATA(USER(ITDSRV)) SETROPTS RACLIST(STARTED) REFRESH A sample JCL is provided that you can use for the started task. To use this sample JCL, copy the <ITDHLQ>.ITDSAMP(ITDSRV) member from the sample dataset into a PROCLIB dataset in your PROCLIB concatenation. Updating the IBM WebSphere application server environment Objective To update the IBM WebSphere application server environment with information about IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. Background information Before you can run IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server monitoring on your z/os systems, you must update the IBM WebSphere application server environment with information about IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. Perform this procedure only for the application servers that you want to monitor. Required authorization role WebSphere administration authority Before you begin Ensure that the System Management User Interface is correctly installed and configured. See the WebSphere Application Server V4.0.1 for z/os and OS/390: System Management User Interface guide for information about installation and configuration. When you finish Set up the IBM Tivoli Monitoring environment and distribute resource models to the proxy endpoints. See Setting up the IBM Tivoli Monitoring environment on page 33 for more information. Procedure You can perform this procedure using a supplied script or manually, using the IBM WebSphere Application Server System Management User Interface. To run this procedure as a script, run the itmwasappserverupdate script, located in the /usr/lpp/itmwas/v5r1m1/scripts directory: itmwasappserverupdate [-a] [-s <server>] [-clean] [-i <instance>] <conversationname> You can specify the following parameters: -a Specifies that the conversation should be committed and activated after it has been created and its environment has been updated. Note: If you do not specify the a parameter, the conversation is created but not activated. This enables you to see what the script does before you activate it. 32 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

47 -s <server> Specifies to update only the environment for this server. If omitted, all server environments are updated. clean Specifies to remove IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server paths and Java options from the new conversation rather than adding them. -i <instance> Specifies to update only the environment for only this server instance. This must follow a -s option. If omitted, all instances for the previously specified server are updated. <conversationname> Specifies the name of the conversation to create. Perform the following steps to update the IBM WebSphere application server from the System Management User Interface: 1. Log in to the System Management User Interface. 2. Add a new conversation and modify the application server. 3. Append /usr/lpp/itmwas/v5r1m1/lib to the LIBPATH. 4. Append the following to the CLASSPATH: /usr/lpp/itmwas/v5r1m1/lib/itmwas.jar:/usr/lpp/itmwas/v5r1m1/lib/itmmsgs.jar: \ /usr/lpp/itmwas/v5r1m1/lib/conduit.jar:/usr/lpp/itmwas/v5r1m1/lib/probes.jar: \ /usr/lpp/itmwas/v5r1m1/jlog.jar: 5. Add a new attribute: WAS_JAVA_OPTIONS. This attribute has the following value: Xoptionsfile=/var/itmwas/cfg/<plex>/<server_name>/<instance_name>/java.conf, where plex> is the specific sysplex, <server_name> is the specific application server, and <instance_name> is the specific application server instance. This value changes for each application server to point to its version of java.conf. 6. Add a new attribute: JVM_BOOTCLASSPATH. This attribute has the following value: /usr/lpp/itmwas/v5r1m1/jiti/jiti.jar 7. Add a new attribute: WS_EXT_DIRS. This attribute has the following value: /usr/lpp/itmwas/v5r1m1/wsextdirs 8. Validate, commit, complete, and activate the conversation, and exit the interface. Setting up the IBM Tivoli Monitoring environment Objective To set up the environment required to run IBM Tivoli Monitoring commands. Background information In order to issue IBM Tivoli Monitoring commands such as wdmcmd and wdmlseng in a command window, you first need to source in the Tivoli environment. Required authorization role On UNIX, the user must have root privileges; on Windows, the user must have membership in the Administrators group. Before you begin None Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 33

48 When you finish None Procedure You can perform this procedure from the command line. To set up the environment, enter one of the following commands at the command prompt: 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:. /etc/tivoli/lcf/x/lcf_env.sh For C shell: source /etc/tivoli/lcf/x/lcf_env.csh v v where x is the number of the endpoint installed on the machine. On a Windows managed node, enter: %SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd On a Windows endpoint, enter: %SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd Distributing profiles where x is the number of the endpoint installed on the machine. You can distribute profiles from either the Tivoli desktop or by using MDist2. Distributing profiles from the Tivoli desktop Objective To distribute profiles to specified subscribers. Background information You can distribute profiles to the following groups: All levels of subscribers Distributes the profile to all subscribers in the hierarchy. Next level of subscribers Distributes the profile only to the subscribers named in the Distribute to These Subscribers: scrolling list of the Distribute Profile window. This option does not distribute to subscribers at lower levels of the hierarchy. Perform the distribution process from profile managers at more than one level to reach all the profile endpoints if a profile manager with subscribers resides at the next lower level. Consider the following example. You have a profile in which a dataless profile manager is subscribed to a profile manager, and the dataless profile manager has a subscribed endpoint. If you distribute to the next level of subscribers, the profile manager distributes the profile only to the dataless profile manager. If you 34 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

49 distribute to all levels of subscribers, the profile manager distributes the profile to the dataless profile manager and to the endpoint. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 and Adding customized resource models to profiles on page 115 for information. You can also use the predefined profile managers and profiles created during installation. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailed information about each resource model. When you finish None Procedure You 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 WebSphere Application 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 in which you want to customize a resource model. 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 Select one of the Distribute Will options based on the following descriptions: v Preserve modifications in subscribers copy of the profile retains changes to existing resource models in each copy of the profile. v Make subscribers profile an EXACT COPY of this profile overwrites the subscriber s profile with an exact copy of the profile being distributed. If you edit the configuration of a resource model in the subscriber s copy, those changes 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. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 35

50 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 Subscribers scrolling list is either a profile manager or a supported Tivoli management agent endpoint. IBM Tivoli Monitoring does not support other types of endpoints. 6. Click one of the following: Distribute & Close Distributes the profile immediately, closes the Distribute Profile window, saves the settings you made, and returns to the IBM Tivoli Monitoring Profile window. Distribute Distributes the profile immediately, saves the settings you made, and leaves the Distribute Profile window open. Schedule Schedules the distribution of the profile with the Tivoli Scheduler. For details about using the Tivoli Scheduler, refer to the Tivoli Management Framework User s Guide. You can also see Scheduling a job on page 89 for more information. 7. Click Profile Close to close the IBM Tivoli Monitoring Profile window. Distributing profiles using MDist2 Objective To circulate copies of the monitoring profile to subscribers while using MDist2 so that administrators and users can activate the monitoring process. Background information IBM Tivoli Monitoring uses Multiplexed Distribution (MDist2) to perform asynchronous profile data transfers through a hierarchy of repeaters. MDist2 returns a sequence of responses containing the distribution status from each endpoint to the application initiating the distribution. These responses are sent back to IBM Tivoli Monitoring in a log file, on the MDist2 command line, or through the MDist2 GUI. IBM Tivoli Monitoring uses the following MDist2 functions: Asynchronous delivery IBM Tivoli Monitoring submits a distribution request and immediately receives a distribution identifier and confirmation that the distribution is in progress. MDist2 uses the callback function to send the final distribution status for each endpoint when it completes each endpoint distribution instead of waiting until all endpoints are distributed. Assured delivery Assures that distributed profiles are delivered to the endpoints when there are network interruptions, computer shutdowns, or disconnected endpoints. Assured delivery tries to reestablish the connections until it is either successful or the distribution time expires. Check-point and restart Assures that an interrupted data stream resumes from the last successful checkpoint. You do not have to resend all the IBM Tivoli Monitoring Profile data when the distribution resumes, but only the data that was not sent when the interruption occurred. 36 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

51 Data depoting Stores segments of the profile at a depot close to the endpoint so the endpoints can retrieve the data from the depot instead of from the source host. This reduces network traffic and speeds up the distribution. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 and Adding customized resource models to profiles on page 115 for information. You can also use the predefined profile managers and profiles created during installation. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailed information about each resource model. When you finish None Procedure You can perform this procedure from the command line or from the Tivoli desktop. Command Line: Use the wdistrib command to distribute the profile to the subscribers of the profile manager. This command updates subscriber databases and configuration files. If no subscriber is specified, wdistrib updates all subscribers. Refer to the Tivoli Management Framework Reference Manual for more information about the wdistrib command. 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 WebSphere Application 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 in which you want to customize a resource model. 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 Select one of the Distribute Will options based on the following descriptions: v Preserve modifications in subscribers copy of the profile retains changes to existing resource models in each copy of the profile. Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 37

52 v Make subscribers profile an EXACT COPY of this profile overwrites the subscriber s profile with an exact copy of the profile being distributed. If you edit the configuration of a resource model in the subscriber s copy, those changes 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 Subscribers scrolling list is either a profile manager or a supported Tivoli management agent endpoint. IBM Tivoli Monitoring does not support other types of endpoints. 6. Click one of the following: Distribute & Close Distributes the profile immediately, closes the Distribute Profile window, saves the settings you made, and returns to the IBM Tivoli Monitoring Profile window. Distribute Distributes the profile immediately, saves the settings you made, and leaves the Distribute Profile window open. Schedule Schedules the distribution of the profile with the Tivoli Scheduler. For details about using the Tivoli Scheduler, refer to the Tivoli Management Framework User s Guide. You can also see Scheduling a job on page 89 for more information. 7. Click Profile Close to close the IBM Tivoli Monitoring Profile window. 38 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

53 Chapter 3. Setting up the Tivoli Enterprise Console for event correlation This chapter provides information on setting up the Tivoli Enterprise Console for event correlation. Setting up event correlation requires the following tasks: 1. Configuring the Tivoli Enterprise Console event server on page Configuring the Tivoli Enterprise Console adapter for local systems on page Configuring the Tivoli Enterprise Console z/os adapter on page 46 Note: Before you can configure the event adapter, you must create Tivoli objects for your IBM WebSphere Application Server resources as described in Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page Filtering events on page 48 For information about the event classes and rules included with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server, see Appendix D, Event classes and rules, on page 123. For information about using Tivoli Enterprise Console, see the Tivoli Enterprise Console User s Guide. If you experience problem using the procedures in this chapter, see Appendix E, Problem determination, on page 127. You can also see the IBM Tivoli Monitoring for Web Infrastructure Reference Manual for information about any messages that you receive. Overview of the Tivoli Enterprise Console The Tivoli Enterprise Console provides the following functions: v Receiving events from various sources v Processing events using rules v Grouping events and delegating the groups selectively to administrators v Responding to events automatically v Viewing events at a console In the Tivoli Enterprise Console, rules (.rls) files contain the logic for correlation of events. BAROC (.baroc, Basic Recorder of Objects in C) files contain the defined event classes. The following list explains basic concepts of event management. For more information about the Tivoli Enterprise Console, refer to the Tivoli Enterprise Console User s Guide. Events An event is a structured piece of information. It carries information about itself, including the event class, event identity, severity, location (host where the event originated), and description. IBM Tivoli Monitoring uses events with resource models to verify the persistence of an indication over a period of cycles. 39

54 Note: Only non-tivoli Management Environment events are supported for the OS/400 endpoint adapter. Sources of Events The Tivoli Enterprise Console accepts events from many sources. For example, you can configure resource models to send events. Typically, Tivoli software is set up so that events are sent in response to changes in an application or system resource. Event Processing The Tivoli Enterprise Console uses rules to process events. A rule is made up of a set of logic statements. The rule determines what to do with the 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 drop insignificant events, escalate important events, create new events, or respond to defined relationships of multiple events (event correlation). It can also close an old event when a new event indicates that the original condition is resolved. Event Grouping The Tivoli Enterprise Console can filter events into event groups. These event groups are typically organized by function but can also be organized by other criteria, such as location or organizational jurisdiction. Event groups are especially useful for subdividing all Tivoli Enterprise Console events into manageable chunks. Administrators can be assigned to one or more event groups. Viewing Events The Tivoli Enterprise Console includes a console where administrators can watch for incoming events and respond to them. The Tivoli Enterprise Console can filter out normal events, respond automatically to anticipated problems, and forward only those events that require human intervention. Responses to Events The Tivoli Enterprise Console normally provides automatic responses to many common events, either by executing response programs or by executing Tivoli tasks. For example, you can set up a response to the event that is received when a server becomes unavailable. The specific response can inform an administrator or attempt automatic restarts of the server, or a combination of both. You cannot use the Tivoli Enterprise Console automatic response mechanism with this product. However, you can write Tivoli Enterprise Console rules that accomplish the same thing. Configuring the Tivoli Enterprise Console event server Objective To set up your Tivoli Enterprise Console event server to process IBM WebSphere Application Server events. Background information You must set up the event server before events can be sent to Tivoli Enterprise Console. Use the Configure Event Server task to set up the Tivoli Enterprise Console event server. 40 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

55 The Configure_Event_Server task performs the following actions: v Imports the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server event classes and rule set v Imports the IBM Tivoli Monitoring event classes (if they are not already present) v Imports the Tivoli Business Systems Manager rule set, if appropriate v Compiles the rule base to incorporate new classes and rules v 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 Tivoli management region. When you have interconnected Tivoli management regions, run the Configure Event Server task against each Tivoli management region that contains a Tivoli Enterprise Console event server. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server includes the following sets of event classes and rules specific to IBM WebSphere Application Server: v ITMWAS_Events v ITMWAS_TEC_Adapter_Event v Events for each resource model, such as the WebSphereAS_AdminServer_Down event Note: If the Tivoli Enterprise Console event server machine is also a z/os proxy endpoint, then the Configure_Event_Server task will automatically load a rule set to forward events to Tivoli Business System Manager, because Tivoli Business Systems Manager Event Enablement is a prerequisite for proxy endpoints. If you do not want events forwarded or do not have a Tivoli Business System Manager server, delete the itmwas_forward_tbsm rule set from your rule base using the following steps: 1. Remove the itmwas_forward_tbsm rule from the rule set: wrb -delrbrule itmwas_forward_tbsm -force <rule_base> wrb -deltgtrule itmwas_forward_tbsm EventServer <rule_base> 2. Compile and load the rule set. For information, see the Tivoli Enterprise Console documentation. Required authorization role senior Before you begin None When you finish Configure the Tivoli Enterprise Console event adapter. For more information, see Configuring the Tivoli Enterprise Console adapter for local systems on page 43. Configure Tivoli Business Systems Manager to receive events. See Chapter 4, Integrating with Tivoli Business Systems Manager, on page 51 for more information. Procedure You can run this procedure from the command line or the Tivoli desktop. Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 41

56 Command line: Use the wruntask command to run the Configure_Event_Server task. For the CLI syntax for this task, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Tivoli desktop: Follow these steps to perform this procedure from the Tivoli desktop: 1. From the Tivoli desktop, double-click the Monitoring for WebSphere Application Server policy region. 2. Double-click the WebSphere Event Tasks icon. 3. Double-click the Configure_Event_Server task icon and complete the Execute Task window. Select the managed node on which you want configure the event server. 4. Select Display on Desktop to display the output of the task on the desktop. 5. Increase the timeout value because the Configure_Event_Server task can take a considerable amount of time to finish. 6. Click Execute & Dismiss to display the Configure Event Server window. Figure 3. The Configure Event Server task window Complete the following fields: Rule Base Configuration Specify the way that the rule base is created: Update Current Rule Base Select this to update your existing rule base. Create New Rule Base From Existing If you are creating a new rule base, select the name of an 42 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

57 existing rule base, if you have one available. If you have not previously created a rule base, accept the default, Default. If you select this option, you must type the name of the new rule base in the New Rule Base Name field and the path to the new rule base in the New Rule Base Path field. Create New Rule Base Select this to create a new rule base that is not initialized with an existing rule base. If you select this option, you must type the name of the new rule base in the New Rule Base Name field and the path to the new rule base in the New Rule Base Path field. You cannot select a rule base from the Rule Bases list. New Rule Base Name Enter the name for the new or existing rule base. The default name is ITMWAS. Note: Do not change the Default rule base. Do not enter Default in this field. New Rule Base Path Enter the full path for the new rule base. The default path is $BINDIR/TME/TEC. Rule Base Activation Rules Select one of the following: Compile rule base only Creates or updates the rule base, but does not upload the rule base into the event server. Use this option if you want to review rule base changes before you activate them. Compile and load rule base Creates or updates the rule base and loads it into the event server. The new rule base is active when the event server is restarted. Compile and load rule base and restart system Creates or updates the rule base, loads it into the event server, and restarts the event server. 7. Click Set and Execute to start the task. The Configure Event Server Output window displays the job status after the task is completed. Configuring the Tivoli Enterprise Console adapter for local systems Objective To configure, deploy, and start the Tivoli Enterprise console adapter. Background information The Tivoli Enterprise Console adapter is used to ensure that IBM WebSphere FATAL, ERROR, AUDIT, WARNING, and TERMINATE messages (SeriousEvents) are forwarded to the Tivoli Enterprise Console. The Tivoli Enterprise Console adapter is also self-reporting; you can see the adapter status events in your console. Required authorization role websphereappsvr_admin, websphereappsvr_super Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 43

58 Before you begin Configure the Tivoli Enterprise Console event server. See Configuring the Tivoli Enterprise Console event server on page 40 for more information. Before you can configure the event adapter, you must create Tivoli objects for your IBM WebSphere Application Server resources as described in Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page 17. Ensure that the Tivoli Adapter Configuration Facility is installed. The Tivoli Adapter Configuration Facility is required to use event adapters. For information, see the Tivoli Enterprise Console documentation. Ensure that the IBM WebSphere administration server is running. When you finish View events in the event console. Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command line: Use the wruntask command to run the Configure_WebSphere_TEC_Adapter task. For the CLI syntax for this task, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Tivoli desktop: 1. From the Tivoli desktop, double-click the Monitoring for WebSphere Application Server policy region. 2. Double-click the WebSphere Event Tasks icon. 3. Double-click the Configure_WebSphere_TEC_Adapter task icon and complete the Execute Task window. 4. Select Display on Desktop to display the output of the task on the desktop. 5. Increase the timeout value if you selected more than one IBM WebSphere administration server because this can causes the task to take longer to display output. 6. Click Execute & Dismiss to display the Configure WebSphere TEC Adapter window. 44 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

59 Figure 4. The Configure WebSphere TEC Adapter task window Complete the following fields: Event Adapter Port The port number that the Tivoli Enterprise Console adapter uses for communication. The default port is Event Server (name registry format) The name of the event server to which events are forwarded. Enter one of the three following values: Event server name in registry format To identify an event server that is part of the same management region, For an event server in a different management region, the value where <tmr> is the name of a Tivoli management region. For OS/400 endpoints, you must enter the full IP address of the server, and optionally the server port number. For example: unixtecserver.mycompany.com For UNIX event servers, you can optionally add a colon followed by the server port number. If port mapping is enabled you do not need to specify the port number, but you can add :0 to indicate the default port. For Windows event servers, you must add a colon followed by the server port number. For example: windowstecserver.mycompany.com:5529 NOTECSERVER If you are not using Tivoli Enterprise Console or do not want events to be forwarded to the event server, enter NOTECSERVER. Blank The default is used. Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 45

60 Forward Fatal Events Indicates whether or not you want fatal events forwarded to the Tivoli Enterprise Console with a severity of FATAL. The default value is yes. Forward Terminate Events Indicates whether or not you want terminate events forwarded to the Tivoli Enterprise Console with a severity of CRITICAL. The default value is yes. Forward Error events Indicates whether or not you want error events forwarded to the Tivoli Enterprise Console with a severity of CRITICAL. The default value is yes. Forward Warning events Indicates whether or not you want warning events forwarded to the Tivoli Enterprise Console with a severity of WARNING. The default value is yes. Forward Audit events Indicates whether or not you want audit events forwarded to the Tivoli Enterprise Console with a severity of HARMLESS. The default value is no. 7. Click Set and Execute to start the task. The Configure_WebSphere_TEC_Adapter Output window displays the job status after the task is completed. Configuring the Tivoli Enterprise Console z/os adapter Objective To configure, deploy, and start the Tivoli Enterprise Console z/os adapter. Background information The Tivoli Enterprise Console adapter is used to ensure that IBM WebSphere messages are forwarded to the Tivoli Enterprise Console. The Tivoli Enterprise Console adapter is also self-reporting; you can see the adapter status events in the Tivoli Enterprise Console. You can also see status events in the MVS console. For the z/os event adapter, IBM WebSphere Application Server messages are piped through NetView Message Automation to the NetView Event Automation Service; in turn, the Event Automation Service sends the event to the Tivoli Enterprise Console event server. The messages that are monitored for z/os are listed in Appendix D, Event classes and rules, on page 123. Note: If you are already using Tivoli Business Systems Manager to monitor WebSphere for z/os events, do not use this z/os event adapter. Otherwise, you will receive duplicate events. Required authorization role This NetView user ID needs authority to run the NetView AUTOTBL command. Before you begin Configure the Tivoli Enterprise Console event server. See Configuring the Tivoli Enterprise Console event server on page 40 for more information. 46 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

61 When you finish View events in the event console. Procedure Perform the following steps on each z/os system where you want to run an event adapter. If you have a sysplex with a shared console, you need to perform these steps on only one system in the sysplex. 1. Copy the following members of ITD.ITDSAMP to a PDS on the system: v ITDEACFG v ITDEAINI v ITDEAFMT 2. Copy IDT.ITDSAMP(ITDEVTAD) to a PDS defined in the PROCLIB concatenation. 3. Edit ITDEVTAD: a. Edit the DD statement for Initialization Parameters and Configuration Files Dataset. Change DSN=ITD to DSN=<HLQ>, where <HLQ> is the high level qualifier of the PDS to which you copied the files in step 1. b. Edit the STEPLIB statement and ensure that the HLQ for your NetView installation and for your language environment (LE) installation are correct. 4. Copy the following members of ITD.ITDSAMP to a PDS defined in the NetView DSIPARM concatenation: v ITDSNDEV v ITDRTPEV To see a list of datasets in the DSIPARM concatenation, run the following command from NetView: lista dsiparm If there are no datasets listed, modify the JCL used to start NetView and add the HLQ of a PDS to the DSIPARM section. Restart NetView for the change to take effect. 5. Copy the following members of ITD.ITDSAMP to a PDS defined in the NetView DSICLD concatenation: v ITDEASTA v ITDEASTP To see a list of datasets in the DSICLD concatenation, run the following command from NetView: lista dsicld If there are no datasets listed, modify the JCL used to start NetView and add the HLQ of a PDS to the DSICLD section. Restart NetView for the change to take effect. 6. Edit ITDEACFG in the PDS to which you copied it in step 1: a. Update ServerLocation and ServerPort. b. Optionally, update other options using the help information in the file. 7. To change the trace level of the event adapter, edit ITDEAINI in the PDS to which you copied it in step 1. There are two TRACE statements at the bottom of the file: v v CONTROL Modifies the trace level for the NetView Event Automation Service MESSAGEA Modifies the trace level for the message adapter. Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 47

62 Filtering events 8. Add the following line to the NetView Message Automation Table: %INCLUDE ITDTRPEV 9. Enable NetView Message Automation by issuing the following command: AUTOTBL MEMBER=<NAME> where <NAME> is the member name of the Message Automation Table. Note: The HLQ for this member must be in the DSIPARM concatenation. Follow the instructions in step 4 to determine what HLQs are defined in the DSIPARM concatenation. 10. If you have a sysplex with a shared console, you might need to update the NetView console settings to ensure that the Tivoli Enterprise Console adapter picks up messages from all systems that you want to monitor. Use the following steps to do this: a. Run the DISCONID NetView operator command to find the console name of the task with the load module name CNMCSSIR. Run it on the NetView that is to receive the messages from other systems. b. Run the following z/os operator command to update the console setting: V CN(<console_name>),MSCOPE=<system_list> where <console_name> is the name of the console from step 1, and <system_list> is the list of systems (such as MSCOPE=SYS1,SYS2 ) from which you want messages. If you want messages from all systems in the sysplex, enter MSCOPE=ALL. For example: V CN(CNMCSSIR),MSCOPE=ALL Note: If you specify MSCOPE=ALL., all AUTO(YES) messages for all systems in the sysplex will go through the automation table, which might have performance implications. See the NetView Automation Guide for more information. Events that are forwarded by the WebSphere TEC adapter and regarded as harmless or unlikely to require action can be suppressed from displaying on the event console. The Tivoli Management Framework provides the following methods for you to filter out events that you do not want to see: v For local endpoints, you can specify that the event is not to be forwarded from the endpoint to the event server. In this case, you specify filter criteria with the Configure_WebSphere_TEC_Adapter task. Depending on the frequency of the events, this option can decrease network traffic. See Configuring the Tivoli Enterprise Console adapter for local systems on page 43 for more information. v Note: This does not apply to z/os endpoints. For z/os endpoints, you need to edit the ITDEACFG file in order to set up event filtering. There is an option in this file, FilterMode, that is used for event filtering. You have two options for FilterMode: IN or OUT. If FilterMode is set to OUT, events that match a Filter entry are discarded this is the default setting. If FilterMode is set to IN, only events that match a Filter entry are sent to the event server. FilterMode applies to all Filter and FilterCache entries specified in the configuration file. 48 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

63 You can also specify slot/value pairs using an option in the ITDEACFG file. v v Note: In order to perform event filtering for z/os, you must have the required NetView APARs installed. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for details. You can create new rules to exclude the event. When you do this, the event will be forwarded to the event server, but will be eliminated by the rules engine. The Tivoli Enterprise Console Rule Builder s Guide describes the steps for building and changing rules. You can exclude classes of events using the event console s user interface. Refer to the Tivoli Enterprise Console User s Guide for more information. Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 49

64 50 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

65 Chapter 4. Integrating with Tivoli Business Systems Manager This chapter provides information on using Tivoli Business Systems Manager to manage IBM WebSphere Application Server resources and events. Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server into Tivoli Business Systems Manager includes the following steps: Table 6. Integrating with Tivoli Business System Manager Goal Refer to 1. Install the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program on the Tivoli Business Systems Manager server 2. Configure your Tivoli Enterprise Console event server to forward events to Tivoli Business Systems Manager 3. Define the specific IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects for Tivoli Business Systems Manager using a discovery task. Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager on page 53 Configuring the Tivoli Enterprise Console event server to work with Tivoli Business Systems Manager on page 54 Discovering resources for Tivoli Business Systems Manager on page 54 This chapter also provides a list of the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks that you can run from Tivoli Business Systems Manager and information about uninstalling the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration from Tivoli Business Systems Manager. Understanding Tivoli Business Systems Manager Tivoli Business Systems Manager is a business systems management tool that enables you to graphically monitor and control interconnected business components and operating system resources. A business component and its resources are referred to as a Line of Business (LOB). Note: In IBM Tivoli Business System Manager, Version 2.1, lines of business are referred to as business systems. Tivoli Business Systems Manager consists of the following components: Tivoli Business Systems Manager management server The Tivoli Business Systems Manager management server processes all the availability data that is collected from various sources. Availability data is inserted in the Tivoli Business Systems Manager database, where intelligent agents provide alerts on monitored objects and then broadcast those alerts to Tivoli Business Systems Manager workstations. The management server processes all user requests that originate from the workstations and includes a database server that is built around a Microsoft SQL Server database. 51

66 Tivoli Business Systems Manager console The Tivoli Business Systems Manager console displays objects in customized views, called Line of Business Views. Objects are presented in a hierarchical TreeView so that users can see the relationship between objects. Alerts are overlaid on the objects when the availability of the object is threatened. Tivoli Event Enablement Tivoli Event Enablement is installed on the Tivoli Enterprise Console event server and enables the event server to forward events to Tivoli Business Systems Manager. Tivoli Event Enablement defines event classes and rules for handling events related to Tivoli Business Systems Manager. For more information about Tivoli Business System Manager, see the Tivoli Business System Manager documentation. Prerequisites Working with z/os objects Before you integrate IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server into Tivoli Business Systems Manager, perform the following prerequisite steps: v v v Install Tivoli Business Systems Manager, as described in the Tivoli Business Systems Manager Installation and Configuration Guide. You must install Tivoli Business Systems Manager Version 1.5 with patch 35 or higher. Install and configure the Tivoli Event Enablement (with patch 43) on all Tivoli Enterprise Console event servers that receive events that you want to forward to Tivoli Business Systems Manager. See the Tivoli Business Systems Manager Installation and Configuration Guide for more information. Configure Tivoli Business Systems Manager to communicate with each Tivoli Event Enablement installed in the previous step. See the Tivoli Business Systems Manager Installation and Configuration Guide for more information. Tivoli Business Systems Manager has built-in support for WebSphere for z/os and creates objects and forwards messages automatically. In order to prevent the creation of duplicate objects, follow these steps for your z/os systems: 1. Do not configure the Tivoli Enterprise Console adapter for WebSphere for z/os. Messages are automatically sent to Tivoli Business Systems Manager. 2. Install Tivoli Business Systems Manager, version Install Tivoli Business Systems Manager Event Enablement, version 2.1.1, on the Tivoli Enterprise Console event server. You do not need to run the Send_WebSphere_Discovery_Events_to_TBSM task against z/os objects. This task does not send DISCOVERY or GONE events for z/os objects. With Tivoli Business Systems Manager, version 2.1.1, resource model events from z/os objects are forwarded to Tivoli Business Systems Manager objects already created to monitor WebSphere for z/os. Resource model events from the z/os IBM WebSphere administration server (status up or down events) are not forwarded because WebSphere for z/os already sends this status directly to Tivoli Business Systems Manager. 52 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

67 Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager Objective To integrate IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager so you can receive IBM WebSphere Application Server events on the Tivoli Business Systems Manager. Background information To enable Tivoli Business Systems Manager to manage IBM WebSphere Application Server events, you must install an IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program on the Tivoli Business Systems Manager server. This integration program performs the following steps: v v v Defines the IBM WebSphere Application Server objects in Tivoli Business Systems Manager Adds IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks to the object types in Tivoli Business Systems Manager Defines a line of business for IBM WebSphere Application Server resources Required authorization role You must have administrator authority on the Tivoli Business Systems Manager server. Before you begin Make sure that your Tivoli Business Systems Manager environment is configured correctly and that you have Tivoli Event Enablement installed on each Tivoli Enterprise Console event server that you want to forward events. For more information, see the Tivoli Business Systems Manager Installation and Configuration Guide. Tivoli Business Systems Manager recommends that you stop the Tivoli BSM Application Server NT Service and then stop the Tivoli BSM Propagation Dispatcher NT Service before installing this integration program. When you finish Configure the Tivoli Enterprise Console event server to forward events to Tivoli Business Systems Manager. See Configuring the Tivoli Enterprise Console event server to work with Tivoli Business Systems Manager on page 54 for more information. Procedure Use the following steps to install the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program: 1. On the Tivoli Business Systems Manager server, insert the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application 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\itmwas. Click Browse to select a different installation location. Click Next to continue. 5. Provide the following Microsoft SQL Server information and click Next to start the installation. Chapter 4. Integrating with Tivoli Business Systems Manager 53

68 SQL Server The name of the SQL server with which this Tivoli Business Systems Manager server is associated SQL Userid The SQL user ID SQL Password The password for the user ID defined above A progress bar is displayed to show the progress of the installation. When installation is complete, a message appears. 6. Click Finish to exit the installation wizard. Configuring the Tivoli Enterprise Console event server to work with Tivoli Business Systems Manager Objective To configure the Tivoli Enterprise Console event server to forward events to Tivoli Business Systems Manager. Background information Before Tivoli Enterprise Console event servers can forward events to Tivoli Business Systems Manager, you must configure them to use a rule base to forward the events. Required authorization role senior Before you begin Install the Tivoli Event Enablement on each Tivoli Enterprise Console event server that you want to forward events to Tivoli Business Systems Manager. For more information, see the Tivoli Business Systems Manager Installation and Configuration Guide for more information. When you finish Define your IBM WebSphere Application Server objects for Tivoli Business Systems Manager with the Send_WebSphere_Discovery_Events_to_TBSM task, as described in Discovering resources for Tivoli Business Systems Manager. Procedure Use the Configure Event Server task to configure (or reconfigure) each event server. If you installed the Tivoli Event Enablement on the event server, this task recognizes that and compiles the rule base that forwards events to Tivoli Business Systems Manager. For information on running this task, see Configuring the Tivoli Enterprise Console event server on page 40. Discovering resources for Tivoli Business Systems Manager Objective To define the specific IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects for Tivoli Business Systems Manager. Note: If you are running Tivoli Business Systems Manager 2.1.1, you do not need to define objects. This is done automatically. 54 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

69 Background information The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program that you installed in Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server with Tivoli Business Systems Manager on page 53 defined the types of objects that you want Tivoli Business Systems Manager to manage. After you define the object types, you must define the specific objects. You can do this with the Send_WebSphere_Discovery_Events_to_TBSM task. This task searches a managed node for WSAdministrationServer and WSApplicationServer objects and sends a DISCOVER event to Tivoli Business Systems Manager for each object. The Send_WebSphere_Discovery_Events_to_TBSM task also maintains a list of the objects that have been discovered and alerts Tivoli Business Systems Manager when they have been deleted by sending Tivoli Business Systems Manager a GONE event for each object that no longer exists on the managed node. Required authorization role websphereappsvr_admin, websphereappsvr_super Before you begin Configure your Tivoli Enterprise Console event server, as described in Configuring the Tivoli Enterprise Console event server to work with Tivoli Business Systems Manager on page 54. When you finish Use Tivoli Business Systems Manager to view and manage your IBM WebSphere Application Server objects. For information on using Tivoli Business Systems Manager, see the Tivoli Business Systems Manager User s Guide. For information on the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks that you can run from Tivoli Business Systems Manager, see Working with Tivoli Business Systems Manager on page 56. Procedure You can perform this procedure from the command line or the Tivoli desktop. Command line: Use the wruntask command to run the Send_WebSphere_Discovery_Events_to_TBSM task from the command line. For information on the CLI syntax for this task, see the IBM Tivoli Monitoring for Web Infrastructure Reference 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 WebSphere Application Server policy region icon to display the policy region. c. Double-click the WebSphere Application Server Utility Tasks icon to open the task library window. 2. In the WebSphere Application Server Utility Tasks task library, double-click the Send_WebSphere_Discovery_Events_to_TBSM task. 3. Select the managed node on which you want to search for objects. 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. Chapter 4. Integrating with Tivoli Business Systems Manager 55

70 If the task completes successfully, you receive a list of the DISCOVER and GONE events that were sent to Tivoli Business Systems Manager. Working with Tivoli Business Systems Manager In addition to using Tivoli Business Systems Manager to monitor the state of your resources, you can also run tasks on the objects. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks are loaded into Tivoli Business Systems Manager when you install the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program. These tasks appear on the Operation Tasks menus for the different object types (WSAdministrationServer and WSApplicationServer). This Operation Tasks menu is displayed when you right-click an object. Note: Tivoli Business Systems Manager does not support IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasks. You can perform the following IBM WebSphere administration server tasks from Tivoli Business Systems Manager: v Check_Administration_Server_Status v List_Application_Servers v Start_Administration_Server v Stop_Administration_Server Note: You cannot start or stop administration servers that are located on z/os systems. You can perform the following application server tasks from Tivoli Business Systems Manager: v Check_Application_Server_Status v Start_Application_Server v Stop_Application_Server Tivoli Business Systems Manager also monitors the status of resource models. Events generated by the Tivoli Enterprise Console adapter or resource models are forwarded from Tivoli Enterprise Console to Tivoli Business Systems Manager. For more information about these tasks and resource models, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Uninstalling IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration from Tivoli Business Systems Manager Objective To remove the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program from Tivoli Business Systems Manager. Background information Uninstalling the IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server integration program removes the IBM WebSphere Application Server object definitions and objects from Tivoli Business Systems Manager. 56 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

71 Required authorization role You must have administrator authority on the Tivoli Business Systems Manager server. Before you begin None When you finish None Procedure Use 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 for Web Infrastructure: WebSphere Application Server integration program. The default directory is C:\tivoli\itmwas. 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 Server The name of the SQL server with which this Tivoli Business Systems Manager server is associated SQL Userid The SQL user ID SQL Password The password for the user ID defined above 6. Click Finish to exit the installation wizard. Chapter 4. Integrating with Tivoli Business Systems Manager 57

72 58 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

73 Chapter 5. Working with resource models Resource model library Modifying indications This chapter provides information about using the resource models that are included in IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. You can customize various management aspects of the resource models so that they have the appropriate settings for your monitoring environment. Customizing a resource model involves the following steps: v Modifying indications v Specifying tasks for an indication on page 61 v Sending a notice to administrators when an event occurs on page 63 v Creating scheduling rules on page 64 v Modifying data logging settings on page 66 v Managing profiles and resource models at endpoints on page 68 v Managing IBM Tivoli Monitoring gateways on page 69 v Determining which resource models are running on endpoints on page 70 v Viewing resource model results with the IBM Tivoli Web Health Console on page 70 v Stopping the monitoring of data from an endpoint on page 72 For z/os systems, the WebSphereAS Adminstration Server Status and WebSphereAS Application Server Status resource models require that a Netconv session be running. The remaining resource models require that the data collector is running on z/os and that you have configured metric gathering. See Configuring metric collection for z/os systems on page 24 for information. For information about the default configuration of these resource models, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Objective To modify indication rules so that resources are monitored and events are generated relevant to your environment. Background information Each resource model triggers an indication if certain conditions defined by the resource model s thresholds are not satisfied during the monitoring cycle. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. 59

74 You can also use the predefined profile managers and profiles created during installation. When you finish Distribute the profile to which the resource model belongs. See Distributing profiles from the Tivoli desktop on page 34. 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 61 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 63 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 64 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 66 Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wdmeditprf command to customize a resource model for a profile. See the IBM Tivoli Monitoring Reference Guide for more information. 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 WebSphere Application 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 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 default resource model settings. You can customize the following fields. For more information about these fields, see the IBM Tivoli Monitoring documentation. Number of occurrences Specifies the number of consecutive times the problem occurs before the software generates an indication. You can change this value to specify the number of times a problem occurs before an indication is generated. 60 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

75 Number of holes Determines how many cycles that do not produce an indication can occur between cycles that do produce an indication. Use the value for the Number of Holes in conjunction with the Number of Occurrences parameter and the Cycle Time to define a time window for the generation of an event. Send TEC Events Select this check box to send an event to the Tivoli Enterprise Console. You must have Tivoli Enterprise Console installed and configured. Send to TBSM Sends events to Tivoli Business Systems Manager. You do not need to select this box. If you have Tivoli Business Systems Manager installed and configured, Tivoli Enterprise Console automatically forwards events to Tivoli Business Systems Manager. 7. Specify the serverity of the indication in the Severity pull-down list. You have the following options: v FATAL v CRITICAL v WARNING v HARMLESS v MINOR 8. Click one of the following buttons: Apply Changes Saves the changes and leaves the Indications and Actions window open. Apply Changes and Close Closes the Indications and Actions window and saves the changes. Specifying tasks for an indication Objective To specify a task so administrators and users can determine corrective or reporting tasks for an event. Background information You can select one or more task to run automatically when an event occurs. These tasks can access the IBM Tivoli Monitoring event name and thresholds by accessing the environment variables. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 and for information. Chapter 5. Working with resource models 61

76 You can also use the predefined profile managers and profiles created during installation. When you finish Distribute the profile to which the resource model belongs. See Distributing profiles from the Tivoli desktop on page 34. 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 59 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 63 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 64 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 66 Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wdmeditprf command to customize a resource model for a profile. See the IBM Tivoli Monitoring Reference Guide for more information. 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 WebSphere Application 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 in which you want to customize a resource 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. 62 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

77 Sending a notice to administrators when an event occurs Objective To send a notice in response to an event so administrators can take the appropriate actions or responses. Background information You can select the IBM Tivoli Monitoring Utility task to send notices in response to an event. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. You can also use the predefined profile managers and profiles created during installation. You must create an administrator before you can subscribe the administrator to a notice group. For information about creating administrators, see the Tivoli Management Framework, Version 3.7.1: Reference Manual. When you finish Distribute the profile to which the resource model belongs. See Distributing profiles from the Tivoli desktop on page 34. 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 59 v Specify if you want corrective or reporting tasks for an event. See Specifying tasks for an indication on page 61 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 64 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 66 Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wdmeditprf command to customize a resource model for a profile. See the IBM Tivoli Monitoring Reference Guide for more information. Tivoli desktop: 1. Open the IBM Tivoli Monitoring Profile window by doing the following: a. Open the Tivoli desktop. Chapter 5. Working with resource models 63

78 Creating scheduling rules b. Double-click the Monitoring for WebSphere Application 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 in which you want to customize a resource 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 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 Utility Tasks library are displayed in the Tasks panel. 7. Double-click dm_mn_send_notice in the Tasks panel. The Configure Task window opens. 8. Specify the appropriate parameters in the Configure Task window. Additional information: Run the wlsnotif -g command to see the available Notice Groups. See the IBM Tivoli Monitoring Reference Guide for more information. 9. Click Change & Close to add the task to the Action List panel in the Indications and Actions window. Objective To create schedule rules so administrators and users can determine the time periods on selected days when monitoring takes place. Background information IBM Tivoli Monitoring contains a scheduling feature that enables you to create specific scheduling rules that determine a period when monitoring takes place. You can divide the overall collection period into active and inactive intervals by applying one or more schedule rules. The scheduling rules enable you to define time periods on specific weekdays during which monitoring takes place. You can define any number of rules which allows you set up a complex pattern of resource monitoring for a profile and covers the periods that you want to monitor. If the profile contains more than one schedule rule, all the time intervals are respected, and rules are combined by adding together the time periods they define. For example, if you specify a rule that requests monitoring between 8:00 and 14:00 every day and another that requests all-day monitoring on Fridays, the sum of the two rules gives all-day monitoring only on Fridays, and monitoring between 8:00 and 14:00 on all other days. If the second rule instead requested monitoring from 12:00 to 18:00 on Fridays, the sum of the rules would give monitoring between 8:00 and 18:00 on Fridays 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 a single rule that monitors the same local time period in different time zones. All times of events or activities reported from endpoints or gateways are also logged in the local time of the system from where they originated. The Scheduling window has the following group boxes: 64 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

79 Schedule Sets the data collection period. By default, all resource models are set to always collect data. Schedule Rules Contains a list of the defined scheduling rules, which manage the time intervals during which the resource model is active. Rule Editor Creates and edits schedule rules. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. You can also use the predefined profile managers and profiles created during installation. When you finish Distribute the profile to which the resource model belongs. See Distributing profiles from the Tivoli desktop on page 34. 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 59 v Specify if you want corrective or reporting tasks for an event. See Specifying tasks for an indication on page 61 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 63 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 66 Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wdmeditprf command to customize a resource model for a profile. See the IBM Tivoli Monitoring Reference Guide for more information. 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 WebSphere Application Server policy region icon to display the policy region. c. Double-click the profile manager icon to display the profile manager. Chapter 5. Working with resource models 65

80 d. Double-click the profile icon in which you want to customize a resource 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 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 more than one day from the list. e. Set the Start Time and Stop Time for the collection activity or select the All Day check box. Additional information: Times are always interpreted as local time where the endpoint engine runs. Setting a time interval of 08:00 to 13:00 ensures that monitoring takes place between those times in all time zones to which you distribute 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 the Schedule 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 Objective To modify data logging information so administrators and users can log data collected by a resource model and write it in a local database. Background information You can view the log data through the IBM Tivoli Monitoring Web Health Console after you write it in a local database. You can store one of the following types of data in the database: Raw data Data written exactly as the resource model collects it. All the monitored values are collected and copied in the database. Aggregated data Data collected and aggregated at fixed intervals that you define (Aggregation Period). Only the aggregated values are written in the database. The aggregated data is calculated on the basis of one or more of the following options: v Maximum v Minimum v Average 66 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

81 Tivoli Enterprise Data Warehouse data logging Data collected is logged to the Tivoli Enterprise Data Warehouse. Note: To enable Tivoli Enterprise Data Warehouse data logging, you must disable aggregated data logging. Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. You can also use the predefined profile managers and profiles created during installation. When you finish Distribute the profile to which the resource model belongs. See Distributing profiles from the Tivoli desktop on page 34. 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 59 v Specify if you want corrective or reporting tasks for an event. See Specifying tasks for an indication on page 61 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 63 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 64 Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wdmeditprf command to customize a resource model for a profile. See the IBM Tivoli Monitoring Reference Guide for more information. 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 WebSphere Application 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 in which you want to customize a resource 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 Logging to open the Logging window. Chapter 5. Working with resource models 67

82 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 the database: Maximum Calculates and logs the peak value in each aggregation period. Minimum Calculates and logs the lowest value in each aggregation period. Average Calculates and logs the average of all values in each aggregation period. 6. To enable Tivoli Enterprise Data Warehouse data logging, clear Aggregated data 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 Objective To manage profiles and resource models after they are distributed to endpoints so administrators and users can maintain monitoring processes on those endpoints. Background information None Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. v Distribute the profile. See Distributing profiles from the Tivoli desktop on page 34 for information. You can also use the predefined profile managers and profiles created during installation. When you finish None Procedure You can perform this procedure from the Tivoli command line only. 68 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

83 Command Line: Use the wdmcmd command to stop or restart IBM Tivoli Monitoring 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 at endpoints or to delete profiles at endpoints. Use the wdmlseng command to return a list and the status of all resource models that have been distributed on a specified endpoint. Use the wdmtrceng command to set the trace parameters of the IBM Tivoli Monitoring engine at the endpoint. See the IBM Tivoli Monitoring Reference Guide for information about the syntax of these commands. Managing IBM Tivoli Monitoring gateways Objective To manage IBM Tivoli Monitoring on gateways so administrators and users can run monitoring processes on those gateways. Background information None Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. v Distribute the profile. See Distributing profiles from the Tivoli desktop on page 34 for information. You can also use the predefined profile managers and profiles created during installation. When you finish None Procedure You can perform this procedure from the Tivoli command line only. Command Line: Use the wdmmn command to stop or start selected IBM Tivoli Monitoring processes on one or all gateways. See the IBM Tivoli Monitoring Reference Guide for more information. Chapter 5. Working with resource models 69

84 Determining which resource models are running on endpoints Objective To determine which resource models are running on an endpoint. Background information None Required authorization role admin Before you begin v Create a profile manager and profile. See Creating profile managers and profiles on page 112 for information. v Add subscribers to a profile manager. See Subscribing resources to profile managers on page 114 for information. v Add a resource model to a profile. See Adding default resource models to profiles on page 114 for information. v Distribute the profile. See Distributing profiles from the Tivoli desktop on page 34 for information. You can also use the predefined profile managers and profiles created during installation. When you finish None Procedure You can perform this procedure from the command line. You can also view the resource models distributed to endpoints with the Web Health Console, as described in Viewing resource model results with the IBM Tivoli Web Health Console. Command Line: Use the wdmlseng command to determine which resource models 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 Web Health Console This section provides an overview of the Web Health Console. For complete information on installing and working with the Web Health Console see the latest version of the IBM Tivoli Monitoring User s Guide. The Web Health Console runs on Netscape 6.x and Internet Explorer 6.x. You can use the Web Health Console for the following purposes: v v Checking, displaying, and analyzing the status and health of endpoints that have distributed resource resource models Displaying an endpoint s real-time and historical data logged to the IBM Tivoli Monitoring database 70 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

85 v v v Viewing online and historical data on endpoints as a follow-up to specific problems Starting and stopping the IBM Tivoli Monitoring engine and individual resource models on selected endpoint Removing a profile from the selected endpoint You can use the Web Health Console to check, display, and analyze the status and health of any endpoint with profiles and resource models. Status reflects the state of the endpoint, such as running or stopped. Health is a numeric value determined by resource model settings. You can also use the Web Health Console to work with real-time or historical data from an endpoint that is logged to the IBM Tivoli Monitoring database. You can use the diagnostic and monitoring capabilities of the Web Health Console to perform targeted analysis of problems associated with individual endpoints when an event is sent to the Tivoli Enterprise Console. Use the online and historical data to follow up specific problems with single endpoints. Understanding resource health The Web Health Console obtains events and indications from endpoints. The Web Health Console displays the health of each potential problem as a numeric value between 100 (perfect health) and zero (with zero meaning that the conditions for the corresponding event are met). Intermediate values show the percentage of occurrences currently registered with respect to the total number of occurrences needed to trigger an event. See Table 7 Table 7. Health Determination Example Cycle CPU% Occurrences or Holes H O H O O Occurrence Count Health % Table 7 displays the health percentage changes in steps of 25% because 4 occurrences were required to trigger an event; if the indication required 5 occurrences, the health percentage would have changed by steps of 20%. Resource health is determined at the indication level and passed up to the endpoint. The lowest health of any indication in a resource model is shown as the health of that resource model and the lowest health of any resource model installed on an endpoint is shown as the health of that endpoint. For example, if one indication on one resource model that is installed on an endpoint has a health of zero, the health of the endpoint is shown as zero. The required occurrences, cycle times, thresholds, and parameters for indications are defined when the resource model is created in the IBM Tivoli Monitoring Workbench. If you use the default profile managers created during the installation of IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server, the occurrences, cycle times, thresholds, and parameters are already defined. Connecting the IBM Tivoli Monitoring Web Health Console You can connect the IBM Tivoli Monitoring Web Health Console to any Tivoli management region server, managed node, or endpoint, and configure it to monitor any or all of the endpoints that are found in that region. The IBM Tivoli Monitoring Web Health Console does not have to be within the region itself, Chapter 5. Working with resource models 71

86 although it could be. To connect to the IBM Tivoli Monitoring Web Health Console you need access to the server on which the IBM Tivoli Monitoring Web Health Console server is installed and the IBM Tivoli Managed Region on which you want to monitor health. All user management and security is handled through the IBM Tivoli management environment. This includes creating users and passwords as well as assigning authority. For more information, see the Web Health Console documentation in the IBM Tivoli Monitoring publications library. Stopping the monitoring of data from an endpoint Because the gathering of performance data can have an impact on system performance, you might want to stop monitoring this data for one or more systems in your network. For z/os systems, this is particularly true if you stop using the Data Collector on system. To stop monitoring data on a local endpoint, disable performance counter monitoring in the IBM WebSphere Administrator s console. To stop monitoring data on a z/os system, run the following script: itmwasappserverupdate [-a] [-s <server>] -clean [-i <instance>] <conversationname> You can specify the following parameters: -a Specifies that the conversation should be committed and activated after it has been created and its environment has been updated. Note: If you do not specify the a parameter, the conversation is created but not activated. This enables you to see what the script does before you activate it. -s <server> Specifies to update only the environment for this server. If omitted, all server environments are updated. clean Specifies to remove IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server paths and Java options from the new conversation. -i <instance> Specifies to update only the environment for this server instance. This must follow a -s option. If omitted, all instances for the previously specified server are updated. <conversationname> Specifies the name of the conversation to create. 72 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

87 Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources This chapter provides information about working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources. The following table provides an overview of the topics covered in this chapter. Goal Where to find information Check the status of an object Checking the status of an IBM WebSphere administration or application server Start or stop a server Starting or stopping a server on page 75 List application servers Listing application servers on page 76 View endpoint or callback log files Viewing endpoint or callback log files on page 78 Note: The procedures in this chapter are performed from the Tivoli desktop. You can also perform the procedures from the command line or using the associated tasks. For information about running tasks and jobs, see Chapter 7, Working with tasks and jobs, on page 81. For specific information about tasks, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Checking the status of an IBM WebSphere administration or application server Objective To check the status of an IBM WebSphere administration or application server. The status of the server is one of the following: v Initializing v Up v Terminating v Down v Unknown the status of the server cannot be determined. Check the communication to the server and try again. Note: For z/os, Unknown is returned when all system management servers (represented by a WSAdminstrationServer object) are down. For a WSAdministrationServer object representing z/os system management server instances, status is returned for each instance. A combined status is also returned that represents the status of all the instances as one boolean result (true if the status is up, false if the status is down). For the combined status, if any server instance is up, the status of all instances is reported as up. Background information IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server displays the status of the IBM WebSphere administration or application server. 73

88 Required authorization role websphereappsvr_user, websphereappsvr_admin, websphereappsvr_super Before you begin Create IBM WebSphere Application Server objects. See Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page 17 for more information. For z/os administration or application servers, you must have a NETCONV session running. When you finish Start or stop the server, depending on the status returned. See Starting or stopping a server on page 75 for more information. Procedure You can perform this procedure from the command line, as a task, or from the Tivoli desktop. You can also check the status of a server with a resource model. See Chapter 5, Working with resource models, on page 59 for information about using resource models. Command line: Use the wruntask command to run either the Check_Administration_Server_Status or Check_Application_Server_Status task. For the CLI syntax for these tasks, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Task: Use the Check_Administration_Server_Status task to check the status of the IBM WebSphere administration server. Use the Check_Application_Server_Status task to check the status of an application server. See Chapter 7, Working with tasks and jobs, on page 81 for information about running tasks. Tivoli desktop: Use the following steps to run this procedure from the Tivoli desktop: 1. From the Tivoli desktop, double-click the policy region that contains the administration or application server objects to display the Policy Region window. The default policy region is Monitoring for WebSphere Application Server. If you created additional policy regions, open the one that contains the objects you want to work with. 2. Right-click an IBM WebSphere administration or application server and select Operation to display the Operation pop-up menu. 74 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

89 Figure 5. The Operation menu on a IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server object 3. Select Check Status to display the status of the server. Figure 6. The output window for the Check Status action Starting or stopping a server Objective To start or stop an IBM WebSphere administration or application server. Note: You cannot start or stop an IBM WebSphere administration server on a z/os system. For information about starting or stopping an administration server on z/os, see the Operating WebSphere for z/os chapter in WebSphere Application Server V4.0.1 for z/os and OS/390 Operations and Administration. Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources 75

90 Background information If an IBM WebSphere administration server is down, any IBM WebSphere application servers associated with that administration server are unavailable. If an application server is down, any applications running on that application server are also down. Required authorization role websphereappsvr_admin, websphereappsvr_super Before you begin Check the status of your IBM WebSphere administration and application servers. See Checking the status of an IBM WebSphere administration or application server on page 73 for more information. When you finish None Listing application servers Procedure You can perform this procedure from the command line, as a task, or from the Tivoli desktop. Command line: Use the wruntask command to run either the Start_Administration_Server or Stop_Administration_Server to start or stop an IBM WebSphere administration server. Use the wruntask command to run either the Start_Application_Server task or Stop_Application_Server task to start or stop an application server. For the CLI syntax for these tasks, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Task: Use the Start_Administration_Server task or Stop_Administration_Server task to start or stop an IBM WebSphere administration server. Use the Start_Application_Server task or Stop_Application_Server task to start or stop an application server. See Chapter 7, Working with tasks and jobs, on page 81 for information about running tasks. Tivoli desktop: Use the following steps to run this procedure from the Tivoli desktop: 1. From the Tivoli desktop, double-click the policy region that contains the administration or application server objects to display the Policy Region window. The default policy region is Monitoring for WebSphere Application Server. If you created additional policy regions, open the one that contains the objects you want to work with. 2. Right-click an IBM WebSphere administration or application server and select Operation to display the Operation pop-up menu. 3. Click Start Server or Stop Server to start or stop the server. 4. If you clicked Stop Server, a confirmation window is displayed. Click Yes to stop the server or No to cancel the action. Objective To list the application servers associated with an IBM WebSphere administration server. 76 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

91 Background information IBM WebSphere administration servers have associated application servers. You can list these servers before running the Discover_WebSphere_Resources task to determine which application servers need to have objects created for them before they can be monitored with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. When you have this list, run the Discover_WebSphere_Resources task against the administration servers to create application server objects for them. You can also use this list to determine which tasks to run on your application servers. Required authorization role websphereappsvr_user, websphereappsvr_admin, websphereappsvr_super Before you begin Ensure that your IBM WebSphere administration server is running. See Checking the status of an IBM WebSphere administration or application server on page 73 for more information. When you finish If your list of application servers includes any that do not have IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects, create objects for them. See Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server objects on page 17 for more information. Procedure You can perform this procedure from the command line, as a task, or from the Tivoli desktop. Command line: Use the wruntask command to run the List_Application_Servers task. For the CLI syntax for this tasks, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Task: Use the List_Application_Servers task to list the application servers associated with an IBM WebSphere administration server. See Chapter 7, Working with tasks and jobs, on page 81 for information about running tasks. Tivoli desktop: Use the following steps to run this procedure from the Tivoli desktop: 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 WebSphere Application Server. If you created additional policy regions, open the one that contains the objects you want to work with. 2. Right-click the IBM WebSphere administration server for which you want to list the application servers and select Operation to display the Operation pop-up menu. 3. Select List Application Servers to display a list of the application servers associated with this administration server. Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources 77

92 Figure 7. List of application servers associated with the specified IBM WebSphere administration server. You can also double-click an IBM WebSphere administration server to view a list of the associated application servers. Double-clicking the IBM WebSphere administration server object displays only the application servers that have been discovered by IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server; using the procedure above displays all application servers associated with the IBM WebSphere administration server. Viewing endpoint or callback log files Objective To list or display all IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server endpoint or callback logs for an IBM WebSphere administration or application server. Note: The only files listed or displayed are those on the endpoint or proxy endpoint system. You cannot list or display log files that exist on z/os systems. See Appendix E, Problem determination, on page 127 for information about these log files. Background information You can use the endpoint or callback logs if you encounter any problems while running IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. Required authorization role websphereappsvr_user, websphereappsvr_admin, websphereappsvr_super Before you begin None When you finish None 78 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

93 Procedure You can perform this procedure from the command line, as a task, or from the Tivoli desktop. Command line: Use the wruntask command to run the List_Trace_Logs task. For the CLI syntax for this task, see the IBM Tivoli Monitoring for Web Infrastructure Reference Guide. Task: Use the List_Trace_Logs task to list the callback and endpoint logs. See Chapter 7, Working with tasks and jobs, on page 81 for information about running tasks. Tivoli desktop: Use the following steps to run this procedure from the Tivoli desktop: 1. From the Tivoli desktop, double-click the policy region that contains the administration server objects to display the Policy Region window. The default policy region is Monitoring for WebSphere Application Server. If you created additional policy regions, open the one that contains the objects you want to work with. 2. Right-click an IBM WebSphere administration or application server and select Diagnostics to display the Diagnostics pop-up menu. 3. Select Tivoli Logs. 4. Select the type of log you want to list, either Endpoint or Callback. A list of logs is displayed. Figure 8. The list of endpoint logs associated with the IBM WebSphere administration server Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources 79

94 From the Log Files window, you can select individual callback logs to display or delete. For endpoint logs, you can only select to display or delete all logs. You can refresh this list to display any logs created after you generated the list. 80 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

95 Chapter 7. Working with tasks and jobs This chapter provides information about using tasks and jobs to manage your IBM WebSphere Application Server resources. Table 8 shows the options to manage tasks and jobs. Table 8. Working with tasks and jobs Goal Refer to Run a task to perform a specific operation. Running a task on page 81 Define a standard task with specific arguments to customize the Customizing a task on page 84 task. Create a job from a task so that it can be scheduled to run. Creating a job on page 86 Run a job with predefined arguments. Running a job on page 88 Schedule jobs to run at specified times. Scheduling a job on page 89 Running a task The installation process installs the task library in the product policy region. We recommend that you do not remove the task library from this policy region. The task library contains default policies that affect how the task library works. The policy region containing the task library defines task and job policies. Default policies set profile manager options and endpoints for tasks. Validation policies control the creation and execution of tasks. Notes: 1. Before you can run tasks for z/os objects, you must have a NETCONV session running. 2. For z/os objects, the NetView operator ID that you use must have read/write permission to the /var/itwmas directory and subdirectories and must be a IBM WebSphere Application Server administrator. See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide for more information. Objective To run one of the standard tasks in the task library. Background information A task is an action that must be routinely performed on selected endpoints or managed 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 name under which the task is run. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server provides standard tasks in a task library. Standard tasks run on any system without consideration of platform type. Required authorization roles See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for the authorization role required for each task. Before you begin None 81

96 When you finish None Procedure You can perform this procedure from either the command line or the Tivoli desktop. Command Line: Use the wruntask command to run a task. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for information about running tasks from the command line. For more information about the wruntask command, see the Tivoli Framework Reference 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 WebSphere Application 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 that contains execution parameters for all tasks. 3. Select one of the following check boxes in the Execution Mode group box: Parallel Runs the task simultaneously on all targets. Parallel is typically the fastest method of execution. Serial Runs the task sequentially on all targets in alphabetical order. Staged Runs the task on all targets in alphabetical order according to a schedule you specify. Staged execution is useful if you are running the task on a large number of endpoints. Complete Step 5 to specify the Staging Count (number of targets to run against per stage) and the Staging 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 value specifies the number of seconds the Tivoli desktop waits for the task to complete before it issues an error. The task continues to execute on the endpoint without displaying the output results. Setting an early timeout enables your Tivoli desktop to become available again if the task takes a long time to execute. The default is 60 seconds. If the task takes longer to complete than the specified Timeout and is running in Serial or Staged mode, the product moves on to other endpoints after this time expires. 5. Optional: If you selected Staged in Step 3, specify the number of endpoints to include in each staged set in the Staging Count text box and the number of seconds 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 dialog to choose the output returned upon task completion: 82 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

97 Header Includes a descriptive header for each record, such as the task name and target. Return Code Includes the programming codes produced when the task executes. Standard Error Includes all error messages encountered when the task executes. Standard Output Includes all information that results from the task execution. 7. Select one of the following in the Output Destination group box to choose an output 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 the option, inside the output display window, of saving the information to a file. 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 text box. Additional information: Example: /tmp/mytask.out c. Click Set & Close to set your choices and return to the Execute Task window. 8. Choose the endpoints on which you want to run the task by doing one of the following: v Run the task on specific endpoints by doing the following: a. Select the endpoints from the Available Task Endpoints list. b. Click the left arrow button to move the selected endpoints to the Selected Task Endpoints list. OR v Run the task on all subscribers of the specified profile managers by doing the following: a. Select profile managers from the Available Profile Managers list. b. Click the left arrow button to move the selected profile managers to the Selected Profile Managers list. 9. Click Execute or Execute and Dismiss. If the task requires additional input parameters, the task argument window is displayed. Otherwise, the task executes. Chapter 7. Working with tasks and jobs 83

98 Figure 9. Example of a task argument window Customizing a task Additional information: For information about how to fill in the task argument dialog, refer to the task description in the IBM Tivoli Monitoring for Web Infrastructure Reference Guide or click Task Description to display the online help. 10. Click Set & Execute to run the task. Objective To customize one of the standard tasks in the task library so you can save defined arguments for future use. Note: You can only customize tasks that use additional arguments. Background information A customized task is a standard task with defined arguments saved in the task library with a unique name. For example, you can customize a task to save task output results to a file after each execution. Because you can customize task arguments, the Tivoli environment does not display argument dialogs when you run the task from the Tivoli desktop. However, if you run a customized task from the command line, you still must specify the task arguments. Running a customized task requires additional information before it runs, such as the target of the task. 84 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User s Guide

IBM Tivoli Monitoring for Databases: DB2. User s Guide. Version SC

IBM Tivoli Monitoring for Databases: DB2. User s Guide. Version SC IBM Tivoli Monitoring for Databases: DB2 User s Guide Version 5.1.0 SC23-4726-00 IBM Tivoli Monitoring for Databases: DB2 User s Guide Version 5.1.0 SC23-4726-00 Note Before using this information and

More information

Version Monitoring Agent User s Guide SC

Version Monitoring Agent User s Guide SC Tivoli IBM Tivoli Advanced Catalog Management for z/os Version 02.01.00 Monitoring Agent User s Guide SC23-7974-00 Tivoli IBM Tivoli Advanced Catalog Management for z/os Version 02.01.00 Monitoring Agent

More information

IBM Tivoli Monitoring for Business Integration. User s Guide. Version SC

IBM Tivoli Monitoring for Business Integration. User s Guide. Version SC IBM Tioli Monitoring for Business Integration User s Guide Version 5.1.1 SC32-1403-00 IBM Tioli Monitoring for Business Integration User s Guide Version 5.1.1 SC32-1403-00 Note Before using this information

More information

Internet Information Server User s Guide

Internet Information Server User s Guide IBM Tioli Monitoring for Web Infrastructure Internet Information Serer User s Guide Version 5.1.0 SH19-4573-00 IBM Tioli Monitoring for Web Infrastructure Internet Information Serer User s Guide Version

More information

iplanetwebserveruser sguide

iplanetwebserveruser sguide IBM Tioli Monitoring for Web Infrastructure iplanetwebsereruser sguide Version 5.1.0 SH19-4574-00 IBM Tioli Monitoring for Web Infrastructure iplanetwebsereruser sguide Version 5.1.0 SH19-4574-00 Note

More information

IBM Tivoli Federated Identity Manager Version Installation Guide GC

IBM Tivoli Federated Identity Manager Version Installation Guide GC IBM Tivoli Federated Identity Manager Version 6.2.2 Installation Guide GC27-2718-01 IBM Tivoli Federated Identity Manager Version 6.2.2 Installation Guide GC27-2718-01 Note Before using this information

More information

User s Guide for Software Distribution

User s Guide for Software Distribution IBM Tivoli Configuration Manager User s Guide for Software Distribution Version 4.2.1 SC23-4711-01 IBM Tivoli Configuration Manager User s Guide for Software Distribution Version 4.2.1 SC23-4711-01 Note

More information

Error Message Reference

Error Message Reference Security Policy Manager Version 7.1 Error Message Reference GC23-9477-01 Security Policy Manager Version 7.1 Error Message Reference GC23-9477-01 Note Before using this information and the product it

More information

Tivoli Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint

Tivoli Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint Tivoli Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint Version 6.1.0 User s Guide SC32-9490-00 Tivoli Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint Version 6.1.0 User s Guide SC32-9490-00

More information

IBM Security Access Manager for Enterprise Single Sign-On Version 8.2. Administrator Guide SC

IBM Security Access Manager for Enterprise Single Sign-On Version 8.2. Administrator Guide SC IBM Security Access Manager for Enterprise Single Sign-On Version 8.2 Administrator Guide SC23-9951-03 IBM Security Access Manager for Enterprise Single Sign-On Version 8.2 Administrator Guide SC23-9951-03

More information

Installation and Setup Guide

Installation and Setup Guide IBM Tioli Monitoring for Business Integration Installation and Setup Guide Version 5.1.1 SC32-1402-00 IBM Tioli Monitoring for Business Integration Installation and Setup Guide Version 5.1.1 SC32-1402-00

More information

User Management Guide

User Management Guide IBM Tivoli Monitoring for Databases: Oracle User Management Guide Version 5.1.0 GC23-4731-00 IBM Tivoli Monitoring for Databases: Oracle User Management Guide Version 5.1.0 GC23-4731-00 Note Before using

More information

Problem Determination Guide (Revised March 30, 2007)

Problem Determination Guide (Revised March 30, 2007) IBM Tivoli Configuration Manager for Automated Teller Machines Problem Determination Guide (Revised March 30, 2007) Version 2.1 SC32-1411-01 IBM Tivoli Configuration Manager for Automated Teller Machines

More information

IBM Tivoli Composite Application Manager for WebSphere Application Server Version 7.1. Installation Guide

IBM Tivoli Composite Application Manager for WebSphere Application Server Version 7.1. Installation Guide IBM Tivoli Composite Application Manager for WebSphere Application Server Version 7.1 Installation Guide IBM Tivoli Composite Application Manager for WebSphere Application Server Version 7.1 Installation

More information

IBM Tivoli Decision Support for z/os Version Distributed Systems Performance Feature Guide and Reference IBM SH

IBM Tivoli Decision Support for z/os Version Distributed Systems Performance Feature Guide and Reference IBM SH IBM Tivoli Decision Support for z/os Version 1.8.2 Distributed Systems Performance Feature Guide and Reference IBM SH19-4018-13 IBM Tivoli Decision Support for z/os Version 1.8.2 Distributed Systems Performance

More information

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server SA

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server SA IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 5.1.1 SA30-1706-01 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 5.1.1 SA30-1706-01 !, 185 G. (2003

More information

License Administrator s Guide

License Administrator s Guide IBM Tioli License Manager License Administrator s Guide Version 1.1.1 GC23-4833-01 Note Before using this information and the product it supports, read the information under Notices on page 115. Second

More information

Tivoli Management Solution for Domino. Installation and Setup Guide. Version GC

Tivoli Management Solution for Domino. Installation and Setup Guide. Version GC Tivoli Management Solution for Domino Installation and Setup Guide Version 3.2.0 GC32-0755-00 Tivoli Management Solution for Domino Installation and Setup Guide Version 3.2.0 GC32-0755-00 Tivoli Management

More information

Tivoli IBM Tivoli Monitoring for Network Performance

Tivoli IBM Tivoli Monitoring for Network Performance Tivoli IBM Tivoli Monitoring for Network Performance Version 2 Release 1 Operator Guide SC31-6365-00 Tivoli IBM Tivoli Monitoring for Network Performance Version 2 Release 1 Operator Guide SC31-6365-00

More information

Event Management Guide

Event Management Guide Network Manager IP Edition Version 3 Release 9 Event Management Guide SC27-2763-04 Network Manager IP Edition Version 3 Release 9 Event Management Guide SC27-2763-04 Note Before using this information

More information

Federated Identity Manager Business Gateway Version Configuration Guide GC

Federated Identity Manager Business Gateway Version Configuration Guide GC Tivoli Federated Identity Manager Business Gateway Version 6.2.1 Configuration Guide GC23-8614-00 Tivoli Federated Identity Manager Business Gateway Version 6.2.1 Configuration Guide GC23-8614-00 Note

More information

IBM. Planning and Installation. IBM Tivoli Workload Scheduler. Version 9 Release 1 SC

IBM. Planning and Installation. IBM Tivoli Workload Scheduler. Version 9 Release 1 SC IBM Tivoli Workload Scheduler IBM Planning and Installation Version 9 Release 1 SC32-1273-13 IBM Tivoli Workload Scheduler IBM Planning and Installation Version 9 Release 1 SC32-1273-13 Note Before using

More information

IBM Tivoli Decision Support for z/os Version CICS Performance Feature Guide and Reference IBM SH

IBM Tivoli Decision Support for z/os Version CICS Performance Feature Guide and Reference IBM SH IBM Tivoli Decision Support for z/os Version 1.8.2 CICS Performance Feature Guide and Reference IBM SH19-6820-12 IBM Tivoli Decision Support for z/os Version 1.8.2 CICS Performance Feature Guide and Reference

More information

Exchange 2000 Agent Installation Guide

Exchange 2000 Agent Installation Guide IBM Tivoli Identity Manager Exchange 2000 Agent Installation Guide Version 4.5.0 SC32-1156-03 IBM Tivoli Identity Manager Exchange 2000 Agent Installation Guide Version 4.5.0 SC32-1156-03 Note: Before

More information

Tivoli Access Manager for e-business

Tivoli Access Manager for e-business Tivoli Access Manager for e-business Version 6.1 Problem Determination Guide GI11-8156-00 Tivoli Access Manager for e-business Version 6.1 Problem Determination Guide GI11-8156-00 Note Before using this

More information

IBM Tivoli Decision Support for z/os Version Administration Guide and Reference IBM SH

IBM Tivoli Decision Support for z/os Version Administration Guide and Reference IBM SH IBM Tivoli Decision Support for z/os Version 1.8.2 Administration Guide and Reference IBM SH19-6816-14 IBM Tivoli Decision Support for z/os Version 1.8.2 Administration Guide and Reference IBM SH19-6816-14

More information

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino. User s Guide. Version SC

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino. User s Guide. Version SC IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide Version 5.1.0 SC32-0841-00 IBM Tioli Monitoring for Messaging and Collaboration: Lotus Domino User s Guide Version 5.1.0

More information

User sguidefortheviewer

User sguidefortheviewer Tivoli Decision Support for OS/390 User sguidefortheviewer Version 1.6 SH19-4517-03 Tivoli Decision Support for OS/390 User sguidefortheviewer Version 1.6 SH19-4517-03 Note Before using this information

More information

Tivoli Distributed Monitoring for Active Directory Release Notes. Version 3.7

Tivoli Distributed Monitoring for Active Directory Release Notes. Version 3.7 Tivoli Distributed Monitoring for Active Directory Release Notes Version 3.7 Tivoli Distributed Monitoring for Active Directory Release Notes Version 3.7 Tivoli Distributed Monitoring for Active Directory

More information

IBM Tivoli Directory Server

IBM Tivoli Directory Server IBM Tivoli Directory Server White Pages Version 6.1 SC23-7837-00 IBM Tivoli Directory Server White Pages Version 6.1 SC23-7837-00 Note Before using this information and the product it supports, read the

More information

IBM Tivoli Composite Application Manager for Applications Version 7.3. WebSphere MQ Monitoring Agent User's Guide IBM SC

IBM Tivoli Composite Application Manager for Applications Version 7.3. WebSphere MQ Monitoring Agent User's Guide IBM SC IBM Tivoli Composite Application Manager for Applications Version 7.3 WebSphere MQ Monitoring Agent User's Guide IBM SC14-7523-01 IBM Tivoli Composite Application Manager for Applications Version 7.3

More information

Note: Before using this information and the product it supports, read the information in Notices on on page 102.

Note: Before using this information and the product it supports, read the information in Notices on on page 102. IBM Tivoli Storage Area Network Manager, Version 1.3.1 Warehouse Enablement Pack, Version 1.2.0 Implementation Guide for Tivoli Data Warehouse, Version 1.2 SC32-9078-01 Note: Before using this information

More information

CICS Performance Feature Guide and Reference

CICS Performance Feature Guide and Reference Tivoli Decision Support for OS/390 CICS Performance Feature Guide and Reference Version 1.6 SH19-6820-06 Tivoli Decision Support for OS/390 CICS Performance Feature Guide and Reference Version 1.6 SH19-6820-06

More information

IBM DB2 Query Patroller. Administration Guide. Version 7 SC

IBM DB2 Query Patroller. Administration Guide. Version 7 SC IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 IBM DB2 Query Patroller Administration Guide Version 7 SC09-2958-00 Before using this information and the product it supports, be sure

More information

IBM Tivoli Monitoring for Databases. Release Notes. Version SC

IBM Tivoli Monitoring for Databases. Release Notes. Version SC IBM Tivoli Monitoring for Databases Release Notes Version 5.1.1 SC23-4851-00 IBM Tivoli Monitoring for Databases Release Notes Version 5.1.1 SC23-4851-00 Note Before using this information and the product

More information

IBM. Network Health Dashboard Reference - BETA. Network Manager IP Edition Version 4 Release 2

IBM. Network Health Dashboard Reference - BETA. Network Manager IP Edition Version 4 Release 2 Network Manager IP Edition Version 4 Release 2 Network Health Dashboard Reference - BETA IBM Restricted Materials of IBM R4.2 E1 Network Manager IP Edition Version 4 Release 2 Network Health Dashboard

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation and User's Guide SC27-2809-03 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation

More information

IBM SmartCloud Analytics - Log Analysis Version Installation and Administration Guide

IBM SmartCloud Analytics - Log Analysis Version Installation and Administration Guide IBM SmartCloud Analytics - Log Analysis Version 1.1.0.3 Installation and Administration Guide IBM SmartCloud Analytics - Log Analysis Version 1.1.0.3 Installation and Administration Guide Note Before

More information

Limitations and Workarounds Supplement

Limitations and Workarounds Supplement IBM Tivoli Monitoring for Databases: DB2 Limitations and Workarounds Supplement Version 5.1.0 (Revised April 2003) SC23-4786-00 IBM Tivoli Monitoring for Databases: DB2 Limitations and Workarounds Supplement

More information

IBM. Candle OMEGAMON Platform. Configuring IBM Tivoli Candle Management Server on z/os. Tivoli. Version 360 GC

IBM. Candle OMEGAMON Platform. Configuring IBM Tivoli Candle Management Server on z/os. Tivoli. Version 360 GC Tivoli Candle OMEGAMON Platform IBM Version 360 Configuring IBM Tivoli Candle Management Server on z/os GC32-9414-02 12 1 2 Tivoli Candle OMEGAMON Platform IBM Version 360 Configuring IBM Tivoli Candle

More information

Event Management Guide

Event Management Guide Network Manager IP Edition Version 4 Release 1.1 Event Management Guide R4.1.1 E2 Network Manager IP Edition Version 4 Release 1.1 Event Management Guide R4.1.1 E2 Note Before using this information and

More information

Tivoli Data Warehouse

Tivoli Data Warehouse Tivoli Data Warehouse Version 1.3 Tivoli Data Warehouse Troubleshooting Guide SC09-7776-01 Tivoli Data Warehouse Version 1.3 Tivoli Data Warehouse Troubleshooting Guide SC09-7776-01 Note Before using

More information

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide IBM Internet Security Systems IBM Proventia Management SiteProtector Policies and Responses Configuration Guide Version2.0,ServicePack8.1 Note Before using this information and the product it supports,

More information

Tivoli IBM Tivoli Advanced Catalog Management for z/os

Tivoli IBM Tivoli Advanced Catalog Management for z/os Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring Agent User s Guide SC23-9818-00 Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring Agent User s Guide

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations 6.1.2.0 Client Installation and User's Guide SC27-2809-01 IBM Tivoli Storage Manager FastBack for Workstations 6.1.2.0 Client Installation and User's

More information

Understanding Advanced Workflow

Understanding Advanced Workflow IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 IBM Content Manager for iseries Understanding Advanced Workflow Version 5 Release 1 SC27-1138-00 Note Before

More information

IBM. PDF file of IBM Knowledge Center topics. IBM Operations Analytics for z Systems. Version 2 Release 2

IBM. PDF file of IBM Knowledge Center topics. IBM Operations Analytics for z Systems. Version 2 Release 2 IBM Operations Analytics for z Systems IBM PDF file of IBM Knowledge Center topics Version 2 Release 2 IBM Operations Analytics for z Systems IBM PDF file of IBM Knowledge Center topics Version 2 Release

More information

Tivoli IBM OMEGAMON z/os Management Console

Tivoli IBM OMEGAMON z/os Management Console Tivoli IBM OMEGAMON z/os Management Console Version 1.1.1 Planning, Installation, and Configuration Guide GC32-1902-00 Tivoli IBM OMEGAMON z/os Management Console Version 1.1.1 Planning, Installation,

More information

IMS Performance Feature Guide and Reference

IMS Performance Feature Guide and Reference Tivoli Decision Support for z/os IMS Performance Feature Guide and Reference Version 1.7 SH19-6825-08 Tivoli Decision Support for z/os IMS Performance Feature Guide and Reference Version 1.7 SH19-6825-08

More information

IBM Tivoli OMEGAMON XE for Storage on z/os Version Tuning Guide SC

IBM Tivoli OMEGAMON XE for Storage on z/os Version Tuning Guide SC IBM Tivoli OMEGAMON XE for Storage on z/os Version 5.1.0 Tuning Guide SC27-4380-00 IBM Tivoli OMEGAMON XE for Storage on z/os Version 5.1.0 Tuning Guide SC27-4380-00 Note Before using this information

More information

Installation and Setup Guide

Installation and Setup Guide IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version 5.1.1 GC32-0839-01 IBM Tioli Monitoring for Messaging and Collaboration Installation and Setup Guide Version 5.1.1

More information

Network Performance Feature Reference

Network Performance Feature Reference Tivoli Decision Support for OS/390 Network Performance Feature Reference Version 1.6 SH19-6822-07 Tivoli Decision Support for OS/390 Network Performance Feature Reference Version 1.6 SH19-6822-07 Note

More information

Road map for a Typical installation of IBM Tivoli Monitoring, Version 5.1.0

Road map for a Typical installation of IBM Tivoli Monitoring, Version 5.1.0 Road map for a Typical installation of IBM Tivoli Monitoring, Version 5.1.0 Objective To use an installation wizard to deploy IBM Tivoli Monitoring and the Tivoli Management Framework in a typical Tivoli

More information

IBM. IBM Tivoli Composite Application Manager for SOA WSRR Integration Guide

IBM. IBM Tivoli Composite Application Manager for SOA WSRR Integration Guide IBM Tivoli Composite Application Manager for SOA 7.2 Fix Pack 1 (updated November 2015) IBM Tivoli Composite Application Manager for SOA WSRR Integration Guide IBM SC27-4368-01 IBM Tivoli Composite Application

More information

IBM Tivoli Management Solution for Exchange. User s Guide. Version 1.1 GC

IBM Tivoli Management Solution for Exchange. User s Guide. Version 1.1 GC IBM Tivoli Management Solution for Exchange User s Guide Version 1.1 GC23-4721-00 IBM Tivoli Management Solution for Exchange User s Guide Version 1.1 GC23-4721-00 IBM Tivoli Management Solution for Exchange

More information

High Availability Guide for Distributed Systems

High Availability Guide for Distributed Systems IBM Tivoli Monitoring Version 6.3 Fix Pack 2 High Availability Guide for Distributed Systems SC22-5455-01 IBM Tivoli Monitoring Version 6.3 Fix Pack 2 High Availability Guide for Distributed Systems SC22-5455-01

More information

IBM. Planning and Installation. IBM Workload Scheduler. Version 9 Release 4

IBM. Planning and Installation. IBM Workload Scheduler. Version 9 Release 4 IBM Workload Scheduler IBM Planning and Installation Version 9 Release 4 IBM Workload Scheduler IBM Planning and Installation Version 9 Release 4 Note Before using this information and the product it

More information

BEA WebLogic Server Integration Guide

BEA WebLogic Server Integration Guide IBM Tivoli Access Manager for e-business BEA WebLogic Server Integration Guide Version 5.1 SC32-1366-00 IBM Tivoli Access Manager for e-business BEA WebLogic Server Integration Guide Version 5.1 SC32-1366-00

More information

TME 10 Reporter Release Notes

TME 10 Reporter Release Notes TME 10 Reporter Release Notes Version 2.0 April, 1997 TME 10 Reporter (April 1997) Copyright Notice Copyright 1991, 1997 by Tivoli Systems, an IBM Company, including this documentation and all software.

More information

Service Configuration Guide

Service Configuration Guide Business Service Manager Version 6.1 Service Configuration Guide SC23-6041-07 Business Service Manager Version 6.1 Service Configuration Guide SC23-6041-07 Note Before using this information and the product

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation and User's Guide SC27-2809-04 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation

More information

Tivoli Manager for R/3** User s Guide Version 2.1

Tivoli Manager for R/3** User s Guide Version 2.1 Tivoli Manager for R/3** User s Guide Version 2.1 Tivoli Manager for R/3** User s Guide Version 2.1 Tivoli Manager for R/3 User s Guide (September 2000) Copyright Notice Copyright 1997, 2000 by Tivoli

More information

Central Administration Console Installation and User's Guide

Central Administration Console Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Central Administration Console Installation and User's Guide SC27-2808-03 IBM Tivoli Storage Manager FastBack for Workstations Version

More information

IBM Netcool Operations Insight Version 1 Release 4. Integration Guide IBM SC

IBM Netcool Operations Insight Version 1 Release 4. Integration Guide IBM SC IBM Netcool Operations Insight Version 1 Release 4 Integration Guide IBM SC27-8601-00 Note Before using this information and the product it supports, read the information in Notices on page 249. This edition

More information

Tivoli Decision Support 2.1

Tivoli Decision Support 2.1 ,QVWDOODWLRQ*XLGH Tivoli Decision Support 2.1 Tivoli Decision Support 2.1 Installation Guide (October 1999) Copyright 1999 by Tivoli Systems, an IBM Company, including this documentation and all software.

More information

Limitations and Workarounds Supplement

Limitations and Workarounds Supplement IBM Tivoli Monitoring for Databases: Microsoft SQL Server Limitations and Workarounds Supplement Version 5.1.1 SC23-4850-00 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Limitations and Workarounds

More information

Tivoli SecureWay Policy Director WebSEAL. Installation Guide. Version 3.8

Tivoli SecureWay Policy Director WebSEAL. Installation Guide. Version 3.8 Tivoli SecureWay Policy Director WebSEAL Installation Guide Version 3.8 Tivoli SecureWay Policy Director WebSEAL Installation Guide Version 3.8 Tivoli SecureWay Policy Director WebSEAL Installation Guide

More information

IBM Monitoring Agent for Citrix Virtual Desktop Infrastructure 7.2 FP3. User's Guide IBM SC

IBM Monitoring Agent for Citrix Virtual Desktop Infrastructure 7.2 FP3. User's Guide IBM SC IBM Monitoring Agent for Citrix Virtual Desktop Infrastructure 7.2 FP3 User's Guide IBM SC14-7487-02 IBM Monitoring Agent for Citrix Virtual Desktop Infrastructure 7.2 FP3 User's Guide IBM SC14-7487-02

More information

Road Map for the Typical Installation Option of IBM Tivoli Monitoring Products, Version 5.1.0

Road Map for the Typical Installation Option of IBM Tivoli Monitoring Products, Version 5.1.0 Road Map for the Typical Installation Option of IBM Tioli Monitoring Products, Version 5.1.0 Objectie Who should use the Typical installation method? To use the Typical installation option to deploy an

More information

IBM Spectrum Protect HSM for Windows Version Administration Guide IBM

IBM Spectrum Protect HSM for Windows Version Administration Guide IBM IBM Spectrum Protect HSM for Windows Version 8.1.0 Administration Guide IBM IBM Spectrum Protect HSM for Windows Version 8.1.0 Administration Guide IBM Note: Before you use this information and the product

More information

Installation Guide. Tivoli Decision Support 2.0

Installation Guide. Tivoli Decision Support 2.0 Installation Guide Tivoli Decision Support 2.0 Tivoli Decision Support 2.0 Installation Guide (August, 1998) Copyright 1998 by Tivoli Systems, an IBM Company, including this documentation and all software.

More information

IBM Tivoli Decision Support for z/os Version Messages and Problem Determination IBM SH

IBM Tivoli Decision Support for z/os Version Messages and Problem Determination IBM SH IBM Tivoli Decision Support for z/os Version 1.8.2 Messages and Problem Determination IBM SH19-6902-15 IBM Tivoli Decision Support for z/os Version 1.8.2 Messages and Problem Determination IBM SH19-6902-15

More information

Note: Before using this information and the product it supports, read the information in Notices on page 88.

Note: Before using this information and the product it supports, read the information in Notices on page 88. o IBM Tivoli Storage Resource Manager, Version 1.3 Warehouse Enablement Pack, Version 1.2.. Implementation Guide for Tivoli Data Warehouse, Version 1.2 SC32-977-1 Note: Before using this information and

More information

Introduction and Planning Guide

Introduction and Planning Guide Content Manager OnDemand for Multiplatforms Introduction and Planning Guide Version 7.1 GC27-0839-00 Content Manager OnDemand for Multiplatforms Introduction and Planning Guide Version 7.1 GC27-0839-00

More information

Tivoli Inventory 4.0 Provides A Cross-Platform Automated Solution For Inventory Management

Tivoli Inventory 4.0 Provides A Cross-Platform Automated Solution For Inventory Management Software Announcement May 1, 2001 Tivoli Inventory 4.0 Provides A Cross-Platform Automated Solution For Inventory Management Overview Challenged by the need to efficiently maintain accurate IT asset information

More information

Installing and Administering a Satellite Environment

Installing and Administering a Satellite Environment IBM DB2 Universal Database Installing and Administering a Satellite Environment Version 8 GC09-4823-00 IBM DB2 Universal Database Installing and Administering a Satellite Environment Version 8 GC09-4823-00

More information

IBM Tivoli Monitoring for Applications: mysap.com. Reference Guide. Version SC

IBM Tivoli Monitoring for Applications: mysap.com. Reference Guide. Version SC IBM Tivoli Monitoring for Applications: mysap.com Reference Guide Version 5.1.0 SC23-4813-00 IBM Tivoli Monitoring for Applications: mysap.com Reference Guide Version 5.1.0 SC23-4813-00 IBM Tivoli Monitoring

More information

WebSphere Message Broker Monitoring Agent User's Guide

WebSphere Message Broker Monitoring Agent User's Guide IBM Tioli OMEGAMON XE for Messaging on z/os Version 7.1 WebSphere Message Broker Monitoring Agent User's Guide SC23-7954-03 IBM Tioli OMEGAMON XE for Messaging on z/os Version 7.1 WebSphere Message Broker

More information

IBM Proventia Management SiteProtector Installation Guide

IBM Proventia Management SiteProtector Installation Guide IBM Internet Security Systems IBM Proventia Management SiteProtector Installation Guide Version2.0,ServicePack8.1 Note Before using this information and the product it supports, read the information in

More information

Extended Search Administration

Extended Search Administration IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 IBM Lotus Extended Search Extended Search Administration Version 4 Release 0.1 SC27-1404-02 Note! Before using

More information

SAS Model Manager 2.3

SAS Model Manager 2.3 SAS Model Manager 2.3 Administrator's Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2010. SAS Model Manager 2.3: Administrator's Guide. Cary,

More information

Network Problem Resolution Guide

Network Problem Resolution Guide Tivoli Network Manager IP Edition Version 3 Release 8 Network Problem Resolution Guide GC23-9903-02 Tivoli Network Manager IP Edition Version 3 Release 8 Network Problem Resolution Guide GC23-9903-02

More information

IBM Tivoli Configuration Manager for Automated Teller Machines. Release Notes. Version 2.1 SC

IBM Tivoli Configuration Manager for Automated Teller Machines. Release Notes. Version 2.1 SC IBM Tioli Configuration Manager for Automated Teller Machines Release Notes Version 2.1 SC32-1254-00 IBM Tioli Configuration Manager for Automated Teller Machines Release Notes Version 2.1 SC32-1254-00

More information

Tivoli Remote Control V3.7.1 Delivers Enhanced Function for Enterprise Networks

Tivoli Remote Control V3.7.1 Delivers Enhanced Function for Enterprise Networks Software Announcement October 9, 2001 V3.7.1 Delivers Enhanced Function for Enterprise Networks Overview Tivoli Remote Control can help large enterprises save time and money with remote support for distributed

More information

Cisco TEO Adapter Guide for

Cisco TEO Adapter Guide for Release 2.3 April 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part

More information

IBM Tivoli Agentless Monitoring for Windows Operating Systems Version (Revised) User's Guide SC

IBM Tivoli Agentless Monitoring for Windows Operating Systems Version (Revised) User's Guide SC IBM Tivoli Agentless Monitoring for Windows Operating Systems Version 6.2.1 (Revised) User's Guide SC23-9765-01 IBM Tivoli Agentless Monitoring for Windows Operating Systems Version 6.2.1 (Revised) User's

More information

Tivoli Module Builder TivoliReadyQuickStartUser sguide Version 2.4

Tivoli Module Builder TivoliReadyQuickStartUser sguide Version 2.4 Tivoli Module Builder TivoliReadyQuickStartUser sguide Version 2.4 Tivoli Module Builder TivoliReadyQuickStartUser sguide Version 2.4 Tivoli Module Builder QuickStart User s Guide Copyright Notice Copyright

More information

Netcool Configuration Manager Version 6 Release 4. Reference Guide R2E3

Netcool Configuration Manager Version 6 Release 4. Reference Guide R2E3 Netcool Configuration Manager Version 6 Release 4 Reference Guide R2E3 Netcool Configuration Manager Version 6 Release 4 Reference Guide R2E3 Note Before using this information and the product it supports,

More information

Tivoli SecureWay Policy Director Authorization ADK. Developer Reference. Version 3.8

Tivoli SecureWay Policy Director Authorization ADK. Developer Reference. Version 3.8 Tivoli SecureWay Policy Director Authorization ADK Developer Reference Version 3.8 Tivoli SecureWay Policy Director Authorization ADK Developer Reference Version 3.8 Tivoli SecureWay Policy Director Authorization

More information

Tivoli Storage Manager

Tivoli Storage Manager Tivoli Storage Manager Version 6.1 Server Upgrade Guide SC23-9554-01 Tivoli Storage Manager Version 6.1 Server Upgrade Guide SC23-9554-01 Note Before using this information and the product it supports,

More information

Netcool/Impact Version Release Notes GI

Netcool/Impact Version Release Notes GI Netcool/Impact Version 6.1.0.1 Release Notes GI11-8131-03 Netcool/Impact Version 6.1.0.1 Release Notes GI11-8131-03 Note Before using this information and the product it supports, read the information

More information

HPE Operations Bridge Reporter

HPE Operations Bridge Reporter HPE Operations Bridge Reporter Software Version: 10.21 IBM Application Server Content Pack Reference Document Release Date: August 2017 Software Release Date: August 2017 Legal Notices Warranty The only

More information

IBM Tivoli Risk Manager Provides Protection for the Enterprise through Intrusion and Protection Management

IBM Tivoli Risk Manager Provides Protection for the Enterprise through Intrusion and Protection Management Software Announcement October 15, 2002 Provides Protection for the Enterprise through Intrusion and Protection Management Overview IBM Tivoli Risk Manager is an enterprise risk management solution that

More information

Network Manager IP Edition Version 4 Release 2. Event Management Guide IBM R4.2 E4

Network Manager IP Edition Version 4 Release 2. Event Management Guide IBM R4.2 E4 Network Manager IP Edition Version 4 Release 2 Event Management Guide IBM R4.2 E4 Network Manager IP Edition Version 4 Release 2 Event Management Guide IBM R4.2 E4 Note Before using this information and

More information

IBM Tools Base for z/os Version 1 Release 6. IMS Tools Knowledge Base User's Guide and Reference IBM SC

IBM Tools Base for z/os Version 1 Release 6. IMS Tools Knowledge Base User's Guide and Reference IBM SC IBM Tools Base for z/os Version 1 Release 6 IMS Tools Knowledge Base User's Guide and Reference IBM SC19-4372-02 IBM Tools Base for z/os Version 1 Release 6 IMS Tools Knowledge Base User's Guide and Reference

More information

Getting Started. Citrix Load Manager. Version 1.0. Citrix Systems, Inc.

Getting Started. Citrix Load Manager. Version 1.0. Citrix Systems, Inc. Getting Started Citrix Load Manager Version 1.0 Citrix Systems, Inc. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious

More information

IBM Tivoli Storage Manager HSM for Windows Version 7.1. Administration Guide

IBM Tivoli Storage Manager HSM for Windows Version 7.1. Administration Guide IBM Tivoli Storage Manager HSM for Windows Version 7.1 Administration Guide IBM Tivoli Storage Manager HSM for Windows Version 7.1 Administration Guide Note: Before using this information and the product

More information

IBM. Please refer to the attachment for further description. IBM Software Manufacturing Solutions GC

IBM. Please refer to the attachment for further description. IBM Software Manufacturing Solutions GC IBM To: Licensees of Tivoli Workload Scheduler for z/os, Version 9 Subject: Program Number 5698-T08 Release 1, Modification Level 0 Features 5803, 5823, 5843, 5853, 5863 The material you have received

More information

About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software

About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0 Windows 98 Windows 95 Applications and Support Software IBM Personal Computer About Your Software Windows NT Workstation 4.0 Windows

More information

IBM Security Access Manager for Enterprise Single Sign-On Version AccessStudio Guide IBM SC

IBM Security Access Manager for Enterprise Single Sign-On Version AccessStudio Guide IBM SC IBM Security Access Manager for Enterprise Single Sign-On Version 8.2.1 AccessStudio Guide IBM SC23-9956-05 IBM Security Access Manager for Enterprise Single Sign-On Version 8.2.1 AccessStudio Guide IBM

More information