IBM Tivoli Enterprise Console. User s Guide. Version 3.9 SC

Size: px
Start display at page:

Download "IBM Tivoli Enterprise Console. User s Guide. Version 3.9 SC"

Transcription

1 IBM Tioli Enterprise Console User s Guide Version 3.9 SC

2

3 IBM Tioli Enterprise Console User s Guide Version 3.9 SC

4 Note Before using this information and the product it supports, read the information in Notices on page 107. First Edition (August 2003) This edition applies to ersion 3 release 9 of IBM Tioli Enterprise Console (product number 5698-TEC) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents About this guide Who should read this guide Publications IBM Tioli Enterprise Console library..... Related publications i Accessing publications online i Ordering publications ii Contacting software support ii Participating in newsgroups ii Conentions used in this guide iii Typeface conentions iii Operating system-dependent ariables and paths ix IBM Tioli Enterprise Console icons ix Chapter 1. Oeriew Highlights of the 3.9 release Unified system and network management... 1 Optimized eent management for key e-business applications Components of the Tioli Enterprise Console product 3 Adapter Configuration Facility Eent adapter Tioli Eent Integration Facility Tioli Enterprise Console gateway Tioli NetView Eent serer Eent database User interface serer Eent console Eents Internal eents Eent flow Chapter 2. Configuring the Tioli Enterprise Console product Planning for eent management Predefined eent groups Predefined eent consoles Planning for new eent groups Planning for eent group roles Configuring eent adapters Configuring the Tioli Enterprise Console gateway 22 Configuring the eent serer Updating the source list Changing the logging defaults Managing rule bases Creating an eent console Configuring an eent console Creating and changing an eent group Assigning an eent group to an eent console.. 28 Creating an operator Assigning an operator to an eent console Integrating your trouble ticket system with the trouble ticket rules Customizing an eent console Configuring custom buttons for an eent console 33 Exporting and importing eent console definitions Managing Tioli region definitions for the Web ersion of the eent console Tuning the performance of the Web ersion of the eent console Backing up and tuning the eent database Stopping and starting the eent serer Chapter 3. Sample IT enironment with configuration examples Sample IT enironment Fast path to managing eents Eent adapters Eent serer Extending eent management capabilities Eent adapters Eent serer Example 1: All operators get all eents Example 2: Geographic differentiation Example 3: System management differentiation 50 Example 4: Organizational differentiation Example 5: Eent-type differentiation Chapter 4. Managing eents Key concepts for eent management Eent status Eent seerity Primary operator tasks Using the Jaa ersion of the eent console Starting the eent console Exiting the eent console Viewing eents Acknowledging eents Running tasks Running local commands Closing eents Starting the Tioli NetView component Opening a trouble ticket Viewing eent information Viewing eent properties Customizing the eent iewer Using the Web ersion of the eent console Oeriew of the Web ersion of the eent console Starting the Web ersion of the eent console.. 61 Exiting the eent console Viewing eents Acknowledging eents Running tasks Closing eents Viewing a summary of eents Opening a trouble ticket Viewing eent information Copyright IBM Corp iii

6 Viewing eent properties Customizing the eent iewer Chapter 5. Tioli Enterprise Console gateway Configuring the gateway Gateway configuration file Configuring the gateway to receie eents from non-tme adapters Configuring the gateway for state correlation.. 75 Configuring the rate at which eents are sent to the eent serer Starting and stopping the tec_gwr program Starting the tec_gwr program manually Stopping the tec_gwr program manually Obtaining the status of the tec_gwr program on UNIX Appendix A. Troubleshooting Getting started with problem determination Problems locating an eent Understanding eent serer processes Checking the eent flow Problems starting the Tioli Enterprise Console product Problems with rules Enabling rule tracing Tuning rules Problems with the RIM database Analyzing Tioli Management Framework trace logs 90 Problems with the Tioli Enterprise Console gateway Problems with the tec_gateway program Problems with the tec_gwr program Problems with the Web ersion of the eent console 92 Problems with performance Configuring the eent database Additional information sources Appendix B. Messages Notices Trademarks Index i IBM Tioli Enterprise Console: User s Guide

7 About this guide Who should read this guide Publications The IBM Tioli Enterprise Console product is a rule-based, eent management application that integrates system, network, database, and application management to help ensure the optimal aailability of an organization s IT serices. The Tioli Enterprise Console product is preconfigured so that you can manage eents immediately after installation. The IBM Tioli Enterprise Console User s Guide proides an oeriew of the Tioli Enterprise Console product. It proides information about the preconfigured eent consoles, eent groups, and rules, and information about how to use eent consoles to manage eents. This guide also includes step-by-step instructions about configuring the Tioli Enterprise Console product to extend the management capabilities that the Tioli Enterprise Console product automatically proides. This guide is for system administrators, system programmers, and operators who use Tioli products to monitor and manage eents from a broad range of resources to ensure the aailability of these resources. This guide is also useful for network planners and system managers. Readers should be familiar with the following topics: IT enironment you are managing Operating systems that your enterprise uses Tioli Management Framework This section lists publications in the IBM Tioli Enterprise Console library and related documents. It also describes how to access Tioli publications online and how to order Tioli publications. IBM Tioli Enterprise Console library The following documents are aailable in the IBM Tioli Enterprise Console library: The IBM Tioli Enterprise Console Adapters Guide, SC Proides information about supported adapters, including how to install and configure these adapters. IBM Tioli Enterprise Console Command and Task Reference, SC Proides details about IBM Tioli Enterprise Console commands, predefined tasks that are shipped in the task library, and the enironment ariables that are aailable to tasks that run against an eent. IBM Tioli Enterprise Console Installation Guide, SC Describes how to install, upgrade, and uninstall the IBM Tioli Enterprise Console product. IBM Tioli Enterprise Console Release Notes, SC Copyright IBM Corp. 2003

8 Proides release-specific information that is not aailable until just before the product is sent to market. IBM Tioli Enterprise Console Rule Deeloper s Guide, SC Describes how to deelop rules and integrate them for eent correlation and automated eent management. IBM Tioli Enterprise Console Rule Set Reference, SC Proides reference information about the IBM Tioli Enterprise Console rule sets. IBM Tioli Enterprise Console User s Guide, SC Proides an oeriew of the IBM Tioli Enterprise Console product and describes how to configure and use the IBM Tioli Enterprise Console product to manage eents. IBM Tioli Enterprise Console Warehouse Enablement Pack: Implementation Guide, SC Describes how to install and configure the warehouse enablement pack for the IBM Tioli Enterprise Console product and describes the data flow and structures that are used by the warehouse pack. Tioli Eent Integration Facility Reference, SC Describes how to deelop your own eent adapters that are tailored to your network enironment and the specific needs of your enterprise. This reference also describes how to filter eents at the source. Related publications The Tioli Software Glossary includes definitions for many of the technical terms related to Tioli software. The Tioli Software Glossary is aailable, in English only, at the following Tioli software library Web site: Access the glossary by clicking the Glossary link on the left pane of the Tioli software library window. Accessing publications online The product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both. To access the publications using a Web browser, open the infocenter.html file. The file is in the appropriate publications directory on the product CD. IBM posts publications for this and all other Tioli products, as they become aailable and wheneer they are updated, to the Tioli Software Information Center Web site. Access the Tioli Software Information Center by first going to the Tioli software library at the following Web address: Scroll down and click the Product manuals link. In the Tioli Technical Product Documents Alphabetical Listing window, click the Tioli Enterprise Console link to access the product library at the Tioli Information Center. 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 aailable 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. i IBM Tioli Enterprise Console: User s Guide

9 Ordering publications You can order many Tioli publications online at the following Web site: cgibin/pbi.cgi Contacting software support Participating in newsgroups You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, see the following Web site for a list of telephone numbers: If you hae a problem with any Tioli product, refer to the following IBM Software Support Web site: If you want to contact software support, see the IBM Software Support Guide at the following Web site: The guide proides information about how to contact IBM Software Support, depending on the seerity of your problem, and the following information: Registration and eligibility Telephone numbers and addresses, depending on the country in which you are located Information you must hae before contacting IBM Software Support User groups proide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet and are aailable using standard news reader programs. These groups are primarily intended for user-to-user communication and are not a replacement for formal support. To access a newsgroup, use the instructions appropriate for your browser. Use these instructions for a Microsoft Internet Explorer browser. 1. Open an Internet Explorer browser. 2. From the Tools menu, click Internet Options. 3. On the Internet Options window, click the Programs tab. 4. In the Newsgroups list, click the Down Arrow and then click Outlook Express. 5. Click OK. 6. Close your Internet Explorer browser and then open it again. 7. Cut and paste the newsgroup address of a product into the browser Address field, and press Enter to open the newsgroup. About this guide ii

10 Use these instructions for a Netscape Naigator browser. 1. Open a Netscape Naigator browser. 2. From the Edit menu, click Preferences. The Preferences window is displayed. 3. In the Category iew, click Mail & Newsgroups to display the Mail & Newsgroups settings. 4. Select the Use Netscape mail as the default mail application check box. 5. Click OK. 6. Close your Netscape Naigator browser and then open it again. 7. Cut and paste the newsgroup address of a product into the browser Address field, and press Enter to open the newsgroup. IBM Tioli Enterprise Console news://news.software.ibm.com/ibm.software.tioli.enterprise-console IBM Tioli NetView for UNIX and IBM Tioli NetView for Windows news://news.software.ibm.com/ibm.software.tioli.netiew-unix-windows Conentions used in this guide This guide uses seeral conentions for special terms and actions and operating system-dependent commands and paths. Typeface conentions This guide uses the following typeface conentions: Bold Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text 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:) Column headings in a table Keywords and parameters in text Italic Citations (titles of books, diskettes, and CDs) Words defined in text Emphasis of words (words as words) Letters as letters New terms in text (except in a definition list) Variables and alues you must proide Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type iii IBM Tioli Enterprise Console: User s Guide

11 Values for arguments or command options Operating system-dependent ariables and paths This guide uses the UNIX conention for specifying enironment ariables and for directory notation. When using the Windows command line, replace $ariable with % ariable% for enironment ariables and replace each forward slash (/) with a backslash ( \) in directory paths. Note: If you are using the bash shell on a Windows system, you can use the UNIX conentions. IBM Tioli Enterprise Console icons The following icons are used in the IBM Tioli Enterprise Console product. Table 1. Tioli Enterprise Console Icons Icon Represents Eent Serer The red arrow indicates the eent serer is running. A hollow arrow indicates the eent serer is initializing. Rule Base The red arrow indicates the rule base is actie. Profile A profile is a collection of application-specific data. About this guide ix

12 x IBM Tioli Enterprise Console: User s Guide

13 Chapter 1. Oeriew Highlights of the 3.9 release The IBM Tioli Enterprise Console product is a rule-based eent management application that integrates system, network, database, and application management to help ensure the optimal aailability of the IT resources in an enterprise. The Tioli Enterprise Console product: Proides a centralized, global iew of your computing enterprise. Collects, processes, and automatically responds to common management eents, such as a database serer that is not responding, a lost network connection, or a successfully completed batch processing job. Acts as a central collection point for alarms and eents from a ariety of sources, including those from other Tioli software applications, Tioli partner applications, custom applications, network management platforms, and relational database systems. The Tioli Enterprise Console product helps you effectiely process the high olume of eents in an IT enironment by: Prioritizing eents by their leel of importance. Filtering redundant or low-priority eents. Correlating eents with other eents from different sources. Determining who should iew and process specific eents. Initiating automatic correctie actions, when appropriate, such as escalation, notification, and the opening of trouble tickets. Identifying hosts and automatically grouping eents from the hosts that are in maintenance mode in a predefined eent group. This chapter describes the highlights of this release and the components of the Tioli Enterprise Console product. It also proides information about eents and how the Tioli Enterprise Console product processes eents. Two major highlights of this release include unified system and network management and optimized eent management for the following key e-business applications: IBM WebSphere MQ IBM DB2 IBM WebSphere Application Serer Unified system and network management The Tioli Enterprise Console eent management application integrates the IBM Tioli NetView component, thereby unifying system and network management in a single tool. This integration enables the Tioli Enterprise Console product to automatically: Correlate the status of a system or application to the status of the network that it uses. Determine if the root cause of a system or application problem is an underlying network failure. Copyright IBM Corp

14 To unify system and network management, the Tioli Enterprise Console product proides: Automatic filtering and forwarding of network eents from the Tioli NetView component Rules that correlate system-related and network-related eents. These rules are based on predefined associations and help in performing root cause analysis. For example, Subnet Unreachable eents include the subnet number and mask information. This enhanced eent information enables the rules to determine if a serer is on a subnet that is known to be unreachable. If it is, this would impact the applications on that serer, and the unreachable subnet might be the root cause of any application-related eents that hae occurred. These rules significantly reduce the human interention that is typically required to analyze application-failure or system-failure eents and compare them to network-failure eents to determine the actual problem. By automatically correlating system-related and network-related eents, the Tioli Enterprise Console product saes operators time and proides a more reliable method of problem identification. Rules that understand and automatically process network eents. Only eents that require operator action are displayed in the eent console. This reduces clutter, gies operators significantly fewer eents to assess, and remoes the need for operators to manually sort and close preious network status eents. Operators can still find and iew related eents that hae been closed by correlation. Predefined eent consoles and eent groups for Tioli NetView eents, which you can use to manage these eents immediately. You can use the eent groups as they are proided, or you can customize them for your enterprise. For more information, see Planning for eent management on page 19. Ability to start the Tioli NetView Web console from the Jaa ersion of the eent console, which an operator can use to naigate from an eent in the eent console to the associated network topology and diagnostics. Rules automatically synchronize the status between the eent console and the Tioli NetView Web console. Therefore, when an operator responds to a network eent in the eent console, the status of the network element is immediately updated. This enables system and network management operators to analyze and resole problems more efficiently and effectiely. It also improes the communication among the different operators because both the eent console and the network console immediately display the correct status. For more information about the rules that the Tioli Enterprise Console product proides, refer to the IBM Tioli Enterprise Console Rule Set Reference. For more information about the Tioli NetView component, refer to the Tioli NetView documentation at the following Web site: Optimized eent management for key e-business applications To optimize the eent management for key e-business applications, the Tioli Enterprise Console product proides: Predefined eent consoles and eent groups for WebSphere MQ, DB2, and WebSphere Application Serer eents, which you can use to manage these eents immediately. You can use the eent groups as they are proided, or you can customize them for your enterprise. For more information, see Planning for eent management on page IBM Tioli Enterprise Console: User s Guide

15 Rules that identify the root cause of a problem. Because the rules are based on predefined associations among the WebSphere MQ, DB2, and WebSphere Application Serer applications, the rules can determine how the failure of one application affects another application and, therefore, identify the root cause of the problem. For more information about the rules that the Tioli Enterprise Console product proides, refer to the IBM Tioli Enterprise Console Rule Set Reference. Components of the Tioli Enterprise Console product This section proides an oeriew of the following Tioli Enterprise Console components, which are listed in the order in which an eent flows from its source to the operator: Adapter Configuration Facility on page 4 Eent adapter on page 4 Tioli Eent Integration Facility on page 6 Tioli Enterprise Console gateway on page 6 Tioli NetView on page 6 Eent serer on page 6 Eent database on page 8 User interface serer on page 8 Eent console on page 9 The relationship among the components of the Tioli Enterprise Console product is illustrated in the following diagram. Chapter 1. Oeriew 3

16 User interface serer Web browser Eent console (Web ersion) Eent console (Jaa ersion) Tioli NetView component WebSphere Application Serer Eent database serer Eent serer State correlation rules Eent Integration Facility Eent Integration Facility Prolog rules Tioli Enterprise Console gateway Eent Integration Facility Eent Integration Facility Eent Integration Facility Eent Integration Facility Eent sources (TME and non-tme) Tioli NetView component Network management serer SNMP Figure 1. Tioli Enterprise Console components Adapter Configuration Facility The Adapter Configuration Facility proides a graphical user interface (GUI) to configure and distribute TME adapters. You can use the Adapter Configuration Facility to create profiles for adapters and set adapter configuration and distribution options. You can distribute TME adapters to the subscribers of the profile, thus making configuration changes in a central location and then distributing the changes to the remote endpoints or managed nodes. For more information about the Adapter Configuration Facility, refer to the IBM Tioli Enterprise Console Adapters Guide. Eent adapter An eent adapter is a process that typically resides on the same host as a managed source and monitors the source for eents. A source is an application (such as a database) or a system resource (such as aailable disk space). A typical source is a system resource or an application that is running. For example, if you want to monitor the Windows eent log, install the Windows eent log adapter on eery 4 IBM Tioli Enterprise Console: User s Guide

17 host on which you want to monitor the log. You must either run an eent adapter for each source that you want to monitor or modify the source to send eents to the Tioli Enterprise Console product. When an eent adapter receies information from its source, the adapter formats the information and forwards it to the eent serer for interpretation and response, as illustrated in the following diagram. System Resource or Application eent: natie format Eent Adapter eent: Tioli format To eent serer Figure 2. Eent flow from an eent adapter You can configure an eent adapter to discard selected eents instead of forwarding the eents to the eent serer, which reduces network traffic and eent serer workload. An eent adapter sends eents to the eent serer using either a Tioli interface or a non-tioli interface. A Tioli interface is one that runs in a Tioli enironment and a non-tioli interface is one that runs in a non-tioli enironment. Both Tioli and non-tioli types of interfaces send eents using a simple interprocess communication mechanism. The difference between the two interfaces is the method used to establish the connection. Interfaces in a Tioli enironment establish connections using serices that the Tioli Management Framework proides. Interfaces in a non-tioli enironment establish connections using standard interprocess communication mechanisms. You choose the type of connection for your enironment when you install an eent adapter. For more information about installing and configuring eent adapters, refer to the IBM Tioli Enterprise Console Adapters Guide. Many other Tioli products that operate in Tioli or non-tioli enironments proide additional eent adapters. You can also create a specialized eent adapter for your own applications and serices using the Tioli Eent Integration Facility. For information about the Tioli Eent Integration Facility, refer to the Tioli Eent Integration Facility Reference. Eent source buffering An eent adapter can buffer eents. When eent buffering is enabled for an eent adapter and the eent source cannot connect to the eent serer, eents are buffered until a connection can be established to the eent serer. When a connection is established, the eent adapter sends the buffered eents to the eent serer. Secondary eent serers You can specify one or more secondary eent serers for an eent adapter. A secondary eent serer is a backup eent serer that receies eents when the Tioli Enterprise Console gateway cannot contact the adapter-specified eent serer. You can specify one or more secondary eent serers in the Tioli Enterprise Console gateway configuration file. For information information, see Gateway configuration file on page 68. Chapter 1. Oeriew 5

18 Tioli Eent Integration Facility The Tioli Eent Integration Facility is a toolkit that expands the types of eents and system information that you can monitor. Eent adapters monitor managed resources and send eents to the Tioli Enterprise Console product or other applications. You can use the Tioli Eent Integration Facility to deelop your own adapters that are tailored to your network enironment and your specific needs. For more information about the Tioli Eent Integration Facility, refer to the Tioli Eent Integration Facility Reference. Tioli Enterprise Console gateway The Tioli Enterprise Console gateway receies eents from TME and non-tme adapters and forwards them to an eent serer. By default, the Tioli Enterprise Console gateway uses a connection-oriented serice to the eent serer. A connection-oriented serice is one that establishes a connection when the Tioli Enterprise Console gateway is started, and the connection is maintained for all eents. The Tioli Enterprise Console gateway proides the following benefits: Greater scalability, which allows you to manage sources with less software running on the endpoints. Improed performance of the eent serer. The Tioli Enterprise Console gateway bundles eents before sending the eents to the eent serer, which reduces the amount of communication tasks that the eent serer or the Tioli serer must perform. Simple deployment of adapters and updates to adapters using profiles in the Adapter Configuration Facility. Eent correlation and filtering closer to the sources, which reduces the number of eents sent to the eent serer and improes network performance by decreasing the amount of network traffic. For more information about the Tioli Enterprise Console gateway, see Chapter 5, Tioli Enterprise Console gateway, on page 67. Tioli NetView The Tioli NetView component proides the network management function for the Tioli Enterprise Console product. The Tioli NetView component monitors the status of network deices and automatically filters and forwards network-related eents to the Tioli Enterprise Console product. For information about how the Tioli Enterprise Console product processes network-related eents, see Unified system and network management on page 1. For more information about the Tioli NetView component, refer to the Tioli NetView documentation at the following Web site: Eent serer The eent serer proides a centralized location for the management of eents in a distributed enironment. Each Tioli region contains only one eent serer. The eent serer processes input from eent consoles and updates the eent database. Because the eent consoles read data from the eent database, the status of eents on all eent consoles is updated. The eent serer creates an entry in the eent database for each incoming eent and then ealuates these eents against a set of rules to determine if the eent serer should automatically perform any predefined 6 IBM Tioli Enterprise Console: User s Guide

19 tasks or modify the eent. If human interention is required, the eent serer notifies the appropriate operator. The operator performs the required tasks and then notifies the eent serer when the condition that caused the eent has been resoled. Logging incoming eents When reception logging is enabled, the eent serer alidates and logs incoming eents to the eent database. The eent serer assigns a unique identifier and time stamp to each eent and, if the eent is alid, stores the eent in the eent database. When the eent serer receies a alid eent, the eent serer sends the eent to the rule engine for further processing. If the rule engine is busy, incoming eents are stored in a buffer until the rule engine can process the eents. When the rule engine completes processing any buffered eents, the eent serer stores the eent in the eent database. Applying rules When the eent serer receies an eent or when the eent is modified, the eent serer determines if any existing rules apply to that eent. A rule consists of a set of expressions used to determine if an eent meets the rule conditions. A rule also includes a set of actions that are taken when an eent meets the specified rule conditions. Rules help reduce the amount of interpretation and the number of responses required by operators. For example, a particular eent might be known to trigger one or more instances of another eent. In such a case, a rule can be used to automatically downgrade the seerity of the eent or close eents that are known to be caused by the triggering eent. The eent serer can use rules to delay responses to an eent. If responses are delayed for an eent, eent consoles are not updated and the eent serer does not issue an automatic response until the specified amount of time has elapsed. A delayed response might be preferrable, for example, if you hae a self-correcting problem that occasionally occurs on the network. This feature can preent an operator from needlessly responding to a problem. A rule can specify an action to be taken automatically in response to an incoming eent. For example, if an eent indicates that a router is down, the first response might be to attempt to restart the router and gie an operator a low-seerity notice. If the attempts to restart the router within a designated time period fail, a rule can specify that attempts to retry be cancelled and that a higher-seerity notice be sent to an operator. An operator can monitor actions that are automatically performed for an eent. If an operator does not respond to an eent after a specified period of time, the eent serer can take additional actions beyond displaying the eent on an eent console. For example, the eent serer can send an notice of the unacknowledged eent to an operator. If the operator still does not acknowledge the eent, the serer can then perform actions, such as paging the operator or sending an notice to an alternate contact. You can use the predefined rules that the Tioli Enterprise Console product proides, or you can create your own rules. The predefined rules associate resource-related eents and network-related eents to help you to determine the root cause of a problem. For example, the predefined rules can associate an eent that indicates that a DB2 serer is down with an eent that indicates that a specific host is down. This association enables you to quickly determine that the root cause of the eents related to the DB2 application is a network failure and not a DB2 application failure. For information about the predefined rules, refer to the IBM Chapter 1. Oeriew 7

20 Tioli Enterprise Console Rule Set Reference. For information about creating your own rules, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. A rule can specify, but is not limited to, the following actions: Correlating eents Responding automatically to eents, such as running an application or a script Delaying responses to eents Escalating eents Modifing eent attributes Modifying attributes of other eents Preenting duplicate eents from being displayed Dispatching Tioli or other administratie actions on resources Reealuating a set of eents Discarding an eent Generating a new eent Forwarding an eent to another eent serer Eent database The Tioli Enterprise Console product uses an external relational database management system (RDBMS) to store the large amount of eent data that is receied. In this guide, the RDBMS is referred to as the eent database. The RDBMS Interface Module (RIM) component of the Tioli Management Framework is used to access the eent database. For additional information about the eent database, see the IBM Tioli Enterprise Console Installation Guide. User interface serer The user interface (UI) serer is a process that proides communication serices between the eent consoles and the eent serer. The UI serer communicates with the dispatch engine when it needs to contact the eent serer. The UI serer proides transaction locking for eent console status updates and preents multiple eent consoles from responding to the same eent. The UI serer also automatically updates the status of eents on all eent consoles by forwarding the eent changes from the eent consoles to the dispatch engine, which sends the changes to the eent database. For example, when an operator acknowledges an eent, the UI serer automatically updates the status of the eent on each eent console that contains the eent. The UI serer also proides a set of commands that enable an operator to change any eent attribute, list the eents in a specific eent group, and display one message on the operator s desktop. The UI serer can be installed on any managed node in the Tioli region, but only on one managed node. The UI serer does not hae to be located on the same host as the eent serer. The name of the UI serer process is tec_ui_serer. If the UI serer fails, error messages are written in the /tmp/ui_serer log file. The name of this log file is defined in the $BINDIR/TME/TEC/.ui_serer_diag_config file and can be changed. 8 IBM Tioli Enterprise Console: User s Guide

21 Eent console An eent console proides a GUI that operators can use to iew and respond to eents. The Tioli Enterprise Console product proides two ersions of the eent console, a Jaa ersion and a Web ersion. Administrators must use the Jaa ersion to perform configuration tasks. Administrators or operators must use the Jaa ersion to start Tioli NetView functions and to run local automated tasks. Administrators and operators can use the Jaa ersion or the Web ersion, or both, to manage eents. An eent console displays a window for monitoring eent groups, which operators can use to monitor and respond to incoming eents. An eent group is a set of eents that meet certain filter criteria. An administrator defines the eent groups and assigns them to eent consoles for each operator. Operators can hae independent or shared iews of eents. The UI serer preents multiple eent consoles from updating the same eent and updates eent status on all eent consoles. Therefore, only one operator responds to and works on soling a problem. For more information about the UI serer, see User interface serer on page 8. For more information about eent consoles, see Chapter 4, Managing eents, on page 51. Jaa ersion of the eent console The Jaa ersion of the eent console can be installed on a managed node, endpoint, or a host in a non-tioli enironment. The Jaa ersion of the eent console includes the following features: Tioli secure logon for added security. Each eent console retriees eent information directly from the database for high performance and scalability. The eent console refresh rate is configured to allow different eent consoles to be gien different priorities for eent updates. For more information about refresh rates, see the Eent Viewer Preferences entry proided in the online help for the eent console. Ability to run local actions and commands enables third-party or custom scripts and applications to be run easily from the eent console. For more information about running local commands, see the Executing Local Commands entry proided in the online help for the eent console. Ability to run predefined tasks. For more information about running tasks from a task library, see the online help for running tasks in the eent console. Automated tasks can be configured in adance and run when a particular eent is receied by the eent console. For more information about automated tasks, see the automated task entries proided in the online help for the eent console. Ability to iew more information about an eent in a Web page, which helps an operator to determine the actions to perform and whom to contact. When the sample eent information is installed, samples and hooks are proided to help you enable this feature. Customers must proide the additional information to customize their enironment. For more information, see the Web Serer and Eent Information entries proided in the online help for the eent console. Multiple eent details, iewed in a single window with additional contextual information, improing operator understanding. All attributes, including custom attributes, can be displayed and filtered for eent groups with SQL operators. For more information about attributes, see the Eent Group entries proided in the online help for the eent console. Chapter 1. Oeriew 9

22 Multiple operators can be assigned to a single eent console definition. For more information about defining eent consoles and operators, see the online help for the eent console. When editing eent console definitions, all operators assigned to that eent console automatically pick up the changes, thus eliminating the need for scripts to be used to update or create eent consoles. When there are conflicts between eent consoles, such as two operators simultaneously attempting to change the status of an eent, they are resoled automatically and operators are notified. Import and export functions enable the eent console and eent group definitions to be exported to a file for archiing or for easily migrating from the deelopment enironment into production. For more information about importing eent console definitions, see the Exporting and Importing From Other Consoles entry proided in the online help for the eent console. The Jaa ersion of the eent console proides the following iews: Configuration iew The Configuration iew is used to configure both the Jaa ersion and the Web ersion of the eent console. Only administrators hae access to this iew. Summary Chart iew The Summary Chart iew is used to show a high-leel oeriew of the health of resources represented by an eent group. Each eent group is represented by a single bar, similar to a bar graph, on an operator s eent console. To open an eent group, click the bar representing that group. Priority iew In the Priority iew, eent groups are represented by buttons. The buttons representing each eent group display the eent group name and the color of the button representing each eent group corresponds to the color defined for the highest seerity eent contained in that group. To open an eent group, click the button representing that group. Web ersion of the eent console You can use the Web ersion of the eent console to manage eents from your Web browser. The Web ersion of the eent console includes the following features: Tioli secure logon for added security. Eent console definitions, eent group definitions, and preferences that an administrator defines using the Jaa ersion of the eent console take effect for the Web ersion, so that both the Web ersion and the Jaa ersion of the eent console can be administered from a single place. Ability to iew additional information about an eent in a Web page, which helps an operator determine the actions to perform and whom to contact. Multiple eent details with additional contextual information, iewed in a single Web page, improing operator understanding. Multiple operators can be assigned to a single eent console definition. Changes to eent console definitions are automatically reflected in the eent console in the next logon session. The eent console refresh rate can be changed to update eents at an interal that meets your needs. For information about changing the refresh rate, see the online help for changing user preferences in the eent console. Eent iewer data, eent summary data, and task information are cached, reducing the load on the eent serer database and the Tioli Management 10 IBM Tioli Enterprise Console: User s Guide

23 Framework. You can configure the timeout interals for these caches, which helps you to balance your needs for performance and current information. A single installation of the Web ersion of the eent console can be configured to support the installation of the Tioli Enterprise Console product in multiple Tioli regions. Ability to run predefined tasks. When there are conflicts between eent consoles, such as two operators simultaneously attempting to change the status of an eent, they are are resoled automatically and operators are notified. The Web ersion of the eent console organizes the tasks you can perform in a portfolio, which is titled My Work. The portfolio contains the following tasks: Select an Eent Group Lists the eent groups that hae been assigned to the eent console. To manage the eents in an eent group, select the appropriate eent group from the list. An eent iewer is displayed, which contains the eents in the selected eent group. View Summary of Eents Shows a high-leel oeriew of the health of resources represented by an eent group, indicating the number of eents for each eent seerity in each eent group and the total number of eents for each eent seerity. You can also display the percentage of eents for each eent seerity. To manage the eents in an eent group, select the name of the eent group. An eent iewer is displayed, which contains the eents in the selected eent group. Run Tasks Runs predefined tasks from task libraries. Change User Preferences Controls the display of eents in the eent iewer. For example, you can change the automatic refresh rate and the maximum number of eents to display in the eent iewer. Eent groups An eent group is a configured logical area of responsibility that is used to notify users that an eent matching a specified set of criteria has occurred. An administrator configures eent groups using the Jaa ersion of the eent console. For example, if your network contains a group of computers that are used for critical work, you might want to create an eent group that receies eents for these critical computers. This logical grouping of eents is an eent group. For more information about eent groups and attributes, see Chapter 4, Managing eents, on page 51. To define an eent group, you must specify the selection criteria for the eents in the group. This data constitutes an eent group filter. An eent group filter can include any eent attribute except for extended or customer-defined attributes. The following table lists some of the more commonly used attributes for eent group filtering. Chapter 1. Oeriew 11

24 Table 2. Common attributes for eent group filtering Attribute Name Description eent class Specifies the class of the eent, as assigned by the eent source that forwards the eent. The documentation for the eent adapter lists the possible alues for eent classes for adapters. Other Tioli applications, such as Distributed Monitoring, Software Distribution, and Tioli NetView, can also forward eents to the Tioli Enterprise Console product. origin Identifies the protocol address or host name of a host from which you want to receie eents. If you want to monitor an entire subdomain, enter the protocol address or host name of the subdomain. seerity Specifies the seerity of the eent. The Tioli Enterprise Console product uses the following classifications, listed in order of increasing seerity, to indicate the seerity of an incoming eent: UNKNOWN HARMLESS WARNING MINOR CRITICAL FATAL source status A system administrator can also add custom seerities. Specifies the type of application that created the eent. Sources are defined in the eent adapter or the documentation for your application. Possible alues include, but are not limited to, LOGFILE, NT, HPOV, and SNMP. Specifies the status of the eent as follows: Acknowledged An operator or rule acknowledged receipt of the eent. Closed Open An operator or rule reported that the problem that resulted from the eent is resoled. The sending of a closed eent by an eent adapter indicates that a preiously receied eent of the specified class should be closed as a duplicate. The eent serer receied the eent, but an operator or rule has not acknowledged receipt of the eent. organization_supplied_status The STATUS enumeration that is shipped with the Tioli Enterprise Console product includes this placeholder status that a system administrator can customize and define for an organization. Response A rule has automatically responded to the eent. This status is assigned by a rule language predicate. 12 IBM Tioli Enterprise Console: User s Guide

25 You can use SQL wildcard characters for any of the attributes to simplify eent group filtering options. Entering specific alues for each attribute narrows the types of eents reported in an eent group. Using wildcard characters expands the types and number of eents reported in an eent group. Eent group filters enable you to include specific, and possibly ery different, eents in an eent group. Eent group filters also help reduce the number of eent groups that an operator must manage. For example, an administrator can create an eent group composed of three filters to monitor the eents on hosts , , and , but not Without using eent group filters, you would need three eent groups to manage eents from these hosts. Required Tioli authorization roles The Tioli Enterprise Console product requires both Tioli authorization roles and Tioli Enterprise Console eent group roles. Tioli authorization roles are roles defined for the tasks that Tioli Enterprise Console administrators and operators perform in a Tioli management enironment and are set in the Tioli Management Framework product. For information about assigning Tioli authorization roles, refer to the Tioli Management Framework User s Guide. Tioli Enterprise Console eent group roles are the roles defined for managing eents in an eent console. For information about eent group roles, see Planning for eent group roles on page 21. The following table lists the Tioli authorization roles required for the Tioli Enterprise Console product. Table 3. Required Tioli authorization roles Actiity Context Tioli Authorization Role Assigning administratie roles Eent serer senior for the eent serer Configuring super Starting and stopping senior Assigning an operator to an Eent console senior eent console Configuring your own eent user iewer preferences Assigning eent group roles Eent groups senior Creating, modifying, or senior deleting eent groups Assigning eent groups senior Deleting eents Eents senior Acknowledging and closing eents Viewing eents Sending eents Creating, modifying, or loading rule bases Rule base admin, RIM_iew, and RIM_update user and RIM_iew user, if using the wpostemsg command, otherwise none senior Chapter 1. Oeriew 13

26 Table 3. Required Tioli authorization roles (continued) Actiity Context Tioli Authorization Role Installing the Tioli Enterprise Console product Tioli region super Notes: 1. Each operator must be defined as a Tioli administrator with the appropriate authorization roles to manage eents before you can assign the operator to an eent console. 2. If you add an authorization role to a Tioli administrator after the operator starts the eent console, the authorization role does not take affect until the eent console is restarted. 3. Tioli administrators that existed before the installation of Version 3.9 are automatically gien the authorization roles of RIM_iew and RIM_update during the installation of the eent serer. You must manually assign the authorization roles of user, RIM_iew, and RIM_update to Tioli administrators that hae been created after the installation of the eent serer. Eents In the Tioli Enterprise Console product, an eent is an object that has been created based on data that is obtained from a source that is monitored by an eent adapter. Each eent is identified by a class name, which the eent adapter defines. Some examples of class names include Su_Success, Su_Failure, No_Permission, and Printer_Toner_Low. Class names are used to label eents, but each eent contains additional information that helps define and locate a potential problem. Sample eent information is proided as an example to manage requests for additional eent information that an operator might need. Each eent class has a template, which can be modified to include additional information about an eent and the action required to resole the problem. This facilitates the creation of a comprehensie online system of eent information and troubleshooting. For detailed information about eent classes and attributes proided by the adapters shipped with the Tioli Enterprise Console product, refer to the IBM Tioli Enterprise Console Adapters Guide. Seeral communication protocols are aailable for forwarding eents from eent adapters to the eent serer. The security of each protocol aries. Eents use the credibility eent attribute to indicate that the eents hae been receied using Tioli Management Framework serices. A credibility of 1 indicates that the eent was sent from a TME eent adapter and a credibility of 0 indicates the eent was sent from a non-tme adapter. You can use the credibility eent attribute to determine how to respond to an eent, either as a manual response or in an automatic action defined in a rule. Communication between the eent serer and all eent consoles hae the same leel of security as other Tioli communication. Eents are sent as plain, unencrypted text. Internal eents The Tioli Enterprise Console product generates eents internally to proide information about the Tioli Enterprise Console product itself. Each internal eent has one of the following classes: 14 IBM Tioli Enterprise Console: User s Guide

27 TEC_Notice Eents that contain non-error conditions in the Tioli Enterprise Console product. TEC_Error Eents for certain error conditions in the Tioli Enterprise Console product. TEC_DB Eents for eent database access failures. TEC_Start Eents generated when the eent serer is started. TEC_Stop Eents generated when the eent serer is stopped. Eent flow The eent serer architecture consists of the following fie processes. The process names are in parentheses. Master process (tec_serer) Reception engine process (tec_reception) Rule engine process (tec_rule) Dispatch engine process (tec_dispatch) Task engine process (tec_task) Note: An additional process for UI serer, tec_ui_serer, plays an integral part in the oerall Tioli Enterprise Console architecture. The UI serer is not part of the eent serer, although it communicates with the eent serer. For more information, see User interface serer on page 8. These processes are also known as serices when running in a Windows enironment. The serice names hae a.exe file name extension. If any of the eent serer processes fail, error information is written to a log file as described in the following table. The names of these log files are defined in the $BINDIR/TME/TEC/.tec_diag_config file and can be changed. Table 4. Log files for eent serer processes Process tec_serer tec_reception tec_rule tec_dispatch tec_task Log File /tmp/tec_master /tmp/tec_reception /tmp/tec_rule /tmp/tec_dispatch /tmp/tec_task The following figure illustrates the relationships among the eent serer processes. The arrows represent the flow of communication. Chapter 1. Oeriew 15

28 Incoming Tioli eents from non-tioli communication Incoming Tioli eents from Tioli communication Master (tec_serer) Task engine (tec_task) External tasks or programs Reception engine (tec_reception) Rule engine (tec_rule) Dispatch engine (tec_dispatch) UI serer (tec_ui_serer) Console Reception buffer (RAM) Eent cache (RAM) Console Console RDBMS Figure 3. Relationship among eent serer processes Master process The master process coordinates all of the other eent serer processes. If one of the other eent serer processes stops, the master process attempts to restart the process. If the master process cannot restart the process, the master process stops the rest of the processes. The master process also initially receies incoming eents sent from Tioli communication and forwards the eents to the reception engine. Reception engine process The reception engine process receies incoming eents and logs them to the reception log. The reception engine process also sends receied eents to the rule engine for processing. The following figure illustrates the eent reception steps in detail. The state of an eent during the reception process is explained after the figure. The callouts in the figure are described as follows: 1. The reception engine receies eents directly from non-tioli communication or from the master process if the eent was sent from Tioli communication. 2. All incoming eents are written to the reception log, and marked as QUEUED or WAITING. The reception log is actually a table in the eent database. 3. Eents marked QUEUED are sent to the reception buffer. 4. QUEUED eents are sent from the reception buffer to the rule engine for processing. 5. The dispatch engine signals the reception engine when rule engine processing for an eent is completed. The reception engine marks the eent as PROCESSED in the reception log and remoes it from the reception buffer. If the rule engine cannot successfully parse the eent for processing, the eent is marked as PARSING_FAILED in the reception log. 16 IBM Tioli Enterprise Console: User s Guide

29 Figure 4. Reception process Incoming Tioli eents from non-tioli communication 1 Incoming Tioli eents from Tioli communication 1 Master 1 Reception engine Rule engine Dispatch engine Reception log Reception buffer The state of an eent during the reception process (PARSING_FAILED, PROCESSED, QUEUED, and WAITING) is specific to the reception engine and is not an eent attribute. The states are defined as follows: PARSING_FAILED The eent is not alid. Either the eent class is not known to the eent serer, or the eent class attributes are not formatted correctly. The eent is discarded. That is, the reception engine process does not insert the eent into the eent repository, but you can still iew the eent in the reception log. PROCESSED The eent is alid. The rule engine has successfully processed the eent. QUEUED The eent is waiting in the reception buffer for rule engine processing. The reception buffer is a first in, first out (FIFO) queue. If you routinely see QUEUED eents in the output from the wtdumprl command, the rule engine is too busy. If you see only PROCESSED eents in the output from the wtdumprl command, the reception buffer is adequately sized, and rule engine processing is efficient. WAITING The reception buffer is full. When the reception buffer accepts the eent, the reception engine process changes the eent to the QUEUED state. If you routinely see WAITING eents in the output of the wtdumprl command, the reception buffer is not large enough, or the rule engine is too busy, or both. When the eent serer is restarted, the reception engine is reloaded with eents from the reception log that are in the WAITING or the QUEUED state. Chapter 1. Oeriew 17

30 The reception engine does not process internally generated eents (for example, those generated by rules). Internally generated eents neer appear in the reception log or the reception buffer. The reception buffer is located in system memory (RAM). You can configure the size of the reception buffer using the wsetesrcfg command or from the Eent Serer Parameters dialog. Rule engine process The rule engine is a rule-based eent processor. The reception engine sends an eent to the rule engine. Then the eent is ealuated against the rules. After rule processing, the eent is placed into the eent cache of the rule engine. The eent in the rule engine currently being ealuated is referred to as the eent under analysis. An eent that satisfies the specification criteria of a rule causes the rule to run, which means the actions defined by the rule are performed. This is the first input stream into the rule engine. A second input stream comes from the dispatch process. This input stream contains changes made to eents that hae already been receied by the eent serer, typically coming from a change made by actiity at an eent console. A third input stream comes from requests for changes to eents from running actions by the task process. This input stream comes to the rule engine from a task process thread through the dispatch process. The output stream from the rule engine goes to the dispatch process. After an eent is ealuated against the rules, it is forwarded to the dispatch process for storage in the eent repository. The rule engine ealuates and correlates eents with other eents in the eent cache. The rule engine uses the eent cache for its processing, and the eent cache is kept in memory. The rule engine interacts with the dispatch engine to synchronize the updates of its eent cache with the eent database. Dispatch engine process The main functions of the dispatch engine are to keep the eent database current and send updated eent information to the eent consoles. The dispatch engine communicates with the rule engine and the task engine to know when to update eent information. If tasks or programs need to be run for an eent, the dispatch engine contacts the task engine for running them. The dispatch engine also manages requests for eent changes coming from an eent console (through the UI serer) and sends them to the rule engine. When the eent serer is started, the dispatch engine retriees eents from the eent database to reload the eent cache for the rule engine. Task engine process The task engine runs programs, tasks, scripts, and commands initiated by rules. The task engine process monitors these running items and can return their exit statuses to the dispatch engine, which writes the statuses to the eent database. The task engine runs these items as it receies requests to do so. It does not wait for a running item to complete before starting another one. The num_actions attribute for an eent contains the number of actions (tasks or programs) currently being tracked by the eent serer for the eent. 18 IBM Tioli Enterprise Console: User s Guide

31 Chapter 2. Configuring the Tioli Enterprise Console product This chapter is intended for administrators. It describes the planning decisions you need to make and the configuration tasks you can perform so that operators can manage eents. This chapter also proides information about backing up and tuning the eent database, managing Tioli region definitions for the Web ersion of the eent console, and stopping and starting the eent serer. Planning for eent management To manage eents, you and your operators must hae the appropriate Tioli authorization roles. For information about the required Tioli authorization roles, see Required Tioli authorization roles on page 13. You must also decide about the eent groups that will meet your needs. Eent groups specify the eents that are displayed on the eent console based on the filter criteria you specify. When you assign an operator to an eent console, you are defining the area of responsibility for that operator. The Tioli Enterprise Console product proides predefined eent groups and eent consoles so that operators can manage eents immediately with little or no configuration required. If the predefined eent groups and eent consoles do not entirely meet your needs, you can modify the predefined eent groups, and you can create additional eent groups and eent consoles. Predefined eent groups The Tioli Enterprise Console product proides the following predefined eent groups: AllActieEents Eents that are in open and acknowledged state. EbusinessEents Eents for IBM WebSphere Application Serer, DB2, and WebSphere MQ resources that are monitored by the IBM Tioli Monitoring product. UnMonitoredEBusiness Eents for IBM WebSphere Application Serer, DB2, and WebSphere MQ resources that are not being monitored by the IBM Tioli Monitoring product. If the Tioli NetView component is enabled to do port scans, the Tioli NetView component can discoer the hosts that are running IBM WebSphere Application Serer, DB2, or WebSphere MQ resources. The Tioli NetView component then forwards eents related to these resources to the eent serer. ProbableEentAssn Eents that define the probable root cause of eents for IBM WebSphere Application Serer, DB2, or WebSphere MQ resources. For example, if the Tioli Enterprise Console product repeatedly receies a sequence of WebSphere Application Serer eents related to its access to a DB2 resource and at the same time receies eents indicating a DB2 failure, the Tioli Enterprise Console product determines that the root cause of the problem is that the host on which DB2 resides is down. The Tioli Enterprise Console product then sends a TEC_Probable_Eent_Association eent. If you are receiing numerous TEC_Probable_Eent_Association eents, you might need to define this association for the predefined rules Copyright IBM Corp

32 that the Tioli Enterprise Console product uses for root cause analysis. For more information about the predefined rules, refer to the IBM Tioli Enterprise Console Rule Set Reference. Maintenance Maintenance eents that are not closed. Eents in this group are used to inform an operator that a specific system is in maintenance mode. When a system is in maintenance mode, eents from that system cannot be processed. Eents in this eent group can be in open state or acknowledged state. Eents in open state indicate a scheduled maintenance time for the system identified in the eent. Eents in acknowledged state indicate that the system identified in the eent is within the scheduled maintenance time. OpenNetView Tioli Netiew eents that are open. OtherNetView Tioli Netiew eents that are acknowledged or closed. SericeUnaailable Eents from the Tioli Netiew component that indicate that IBM WebSphere Application Serer, DB2, or WebSphere MQ applications are not aailable. Predefined eent consoles The Tioli Enterprise Console product proides the following predefined eent consoles: AdministratieConsole Default eent console to which all predefined eent groups are assigned. This eent console is assigned to the root administrator. The root administrator can immediately manage eents in the predefined eent groups without haing to perform any additional configuration. EBusinessEentsConsole Eent console to which the e-business eent groups (EbusinessEents, UnMonitoredEBusiness, and ProbableEentAssn) are assigned. Assign an operator to this eent console for management of all e-business eents. For information about creating an operator and assigning an operator to an eent console, see Creating an operator on page 29 and Assigning an operator to an eent console on page 29, respectiely. Planning for new eent groups To create your own eent groups (in addition to the predefined eent groups that the Tioli Enterprise Console product proides), you must decide which eents to monitor and which attributes of those eents to use in filters for the eent group. These attributes collectiely constitute the eent group filter. Operators can monitor multiple eent groups. When you define eent groups, you can decide, for example, that an operator is responsible for all NFS-related problems across the network or for only specific hosts. Because eent groups specify the type of eents (such as, all eents from the engineering department) that are displayed on an eent console, the eent group can include eents from seeral different eent sources. (Eent sources refer to the eent adapters that send eents to the eent serer.) Use a worksheet similar to the following to plan your eent groups. Remember that you can filter on all base eent attributes (not extended or customer-defined 20 IBM Tioli Enterprise Console: User s Guide

33 attributes), not only the eent attributes shown in the example. You can use SQL wildcard characters to specify eent filters. For more information about creating an eent group, see Creating an eent group on page 27. Note: When you create an eent group, consider adding a criterion to the filter on the date_reception eent attribute that limits the time range of the eents that are retrieed. Doing this improes performance. Table 5. Worksheet for creating an eent group Eent Group Definition Eent Group: Filter Name Eent Classes Seerity Status Sources Origins Sub-Origins Planning for eent group roles When you assign an eent group to an eent console, you also assign Tioli Enterprise Console eent group roles to the eent console. Assigning an operator to the eent console gies that operator the Tioli Enterprise Console eent group roles associated with that eent console. The access control list (acl) attribute of each eent defines the Tioli Enterprise Console eent group roles that are required to acknowledge and close an eent. The acl attribute can hae a alue of super, senior, admin, or user, or any combination of these. The default alue for the acl attribute is admin. If an eent is configured to be part of two different eent groups and you assign both eent groups to the same eent console with different eent group roles, it is possible that an operator can acknowledge and close the eent in one eent group and only iew the same eent in another eent group. Assume that you hae defined the eent Su_Failure, which has an acl alue of admin, to be part of both the Network and the System eent groups. You hae assigned the Network eent group to an eent console with an eent group role of admin, and you hae assigned the System eent group to the same eent console with an eent group role of user. The operator can acknowledge and close the Su_Failure eent in the Network eent group, but the operator can only iew the Su_Failure eent in System eent group. Use a worksheet similar to the following to correlate each eent group with the eent console and eent group roles to which the eent group is assigned. Table 6. Worksheet for correlating an eent group with an eent console and eent group roles Eent Group Roles Eent Group: Eent console Eent group roles Chapter 2. Configuring the Tioli Enterprise Console product 21

34 Table 6. Worksheet for correlating an eent group with an eent console and eent group roles (continued) Eent Group Roles Eent Group: Configuring eent adapters Eent adapters send eents to the eent serer through the Tioli Management Framework or through standard TCP/IP communication. If you anticipate that an eent adapter will produce eents at a relatiely high rate, or if it is critical that eents be deliered to the eent serer as quickly as possible, you should use a connection-oriented eent deliery method. If you anticipate that an eent adapter will produce eents at a relatiely low rate, and it is not critical that eents be deliered to the eent serer as quickly as possible, you can aoid the system oerhead of maintaining a connection between the eent adapter and the eent serer at all times by using a connectionless eent deliery method. If you use this method, a connection is established when an eent occurs, the eent is sent to the eent serer, and the connection is ended. Third-party endors can also proide eent adapters. For information about installing and configuring eent adapters, refer to the IBM Tioli Enterprise Console Adapters Guide. Configuring the Tioli Enterprise Console gateway Configuring the eent serer If you are using endpoint adapters, you must install and configure the Tioli Enterprise Console gateway. You can also use the Tioli Enterprise Console gateway if you want to consolidate eents at a single point and control the number of eents sent across your network or if you hae geographically dispersed sites and want to consolidate eents locally before eents are sent to a central serer. For more information, see Chapter 5, Tioli Enterprise Console gateway, on page 67. After you configure the eent adapters, you need to configure the components of the eent serer. If you add a new eent adapter to your system, you might need to configure the eent serer. For example, you might need to update an eent source list or add a BAROC file to the rule base. You can configure the following components of the eent serer: Eent source (source list) Eent serer and logging options Rule bases 22 IBM Tioli Enterprise Console: User s Guide

35 Updating the source list The name you use for an eent adapter in the source list must be the same as the source name defined in the eent adapter. The source name of an eent adapter is identified in the documentation for the eent adapter. The source name for an eent adapter is unique to that adapter. Creating a source item When the eent serer is installed, sources are defined for all adapters that the Tioli Enterprise Console product proides. If you add an eent adapter, you must create a source for the adapter. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Create a source Eent serer senior To create a source for an adapter type, follow these steps from the Tioli desktop: 1. Right-click the EentSerer icon and select Sources to display the TEC Source List dialog box. 2. Type the source name in the Name text box. This name must match the source name used for the eents that are produced by the eent adapter. For more information about eent adapters, refer to the IBM Tioli Enterprise Console Adapters Guide. The following list describes the source that corresponds to each eent adapter: Source Adapter AS400_ALERT AS/400 alert AS400_MSGQ AS/400 message HPOV HP OpenView LOGFILE UNIX logfile NT Windows NT and Windows eent log adapters NV390ALT NetView/390 alert NV390MSG NetView/390 message NV6K Tioli NetView adapter SNMP Simple Network Management Protocol 3. Type a description of the source in the Label text box. 4. Click Add Source to add the source item to the Sources scrolling list. 5. Click Sae & Close. For information about using a command to create a source item, refer to the wcrtsrc command in the IBM Tioli Enterprise Console Command and Task Reference. Changing a source item You can change a source item to change the icon or label for the source. Do not change the source name unless you entered a source name that is not alid when you created the source. The following table lists the context and authorization role required to perform this task. Chapter 2. Configuring the Tioli Enterprise Console product 23

36 Actiity Context Required Role Edit a source Configuration iew in the Jaa ersion of the eent console senior To change a source item, follow these steps from the Tioli desktop: 1. Right-click the EentSerer icon and select Sources to display the TEC Source List dialog box. 2. Select the source item to edit from the Sources scrolling list and click Edit. 3. Modify the Name and Label text box as appropriate. 4. Click Replace Source to make your changes. 5. Click Sae & Close. For information about using a command to edit a source item, refer to the wsetsrc command in the IBM Tioli Enterprise Console Command and Task Reference. Deleting a source item Delete a source item when the source item becomes obsolete, for example, when you are no longer using the eent adapter or when a resource is remoed from the network. Delete all eents with an obsolete source from the eent repository and eent cache before deleting the source. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Delete a source Configuration iew in the Jaa ersion of the eent console senior To delete a source item from the source list, follow these steps from the Tioli desktop: 1. Right-click the EentSerer icon and select Sources from the context menu to display the TEC Source List dialog box. 2. Select the source item to be deleted from the Sources scrolling list and click Delete. 3. Click Sae & Close. For information about using a command to delete a source item, refer to the wdelsrc command in the IBM Tioli Enterprise Console Command and Task Reference. Changing the logging defaults You can specify how the eent serer processes Tioli Enterprise Console logs (the type of information to be logged and how long to retain this information). You can also change the default alues of the following items: Size of the eent cache Amount of time to keep eents in the eent cache Amount of time to allow for the eent serer to start Whether or not to actiate rule tracing 24 IBM Tioli Enterprise Console: User s Guide

37 The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Configure the eent serer Eent serer senior To change the default alues for logging, follow these steps from the Tioli desktop: 1. Right-click the EentSerer icon and select Parameters. The Eent Serer Parameters dialog is displayed. 2. The Eent Serer Parameters dialog contains the following options: Log reception of eents Determines whether eents are logged and is used in conjunction with the Time to keep eent reception log information option. Note: This setting is not automatically enforced and is used by the Clean_Database task in the TEC Tasks library. You can run the Clean_Database task immediately or you can schedule the Clean_Database job to run the task later. Maximum number of eent messages buffered in memory Specifies the maximum number of incoming eents to store in the memory of the tec_reception process while the serer processes an existing eent. The default alue is 500 eents. Eent cache size Specifies the maximum number of eents to keep in the eent cache for rule ealuation. The rule engine uses the eents in the eent cache for correlation. The default alue is 1000 eents. Time to keep closed eents in cache Specifies the amount of time, in hours, to keep a closed eent in the eent cache. The default alue is 24 hours. Time to keep eent reception log information Specifies the amount of time, in hours, to keep logged eents. The default alue is 24 hours. This option is aailable when the Log reception of eents option is actiated. Time to keep non-closed eents Specifies the amount of time, in days, to keep an eent that is in the OPEN or ACK state in the eent cache. The default alue is 180 days. Time allowed for serer initialization Specifies the amount of time, in seconds, to allow the eent serer to synchronize its processes. If the serer cannot synchronize its processes within the specified time, the serer generates an error message and shuts down. The default alue is 300 seconds. Trace Rules Determines whether rules are traced and is used in conjunction with the Rule Trace File text box. To trace rules, the rules must be compiled with the tracing option actiated. See the IBM Tioli Enterprise Console Rule Deeloper s Guide for more information about rule tracing. Rule Trace File Specifies the path name for the trace file. The default file name is /tmp/rules.trace. Chapter 2. Configuring the Tioli Enterprise Console product 25

38 3. Click Sae & Close. Stop and restart the eent serer to incorporate the changes. For information about using commands to change the logging defaults, refer to the wsetesrcfg and the wlsesrcfg commands in the IBM Tioli Enterprise Console Command and Task Reference. Managing rule bases You can perform the following rule base operations: List all known rule bases List the rule base currently being used by the eent serer List all the rule sets that are contained in a specified rule base Change the properties of a rule base Create a new rule base Copy a rule base Delete a rule base Add a rule set to a rule base Add class definitions to a rule base Compile a rule base Load a rule base Creating an eent console For information about performing rule base operations, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide and the wrb command in the IBM Tioli Enterprise Console Command and Task Reference. The following table lists the context and Tioli authorization role required to perform this task: Actiity Context Required Role Create an eent console Configuration iew in the Jaa ersion of the eent console senior Configuring an eent console For information about creating an eent console from the Jaa ersion of the eent console, refer to the online help. For information about using a command to create an eent console, refer to the wconsole command in the IBM Tioli Enterprise Console Command and Task Reference. If you are creating eent consoles for multiple administrators, you can copy an existing eent console. To do this, use the c option of the wconsole command. This section describes the configuration tasks to perform if you are not using the predefined eent groups and the predefined eent consoles. It also describes some optional configuration tasks, such as configuring custom buttons for an eent console. You can configure an eent console only from the Jaa ersion of the eent console. The Jaa ersion and the Web ersion of the eent console use the same configuration settings. 26 IBM Tioli Enterprise Console: User s Guide

39 This section describes the following topics: Creating and changing an eent group Assigning an eent group to an eent console on page 28 Creating an operator on page 29 Assigning an operator to an eent console on page 29 Integrating your trouble ticket system with the trouble ticket rules on page 29 Customizing an eent console on page 33 Configuring custom buttons for an eent console on page 33 Exporting and importing eent console definitions on page 38 Creating and changing an eent group This section describes how to create, modify, and delete an eent group. Creating an eent group To create an eent group, you specify the eent filters that define the eents that are to be included in the eent group. After you create an eent group, assign the eent group to one or more eent consoles and then assign an operator to each eent console. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Create an eent group Configuration iew in the Jaa ersion of the eent console senior For information about creating eent groups, eent group filters, and eent group filter constraints, refer to the following entries in the online help. Creating an Eent Group Creating an Eent Group Filter Creating an Eent Group Filter Constraint Creating an Eent Group Filter Constraint with SQL Editing eent group properties When you edit eent group properties, you can change the name or description of the eent group. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Edit eent group properties Configuration iew in the Jaa ersion of the eent console senior For information about editing eent groups properties, see Editing Eent Group Properties in the online help. Editing an eent group filter You might need to edit an eent group filter when users, hosts, and applications are added to or remoed from the network. Chapter 2. Configuring the Tioli Enterprise Console product 27

40 The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Editing an eent group filter Configuration iew in the Jaa ersion of the eent console senior For information about editing an eent group filter, refer to the Editing Eent Group Filter Properties entry in the online help. Deleting an eent group Delete obsolete eent groups to help consere system resources. When you delete an eent group, filters associated with that eent group are also deleted. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Delete an eent group Configuration iew in the Jaa ersion of the eent console senior For information about deleting eent groups, see the Deleting an Eent Group entry in the online help. Deleting eent group filters Filters can be deleted as system resources change. Deleting a filter can change the eents displayed on eent consoles. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Delete a filter Configuration iew in the Jaa ersion of the eent console senior For information about deleting eent group filters, see the Deleting an Eent Group Filter entry in the online help. Assigning an eent group to an eent console After you hae created an eent console, assign one or more eent groups to the eent console. When you assign an eent group to an eent console, you also assign the appropriate eent group roles to the eent console. Assigning an operator to an eent console gies that operator the eent group roles associated with that eent console. For more information about eent group roles, see Planning for eent group roles on page 21. The following table lists the context and authorization role required to perform this task. 28 IBM Tioli Enterprise Console: User s Guide

41 Actiity Context Required Role Assign an eent group Configuration iew in the Jaa ersion of the eent console senior For more information about using and configuring eent consoles, refer to the online help. Creating an operator The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Create an operator Configuration iew in the Jaa ersion of the eent console senior For information about how to create an operator for an eent console, refer to the online help. Assigning an operator to an eent console Before you can assign an operator to an eent console, the operator must be defined as a Tioli administrator and hae the appropriate Tioli authorization roles. For information about defining an administrator, refer to the Tioli Management Framework User s Guide. For information about the authorization roles that the Tioli Enterprise Console product requires, see Required Tioli authorization roles on page 13. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Assign an operator to an eent console Configuration iew in the Jaa ersion of the eent console senior For information about how to assign an operator to an eent console, refer to the online help. Integrating your trouble ticket system with the trouble ticket rules To help you manage problems more efficiently, you can integrate your trouble ticket system, such as Peregrine System s Serice Center, with the Tioli Enterprise Console product. To integrate your trouble ticket system, the Tioli Enterprise Console product proides the following items: Trouble ticket rules, which are defined in the troubleticket.rls file The trouble ticket rules automatically open, update, or close a trouble ticket in response to an eent that meets the criteria you specify. The trouble ticket rules also proide the function to associate an existing trouble ticket with the eent for which the trouble ticket was opened. The troubleticket.rls file is located in the default rule base in the TEC_RULES subdirectory. Chapter 2. Configuring the Tioli Enterprise Console product 29

42 A sample script, TroubleTicket.sh The TroubleTicket.sh script simulates the interface to a trouble ticket system. The TroubleTicket.sh script is located in the Install_dir/bin/interp/TME/TEC directory on the eent serer. As proided, when an eent is receied that matches the eent criteria, the TroubleTicket.sh script writes the eent information in a text file in the /tmp directory named tteentid.log where eentid is the ID of the eent. The TroubleTicket.sh script updates the tteentid.log file with status and seerity changes for the eent and with information about associated eents. The TroubleTicket.sh script also proides the function to perform these actions: Associate an existing trouble ticket ID to an eent Reflect changes made in a trouble ticket in the associated eent To integrate your trouble ticket system with the Tioli Enterprise Console product, complete the following procedures: 1. Customize the trouble ticket rules to automatically respond to eents as described in Customizing the trouble ticket rules. 2. Optionally, customize the TroubleTicket.sh script to add the script that inokes your trouble ticket system so that it automatically opens, updates, and closes a trouble ticket in response to an eent that meets your criteria. 3. Optionally, enable your trouble ticket system to update eents when an action has been performed on a trouble ticket. Note: Your trouble ticket system must be installed and operational. For information about installing your trouble ticket system, refer to the appropriate documentation for your trouble ticket system. Customizing the trouble ticket rules To customize the trouble ticket rules to act on eents that meet the criteria you specify, follow these steps: 1. Load the troubleticket.baroc file, which is located in the default rule base in the TEC_CLASSES subdirectory. The troubleticket.baroc file defines the TT_OPEN_EVENT, the TT_UPDATE_EVENT and the TT_CLOSE_EVENT classes, which the Tioli Enterprise Console product uses to respectiely associate, update, and close eents for existing trouble tickets. 2. Modify the troubleticket.rls file to meet your needs. In particular, you might want to edit the eent criteria that cause the rules to automatically open a trouble ticket in response to an eent. Edit the troubleticket.rls file as follows: a. Change any of the following parameters as appropriate: _tt_admin Specifies the administrator name to use when automatically acknowledging or closing eents. The default alue is troubleticket.rls. _tt_err_log Specifies the name of the log file. The default log file is /tmp/troubleticket.err. _assoc_flag Specifies whether or not multiple eents can be associated with the same trouble ticket. The default alue is ON, which associates multiple eents with the same trouble ticket. To create a trouble ticket for each eent that matches the specified criteria, set this alue to OFF. 30 IBM Tioli Enterprise Console: User s Guide

43 _kbase_file Specifies the name of the file used to store trouble ticket facts in the knowledge base. The default file name is $DBDIR/troubleticket.pro. _tt_elapsed Specifies the amount of time (in seconds) to search backward or forward in the eent cache for an associated eent. The default alue is (one week). b. Specify the eent criteria for which to open a trouble ticket automatically in the configure_knowledge_base action of the tt_configure rule. The eent criteria includes the eent class, seerity, and the fully qualified host name in the eent. To match all possible alues for the eent class, the seerity, or the host name, use an underscore character (_). Herearesome examples. This eent criteria assert_tt(_, _, _) assert_tt(_, CRITICAL, _) assert_tt(_, CRITICAL, myhost.raleigh.ibm.com ) Opens a trouble ticket for All eents All critical eents All critical eents from myhost.raleigh.ibm.com As proided, the troubleticket.rls file defines the following eent criteria: assert_tt( TEC_Error, FATAL, _) This eent criteria causes the trouble ticket rules to open a trouble ticket for all fatal TEC_Error eents from any host. For more information about the trouble ticket rules and rule language predicates, refer to the IBM Tioli Enterprise Console Rule Set Reference. 3. Actiate, compile, and load the troubleticket.rls file. Automatically opening, updating, and closing a trouble ticket The following table describes how the trouble ticket rules and the TroubleTicket.sh script automatically open, update, and close a trouble ticket in response to an eent. This example assumes that you hae customized the trouble ticket rules as described in Customizing the trouble ticket rules on page 30. Chapter 2. Configuring the Tioli Enterprise Console product 31

44 Condition A new eent is receied that matches the specified criteria. The status of an eent associated with a trouble ticket has been changed to any alue other than CLOSED. An eent associated with a trouble ticket has been closed. Action A rule checks the alue of the _assoc_flag parameter in the TroubleTicket.sh script and performs one of these actions: If the alue of the _assoc_flag is ON (the default alue), the rule searches the eent cache for a similar eent (one with the same eent class, seerity, and host name) that has a trouble ticket ID in the ttid eent slot. If such an eent is found in the eent cache, the TroubleTicket.sh script associates the new eent with the existing trouble ticket for the cached eent. The TroubleTicket.sh script sends the trouble ticket ID for the cached eent to the eent serer, and the eent serer updates the ttid eent slot in the new eent with the trouble ticket ID. The TroubleTicket.sh script updates the /tmp/tteentid.log file with information about the associated eent. If a similar eent is not found in the eent cache, the TroubleTicket.sh sends a new trouble ticket ID to the eent serer, and the eent serer updates the ttid eent slot in the new eent with the trouble ticket ID. The TroubleTicket.sh script writes all the eent slots of the eent in the /tmp/tteentid.log file and includes a message indicating that a trouble ticket should be opened for this eent. If the alue of the _assoc_flag is OFF, the TroubleTicket.sh script sends a new trouble ticket ID to the eent serer, and the eent serer updates the ttid eent slot in the new eent with the trouble ticket ID. The TroubleTicket.sh script writes all the eent slots of the eent in the /tmp/tteentid.log file and includes a message indicating that a trouble ticket should be opened for the eent. The TroubleTicket.sh script updates the /tmp/tteentid.log file with information describing the change made to the eent. A rule checks the alue of the _assoc_flag parameter in the TroubleTicket.sh script and performs one of these actions: If the alue of the _assoc_flag is ON (the default alue), the rule searches for an eent in the eent cache that has the same trouble ticket ID in the ttid eent slot and is not closed. If an associated eent is found, the TroubleTicket.sh script updates the /tmp/tteentid.log file with a message indicating that the eent has been closed, but the trouble ticket is still open. If an associated eent is not found, the TroubleTicket.sh script updates the /tmp/tteentid.log file with a message indicating that the original eent for the trouble ticket has been resoled and closed. If the alue of the _assoc_flag is OFF, the TroubleTicket.sh script updates the /tmp/tteentid.log file with a message indicating that the original eent for the trouble ticket has been resoled and closed. Enabling your trouble ticket system to update eents You can enable your trouble ticket system to update eents based on an action that is performed on a trouble ticket. To do this, run the TroubleTicket.sh script, which is located in Install_dir/bin/interp/TME/TEC directory on the eent serer. The TroubleTicket.sh script uses the following parameters: fully_qualified_hostname Name of the host on which the trouble ticket system is running. ttid Trouble ticket ID. eent_handle Value in the eent_handle eent slot of the eent you want to update. date_reception Value in the date_reception eent slot of the eent you want to update. 32 IBM Tioli Enterprise Console: User s Guide

45 serer_handle Value in the serer_handle eent slot of the eent you want to update. slotector Comma separated list of the name=alue pairs for the eent slots that you want to change. Each name=alue pair must be enclosed in single quotation marks as follows: seerity=harmless, source=source1 To update the ttid eent slot of an eent when a new trouble ticket has been opened, run the following command from a script or the command line: TroubleTicket.sh ASSOCIATE_TEC_EVENT fully_qualified_hostname ttid \ eent_handle date_reception serer_handle To update one or more eent slots of an eent (such as, the seerity or status of the eent) when an action is performed on a trouble ticket, run the following command from a script or the command line: TroubleTicket.sh UPDATE_TEC_EVENT fully_qualified_hostname ttid \ eent_handle date_reception serer_handle slotector To close an eent when a trouble ticket has been closed, run the following command from a script or the command line: TroubleTicket.sh CLOSE_TEC_EVENT fully_qualified_hostname ttid \ eent_handle date_reception serer_handle Customizing an eent console You can customize many preference settings for eent consoles. Both the Jaa ersion and the Web ersion of the eent console use these preference settings. For example, you can change the seerity color for eents, and you can customize the fields you want to display in the eent iewer. The eent iewer shows the Eent Type, Status, Class, Seerity, Hostname, Message, and Time Receied fields. You can customize the eent iewer by adding or deleting one or more fields. The eent console preferences are stored centrally in the eent database. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Customize an eent console Editing eent console properties in the Jaa ersion of the eent console senior Some eent console preferences pertain to only the Jaa ersion of the eent console. For example, you can configure eent console appearance properties to display raw alues or percentages in the tool tips in either the Summary Chart iew or the Priority iew of the Jaa ersion of the Web console. You can also customize the Jaa ersion of the eent console to initialize with the eent iewer for a specific eent group using the tec_console command. For more information about the tec_console command, refer to the IBM Tioli Enterprise Console Command and Task Reference. For more information about customizing an eent console, refer to the online help. Configuring custom buttons for an eent console You can configure up to three custom buttons for the Jaa ersion and the Web ersion of the eent console. An operator can then select an eent in the eent iewer and click the custom button to perform a user-defined action. You can Chapter 2. Configuring the Tioli Enterprise Console product 33

46 configure a button in the Jaa ersion of the eent console to run a script or local command on the selected eent. You can configure a button in the Web ersion of the eent console to open a URL in the context of the selected eent and run a Web application. To configure a custom button, you create the button and you associate an action with the button. Use the Console Properties dialog from the Jaa ersion of the eent console to create, modify, or delete custom buttons for an eent console. To display new custom buttons in an eent iewer that is already open, you must close and restart the eent console. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Create, modify, or remoe custom buttons for eent consoles Editing eent console properties in the Jaa ersion of the eent console senior For more information about configuring custom buttons, refer to the online help. Associating an action with a custom button in the Jaa ersion of the eent console The following sections include examples of command scripts that start a Jaa application from a custom button in the eent iewer. When an operator selects an eent and then selects a custom button in the Jaa ersion of the eent console, the attributes of the selected eent are passed to the script as enironment ariables. The SLOTS enironment ariable contains a string array with all eent attributes exported by the eent console, as shown in the following example. SLOTS=num_actions hostname serer_path adapter_host source cause_eent seerity status Each of the eent attributes in the string array are also enironment ariables and can be used indiidually in a custom script. For a complete list of eent attributes aailable to the SLOTS enironment ariable, refer to the IBM Tioli Enterprise Console Command and Task Reference. Note: If enironment ariables were specified to create custom buttons in a prior release, the enironment ariables are ignored when creating custom buttons as console properties. Custom buttons created as console properties always supersede those created by using enironment ariables in prior product ersions. Example command script for running a Jaa application in a Windows enironment: To run a CMD or a BAT file from a custom button in the eent iewer in a Windows enironment, you must first specify off tag as the first line of your command script, as shown in the following example. The following example runs a Jaa application in a Windows enironment using the SLOTS enironment ariable as the Sample script to use as a Custom This script checks information about the selected Eent and it into a temp file. SET TMP_FILE=C:\TEMP\CustomButtonSample.txt 34 IBM Tioli Enterprise Console: User s Guide

47 @REM SLOTS contains all slots defined in the if SLOTS is not defined then NO Eent has selected in the Eent Viewer IF "%SLOTS%" == "" GOTO Initialize new log SET EVENT_ID=%eent_hndl%:%serer_hndl%:%date_reception% ECHO Start log for eent %EVENT_ID% >> %TMP_FILE% ECHO Slots of the selected eent: ECHO %SLOTS% >> %TMP_FILE% >> Use class, status and seerity to determine which action take against the Eent selected IF "%class%" == "TEC_Start" ECHO TEC Serer has been started. >> %TMP_FILE% IF "%class%" == "TEC_Stop" ECHO TEC Serer has been stopped. >> %TMP_FILE% IF "%seerity%" == "FATAL" ECHO Seerity is FATAL: immediate action required. / >> %TMP_FILE% IF "%status%" == "OPEN" ECHO Status is OPEN: no operator is responsible / for this eent. >> Finalize log ECHO Stop log for eent %EVENT_ID% >> %TMP_FILE% GOTO EndScript :NeedEent ECHO No eent has been selected. >> %TMP_FILE% on Example script for running a Jaa application in a UNIX or Linux enironment: To run a shell script from a custom button in the eent iewer within a UNIX or Linux enironment, you must first specify the shell program before the script. If the custom button script starts a graphical application, such as a Jaa GUI, you must specify the export DISPLAY enironment ariable in your script, as shown in the following example. #!/bin/sh export DISPLAY=:0.0 /usr/jdk/bin/jaa MyCustomButton $(SLOTS) The following example starts a Jaa application in a UNIX enironment using the SLOTS enironment ariable as the argument: #!/bin/sh # Sample script to use as a Custom Button # This script checks some information about # the selected Eent and logs it into a temp # file. TMP_FILE=/tmp/CustomButtonSample.txt # SLOTS contains all slots defined in the Eent # if SLOTS is not defined then NO Eent has been # selected in the Eent Viewer if [ "${SLOTS}" = "" ] then echo "You must select an eent to run this script!" Chapter 2. Configuring the Tioli Enterprise Console product 35

48 exit 1 fi # Initialize new log EVENT_ID=${eent_hndl}:${serer_hndl}:${date_reception} echo "Start log for eent ${EVENT_ID}" >> ${TMP_FILE} # Print all slots alues # slot=alue echo "Slots of the selected eent: " >> ${TMP_FILE} for i in ${SLOTS} do alue=`en grep $i grep - SLOTS cut -f2 -d = ` echo "$i = $alue" >> $TMP_FILE done # Use class, status and seerity to determine # which action to take against the Eent selected if [ "${class}" = "TEC_Start" ] then echo "TEC Serer has been started." >> ${TMP_FILE} fi if [ "${class}" = "TEC_Stop" ] then echo "TEC Serer has been stopped." >> ${TMP_FILE} fi if [ "${seerity}" = "FATAL" ] then echo "Seerity is FATAL: immediate action required." >> ${TMP_FILE} fi if [ "${status}" = "OPEN" ] then echo "Status is OPEN: no operator is responsible for this eent." >> ${TMP_FILE} fi # Finalize log echo "Stop log for eent ${EVENT_ID}" >> ${TMP_FILE} echo " " >> ${TMP_FILE} Associating an action with a custom button in the Web ersion of the eent console When an operator selects an eent and then selects a custom button in the Web ersion of the eent console, the attributes of the selected eent are passed to the URL that you defined when you created the custom button. The following example is a sample serlet that can be associated with a custom button. package test.launch; import jaa.io.ioexception; import jaa.io.writer; import jaa.util.enumeration; import jaa.util.iterator; import jaa.util.map; 36 IBM Tioli Enterprise Console: User s Guide import jaax.serlet.serletexception; import jaax.serlet.http.httpserlet; import jaax.serlet.http.httpserletrequest; import jaax.serlet.http.httpserletresponse; /** *<code>samplelaunchintoappserlet</code> serices HTTP requests from eent console. * It does not hae a mapping in the web.xml for the eent console web application.

49 * The purpose of this serlet is to demonstrate the initialization of * different parts of an application when the eent console custom buttons * are configured. * <P> * */ public class SampleLaunchIntoAppSerlet extends HttpSerlet { public static final String CLASSNAME = SampleLaunchIntoAppSerlet.class.getName(); /**************************************************************************** * Implements HttpSerlet.doPost() * <P> * Launch the task specified by the pathinfo of the URI. * request The HTTP request response The HTTP response * ****************************************************************************/ public oid dopost(httpserletrequest request, HttpSerletResponse response) throws SerletException, IOException { // trace entry doget(request, response); // trace exit } /**************************************************************************** * Implements HttpSerlet.doGet() * <P> * Launch the task specified by the pathinfo of the URI. * request The HTTP request response The HTTP response * ****************************************************************************/ public oid doget(httpserletrequest request, HttpSerletResponse response) throws SerletException, IOException { // trace entry // expire all responses immediately so that no pages get cached ConsoleUtilities.setNoCachingHeaders(response); // let s read some request parms! Map parmmap = request.getparametermap(); StringBuffer content = new StringBuffer("Eent Context Information"); content.append("\n<p>request Parameter Map:\n"); String key = null; String[] al = new String[1]; for (Iterator i=parmmap.keyset().iterator(); i.hasnext(); ) { content.append("<p>"); key = (String)i.next(); content.append(key); content.append(": "); System.arraycopy(parmMap.get(key), 0, al, 0, 1); content.append(al[0]); } response.setcontenttype("text/html"); //$NON-NLS-1$ Writer respout = response.getwriter(); // write some basic html here respout.write("<html><head><title>a sample web app launched from a web custom button in context of an eent</title></head><body>"); respout.write(content.tostring()); respout.write("</body></html>"); Chapter 2. Configuring the Tioli Enterprise Console product 37

50 respout.close(); // trace exit } } Exporting and importing eent console definitions Exporting and importing console definitions is an efficient way to create backups and a base set of eent consoles in one Tioli region and import them into other Tioli regions for implementation or additional configuration. Therefore, you can use the eent console definitions in one Tioli region as a single point of control for console configuration in an enironment with multiple Tioli regions. To do this, you export the definitions of eent groups, eent consoles, and operators to a file and then import the definitions to a different installation of the Tioli Enterprise Console product in another Tioli region. After you import the definitions, all Tioli administrators hae the same configuration iew of object definitions for eent consoles in a Tioli region. Exporting and importing definitions from the Tioli desktop The following table lists the context and authorization role required to export and import definitions from the Tioli desktop. Actiity Context Required Role Exporting and Importing Jaa ersion of the eent console senior For more information about exporting and importing eent console definitions, see the Exporting a Console and Importing a Console entries in the online help. Exporting and importing definitions from the command line For information about using the command line to export and import eent console definitions, refer to the wtecexport and the wtecimport commands in the IBM Tioli Enterprise Console Command and Task Reference. Managing Tioli region definitions for the Web ersion of the eent console When the Tioli Enterprise Console product is installed, an administrator can configure the Tioli region definitions for the Web ersion of the eent console within the IBM WebSphere Application Serer product. These definitions specify the following items: Managed nodes to which an operator can connect when logging on to the Web ersion of the eent console User ID and password used to access the RIM database Cache timeout alues for the eent console A Tioli region is represented in the IBM WebSphere Application Serer product by an authentication alias, a data source, and a connection factory as follows: The authentication alias is used to encode and store the user name and password, which the data source uses to access the RIM database. The data source represents the connection to the eent database. Eent data, console definitions, and operator preferences are stored in the eent database. The connection factory performs the following functions: 38 IBM Tioli Enterprise Console: User s Guide

51 Interfaces with the Tioli Management Framework to authenticate operators and alidate that they are authorized to use the eent console Interfaces with the Tioli Management Framework to obtain task information, start tasks, and obtain task results Interfaces with the UI serer to update eents and receie notifications for operators Caches eent and summary information after the information is retrieed from the eent database You might need to add or change the Tioli region definitions after installation for the following reasons: If you add a Tioli region after installation If the host name of the Tioli serer has changed If you want to change the user ID and password that is used to access the RIM database If you want to change the cache timeout alues for the eent console If you delete a Tioli region after installation The procedure in this section describes the information that is releant to the Tioli Enterprise Console product. For specific information about the IBM WebSphere Application Serer product, refer to the online help in the WebSphere Application Serer Administratie console and the IBM WebSphere Application Serer product documentation, which you can access from the WebSphere InfoCenter at the following Web site: To add, change, or delete a Tioli region definition, follow this general procedure: 1. From the WebSphere Application Serer Administratie Console, naigate to Security > JAAS Configuration > J2C Authentication Data to create or change the alias using the following information. Name Type the name of the alias in the following format: TEC_region_host_name_DS_ALIAS User ID Type the user ID to access the RIM database. Password Type the password for the specified user ID. Note: If you are deleting a Tioli region definition, select the name of the appropriate alias and click Delete. 2. Naigate to the Resources > JDBC proiders. Select Serer and then select the JDBC proider for the Tioli Enterprise Console product, TEC RIM JDBC Proider. 3. Click Data Sources. Note: If you are deleting a Tioli region definition, select the name of the appropriate data source, and click Delete. 4. If you want to change the host name or port number of the Tioli serer, go to step 5 on page 40. If you want to create a Tioli region definition, create a data source using the following information: Name Type the name of the data source in the following format: Chapter 2. Configuring the Tioli Enterprise Console product 39

52 TEC_region_host_name_DS Where region_host_name is the fully qualified host name of the Tioli serer. JNDI Name Type jdbc/tec_region_host_name_ds. Datasource Helper Classname Type com.tioli.tec.rimds.rimdatastorehelper. Component-managed Authentication Alias Select the name of the alias you created in Step 1 on page 39 from the drop-down list. Note: Do not create a container-managed authentication alias. 5. Select the name of the data source and click Custom Properties. Add or change two custom properties, one for the serer name and one for the port number. To add a custom property for the serer name, use the following information: Name Type serername. Value Type the host name of the Tioli serer. Type Select jaa.lang.string from the drop-down list. Add the property for the port number with the following information: Name Type portnumber. Value Type the port number for the Tioli serer. The default port number is 94. Type Select jaa.lang.string from the drop-down list. 6. Optionally, change the connection pool properties. To do this, select the name of the data source and click Connection Pool. 7. Naigate to Resources > Resource Adapters. Select Node and then select the resource adapter for the Tioli Enterprise Console product, TEC Resource Adapter. 8. Click J2C Connection Factories. Note: If you are deleting a Tioli region definition, select the name of the appropriate connection factory and click Delete. 9. If you want to change the cache timeout alues, go to step 10 on page 41. If you are creating a Tioli region definition, define one connection factory for the Tioli region using the following information: Name Type the name of the connection factory in the following format: TEC_region_host_name_CF Where region_host_name is the host name of the Tioli serer. JNDI Name Type the following string: eis/tec3_9/tec_region_host_name_cf Note: Do not define any authentication aliases. 40 IBM Tioli Enterprise Console: User s Guide

53 10. Select the name of the connection factory and optionally change the custom properties. You can also optionally change the connection pool properties. You can change any of the following custom properties: eentdatacachetimeout Specifies the amount of time (in seconds) to cache eent data from the eent database. Note: Setting the eentdatacachetimeout alue to less than 60 seconds can impact performance. eentsummarycachetimeout Specifies the amount of time (in seconds) to cache eent summary data. managednodelist Specifies a list of host names, each host name separated by a space, to which an operator can connect when logging on to the eent console. This parameter is required. rimdatasourcename Type the JNDI name of the data source: jdbc/tec_region_host_name_ds This parameter is required. taskcachetimeout Specifies the amount of time (in minutes) to cache task information from the Tioli Management Framework. 11. Click Sae on the taskbar. 12. Stop and restart the WebSphere Application Serer for the changes to take effect. Tuning the performance of the Web ersion of the eent console For optimal performance of the Web ersion of the eent console, consider the following recommendations: Consider the number of open and actie eent groups that are aailable to operators using the Web ersion of the eent console. As the number of actie and open eent groups increases and the eent database grows, you might need to adjust the frequency at which eent iews are refreshed or the rate at which outdated eents are deleted from the eent database. Ensure that the maximum number of connections for the J2C connection pool is greater than the number of users logged in to the Web ersion of the eent console at a gien time. By default, the maximum number of connections for the J2C connections pool is 50. To change the maximum number of connections for the J2C connection pool, follow these steps from the WebSphere Application Serer Administratie Console: 1. Naigate to Resources > Resource Adapters. 2. Select Node and then select the resource adapter for the Tioli Enterprise Console product, TEC Resource Adapter. 3. Click J2C Connection Factories in the Additional Properties section. 4. Select the appropriate connection factory and click Connection Pool in the Additional Properties section. Chapter 2. Configuring the Tioli Enterprise Console product 41

54 5. Type the appropriate alue in the Max connections field and click OK. 6. Sae and confirm your changes. 7. Stop and restart the IBM WebSphere Application Serer to incorporate the changes. Backing up and tuning the eent database To ensure optimal performance of the Tioli Enterprise Console product, back up and tune your eent database on a regular basis. For detailed information about backing up and tuning your database, refer to the appropriate RDBMS database documentation. Also, perform the following tasks on a regular basis: Clear unneeded data from the eent database. To do this, use the wtdbclear command. For information about the wtdbclear command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Update database statistics and reorganize tables and indexes to eliminate fragmentation. To do this, use the wdbmaint.sh command. For information about the wdbmaint.sh command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Stopping and starting the eent serer Some configuration tasks require that you stop and restart the eent serer. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Stop or start the eent serer Tioli desktop senior To stop the eent serer, right-click the Eent Serer icon on the Tioli desktop and select Shut Down. To start the eent serer, right-click the Eent Serer icon on the Tioli desktop and select Start-up. You can also stop and restart the eent serer manually using the wstopesr and the wstartesr commands, respectiely. For more information about the wstopesr and wstartesr commands, refer to the IBM Tioli Enterprise Console Command and Task Reference. If an eent serer goes down, the UI serer reconnects automatically when the serer comes back up. It is not necessary to shut down the UI serer or an eent console to establish communication with the eent serer. 42 IBM Tioli Enterprise Console: User s Guide

55 Chapter 3. Sample IT enironment with configuration examples Sample IT enironment This chapter proides examples that are based on the IT enironment in the Acme Company, a fictitious company, and the key personnel in the Acme Company who are responsible for ensuring the optimal aailability of the IT resources in the Acme Company. The examples illustrate how you can use the preconfigured features of the Tioli Enterprise Console product to begin managing your enironment quickly, efficiently, and effectiely. The examples also illustrate how you can extend the management capabilities that the Tioli Enterprise Console product proides. This sample customer scenario assumes that the Acme Company has its main office in Raleigh, North Carolina, and branch offices in New York, Chicago, and Los Angeles. To support its business, the Acme Company uses the following applications: Business applications that run on IBM WebSphere Application serers WebSphere MQ for messaging serices among the business applications DB2 product for data storage The business applications are distributed among the branch offices with the core parts of the applications installed in the main office in Raleigh. The IP addresses for hosts in the main office range from to The IP addresses for hosts in the branch offices begin with (for New York), (for Chicago), and (for Los Angeles). The Acme Company has the following departments in its main office in Raleigh, North Carolina. Data entry Consists of seen people who primarily enter data into the business applications. The data is stored in a DB2 database that is running on an AIX system in the main office. Marketing Consists of fie people who plan and implement sales strategies. Marketing personnel use the business applications to gather and analyze data. The analytical data is stored in a DB2 warehouse that is running on an AIX system in the main office. Trading Consists of ten people who buy and sell securities. Trading personnel use the business applications, including Web-based applications, to perform their jobs. Information technology Consists of six people who maintain the computer systems and the network. IT personnel use the Tioli Enterprise Console product and other Tioli products to manage and ensure the optimal aailability of the IT resources. Copyright IBM Corp

56 The following people are the system administrators and operators in the Acme Company. Mary is the Database Manager. Mary is responsible for resoling database-related problems. Susan and George are Network Managers. Susan and George are responsible for installing, configuring, and maintaining a heterogeneous network. Susan is the root user and has the administrator role. Jim is the System Manager. Jim is responsible for maintaining and configuring the workstations, printers, and mail systems. Carla is a System Manager. Carla is responsible for installing, configuring and maintaining the business application infrastructure, consisting of IBM WebSphere Application serers and WebSphere MQ messaging serers. Mark is the Help Desk Manager. Mark primarily answers questions about applications that the Acme Company uses. Mark receies notification of all eents so that he can be informed of the types of problems that users might encounter. All system administrators and operators are located in the main office in Raleigh and are responsible for maintaining the aailability of the business applications and the infrastructure that supports the applications without impacting the business objecties of the company. The Acme Company relies on the Tioli Enterprise Console product to maintain aailability of its IT resources because the Tioli Enterprise Console product unifies system and network management and proides optimized eent management for the following key e-business applications: WebSphere MQ DB2 IBM WebSphere Application Serer Fast path to managing eents This example illustrates how Susan, the root administrator, can set up the Tioli Enterprise Console product to manage eents quickly and efficiently. Susan does not need to configure the Tioli Enterprise Console product because she can use the predefined rule sets, eent groups, and eent consoles. Susan only needs to install and set up the adapters and install the rule base with the predefined rule sets to begin managing eents. Susan can also associate each predefined eent group to an eent console and associate the appropriate operator to that area of responsibility so that operators can begin managing eents immediately. Eent adapters The main office uses the IBM Tioli NetView component to manage its network. The local networks in the branch offices are managed with an SNMP-type adapter. A log-file adapter is installed on each indiidual employee s computer (endpoint) on the network. The eent adapters are installed on the same nodes as their respectie resources. A Tioli Management Framework gateway is created on a managed node in each location. The Tioli Management Framework gateway is installed on Shamrock ( ) in the Raleigh office, on Wheeler ( ) in the New York City office, on Fairiew ( ) in the Chicago office, and on Bandera ( ) in the Los Angeles office. A Tioli Enterprise Console gateway is set up in each Tioli Management Framework gateway to perform eent correlation and filtering close 44 IBM Tioli Enterprise Console: User s Guide

57 to the eent source. Endpoints are created on each host (managed node) and indiidual computer (endpoint). Although a host is considered a managed node, an endpoint must be installed to run an eent adapter. The Adapter Configuration Facility is used to distribute and start each adapter on endpoints in the network. This facility is installed on the Tioli serer and all managed nodes in the network. This facility must be used to distribute the adapter to each endpoint. For additional information about the Adapter Configuration Facility, refer to the IBM Tioli Enterprise Console Adapters Guide. Eent serer The eent serer is located in the Raleigh office. It is installed on host wichita, which has an IP address of The default eent serer configuration is used. Serer configuration The default alues are used for the eent serer as follows: Log eents in reception log The default alue is seconds (24 hours). Maximum number of eent messages buffered in memory The default alue is 500 eents. Eent cache size The default alue is eents. Time to keep closed eents in cache The default alue is 24 hours. Time to keep non-closed eents The default alue is 180 days. Time allowed for serer initialization The default alue is 300 seconds. Eent sources The sources used correspond to the eent adapters installed throughout the Acme Company as follows: NV6K LOGFILE SNMP Rule bases Susan uses the Default rule base, which includes the following rule sets: ebusiness.rls Analyzes eents related to the following key e-business serices (IBM WebSphere Application Serer, DB2, and WebSphere MQ) to determine whether the eents are causally related to one another or to network eents. To use the ebusiness.rls rule set, Susan defines the dependency relationships that apply to the e-business serices and network resources and loads the relationships into the knowledge base. netiew.rls Manages eents from the Tioli NetView component. The netiew.rls rules correlate related Tioli NetView eents and manage the synchronization of the eent serer with the Tioli NetView component. Susan also loads and actiates the following rule sets: Chapter 3. Sample IT enironment with configuration examples 45

58 maintenance_mode.rls Proides automated eent processing for a monitored system that is in maintenance mode. By default, eents receied from a system in maintenance mode are closed. notify.rls Supports sending notification to support personnel about new or changed eents. Susan configures the notify.rls rule set to send notification to Mary, the Database Manager, wheneer a critical DB2 eent is receied. Eent groups Susan uses the predefined eent groups to monitor the e-business serices and network resources. The predefined eent groups are: AllActieEents EbusinessEents UnMonitoredEBusiness ProbableEentAssn Maintenance OpenNetView OtherNetView SericeUnaailable The Tioli Enterprise Console product also proides the following predefined eent consoles: AdministratieConsole Default eent console to which all predefined eent groups are assigned. When the Tioli Enterprise Console product is installed, Susan, the root administrator, is automatically assigned to the AdministratieConsole. Because all predefined eent groups are automatically assigned to the AdministratieConsole, Susan can start managing IT resources immediately, receiing and displaying eents in their related eent groups for network impacts, impacts to e-business serices, and so forth. EBusinessEentsConsole Eent console to which the e-business eent groups are assigned. Susan assigns Carla, who is responsible for maintaining the aailability of the business application infrastructure, to the EBusinessEentsConsole. Susan associates the responsibilities of each operator with the predefined eent groups so that the operators can monitor the resources for which they are responsible. To do this, Susan assigns one or more eents groups to an eent console and then assigns the appropriate operator to that eent console. For example, Susan assigns the OpenNetView and the OtherNetView eent groups to an eent console and then assigns George, who is responsible for maintaining the aailability of the network, to that eent console. Susan assigns the AllActieEents to an eent console and assigns Mark, the Help Desk Manager, to that eent console. 46 IBM Tioli Enterprise Console: User s Guide

59 Extending eent management capabilities The examples in this section illustrate how you can extend the eent management capabilities that the Tioli Enterprise Console product proides. For example, Susan can add new adapters and eent sources, change eent serer defaults, and create new eent groups. Eent adapters To extend the eent management capabilities that the Tioli Enterprise Console proides, Susan can customize the adapters that the Tioli Enterprise Console product proides using the Adapter Configuration Facility. For information about the Adapter Configuration Facility, refer to the IBM Tioli Enterprise Console Adapters Guide. Susan can also create new adapters that are tailored to the network enrionment using the Tioli Eent Integration Facility. For information about the Tioli Eent Integration Facility, refer to the Tioli Eent Integration Facility Reference. Eent serer The default alues for the eent serer can be changed to ensure optimal performance. The default alues determine how the eent serer stores and processes logs and how long it should wait for eent serer initialization. To determine the alues to use for the eent serer, Susan starts with an estimate of the number of eents that the eent serer processes on a daily basis. After the eent serer runs for some time and Susan can determine the actual number of eents that the eent serer processes on a daily basis, Susan adjusts the alues to ensure optimal performance. Susan determines the alues for the eent serer based on the following information: Aerage number of eents that the tec_reception process receies daily and stores in the reception log. To determine this information, Susan runs the following command on the eent serer: wtdumper t start_time e end_time grep END wc For more information about the wtdumper command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Aerage number of open eents that are stored daily in the eent repository. To determine this information, Susan runs the following command on the eent serer: wtdumper t start_time e end_time grep "status=open" wc Maximum number of eents that the eent serer can potentially store in memory. Susan must consider the peak periods in which a large number of eents are sent to the eent serer and are queued until the eent serer is able to process them. The eent serer stores queued eents in the reception log and also keeps queued eents in memory. Time period in which to keep open eents for correlation. Time period in which to keep closed eents for correlation. This example assumes the following information: The eent serer receies an aerage of eents daily. The aerage number of open eents that are stored daily in the eent repository is The maximum number of queued eents is Keep non-closed eents for two days for correlation. Chapter 3. Sample IT enironment with configuration examples 47

60 Do not keep closed eents for correlation. Serer configuration Based on the information in this example, Susan configures the eent serer as follows: Log eents in reception log The default alue, seconds (24 hours), is used for this example. Maximum number of eent messages buffered in memory The default alue, 500, is changed to This alue is based on the maximum number of queued eents (3 000 in this example) plus 30% more (900) for padding. If eents get in a WAITING state, the buffer is too small, and the size of the buffer should be increased. Eent cache size The default alue, 1 000, is changed to This alue is based on the aerage number of eents stored daily in the eent repository ( in this example) multiplied by the number of days in which Susan wants eents to remain in open state for correlation (2 in this example) plus 30% more (900) for padding. If the eent cache size is too small, eents might be deleted from the cache when new eents must be stored. In this situation, a Rule Cache full: forced cleaning eent is sent to the eent serer, and the eent cache size should be increased. On the other hand, configuring the eent cache to too large a alue can affect performance when searching the eent cache. Time to keep closed eents in cache The default alue, 24 hours, is changed to 1 hour. This example assumes that closed eents do not need to be correlated and, therefore, do not need to be kept in the eent cache. Time to keep non-closed eents The default alue, 180 days, is changed to 2 days. This example assumes that open eents are kept for two days for correlation. Time allowed for serer initialization The default alue, 300 seconds, is used for this example. Eent sources If Susan adds new adapters, she must create eent sources for the new adapters in addition to the following eent sources that hae already been defined: NV6K LOGFILE SNMP For more information, see Creating a source item on page 23. Rule bases Susan can create a rule set that filters eents based on the eent sources that correspond to the adapters that are installed in the Acme Company. For information about creating a rule set, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. For information about loading and actiating a rule set, refer to the IBM Tioli Enterprise Console Rule Set Reference. Eent groups The following examples show how Susan, the root administrator, creates new eent groups for the Acme Company. Each example contains worksheets for defining 48 IBM Tioli Enterprise Console: User s Guide

61 possible eent groups and operator roles. The examples use a subset of the attributes that you can use to specify filters. You can use any basic attribute of an eent to define a filter. All operators get all eents Geographic differentiation Network topology differentiation Organizational differentiation Eent-type differentiation Susan can assign the new eent groups to the predefined eent consoles, or she can create new eent consoles and assign the eent groups to the new eent consoles. Example 1: All operators get all eents In this example, all operators are notified of all eents. Susan, the root administrator, receies eent notification for informational purposes. Eent Group Filter Constraints All Eents None (specifying no filter means all eents are receied.) None Eent Console Operators Eent Group Roles All Eents Mary, George, Jim, All Eents admin user Carla All Eents root Susan All Eents super senior admin user All Eents Read Only Mark All Eents user Example 2: Geographic differentiation In this example, George in Raleigh resoles network problems for the branch offices in New York, Chicago, and Los Angeles. Susan receies notification because she is George s backup. Because the origins of the remote sites cannot be expressed as a single alue (the main office IP addresses are to ), three filters are created. Eent Group Filter Constraints Sales Network Subnet Source = SNMP Origin LIKE % Subnet Subnet Source = SNMP Origin LIKE % Source = SNMP Origin LIKE % Eent Console Operators Eent Group Roles Sales Network root George Sales Network super senior admin user Sales Network Susan Sales Network senior admin user Chapter 3. Sample IT enironment with configuration examples 49

62 Example 3: System management differentiation In this example, Jim is responsible for resoling all hardware and operating system problems not related to the network. Carla is Jim s backup. Eent Group Filter Constraints System Monitored Sources Source IN LOGFILE, OS2, NT Management Eent Console Operators Eent Group Roles System Management root Jim System Management super senior admin user System Management Carla System Management admin user Example 4: Organizational differentiation In this example, Susan and George are responsible for resoling the network and system problems for the Marketing department. The members of the Marketing department use IP addresses beginning with Eent Group Filter Constraints Marketing Subnet Origin LIKE % Eent Console Operators Eent Group Roles Marketing Susan, George Marketing super senior admin user Example 5: Eent-type differentiation In this example, Susan is responsible for resoling ery specific Tioli NetView problems. George is Susan s backup. The classes are defined in the BAROC file for the Tioli NetView adapter. Three filters are required. Eent Group Filter Constraints Tioli NetView Faults NetView Faults Class IN TEC_ITS_INTERFACE_STATUS, TEC_ITS_NODE_STATUS, TEC_ITS_SUBNET_CONNECTIVITY Source = NV6K Eent Console Operators Eent Group Roles NetView Faults root Susan Tioli NetView Faults super senior admin user NetView Faults George Tioli NetView Faults senior admin user 50 IBM Tioli Enterprise Console: User s Guide

63 Chapter 4. Managing eents This chapter is intended for operators. It describes how to use the eent console to manage eents. The Tioli Enterprise Console product proides two ersions of the eent console: a Jaa ersion and a Web ersion. You can use the Jaa ersion or the Web ersion, or both, to manage eents. Managing eents using the Web ersion of the eent console is ery similar to managing eents using the Jaa ersion of the eent console. Howeer, you need to understand the differences between the two ersions of the eent console. You can run automated tasks that you configure only from the Jaa ersion of the eent console. You can start Tioli NetView functions only from the Jaa ersion of the eent console. You can sort eents based on any number of columns in the Jaa ersion of the eent console. You can sort eents based on up to three columns in the Web ersion of the eent console. Custom buttons are implemented differently in the Jaa ersion and the Web ersion of the eent console. If your administrator has configured one or more custom buttons for the Jaa ersion of the eent console, selecting an eent and then clicking a custom button runs a script or a local command on the selected eent. If your administrator has configured one or more custom buttons for the Web ersion of the eent console, selecting an eent and then clicking a custom button passes the attributes of the selected eent to a predefined URL and runs a Web application. Key concepts for eent management This section describes the following concepts, which are basic to managing eents: Eent status Eent seerity Primary operator tasks Eent status An eent begins in the open state, and an operator can change eents to other states. The possible states of an eent include the following: ACK An operator has acknowledged the eent and assumed responsibility for it. CLOSED The eent has been resoled. An eent adapter can also send an eent with a status of CLOSED to indicate that a preiously receied eent of the specified class should hae the status changed to CLOSE. The preiously receied eent to be closed is the most recent duplicate of the same eent description. The eent is dropped and not stored in the eent database. Do not change the status of a CLOSED eent. custom_status A status that has been added to the STATUS enumeration for site-specific purposes. An administrator defines the STATUS enumeration in the root.baroc file. OPEN No action has been taken on the eent. Copyright IBM Corp

64 RESPONSE A rule has automatically responded to the eent. The RESPONSE status is assigned by a rule language predicate and is not aailable from an eent console. Eent seerity Eents are classified with different seerity leels. The seerity leels help you to focus on the most seere problems first. The eent console uses the following indicators, listed in order of decreasing seerity, to indicate the seerity of an incoming eent: FATAL CRITICAL MINOR WARNING HARMLESS UNKNOWN Custom seerities can be created by adding new enumeration alues to the root.baroc file. Primary operator tasks Whether you use the Jaa ersion or the Web ersion of the eent console to manage eents, your primary tasks are the same. To manage eents, use this basic procedure: 1. Start the eent console. 2. View the eents in an eent group. If an eent is for informational purposes only, go to step 5. If you are responsible for resoling the problem associated with the eent, go to the next step. 3. Acknowledge the eent. You must first acknowledge an eent before you can resole the problem associated with the eent. When you acknowledge an eent, you let other operators know that you hae taken responsibility for the eent. You must hae the appropriate eent group role to acknowlege the eent. 4. Run system management tasks on the eent. A task is a script that runs other Tioli commands. Variable alues are passed to a task when you run the task. The alues passed can come from input parameters and options specified or from eent attributes aailable to the task. For tasks that need the attributes of an eent aailable to them, you must associate the eent with the task. The eent console proides a set of predefined tasks in the task library named T/EC Tasks. The name, T/EC Tasks, shows in task dialogs and is used when specifying the task library from a command line. 5. Close the eent. When you hae completed all the actiities associated with an eent, you can close the eent. Closing an eent requires the same eent console eent group role as acknowledging the eent. 6. Exit the eent console. 52 IBM Tioli Enterprise Console: User s Guide

65 Using the Jaa ersion of the eent console This section describes the tasks you can perform using the Jaa ersion of the eent console. Starting the eent console You can start the eent console from the command line in a bash shell or you can start the eent console from the Windows task bar. Starting the eent console from the command line in a bash shell To start the eent console from the command line in a bash shell, follow these steps: 1. Enter the following command from the bash shell: From a DOS prompt or the bash shell on Windows: tec_console.cmd From a UNIX shell: tec_console The Tioli Management Enironment dialog is displayed. 2. From the Tioli Management Enironment dialog, type the following information in the text fields: The name and port number of your host computer in the following format: host_computer_name:port_number Your Tioli Management Framework login ID Your Tioli Management Framework password 3. Click OK. Starting the eent console from the Windows task bar To start an eent console from the Start menu in a Windows enironment, follow these steps: Note: This option is aailable only when you install an eent console in a non-tioli enironment. 1. From the Windows task bar, click Start > Programs > IBM Tioli Eent Console > IBM Tioli Enterprise Console. The Tioli Management Enironment dialog is displayed. 2. From the Tioli Management Enironment dialog, type the following information in the text fields: The name and port number of your host computer in the following format: host_computer_name:port_number Your Tioli Management Framework login ID Your Tioli Management Framework password 3. Click OK. The tec_console command starts the eent console. This command is located in the $BINDIR/bin directory on the managed node where the eent console is installed. On a host in a non-tioli enironment or an endpoint with the non-tioli ersion of the eent console installed, the command is located in the directory where the eent console was installed. For more information about the tec_console command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Chapter 4. Managing eents 53

66 Exiting the eent console To exit the eent console, select Close from the File menu in the initial iew in the eent console. The initial iew can be the Summary View, the Priority View, or the Configuration View. Viewing eents The Summary Chart iew is the initial iew, which offers a quick iew of the eent actiity of all eent groups for an eent console using stacked bar charts. Click any bar representation of an eent group to display details about that eent group. You can change the initial eent console iew to the Priority iew and click on the button representing a specific eent group to iew eents. For more information about eent iewer options, refer to the online help. The eent iewer displays all eents for a selected eent group. The top pane of the eent iewer displays the Working Queue and the bottom pane displays the All Eents Queue. To hide the Working Queue or the All Eents Queue, expand or collapse the appropriate iew using the arrow button displayed on the horizontal bar between the two iews. The All Eents Queue displays all eents at all times. You can filter the eents displayed in the Working Queue using the filter buttons on the tool bar of the eent iewer. You can iew an eent from the eent console or from the command line. To iew an eent from the eent console, select the eent and click View. For information about using the command line to list eents, refer to the wlsemsg command in the IBM Tioli Enterprise Console Command and Task Reference. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role View an eent Jaa ersion of the eent user, rim_iew console Acknowledging eents You must hae the eent iewer displayed to acknowledge an eent. When you select an eent group in the eent iewer, all eents for that eent group are displayed. To acknowledge eents, select one or more eents from the Working Queue and click Acknowledge. For information about using the command line to acknowledge an eent, refer to the wsetemsg command in the IBM Tioli Enterprise Console Command and Task Reference. The following table lists the context and eent group role required to perform this task. Actiity Context Required Role Acknowledge an eent Jaa ersion of the eent admin console Running tasks You can configure and run tasks from task libraries using eent console dialogs. You can also configure and run most tasks from the command line using the 54 IBM Tioli Enterprise Console: User s Guide

67 wruntask command. For more information about the wruntask command, refer to the Tioli Management Framework Reference Manual. Note: In this section, the term configure means to specify the input parameters and target hosts for the task. To configure and run a task immediately, select Task Execution from the Selected menu in the eent iewer. Details about each task and how to configure and run tasks from the command line are described in the Tioli Enterprise Console Reference and the TEC Library Tasks entries in the online help. The eent console also proides the ability to run automated tasks from the eent console. Automated tasks are configured ahead of time and run when a particular eent is receied. For example, an administrator can configure an automated task to send an message to an administrator when an eent matching the criteria you defined is receied by the eent console. To configure automated tasks, select Automated from the Selected menu in the eent iewer. From the Automated Tasks dialog, you can define or modify the following properties: Name Description When an eent matches Execute these tasks When an automated task completes, the task issues information about its success or failure and the output of the task, if any. A task-completion icon is displayed in the first column of the eent iewer when an automated task completes. You can click the icon to iew details about the automated task results. Automated task results can also be written to a text file, which an administrator configures in the Console Properties dialog for each console. For more information about running an automated task, refer to the Automated Task entries in the online help. Running local commands You can run a user-defined local command on selected eents by running a user-defined script. The attributes of the eent are passed to the script as enironment ariables. The name of the attribute enironment ariables can be referenced by using the non-formatted attribute name. The full list of non-formatted attribute names is contained in the SLOTS enironment ariable, which is passed to the script. To run a local command, follow these steps: 1. From the eent iewer, select the appropriate eent in the Working Queue. 2. From the Selected menu, click Local Command. 3. From the Run dialog box, browse to the location of the script that you want to run. 4. Click OK. Chapter 4. Managing eents 55

68 Closing eents You must hae the eent iewer displayed to close an eent. When you select an eent group in the eent iewer, all eents for that eent group are displayed. To close eents, select one or more eents from the Working Queue and click Close. For information about using the command line to close an eent, refer to the wsetemsg command in the IBM Tioli Enterprise Console Command and Task Reference. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Close an eent Jaa ersion of the eent console admin Starting the Tioli NetView component You can start a Tioli NetView console from the eent iewer in the context of an eent and drill down with Tioli NetView tools to troubleshoot a network problem. You can open the Tioli NetView Submap Explorer, Object Properties, or Diagnosis windows to iew information about a problem node and take action if necessary. To successfully use Tioli NetView functions from the eent iewer, certain prerequisite Tioli NetView software must be installed and configured. For more information, refer to the IBM Tioli Enterprise Console Installation Guide. To run Tioli NetView functions, select NetView from the Selected menu in the eent iewer. For information about using the Tioli NetView functions, refer to the online help in the eent console. For information about using the Tioli NetView network management console, refer to the Tioli NetView documentation at the following Web site: Opening a trouble ticket You can use trouble tickets to track eents or send notification of an eent to someone who does not normally use the eent console. To open a trouble ticket, follow these steps: 1. From the eent iewer, select an eent in the Working Queue. 2. From the Selected menu in the eent iewer, click Trouble Ticket. Note: The implementation of trouble tickets depends on how your administrator integrated your trouble ticket system with the trouble ticket rules that the Tioli Enterprise Console proides. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Open a trouble ticket Jaa ersion of the eent console user 56 IBM Tioli Enterprise Console: User s Guide

69 Viewing eent information You can iew additional information about an eent in a Web page. To do this, an administrator must hae configured the eent console and a CGI program must exist that proides the eent information. To iew eent information in a Web browser, select the appropriate eent in the Working Queue. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role View eent information in the eent iewer Jaa ersion of the eent console user, rim_iew Viewing eent properties To iew details about an eent in the eent iewer, double-click the eent or select one or more eents in the Working Queue and click Details. If you selected more than one eent, you can naigate between the details of each eent by clicking Next or Preious in the eent details window. To iew a category of the details of an eent, click one of the tabs in the eent details window. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role View eent details in the eent iewer Jaa ersion of the eent console user, rim_iew Customizing the eent iewer This section describes the following topics related to customizing the eent iewer: Changing general preferences Changing seerity colors on page 58. Sorting eents on page 59 Filtering eents on page 59 Changing general preferences The preferences control how eents are shown in the eent iewer. To change the general preferences, from the Edit menu in the eent iewer, click Preferences. You can change one or more of the following general preferences: Refresh Time Specifies the rate (in seconds, minutes, or hours) at which eents are automatically refreshed in the eent iewer. Maximum Age of Closed Eent to Display Specifies the maximum age (in seconds, minutes, hours, days, weeks, months, or years) of closed eents to display in the eent iewer. Note: When setting eent time limits on the eent consoles, be aware that eent consoles compare local system time with the date of the eents to determine which eent should be displayed on the eent Chapter 4. Managing eents 57

70 console. For example, if the time on the node is 9:00 and the time on the eent serer is 10:30, all new eents appear to be 90 minutes old to the eent consoles. Maximum Number of Eents Specifies the maximum number of eents to display in the eent iewer. For more information about changing general preferences, refer to the online help. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Change general preferences Jaa ersion of the eent console user Because the general user preferences, the name of the last managed node you logged in to, and your user ID are stored locally in the $HOME/.tmeconsole directory, your preferences are maintained between sessions. Similarly, the preferences you set are used when you log on to the Jaa ersion of the eent console on another computer. Changing seerity colors You can change the seerity colors only if your administrator has made this option aailable to you. Each eent is color-coded to indicate the seerity leel for that eent. The following table lists each default seerity leel and the corresponding default color. Table 7. How eent seerity is indicated in the Jaa ersion of the eent console Seerity FATAL CRITICAL MINOR WARNING HARMLESS UNKNOWN Color Black Red Orange Yellow Green Blue To change the seerity colors, follow these steps: 1. From the Edit menu in the eent iewer, select Preferences. The Preferences window is displayed. 2. From the Preferences window, expand Eent Viewer and then click Seerity Colors. 3. Change the settings in the Seerity Colors window, referring to the online help for additional information. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Change seerity colors Jaa ersion of the eent console user 58 IBM Tioli Enterprise Console: User s Guide

71 Sorting eents You can sort all eents or only eents in the Working Queue based on any eent field in the eent iewer. Initially eents are sorted based on eent seerity. If multiple eents hae the same seerity, the eents are sorted based on the eent date. Eents with the highest seerity are displayed at the bottom, and eents with the lowest seerity are displayed at the top. To sort eents, follow these steps: 1. From the Edit menu in the eent iewer, select Preferences. The Preferences window is displayed. 2. From the Preferences window, expand Eent Viewer and then click either All Eents to sort all eents or Working Queue to sort eents in the Working Queue. 3. Set the sort criteria you want in the Sort window, referring to the online help for additional information. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Sort eents Jaa ersion of the eent console user Filtering eents You can filter the eents in the Working Queue based on seerity, status, and operator ownership to help you focus on important eents. When you filter eents for one eent group, other eent groups are not affected. To filter eents, follow these steps: 1. From the Options menu in the eent iewer, select Filter Eents. 2. Select the checkboxes for the types of eents you want to display in the eent iewer. Clear the checkboxes for the types of eents you do not want to display in the eent iewer. The following table lists the context and authorization role required to perform this task. Actiity Context Required Role Filter eents by seerity and status Jaa ersion of the eent console user For information about using a command to list eents based on seerity and status to standard output, refer to the wlsemsg command in the IBM Tioli Enterprise Console Command and Task Reference. Using the Web ersion of the eent console This section describes the tasks you can perform using the Web ersion of the eent console. Oeriew of the Web ersion of the eent console The Web ersion of the eent console is comprised of the following areas: Chapter 4. Managing eents 59

72 Portfolio The primary way that your work is organized within the eent console. It is titled My Work. Each entry in the portfolio represents a task that you can perform. The following table describes the tasks in the portfolio. Table 8. Portfolio tasks in the Web ersion of the eent console Task Function Select an Eent Group Lists the eent groups aailable to the operator. An operator can select an eent group to iew the eents assigned to the operator. View Summary of Eents Displays a table that summarizes eents by seerity. Run Tasks Runs predefined tasks from task libraries when an eent is not required to run the task. Note: When an eent is required to run the task, you must run the task from the eent iewer. Change User Preferences Changes how eents are shown in the eent iewer. Welcome Displays the Welcome page. The portfolio is open when you start the eent console. To close and open the portfolio, click the Hide Tasks and Show Tasks icons, respectiely, on the left side of the tool bar in the eent console. You might want to close the portfolio to increase the size of the work area. Work Area The area in which task windows are displayed. When the portfolio is closed, the entire page is the work area. taskbar The bar that is located aboe the work area. The taskbar contains a button for each task that you start so that you can switch between tasks. The taskbar also contains the following icons: All Tasks Displays the Task Manager, which contains a list of all tasks you hae started. To switch to a task, select the task and click Switch Task. To end a task, select the task and click End Task. The All Tasks icon is located on the far left corner of the taskbar. Sign Off Signs off the eent console. The Sign Off icon is located on the far right corner of the taskbar. Recent Eent Groups The area of the portfolio that contains the last fie eent groups that hae been iewed in the eent iewer. Task button A button on the taskbar that represents each portfolio task that you hae started. When you click a task button, the associated task window opens in the work area. Task Assistant Help for the currently displayed portfolio task. The Task Assistant is represented by a question mark in the upper right corner of the eent console. When it is open, the Task Assistant is displayed within the eent console to the right of the work area. For windows that require user input, 60 IBM Tioli Enterprise Console: User s Guide

73 you can also display field descriptions. The icon for field descriptions is represented by an i. This icon is located to the left of the Task Assistant icon. Task Close The icon on the far right of the title bar of the work area, which you can use to close the task that is displayed. Note: When using the Web ersion of the eent console, you might find that some pages display better if you reduce the size of the text. Use the controls that your Web browser proides to reduce the size of the text. Starting the Web ersion of the eent console To sign on to the the eent console, follow these steps: 1. Open your Web browser. 2. Type the address your administrator proided, which is similar to the following example: Where computer_name is the fully-qualified name of a computer where the Web serer is running. 3. Type your Tioli Management Framework user ID in the User Name field. 4. Type the password for the specified user ID in the Password field. 5. Select the appropriate managed node from the Serer Name drop-down list. 6. Click OK. Exiting the eent console To exit the eent console, click the Sign Off icon in the right corner of the taskbar. Viewing eents To iew eents, follow these steps: 1. Click Select an Eent Group from the portfolio in the eent console. A list of eent groups is displayed. 2. Click the name of the appropriate eent group. An eent iewer is opened, which contains the eents in the selected eent group. The eent iewer automatically refreshes at specific time interals. To suspend the automatic refresh, click the Suspend icon on the toolbar. To resume the refresh, click the Resume icon. The status bar at the bottom of the window indicates if automatic refresh is enabled, suspended, or needed (automatic refresh has been suspended and the refresh interal has been exceeded). You can also select an eent group from the Summary of Eents table. To iew the Summary of Eents table, click View Summary of Eents from the portfolio. Acknowledging eents To acknowledge eents, select one or more eents in the eent iewer and click Acknowledge on the tool bar. You can also use wsetemsg command to acknowledge an eent. For more information about the wsetemsg command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Chapter 4. Managing eents 61

74 Running tasks To run a task, choose one of these methods: If the task requires a source eent, select one or more eents in the eent iewer. Then select Run Task from the Action menu in the eent iewer and click Go. If the task does not require a source eent, select Run Tasks from the portfolio. The task wizard guides you through the steps required to run the task. For more information about running a task, refer to the online help in the eent console. The task results are shown in a new window of your Web browser. Use the print option of your Web browser controls to print the task results. You can also run most tasks from the command line using the wruntask command. For more information about the wruntask command, refer to the Tioli Management Framework Reference Manual. For information about tasks in the T/EC Tasks library, refer to the Tioli Enterprise Console Reference. Closing eents To close eents, select one or more eents in the eent iewer and click Close on the tool bar. You can also use the wsetemsg command to close an eent. For information about the wsetemsg command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Viewing a summary of eents To iew a summary of the eents contained in each eent group, select View Summary of Eents from the portfolio. By default, the table shows the number of eents for each seerity in each eent group, the total number of eents in each eent group, and the total number of eents for each seerity. To show the percentage of eents in each category, click Percentage on the tool bar. If the percentage of eents in each category is shown and you want to show the number of eents in each category, click Absolute on the tool bar. The window automatically refreshes at specific time interals. To suspend the automatic refresh, click the Suspend icon on the toolbar. To resume the refresh, click the Resume icon. The status bar at the bottom of the window indicates if automatic refresh is enabled, suspended, or needed (automatic refresh has been suspended and the refresh interal has been exceeded). Opening a trouble ticket To open a trouble ticket, follow these steps: 1. Select one or more eents in the eent iewer. 2. Select Trouble Ticket from the Action menu on the toolbar and click Go. When multiple eents are selected, a separate trouble ticket is opened for each selected eent. 62 IBM Tioli Enterprise Console: User s Guide

75 Note: The implementation of trouble tickets depends on how your administrator integrated your trouble ticket system with the trouble ticket rules that the Tioli Enterprise Console proides. Viewing eent information To iew information for an eent, select an eent in the eent iewer and click Information on the tool bar. The information is displayed in a new window of your Web browser. Viewing eent properties Details about eents are called properties. To display eent properties, choose one of these methods: Select the appropriate eent in the eent iewer and click Properties on the tool bar. Click on the seerity in the Seerity column of the eent iewer for the appropriate eent. An eent properties notebook is displayed that contains the following pages: General Displays general information about the selected eent, such as status and date receied. If a rule has automatically responded to the eent (the eent status is RESPONSE), you can iew the rule engine output. To do this, click View Rule Engine Output on this page. The results are shown in a new window of your Web browser. Cause Eents Displays the cause eents of the selected eent when you click Show Cause Eents. The cause eents are listed in a table. To manage one or more cause eents, select the eents and then select Manage Eents from the table menu. An eent iewer is opened for the selected eents. Effect Eents Displays the effect eents of the selected eent when you click Show Effect Eents. To manage one or more effect eents, select the eents and then select Manage Eents from the table menu. An eent iewer is opened for the selected eents. Attributes Displays the attributes of the selected eent. If you want to print the eent properties, click Format a Print Version on any page of the eent properties notebook. The formatted ersion of the eent properties is shown in a new window of your Web browser. Use the print option of your Web browser to print the eent properties. Customizing the eent iewer This section describes the following topics related to customizing the eent iewer: Changing preferences on page 64 Sorting eents on page 65 Filtering eents on page 65 Chapter 4. Managing eents 63

76 Changing preferences The preferences control how eents are shown in the eent iewer. The changes you make, except for changes to the maximum number of eents to show in the each eent iewer, are reflected immediately in all open eent iewers. Because changes to the preferences are stored in cookies, ensure that the priacy settings for your Web browser are set to allow cookies if you want the changes to be persistent. If cookies are not allowed, changes to the preferences affect only the current session. The preferences you set do not affect a Web console on a different computer. To change the preferences, click Change User Preferences in the portfolio. You can change one or more of the following user preferences: Refresh rate Specifies the rate at which you want eents automatically refreshed in the eent iewer and in the summary of eents. Maximum number of eents to show on each page Specifies the maximum number of eents you want to show on each page in the eent iewer. Seerity counts Specifies whether or not to show the number of eents in each seerity on the eent filter icons in the eent iewer. Maximum number of eents to show in each eent iewer Specifies the maximum number of eents you want to show in the eent iewer. The alue for this preference is determined in combination with the preference setting for the maximum number of eents in the Jaa ersion of the eent console. If the alue specified in the Web ersion of the eent console differs from the alue specified in the Jaa ersion of the eent console, the maximum number of eents is set to the lower of the two alues. Changes to the maximum number of eents to show in each eent iewer are reflected the next you time open an eent iewer. Banner Specifies whether or not to show the banner in the eent iewer. Show the eent seerity as Specifies how to show the eent seerity in the eent iewer. The eent console uses color and icons to indicate the seerity leel for an eent. The following table describes the color and icon that corresponds to each eent seerity. Table 9. How eent seerity is indicated in the Web ersion of the eent console Seerity Color Icon Fatal Black Critical Red Minor Orange Warning Yellow 64 IBM Tioli Enterprise Console: User s Guide

77 Table 9. How eent seerity is indicated in the Web ersion of the eent console (continued) Seerity Color Icon Harmless Green Unknown Blue Sorting eents By default, eents are sorted in the eent iewer by the date receied field. You can sort eents based on up to three eent fields. To do this, click the Edit Sort icon on the tool bar in the eent iewer. Filtering eents You can filter eents in the eent iewer by eent seerity, eent status, and eent owner. Filtering eents in this manner helps you focus on the eents of interest. To filter eents, use the eent filter icons on the tool bar in the eent iewer. Chapter 4. Managing eents 65

78 66 IBM Tioli Enterprise Console: User s Guide

79 Chapter 5. Tioli Enterprise Console gateway Configuring the gateway The Tioli Enterprise Console gateway can receie eents from TME adapters and non-tme adapters. The Tioli Enterprise Console gateway forwards eents to the eent serer and communicates with the eent serer using the Tioli Eent Integration Facility. The Tioli Enterprise Console gateway is comprised of the tec_gateway and the tec_gwr programs. The tec_gateway program processes eents from TME adapters. The tec_gateway program and all of the necessary adapter files for each endpoint operating system are installed when the Adapter Configuration Facility is installed on a managed node. The Adapter Configuration Facility must be installed on any managed node that is configured as a Tioli Enterprise Console gateway. For more information about the Adapter Configuration Facility, refer to the IBM Tioli Enterprise Console Adapters Guide. The tec_gwr program receies eents from non-tme adapters and sends them to the tec_gateway program. The tec_gwr program is installed when a Tioli Enterprise Console gateway adapter configuration profile is distributed to an endpoint using the Adapter Configuration Facility. The tec_gwr program is essentially an endpoint adapter that receies eents from non-tme adapters. The tec_gwr program uses the LCF (endpoint) transport type to send eents to the tec_gateway program in a manner similar to that of the SNMP and logfile endpoint adapters. By default, the Tioli Enterprise Console gateway does not receie eents from non-tme adapters. You can configure the Tioli Enterprise Console gateway to receie eents from non-tme adapters using a keyword in the Tioli Enterprise Console gateway configuration file. For information about adapters that send eents to the Tioli Enterprise Console gateway, refer to the IBM Tioli Enterprise Console Adapters Guide. You can use the Tioli Enterprise Console gateway as installed, or you can create a gateway configuration file. You might want to configure the Tioli Enterprise Console gateway for the following reasons: To enable the Tioli Enterprise Console gateway to receie eents from non-tme adapters. See Configuring the gateway to receie eents from non-tme adapters on page 74. To control network traffic and improe eent serer and network performance as follows: Use state correlation at the Tioli Enterprise Console gateway. See Configuring the gateway for state correlation on page 75. Control the rate at which the Tioli Enterprise Console gateway sends eents to the eent serer. See Configuring the rate at which eents are sent to the eent serer on page 76. Note: To control the number of eents sent from an adapter, refer to the eent filtering information in the IBM Tioli Enterprise Console Adapters Guide. To configure the Tioli Enterprise Console gateway, modify the keywords in the gateway configuration file as appropriate. Then create and distribute an adapter Copyright IBM Corp

80 configuration profile that contains the tec_gateway or the tec_gateway_sce profile. Use the tec_gateway_sce profile if you want to use state correlation at the Tioli Enterprise Console gateway. For information about the gateway configuration file, see Gateway configuration file. For more information about using an adapter configuration profile, refer to the IBM Tioli Enterprise Console Adapters Guide. Note: To distribute a modified Tioli Enterprise Console gateway adapter configuration profile to a managed node with a gateway installed, the managed node must also hae an endpoint installed on it. When you distribute the adapter configuration profile, the subscriber must be the endpoint on that managed node. Gateway configuration file The Tioli Enterprise Console gateway configuration file is optional and does not exist on the managed node until an adapter configuration profile containing the gateway configuration information is distributed to the endpoint on that managed node. The Tioli Enterprise Console gateway uses default alues unless you modify the keywords in the Tioli Enterprise Console gateway configuration file and distribute an adapter configuration profile containing the changed gateway configuration information. Also, if you do not specify a alue for a keyword, the default alue is used. The Tioli Enterprise Console gateway uses one of the following configuration files: UNIX: /etc/tioli/tec/tec_gateway.conf Windows: %SystemRoot%\driers\etc\Tioli\tec\tec_gateway.conf The following example shows how the Windows path notation can be expanded: c:\winnt\system32\driers\etc\tioli\tec\tec_gateway.conf The configuration file defines the behaior of the Tioli Enterprise Console gateway. For information about the common keywords for the configuration file, refer to the IBM Tioli Enterprise Console Adapters Guide or the Tioli Eent Integration Facility Reference. The configuration file can also use the following custom keywords: APPEND_CLASSPATH=string Specifies the string that is appended to the CLASSPATH enironment ariable before Jaa-based state correlation is started. The string is appended using the appropriate delimiter, a semicolon (;) for Windows or a colon (:) for UNIX. The string must contain alid data for your enironment as shown in the following example: UNIX: APPEND_CLASSPATH=/my_product/my_jaa.class:/my_product/my_jar.jar Windows: APPEND_CLASSPATH=\my_product\my_jaa.class;d:\my_product\my_jar.jar 68 IBM Tioli Enterprise Console: User s Guide

81 For the tec_gateway program, the specified string is appended to the list of jar files used for state correlation. For a C Adapter, the specified string is appended to the CLASSPATH enironment ariable. BufEtPath Notes: 1. The CLASSPATH enironment ariable will not be changed. The CLASSPATH information is only passed to the Jaa code when state correlation is started. 2. You can specify the APPEND_CLASSPATH keyword only one time in your configuration file. Specifies the file in which to buffer eents when the Tioli Enterprise Console gateway cannot forward the eents to the eent serer. Because a single Tioli Enterprise Console gateway can forward eents to multiple eent serers, it must hae an eent buffer file for each eent serer. When the Tioli Enterprise Console gateway reestablishes the connection to the eent serer, it sends the buffered eents to the eent serer. The Tioli Enterprise Console gateway creates a buffer file for each eent serer by appending the eent serer location specified by the SererLocation keyword to the name of the file specified by the BufEtPath keyword. Assume that the SererLocation and the BufEtPath keywords are specified as follows: SererLocation=@EentSerer#tmr-central BufEtPath=/etc/Tioli/tec/gateway_cache The Tioli Enterprise Console gateway creates the /etc/tioli/ tec/gateway_cache@eentserer#tmr-central buffer file. If the Tioli Enterprise Console gateway receies an eent from an adapter that specified serer location the Tioli Enterprise Console gateway also creates a buffer file named /etc/tioli/tec /gateway_cache@eentserer#tmr-east. The default alue is one of the following: UNIX: /etc/tioli/tec/cache@eentserer#region Windows: $DBDIR/cache.dat@EentSerer#region (on managed nodes) $TIVOLIHOME/tec/$(AC_TYPE).cache@ EentSerer#region (on endpoints) Note: To reduce network traffic and improe performance, filter eents as close to the source as possible by specifying filter options in adapter configuration files. You can also use the Filter, FilterCache, FilterMode, and UseStateCorrelation keywords in the Tioli Enterprise Console gateway configuration file. EentSendThreshold Specifies the maximum number of eents per second to send to the eent serer. Use this keyword in conjunction with the Chapter 5. Tioli Enterprise Console gateway 69

82 BufferFlushRate keyword. For more information about how to set the alue for this keyword, see Gateway configuration example on page 76. GatewayAckInteral Specifies the timeout interal, in seconds, to wait for acknowledgement from the eent serer. The default alue is 30 seconds. This keyword works in conjunction with the GatewayTMEAckEnabled keyword for eent deliery. GatewayQueueSize Specifies the size, in bytes, for the eent buffers. If any of the eent buffers fill before expiration of the interal specified by the GatewaySendInteral keyword, the Tioli Enterprise Console gateway immediately sends the the waiting eents to the eent serer. The minimum alue for this keyword is 4096 bytes. If the GatewayQueueSize keyword is set to a alue lower than 4096, this keyword is set to 40000, which is the default. GatewaySendInteral Specifies the interal, in seconds, at which to forward eents to the eent serers. The Tioli Enterprise Console gateway holds eents when they are receied. When this interal expires, the Tioli Enterprise Console gateway bundles and forwards the eents in a message to the appropriate eent serers. The default interal is fie seconds. GatewayTMEAckEnabled Specifies whether or not an acknowledgement is expected from the eent serer. To ensure eent deliery, set this keyword to YES (connection-oriented). The default alue is NO. gwr_actieconnections=nn Specifies the number of actie connections that the tec_gwr program manages at one time. The number of possible connections ranges from 2 to If the alue specified for this keyword is greater than 1000, the number of actie connections is set to If the alue specified for the keyword is less than 2, the number of actie connections is set to 2. If you do not specify a alue for this keyword, the number of possible actie connections is not limited. gwr_actieconnectionssafety=nn Specifies the percentage of actie connections that the connections specified by gwr_actieconnections keyword must be reduced to before connections can be processed again. Valid alues range from 10 to 90. When the number of actie connections specified in the gwr_actieconnections keyword is reached, no new connections are accepted until the number of connections drops below this specified threshold. For example, if the gwr_actieconnections keyword is set to 20 and the gwr_actieconnectionssafety is set to 80, the tec_gwr program stops accepting connections when 20 connections are reached. The tec_gwr program accepts new connections when the number of actie connections is reduced to 16 or less (80% of 20). The default alue is 80. This keyword is used only when a alue is specified for the gwr_actieconnections keyword. 70 IBM Tioli Enterprise Console: User s Guide

83 gwr_connectionsqueued=nn Specifies the number of connections that the serer socket queues. The serer socket queues connections that are waiting to be accepted by the tec_gwr program. Use this option to limit the number of connections that can be queued. Valid alues range from 1 to The actual number of queued connections can be slightly more or less than the alue you specify. The default alue is 500. This keyword is optional. gwr_enable=yes NO Specifies whether or not the tec_gateway program receies eents from non-tme adapters. To enable the tec_gateway program to receie eents from non-tme adapters, specify YES. The default alue is NO. This keyword is optional. gwr_optionportnotaailable=error WAIT Specifies how the tec_gwr program processes eents when the port specified by the gwr_receptionport keyword is not aailable. When this keyword is set to ERROR, the tec_gwr program ends if the port specified in the gwr_receptionport keyword is not aailable. When this keyword is set to WAIT, the tec_gwr program continues processing instead of returning an error when the port is not aailable. When the port becomes aailable, a serer socket is created. The default alue is ERROR. This keyword is optional. gwr_receptionport=port Specifies the port on which to listen and receie eents from non-tme adapters. The default alue is This keyword is optional. gwr_receptiontestmode=path Specifies the path and the file name from which to read test mode eents. This keyword is similar to the TestMode keyword in that eents are read from a data file as opposed to being receied on a port. This keyword is optional. gwr_retrycount=nn Specifies the number of times to resend an eent when the tec_gateway program fails to receie an eent from the tec_gwr program. The default alue is 10. This keyword is optional. gwr_retryinteral=nn Specifies the interal, in seconds, between retry attempts specified by the gwr_retrycount keyword. The default alue is 1. This keyword is optional. gwr_sererlocation=host_name Specifies the name of the host on which the eent serer is installed. The default alue is the alue of the SererLocation keyword. This keyword is optional. gwr_sererport=port_number Specifies the serer port to use for the host specified by the gwr_sererlocation keyword when eents are receied from non-tme adapers. The specified serer port is used when the alue for gwr_sererlocation is any alue other The default alue is 0. This keyword is optional. gwr_sericeserer=host_name:port_number Specifies the host and port number to which to send serice-related Chapter 5. Tioli Enterprise Console gateway 71

84 eents. The tec_gwr program sends serice status eents that belong to the TEC_Notice class to the eent serer specified by this keyword. The tec_gwr program sends a serice status eent when the tec_gwr program is started or stopped or when the submission handle is reset. Specify the host and port number as follows: myeentsererhost:5529 To send serice status eents from the tec_gwr program to the tec_gateway program, set this keyword to SAME as follows: gwr_sericeserer=same gwr_submissiontestmode=path Specifies the path and file name from which to read test mode eents. This keyword is similar to the TestMode keyword in that eents are read from a data file instead of being receied on a port. This keyword is optional. MaxGWCacheSizeMegs Specifies the maximum size, in megabytes, of the eent cache. By default, the maximum size of the eent cache is 1 MB. The keyword is not included in the configuration file as proided. PREPEND_CLASSPATH=string Specifies the string that is prepended to the CLASSPATH enironment ariable before Jaa-based state correlation is started. The specified string is prepended using the appropriate delimiter, a semicolon (;) for Windows or a colon (:) for UNIX. The string must contain alid data for your enironment as shown in the following example: UNIX: PREPEND_CLASSPATH=/my_product/my_jaa.class:/my_product/my_jar.jar Windows: PREPEND_CLASSPATH=\my_product\my_jaa.class;d:\my_product\my_jar.jar For the tec_gateway program, the specified string is prepended to the list of jar files used for state correlation. For a C Adapter, the specified string is prepended to the CLASSPATH enironment ariable. RetryInteral Notes: 1. The CLASSPATH enironment ariable will not be changed. The CLASSPATH information is only passed to the Jaa code when state correlation is started. 2. You can specify the PREPEND_CLASSPATH keyword only one time in your configuration file. Specifies the interal, in seconds, to wait before connecting to a secondary eent serer when the Tioli Enterprise Console gateway cannot send eents to the eent serer. While the Tioli Enterprise Console gateway is waiting for this time interal to expire, the Tioli Enterprise Console gateway continues to receie and cache new eents. To adjust the size of the Tioli Enterprise Console gateway memory queues, use the GatewayQueueSize keyword. 72 IBM Tioli Enterprise Console: User s Guide

85 The RetryInteral keyword enables adapters to send all eents to the primary eent serer een if the primary eent serer is stopped briefly, such as when loading a new rule base. If you use this option to wait for the eent serer to restart, set the alue for a period of time longer than needed for the eent serer to be stopped and restarted. The RetryInteral keyword is optional. ReceieAckPort=number Specifies the port number that the Tioli Enterprise Console gateway uses to receie acknowledgements from state correlation. The acknowledgements indicate that state correlation has receied and stored the eents. This keyword is used in conjunction with the SendEentPort keyword. This keyword is required when the UseStateCorrelation keyword is set to YES. ReceieEentPort=number Specifies the port number that the Tioli Enterprise Console gateway uses to reciee eents from state correlation. This keyword is used in conjunction with the SendAckPort keyword. This keyword is required when the UseStateCorrelation keyword is set to YES. SendAckPort=number Specifies the port number that the Tioli Enterprise Console gateway uses to acknowledge the reception of eents sent from state correlation. This keyword is required when the UseStateCorrelation keyword is set to YES. SendEentPort=number Specifies the port number that the Tioli Enterprise Console gateway uses to send eents to state correlation. This keyword is required when the UseStateCorrelation keyword is set to YES. SererLocation Specifies the default eent serer location if adapters do not specify an eent serer location in an eent instance. If the SererLocation keyword is specified in the configuration file for an adapter, the Tioli Enterprise Console gateway sends eents to the adapter-specified eent serer. If SererLocation is not specified in an adapter configuration file, the Tioli Enterprise Console gateway sends eents to the eent serer specified by SererLocation keyword in the Tioli Enterprise Console gateway configuration file. If the SererLocation keyword is not specified in the Tioli Enterprise Console gateway configuration file, the Tioli Enterprise Console gateway sends the eent to the eent serer in the local Tioli region. The default alue You can specify multiple eent serer names as a comma-delimited list. Eent serer names later in the list can be backup eent serers when the Tioli Enterprise Console gateway cannot contact its primary eent serer for an eent and the interal specified by the RetryInteral keyword has expired without successfully contacting the primary serer. You can specify a host name as you would for a non-tme adapter, and the eents are then forwarded Chapter 5. Tioli Enterprise Console gateway 73

86 to that host using non-tioli communication. For more information, see the examples in the description of the SererPort keyword. When the Tioli Enterprise Console gateway cannot contact the adapter-specified eent serer, the eent serer names specified in the list are backup eent serers. If SererLocation is not present in the Tioli Enterprise Console gateway configuration file, the Tioli Enterprise Console gateway uses the alue as the backup eent serer. To preent eent deliery to backup eent serers, set the SererLocation keyword to NONE. Note: When the SererLocation keyword is used in conjunction with the TestMode=YES keyword, the SererLocation keyword defines the path and the file name for logging eents instead of the eent serer. SererPort Specifies the port that the eent serer uses to send eents using non-tioli communication. The default alue is 0, which causes the portmapper daemon on the specified host to determine the port on which the eent serer is listening for incoming eents. If you are forwarding eents to a Tioli Aailability Intermediate Manager, you cannot specify 0 as the port because the Tioli Aailability Intermediate Manager does not register itself with the portmapper daemon. If you specify a alue for the SererPort keyword, the alue must be either a single port number or a comma-delimited list of port numbers that correspond to the list of eent serers specified in the SererLocation keyword. If you specify a single port number and you hae specified multiple eent serers in the SererLocation keyword, all eent serers use the port number specified. Assume that you hae a Tioli Aailability Intermediate Manager running on hosts aim.xyz.com and aimbkup.xyz.com, and the SererLocation and the SererPort keywords are specified as follows: SererLocation=aim.xyz.com,aimbkup.xyz.com,@EentSerer SererPort=5530,5531,0 Eents are sent to port 5530 on the host aim.xyz.com using non-tioli communication. If that fails, eents are sent to port 5531 on the host aimbkup.xyz.com. If that also fails, eents are sent directly to the eent serer in the local Tioli region using Tioli communication. The port alue of 0 specified is ignored because port numbers are not needed when using Tioli communication. Configuring the gateway to receie eents from non-tme adapters To configure the tec_gwr program to receie eents receie eents from non-tme adapters, set the alue of the gwr_enable keyword in the gateway configuration file to YES. The tec_gwr program listens on a socket port for incoming eents from non-tme adapters. The port used must not be in use by another application, such as the eent serer. 74 IBM Tioli Enterprise Console: User s Guide

87 If an eent sent from the tec_gwr program to the tec_gateway program fails, the tec_gwr program resends the eent when the gwr_retrycount keyword is set to a alue greater than or equal to 1. The tec_gwr program resends the eent after waiting for the time period specified by the gwr_retryinteral keyword. The number of retry attempts is equal to the alue specified for the gwr_retrycount keyword. To configure non-tme adapters to use the IBM Tioli Enterprise Console gateway, set the SererLocation/channelSererLocation and the SererPort/channelPort keywords in the configuration file of the adapter to the host name and port number that the tec_gwr program uses. If the tec_gwr program is not running on the same host as the eent serer, you can register the tec_gwr program with the portmapper daemon. To do this, set the alue of the gwr_receptionport keyword in the Tioli Enterprise Console gateway configuration file to 0. Note: Messages receied on the socket are generated by non-tme adapters and must be in the correct format as defined by the Tioli Eent Integration Facility in the Tioli Enterprise Console product. Other types of messages are discarded. The Tioli Enterprise Console product uses the following files to receie eents from non-tme adapters: UNIX and Windows: tec_gwr.cfg Installation script. init.tec_gwr Script used to start and shut down the tec_gwr program. Windows only tec_gwr.exe Executable file. tec_gwrs.exe Executable file as a serice. sctlgwr.exe Serice controller and installation utility. UNIX only tec_gwr Executable file. Configuring the gateway for state correlation To decrease the number of eents that are sent to the eent serer, you can configure the Tioli Enterprise Console gateway for state correlation. Using state correlation at the Tioli Enterprise Console gateway to perform adanced filtering, duplication detection, and eent correlation closer to the source off-loads filtering and eent correlation from the eent serer. For information about writing rules for state correlation, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Actiating state machines Before you actiate the state machine, ensure that you hae written your rules based on the information described in the IBM Tioli Enterprise Console Rule Deeloper s Guide. Chapter 5. Tioli Enterprise Console gateway 75

88 Follow this procedure to run a state machine: 1. Modify the state correlation keywords in the configuration file. The following code fragment illustrates the use of the appropriate keywords: UseStateCorrelation=YES # for Windows NT only StateCorrelationConfigURL=file:C:\tmp\test.xml # for all other INTERPs # StateCorrelationConfigURL=file:///tmp/test.xml # SendEentPort=1234 # ReceieAckPort=4321 # ReceieEentPort=5678 # SendAckPort= To run state correlation on an IBM Tioli Enterprise Console gateway, change the adapter configuration profile (ACP) record, tec_gateway_sce, as follows: a. In the Current EIF Enironment list, ensure that the UseStateCorrelation, SendEentPort, ReceieAckPort, ReceieEentPort, and SendAckPort keywords are set. b. Select the XML file to distribute, which you specified in step 1. c. Distribute the tec_gateway_sce ACP. After the state machine is running, you can test whether state correlation is properly filtering eents in the following ways: If you hae written rules to generate eent summaries, ensure that the eent serer is receiing the eent summaries. If you hae written rules to suppress eents, ensure that suppressed eents do not arrie at the eent serer. Configuring the rate at which eents are sent to the eent serer At certain times, the number of eents coming from endpoint adapters can oerwhelm the Tioli Enterprise Console gateway, the eent serer, and een the network. You can control the rate at which the Tioli Enterprise Console gateway sends eents to the eent serer using the EentSendThreshold, the BufferFlushRate, and the MaxGWCacheSizeMegs keywords in the Tioli Enterprise Console gateway configuration file. The example in this section shows how to determine the alues for the BufferFlushRate and EentSendThreshold keywords in the Tioli Enterprise Console gateway configuration file to improe eent serer performance. Gateway configuration example This example assumes that the eent serer processes an aerage of 120 eents per second without degrading its performance. The example enironment contains two Tioli Enterprise Console gateways, where gateway A is responsible for Web commerce serers and gateway B is responsible for the secretaries systems. The alues proided in this example can ary greatly from installation to installation, depending on how many eents, adapters, and Tioli Enterprise Console gateways are in a particular enironment. Use the worksheets proided in Worksheets and calculations on page 77 to collect and calculate the data for your enironment. All numerical alues are expressed in eents per second, except where noted. 1. Determine the aerage number of eents that the eent serer can process (120 in this example). 76 IBM Tioli Enterprise Console: User s Guide

89 2. Determine the number of Tioli Enterprise Console gateways and the resulting number of eents that they can send to the eent serer. Diide the aerage capacity of the eent serer by the number of Tioli Enterprise Console gateways as shown in the following example: 120 2=60 The resulting alue of 60 indicates the aerage number of eents each Tioli Enterprise Console gateway can send without oerwhelming the eent serer. Continue with step 3 to obtain the adjusted alues for the Tioli Enterprise Console gateway send rate. 3. Calculate the alue for the EentSendThreshold keyword. The EentSendThreshold keyword sets the maximum number of eents per second that the Tioli Enterprise Console gateway sends to the eent serer. Because gateway A forwards eents from mission-critical systems, more gateway A eents should be sent to the eent serer than gateway B eents. Thus, the EentSendThreshold keyword for gateway A is set to 80 eents per second. Gateway B has the EentSendThreshold keyword set to 40 eents per second. This way, more gateway A eents get to the eent serer. The sum of the alues for gateway A and gateway B must be less than or equal to the 120 eents that the eent serer can process: Determine the alue for the BufferFlushRate keyword. Any eents aboe the alue specified for the EentSendThreshold keyword are stored in the cache on the Tioli Enterprise Console gateway. To regulate the number of eents being sent to the eent serer, the BufferFlushRate keyword controls the number of eents per minute to be sent from the cache, when the gateway recoers a lost connection to the eent serer. For gateway A, the BufferFlushRate keyword is set to 5400 eents per minute (90 eents per second), and for gateway B the keyword is set to 3000 eents per minute (50 eents per second). Thus at peak traffic times, the eent serer is receiing 140 eents per second from both Tioli Enterprise Console gateways: 90+50=140 Although 140 eents per second is greater than the aerage capacity of the eent serer (120 eents per second), the eent serer has the capability to process excess eents during brief, intermittent periods of time. Tip: Remember to conert eents per second to eents per minute before setting the alue for the BufferFlushRate keyword. 5. Modify the adapter configuration profile for the Tioli Enterprise Console gateway with the alues calculated in step 3 and step Distribute the Tioli Enterprise Console gateway adapter configuration profile. Depending on the number of Tioli Enterprise Console gateways and endpoints in your enironment, you need to carefully consider the rates you specify for the keywords. For instance, an improper configuration might hae multiple Tioli Enterprise Console gateways sending eents at the same rate, thus flooding the eent serer at the same time. See Gateway configuration file on page 68 for details about these keywords. Worksheets and calculations Table 10 on page 78 and Table 11 on page 78 summarize the alues for this example. You can use these tables as worksheets to assemble the alues you measure and calculate for your enironment. All numerical alues are expressed in eents per Chapter 5. Tioli Enterprise Console gateway 77

90 second, except where noted. Table 10. Example rate at which the eent serer processes eents Aerage Receie Rate Expected Peak Rate for High Traffic Table 11. Example rate at which eents are sent to the eent serer Eent Send Rate Adjusted Rate EentSendThreshold BufferFlushRate Gateway A eents per minute (90 eents per second) Gateway B eents per minute Total Eents Sent to Eent Serer (50 eents per second) eents per second The following are the calculations to control eent traffic: eent serer aerage rate gateway A eents + gateway B eents EentSendThreshold = adjusted send rate for gateway gateway A gateway B BufferFlushRate + BufferFlushRate eent serer peak rate Starting and stopping the tec_gwr program By default, the tec_gwr program is automatically started when the host starts. The tec_gwr program is automatically started when an adapter configuration profile containing the tec_gateway or tec_gateway_sce entry is distributed using the Adapter Configuration Facility. You can also manually start the tec_gwr program. Starting the tec_gwr program causes the tec_gwr program to reread the tec_gateway.conf configuration file and restart the daemons. The tec_gwr program is automatically stopped when you distribute an adapter configuration profile that has the init.tec_gwr start command remoed from the after-file-distribution actions. You can also manually stop the tec_gwr program. Starting the tec_gwr program manually To start the tec_gwr program manually, use one of the following commands: UNIX: init.tec_gwr start & Windows: net start TECGWR Stopping the tec_gwr program manually To manually stop the tec_gwr program, use one of the following commands: UNIX: init.tec_gwr stop 78 IBM Tioli Enterprise Console: User s Guide

91 Windows: net stop TECGWR Obtaining the status of the tec_gwr program on UNIX To obtain the status of the tec_gwr program on a UNIX system, use the init.tec_gwr command as follows: To obtain status, type the following command: init.tec_gwr status & To obtain the process ID, type the following command: init.tec_gwr pid & To obtain enironment settings, type the following command: init.tec_gwr en & Chapter 5. Tioli Enterprise Console gateway 79

92 80 IBM Tioli Enterprise Console: User s Guide

93 Appendix A. Troubleshooting This appendix contains suggestions for isolating problems that you might encounter when using the Tioli Enterprise Console product. To use the troubleshooting information in this appendix, you must hae administration experience with the the Tioli Enterprise Console product and you must be able to read Tioli Management Framework log and trace files. The troubleshooting information in this appendix also requires that you hae knowledge about the following items: SQL Three-tier architecture (database management, process management, and user system interface) Installed Tioli applications Tioli Management Framework Getting started with problem determination Problems locating an eent To begin isolating where you might hae a problem with the Tioli Enterprise Console product, ask yourself the following questions: Where is the eent? What is the most likely candidate for the problem in my specific enironment? Eent serer Rules Performance This section describes the arious commands and tools that you can use to determine where processing stopped for an eent and where an eent is currently located. The following commands can be useful: wtdumprl Generates a report of eents that the eent serer receies by producing the contents of the reception log. The following example is a sample of an output fragment from running the wtdumprl command. $ wtdumprl -o DESC more 1~10782~65537~ (Jun 20 15:20: ) ### EVENT ### BadClass;source=EVENT;msg= Test Parsing ;origin= ;end ### END EVENT ### PARSING_FAILED~ Line 1: Class BadClass undefined 1~10781~65537~ (Jun 20 15:20: ) ### EVENT ### BadClass;source=EVENT;msg= Test Parsing ;origin= ;end ### END EVENT ### PARSING_FAILED~ Line 1: Class BadClass undefined 1~10780~2~ (Jun 20 15:15: ) ### EVENT ### TEC_Notice;source=LOGFILE;seerity=HARMLESS;msg= HARMLESS postemsg test ;origin= ;end Copyright IBM Corp

94 ### END EVENT ### PROCESSED Note the PARSING_FAILED line in the wtdumprl output. For detailed information about how PARSING_FAILED affects performance, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. wtdumper Generates a report of eents in the eent repository. The eent repository is a table of receied eents in the eent database. The following example is a sample output fragment from running the wtdumper command. $ wtdumper -o DESC more ES~1~ (Jun 20 15:20: )~6~TEC_Notice~ LOGFILE~~ ~~~~OPEN~ ~[ admin]~critical~ Jun 20 15:20: ~ CRITICAL postemsg test~ ~0~ 0~0~ES~1~ (Jun 20 15:20: )~1~Su_Success~ TEC~LOGFILE~ ~N/A~~N/A~OPEN~ ~[ admin]~warning~ Jun 20 15:20: ~ WARNING wpostemsg test~ none~0~ wtdbclear Deletes eents from the eent database. Use the wtdbclear command to delete eents from the eent database on a regular basis. Doing so helps to maintain good performance of the Tioli Enterprise Console product. Use caution when running the wtdbclear command from a managed node other than the eent serer. The time from the local machine from which the command has been run is used to determine which eents to clear, not the time from the eent serer. Note: For optimal performance, run the wtdbclear command during non-peak processing hours. For more information about the wtdumprl, the wtdumper, and the wtdbclear commands, refer to the IBM Tioli Enterprise Console Command and Task Reference. Understanding eent serer processes To effectiely use reports generated by the wtdumprl and the wtdumper commands, you need to understand how an eent is processed before the eent is displayed on an eent console. The eent serer architecture consists of fie processes, each of which impacts deeloping and running rules. An additional process, the UI serer process, plays an integral part in the oerall Tioli Enterprise Console architecture. The UI serer is not a part of the eent serer, although it communicates with the eent serer. The eent serer runs as fie main processes, as shown in the following table: Table 12. Eent serer processes Process Name Description tec_serer The master process tec_reception The reception engine process 82 IBM Tioli Enterprise Console: User s Guide

95 Table 12. Eent serer processes (continued) Process Name Description tec_rule The rule engine process tec_dispatch The dispatch engine process tec_task The task engine process If any of the eent processes fail, messages are written to files defined in the $BINDIR/TME/TEC/.tec_diag_config file. For more information about this file and the log files, see Eent serer process log files on page 85. The following figure illustrates the relationships among the eent serer processes. The arrows represent the flow of communications. Incoming Tioli eents from non-tioli communication Incoming Tioli eents from Tioli communication Master (tec_serer) Task engine (tec_task) External tasks or programs Reception engine (tec_reception) Rule engine (tec_rule) Dispatch engine (tec_dispatch) UI serer (tec_ui_serer) Console Reception buffer (RAM) Eent cache (RAM) Console Console RDBMS Figure 5. Relationship among eent serer processes The following sections describe the flow of an eent through each of the Tioli Enterprise Console s fie processes. Master process The controlling (master) process, tec_serer, initializes the tec_dispatch, the tec_reception, the tec_rule, and the tec_task processes and restarts them if they stop. The tec_serer process manages eents as follows: 1. The tec_serer process receies incoming eents from Tioli communication. 2. The tec_serer process forwards receied eents to the tec_reception process. If errors are encountered during the tec_serer process, the error messages are written to the /tmp/tec_master file by default. Reception engine process When an eent is receied, the eent is immediately placed in the reception buffer by the reception engine process, tec_reception. Appendix A. Troubleshooting 83

96 84 IBM Tioli Enterprise Console: User s Guide The following list explains what happens to an eent during the tec_reception process: 1. An eent is receied by the tec_reception process. 2. The eent is stored in the reception buffer with a status of QUEUED. 3. If the reception buffer is full, the eent is stored in an eent database table named tec_t_et_rec_log with a status of WAITING. 4. When space is aailable in the reception buffer, the eents in the database in WAITING status are read into the reception buffer and marked as QUEUED. If errors are encountered by the tec_reception process, the error messages are written to the /tmp/tec_reception file by default. Rule engine process Eents with a status of QUEUED are now aailable for rule processing. The rule engine process, tec_rule, manages eents as follows: 1. Eents are passed from the tec_reception process to the tec_dispatch process and then to the tec_rule process. 2. A copy of the eent is stored in the eent cache where eent correlation (rule processing) can occur. If errors are encountered during rule processing, the error messages are written to the /tmp/tec_rule file by default. Dispatch engine process The dispatch engine process, tec_dispatch, uses the tec_serer process to notify the tec_reception process that an eent has completed processing. The tec_dispatch process manages eents as follows: 1. The tec_dispatch process places a copy of the eent (including changes made during rule processing) in the eent repository using RDBMS Interface Module (RIM). The eent repository table name is tec_t_et_rep. 2. The tec_dispatch process sends a message to the tec_task process to run assigned tasks or programs associated with the eent. 3. The eent is now aailable to the appropriate eent consoles for iewing. 4. After the eent is stored in the eent repository, an acknowledgement is sent to the tec_reception process, which updates the status to PROCESSED. If the eent is labeled as PROCESSED in the reception log, the rules hae processed the eent. If errors are encountered during the tec_dispatch process, the error messages are written to the /tmp/tec_dispatch file by default. UI serer process The UI serer process proides communication serices between eent consoles and the eent serer, and between eent consoles and the eent database. It communicates with the dispatch engine when it needs contact with the eent serer. The UI serer proides the eent consoles with updated eent information and proides the dispatch engine with change requests to eents from eent consoles. For more information about the UI serer process, see the IBM Tioli Enterprise Console Rule Deeloper s Guide.

97 Task engine process The task engine process, tec_task, is responsible for managing actions as directed by the tec_rule process and manages running the rule language predicates. The process runs programs, tasks, scripts, and commands initiated by the rules. The exit status of the monitored items is returned to the dispatch engine, which writes the status to the eent database if watch status is set to YES in the exec_prog or exec_task predicates. The num_actions attribute for an eent contains the number of actions (tasks or programs) currently being tracked by the eent serer for the eent. The tec_task process passes the eent through the following assigned actiity sources (rule language predicates): exec_task Assigned tasks are run on the eent. exec_program Assigned scripts or programs are run on the eent. forward_eent The eent is forwarded to another eent serer with changes applied from running the assigned task and program. If errors are encountered during the tec_task process, the error messages are written to the /tmp/tec_task file by default. For additional information about eent serer architecture and details about the eent serer processes, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Eent serer process log files Error information is written to specific log files when eent serer processes fail. The log files are defined in the $BINDIR/TME/TEC/.tec_diag_config file. The following table lists each eent serer process and its corresponding default log file name and location: Table 13. Log files for eent serer processes Process Name Log File tec_serer /tmp/tec_master tec_reception /tmp/tec_reception tec_rule /tmp/tec_rule tec_dispatch /tmp/tec_dispatch tec_task /tmp/tec_task Note: In a Windows or UNIX enironment, the /tmp directory must already exist on your system for the log files to be properly created and saed. UNIX systems usually hae a /tmp directory by default, but Windows temporary directories are named /temp. Rename /temp to /tmp, or add a directory named /tmp. For information about.tec_diag_config file parameters, refer to the IBM Tioli Enterprise Console Command and Task Reference. Appendix A. Troubleshooting 85

98 Checking the eent flow To check the eent flow and determine why an eent is not displayed on the eent console: Examine the adapter and the Tioli Enterprise Console gateway cache files. If the eent serer is down, the Tioli Enterprise Console gateway buffers eents at the gateway. Locate and inspect the cache files to find eents that stop at the Tioli Enterprise Console gateway. The file location is specified in the adapter configuration file. If eents are found in the cache files, these eents hae not been forwarded to the eent serer. Ensure that the endpoint, the Tioli Enterprise Console gateway, the Tioli Management Framework gateway, and the eent serer are running. Ensure that you do not filter out this eent class at the adapter with the PreFilter and Filter adapter configuration options. Use the wtdumprl command to check the reception log and determine if the eent serer receied the eent. For more information about using the wtdumprl command, see Problems locating an eent on page 81. Use the wtdumper command to check the eent repository. If the eent is in the eent repository, it should be displayed on the eent console. If the eent is not displayed on the eent console and the eent is in the wtdumper command output, first check the time limits that were set during configuration for displaying eents. Ensure that the time limits fit the criteria for the eent in question. Time limits for displaying eents can be modified in the following areas: Eent serer parameters Eent group filters Eent iewer filtering Rule processing For more information about using the wtdumper command, see Problems locating an eent on page 81. Use the rule tracing facility to ensure that eents are being processed through the rule engine. If the eent is shown in the wtdumprl command output but not in the wtdumper command output, you might hae a rule that is causing the eent to be dropped. Checking the eent flow in a Tioli enironment To check the eent flow in a Tioli enironment, use the wpostemsg command. The wpostemsg command sends an eent to the eent serer. Sending eents is a good way to test the eent serer after you hae created new eent groups, created eent group assignments, edited rules, or otherwise changed the behaior of eent processing at the eent serer leel. The following example sends a test message with the source of LOGFILE to the eent serer: wpostemsg -m test message from EP TEC_Notice LOGFILE For additional troubleshooting using the wpostemsg command, use the wtrace command, as described in Analyzing Tioli Management Framework trace logs on page 90. For defining specific results using the wtrace command, use the odstat command to filter for specific details. 86 IBM Tioli Enterprise Console: User s Guide

99 Notes: 1. The wpostemsg command is a form of the Eent Integration Facility implementation that uses caching ability. 2. If the connect_agent method call returns an e=12 return code, the wpostemsg command caches the eent. The e=12 return code indicates that the eent serer is not aailable. For more information about using the wpostemsg command, see the IBM Tioli Enterprise Console Command and Task Reference. Checking the eent flow in a non-tioli enironment To check the eent flow in a non-tioli enironment, use the postemsg command. The postemsg command sends an eent to the eent serer. Sending eents is a good way to test the serer after you hae created new eent groups, created eent group assignments, edited rules, or otherwise changed the behaior of eent processing at the serer leel. The following example sends a test message that displays an Su_Failure eent on the eent console. postemsg -S tecbox -r WARNING -m su login failure. Su_Failure LOGFILE Using the f option with the postemsg command specifies the name of the adapter configuration file. The adapter configuration file must specify the SererLocation keyword and, if necessary, the SererPort keyword. You can use any of the keywords in the adapter configuration file specified by the f option with the postemsg command. Using the f option with the postemsg command is preferred oer the S option because it offers more flexibility and because you can specify a standard configuration file. Note: Output from the postemsg command is not included in Tioli Management Framework trace file output. For more information about the postemsg command, refer to the IBM Tioli Enterprise Console Command and Task Reference. Problems starting the Tioli Enterprise Console product When you cannot start the Tioli Enterprise Console product from the Tioli desktop or the command line, look first at the following items: Tioli Management Framework or Tioli Enterprise Console enironment problems: If the tec_serer eent serer process is no longer responding, restart it using the wstartesr command. To check the status of the eent serer, use the wstatesr command. When the eent serer is restarted, eent consoles that were connected to it are automatically reconnected. For details about using the wstartesr or wstatesr commands, refer to the IBM Tioli Enterprise Console Command and Task Reference. Ensure that all interconnected Tioli regions are running. If your enironment contains seeral Tioli regions that are connected, administration can be complex if you do not hae a good diagram of the connections between the Tioli regions. Before you begin troubleshooting, create a diagram of the connections between the Tioli regions to assist you in determining the location of your Tioli regions and the connection types. Appendix A. Troubleshooting 87

100 The following list describes the common problem types you can encounter with interconnected Tioli regions: - Inter-region passwords - Secure and remote connections - One-way and two-way connections - Inability to connect to a preiously connected Tioli region - Unable to disconnect a Tioli region - Updating the name registry - Updating resources - Remote resources are not isible or accessible - Inability to perform actions on remote objects - Application failures across Tioli region boundaries For information about troubleshooting each of these potential problems with interconnected Tioli regions, refer to the Tioli Management Framework Maintenance and Troubleshooting Guide. For troubleshooting possible database and RIM problems, see Problems with the RIM database on page 89. If you suspect problems with the rule base, load and run the default rule base or a known working rule base as a test. If this confirms a problem with the rule base, see Problems with rules on page 88 and the IBM Tioli Enterprise Console Rule Deeloper s Guide for additional troubleshooting information. Problems with rules The most common problems related to rules are: Failure to recompile, reload, and actiate the rule base. Failure to restart all Tioli Enterprise Console processes after making changes to the rule base. For information about the Tioli Enterprise Console processes, see Understanding eent serer processes on page 82. Introduction of hidden characters or the Windows end-of-line (^M) character in a rule set causing unpredictable results, such as the product failing to start or the eent console not being updated. For more information about writing rules, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Enabling rule tracing The Tioli Enterprise Console product proides a rule tracing facility for debugging problems related to rules. You can use the rule tracing facility to trace rules at different leels of granularity. For example, you can trace all rules, a particular rule set, part of a rule set, or a particular rule. To enable rule tracing, follow these steps: 1. Compile the rule base with tracing enabled. To do this, use the wrb comprules trace command with a trace directie specified in a rule or rule set. You can also trace rules from the rule builder. To do this, select Trace Rules in the Compile Rule Base dialog box. 2. Turn on tracing using the wsetesrcfg command with the t option. 3. Load and actiate the compiled rule base. 88 IBM Tioli Enterprise Console: User s Guide

101 Note: When a rule base is compiled for the production enironment, disable rules tracing because rule tracing impacts eent processing performance. Rules generate trace output in a file. You can examine the resulting trace file to analyze and debug problems related to rules. The name and location of the trace file is set when the eent serer is configured. The following table describes the information found in rule trace files. Table 14. Output in rule trace files Output Type action condition prolog calls rule predicate Description The action set when the rule trace is entered and exited The condition set when the rule trace is entered and exited The prolog calls trace, limited to a leel of one depth The trace rule whose header matches the current eent The predicate used when entering, exiting, or failing a predicate action For more information and specific instructions for determining the leel of granularity for your trace results, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Tuning rules The following list describes suggested techniques for tuning rules. Write rules to drop unneeded eents immediately (as one of the first rules encountered so that eents do not hae to process through all rules in the rule base). Use the commit_action, commit_rule, and commit_set rule language predicates frequently. Monitor the number of rule timers used. When writing rules, limit the use of the following predicates: all_instances all_duplicates generate_eent predicates For detailed information about tuning rules, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Problems with the RIM database The following commands are useful tools for troubleshooting problems with the RIM database. For additional information about the RIM commands, refer to the Tioli Management Framework Reference Manual. wrimtest Verifies the connectiity and functionality of a RIM object as follows: wrimtest l tec Use the wrimtest command to connect to a specified database and run RIM methods. Appendix A. Troubleshooting 89

102 wlookup RIM Displays a list of aailable RIM objects as follows: wlookup ar RIM wrimtrace Enables or disables tracing for RIM objects. The contents of the Inter-Object Message (IOM) packets are passed between the RIM object and client program. RDBMS errors are then printed to the RIM log file. Note: The RIM tracing function is intended for debugging purposes. If enabled for extended periods of time, tracing can decrease performance and considerably slow the processing of RIM calls. For additional information about RIM Troubleshooting, refer to the Tioli Management Framework User s Guide and the Tioli Management Framework Maintenance and Troubleshooting Guide. Additional information about troubleshooting RIM problems and RIM tuning can be found in the Using Databases with Tioli Applications and RIM redbook. Analyzing Tioli Management Framework trace logs The Tioli Management Framework product supports an object tracing mode that records in a log file either all operations or only those operations that fail. Use the wtrace log file to diagnose problems. The wtrace command extracts information used to debug methods and diagnose problems in custom methods and executable files. The wtrace command examines the method input, transactions, and method output. The wtrace log file proides detailed information and should be used in conjunction with an odstat command listing option. The odstat command lists the status of current and recent object calls. The odstat serice status command displays the currently running operations and the preious 200 operations for a specific managed node. You can find an error in the odstat command listing and use the thread ID associated with it to find additional information in a wtrace log file. Using the odstat command results in more explicit way to iew the output data from the wtrace command. For more information about Tioli Management Framework trace logs, refer to the Tioli Management Framework Maintenance and Troubleshooting Guide. For information about using the wtrace and the odstat commands, refer to the Tioli Management Framework Reference Manual. Problems with the Tioli Enterprise Console gateway This section describes how to troubleshoot problems with the tec_gateway and the tec_gwr programs of the Tioli Enterprise Console gateway. Problems with the tec_gateway program To troubleshoot problems with the tec_gateway program, you can configure tracing for the tec_gateway process. Tracing for the tec_gateway process is controlled by one of the following files: UNIX: 90 IBM Tioli Enterprise Console: User s Guide

103 /etc/tioli/tec/.tec_gateway_diag_config Windows: %SystemRoot%\system32\driers\etc\Tioli\.tec_gateway_diag_config To configure tracing for the tec_gateway process, follow these steps: 1. Edit the.tec_gateway_diag_config file to specify the leel of tracing that you want. The sample.tec_gateway_diag_config file is located on the eent serer in the $BINDIR/../generic_unix/TME/ACF_REP directory. By default, the.tec_gateway_diag_config file looks similar to the following: Highest_leel error Truncate_on_restart true # tec_gateway ############# tec_gateway Highest_leel error tec_gateway GW_Send error /tmp/tec_gateway tec_gateway State_Correlator error /tmp/tec_gateway Both Highest_leel keywords set the highest trace leel possible within the following sections in the file. The tracing leels from least erbose to most erbose are: error warning trace0 trace1 trace2 The Truncate_on_restart keyword specifies whether or not trace files are truncated to zero bytes when the tec_gateway process starts up. 2. Distribute a gateway configuration profile with the Adapter Configuration Facility. Note: If you hae upgraded from a preious release of the Tioli Enterprise Console product, the Distribution tab for existing gateway configuration profiles is not updated with the.tec_gateway_diag_config file. If you want to enable tracing, you must delete the existing gateway configuration profile and distribute a new gateway configuration profile. Set tracing on to determine the cause of a problem. Otherwise, disable tracing or set tracing at the error leel. If you are distributing a gateway configuration profile and you want to disable tracing, delete the.tec_gateway_diag_config file from the gateway configuration profile. If you hae already distributed the.tec_gateway_diag_config file and you want to disable tracing, delete the.tec_gateway_diag_config file manually from the Tioli Enterprise Console gateway. Problems with the tec_gwr program To troubleshoot problems with the tec_gwr program, follow these steps: 1. Stop all tec_gwr processes currently running on the machine. 2. Type the following command to cold start the tec_gwr program: tec_gwr [-d] [-c configuration_file] Where: Appendix A. Troubleshooting 91

104 d Starts the tec_gwr program in debug mode. c configuration_file Specifies the location of the Tioli Enterprise Console gateway configuration file. If you do not specify this parameter, the tec_gwr program searches one of the following directories to locate the tec_gateway.conf configuration file. UNIX: /etc/tioli/tec/tec Windows: \WINNT\system32\driers\etc\Tioli\tec 3. Ensure that no other processes are listening on the reception port. To determine if the reception port is in use, type the following command: netstat a grep port_number Where port_number is the port that the tec_gwr program uses to receie eents. The first process to start on a port uses the port, and subsequent processes cannot receie eents from that same port. 4. Use the postzmsg or the postemsg command to send eents to the tec_gwr program for testing. Problems with the Web ersion of the eent console If you experience problems with the Web ersion of the eent console, you can create trace files that IBM Customer Support can use to determine the cause of the problem. To create the trace files, use the following general procedure from the WebSphere Application Serer Administratie Console. The following procedure describes the information that is releant to the Tioli Enterprise Console product. For specific information about the IBM WebSphere Application Serer product, refer to the online help in the WebSphere Application Serer Administratie console and the IBM WebSphere Application Serer product documentation, which you can access from the WebSphere InfoCenter at the following Web site: 1. From the WebSphere Application Serer Administratie console, naigate to Troubleshooting > Logs and Trace. 2. Select your serer. The default name is serer1. 3. Select Diagnostic Trace. 4. Do one of the following: Select the Configuration tab to change the trace settings that are stored in the WebSphere Application Serer configuration files. Select the Runtime tab to change the trace settings of the currently running WebSphere Application Serer. The Runtime tab contains the Sae Trace option, which saes your settings in the WebSphere Application Serer configuration files so that the changes remain in effect the next time the WebSphere Application Serer is started. 5. In the Trace Specification field, click Modify. The Trace Serice page is opened in a new window. 6. Select the Components tab on the Trace Serice page. 7. On the Trace Serice page, expand the com.tioli.tec and the com.tioli.tec.wc components. The following trace files are useful to IBM Customer Support: 92 IBM Tioli Enterprise Console: User s Guide

105 com.tioli.paa.jdbc.util.abstractjdbc com.tioli.tec.rimds.rimjdbcpro com.tioli.tec.wc.tectrace com.tioli.tec.wc.jca.tecresadap Problems with performance Note: The com.tioli.tec.wc.tectrace file produces a large amount of data. 8. Select a trace file group or an indiidual trace file name to specify the leel of tracing you want. 9. Optionally, change the maximum trace file size and the number of old trace files to maintain in the Trace Output field on the Runtime tab. 10. Click Sae on the taskbar. No two work enironments are the same and there are typically many things an administrator can do to tune the enironment for optimal performance. As a starting point, the following items should be considered when tuning your enironment: Attempt to tune first at the source. Tuning the sources that send eents, such as filtering at the adapter leel, can reduce unnecessary network traffic. For information about filtering at the adapter leel, refer to the IBM Tioli Enterprise Console Adapters Guide. Ensure that the Tioli region and the Tioli Enterprise Console product reside on separate machines, free of other major processes. Ensure that the Tioli Enterprise Console database resides on a separate machine. Do not run eent consoles on the Tioli serer or the UI serer. Aoid shutting down the database while the Tioli Enterprise Console product is running. Tuning RDBMS The RDBMS serer can be tuned for locking and recoery considerations that can impact the performance of the Tioli Enterprise Console product. For more information about database configuration and tuning the RDBMS serer, see the IBM Tioli Enterprise Console Installation Guide. To check RDBMS error logs, see Problems with the RIM database on page 89. Use filters and rules to iew only required eents. For optimal performance, aoid the following practices: Attempting to monitor eerything possible in an enironment Attempting to dump eerything possible to a central log file Inefficient rules Improper eent handling Configuring the eent database The Tioli Enterprise Console product offers automated database endor configuration options to customize your eent database application for optimal performance. Appendix A. Troubleshooting 93

106 The following tables are the largest, most frequently accessed Tioli Enterprise Console tables: TEC_T_EVT_REP TEC_T_EVT_TEC_LOG TEC_T_SLOTS_EVT These tables frequently read, insert, delete, and update information and therefore require indexes so that rows can be quickly returned to the application. For example, if each of the tables and their indexes are split across six different input/output (I/O) deices, they will not encounter I/O contention from the read/write (R/W) head on the deice. Database transaction logs operate more efficiently when placed on their own I/O deice. Use higher performance deices for index tables, temporary work areas, and transaction logs to proide optimal results when updating and retrieing data. If you cannot attain these specifications, you can achiee optional performance improements by combining arious tables and indexes across aailable I/O deices so that tables accessed less frequently are mixed with frequently-accessed table and data table operations are split from index table operations. After the TEC_T_EVT_REP, the TEC_T_EVT_TEC_LOG, and the TEC_T_SLOTS_EVT tables, the TEC_T_TASK_REP table is the next most frequently accessed table in the eent serer. This table contains an index for performance, as do most Tioli Enterprise Console tables. A row cannot be inserted into the TEC_T_EVT_REP or the TEC_T_SLOTS_EVT tables unless the row has a parent row in the TEC_T_EVT_REP table. Referential integrity is therefore established on these tables so that a row deleted from the TEC_T_EVT_REP table causes rows in the two tables with the same serer handle, eent handle, and date reception, to be deleted. Referential integrity enhances data integrity by speeding up the deletion process. The eent console tables are small and usually contain a LONG or a text column. These columns store a descriptor in the table pointing to the actual location of the data. The eent console tables are only updated during the eent console configuration processes, such as creating consoles, assigning operators and eent groups, creating filters, or assigning console preferences. In cases where there are large numbers of consoles, operators, eent groups, and filters, these tables contain indexes that enhance performance. The TEC_T_CONSOLES, the TEC_T_EVENT_GROUPS, and the TEC_T_OPERATORS tables are the base tables for storing eent console information. The TEC_T_ASSIGN_OP, the TEC_T_ASSIGN _EG, and the TEC_T_EG_WHRCLAUS tables proide data needed for correlation to determine which operators and eent groups are assigned to which eent consoles and which eent filters are assigned to which eent groups. A row in these tables can only exist if a corresponding row also exists in the parent table. Referential integrity ensures that a row deletion from a parent table deletes the corresponding row in the child table. These tables can be installed on the same I/O deice because these tables hae less frequent I/O requests. The TEC_T_ISA and the TEC_T_ENUMERATIONS tables are cleared and reloaded when the Tioli Enterprise Console product starts but are subsequently read on an infrequent basis. The TEC_T_ARCHIVE table is installed in the eent database when the TDS Tioli Enterprise Console Eent Management Guide is installed and is only updated when eents are closed. Therefore, the table has less frequent I/O requests. These tables are all good candidates to install on the same I/O deice as with the other more actie tables for a mix of workload types. 94 IBM Tioli Enterprise Console: User s Guide

107 For more information about automated eent database configuration using the eent database installation assistant, refer to the IBM Tioli Enterprise Console Installation Guide. Additional information sources This section lists information sources that discuss troubleshooting and experience with the administration of the Tioli Enterprise Console product. The Web sites listed in this section were current at the time of this publication. Tioli Field Guides for Technical Issues Tioli Field Guides for technical issues are white papers and scripts written by Tioli software deelopers and customers. The papers address complex technical scenarios or concepts, such as the following: Endpoint Mobility Migration Heartbeat Monitoring in Large Enironments Using Precompiled Fact Files Within the Rule Base Getting the Most out of Traces Endpoint Policy Issues Tioli Field Guides for Technical Issues are located at the following Web site: Tioli Field Guides for Business Issues Tioli Field Guides for Business Issues are white papers written by Tioli software deelopers and customers that are designed to address specific business practices and hae a high impact on the success or failure of an Enterprise System Management (ESM) project. The business papers include the following topics: Change Management Asset Management Project Management Deeloping Requirements Building a Case for a Test Enironment Going for the Quick Win Understanding the Phases of Deelopment Tioli Field Guides for Business Issues are located at the following Web site: Tioli Customer Support Knowledge Base (Ask Tioli) Tioli software customers can access a Web-based support tool called Ask Tioli to search the support knowledge base for resolution of issues with Tioli products. You can search multiple databases simultaneously for information from redbooks, white papers, Release Notes, and Tioli Serice Desk (TSD) for Customer Relationship Management (CRM) solutions. The solutions accessed from the Tioli Customer Support Knowledge Base are deeloped by the Tioli product support staff and hae been reiewed to assure alidity and accuracy. Appendix A. Troubleshooting 95

108 Solutions proided through the Ask Tioli tool are located at the following Web site: Ask Tioli Frequently Asked Questions (FAQ) Tips and instructions for using the Ask Tioli tool on the Tioli Customer Support Knowledge Base are located at the following Web site: TME10 Mailing List The TME10 mailing list is an list, which is read and posted to by oer subscribers around the world. Members subscribing to TME10 listser are those who create, maintain, support, and use Tioli software. Members share experiences and ask questions. Access to the TME10 mailing list is controlled. You can subscribe to the TME10 mailing list at the following Web site:. Rule Writing Deeloping Tioli Enterprise Console rules requires considerable skill and knowledge. Proper rule writing and sharing rule writing experience with others can help increase the power and performance of the Tioli Enterprise Console product. You can find articles on rule writing topics, such as rule writing and tuning, multiple inheritance in BAROC, and how to use assertion lists with rules at the following Web site: The communication on the referenced Web sites is primarily customer experience and dialog and is not intended to replace IBM Customer Support. For information about contacting IBM Customer Support, see Contacting software support on page ii. 96 IBM Tioli Enterprise Console: User s Guide

109 Appendix B. Messages This appendix describes messages related to using the Web ersion of the eent console. ECOWEP001E An error occurred when retrieing eent details from the eent serer database. Retry the operation or close the Eent Properties window. Explanation: The connection to the eent serer database or the eent serer database itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWEP002E The cause eents cannot be retrieed from the eent serer database. Retry the operation or close the Eent Properties window. Explanation: The connection to the eent serer database or the eent serer database itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWEP003E The effect eents cannot be retrieed from the eent serer database. Retry the operation or close the Eent Properties window. Explanation: The connection to the eent serer database or the eent serer database itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWEV001E The eents cannot be retrieed from the eent serer database. Refresh the eent iewer. Explanation: The eent serer retriees eents from a database when an eent iewer is displayed for the first time or when the list of eents shown in an existing eent iewer is refreshed. If the eents cannot be retrieed, the eent group definition might not be correct or the connectiity to the eent serer database might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWEV002E The status of the eent cannot be updated. Refresh the eent iewer. Explanation: The eent serer updates the status of an eent on a database when an action is submitted from an eent iewer. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWEV003I A trouble ticket has been opened for the selected eents. Explanation: No additional information is aailable for this message. ECOWEV004E A trouble ticket cannot be opened for the selected eents. Explanation: Possible causes for this problem include the following: You might not hae the appropriate authorization role to open a trouble ticket. Either admin or user role is required. A problem exists with the trouble ticket integration software. Copyright IBM Corp

110 ECOWEV005E ECOWPV003I Operator Response: Contact the administrator of the eent serer. ECOWEV005E The trouble ticket integration program for the selected eents did not complete. Explanation: The trouble ticket integration program, which is supplied by the IBM Tioli Enterprise Console, integrates your problem reporting software with the IBM Tioli Enterprise Console. Operator Response: eent serer. Contact the administrator of the ECOWEV006W Do you want to exit this eent iewer? Explanation: This message confirms whether or not you want to exit the eent iewer. Operator Response: If you want to exit the eent iewer, click Exit. If you do not want to exit the eent iewer, click Cancel. ECOWEV009W You hae selected actual_sels eents. Running the requested action against this many eents results in a heay processing load on the eent serer. Do you want to continue? Explanation: See message. This message confirms whether or not you want to continue with the action. Operator Response: If you want to continue with the action, click Continue. If you do not want to continue with the action, click Cancel. ECOWGE001E An internal error has occurred. Explanation: Your request could not be completed due to an internal error. Operator Response: Contact your administrator. Administrator Response: To determine the cause of the problem, look in the IBM Web Application Serer log files. ECOWEV007E The details for the selected eent cannot be retrieed from the eent serer. The action associated with the customized button cannot run. Explanation: When you click a customized button, the full set of eent details for the selected eent is retrieed from the eent serer. If the communication with the eent serer fails, the action associated with the customized button cannot run. Operator Response: eent serer. Contact the administrator of the ECOWEV008W You hae selected actual_sels eents. Running the requested action against this many eents results in actual_sels popup windows. Do you want to continue? Explanation: More than one eent was selected when you performed an action from the eent iewer. Proceeding with this action will result in a popup window for each of the selected eents. This message confirms whether or not you want to continue with the action. Operator Response: If you want to continue with the action, click Continue. If you do not want to continue with the action, click Cancel. ECOWPV001I The user preferences were saed. Explanation: No additional information is aailable for this message. ECOWPV002W Do you want to continue making changes or cancel without saing? Explanation: This message confirms whether or not you want to exit the user preferences without saing the changes. Operator Response: If you want to continue making changes to the user preferences, click Continue. Ifyou want to cancel the changes to the user preferences, click Cancel. ECOWPV003I The user preferences cannot be saed because cookies are not enabled for your browser. Explanation: The user preferences are saed on your computer as a cookie, but the cookie option on your browser is disabled. Operator Response: To sae the user preferences, change the priacy settings for your browser to accept cookies. If you do not enable the cookie option, the user preferences affect only the current session. 98 IBM Tioli Enterprise Console: User s Guide

111 ECOWPV004I ECOWRA007W ECOWPV004I The user preferences cannot be saed because cookies are not enabled for your browser. Do you want to exit the user preferences? Explanation: The user preferences are saed on your computer as a cookie, but the cookie option on your browser is disabled. Operator Response: To sae user preferences, change the priacy settings for your browser to accept cookies. If you do not enable the cookie option, the user preferences affect only the current session. If you want to exit the user preferences, click Exit. If you do not want to exit the user preferences, click Cancel. ECOWRA001W The eent group eent_group_id is not recognized. Explanation: The specified eent group ID does not correspond to any known eent group. System Action: The command that referenced the specified eent group failed. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA002W The eent ID class_name is not recognized. Explanation: The specified eent ID does not correspond to any known eent ID class. System Action: The command that referenced the specified eent ID failed. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA003W ConnectionSpec class_name is not supported. Explanation: See message. System Action: The command that specified the ConnectionSpec failed. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA004W InteractionSpec class_name is not supported. Explanation: See message. System Action: The command that specified the InteractionSpec failed. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA005W The Web console serer encountered an error communicating with serer serer for user ID userid. Explanation: See message. System Action: The command that encountered the problem communicating with the Tioli Management Framework failed. Other processing is unaffected. Operator Response: Administrator. Contact the System Administrator Response: The CommunicationFailureException that includes this message includes a nested exception that proides additional details about the failure. To correct the problem, use the information in the nested exception together with other Tioli Management Framework diagnostic tools to determine why the Web console serer is unable to communicate with the Tioli Management Framework. ECOWRA006W User userid on serer serer is not authorized to iew eent data. Explanation: See message. System Action: The specified user is denied access to the Web console serer. Operator Response: Administrator. Contact the System Administrator Response: Ensure that the user is defined to the Tioli Management Framework and that the user has read access to the eent serer database. Then use the eent console to assign the operator to an eent console. ECOWRA007W The Web console serer encountered an unexpected exception when logging on to the IBM Tioli Management Framework: exception. Explanation: System Action: console serer. Operator Response: Administrator. See message. The user is denied access to the Web Contact the System Administrator Response: To determine the cause of the problem, use the included exception text. Appendix B. Messages 99

112 ECOWRA008W ECOWRA100W ECOWRA008W The task taskname failed. Explanation: The Web console serer could not run the task due to an internal error. System Action: The current task failed. Depending on the seerity of the error, processing on other tasks might also be impacted. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA009W User userid does not hae the role required to update eents in this eent group. Explanation: System Action: the actions. Operator Response: See message. The specified user is denied access to Contact your administrator. Administrator Response: Ensure that the user is defined to the Tioli Management Framework and that the user has the appropriate roles to make updates. Then use the eent console properties to assign the operator roles to an eent console. ECOWRA050E An internal error has occurred. Explanation: The Web console serer has detected an internal error. System Action: The current thread s processing fails. Depending on the seerity of the error, processing on other threads might also be impacted. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRA051E The Web console serer encountered a problem communicating with the eent serer database. Explanation: See message. System Action: The system continues to run, but communication with the eent serer database might not be possible. Administrator Response: An exception should hae been logged along with this message. For information about how to correct this problem, refer to the help text for the message contained in the exception. ECOWRA052W The UI serer has taken longer than seconds seconds to process a status change for eent eent_id. Explanation: System Action: See message. The Web console serer discards the pending status change for the eent. The status for the eent reerts to its preious alue until the eent is updated in the database and the caches for the Web console eent data expire. Administrator Response: This message indicates that the UI serer either neer receied the status change or it has not processed all of the status change requests. If this message occurs occasionally during periods of heay workload on the UI serer, you can ignore this message. Otherwise, determine why the UI serer is haing problems receiing and processing status change requests. ECOWRA053W The eent data cache timeout alue must be minimum_cache_time seconds or greater. The default alue, default_cache_time seconds, is used. Explanation: System Action: See message. See message. Administrator Response: Change the eent data cache timeout alue as specified in the message. The timeout alue must be specified in seconds. ECOWRA054W The eent summary cache timeout alue must be minimum_cache_time seconds or greater. The default alue, default_cache_time seconds, is used. Explanation: System Action: See message. See message. Administrator Response: Change the eent summary cache timeout alue as specified in the message. The timeout alue must be specified in seconds. ECOWRA100W The pending change for eent eent_id to status status timed out before completing. Explanation: See message. System Action: The Web console serer discards the pending status change for the eent. The status for the eent reerts to its preious alue until the eent is updated in the database and the Web console eent data caches expire. Operator Response: The status change for the eent might hae been lost before the UI serer processed the request. Acknowledge or close the eent again to ensure the change is processed. If this error persists, contact the System Administrator. Administrator Response: The Web console serer logs message ECOWRA052 in the IBM WebSphere Application Serer log file in conjunction with this message. For more information, refer to the help for message ECOWRA IBM Tioli Enterprise Console: User s Guide

113 ECOWRA101W ECOWRJ007W ECOWRA101W action on eent eent_id has been skipped due to preiously pending action. Explanation: See message. System Action: The Web console serer skips the specified action for the eent. Processing of other actions continues. Operator Response: Another operator has requested an action on the eent. Open or refresh the eent iewer to see the updated status of the eent with the pending action. ECOWRA102W Your request could not be completed in its entirety. The eents you were attempting to modify hae been modified since your last refresh or were being modified by another operator. Explanation: See message. Operator Response: Open or refresh the eent iewer to see the current status of the eents you were attempting to modify. If your changes are still necessary, modify the eents again. store the extracted files. Restart IBM WebSphere Applicaton Serer to force the Web console serer to retry the file extraction. ECOWRJ003E The ClassLoader URL url is not recognized. Explanation: The Web console serer encountered an unrecognized URL when examining its own classloader. Administrator Response: Ensure that IBM WebSphere Application Serer is using its own JRE and not an unsupported JRE. If this problem persists, contact IBM Customer Support. ECOWRJ004W The SQL AS keyword is not supported. Explanation: IBM Tioli Enterprise Console RIM JDBC Proider does not support the SQL AS keyword. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ001W Connection pool properties cannot be changed when open connections exist. Explanation: An attempt was made to change a property of the connection pool when the connection pool contained open connections. Connection pool properties can only be changed when there are no open connections. System Action: The system continues to use the preious property alues. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ002E The extract directory directory_name could not be created. Explanation: The Web console serer could not extract the required files to the specified directory. System Action: The Web console serer continues to run, but information stored in the database is not accessible until the error is corrected. Administrator Response: This problem preents the Web console serer from accessing eent data and operator console definitions that are stored in the eent serer database. Ensure that the operating system identity that IBM WebSphere Application Serer uses has permission to create and write to the specified directory. Also, ensure that the file system has at least 8MB of free space to ECOWRJ005W The SQL WHERE keyword was expected but token was found instead. Explanation: The IBM Tioli Enterprise Console RIM JDBC Proider found the specified token in the SQL query instead of the SQL WHERE keyword. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ006W The SQL query must contain a FROM clause. Explanation: The SQL query did not contain the required SQL FROM clause. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ007W A locale was not specified in a LOCALE clause. Explanation: The LOCALE keyword was not followed by a locale specifier. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an Appendix B. Messages 101

114 ECOWRJ008W ECOWSO001E internal problem in the Web console serer. Contact IBM Customer Support. internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ008W A condition was not specified specified for a WHERE clause. Explanation: The SQL WHERE keyword was not followed by any conditions. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ050E An internal error has occurred. Explanation: The Web console serer has detected an internal error. System Action: The current thread s processing failed. Depending on the seerity of the error, processing on other threads might also be impacted. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ009W An SQL query must start with the SELECT keyword. Explanation: The SQL query does not begin with the required SELECT keyword. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ010W The Column column in table table is not recognized. Explanation: The SQL query specified a column or a table that is not understood by the IBM Tioli Enterprise Console RIM JDBC Proider. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ011W The data class class for column column is not recognized. Explanation: The internal metadata for the indicated column specifies an unrecognized data class. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an internal problem in the Web console serer. Contact IBM Customer Support. ECOWRJ012W The Connection is no longer actie. Explanation: An attempt was made to use a connection that has been closed. System Action: The erroneous SQL command failed with an exception. Other processing is unaffected. Administrator Response: This error indicates an ECOWRJ051E The Web console serer encountered a problem extracting the JCF and JRIM JAR files. Explanation: The Web console serer was unable to extract the required JAR files. Communication with the eent serer database is not possible without these files. System Action: The system continues to run, but communication with the eent serer database is not possible. Administrator Response: An exception should hae been logged along with this message. Refer to the help text for the message contained in that exception for additional information. ECOWRJ052E The Web console serer encountered a problem communicating with the eent serer database. Explanation: See message. System Action: The system continues to run, but communication with the eent serer database might not be possible. Administrator Response: An exception should hae been logged along with this message. Refer to the help text for the message contained in that exception for additional information. ECOWSO001E An error occurred when communicating with the Tioli managed node. Explanation: See message. Operator Response: Retry the operation. If the problem persists, contact your administrator. Administrator Response: This error indicates a problem with the connection between the Web console serer, which uses the system information proided to the Web console, and the managed node. The information in the configuration preferences is used to 102 IBM Tioli Enterprise Console: User s Guide

115 ECOWSO002E ECOWTE003E establish a system-leel connection to the managed node. If the problem occurs on a consistent basis at startup for many or all Web consoles that attempt to connect to the Web console serer, erify that the following conditions are met: The serer name, the user name, and the password specified in the configuration preferences are correct. The computer running the Web console is connected to the network, and TCP/IP is functioning correctly. The Web console serer is running. The Web console serer and any firewalls between the computer running the Web console and the Web console serer are configured consistently. The port specified for access to the Web console serer is alid. If the problem is intermittent, it might be due to network traffic or a transient network problem. If the problem seems to be related to a specific operation, contact IBM Customer Support. ECOWSO002E Authentication failed. Explanation: The user name and password specified on the logon screen are not alid. Operator Response: Enter your user name and password again, ensuring that your user name and password are spelled correctly. ECOWSO003E The bootstrap process for the Web console application failed. The Web console might not function correctly. Report this problem to your administrator. Explanation: Operator Response: See message. See message. Administrator Response: To determine the cause of the problem, look in the IBM Web Application Serer log files. ECOWSO004I Your logon session has expired. Explanation: A logon session expires after a prolonged period of inactiity. Operator Response: If you want to use the Web console, log on again. ECOWSO005I Signoff is complete. Explanation: No additional information is aailable for this message. ECOWSV001E An error occurred when retrieing eent summary data from the eent serer database. Retry the operation or close the View Summary of Eents window. Explanation: The connection to the eent serer database or the eent serer database itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. ECOWTE001E An error occurred when retrieing task library names from the eent serer. Try running the task again. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: your administrator. If the problem persists, contact Administrator Response: To determine the cause of the problem, look in the Web console serer and the eent serer log files. ECOWTE002E An error occurred when retrieing task names from the eent serer. Try running the task again. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: your administrator. If the problem persists, contact Administrator Response: To determine the cause of the problem, look in the Web console serer and the eent serer log files. ECOWTE003E An error occurred when retrieing task information from the eent serer. Run the task again. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: your administrator. If the problem persists, contact Administrator Response: To determine the cause of the problem, look in the Web console serer and the eent serer log files. Appendix B. Messages 103

116 ECOWTE004E ECOWTE012E ECOWTE004E An error occurred when retrieing the names of the managed nodes from the eent serer. Retry the operation or cancel the task. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. Also, look in the eent serer log files. ECOWTE005E An error occurred retrieing the host names from the eent serer. Retry the operation or cancel the task. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. Also, look in the eent serer log files. ECOWTE006E The attempt to check the task prior to running it on the eent serer failed. Run the task again or cancel the task. Explanation: The connection to the eent serer or the eent serer itself might be down. Operator Response: See message. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. Also, look in the eent serer log files. ECOWTE007E The task failed to start on the eent serer. Make sure that the task can be run on the selected eents, and run the task again. Explanation: The task might hae failed for one of the following reasons: An eent was not selected prior to running the task. The task cannot be run on one of the selected eents. The connection to the eent serer or the eent serer itself might be down. Operator Response: Select an eent prior to running the task, or make sure that the task can be run on all of the selected eents. Then run the task again. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files for problems logged by the resource adapter or the JDBC proider. Also, look in the eent serer log files. ECOWTE008W You must select a task library and a task name. Explanation: When running a task, a task library and a task name hae not been selected. Operator Response: name. ECOWTE009W Select a task library and a task You must select a task name. Explanation: When running a task, a task name has not been selected. Operator Response: Select a task name. ECOWTE010W You must select one or more target hosts. Explanation: When running a task, one or more target hosts hae not been selected. Operator Response: Select one or more target hosts. ECOWTE011E The task failed because the configuration of the task is unsupported. Explanation: Operator Response: See message. Contact your administrator. Administrator Response: The layout for the task is unsupported. The Web console supports seen standard layouts: text (0) choice (1) text choice (2) choice button (3) radio button (4) crypto text (5) list selector (6) ECOWTE012E Your logon session is no longer alid. Explanation: Your session might hae timed out, or you might hae tried to access the Web console from a bookmark. Operator Response: Log on to the IBM Tioli Enterprise console again. 104 IBM Tioli Enterprise Console: User s Guide

117 ECOWTE013E ECOWUM004E ECOWTE013E The task failed due to a shortage of resources in the Web console serer. Explanation: See message. Operator Response: Run the task again. If the failure persists, contact your administrator. Administrator Response: The Web console serer could not create a thread to run the task. Configure IBM WebSphere Application Serer to make more resources aailable. ECOWTE014E The task output has not been receied. Explanation: The task output was not receied within the timeout period. Howeer, the task might hae completed on the eent serer. It is also possible that the task did not complete or was neer started if the connection to the eent serer or the eent serer itself is down. Operator Response: Run the task again if doing so will not cause problems if the original task completed. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log file for problems logged by the resource adapter or the JDBC proider. Also, look in the eent serer log files. ECOWTE015E The task did not complete due to a problem in the Web console serer. Explanation: See message. Operator Response: Run the task again. If the problem persists, contact your administrator. Administrator Response: To determine the cause of the problem, look in the Web console serer log files. ECOWTE018W Do you want to continue? Explanation: This message confirms whether or not you want to cancel this operation in the task wizard. Operator Response: If you want to continue this operation, click Continue. If you do not want to cancel this operation, click Cancel. ECOWUM001E You are not authorized the run the action_name action on the selected item number sel_row. Explanation: You must log on with the appropriate authorization to run this action. Operator Response: Contact your adminstrator to get the appropriate authorization. ECOWUM002E You hae selected actual_sels items. You must select needed_sels to run the action_name action. Explanation: Each action requires that you select a specific number of items. Operator Response: Select the appropriate number of items and retry the action. ECOWUM003E Because you are not authorized the run the action_name action on some of the selected items, the action has not been run on any of the selected items. Explanation: You must hae the appropiate authorization to run the action on all of the items you select. Operator Response: Deselect the items for which you do not hae appropriate authorization and try the action again. ECOWTE016E The task cannot run on the eent source host because the eent does not contain the eent source host name. Explanation: A task has been configured to run on the eent source host in one or more eents. Howeer, the hostname slot in one or more of the eents does not contain the eent source host name. Operator Response: Run the task on the appropriate host instead of on the eent source host. ECOWTE017W Do you want to exit the task wizard? Explanation: This message confirms whether or not you want to exit the task wizard. Operator Response: If you want to exit the task wizard, click Exit. If you do not want to exit the task wizard, click Cancel. ECOWUM004E An error occurred when running the action_name action against the selected item number sel_row. Explanation: The Web console encountered an error when communicating with the eent serer. Operator Response: Try the operation again. If the problem persists, contact your administrator. Administrator Response: This error indicates a problem with the connection between the Web console serer, which uses the system information proided in the Web console configuration preferences, and the eent serer. The information in the configuration preferences is used to establish a system-leel connection to the eent serer. If the problem persists at startup for many or all consoles that attempt to connect to the Web console serer, ensure that the following conditions are met: Appendix B. Messages 105

118 The serer name, user name, and password specified in the configuration preferences are correct. The computer running the Web console is connected to the network, and TCP/IP networking is functioning correctly. The Web console serer is running. The Web console serer and any firewalls between the computer running the Web console and Web console serer are configured consistently. If the problem is intermittent, it might be due to network traffic or a transient network problem. If the problem seems to be related to a specific operation, contact IBM Customer Support. 106 IBM Tioli Enterprise Console: User s Guide

119 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user s responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Copyright IBM Corp

120 IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of deeloping, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. Trademarks IBM, the IBM logo, Tioli, the Tioli logo, AIX, AS/400, DB2, NetView, Tioli Enterprise, Tioli Enterprise Console, TME, TME 10, Tioli Management Enironment, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation or Tioli Systems Inc. in the United States, other countries, or both. 108 IBM Tioli Enterprise Console: User s Guide

121 Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of the Open Group in the United States and other countries. Other company, product, and serice names may be trademarks or serice marks of others. Notices 109

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

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 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

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

Tivoli Business Systems Manager

Tivoli Business Systems Manager Tioli Business Systems Manager Version 3.1 Problem and Change Management Integration Guide SC32-9130-00 Tioli Business Systems Manager Version 3.1 Problem and Change Management Integration Guide SC32-9130-00

More information

Tivoli Business Systems Manager

Tivoli Business Systems Manager Tioli Business Systems Manager Version 3.1 Introducing the Consoles SC32-9086-00 Tioli Business Systems Manager Version 3.1 Introducing the Consoles SC32-9086-00 Note Before using this information and

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

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

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

WebSphere MQ Configuration Agent User's Guide

WebSphere MQ Configuration Agent User's Guide IBM Tioli Composite Application Manager for Applications Version 7.1 WebSphere MQ Configuration Agent User's Guide SC14-7525-00 IBM Tioli Composite Application Manager for Applications Version 7.1 WebSphere

More information

xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide

xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide xseries Systems Management IBM Diagnostic Data Capture 1.0 Installation and User s Guide Note Before using this information and the product it supports, read the general information in Appendix C, Notices,

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

Monitor Developer s Guide

Monitor Developer s Guide IBM Tioli Priacy Manager for e-business Monitor Deeloper s Guide Version 1.1 SC23-4790-00 IBM Tioli Priacy Manager for e-business Monitor Deeloper s Guide Version 1.1 SC23-4790-00 Note: Before using this

More information

IBM Tivoli Monitoring: AIX Premium Agent Version User's Guide SA

IBM Tivoli Monitoring: AIX Premium Agent Version User's Guide SA Tioli IBM Tioli Monitoring: AIX Premium Agent Version 6.2.2.1 User's Guide SA23-2237-06 Tioli IBM Tioli Monitoring: AIX Premium Agent Version 6.2.2.1 User's Guide SA23-2237-06 Note Before using this information

More information

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

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server. User s Guide. Version SC IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server User s Guide Version 5.1.1 SC23-4705-01 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server User s Guide

More information

Tivoli Identity Manager. End User Guide. Version SC

Tivoli Identity Manager. End User Guide. Version SC Tioli Identity Manager End User Guide Version 4.5.1 SC32-1152-02 Tioli Identity Manager End User Guide Version 4.5.1 SC32-1152-02 NOTE: Before using this information and the product it supports, read

More information

Version 8.2 (Revised December 2004) Plus Module User s Guide SC

Version 8.2 (Revised December 2004) Plus Module User s Guide SC Tioli IBM Tioli Workload Scheduler Version 8.2 (Reised December 2004) Plus Module User s Guide SC32-1276-02 Tioli IBM Tioli Workload Scheduler Version 8.2 (Reised December 2004) Plus Module User s Guide

More information

Installing and Configuring Tivoli Enterprise Data Warehouse

Installing and Configuring Tivoli Enterprise Data Warehouse Installing and Configuring Tioli Enterprise Data Warehouse Version 1 Release 1 GC32-0744-00 Installing and Configuring Tioli Enterprise Data Warehouse Version 1 Release 1 GC32-0744-00 Installing and Configuring

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Windows GC32-1604-00 Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Windows GC32-1604-00

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

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Linux on Intel and Linux on iseries GC32-1616-00 Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Linux on Intel and

More information

IBM i Version 7.2. Security Service Tools IBM

IBM i Version 7.2. Security Service Tools IBM IBM i Version 7.2 Security Serice Tools IBM IBM i Version 7.2 Security Serice Tools IBM Note Before using this information and the product it supports, read the information in Notices on page 37. This

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

Installation and Configuration Guide

Installation and Configuration Guide IBM Tioli Directory Serer Installation and Configuration Guide Version 6.2 SC23-9939-00 IBM Tioli Directory Serer Installation and Configuration Guide Version 6.2 SC23-9939-00 Note Before using this information

More information

Web Services Security Management Guide

Web Services Security Management Guide IBM Tioli Federated Identity Manager Version 6.2.2 Web Serices Security Management Guide GC32-0169-04 IBM Tioli Federated Identity Manager Version 6.2.2 Web Serices Security Management Guide GC32-0169-04

More information

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide IBM Director 4.20 Virtual Machine Manager 1.0 Installation and User s Guide Note Before using this information and the product it supports, read the general information in Appendix D, Notices, on page

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 Planning and Configuration Guide SC23-9820-00 Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring

More information

IBM Operational Decision Manager Version 8 Release 5. Installation Guide

IBM Operational Decision Manager Version 8 Release 5. Installation Guide IBM Operational Decision Manager Version 8 Release 5 Installation Guide Note Before using this information and the product it supports, read the information in Notices on page 51. This edition applies

More information

Tivoli Monitoring: Windows OS Agent

Tivoli Monitoring: Windows OS Agent Tioli Monitoring: Windows OS Agent Version 6.2.2 User s Guide SC32-9445-03 Tioli Monitoring: Windows OS Agent Version 6.2.2 User s Guide SC32-9445-03 Note Before using this information and the product

More information

Extended Search Administration

Extended Search Administration IBM Extended Search Extended Search Administration Version 3 Release 7 SC27-1404-00 IBM Extended Search Extended Search Administration Version 3 Release 7 SC27-1404-00 Note! Before using this information

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Unix GC32-1605-00 Tioli Tioli Intelligent ThinkDynamic Orchestrator Version 2.1 Installation Guide for Unix GC32-1605-00

More information

Tivoli IBM Tivoli Advanced Audit for DFSMShsm

Tivoli IBM Tivoli Advanced Audit for DFSMShsm Tioli IBM Tioli Adanced Audit for DFSMShsm Version 2.2.0 Monitoring Agent Planning and Configuration Guide SC27-2348-00 Tioli IBM Tioli Adanced Audit for DFSMShsm Version 2.2.0 Monitoring Agent Planning

More information

Tivoli Tivoli Provisioning Manager

Tivoli Tivoli Provisioning Manager Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Unix GC32-1615-00 Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Unix GC32-1615-00 Note: Before using this information

More information

Tivoli Business Systems Manager

Tivoli Business Systems Manager Tioli Business Systems Manager Version 3.1 Installation and Configuration Guide SC32-9089-00 Tioli Business Systems Manager Version 3.1 Installation and Configuration Guide SC32-9089-00 Note Before using

More information

IBM. Installing, configuring, using, and troubleshooting. IBM Operations Analytics for z Systems. Version 3 Release 1

IBM. Installing, configuring, using, and troubleshooting. IBM Operations Analytics for z Systems. Version 3 Release 1 IBM Operations Analytics for z Systems IBM Installing, configuring, using, and troubleshooting Version 3 Release 1 IBM Operations Analytics for z Systems IBM Installing, configuring, using, and troubleshooting

More information

IBM Tivoli Service Level Advisor. Getting Started. Version 2.1 SC

IBM Tivoli Service Level Advisor. Getting Started. Version 2.1 SC IBM Tioli Serice Leel Adisor Getting Started Version 2.1 SC32-0834-03 IBM Tioli Serice Leel Adisor Getting Started Version 2.1 SC32-0834-03 Fourth Edition (September 2004) This edition applies to Version

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

IBM Sterling Gentran:Server for Windows. Installation Guide. Version 5.3.1

IBM Sterling Gentran:Server for Windows. Installation Guide. Version 5.3.1 IBM Sterling Gentran:Serer for Windows Installation Guide Version 5.3.1 IBM Sterling Gentran:Serer for Windows Installation Guide Version 5.3.1 Note Before using this information and the product it supports,

More information

System i and System p. Capacity on Demand

System i and System p. Capacity on Demand System i and System p Capacity on Demand System i and System p Capacity on Demand Note Before using this information and the product it supports, read the information in Notices on page 65 and the IBM

More information

IBM Tivoli Storage Manager for Windows Version 7.1. Installation Guide

IBM Tivoli Storage Manager for Windows Version 7.1. Installation Guide IBM Tioli Storage Manager for Windows Version 7.1 Installation Guide IBM Tioli Storage Manager for Windows Version 7.1 Installation Guide Note: Before using this information and the product it supports,

More information

IBM Tivoli Service Level Advisor. SLM Reports. Version 2.1 SC

IBM Tivoli Service Level Advisor. SLM Reports. Version 2.1 SC IBM Tioli Serice Leel Adisor SLM Reports Version 2.1 SC32-1248-00 IBM Tioli Serice Leel Adisor SLM Reports Version 2.1 SC32-1248-00 Fourth Edition (September 2004) This edition applies to Version 2.1

More information

Tivoli Decision Support for OS/390. Administration Guide. Version 1.6, December 2003 SH

Tivoli Decision Support for OS/390. Administration Guide. Version 1.6, December 2003 SH Tioli Decision Support for OS/390 Administration Guide Version 1.6, December 2003 SH19-6816-08 Tioli Decision Support for OS/390 Administration Guide Version 1.6, December 2003 SH19-6816-08 Note Before

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

Troubleshooting Guide

Troubleshooting Guide Tioli Access Manager for e-business Version 6.1.1 Troubleshooting Guide GC27-2717-00 Tioli Access Manager for e-business Version 6.1.1 Troubleshooting Guide GC27-2717-00 Note Before using this information

More information

IBM InfoSphere Information Server Integration Guide for IBM InfoSphere DataStage Pack for SAP BW

IBM InfoSphere Information Server Integration Guide for IBM InfoSphere DataStage Pack for SAP BW IBM InfoSphere Information Serer Version 11 Release 3 IBM InfoSphere Information Serer Integration Guide for IBM InfoSphere DataStage Pack for SAP BW SC19-4314-00 IBM InfoSphere Information Serer Version

More information

Upward Integration Modules Installation Guide

Upward Integration Modules Installation Guide IBM Director 4.1 Upward Integration Modules Installation Guide SC01-R051-20 IBM Director 4.1 Upward Integration Modules Installation Guide SC01-R051-20 Note: Before using this information and the product

More information

Web Security Developer Reference

Web Security Developer Reference IBM Tioli Access Manager for e-business Web Security Deeloper Reference Version 5.1 SC32-1358-00 IBM Tioli Access Manager for e-business Web Security Deeloper Reference Version 5.1 SC32-1358-00 Note Before

More information

LotusLive. LotusLive Engage and LotusLive Connections User's Guide

LotusLive. LotusLive Engage and LotusLive Connections User's Guide LotusLie LotusLie Engage and LotusLie Connections User's Guide LotusLie LotusLie Engage and LotusLie Connections User's Guide Note Before using this information and the product it supports, read the information

More information

Problem Determination Guide

Problem Determination Guide IBM Tioli Monitoring for Business Integration Problem Determination Guide 5.1.1 SC32-1404-00 IBM Tioli Monitoring for Business Integration Problem Determination Guide 5.1.1 SC32-1404-00 Note Before using

More information

Managing Server Installation and Customization Guide

Managing Server Installation and Customization Guide IBM Tioli Composite Application Manager for Application Diagnostics Version 7.1.0.4 Managing Serer Installation and Customization Guide SC27-2825-00 IBM Tioli Composite Application Manager for Application

More information

IBM Agent Builder Version User's Guide IBM SC

IBM Agent Builder Version User's Guide IBM SC IBM Agent Builder Version 6.3.5 User's Guide IBM SC32-1921-17 IBM Agent Builder Version 6.3.5 User's Guide IBM SC32-1921-17 Note Before you use this information and the product it supports, read the information

More information

Installation and Configuration Guide

Installation and Configuration Guide IBM Tioli Directory Serer Installation and Configuration Guide Version 6.3 SC27-2747-00 IBM Tioli Directory Serer Installation and Configuration Guide Version 6.3 SC27-2747-00 Note Before using this information

More information

IBM System Migration Assistant 4.2. User s Guide

IBM System Migration Assistant 4.2. User s Guide IBM System Migration Assistant 4.2 User s Guide IBM System Migration Assistant 4.2 User s Guide Note: Before using this information and the product it supports, read the general information in Appendix

More information

IBM Tivoli Privacy Manager for e-business. Installation Guide. Version 1.1 SC

IBM Tivoli Privacy Manager for e-business. Installation Guide. Version 1.1 SC IBM Tioli Priacy Manager for e-business Installation Guide Version 1.1 SC23-4791-00 IBM Tioli Priacy Manager for e-business Installation Guide Version 1.1 SC23-4791-00 Note: Before using this information

More information

Troubleshooting Guide

Troubleshooting Guide Security Policy Manager Version 7.1 Troubleshooting Guide GC27-2711-00 Security Policy Manager Version 7.1 Troubleshooting Guide GC27-2711-00 Note Before using this information and the product it supports,

More information

Deployment Overview Guide

Deployment Overview Guide IBM Security Priileged Identity Manager Version 1.0 Deployment Oeriew Guide SC27-4382-00 IBM Security Priileged Identity Manager Version 1.0 Deployment Oeriew Guide SC27-4382-00 Note Before using this

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

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

High Availability Guide for Distributed Systems

High Availability Guide for Distributed Systems IBM Tioli Monitoring Version 6.2.3 Fix Pack 1 High Aailability Guide for Distributed Systems SC23-9768-03 IBM Tioli Monitoring Version 6.2.3 Fix Pack 1 High Aailability Guide for Distributed Systems SC23-9768-03

More information

Registration Authority Desktop Guide

Registration Authority Desktop Guide IBM SecureWay Trust Authority Registration Authority Desktop Guide Version 3 Release 1.1 SH09-4530-01 IBM SecureWay Trust Authority Registration Authority Desktop Guide Version 3 Release 1.1 SH09-4530-01

More information

Monitoring: Windows OS Agent Version Fix Pack 2 (Revised May 2010) User s Guide SC

Monitoring: Windows OS Agent Version Fix Pack 2 (Revised May 2010) User s Guide SC Tioli Monitoring: Windows OS Agent Version 6.2.2 Fix Pack 2 (Reised May 2010) User s Guide SC32-9445-03 Tioli Monitoring: Windows OS Agent Version 6.2.2 Fix Pack 2 (Reised May 2010) User s Guide SC32-9445-03

More information

IBM Tivoli Storage Manager for Windows Version Installation Guide

IBM Tivoli Storage Manager for Windows Version Installation Guide IBM Tioli Storage Manager for Windows Version 7.1.1 Installation Guide IBM Tioli Storage Manager for Windows Version 7.1.1 Installation Guide Note: Before using this information and the product it supports,

More information

IBM Tivoli Composite Application Manager Agent for DB2 Version 7.1. User s Guide SC

IBM Tivoli Composite Application Manager Agent for DB2 Version 7.1. User s Guide SC IBM Tioli Composite Application Manager Agent for DB2 Version 7.1 User s Guide SC27-2491-01 IBM Tioli Composite Application Manager Agent for DB2 Version 7.1 User s Guide SC27-2491-01 Note Before using

More information

Network Service Manager REST API Users Guide

Network Service Manager REST API Users Guide Netcool Configuration Manager Version 641 Network Serice Manager REST API Users Guide for R2E3 Netcool Configuration Manager Version 641 Network Serice Manager REST API Users Guide for R2E3 Note Before

More information

IBM i Version 7.2. Connecting to IBM i IBM i Access for Web IBM

IBM i Version 7.2. Connecting to IBM i IBM i Access for Web IBM IBM i Version 7.2 Connecting to IBM i IBM i Access for Web IBM IBM i Version 7.2 Connecting to IBM i IBM i Access for Web IBM Note Before using this information and the product it supports, read the information

More information

IBM i Version 7.3. Networking TCP/IP troubleshooting IBM

IBM i Version 7.3. Networking TCP/IP troubleshooting IBM IBM i Version 7.3 Networking TCP/IP troubleshooting IBM IBM i Version 7.3 Networking TCP/IP troubleshooting IBM Note Before using this information and the product it supports, read the information in

More information

IBM Tivoli Service Level Advisor. Troubleshooting. Version 2.1 SC

IBM Tivoli Service Level Advisor. Troubleshooting. Version 2.1 SC IBM Tioli Serice Leel Adisor Troubleshooting Version 2.1 SC32-1249-00 First Edition (September 2004) This edition applies to Version 2.1 of IBM Tioli Serice Leel Adisor (program number 5724 C40) and to

More information

IBM. RSE for z/os User's Guide. IBM Explorer for z/os. Version 3 Release 1 SC

IBM. RSE for z/os User's Guide. IBM Explorer for z/os. Version 3 Release 1 SC IBM Explorer for z/os IBM RSE for z/os User's Guide Version 3 Release 1 SC27-8433-03 IBM Explorer for z/os IBM RSE for z/os User's Guide Version 3 Release 1 SC27-8433-03 Note Before using this information,

More information

IBM Monitoring Agent for OpenStack Version User's Guide IBM SC

IBM Monitoring Agent for OpenStack Version User's Guide IBM SC IBM Monitoring Agent for OpenStack Version 7.5.0.1 User's Guide IBM SC27-6586-01 IBM Monitoring Agent for OpenStack Version 7.5.0.1 User's Guide IBM SC27-6586-01 Note Before using this information and

More information

User s Guide GC

User s Guide GC Tioli IBM Tioli Monitoring for Databases: Sybase ASE 5.1.2 User s Guide GC32-9136-00 Tioli IBM Tioli Monitoring for Databases: Sybase ASE 5.1.2 User s Guide GC32-9136-00 Note Before using this information

More information

Live Partition Mobility ESCALA REFERENCE 86 A1 85FA 01

Live Partition Mobility ESCALA REFERENCE 86 A1 85FA 01 Lie Partition Mobility ESCALA REFERENCE 86 A1 85FA 01 ESCALA Lie Partition Mobility Hardware May 2009 BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDE 01 FRANCE REFERENCE 86 A1 85FA 01 The following

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

IMS Performance Feature Guide and Reference

IMS Performance Feature Guide and Reference Tioli Decision Support for OS/390 IMS Performance Feature Guide and Reference Version 1.6, December 2003 SH19-6825-07 Tioli Decision Support for OS/390 IMS Performance Feature Guide and Reference Version

More information

WebSEAL Installation Guide

WebSEAL Installation Guide IBM Tioli Access Manager WebSEAL Installation Guide Version 4.1 SC32-1133-01 IBM Tioli Access Manager WebSEAL Installation Guide Version 4.1 SC32-1133-01 Note Before using this information and the product

More information

IBM i Version 7.2. Networking TCP/IP troubleshooting IBM

IBM i Version 7.2. Networking TCP/IP troubleshooting IBM IBM i Version 7.2 Networking TCP/IP troubleshooting IBM IBM i Version 7.2 Networking TCP/IP troubleshooting IBM Note Before using this information and the product it supports, read the information in

More information

IBM System Migration Assistant 4.1. User s Guide SC90-P288-70

IBM System Migration Assistant 4.1. User s Guide SC90-P288-70 IBM System Migration Assistant 4.1 User s Guide SC90-P288-70 Note: Before using this information and the product it supports, read the general information in Appendix D, Notices, on page 81. Third Edition

More information

Tivoli Application Dependency Discovery Manager Version 7.3. Installation Guide IBM

Tivoli Application Dependency Discovery Manager Version 7.3. Installation Guide IBM Tioli Application Dependency Discoery Manager Version 7.3 Installation Guide IBM Tioli Application Dependency Discoery Manager Version 7.3 Installation Guide IBM Note Before using this information and

More information

IBM. Basic system operations. System i. Version 6 Release 1

IBM. Basic system operations. System i. Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 IBM System i Basic system operations Version 6 Release 1 Note Before using this information and the product it supports, read the information in

More information

IBM Tivoli Access Manager for WebSphere Application Server. User s Guide. Version 4.1 SC

IBM Tivoli Access Manager for WebSphere Application Server. User s Guide. Version 4.1 SC IBM Tioli Access Manager for WebSphere Application Serer User s Guide Version 4.1 SC32-1136-01 IBM Tioli Access Manager for WebSphere Application Serer User s Guide Version 4.1 SC32-1136-01 Note Before

More information

Maintenance and Troubleshooting Guide

Maintenance and Troubleshooting Guide Tioli Management Framework Maintenance and Troubleshooting Guide Version 4.1.1 GC32-0807-01 Tioli Management Framework Maintenance and Troubleshooting Guide Version 4.1.1 GC32-0807-01 Note Before using

More information

IBM Tivoli Netcool Performance Manager Wireline Component October 2015 Document Revision R2E1. Pack Upgrade Guide IBM

IBM Tivoli Netcool Performance Manager Wireline Component October 2015 Document Revision R2E1. Pack Upgrade Guide IBM IBM Tioli Netcool Performance Manager Wireline Component October 2015 Document Reision R2E1 Pack Upgrade Guide IBM Note Before using this information and the product it supports, read the information in

More information

Administrator s Guide

Administrator s Guide Tioli NetView for UNIX Administrator s Guide Version 7 1. 4 SC32-1246-00 Tioli NetView for UNIX Administrator s Guide Version 7 1. 4 SC32-1246-00 Note Before using this information and the product it

More information

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

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

More information

IBM Tivoli Storage Manager for Windows Version Tivoli Monitoring for Tivoli Storage Manager

IBM Tivoli Storage Manager for Windows Version Tivoli Monitoring for Tivoli Storage Manager IBM Tioli Storage Manager for Windows Version 7.1.0 Tioli Monitoring for Tioli Storage Manager IBM Tioli Storage Manager for Windows Version 7.1.0 Tioli Monitoring for Tioli Storage Manager Note: Before

More information

DocumentationcorrectionsforIBMTivoli Storage Productivity Center V4.2

DocumentationcorrectionsforIBMTivoli Storage Productivity Center V4.2 DocumentationcorrectionsforIBMTioli Storage Productiity Center V4.2 ii Documentation corrections for IBM Tioli Storage Productiity Center V4.2 Contents Documentation corrections for IBM Tioli Storage Productiity

More information

Tivoli Identity Manager

Tivoli Identity Manager Tioli Identity Manager Version 4.6 Serer Installation and Configuration Guide for WebSphere Enironments SC32-1750-01 Tioli Identity Manager Version 4.6 Serer Installation and Configuration Guide for WebSphere

More information

Tivoli Storage Manager for Enterprise Resource Planning

Tivoli Storage Manager for Enterprise Resource Planning Tioli Storage Manager for Enterprise Resource Planning Version 6.1 Data Protection for SAP Installation and User s Guide for Oracle SC33-6340-10 Tioli Storage Manager for Enterprise Resource Planning

More information

Adapters in the Mainframe Connectivity Suite User Guide

Adapters in the Mainframe Connectivity Suite User Guide IBM WebSphere Business Integration Adapters Adapters in the Mainframe Connectiity Suite User Guide Adapter Version 2.2.x IBM WebSphere Business Integration Adapters Adapters in the Mainframe Connectiity

More information

AdapterforVantiveUserGuide

AdapterforVantiveUserGuide IBM WebSphere Business Integration Adapters AdapterforVantieUserGuide V3.6.x IBM WebSphere Business Integration Adapters AdapterforVantieUserGuide V3.6.x Note! Before using this information and the product

More information

Tivoli Application Dependency Discovery Manager Version 7 Release 2.1. Installation Guide

Tivoli Application Dependency Discovery Manager Version 7 Release 2.1. Installation Guide Tioli Application Dependency Discoery Manager Version 7 Release 2.1 Installation Guide Tioli Application Dependency Discoery Manager Version 7 Release 2.1 Installation Guide Note Before using this information

More information

IBM Tivoli OMEGAMON XE for CICS TG on z/os Version User's Guide SC

IBM Tivoli OMEGAMON XE for CICS TG on z/os Version User's Guide SC IBM Tioli OMEGAMON XE for CICS TG on z/os Version 5.1.0 User's Guide SC14-7476-00 IBM Tioli OMEGAMON XE for CICS TG on z/os Version 5.1.0 User's Guide SC14-7476-00 Note Before using this information and

More information

Solutions for BSM Version 1.1. Solutions for BSM Guide

Solutions for BSM Version 1.1. Solutions for BSM Guide Solutions for BSM Version 1.1 Solutions for BSM Guide Solutions for BSM Version 1.1 Solutions for BSM Guide Note Before using this information and the product it supports, read the information in Notices.

More information

IBM Tivoli Directory Server. System Requirements SC

IBM Tivoli Directory Server. System Requirements SC IBM Tioli Directory Serer System Requirements Version 6.2 SC23-9947-00 IBM Tioli Directory Serer System Requirements Version 6.2 SC23-9947-00 Note Before using this information and the product it supports,

More information

IBM. Client Configuration Guide. IBM Explorer for z/os. Version 3 Release 1 SC

IBM. Client Configuration Guide. IBM Explorer for z/os. Version 3 Release 1 SC IBM Explorer for z/os IBM Client Configuration Guide Version 3 Release 1 SC27-8435-01 IBM Explorer for z/os IBM Client Configuration Guide Version 3 Release 1 SC27-8435-01 Note Before using this information,

More information

ImageUltra Builder Version 1.1. User Guide

ImageUltra Builder Version 1.1. User Guide ImageUltra Builder Version 1.1 User Guide ImageUltra Builder Version 1.1 User Guide Note Before using this information and the product it supports, be sure to read Notices on page 83. First Edition (October

More information

Tivoli IBM Tivoli Monitoring for Messaging and Collaboration: Microsoft Exchange Server

Tivoli IBM Tivoli Monitoring for Messaging and Collaboration: Microsoft Exchange Server Tioli IBM Tioli Monitoring for Messaging and Collaboration: Microsoft Exchange Serer Version 5.1.2 Problem Determination Guide SC32-9113-00 Tioli IBM Tioli Monitoring for Messaging and Collaboration:

More information

IBM Unica Detect Version 8 Release 5 October 26, Administrator's Guide

IBM Unica Detect Version 8 Release 5 October 26, Administrator's Guide IBM Unica Detect Version 8 Release 5 October 26, 2011 Administrator's Guide Note Before using this information and the product it supports, read the information in Notices on page 175. This edition applies

More information

Administration Java Classes Developer Reference

Administration Java Classes Developer Reference IBM Tioli Access Manager for e-business Administration Jaa Classes Deeloper Reference Version 5.1 SC32-1356-00 IBM Tioli Access Manager for e-business Administration Jaa Classes Deeloper Reference Version

More information

User s Guide for PeopleSoft Access Method

User s Guide for PeopleSoft Access Method IBM Tioli Workload Scheduler for Applications User s Guide for PeopleSoft Access Method Version 8.1.1 (Maintenance Release Noember 2003) SH19-8502-01 IBM Tioli Workload Scheduler for Applications User

More information