Solutions for BSM Version 1.1. Solutions for BSM Guide

Size: px
Start display at page:

Download "Solutions for BSM Version 1.1. Solutions for BSM Guide"

Transcription

1 Solutions for BSM Version 1.1 Solutions for BSM Guide

2

3 Solutions for BSM Version 1.1 Solutions for BSM Guide

4 Note Before using this information and the product it supports, read the information in Notices. Edition notice This edition applies to ersion 1.1 of IBM Solutions for Business Serice Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii About this publication ix Intended audience ix Chapter 1. Introduction Persona-based iews of Business Serice Management Dashboard oeriew Architectural oeriew Chapter 2. Deploying the Solutions for BSM Product requirements Running the Deployment Wizard Launchpad options Deploy Best Practice Monitoring Situation types and queries Specifying target computer for situations Situation and query configuration Summary for situation deployment Deploy Best Practice ITCAM Monitoring Configuring the ITCAM Application Management Configuration Editor Specifying target computer for integration packages Specifying target for Transaction Tracking DLA 32 Specifying target for Application DLA templates 33 TBSM Integration package serer configuration 34 DLA Integration package serer configuration.. 36 Transaction Tracking DLA configuration Application DLA template configuration Summary for ITCAM Monitoring deployment.. 40 Deploying Automated Discoery Specifying target for monitoring DLA automation 42 Specifying target for TADDM DLA automation 43 Monitoring DLA Automation configuration TADDM DLA Automation configuration Summary for Automated Discoery deployment 47 DLA automation steps Deploy eent manager customizations Failoer and multi-host ObjectSerer and probe considerations Specifying target computer for Eent Manager tasks Tioli Monitoring Eent synchronization configuration Netcool/OMNIbus and Tioli Monitoring eent configuration Modify Netcool/OMNIbus default deduplication trigger Netcool/OMNIbus ITCAM Eent configuration 63 Configure Solutions for BSM Netcool/OMNIbus schema Configure EIF probe for ITM eents Configure EIF probe for TADDM eents Summary for Eent Customizations deployment 71 Deploy TBSM customizations Deploying a Data serer in a failoer enironment Specifying target computer for TBSM tasks Configure TBSM data serer Configure TBSM Dashboard serer Configure Web GUI customizations Deploy a Single Sign-On configuration Prerequisites for Single Sign-On configuration.. 78 Specifying the target computer for Single Sign-on tasks Configuring the TBSM Dashboard serer for LDAP Configuring the TBSM Dashboard serer for Single Sign-On Configuring the TBSM Data serer for LDAP.. 84 Configuring the TADDM WebSphere serer for LDAP Configure the TADDM WebSphere Serer for the Virtual Member Manager Serice EJB Configuring the TADDM WebSphere serer for Single Sign-On Exporting the LTPA keys from the TBSM Dashboard serer Importing the LTPA keys into the TADDM WebSphere serer Configuring the TADDM connection to the WebSphere serer Configuring Tioli Monitoring for LDAP and Single Sign-On Remoing the Single Sign-On configuration deployed by Solutions for Business Serice Management Remoing Single Sign-On and LDAP from WebSphere serers Chapter 3. Post-installation configuration Tioli Monitoring situations Relationship Wizard Configuring and Running the Relationship Wizard Using the Relationship Wizard DLA automation considerations BSMAcceleratorUser role Discoery Library Toolkit considerations Single sign-on configuration Chapter 4. Uninstalling Solutions for BSM modifications Remoing TBSM Dashboard serer modifications 105 Remoing TBSM Data serer modifications Remoing the database objects Copyright IBM Corp iii

6 2. Remoing Netcool/Impact objects Remoing the Business Serice Composer project Remoing the xml template mapping modifications Inalidating modified serice tree hierarchy Remoing serice templates Remoing custom data fetchers Remoe the BSM Accelerator root serice Delete backup directory and bsma_tbsminstall.properties file Uninstalling DLA Automation feature Uninstalling TADDM artifacts for DLA automation Uninstalling ITCAM for Transactions integration from TBSM Uninstalling ITCAM for Transactions integration from Netcool/OMNIbus Uninstalling ITCAM for Transaction Tracking Discoery Library Adapter objects Uninstalling ITCAM for Applications WebSphere and the HTTP serer agent Discoery Library Adapter objects Remoe Tioli Monitoring modifications Remoing Tioli Monitoring DLA templates Uninstall Tioli Monitoring queries Remoing Tioli Monitoring situations Remoing the OMNIbus customizations Uninstalling the ITM Eent Synchronization component Remoing the ObjectSerer database customizations Remoing the EIF probe customizations Remoing OMNIbus Web GUI iews and filters 121 Chapter 5. Product modifications TBSM updates About the TBSM serice templates Class mapping for Solutions for Business Serice Manager TBSM serice templates Serice tree scorecard templates Customizations to the TBSM right-click menus 130 Customization of the TBSM BIRT charts Main_CheckForDepsEntry Impact policy Discoery Library Toolkit artifacts Business Serice Composer Netcool/Impact policies for the Solutions for BSM 133 Customizing eent enrichment behaior Netcool/OMNIbus updates ObjectSerer database updates EIF Probe rules updates WebGUI AEL filtering Configuring Tioli Application Dependency Discoery Manager Discoery Library Adapter for the HTTP serer monitoring agent About the HTTP Serer Agent DLA HTTP Serer Agent data model classes Discoery Library Adapter for ITCAM for Transactions agents About the ITCAM for Transactions DLA ITCAM for Transactions agent data model classes Discoery Library Adapter for ITCAM Agent for WebSphere Applications About the WebSphere Agent DLA WebSphere Agent data model classes Predefined situations for Solutions for BSM Predefined situations for ITM OS agents Predefined situations for ITM database agents 165 Predefined situations for application agents Predefined situations for VMware agents Support for Time Window Analyzer metric collection Chapter 6. Isolating problems using the Business Serice Health pages Business Serice Health page oeriew Business Serice Health Details page Oeriew Custom solutions using the Business Serice Healthproide portlets Building a page using the Business Serice Health portlets Adding custom charts to a page Adding metrics to the Time Window Analyzer 189 Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) About the Time Window Analyzer portlet Software requirements Change eent process oeriew Application Dependency Discoery Manager change eent modifications Enabling the generation of change eents Configuring the resources to track Configuring the change eent recipient Updating the EIF probe properties Configuring change eents for a business system Defining the configuration files to be monitored 194 Scheduling the discoery Restarting TADDM to implement the changes 196 Enabling the EIF probe to process change eents in Netcool/OMNIbus Setting change eents expiration in Netcool/OMNIbus Registering the Marker Proider serice in Netcool/Impact Enabling the TBSM Update serice Creating the Object Serer Eent Reader in Netcool/Impact Triggering a change eent in TADDM Viewing the change eent in the Time Window Analyzer Chapter 8. Troubleshooting Getting started with diagnosis Obtaining IBM Software Support Logs i Solutions for BSM Guide:

7 Deployment issues Linux HTTP Serer situations do not work Test Connection button not acting as expected 206 Conflict detected on port Deployment wizard fails to start Deployment of Situation Update Forwarder task failed: missing library Deployment of Situation Update Forwarder task failed: RC Preious deployment status misleading Confusing password erification ITCAM for Transaction Integration Packages task fails ITM Eent Synchronization Forwarder installation error Troubleshooting DLA automation Business Serice Health pages issues The BSM Accelerator serice tree is not populated Business Serice Health pages scroll down in the browser Business Serices panel displays no serice tree 211 Time Window Analyzer panel displays no data 212 Time Window Analyzer shows extra data line 212 Cannot reopen Business Serice Health page 212 Business Serice Status Oer Time chart has last timestamp in X-axis oerwritten Chart titles in Business Serice Health page not displayed correctly Chapter 9. Customizing the solutions 215 Introduction WebSphere MQ Agent scenario Configuring Tioli Monitoring for WebSphere MQ Monitoring Agent Integrating WebSphere MQ resources into the serice model Eent Flow from Tioli Monitoring to TBSM 234 Metric data flow from Tioli Monitoring to TBSM Custom Serice Model scenario Integrating Custom Namespace Resources into the Serice Model Sending Eents Third party monitoring product scenario Without TADDM in the enironment scenario Customizing the scorecard for new technology types Appendix. Accessibility Notices Trademarks Contents

8 i Solutions for BSM Guide:

9 Figures 1. Persona-based iew of a Business Serice 3 2. IT problem determination work flow Problem resolution work flow Business Serice Health page Business Serice Health Details page Business Serice Components scorecard showing application serer details Launch to options for the Business Serice Components scorecard Solutions for BSM Architecture Flow diagram for TADDM and the Time Window Analyzer Adding the configuration files Time Window Analyzer showing the change eents Data flow diagram of WebSphere MQ customization WebSphere MQ workspace Business applications and technology types including MQ_QueueManagers technology type TADDM Grouping Composer TADDM Application Content tab TADDM Application Content tab showing the assigned resources Creating the DirectChildEentStatus dependency rule Creating the Numeric Dependency Rule TBSM Adding properties to the template Configuring the Output Expressions Creating the Dependency rule CRViewer: Business Serice Composer icon Business Serice Composer Project View Input alues for new row Completed new row Configuring the Name, Description, and Formula of a situation Configuring the distribution for the situation Configuring the situation to forward eents to the EIF probe Setting the BSM_Identity fields Configure the Name, Description, Category, and Data Source for the Query Assigning an attribute group to the query Assigning the Origin Node to the query Serice Naigation Data Fetcher Creating a data fetcher Incoming status rule to receie data from the data fetcher Resource matching Simple network topology model BSM_VLAN Template Creating the dependency rule Creating a dependency rule for the BSMAccelerator_NetworkGroup template Setting a maximum dependency rule Dependency worst case rule Input alues for new row Complete new row: my:switch Input alues for new row Complete new row: my:router Newwork technology type Sending eents BSM_Accel_Scorecard Template Tree editor Adding columns for the new technology types Configuring rules to map to columns Update scorecard columns Copyright IBM Corp ii

10 iii Solutions for BSM Guide:

11 About this publication Intended audience The IBM Solutions for Business Serice Management Guide contains instructions on deploying the solution. This publication is for users who are responsible for installing, customizing and monitoring IBM Solutions for Business Serice Management. Copyright IBM Corp ix

12 x Solutions for BSM Guide:

13 Chapter 1. Introduction The IBM Solutions for Business Serice Management integrates products from the Tioli portfolio to delier pre-configured content, isualizations, best practices, and demos for Business Serice Management. The solutions help improe time to alue for customers who want to achiee business serice management. General goals The solution helps achiee these goals: Reduce deployment time for Business Serice Management solutions and applications or logical collections. Reduce customer deelopment / serices expenses by: Building an integration foundation based on industry best practices Reducing the complexity of integration Technical goals The solution has these technical goals: Improe integration between products. Dynamically build business serice models: To aid in quick problem determination and isolation for key business serices. To create a foundation for deliering higher alue, and more customized business dashboards. Create pre-configured dashboards for selected personas such as Information Technology Operators and Subject-Matter-Experts. Deploy industry gathered best practices for monitoring and eent management Drill-down capability Proide integration installer for simplifying integration deployment tasks. Product publications For the latest ersion of this documentation for Solutions for BSM, see: Tioli Business Serice Manager Documentation The ersion 6.1 information center contains the entire TBSM publication set, and also includes the Solutions for BSM documentation. For more information about the products used with the Solutions for BSM, see: Tioli Business Serice Manager Documentation Tioli Business Serice Manager (TBSM) maps incoming data to business serices and creates serice models based on this data. The ersion 6.1 information center contains the entire TBSM publication set, and includes information about new features, general updates, and enhancements. The information center contains topics that help you with basic, as well as adanced tasks. TBSM includes Netcool/Impact and Netcool/OMNIbus. Tioli Business Serice Manager Wiki The Tioli deeloperworks Wiki for TBSM contains arious information Copyright IBM Corp

14 including a Media Gallery, scenarios on installation and integration, and information about best practices, planning, and troubleshooting. Netcool/Impact Documentation TBSM uses Netcool/Impact to parse, filter, and aggregate incoming data. TBSM includes a ersion 6.1 of Netcool/Impact with TBSM-specific customizations. Netcool/OMNIbus Documentation TBSM monitors the Tioli Netcool/OMNIbus ObjectSerer for incoming eents. The ObjectSerer collects eents from probes, monitors, and other applications such as IBM Tioli Monitoring. You use TBSM to create serice models that respond to the data receied in the incoming eents. TBSM includes ersion of Netcool/OMNIbus with TBSM-specific customizations. The Netcool/OMNIbus Web GUI is also included. Tioli Application Dependency Discoery Manager Solutions for BSM uses the Tioli Application Dependency Discoery Manager to help discoer and manage business serices. The publications include instructions for installing, configuring, and completing all of the major tasks with the product Tioli Monitoring The Solutions for BSM uses the Tioli Monitoring ersion 6 release 2.3 and Fix pack 1 to deploy and manage the Tioli Monitoring product suite. These products and components monitor and collect resource data for the Solutions for BSM. Tioli Composite Application Manager for Transactions IBM Tioli Composite Application Manager for Transactions (ITCAM for Transactions) integrates with the Tioli Enterprise Portal in IBM Tioli Monitoring enabling you to manage your entire enterprise with a single user interface. This includes Web Serer Deployment and Monitoring, which helps deploy and manage the Web Serer application infrastructure. Additional tasks include installing and configuring the Web Response Time and OS agents. Tioli Composite Application Manager for Applications Responsible for the deployment and management of ITCAM for Applications which coers WebSphere, HTTP Serers, and DB2. TBSM Media Gallery The Media Gallery contains ideos, tutorials, education modules, and demos on subjects such as tasks and integration. Persona-based iews of Business Serice Management The IBM Solutions for Business Serice Management addresses two broad iews of Business Serice Management: business unit groups who proide serices to customers and information technology (IT) operations group who support the business units. For this release, the Solution coers the IT Operations work flow. The business unit group supports the deelopment, marketing, and sales, of a specified serice or product. The IT operations group supports the underlying infrastructure required for the business serices. 2 Solutions for BSM Guide:

15 Figure 1. Persona-based iew of a Business Serice The key roles for the business unit group are: Line of business (LOB) owner This role focuses on marketing and business, not on IT. The line of business owner depends on the IT serices to get the work of the business done. The line of business owner needs to know how things are running and if there are any problems that affect the serices. Application owner This role is responsible for keeping an important business application up and running so the company can make money. IT operations The IT Operations personnel work to manage end-to-end business serices and applications by haing isibility into key technology enabling serice and application deliery. They desire to quickly understand the impact incidents hae upon business serices and applications by interpreting the context proided by the Solutions for BSM and taking appropriate actions based upon this knowledge. Chapter 1. Introduction 3

16 Figure 2. IT problem determination work flow The key roles for the IT operations group are: IT operations manager Leads a group that works to classify, inestigate, and resole incidents that affect the business serice infrastructure Serice Desk Analyst Proides initial customer support This role creates, classifies, and assigns incidents based on end-user calls. Leel 1 (L1) Operator Inestigates highest priority incidents and resoles known incident types. Assigns unresoled incidents to Leel 2 operator. Leel 2 (L2) Operator Inestigates unresoled incidents and identifies the root cause. Isolates the domain in which the problem occurred. Subject matter expert (SME) Inestigates and resoles a domain-specific problem. Validates the resolution. Problem resolution work flow This diagram shows how the Solutions for BSM dashboards help IT operations users detect, analyze, and resole a problem. 4 Solutions for BSM Guide:

17 Figure 3. Problem resolution work flow Dashboard oeriew In this case, the VIP client reports that sell trades take too long to complete. The business unit owner sees a problem on Application Health dashboard and reports it to IT operations, who isolate, diagnose, and resole a irtualization storage problem. The Application Health and other Business application dashboards are not aailable for this release. The IBM Solutions for Business Serice Management employs a series of dashboards to support IT operations roles. Business Application Dashboards The business unit roles, such as the application owner use the Business application dashboards to show the status of serices at a high leel. These dashboards are not aailable for this release. The business unit group supports the deelopment, marketing, and sales, of a serice or product. The application owner is responsible for keeping an important business application up and running so the company can make money. IT operations The IT operations personnel work to classify, inestigate, and resole incidents that affect the business serice infrastructure. The Solutions for BSM gies this group easy access to the information they need to handle serice-affecting incidents. Chapter 1. Introduction 5

18 Figure 4. Business Serice Health page The Business Serice Health page contains the Business Serices scorecard, charts, and an Actie Eent List (AEL). Business Serices scorecard The columns in the scorecard represent the health of different technology components that support the business serices. Each row represents a top-leel Serice, Application, or Collection class instance. For each column, the status reflects the worst seerity of eents that are currently directly affecting the resources such as clients, transactions, and web serers. If you right-click on a serice here, you can open a Business Serice Health Details page for that serice. Business Serice Status Oer Time chart The Business Serice Status Oer Time chart at the upper right of the page proides a 12-hour historical window of the oerall status of the serice. The time period displayed shows the preious 12 hours before the current time. The time period is diided into 15-minute interals. If other business serices are monitored, the contents of the chart would change when you click the business serice. Business Serice Eent Count Oer Time chart The Business Serice Eent Count Oer Time chart shows the eent count for a gien serice or application oer time. Like the preious chart, this chart also displays the data for the business serice clicked. When you mouse oer a data point on the chart it tells you how many eents were there at the time. 6 Solutions for BSM Guide:

19 Actie Eent List The eent list at the bottom of the page shows all eents affecting all components of the selected business serice or application. The Serice column indicates which business serice is being affected by the eent. The Function column shows which technology component is affected by the eent. The Transaction column displays the name of the transaction if the eent is reporting on the status of a transaction. The Client column displays the name of the client (or client group) if the eent is reporting on the status of an ITCAM for Transactions client. You can click the Function column to sort the eent list by the technology component. This column proides a quick way of assessing the types and quantity of eents affecting the different technology components. (By default, the eent list is sorted by timestamp, such that the most recent eents are on top). Business Serice Health Details page This page shows more detail for a serice. When you right click the business application serice row in the scorecard the menu contains the option to display the Business Serice Health Details page. The Business Serice Health Details page consists of three portlets. There is a scorecard which allows you to drill down into the technology components affecting the business serices. The Time Window Analyzer portlet shows the Oerall status oer time of the business serice at the top of the scorecard. At the bottom, there is an actie eent list which shows the eents that affect the serice clicked. Chapter 1. Introduction 7

20 Figure 5. Business Serice Health Details page Business Serices Components scorecard The scorecard lists the number of eents where the Seerity is greater than or equal to Warning for each type of technology resource. You can expand the business application serice tree on the details page to show the eent count and status for the underlying resources which contribute to the oerall status of the application. In following figure, you can see the serer resources with statuses of marginal and critical that are affecting the application. You can also customize this score card. Figure 6. Business Serice Components scorecard showing application serer details 8 Solutions for BSM Guide:

21 When you right-click on a serice, you can launch to a component dashboard such as the Tioli Enterprise Portal. Actie Eent List The Actie Eent List shows the eents affecting the serice you click in the scorecard. If you click one of the child serices, the Eent List shows only eents for that serice and any of its children. For example, if you click the quotes serice, the Eent List shows the eents that affect the quotes serice. When you double-click an eent, you see details for the eent. Time Window Analyzer The Time Window Analyzer portlet shows the oerall status oer time of the business serice application at the top leel of the scorecard. The context of this chart does not change when you click a child serice. You can add other serices, for example child serices to the Time Window Analyzer, as well as display other metrics for that serice. The Status Change metric is shown by default. Component dashboards When you right-click on a serice in the Business Serice Components scorecard, you can launch to another application such as the Tioli Enterprise Portal. Figure 7. Launch to options for the Business Serice Components scorecard Architectural oeriew The IBM Solutions for Business Serice Management is an example of how you can integrate seeral products to support business serices. The data from these discoery and monitoring products is used to build a hierarchy of serices that represent your information technology (IT) and business operations. The resulting TBSM serice model and dashboards help you track the status of your business operations and the information technology (IT) resources that affect your business operations. Chapter 1. Introduction 9

22 The Solutions for BSM gathers data from seeral products that monitor key technology types. The information is collected, processed, and organized into technology components that support a business application represented as a serice within TBSM. Table 1. Data sources for technology components Data source Technology components Description Tioli Monitoring Agents for Operating Systems ITCAM for Applications ITCAM for Transactions Tioli Monitoring for Virtual Enironments Serers Application Serers Web Serers Databases Client Transactions Transactions Virtualization Enironments Base Monitoring, Situations, and Status for serer hosts. Discoery and monitoring of serices based on application serers, clients, web serers, and databases. Discoery and monitoring of serices based on transactions Base monitoring, situations, and status for irtual serer hosts This diagram shows the relationships between the Tioli products within the Solutions for BSM architecture. Two primary processes support the serice model and dashboards: Discoery of resources and the creation of a serice model based on the discoered resources Monitoring of the serice model based on real-time status and key performance indicators 10 Solutions for BSM Guide:

23 Figure 8. Solutions for BSM Architecture Discoery process The Solutions for BSM includes Discoery Library adapter templates for additional agents that help automate the discoery process flow. The discoered IT resource data is used to create a TBSM serice model. The left side of the diagram illustrates the discoery process. 1. The baseline monitoring application, such as ITCAM for Applications uses its Discoery Library adapter (DLA) to create an Identity Markup Language (IdML) book file. IdML books, also known as Discoery Library books, are XML files containing details about resources and resource relationships written to conform to the IdML schema. Each IdML book represents the distinct iew of the resources and relationships at a point in time. 2. The IBM Tioli Application Dependency Discoery Manager (TADDM) reads the data in the IdML books, normalizes the data, and creates resource dependencies. The resource and relationship data can then be loaded/imported into TBSM. 3. TBSM uses the Discoery Library Toolkit to create a hierarchical serice model based on the data from the TADDM. TBSM organizes the resources into technology components, using serice templates to establish dependencies between the new serices. Each serice has a unique BSM_Identity alue. This alue is used to correlate incoming eents with the discoered serices. 4. Operational dashboards show information about the discoered serice model in score cards, charts, and actie eent lists. The score cards help you monitor status, business impact, and key performance indicators. You can also perform root cause analysis from the dashboards. Chapter 1. Introduction 11

24 Eent management and status monitoring The Solutions for BSM helps configure eent customization for the products that manage the incoming eents. These eents affect the status of the discoered serices in the TBSM serice model. The eents include the BSM_Identity field, which is used to correlate eents with discoered serices. The eents contain information about status, business impact, and key performance indicators that affect the serices. The right side of the diagram illustrates the eent management process. 1. The baseline monitoring application, such as ITCAM for Transactions collect and consolidate data on key performance indicators from systems, applications, middleware, and transactions. When the monitoring application detects an alert condition, it creates a situation eent that is forwarded to the Tioli Eent Integration Facility probe (EIF probe). 2. The EIF probe conerts the situation eents to Netcool/OMNIbus eents and inserts the eents into the Netcool/OMNIbus ObjectSerer. 3. Netcool/OMNIbus collects and consolidates the eents and TBSM and Netcool/Impact read the eents from Netcool/OMNIbus. 4. Netcool/Impact enriches the eents with business context and other additional data when needed. 5. TBSM collects the eents and uses the BSM_Identity field alue to correlate the incoming eents with the discoered serices. TBSM also sends serice-status eents back to Netcool/OMNIbus. 6. Operational dashboards show information from the eents in score cards, charts, and actie eent lists. The dashboards help you monitor status, business impact, and key performance indicators. You can also perform root cause analysis from the dashboards. 12 Solutions for BSM Guide:

25 Chapter 2. Deploying the Solutions for BSM These topics describe how to deploy the IBM Solutions for Business Serice Management to the Tioli stack of products. The deployment is a group of enhancements, configuration elements, and integrations. Before you begin Before you begin, reiew the product and user requirements. Product requirements Reiew the Product requirements to ensure that you hae the required Tioli products and ersions of these products. Deployment user You need to be logged on as a user on the local machine that runs the Deployment Wizard. You specify the destination accounts on the destination machines as part of the deployment process. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Backup products before you deploy. It is good practice to back up the Tioli products before you deploy the Solutions for BSM. Either use your local back up procedures or the procedures described in the product publications. For links to all the product publications, see Chapter 1, Introduction, on page 1 Netcool/OMNIBus backups: Make a backup of the ObjectSerer configuration, before you deploy the Solutions for BSM. Otherwise, you cannot remoe all the Solutions for BSM modifications to the ObjectSerer. For more information, see the Importing, and exporting ObjectSerer configurations section in the Netcool/OMNIbus information center: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/welcome.htm. About this task To deploy the Solutions for BSM follow these high-leel steps. 1. Run the Deployment Wizard. 2. The Select Tasks page lets you select the main task groups for the deployment. The steps are presented in the ideal order, please follow this sequence from top to bottom. Other deployment sequences hae not been erified. Each task group lets you select from a set of subordinate tasks and guides you through the tasks, where you specify your target hosts, user information, and other deployment data. When you complete a main task group, click Select Tasks to return to the main task page. Copyright IBM Corp

26 3. Complete the task groups in this sequence: Deploy Best Practice Monitoring Deploys situations to your IBM Tioli Monitoring serers. Deploy Best Practice ITCAM Monitoring Deploys the integration and configuration elements for IBM Tioli Composite Application Manager for Transactions and ITCAM for Applications Automate Discoery ITM/ITCAM to TADDM Deploys the Discoery Library Adapter (DLA) automation package configuration elements to: Tioli Monitoring and ITCAM hosts. IBM Tioli Application Dependency Discoery Manager (TADDM). Deploy Eent Manager Customizations Deploys eent management configuration and integration elements to Tioli Monitoring IBM Tioli Netcool/OMNIbus Tioli Eent Integration Facility probe (EIF probe). Deploy TBSM Customizations Deploys configuration and integration elements to: IBM Tioli Business Serice Manager Data serer TBSM Dashboard serer Netcool/OMNIbus Web GUI Set up Single Sign-On Deploy Single Sign-on configuration for launching in context between TBSM, TADDM, and Tioli Monitoring (Tioli Enterprise Portal). If you configure Single Sign-On, user will not need to enter credentials when they launch from one application to another. 4. Post-installation configuration. Saing your progress If at any time, you want to sae your work in the Deployment Wizard, use the Sae as option, since the default file name is read-only. 1. From the File menu, select Sae as. 2. Enter the file name you want, such as mydeployment.ser and click Sae.. 3. The next time you start the Deployment Wizard, select Open from the File menu. 4. Select the file you saed and click Open. Getting help To get help on the Deployment Wizard, click the Help button. Logs The logs are copied to /tmp/solutionforbsm_user name/task group name on the target computer that was specified in the Specify Target Computer panel. Where: user name is the name specified in the target computer panel not the user who is running the deployment (if they are different). task group name is the name of the main task group. 14 Solutions for BSM Guide:

27 Product requirements The logs are also oerwritten by each task for eery run. You will only see the last run logs. As a best practice, make a back up copy of the log before you run the deployment wizard again. There are two types of logs: solution components logs These logs are created on the target machine you specify for a component in the deployment wizard. These logs are in corresponding subdirectories of the logs directory for the component. For example, if you are installing as user tbsm, the log for the Deploy Best Practice Monitoring task is in the /tmp/solutionforbsm_tbsm/enable_best_practice subdirectory on the target machine you specified in the Deploy Best Practice Monitoring task. master log file The IRU_DeploymentWizard.log file is created at the beginning of the installation and copied to the logs directory at the end of the installation. Important: The master log file is copied to the directory on the machine where you run the deployment wizard. The master log gets oerwritten each time the deployment wizard is run. As a best practice, make a back up copy of the log before you run the deployment wizard again. The subsequent topics describe the options for each of the task groups. This topic lists the specific product requirements for the IBM Solutions for Business Serice Management, including operating system, ersion, release, and fix pack information. The Solutions for BSM are pre-configured to use and modify these products to support TBSM isualizations. If any product is going to be modified by the Solutions for BSM, you need the ersion and fix pack leels described below. Not all products listed below are necessarily required to exist in the enironment in order to get alue from the Solution. Howeer, to fully utilize the Solutions for BSM functionally, you should install and configure the following products. You will be prompted during deployment for the product configuration information. To get full alue of Solution for BSM, use these products at the ersion leels listed in this table. If you do not hae all these products you will get less alue from solution. If you want to use a third-party application to replace one of these products, see the Customizing the Solution topics in the Solutions for BSM documentation included with the Tioli Business Serice Manager Documentation. Product ersions and component ersions are the same unless otherwise noted. All products must run on Redhat Enterprise Linux bit or 64 bit. Chapter 2. Deploying the Solutions for BSM 15

28 Table 2. Tioli products supported for IBM Solutions for BSM Product Version Description IBM Tioli Monitoring with the components: Tioli Enterprise Management Serer Tioli Enterprise Portal Serer Warehouse agents (Summarization and Pruning, Warehouse Proxy) Agents for Operating Systems Tioli Monitoring for Virtual Enironments 6 release 2.3 Fix Pack 1 Base Monitoring, Situations, and Status 7 release 1 Base Monitoring, Situations, and Status VMWare Agent 7.1 interim fix 1 IBM Tioli Composite Application Manager (ITCAM) for Transactions with the components: Application Management Console Agent for Web Response Time Agent for Robotic Response Time Agent for Transaction Tracking Transaction Tracking Collector Agent for Transaction Tracking Collector Requires the ITCAM Integration package DLA component deployed to the target machine to enable ITCAM for Response Time DLA automation. This component is included in the Deployment Wizard. ITCAM for Applications Agent for DB2 ersion 6 release Agent for WebSphere Application Serer ersion 7 release Agent for HTTP Serer ersion 7 release An LDAP serer such as Tioli Directory Serer 7 release 3 Discoery and monitoring of serices based on transactions 6 release 2.4 Discoery and monitoring of serices based on applications User authentication across products and support for Single Sign-On. 16 Solutions for BSM Guide:

29 Table 2. Tioli products supported for IBM Solutions for BSM (continued) Product Version Description Tioli Business Serice Manager (TBSM) with the components: Netcool/OMNIbus Apply Fix Pack 3 after installation After you apply the fix pack, complete the steps in APAR IV Tioli Eent Integration Facility probe (EIF probe) Data Serer Dashboard Serer Discoery Library Toolkit configured to discoer resources from TADDM (if you want to use TADDM as part of your deployment) Tioli Application Dependency Discoery Manager (TADDM) ITCAM for Application Diagnostics with the components: Managing Serer 7.1 Agent for WebSphere Application Serer ersion 7 release (also included in ITCAM for Applications 6.2.4) Agent for HTTP Serer ersion 7 release (also included in ITCAM for Applications 6.2.4) Extended Agent for Oracle Database Agent for MS SQL IBM Optim Performance Manager Optim Performance Manager Serer Optim Extended Insight Client 6 release 1 interim fix 1 or higher Netcool/OMNIbus APAR IV10457: support/ dociew.wss?crawler=1 &uid=swg1iv10457 Serice model creation, modeling, and isualization. 7 release 2.1 Fix Pack 1 Helps to discoer resources and their relationships in the enironment. 7 release release 1 Red Hat Linux library requirements The host where you run the Deployment Wizard and the target systems must be running the Red Hat Enterprise Linux ersion 5 operating system. The Solutions for BSM deployment requires the following libraries on Red Hat Linux systems: Both 32- and 64 -bit systems. Chapter 2. Deploying the Solutions for BSM 17

30 ibxmu.i386 libxp.i386 For 64-bit systems libxmu.x86_64 libxp.x86_64 Netcool/OMNIbus considerations Install the Netcool/OMNIbus included with TBSM 6.1. Apply fix pack 3 for Netcool/OMNIbus and Complete the steps described in APAR IV10457 here: If you are planning to install the Situation Forwarder task under Eent Manager Customization, you need to install the following 32-bit libraries on your Netcool/OMNIbus host: libxp.so.6 libxmu.so.6 Running the Deployment Wizard This topic describes how to run the IBM Solutions for Business Serice Management deployment wizard. Before you begin Before you begin, obtain a copy of the deployment image from the Integrated Serice Management Library here: Search for Solutions for Business Serice Management or Solutions for BSM. System credential considerations: When you enter credentials (user ID/password) for the target machine where you want to configure a Tioli product for integration, use the same user ID that was used to install the Tioli product. If the target machine is the local machine where you want to configure a Tioli product for integration: 1. Log in as the user ID that was used to install Tioli product 2. Start the Deployment Wizard. Secure Shell (SSH) limitations: For deployments to remote target machines, the deployment wizard utilizes Secure Shell (SSH) to transfer data to the target machine. This requires that the default SSH port (22) be open and accepting connections on the target machine. The deployment wizard cannot use any other SSH port for remote deployments. 18 Solutions for BSM Guide:

31 If you cannot use the default SSH port, run the deployment wizard locally on the target machine. If the target machine does not hae a console, export the DISPLAY to an X serer. Setup files location: Setup files must be copied to a temporary location on the target computer. The default is to use the system-specific temporary location. If you want to use another location, or if there is insufficient space aailable in the system-specific temporary location, you can specify a location where setup files are copied. Select the option that you want to use. The deployment wizard allows you to determine the amount of space that is aailable on the target computer: 1. From the deployment wizard menu select Edit > Preferences. 2. In the Deployment Preferences window, click Target Computer Settings button. 3. Clicking the Check Disk Space button in the Target Computer Settings window will show the amount of disk space remaining on the target setup file location in units of megabytes. Note: If you encounter an issue using the launchpad, you may need to set an enironment ariable BROWSER to a specific location of your web browser. Here is an example using Firefox In the command window locate the Firefox executable: /usr/lib/firefox-3.6/firefox 2. Set the ariable BROWSER - export BROWSER=/usr/lib/firefox-3.6/firefox 3. Start the launchpad:./launchpad.sh Procedure 1. Unpack the accelerator_1.1_install.tar file to a directory on your local host. 2. Start the launchpad with the command:./launchpad.sh 3. Click Deploy IBM Solutions for Business Serice Management. 4. From the panel that opens, click: Run the install program of IBM Solutions for Business Serice Management Installation (it may take a few minutes to load the Deployment Wizard). 5. Click Accept on the Software License Agreement window. 6. Click Next and the Select Tasks window opens. 7. Run the tasks from top to bottom, starting with Deploy Best Practice Monitoring and ending with Deploy Single Sign-On. It may be possible to run the tasks in a different sequence, but these scenarios hae not been erified. Note: Steps that inole Tioli products that are not part of your enironment may be skipped. It is not necessary to set up Single Sign-On. Single Sign-On allows you to launch in context between applications without haing to enter login details for each application. 8. When you choose a task, the naigation frame shows your progress for each main task. The steps for each task are: Chapter 2. Deploying the Solutions for BSM 19

32 Select Tasks Select the main task you want to complete from this panel. Each main task contains multiple subordinate tasks. Specify Targets Specify the host where you want to deploy the objects for the task. You are prompted for a different host for each deployment task. Configure Parameters Specify the unique parameters for each main task. These parameters include directories, database information, and the hosts for supporting applications such as the Tioli Enterprise Monitoring Serer. Summary Shows the summary of the deployment tasks you configured and a time estimate for each task. You can choose to deploy the tasks indiidually or deploy all the tasks with one click. Note: The actual deployment times may ary from the estimates depending on whether the deployment is to a remote target machine or to the local machine (same machine as where installer is running), network latency, target machine specifications, and so on. Launchpad options The IBM Solutions for Business Serice Management Launchpad is a graphical user interface (GUI) for the deployment tasks. You use the Launchpad to run the Deployment Wizard and access information about the Solutions for BSM. The launchpad proides a single mechanism for deploying the Solutions for BSM. From the launchpad, you can launch the following: Welcome Welcomes you with a brief oeriew. Release Information Opens link to the Release Notes. Systems Requirements and Prerequisites Product requirements and other prerequisite information. IBM Solutions for Business Serice Management Online Documents and Wiki Information about and links to the Online Documents and Wiki. Deploy IBM Solutions for Business Serice Management Start the Deployment Wizard. Exit Exit the Launchpad. Deploy Best Practice Monitoring This deployer automatically configures your IBM Tioli Monitoring infrastructure with best practice situations for Business Serice Management. Tioli Monitoring is configured such that the situations are created, and they are set to automatic start. Howeer, the situations are not distributed to the target agents. You must distribute the situations to the target agents after you complete these deployment tasks. 20 Solutions for BSM Guide:

33 Before you begin The naigation frame shows the task: Select Tasks Deploy Best Practice Monitoring Before you deploy the situations, know your Tioli Enterprise Monitoring Serer and Tioli Enterprise Portal host and user information. About this task These situation groups work with specific agents. If the supporting agent is not installed, the situations eents for that agent cannot be created and forwarded to TBSM. To deploy the situations. Procedure 1. Select Deploy Best Practice Monitoring from the Select Tasks page. 2. Click Next. 3. The Deployment wizard guides you through these high-leel steps: Situation types and queries For each agent, there is a set of situations you can deploy. Select the situations you want. Also specify whether you want to deploy the Time Window Analyzer queries on your IBM Tioli Monitoring serers. These queries are required for the Time Window Analyzer portlet on the Business Serice Health Details page. Specify target computer for deployment Specify the target computer where you want to deploy the situations. The target must be the computer where Tioli Enterprise Portal Serer is installed. Serer, situation, and query information For each set of situations, you specify information for your Tioli Monitoring serer and you select the situations and queries you want to deploy. In most cases, select All. In the Adanced tab, you can also choose whether you want: Skip predeployment check Oerwrite existing situations The default for each option is No. 4. For more details about deploying situations, see the subsequent topics. Situation types and queries Specify the agent situations and whether you want to install the Time Window Analyzer queries on your IBM Tioli Monitoring serers. Purpose The baseline monitoring application, such as Operating System Agents collect and consolidate data on key performance indicators from systems, applications, Chapter 2. Deploying the Solutions for BSM 21

34 middleware, and transactions. When the monitoring application detects an alert condition, it creates a situation eent that is forwarded to TBSM as a Netcool/OMNIbus eent. TBSM matches the eent to a serice instance, and the serice data is updated and displayed on the dashboard. The naigation frame shows the task: Select Tasks Deploy Best Practice Monitoring Choices If you want to collect and isualize data from an agent, deploy situations for the agent on this page. If you do not select an agent type, the Solutions for BSM does not collect or isualize data from that agent. All tasks are grouped to use one target host You can choose from the following options: ITM Operating System Agent Situations Deploy the set of situations for the Tioli Monitoring Operating System Agents. These situations are intended to implement effectie operating system monitoring for most enironments. Situations are proided for the following agents: Monitoring Agent for UNIX OS Monitoring Agent for UNIX Logs Premium Monitoring Agent for AIX Monitoring Agent for Linux OS Monitoring Agent for Windows OS ITM Database Agents (Microsoft SQL Serer, Oracle Serer) Situations Deploy the set of situations for the database agents for Microsoft SQL Serer and Oracle. ITM (WAS, HTTP Serer, Uniersal) Agent Situations Deploy the set of situations for ITCAM for Applications. These situations include the HTTP Serer, WebSphere, and Uniersal Agents. ITM VMWare Situations Deploy the set of situations for Tioli Monitoring for Virtual Enironments. ITM Custom Queries for TWA Metrics Deploy the set of metric queries to Tioli Monitoring. These queries are the data sources for metrics displayed on the Time Window Analyzer portlet on the Business Serice Health Details page. Specifying target computer for situations Specify the target computer where you want to deploy the situations. Before you begin The naigation frame shows the task: Specify Targets Best Practice Monitoring 22 Solutions for BSM Guide:

35 Before you deploy the situations, know your Tioli Enterprise Portal Serer host name and credentials. The user account needs permission to create situations. About this task The target computer must be your Tioli Enterprise Portal Serer. The user ID must be for the user who originally installed IBM Tioli Monitoring. Note: You can specify multiple target computers. If so, the configuration such as hostname, username, passwords, directories must be identical in all computers To deploy the situations. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Situation and query configuration For each set of situations, you specify information for your IBM Tioli Monitoring serer and the situations you want to deploy. You also specify the Time Window Analyzer queries you want to deploy. Chapter 2. Deploying the Solutions for BSM 23

36 Purpose For each set of situations, you specify information for your Tioli Enterprise Monitoring Serer and Tioli Enterprise Portal. You also choose the situations you want to install. In most case, choose All situations. The naigation frame shows the task: Configure ITM Operating Systems Agent Situations ITM Databases Microsoft SQL Serer, Oracle (Oracle Serer) Agent Situations ITM (WAS, HTTP Serer, Uniersal) Agent Situations ITM VMWare Agent Situations ITM Custom Queries for TWA Metrics Parameters If you want to collect and isualize data from an agent, deploy situations for that agent from this page. If you do not deploy a situation or group of situations, the Solutions for BSM does not collect or isualize data from that situation or situation group. All tasks are grouped to use one target host. The parameters you enter in the first configuration panel are pre-filled in the next panels because all the tasks are expected to be deployed to the same Tioli Enterprise Portal Serer host Specify these parameters: Hub TEMS host name The fully qualified host name or IP address for your Tioli Enterprise Monitoring Serer Hub. Username for TEMS The user account with permission to create situations on your Tioli Enterprise Monitoring Serer. Password for TEMS Password for the user account. Verify Password Enter the password again. ITM Home Directory on TEPS Home directory for the Tioli Enterprise Portal serer. Default: /opt/ibm/itm Choose situations/queries to import (All, None, Some) In most cases, select All to deploy all situations. Select None to deploy no situations Select Some if you want to only deploy some situations. Scroll down to see your choices. For detailed instructions, see Selecting subsets of situations and queries. 24 Solutions for BSM Guide:

37 Selecting subsets of situations and queries If you do not want to deploy all the situations or queries, complete this task. If you deploy all situations and queries, you can skip this task. Before you begin The naigation frame shows the tasks: Configure ITM Operating Systems Agent Situations ITM Databases Microsoft SQL Serer, Oracle (Oracle Serer) Agent Situations ITM (WAS, HTTP Serer, Uniersal) Agent Situations ITM VMWare Agent Situations ITM Custom Queries for TWA Metrics On the Configure Parameters panel where you specify the Tioli Enterprise Monitoring Serer and Tioli Enterprise Portal information, you can choose to deploy a subset of situations or queries. About this task To deploy a subset of queries or situations. Procedure 1. Select Some from the Choose situations to import (All, None, Some) or Choose queries to import (All, None, Some) drop-down list. The panel expands to display the new options. Use the scroll bar to moe down the panel. For the queries, select the queries you want to import by clicking Yes or No for each query type and click Next to continue. For situations, see the remaining steps. 2. For each group of situations, there is a drop-down list where you can choose to import All, None, or Some of the items. The list of situations in the group you selected displays below the drop-down list. For example, for the operating system agent situations, there is a group of situations for each operating system. 3. Click None for each situation group you do not want to deploy. 4. For each situation group, choose All, None, or Some from the drop-down list and select No for the situations you do not want to deploy. 5. If you want to distribute the situations to a managed list, enter the list name in the Managed List field for each group. If the managed list does not already exist, then it will still distribute the situation(s) to the managed list, howeer no systems will be distributed with the situation. Howeer, once you create the managed list, then the situation will become distributed with the systems added to the managed list. Summary for situation deployment After you hae specified information for your IBM Tioli Monitoring serer, the situations, and queries you want to deploy, the Summary panel lets you choose how to run the deployment. Chapter 2. Deploying the Solutions for BSM 25

38 Purpose You can run the deployment for each set of situations and the queries one at a time, or you can run them all at once. The naigation frame shows the tasks: Summary To run a task by itself, click Deploy Task for the task you want to run. To deploy all the tasks in the summary, click Deploy all. Next steps When you complete these tasks, the situations get created and set to auto-start, but they do not hae a distribution target. You must distribute the situations using the IBM Tioli Monitoring Situation editor. For information about distributing situations, see the Tioli Monitoring Information Center for ersion Fix Pack 1 at: Tioli+Monitoring Click Version Fix Pack 1 and naigate to: In the Naigation frame, click + for IBM Tioli Monitoring. Click + for Version Fix Pack 1 and select the topics: User's Guides > Tioli Enterprise Portal User's Guide > Situations for eent monitoring > Creating the situation > Distributing the situation Deploy Best Practice ITCAM Monitoring 26 Solutions for BSM Guide: Deploys the integration package, and Discoery Library Adaptors (DLAs) for IBM Tioli Business Serice Manager, IBM Tioli Composite Application Manager for Transactions, and IBM Tioli Composite Application Manager for Applications. Before you begin Important: Configure the application management console (AMC) to filter data discoered by the Web Response Time (WRT) and Transaction Tracking (TT) agents. This manual procedure is included as a topic in this section. The naigation frame shows the task: Select Tasks Deploy Best Practice ITCAM Monitoring Before you deploy the ITCAM components you need: Host and user information for the TBSM Data serer Host and user information for the IBM Tioli Monitoring serer used by ITCAM for Transactions and ITCAM for Applications.

39 Tioli Monitoring data warehouse credentials. The name of the Application Management Console Agent name. The user needs write permission to the Tioli common logging directory, for example write permission to /ar/ibm/tioli/common. About this task Discoery Library Adapters (DLAs) are packages that export XML data known as IDML books from Tioli products or components. This deployer automatically creates two DLA packages for Transaction Tracking and Applications and also automatically generates an instance of their corresponding IDML books. The IDML books created by these DLA packages are required by the subsequent "Deploying Automated Discoery" deployer. This deployer also creates a set of related artifacts known as the TBSM integration package which includes some recommended configurations for ITCAM in this context (such as eent identifier tree templates, template mappings, and TADDM class filters). To deploy the ITCAM monitoring components. Procedure 1. Click Deploy Best Practice ITCAM monitoring. 2. Click Next. 3. The Deployment wizard guides you through these high-leel steps: ITCAM for Transactions Integration Packages This option deploys the integration packages for the TBSM Data serer and DLA. The TBSM package creates objects such as data sources, serice templates, and charts. The DLA package is a Jaa program that can run from any host that can connect to the Tioli Monitoring Data Warehouse. The DLA creates an Identity Markup Language (IdML) book file. This package includes files required for the ITCAM for Response Time DLA automation and must be deployed to the target machine before you deploy this DLA automation. The package ersion included in the Deployment Wizard is ersion 7 release ( ). Check for updated ersions at the Integrated Serice Management Library here: details?catalog.label=1tw10cp2b DLA for ITCAM TT This option deploys the DLA package for the ITCAM for Transactions. This package consists of the itcamttdla.jar file which is used to generate an IdML book file from transaction data. The target host requires the ITCAM for Transactions Tracking Component. It is best practice to install this DLA on the Tioli Enterprise Monitoring Serer host. This task installs a customized ersion of itcamfttdla.jar file. By default, the task does not oerwrite the existing JAR file. If you want to oerwrite the existing JAR file, go to the Adanced tab in the configuration panel and select to Oerwrite existing package. The task will make a copy of the existing JAR file, in the same directory where it resides, and names it itcamfttdla_bsma_backup_date.jar. Chapter 2. Deploying the Solutions for BSM 27

40 ITM WAS and HTTP Serer DLA Templates This option deploys the ITCAM for Applications Websphere Application Serer and HTTP serer agent DLAs on the Tioli Enterprise Monitoring Serer host. This option generates the DLA templates that are used by Tioli Monitoring to produce IdML files. The task installs kht_tmsdla.[jar xml] and kyn_tmsdla.[jar xml]. By default, they will not be oerwritten. If the files exist, you must choose to "oerwrite exiting DLAs". The files are not backed up. 4. For each task you specify the target computer and configuration information. Specify target computer for deployment Specify the target computer where you want to deploy the integration packages and DLAs. Configuration For each option, you specify directories, credentials, and database information. 5. For more details about deploying ITCAM Monitoring components, see the subsequent topics. Configuring the ITCAM Application Management Configuration Editor You must complete this manual configuration task before you start to deploy the Best Practice ITCAM Monitoring components. Before you begin An application consists of a set of transactions that are performed, the serers that the transactions use, and the clients that initiate the transactions. The discoery library adapters (DLAs) created by the IBM Tioli Composite Application Manager for Transactions agents export the data that is displayed in the workspace and which can then be displayed in TBSM dashboards. This topic outlines how to configure the Application Management Configuration Editor to filter data discoered by the Web Response Time and Transaction Tracking agents. To ensure that you configure the Application Management Configuration Editor to filter data appropriately, you must hae a technical understanding of your web application. You must be able to identify the important web application transactions and be able to distinguish them from other transactions. About this task The steps that must be performed in the Application Management Configuration Editor to define an application are: Procedure 1. Identify and define the application that you want to monitor. 2. Identify and define the transaction filtering for each transaction in the application that you want to monitor. 3. Identify and define the client filtering for each client group that connects to the application. 4. Customize the serer components to match the application enironment. 28 Solutions for BSM Guide:

41 Example To illustrate the procedure required to complete these steps, the DayTrader web application is used in the procedure outlined. We want to create a DayTrader application that consists of all of our Daytrader transactions, in other words login, buy, sell, logoff, and so on. We must also define the serers required, webserers, WebSphere serers, and database serers. Finally, we must define the clients that use the application, Austin clients, Raleigh clients, VIP clients, and so on. Creating a new monitored application 1. To open the Application Management Configuration Editor, click the Application Management Configuration Editor icon in the Tioli Enterprise Portal. 2. Click the Create New Application toolbar button. In resultant dialog box, type the name DayTrader and click OK. Creating transactions 1. Under this application, create a set of Web Response Time transactions. To create a transaction, right-click the DayTrader application node in the Applications tree and click Create New Transaction. For each of the transactions listed, choose Web Response Time from the Agent type list. Create and name each Web Response Time transaction as listed: All other This is a general transaction. If the transaction does not meet the filtering requirements of the other defined transactions, it is added to this list. All DayTrader GET transactions Any transaction using the HTTP.GET:action method, is added to this transaction category. All DayTrader POST transactions Any transaction using the HTTP.POST:action method, is added to this transaction category. login User log in attempts are stored in this transaction category. register User registration attempts are stored in this transaction category. Note: A transaction can match multiple filters. 2. For all transactions: Because the DayTrader web application is contained in the URL of all of the web serer transactions, add a filter to reflect this: a. Click to select the transaction, and click the Filter tab. b. Click Add. The Filter dialog box is displayed. c. Choose URL from the Name list. d. Type *daytrader* in the Value field and select Include from the Type list. 3. Create a login transaction filter: All user IDs are recorded for all HTTP.POST:uid methods. Therefore, in addition to the URL filter, add a filter with the name HTTP.POST:uid and with the alue * to the login transaction. To set the alue for the name, select HTTP.POST:XXX from the Name list and edit this name so that it has the appropriate alue. 4. Create a register transaction filter: For the register transaction, add an additional filter with the name URL and the alue register and a third filter Chapter 2. Deploying the Solutions for BSM 29

42 with the name HTTP.POST:action and alue *. To set the alue for the name correctly, select HTTP.POST:XXX from the Name list and edit this name so that it has the appropriate alue. 5. Create an All DayTrader GET Transactions transaction filter: The DayTrader transaction is an important transaction definition. Any transaction that uses the HTTP.GET:action method is recorded. Add a filter with the name HTTP.GET:action and alue * to the DayTrader transaction. To set the alue for the name correctly, select HTTP.GET:XXX from the Name list. Edit this name so that it has the appropriate alue. The transaction name is the method name $HTTP.GET:action$. For example, when a HTTP.GET:buy or a HTTP.GET:sell occur, the transaction names are displayed as buy and sell. This enables a generic transaction to be created that records all HTTP.GET methods, but that displays them exactly as they were designed and intended to be displayed. To ensure that the transaction name is shown with the correct alue, in other words as a buy or sell, insert the ariable $HTTP.GET:action$ in the Transaction name field of the Reporting tab of the DayTrader transaction. 6. Create an All DayTrader POST Transactions transaction filter: This filter is similar to the HTTP.GET:action method, any transaction that uses the HTTP.POST:action method is recorded. Repeat the procedure for the All DayTrader GET Transactions transaction filter. Substitute HTTP.POST:action for the HTTP.GET:action method. 7. Create an all other transaction filter: The all other transaction filter is a catch all for any transaction that does not meet the preious transaction definitions. Therefore, the filters are created that exclude the conditions created preiously. Creating clients 1. After you hae defined the applications and transactions, you must define the clients. A client is a system or a group of systems or users that connect to the application. You can define a range of different clients. To iew the list of clients that are already defined, select Clients from the toolbar list. 2. All Clients proides a complete list of all defined clients, regardless of whether they are defined in any other categories. Other clients are defined either by a set of IP addresses, hostnames, users, or a combination. 3. If you require specific clients, for example VIP clients, you can specify them. Ensure that appropriate alues are set in the Filter tab. 4. Define specific clients for the serers that are running the robotic response time scripts, so that you can uniquely identify them in the workspace. Ensure that appropriate alues are set in the Filter tab. Customizing serer components 1. After the applications, transactions, and clients are defined in the Application Management Configuration Editor, you must ensure that any component in the enironment that has a customized configuration is also defined. For example, if a DB2 serer is running on a non-standard port, you might hae to define it. Enabling user session tracking 1. To enable tracking of user sessions, select the DayTrader application and in the Session tab, click to select the Enable session tracking check box. Create a new entry with type HTTP Cookie and alue JSESSIONID. 2. In the Users tab, enable Enable user tracking. Under User Identification section, add an entry specifying HTTP Form Post as the type and also specify a Key name, for example uid. 30 Solutions for BSM Guide:

43 To finalize your configuration, select Profiles from the toolbar list. Expand the Web Response Time node and click Default. Click the Transactions tab. Ensure that all of the transactions you created hae a status of Started. If not, select the transaction and click the Start button on the toolbar. After the Application Management Configuration Editor is configured, and transactions occur in the web application, the application workspace is populated with data. Specifying target computer for integration packages Specify the TBSM Data serer where you want to deploy the IBM Tioli Composite Application Manager for Transactions integration packages. Before you begin The naigation frame shows the task: Specify Targets ITCAM for Transactions Integration Packages Before you deploy the integration packages, know your TBSM Data serer host name and credentials. About this task To deploy the integration package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Chapter 2. Deploying the Solutions for BSM 31

44 Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Specifying target for Transaction Tracking DLA Specify the host where you want to deploy the IBM Tioli Composite Application Manager for Transaction Tracking DLA package. Before you begin The naigation frame shows the task: Specify Targets DLA for ITCAM TT Before you deploy the package, know the name and credentials for the host where the ITCAM for Transaction Tracking Reporter component is installed. About this task To specify the target host for the Transaction Tracking DLA package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. 32 Solutions for BSM Guide:

45 Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Specifying target for Application DLA templates Specify the host where you want to deploy the IBM Tioli Composite Application Manager for Applications DLA templates for WebSphere Application Serer and HTTP serer. Before you begin The naigation frame shows the task: Specify Targets ITM WAS and HTTP serer DLA Templates Before deploying the DLA templates, know the name and credentials for the Tioli Enterprise Portal Serer host. About this task To specify the Tioli Enterprise Portal Serer host where the deployment task will run. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. Chapter 2. Deploying the Solutions for BSM 33

46 5. Click Add and the computer name is added to the Selected target computer list. Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. TBSM Integration package serer configuration Specify the directory and database information for IBM Tioli Business Serice Manager Data serer and the IBM Tioli Monitoring data warehouse on this panel. Purpose These integrations enable you to discoer resources from transaction data and create a serice model in TBSM. To monitor these resources, you need to deploy the Eent Manager Customizations for ITCAM eents. The naigation frame shows the task: Configure ITCAM for Transactions Integration Packages Linux Tioli ITCAM for Transactions TBSM Integration Package Parameters Use these parameters to specify information for your TBSM Data serer and Tioli Monitoring warehouse database. You need to scroll down to see all the parameters. Specify these parameters: Deploy TBSM integration package Select whether to deploy the package. The default is Yes. Directory to copy the TBSM integration package The directory on your Data serer where you want to copy the package. The default is: /opt/ibm/tioli/itcam_integration_package TBSM home directory Home directory for your Data serer. The default is: /opt/ibm/tioli/tbsm TBSM Database Username The name of a user that has permission to update tables in the database. This user is the same as the TBSM DB2 user name. TBSM Database password The database user password. Verify password Verify the user password. 34 Solutions for BSM Guide:

47 ITM warehouse database type The database used for the Tioli Monitoring warehouse database. Select from the drop-down list: DB2 Microsoft SQL Serer 2000 Microsoft SQL Serer 2005 Oracle Other The default is DB2. If you selects Other as a supported ersion, the warehouse fields collapse and you must enter the fields: JDBC URL for the ITCAM database The URL format is determined by the jdbc drier you are using to connect to the database. For information about the URL format, see the JDBC drier documentation. For example, the DB2 (Uniersal Type 4 Drier): jdbc:db2://hostname:portnumber/databasename JDBC Jaa Drier classname The JDBC drier to use. Default: com.ibm.db2.jcc..db2drier ITM warehouse database host name The host name for the Tioli Monitoring warehouse database. ITM warehouse database port The port for the Tioli Monitoring warehouse database. The default is ITM warehouse user name The installation user for the Tioli Monitoring warehouse database. The default is db2inst1. ITM warehouse password The password for the Tioli Monitoring warehouse database user. Verify password Verify the user password. ITM warehouse database name The name of the Tioli Monitoring warehouse database. The default is WAREHOUS. ITM warehouse database drier type The drier type for the Tioli Monitoring warehouse database. The default is 4. Adanced In the Adanced tab, you can also choose whether you want to: Skip predeployment check Oerwrite existing package - This option allows you oerride an existing integration package. Use updated ITCAM package. Chapter 2. Deploying the Solutions for BSM 35

48 If you select Yes for this option, a new parameter prompts you for the location of the integration package. The package must reside on the target host. Full path to the updated ITCAM Integration package (must be in *.tar.gz file): Enter the full path to the package_name.tar.gz for the integration package. Click Browse to browse your file system. The default for each option is No. DLA Integration package serer configuration Specify the directory and database information for IBM Tioli Business Serice Manager Data serer, the Tioli Enterprise Portal serer, and the IBM Tioli Monitoring warehouse on this panel. Purpose The DLA integration helps create TBSM seriices. To monitor these resources, you need to deploy the Eent Manager Customizations for ITCAM eents. The naigation frame shows the task: Configure ITCAM for Transactions Integration Packages Linux Tioli ITCAM for Transactions DLA Integration Package The package ersion included in the Deployment Wizard is ersion 7 release ( ). Check for updated ersions at the Integrated Serice Management Library here: details?catalog.label=1tw10cp2b Parameters Use these parameters to specify information for your TBSM Data serer and Tioli Monitoring warehouse database. You need to scroll down to see all the parameters. Specify these parameters: Deploy DLA integration package Select whether to deploy the package. The default is Yes. Directory to copy the DLA integration package The directory on your TBSM Data serer where you want to copy the package. The default is: /opt/ibm/tioli/itcam_integration_package JAVA_HOME directory The JAVA_HOME directory is required to execute the commands that generate an IdML book. The default is /opt/ibm/tioli/tip2/jaa. 36 Solutions for BSM Guide:

49 Full path to JDBC drier JARs separated by a colon The JDBC driers are required to set the JDBC CLASSPATH and connect to the database. If you do not hae this file on the Data serer host, find the file and copy it to your system. These files are typically proided by the database endor with the database or the database client package. For example, you can find this file on your Oracle host system or as part of your Oracle client installation. Example entries for DB2: /opt/ibm/db2/9.7/jaa/db2jcc.jar: /opt/ibm/db2/9.7/jaa/db2jcc_license_cu.jar TEPS host name Host name for your Tioli Enterprise Portal serer. TEPS port Host name for your Tioli Enterprise Portal serer. The default is The output directory for the IDML XML book file Directory where the generated IdML book is copied. Enter the directory name that is monitored for new book files. When a new book file is detected in the directory you specify, the file is read and processed. The default is /opt/ibm/tioli/itcam_integration_package. Name of the Application Management Console Agent (T3) The name of the Tioli Monitoring managed system name of the application management console agent (T3) connected to your monitoring enironment. For example: s21-m6:t3. This name is the application name you created when you configured the application management console as described in: Configuring the ITCAM Application Management Configuration Editor on page 28 Number of hours of TDW data the DLA should consider when creating the book The span of hours the DLA uses when it creates an IdML book from the Tioli Data Warehouse. The default is 8. ITM warehouse database type The database used for the Tioli Monitoring warehouse database. Select from the drop-down list: DB2 Microsoft SQL Serer 2000 Microsoft SQL Serer 2005 Oracle Other The default is DB2. If you selects Other as a supported ersion, the warehouse fields collapse and you must enter the fields: JDBC URL for the ITCAM database The URL format is determined by the jdbc drier you are using to connect to the database. For information about the URL format, see the JDBC drier documentation. For example, the DB2 (Uniersal Type 4 Drier): Chapter 2. Deploying the Solutions for BSM 37

50 jdbc:db2://hostname:portnumber/databasename JDBC Jaa Drier classname The JDBC drier to use. Default: com.ibm.db2.jcc..db2drier ITM warehouse database host name The host name for the Tioli Monitoring warehouse database. ITM warehouse database port The port for the Tioli Monitoring warehouse database. The default is ITM warehouse user name The installation user for the Tioli Monitoring warehouse database. The default is db2inst1. ITM warehouse password The password for the itioli Monitoring warehouse database user. Verify password Verify the user password. ITM warehouse database name The name of the Tioli Monitoring warehouse database. The default is WAREHOUS. ITM warehouse database drier type The drier type for the Tioli Monitoring warehouse database. The default is 4. Adanced In the Adanced tab, you can also choose whether you want to: Skip predeployment check Oerwrite existing package - This option allows you oerride an existing integration package. Use updated ITCAM package. If you select Yes for this option, a new parameter prompts you for the location of the integration package. The package must reside on the target host. Full path to the updated ITCAM Integration package (must be in *.tar.gz file): Enter the full path to the package_name.tar.gz for the integration package. Click Browse to browse your file system. The default for each option is No. Transaction Tracking DLA configuration Specify the IBM Tioli Monitoring home directory for the host where the Transaction Tracking Reporter component is installed. Purpose The DLA package helps create TBSM serices from transactions. To monitor these resources, you also need to deploy the Eent Manager Customizations for ITCAM eents. 38 Solutions for BSM Guide:

51 The naigation frame shows the task: Configure DLA for ITCAM TT Linux Tioli ITCAM TT DLA Parameters Use these parameters to specify information for your host. Specify these parameters: ITM home directory The HOME directory for Tioli Monitoring The default is /opt/ibm/itm. Adanced In the Adanced tab, you can also choose whether you want to: Skip predeployment check Oerwrite existing package - This option allows you oerride an existing integration package. Use updated ITCAM package. If you select Yes for this option, a new parameter prompts you for the location of the integration package. The package must reside on the target host. Full path to the updated ITCAM Integration package (must be in *.tar.gz file): Enter the full path to the package_name.tar.gz for the integration package. Click Browse to browse your file system. The default for each option is No. Application DLA template configuration Specify the IBM Tioli Monitoring home directory for thetioli Enterprise Portal Serer host and the DLA templates you want to deploy. Purpose The DLA package helps create TBSM serices from application data collected by the agents. The naigation frame shows the task: Configure ITM WAS and HTTP Serer DLA Templates Linux Tioli ITM WAS and HTTP Serer DLA Templates Parameters Use these parameters to specify information for your Tioli Enterprise Portal Serer host. Specify these parameters: Chapter 2. Deploying the Solutions for BSM 39

52 ITM home directory The HOME directory for Tioli Monitoring The default is /opt/ibm/itm. Deploy the HTTP serer DLA Template Specify if you want to deploy this DLA template. The default is Yes. Deploy the WAS DLA Template Specify if you want to deploy this DLA template. The default is Yes. Adanced In the Adanced tab, you can also choose whether you want to: Skip predeployment check Oerwrite existing DLAs - If you select Yes, the original file is oerwritten and backed up in the same directory where the original itcamfttdla.jar existed. The file name for the back up is in the format: itcamfttdla_bsma_backup_date.jar. For example in this directory and filename.: $ITM_HOME_DIRECTORY/arch/bin/itcamfttdla_BSMA_BK_date.jar The default for each option is No. Summary for ITCAM Monitoring deployment After you hae specified information for the IBM Tioli Composite Application Manager packages and DLA templates you want to deploy, the Summary panel lets you choose how to run the deployment. Purpose You can run the deployment for each task one at a time, or you can run them all at once. The naigation frame shows the task: Summary To run a task by itself, click Deploy Task for the task you want to run. To deploy all the tasks in the summary, click Deploy all. Deploying Automated Discoery Deploys the automated discoery components required to automate the discoery process between IBM Tioli Monitoring, the IBM Tioli Composite Application Manager products, and the IBM Tioli Application Dependency Discoery Manager. Before you begin The naigation frame shows the task: 40 Solutions for BSM Guide:

53 Select Tasks Deploy Automated Discoery from ITM/ITCAM to TADDM Before you deploy the discoery components, you need: Host and user information for TADDM. Host and user information for the Tioli Enterprise Monitoring Serer used by ITCAM products. The DLA automations hae these requirements: Tioli Management Serices (TMS) DLA automation This DLA automation must be run from the Tioli Enterprise Portal Serer host. ITCAM for Transaction Tracking DLA automation This DLA automation can be run from any system that has a tacmd command line interface, such as the Tioli Enterprise Portal Serer host. ITCAM Response Time DLA automation This DLA automation can be run from any machine, but requires that you deploy the ITCAM Integration package DLA component to the target machine before you begin this task. Use the deployment wizard and select Deploy Best Practice ITCAM Monitoring-> ITCAM Integration Package. The DLA integration package is the required component. Configure the application management console (AMC) to filter data discoered by the Web Response Time (WRT) and Transaction Tracking (TT) agents. About this task This task helps you configure Discoer Library Adaptors to run automatically and transfer the IdML output to TADDM (only not TBSM). You can use any machine in the enironment as the target, but the simplest method is to deploy the automation to the TADDM host. Post Deployment task After you complete these tasks, you must complete a manual procedure to enable DLA automation. To enable the DLA automation, you need to run the dlaautomate.sh script that is included in this package as described in the topic: DLA automation steps on page 48 To deploy Automated Discoery: Procedure 1. If you hae not already done so, configure the application management console (AMC) to filter data discoered by the Web Response Time (WRT) and Transaction Tracking (TT). 2. Click Deploy Automated Discoery from ITM/ITCAM to TADDM. 3. Click Next. 4. The Deployment wizard guides you through these high-leel steps: Chapter 2. Deploying the Solutions for BSM 41

54 ITM and ITCAM DLA Automation This option deploys the DLA Automation Package to the directory you specify. It updates a properties file with the information you enter in the configuration panel. TADDM artifacts for DLA automation This option deploys two components. The first component enables the IdML books to reconcile with objects discoered in TADDM. The second component helps automate the importation of IdML books into TADDM. 5. For each task you specify the target computer and configuration information. Specify target computer for deployment Specify the target computer where you want to deploy the integration packages and DLAs. Configuration For each option, you specify information about your TADDM, Tioli Monitoring, and ITCAM enironments. You are only asked for both targets if you choose to install both components. If you only select to deploy to IBM Tioli Monitoring/ITCAM then you will not see a target for the TADDM system. You do hae to enter TADDM credentials in the configuration menu and you are not asked for the TADDM target system. 6. For more details about deploying situations, see the subsequent topics. Specifying target for monitoring DLA automation Specify the host where you want to deploy the automation components for Tioli Monitoring and ITCAM applications. Before you begin The naigation frame shows the task: Specify Targets ITM and ITCAM DLA Automation Specify your target host depending on your enironment and what DLA automations you want to deploy as follows: Tioli Management Serices (TMS) DLA automation This DLA automation must be run from the Tioli Enterprise Portal Serer host. ITCAM for Transaction Tracking DLA automation This DLA automation can be run from any system that has a tacmd command line interface, such as the Tioli Enterprise Portal Serer host. ITCAM Response Time DLA automation This DLA automation can be run from any machine, but requires that you deploy the ITCAM Integration package DLA component to the target machine before you begin this task. Use the deployment wizard and select Deploy Best Practice ITCAM Monitoring-> ITCAM Integration Package. The DLA integration package is the required component. 42 Solutions for BSM Guide:

55 About this task To deploy the integration package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Specifying target for TADDM DLA automation Specify the host where you want to deploy the automation components for IBM Tioli Application Dependency Discoery Manager. Before you begin The naigation frame shows the task: Specify Targets TADDM artifacts for DLA Automation Specify your TADDM host as the target computer. Chapter 2. Deploying the Solutions for BSM 43

56 About this task To deploy the integration package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Monitoring DLA Automation configuration Specify the information required for DLA automation about the TADDM, IBM Tioli Monitoring, and IBM Tioli Composite Application Manager applications on this panel. Purpose The DLA automation helps you specify the information needed to automate the discoery process between the monitoring applications and TADDM. The naigation frame shows the task: 44 Solutions for BSM Guide:

57 Configure Parameters ITM and ITCAM DLA Automation Linux ITM-ITCAM Automation Parameters Use these parameters to specify information for your TADDM, Tioli Monitoring, and ITCAM applications. You need to scroll down to see all the parameters. Specify these parameters: Full directory path for package installation The directory where you want to deploy the package. Default: /opt/ibm/tioli/dla_automation Use TADDM shared directory Select No, you enter the host information for your TADDM serer. If you hae a shared directory set up for TADDM, select Yes and the Shared Directory for TADDM displays below this field. You need write and delete permissions to this directory. If you do not select to use TADDM share, it will use the TADDM DLA web serice to send files. Default: No TADDM host name The host name for your TADDM serer. You must add the port number after the host name, separated by a colon. The port number must match the com.collation.webport property in the collation.properties file for TADDM. For example: myhost.mydi.mycity.mycompany.com:9430 TADDM user name The user name for TADDM. TADDM password The password for the user name Verify password Verify the password. Sleep time between each iteration (in milliseconds) The time interal between IdML book processing iterations in milliseconds. Default: Enable TMSDLA automation Select whether to automate the running of the Tioli Management Serices DLA. This DLA automation must be run from the Tioli Enterprise Portal Serer host. If your target machine is not a Tioli Enterprise Portal Serer host, do not enable this DLA automation. Default: Yes. Enable ITCAM TT automation Select whether to automate the running of the ITCAM for Transactions DLA. This DLA automation can be run from any host that has a tacmd command line interface, such as the Tioli Enterprise Portal Serer host. Chapter 2. Deploying the Solutions for BSM 45

58 The default is Yes. Hub TEMS host name The hub Tioli Enterprise Monitoring Serer host name. TEPS Home directory The fully qualified path where the Tioli Enterprise Portal Serer is installed. Default: /opt/ibm/itm Hub TEMS user name The installation user for the Tioli Enterprise Monitoring Serer. Hub TEMS password The password for the user. Verify password Verify the password for the user. Managed System Name The name of the Tioli Monitoring managed system name of the Transaction Reporter Agent. Note: The agent ersion of the managed system name needs to be at the leel or higher. If the transaction reporter agent is not currently at 6.2.2, any other agent on the same system can be used as long as it is at a leel of or higher. Execute DLA in remote MSN Select this option if the ITCAM for Transaction Tracking agent is produced on a remote Tioli Monitoring agent. The default is No. If you select Yes, you need to specify these additional parameters: Tioli Monitoring home directory on remote serer Remote MSN host Enable ITCAM RT DLA automation Select whether to automate the running of the ITCAM for Response Time DLA. This DLA automation can be run from any machine, but requires that you deploy the ITCAM Integration package DLA component to the target machine before you begin this task. Use the deployment wizard and select Deploy Best Practice ITCAM Monitoring-> ITCAM Integration Package. The DLA integration package is the required component. The default is Yes. Full path to ITCAM RT DLA directory (to run dlaadaptor script) Path to the directory containing the dlaadaptor.sh script. This script is included with the required ITCAM for Transactions DLA Integration package you deployed with the Deploy Best Practice ITCAM Monitoring > ITCAM for Transactions Integration Packages option in the Deployment Wizard. The DLA integration package is the required component. The package is unpacked in the directory you specify at this prompt in the DLA integration package configuration panel.: Full directory path for package installation The dlaadaptor.sh script is located in the dla subdirectory, for example: 46 Solutions for BSM Guide:

59 /opt/ibm/tioli/itcam_integration_package/dla Adanced In the Adanced tab, you can also choose whether you want to: Oerwrite existing package The default is No. TADDM DLA Automation configuration Specify the information required for DLA automation about the TADDM serer on this panel. Purpose The DLA automation helps you specify the information needed to automate the discoery process between the monitoring applications and TADDM. The naigation frame shows the task: Configure Parameters TADDM artifacts for DLA Automation Linux Configure TADDM for DLA Automation Parameters Use these parameters to specify information for your TADDM host. Specify these parameters: TADDM dist directory The dist directory under the TADDM installation directory. This is the $COLLATION_HOME ariable alue. On Linux systems, the default location for installing TADDM is the /opt/ibm/taddm directory. Therefore, in this case, the $COLLATION_HOME default directory is /opt/ibm/taddm/dist. Monitor shared directory The directory where the IdML book files are written. Share this directory with read and write permissions. Default: /home/taddm/share Sleep time between each iteration (in milliseconds) The time interal between IdML book processing iterations in milliseconds. Default: 3000 Summary for Automated Discoery deployment After you hae specified information for Automated Discoery, the Summary panel lets you choose how to run the deployment. Purpose The naigation frame shows the task: Summary Chapter 2. Deploying the Solutions for BSM 47

60 You can run the deployment for each task one at a time, or you can run them all at once. To run a task indiidually, click Deploy Task for the task you want to run. To deploy all the tasks in the summary, click Deploy all. DLA automation steps After you deploy the Automated Discoery components with the Deployment Wizard, you must enable DLA automation using this manual procedure. Before you begin Note: If you are using file sharing to moe the IdML files, you must create a shared drie on the Tioli Application Dependency Discoery Manager serer and mount this drie on the system where you intend to run the DLAs using the dlaautomate command. Ensure that the user ID that you use to run DLAAutomateLoader command on the Tioli Application Dependency Discoery Manager serer can create and delete files on the monitoring directory. Also ensure that the user ID for the serer where the dlaautomate command is run has the permissions required to read and delete files on the mounted directory. These requirements must be tested before you begin. Note: Verify each DLA command before attempting to automate it. About this task This procedure describes how to enable the automation of the Discoery Library Adapters (DLA) and their interaction with the IBM Tioli Application Dependency Discoery Manager serer. Procedure 1. Log in to the TADDM serer as a user such as taddmusr. 2. At a command prompt, change directory to the Tioli Application Dependency Discoery Manager serer dist/bin directory. 3. Start the Tioli Application Dependency Discoery Manager serer. 4. Run the./dlaautomateloader.sh command. Note: If you want the script to run in the background, execute the script with the &, for example./dlaautomateloader.sh &. 5. Using an appropriate user ID, log in to a system on which you want to run a DLA. 6. (Optional) If you using HTTP to transfer IdML files to the Tioli Application Dependency Discoery Manager serer, open, and edit the DLAAutomateClient.properties file. Add alues for the following properties: taddm.host= taddm.userid= taddm.password= Notes: The taddm.host property can indicate a port. The port you add, must match com.collation.webport in the Tioli Application Dependency Discoery 48 Solutions for BSM Guide:

61 Manager collation.properties file. An example port is: taddm.host=taddmserer.mynet.com:9430. Each set of properties that starts with the string, agent. is used to run a separate DLA. The next part of the string indicates the DLA to which the property is associated. The name that can be used is unrestricted. To run a DLA, set the run property for the DLA to true. When you are configuring your system, turn on each agent indiidually and test that the configuration is operating properly before proceeding to the next DLA. When all DLAs hae been erified, turn on all of the agents together. When the dlaautomate command is run, any property that ends with.password is encrypted. The dladir property sets the path for the directory from which the DLA is run from. You must include two backslashes for the Windows directory separator. The dlaoutputdir property specifies the location in which the IdML book are produced. The dlafilenameregexp is a regular expression that matches the IdML books produced. The taddmshare property specifies the full path of the directory that is shared with Tioli Application Dependency Discoery Manager. You must test this property by copying a file to this directory and then confirming that the file was written to the Tioli Application Dependency Discoery Manager. You must also confirm that it can be deleted by the Tioli Application Dependency Discoery Manager user ID. The taddmshare property oerrides HTTP as the method used to send the file to the Tioli Application Dependency Discoery Manager serer. The loadidml property allows you to set options for the Tioli Application Dependency Discoery Manager loadidml command. Only the -g attribute is allowed. All other attributes are ignored. The commands that must be run are listed in the commands property and are executed in the order listed in the file. You must use the full path of the command. Commands containing ${propertname} are substituted with the property. This is used primarily for passwords. If there is no matching property the ${..} is left unchanged. 7. (Optional) For some DLAs, the output is produced on a remote IBM Tioli Monitoring agent. The agent must be built on IBM Tioli Monitoring ersion or higher to ensure that the remote execute command and getfile tacmd actions can be run. To retriee these DLAs set the following properties: a. The dlaremotelochostmsn property sets the ITM MSN of the machine where the DLA is produced. b. The dlaremotelocdir property sets the full path of the directory on the remote machine to which the DLA is produced. c. The dlaremotefnameexp is a regular expression that matches the filename of the books produced. d. After you hae set these properties, edit the Tioli Enterprise Monitoring Serer configuration file, for example u_ms_tems.config and set the KT1_TEMS_SECURE ariable to yes. e. Restart the Tioli Enterprise Monitoring Serer. 8. To run the DLA automation script, enter the dlaautomate command: UNIX systems Chapter 2. Deploying the Solutions for BSM 49

62 ./dlaautomate.sh Note: If you want the script to run in the background, execute the script with the &, for example./dlaautomate.sh &. What to do next The automation proided by Solutions for Business Serice Management for Discoery Library Adapters (DLAs) means that, for each enabled DLA, an IdML book is created eery time the DLA is run. By default, the dlaautomate scripts are run eery 120 seconds. As a result, a large number of IdML books are generated. This can result in significant disk space usage. You can control the number of IdML books created by controlling the iteration time. This is configured by setting the properties: sleeptime=<number of milliseconds> agent.<dla type>.sleeptime=<number of milliseconds> Where the DLA type is the DLA for which an IdML book is created and the time between each script execution is set by setting a alue for number of milliseconds. To change these properties, edit these properties for each DLA type in the DLAAutomateClient.properties file located in the directory into which you hae installed the DLA automation package. Alternatiely, you can periodically delete the older IdML books that are no longer required. Deploy eent manager customizations Deploys the eent manager modifications to IBM Tioli Netcool/OMNIbus ObjectSerer (Netcool/OMNIbus) and the Tioli Eent Integration Facility probe (EIF probe). These modifications integrate Netcool/OMNIbus and IBM Tioli Monitoring so that their respectie consoles are able to share eents and eent actions taken by operators of both. These tasks also ensure that eents coming from arious elements in the infrastructure arrie at IBM Solutions for Business Serice Management dashboards so as to indicate status isually. Before you begin Before you deploy any of the any of the eent manager customization tasks, back up your Netcool/OMNIbus ObjectSerer configuration with the nco_confpack utility. For information about the nco_confpack utility, see the Tioli Netcool/OMNIbus information center, aailable from this URL: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/welcome.htm Naigate to the following topics about the nco_confpack utility; Setting up Tioli Netcool/OMNIbus, Importing, and exporting ObjectSerer configurations, Using the nco_confpack utility. Read the topics Importable and exportable objects, Exporting configurations, and Importing configurations. Before you deploy the eent customizations, you also need: 50 Solutions for BSM Guide:

63 Host and user information for the Netcool/OMNIbus. Host and user information for the EIF probe The naigation frame shows the task: Select Tasks Deploy Eent Manager Customizations About this task This task helps you configure Netcool/OMNIbus and the EIF probe to collect, manage, and correlate eents for the serice model that was created with data from monitoring applications, such as IBM Tioli Monitoring as follows: 1. The baseline monitoring application, such as Tioli Monitoring collects and consolidates data on key performance indicators from systems, applications, middleware, and transactions. When the monitoring application detects an alert condition, it creates a situation eent that is forwarded to the EIF probe. 2. The EIF probe conerts the situation eents to Netcool/OMNIbus eents and inserts the eents into the Netcool/OMNIbus ObjectSerer Database table. 3. Netcool/OMNIbus collects and consolidates the eents and TBSM reads these eents. Important: The Eent Manager Customization tasks require a Netcool/OMNIbus instance that is configured for TBSM. If you installed Netcool/OMNIbus from your TBSM installation package, than it is ready for the Eent Manager modifications. Otherwise, you need to add the TBSM configuration by hand. For information on configuring Netcool/OMNIbus for TBSM, see the TBSM information center aailable from this URL: %2Fcom.ibm.tioli.itbsm.doc_6.1%2Fwelcome.htm Naigate to the following topic: Business Serice Manager, Installation Guide, Planning, Netcool/OMNIbus considerations. To deploy the eent manager modifications:. Procedure 1. Select Eent Manager Customizations. 2. Click Next. 3. The Deployment wizard guides you through these high-leel steps: Install ITM Eent Synchronization Component This task deploys the Tioli Monitoring Situation Update Forwarder. To complete this task, you need the tools-package installation image for Tioli Monitoring ersion 6 release 2.3 Fix Pack 1 or higher. The Situation Update forwarder requires the following 32-bit libraries on the Netcool/OMNIbus host: libxp.so.6 libxmu.so.6 Configure OMNIbus for ITM Eents This task configures Netcool/OMNIbus for Tioli Monitoring eents by installing the schemas: Chapter 2. Deploying the Solutions for BSM 51

64 itm_proc.sql itm_db_update.sql itm_eent_cache.sql itm_sync.sql These updates enable you to manage the situations eents that were created with the Deploy Best Practice Monitoring task. Modify OMNIbus default deduplication trigger This task modifies the Netcool/OMNIbus deduplication trigger. Configure OMNIbus Schema and Rules for ITCAM eents This task runs the omnibusupdater.sh to add these rules files for the EIF probe: kt3.rules - Application Management Console (AMC) kt4.rules - Client Response Time (CRT) kt5.rules - Web Response Time (WRT) kt6.rules - Robotic Response Time (RRT) kto.rules - Transaction Tracking (TT) This task also updates the Netcool/OMNIbus to enable eent management for the ITCAM products. Important: To complete this task, you must also customize the itm_eent_cache.sql file for the ITCAM attributes as a post-installation task. The instructions for this post-installation task are included at the end of the Configure OMNIbus Schema and Rules for ITCAM eents task. Configure OMNIbus Schema for IBM Solutions for Business Serice Management This task runs the nco_sql command on bsm_accelerator_schema.sql script to configure the Netcool/OMNIbus schema for Solutions for BSM. Configure EIF Probe for ITM Eents This task copies and enables the rules files you need to correlate the TBSM business serices or resources with the situation eents from the Tioli Monitoring Situation Update Forwarder. The rules files are: itm_eents.rules - generic Tioli Monitoring situation handling tbsm_eif_eent.rules - EIF eent handling for TBSM km_tbsm.rules- VMware agent situation handling Configure EIF probe for TADDM Integration This task copies and enables the tioli_eif_taddm.rules file for the TADDM integration. 4. For each task you specify the target computer and configuration information. Specify target computer for deployment Specify the target computer where you want to deploy the eent manager customizations. Configuration For each option, you specify information about your TADDM, Tioli Monitoring, and ITCAM enironments. 5. For more details about these deployment tasks, see the subsequent topics. 52 Solutions for BSM Guide:

65 For more information about eent forwarding from Tioli Monitoring to Netcool/OMNIbus, see the Tioli Monitoring Information Center Setting up eent forwarding to Netcool/OMNIbus topic at: com.ibm.itm.doc_6.2.3fp1/ itm623fp1_install601.htm?path=3_0_3_0_9_1#omnibus_install From the main topic Setting up eent forwarding to Netcool/OMNIbus, see these additional subsections: For One hub architecture scenario, see: Architecture scenarios > One hub Tioli Enterprise Monitoring Serer and one Netcool/OMNIbus ObjectSerer For multiple Tioli Enterprise Monitoring Serers, see: Customizing Eent Integration > Updating the IBM Tioli Monitoring Situation Forwarder to forward eent status updates to additional monitoring serers For eent synchronization upgrade see: Upgrading from a preious installation of IBM Tioli Monitoring and Netcool/OMNIbus integration For information about customizing eent integration, see Customizing Eent Integration Failoer and multi-host ObjectSerer and probe considerations If you are deploying to a failoer or mult-tiered enironment, read this topic. To deploy in a failoer or multitiered enironment of ObjectSerers and Tioli Eent Integration Facility probes (EIF probe): Restriction: The IBM Solutions for Business Serice Management requires that the ObjectSerer and EIF probe reside on the same host. Specify all your ObjectSerer and EIF probe hosts when you specify target machines for these eent customization tasks: Install ITM Eent Synchronization Component Configure OMNIbus for ITM Eents Modify OMNIbus default deduplication trigger Configure OMNIbus Schema and Rules for ITCAM eents Configure OMNIbus Schema for IBM Solutions for Business Serice Management Configure EIF Probe for ITM Eents Configure EIF probe for TADDM Integration If you hae master and slae EIF probes, run the EIF probe deployment tasks on the target hosts for both the master and slae probes. On each host in the failoer enironment, update the bi-directional gateway mapping file (NCO_GATE.map) file with the column names that are added to the alerts.status table by the Deployment Wizard. For more information, see the example in the next topic. Chapter 2. Deploying the Solutions for BSM 53

66 On each host in a multitiered enironment, update the bidirectional aggregation ObjectSerer Gateway (AGG_GATE. map) with the column names that are added to the alerts.status table by the Deployment Wizard. The entries are the same as the entries for NCO_GATE.map. Restart the ObjectSerer and for multitiered enironments, the AGG_GATE gateway. More information For information about ObjectSerer gateways, see: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/gateways/objectserergw/wip/ concept/objsrgw_intro.html For information about multitier deployments see: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/install/concept/ omn_ins_multitieredhighaailability.html For more information about architecture scenarios for setting up Tioli Monitoring and Netcool/OMNIbus, see: com.ibm.itm.doc_6.2.3fp1/itm623fp1_install605.htm?path=3_0_3_0_9_1_1#arch_scen Map file example For each ObjectSerer in your enironment, you need to update the NCO_GATE.map with the columns for the IBM Solutions for Business Serice Management. The NCO_GATE.map file is typically located in the installdirectory/netcool/omnibus/ gates/nco_gate/ directory. Contents of the NCO_GATE.map file If you hae a multi-tiered enironment, you need to make the same edits to the default AGG_GATE.map file in the directory: installdirectory/netcool/omnibus/extensions/multitier/gateway Manually edit this file, and add all the entries shown in bold type. You must also add a comma (,) at the end of the following line: ticket_eligible ############################################################################## # Netcool/OMNIbus Bi-directional ObjectSerer Gateway 7.2 # # Default map definition file. # # Ident: $Id: objser_bi.map /10/13 10:36:35 cappl Deelopment $ # # Reision History: # 1.1: Initial reision. # 1.2: User related system table maps added. # 1.3: Dynamic tool tables and destop table maps added. # # Notes: # # Fields that are marked as ON INSERT ONLY will only be passed when an eent 54 Solutions for BSM Guide:

67 # is inserted for the first time. (ie. they will not be updated). The ordering # of the fields is not important as the gateway will use named alue insertion. # ############################################################################## CREATE MAPPING StatusMap ( Identifier ON INSERT ONLY, Node ON INSERT ONLY, NodeAlias ON INSERT ONLY Manager ON INSERT ONLY, Agent ON INSERT ONLY, AlertGroup ON INSERT ONLY, AlertKey ON INSERT ONLY, Seerity Summary StateChange FirstOccurrence ON INSERT ONLY, LastOccurrence InternalLast Poll ON INSERT ONLY, Type ON INSERT ONLY, Tally Class ON INSERT ONLY, Grade ON INSERT ONLY, Location ON INSERT ONLY, OwnerUID OwnerGID Acknowledged Flash EentId ON INSERT ONLY, ExpireTime ON INSERT ONLY, ProcessReq SuppressEscl Customer ON INSERT ONLY, Serice ON INSERT ONLY, PhysicalSlot ON INSERT ONLY, PhysicalPort ON INSERT ONLY, PhysicalCard ON INSERT ONLY, TaskList NmosSerial ON INSERT ONLY, NmosObjInst ON INSERT ONLY, NmosCauseType LocalNodeAlias ON INSERT ONLY, LocalPriObj ON INSERT ONLY, LocalSecObj ON INSERT ONLY, LocalRootObj ON INSERT ONLY, RemoteNodeAlias ON INSERT ONLY, RemotePriObj ON INSERT ONLY, RemoteSecObj ON INSERT ONLY, RemoteRootObj ON INSERT ONLY, X733EentType ON INSERT ONLY, X733ProbableCause ON INSERT ONLY, X733SpecificProb ON INSERT ONLY, X733CorrNotif ON INSERT ONLY, URL ON INSERT ONLY, ExtendedAttr ON INSERT ONLY, SererName ON INSERT ONLY, SererSerial ON INSERT ONLY, BSM_Identity BSM_ClassName BSM_SubIdentity RAD_SericeName RAD_SLAName RAD_SericeID RAD_SericeTypeName RAD_SericeTypeID Chapter 2. Deploying the Solutions for BSM 55

68 RAD_FilterIDList RAD_FunctionName RAD_UserFunctionName RAD_IsIntermediateFunction RAD_FunctionType RAD_TimeWindow RAD_TimeWindowStart RAD_TimeWindowEnd RAD_TimeWindowLength RAD_CurrentRawMetric RAD_CurrentRawMetricNumeric RAD_CurrentRelatieMetric RAD_CurrentFunctionState RAD_ThresholdNum RAD_ViolationThresholdRelatieM RAD_ViolationThresholdRawMetric RAD_ViolationRemainingRawMetric RAD_NextThresholdRelatieMetric RAD_NextThresholdRawMetric RAD_NextThresholdRemainingRawM RAD_TotalRawMetric RAD_RawInputValue RAD_RawInputLastValue RAD_LastCount RAD_WebtopTool1 RAD_WebtopTool2 ITMStatus ITMDisplayItem ITMEentData ITMTime ITMHostname ITMIntType ITMResetFlag TECHostname TECFQHostname TECDate TECRepeatCount TECStatus TECSererHandle TECEentHandle TECDateReception ticket_eligible BSMAccelerator_Serice BSMAccelerator_Serice, BSMAccelerator_Function TECHostname TECFQHostname TECDate TECRepeatCount ITMStatus ITMDisplayItem ITMEentData ITMTime ITMHostname ITMPort ITMIntType ITMResetFlag ITMSitType ITMThruNode ITMSitGroup ITMSitFullName ITMApplLabel ITMSitOrigin CAM_Application_Name CAM_Transaction_Name CAM_SubTransaction_Name CAM_Client_Name CAM_Serer_Name 56 Solutions for BSM Guide:

69 CAM_Profile_Name CAM_Response_Time CAM_Percent_Aailable CAM_Expected_Value CAM_Actual_Value CAM_Details CAM_Total_Requests ); CREATE MAPPING JournalMap ( KeyField = TO_STRING(STATUS.SERIAL) + ":" + ) + ":" + ) ON INSERT ONLY, Serial = STATUS.SERIAL, Chrono UID = ), Text1 Text2 Text3 Text4 Text5 Text6 Text7 Text8 Text9 Text10 Text11 Text12 Text13 Text14 Text15 Text16 ); CREATE MAPPING DetailsMap ( KeyField + #### + ) ON INSERT ONLY, Identifier AttrVal Sequence Name Detail ); Specifying target computer for Eent Manager tasks Specify the hosts where you want to deploy the Eent Manager packages. Before you begin The naigation frame shows the task: Specify Targets Install ITM Eent Synchronization Component Configure OMNIbus for ITM Eents Modify OMNIbus default deduplication trigger Configure OMNIbus Schema and Rules for ITCAM eents Configure OMNIbus Schema for IBM Solutions for Business Serice Management Configure EIF Probe for ITM Eents Chapter 2. Deploying the Solutions for BSM 57

70 Configure EIF probe for TADDM Integration Before you deploy the eent manager customizations, know your Netcool/OMNIbus ObjectSerer and EIF probe host names and credentials. User The user you specify must be the user that installed the ObjectSerer and the EIF probe. Target host The EIF probe and ObjectSerer must be installed on the same host. You can hae multiple computers in this configuration, but each host must hae an ObjectSerer and an EIF probe. About this task To deploy the integration package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 58 Solutions for BSM Guide:

71 7. Click Next. Tioli Monitoring Eent synchronization configuration This task deploys the Tioli Monitoring Situation Update Forwarder. Prerequisites To complete this task, copy the tools package installation image for Tioli Monitoring ersion 6 release 2.3 Fix Pack 1 or higher to the target machine. The Situation Update Forwarder requires the following 32-bit libraries on the Netcool/OMNIbus host: libxp.so.6 libxmu.so.6 Purpose This task deploys the Situation Update Forwarder that enables IBM Tioli Netcool/OMNIbus to forward eents updates to IBM Tioli Monitoring. The naigation frame shows the task: Configure Install ITM Eent Synchronization Component LNX Install ITM Eent Synchronization Component (Situation Update Forwarder) Parameters Scroll down to see all the parameters. Specify these parameters: Specify fully qualified path of IBM Tioli Monitoring The fully qualified path of IBM Tioli Monitoring Tools image file for ersion Fix pack 1 or higher. Make sure you hae a copy this file on the target machine before you start this deployment task. ITM Eent Synchronization installation location (Required 200 MB free space)... The deployment wizard creates the directory you specify and installs the Situation Update Forwarder to this directory. Default: /opt/ibm/sitforwarder Name of configuration file The file where the configuration information for the Situation Update Forwarder is stored. Default: situpdate.conf Polling interal for situation updates The polling interal (in seconds) that Tioli Monitoring uses to determine if there are new eent updates to send from Netcool/OMNIbus to the hub Tioli Enterprise Monitoring Serer. The minimum alue is 1. Default: 3 seconds Number of bytes to use to sae last eent The number of bytes the Situation Update Forwarder uses when it saes the location of the last eent it processed. Chapter 2. Deploying the Solutions for BSM 59

72 Default: 50 Rate for sending SOAP requests from the Situation Update Fowarder to the Tioli Enterprise Monitoring Serer The maximum number of eent updates sent at one time from the Situation Update Fowarder to the hub Tioli Enterprise Monitoring Serer. Default: 10 Logging detail leel The detail leel for information that is logged for eent synchronization. The alues are low, med, and erbose. Default: low Maximum size of any single cache file The maximum size in bytes for any one eent cache file used by the Situation Update Fowarder. Default: 5000 Maximum number of cache files The maximum number of eent cache files used by Situation Update Fowarder at one time. The minimum alue is 2. Default: 10 Cache files directory The location where the Situation Update Forwarder eent cache files are stored. Default: /opt/ibm/sitfowarder/persistence TEMS hub host name The fully qualified host name for the computer where the hub Tioli Enterprise Monitoring Serer is running. The host name must match the name included in eents from the hub serer. TEMS user name The user account on your Tioli Enterprise Monitoring Serer machine. TEMS password Password for the user. Verify password. Verify the password. Adanced In the Adanced tab, you can also choose whether you want to: Use temp directory - Specify a different temporary directory to use if the system default temporary directory does not hae enough free space. This task requires a temporary directory with a minimum of 2 GB of free space. Skip Pre Deployment Check The default for each option is No. Netcool/OMNIbus and Tioli Monitoring eent configuration This task configures Netcool/OMNIbus for IBM Tioli Monitoring eents. 60 Solutions for BSM Guide:

73 Purpose This task deploys these schemas to your ObjectSerer database: itm_proc.sql itm_sync.sql itm_db_update.sql itm_eent_cache.sql These updates enable Netcool/OMNIbus to manage the situations eents that were created with the Deploy Best Practice Monitoring task. The naigation frame shows the task: Configure Configure OMNIbus for ITM Eents Linux Configure OMNIbus schema for ITM Eents Parameters Scroll down to see all the parameters. Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). Default: NCOMS ObjectSerer user name The user name. Default: root ObjectSerer password The password for user name. Verify password Verify the password. ITM Eent Synchronization (Situation Forwarder) directory The directory where you installed the Situation Update Forwarder. Default: /opt/ibm/sitforwarder Specify if the ObjectSerer is configured for process agent... If the ObjectSerer is configured for the Netcool/OMNIbus process agent, enter information about the process agent configuration. Note: The Situation Update Forwarder only starts automatically if the ObjectSerer is configured for the process agent. Default: Yes If you select Yes, enter these parameters: Process Agent serer name The process agent name for your ObjectSerer host. Process agents are programs that are installed on each host to manage processes Chapter 2. Deploying the Solutions for BSM 61

74 in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA ObjectSerer process name The ObjectSerer process name as defined for process agent. For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. ObjectSerer process user name The user that runs the ObjectSerer process defined for process agent. Default: root ObjectSerer process password The user password. Verify password Verify the password. OS architecture Operating system architecture. Default: linux2x86 Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Modify Netcool/OMNIbus default deduplication trigger This task modifies the Netcool/OMNIbus deduplication trigger. Purpose This task modifies the default deduplication trigger for the IBM Solutions for Business Serice Management. The naigation frame shows the task: Configure Modify OMNIbus default deduplication trigger Linux Modify default deduplication trigger Parameters Scroll down to see all the parameters. Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). 62 Solutions for BSM Guide:

75 Default: NCOMS ObjectSerer user name The user name. Default: root ObjectSerer password The password for user name. Verify password Verify the password. Is ObjectSerer configured for process agent? If the ObjectSerer is configured for the Netcool/OMNIbus process agent, enter information about the process agent configuration. Default: No If you select Yes, enter these parameters: Process Agent serer name The process agent name for your ObjectSerer host. Process agents are programs that are installed on each host to manage processes in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA ObjectSerer process name The ObjectSerer process name as defined for process agent. For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. ObjectSerer process user name The user that runs the ObjectSerer process defined for process agent. Default: root ObjectSerer process password The user password. Verify password Verify the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Netcool/OMNIbus ITCAM Eent configuration This task configures the Tioli Eent Integration Facility probe (EIF probe) rules and Netcool/OMNIbus for ITCAM eents. Purpose This task runs the omnibusupdater.sh to add these rules files for the EIF probe: kt3.rules - Application Management Console (AMC) Chapter 2. Deploying the Solutions for BSM 63

76 kt4.rules - Client Response Time (CRT) kt5.rules - Web Response Time (WRT) kt6.rules - Robotic Response Time (RRT) kto.rules - Transaction Tracking (TT) 64 Solutions for BSM Guide: These rules enable the EIF probe to normalize the ITCAM situation eents and forward them to Netcool/OMNIbus as eents. This task also updates the Netcool/OMNIbus to enable eent management for the ITCAM products. These updates enable Netcool/OMNIbus to manage the eents related to components configured in the Deploy Best Practice ITCAM Monitoring task. Important: To complete this task, you must also customize the itm_eent_cache.sql file for the ITCAM attributes. For more information, see the subsequent task. The naigation frame shows the task: Configure Configure OMNIbus Schema and rules for ITCAM Eents LNX Configure OMNIbus for ITCAM Eents Parameters Scroll down to see all the parameters. Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). Default: NCOMS ObjectSerer user name The user name. Default: root ObjectSerer password The password for user name. Verify password Verify the password. Specify if the ObjectSerer is configured for process agent... If the ObjectSerer is configured for the Netcool/OMNIbus process agent, enter information about the process agent configuration. Note: The Situation Update Forwarder starts automatically only if the ObjectSerer is configured for the process agent. Default: Yes If you select Yes, enter these parameters:

77 Process Agent serer name The process agent name for your ObjectSerer host. Process agents are programs that are installed on each host to manage processes in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA ObjectSerer process name The ObjectSerer process name as defined for process agent. For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. ObjectSerer process user name The user that runs the ObjectSerer process defined for process agent. Default: root ObjectSerer process password The user password. Verify password Verify the password. OS architecture Operating system architecture. Default: linux2x86 Specify if the EIF probe is configured for process agent If the EIF probe is configured for the process agent, select Yes, and enter the process name. Default: No EIF probe process name The EIF probe process name as defined for process agent. Processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Customizing the ITCAM integration for ITM eent caching If you configure the OMNIbus schema, and rules for ITCAM eents, you must update the OMNIbus table and triggers used to cache sampled monitoring agent eents that were cleared in OMNIbus. Before you begin Before you begin, you must complete these deployment tasks in this order: 1. Deploy Eent Manager Customizations ->Configure OMNIbus for ITM Eents (Netcool/OMNIbus Tioli Monitoring eent configuration) Chapter 2. Deploying the Solutions for BSM 65

78 66 Solutions for BSM Guide: 2. Deploy Eent Manager Customizations -> Configure OMNIbus Schema and rules for ITCAM Eents (Netcool/OMNIbus ITCAM Eent configuration) About this task The sampled monitoring agent eents that were cleared in OMNIbus are temporarily cached so that the full set of eent data can be restored from the cache if the situation eent condition is still true and the sampled eent is re-opened by IBM Tioli Monitoring. To update the OMNIbus eent cache table and triggers, perform the following procedure on the computer where the OMNIbus ObjectSerer is installed: Procedure 1. Open the itm_eent_cache.sql file using a text editor. The file is located in the eent_sync_install_dir/omnibus directory where eent_sync_install_dir is the directory where the IBM Tioli Monitoring eent synchronization component is installed. 2. Find the line that contains --NewAttributeGoesHere type(size), and add the following lines after it: CAM_Application_Name archar(128), CAM_Transaction_Name archar(128), CAM_SubTransaction_Name archar(128), CAM_Client_Name archar(128), CAM_Serer_Name archar(128), CAM_Profile_Name archar(128), CAM_Response_Time archar(30), CAM_Percent_Aailable archar(10), CAM_Expected_Value archar(128), CAM_Actual_Value archar(128), CAM_Details archar(1024), CAM_Total_Requests integer, 3. Find the line that contains --statusr.newattributegoeshere, and add the following lines after it: statusr.cam_application_name, statusr.cam_transaction_name, statusr.cam_subtransaction_name, statusr.cam_client_name, statusr.cam_serer_name, statusr.cam_profile_name, statusr.cam_response_time, statusr.cam_percent_aailable, statusr.cam_expected_value, statusr.cam_actual_value, statusr.cam_details, statusr.cam_total_requests, 4. Find the line that contains --set new.newattributegoeshere = cachedeent.newattributegoeshere ;, and add the following lines after it: new.cam_application_name = cachedeent.cam_application_name ; new.cam_transaction_name = cachedeent.cam_transaction_name ; new.cam_subtransaction_name = cachedeent.cam_subtransaction_name ; new.cam_client_name = cachedeent.cam_client_name ; new.cam_serer_name = cachedeent.cam_serer_name ; new.cam_profile_name = cachedeent.cam_profile_name ; new.cam_response_time = cachedeent.cam_response_time ; new.cam_percent_aailable = cachedeent.cam_percent_aailable ; new.cam_expected_value = cachedeent.cam_expected_value ; new.cam_actual_value = cachedeent.cam_actual_value ; new.cam_details = cachedeent.cam_details ; new.cam_total_requests = cachedeent.cam_total_requests ;

79 5. Update the OMNIbus database schema by using this command: $OMNIHOME/bin/nco_sql -user username -password password -serer serer_name < path_to_file/itm_eent_cache.sql where $OMNIHOME is the system-defined ariable defining the installation location of OMNIbus. username is the OMNIbus ObjectSerer user name. password is the OMNIbus ObjectSerer password. serer_name is the OMNIbus ObjectSerer name defined for process control. path_to_file is the fully qualified path to the itm_eent_cache.sql file. You do not hae to restart the ObjectSerer to enable these changes. For more information about eents and agents, see the Tioli Monitoring Information Center at: com.ibm.itm.doc_6.2.3fp1/ itm623fp1_install641.htm?path=3_0_3_0_9_1_5_1#genmap Configure Solutions for BSM Netcool/OMNIbus schema This task modifies the Netcool/OMNIbus ObjectSerer schema to support the IBM Solutions for Business Serice Management. Purpose This task runs the nco_sql command and bsm_accelerator_schema.sql schema to configure the Netcool/OMNIbus schema for Solutions for BSM. The naigation frame shows the task: Configure Configure OMNIbus Schema for IBM Solutions for Business Serice Management LNX Configure OMNIbus for BSM Parameters Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). Default: NCOMS ObjectSerer user name The user name. Default: root ObjectSerer password The password for user name. Chapter 2. Deploying the Solutions for BSM 67

80 Verify password Verify the password. Specify if the ObjectSerer is configured for process agent... If the ObjectSerer is configured for the Netcool/OMNIbus process agent, enter information about the process agent configuration. Default: No If you select Yes, enter these parameters: Process Agent serer name The process agent name for your ObjectSerer host. Process agents are programs that are installed on each host to manage processes in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA ObjectSerer process name The ObjectSerer process name as defined for process agent. For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. ObjectSerer process user name The user that runs the ObjectSerer process defined for process agent. Default: root ObjectSerer process password The user password. Verify password Verify the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configure EIF probe for ITM eents This task configures the Tioli Eent Integration Facility probe (EIF probe) rules for IBM Tioli Monitoring eents. Purpose This task copies and enables the rules files you need to conert situation eents to IBM Tioli Netcool/OMNIbus eents. TBSM correlates these eents with business serices. The rules files are: itm_eents.rules - generic Tioli Monitoring situation handling tbsm_eif_eent.rules - EIF eent handling for TBSM km_tbsm.rules- VMware agent situation handling 68 Solutions for BSM Guide:

81 These rules enable the EIF probe to normalize the situation eents and forward them to Netcool/OMNIbus as eents. These situation eents were configured in the Deploy Best Practice Monitoring task. The naigation frame shows the task: Configure Configure EIF Probe Schema for ITM Eents Linux Configure EIF Probe Schema for ITM Eents Parameters Scroll down to see all the parameters. Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). Default: NCOMS ITM Eent Synchronization (Situation Forwarder) directory The directory where you installed the Situation Update Forwarder. Default: /opt/ibm/sitforwarder Specify if the EIF probe is configured for process agent If the EIF probe is configured for the process agent, select Yes, and enter the process name. Default: No Process Agent serer name The process agent name for your host. Process agents are programs that are installed on each host to manage processes in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA EIF probe process name For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. Processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. Process agent user name The user that runs the EIF probe process defined for process agent. Default: root Process agent password The user password. Verify password Verify the password. Adanced Chapter 2. Deploying the Solutions for BSM 69

82 In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configure EIF probe for TADDM eents This task enables the Tioli Eent Integration Facility probe (EIF probe) rules for the IBM Tioli Application Dependency Discoery Manager integration. Purpose This task enables the tioli_eif_taddm.rules file for the TADDM integration. The naigation frame shows the task: Configure Configure EIF Probe for TADDM Linux Configure EIF Probe or TADDM Parameters Scroll down to see all the parameters. Specify these parameters: Netcool home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool ObjectSerer name The name of the ObjectSerer configured for IBM Tioli Business Serice Manager (TBSM). Default: NCOMS OS Architecture Operating system for the EIF probe. Default: linux2x86 Specify if the EIF probe is configured for process agent If the EIF probe is configured for the process agent, select Yes, and enter the process name and user information. Default: No Process Agent serer name The process agent name for your host. Process agents are programs that are installed on each host to manage processes in a process control system. Any participating host must hae a process agent and an associated configuration file installed. By default, the first process agent installed in a configuration is named NCO_PA. Default: NCO_PA EIF probe process name For the default NCO_PA process agent, the processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. Processes are defined in the $NCHOME/omnibus/etc/nco_pa.conf configuration file. 70 Solutions for BSM Guide:

83 Process agent user name The user that runs the EIF probe process defined for process agent. Default: root Process agent password The user password. Verify password Verify the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for this option is No. Summary for Eent Customizations deployment After you specify information for the Eent Customization main tasks, the Summary panel lets you choose how to run the deployment. Purpose The naigation frame shows the task: Summary Deploy TBSM customizations You can run the deployment for each task one at a time, or you can run them all at once. To run a task by itself, click Deploy Task for the task you want to run. To deploy all the tasks in the summary, click Deploy all. Deploys the modifications to IBM Tioli Business Serice Manager. Before you begin Before you deploy the TBSM customizations, log in to the TBSM serer as the installation user or specify those credentials when connecting to a remote TBSM machine. If you are local to one of the TBSM serers, you cannot change the credentials once your start. The naigation frame shows the task: Select Tasks Deploy TBSM Customizations Important: You must complete the Configure OMNIbus Schema and Rules for ITCAM eents and Configure OMNIbus Schema for IBM Solutions for Business Serice Management tasks before you start this task. These tasks are part of the Deploy Eent Manager Customizations task group. Chapter 2. Deploying the Solutions for BSM 71

84 About this task To deploy TBSM modifications: Procedure 1. Select TBSM Customizations. 2. Click Next. 3. The Deployment wizard guides you through these high-leel steps: TBSM Data Serer Customizations This task configures the TBSM data serer to support the Solutions for BSM. These modifications include updates to: Serice templates Data fetchers Discoery Library Toolkit Netcool/Impact policies. TBSM Dashboard Serer Components This task deploys a WAR file to the TBSM Tioli Integrated Portal profile and adds the System Status and Health pages to the TBSM dashboard. Web GUI Customizations This task configures the appropriate iew and filter to support the Solutions for BSM. 4. For each task you specify the target computer and configuration information. Specify target computer for deployment Specify the target computer where you want to deploy the packages. Configuration For each option, you specify information about your TBSM enironment. 5. For more details about deploying the customizations, see the subsequent topics. Deploying a Data serer in a failoer enironment A failoer enironment contains a primary and backup Data serer. If the primary host fails or the network connection between the primary and backup serers is lost, the backup serer takes oer the processes of the primary serer. This topic outlines the considerations when configuring failoer for Solutions for Business Serice Management. For complete information about installing failoer for TBSM, see the TBSM Installation Guide. In addition to these requirements, the additional requirements for Solutions for Business Serice Management are: You must run the run the Deployment Wizard on both you primary and backup Data serers. Deploy Single Sign-On on both the primary and backup Data serers. Specifying target computer for TBSM tasks Specify the hosts where you want to deploy the TBSM packages. 72 Solutions for BSM Guide:

85 Before you begin Before you begin this task, gather information for: Specify Targets TBSM Data Serer Customizations TBSM Dashboard Serer Components Web GUI Customizations Before deploy the TBSM modifications, know your TBSM Data and Dashboard serer host names and credentials. Specify the appropriate host for each main task: Task where the Data serer host is the target TBSM Data Serer Customizations Tasks where the Dashboard serer host is the target: TBSM Dashboard Serer Components Web GUI Customizations About this task To deploy the integration package. Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. Chapter 2. Deploying the Solutions for BSM 73

86 Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Configure TBSM data serer This task configures the IBM Tioli Business Serice Manager data serer for IBM Solutions for Business Serice Management. Purpose This task deploys components to the data serer such as: Data fetchers Discoery Library Toolkit artifacts. Netcool/Impact policies.. The naigation frame shows the task: Configure Configure TBSM Data Serer Customizations Linux TBSM Data Serer for Accelerator Parameters Scroll down to see all the parameters. Specify these parameters: TBSM Data serer admin user name The user name with administrator permissions. Default: tipadmin TBSM Data serer admin password The password for the user with administrator permissions. Verify password Re-enter the password. TBSM Home directory The fully qualified path where the data serer is installed. Default: /opt/ibm/tioli/tbsm TBSM Data serer database user name The name of a user that the data serer uses to access the TBSM DB2 database. Default: None. TBSM Data serer database password The password for the Data serer database user name. Verify password Re-enter the password. 74 Solutions for BSM Guide:

87 Is the TIP Web Serice (ITM WebSerice) aailable on the Tioli Enterprise Portal Serer (TEPS) Specify if you want to configure the Data Serer for the IBM Tioli Monitoring web serice. TBSM uses this web serice for Tioli Monitoring policy-based data fetchers Default: No If you select Yes, specify these additional parameters: Tioli Enterprise Portal Serer Host Name Host name for your Tioli Enterprise Portal serer. Tioli Enterprise Portal Serer administrator ID User name of the Tioli Enterprise Portal Serer administrator. Tioli Enterprise Portal Serer administrator password Password of the Tioli Enterprise Portal Serer administrator. Verify password Re-enter the password. TIP Web Serice Name configured on the Tioli Enterprise Portal Serer The name of the ITM Web serice. Default: TIPWebSererHttpRouter ITM Web Serice Port Number configured on the Tioli Enterprise Portal Serer The port number that the web serice is listening on. Typically this port is for http and for https. Default: Select the ITM Web Serer Protocol configured on the Tioli Enterprise Portal Serer Select either http or https. Specify agents deployed in your Tioli Monitoring enironment. Select Yes for each of the agents that are deployed in your Tioli Monitoring enironment. Defaults: No To enable all the features of the Solutions for BSM, select Yes for all the agents. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configure TBSM Dashboard serer This task configures the IBM Tioli Business Serice Manager Dashboard serer for IBM Solutions for Business Serice Management. Purpose This task deploys the WAR file for the consolidated operations dashboard feature of the IBM Solutions for Business Serice Management.. The naigation frame shows the task: Chapter 2. Deploying the Solutions for BSM 75

88 Configure Configure TBSM Dashboard Serer Components Linux Deploy Consolidated Operations WAR file to the TBSM Dashboad Serer (TIP) Parameters Note: If you are deploying Solutions for BSM in a Tioli Integrated Portal load balancing enironment, you must remoe each Tioli Integrated Portal from the load balancing cluster before deploying TBSM Dashboard serer components. For more information, see publib.boulder.ibm.com/infocenter/tiihelp/3r1/topic/ com.ibm.tioli.itbsm.doc_6.1/tip/ttip_config_ha_unjoin.html. Specify these parameters: TIP Home directory The fully qualified path where Tioli Integrated Portal serer is installed. Default: /opt/ibm/tioli/tip2 TIP administrator user name The user name with administrator permissions. Default: tipadmin TIP administrator password The password for the user with administrator permissions. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configure Web GUI customizations This task configures the IBM Tioli Netcool/OMNIbus Web GUI for IBM Solutions for Business Serice Management. Before you begin Before beginning this task, complete the steps in the topics: Configure OMNIbus Schema and Rules for ITCAM Eents Configure OMNIbus Schema for IBM Solutions for Business Serice Management contained in the Deploy Eent Management Customizations section of this guide. Purpose The Solutions for BSM deployment wizard adds the BSMAccelerator_Health iew and filter to the Web GUI. This task the Web GUI components for the Solutions for BSM. The naigation frame shows the task: 76 Solutions for BSM Guide:

89 Configure Configure Web GUI Customizations Tioli Netcool/OMNIbus Web GUI Parameters Specify these parameters: Netcool Home directory The fully qualified path where Netcool/OMNIbus is installed. Default: /opt/ibm/tioli/netcool TBSM administrator user name The user name with administrator permissions. Default: tbsmadmin TBSM administrator password The password for the user with administrator permissions. TBSM administrator password The password for the user with administrator permissions. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Deploy a Single Sign-On configuration Single Sign-On can be configured to allow you to launch in context between IBM Tioli Business Serice Manager (TBSM) and IBM Tioli Application Dependency Discoery Manager (TADDM) or between TBSM and the Tioli Enterprise Portal Serer (TEPS) without haing to enter login details for each application. The Deploy Single Sign-On option in the IBM Solutions for Business Serice Management deployment accelerator is used to set up Single Sign-On. The steps in the process outlined in this task must be followed in the sequence listed. Howeer, you can skip any steps that do not apply to your configuration. To ensure that Single Sign-On works correctly after configuration, TBSM, TADDM, and Tioli Enterprise Portal Serer must be configured so that they: authenticate against a common central user repository such as an LDAP serer specify the same SSO domain, for example, mycompany.com share a common set of Lightweight Third Party Authentication (LTPA) keys use the same Federated repository realm name. use the same base entry name to define users in the common LDAP repository. You can complete one or more of the Single Sign-On steps proided in the deployment wizard to complete a Single Sign-On configuration depending on the number of products inoled and any existing configuration that might already be in place. For example, you can skip the LDAP-related steps if the participating products are already configured for an LDAP serer. The full set of configuration steps is: Chapter 2. Deploying the Solutions for BSM 77

90 1. Configure the TBSM Dashboard serer for LDAP. 2. Configure the TBSM Dashboard serer for Single Sign-On. 3. Configure the TBSM Data serer for LDAP. 4. Configure the TADDM WebSphere serer for LDAP. 5. Configure the TADDM WebSphere serer for the Virtual Member Manager Serice EJB 6. Configure the TADDM WebSphere serer for Single Sign-On. 7. Export the LTPA keys from the TBSM Dashboard serer 8. Import the LTPA keys into the TADDM WebSphere serer 9. Configure the TADDM Connection to the TADDM WebSphere serer 10. Configure ITM and import the LTPA keys The considerations for each of these steps is outlined in the topics in this section. Prerequisites for Single Sign-On configuration There are a number of configuration files that are modified by the Single Sign-On configuration process. Not all of these files are backed up during this process. This topic discusses the configuration files for which you must create backup copies and outlines the location of backup configuration files created by the Single Sign-On installer. Backing up WebSphere Application Serer configuration files Create backup copies of the WebSphere Application Serer configuration files before you run the Single Sign-On installer. These files are modified during the Single Sign-On configuration and the Single Sign-On installer does not create backup copies of the files. TBSM Dashboard serer TIP_HOME/profiles/TIPProfile/config/cells/TIPCell/security.xml TIP_HOME/profiles/TIPProfile/config/cells/TIPCell/wim/config/ wimconfig.xml TIP_HOME/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/ ltpa.jceks TBSM Data serer TIP_HOME/profiles/TBSMProfile/config/cells/TBSMCell/wim/config/ wimconfig.xml WebSphere serer Used by TADDM WAS_HOME/profiles/<profileName>/config/cells/<cellName>/ security.xml WAS_HOME/profiles/<profileName>/config/cells/<cellName>/wim/ config/wimconfig.xml WAS_HOME/profiles/<profileName>/config/cells/<cellName>/nodes/ <nodename>/ltpa.jceks where: <profilename> is replaced with the profile name of the WebSphere serer that is used by TADDM <cellname> is replaced with the cell name of the WebSphere serer that is used by TADDM 78 Solutions for BSM Guide:

91 <nodename> is replaced with the node name of the WebSphere serer that is used by TADDM ITM TEPS Serer ITM_HOME/<arch>/iw/profiles/ITMProfile/config/cells/ITMCell/ security.xml ITM_HOME/<arch>/iw/profiles/ITMProfile/config/cells/ITMCell/wim/ config/wimconfig.xml ITM_HOME/<arch>/iw/profiles/ITMProfile/config/cells/ITMCell/nodes/ ITMNode/ltpa.jceks where <arch> is replaced with the platform architecture directory name. For example, li6263. Backing up TADDM configuration files As the deployment step Configure TADDM Connection to TADDM WebSphere Serer edits the TADDM configuration directly, backup copies of the TADDM configuration files listed are automatically created and placed in the directory that you enter during that step: COLLATION_HOME/etc/collation.properties COLLATION_HOME/etc/ibmessclientauthnconfig.properties COLLATION_HOME/etc/sas.client.props Backup files are created with a timestamp suffix indicating the time that the step was executed. Specifying the target computer for Single Sign-on tasks Specify the hosts where you want to deploy the Single Sign-On configuration. Before you begin The naigation frame shows the tasks: Specify Targets Configure the TBSM Dashboard serer for LDAP. Configure the TBSM Dashboard serer for Single Sign-On. Configure the TBSM Data serer for LDAP. Configure the TADDM WebSphere serer for LDAP. Configure the TADDM WebSphere serer for the Virtual Member Manager Serice EJB Configure the TADDM WebSphere serer for Single Sign-On. Export the LTPA keys from the TBSM Dashboard serer Import the LTPA keys into the TADDM WebSphere serer Configure the TADDM Connection to the TADDM WebSphere serer Configure ITM and import the LTPA keys Before completing this task, know your serer host names and credentials. Specify the appropriate host for each main task. The target machine is the host for the product listed in the task description. Chapter 2. Deploying the Solutions for BSM 79

92 Tasks where the Dashboard serer host is the target: Configure the TBSM Dashboard serer for LDAP Configure the TBSM Dashboard serer for Single Sign-On Export the LTPA keys from the TBSM Dashboard serer Task where the TBSM Data serer host is the target Configure the TBSM Data serer for LDAP. Tasks where the TADDM host is the target Configure the TADDM Connection to the TADDM WebSphere serer Tasks where the host running the WebSphere serer used by TADDM is the target: Configure the TADDM WebSphere serer for LDAP Configure the TADDM WebSphere serer for the Virtual Member Manger Serice EJB Configure the TADDM WebSphere serer for Single Sign-On. Import the LTPA keys into the TADDM WebSphere serer Task where the Tioli Enterprise Portal Serer host is the target Configure ITM and import the LTPA keys About this task To specify a target host: Procedure 1. Enter the host name or IP address in the Target Computer field. 2. Click Add and the Target Computer Credentials window opens. 3. In the Target Computer Credentials window specify: Operating system Select Linux x86 32 Bit or Linux x86 64 Bit from the drop-down list. This release only supports Red Hat Enterprise Linux ersion 5. User ID The user account with the permissions needed for this task. If you are going to be deploying configuration elements to the local machine, you must be logged in as the user who originally installed the associated Tioli product. You do not hae the opportunity to specify a different installation user for the local host. For any other remote machine, you will hae the opportunity to specify the user ID and password for the target machine. Password Password for the user account. Sae this login information Select this option if you want to sae the target computer credentials for use in another task. 4. To test the credentials, click Test Login. A message displays indicating whether the test succeeded or failed. 5. Click Add and the computer name is added to the Selected target computer list. 80 Solutions for BSM Guide:

93 Attention: If you enter incorrect target machine information, and then remoe that target from the list, the Deployment Wizard may continue to use the incorrect target machine information. If this error occurs, exit the Deployment Wizard and start it again. The wizard will now function correctly. 6. To modify the computer credentials, click on the computer name and click Edit and the Target Computer Credentials window opens for the computer you selected. 7. Click Next. Configuring the TBSM Dashboard serer for LDAP This task configures a TBSM Dashboard Serer for an LDAP user repository. The considerations that you must take into account when configuring the TBSM Dashboard serer for LDAP are: The Dashboard serer profile TIPProfile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the Dashboard serer TIPProfile so that the configuration can take effect. If you want to use LDAP and hae not already installed TBSM, complete an adanced installation of TBSM and select the file-registry option as the repository. After the installation completes, follow the steps in this procedure to configure the Dashboard serer for LDAP. If TBSM has already been installed with a Netcool/OMNIbus user repository, you can complete this step to configure the Dashboard serer for LDAP as an additional repository. Howeer, you must ensure that the same users and groups do not exist in both repositories. If configuring the Dashboard serer for LDAP results in duplicate users and groups, you must remoe the Netcool/OMNIbus user repository from the TBSM configuration before running this step or ensure that the same users and groups are not defined in both repositories. If you are configuring Single Sign-On for an existing TBSM enironment already configured for LDAP, you can skip this step. For the LDAP Repository Name, required as an input parameter, enter any name that uniquely identifies the repository within the WebSphere configuration for the Dashboard serer. TBSM Dashboard serer LDAP settings This task configures the IBM Tioli Business Serice Manager (TBSM) Dashboard serer for Lightweight Directory Access Protocol (LDAP). Purpose This task configures the Dashboard serer for LDAP. The naigation frame shows the task: Configure Configure TBSM Dashboard Serer for LDAP Configure TBSM Dashboard Serer for LDAP Parameters Specify these parameters: TBSM Home directory The fully qualified path where the Dashboard serer is installed. Default: /opt/ibm/tioli/tbsm Chapter 2. Deploying the Solutions for BSM 81

94 Tioli Integrated Portal (TIP) user name The user name with administrator permissions. Default: tipadmin Tioli Integrated Portal (TIP) password The password for the user with administrator permissions. Verify password Re-enter the password. LDAP serer type Select your LDAP serer type from the drop-down list. If your serer type is not on the list, select Other and enter your LDAP serer type. LDAP repository name The repository name. This name must be unique in the TBSM serer realm configuration. Default: accelerator_ldap LDAP host name The fully qualified name or IP address for your LDAP host. LDAP port The port number for your LDAP host. Default: 389 For SSL configuration the default is typically 636. LDAP bind password Bind password for the repository. SSL enabled Specify whether the repository is enabled for Secure Socket Layer (SSL). Default: No SSL configuration Specify the SSL configuration name. For example: NodeDefaultSSLSettings. LDAP bind DN The LDAP user name for bind authentication. The LDAP user name must be authorized to search for LDAP users. For example: cn=root. LDAP base The LDAP base used in searches for your LDAP serer. Contact your LDAP administrator for this alue. For example, ou=deelopment,dc=ibm,dc=com Realm name To obtain the name of the default realm, issue the following wsadmin command: $AdminTask getidmgrdefaultrealm VMMRealmName=defaultWIMFileBasedRealm Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. 82 Solutions for BSM Guide:

95 Configuring the TBSM Dashboard serer for Single Sign-On This step enables Single Sign-On on the TBSM Dashboard serer and sets the Single Sign-On domain name to the specified input alue. The same Single Sign-On domain name must be used for all products participating within the Single Sign-On domain. By default, Single Sign-On is enabled on the Dashboard serer. This step, howeer, sets the domain name to the alue you enter. The Dashboard Serer profile TIPProfile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the Dashboard Seer TIPProfile so that the configuration can take effect. TBSM Dashboard serer Single Sign-on settings This task configures the IBM Tioli Business Serice Manager (TBSM) Dashboard serer for Single Sign-On. Purpose This task configures the Dashboard serer for Single Sign-On. The naigation frame shows the task: Configure Configure TBSM Dashboard Serer for Single Sign-On Configure TBSM Dashboard Serer for Single Sign-On Parameters Specify these parameters: TBSM Home directory The fully qualified path where the Dashboard serer is installed. Default: /opt/ibm/tioli/tbsm Tioli Integrated Portal (TIP) user name The user name with administrator permissions. Default: tipadmin Tioli Integrated Portal (TIP) password The password for the user with administrator permissions. Verify password Re-enter the password. SSO domain name Enter the Single Sign-On domain name you want to use. For example, ibm.com. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Chapter 2. Deploying the Solutions for BSM 83

96 Configuring the TBSM Data serer for LDAP This step configures a TBSM Data serer for an LDAP user repository. The considerations that you must take into account when configuring the TBSM Data serer for LDAP are: The Data serer profile TBSMProfile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the Data serer TBSMProfile so that the configuration can take effect. If you want to use LDAP and hae not already installed TBSM, complete an adanced installation of TBSM and select the file-registry option as the repository. After the installation completes, follow the steps in this procedure to configure the Data serer for LDAP. If TBSM has already been installed with a Netcool/OMNIbus user repository, you can complete this step to configure the Data serer for LDAP as an additional repository. Howeer, you must ensure that the same users and groups do not exist in both repositories. If configuring the Data serer for LDAP results in duplicate users and groups, you must remoe the Netcool/OMNIbus user repository from the TBSM configuration before running this step or ensure that the same users and groups are not defined in both repositories. If you are configuring Single Sign-On for an existing TBSM enironment already configured for LDAP, you can skip this step. For the LDAP Repository Name, required as an input parameter, enter any name that uniquely identifies the repository within the WebSphere configuration for the Data serer. TBSM Data serer LDAP settings This task configures the IBM Tioli Business Serice Manager (TBSM) Data serer for Lightweight Directory Access Protocol (LDAP). Purpose This task configures the Data serer for LDAP. The naigation frame shows the task: Configure Configure TBSM Data Serer for LDAP Configure TBSM Data Serer for LDAP Parameters Specify these parameters: TBSM Home directory The fully qualified path where the Data serer is installed. Default: /opt/ibm/tioli/tbsm Tioli Integrated Portal (TIP) user name The user name with administrator permissions. Default: tipadmin Tioli Integrated Portal (TIP) password The password for the user with administrator permissions. Verify password Re-enter the password. 84 Solutions for BSM Guide:

97 LDAP serer type Select your LDAP serer type from the drop-down list. If your serer type is not on the list, select Other and enter your LDAP serer type. LDAP repository name The repository name. This name must be unique in the TBSM serer realm configuration. Default: accelerator_ldap LDAP host name The fully qualified name or IP address for your LDAP host. LDAP port The port number for your LDAP host. Default: 389 For SSL configuration the default is typically 636. LDAP bind password Bind password for the repository. SSL enabled Specify whether the repository is enabled for Secure Socket Layer (SSL). Default: No SSL configuration Specify the SSL configuration name. For example: NodeDefaultSSLSettings. LDAP bind DN The LDAP user name for bind authentication. The LDAP user name must be authorized to search for LDAP users. For example: cn=root. LDAP base The LDAP base used in searches for your LDAP serer. Contact your LDAP administrator for this alue. For example, ou=deelopment,dc=ibm,dc=com Realm name To obtain the name of the default realm, issue the following wsadmin command: $AdminTask getidmgrdefaultrealm VMMRealmName=defaultWIMFileBasedRealm Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configuring the TADDM WebSphere serer for LDAP This step configures a stand-alone WebSphere serer to use an LDAP user repository. The considerations that you must take into account when configuring the TADDM WebSphere serer for LDAP are: If you are configuring Single Sign-On for an existing TADDM enironment where TADDM is already connected to a WebSphere serer that authenticates against your LDAP serer, you can skip this step. The specified serer profile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the WebSphere serer so that the configuration can take effect. Chapter 2. Deploying the Solutions for BSM 85

98 This WebSphere serer is used by TADDM for authentication. As TADDM does not run within WebSphere, it must be connected to a WebSphere serer to participate in the Single Sign-On domain. The WebSphere serer allows TADDM to: access user and group information from the underlying central user repository to which the WebSphere instance is configured authenticate and alidate a Lightweight Third Party Authentication (LTPA) token passed in during the launch. This token alidation requires the use of the Embedded Security Serice (ESS) component which must be installed on the WebSphere instance to which TADDM is connected. As the ESS is a Tioli component and not a product, it cannot be separately obtained and installed/deployed. ESS is only installed as part of a product that includes it. Examples of products that proide ESS as a component are TBSM and CCMDB. For the LDAP Repository Name, required as an input parameter, enter any name that uniquely identifies the repository within the WebSphere configuration for the TADDM serer. The specified serer profile must be running for this step to complete successfully. As part of its processing, this step will automatically restart the WebSphere serer so that the configuration can take effect. TADDM Websphere LDAP settings This task configures the IBM Tioli Application Dependency Discoery Manager (TADDM) Websphere serer for Lightweight Directory Access Protocol (LDAP). Purpose This task configures the TADDM Websphere serer for LDAP. You need to configure LDAP before you can use Single Sign-On when launching in context from TBSM to TADDM. The naigation frame shows the task: Configure Configure TADDM Websphere Serer for LDAP Configure TADDM Websphere Serer for LDAP Parameters Scroll down to see all the parameters. Specify these parameters: WAS Home directory The fully qualified path where the TADDM Websphere Application Serer is installed. Default: /usr/websphere/appserer WAS profile name The Websphere Application Serer profile name. Default: Default WAS administrator user name The user name with administrator permissions. Default: admin 86 Solutions for BSM Guide:

99 WAS password The password for the user with administrator permissions. Verify password Re-enter the password. LDAP serer type Select your LDAP serer type from the drop-down list. If your serer type is not on the list, select Other and enter your LDAP serer type. LDAP repository name The repository name. This name must be unique in the TBSM serer realm configuration. Default: accelerator_ldap LDAP host name The fully qualified name or IP address for your LDAP host. LDAP port The port number for your LDAP host. Default: 389 For SSL configuration the default is typically 636. LDAP bind password Bind password for the repository. SSL enabled Specify whether the repository is enabled for Secure Socket Layer (SSL). Default: No SSL configuration Specify the SSL configuration name. For example: NodeDefaultSSLSettings. LDAP bind DN The LDAP user name for bind authentication. The LDAP user name must be authorized to search for LDAP users. For example: cn=root. LDAP base The LDAP base used in searches for your LDAP serer. Contact your LDAP administrator for this alue. For example, ou=deelopment,dc=ibm,dc=com Realm name To obtain the name of the default realm, issue the following wsadmin command: $AdminTask getidmgrdefaultrealm VMMRealmName=defaultWIMFileBasedRealm Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configure the TADDM WebSphere Serer for the Virtual Member Manager Serice EJB This step deploys the wimejb JAR file to the stand-alone WebSphere serer used by TADDM within the Single Sign-On enironment. The wimejb JAR file must be Chapter 2. Deploying the Solutions for BSM 87

100 added to allow TADDM to read user and group information from the LDAP repository through the WebSphere serer. The considerations that you must be aware of when completing this step are: If you are configuring Single Sign-On for an existing TADDM enironment where TADDM is already connected to a WebSphere serer that authenticates against your LDAP serer, you can skip this step. The specified serer profile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the WebSphere serer so that the configuration can take effect. TADDM WebSphere Serer for the Virtual Member Manager settings This task configures the IBM Tioli Application Dependency Discoery Manager (TADDM) Websphere serer for the Virtual Member Manager Serice EJB. Purpose This task deploys the wimejb JAR file to the stand-alone WebSphere serer used by TADDM within the Single Sign-On enironment. The wimejb JAR file must be added to allow TADDM to read user and group information from the LDAP repository through the WebSphere serer. The naigation frame shows the task: Configure Configure TADDM Websphere Serer for the Virtual Member Manager Serice EJB Configure TADDM Websphere Serer for the Virtual Member Manager Serice EJB Parameters Scroll down to see all the parameters. Specify these parameters: WAS Home directory The fully qualified path where the TADDM Websphere Application Serer is installed. Default: /usr/websphere/appserer WAS profile name The Websphere Application Serer profile name. Default: Default WAS administrator user name The user name with administrator permissions. Default: admin WAS password The password for the user with administrator permissions. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check 88 Solutions for BSM Guide:

101 The default for each option is No. Configuring the TADDM WebSphere serer for Single Sign-On This task enables Single Sign-On on the WebSphere serer that is used by TADDM. The considerations that you must be aware of when completing this step are: By default Single Sign-On is enabled on the WebSphere serer that is used by TADDM. This step, howeer, sets the domain name to the specified input alue. This step enables Single Sign-On on the WebSphere serer used by TADDM and sets the Single Sign-On domain name to the specified input alue. The same Single Sign-On domain name must be used for all products participating within the Single Sign-On domain. The specified serer profile must be running for this step to complete successfully. As part of its processing, this step automatically restarts the WebSphere serer so that the configuration can take effect. TADDM Websphere Single Sign-On settings This task configures the IBM Tioli Application Dependency Discoery Manager (TADDM) Websphere serer for Single Sign-on. Purpose This task configures the TADDM Websphere serer for Single Sign-On. The naigation frame shows the task: Configure Configure TADDM Websphere Serer for Single Sign-On Configure TADDM Websphere Serer for Single Sign-On Parameters Scroll down to see all the parameters. Specify these parameters: WAS Home directory The fully qualified path where the TADDM Websphere Application Serer is installed. Default: /usr/websphere/appserer WAS profile name The Websphere Application Serer profile name. Default: Default WAS administrator user name The user name with administrator permissions. Default: admin WAS password The password for the user with administrator permissions. Verify password Re-enter the password. SSO domain name Enter the Single Sign-On domain name you want to use. For example, ibm.com. Adanced Chapter 2. Deploying the Solutions for BSM 89

102 In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Exporting the LTPA keys from the TBSM Dashboard serer This step exports the Lightweight Third Party Authentication keys from the TBSM Dashboard serer into a key file that is stored on the Dashboard serer at the location you specify during this step. The considerations that you must be aware of when completing this step are: After running this step, the key file must be copied manually to the other machines hosting the Tioli Enterprise Portal Serer and the WebSphere serer used by TADDM for authentication. It is important that you take note of the key file password specified as input to this step. The Dashboard Serer profile TIPProfile must be running for this step to complete successfully. Export LTPA Keys from Dashboard serer settings This task exports Lightweight Third Party Authentication keys from the TBSM Dashboard serer into a key file that is stored on the Dashboard serer at the location you specify during this step. Purpose After running this step, the key file must be copied manually to the other machines hosting the Tioli Enterprise Portal Serer and the WebSphere serer used by TADDM for authentication. It is important that you take note of the key file password specified as input to this step. The naigation frame shows the task: Configure Export LTPA Keys from TBSM Dashboard serer Export LTPA Keys from TBSM Dashboard serer Parameters Specify these parameters: TBSM Home directory The fully qualified path where the Dashboard serer is installed. Default: /opt/ibm/tioli/tbsm TIP administrator user name The user name with administrator permissions. Default: tipadmin TIP administrator password The password for the user with administrator permissions. Verify password Re-enter the password. Fully qualified name of LTPA key file to be exported The file that you export into another Websphere Application Serer. 90 Solutions for BSM Guide:

103 Password for LTPA key file The password you use when you import the key file to another serer. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Importing the LTPA keys into the TADDM WebSphere serer This task imports the Lightweight Third Party Authentication (LTPA) keys exported from the TBSM Dashboard serer into the WebSphere serer used by IBM Tioli Application Dependency Discoery Manager for authentication. The considerations that you must be aware of when completing this step are: The specified serer profile must be running for this step to complete successfully. This task assumes that the key file exported from the TBSM Dashboard serer has been transferred to a location on the WebSphere serer used by TADDM. When prompted, you must specify the fully-qualified location of the key file on the WebSphere serer and you must enter the same password that was used when the LTPA keys were exported. Import LTPA Keys into TADDM WebSphere serer This task imports Lightweight Third Party Authentication keys that you exported from the TBSM Dashboard serer into the IBM Tioli Application Dependency Discoery Manager WebSphere serer. Purpose The key file is required for single sign-on for TADDM. The naigation frame shows the task: Configure Import LTPA Keys into TADDM WebSphere serer Import LTPA Keys into TADDM WebSphere serer Parameters Specify these parameters: WAS Home directory The fully qualified path where the TADDM WebSphere Application Serer is installed. Default: /usr/websphere/appserer WAS profile name The WebSphere Application Serer profile name. Default: Default WAS administrator user name The user name with administrator permissions. Default: admin Chapter 2. Deploying the Solutions for BSM 91

104 WAS password The password for the user with administrator permissions. Verify password Re-enter the password. Fully qualified name of LTPA key file to be imported. If the target serer is remote, you must place the key file on the serer before running this deployment. The path and file name for the LTPA file you copied to the TADDM WebSphere serer LTPA key file password The password you specified when you exported the file from the TBSM Dashboard serer. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configuring the TADDM connection to the WebSphere serer This task configures your IBM Tioli Application Dependency Discoery Manager (TADDM) serer to connect to the WebSphere serer that is used for authentication. The considerations that you must be aware of when completing this step are: If you are configuring Single Sign-On for an existing TADDM enironment where TADDM is already connected to a WebSphere serer that authenticates against your LDAP serer, you can skip this step. The TADDM serer is restarted by this step to ensure that the changes take effect. As this step edits the TADDM configuration directly, backup copies of the configuration files are created with a suffix of the timestamp when the step was executed. The backup copies are stored in the directory specified during the step. The files that are modified and copied are: collation.properties ibmessclientauthnconfig.properties sas.client.props TADDM connection to WebSphere settings This task configures the IBM Tioli Application Dependency Discoery Manager (TADDM) connection to the TADDM WebSphere serer. Purpose This task configures the TADDM connection to the TADDM WebSphere serer. The naigation frame shows the task: Configure Configure TADDM connection to the TADDM Websphere serer. Configure TADDM connection to the TADDM Websphere serer. 92 Solutions for BSM Guide:

105 Parameters Scroll down to see all the parameters. Specify these parameters: TADDM dist directory The dist directory under the TADDM installation directory. This directory is defined by the $COLLATION_HOME ariable. On Linux systems, the default location for installing TADDM is the /opt/ibm/taddm directory. Therefore, in this case, the $COLLATION_HOME default directory is /opt/ibm/taddm/dist. Backup directory The TADDM backup directory located in the /opt/ibm/taddm/dist/ bsm_backup directory. WAS host name The fully qualified name for the host where the TADDM WebSphere Application Serer is installed. WAS bootstrap port The WebSphere Application Serer bootstrap port as defined in the file: $WAS_HOME/profiles/PROFILE_NAME/properties/portdef.props Default: WAS HTTP port The Websphere Application Serer HTTP port as defined in the file: $WAS_HOME/profiles/PROFILE_NAME/properties/portdef.props Default: WAS administrator user name The user name with administrator permissions. Default: admin WAS password The password for the user with administrator permissions. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: Skip Pre Deployment Check The default for each option is No. Configuring Tioli Monitoring for LDAP and Single Sign-On This step configures the IBM Tioli Monitoring (ITM) Tioli Enterprise Portal Serer (TEPS) for LDAP and Single Sign-On. This step also imports the Lightweight Third Party Authentication (LTPA) keys that were exported from the TBSM Dashboard serer. Before you begin Before beginning this step, you must manually set the.wasadmin password for the TEPS WebSphere serer. Chapter 2. Deploying the Solutions for BSM 93

106 94 Solutions for BSM Guide: About this task The considerations that you must be aware of when completing this step are: This step assumes that the key file exported from the TBSM Dashboard serer has been transferred to a location on the TEPS. You must specify the fully-qualified location of the key file on the TEPS and you must enter the same password as was used when the LTPA keys were exported. Because this step uses existing TEPS scripts to complete the configuration, the LDAP and Single Sign On configuration are completed at the same time and a separate option is proided within the step to import the LTPA keys. Regardless of which options are selected, executing this step stops and restarts the TEPS. If you are configuring Single Sign-On for an existing ITM enironment where TEPS has already been configured for LDAP, only use this step to import the LTPA keys. That is, select No for the Enable LDAP/SSO option for this step and select Yes for the Import LTPA Key option. This procedure is only necessary for an existing TEPS that has been configured for LDAP. In that scenario, you must complete these manual steps to complete the Single Sign-On configuration: Procedure 1. If the administration console is not already running, enable the TEPS Embedded WebSphere Application Serer administration console using the command: ITM_DIR/li6263/iw/scripts/enableISCLite.sh true 2. If the TEPS Embedded WebSphere Application Serer administrator password has not already been set, set it using the command: ITM_DIR/li6263/iw/scripts/updateTEPSEPass.sh wasadmin <password> 3. Log in to the TEPS Embedded WebSphere Application Serer administration console as the wasadmin user. Use the password set in the preious step to log in In the left-hand naigation area, expand the Security folder and click Global Security. 5. Under Authentication, expand Web security and click Single sign-on (SSO). 6. On the resultant page, ensure that the Enabled check box is selected and that the Domain name field is set to the same domain that was specified for TBSM and TADDM. If you make changes, click OK button then click the Sae link in the Messages box to sae your changes. 7. Open to the Global security page and click Configure next to Federated repositories in the Aailable realm definitions field. 8. On the Federated repositories page: Ensure that the alue specified for the Realm name field, for example defaultwimfilebasedrealm, matches the realm names set for TBSM and the WebSphere serer used by TADDM. If not, set the correct realm name used by all participating products. If you make changes to the Realm name field, click Apply and then click the Sae link in the Messages box to sae your changes and return to the Global security page. In Repositories in the realm area, ensure that the base entry specified for the ITM_TEPS_LDAP repository identifier matches the base entry specified for TBSM and the WebSphere serer used by TADDM. If the base entry does not match, click the base entry and on the resultant panel set the alue of

107 the Distinguished name of a base entry that uniquely identifies this set of entries in the realm field to match the base entry configured in TBSM and the WebShpere serer used by TADDM. If you make changes, click OK button then click the Sae link in the Messages box to sae your changes. 9. Click Logout to log out of the administration console. 10. Restart the TEPS using the commands: ITM_DIR/bin/itmcmd agent stop cq ITM_DIR/bin/itmcmd agent start cq Tioli Monitoring LDAP and Single Sign-On settings This task configures the IBM Tioli Monitoring (Tioli Monitoring) Tioli Enterprise Portal Serer for LDAP, Single Sign-On, and imports the LTPA key file. Purpose This task configures the Tioli Enterprise Portal Serer for LDAP, Single Sign-on, and imports the LTPA key file. Before you begin Copy the LTPA key file you exported from the TBSM Dashboard serer to the host for the Tioli Enterprise Portal Serer. The naigation frame shows the task: Configure Configure ITM TEPS LDAP, Single Sign-On, and Import LTPA Keys Configure ITM-TEPS LDAP SSO Configuration Parameters Scroll down to see all the parameters. Specify these parameters: TEPS Home directory The fully qualified path where the Tioli Enterprise PortalSerer is installed. Default: /opt/ibm/itm Enable LDAP/SSO Enable LDAP and Single Sign-On for your serer. If you are configuring Single Sign-On for an existing Tioli Monitoring enironment where the Tioli Enterprise Portal Serer is already configured for LDAP, select No and import only the LTPA keys. Default: Yes If you select No, specify these parameters: Import LTPA key Specify if you want to Import the LTPA key file you exported from the TBSM Dashboard serer. Default: Yes If you select No, the parameters required for the LTPA key file import are hidden. Automatically Restart ITM/TEPS Agent Specify whether you want the Tioli Enterprise Portal agent restarted automatically. Chapter 2. Deploying the Solutions for BSM 95

108 LDAP serer type Select your LDAP serer type from the drop-down list. If your serer type is not on the list, select Other and enter your LDAP serer type. LDAP host name The fully qualified name or IP address for your LDAP host. LDAP port The port number for your LDAP host. Default: 389 For SSL configuration the default is typically 636. LDAP base The LDAP base used in searches for your LDAP serer. Contact your LDAP administrator for this alue. For example, ou=deelopment,dc=ibm,dc=com LDAP bind ID The LDAP user name for bind authentication. The LDAP user name must be authorized to search for LDAP users. For example: cn=root. LDAP bind password Bind password for the repository. Verify password Verify the password. Realm name To obtain the name of the default realm, issue the following wsadmin command: $AdminTask getidmgrdefaultrealm VMMRealmName=defaultWIMFileBasedRealm SSO domain name Enter the Single Sign-On domain name you want to use. For example, ibm.com. WAS administrator user name The user name with administrator permissions. Default: wasadmin WAS password The password for the user with administrator permissions. Verify password Re-enter the password. Fully qualified name of LTPA key file to be imported. If the target serer is remote, you must place the key file on the serer before running this deployment. The path and file name for the LTPA file you copied to the Tioli Enterprise Portal serer host. LTPA key file password The password you specified when you exported the file from the TBSM Dashboard serer. Verify password Re-enter the password. Adanced In the Adanced tab, you can also choose whether you want to: 96 Solutions for BSM Guide:

109 Skip Pre Deployment Check Default: No. Time to wait after starting TEPS (seconds) Default: 20 Remoing the Single Sign-On configuration deployed by Solutions for Business Serice Management This topic outlines the steps that you must complete to remoe the Single Sign-On configuration that is created by Solutions for Business Serice Management. Remoing the TADDM connection to the TADDM WebSphere serer To remoe the TADDM connection to the TADDM WebSphere serer, restore the backup copy of the TADDM configuration files: COLLATION_HOME/etc/collation.properties COLLATION_HOME/etc/ibmessclientauthnconfig.properties COLLATION_HOME/etc/sas.client.props Note: Any changes made to these product configuration files after the backup files were created are lost when the backup copies are restored. Note: After the backup configuration files hae been restored, you must restart the TADDM serer. Remoing the Single Sign-On configuration from WebSphere serers To remoe the Single Sign-On and LDAP configuration deployed by Solutions for Business Serice Management into the WebSphere serers used by TBSM, TADDM, and ITM TEPS, you can take one of two approaches. If you hae saed backup copies of the WebSphere configuration files, you can restore them. These files are outlined in the Prerequisites for Single Sign-On configuration section of this document. If you hae not created backup configuration files, you can manually reset the Single Sign-On configuration and remoe the LDAP repository configuration using the WebSphere administratie console. Note: Any changes made to these WebSphere configuration files after the backup files were created are lost when the backup copies are restored. Note: After the backup configuration files hae been restored, you must restart each serer where one or more backup configuration files hae been restored. Remoing Single Sign-On and LDAP from WebSphere serers To remoe the Single Sign-On and LDAP configuration from the WebSphere serers using the WebSphere administratie console: Procedure 1. Log in to the WebSphere administratie console. 2. In the left-hand naigation area, expand the Security folder and click Global Security. 3. Under Authentication, expand Web security and click Single sign-on (SSO). 4. On the resultant page, clear the Single Sign-On domain name from the Domain name field and then click the OK button then click the Sae link in the Messages box to sae your changes. Chapter 2. Deploying the Solutions for BSM 97

110 5. Open to the Global security page and click Configure next to Federated repositories in the Aailable realm definitions field. 6. On the Federated repositories page: In the Repositories in the realm area select the base entry corresponding to the LDAP repository identifier that was created by the Solutions for Business Serice Management installer, and click the Remoe button. Next, click the Sae link in the Messages box to sae your changes. In the Related Items area, click the Manage repositories link. On the resultant page, select the Repository identifier that represents the LDAP repository added to the configuration by the Solutions for Business Serice Management installer, and click the Delete button. Next, click the Sae link in the Messages box to sae your changes. 7. Click Logout to log out of the administration console. 8. Restart the WebSphere serer for the changes to take effect (for ITM, restart the TEPS). 98 Solutions for BSM Guide:

111 Chapter 3. Post-installation configuration Tioli Monitoring situations Relationship Wizard These topics describe post-installation configuration tasks and considerations. The IBM Tioli Monitoring best practice situations that are deployed by IBM Solutions for Business Serice Management are neither distributed nor started within the Tioli Monitoring enironment as part of the deployment. After the best practice situations hae been deployed using IBM Solutions for Business Serice Management, you need to administer them using the Tioli Monitoring interfaces to organize them into situation groups if necessary, then distribute the situations or situation groups to managed system groups or managed systems, and then start them. For more information on managing situations, please see the Tioli Monitoring information center at the following locations: Grouping objects - %2Fcom.ibm.itm.doc_6.2.3%2Fgroup_objectintro_tep.htm Distributing a situation - %2Fcom.ibm.itm.doc_6.2.3%2Fsituation_distribute_tep.htm Starting or stopping a situation - %2Fcom.ibm.itm.doc_6.2.3%2Fsituation_startstop_tep.htm The Relationship Wizard allows you to automatically create business applications based on existing relationships between objects. These business applications can be iewed in Tioli Application Dependency Discoery Manager. You can also use the Relationship Wizard to iew business applications that hae been created in Tioli Application Dependency Discoery Manager. This topic discusses the features of the Relationship Wizard and outlines how to use it to manipulate business applications. Configuring and Running the Relationship Wizard Before you can use the Relationship Wizard, you must first perform a number of configuration steps. This topic outlines the steps to configure, and run the Relationship Wizard. Before you begin The Relationship Wizard must be configured and run from your IBM Tioli Application Dependency Discoery Manager (TADDM) host machine. The Relationship Wizard uses the JAVA_HOME ariable to locate jaa command. If this ariable is not set, the Relationship Wizard attempts to run the jaa command without a path. Set the JAVA_HOME ariable to the path appropriate to your configuration. Copyright IBM Corp

112 The files for the relationship wizard are located in the IBM Solutions for Business Serice Management deployment image in the directory: IMAGE_ROOT/scripts/TADDM/RelationshipWizard Procedure 1. Copy the file RelationshipWizard.jar from directory IMAGE_ROOT/scripts/TADDM/RelationshipWizard/lib to the directory: $COLLATION_HOME/sdk/lib 2. Copy the file RelationshipWizard.sh from directory IMAGE_ROOT/scripts/TADDM/RelationshipWizard to the directory: $COLLATION_HOME/sdk 3. To launch the Relationship Wizard, at the command prompt: a. Export your display. b. Export the JAVA_HOME ariable. c. To start the wizard, type the command: RelationshipWizard.sh Note: By default the Relationship Wizard uses localhost to identify the location of the Tioli Application Dependency Discoery Manager serer. If you want to change this setting, you can do so by setting the parameters of the RelationshipWizard command. For more information, at the command prompt type RelationshipWizard.sh --help for UNIX systems. Note: Logs created and maintained by the Relationship Wizard are stored in the directory from which the Relationship Wizard is run. The contents of this log are updated and displayed in real time by the Relationship Wizard. Using the Relationship Wizard You can use the Relationship Wizard to create entirely new business applications or to delete business applications. The purpose and features of each of these areas is described in detail in this topic. Note: The Relationship Wizard loads any existing business applications when it is started. If you are using the Relationship Wizard to manage applications any changes you make in the Relationship Wizard are displayed. Howeer, after you hae started the Relationship Wizard, any changes you make, or new business applications you create, in Tioli Application Dependency Discoery Manager are not isible until you restart the Relationship Wizard. Business Application Use the Business Application field to choose an existing business application and to create new business applications. When you select an application from the Business Application list, the options aailable in the remaining Relationship Wizard fields change dynamically to reflect the properties of the chosen business application. The options for the Business Application field are: Delete: Deletes the business application that is currently selected. To delete a business application, select it from the Business Application list and click Delete. Note: When you click the Delete button, the business application is deleted immediately and without additional warning. 100 Solutions for BSM Guide:

113 Create: Creates new business application. To create a business application, click Create. Type a name for your business application and click OK. Current Rule Use the Current Rule field to choose from the rules that apply to a selected business application. For existing rules, the aailable options are: Delete Rule: Deletes existing rule. Note: When you click the Delete button, the rule is deleted immediately and without additional warning. Edit Rule: Opens the Edit Rule dialog box. You can update the query associated with the rule by amending the statements. After you hae amended the statements, click Update Rule to apply your changes. Click Execute Rule to execute the query associated with the rule and display the results in a separate window. Show Rule Results : Executes the query associated with the selected rule and displays the result in a separate window. Note: To create a rule, use the Create Rule for Current Query button in the Results window. Show The Show area of the Relationship Wizard allows you to define a new query. You can use the queries you define to locate objects and include them in a business application. The syntax for a query is: Show [Objects][Group/Rule] of class [Class]; The syntax is defined by choosing options from the list for each option. The options for each parameter are: Objects From the Objects list, select one of the alues: all objects: Displays all objects of a gien class. If this alue is set, The Group/Rule parameter is not aailable. members of group:: Displays all objects assigned to a chosen group or rule that belong to a gien class. target/dependencies of group: Displays all objects of a gien class to which chosen group or rule has dependencies. source/dependents of group: Displays all objects of a gien class that depend on a selected group or rule. Group/Rule From the Group/Rule list, select an existing group or rule. The members of the group or rule and any relationships are applied when the query is executed. Class The Class list contains the names of the aailable common data model (CDM) classes. Objects belonging to a selected class are displayed as query results after satisfying all query criteria. If a required class is not listed, click Add class, select the class you want to add and click OK. This adds the additional class to your list. Where The Where area of the Relationship Wizard allows you to filter query results using the displayname attribute. You can narrow your search results by selecting from the Constraints list. The options aailable are: contains Chapter 3. Post-installation configuration 101

114 starts-with ends-with equals not-equals instance of ==!= > >= < <= You can choose the logical alues and or or to connect two filter criteria. After you hae selected your filter criteria, type the search alue in the text box to the right of each applicable constraint and click Show Query Results to display the results of your query. The Results window From the results window, you can perform a number of additional actions. The Results window options are: Create Rule for Current Query Click Create Rule for Current Query to create a rule based on the query and filter criteria that you hae defined. When you click Create Rule for Current Query, you are prompted to type a name for the rule, type a name in the Rule Name field and click OK. Create Group from Selected Items Click Create Group from Selected Items to create a group based on your query results. To create a group, select one or more items from the list and click Create Group from Selected Items. You are prompted to type a name for the group, type a name in the Group Name field and click OK. Close Click Close to close the Results. DLA automation considerations BSMAcceleratorUser role After deploying the tasks within the "Deploy Automated Discoery from ITM/ITCAM to TADDM" task group, you need to manually execute the scripts on the target machines to start the discoery automation processes. For more information see: DLA automation steps on page 48. When you deploy the TBSM Dashboard Serer Components task, a new role called BSMAcceleratorUser is created. This role controls access to the two new IBM Solutions for Business Serice Management pages that are also created by the same task. One of the new pages exists under the System Status and Health task in the left-hand naigation pane and is called Business Serice Health. The other new page, Business Serice Health Details, is accessed by right-clicking on any serice 102 Solutions for BSM Guide:

115 within the Business Serices portlet on the Business Serice Health page and then selecting the Business Serice Health Details item in the resultant context menu. In order to access the Business Serice Health and Business Serice Health Details pages, the logged-in user must hae the BSMAcceleratorUser role either assigned directly or assigned to a group to which the user belongs. This role is added to the tbsmadmin and tbsmreadonly groups when you deploy the TBSM components of the Solutions for BSM. Discoery Library Toolkit considerations Single sign-on configuration In order for critical or marginal serices to appear in the Business Serices portlet of the Business Serice Health page, or in the Business Serice Components portlet of the Business Serice Health Details page, the Discoery Library Toolkit component of TBSM must be running in order to process data into the Serice Component Registry and subsequently into TBSM. Additionally, when TADDM is in the enironment and contains the business application model to be represented on the Business Serice Health and Business Serice Health Details pages, the Discoery Library Toolkit component must be configured to import data from TADDM. Typically, the Discoery Library Toolkit is configured to import data from TADDM during the installation of the TBSM Data Serer, howeer, if it was not done at that time it can be done post install by running the TBSM_HOME/XMLtoolkit/bin/taddmconfig script which is part of TBSM interim fix 1 or higher. Running the script will allow you to configure TADDM as a data source for the Discoery Library Toolkit. From a command line on the TBSM Data Serer, you can issue 'taddmconfig.sh -?' to display the usage information for the script. In order to determine whether the Discoery Library Toolkit component of TBSM is running or not, you can issue the following command from a command prompt on the TBSM Data Serer: ps -ef grep XMLtoolkit If nothing is returned, then Discoery Library Toolkit is not running. For information on how to start the Discoery Library Toolkit, please see Running the Discoery Library Toolkit section within the TBSM 6.1 information center at: %2Fcom.ibm.tioli.itbsm.doc_6.1%2Fadminguide %2Fbsma_t_running_discoery_library_toolkit.html The IBM Solutions for Business Serice Management LDAP-related tasks within the Deploy Single Sign-On task group, configures a basic connection between the target product (TBSM, TADDM, or Tioli Monitoring) and a specified LDAP repository. The Single Sign-On tasks do not perform any user management or authorization operations against the target products. As such, it may be necessary to further configure and authorize users requiring Single Sign-On within each product (for example, to assign roles enabling a user to Chapter 3. Post-installation configuration 103

116 access particular data objects). For more information regarding user management and authorization within each product, please see the following on-line information center topics: TBSM Configuring users, groups, and roles - %2Fcom.ibm.tioli.itbsm.doc_6.1%2Fadminguide %2Fbsma_t_configuring_users_groups_roles.html IBM Tioli Application Dependency Discoery Manager - Security Oeriew - %2Fcom.ibm.taddm.doc_7.2%2FAdminGuide%2Fc_cmdb_sec_security.html IBM Tioli Monitoring - User administration - %2Fcom.ibm.itm.doc_6.2.3%2Fuser_administerintro_tep.htm 104 Solutions for BSM Guide:

117 Chapter 4. Uninstalling Solutions for BSM modifications This section describes how to uninstall the IBM Solutions for Business Serice Management. About this task To uninstall the modifications made to the products in the Solutions for BSM, you need to remoe the modifications to each product separately as described in these topics. Remoing TBSM Dashboard serer modifications Remoe the IBM Solutions for Business Serice Management modifications from the IBM Tioli Business Serice Manager Dashboard serer. Before you begin You need: The Tioli Integrated Portal administrator user ID and password. The TBSM Dashboard serer is a Tioli Integrated Portal serer instance. The path name to the Tioli Integrated Portal installation directory. The Solutions for BSM installation package, which contains the script that helps you remoe the TBSM Dashboard serer objects. About this task The bsma_tipundeploywar.sh script in the installation package helps you remoe the Solutions for BSM objects that were deployed to the TBSM Dashboard serer. These artifacts include Tioli Integrated Portal dashboard pages and portlets. Procedure 1. Hae all Tioli Integrated Portal users log out. 2. In the installation image, change to the IMAGE_HOME/scripts directory and open the bsma_install.properties file in a text editor. 3. Specify the alues for these properties: tip_tipadmin_userid The Tioli Integrated Portal administrator user. tip_tipadmin_password The password for the Tioli Integrated Portal administrator user. 4. Change to the Tioli Integrated Portal uninstall directory: IMAGE_HOME/scripts/TIP/ConsolidatedOperations/uninstall 5. Run the command: bsma_tipundeploywar.sh $TIP_HOME For example, this command specifies the default $TIP_HOME directory:./bsma_tipundeploywar.sh /opt/ibm/tioli/tip2 Copyright IBM Corp

118 Remoing TBSM Data serer modifications These tasks describe how to remoe modifications made to the IBM Tioli Business Serice Manager Data serer and the Discoery Library Toolkit and the related Netcool/Impact project. Before you begin You must know the user account and password for the TBSM database and the administrator account for Tioli Integrated Portal that was used to deploy the IBM Solutions for Business Serice Management. About this task The IMAGE_HOME/scripts/TBSM/uninstall/bin directory in the IBM Solutions for Business Serice Management deployment package, contains commands to help you remoe some of the Data serer and Discoery Library Toolkit objects. You must remoe other objects by hand. Complete these tasks in the sequence: Procedure 1. Remoe database objects. 2. Remoe Netcool/Impact objects. 3. Remoe the Business Serice Composer project from the Discoery Library Toolkit. 4. Remoe the modifications from the template mapping file from the Discoery Library Toolkit. 5. Inalidate the modified serice tree hierarchy. 6. Remoe the customized serice templates from the TBSM Data serer. 7. Remoe the customized data fetchers from TBSM Data serer. 8. Remoe the BSM Accelerator root serice. 9. Delete backup directory and bsma_tbsminstall.properties file. What to do next Note: To remoe the Data serer modifications for Solutions for Business Serice Management, you must complete the procedures outlined by using a Web Browser launched locally on your Data serer. 1. Remoing the database objects Remoe the IBM Tioli Business Serice Manager Data serer and Discoery Library Toolkit objects from the database. Before you begin Complete these steps: 1. If they are not already running, start the TBSM Data serer and the Discoery Library Toolkit 2. Log in to the TBSM Data serer host with the user account that deployed the IBM Solutions for Business Serice Management package. 106 Solutions for BSM Guide:

119 3. Add the username and password for the TBSM database and the Tioli Integrated Portal administrator account to the bsma_tbsmundeploy.properties file located in the IMAGE_HOME/scripts/TBSM/uninstall/bin directory. Note: To ensure that the operating enironment is secure, the passwords in the properties file are automatically cleared during the execution of the script in this step. The passwords must be reentered in the properties file when you run other scripts used when remoing the Data serer modifications.. About this task The IMAGE_HOME/scripts/TBSM/uninstall/bin directory in the Solutions for BSM deployment package, contains commands to help you remoe the Data serer and Discoery Library Toolkit objects. From the IMAGE_HOME/scripts/TBSM/uninstall/bin directory, execute the following command: bsma_tbsmdataundeploy_configdb.sh tbsm-home-dir The tbsm-home-dir command parameter is optional if the $TBSM_HOME enironmental ariable is set. This sample specifies the default $TBSM_HOME directory path. bsma_tbsmdataundeploy_configdb.sh /opt/ibm/tioli/tbsm Note: When this command completes, you are asked to iew the log file for results. You must examine this log as issues that result in failed completion of this command do not result in error messages in the user interface. Ensure that the statement BUILD SUCCESSFUL is contained at the end of the log file. If this statement is not present, you must resole any issues and rerun this command to ensure that the remoal is complete. 2. Remoing Netcool/Impact objects Remoe the modified Netcool/Impact project and policies from the IBM Tioli Business Serice Manager Data serer. Before you begin Complete the preious task. About this task To remoe the Netcool/Impact project and policies complete these steps. Procedure 1. If they are not already running, start the TBSM Data serer and the Dashboard serer. 2. Log in to the Tioli Integrated Portal serer as a user with permission to modify Netcool/Impact project and policies. For example, a member of the tbsmadmins group. 3. From the left naigation pane click System Configuration > Eent Automation > Policies. 4. From the Projects drop-down list, select BSMAccelerator. Chapter 4. Uninstalling Solutions for BSM modifications 107

120 5. From the policy list, select each of the following policies and click Delete Policy: BusinessSericeChartLib BusinessSericeEentCountChart BusinessSericeOerTimeChart Main_CheckForDepsEntry 6. To remoe the BSMAccelerator project, click Delete Project to the right of the Projects drop-down list. 7. From the Projects drop-down list, select TBSM_BASE. 8. Click the Upload a Policy File button. 9. In the Upload a Policy File pop-up dialog, select the Policy file box and click the Browse button, and naigate to the $TBSM_HOME/BSMAcceleratorV1/backup directory and select the Main_CheckForDepsEntry.ipl file to be uploaded. 10. Click Upload. 3. Remoing the Business Serice Composer project Use this procedure to remoe the customized Business Serice Composer (BSC) project from the Discoery Library Toolkit. 108 Solutions for BSM Guide: Before you begin In the IMAGE_HOME/scripts/TBSM/uninstall/dlbooks directory, you will find fie DLA book files used for the remoal of the BSC Project: BSC-itbsm.BSMAccelerator_1r1_A_DefineTechGroups+cdm_Name+policy+CreateShadow T Z.refresh.empty.xml.1 BSC-itbsm.BSMAccelerator_1r1_A_DefineTechGroupsByAttr+cdm_Name+cdm_ActiityName+ policy+createshadow t z.refresh.empty.xml.2 BSC-itbsm.BSMAccelerator_1r1_Z_DefineTechGroups+cdm_Name+policy+TechGrp T Z.refresh.empty.xml.3 BSC-itbsm.BSMAccelerator_1r1_Z_DefineTechGroupsByAttr+cdm_Name+cdm_ActiityName+ policy+techgrp t z.refresh.empty.xml.4 BSC-itbsm.ProductName=BSMAccelerator+Manufacturer=IBM+Hostname=bsc T Z.refresh.empty.xml.5 Note: If you are not using the Business Serice Composer, hae not configured TBSM to send auto-population objects to the Discoery Library Toolkit, or are not using the Serice Component Registry API to enrich eents, it is recommended that you stop the ResEnrichReader serice and before you begin remoing the Business Serice Composer project. Also ensure that the Automatically when serer starts checkbox is cleared for the ResEnrichReader serice. Procedure 1. Start the Discoery Library Toolkit serice if it is not running. Start the Discoery Library Toolkit daemon by running the tbsmrdr_start.sh script in the $TBSM_HOME/XMLtoolkit/bin directory. 2. From the $TBSM_HOME/XMLtoolkit/bin directory, execute the following command:./listartifact.sh -name BC.ProductName=BSMAccelerator+Manufacturer= IBM+Hostname%notifications.xml -category notifications Enter the TBSM database user ID and password when prompted. 3. From the $TBSM_HOME/XMLtoolkit/bin directory, execute the following command using the notifications artifact name returned in the listartifact output:

121 ./remoeartifact.sh -name BC.ProductName=BSMAccelerator+Manufacturer= IBM+Hostname=<Hostname of the Discoery Library Toolkit machine>.noti fications.xml -category notifications Enter the TBSM database user ID and password when prompted. 4. From the $TBSM_HOME/XMLtoolkit/bin directory, execute the following command:./utils.sh -e../scripts/reload_cdm_definitions.xml Enter the TBSM database user ID and password when prompted. 5. Update the localhost address ( ) in each DLA book filename to match the hostname or the IP address of the Data serer. It must match the host name in the Business Serice Composer project file preiously installed. The preiously installed BSC project file name begins with BSC-itbsm.ProductName=BSMAccelerator+Manufacturer=IBM+Hostname=. This file is in the directory from where the Discoery Library Toolkit reads its discoery books (that is, $TBSM_HOME/discoery/dlbooks), which is defined by the DL_FileSystem property in the $TBSM_HOME/XMLtoolkit/bin/ xmltoolkitsc.properties file. 6. Update the timestamp in the file name ( T Z) of each DLA book filename to the current date and time. Important: It is important that you presere the original timestamp format: year-month-daythour.minute.second 7. Copy the discoery book file number 1 (with the filename ending with.xml.1) into the directory from where the Discoery Library Toolkit reads its discoery books. a. Remoe the number postfix from the end of the file name so that the file ends with the.xml extension only. b. Monitor the msggtm_xt.log.0 file in the TBSM_HOME/XMLtoolkit/log directory for the following messages: GTMCL5289I: Begin processing book book file name. GTMCL5290I: Book book file name processed successfully. where book file name is the name of the book file that you just copied. The GTMCL5290I message indicates that the discoery of this book file was complete and successful. 8. Copy the discoery book file number 2 (with the filename ending with.xml.2) into the directory from where the Discoery Library Toolkit reads its books. a. Remoe the number postfix from the end of the file name so that the file ends with the.xml extension only. b. Monitor the msggtm_xt.log.0 file in the TBSM_HOME/XMLtoolkit/log directory for the following messages: GTMCL5289I: Begin processing book book file name. GTMCL5290I: Book book file name processed successfully. where book file name is the name of the book file that you just copied. The GTMCL5290I message indicates that the discoery of this book file was complete and successful. 9. Copy the discoery book file number 3 (with the filename ending with.xml.3) into the directory from where the Discoery Library Toolkit reads its books. a. Remoe the number postfix from the end of the file name so that the file ends with the.xml extension only. Chapter 4. Uninstalling Solutions for BSM modifications 109

122 b. Monitor the msggtm_xt.log.0 file in the TBSM_HOME/XMLtoolkit/log directory for the following messages: GTMCL5289I: Begin processing book book file name. GTMCL5290I: Book book file name processed successfully. where book file name is the name of the book file that you just copied. The GTMCL5290I message indicates that the discoery of this book file was complete and successful. 10. Copy the discoery book file number 4 (with the filename ending with.xml.4) into the directory from where the Discoery Library Toolkit reads its books. a. Remoe the number postfix from the end of the file name so that the file ends with the.xml extension only. b. Monitor the msggtm_xt.log.0 file in the TBSM_HOME/XMLtoolkit/log directory for the following messages: GTMCL5289I: Begin processing book book file name. GTMCL5290I: Book book file name processed successfully. where book file name is the name of the book file that you just copied. The GTMCL5290I message indicates that the discoery of this book file was complete and successful. 11. Copy the discoery book file number 5 (with the filename ending with.xml.5) into the directory from where the Discoery Library Toolkit reads its books. a. Remoe the number postfix from the end of the file name so that the file ends with the.xml extension only. b. Monitor the msggtm_xt.log.0 file in the TBSM_HOME/XMLtoolkit/log directory for the following messages: GTMCL5289I: Begin processing book book file name. GTMCL5290I: Book book file name processed successfully. where book file name is the name of the book file that you just copied. The GTMCL5290I message indicates that the discoery of this book file was complete and successful. 12. Optional: If it is not required for other purposes as part of your configuration, stop the ResEnrichReader Impact serice. 4. Remoing the xml template mapping modifications Remoe the modifications from the Discoery Library Toolkit CDM_TO_TBSM4x_MAP_Templates.xml SCR configuration file. Before you begin Complete the preious 3 tasks. Complete these steps: 1. Start the Discoery Library Toolkit serice if it is not running. 2. Add the username and password for the TBSM database account to the bsma_tbsmundeploy.properties file located in the IMAGE_HOME/scripts/TBSM/ uninstall/bin directory. Note: To ensure that the operating enironment is secure, the passwords in the properties file are automatically cleared during the execution of the script in this step. The passwords must be reentered in the properties file when you run other scripts used when remoing the Data serer modifications. 110 Solutions for BSM Guide:

123 About this task From the IMAGE_HOME/scripts/TBSM/uninstall/bin directory, run the command: bsma_tbsmdataundeploy_cdmmap.sh tbsm-home-dir The tbsm_home_dir command parameter is optional if the $TBSM_HOME enironment ariable is set. bsma_tbsmdataundeploy_cdmmap.sh /opt/ibm/tioli/tbsm Note: When this command completes, you are asked to iew the log file for results. You must examine this log as issues that result in failed completion of this command do not result in error messages in the user interface. Ensure that the statement BUILD SUCCESSFUL is contained at the end of the log file. If this statement is not present, you must resole any issues and rerun this command to ensure that the remoal is complete. 5. Inalidating modified serice tree hierarchy Inalidate the serice tree hierarchy created for the IBM Solutions for Business Serice Management. Before you begin Complete the preious 4 tasks. Procedure 1. If they are not already running, start the TBSM Data serer and the Dashboard serer. 2. Log in to the Tioli Integrated Portal serer where the TBSM dashboard serer is installed. 3. From the left naigation pane click Administration > Serice Configuration. 4. Select Serices from the Serice Naigation drop-down list. 5. Select the BSM Accelerator serice instance from Serice Naigation portlet. The BSM Accelerator serice instance opens in the Serice Editor. 6. In the Serice Editor, click Inalidate. 6. Remoing serice templates Remoe the custom serice templates from IBM Tioli Business Serice Manager Data serer. Before you begin Complete the preious 5 tasks. Complete these additional steps: 1. If it is not already running, start the TBSM Data serer. About this task The bsma_tbsmdataundeploy_radshell.sh command in the IMAGE_HOME/scripts/ TBSM/uninstall/bin directory in the Solutions for BSM deployment package, helps you remoe the custom serice templates. Chapter 4. Uninstalling Solutions for BSM modifications 111

124 Procedure From the IMAGE_HOME/scripts/TBSM/uninstall/bin directory, execute the following command: bsma_tbsmdataundeploy_radshell.sh tbsm-home-dir The tbsm_home_dir command parameter is optional if the $TBSM_HOME enironment ariable is set. This sample specifies the default TBSM_HOME directory path. bsma_tbsmdataundeploy_radshell.sh /opt/ibm/tioli/tbsm Note: When this command completes, you are asked to iew the log file for results. You must examine this log as issues that result in failed completion of this command do not result in error messages in the user interface. Ensure that the statement BUILD SUCCESSFUL is contained at the end of the log file. If this statement is not present, you must resole any issues and rerun this command to ensure that the remoal is complete. Results The command remoes the following serice templates along with their supporting rules: BSMAccelerator_ApacheWebSererMetrics BSMAccelerator_AppSerersGroup BSMAccelerator_ApplicationsClientMetrics BSMAccelerator_ApplicationsTransactionMetrics BSMAccelerator_ClientsGroup BSMAccelerator_DB2Metrics BSMAccelerator_DBGroup BSMAccelerator_EentCount BSMAccelerator_Library BSMAccelerator_LinuxOSMetrics BSMAccelerator_Metrics BSMAccelerator_SerersGroup BSMAccelerator_SericeApplication BSMAccelerator_TransactionsGroup BSMAccelerator_VMWareVIMetrics BSMAccelerator_VirtualEnironmentsGroup BSMAccelerator_WASMetrics BSMAccelerator_WebSerersGroup BSMAccelerator_WindowsOSMetrics 7. Remoing custom data fetchers Remoe the data fetchers created for the IBM Solutions for Business Serice Management. Before you begin Complete the preious 6 tasks. Procedure 1. If they are not already running, start the TBSM Data serer and the Dashboard serer. 2. Login to the Tioli Integrated Portal Serer where the TBSM dashboard serer is running. 3. From the left naigation pane click Administration > Serice Configuration. 4. Select Data Fetchers from the Serice Naigation drop-down list. 112 Solutions for BSM Guide:

125 5. Delete the following data fetchers from the Data Fetchers iew: ApacheWebSerer-Sites Applications-AMCClient Applications-AMCTrans DB2-Database01 LinuxOS-CPUUsage LinuxOS-SwapSpaceUsed VMWareVIMetrics-CPUUsage VMWareVIMetrics-LinksUsage WAS-DBConnPoolUsedPct WAS-MethodInocRate WindowsOS-CPUUsage Depending on the original installation, only a subset of the data fetchers may be installed. 8. Remoe the BSM Accelerator root serice Remoe the BSM Accelerator root node serice from the TBSM serice tree. Before you begin Complete the preious 7 tasks. Note: The preious tasks remoes all child serices from the BSM Accelerator root node serice. If you hae added child serices that were not based on the BSMAccelerator_Library serice templates, those serices are still displayed as child serices under the BSM Accelerator root node serice. Before you remoe the BSM Accelerator root node serice, determine whether the child serices can be deleted or should be moed under another parent serice. Procedure 1. If they are not already running, start the TBSM Data serer and Dashboard serer. 2. Log in to Tioli Integrated Portal. 3. From the left naigation pane, click Administration > Serice Configuration. 4. Select Serices from the Serice Naigation list. 5. Click the Delete Serices button in the Serice Naigation portlet. 6. In the Serice Editor portlet, select the BSM Accelerator serice and click Delete Selected. 9. Delete backup directory and bsma_tbsminstall.properties file As the final step in the remoal of the Data serer, manually delete the backup directory and the bsma_tbsminstall.properties file from the $TBSM_HOME/ BSMAcceleratorV1 directory. Note: You must delete these items to ensure that reinstallation of Solutions for Business Serice Management can be completed successfully after remoing all of the TBSM Data serer modifications described in the preious tasks. Uninstalling DLA Automation feature The Discoery Library Adaptor (DLA) Automation feature uses files spread across multiple products in the IBM Solutions for Business Serice Management. These tasks describe how to remoe the DLA Automation objects from these products. Chapter 4. Uninstalling Solutions for BSM modifications 113

126 Uninstalling TADDM artifacts for DLA automation Uninstall the IBM Solutions for Business Serice Management DLA automation artifacts from the IBM Tioli Application Dependency Discoery Manager (TADDM) serer. Before you begin TADDM and the DLA Automation tool must be stopped before performing these steps. About this task To uninstall the modifications, you need to delete seeral files by hand. Log in to the TADDM host as a user with write permissions to the $COLLATION_HOME directory. On Linux systems, the default location for installing TADDM is the /opt/ibm/taddm directory. Therefore, in this case, the $COLLATION_HOME default directory is /opt/ibm/taddm/dist. Procedure 1. Change to the $COLLATION_HOME directory. 2. The./etc/DLAAutomateLoader.properties file contains a property that specifies the directory for sharing data. The directory is specified by this property at the top of the file: monitordirectory=path Remoe the directory specified by the monitordirectory= property. 3. Delete the following files:./bin/addwasmsndla.sh./lib/itnmsnwasdla.jar./bin/dlaautomateloader.sh./lib/clientdlaautomate.jar./lib/sererdlaautomate.jar./etc/dlaautomateloader.properties./deploy-tomcat/dla.war There are also TADDM related changes made to the Tioli Eent Integration Facility probe. For information about how to restore the original Netcool/OMNIbus EIF probe rules that were used before deploying Solutions for BSM, see: Remoing the EIF probe customizations on page 120 Uninstalling ITCAM for Transactions integration from TBSM Uninstall the integration package for IBM Tioli Composite Application Manager for Transactions from IBM Tioli Business Serice Manager. Before you begin Make sure that the TBSM data serer is currently running. 114 Solutions for BSM Guide:

127 About this task The ITCAMT_Integration_OPAL_Refresh.tar.gz file in the installation image contains all the files you need to delete the integration package for IBM Tioli Composite Application Manager for Transactions from the TBSM Data serer. This task is for the TBSM host only. You also must remoe the integration package from IBM Tioli Netcool/OMNIbus. Procedure 1. Log in to the TBSM Data serer host as the same user that runs TBSM (for example, bsmadmin). 2. From the installation package, copy the ITCAMT_Integration_OPAL_Refresh.tar.gz file from the IMAGE_HOME/scripts/ ITCAM/ExtendedDLAs/itcam-wrt directory to the TBSM host. 3. Extract the ITCAMT_Integration_OPAL_Refresh.tar.gz file into a temporary directory. 4. After extracting the files, change to the tbsm61 directory. 5. Extract the TBSM integration file: ITCAMT _TBSM61.tar.gz. 6. Source the TBSM_HOME enironment ariable with the command: $TBSM_HOME/bin/setupTBSMData.sh 7. Source the TIP_HOME enironment ariable with the command:./$tbsm_home/bin/setuptbsmdash.sh 8. Run the uninstall.sh script with thetbsm database username and password with the command./uninstall.sh username password 9. The script shows the following information: Uninstallation of ITCAMfRT TBSM Integration package completed. Please restart TBSM dataserer and dashboard serer for changes to take effect. Restart the TBSM dataserer and dashboard serer to enable the changes. What to do next Remoe the integration package from Netcool/OMNIbus. Uninstalling ITCAM for Transactions integration from Netcool/OMNIbus Uninstall the integration package for IBM Tioli Composite Application Manager for Transactions from IBM Tioli Netcool/OMNIbus. Before you begin The ObjectSerer should be running when you perform this procedure. About this task The ITCAMT_Integration_OPAL_Refresh.tar.gz file in the installation image contains all the files you need to delete the integration package for IBM Tioli Composite Application Manager for Transactions from Netcool/OMNIbus. This task is for the Netcool/OMNIbus host only. You also must remoe the integration package from the TBSM Data serer. Chapter 4. Uninstalling Solutions for BSM modifications 115

128 Procedure 1. Log in to Netcool/OMNIbus host as the same user that runs Netcool/OMNIbus (for example, bsmadmin). 2. From the installation package, copy the ITCAMT_Integration_OPAL_Refresh.tar.gz file from the IMAGE_HOME/scripts/ ITCAM/ExtendedDLAs/itcam-wrt to the Netcool/OMNIbus host. 3. Extract the ITCAMT_Integration_OPAL_Refresh.tar.gz file into a temporary directory. 4. After extracting the files, change to the omnibus directory. 5. Extract the Netcool/OMNIbus integration file: ITCAMT _Omnibus.tar.gz. 6. Set the NCHOME enironment ariable with the command: export NCHOME=/opt/IBM/tioli/netcool 7. Run the omnibusupdater.sh to uninstall the transaction rules files and schema updates with the command./omnibusupdater.sh -b kt3.baroc kt4.baroc kt5.baroc kt6.baroc -u user -p password -r Note: When the password is blank, the -p option is not required. 8. Run the omnibusupdater.sh to uninstall the transaction tracking rules files with the command./omnibusupdater.sh -l kto.rules -u user -p password -r Note: The -u parameter is the Netcool/OMNIbus username. The default alue for this parameter is root. 9. Restart Netcool/OMNIbus and the Tioli Eent Integration Facility probe (EIF Probe) to enable the changes. Uninstalling ITCAM for Transaction Tracking Discoery Library Adapter objects Complete the following steps to uninstall the ITCAM for Transaction Tracking Discoery Library Adapter objects. About this task The associated installer is the ITCAM for Transaction Tracking installer package. There are two files containing the name itcamfttdla.jar. The file containing the name with a date is the original JAR file. At installation, the installer takes the original file itcamfttdla.jar and renames it with a timestamp for example, itcamfttdla_bsma_bk_<date>.jar. The installer then puts a new itcamfttdla.jar file in place. When you want to uninstall you are reersing the process and reinstating the original file which now has a date in its name. Procedure 1. Log in to the system that contains the Transaction Reporter monitoring agent as the user who installs and runs the agent. 2. Go to the transaction reporter bin directory. The default directory is /opt/ibm/itm/<arch>/to/bin. If you are not using the default directory, go to $CANDLEHOME/<arch>/to/bin. 3. Moe the itcamfttdla.jar file to a backup location. 4. Rename the itcamfttdla_bsma_bk_<date>.jar file with the date to itcamfttdla.jar. 116 Solutions for BSM Guide:

129 5. The next time the Discoery Library Adapter runs, the original Discoery Library Adapter JAR file without the timestamp is used. Uninstalling ITCAM for Applications WebSphere and the HTTP serer agent Discoery Library Adapter objects To uninstall the files used with the Discoery Library Adapter for WebSphere and the HTTP serer agent that are installed as part of Tioli Monitoring. About this task Use the same steps outlined in Remoing Tioli Monitoring DLA templates to remoe WebSphere and the HTTP serer agent Discoery Library Adapter objects. Remoe Tioli Monitoring modifications Uninstall the IBM Solutions for Business Serice Management modifications from IBM Tioli Monitoring. Before you begin You need a user account with write permission to the directories that contain the DLA templates, situations, and queries. About this task The scripts in the IMAGE_HOME/scripts/ITM/uninstall directory help you remoe some of the Solutions for BSM objects that were deployed to the Tioli Monitoring serer. These artifact types are: DLA Templates queries (must be remoed by hand) situations The following files will be remoed from the $CANDLEHOME/<arch>/cq/bin/tmsdla directory: kht_tmsdla.xml kht_tmsdla.jar kyn_tmsdla.xml kyn_tmsdla.jar Remoing Tioli Monitoring DLA templates Remoe the IBM Solutions for Business Serice Management DLA templates from the IBM Tioli Monitoring serer. Before you begin You need a user account with write permission to directories that contain the DLA templates. About this task The bsma_itmdlatemplatedelete script in theimage_home/scripts/itm/uninstall directory of the deployment image helps you remoe the DLA templates that were added to the Tioli Monitoring serer. Chapter 4. Uninstalling Solutions for BSM modifications 117

130 Procedure 1. Copy the bsma_itmdlatemplatedelete.sh script to your Tioli Monitoring host. 2. To remoe all the DLA templates, run the command: bsma_itmdlatemplatedelete.sh -i ITM_HOME_DIRECTORY -h true -w true Where: -i Home directory for TEPS; for example: /opt/ibm/itm -h To remoe the HTTP DLA Template specify true (default false) -w To remoe the WAS DLA Template specify true (default false) Run the script with no arguments for additional information. Example For example to remoe all DLA templates: bsma_itmdlatemplatedelete.sh -i /opt/ibm/itm -h true -w true Uninstall Tioli Monitoring queries Uninstall the IBM Solutions for Business Serice Management queries from the IBM Tioli Monitoring serer. Before you begin You need a user account with permission to delete queries. About this task Custom queries for TWA Metrics were deployed for the Solutions for BSM. Tioli Monitoring does not proide a command line interface for deleting queries. Accordingly, you must delete the queries using the Tioli Enterprise Portal Query editor. For a list of the custom queries that were deployed, for the Solutions for BSM, look in the IMAGE_HOME/scripts/ITM/queries directory of the installation image. Procedure 1. Open your Tioli Enterprise Portal and do the following to open the Query editor: Click Query Editor. In the iew whose query you want to delete, click Properties. Click Properties editor and select the iew from the Properties tree. 2. Select the Query name in the tree. The query specification is displayed in the right frame. 3. Click Delete Query. IftheDelete Query tool is disabled, your user ID does not hae Modify Query permission. Remoing Tioli Monitoring situations Remoe the IBM Solutions for Business Serice Management situations from IBM Tioli Monitoring. Before you begin You need a user account with write permission to directories that contain the situations. 118 Solutions for BSM Guide:

131 About this task The deployment program creates about 120 situations for Tioli Enterprise Monitoring Serer (referred to as the monitoring serer) component of Tioli Monitoring. The script bsma_itmsituationsdelete in the IMAGE_HOME/scripts/ITM/ uninstall directory of the deployment image helps you delete these situations. Before you run the script, reiew the situation.list file in this directory. This file specifies the situations remoed by the bsma_itmsituationsdelete script. If you do not want to remoe some of the situations, remoe these situations from the situation.list file before you run the bsma_itmsituationsdelete script. This task must be completed on a local Tioli Enterprise Management Serer and not a remote Tioli Enterprise Management Serer. Procedure 1. Copy the bsma_itmdlasituationsdelete.sh script and the situation.list file to your monitoring serer host. 2. If you do not want to remoe some of the situations, remoe these situations from the situation.list file. 3. To remoe the situations, run the command: bsma_itmsituationsdelete.sh ITM_HOME_DIERCTORY hostname username password situations_list Where: ITM_HOME_DIRECTORY Home directory for the monitoring serer; for example: /opt/ibm/itm hostname monitoring serer host name username User to login to the monitoring serer with password Password for the aboe username situations_list (Optional) Directory containing the situation.list file. If you do not specify a directory, the commmand assumes the situation_list file is in the same directory as bsma_itmdlasituationsdelete.sh script. Run the script with no arguments for additional information. Example This example remoes the situation from the default ITM_HOME_DIRECTORY bsma_itmsituationsdelete.sh /opt/ibm/itm localhost bsmadmin netcool Remoing the OMNIbus customizations Use this procedure to remoe the IBM Solutions for Business Serice Management OMNIbus customizations. You must reerse the changes in the following components: Eent Synchronization Component ObjectSerer database EIF probe OMNIbus WebGUI Uninstalling the ITM Eent Synchronization component Use this procedure to remoe the ITM Eent Synchronization component from OMNIbus. Chapter 4. Uninstalling Solutions for BSM modifications 119

132 About this task The ITM Eent Synchronization component uninstaller script, uninstaller.bin is located in the /opt/ibm/sitforwarder/_uninst/ directory. Important: The aboe is the default location where this component is installed on the serer where OMNIbus is running. Remoing the ObjectSerer database customizations To remoe the ObjectSerer customizations, you must reerse the database schema changes, and restore the preious ersion of the deduplication trigger using the nco_confpack utility. About this task This procedure assumes that you used the nco_confpack utility to export your ObjectSerer configuration settings before running the IBM Solutions for Business Serice Management wizard. For more information about using this utility, see the Importing, and exporting ObjectSerer configurations section in the Netcool/OMNIbus information center: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/welcome.htm. Procedure Run the nco_confpack utility with the following options: nco_confpack -import -package configuration_package.jar -user username -serer serername where configuration_package.jar is the package that contains the exported ObjectSerer configuration settings, username is the ObjectSerer administrator, and serername is the ObjectSerer name. For example: nco_confpack -import -package configuration.jar -user root -serer NCO -nowarn The aboe command imports the configuration that is contained in the configuration.jar package into the NCO ObjectSerer. What to do next To complete restoring the ObjectSerer configuration you must restart the ObjectSerer. For detailed steps, refer to the Creating and running the ObjectSerer section in the Netcool/OMNIbus information center. Remoing the EIF probe customizations To remoe the EIF probe customizations you must restore the original EIF probe rules from backup. About this task The Solutions for BSM deployment wizard takes a backup of the EIF probe rules files in NC_HOME/omnibus/probes/<os_arch>/backuptimestamp directories. 120 Solutions for BSM Guide:

133 Procedure 1. Restore the original rules files from their associated backup directories, to the EIF probe directory, OMNIHOME/probes/linux2x86/. Note: For a full list of the modified or new EIF probe rule files, see EIF Probe rules updates on page 138. The backup directories hae the following path: OMNIHOME/probes/<os_arch>/backuptimestamp where timestamp is the the system clock time at the time the backup directory was created. 2. Optional: Remoe the new rule files that were installed as part of the Solutions for BSM deployment. What to do next To complete restoring the original EIF probe rules you must restart the EIF probe. For more information, see the Running the Tioli Eent Integration Facility probe on UNIX systems section in the Netcool/OMNIbus information center: com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/welcome.htm. Remoing OMNIbus Web GUI iews and filters Use this procedure to remoe the Web GUI iew and filters that were installed as part of Solutions for BSM. Procedure 1. In Web GUI, ensure that the WAAPI client is running. 2. Send the command file to the Web GUI serer using runwaapi. To delete the filter: runwaapi -file path/bsma_delete_filter.xml -user TBSM_ADMIN_USERID -password TBSM_ADMIN_PASSWORD where path is the full path to the bsma_delete_filter.xml file, TBSM_ADMIN_USERID is the TBSM administrator ID, and TBSM_ADMIN_PASSWORD is the TBSM administrator password. For example: /opt/ibm/netcool/omnibus_webgui/waapi/bin/runwaapi -file./bsma_delete_filter.xml -user tbsmadmin -password tbsmpass To delete the iew: <NETCOOL_HOME>/omnibus_webgui/waapi/bin/runwaapi -file./bsma_delete_iew.xml -user <TBSM_ADMIN_USERID> -password <TBSM_ADMIN_PASSWORD> Note: You can find the bsma_delete_filter.xml, and bsma_delete_iew.xml file in the <IMAGE_ROOT>/scripts/OMNIbus/uninstall directory. Chapter 4. Uninstalling Solutions for BSM modifications 121

134 122 Solutions for BSM Guide:

135 Chapter 5. Product modifications TBSM updates The IBM Solutions for Business Serice Management includes modification and integration code for multiple Tioli products. During the deployment process, these modifications are applied to the supported Tioli products in order to implement a consistent methodology for managing business serices. These topics describe the IBM Solutions for Business Serice Management updates to IBM Tioli Business Serice Manager. The deployment wizard will apply changes to the following components: Serice templates Serice tree scorecard templates Right-click menus BIRT charts Netcool/Impact policies Discoery Library Toolkit Business Serice Composer About the TBSM serice templates To simplify the process for defining and configuring serices, TBSM proides tools to help you create serice templates for serices instances with common behaior. Rather than define each of your serices and their dependencies indiidually, you can create one template for a type of serice and then assign applicable serices to the template. For more information about the serice templates and how they work with DLAs, see the TBSM documentation at: display/tiolidoccentral/tioli+business+serice+manager. For general information on serice templates, see the Serice Configuration and Scenarios guides. For information on how templates work with the Discoery Library Toolkit, see the Customization Guide. Class mapping for Solutions for Business Serice Manager The Solutions for Business Serice Manager use common data model classes to assign technology components to technology types. For each unique business serice or application of a gien class in the Serice Component Repository, all related or dependent items are grouped based on their class into the appropriate technology type. The CDM classes app.application, sys.businesssystem, and core.collection are the basis for the CDM to technology type mapping. Within the technology types, technology components are displayed under eery applicable business applications, business serices, or collection with which they are associated. Copyright IBM Corp

136 Table 3. Sample class mapping for Solutions for Business Serice Manager. Sample class mapping for Solutions for Business Serice Manager Serice template Technology type CDM class BSMAccelerator_AppSerersGroup Application Serers cdm:app.j2ee.j2eeserer BSMAccelerator_ClientsGroup Clients cdm:core.homogenouscollection BSMAccelerator_DBGroup Databases cdm:app.db.databaseserer BSMAccelerator_SerersGroup Serers cdm:sys.computersystem BSMAccelerator_TransactionsGroup Transactions cdm:process.actiity BSMAccelerator_VirtualEnironmentsGroup Virtual Enironments cdm:sys.mware.datacenter BSMAccelerator_WebSerersGroup Web Serers cdm:app.web.webserer In addition to the standard class mappings, you can also define custom technology groups. TBSM serice templates The TBSM serice templates contain rules that ealuate eents and data from Netcool/OMNIbus and data feeders. The data feeders can be data fetchers, configured in TBSM, and Impact serices. These rules are used by TBSM to correlate eents from the agents with discoery data from TADDM. The rules also define the structure of the TBSM serice model. The templates hae the prefix BSMAccelerator_* are organized with : The Eent Count template has rules which proide eent counts for the technology types and the serice or application parent serice. The Metric Collection templates hae rules to collect metrics which are considered best practice for specific technology types. The technology type templates hae rules to propagate the status of children directly related to the technology type. You can add additional templates to help discoer more business transactions and associate them with business applications in the TBSM serice model. Serice model structure This section contains information about how the serice templates are used to define the serice model structure. The serice model structure is based on the default TADDM-TBSM integration and its defined collections, business serices, and business applications. The serice model is defined and maintained by the Discoery Library toolkit. The serice templates define the key field/alue pairs for each type of serice and set the hierarchy of the serice model. The aggregation rules in the templates define the dependencies between the parent and child serices. For example, in the structure below, each template includes aggregation rules that define the child templates affecting the parent template status. BSMAccelerator_SericeApplication BSMAccelerator_AppSerersGroup BSM_WebSphere_Serer BSMAccelerator_Library: 124 Solutions for BSM Guide:

137 In addition to using the standard templates that are proided by default by TBSM, Solutions for Business Serice Management contains a set of additional templates maintained within the BSMAccelerator_Library template library. These templates contains rules that define the application group dependencies in the serice model and a isibility rule. These templates are used in conjunction with the standard TBSM templates to generate the Solutions for Business Serice Management structure model. This topic proides an oeriew of the Solutions for Business Serice Management templates. BSMAccelerator_EentCount The BSMAccelerator_EentCount template allows you to associate metric collection rules to eents. This allows you to determine how many actie eents are aailable for a specific application or technology component. BSMAccelerator_Metrics The Technology Metric template allows you to collect metrics and key performance indicators for technology components based on data collected by the IBM Tioli Monitoring agents. BSMAccelerator_SericeApplication The Serice Application template is assigned to your collection, business serice, or business application serice instance shadow that are defined within TADDM. The template contains aggregation rules that define dependencies on these applications groups: Note: If you are not using TADDM, use the Business Serice Composer to create a project and group your resources into the sys.businesssystem, app.application, or core.collection classes. BSMAccelerator_AppSerers Dependent on technology types associated with application serers. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_Client Dependent on technology types associated with client applications. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_Databases Dependent on technology types associated with databases. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_Serers Dependent on technology types associated with serers. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_Transactions Dependent on technology types associated with transactions The template Chapter 5. Product modifications 125

138 contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_Virtualization Dependent on technology types associated with irtualization. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. BSMAccelerator_WebSerers Dependent on technology types associated with web serers. The template contains the child status rule propagation, technology group leel metrics such as eent counts, and child templates for the associated technology types. DirectChildEentStatus rule: The default incoming status rule is the SCR_SericeComponentRawStatusTemplate. This has not changed for the Solutions for Business Serice Management templates. You can customize the rule if you want different seerity eents to affect the serice status. The DirectChildEentStatus numerical aggregation rule uses the SCR_SericeComponentRawStatusTemplate to aggregate the eents of children directly dependent on the technology group. The rule alue is used by the technology group template output expression to determine the oerall attribute of the technology group instance. The DirectChildEentStatus rule uses only the eent-specific status of direct children to determine the status. In the following example, a serice instance tree is displayed with the Day Trader application is tagged with the BSMAccelerator_SericeApplication template. It has an Application Serers technology group with dependents: Day Trader application(s) Applications Serers J2EE_Application_Serer_instance_X Linux_Serer_instance_X VM_Serer_instance_X If the VM_Serer_instance_X status becomes critical, the default behaior is to propagate the worse child status. Howeer with the DirectChildEentStatus rule, the Application Serers technology group instance does not change status because a direct child, in other words, an application serer technology group did not cause the status change. Output expression The output expression applied to each technology group template is used to control the oerall status of the technology group instance. Therefore, only the status of direct children affects the status of the technology group. They syntax for the output expression is: (DirectChildEentStatus.Value >= <seerity>) where <seerity> is >=5 to reflect a bad status and >=3 for a marginal status. Rules for the BSMAcceleratorEentCount template: 126 Solutions for BSM Guide:

139 The eent count metric is seen on the Business Serice Health details scorecard. The appropriate metric is calculated and shown for each leel, serice/application/collection, technology group, and resource based on the following rules: Collect All Eents The BSMAccelerator_EentCountTrigger incoming status rule outputs the seerity alue of the eents for a set of classes. The alue is used by the BSMAccelerator_TotalEentCount rule to proide a total count of eents by seerity for an instance based on the BSM_Identity. Note: By default, this rule has been configured to iew specific eent classes. These are the same classes as the default SCR_* status templates. You can customize the rule with additional classes that you require in the selected Eent Discriminators list. Total Eent Count Roll Up The BSMAccelerator_EentCountRollUp Numerical Aggregation rule aggregates the total eent count for each instance to proide an aggregate eent count for each technology group. Dynamic Eent Count Roll Up The BSMAccelerator_DynamicEentCountRollUp numerical aggregation rule proides the total eent count for the serice or application, in other words, the app.application, sys.businesssystem, orcore.collection serice instance. It rolls up the eent counts determined by the BSM_Accelerator_DynamicEentCount rule policy ealuation. This rule also stores the deried data so it can be iewed in the Time Window Analyzer (TWA). Total Eent Count The BSM_Accelerator_TotalEentCount rule outputs the number of matching eents with a seerity greater than or equal to 2. It applies an internal attribute, NumEentsSeGE2, to the eents collected by the BSMAccelerator_EentCountTrigger rule. The NumEentsSeGE2 attribute can be qualified using additional logic filters. The generic syntax for the attribute is: NumEentsSe<qualifier><seerity> where <qualifier> can be GE to indicate that the seerity must be greater than or equal to the seerity alue oreq to indicate that the alue must be equal to the seerity alue. The alue for <seerity> must be in the range from0to5. The Solution for Business Serice Management supplied rule expression is BSMAccelerator_EentCountTrigger.NumEentsSeGE2 Dynamic Eent Count The BSMAccelerator_DynamicEentCount numerical formula rule proides the eent count metric displayed in the scorecard. It calculates the eent count based on an instance type. The instance type alue is determined by an additional property set on the BSMAccelerator_* templates. The instance type identifies whether the eent count creates a total the eents for the serice, application, collection leel, the technology group, or the resource. An Impact policy is used to determine total based on the instance type. The additional property is the DynamicEentCountRollUpLeel. The alue leaf is set on the technology group templates. The alue branch is set on the template for a business application or a business serice or a collection. Chapter 5. Product modifications 127

140 128 Solutions for BSM Guide: Additional properties for the BSMAccelerator_EentCount template A number of additional properties hae also been applied to the BSMAccelerator_EentCount template and enrich eery instance tagged with the BSMAccelerator_EentCount template. These properties: WebtopFilterName WebtopFilterValue WebtopViewName are used oerride the default behaiour between the scorecard portlet and the Actie Eent List (AEL) portlet. These properties assign a Netcool/OMNIbus WebGUI filter and iew and apply it when you are passing context from the scorecard to the Actie Eent List (AEL) portlet. These properties ensure that unnecessary OMNIbus WebGUI fields are not displayed. Metric collection templates A number of metric collection templates hae been made aailable by default for Solutions for Business Serice Management. These templates allow you to gather key performance indicator (KPI) data for specific technology types. These templates are automatically assigned to instances based on the common data model (CDM) class of the instance. These templates use data fetchers that query IBM Tioli Monitoring (ITM) agents through the ITM charts web serices. The default metrics are stored for display in the Time Window Analyzer (TWA) portlet. The default templates proided are: BSMAccelerator_ApacheWebSererMetrics This template is used to collect metrics for Apache Web Serers and IBM HTTP Serers. The following rules hae been created for this template: Apache Web Serer Failures Rate Apache Web Serer Failed Pages Rate Apache Web Serer Failed Login Rate BSMAccelerator_ApplicationsClientMetrics This template is used to collect metrics for the clients group. The following rules hae been created for this template: Client Percent Failed Client Percent Slow BSMAccelerator_ApplicationsTransactionMetrics This template is used to collect metrics for the transactions group. The following rules hae been created for this template: Transaction Aerage Requests Transaction Response Time Transaction Percent Failed BSMAccelerator_DB2Metrics This template is used to collect metrics for DB2 systems. The following rules hae been created for this template: DB2 Buffer Pool Hit Ratio DB2 Deadlocks BSMAccelerator_LinuxOSMetrics This template is used to collect metrics for Linux operating system computers. The following rules hae been created for this template: Linux OS CPU Current Aerage

141 Linux OS Swap Space Used BSMAccelerator_VMWareVIMetrics This template is used to collect metrics for VMWareVI objects. The following rules hae been created for this template: VMWare VI CPU Utilization VMWare VI Link Utilization BSMAccelerator_WASMetrics This template is used to collect metrics for the application serer group. The following rules hae been created for this template: WAS Database Connections Used WAS Method Inocation Rate BSMAccelerator_WindowsOSMetrics This template is used to collect metrics for Windows operating system computers. The following rules hae been created for this template: Windows OS CPU Usage SericeVisibility rule The SericeVisibility Internal Formula Rule is used by Solutions for Business Serice Management to ensure that only items that are in a marginal or critical state are displayed in the Business Serice Health scorecard. This rule is associated with the BSMAccelerator_SericeApplication template and establishes a simple binary alue to control the isibility of the collection, business serice, or business application within the Business Serice Health scorecard. This allows you to hae greater control by limiting the Business Serice Health scorecard to show only items in an abnormal state. An Impact policy is used to determine whether the technology group is displayed on the Business Health page. If the technology group has resources that are marginal or critical, it is displayed. You can change the default behaiour by editing the Impact Policy that controls the behaiour. For more information about editing Impact policies, see the TBSM Customization Guide. Serice tree scorecard templates The following new serice tree scorecard templates hae been added for Solutions for Business Serice Management: BSM_Accel_Details_Scorecard This template defines the column names and column content information in the Business Serice Components serice tree portlet on the Business Serice Health Details page. The BSM_Accel_Details_Scorecard.xml file has been added to the TBSM database to create this template. BSM_Accel_Scorecard This template defines the column names and column content information in the Business Serices serice tree portlet on the Business Serice Health page. The BSM_Accel_Scorecard.xml file has been added to the TBSM database to create this template. Serice tree scorecard policy The TBSM_GetTreeColumnValue.ipl has been updated for Solutions for Business Serice Management. This policy defines how the column content, such as icons and the formatting of data, is rendered in the installed serice tree scorecard templates. Chapter 5. Product modifications 129

142 Customizing the serice tree portlet column titles A serice tree template has been created for Solutions for Business Serice Management. This template named BSM_Accel_Scorecard is used to controls the rules and control how the status of technology types is displayed. Within this BSM_Accel_Scorecard template an Impact policy is used to replace the numeric alues 0,3,5 with good, marginal, and bad status icons in the serice tree portlet. The column titles for the serice tree portlet are also defined within this Impact policy. Howeer, the Impact policy references a series of ariables that control the labels applied to the serice tree portlet columns. You can edit the column names by editing the scorecard_labels.properties file located in the $TIP_HOME/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/WEB-INF on the TBSM Dashboard serer to amend the following properties: BSMAccel_Clients: The default label for this column is Clients. BSMAccel_Web_Serer: The default label for this column is Web Serer. BSMAccel_Serer: The default label for this column is Serer. BSMAccel_DBs: The default label for this column is DBs. BSMAccel_Transactions: The default label for this column is Transactions. BSMAccel_App_Serer: The default label for this column is App Serer. BSMAccel_VEs: The default label for this column is VEs. BSMAccel_Eents: The default label for this column is Eents. Change each of the properties to reflect the label that you want to apply to the column. Note: If your enironment inoles more than one Dashboard serer, the scorecard_labels.properties file must be updated on each Dashboard serer. Note: You must restart each Dashboard serer to ensure that the changes made to the scorecard_labels.properties file take effect. Customizations to the TBSM right-click menus A number of right-click menu options hae been added to TBSM for Solutions for Business Serice Management: Business Serice Health Details The Business Serice Health Details right-click menu option allows you to launch the Business Serice Health Details page from a selected business serice in the Business Serice Health page. This option is proided by the addition of the LaunchBSMAccelDetailsPage.xml file to the TBSM database. Show VMWare Network Details When you select a serice that represents a irtual enironment cluster, serer, or data store on the Business System Health Details page and right-click, the Show VMWare Serer Details option is aailable in the Launch to submenu. This option allows you to launch the network details iew of the IBM Tioli Monitoring Virtualization Dashboard. The ShowVirtNetworkDetails.xml file has been added and the IntegrationTools.xml file has been updated to proide this option. These files are stored in the TBSM database. Show VMWare Serer Details When you select a serice that represents a irtual enironment cluster or serer on the Business System Health Details page and right-click, the Show VMWare Network Details option is aailable in the Launch to 130 Solutions for BSM Guide:

143 submenu. This option allows you to launch the Serer details iew of the IBM Tioli Monitoring Virtualization Dashboard. The ShowVirtSererDetails.xml file has been added and the IntegrationTools.xml file has been updated to proide this option. These files are stored in the TBSM database. ShowVirtStorageDetails.xml When you select a serice that represents a irtual enironment cluster or serer on the Business System Health Details page and right-click, the Show VMWare Storage Details option is aailable in the Launch to submenu. This option allows you to launch the Storage details iew of the IBM Tioli Monitoring Virtualization Dashboard. The ShowVirtStorageDetails.xml file has been added and the IntegrationTools.xml file has been updated to proide this option. These files are stored in the TBSM database. Customization of the TBSM BIRT charts The following new Business Intelligence and Reporting Tools (BIRT) chart artifacts are installed for Solutions for Business Serice Management: BusinessSericeEentCountChart This chart defines the Business Serice Eent Count Oer Time charting portlet on the Business Serice Health page. This TBSM_BusinessSericeEentCountChart.rptdesign file has been added to the TBSM database for this BIRT chart. The BusinessSericeEentCountChart.js Impact policy has been added for Solutions for Business Serice Management and is used to generate the data displayed by the Business Serice Eent Count Oer Time chart. Note: Do not edit this policy, and do not edit the chart definition in the TBSM Naigator portlet. BusinessSericeStatusChart This chart defines the Business Serice Status Oer Time charting portlet on the Business Serice Health page. This TBSM_BusinessSericeStatusChart.rptdesign file has been added to the TBSM database for this BIRT chart. The BusinessSericeOerTimeChart.js Netcool/Impact Impact policy has been added for Solutions for Business Serice Management and is used to generate the data displayed by the Business Serice Status Oer Time chart. Note: Do not edit this policy, and do not edit the chart definition in the TBSM Naigator portlet. In addition to the Impact policies used to generate the BIRT charts, the BusinessSericeChartLib.js has also been added for Solutions for Business Serice Management. This policy contains a shared policy function library that: Retriees a metric from the TBSM Metric History database Uses the retrieed metric data to populate the data points to be displayed for the 12 hour time window with four slots of 15 minute duration per hour. Main_CheckForDepsEntry Impact policy For Solutions for Business Serice Management, the Main_CheckForDepsEntry.ipl policy has been updated to perform eent enrichment. The update to the policy Chapter 5. Product modifications 131

144 allows information to be passed to the policy to indicate whether it is being called by a Business Serice or a technology type serice. If it is either of these 2 serice types. the policy updates the enrichment fields in the raw eent. The business serice name is added to the BSMAccelerator_Serice field and the technology type is added to the BSMAccelerator_Function field. Discoery Library Toolkit artifacts A number of Discoery Library Toolkit artifacts hae been added to TBSM for Solutions for Business Serice Management. Serice Component Repository configuration artifact The CDM_TO_TBSM4x_MAP_Templates.xml file has been updated for Solutions for Business Serice Management. This Serice Component Repository (SCR) configuration file defines the mapping of resource classes located within the SCR to one or more Solutions for Business Serice Management templates. This file is stored in the TBSM database. Eent identifier rules artifact The BSMAccelerator_EentIdentifiers.xml has been added to TBSM for Solutions for Business Serice Management. This Eent identifier rules file defines the mechanism for enriching Solutions for Business Serice Management serices in the Serice Component Repository. This file is stored in the TBSM database. TBSM attributes artifact The BSMAccelerator_attributesiee.xml file defines the list of attributes, stored in the Serice Component Repository, that can be passed to the TBSM memory model for Solutions for Business Serice Management serices. This file is stored in the TBSM database. Business Serice Composer The Business Serice Composer is an application that creates and maintains project files containing business serice definitions and the placement rules used to build business serice hierarchies. The business serice hierarchies are built using the enterprise resources discoered by TBSM. The Business Serice Composer creates the rules that use the Common Data Model (CDM) classes to assign the components of Tioli Application Dependency Discoery Manager collections, business serices, and business applications to the appropriate technology types in Solutions for Business Serice Management. Business Serice Composer project file The BSMAccelerator_1r1 project file is installed for the Business Serice Composer as part of the Solutions for Business Serice Management installation. This project file defines the static resource definitions and policy pattern definitions that create the modeling structure used by Solutions for Business Serice Management. When the project file is loaded, a new notifications rules artifact is generated. This artifact defines the mechanism for the interaction of Impact policies with resource, attribute, and relationship data that is imported into the Serice Component Repository. It also creates the idml Discoery Library book that defines the static resources. 132 Solutions for BSM Guide:

145 When the notifications file and in idml book are generated, the notifications rules file is loaded into the TBSM database and is assigned a name. The naming conention for this file follows the conention: BC.ProductName=BSMAccelerator+Manufacturer=IBM+Hostname=<hostname of the Discoery Library Toolkit machine>.notifications.xml where the book's file name source identification, the management software system (MSS), is deried from the project properties. The idml book is assigned a name based on the conention: BSC-itbsm.ProductName=BSMAccelerator+Manufacturer=IBM+Hostname=bsc.<hostname of the Discoery Library Toolkit machine>.<timestamp when file was generated>.refresh.xml where the book's file name source identification, the management software system (MSS), is deried from the project properties. The idml book is placed in the books directory defined by DL_FileSystem property of the Discoery Library Toolkit. This property is set in the xmltoolkitsc.properties file located in the $TBSM_HOME/XMLtoolkit/bin directory. Business Serice Composer policy pattern A Business Serice Composer pattern called DefineTechGroups_1.0 is used to define the Solutions for Business Serice Management structure model. The structure model defined by Solutions for Business Serice Management is easy to customize to meet your requirements. For more information about using the Business Serice Composer, see the TBSM wiki located: home?lang=en#/wiki/tioli%20business%20serice%20manager1 Netcool/Impact policies for the Solutions for BSM The TBSM BSMAccelerator project proides a number of Netcool/Impact policies. Three of these policies were created for the IBM Solutions for Business Serice Managementand are used to customize charts. The fourth policy, Main_CheckForDepsEntry is used to perform eent enrichment. This topic proides information on the Impact policies in the BSMAccelerator project. Note: All of the policies in the TBSM BSMAccelerator project apply to the TBSM Data serer. Charting policies These policies are used to customize charts in TBSM: BusinessSericeChartLib This policy contains a library of JaaScript functions that are used to generate the x and y data points for the custom charts proided as part of the Solutions for BSM. This data is imported into Business Intelligence and Reporting Tools (BIRT) to create the required charts. BusinessSericeEentCountChart This policy is inoked when the charting portlet renders the Business Serice Eent Count Oer Time chart. Chapter 5. Product modifications 133

146 BusinessSericeOerTimeChart This policy is inoked when the charting portlet renders the Business Serice Status Oer Time chart. Eent enrichment policy This policy is used for eent enrichment in TBSM: Main_CheckForDepsEntry This policy was aailable as part of the TBSM installation, but it has been customized for the Solutions for BSM to perform eent enrichment for the Serice and Function columns in the raw eents. Customizing eent enrichment behaior You can customize the eent enrichment behaior in the IBM Solutions for Business Serice Management by editing the Main_CheckForDepsEntry policy in the BSMAccelerator project. This topic outlines the procedure to make changes to aspects of eent enrichment behaiour in Netcool/Impact. 134 Solutions for BSM Guide: Disabling eent enrichment If it is necessary for you to disable eent enrichment, follow this procedure: 1. In the naigation tree, expand System Configuration > Eent Automation > Policies. 2. From the Project list, choose BSMAccelerator. 3. Double-click the Main_CheckForDepsEntry policy in the Policies list. The Main_CheckForDepsEntry policy is displayed. 4. Locate and add the opening comment symbol /* to the lines // The following is a BSMAccelerator feature to enrich the raw eents with the high leel// business serice and technology groupings it affects 5. Add the comment end symbol */ to the line that reads: // END section for BSMAccelerator Note: This line is at the end of the policy. 6. Click Sae to sae your changes. Changing the delimiter between business serices If an eent affects multiple business serices, the business serice names are shown in the enriched field concatenated with colon (:) as the delimiter. If you want to change that delimiter, for example to an underscore, you must change the following lines in the policy: 1. In the naigation tree, expand System Configuration > Eent Automation > Policies. 2. From the Project list, choose BSMAccelerator. 3. Double-click the Main_CheckForDepsEntry policy in the Policies list. The Main_CheckForDepsEntry policy is displayed. 4. Locate and edit the line: ExistingSerices = split(theserice, ":"); to read: ExistingSerices = split(theserice, "_"); 5. Change the line:

147 TheSerice = TheSerice + ":" + InstanceToProcess.displayname; to read: Netcool/OMNIbus updates TheSerice = TheSerice + "_" + InstanceToProcess.displayname; 6. Click Sae to sae your changes. This topic documents IBM Solutions for Business Serice Management updates to IBM Tioli Netcool/OMNIbus. The deployment wizard will apply changes to the following components of the IBM Tioli Netcool/OMNIbus installation: Netcool/OMNIbus ObjectSerer database Netcool/OMNIbus EIF Probe rules Netcool/OMNIbus WebGUI (iew and filter) ObjectSerer database updates The IBM Solutions for Business Serice Management deployment wizard creates new tables, columns, and triggers in the ObjectSerer database. These changes are a result of the IBM Solutions for Business Serice Management deployment wizard running the following scripts: sitforwardir/omnibus/itm_proc.sql (Tioli Monitoring Eent Integration) sitforwardir/omnibus/itm_db_update.sql (Tioli Monitoring Eent Integration) sitforwardir/omnibus/itm_sync.sql (Tioli Monitoring Eent Integration) sitforwardir/omnibus/itm_eent_cache.sql (Tioli Monitoring Eent Integration) itcam_eent/omnibus/sql_update.sql (ITCAM Eent Integration) OMNIbus/Schema/bsm_accelerator_schema.sql (additional fields required by Solutions for BSM) Business Serice Manager related changes The IBM Solutions for Business Serice Management deployment wizard adds the following columns (slots) to the alert.status table: BSMAccelerator_Serice The defined business serice/system, application or collection as defined in TADDM. BSMAccelerator_Function The technology type in which the BSMAccelerator_Serice resides. Remember: The aboe changes are applied on top of the changes that the Business Serice Manager installer makes to the OMNIbus schema. For more information about these changes, see the Tioli Business Serice Manager 6.1 documentation. For example, see IBM Tioli Netcool OMNIbus Considerations at this URL: com.ibm.tioli.itbsm.doc_6.1/installguide/bsmi_c_netcool_omnibus.html Chapter 5. Product modifications 135

148 Monitoring Situation Forwarder and Eenting related changes The IBM Tioli Monitoring Situation Forwarder and Eenting related changes make possible receiing and mapping the situation eents forwarded by an IBM Tioli Monitoring Serer. They are required to enable eent correlation between the objects in the IBM Tioli Business Serice Manager serice model with eents contained in the ObjectSerer. After applying the updates these eents can also be iewed in WebGUI. Tables The following tables are created by the itm_proc.sql script: alerts.itm_send_eents alerts.itm_loopback_eents alerts.itm_situation_timeouts The following table is created by itm_db_update.sql script: alerts.itm_problem_eents Columns The following columns (slots) added to the alert.status table by the itm_db_update.sql script: TECHostname TECFQHostname TECDate TECRepeatCount ITMStatus ITMDisplayItem ITMEentData ITMTime ITMHostname ITMPort ITMIntType ITMResetFlag ITMSitType ITMThruNode ITMSitGroup ITMSitFullName ITMApplLabel ITMSitOrigin Desktop type conersions The following desktop type conersions added to the alerts.conersions table by the itm_db_update.sql script: ITM Problem ITM Resolution 136 Solutions for BSM Guide:

149 Triggers These triggers are added by the itm_db_update.sql script: itm_eent_clear itmerror itm_deduplication thrunode_change_handler itm_eent_clear These triggers are added by the itm_sync.sql script: itm_eent_send start_suf stop_suf check_suf_status process_sit_timeout deduplication_itm_loopback_eents deduplication_itm_send_eents synchronizeitm deleteitm Procedures The following procedures are added by the itm_proc.sql script: eentcmd get_debug_itmsync get_config_parms get_sit_timeout get_install_loc get_itmfile send_to_itm resole_itm_action sendackbacktoitm Composite Application Manager for Transactions related changes IBM Tioli Composite Application Manager for Transactions requires the addition of the following columns (slots) to the alert.status table: CAM_Application_Name CAM_Transaction_Name CAM_SubTransaction_Name CAM_Client_Name CAM_Serer_Name CAM_Profile_Name CAM_Response_Time CAM_Percent_Aailable CAM_Expected_Value CAM_Actual_Value CAM_Details Chapter 5. Product modifications 137

150 CAM_Total_Requests EIF Probe rules updates The IBM Solutions for Business Serice Management deployment wizard copies a set of rules to the EIF probe directory, by default, $NCHOME/omnibus/probes/ {architecture}. The rules are also included in the EIF probe rules file, tioli_eif.rules, that you can find in the same directory. For example, /opt/ibm/tioli/netcool/omnibus/ probes/linux2x86/tioli_eif.rules. Monitoring Situation Forwarder and Eenting rules The IBM Tioli Monitoring rules coer OS, Database, WAS, and HTTP. The following rules are copied to the EIF probe directory: itm_eent.rules tbsm_eif_eent.rules At the same time, itm_eent.rules is included in the EIF probe rules file, with the following "include" statement: include "itm_eent.rules" And tbsm_eif_eent.rules is included in the itm_eent.rules file: include "tbsm_eif_eent.rules" Important: If, for some reason, the rules files are not found in the default directory, the EIF probe directory, the include statement must contain the full path to the rule file. Composite Application Manager for Transactions rules The IBM Tioli Composite Application Manager for Transaction rules coer Application Management Console (AMC), Client Response Time (CRT), Web Response Time (WRT), Robotic Response Time (RRT) and Transaction Tracking (TT). The following rules are copied to the probe directory and included in the EIF rules file: custom_mapping.rules kt3.rules (AMC) kt4.rules (CRT) kt5.rules (WRT) kt6.rules (RRT) kto.rules (TT) For example, on Linux: include "custom_mapping.rules" include "kt3.rules" include "kt4.rules" include "kt5.rules" include "kt6.rules" include "kto.rules" Application Discoery Manager rules These rules coer IBM Tioli Application Discoery Manager change eents. 138 Solutions for BSM Guide:

151 The rules file, tioli_eif_taddm.rules, is copied to the probe directory and included with the following statement in the EIF probe rules file: include "tioli_eif_taddm.rules" Monitoring for Virtual Enironments rules These rules coer IBM Tioli Monitoring for Virtual Enironments (VMWare Agent). The VMWare rules file, km_tbsm.rules, is copied to the probe directory and included in the EIF probe rules file: include "km_tbsm.rules" WebGUI AEL filtering The IBM Solutions for Business Serice Management deployment wizard adds the BSMAccelerator_Health iew and filter to the WebGUI. Configuring Tioli Application Dependency Discoery Manager This topic outlines the steps that you must complete to configure Tioli Application Dependency Discoery Manager with the IBM Solutions for Business Serice Management. Configuring Tioli Application Dependency Discoery Manager for TBSM There are a number of configuration tasks that you must complete when integrating Tioli Application Dependency Discoery Manager with TBSM. If you hae preiously installed TBSM and are using Tioli Application Dependency Discoery Manager, it is likely that you hae already completed these tasks. For additional information about the procedures for any of these configuration steps, refer to the Tioli Application Dependency Discoery Manager Information Center. Discoery profiles Create a Tioli Application Dependency Discoery Manager discoery profile. A discoery profile defines a set of options for discoery, including sensor discoery modes, discoery scope, and configuration details for indiidual sensors. You can use profiles to manage multiple configurations of the same sensor, pick the appropriate configuration based on a set of criteria, and manage sets of configurations of different sensors to be applied on a single discoery run. Create a discoery profile that is based on the Leel 3 discoery defined by Tioli Application Dependency Discoery Manager. Leel 3 discoery captures information about the entire application infrastructure, including physical serers, network deices, irtual LANs, host configuration, deployed software components, application configuration, and host data used in the enironment. This leel of discoery requires application operating-system and application credentials. In the newly created profile, create a new configuration for the WebSphere Cell sensor to enable deep discoery. Groups Compose a business application, business system, serice or collection within the Tioli Application Dependency Discoery Manager Data Management Portal Grouping composer. Only those discoered elements Chapter 5. Product modifications 139

152 within Tioli Application Dependency Discoery Manager that hae been associated with one or more business applications, business systems, serices or collections can be added to the Solutions for BSM. Scopes Proide IP scopes that include the system that you want to discoer. Authorization Add the login details for each operating system or application that you want Tioli Application Dependency Discoery Manager to discoer. DLA configuration required for the Solutions for BSM In addition to the standard configuration steps, there are a number of tasks that you must complete for Tioli Application Dependency Discoery Manager in the Solutions for BSM. There are three Discoery Library Adapters (DLAs) that must be run and loaded into Tioli Application Dependency Discoery Manager: Tioli Monitoring Serices (TMS) DLA IBM Tioli Composite Application Manager For Transaction Tracking (ITCAMfTT) DLA IBM Tioli Composite Application Manager For Response Tracking (ITCAMfRT) DLA The TMS DLA and ITCAMfTT reconciled for DB2 and WebSphere objects. The Solutions for BSM installs the addwasmsndla command in the Tioli Application Dependency Discoery Managerdist/bin directory. This command allows you to perform the reconciliation. Run the command and then load the resulting reconciled DLA into Tioli Application Dependency Discoery Manager. Note: Before you run the addwasmsndla command, you must complete a deep discoery of WebSphere Application Serer. Note: When the addwasmsndla command completes, an IdML book is created with a file name similar to the original IdML book but with the extension.reconciled.xml When you are importing the IdML book into Tioli Application Dependency Discoery Manager, you must import the file with the.reconciled.xml file extension. After you hae run addwasmsndla and loaded the output into Tioli Application Dependency Discoery Manager, run the Tioli Application Dependency Discoery Manager loadidml command to load the ITCAMfRT DLA into Tioli Application Dependency Discoery Manager. Discoery Library Adapter for the HTTP serer monitoring agent 140 Solutions for BSM Guide: The Discoery Library Adapater (DLA) for the HTTP serer monitoring agent creates Common Data Model (CDM) resource definitions based on data from the ITCAM Agent for HTTP Serers. These resource definitions are used by TBSM to correlate eents from the agent with discoery data from TADDM. For each monitored HTTP serer, the DLA creates a CDM WebSerer object that conforms to the Primary SAP naming rules. This makes it possible to reconcile eents from the ITCAM Agent for HTTP Serers with discoery data from TADDM so that eents can be associated with the correct serers shown in the TBSM serice tree.

153 Een if TADDM discoery data is not aailable, TBSM can use the IdML book generated by the DLA for eent correlation. About the HTTP Serer Agent DLA The Tioli Management Serices DLA discoers resources and relationships and creates a Discoery Library Book file. The Book file follows the Discoery Library IdML schema and is used to populate the Configuration Management Database (CMDB) and Tioli Business System Management products. The Tioli Management Serices DLA discoers resources and relationships and creates a Discoery Library Book file. The Book file follows the Discoery Library IdML schema and is used to populate the Configuration Management Database (CMDB) and Tioli Business System Management products. The Tioli Management Serices DLA discoers HTTP serer resources. For all HTTP serer systems that are actie and online at the Tioli Enterprise Portal Serer, information is included in the discoery book for those resources. The Tioli Management Serices DLA discoers actie resources. It is run on demand and can be run periodically to discoer resources that were not actie during preious discoeries. The DLA discoers HTTP serer components. More information about DLAs The following sources contain additional information about using the DLA program with all monitoring agents: The IBM Tioli Monitoring Administrator's Guide contains information about using the Tioli Management Serices Discoery Library Adapter. For information about using a DLA with Tioli Application Dependency Discoery Manager (TADDM), see the information center at com.ibm.taddm.doc_7.2/welcome_page/welcome.html. For information about using a DLA with the Tioli Business Serice Manager product, see the information center at infocenter/tiihelp/3r1/topic/com.ibm.tioli.itbsm.doc/customization/ bsms_dscc_discoerylibraryeentmapping.html. HTTP Serer Agent data model classes This section contains information about how the arious source application data objects map to classes in the Common Data Model (CDM) for the ITCAM Agent for HTTP Serers. The following information is proided for each class: CDM class name Class name for which the agent is proiding information Relationships CDM hierarchical relationships between currently identified model objects CDM attributes, agent attributes, descriptions, and examples CDM and agent attributes that are required to create an instance of a resource, with descriptions and examples of the attributes Chapter 5. Product modifications 141

154 ManagementSoftwareSystem class This class represents the source application that proided the data about the monitored resources. CDM class name process.managementsoftwaresystem Relationships None CDM attributes, agent attributes, descriptions, and examples Table 4. Management SoftwareSystem class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example MSSName None A unique identifier for the management software system, proided by the TMS DLA. Manufacturer None The manufacturer of the management software system. ProductName None The product name of the management software system. ProductVersion None The ersion and release of the management software system. ibm-cdm: ///CDMMSS/ Hostname= x86ondemand06 +ManufacturerName =IBM+ProductName =IBM Tioli Monitoring Serices IBM IBM Tioli Monitoring Serices WebSerer class This class represents an instance of an HTTP serer. CDM class name app.web.webserer Relationships As source: Relationship runson runson accessedvia Target sys.computersystem sys.operatingsystem net.bindaddress As target: 142 Solutions for BSM Guide:

155 Relationship monitors Source app.tmsagent CDM attributes, agent attributes, descriptions, and examples Table 5. WebSerer class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example Name ProductName ProductVersion Status ManagedSystem Name KHT.KHTWSRS: SERVER_NAM KHT.KHTAWEBSR: VER KHT.KHTAWEBSR: VER KHT.KHTAWEBSR: STATUS None (TMS DLA ariable %{MSYSN} The name of the HTTP serer. The product name of the HTTP serer. The ersion and release of the HTTP serer. The current status of the HTTP serer. The managed system name of the HTTP Serer agent. KeyName None (static alue) The static alue AppSerer. IBM_HTTP_Serer (Unix) Running daytrader: delta01:khtp AppSerer BindAddress class This class represents the combination of an IP address and TCP port, and is used to indicate the port number of the HTTP serer. CDM class name net.bindaddress Relationships As source: Relationship bindsto bindsasprimary Target net.ipv4address net.ipv4address As target: Relationship accessedvia Source app.web.webserer CDM attributes, agent attributes, descriptions, and examples Table 6. BindAddress class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example PortNumber KHT.KHTWSRS: SERVER_NAM The TCP port number of the HTTP serer. 80 Chapter 5. Product modifications 143

156 Table 6. BindAddress class: CDM attributes, agent attributes, descriptions, and examples (continued) CDM attribute Agent attribute Description Example Path None Used only for Windows serers; otherwise, the static string (none). (none) IpV4Address class This class represents the IP4 address of the HTTP serer. CDM class name net.ipv4address Relationships As source: Relationship bindsto bindsasprimary Target net.bindaddress net.bindaddress As target: Relationship assignedto Source net.fqdn CDM attributes, agent attributes, descriptions, and examples Table 7. IpV4Address class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example DotNotation O4SRV.INODESTS: HOSTADDR The IP address in standard dotted-decimal notation StringNotation O4SRV.INODESTS: HOSTADDR The IP address in string form Fqdn class This class represents the fully qualified domain name of the HTTP serer (an attribute of the IpAddress class). CDM class name net.fqdn Relationships As source: Relationship assignedto Target net.ipv4address 144 Solutions for BSM Guide:

157 CDM attributes, agent attributes, descriptions, and examples Table 8. Fqdn class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example Fqdn KHT.KHTWSRS: SERVER_NAM The fully qualified domain name. TMSAgent class This class represents a Tioli Monitoring Serices agent. CDM class name app.tmsagent Relationships As source: Relationship monitors Target app.web.webserer CDM attributes, agent attributes, descriptions, and examples Table 9. TMSAgent class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Agent attribute Description Example ManagedObject Name ManagedSystem Name SoftwareVersion ProductCode Affinity Name Label TMSDLA Var: % {SUBNODE_MSYSN} TMSDLA Var: % {SUBNODE_MSYSN} TMSDLA Var: % {PRODVER} TMSDLA Var: % {PRODUCT} TMSDLA Var: % {PRODAFF} TMSDLA Var: % {SUBNODE_MSYSN} TMSDLA Var: % {SUBNODE_MSYSN} The name of the ITCAM component that proides data for the management of the HTTP serer agent instance. The name of the ITCAM component that proides data for the management of the HTTP serer agent instance. The ersion of the HTTP serer agent instance. The product code of the HTTP serer agent instance. The affinity of the HTTP serer agent. The name of the HTTP serer agent. The label of the HTTP serer agent. p@delta01:khta delta01:khta HT G yw0a7 daytrader:delta01: KHTP- WebSererAgent daytrader:delta01: KHTP- WebSererAgent Chapter 5. Product modifications 145

158 Discoery Library Adapter for ITCAM for Transactions agents The ITCAM for Transactions Discoery Library Adapater (DLA) creates Common Data Model (CDM) resource definitions based on data from the ITCAM for Transactions Web Response Time, Robotic Response Time, and Client Response Time agents. These resource definitions are used by TBSM to correlate eents from the agent with discoery data from TADDM. This DLA is an enhancement to the ITCAM for Transactions DLA to proide the following resource definitions and the relationships among them: BusinessProcess (applications) Actiity (transactions and subtransactions) Client (homogeneous collections) Serer (application serers) This data enables TADDM to discoer business transactions and associate them with business applications in the TBSM serice model. About the ITCAM for Transactions DLA The Tioli Management Serices DLA discoers resources and relationships and creates a Discoery Library Book file. The Book file follows the Discoery Library IdML schema and is used to populate the Configuration Management Database (CMDB) and Tioli Business System Management products. For more information about the ITCAM for Transactions DLA, see the ITCAM for Transactions documentation at 24r1/topic/com.ibm.itcamt.doc_7.3/rt/User%20Guide/TBSM/ tbsm_dla_oeriew.html. ITCAM for Transactions agent data model classes This section contains information about how the arious source application data objects map to classes in the Common Data Model (CDM) for the ITCAM for Transactions Web Response Time, Robotic Response Time, and Client Response Time agents. The following information is proided for each class: CDM class name Class name for which the agent is proiding information Relationships CDM hierarchical relationships between currently identified model objects CDM attributes, agent attributes, descriptions, and examples CDM and agent attributes that are required to create an instance of a resource, with descriptions and examples of the attributes BusinessProcess class This class represents a high-leel business serice or application that can hae multiple child transactions (represented by the Actiity class) and clients (represented as the HomogeneousCollection class). CDM class name process.businessprocess 146 Solutions for BSM Guide:

159 Relationships As source: Relationship federates uses uses Target process.actiity net.fqdn process.homogeneouscollection As target: Relationship monitors Source app.tmsagent CDM attributes, agent attributes, descriptions, and examples Table 10. BusinessProcess class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example ActiityName Situation Application Name from ITM situation definition A user-defined identifier for the business application or serice. Bank21 DisplayName Situation Application Name from ITM situation definition A user-defined identifier for the business application or serice. Bank21 SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. managed_system_name= DayTrader: x86ondemand10:kt3a Actiity class This class represents a transaction. CDM class name process.actiity Relationships As source: Relationship uses uses uses Target net.fqdn process.homogeneouscollection app.appserer Chapter 5. Product modifications 147

160 As target: Relationship federates monitors Source process.businessprocess app.tmsagent CDM attributes, agent attributes, descriptions, and examples Table 11. Actiity class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example ActiityName Web Response Time agent: Application name + transaction separator + transaction column in the TxOT table Web Response Time agent (clients only): Application name + transaction separator + transaction column in the TxOT table + client separator + client column in the TxOT table Client Response Time and Robotic Response Time agents: Application Name + application separator + transaction column in the TxOT table A user-defined identifier for the business application or serice. DisplayName TransactionName A user-defined identifier for the transaction. SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. Web Response Time agent: DayTrader#t #login#c#all Clients Robotic Response Time agent: DayTrader# t#login CheckBalance managed_system _name= DayTrader: x86ondemand10: KT3A IpAddress class This class represents the IP address of the application serer. CDM class name net.ipaddress Relationships As target: Relationship assignedto bindsto bindstoasprimary Source net.fqdn net.bindaddress net.bindaddress 148 Solutions for BSM Guide:

161 CDM attributes, agent attributes, descriptions, and examples Table 12. IpAddress class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example StringNotation DisplayName SourceToken DNS lookup of domain name DNS lookup of domain name Application Name attribute (Application Management Console agent) The numeric IP address in string form. The numeric IP address in string form. A unique identifier for the business application or serice managed_system _name =DayTrader: x86ondemand10: KT3A Fqdn class This class represents the fully qualified domain name of the application serer. CDM class name net.fqdn Relationships As source: Relationship assignedto Target net.ipaddress As target: Relationship uses uses Source process.actiity process.businessprocess CDM attributes, agent attributes, descriptions, and examples Table 13. Fqdn class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example Fqdn Serer column in TxOT table The fully qualified domain name of the application serer DisplayName Serer column in TxOT table The fully qualified domain name of the application serer SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. managed_system_name= DayTrader:x86ondemand10: KT3A Chapter 5. Product modifications 149

162 TMSAgent class This class represents a Tioli Monitoring Serices agent. CDM class name app.tmsagent Relationships As source: Relationship monitors monitors Target process.businessprocess process.actiity CDM attributes, agent attributes, descriptions, and examples Table 14. TMSAgent class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example ManagedSystem Name Origin_node column in TxOT table The name of the ITCAM for Transactions component proiding the data. ProductCod Agent product code The product code of the ITCAM for Transactions agent proiding the data. SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. Primary:hours:T4 T5 managed_system _name=daytrader: x86ondemand10: KT3A AppSerer class This class represents a monitored application serer. CDM class name app.appserer Relationships As target: Relationship uses Source process.actiity 150 Solutions for BSM Guide:

163 CDM attributes, agent attributes, descriptions, and examples Table 15. AppSerer class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example Name Serer column in TxOT table The name of the application serer, if defined as an IP address and TCP/IP port :80 Label Serer column in TxOT table The name of the application serer, if defined as an IP address and TCP/IP port :80 KeyName None (hardcoded alue) The string AppSerer AppSerer SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. managed_system_name= DayTrader:x86ondemand10: KT3A Note: If the alue in the Serer column of the TxOT table does not match the pattern ip_address:port_number, no AppSerer object is created. BindAddress class This class represents the IP address of the application serer. CDM class name net.bindaddress Relationships As source: Relationship bindsto bindstoasprimary Target net.ipaddress net.ipaddress As target: Relationship accessedvia Source app.appserer CDM attributes, agent attributes, descriptions, and examples Table 16. BindAddress class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example ManagedSystem Name Origin_node column in TxOT table The name of the ITCAM for Transactions component proiding the data. Primary:hours:T4 Chapter 5. Product modifications 151

164 Table 16. BindAddress class: CDM attributes, agent attributes, descriptions, and examples (continued) CDM attribute Source Description Example SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. managed_system _name =DayTrader: x86ondemand10: KT3A HomogeneousCollection class This class represents a client of the application serer. CDM class name process.homogeneouscollection Relationships As target: Relationship uses uses Source process.actiity process.businessprocess CDM attributes, agent attributes, descriptions, and examples Table 17. HomogeneousCollection class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example Name Application + client separator + Client column in TxOT table Label Application + client separator + Client column in TxOT table The name of the client The name of the client DayTrader#c#All Clients DayTrader#c#All Clients SourceToken Application Name attribute (Application Management Console agent) A unique identifier for the business application or serice. managed_system_name =DayTrader: x86ondemand10:kt3a 152 Solutions for BSM Guide:

165 Discoery Library Adapter for ITCAM Agent for WebSphere Applications The Discoery Library Adapter (DLA) for the ITCAM WebSphere monitoring agent creates Common Data Model (CDM) resource definitions based on data from the ITCAM for Applications Agent for WebSphere Applications. These resource definitions are used by TBSM to correlate eents from the agent with discoery data from TADDM. The ITCAM monitoring Agent for WebSphere Applications is a component of ITCAM for Applications and ITCAM for Application Diagnostics. If you use transaction tracking, you need to use the Agent for WebSphere Applications as part of ITCAM for Applications Diagnostics where the Managing Serer functionality is also aailable. For each monitored WebSphere application serer, the DLA creates a CDM WebSphereSerer object containing a WebSphereProperty object. The addwasmsndla script, which runs on the TADDM serer, searches the TADDM database for discoered WebSphere serers that match the attributes of the WebSphereProperty objects created by the DLA. When a match is found, the script creates a CDM BindAddress object conforming to the PrimarySAP naming rule. Consequently it is possible to reconcile eents from the WebSphere monitoring agent with discoery data from TADDM. As a result, eents can be associated with the correct serers shown in the TBSM serice tree. Een if TADDM discoery data is not aailable, TBSM can use the IdML book generated by the DLA for eent correlation. About the WebSphere Agent DLA The Tioli Management Serices DLA discoers resources and relationships and creates a Discoery Library Book file. The Book file follows the Discoery Library IdML schema and is used to populate the Configuration Management Database (CMDB) and Tioli Business System Management products. The Tioli Management Serices DLA discoers WebSphere serer resources. For all WebSphere serer systems that are actie and online at the Tioli Enterprise Portal Serer, information is included in the discoery book for those resources. The Tioli Management Serices DLA discoers actie resources. It is run on demand and can be run periodically to discoer resources that were not actie during preious discoeries. The DLA discoers WebSphere serer components. More information about DLAs The following sources contain additional information about using the DLA program with all monitoring agents: The IBM Tioli Monitoring Administrator's Guide contains information about using the Tioli Management Serices Discoery Library Adapter. For information about using a DLA with Tioli Application Dependency Discoery Manager (TADDM), see the information center at com.ibm.taddm.doc_7.2/welcome_page/welcome.html. Chapter 5. Product modifications 153

166 For information about using a DLA with the Tioli Business Serice Manager product, see the information center at infocenter/tiihelp/3r1/topic/com.ibm.tioli.itbsm.doc/customization/ bsms_dscc_discoerylibraryeentmapping.html. WebSphere Agent data model classes This section contains information about how the arious source application data objects map to classes in the Common Data Model (CDM) for the ITCAM for Application Diagnostics Agent for WebSphere Applications. The following information is proided for each class: CDM class name Class name for which the agent is proiding information Relationships CDM hierarchical relationships between currently identified model objects CDM attributes, agent attributes, descriptions, and examples CDM and agent attributes that are required to create an instance of a resource, with descriptions and examples of the attributes ManagementSoftwareSystem class This class represents the source application that proided the data about the monitored resources. CDM class name process.managementsoftwaresystem Relationships None CDM attributes, agent attributes, descriptions, and examples Table 18. ManagementSoftwareSystem class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example MSSName TMS DLA A unique identifier for the management software system, proided by the TMS DLA. Manufacturer TMS DLA The manufacturer of the management software system. ProductName TMS DLA The product name of the management software system. Product Version TMS DLA The ersion and release of the management software system. ibm-cdm:///cdmmss/ Hostname= x86ondemand06+ ManufacturerName= IBM+ProductName= IBM Tioli Monitoring Serices IBM IBM Tioli Monitoring Serices Solutions for BSM Guide:

167 WebSphereSerer class This class represents an instance of a WebSphere serer. CDM class name app.j2ee.websphere.websphereserer Relationships As source: Relationship runson runson accessedvia contains Source sys.computersystem sys.operatingsystem net.bindaddress app.j2ee.websphere.websphereproperty As target: Relationship monitors Source app.tmsagent CDM attributes, agent attributes, descriptions, and examples Table 19. WebSphereSerer class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example Name KYNAPSST:NODENAME KYNAPSST:SERVERNAME The node name and serer name of the WebSphere serer. ProductName None (hardcoded alue) The string IBM WebSphere Application Serer ProductVersion KYNAPSRV:WAS_VER The product ersion of the WebSphere serer. Status KYNAPSST:STATUS The current status of the WebSphere serer. ManagedSystem Name TMS DLA ariable %{MSYSN} The managed system name of the WebSphere agent. KeyName None (hardcoded alue) The string AppSerer delta03node01: TradeSerer2 IBM WebSphere Application Serer Running delta03node01 TradeS: delta03:kyns AppSerer WebSphereProperty class This class represents an instance of a WebSphere serer property. Chapter 5. Product modifications 155

168 CDM class name app.j2ee.websphere.websphereproperty Relationships As target: Relationship contains Source app.j2ee.websphere.websphereserer CDM attributes, agent attributes, descriptions, and examples Table 20. WebSphereProperty class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example Name KYNAPSST:DIR_NAME KYNAPSST:NODENAME KYNAPSST:SERVERNAME KYNAPSST:CELLNAME The cell name, node name, and serer name of the WebSphere serer. Value INODESTS:HOSTADDR The IP address of the WebSphere serer. TADDMITMMSNLINK: /opt/ibm/websphere /AppSerer/profiles/ AppSr01 /config/cells/delta02cell01 /nodes/delta03node01/ serers /TradeSerer2/serer.xml BindAddress class This class represents the TCP/IP port of the WebSphere serer. CDM class name net.bindaddress Relationships As source: Relationship bindsto bindsasprimary Target net.ipv4address net.ipv4address As target: Relationship accessedvia Source app.j2ee.websphere.websphereserer 156 Solutions for BSM Guide:

169 CDM attributes, agent attributes, descriptions, and examples Table 21. BindAddress class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example PortNumber ADDWASMSN:TADDM The TCP/IP port of the WebSphere serer. 80 Path Static The string (none). (none) IpV4Address class This class represents the IP4 address of the WebSphere serer. CDM class name net.ipv4address Relationships As target: Relationship bindsto bindsasprimary Source net.bindaddress net.bindaddress CDM attributes, agent attributes, descriptions, and examples Table 22. IpV4Address class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example DotNotation INODESTS:HOSTADDR The IP address in standard dotted-decimal notation. StringNotation INODESTS:HOSTADDR The IP address in string form TMSAgent class This class represents a Tioli Monitoring Serices agent. CDM class name app.tmsagent Relationships As source: Relationship monitors Target app.j2ee.websphere.websphereserer Chapter 5. Product modifications 157

170 CDM attributes, agent attributes, descriptions, and examples Table 23. TMSAgent class: CDM attributes, agent attributes, descriptions, and examples CDM attribute Source Description Example ManagedObjectName ManagedSystemName SoftwareVersion TMS DLA ariable %{SUBNODE_MSYSN} TMS DLA ariable %{SUBNODE_MSYSN} TMS DLA ariable %{PRODVER} The object name of the WebSphere agent. The system name of the WebSphere agent. The ersion of the WebSphere agent. ProductCode Agent product code The product code of the WebSphere agent. Affinity Name Label TMS DLA ariable %{PRODAFF} TMSDLA Var: %{SUBNODE_MSYSN} TMSDLA ariable %{SUBNODE_MSYSN} The affinity of the WebSphere agent. The name of the WebSphere agent. The label of the WebSphere agent. TradeS:delta02: KYNS delta02node01 TradeS:delta02: KYNS YN yw0a7 delta02node01 TradeS:delta02: KYNS-KYNAgent delta02node01 TradeS:delta02: KYNS-KYNAgent Predefined situations for Solutions for BSM The IBM Solutions for Business Serice Management includes a set of predefined situations for IBM Tioli Monitoring (ITM) agents. These situations are intended to implement effectie monitoring for s for operating systems, databases, middleware, and irtual machines. Predefined situations for ITM OS agents The IBM Solutions for Business Serice Management includes a set of predefined situations for IBM Tioli Monitoring (Tioli Monitoring) operating system agents. These situations are intended to implement effectie operating system monitoring for most enironments. Situations are proided for the following Tioli Monitoring agents: Monitoring Agent for UNIX OS Monitoring Agent for UNIX Logs Premium Monitoring Agent for AIX Monitoring Agent for Linux OS Monitoring Agent for Windows OS 158 Solutions for BSM Guide:

171 The situations are named using the following conention: target_agent_name_seerity where: target agent name seerity The target operating system type (AIX, UNIX, Linux, or Windows) The two-letter product code of the agent A descriptie name for the situation The seerity of eents generated by the situation (WARNING or CRITICAL) AIX situations The following predefined situations monitor AIX systems. These situations are run by the Premium Monitoring Agent for AIX (product code PX) and the Monitoring Agent for UNIX Logs (product code UL). For more information about these agents, including the supported AIX ersions, refer to the Tioli Monitoring documentation. Table 24. Predefined AIX situations Situation name Description Seerity Formula AIX_PX_LparEntUsedPct_W Monitors the LPAR CPU utilization for alues exceeding 100 percent of its entitlement. WARNING *IF *VALUE KPX_LOGICAL_PARTITION. Entitlement_Used_Pct *GT 100 AIX_UL_Errpt_C AIX_UX_ProcMissing_C Monitors the /ar/adm/ras/errlog file for entries of class Error_logger(O), Hardware(H), or Software (S), with types of errors P (PERF, PEND, PERM), U (UNKN), or I (INFO). Monitors specified processes that are not running, either because they hae been stopped or because they were neer started. CRITICAL CRITICAL *IF ((*VALUE Log_Entries.Class *EQ 'Error_Logger' *AND ((( *VALUE Log_Entries.Type *EQ I ) *OR ( *VALUE Log_Entries.Type *EQ P ) *OR ( *VALUE Log_Entries.Type *EQ U))))*OR(*VALUE Log_Entries.Class *EQ Hardware *AND (((*VALUE Log_Entries.Type *EQ P ) *OR ( *VALUE Log_Entries.Type *EQ U))))*OR(*VALUE Log_Entries.Class *EQ Software *AND(((*VALUE Log_Entries.Type *EQ P ) *OR ( *VALUE Log_Entries.Type *EQ U))))) *IF *MISSING Process.Command_U *EQ ( '/usr/*/errdemon','/usr/*/ portmap','/usr/*/qdaemon','/ usr/*/srcmstr','/usr/*/syncd' ) Linux situations The following predefined situations monitor Linux systems. These situations are run by the Monitoring Agent for Linux OS (product code LZ). For more information about this agent, including the supported operating systems, refer to the Tioli Monitoring documentation. Chapter 5. Product modifications 159

172 Table 25. Predefined Linux situations Situation name Description Seerity Formula Linux_LZ_AgCpuBusyPct60Min_C Monitors the total CPU usage (including both system and user processes for all CPUs) for alues exceeding 95 percent. CRITICAL *IF *VALUE Linux_CPU_Aerages. CPU_Usage_Current_Aerage *GE 95.0 Linux_LZ_CpuBusyPct_C Linux_LZ_CpuWaitIO_W Linux_LZ_LoadAg5min_C Monitors for high CPU workload. Monitors CPU input/output waits. Monitors the load on the system during the last fie minutes. CRITICAL WARNING CRITICAL *IF ((*VALUE Linux_CPU.CPU_ID *NE Aggregate *AND *VALUE Linux_CPU.Busy_CPU *GT 95.0 ) *OR ( *VALUE Linux_CPU.CPU_ID *EQ Aggregate *AND *VALUE Linux_CPU.Busy_CPU *GT 90.0 ) ) *IF *VALUE Linux_CPU.Wait_IO_CPU *GT 10 *AND *VALUE Linux_CPU.CPU_ID *EQ Aggregate *IF ((*VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 1 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 4.0 ) *OR ( *VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 2 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 8 ) *OR ( *VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 3 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 12 ) *OR ( *VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 4 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 16 ) *OR ( *VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 6 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 24 ) *OR ( *VALUE Linux_Machine_Information. Number_of_Processors_Online *EQ 8 *AND *VALUE Linux_System_Statistics. System_Load_5min *GT 32 ) ) 160 Solutions for BSM Guide:

173 Table 25. Predefined Linux situations (continued) Situation name Description Seerity Formula Linux_LZ_NetTotalErrPct_W Monitors the percentage of errors from receied or transmitted network packets. WARNING *IF *VALUE Linux_Network.Total_Error_Percent *GT 10 Linux_LZ_NumberZombies_W Linux_LZ_ProcHighCpu_C Linux_LZ_ProcMissing_C Linux_LZ_SpaceUsedPct_C Linux_LZ_SwapSpaceUsedPct_C Linux_UL_SyslogError_C Monitors the number of defunct processes. Monitors the CPU utilization by all processes except kswapd. Monitors specified processes that are not running, either because they hae been stopped or because they were neer started. Monitors all mounted file systems for the percentage of space used. Monitors the the percentage of swap space used. Monitors log file for entries containing the string error. WARNING CRITICAL CRITICAL CRITICAL CRITICAL CRITICAL *IF *VALUE Linux_System_Statistics. Processes_Zombie_Count *GE 50 *IF *VALUE Linux_Process. Busy_CPU_Pct *GE 95.0 *AND *VALUE Linux_Process. Process_Command_Name_U *NE kswapd *IF *MISSING Linux_Process.Proc_CMD_Line_U *EQ ( '/usr/*/sshd','/usr/*/ syslogd','/usr/*/ntpd','/usr/*/ inetd','/usr/*/crond' ) *IF *VALUE Linux_Disk.Space_Used_Percent *GE 95 *AND *VALUE Linux_Disk.FS_Type *NE nfs *IF *VALUE Linux_VM_Stats.Swap_Pct_Used *GT 40 *IF ((*VALUE Log_Entries.Log_Path_U *EQ '/ar/adm' *AND *VALUE Log_Entries.Log_Name_U *EQ 'messages' *AND *SCAN Log_Entries.Description_U *EQ 'error' *AND *SCAN Log_Entries.Description_U *NE 'PAM' ) *OR ( *VALUE Log_Entries.Log_Path_U *EQ '/ar/log' *AND *VALUE Log_Entries.Log_Name_U *EQ 'messages' *AND *SCAN Log_Entries.Description_U *EQ 'error' *AND *SCAN Log_Entries.Description_U *NE 'pam_ldap' *AND *SCAN Log_Entries.Description_U *NE 'PAM' ) ) UNIX situations The following predefined situations monitor UNIX systems. These situations are run by the Monitoring Agent for UNIX OS (product code UX) and the Monitoring Agent for UNIX Logs (product code UL). Chapter 5. Product modifications 161

174 For more information about these agents, including the supported operating systems, refer to the Tioli Monitoring documentation. Table 26. Predefined UNIX situations Situation name Description Seerity Formula Unix_UL_SyslogError_C Monitors log file for entries containing the string error CRITICAL *IF ((*VALUE Log_Entries.Log_Path_U *EQ '/ar/adm' *AND *VALUE Log_Entries.Log_Name_U *EQ 'messages' *AND *SCAN Log_Entries.Description_U *EQ 'error' *AND *SCAN Log_Entries.Description_U *NE 'PAM' ) *OR ( *VALUE Log_Entries.Log_Path_U *EQ '/ar/log' *AND *VALUE Log_Entries.Log_Name_U *EQ 'messages' *AND *SCAN Log_Entries.Description_U *EQ 'error' *AND *SCAN Log_Entries.Description_U *NE 'pam_ldap' *AND *SCAN Log_Entries.Description_U *NE 'PAM' ) ) Unix_UX_AgCpuBusyPct5min_C Unix_UX_CpuBusyPct_C Monitors the total CPU usage (both system and user processes) for all CPUs. Monitors for high CPU workload. CRITICAL CRITICAL *IF *VALUE SMP_CPU.Ag_CPU_Busy_5 *GT 90 *AND *VALUE SMP_CPU.CPU_ID *EQ aggregate *IF ((*VALUE SMP_CPU.CPU_Busy *GT 90 *AND *VALUE SMP_CPU.CPU_ID *EQ aggregate ) *OR ( *VALUE SMP_CPU.CPU_Busy *GT 95 *AND *VALUE SMP_CPU.CPU_ID *NE aggregate ) ) 162 Solutions for BSM Guide:

175 Table 26. Predefined UNIX situations (continued) Situation name Description Seerity Formula Unix_UX_LoadAg5min_C Monitors the aerage number of processes in the UNIX kernel run queue during the last fie minutes. CRITICAL *IF ((*VALUE Machine_Information. Number_of_Physical_Processors *EQ 1 *AND *VALUE System.Load_Aerage_5_Min *GT 4.0 ) *OR ( *VALUE Machine_Information. Number_of_Physical_Processors *EQ 2 *AND *VALUE System.Load_Aerage_5_Min *GT 8 ) *OR ( *VALUE Machine_Information. Number_of_Physical_Processors *EQ 3 *AND *VALUE System.Load_Aerage_5_Min *GT 12 ) *OR ( *VALUE Machine_Information. Number_of_Physical_Processors *EQ 4 *AND *VALUE System.Load_Aerage_5_Min *GT 16 ) *OR ( *VALUE Machine_Information. Number_of_Physical_Processors *EQ 6 *AND *VALUE System.Load_Aerage_5_Min *GT 24 ) *OR ( *VALUE Machine_Information. Number_of_Physical_Processors *EQ 8 *AND *VALUE System.Load_Aerage_5_Min *GT 32 )) Unix_UX_NumberZombies_W Unix_UX_PagingRate_C Unix_UX_ProcMissing_C Monitors the number of defunct processes. Monitors the aerage number of pages examined per second during the sampling interal. Monitors specified processes that are not running, either because they hae been stopped or because they were neer started. WARNING CRITICAL CRITICAL *IF *VALUE System.Processes_Zombie *GE 50 *IF *VALUE System.Page_Scan_Rate *GT 500 *IF *MISSING Process.Command_U *EQ ( '/usr/*/cron','/usr/*/ dsmcad','/usr/*/gmond','/usr/*/ inetd','/usr/*/ntpd','/usr/*/ snmpd','/usr/*/sshd','/usr/*/ syslogd' ) Chapter 5. Product modifications 163

176 Table 26. Predefined UNIX situations (continued) Situation name Description Seerity Formula Unix_UX_ProcHighCpu_C Monitors the CPU utilization by all processes except kproc and swapper. CRITICAL *IF *VALUE Process.CPU_Utilization *GE 95 *AND *SCAN Process.Process_Command_U *NE 'wait' *AND *SCAN Process.Process_Command_U *NE 'swapper' *AND *SCAN Process.Process_Command_U *NE 'kproc' Unix_UX_NetInOutErrPct_W Unix_UX_SpaceUsedPct_C Unix_UX_SwapSpaceUsedPct_C Unix_UX_SysWaitIOPct_W Monitors the percentage of errors occurring with receied or transmitted network packets. Monitors all mounted file systems for the percentage of space used. Monitors the the percentage of swap space used. Monitors the percentage of time the CPU spends waiting for I/O operations. CRITICAL CRITICAL CRITICAL *IF ((*VALUE Network.Interface_Status *EQ Up *AND *VALUE Network.Input_Packet_ Errors_Percent *GT 10 ) *OR ( *VALUE Network.Interface_Status *EQ Up *AND *VALUE Network.Output_Packet_Errors _Percent *GT 10 ) ) *IF *VALUE Disk.Space_Used_Percent *GE 95 *IF *VALUE Unix_Memory.Used_Swap_Space_Pct *GT 40.0 WARNING *IF *VALUE System.Wait_I/O *GT 20 Windows situations The following predefined situations monitor Windows systems. These situations are run by the Monitoring Agent for Windows OS (product code NT). For more information about this agent, including the supported Windows ersions, refer to the Tioli Monitoring documentation. Table 27. Predefined Windows situations Situation name Description Seerity Formula Win_NT_CpuTimePct_W Monitors oerall CPU utilization for each processor. WARNING *IF *VALUE NT_Processor. %_Processor_Time *GE 90 Win_NT_DiskUsedPct_C Win_NT_EtlogSpaceUsedPct_W Monitors all logical disks for the percentage of space used. Monitors the space used by eent logs. CRITICAL WARNING *IF *VALUE NT_Logical_Disk. %_Used *GE 95 *AND *VALUE NT_Logical_Disk.Disk_Name *NE '_Total' *IF *VALUE NT_Monitored_Logs_Report. %_Usage *GE Solutions for BSM Guide:

177 Table 27. Predefined Windows situations (continued) Situation name Description Seerity Formula Win_NT_Etlog_All_W Monitors the windows eent log for specific eent IDs. CRITICAL *IF ((*VALUE NT_Eent_Log.Source_U *EQ 'Rdr' *AND *VALUE NT_Eent_Log.Eent_ID *EQ 3013 ) *OR ( *VALUE NT_Eent_Log.Source_U *EQ 'Sr' *AND *VALUE NT_Eent_Log.Eent_ID *EQ 2011 ) *OR ( *VALUE NT_Eent_Log.Source_U *EQ 'disk' *AND *VALUE NT_Eent_Log.Eent_ID *EQ 11 ) *OR ( *VALUE NT_Eent_Log.Source_U *EQ 'Netlogon' *AND *VALUE NT_Eent_Log.Eent_ID *EQ 5719 ) ) Win_NT_MemAailKB_C Win_NT_ProcCpuPct_W Win_NT_ProcMissing_C Win_NT_SericeAutomatic_C Win_NT_TcpRetrans_W Monitors aailable irtual memory. Monitors CPU utilization by all processes except antiirus, Tioli Storage Manager, and idle processes. Monitors standard processes on a Windows system. Monitors automatically started serices. Monitors the rate of segments transmitted containing preiously transmitted bytes, to help to identify a failing network interface. CRITICAL WARNING CRITICAL CRITICAL WARNING *IF *VALUE NT_Memory.Aailable_kBytes *LT *IF *VALUE NT_Process. %_Processor_Time *GE 95 *AND *VALUE NT_Process.Process_Name *NE '_Total' *AND *VALUE NT_Process.Process_Name *NE Idle *AND *VALUE NT_Process.Process_Name *NE Rtscan *AND *VALUE NT_Process.Process_Name *NE dsmcsc *AND *VALUE NT_Process.Process_Name *NE Priority Base *IF *MISSING NT_Process.Process_Name *EQ ('lsass','serices,'schost') *IF *VALUE NT_Serices.Start_Type *EQ Automatic *AND *VALUE NT_Serices.Current_State *EQ 'Stopped' *IF *VALUE TCP_Statistics. Segment_Retransmitted/sec *GT 1 Predefined situations for ITM database agents The IBM Solutions for Business Serice Management includes a set of predefined situations for IBM Tioli Monitoring (Tioli Monitoring) database agents. These situations are intended to implement effectie database monitoring for most enironments. Chapter 5. Product modifications 165

178 Situations are proided for the following Tioli Monitoring agents: Microsoft SQL (MS SQL) Serer Oracle The situations are named using the following conention: target_agent_name_seerity where: target The target database type (MSSQL or Oracle) agent The two-letter product code of the agent name A descriptie name for the situation seerity The seerity of eents generated by the situation (such as WARNING or CRITICAL) MS SQL situations The following predefined situations monitor Microsoft SQL (MS SQL) Serer systems. These situations are run by the Monitoring Agent for Microsoft SQL Serer (product code OQ). For more information about these agents, including the supported MS SQL ersions, refer to the Tioli Monitoring documentation. Table 28. Predefined MS SQL situations Situation name Description Seerity Formula MSSQL_OQ_BatchRequests_M Batch Requests per second MINOR *IF *VALUE MS_SQL_Batch_Stats.Batch_Reuests *GT MSSQL_OQ_CacheHitRatio_M Percentage of data cache hits to total data requests. MINOR *IF *VALUE MS_SQL_Serer_Summary.Cache_Hit_Ratio *LT *AND *VALUE MS_SQL_Serer_Summary.Serer_Status *EQ Actie MSSQL_OQ_ClusterFailoer_M Serer Errors occurred in the current interal MINOR *IF *VALUE MS_SQL_Problem_Detail.Error_ID *EQ 1069 MSSQL_OQ_ClusterFailoer_W Serer Errors occurred in the current interal WARNING *IF ((*VALUE MS_SQL_Problem_Detail.Error_ID *EQ ) *OR ( *VALUE MS_SQL_Problem_Detail.Error_ID *EQ *AND *VALUE MS_SQL_Problem_Detail.Message_Age *LE 60 *AND *VALUE MS_SQL_Problem_Detail.Seerity_Leel *LT 10 ) ) MSSQL_OQ_CPU_W Percent of MS SQL CPU > 90 WARNING *IF *VALUE MS_SQL_Serer_Summary.Total_OS_CPU_Percent *GT *UNTIL ( *TTL 0:02:15:00 ) MSSQL_OQ_DatabaeState_C Where Database status suspect CRITICAL *IF *VALUE MS_SQL_Database_Detail.Suspect_Database *EQ True 166 Solutions for BSM Guide:

179 Table 28. Predefined MS SQL situations (continued) Situation name Description Seerity Formula MSSQL_OQ_DatabaseStatus_H Where Database status offline HARMLESS *IF *VALUE MS_SQL_Database_Detail.Database_Status *EQ Not_Aailable *AND *VALUE MS_SQL_Database_Detail.Database_Name *NE model *UNTIL ( *SIT MSSQL_OQ_DatabaeState_C ) MSSQL_OQ_DBFreeSpace_M Percent of Database Freespace Minor => 20 MSSQL_OQ_FailedJobs_W Failed SQL Serer Agent jobs MSSQL_OQ_FailedTopJobs_C Failed Important SQL Serer Agent Jobs SSQL_OQ_FreeSpaceTempDB_C Percent of Database Freespace < 10 MB MSSQL_OQ_Growth_M Growth oer 5% warning MSSQL_OQ_LogFreeSpace_M MSSQL_OQ_Logon_C MSSQL_OQ_LogShipping_W MSSQL_OQ_LogShipping Threshold_W MSSQL_OQ_LongRunning Trans_M Percent of Log Freespace Minor <= 20 Actie user connection > X Log Shipping Job Failed Log Shipping Database backup/restore threshold exceeded Longest Transaction Name has been the same for the last 2 cycles MINOR WARNING CRITICAL CRITICAL MINOR MINOR CRITICAL WARNING WARNING MINOR *IF *VALUE MS_SQL_Database_Detail.Data_Freespace_Percent *LE 2.00 *AND *VALUE MS_SQL_Database_Detail.Database_Status *EQ Aailable *UNTIL ( *SIT MSSQL_OQ_SererStatus_F ) *IF *VALUE MS_SQL_Job_Detail.Job_Status *EQ Failed *UNTIL ( *SIT MSSQL_OQ_FailedTopJobs_C ) *IF *VALUE MS_SQL_Job_Detail.Job_Status *EQ Failed *AND *SCAN MS_SQL_Job_Detail.Job_Name *EQ 'Backup Job' *IF *VALUE MS_SQL_Database_Detail.Database_Name *EQ Tempdb *AND *VALUE MS_SQL_Database_Detail.Data_Freespace *LT *AND *VALUE MS_SQL_Database_Detail.Database_Status *EQ Aailable *IF *VALUE MS_SQL_Database_Detail.Database_ Growth_Percent *GT *IF *VALUE MS_SQL_Database_Summary._ Minimum_Pct_Log_Freespace *GT 0.00 * AND *VALUE MS_SQL_Database_ Summary.Minimum_Pct_Log_Freespace *LE *IF *VALUE MS_SQL_Statistics_Summary.Current_Logons *GT 2000 *IF *VALUE MS_SQL_Log_Shipping_Jobs_Detail.Job_Status *EQ Error *IF *VALUE MS_SQL_Log_Shipping_DB_Details. Threshold_Exceeded *EQ Yes *IF *VALUE MS_SQL_Database_Detail.Long_Running_ Transaction_Time_Per_Sec *GT *UNTIL ( *TTL 0:01:00:00 ) Chapter 5. Product modifications 167

180 Table 28. Predefined MS SQL situations (continued) Situation name Description Seerity Formula MSSQL_OQ_MirrorFailoer_C Mirroring State is Pending Failoer CRITICAL *IF *VALUE MS_SQL_Database_Mirroring.Mirroring_State *EQ Pending_Failoer MSSQL_OQ_MirrorLagging_W MSSQL_OQ_Mirror Suspended_W MSSQL_OQ_NumProcess Block_M MSSQL_OQ_ProcessesBad_W MSSQL_OQ_ProcessesTotal_W MSSQL_OQ_ReplLatency_C MSSQL_OQ_ReplLatency_W MSSQL_OQ_SererStatus_F Mirroring State is Synchronizing Mirroring State is Suspended Number of blocked processes Number of bad processes => 1 Total Processes > 1200 Replication processing delay (in milliseconds) Replication processing delay (in milliseconds) Where Serer status is not actie WARNING WARNING MINOR WARNING WARNING CRITICAL WARNING FATAL *IF *VALUE MS_SQL_Database_Mirroring.Mirroring_State *EQ Synchronizing *IF *VALUE MS_SQL_Database_Mirroring.Mirroring_State *EQ Suspended *IF *VALUE MS_SQL_Process_Summary.Total_Processes_ Blocked *GT 20 *IF *VALUE MS_SQL_Process_Summary.Total_Processes_Bad *GE 1 *IF *VALUE MS_SQL_Process_Summary.Total_Processes *GT 1200 *IF *VALUE MS_SQL_Database_Detail.Replication_Latency *GT *IF *VALUE MS_SQL_Database_Detail.Replication_Latency *GT *AND *VALUE MS_SQL_Database_Detail.Replication_Latency *LE *IF *VALUE MS_SQL_Serer_Summary.Serer_Status *EQ Inactie Oracle situations The following predefined situations monitor Oracle databases. These situations are run by the Monitoring Agent for Oracle (product code OR). For more information about these agents, including the supported Oracle ersions, refer to the Tioli Monitoring documentation. Table 29. Predefined Oracle situations Situation name Description Seerity Formula Oracle_OR_ArchiDestFull_C Oracle archie destination percent full greater or equal to 98% CRITICAL *IF *VALUE Oracle_Serer.Archie_Dest_Percent _Full *GE 98 Oracle_OR_ArchiDestFull_M Oracle archie destination percent full >=95% AND <98% MINOR *IF *VALUE Oracle_Serer.Archie_Dest_Percent _Full *GE 95 *AND *VALUE Oracle_Serer.Archie_Dest_Percent_Full *LT Solutions for BSM Guide:

181 Table 29. Predefined Oracle situations (continued) Situation name Description Seerity Formula Oracle_OR_ArchiDestFull_W Oracle archie destination percent full >=90% AND <95% WARNING *IF *VALUE Oracle_Serer.Archie_Dest_Percent _Full GE 90 *AND *VALUE Oracle_Serer.Archie_Dest_Percent_Full *LT 95 Oracle_OR_BkgdDumpSpace_W Background Dump Space Percent Used is greater than 98 Oracle_OR_FreeTbsp_C Percent Free Space is less than 2 Oracle_OR_FreeTbsp_M Percent Free Space is 2 <= Value < 8 Oracle_OR_FreeTbsp_W Oracle_OR_JobBroken_C Oracle_OR_JobQueue Failures_C Oracle_OR_JobQueue Failures_M Oracle_OR_JobQueue Failures_W Oracle_OR_Listener_C Oracle_OR_RedoLogs_C Total Oracle_OR_RedoLogs_W Oracle_OR_SererNotActie_C Oracle_OR_SnapshotOld ErrCount_C Percent Free Space is 8<= Value < 15 Oracle job is broken Oracle Maximum JobFailures >= 12 Oracle Maximum JobFailures 8 <= alue < 12 Oracle Maximum JobFailures 4 <= alue < 8 Oracle Listener status is not actie Redo Logs is less than 5 Total Redo Logs is 5<= Value < 10 Oracle serer status is inactie Maximum Snapshot Too Old Error Count (Interal) WARNING CRITICAL MINOR WARNING CRITICAL *IF *VALUE Oracle_Statistics_Summary. Background_Dump_Space_Percent _Used *GT 98 *IF *VALUE Oracle_Tablespaces.Percent_Free _Space_Including_Auto_Extend *LT 2 *IF *VALUE Oracle_Tablespaces.Percent_Free _Space_Including_Auto_Extend *GE 2 *AND *VALUE Oracle_Tablespaces.Percent_ Free_Space_Including_Auto_Extend *LT 8 *IF *VALUE Oracle_Tablespaces.Percent_Free _Space_Including_Auto_Extend *LT 15 *AND *VALUE Oracle_Tablespaces.Percent_Free_Space _Including_Auto_Extend *GE 8 *IF *VALUE Oracle_Job_Summary.Broken *EQ Yes CRITICAL *IF *VALUE Oracle_Job_Summary.Failures *GE 12 MINOR *IF *VALUE Oracle_Job_Summary.Failures *GE 8 *AND *VALUE Oracle_Job_Summary.Failures *LT 12 WARNING *IF *VALUE Oracle_Job_Summary.Failures *GE 4 *AND *VALUE Oracle_Job_Summary.Failures *LT 8 CRITICAL *IF *VALUE Oracle_Listener_Detail.Listener_Status *EQ Inactie CRITICAL *IF *VALUE Oracle_Serer.Total_Redo_Logs *LT 5 WARNING CRITICAL CRITICAL *IF *VALUE Oracle_Serer.Total_Redo_Logs *LT 10 *AND *VALUE Oracle_Serer.Total_Redo_Logs *GE 5 *IF *VALUE Oracle_Serer.Serer_Status *EQ Inactie *IF *VALUE Oracle_Undo_Stat_Summary.Snapshot_Too_Old_Error_Count_64 *GT 0 *UNTIL ( *TTL 0:00:15:00 ) Chapter 5. Product modifications 169

182 Table 29. Predefined Oracle situations (continued) Situation name Description Seerity Formula Oracle_OR_UndoSpaceErr Count_C Maximum No Space Error Count (Interal) CRITICAL *IF *VALUE Oracle_Undo_Stat_Summary.No_Space_Error_Count *GT 0 Oracle_OR_UsedCore DumpSpace_W Maximum used core dump space WARNING *IF *VALUE Oracle _Statistics_Summary.Core_Dump_Space_Percent _Used *GT 95 Oracle_OR_UserDumpSpace_W Maximum user dump space WARNING *IF *VALUE Oracle _Statistics_Summary.User_Dump_Space_Percent _Used *GT 90 Predefined situations for application agents The IBM Solutions for Business Serice Management includes a set of predefined situations for IBM Tioli Monitoring (Tioli Monitoring) agents for IBM Tioli Composite Application Manager for Applications (ITCAM for Applications). Situations are proided for the following Tioli Monitoring agents: WebSphere Application Serer Web Serers Uniersal The situations are named using the following conention: target_agent_name_seerity where: target The target type (WAS, Apache, URL) agent The two-letter product code of the agent name A descriptie name for the situation seerity The seerity of eents generated by the situation (such as WARNING or CRITICAL) WebSphere situations The following predefined situations monitor WebSphere Application Serers. These situations are run by the for Monitoring Agent for WebSphere (product code YN). For more information about these agents, including the supported WebSphere ersions, refer to the Tioli Monitoring documentation. Table 30. Predefined WebSphere Application Serer situations Situation name Description Seerity Formula WAS_YN_AppDiscoered_I WAS_YN_ApplicationHealth_C WAS Application is Discoered WAS Application Health is Bad Informational *IF *VALUE Application_Monitoring _Configuration.Mon_Status *EQ Discoered CRITICAL *IF *VALUE Application_Health_Status.Application_Health *EQ Bad 170 Solutions for BSM Guide:

183 Table 30. Predefined WebSphere Application Serer situations (continued) Situation name Description Seerity Formula WAS_YN_ApplicationHealth_I WebSphere Application has returned to a Good status. Informational *IF *VALUE Application_Health_Status.Application _Health *EQ Good *UNTIL ( *TTL 0:00:00:30 ) WAS_YN_ApplicationHealth_W WAS Application Health is Fair WAS_YN_AppSererActiity_H WAS Application Serer Actiity WAS_YN_AppSerer NoActiity_W WAS_YN_AppSererStatus_C WAS_YN_AppSererStatus_W WAS_YN_DBConnPoolAct_C WAS_YN_DBConnPoolAct_W WAS_YN _DBConnPoolUsage_C WAS_YN _DBConnPoolUsage_W WAS Application Serer No Actiity Warning WAS Application Serer Status WAS Application Serer Status WAS Application Serer Database Connection Pool Actiity WAS Application Serer Database Connection Pool Actiity Warning WAS Application Serer Database Connection Pool Usage Critical WAS Application Serer Database Connection Pool Usage Warning WARNING Harmless WARNING CRITICAL WARNING CRITICAL WARNING CRITICAL WARNING *IF *VALUE Application_Health_Status.Application _Health *EQ Fair *UNTIL ( *SIT WAS_YN_ApplicationHealth_C ) *IF ( ( *SIT WAS_YN_EJBConActiity_H *EQ *TRUE ) *OR ( *SIT WAS_YN_WebAppActiity_H *EQ *TRUE ) ) *IF *SIT WAS_YN_EJBConNoActiity_W *EQ *TRUE *AND *SIT WAS_YN _WebAppNoActiity_W *EQ *TRUE *UNTIL ( *SIT WAS_YN_AppSererActiity_H ) W*IF *VALUE Application_Serer.Status *NE Connected *IF *VALUE Application_Serer.Status *NE Connected *UNTIL ( *SIT WAS_YN_AppSererStatus_C ) *IF *SCAN DB_Connection_Pools.Datasourc _Name *EQ Summary *AND *VALUE DB_Connection_ePools.Aerage_Pool_Size *EQ 0.0 *AND *VALUE DB_Connection _Pools.Maximum_Pool_Size *GT 0 *AND *SIT WAS_YN_AppSererActiity _H *EQ *TRUE *IF *SCAN DB_Connection_Pools. Datasource_Name *EQ Summary *AND *VALUE DB_Connection_Pools.Aerage_Usage_Time *EQ 0.0 *AND *VALUE DB_Connection_Pools.Maximum_Pool_Size *GT 0 *AND *SIT WAS_YN_AppSererActiity _H *EQ *TRUE *UNTIL ( *SIT WAS_YN_DBConnPoolAct_C ) *IF ((*VALUE DB_Connection_Pools.Percent_Used *GE 95 ) *OR ( *VALUE DB_Connection_Pools.Aerage_Wait_Time *GT 0.0 *AND *VALUE DB_Connection_Pools.Percent_Used *GE 90 ) ) *IF ((*VALUE DB_Connection _Pools.Percent_Used *GE 70 *AND *VALUE DB_Connection_Pools.Aerage_Wait_Time *GT 0.0 ) *OR ( *VALUE DB_Connection_Pools.Percent_Used *GE 90 ) ) *UNTIL ( *SIT WAS_YN_DBConnPoolUsage_C ) Chapter 5. Product modifications 171

184 Table 30. Predefined WebSphere Application Serer situations (continued) Situation name Description Seerity Formula WAS_YN_ DBConnPoolWaitTime_C WAS_YN_DBConnPool WaitTime_W WAS_YN_EJBConActiity_H WAS_YN_ EJBConNoActiity_W WAS_YN_GCActiity_C WAS_YN_GCActiity_W WAS_YN_GCCPUOerhead_C WAS_YN_GCCPUOerhead_W WAS Application Serer Database Connection Pool Wait Critical WAS Application Serer Database Connection Pool Wait Warning WAS Application Serer EJB Container Actiity Harmless WAS Application Serer EJB Container No Actiity Warning WAS Application Serer Garbage Collection Actiity Critical WAS Application Serer Garbage Collection Actiity Warning WAS Application Serer Grabage Collection Analysis Critical WAS Application Serer Grabage Collection Analysis Critical CRITICAL WARNING HARMLESS WARNING CRITICAL WARNING CRITICAL WARNING *IF *VALUE DB_Connection _Pools.Aerage_Wait_Time *GT 0 *AND *VALUE DB_Connection _Pools.Percent_Used *LT 70 *IF *VALUE DB_Connection _Pools.Aerage_Wait_Time *GT 0.0 *AND *VALUE DB_Connection _Pools.Percent_Used *LT 90 *UNTIL ( *SIT WAS_YN_DBConnPoolWaitTime_C ) *IF *VALUE EJB_Containers.Method_Inocation_Rate *GT 0.0 *UNTIL ( *TTL 0:00:02:00 ) *IF *VALUE EJB_Containers.Method _Inocation_Rate *EQ 0 *IF ((*VALUE Garbage_Collection _Analysis.Times_Run *GT 20 ) *OR ( *VALUE Garbage_Collection _Analysis.Objects_Moed *GT 0)) *IF ((*VALUE Garbage_Collection _Analysis.Times_Run *GT 20 ) *OR ( *VALUE Garbage_Collection _Analysis.Objects_Moed *GT 0))*UNTIL ( *SIT WAS_YN_GCActiity_C ) *IF *VALUE Garbage_Collection _Analysis.Real_Time_Percent *GE 70.0 *IF *VALUE Garbage_Collection _Analysis.Real_Time_Percent *GE 30.0 *UNTIL ( *SIT WAS_YN_GCCPUOerhead_C ) 172 Solutions for BSM Guide:

185 Table 30. Predefined WebSphere Application Serer situations (continued) Situation name Description Seerity Formula WAS_YN_GCMonitor_W WAS Application Serer Garbage Collection Monitoring Disabled Warning WARNING *IF *VALUE Application _Serer.Garbage_Collection_Monitoring *EQ Disabled WAS_YN_PltMsgNoActiity_W WAS Application Serer JMS Message No Actiity Warning WAS_YN_ResourceMonitor_W WAS_YN_ThrdPoolAtMax_C WAS_YN_ThrdPoolAtMax_W WAS_YN_WebAppActiity_H WAS_YN_WebApp NoActiity_W WAS_YN_ WebAppUncaughtExcpt_W WAS Application Serer Resource Data Monitoring Disabled Warning WAS Application Serer Thread Pool at Maximum Critical WAS Application Serer Thread Pool at Maximum Warning WAS Application Serer Web Applications Actiity WAS Application Serer Web Applications No Actiity Warning WAS Application Serer Web Applications Uncaught Exception Warning WARNING WARNING CRITICAL WARNING HARMLESS WARNING WARNING *IF *VALUE JMS_Summary.Browse_Rate *EQ 0 *AND *VALUE JMS_Summary.Receie_Rate *EQ 0 *AND *VALUE JMS_Summary.Send_Rate *EQ 0 *IF *VALUE Application_Serer.Resource_Data_Monitoring *EQ Disabled *IF *VALUE Thread_Pools.Percent_of_Time_Pool_at_Max *GT 0.0 *AND *VALUE Thread_Pools.Thread_Creation_Rate *GE Thread_Pools.Thread_Destruction_Rate *IF *VALUE Thread_Pools.Percent _of_time_pool_at_max *GT 0.0 *UNTIL ( *SIT WAS_YN_ThrdPoolAtMax_C ) *IF *SCAN Web_Applications.Enterprise _Application_Name *EQ Summary *AND *VALUE Web_Applications.Request_Count *GT 0 *UNTIL ( *TTL 0:00:02:00 ) *IF *SCAN Web_Applications.Enterprise_Application_Name *EQ Summary *AND *VALUE Web_Applications.Request_Count *EQ 0 *IF *VALUE Web_Applications.Error_Rate *GT 0.0 *AND *VALUE Web_Applications.Enterprise_Application_Name *NE '[Summary]' Chapter 5. Product modifications 173

186 Table 30. Predefined WebSphere Application Serer situations (continued) Situation name Description Seerity Formula WAS_YN_ WebSrNoActiity_W WAS_PBW_ErrorInocation_C WAS Application Serer - Web Serer - No Actiity Warning WAS Application Serer - Plants By WebSphere - Error Inocation Critical WARNING CRITICAL *IF *VALUE Web_Serices.Dispatched_Requests *EQ 0 *AND *VALUE Web_Serices.Processed_Requests *EQ 00 *AND *VALUE Web_Serices.Receied_Requests *EQ 0 *IF *VALUE Serlets_JSPs.Serlet /JSP_Name *EQ '/error.jsp' *AND *VALUE Serlets_JSPs.Enterpris e_application_name *EQ PlantsByWebSphere *AND *VALUE Serlets_JSPs.Request_Count *GT 0 Web serer situations The following predefined situations monitor Apache Web Serers. These situations are run by the for Monitoring Agent for Web Serers (product code HT). For more information about these agents, including the supported web serer ersions, refer to the Tioli Monitoring documentation. Table 31. Predefined Web Serer situations Situation name Description Seerity Formula Apache_HT_WebSiteDown_C The Web Site is Down - Critical CRITICAL *IF *VALUE Apache_Web_Sites.Web_Site_Status *NE Running Apache_HT _WebSiteFailures_C Apache_HT _WebSiteFailures_W Serer failures per second iolation - Criticall Serer failures per second iolation - Warning CRITICAL WARNING *IF *VALUE Apache_Web_Sites.Serer _Failures_Rate *GT *IF *VALUE Apache_Web_Sites.Serer_Failures_Rate *GT *UNTIL ( *SIT Apache_HT_WebSiteFailures_C ) Uniersal Agent situations The following predefined situations monitor Uniersal Agents. These situations are run by the for Uniersal Agent (product code UM). For more information about these agent, refer to the Tioli Monitoring documentation. Table 32. Predefined Uniersal Agent situations Situation name Description Seerity Formula URL_UM_URLStatus_C URL Status Critical CRITICAL *IF *VALUE INTERNETMANAGED _URL00.Status *NE OK URL_UM_URLStatus_W URL Status Warning WARNING *IF *VALUE INTERNETMANAGED _URL00.Status *NE OK *UNTIL ( *SIT URL_UM_URLStatus_C ) 174 Solutions for BSM Guide:

187 Predefined situations for VMware agents The IBM Solutions for Business Serice Management includes a set of predefined situations for IBM Tioli Monitoring (Tioli Monitoring) agents for Virtual Serers. Situations are proided for the following Tioli Monitoring agents: VMware ESX VMware The situations are named using the following conention: target_agent_name_seerity where: target The target type (KVM) agent The two-letter product code of the agent name A descriptie name for the situation seerity The seerity of eents generated by the situation (such as WARNING or CRITICAL) VMware ESX situations The following predefined situations monitor VMware ESX agents. These situations are run by the IBM Tioli Monitoring for Virtual Serers (product code VM) agents. For more information about these agent, refer to the Tioli Monitoring documentation. Table 33. Predefined VMWare ESX situations Situation name Description Seerity Formula KVM_VM_CPUUsage_M CPU usage on CPU 0 to high MINOR *IF *VALUE KVM_SERVER_CPU.CPU _Number *EQ 0 *AND *VALUE KVM_SERVER_CPU.CPU _Utilization *GT 95 KVM_VM_DatastoreStorage_C ESX storage CRITICAL *IF *VALUE KVM_SERVER _DATASTORE.Free_Space *LE KVM_VM_HardwareESX_C KVM_VM_HardwareESX_M KVM_VM_Maintenance ModeESX_I KVM_VM_NetworkDuplex_M ESX Hardware Monitoring ESX Hardware Monitoring Set ESX serer in maintenance mode ESX Serer Network Duplex CRITICAL MINOR Informational MINOR *IF ((*VALUE KVM_SERVER _HEALTH.Sensor_Status *EQ 'Red' ) *OR ( *VALUE KVM_SERVER_HEALTH. Sensor_Status *EQ 'red' ) ) *IF ((*VALUE KVM_SERVER _HEALTH.Sensor_Status *EQ 'yellow' ) *OR ( *VALUE KVM_SERVER _HEALTH.Sensor_Status *EQ 'Yellow' ) ) *IF *VALUE KVM_SERVER.Maintenance_Mode *EQ Yes *IF *VALUE KVM_SERVER_ NETWORK.Duplex *NE 'full' *AND *VALUE KVM_SERVER_ NETWORK.Duplex *NE 'Unaailable' Chapter 5. Product modifications 175

188 Table 33. Predefined VMWare ESX situations (continued) Situation name Description Seerity Formula KVM_VM_NetworkUsage_M ESX Serer Network Link Utilization MINOR *IF *VALUE KVM_SERVER_ NETWORK.Link_Utilization *GT VMware situations The following predefined situations monitor VMware agents. These situations are run by the IBM Tioli Monitoring for Virtual Serers (product code VM) agents. For more information about these agent, refer to the Tioli Monitoring documentation. Table 34. Predefined VMWare situations Situation name Description Seerity Formula KVM_VM _ConnVirtualCenter_C KVM_VM_Datastore Oercommit_C KVM_VM_Datastore Oercommit_M KVM_VM_DatastoreUsage_C KVM_VM_DatastoreUsage_M KVM_VM_Eent1_C KVM_VM_Eent1_M VM agent can't connect to VirtualCenter The data store is oer commited The data store is oer commited The data store is nearing or is at its defined capacity The data store is nearing or is at its defined capacity Virtual Center Critical Eent: Alarm Status and Triggered Entity Virtual Center Minor Eent: Alarm Status and Triggered Entity CRITICAL CRITICAL MINOR CRITICAL MINOR CRITICAL MINOR *IF *VALUE KVM_AGENT _EVENTS.Seerity *EQ Seere *AND *VALUE KVM_AGENT_EVENTS.Subsystem *EQ Connection *UNTIL ( *TTL 0:00:15:00 ) *IF *VALUE KVM_DATASTORES.Percent_Oercommitted *GT *IF *VALUE KVM_DATASTORES.Percent_Oercommitted *GT *IF *VALUE KVM_DATASTORES.Free_Space *LT *AND *SCAN KVM_DATASTORES.Name *NE 'local' *IF *VALUE KVM_DATASTORES.Free_Space *LT *AND *SCAN KVM_DATASTORES.Name *NE 'local' *IF ((*VALUE KVM_TRIGGERED _ALARMS.Alarm_Status *EQ 'red' *AND *SCAN KVM_TRIGGERED _ALARMS.Triggered_Entity *NE '.' ) *OR ( *VALUE KVM_TRIGGERED_ ALARMS.Alarm_Status *EQ 'rot' *AND *SCAN KVM_TRIGGERED_ALARMS. Triggered_Entity *NE '.' ) ) *IF ((*VALUE KVM_TRIGGERED _ALARMS.Alarm_Status *EQ 'gelb' *AND *SCAN KVM_TRIGGERED_ALARMS.Triggered_Entity *NE '.' ) *OR ( *VALUE KVM_TRIGGERED_ALARMS.Alarm_Status *EQ 'yellow' *AND *SCAN KVM_TRIGGERED_ALARMS.Triggered_Entity *NE '.' ) ) 176 Solutions for BSM Guide:

189 Table 34. Predefined VMWare situations (continued) Situation name Description Seerity Formula KVM_VM_Eent2_C Virtual Center Critical Eent: Alarm Status and Triggered Entity CRITICAL *IF ((*VALUE KVM_TRIGGERED _ALARMS.Alarm_Status *EQ 'red' *AND *SCAN KVM_TRIGGERED_ALARMS.Triggered_Entity *EQ '.' ) *OR ( *VALUE KVM_TRIGGERED_ALARMS.Alarm_Status *EQ 'rot' *AND *SCAN KVM_TRIGGERED_ALARMS.Triggered_Entity *EQ '.' ) ) KVM_VM_Eent2_M KVM_VM_HeartbeatESX1_C KVM_VM_HeartbeatESX2_C Virtual Center Minor Eent: Alarm Status and Triggered Entity ESX subnode of VM agent is offline ESX subnode of VM agent is offline MINOR CRITICAL CRITICAL *IF ((*VALUE KVM_TRIGGERED _ALARMS.Alarm_Status *EQ 'gelb' *AND *SCAN KVM_TRIGGERED _ALARMS.Triggered_Entity *EQ '.' ) *OR ( *VALUE KVM_TRIGGERED_ALARMS.Alarm_Status *EQ 'yellow' *AND *SCAN KVM_TRIGGERED_ALARMS.Triggered_Entity *EQ '.' ) ) *IF *VALUE KVM_TOPOLOGY.NodeType *EQ 'km.esx_serer' *AND *VALUE KVM_TOPOLOGY.NodeStatus *EQ 'notresponding' *AND *SCAN KVM_TOPOLOGY.NodeName *NE '.' *UNTIL ( *TTL 0:00:15:00 ) *IF *VALUE KVM_TOPOLOGY. NodeType *EQ 'km.esx_serer' *AND *VALUE KVM_TOPOLOGY.NodeStatus *EQ 'notresponding' *AND *SCAN KVM_TOPOLOGY.NodeName *EQ '.' *UNTIL ( *TTL 0:00:15:00 ) Support for Time Window Analyzer metric collection The two groups of artifacts that support the Time Window Analyzer metric collection are ITM custom queries and TBSM ITM policy-based data fetchers. The queries run in ITM, and the TBSM data fetchers retriee the results of the ITM queries, and make the data aailable for TBSM. Custom ITM queries These custom ITM queries are deployed to the ITM host: BSMA-ApacheWebSerer-Sites Query to collect metrics from the ITCAM for Applications, Agent for HTTP Serer (includes Apache Serer and IBM HTTP Serer) BSMA-Applications-AMCClient Query to collect client metrics from ITCAM fortransactions, WRT Agent (aggregated by the AMC Applications Agent) BSMA-Applications-AMCTrans Query to collect transaction metrics from ITCAM fortransactions, WRT Agent (aggregated by the AMC Applications Agent) BSMA-DB2-Database01 Query to collect metrics from ITCAM for Applications, Agent for DB2 Chapter 5. Product modifications 177

190 BSMA-LinuxOS-CPUUsage Query to collect metrics from the ITM Linux OS Agent BSMA-LinuxOS-SwapSpaceUsed Query to collect metrics from the ITM Linux OS Agent BSMA-VMWareVIMetrics-CPUUsage Query to collect metrics from the ITM for Virtual Enironments, VMWare VI Agent BSMA-VMWareVIMetrics-LinksUsage Query to collect metrics from the ITM for Virtual Enironments, VMWare VI Agent BSMA-WAS-DBConnPoolUsedPct Query to collect metrics from the ITCAM for Applications, Agent for WAS BSMA-WAS-MethodInocRate Query to collect metrics from the ITCAM for Applications, Agent for WAS BSMA-WindowsOS-CPUUsage Query to collect metrics from the ITM Windows OS Agent TBSM ITM policy-based data fetchers These TBSM ITM policy-based data fetchers are deployed to the TBSM data serer host: ApacheWebSerer-Sites Collects metrics from the ITCAM for Applications, Agent for HTTP Serer (includes Apache Serer and IBM HTTP Serer) Applications-AMCClient Collects client metrics from ITCAM fortransactions, WRT Agent (aggregated by the AMC Applications Agent) Applications-AMCTrans Collects transaction metrics from ITCAM fortransactions, WRT Agent (aggregated by the AMC Applications Agent) DB2-Database01 Collects metrics from ITCAM for Applications, Agent for DB2 LinuxOS-CPUUsage Collects metrics from the ITM Linux OS Agent LinuxOS-SwapSpaceUsed Collects metrics from the ITM Linux OS Agent VMWareVIMetrics-CPUUsage Collects metrics from the ITM for Virtual Enironments, VMWare VI Agent VMWareVIMetrics-LinksUsage Collects metrics from the ITM for Virtual Enironments, VMWare VI Agent WAS-DBConnPoolUsedPct Collects metrics from the ITCAM for Applications, Agent for WAS WAS-MethodInocRate Collects metrics from the ITCAM for Applications, Agent for WAS WindowsOS-CPUUsage Collects metrics from the ITM Windows OS Agent 178 Solutions for BSM Guide:

191 Chapter 6. Isolating problems using the Business Serice Health pages You can use the Business Serice Health and Business Serice Health Details pages to determine which component of a business serice is causing a problem. You can then route the problem to the appropriate subject matter expert for resolution. Before you begin Open the Business Serice Health page by clicking System Status and Health > Business Serice Health in the Tioli Integrated Portal naigation pane. Procedure 1. In the Business Serices table, find the business serice you are interested in. This table proides an oeriew of the managed business serices that are currently experiencing problems. If all serices are operating normally, the following message is displayed: All monitored business serices are running normally. By default, the Business Serices table is sorted in descending order by critical eent count, so the serices that hae experienced the most problems are at the top. For each business serice, the table shows a summary of the status of the serice and of each supporting component. After you hae found the business serice you want to work with, click the corresponding row in the table. The other portlets on the page update in context to show data related to the business serice you select. 2. Use the Business Serice Eents list to see information about eents affecting the selected business serice. This list is a NetCool/OMNIbus Actie Eent List (AEL) showing all actie eents of seerity Warning and aboe that affect the business serice currently selected in the Business Serices table. You can use the features of the AEL to search, filter, and sort the list of eents. 3. Use the Business Serice Status Oer Time and Business Serice Eent Count Oer Time charts to see how the status and critical eent counts for the business serice hae changed oer time. These charts can help you determine which eents are releant to the problem. 4. To see more detailed information about the components of the business serice, including eent data and metrics oer time, right-click on the row in the Business Serices table and then click Open > Business Serice Health Details. The Business Serice Health Details page opens in another tab. 5. In the Business Serice Components table, find the business serice component or resource you are interested in. This table shows the business serice you selected on the Business Serice Health page, with the supporting components of the business serice and the specific resources within each component displayed in a hierarchical tree iew. For each component or resource, the table shows the current status and critical eent count, so you can identify which components of the business serice might be causing the problem. After you hae found the component or resource you want to work with, click the corresponding row in the table. The Business Serice Eents portlet updates in context to show data related to your selection. Copyright IBM Corp

192 6. Use the Business Serice Eents list to see information about eents affecting the selected business serice, component, or resource. This list is a NetCool/OMNIbus Actie Eent List (AEL) showing all actie eents of seerity Warning and aboe that affect the item currently selected in the Business Serice Components list. You can use the features of the AEL to search, filter, and sort the list of eents. 7. Use the Time Window Analyzer portlet to iew metrics for the business serice and its supporting components, charted oer time. The default Time Window Analyzer iew shows status changes for the selected business serice. You can add additional metrics to the chart to see how eents hae contributed to status changes: To add charting of status changes for supporting components of the business serice, or status changes of other business serices, click Add Serice. You can then select the components or serices for which you want to chart status changes. To choose the metric to chart, select a metric from the drop-down list. The default metric displayed is Status Changes. To see additional details about status changes and eents, click Oerlay. What to do next After you hae identified the underlying cause, you can take further action to resole the problem or refer the problem to a subject-matter expert. If you hae access to the Tioli Enterprise Portal or Tioli Monitoring console, you can use the launch-in-context capabilities of the TBSM serice tree to open the appropriate application. Right-click on a row in the Business Serice Components table to see a menu of applications you can launch to; these include arious ITCAM, TEP, TADDM, and CCMDB iews, depending on the specific resource you selected. Business Serice Health page oeriew The Business Serice Health page proides an oeriew of your business serices and the components that support them, including eent counts and status information about each supporting component. You can use this page to determine the health of each business serice and identify which component of a business serice might be causing an outage or other problem. This page is part of the Business Serice Health iew and is aailable to the BSMAcceleratorUser role. The Business Serice Health page shows status and eent information about all of your managed business serices that are not currently running normally. This information is gathered from multiple monitoring and diagnostic tools. From this page, you can naigate to the Business Serice Health Details page to see more detailed information about a specific business serice and its supporting components. The Business Serice Health page includes seeral portlets you can use to iew information about your business serices. 180 Solutions for BSM Guide:

193 Business Serices table The Business Serices table shows a consolidated oeriew of each managed business serice and its supporting components. A component of a business serice represents a functional or technological category, such as databases, transactions, or serers. Each row in the Business Serices table represents a business serice as defined in the Tioli Business Serice Manager (TBSM) serice model. Each row proides summary information about the status of a business serice: The Eents column shows the total number of eents affecting the business serice that hae a seerity of Critical or greater. This eent count is the sum of the critical eent counts from the components supporting the business serice. Each subsequent column shows the status of a component supporting the business serice. At least one of these will be yellow or red. The status of a component is determined by the highest-seerity eent affecting the component. This information can proide an indication of which component of the business serice is the cause of the problem. The Business Serices table is based on the TBSM Serice Tree portlet. The displayed TBSM data is integrated from multiple sources, including the following: Resource definitions from Tioli Application Dependency Discoery Manager (TADDM) discoery data and Discoery Library Adapter (DLA) data, organized within a TBSM serice model Eent data from IBM Tioli Monitoring and IBM Tioli Composite Application Manager agents, enriched with data from Tioli Netcool/Impact and collected by Tioli Netcool/OMNIbus By default, the supporting components for a business serice are as follows: Component Clients Transactions Web Serer App Serer Serer Virtual Enironments (VEs) Databases (DBs) Source of eents determining status ITCAM for Web Response Time ITCAM for Web Response Time ITCAM Agent for HTTP Serers ITCAM for Application Diagnostics Tioli Monitoring OS Agent Tioli Monitoring for Virtual Serers Tioli Monitoring for DB (DB2 Agent) You can change the displayed components by customizing the TBSM serice tree template By default, the Business Serices table is sorted by critical eent count, in descending order. This ensures that the business serices experiencing the most problems (as indicated by eents of seerity Critical or greater) are at the top of the table. The table includes only serices that are experiencing problems; therefore, any serice with a status of Clear is not shown. Business Serice Eents The Business Serice Eents table shows a list of all actie eents affecting the business serice currently selected in the Business Serices table. This list includes all eents affecting any supporting component of the business serice. By default, Chapter 6. Isolating problems using the Business Serice Health pages 181

194 182 Solutions for BSM Guide: the list is sorted by seerity, in descending order, so the most seere eents are at the top of the list. You can use this list to get more information about the eents that are causing problems with a business serice and which component they originate from. The Business Serice Eents list is displayed using a Tioli Netcool/OMNIbus Actie Eent List (AEL). You can use the features of the AEL to search, filter, and sort the eents in the list, as well as take administratie actions. For more information about the AEL, refer to the Netcool/OMNIbus documentation at %2Fcom.ibm.netcool_OMNIbus.doc_7.3.1%2Fwebtop%2Fwip%2Ftask %2Fweb_use_ael_managingeents.html. Business Serice Status Oer Time The Business Serice Status Oer Time chart is a historical graph showing the changes in the oerall status of the selected business serice during the last 12 hours, sampled at 15-minute interals. The oerall status of a business serice is based on the most seere status of any supporting component; for example, if the status of any component is Critical, then the oerall business serice status is at least Critical. If other business serices are monitored, the contents and title of the chart changes when you click the business serice. The chart refreshes automatically and the time of the last refresh displays with the chart. Business Serice Eent Count Oer Time The Business Serice Eent Count Oer Time chart is a historical graph showing the number of eents affecting the selected business serice during the last 12 hours, sampled at 15-minute interals. The eent count includes all eents of Critical seerity or greater. If other business serices are monitored, the contents and title of the chart changes when you click the business serice. The chart refreshes automatically and the time of the last refresh displays with the chart. What does the number mean in the titles of the Oer Time charts? The title of the chart is the serice name and a number that represents the number of recorded data points (retrieed from the TBSM metric history database) mapped to the 48 displayed plot points in the chart. For example, if the chart title is OnlineBanking -- 14, the chart displays information about 14 alues that were collected during the 12-hour time window for the OnlineBanking serice. If multiple alues were collected during the same 15-minute plot point, only the last alue is plotted. That is, the chart can only plot one alue per 15-minute plot point. As a result, you could hae 14 eents, but only 7 plot points in the chart. The alues 1** and 0 hae special meaning as shown in these examples: OnlineBanking -- 1 = The chart displays the 1 alue that was collected during the 12-hour time window..

195 OnlineBanking -- 1** = The chart carries forward the last alue that was collected before the 12-hour time window OnlineBanking -- 0 = No data has been collected for OnlineBanking Business Serice Health Details page Oeriew The Business Serice Health Details page proides detailed information about a selected business serice and its supporting components, including status information, eents, and metrics analyzed oer time. You can use this page to identify the eents and corresponding status changes that might be causing an outage or other problem with a business serice component. A new Business Serice Health Details page is opened eerytime the pop-up menu is used from a business serice listed on the Business Serice Health page. This page is part of the Business Serice Health iew and is aailable to the BSMAcceleratorUser role. The Business Serice Health Details page shows status and eent information about a selected business serice. This information is gathered from multiple monitoring and diagnostic tools. The Business Serice Health Details page includes seeral portlets you can use to iew information about your business serices. Business Serice Components table The Business Serices table shows a consolidated oeriew of the status of the selected business serice and its supporting components. This table shows an expandable tree iew based on the Tioli Business Serice Manager (TBSM) serice model, with the supporting components of the business serice shown as indented rows beneath the business serice they support. The Business Serice Components table is based on the TBSM Serice Tree portlet. The displayed TBSM data is integrated from multiple sources, including the following: Resource definitions from Tioli Application Dependency Discoery Manager (TADDM) discoery data and Discoery Library Adapter (DLA) data, organized within a TBSM serice model Eent data from IBM Tioli Monitoring and IBM Tioli Composite Application Manager agents, enriched with data from Tioli Netcool/Impact and collected by Tioli Netcool/OMNIbus By default, the supporting components for a business serice are as follows: Component Clients Transactions Web Serer App Serer Serer Virtual Enironments (VEs) Databases (DBs) Source of eents determining status ITCAM for Web Response Time ITCAM for Web Response Time ITCAM Agent for HTTP Serers ITCAM for Application Diagnostics Tioli Monitoring OS Agent Tioli Monitoring for Virtual Serers Tioli Monitoring for DB (DB2 Agent) You can change the displayed components by customizing the TBSM serice model. Chapter 6. Isolating problems using the Business Serice Health pages 183

196 The first row of the table shows the total number of critical eents affecting the business serice, as well as an icon representing the oerall serice status (based on the most seere status of any supporting component). You can expand the serice tree to see status information about the supporting components, and the types of eents affecting each component. Business Serice Eents The Business Serice Eents table shows a list of all actie eents affecting the business serice or component currently selected in the Business Serice Components table. By default, the list is sorted by seerity, in descending order, so the most seere eents are at the top of the list. You can use this list to get more information about the eents that are causing problems with a component of a business serice. The Business Serice Eents list is displayed using a Tioli Netcool/OMNIbus Actie Eent List (AEL). You can use the features of the AEL to search, filter, and sort the eents in the list, as well as take administratie actions. For more information about the AEL, refer to the Netcool/OMNIbus documentation at %2Fcom.ibm.netcool_OMNIbus.doc_7.3.1%2Fwebtop%2Fwip%2Ftask %2Fweb_use_ael_managingeents.html. Time Window Analyzer The Time Window Analyzer portlet shows metrics for the business serice in the context of the Business Serice Health page launch. You can also use this portlet to oerlay information about eents, which can help to identify which eents caused the status changes. The default Time Window Analyzer iew shows status changes for the business serice; you can add charting for supporting components by clicking Add Serice, or chart other metrics by selecting them from the drop-down list. The following metrics are aailable: Table 35. Aailable metrics for the Time Window Analyzer Component Metrics Clients Percent Failed The percentage of transactions whose requests were marked as Failed. This alue is calculated by diiding Failed Requests by Total Requests and multiplying by 100. The sum of this attribute alue and the alue of the Percent Aailable attribute should total 100. This metric is collected from the Applications Agent, AMC Client attribute group, Percent Failed attribute. Percent Slow The percentage of transactions whose requests were marked as Slow. This alue is calculated by diiding Slow Requests by Total Requests and multiplying by 100. The sum of this attribute alue and the alue of the Percent Good attribute should equal the alue of the Percent Aailable attribute. This metric is collected from the Applications Agent, AMC Client attribute group, Percent Slow attribute. 184 Solutions for BSM Guide:

197 Table 35. Aailable metrics for the Time Window Analyzer (continued) Component Metrics Transactions AMC Transaction-Response Time Reports the number of seconds (up to 3 decimal places) that was required for the transaction to complete. This metric is collected from Applications Agent, AMC Transactions attribute group, Response Time attribute App Serer Web Serer AMC Transaction-Aerage Requests Reports the aerage number of requests for a data interal during the time span for which data is displayed. This metric is collected from Applications Agent, AMC Transactions attribute group, Aerage Requests attribute. AMC Transaction-Percent Failed Reports the percentage of transactions with aailability iolations. The sum of percent aailable and percent failed equals 100%. This metric is collected from Applications Agent, AMC Transactions attribute group, Percent Failed attribute. WAS Method Inocation Rate The rate of inocations (per second) during the interal. This metric is collected from the WebSphere App Serer Agent, EJB_Containers attribute group, Method Inocation Rate (per sec) attribute. WAS Database Connection Used The aerage percentage of the connection pool in use during the interal. This alue is an aerage of seeral alues collected oer an interal. The interal can be either between this time and the preious time you actiated this workspace, or fixed (normally 60 seconds), depending on the configuration of the monitoring agent. This metric is collected from the WebSphere App Serer Agent, DB_Connection_Pools attribute group, Percent Used attribute. Apache Web Sites-Serer Failures Rate The serer failures rate per minute for the website This metric is collected from the ITCAM for Applications, Agent for HTTP Serer, Apache Web Sites attribute group, Serer Failure Rate attribute. Apache Web Sites-Failed Pages Rate The failed pages rate per minute for the website. This metric is collected from the ITCAM for Applications, Agent for HTTP Serer, Apache Web Sites attribute group, Failed Pages Rate attribute. Apache Web Sites-Failed Login Rate The failed login rate per minute for the website. This metric is collected from the ITCAM for Applications, Agent for HTTP Serer, Apache Web Sites attribute group, Failed Login Rate attribute. Chapter 6. Isolating problems using the Business Serice Health pages 185

198 Table 35. Aailable metrics for the Time Window Analyzer (continued) Component Metrics Serer Linux OS CPU Current Aerage The current aerage of the system CPU time, expressed as a percentage. The aerage is calculated hourly. This metric is collected from the ITM Linux Agent, CPU Aerages attribute group, System CPU Current Aerage attribute. Virtual Enironment Databases Linux OS Swap Space Used The size (in MB) of swap space used. This metric is collected from the ITM Linux Agent, VM Statistics attribute group, Swap Space Used (MB) attribute. Windows OS Processor Time The aerage percentage of elapsed time that a processor has been busy executing non-idle threads, expressed as a percentage. This metric is collected from the ITM Windows Agent, Processor attributes group, % Processor Time attribute. VMWare VI CPU Utilization The aerage utilization of the CPU, expressed as a percentage. This metric is collected from the VMWare VI agent, KVM_SERVER_CPU attribute group, CPU Utilization attribute. VMWare VI Link Utilization The aerage percent usage of the NIC relatie to the the capacity of the link (including duplex). This metric is collected from the VMWare VI agent, KVM_SERVER_NETWORK attribute group, Link Utilization attribute. DB2 Buffer Pool Hit Ratio The oerall buffer pool hit ratio as a percentage for the database during the monitoring interal. This metric is collected from the DB2 Agent, Database01 attribute group, pool_hit_ratio_pct_for_int attribute. DB2 Deadlocks The number of deadlocks detected in the database during the monitoring interal. This metric is collected from the DB2 Agent, Database01 attribute group, deadlocks for int attribute. For more information about the Time Window Analyzer portlet, see the TBSM documentation at index.jsp?topic=%2fcom.ibm.tioli.itbsm.doc_6.1%2fsericeconfigurationguide %2Fbsmu_srtc_about_ui.html. Custom solutions using the Business Serice Healthproide portlets You can customize the Business Serice Health page in Tioli Integrated Portal as described in these topics. Building a page using the Business Serice Health portlets You can build your own pages that include the Business Serice Health portlets. 186 Solutions for BSM Guide:

199 About this task The portlets used on the Business Serice Health page and the Business Serice Health Details page are also aailable from the Tioli Intergrated Portal portlet palette. You can use these portlets to include business serice management features on custom pages that you build. Procedure 1. In the Tioli Integrated Portal, create a new free-form work page. You can create a new page by clicking the + tab. 2. Browse the portlet catalog to find the portlets you want to use on your page. The following BSM Accelerator portlets are aailable: Business Serices A TBSM Serice Tree portlet that shows a consolidated oeriew of each managed business serice and its supporting components. This portlet is part of the Business Serice Health page. By default, this portlet sends a NodeClickedOn eent to other portlets on the page, which can then display more information about the selected business serice. This portlet is aailable from the Business Serice Health portlet catalog. Business Serice Components A TBSM Serice Tree portlet that shows an oeriew of a managed business serice and its supporting components in an expandable tree iew. This portlet is part of the Business Serice Health Details page. By default, this portlet sends a NodeClickedOn eent to other portlets on the page, which can then display more information about the selected business serice. This portlet is aailable from the Business Serice Health portlet catalog. Business Serice Status Oer Time A Charting portlet that shows a historical graph of changes in the oerall status of a business serice during the last 12 hours, sampled at 15-minute interals. This portlet is part of the Business Serice Health page. By default, this portlet receies NodeClickedOn eents, which determine the serice for which data is shown. This portlet is aailable from the Business Serice Health portlet catalog. Business Serice Eent Count Oer Time A Charting portlet that shows a historical graph of the number of eents affecting a business serice during the last 12 hours, sampled at 15-minute interals. This portlet is part of the Business Serice Health page. By default, this portlet receies NodeClickedOn eents, which determine the serice for which data is shown. This portlet is aailable from the Business Serice Health portlet catalog. Business Serice Eents A TBSM Actie Eent List (AEL) portlet that shows all actie eents affecting a selected business serice or component. This portlet is part of the Business Serice Health and Business Serice Health Details pages. By default, this portlet receies NodeClickedOn eents from the Chapter 6. Isolating problems using the Business Serice Health pages 187

200 Business Serices or Business Serice Components portlet, which determine the serice or component for which eents are shown. This portlet is aailable from the Eents portlet catalog. Time Window Analyzer A TBSM Time Window Analyzer portlet that shows metrics and eents for selected business serices or components, charted oer time. This portlet is part of the Business Serice Health Details page. This portlet is aailable from the Analysis portlet catalog. 3. Drag the portlets you want to use to the content area of your page. 4. Optional: Click the Show Wires toolbar button to make any necessary changes to the default wiring of portlets on the page. By default, NodeClickedOn eents from the serice tree portlets select the context for information displayed in other portlets. You can disable these connections to remoe this behaior. 5. Click Sae to sae the page. Example To create a simple page for charting the eent count metric for business serices, you might create a page including the Business Serices and Business Serice Eent Count Oer Time portlets. The default wiring connects these portlets so that clicking a business serice in the Business Serices portlet automatically updates the Business Serice Eent Count Oer Time portlet to show data for the selected business serice. Adding custom charts to a page You can use TBSM Charts tool and the Charting portlet to add custom charts to a page. About this task The charts included on the Business Serice Health page show business serice status and eent count charted oer time. If you want your custom page to include charts for other metrics, you can use the TBSM Charts tool to create the charts and the Tioli Integrated Portal Charting portlet to add the charts to your page. Procedure 1. Use the TBSM Charts tool to create a new chart. To create a new chart, naigate to Administration > Serice Configuration, click Charts, and then click New. 2. For the data source, select one of the following: Database Data Source Uses data from a SQL query. Use TBSM Model Data Uses metrics from a serice or list of serices in the TBSM serice model. If your page includes a serice tree portlet (such as the Business Serices or Business Serice Components portlet), you can use a metric from the serice that is currently selected in that portlet. Use Policy For Data Uses data from an Impact policy. 3. If you are using a SQL query or an Impact policy as the data source, you can parameterize your SQL to accept the serice instance name or display name from the nodeclickedon eent from a serice tree portlet. This makes it 188 Solutions for BSM Guide:

201 possible to chart a metric based on the currently selected serice in a serice tree portlet on the same page. Add a new parameter and set the Serice Property Name to sericeinstancename for the instance name or displayname for the display name. You can also specify a default alue to be used when the page opens. Use param for the parameter to be substituted at run time, as in the following example: select * from TBSMHistory.metric where instancename = param 4. Click Sae to sae the TBSM chart. 5. Edit the page you want to include the chart. 6. From the portlet palette, drag a new Charting portlet to the page. 7. On the Chart Sources page, click Custom Charts. 8. Select the TBSM chart you created and then click Finish. Adding metrics to the Time Window Analyzer You can edit TBSM serice template rules to make additional metrics aailable for charting in the Time Window Analyzer (TWA) portlet. About this task The Time Window Analyzer portlet (included on the Business Serice Health Details page) shows metrics for the selected business serice components, charted oer time. You can add more metrics to those aailable by editing any TBSM serice template rule that has numerical output. Procedure 1. On the Edit Template tab of the TBSM Serice Editor, edit the rule whose data you want to make aailable in the TWA. The following types of rules are supported: Good, marginal, and bad incoming status rules Good marginal, and bad aggregation rules Numerical aggregation rules Numerical formula rules 2. In the rule properties, select the Store data for this rule for TWA check box. 3. Click OK to sae your changes. 4. In the Time Window Analyzer, select the new metric from the drop-down list to add it to the chart. The new metric shows as the rule's Display Name in the drop-down list. Chapter 6. Isolating problems using the Business Serice Health pages 189

202 190 Solutions for BSM Guide:

203 Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) This optional scenario builds on the base functionality proided by IBM Solutions for Business Serice Management to integrate the IBM Tioli Application Dependency Discoery Manager change eents into IBM Tioli Business Serice Manager (TBSM). It is expected that you are an experienced TBSM, TADDM, and Netcool/Impact user. The Solutions for BSM collects a set of best practice metrics from arious agents. This scenario allows those metrics to be oerlaid with TADDM change eents on the TBSM Time Window Analyzer. The Time Window Analyzer proides parallel time context data to the displayed metric data which can help with problem determination. About the Time Window Analyzer portlet Software requirements The Time Window Analyzer portlet charts metric data, which is frequently referred to as key performance indicators (KPIs). Oerlaid with releant occurrences or markers the Time Window Analyzer can show how to interpret the measured alues of the KPIs. This portlet proides a framework for presenting data so that it possible to infer meaningful information. The information can be acted upon with the goal of enhancing the customer's ability to better manage IT resources to the business needs. For a list of software requirements, see Product requirements on page 15. For more information about the components, refer to the following information center publications. IBM Tioli Netcool/OMNIbus, Installation and Deployment Guide com.ibm.netcool_omnibus.doc_7.3.1/omnibus/wip/welcome.htm IBM Tioli Application Dependency Discoery Manager, Administering. com.ibm.taddm.doc_721/welcome_page/welcome.html IBM Tioli Business Serice Manager, Administrator's Guide. com.ibm.tioli.itbsm.doc_6.1/welcome.htm. Copyright IBM Corp

204 Change eent process oeriew The following change eent flow diagram shows how these components work together to send change eents from TADDM to the Time Window Analyzer. A change on the application host is detected by TADDM Discoery, processed by the TADDM Change Eent Process and forwarded to Netcool/OMNIbus by way of an EIF probe. TADDM Change Eent Markers are proided through Netcool/Impact using policies that are proided by TBSM. TADDM Change Eents are detected by a Netcool/Impact eent reader. When the Netcool/Impact eent reader detects a change eent, the Netcool/Impact Change Marker Proider policy is triggered to write new entry to the marker data store. The Time Window Analyzer displays the new entry. Figure 9. Flow diagram for TADDM and the Time Window Analyzer Application Dependency Discoery Manager change eent modifications Complete the following tasks in each component to enable the display of TADDM change eents in the Time Window Analyzer user interface. This scenario describes monitoring a Linux system for changes to the configuration file/ect/hosts. TADDM can generate change eerts for a ariety of reasons. This scenario is based on the ability of TADDM to monitor important system files for changes. Integrating other change sources is outside the scope of this scenario. 192 Solutions for BSM Guide:

205 Remember: As best practice, to back up all files before making configuration changes. Enabling the generation of change eents In TADDM, complete the following steps to enable change eents. Procedure 1. Edit the file $COLLATION_HOME/etc/collation.properties. 2. Change the property com.ibm.cdb.omp.changeeent.enabled=true. 3. Sae the file. Configuring the resources to track Configure which resources you want to track for change eents and to which eent-handling systems the eents are sent: Procedure 1. Edit the $COLLATION_HOME/etc/EentConfig.xml file. 2. Insert the <listener> elements from one or more agent-specific sections. This example, inserts a listener for changes to configuration file objects on Linux computer systems and forward alerts to Netcool/OMNIbus. <listener object="computersystem" enabled="true" sendcauses="true" sendoriginguid="true"> <alert recipient="enterprise-eenthost-omnibus"/> <attribute name= fqdn operator= ends-with > <alue>ibm.com</alue> </attribute> <causefilter object="configfile" sendoriginguid= true /> <causefilter object="linuxunitarycomputersystem" sendoriginguid="true" /> <causefilter object="linux" sendoriginguid="true" /> </listener> For information about the format you must use to specify information in the EentConfig.xml file, see the comments within the file. More information and examples can also be found in the EentConfigDefault.xml file. Configuring the change eent recipient Configure the eent recipient that receies the change eents generated by TADDM. Procedure 1. Edit the $COLLATION_HOME/etc/EentConfig.xml file. 2. Update the Eent Recipients section at the bottom of the file to specify your EIF probe listener. The update defines the location of the Netcool/OMNIbus EIF probe properties file. The recipient name must match the alert recipient name, for example, enterprise-eenthost-omnibus used in Configuring the resources to track. <!--===================================================================--> <!-- DEFINE EVENT RECIPIENTS BELOW --> <!-- ==================================================================--> <!-- Template for Netcool/OMNIBus eent recipient --> <recipient name="enterprise-eenthost-omnibus" type="omnibus"> <config>/opt/ibm/taddm/dist/etc/omnibus.eif.properties</config> </recipient> Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) 193

206 Updating the EIF probe properties Edit the EIF probe properties file to assign the serer location and serer port properties for your enironment. Procedure 1. Edit the $COLLATION_HOME/etc/omnibus.eif.properties file. 2. Specify the EIF probe location by updating the SererLocation and SererPort properties to correspond to your enironment. Configure the Netcool/OMNIbus EIF probe properties file specified as the eent recipient in Configuring the change eent recipient on page 193. # Hostname where the NetCool/OMNIbus EIF probe resides SererLocation=myTBSMMachine.mylocation.com # Port the NetCool/OMNIbus EIF probe is listening on SererPort=9998 Configuring change eents for a business system Complete the following steps to configure change eents to communicate with the applications and business systems associated with the releant resource. Procedure 1. Edit the /$COLLATION_HOME/etc/propagationserer.xml file. 2. In each of the following sections, change the enabled attribute to "true". <!-- ================= to Application --> <relationship enabled="true" source="sys.computersystem" attribute="groups" target="app.application" targetattribute="true" collectiontype="app.functionalgroup" radius="1"/> <!-- ================= to BusinessSystem --> <relationship enabled="true" source="sys.computersystem" attribute="components" target="sys.businesssystem" targetattribute="true"/> Defining the configuration files to be monitored This step defines the configuration files that TADDM needs to monitor for changes that initiate a change eent. About this task This example monitors the /etc/hosts configuration file. Procedure 1. Start the TADDM Discoery Management Console. 2. Enable the Computer Systems template: a. In the Discoery pane, click Computer Systems, and select the template you want to edit. In this example, the LinuxComputerSystem template. b. Click Edit to open the Computer System Details window. c. In the Computer System Details window, select the Enabled check box. 3. Add the configuration files. a. In the Computer System Details window, click the Config Files tab. 194 Solutions for BSM Guide:

207 b. Click Add to specify the files to monitor. c. In the Search Path for Capture File window, specify the Type as Config file. d. Enter the Search Path as /etc/hosts. e. Select the Capture file contents check box, and click OK. 4. Click OK again to the sae the changes to the Computer System Details window. 5. Repeat this step to add other configuration files. Figure 10. Adding the configuration files. Scheduling the discoery Using the Discoery Management Console, set your discoery interal. About this task Set the discoery interal to an interal that you require, for example, eery 3 hours. Choose the interal based on how often you want your changes to be detected in your enironment. Procedure 1. Start the TADDM Discoery Management Console. 2. In the Discoery pane, click Schedule. 3. Click Add to open the Discoery Schedule window. 4. In the Details tab, complete the Name, Start Time, and Repeat information. Click OK. 5. In the Scope tab, select the scope for the discoery. Click OK to close the Discoery Schedule window. Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) 195

208 Restarting TADDM to implement the changes How to start and stop TADDM to implement the change eent configuration changes. Procedure 1. Stop TADDM. For Linux, Solaris, AIX, and Linux on System z Operating Systems: $COLLATION_HOME/bin/control stop 2. Start TADDM. For Linux, Solaris, AIX, and Linux on System z Operating Systems: $COLLATION_HOME/bin/control start Enabling the EIF probe to process change eents in Netcool/OMNIbus Configure the Netcool/OMNIbus EIF probe rules to include TADDM change eents. About this task Important: The following task is completed by the Solutions for BSM deployment utility if you ran the steps, Deploy Eent Manager Customizations and Configure EIF probe for TADDM Integration. Procedure 1. The TADDM rules files are shipped with Netcool/OMNIbus Deploy the subordinate rules files into the appropriate directory. cp $NETCOOL_HOME/omnibus/extensions/taddm/tioli_eif_taddm.rules $NETCOOL_HOME/omnibus/probes/<arch> where <arch> is your architecture 2. Uncomment the TADDM rules include statement in the master rules file, tioli_eif.rules. a. Edit the file $NETCOOL_HOME/omnibus/probes/<arch> /tioli_eif.rules. where <arch> is your architecture b. Find the following section and remoe the comment character # preceding the include line so that it looks like the following example: # Uncomment the following include line when using the TADDM integration # rules file found in.../extensions/taddm/ : include "tioli_eif_taddm.rules" Tip: When the EIF probe is correctly processing TADDM change eents, you can iew the change eents in the Netcool/OMNIbus eent list. In this scenario, the change eents hae an alert group alue of ConfigFile. If you are not seeing the change eents in the eent list, then check the eent filter defined in $COLLATION_HOME/etc/EentConfig.xml. The eent filter defines what change eents get sent to the EIF probe. After changing EentConfig.xml, you can run the TADDM changeeents.sh command to reprocess any change eents since the last discoery. 196 Solutions for BSM Guide:

209 Setting change eents expiration in Netcool/OMNIbus Because there is neer an automatic resolution of TADDM change eents, it is best practice to hae them automatically expire and be remoed from the ObjectSerer data store. This step is optional, but is considered best practice. Procedure 1. Edit the file $NETCOOL_HOME/omnibus/probes/<arch>/tioli_eif_taddm.rules. 2. Locate this section of the tioli_eif_taddm.rules file and remoe the comment character # so that it looks like the following section: # ExpireTime is not set. # Eents will remain in ObjectSerer foreer. # If required, the line below can be uncommented to set an expire time. # In the line below, the ExpireTime is set to 1 =7*24*60*60 3. Restart the EIF probe. Registering the Marker Proider serice in Netcool/Impact The Marker Proider Serice implements the marker proider role to capture TBSM data into the marker repository. About this task TBSM includes a Marker Proider Serice through the Netcool/Impact policies that are shipped in TBSM 6.1. The Marker Proider Serice conerts TADDM change eents coming into the Netcool/OMNIbus EIF probe and conerts them into markers. Complete the following steps to register the marker proider serices. Procedure 1. Log in to the TBSM Console. 2. In the Naigation area, select System Configuration > Eent Automation > Policies. 3. On the Policies tab, from the Global project menu, select the policy markerregisterproiders. 4. Click Edit to open the policy. 5. In the policy editor toolbar, click Run to run the policy and register the marker proider. You need to run the marker proider serice policy only once to register the policy. Tip: To erify that the Marker Proider Serice was registered, run the following command: $TBSMHOME/bin/tbsmmarker.sh GetMarkerProiderClasses -username <tipuser> -password <tippassword> Enabling the TBSM Update serice You must enable the $TBSM_HOME/etc/TBSM_tbsm_marker_user.props file so that the TADDM change eent markers are detected by TBSM. Procedure 1. On the TBSM data serer, edit the file, $TBSM_HOME/etc/ TBSM_tbsm_marker_user.props. Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) 197

210 2. Scroll to the end of the file, and find the following lines. Change the property impact.markerupdater.actiate to true. Important: The property can appear in the file more than once. You must update the last occurrence of this property, as the last occurrence takes precedence. # Added by TBSM_DataSr_Install-post-install impact.markerupdater.actiate=true 3. Restart the TBSM data serer. Tip: When you trigger a TADDM change eent, you can erify that the markers were generated. Run the following command on your TBSM data serer machine: $TBSMHOME/bin/tbsmmarker.sh GetMarkers -username <tipadmin> -password <tippassword> Markers with a category and type of CHANGEEVENT display. In addition, the marker has both a tbsm and taddm resource identifier. If it does not hae a tbsm resource identifier, then the marker update serice is not running. Creating the Object Serer Eent Reader in Netcool/Impact Create the Object Serer eent reader serice in Netcool/Impact to detect the TADDM change eents. Procedure 1. Log in to the TBSM Console. 2. In the Naigation area, select System Configuration > Eent Automation > Serices. 3. In the Serices tab, click the New serice icon to create the serice based on the OMNIbusEentReader serice. 4. In the General Settings tab, add a serice name, and select ObjectSerer_DS as the data source. 5. Select the Serice Log check box next to Write to file. 6. Select the Startup check box next to Automatically when serer starts. 7. In the Eent Mapping tab, select Stop testing after first match and select Get Updated Eents. 8. Click New to create the mapping. a. In the Create New Mapping window, enter the Filter Expression Agent = 'TADDM OMP Change Eent Module'. b. Select the Policy to Run as markerchangeproider. c. Select the Actie check box. You can optionally click the Analyze Filter button to erify the filter syntax. d. Click OK to sae the filter. 9. Click Sae to sae the new serice. 10. The new serice shows in the Serices list. Select the serice and select Start Serice from the menu to start the serice. Tip: When you trigger a TADDM change eent, you can erify that the markers were generated. Run the following command on your TBSM data serer machine: 198 Solutions for BSM Guide:

211 $TBSMHOME/bin/tbsmmarker.sh GetMarkers -username <tipadmin> -password <tippassword> Markers created with a category and type of CHANGEEVENT display. Triggering a change eent in TADDM You can now trigger a change eent in TADDM and see it display as a change eent marker in the Time Window Analyzer. About this task In this example, we are monitoring a Linux system for changes to the/etc/hosts file. Procedure 1. In one of the Linux systems being monitored, edit the file /etc/hosts. 2. Edit the file and add a comment to trigger a change. 3. Log in to the TADDM Discoery Management Console. 4. Run a new discoery in TADDM to pick up the change to the Linux system. Tip: You can erify that the change to the configuration file was detected in TADDM using the TADDM Data Management Portal. Run a Change History Report on the Linux system that was monitored. A change of type ConfigFile is reported. Viewing the change eent in the Time Window Analyzer After TADDM discoers the changes to the/etc/hosts file, it generates a change eent which is sent to the EIF probe, and then to Netcool/OMNIbus. The Netcool/Impact Proider Marker serice detects this eent and creates a marker which is displayed in the Time Window Analyzer. Procedure 1. Log in to the TBSM console. 2. In the Naigation area, select Aailability > Serice Aailability. 3. In the Serice Tree portlet, expand the tree to find the serice where the change was made. Right click the serice to show the menu. 4. Select Show > Compare Serice Metrics from the menu. 5. When the Time Window Analyzer opens, select the Oerlay check box and select Change Eents from the list menu. The change eent markers are oerlaid on top of the metric data in the charts. Chapter 7. Enabling change eents in TADDM to display the Time Window Analyzer (Optional) 199

212 200 Solutions for BSM Guide:

213 Figure 11. Time Window Analyzer showing the change eents Chapter 8. Troubleshooting This section will document troubleshooting common problems with the BSM Accelerator solution. Getting started with diagnosis This section contains information that assists you in troubleshooting problems with IBM Solutions for Business Serice Management. For an oeriew of the solution components and how they work together, see the Chapter 1, Introduction, on page 1. Finding solutions If you hae the IBM Information/Access program, you can search the RETAIN database, based on a keyword string, to find similar problems and their solutions. Working with IBM software support If it is necessary to call IBM Software Support, first collect the appropriate information as described in Obtaining IBM Software Support. Obtaining IBM Software Support This section describes options for obtaining support for IBM software products. Copyright IBM Corp

214 Obtaining fixes A product fix might be aailable to resole your problem. To determine what fixes are aailable for your IBM software product, follow these steps: 1. Go to the IBM Software Support Web site at support. 2. Click Download under the Software support section. 3. Select the releant product name for the from the alphabetic list, for example select I and choose IBM Tioli Business Serice Manager. 4. Optionally, select an operating system, or leae the default as Any operating system. 5. Type more search terms in the Enter search terms field if you want to refine your search. 6. You can refine your search by changing the categories in the Limit and sort results check boxes. 7. Click Search. 8. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix. For more information about the types of fixes that are aailable, see the IBM Software Support Handbook at handbook.html. Receiing weekly support updates To receie weekly notifications about fixes and other software support news, follow these steps: 1. Go to the IBM Software Support Web site at support. 2. Click My support in the upper right corner of the page. 3. If you hae already registered for My support, sign in and skip to the next step. If you hae not registered, click Register now. Complete the registration form using your address as your IBM ID and click Submit. 4. Click Edit profile. 5. In the Products list, select Software. A second list is displayed. 6. In the second list, select a product segment, for example, Application serers. A third list is displayed. 7. In the third list, select a product subsegment, for example, Distributed Application & Web Serers. A list of applicable products is displayed. 8. Select the products for which you want to receie updates, for example, IBM HTTP Serer and WebSphere Application Serer. 9. Click Add products. 10. After selecting all products that are of interest to you, click Subscribe to on the Edit profile tab. 11. Select Please send these documents by weekly Update your address as needed. 13. In the Documents list, select Software. 14. Select the types of documents about which you want to receie information. 15. Click Update. 202 Solutions for BSM Guide:

215 If you experience problems with the My support feature, you can obtain help in one of the following ways: Online Send an message to describing your problem. By phone Call IBM-4You ( ). IBM Software Support IBM Software Support proides assistance with product defects. Contacting IBM Software Support Before contacting IBM Software Support, your company must hae an actie IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you hae: For IBM distributed software products (including, but not limited to, Tioli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Adantage in one of the following ways: Online Go to the Passport Adantage Web page at software/howtobuy/passportadantage/pao_customers.htm. By phone For the phone number to call in your country, go to the IBM Software Support Web site at contacts.html and click the name of your geographic region. For customers with Subscription and Support (S & S) contracts, go to the Software Serice Request Web site at login. For customers with IBMLink, CATIA, Linux, OS/390, iseries, pseries, zseries, and other support agreements, go to the IBM Support Line Web site at For IBM eserer software products (including, but not limited to, DB2 and WebSphere products that run in zseries, pseries, and iseries enironments), you can purchase a software maintenance agreement by working directly with an IBM marketing representatie or an IBM Business Partner. For more information about support for eserer software products, go to the IBM Technical Support Adantage Web site at If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at and click the name of your geographic region for phone numbers of people who proide support for your location. To contact IBM Software support, follow these steps: 1. Determining the business impact on page Describing problems and gathering information on page Submitting problems on page 204 Chapter 8. Troubleshooting 203

216 Determining the business impact: When you report a problem to IBM, you are asked to supply a seerity leel. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria to assess the business impact of a problem: Seerity 1 The problem has a critical business impact. You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Seerity 2 The problem has a significant business impact. The program is usable, but it is seerely limited. Seerity 3 The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unaailable. Seerity 4 The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumention to the problem was implemented. Describing problems and gathering information: When describing a problem to IBM, be as specific as possible. Include all releant background information so that IBM Software Support specialists can help you sole the problem efficiently. To sae time, know the answers to these questions: What software ersions were you running when the problem occurred? Do you hae logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information. Can you recreate the problem? If so, what steps were performed to re-create the problem? Did you alter the system? For example, did you alter the hardware, operating system, networking software, and so on. Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem. Submitting problems: Use this topic to learn how to submit a problem to IBM Software Support. Submit your problem to IBM Software Support in one of two ways: Online Click Submit and track problems on the IBM Software Support site at Type your information into the appropriate problem submission form. By phone For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook at contacts.html and click the name of your geographic region. 204 Solutions for BSM Guide:

217 If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Wheneer possible, IBM Software Support proides a workaround that you can implement until the APAR is resoled and a fix is deliered. IBM publishes resoled APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution. Logs You can use logs when isolating issues with the deployment wizard and the IBM Solutions for Business Serice Management solution components. Deployment issues Logs can be found in the /tmp/solutionforbsm_userid directory, where userid is the current user running the deployment wizard. There are two types of logs: solution components logs These logs are created on the target machine you specify for a component in the deployment wizard. These logs are in corresponding subdirectories of the logs directory for the component. For example, if you are installing as user tbsm, the log for the Deploy Best Practice Monitoring task is in the /tmp/solutionforbsm_tbsm/enable_best_practice subdirectory on the target machine you specified in the Deploy Best Practice Monitoring task. The logs are also oerwritten by each task for eery run. You will only see the last run logs. As a best practice, make a back up copy of the log before you run the deployment wizard again. master log file The IRU_DeploymentWizard.log file is created at the beginning of the installation and copied to the logs directory at the end of the installation. Important: The master log file is copied to the directory on the machine where you run the deployment wizard. The master log gets oerwritten each time the deployment wizard is run. As a best practice, make a back up copy of the log before you run the deployment wizard again. This section contains information that assists you in troubleshooting problems related to deployment. Linux HTTP Serer situations do not work If the HTTP serer is installed to a location other than the default directory /opt/ibm/websphere, the file path names for the Tioli Monitoring situations Linux_LZ_HTTPSrPrcMissing_C and Linux_LZ_HTTPSrPrcMissing_W need to be manually updated to reflect the location change. Symptom On installing the HTTP serer, the Tioli Monitoring situations Linux_LZ_HTTPSrPrcMissing_C and Linux_LZ_HTTPSrPrcMissing_W do not work. Chapter 8. Troubleshooting 205

218 Resolution The following Tioli Monitoring situations point to the default HTTP serer installation directory, /opt/ibm/websphere. Linux_LZ_HTTPSrPrcMissing_C Linux_LZ_HTTPSrPrcMissing_W When you install the HTTP serer to a different directory, you also need to update the installation directory path for the situations. 1. Install Tioli Monitoring situations. 2. View Linux_LZ_HTTPSrPrcMissing_C and Linux_LZ_HTTPSrPrcMissing_W 3. Add the updated HTTP serer installation directory path to the situations. Test Connection button not acting as expected Using the Test Connection button on the Specify Target Computers panel, I cannot check if the target computers meet the conditions necessary for deployment. Problem description The text on the Specify Target Computers panel reads: "You can click Test Connection to iew whether or not the target computers you specified meet the conditions necessary for deployment." This text is misleading. By clicking the button you cannot check that the required software is running on the target system. You can only check that there is network connectiity, and that the username and password that you proided will work. Conflict detected on port The TBSM DashBoard Serer Component task generated errors in the log file. Problem description The TBSM DashBoard Serer Component task generated the following errors in the log file :27:03, **** ***SDF : The alue of COMMAND_INVOKED is /opt/ibm/tioli/tip2/profiles/tipprofile/bin/startserer.sh serer1 -user tipadmin -password xxxxx :27:03, **** IRU10000: The following command was issued: /bin/sh -c /tmp/iru/bsma_tbsm_start_stop.sh :27:14, **** IRU03807: The command generated the following output: ADMU0116I: Tool information is being logged in file /opt/ibm/tioli/tip2/profiles/tipprofile/logs/serer1/startserer.log ADMU0128I: Starting tool with the TIPProfile profile ADMU3100I: Reading configuration for serer: serer1 ADMU3028I: Conflict detected on port Likely causes: a) An instance of the serer serer1 is already running b) some other process is using port ADMU3027E: An instance of the serer may already be running: serer1 Resolution You can ignore the error. This error is caused by the deployment wizard trying to start the TBSM/TIP serer while the serer is already running. Deployment wizard fails to start The deployment wizard failed to start with an error [jaa] Jaa Result: Solutions for BSM Guide:

219 Problem description Jaa cannot run the installer in GUI mode. Resolution Run the deployment wizard from the root/main console Use VNC, not telnet to run the installation Export DISPLAY Deployment of Situation Update Forwarder task failed: missing library The deployment wizard failed to deploy the Situation Update Forwarder task. Problem description The deployment of the Situation Update Forwarder task failed with the following error: STACK_TRACE: 27 jaa.lang.unsatisfiedlinkerror: /tmp/isjozdngb/jre/bin/libawt.so: libxmu.so.6: cannot open shared object file: No such file or directory at jaa.lang.classloader$natielibrary.load(natie Method) at jaa.lang.classloader.loadlibrary0(classloader.jaa:2120) at jaa.lang.classloader.loadlibrary(classloader.jaa:1986) at jaa.lang.runtime.loadlibrary0(runtime.jaa:824) at jaa.lang.system.loadlibrary(system.jaa:908) at sun.security.action.loadlibraryaction.run(loadlibraryaction.jaa:76) at jaa.security.accesscontroller.dopriileged1(natie Method) Resolution This is because the ITM Situation Update Forwarder uses JDK1.4 which requires the libawt.so library. Install libxmu.so.6. Deployment of Situation Update Forwarder task failed: RC -46 The deployment wizard failed to deploy the Situation Update Forwarder task with error RC: -46. Problem description Deployment wizard failed to deploy the Situation Update Forwarder task with a return code RC: -46: :22:54, **** IRU10000: The following command was issued: /bin/sh c /tmp/iru//tec/esync2300linux.bin -options /tmp/sl_3723/solutionenabler/deployment/logs/tiolimntrgtools623a4tools.rsp -silent :23:15, **** IRU03807: The command generated the following output: :23:15, **** IRU03808: Process Returned RC: -46 Resolution libxp.so.6 is missing, install libxp.so.6. Preious deployment status misleading The Preious Deployment status section of the Summary panel is misleading. Chapter 8. Troubleshooting 207

220 Problem description The Preious Deployment status only references the current session and is not an indication of what has been deployed on the particular target system. Since the deployments is not usually done in one session the status displayed in the Preious deployment section is the status for preious deployments, as performed only within the current session of the installer. That is, when you close the installer and then reopen, the Preious Deployment status is reset to "Unattempted". Confusing password erification The password alidation does not behae as expected. Problem description You can come across this issue in the Solutions for BSM Deployment Wizard screens where you are asked to proide and erify a password. If the proided password and its erification do not match, you will get the following error message: IRU02027: The following confgure parameters require a alue: <password field> where <password field> is the name of the field containing the password alue. Resolution Click OK to dismiss the message and then ensure that the alues entered into the password field and the corresponding erify password field match. You can tell when the alues entered into the two fields do not match by a red circle with a white x next to the Typical tab name. ITCAM for Transaction Integration Packages task fails If I run the ITCAM for Transaction Integration Packages task twice it will fail the second time. Resolution Use these steps to recoer: 1. Open the tioli_directory/netcool/omnibus/probes/linux2x86/ tioli_eif.rules file for editing. 2. Find the line the following line: include "/xxxxx/custom_mapping.rules" 3. Comment out the line with a hash mark in the following manner: # include "/xxxxx/custom_mapping.rules" 4. Re-run the task. ITM Eent Synchronization Forwarder installation error Running the Install ITM Eent Synchronization Forwarder results in the return code RC = Solutions for BSM Guide: Resolution The target machine must hae 32-bit libxp and libxmu libraries een on a 64-bit OS. For example, both 32-bit and 64-bit machines must hae these libraries: libxmu.i386 libxp.i386

221 And 64-bit machines must hae these libraries: libxmu.x86_64 libxp.x86_64 Troubleshooting DLA automation This topic proides guidance when issues arise with the DLA Automation process. New IDML files from the DLAs are not loaded into TADDM To troubleshoot this issue, complete this procedure 1. Verify that the IdML books hae been created by the DLA programs: a. Open the client-side utility on the IBM Tioli Monitoring (ITM) serer. To erify that the DLA Automate tool is running. execute the command: ps -ef grep dlaautomate.sh b. Open the DLAAutomateClient.log file to determine if errors are present. c. Open the DLAAutomateClient.properties file, locate the agent.*.dlaoutputdir parameter, and take note of the location specified. Verify that IdML books hae been added to this directory. d. If the agent.*.taddmshare directory parameter is set in the DLAAutomateClient.properties, taddmshare directory is used instead of webserice to copy files to the TADDM serer. Ensure that this directory is mounted from the TADDM serer and that the IdML books are copied to that location. e. If the agent.*.taddmshare directory parameter is commented out in the DLAAutomateClient.properties and the taddmshare directory is not used, the webserice is used to copy files to the TADDM serer. Ensure that the system hosting the client-side utility can access TADDM serer on port Verify that the that the IdML books are loaded into TADDM: a. Open the serer-side utility on the TADDM serer and erify that the DLA Automate serer side tool is running. Execute the command: ps -ef grep dlaautomate.sh b. To erify that TADDM is running, execute the comment:./control.sh status c. Open the DLAAutomateLoader.log file and reiew it for any errors. Note: For more detailed tracing, set additional tracing in the TADDM collation.properties file. d. Open the DLAAutomateLoader.properties file and erify that IdML books are being created in the directory specified by the loaddirectory parameter. By default the directory set is the TADDM ar/loadidml directory. e. If IdML books are created, reiew the TADDM bulkload.log file for loadidml errors that result from errors in the IdML files. If IdML books are not created, stop the DLA Automate serer-side utility and erify that new IdML books then created in the directory specified by the monitordirectory parameter in the DLAAutomateLoader.properties file. Duplicate objects exists for the WebSphere serer To troubleshoot this issue, complete this procedure: Chapter 8. Troubleshooting 209

222 1. Ensure that the TADDM discoery has taken place before loading the IdML books. If not, successie loads might resole the issue. 2. Reiew the addwasmsndla.log file for any errors. 3. Open the DLAAutomateLoader.properties file. Locate the loaddirectory parameter and note the directory specified. By default, this is set to the TADDM ar/loadidml directory. Obtain the latest TMSDISC620*.zip file and if applicable, obtain the latest ITCAMfTT*.zip file. 4. After extracting the files, reiew the *.xml.reconcilied ersion of these IdML books. For your WebSphere serer objects, a BindAddress, Port, and IP Address are associated with each WebSphere serer. Verify that these alues match the alues that are stored in TADDM. 5. If the WebSphere serer objects does not contain these objects, but contains the.websphereproperty, erify that the alues match a WebSphere serer stored in TADDM. Business Serice Health pages issues This section contains information that assists you in troubleshooting problems related to the Business Serice Health pages. The BSM Accelerator serice tree is not populated In the Serice Naigation portlet, the BSM Accelerator serice tree folder is not populated and the BSM Accelerator serices are not displaying. Complete the following steps to resole the issue. Symptom From the Tioli Integrated Portal, click Adminstration > Serice Configuration > Serice Naigation > Serices or Serice Administration > Serice Naigation > Serices. The BSM Accelerator serice tree folder is not populated and the serices do not display. The resources exist in the Serice Component Repository (Serice Naigation > Serice Component Repository) but are not included in the BSM Accelerator serice in the Serice Naigation portlet. Resolution 1. Verify that the Discoery Library toolkit is running. You can start the toolkit on UNIX: $TBSM_HOME/XMLtoolkit/bin/tbsmrdr_start.sh. 2. Verify the resource enrichment serice ResEnrichReader is running. If the ResEnrichReader is running go to step number 3. If the ResEnrichReader serice is not running complete the following substeps. a. From the Tioli Integrated Portal naigation tree, select System Configuration > Eent Automation > Serices. b. From the Project list menu, select the TBSM_BASE project. c. From the list of serices that display check that the serice ResEnrichReader has a green check box next to it to indicate that the serice is running. If not, click the green arrow on the toolbar to start the serice. d. In the Discoery Library toolkit, reload the notifications which trigger the building of the serice tree and technology components. 1) Run $TBSM_HOME/XMLtoolkit/bin/utils.sh -e reload_notifications.xml. 210 Solutions for BSM Guide:

223 2) You are prompted for the TBSM database user ID and password. This command dries Netcool/Impact policies and toolkit processing which can take a few minutes depending on the number of resources in the Serice Component Repository. 3. Verify through the CRViewer that the shadow resources are created. You can start the CRViewer using the command: $TBSM_HOME/XMLtoolkit/tools/criewer.CRC-Start.sh The following classes which are created for the Solutions for BSM are displayed. tbsm:applicationshadow tbsm:technologygroup 4. If the classes exist, but the serice tree structure does not show, from the Tioli Integrated Portal naigation tree, select Adminstration > System Configuration. IntheSerice Naigation tree, select Serices > BSM Accelerator and in the Edit Serice tab, click Inalidate. The serice tree structure is displayed. Business Serice Health pages scroll down in the browser How to adjust the browser to display the contents of the Business Serice Health page or the Business Serice Health Details page properly. Symptom When opening the Business Serice Health page or the Business Serice Health Details page, the page sometimes scrolls down to display the Actie Eent List (AEL) portlet as the main portion of the page. Resolution This behaior is more prealent when using the Internet Explorer browser and can still occur een if the browser window is maximized. For Internet Explorer, there is no workaround. On Mozilla Firefox, you can aoid this behaior. Adjust the height of the browser window so that it is large enough to show more than the height of the Actie Eent List (AEL) portlet title. Business Serices panel displays no serice tree On Firefox, the Business Serices panel the Business Serice Health page, displays no serice tree. Problem description If you open the Business Serice Health page, the Business Serices panel is empty. The serice tree is not displayed, and you hae to refresh the page for the All monitored business serices are running normally. message to be displayed. Resolution There is no resolution aailable, because this is a Firefox 3.6.x bug. As Firefox 3.6.x is scheduled for EOL soon, and a new ersion will be aailable, this bug will not be fixed in the current ersion. Chapter 8. Troubleshooting 211

224 Time Window Analyzer panel displays no data On Firefox, the Time Window Analyzer panel on the Business Serice Health Details page displays no data for the selected serice. Problem description Select a serice in the Business Serice Components panel of the Business Serice Health Details page. You do not see any information about the serice in the displayed in the Time Window Analyzer panel. Howeer, if you right click a serice in the Business Serice Components panel, and select Compare Metrics, the new Time Window Analyzer page that opens, will display the data for the selected serice. If you turn on Firebug the issue will go away, but turning Firebug off again will bring it back. Resolution There is no resolution aailable, because this is a Firefox 3.6.x bug. As Firefox 3.6.x is scheduled for EOL soon, and a new ersion will be aailable, this bug will not be fixed in the current ersion. A temporary workaround would be to install, and turn on Firebug on the Business Serice Health Details page. Time Window Analyzer shows extra data line The Time Window Analyzer shows an extra data line that connects chart end points. Problem description When serice data is displayed in the Time Window Analyzer window of the Business Serice Health Details page an extra data line is included that joins the initial and final points of the graph. This seems to only occur when both critical and marginal eents are both logged against the serice in question. If either one or other eents exists then you cannot see this superimposed line. The problem also occurs regardless of whether the initial status in the graph was critical or marginal. Resolution This is only a Firefox issue, for the same setup the problem is not isible in Internet Explorer 8. There is no resolution for this issue. Cannot reopen Business Serice Health page If I close the Business Serice Health page I get an error when I try to open it again. Problem description Open the Business Serice Health page from the naigator, and then close it by clicking the X on the page's tab. If you try to open the page again, the browser reports an error and the page will not load. 212 Solutions for BSM Guide:

225 Resolution This issue occurs only on Internet Explorer. There is no resolution. As a workaround you can log out of IBM Solutions for Business Serice Management and log in again. Business Serice Status Oer Time chart has last timestamp in X-axis oerwritten The Business Serice Status Oer Time chart in the Business Serice Health page has two hours oerwritten as the last timestamp on the X-axis. Resolution There is no resolution or workaround. Chart titles in Business Serice Health page not displayed correctly The titles of the Business Serice Status and Business Serice Eent Count charts are displayed incorrectly. Problem description The titles of the Business Serice Status and Business Serice Eent Count charts are displayed with underscores, TITLE suffix, and all capital letters: BUSINESS_SERVICE_STATUS_TITLE BUSINESS_SERVICE_EVENT_COUNT_TITLE This problem occurs when certain browser locales are set. Resolution You can workaround an unsupported browser locale. First, determine what unsupported locale the browser is using: 1. Log in to the IBM Solutions for Business Serice Management and open the About portlet. 2. Switch to the Support tab. 3. The current locale is shown in the Dojo > Locale > Serer request field. Only the following browser locales will result in proper string resolution on the charts: cs de en en_us es fr hu it ja ko pl Chapter 8. Troubleshooting 213

226 pt_br ru zh_cn zh_tw Now, you need to add support to this unsupported locale. For the sake of this example, we will add support for the de_ch locale: 1. In the the Dashboard serer, naigate to the %TIP_HOME%\..\tip2Components\ BIRTExtension\platform\workspace\msg directory. 2. Create a copy of the business_sericechart.properties file for the unsupported locale: cp business_sericechart.properties business_sericechart_de_ch.properties Verify that the workaround is in effect: 1. Log out of the IBM Solutions for Business Serice Management and log in again. 2. Open the Business Serice Health page and check that the the Business Serice Status and Business Serice Eent Count charts titles are now displayed properly. 214 Solutions for BSM Guide:

227 Chapter 9. Customizing the solutions Introduction These topics describe how to customize the default configuration of the IBM Solutions for Business Serice Management. The IBM Solutions for Business Serice Management dashboard displays key information about a number of technology types to show how different technology components are performing for the business serices they support. The technology types monitored by default are: Application Serers Clients Databases Serers Transactions Virtual Enironments Web Serers For technology types, you need to collect data from arious resources and eents that affect the associated business serices. This section of the document describes arious configuration steps you complete to create a technology type serice and ensure that the dependent resources and eent mapping are configured correctly. Consider the following scenarios types when bringing resources into the Solutions for BSM model. Agent with Discoery Library Adapter supported by Solutions for BSM Agent with Discoery Library Adapter not supported by Solutions for BSM Resources from a non Discoery Library Adapter source Without TADDM in the enironment Agent with Discoery Library Adapter supported by Solutions for BSM This scenario is for resources that are discoered by an agent that has a Discoery Library Adapter and is supported by Solutions for BSM. These agents are: Agents for Operating Systems Application Management Console Agent for Web Response Time Agent for Robotic Response Time Agent for Transaction Tracking Agent for DB2 Agent for WebSphere Application Serer Agent for HTTP Serer Agent for Virtual Serers Copyright IBM Corp

228 Resources discoered by these agents are automatically imported into Solutions for BSM and assigned to the appropriate technology type and no configuration is required from the user. Agent with Discoery Library Adapter not supported by Solutions for BSM This scenario is for resources that are discoered by an agent that has a Discoery Library Adapter but is not supported automatically by Solutions for BSM. The process of importing these resources into TBSM and incorporating them into the Solutions for BSM technology type model is described in detail in WebSphere MQ Agent scenario on page 217. In the procedure, the user needs to configure components in IBM Tioli Monitoring, IBM Tioli Application Dependency Discoery Manager, IBM Tioli Netcool/OMNIbus, and IBM Tioli Business Serice Manager, as well as the agent itself, in order to integrate MQ resources in the Solutions for BSM. Some examples of other agents in this category include: ITCAM for Microsoft Applications Agent Agents ITCAM for Siebel Agent ITCAM for PeopleSoft ITCAM for Energy Management Agents Resources from a non Discoery Library Adapter source This scenario is for resources for which there is no Discoery Library Adapter. This scenario could include IBM Tioli Monitoring or ITCAM agents which do not hae a Discoery Library Adapter written for them. Generally, this would include any third party source of model data. Bringing resources without a Discoery Library Adapter into the Solutions for BSM model requires either creation of a custom IdML book to import into TBSM or the usage of the Serice Component Registry API in TBSM. The Custom Serice Model scenario on page 243 in this document describes the procedure of creating a custom IdML book to bring third party resources into the Solutions for BSM model. It goes through an example of a fictitious third party network discoery tool and describes how to bring the network topology into a technology type serice in the Solutions for BSM model. Without TADDM in the enironment TADDM plays an integral role in the Solutions for BSM enironment. Resources discoered by the agents are sent from IBM Tioli Monitoring to TADDM using Discoery Library Adapters. In Solutions for BSM they are assigned to business serices or business applications (and additional discoered resources may be added or merged with the model in Solutions for BSM as well) and then the model is imported from Solutions for BSM to TBSM through the discoery library toolkit. If a customer does not hae Solutions for BSM in the enironment, it is still possible to import the resources into technology types. This scenario is described in Without TADDM in the enironment scenario on page Solutions for BSM Guide:

229 WebSphere MQ Agent scenario To configure the ITCAM for WebSphere MQ agent, the WebSphere MQ serer must be installed and configured. This document does not go through configuration of WebSphere MQ but it assumes that there is an existing WebSphere MQ serer with one or more queue managers. The agent monitors the queue managers, gathering many different metrics about their queues. The ITCAM for WebSphere MQ agent can be installed on the same system as the WebSphere MQ serer or on a remote system. If it is installed remotely then it has some limitations on the statistics in can monitor. For more information about the WebSphere MQ Agent, see the documentation aailable from the following URL: %2Fcom.ibm.omegamon.mes.doc_7.0.1%2Fkmquserguide701.htm The WebSphere MQ agent must be configured to point to a Tioli Enterprise Monitoring Serer using the following command: <ITM_INSTALL_HOME>/bin/itmcmd configure A mq The WebSphere MQ agent is then configured to monitor a queue manager. When that is complete, the agent is started with the command: ITM_INSTALL_HOME/bin/itmcmd agent o <queue manager name> start mq. The following flow diagram illustrates the architecture of data flow from WebSphere MQ to the agent, Tioli Monitoring, and then on to TADDM, Netcool/OMNIbus, and TBSM. Chapter 9. Customizing the solutions 217

230 Figure 12. Data flow diagram of WebSphere MQ customization Configuring Tioli Monitoring for WebSphere MQ Monitoring Agent These topics describe how to configure the IBM WebSphere MQ Monitoring agent for theibm Solutions for Business Serice Management. The WebSphere MQ Monitoring agent is part of the IBM Tioli Composite Application Manager for Applications product suite. You can use the WebSphere MQ Monitoring agent, to collect and analyze data that is specific to WebSphere MQ for all your remote and local queue managers from a single antage point. You can then track trends in the data that is collected and troubleshoot system problems using the product proided workspaces. Installing supporting files Installing the supporting files for Tioli Enterprise Portal and Tioli Enterprise Monitoring Serer. When any agent is deployed in Tioli Monitoring, the support files for the agent must be installed in Tioli Enterprise Monitoring Serer and Tioli Enterprise Portal. Run the command install.sh from the agent installation media on the Tioli Enterprise Monitoring Serer and Tioli Enterprise Portal serers. Details on these instructions can be found at the following link: %2Fcom.ibm.wrs62.doc%2Finstagentsupfiles.html 218 Solutions for BSM Guide:

231 Installing WebSphere MQ Agent DLA template into Tioli Enterprise Portal Serer In order for WebSphere MQ resources to be exported from the Tioli Monitoring, the WebSphere MQ discoery library adapter must also be installed in the Tioli Enterprise Portal Serer. You can download the WebSphere MQ discoery library adapter is from the following URL, details?catalog.label=1tw10tm91. Extract the following two files from the WebSphere MQ Agent discoery library adapter package and copy them into the tmsdla directory of the Tioli Enterprise Portal Serer installation. kmq_tmsdla.xml kmq_tmsdla.jar On Linux, the tmsdla directory is <ITM_INSTALLDIR>/<arch>/cq/bin/tmsdla. Viewing the WebSphere MQ series workspace To erify that Tioli Monitoring is configured properly for the WebSphere MQ agent and that data is coming from the agent, you can iew the WebSphere MQ Series workspace in the Tioli Enterprise Portal. The following figure shows an example of two queue managers BK6_1 and BK7_1 being monitored by the WebSphere MQ agent and showing in the Tioli Enterprise Portal. Figure 13. WebSphere MQ workspace Chapter 9. Customizing the solutions 219

232 Integrating WebSphere MQ resources into the serice model Integrating WebSphere MQ resources into your serice model technology groups. The Solutions for BSM model in TBSM for resources obtained through any agent contains a Business Application serice at the top and set of children representing the different technology groups that support the application. Under each technology grouping object are the actual resources for the technology that are imported using the discoery library toolkit. There can be any number of top-leel Business Applications, each with their own set of technology type children that represents its own collection of technology resources. The end goal is to produce a model structure similar to the following example: DayTrader and Inentory Application are the top-leel business applications. Each business application has its set of technology resources that support it and these resources are diided into the technology type serices below them, for example Application Serers, Clients, and Databases. This example shows how to configure TBSM to add the MQ_QueueManagers technology type. All the other technology types show automatically with the Solutions for BSM. The MQ_QueueManagers type contains all the Queue Managers that support the Business Application of the type Inentory Application. 220 Solutions for BSM Guide:

233 Figure 14. Business applications and technology types including MQ_QueueManagers technology type Complete the following steps to bring WebSphere MQ resources discoered by the WebSphere MQ agent into the Solutions for BSM model using the three model leels: 1. Run tmsdla on Tioli Monitoring. 2. Import the resulting discoery library adapter book into TADDM. 3. Assign the WebSphere MQ Queue Manager resources in TADDM to a Business Application. 4. Load the TADDM Model into TBSM. 5. Create Templates/Rules in TBSM to be assigned to the WebSphere MQ resources. 6. Configure the Discoery Library Toolkit and Business Serice Composer to create a Technology type for the WebSphere MQ resources. 7. Configure the custom Tree templates in TBSM to incorporate the WebSphere MQ resources. Running the discoery library adapter on Tioli Monitoring If the Solutions for BSM glue code is deployed, the Tioli Monitoring discoery library adapter runs automatically periodically. Chapter 9. Customizing the solutions 221

234 Procedure 1. To manually run the Tioli Monitoring discoery library adapter issue the following command from the command line on the computer where the Tioli Enterprise Portal is installed: <itm_installdir>/bin/itmcmd execute cq "tmsdla.sh" 2. The Tioli Monitoring discoery library adapter generates an IdML book to the tmsdla directory by default. The tmsdla directory is similar to the following example: <itm_installdir>/lx8263/cq/bin/tmslda. The output file is gien a name that includes both the computer it was run on and the time that the file was generated. TMSDISC100-A.<FQHN>.<date>T<time>Z.refresh.xml For example: TMSDISC620-A.IBMSYL T Z.refresh.xml 3. If there are WebSphere MQ resources present in Tioli Monitoring, the discoery library adapter book contains WebSphere MQ resources under the section that starts with: <! tmsdla/kmq_tmsdla.xml Importing the discoery library adapter into TADDM Importing the discoery library adapter into TADDM. About this task The Solutions for BSM glue code handles transferring the discoery library adapter book from the Tioli Monitoring serer to the TADDM serer and imports it automatically into TADDM. Procedure To do this step manually, you copy the IdML book to the TADDM serer and run the following command in TADDM:./loadidml.sh -o -f <idml file> Assigning the MQ resources in TADDM to a business application Assign the MQ resources in IBM Tioli Application Dependency Discoery Manager. About this task To assign the MQ resources under the application, click on the Messaging Serers link, and drill down to assign the desired MQ resources to the application. Procedure 1. Log into the TADDM Data Management Portal and bring up the Grouping Composer from the Discoery tab. 222 Solutions for BSM Guide:

235 Figure 15. TADDM Grouping Composer 2. Click New to create a new Business Application or edit an existing business application, where you can place the MQ resources. 3. Select the Content tab for the Application and click Inentory Summary. Figure 16. TADDM Application Content tab 4. To assign the MQ resources under the application, click the Messaging Serers link, and drill down to assign the desired MQ resources to the application. The resources show by category in the top leel of the Content tab. Chapter 9. Customizing the solutions 223

236 Figure 17. TADDM Application Content tab showing the assigned resources Loading the TADDM model into TBSM Load the TADDM Model into TBSM About this task Assuming the Discoery Library Toolkit in TBSM is configured to read directly from TADDM, you do not need to export/import any IdML books from TADDM to TBSM. Procedure 1. You can trigger a TADDM import to happen right away by running the following command: $TBSM_HOME/XMLToolkit/bin/cmdbdiscoery.sh b r. This process can take some time, depending on the size of the model. 2. You can monitor the progress using the log file $TBSM_HOME/XMLToolkit/log/ msggmt_xt.log. Creating templates and rules in TBSM for WebSphere MQ resources The next step is to create templates and rules in TBSM to incorporate the WebSphere MQ resources into the Solutions for BSM structure. Procedure 1. Create the BSMAccelerator_MQGroup template. This template is assigned the WebSphere MQ technology type serices that are created. 2. Create DirectChildEentStatus dependency rule. 224 Solutions for BSM Guide:

237 Figure 18. Creating the DirectChildEentStatus dependency rule 3. Now create a Numeric Dependency Rule by clicking the button shown in the following figure: Figure 19. Creating the Numeric Dependency Rule 4. Name the rule DirectChildEentStatus. 5. From the Child Template menu, select SCR_SericeComponentRawStatusTemplate. 6. From the Child Metric rule menu, select ComponentRawEentStatusRule. 7. From the Aggreagation function: options, select Maximum The rule depends on the ComponentRawEentStatusRule and is configured as a maximum dependency rule. This rule enables the WebSphere MQ Chapter 9. Customizing the solutions 225

238 technology type serice to hae its status affected only from children (WebSphere MQ Queue Managers) that hae eents directly affecting them. If a machine that a Queue Manager runs on gets an eent, the status propagates to the Queue Manager, but not to the Queue Manager type serice. 8. Add the following parameters to the BSMAccelerator_MQGroup template. The properties names and alues are: DoFunctionEnrichment true DynamicEentCountRollUpLeel leaf Figure 20. TBSM Adding properties to the template 9. Configure the Output Expressions for the BSMAccelerator_MQGroup template. a. Add the Bad expression DirectChildEentStatus.Value >=5. b. Add the Marginal expression DirectChildEentStatus.Value >= Solutions for BSM Guide:

239 Figure 21. Configuring the Output Expressions 10. Create the BSMAccelerator_MQGroup rule on the BSMAccelerator_SericeApplication template. The next step is to create a dependency worst case rule on the BSMAccelerator_SericeApplication template that depends on the BSMAccelerator_MQGroup template. This rule enables the status to propagate from the WebSphere MQ technology type serice to the business application it depends on. Chapter 9. Customizing the solutions 227

240 Figure 22. Creating the Dependency rule 11. Edit the policy in the Serice Visability Rule. On the BSMAccelerator_SericeApplication template, edit the Serice Visability Rule and click the Edit Policy button. Scroll toward the bottom of the policy and look for the line containing the BSMAccelerator grouping templates. Add the BSMAccelerator_MQGroup template to this code, see the phrase (InstanceNode.BSMAccelerator_MQGroup.Value > 0) or and sae the policy: if ((InstanceNode.BSMAccelerator_SerersGroup.Value > 0) or (InstanceNode.BSMAccelerator_TransactionsGroup.Value > 0) or (InstanceNode.BSMAccelerator_AppSerersGroup.Value >0)or (InstanceNode.BSMAccelerator_WebSerersGroup.Value > 0) or (InstanceNode.BSMAccelerator_DBGroup.Value > 0) or (InstanceNode.BSMAccelerator_VirtualEnironmentsGroup.Value > 0) or (InstanceNode.BSMAccelerator_ClientsGroup.Value > 0) or (InstanceNode.BSMAccelerator_MQGroup.Value > 0) or ) This SericeVisibility rule ensures that only technology types with non-green status appear underneath a business application in the Serice Health iew. 12. Create MQ Metric Template/Rules as you need. If you want to bring in metric data for the WebSphere MQ Queue Manager serices into TBSM, you must first create data fetchers against Tioli Monitoring. This procedure is described in the section: Metric data flow from Tioli Monitoring to TBSM > Creating a data fetcher to pull metric data from Tioli Monitoring. You must create a template named BSMAccelerator_MQMetrics and create a dependency rule from the BSMAccelerator_Metrics template to depend on this new template. In the BSMAccelerator_MQMetrics template, you configure incoming status rules fed by the WebSphere MQ data fetchers you 228 Solutions for BSM Guide:

241 created. This procedure is described in the section: Metric data flow from Tioli Monitoring to TBSM > Create Incoming Status Rule to receie data from the data fetcher. Configuring Discoery Library Toolkit for WebSphere MQ resources Configuring the Discoery Library Toolkit for importing WebSphere MQ resources. About this task The Discoery Library Toolkit needs to be configured to map the resources defined in the IdML book it receies from TADDM into serices in TBSM. A key configuration piece for this step is the CDM_TO_TBSM4x_MAP_Templates.xml file. This file maps resource classes that are read by TADDM to templates in TBSM. Any resources in the TADDM IdML book that do not hae classes that are mapped in the CDM_TO_TBSM4x_MAP_Templates.xml file are not imported into the TBSM model. An additional requirement to import a resource type from TADDM is the classfilters.xml file in the toolkit which must be configured to import the cdm class. The classfilters.xml file contains the list of all cdm classes that the discoery library toolkit is to import into resources in TBSM. For many discoery library adapters, such as WebSphere MQ, classfilters.xml is configured automatically with the classes that are useful to import into TBSM. In some scenarios, this file would need to be edited. The WebSphere MQ agent discoery library adapter creates many different types of resources corresponding to different components of the WebSphere MQ queuing model. These resources are mapped to different cdm classes in the discoery library adapter. TBSM is configured to import only a few of these resource types using the classfilters.xml file since most them are too low leel to be interesting for a TBSM model or iew. The primary WebSphere MQ resource type of interest to TBSM is the WebSphere MQ Queue Manager, which is represented by the cdm class, cdm:app.messaging.mq.mqqueuemanager. The CDM_TO_TBSM4x_MAP_Templates.xml file maps this cdm class to the BSM_AppSererGroup template as the primary template. It adds the additional templates SCR_RetrieeDependentObjectsTemplate, SCR_SericeComponentRawStatusTemplate, and BSMAccelerator_EentCount. Solutions for BSM adds the last mapping. This is done in the following configuration: <template primary="bsm_appserergroup"> <othertemplate name="scr_retrieedependentobjectstemplate"/> <othertemplate name="scr_sericecomponentrawstatustemplate"/> <!-- Added for BSMAccelerator Eent Count Metric --> <othertemplate name="bsmaccelerator_eentcount"/> <cdmclass name="cdm:app.j2ee.websphere.webspherecell"/> <cdmclass name="cdm:app.j2ee.jboss.jbossdomain"/> <cdmclass name="cdm:sys.zos.mqsubsystem"/> <cdmclass name="cdm:app.packagedapp.siebel.siebelenterprise"/> <cdmclass name="cdm:app.j2ee.websphere.webspherenode"/> <cdmclass name="cdm:app.messaging.mq.mqqueuemanager"/> </template> Chapter 9. Customizing the solutions 229

242 In this example, change the template mapping for MQQueueManager resources to add the BSMAccelerator_MQMetrics template so that the Queue Manager resources that are imported into TBSM also belong to the BSMAccelerator_MQMetrics template. Remoe the MQQueueManager line from the aboe mapping and create a new mapping uniquely for QueueManagers. So the configuration looks like the following example: <template primary="bsm_appserergroup"> <othertemplate name="scr_retrieedependentobjectstemplate"/> <othertemplate name="scr_sericecomponentrawstatustemplate"/> <!-- Added for BSMAccelerator Eent Count Metric --> <othertemplate name="bsmaccelerator_eentcount"/> <cdmclass name="cdm:app.j2ee.websphere.webspherecell"/> <cdmclass name="cdm:app.j2ee.jboss.jbossdomain"/> <cdmclass name="cdm:sys.zos.mqsubsystem"/> <cdmclass name="cdm:app.packagedapp.siebel.siebelenterprise"/> <cdmclass name="cdm:app.j2ee.websphere.webspherenode"/> </template> <template primary="bsm_appserergroup"> <othertemplate name="scr_retrieedependentobjectstemplate"/> <othertemplate name="scr_sericecomponentrawstatustemplate"/> <!-- Added for BSMAccelerator Eent Count Metric --> <othertemplate name="bsmaccelerator_eentcount"/> <othertemplate name= BSMAccelerator_MQMetrics /> <cdmclass name="cdm:app.messaging.mq.mqqueuemanager"/> </template> The next step is to assign the WebSphere MQ technology type serices to the BSM_MQGroup template. To assign the template, you must edit the CDM_TO_TBSM4x_MAP_Templates.xml file. For more information, see Configuring CDM_TO_TBSM4x_MAP_Template.xml for the WebSphere MQ type templates. Configuring CDM_TO_TBSM4x_MAP_Template.xml for the WebSphere MQ type templates: Assign the WebSphere MQ technology type serices to the BSM_MQGroup template. About this task To assign the template, you need to edit the CDM_TO_TBSM4x_MAP_Templates.xml file. The same file that you edited to assign the actual QueueManager resources to the BSMAccelerator_MQMetrics template. Procedure 1. First, obtain the current copy of the file from the database, using the following command: <tbsm_installdir>/tbsm/xmltoolkit/bin/getartifact U <dbuser> -P <dbpass> -d <directory to write file to> -n CDM_TO_TBSM4x_MAP_Templates.xml c scrconfig. 2. Now edit the file and add the following section: <!-- Assign BSMAccelerator_MQGroup template to all MQ grouping objects --> <Policy name="mqgrouptemplateassignment"> <Rule name="mqgrouptemplates"> <condition attrkeyword="tbsm:label" operator="=" alue="mq_queuemanagers" /> </Rule> <template primary="bsmaccelerator_mqgroup"> 230 Solutions for BSM Guide:

243 <othertemplate name="scr_retrieedependentobjectstemplate" /> <!-- Added for BSMAccelerator Eent Count Metric --> <othertemplate name="bsmaccelerator_eentcount" /> </template> </Policy> <Mapping policy="mqgrouptemplateassignment" class="tbsm:technologygroup" /> This configuration assigns the template BSMAccelerator_MQGroup as the primary template of the technology type resources that are created from the Business Serice Composer. It also assigns the additional templates SCR_RetrieeDepedentObjectsTemplate and BSMAccelerator_EentCount template. 3. Upload the file to the database using the following command: <tbsm_installdir>/tbsm/xmltoolkit/bin/putartifact.sh U <dbuser> -P <password> -n <path to CDM_TO_TBSM4x_MAP_Templates.xml> -c scrconfig. Configuring Business Serice Composer and Discoery Library Toolkit to create a technology type Use the Business Serice Composer feature to configure the creation of the technology types for WebSphere MQ resources. About this task The Component Registry Viewer includes the Business Serice Composer feature. To open the Business Serice Composer, you must hae the Solutions for BSM project file in the directory <tbsm_installdir>/tbsm/xmltoolkit/tools/criewer/ projects. The project file can be obtained by extracting the file <tbsm_installhome>/tbsm/xmltoolkit//xml/scr/archie/projects/ BSMAccelerator_1r1.xml_<DDDD>.zip into the projects directory called BSMAccelerator_1r1.xml. To start the Component Registry Viewer: Procedure 1. Change to the directory, <tbsm_installdir>/tbsm/xmltoolkit/tools/ criewer/. 2. Run the command: CRC-Start.sh. 3. Once inside the CRViewer, click the Business Serice Composer icon: Figure 23. CRViewer: Business Serice Composer icon Chapter 9. Customizing the solutions 231

244 4. Select the BSMAccelerator_1r0 project 5. Click the Open Selected Folder icon aboe the Projects tab. 6. In the Project View on the right side, right click Input -- cdm:name::definetechgroups+cdm:name+policy and select Edit. 7. In the bottom panel, click matchingcriteria to open a table in the Input Values panel on the lower right. 8. Click any row in the table, you can add, edit, or delete a row. Figure 24. Business Serice Composer Project View 9. Click the little green plus sign to add a new row, to create the WebSphere MQ technology type. Figure 25. Input alues for new row 10. Complete the columns in the table as follows: Figure 26. Completed new row a. Selection Class: set to cdm:app.application, to create a technology type under a Business Application object coming from TADDM. b. Selection Pattern: set to %, to indicate that you are creating a type regardless of the name of the application. c. Category Identifier: set to MQ_QueueManagers. 232 Solutions for BSM Guide:

245 d. Category Label: set to MQ_QueueManagers the same as the Category Identifier. e. Technology Group Class: set to cdm:app.messaging.mq.mqqueuemanager to map the WebSphere MQ Queue Manager resources underneath this technology type. 11. Create two more identical rows to this example with the one exception, set the Selection Class to cdm:core.collection and cmd:sys.businesssystem. These rows enable technology types to be created for Business System and Collection objects coming from TADDM as well as for Business Application objects. 12. Click Update to update the changes. 13. Click the X on the upper right of the Business Serice Composer Workspace inside the CRViewer window. You are prompted to sae the changes for the Solutions for BSM project. Click Yes. Process the changes to Discoery Library Toolkit To process the changes to the Discoery Library Toolkit you run two commands. Once processing is complete you can iew the WebSphere MQ serice type and resources. About this task Before running the processing for the Discoery Library Toolkit, the ResEnrichReader serice must be running in Netcool/Impact. Procedure 1. Log in to the TBSM Console. 2. In the Naigation area, select System Configuration > Eent Automation > Serices. 3. On the Serices tab, from the Project menu, select Global project to iew a list of all the serices. 4. View the ResEnrichReader serice, if the icon is red, right click the serice and select Edit. 5. Select the Startup check box next to Automatically when serer starts so that the serice starts automatically when the serer starts. Click Sae. 6. In the Serices tab, Select the serice and select Start Serice from the menu to run the serice. 7. Once the serice is running, you can run the following commands on the Discoery Library Toolkit. Run <tbsm_installdir>/tbsm/xmltoolkit/bin/utils.sh U <dbuser> -P <dbpassword> -e reload_cdm_definitions.xml This command updates the toolkit with the changes made to the CDM_TO_TBSM4x_MAP_Templates.xml. View the msggmt_xt.log file to check when the processing is finished. 8. Next run the command: <tbsm_installdir>/tbsm/xmltoolkit/bin/ loadbusinesscomposerdefinitions.sh U <dbuser> -P <dbpassword> -n <tbsm_installhome>/tbsm/xmltoolkit /tools/criewer/projects/bsmaccelerator_1r0.xml When processing is finished click down from your application in the serice tree in TBSM and iew the MQ_QueueManagers type serice with the Queue Manager resources underneath. Chapter 9. Customizing the solutions 233

246 Eent Flow from Tioli Monitoring to TBSM Configure situation eents and the Eent Integration Facility (EIF) probe for the WebSphere MQ agent. To get status eents flowing for the WebSphere MQ agent to the corresponding resources in TBSM, complete the following steps: Configure a situation in Tioli Monitoring. Configure the situation eent to be forwarded to the EIF probe for Netcool/OMNIbus used by TBSM. Configure the EIF probe with the WebSphere MQ agent rules file. Configuring a situation in Tioli Monitoring Configuring a new situation for the WebSphere MQ serer. About this task With the WebSphere MQ support package in Tioli Monitoring, many situations are configured automatically that trigger when certain metrics in the WebSphere MQ serer exceed gien thresholds. These situations can be iewed in the Situation Editor accessed from the Edit option in the main menu. You can configure a new situation from the Situation Editor by clicking the MQSeries group. A simple example is outlined here: Procedure 1. Configure the Name, Description, and Formula of the situation. Figure 27. Configuring the Name, Description, and Formula of a situation 234 Solutions for BSM Guide:

247 In this example, the situation name is MQSeries_QueueIsActie and is set up to fire when the QMgr Status attribute of a queue manager is equal to Actie. In reality, a situation is triggered for a queue manager being Inactie, rather than Actie. For demonstration purposes, the example shows an easy demonstration of the eent flow configuration. 2. Configure the distribution for the situation. The distribution for the situation is configured to include the queue managers to send the eents. In this example, both BK6 and BK7 queue managers are selected. Figure 28. Configuring the distribution for the situation 3. Configure the situation to forward eents to the EIF probe. The eents are configured to be forwarded to the EIF probe in the EIF tab. This example shows that the situation eents are forwarded to the EIF probe running on host nc , as well as the default EIF host. Figure 29. Configuring the situation to forward eents to the EIF probe For Tioli Monitoring to list the EIF eent destination host, you can use the tacmd createeentdest command-line command on the Tioli Enterprise Monitoring Serer serer. Details of this procedure can be found at: %2Fcom.ibm.itm.doc_6.2.3%2Fitm623_cmdref30.htm You do not need to customize the EIF Slot Customization for this example. Since WebSphere MQ situation eents by default hae the fields required to populate the BSM_Identity field in the eent. The important field is the ManagedSystemName which is passed in the $situation_origin field to the probe. Chapter 9. Customizing the solutions 235

248 Configuring the EIF probe to forward WebSphere MQ Eents: Setting BSM_Identity Complete the following steps to configure the EIF probe to send WebSphere MQ eents to Netcool/OMNIbus. Procedure 1. Copy the kmq_tbsm.rules file into the omnibus/probes/<arch> directory in the Netcool/OMNIbus installation where the EIF probe is running. 2. Edit the tioli_eif.rules file in that directory uncomment the following line: "include kmq_tbsm.rules 3. Restart the EIF probe. Stop the existing probe process and restart it using OMNIHOME/probes/nco_p_tioli_eif. The kmq_tbsm.rules file sets the BSM_Identity field in Netcool/OMNIbus so that it matches with the eent identifiers configured for the WebSphere MQ resources that get imported into TBSM. This way TBSM can match the eent to the resource using the BSM_Identity in the eent. Figure 30. Setting the BSM_Identity fields The kmq_tbsm.rules file sets the BSM_Identity field to be in the form <managed system name>:mqqueuemanager:<queue manager name>. The same format is used in the third eent identification field shown here for a Queue Manager resource that was imported into TBSM. The rules for creating the different eent identification fields for the resources are configured in the EentIdentifierRules.xml file, in the Discoery Library Toolkit. In general, when configuring an eent flow from an agent to TBSM, you must ensure that the rules file for the agent is included by the tioli_eif.rules file. The rules file must also set the BSM_Identity field to a alue that is configured as an eent identifier in the resources that get imported into TBSM set by the EentIdentifierRules.xml file in the Discoery Library Toolkit. Additionally, all the eent fields that are assigned in the rules file for the agent must exist in Netcool/OMNIbus. For the WebSphere MQ agent rules file, no new fields are set. If the rules file sets a field that does not exist in Netcool/OMNIbus, the schema in Netcool/OMNIbus must be changed to include this field. Once the situations and eent forwarding are configured and the resources are imported into TBSM, the eents start affecting the resources in TBSM without any additional configuration in TBSM. Metric data flow from Tioli Monitoring to TBSM You can bring any metric data for resources in Tioli Monitoring into the corresponding resources in the TBSM model. The steps inoled are: 1. Create a query in Tioli Monitoring to proide the data needed if such a query does not exist in the support package for the agent. 236 Solutions for BSM Guide:

249 2. Create an Tioli Monitoring data fetcher in TBSM to use the Tioli Monitoring query as its data feed 3. Create an Incoming Status Rule in TBSM to use the data fetcher from the preious step. Creating a query in Tioli Monitoring Create a query in IBM Tioli Monitoring with the Query Editor. Procedure 1. Create a query in Tioli Monitoring from the Query Editor. Accessed from the Edit option in the top menu. 2. In the Query Editor, scroll down to the agent type that corresponds to the agent you want to configure, MQSeries in this case. Under the agent type, right click the metric group to be used, and create a query panel on the right side of the screen. Figure 31. Configure the Name, Description, Category, and Data Source for the Query. 3. You are prompted to assign an attribute group for the query, choose Managers, to get metric data for the MQ Queue Managers. 4. Configure the Origin Node as an Attribute Item. Click OK. Chapter 9. Customizing the solutions 237

250 Figure 32. Assigning an attribute group to the query 5. The query shows under the selected attribute group in the naigation. Edit the query and assign all the metrics you want to be passed in to TBSM. Select #Of Queues, Inactie Channels, and QMgr Name. 6. Assign the Origin Node to == $NODE$ so the managed system name is sent through for TBSM to map to the BSM_Identity of the resource. 238 Solutions for BSM Guide:

251 Figure 33. Assigning the Origin Node to the query What to do next Once you hae saed the query, the next step is to create a data fetcher in TBSM to pull data from the query. Creating a data fetcher to pull metric data from Tioli Monitoring Procedure 1. In the TBSM Serice Administration iew, select Data Fetcher from the menu in the naigation tree and click the New icon to create a new data fetcher. Figure 34. Serice Naigation Data Fetcher 2. Assign the Date Fetcher Name and Type. In this example MQ-InactieChannels and ITM Policy. 3. Assign interal period for queries to run between TBSM and IBM Tioli Monitoring. 4. Configure the connectiity information to the IBM Tioli Monitoring query. a. Select the Serice TIPWebSericeHttpRouter. b. Add the Serice Name, Protocol, Host Name, Port Number, User id, and Password of the Tioli Enterprise Portal. 5. Click the Test Web Serice Connection to populate the Agent Id menu with the list of agent types. Chapter 9. Customizing the solutions 239

252 Figure 35. Creating a data fetcher 6. Select Agent and Query. a. When you select an agent type MQSERIES in this example, the Agent Query menu is populated with all the aailable queries for that agent type. The custom created queries hae cryptic names, for example none UDQ..., so if you hae only created one or two custom queries it is easy to identify them in the menu. Tip: To determine the query ID for your IBM Tioli Monitoring custom query, execute the follow SQL statement on your Tioli Enterprise Portal database: Select ID, NAME, TEXT FROM teps.kfwquery Where NAME ="query-name>" b. Once you select a custom query, you can iew the fields returned in the query in the Query Meta Data tab. c. Click the Query Data tab to show the actual rows returned. This is the data that is passed into the TADDM model when the data fetcher runs. 7. Edit policy and sae data fetcher. 240 Solutions for BSM Guide:

253 a. Click Edit policy to show the policy that the data fetcher uses. b. Edit the policy, and sae it as part of saing the data fetcher definition. c. Sae the data fetcher and it is ready to be assigned to an Incoming Status Rule. Create Incoming Status Rule to receie data from the data fetcher About this task To bring the WebSphere MQ metric data to the QueueManager resources in TBSM, an incoming status rule is configured on the BSMAccelerator_MQMetrics template. For information about how to create the template, see Creating templates and rules in TBSM for WebSphere MQ resources on page 224. The data feed of the incoming status rule is the data fetcher that queries IBM Tioli Monitoring for the required metric data for the queue managers. Figure 36. Incoming status rule to receie data from the data fetcher In the incoming status rule, the data feed is the MQ-InactieChannels data fetcher you configured. Procedure 1. Select BSM_Identity as the field for instance matching. Chapter 9. Customizing the solutions 241

254 2. For the metric expression, select Inactie_Channels which is the field name from IBM Tioli Monitoring that contains the metric data you want. 3. Select the option Store data for this rule for TWA to track this KPI oer time. BSM_Identity resource matching For the rows fetched from IBM Tioli Monitoring to match the resources in TBSM, the eent identifier for the incoming status rule must match the alue in the BSM_Identity field coming in from the data fetcher to IBM Tioli Monitoring. The BSM_Identity field in the row fetched is set by the policy that you edit from the data fetcher. By default, the BSM_Identity field is set to the first field passed in by the IBM Tioli Monitoring query in this example, OriginNode. For WebSphere MQ resources, the OriginNode field is set by IBM Tioli Monitoring to the ManagedSystemName field and the ManagedSystemName also comes in from the discoery library adapter through TADDM into TBSM. The fields are configured by the discoery library adapter as an eent identifier for the incoming status rules of the resource. The following image shows the three eent identifier alues that are assigned by the discoery library adapter to the incoming status rules of the queue managers. The alue circled is the alue of the Managed System Name. This is the same alue that the IBM Tioli Monitoring query assigns to the OrginName field so the row returned by the data fetcher matches the resource in TBSM. 242 Solutions for BSM Guide:

255 Figure 37. Resource matching If you are haing trouble getting IBM Tioli Monitoring query rows mapped to a serice, you can debug it. To debug, you look at the data fetcher definition in the Serice Editor. Look at the Query Data tab, which shows the BSM_Identity field as assigned by the data fetcher policy. Custom Serice Model scenario This scenario describes bringing a serice model from a non-ibm source, in this case a fictitious third party network discoery tool. In general, third party data can be brought into the TBSM model in a number of ways, for example through ESDA and radshell. To transform the model data into the technology type you need to use the Business Serice Composer IdML books, and the discoery library toolkit. The resource data is imported through either an IdML book or by using the SCR API. This scenario describes how to do so with an IdML book. The Serice Component Registry API approach is a parallel approach, and is described in the TBSM documentation. The approach taken here goes through the following steps: Create an IdML book from the data model. The book must include the resources and relationships to import to TBSM. Chapter 9. Customizing the solutions 243

256 Configure the OtherNamespaces.xml file to contain the resource types in the IdML book. Create templates in TBSM to correspond to the resources types to be imported. Configure the CDM_TO_TBSMx_MAP_Templates.xml file to map the resource types from the IdML book to templates in TBSM. Configure an eentidentifierrules xml file to ensure appropriate alues for BSM_Identity are assigned for the resources being imported. This is necessary to get eents to match the imported resources. Configure the Business Serice Composer to create a technology type from the imported resources Load the IdML book into TBSM. The following scenario imports a simple network topology model with VPNs, Routers, Switches, and Serers. The topology model represented by the book is displayed here. Figure 38. Simple network topology model Integrating Custom Namespace Resources into the Serice Model Customizing the IdML book The following example shows the IdML book used for the import. 1. Add to the section before the BEGINNING OF CONTENT comment to any custom IdML book. 244 Solutions for BSM Guide:

257 2. Append the section after the END OF CONTENT comment to any custom IdML book. <?xml ersion="1.0" encoding="utf-8"?> <idml:idml xmlns:idml=" xmlns:cdm=" xmlns:tbsm=" xmlns:my=" xmlns:xsi=" xsi:schemalocation=" idml.xsd"> <!-- NOTE THIS IDML BOOK DOES NOT FOLLOW STANDARD IDML CONVENTION ITS CONTENTS ARE SUPPORTED ONLY WITH TBSM 4.2 PLUS ENHANCEMENTS --> <!-- Source and Software... --> <idml:source IdMLSchemaVersion="0.8"> <cdm:process.managementsoftwaresystem CDMSchemaVersion="2.7"> <cdm:mssname>ibm-cdm:///cdmmss/manufacturername=anycustomer+productname= AnyProductName</cdm:MSSName> </cdm:process.managementsoftwaresystem> </idml:source> <!-- Operation... --> <idml:operationset opid="1"> <idml:refresh> <idml:create> <cdm:cdm-er-specification> <!-- BEGINNING OF CONTENT --> <my:router id= RouterA > <tbsm:restype>router</tbsm:restype> <tbsm:label>routera: Cisco 3845</tbsm:Label> <my:identity>routera</my:identity> <tbsm:attr1> </tbsm:attr1> </my:router> <my:router id= Router1 > <tbsm:restype>router</tbsm:restype> <tbsm:label>router1: Cisco 3845</tbsm:Label> <my:identity>router1</my:identity> <tbsm:attr1> </tbsm:attr1> </my:router> <my:router id= Router2 > <tbsm:restype>router</tbsm:restype> <tbsm:label>router2: Cisco 3845</tbsm:Label> <my:identity>router2</my:identity> <tbsm:attr1> </tbsm:attr1> </my:router> <my:lan id= VLAN1 > <tbsm:restype>vlan</tbsm:restype> <tbsm:label>vlan1</tbsm:label> <my:identity>vlan1</my:identity> <tbsm:attr1> </tbsm:attr1> </my:lan> <my:lan id= VLAN2 > <tbsm:restype>vlan</tbsm:restype> <tbsm:label>vlan2</tbsm:label> <my:identity>vlan2</my:identity> Chapter 9. Customizing the solutions 245

258 <tbsm:attr1> </tbsm:attr1> </my:lan> <my:switch id= Switch1 > <tbsm:restype>switch</tbsm:restype> <tbsm:label>switch1: Cisco (24 Port)</tbsm:Label> <my:identity>switch1</my:identity> <tbsm:attr1> </tbsm:attr1> </my:switch> <my:switch id= Switch2 > <tbsm:restype>switch</tbsm:restype> <tbsm:label>switch2: Cisco 3560</tbsm:Label> <my:identity>switch2</my:identity> <tbsm:attr1> </tbsm:attr1> </my:switch> <my:switch id= Switch3 > <tbsm:restype>switch</tbsm:restype> <tbsm:label>switch3: Cisco 3560</tbsm:Label> <my:identity>switch3</my:identity> <tbsm:attr1> </tbsm:attr1> </my:switch> <my:switch id= Switch4 > <tbsm:restype>switch</tbsm:restype> <tbsm:label>switch4: Cisco 2950 (24 Port)</tbsm:Label> <my:identity>switch4</my:identity> <tbsm:attr1> </tbsm:attr1> </my:switch> <my:switch id= Switch5 > <tbsm:restype>switch</tbsm:restype> <tbsm:label>switch5: Cisco 2950 (24 Port)</tbsm:Label> <my:identity>switch5</my:identity> <tbsm:attr1> </tbsm:attr1> </my:switch> <my:serer id= Serer1 > <tbsm:restype>linux Serer</tbsm:resType> <tbsm:label>serer1</tbsm:label> <my:identity>serer1</my:identity> <tbsm:attr1> </tbsm:attr1> </my:serer> <my:serer id= Serer2 > <tbsm:restype>linux Serer</tbsm:resType> <tbsm:label>serer2</tbsm:label> <my:identity>serer2</my:identity> <tbsm:attr1> </tbsm:attr1> </my:serer> <my:serer id= Serer3 > <tbsm:restype>linux Serer</tbsm:resType> <tbsm:label>serer3</tbsm:label> <my:identity>serer3</my:identity> <tbsm:attr1> </tbsm:attr1> </my:serer> <my:serer id= Serer4 > <tbsm:restype>windows Serer</tbsm:resType> <tbsm:label>serer4</tbsm:label> <my:identity>serer4</my:identity> <tbsm:attr1> </tbsm:attr1> </my:serer> 246 Solutions for BSM Guide:

259 <my:serer id= Serer5 > <tbsm:restype>windows Serer</tbsm:resType> <tbsm:label>serer5</tbsm:label> <my:identity>serer5</my:identity> <tbsm:attr1> </tbsm:attr1> </my:serer> <cdm:app.application id= myapp > <cdm:name>inentory Application</cdm:Name> </cdm:app.application> <!-- relationships that link lans, routers, switches, serers --> <! first assign the VLAN resources as children of the Inentory Application serice that was imported from TADDM --> <tbsm:uses source= myapp target= VLAN1 /> <tbsm:uses source= myapp target= VLAN1 /> <tbsm:uses source= RouterA target= Router1 /> <tbsm:uses source= RouterA target= Router2 /> <tbsm:uses source= VLAN1 target= Router1 /> <tbsm:uses source= VLAN2 target= Router2 /> <tbsm:uses source= Router1 target= Switch1 /> <tbsm:uses source= Router1 target= Switch2 /> <tbsm:uses source= Router2 target= Switch3 /> <tbsm:uses source= Router2 target= Switch4 /> <tbsm:uses source= Switch1 target= Switch5 /> <tbsm:uses source= Switch1 target= Serer1 /> <tbsm:uses source= Switch1 target= Serer2 /> <tbsm:uses source= Switch5 target= Serer3 /> <tbsm:uses source= Switch4 target= Serer4 /> <tbsm:uses source= Switch4 target= Serer5 /> <!-- END OF CONTENT --> </cdm:cdm-er-specification> </idml:create> </idml:refresh> </idml:operationset> </idml:idml> The two main configuration entities in the xml file are the resource definitions and the relationship definitions. A resource definition is similar to the following example: <my:router id= Router2 > <tbsm:restype>router</tbsm:restype> <tbsm:label>router2: Cisco 3845</tbsm:Label> <my:identity>router2</my:identity> <tbsm:attr1> </tbsm:attr1> </my:router> The my:router entity name is what TBSM uses as the class of the resource. The my:router entity name is mapped to a defined set of templates in TBSM.my:router is referred to as a custom namespace element since it is not part of the IBM cdm (common data model) set of classes. All custom namespace elements need to be configured in the OtherNamespaces.xml file. The id attribute, Router2 is not imported to TBSM, but it needs to be uniquely assigned in the IdML book, as this is how other elements in the book refer to this element. The tbsm:label element Router2: Cisco 3845 is the field TBSM uses to configure the display name of the serice in TBSM. Chapter 9. Customizing the solutions 247

260 The my:identity element Router2 is what TBSM uses to uniquely identify this element. my:identity is not a cdm attribute, so it also needs to be configured in the OtherNamespaces.xml. See Configuring OtherNamespaces.xml. The tbsm:restype and tbsm:attr1 elements are not used for anything in this example. They demonstrate that other resource information can be assigned to the resources, and they can be pulled into TBSM as additional properties through custom configuration of the toolkit. The dependency definitions are represented as simple xml entries as follows: <tbsm:uses source= Router2 target= Switch3 /> This entry instructs for the element whose id is Router2 to depend on that whose id is Switch3. One other resource to note in the IdML book is the cdm:app.application entry: <cdm:app.application id= myapp > <cdm:name>inentory Application</cdm:Name> </cdm:app.application> This entry represents the Business Application named Inentory Application that we created and imported from TADDM. The IdML book references this resource through the cdm:name attribute, which matches the cdm:name attribute of the resource from TADDM and assigns the VLAN resources as children of the Inentory Application. This is necessary to assign network resources from the book into a technology type, since the resource to type assignment only occurs when the resources lie under a Business Serice or Application. The same configuration applies when the Inentory Application does not come from TADDM. TBSM creates the serice rather than "reconciles" it with the serice imported from TBSM. Configuring OtherNamespaces.xml About this task For each type of resource that is being imported from the custom IdML book, an entry must be created in the OtherNamespaces.xml file. The OtherNamespaces.xml is obtained through the getartifact file utility in the XMLToolkit/bin directory. Procedure 1. Run the command: getartifact U <db2user> -P <db2password> -d <directory to write the file to> -n OtherNamespaces.xml c scrconfig 2. Edit the OtherNamespaces.xml file you exported and add the following lines just aboe the </document> tag at the end of the file. <NameSpaceDefinition classname= my:router identityattribute= my:identity /> <NameSpaceDefinition classname= my:switch identityattribute= my:identity /> <NameSpaceDefinition classname= my:lan identityattribute= my:identity /> <NameSpaceDefinition classname= my:serer identityattribute= my:identity /> 248 Solutions for BSM Guide:

261 These entries proide the discoery library toolkit the custom resource types that exist in the IdML book, my:router, my:switch, my:lan, my:serer and it also specifies that the my:identity attribute is used for each of these class types to uniquely identify the resource. 3. Import the file to the database through the putartifactfile utility: putartifact U <db2user> -P <db2password> -n <path to file to import> -c scrconfig Configuring CDM_TO_TBSM4x_MAP_Templates.xml About this task Configure the template mapping to indicate to the discoery library toolkit which templates to assign to the different resource types that it imports. Procedure 1. Get a copy of the existing file from the database using the following command: XMLToolkit/bin/getArtifact U <db2user> -P <db2password> -d <directory to write file to> -n CDM_TO_TBSM4x_MAP_Templates.xml c scrconfig. The default TBSM template model already contains templates called BSM_Switch and BSM_Router. The CDM_TO_TBSM4x_MAP_Templates.xml file automatically assigns these templates to resource elements with the cdm class cdm:sys.genericswitch and cdm:sys.genericrouter respectiely. 2. Add an additional entry for the BSM_Router and BSM_Switch templates to map resources of class my:router to the BSM_Router template and resources of the class my:switch to the BSM_Switch template. 3. Add an entry to assign resources of class my:lan to the BSM_VLAN template. 4. Assign the additional templates SCR_RetrieeDependentObjectsTemplate, SCR_SericeComponentRawStatusTemplate, BSM_NetworkSerice, and BSMAccelerator_EentCount templates to the router, switch, lan, and serer resources imported from the custom IdML book. <template primary= BSM_Router > <othertemplate name= SCR_RetrieeDependentObjectsTemplate /> <othertemplate name= SCR_SericeComponentRawStatusTemplate /> <othertemplate name= BSM_NetworkSerice /> <othertemplate name="bsmaccelerator_eentcount" /> <cdmclass name= tbsm:net.router /> <cdmclass name= cdm:sys.genericrouter /> <cdmclass name= my:router /> </template> <template primary= BSM_Switch > <othertemplate name= SCR_RetrieeDependentObjectsTemplate /> <othertemplate name= SCR_SericeComponentRawStatusTemplate /> <othertemplate name= BSM_NetworkSerice /> <othertemplate name="bsmaccelerator_eentcount" /> <cdmclass name= tbsm:net.switch /> <cdmclass name= cdm:sys.genericswitch /> <cdmclass name= my:switch /> </template> <template primary= BSM_VLAN > <othertemplate name= SCR_RetrieeDependentObjectsTemplate /> <othertemplate name= SCR_SericeComponentRawStatusTemplate /> <othertemplate name= BSM_NetworkSerice /> <othertemplate name="bsmaccelerator_eentcount" /> Chapter 9. Customizing the solutions 249

262 <cdmclass name= my:lan /> </template> 5. You can also map the my:serer resource type used by our IdML to the existing BSM_Node template using the following example. Note that only the bottom entry in this xml segment is added for this scenario. The rest of the segment is there by default. <template primary="bsm_node"> <othertemplate name="scr_retrieedependentobjectstemplate"/> <othertemplate name="scr_sericecomponentrawstatustemplate"/> <othertemplate name="bsmaccelerator_eentcount"/> <cdmclass name="my:serer"/> </template> <othertemplate name="bsmaccelerator_eentcount" /> <cdmclass name= cdm:sys.computersystem /> <cdmclass name= cdm:sys.genericcomputersystem /> <cdmclass name= cdm:sys.unitarycomputersystem /> <cdmclass name= cdm:sys.aix.aixunitarycomputersystem /> <cdmclass name= cdm:sys.cisco.ciscopixcomputersystem /> <cdmclass name= cdm:sys.freebsd.freebsdunitarycomputersystem /> <cdmclass name= cdm:sys.hpux.hpuxunitarycomputersystem /> <cdmclass name= cdm:sys.ipso.ipsounitarycomputersystem /> <cdmclass name= cdm:sys.linux.linuxunitarycomputersystem /> <cdmclass name= cdm:sys.netware.netwareunitarycomputersystem /> <cdmclass name= cdm:sys.openms.openvmsunitarycomputersystem /> <cdmclass name= cdm:sys.sun.sunsparcunitarycomputersystem /> <cdmclass name= cdm:sys.sun.sunsparcvirtualcomputersystem /> <cdmclass name= cdm:sys.mware.vmwareunitarycomputersystem /> <cdmclass name= cdm:sys.windows.windowscomputersystem /> <cdmclass name= cdm:sys.systempcomputersystem /> <cdmclass name= cdm:sys.zos.zvm /> <cdmclass name= cdm:sys.zos.zlinux /> <cdmclass name= cdm:sys.zos.zos /> <cdmclass name= cdm:sys.zos.zvmguest /> <cdmclass name= my:serer /> </template> 6. After adding the lines to the file, you must import the template mapping file to the database through the putartifactusing the following command: putartifact U <db2user> -P <db2password> -n <path to file to import> -c scrconfig 7. The default TBSM templates do not contain a template for VLANs, create a template in TBSM called BSM_VLAN and create a dependency rule from BSM_NetworkTemplates template to BSM_VLAN. 250 Solutions for BSM Guide:

263 Figure 39. BSM_VLAN Template 8. Create the dependency rule by editing the BSM_NetworkTemplates template and creating a worst case rule as follows. In this example, this rule is purely to put the BSM_VLAN template in an appropriate place in the template hierarchy. There are no instances of the parent template BSM_NetworkTemplates that to be created, so no status propagates due to this rule. Chapter 9. Customizing the solutions 251

264 Figure 40. Creating the dependency rule Configuring Eent Identifier configuration file You must edit the eent identification configuration file in the discoery library toolkit file before the book can be imported to assign the appropriate eent identification alues for the imported TBSM resources. Then, the BSM_Identity alues in incoming eents match the appropriate resources in TBSM. Procedure 1. Configure a new eent identifier configuration file, rather than using the default one. This example creates and configures a file called MyIdentifierRules.xml. The line <Mapping policy="myidentitybase" class="%" /> specifies that resources belonging to all classes the % wildcard hae the myidentitybase policy associated with them. In this example, the myidentitybase policy, assigns the my:identity attribute of the resource as defined in the NetworkTopology.xml IdML book as the alue of the eent identifiers for the resource in TBSM. When the BSM_Identity field in the incoming eent equals the my:identity attribute of the resource in the IdML book, the eent affects the resource in TBSM. Example: <?xml ersion="1.0" encoding="utf-8"?> <!-- **********************************************{COPYRIGHT-TOP-RM} Licensed Materials - Property of IBM Restricted Materials of IBM 5724-C51 (C) Copyright IBM Corp. 1999,2011 All Rights Resered. US Goernment Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ***************************************************{COPYRIGHT-END-RM} Module Description 252 Solutions for BSM Guide:

265 - Contains rules for creating TBSM Identifiers for common data model instances --> <EentIdentifierRules ersion="1.0.0"> <Policy name="myidentitybase" useassin= true > <Rule name="networkidentity"> <Token keyword="attr" alue="my:identity"/> </Rule> </Policy> <Mapping policy="myidentitybase" class="%" /> </EentIdentifierRules> 2. To upload the file to the discoery library toolkit, us the following command: XMLToolkit/bin/putArtifact U <db2user> -P <db2password> -n <path to MyIdentifiers.xml> -c eentidentifiers Loading the IdML Book Procedure 1. To load the IdML book, run the following command: <tbsm_installdir>/xmltoolkit/bin/utils.sh e reload_cdm_definitions.xml 2. Copy the NetworkTopology.xml into the TBSM_INSTALL/tbsm/discoery/dlbooks directory and the discoery library toolkit identifies and loads IdML book. Creating templates and rules in TBSM for custom namespace network resources About this task The next step is to create templates and rules in TBSM to incorporate the imported network resources into the Solutions for BSM structure. Procedure 1. Create a template called BSMAccelerator_NetworkGroup. This template is assigned the network technology type serices that will be created. 2. Create the DirectEentEentStatus dependency rule. Create a Numeric Dependency Rule: Chapter 9. Customizing the solutions 253

266 Figure 41. Creating a dependency rule for the BSMAccelerator_NetworkGroup template a. Call the rule DirectChildEentStatus. b. Set the dependency as a Maximum Dependency Rule that depends on the ComponentRawEentStatusRule of the SCR_SericeComponentRawStatusTemplate template. This rule enables the Network technology type serice to hae its status affected only from children that hae eents directly affecting them. 254 Solutions for BSM Guide: Figure 42. Setting a maximum dependency rule 3. Create BSMAccelerator_NetworkGroup rule on BSMAccelerator_SericeApplication template. a. Add the following properties to the BSMAccelerator_NetworkGroup template:

267 DoFunctionEnrichment true DynamicEentCountRollUpLeel leaf b. Configure the Output Expressions for the BSMAccelerator_NetworkGroup template. 1) The Bad expression: DirectChildEentStatus.Value >=5. 2) The Marginal expression: DirectChildEentStatus.Value >=3. 4. The next step is to create a dependency worst case rule on the BSMAccelerator_SericeApplication template that depends on the BSMAccelerator_NetworkGroup template. The rule enables the status to propagate from the MQ technology type serice to the business application it depends on. Figure 43. Dependency worst case rule 5. Edit the policy in the SericeAailability Rule. a. On the BSMAccelerator_SericeApplication template, edit the SericeAailability Rule and click Edit Policy. b. Scroll towards the bottom of the policy and look for the line containing the BSMAccelerator grouping templates. Add the BSMAccelerator_NetworkGroup template to this code (see green text below) and sae the policy: if ((InstanceNode.BSMAccelerator_SerersGroup.Value > 0) or (InstanceNode.BSMAccelerator_TransactionsGroup.Value > 0) or (InstanceNode.BSMAccelerator_AppSerersGroup.Value >0)or (InstanceNode.BSMAccelerator_WebSerersGroup.Value > 0) or (InstanceNode.BSMAccelerator_DBGroup.Value > 0) or (InstanceNode.BSMAccelerator_VirtualEnironmentsGroup.Value > 0) or (InstanceNode.BSMAccelerator_ClientsGroup.Value > 0) or (InstanceNode.BSMAccelerator_NetworkGroup.Value > 0) ) c. The SericeVisibility rule ensures that only technology types with non-green status appear underneath a business application in the Serice Health iew. Chapter 9. Customizing the solutions 255

268 Configuring the Business Serice Composer for custom namespace resources About this task The procedure for configuring the Business Serice Composer to create technology types for the network resources is similar to that done for the WebSphere MQ resources. The following example shows how to configure the Business Serice Composer to assign all router and switch resources that are dependents of a business application grouped together under a network technology type for the business application. Procedure 1. To assign the switch resources to the technology type add the following row in the composer: Figure 44. Input alues for new row Figure 45. Complete new row: my:switch 2. In the Selection Class, select cdm:app.application to indicate you want to create the technology type for any Business Application resource. 3. For Selection Patten, select %, so that any Business Application technology type is created. 4. Configure the Category Identifier and Category Label as Network, to name the technology type Network. 5. Configure the Technology Group Class as my:switch, which is the custom namespace resource identifier used to describe Switches in the IdML book. 6. Similarly you can create identical rows where the Selection Class is cdm:core.collection and cdm:sys.businesssystem respectiely to create network technology types under Collection and BusinessSystem resources. 7. To add an additional resource types grouped under the same technology type, add a new row to the Business Serice Composer, with the class of the resource type you can include router resources under the network technology type by adding the following line: Figure 46. Input alues for new row Figure 47. Complete new row: my:router 256 Solutions for BSM Guide:

269 Configure CDM_TO_TBSM4x_MAP_Template.xml for network technology type templates This configuration assigns the template BSMAccelerator_NetworkGroup as the primary template of the technology type resources that are created from the Business Serice Composer. It assigns the additional templates SCR_RetrieeDepedentObjectsTemplate and BSMAccelerator_EentCount template. About this task Assign the Network technology type serices to the BSM_NetworkGroup template you hae configured using the CDM_TO_TBSM4x_MAP_Templates.xml file. Procedure 1. Get the current copy of the file from the database, using the following command: <tbsm_installdir>/tbsm/xmltoolkit/bin/getartifact U <dbuser> -P <dbpass> -d <directory to write file to> -n CDM_TO_TBSM4x_MAP_Templates.xml c scrconfig. 2. Edit that file and add the following section to the bottom of the file: <!-- Assign BSMAccelerator_NetworkGroup template to all Network grouping objects --> <Policy name="networkgrouptemplateassignment"> <Rule name="networkgrouptemplates"> <condition attrkeyword="tbsm:label" operator="=" alue= Network"/> </Rule> <template primary="bsmaccelerator_networkgroup"> <othertemplate name="scr_retrieedependentobjectstemplate" /> <!-- Added for BSMAccelerator Eent Count Metric --> <othertemplate name="bsmaccelerator_eentcount" /> </template> </Policy> <Mapping policy="networkgrouptemplateassignment" class="tbsm:technologygroup"/> 3. Add the file to the database using the following command: <tbsm_installdir>/tbsm/xmltoolkit/bin/putartifact.sh U <dbuser> -P <password> -n <path to CDM_TO_TBSM4x_MAP_Templates.xml> -c scrconfig Processing the changes to the discoery library toolkit Use the commands to process the changes to the discoery library toolkit to iew the network technology type with the switches and routers that support the business application. About this task Before running the processing for the Discoery Library Toolkit, the ResEnrichReader serice must be running in Netcool/Impact. Once the serice is running you can run the following discoery library toolkit commands to process all the changes in the toolkit. Procedure 1. Log in to the TBSM Console. Chapter 9. Customizing the solutions 257

270 2. In the Naigation area, select System Configuration > Eent Automation > Serices. 3. On the Serices tab, from the Project menu, select Global project to iew a list of all the serices. 4. View the ResEnrichReader serice, if the icon is red, right click the serice and select Edit. 5. Select the Startup check box next to Automatically when serer starts so that the serice starts automatically when the serer starts. Click Sae. 6. In the Serices tab, Select the serice and select Start Serice from the menu to run the serice. 7. Once the serice is running, you can run the following commands on the Discoery Library Toolkit. Run the following command to update the discoery library toolkit with the changes made to the CDM_TO_TBSM4x_MAP_Templates.xml. <tbsm_installdir>/tbsm/xmltoolkit/bin/utils.sh U <dbuser> -P <dbpassword> -e reload_cdm_definitions.xml 8. Check the msggmt_xt.log file to check when the processing is finished. 9. Run the following command: <tbsm_installdir>/tbsm/xmltoolkit/bin/loadbusinesscomposerdefinitions.sh U <dbuser> -P <dbpassword> -n <tbsm_installhome>/tbsm/xmltoolkit/tools/criewer/projects/ BSMAccelerator_1r0.xml 10. Click the business application Inentory Application to iew the network technology type with the switches and routers that support the application underneath it. 258 Solutions for BSM Guide:

271 Figure 48. Newwork technology type Sending Eents How to send eents to TBSM. About this task Once the model has been imported from the IdML book, you can send eents to TBSM by any means in which IBM Tioli Netcool/OMNIbus can receie eents. The only requirement for eent matching is the BSM_Identity field in the eent must match the my:identity alue that was configured in the IdML book. Procedure 1. You can send an eent using theibm Tioli Netcool/OMNIbus sql command line: 2. Create a sql file: 3. insert into alerts.status (BSM_Identity, Identifier, Seerity, Summary) alues ('Switch5', 'EentForSwith5', 5, 'Switch5 is down'); go 4. Now run cat <sql file> OMNIHOME/bin/nco_sql u root. to add the eent to IBM Tioli Netcool/OMNIbus. If the model is imported already, then TBSM matches the eent to the identifier field in the Switch5 resource and turn that resource red, when in turn propagates red status up the hierarchy. Chapter 9. Customizing the solutions 259

272 Figure 49. Sending eents Third party monitoring product scenario If eents are coming from a third party monitoring product, the eent identifier alue in the resource for the field specified by the instance matching field in the incoming statue rule must match the alue of that field in the eent. If you use the ComponentRawEentStatusRule incoming status rule on the SCR_SericeComponetRawStatus template, the field in the eent to do the matching is the BSM_Identity field. The BSM_Identity field is what is used to match eents to resources for ITM eents and resources imported through discoery library adapters. In this case, the rules file for whateer probe used to send these third party eents to Omnibus must set the BSM_Identity field in the eent to equal one of the alues configured in the identification fields for the resource. If you use the ComponentRawEentStatusRule incoming status rule to match eents from a third party eent source, you also need to ensure that the Class field of the eent is one of the classes selected in the incoming status rule. You can edit the incoming status rule to add the new Class if it is not there. For example, if you are getting eents from the BSM Patrol probe, you must add the Class BMC Patrol(4600) to the list of selected Classes in the incoming status rule. If you create a new Incoming status rule to map the third party eents to your resources, you must configure the Class in the incoming status rule to be the Class assigned to these eents. For the instance matching field, check that the eent identification field for the resource for this field name is set to the alue that will be set in the field in the eent that should be affecting the resource. Without TADDM in the enironment scenario If you do not hae TADDM in the enironment it is still possible to incorporate resources in the technology type model in TBSM. 260 Solutions for BSM Guide:

273 Without TADDM, you must ensure that the IdML used to create the model in TBSM is placed in the directory <TBSM_InstallHome>/discoery/dlbooks. Once an IdML book is placed in that directory, the discoery library toolkit identifies it and imports it into TBSM. Resources that come from a Discoery library adapter For resources in the IdML that are from a discoery library adapter, the approach is similar to the first two scenarios described in the Introduction on page 215. For discoery library adapters that are supported Solutions for BSM, you must create business serices in the IdML and assign relationships between the business serices and the top leel resources in the IdML that support the business serice. For discoery library adapters that are not supported by Solutions for BSM, use an approach similar to Custom Serice Model scenario on page 243. Templates to assign to the resources and the new technology groups must be configured in TBSM, the discoery library toolkit must be configured to assign the templates to the appropriate classes of resources, and the Business Serice Composer must configured to create the required desired technology type for the required types of business serices and resources to assign underneath them. The main additional piece necessary to configure the high leel business serices and their relationships in the IdML. Creating Business Serices and Relationships in IdML When TADDM is not in the enironment, the business serices or applications that contain the technology types must be created in the IdML book. This is simply a question of creating an entry in the book for the business serice and then an entry for each relationship you want to assign as a direct child of the business serice. In the network topology example from Custom Serice Model scenario on page 243, you can create a business serice by adding the following entry into the IdML book: <cdm:app.application id= myapp > <cdm:name>inentory Application</cdm:Name> <cdm:label>inentory Application></cdm:Label> </cdm:app.application> This entry tells the discoery library toolkit to create a resource of class cdm:app.application, whose name will be Inentory Application. You can also choose to set the class to be cdm:sys.businesssystem. In fact, the class can be any cdm class or custom class as long as the custom class is configured in the OtherNamespaces.xml file for custom namespaces. For more information see, Configuring OtherNamespaces.xml on page 248. The one requirement is that in the Business Serice Composer, the alue you configure for the Selection Class must be the name of the class you assign to the business serice resource in the IdML book. If TADDM was in the enironment and a business serice resource was created in TADDM with a name the same as the cdm:name field in the IdML, then the resource in the IdML would be merged with the existing resource from TADDM into a single resource in TBSM. If TADDM is not in the enironment, then TBSMstill imports a business serice resource as specified by the IdML book. In order to assign relationships to the business serice, you add entries in the IdML book, similar to the following: Chapter 9. Customizing the solutions 261

274 <tbsm:uses source= myapp target= VLAN1 /> <tbsm:uses source= myapp target= VLAN2 /> <tbsm:uses source= myapp target= Db2System-db2inst1:w:UD /> For each relationship, the parent (source) resource is identified by its id property, myapp is the id we assigned to the Inentory Application resource. The child (target) resource is identified by the id of the child resource. In the first two examples, the ids are assigned the VLANs in the custom Network topology IdML book. The third example is an id of a db2 serer resource that was obtained from the DLA from the ITCAM for DB2 agent. Resources that do not come from a discoery library adapter For resources that do not come from a discoery library adapter, use the approach outlined in Custom Serice Model scenario on page 243. Assigning the resources underneath business serices in the IdML, as described in section: Creating Business Serices and Relationships in IdML on page 261. Customizing the scorecard for new technology types The Solutions for BSM comes with two custom scorecards. The BSM_Accel_Scorecard and the BSM_Accel_Details_Scorecard. The BSM_Accel_Scorecard shows on the Business Serice Health page. The BSM_Accel_Details_Scorecard shows on the Business Serice Isolation page. About this task The BSM_Accel_Scorecard shows the oerall status of the different technology types for the Business Applications. Figure 50. BSM_Accel_Scorecard Procedure 1. To add columns for the new technology types, bring up the tree template editor from the Serice Naigation: 262 Solutions for BSM Guide:

275 Figure 51. Template Tree editor 2. Select the BSM_Accel_Scorecard from the Tree Template Name list menu. 3. Add columns for the new technology types in this example MQ and Network. Figure 52. Adding columns for the new technology types 4. In the bottom section of the window, click the BSMAccelerator_SericeApplication template and configure rule to map to the MQ column and configure rule to map to the Network column. Figure 53. Configuring rules to map to columns 5. Click OK to sae the changes. 6. The resulting scorecard contains the MQ and Network columns. Chapter 9. Customizing the solutions 263

276 Figure 54. Update scorecard columns An additional customization piece for this scorecard is the GetTreeColumnValue policy that you bring up by clicking on the Edit Policy button at the bottom of the Tree Template configuration screen. The policy checks if the column name is one of the columns configured in the BSM_Accel_Scorecard scorecard. Add the names of your custom columns to this line in the policy and then sae the policy. This policy changes to column alue from a number to a red, yellow, or green status icon. The rules that determine the status of the technology type status are actually numeric rules (for example, the BSMAccelerator_MQGroup rule), that display as numbers by default. In order to display the status in the tree as the red, yellow, and green icons, add the new column name to the tree template policy. In this example, the MQ column is added to the policy. The releant line in the policy is similar to the following example: if (columnname == "BSMAccel_Clients" columnname == "BSMAccel_Transactions" columnname == "BSMAccel_Web_Serer" columnname == "BSMAccel_App_Serer" columnname == "BSMAccel_Serer" columnname == "BSMAccel_VEs" columnname == "BSMAccel_DBs" columnname == "MQ") { 7. The second custom scorecard that ships with the BSM Accelerator is the BSM_Accel_Details_Scorecard. This scorecard is displayed in the Accelerator Isolation page. In order for the scorecard to display the correct status for the resources in the tree, the template of eery resource that appears in the tree must be configured in this scorecard. In this example, you configure the BSM_Accel_Details_Scorecard for the MQ technology type. a. Select BSM_Accel_Details_Scorecard from the Tree Template Name list menu. b. Add the BSMAccelerator_MQGroup to the list of Selected Templates. c. Highlight BSMAccelerator_MQGroup in the Actie Template list. d. In the Aailable Attributes section on the bottom, assign the sericestatusimage to the BSMAceel_Status (or Status) column. When you map this attribute to the column, it enables the status light to show in the serice tree for the MQ_QueueManagers technology type in the Accelerator Isolation page. This must be done for templates for all serices that you want to be able to show status in this portlet. For example, in the Network scenario, add the BSM_Router and BSM_Switch templates to the list of Selected Templates, and configure the columns for each template. 264 Solutions for BSM Guide:

Solutions for BSM 1.1 Expanded Operating System Release. Solutions for BSM Guide

Solutions for BSM 1.1 Expanded Operating System Release. Solutions for BSM Guide Solutions for BSM 1.1 Expanded Operating System Release Solutions for BSM Guide Solutions for BSM 1.1 Expanded Operating System Release Solutions for BSM Guide Note Before using this information and the

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

IBM Tivoli Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1. User s Guide SC

IBM Tivoli Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1. User s Guide SC IBM Tioli Monitoring for Virtual Enironments: Dashboard, Reporting, and Capacity Planning Version 7.1 Fix Pack 1 User s Guide SC14-7493-01 IBM Tioli Monitoring for Virtual Enironments: Dashboard, Reporting,

More information

High Availability Guide for Distributed Systems

High Availability Guide for Distributed Systems IBM Tioli Monitoring Version 6.3.0 High Aailability Guide for Distributed Systems SC22-5455-00 IBM Tioli Monitoring Version 6.3.0 High Aailability Guide for Distributed Systems SC22-5455-00 Note Before

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

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent Fix Pack 13.

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent Fix Pack 13. IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Exchange Serer Agent 6.3.1 Fix Pack 13 Reference IBM IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft

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

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

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

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13.

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13. IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Actie Directory Agent 6.3.1 Fix Pack 13 Reference IBM IBM Tioli Composite Application Manager for Microsoft Applications:

More information

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

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

More information

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

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

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

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

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

Tivoli System Automation Application Manager

Tivoli System Automation Application Manager Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC33-8420-01 Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC33-8420-01

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

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

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

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

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

IBM Tivoli Enterprise Console. User s Guide. Version 3.9 SC IBM Tioli Enterprise Console User s Guide Version 3.9 SC32-1235-00 IBM Tioli Enterprise Console User s Guide Version 3.9 SC32-1235-00 Note Before using this information and the product it supports, read

More information

Business Service Manager Version Scenarios Guide SC

Business Service Manager Version Scenarios Guide SC Business Service Manager Version 6.1.0.1 Scenarios Guide SC23-6043-08 Business Service Manager Version 6.1.0.1 Scenarios Guide SC23-6043-08 Note Before using this information and the product it supports,

More information

Service Configuration Guide

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

More information

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

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

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

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

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

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

Installation and Setup Guide

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

More information

User s Guide - Beta 1 Draft

User s Guide - Beta 1 Draft IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Actie Directory Agent Next User s Guide - Beta 1 Draft SC23-8879-07 IBM Tioli Composite Application Manager for Microsoft

More information

IBM Tealeaf cximpact Version 9 December 4, Tealeaf Reporting Guide

IBM Tealeaf cximpact Version 9 December 4, Tealeaf Reporting Guide IBM Tealeaf cximpact Version 9 December 4, 2014 Tealeaf Reporting Guide Note Before using this information and the product it supports, read the information in Notices on page 175. This edition applies

More information

IBM Campaign Version 9 Release 1 October 25, User's Guide

IBM Campaign Version 9 Release 1 October 25, User's Guide IBM Campaign Version 9 Release 1 October 25, 2013 User's Guide Note Before using this information and the product it supports, read the information in Notices on page 229. This edition applies to ersion

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

Netcool/Impact Version User Interface Guide SC

Netcool/Impact Version User Interface Guide SC Netcool/Impact Version 6.1.0.2 User Interface Guide SC14-7554-00 Netcool/Impact Version 6.1.0.2 User Interface Guide SC14-7554-00 Note Before using this information and the product it supports, read the

More information

IBM Operations Analytics - Predictive Insights Configuration and Administration Guide IBM

IBM Operations Analytics - Predictive Insights Configuration and Administration Guide IBM IBM Operations Analytics - Predictie Insights 1.3.3 Configuration and Administration Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 117.

More information

IBM Tivoli Storage Manager for Virtual Environments Version Data Protection for VMware Installation Guide IBM

IBM Tivoli Storage Manager for Virtual Environments Version Data Protection for VMware Installation Guide IBM IBM Tioli Storage Manager for Virtual Enironments Version 7.1.6 Data Protection for VMware Installation Guide IBM IBM Tioli Storage Manager for Virtual Enironments Version 7.1.6 Data Protection for VMware

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

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

Planning and Installation

Planning and Installation Tioli Workload Scheduler Version 8.5. (Reised October 200) Planning and Installation SC32-273-09 Tioli Workload Scheduler Version 8.5. (Reised October 200) Planning and Installation SC32-273-09 Note Before

More information

Installation and Configuration Guide

Installation and Configuration Guide System Automation Application Manager Version 4.1 Installation and Configuration Guide SC34-2702-00 System Automation Application Manager Version 4.1 Installation and Configuration Guide SC34-2702-00

More information

IBM. Installing. IBM Emptoris Suite. Version

IBM. Installing. IBM Emptoris Suite. Version IBM Emptoris Suite IBM Installing Version 10.1.0 IBM Emptoris Suite IBM Installing Version 10.1.0 ii IBM Emptoris Suite: Installing Copyright Note: Before using this information and the product it supports,

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

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent Fix Pack 10. Troubleshooting Guide IBM

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Exchange Server Agent Fix Pack 10. Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Exchange Serer Agent 6.3.1 Fix Pack 10 Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft Applications:

More information

IBM Marketing Operations and Campaign Version 9 Release 0 January 15, Integration Guide

IBM Marketing Operations and Campaign Version 9 Release 0 January 15, Integration Guide IBM Marketing Operations and Campaign Version 9 Release 0 January 15, 2013 Integration Guide Note Before using this information and the product it supports, read the information in Notices on page 51.

More information

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

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

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

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

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 Marketing Operations and Campaign Version 9 Release 1.1 November 26, Integration Guide

IBM Marketing Operations and Campaign Version 9 Release 1.1 November 26, Integration Guide IBM Marketing Operations and Campaign Version 9 Release 1.1 Noember 26, 2014 Integration Guide Note Before using this information and the product it supports, read the information in Notices on page 55.

More information

IBM Security Access Manager for Web Version 7.0. Installation Guide GC

IBM Security Access Manager for Web Version 7.0. Installation Guide GC IBM Security Access Manager for Web Version 7.0 Installation Guide GC23-6502-02 IBM Security Access Manager for Web Version 7.0 Installation Guide GC23-6502-02 Note Before using this information and the

More information

IBM Spectrum Control Version User's Guide IBM SC

IBM Spectrum Control Version User's Guide IBM SC IBM Spectrum Control Version 5.2.9 User's Guide IBM SC27-6588-01 Note: Before using this information and the product it supports, read the information in Notices on page 359. This edition applies to ersion

More information

Administrator's Guide

Administrator's Guide IBM Tioli Storage Productiity Center Version 5.2.4 Administrator's Guide SC27-4859-03 Note: Before using this information and the product it supports, read the information in Notices on page 285. This

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

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

Installation and User's Guide

Installation and User's Guide IBM Systems Director VMControl Installation and User's Guide Version 2 Release 3 IBM Systems Director VMControl Installation and User's Guide Version 2 Release 3 ii IBM Systems Director VMControl: Installation

More information

Version 10 Release 0 February 28, IBM Campaign User's Guide IBM

Version 10 Release 0 February 28, IBM Campaign User's Guide IBM Version 10 Release 0 February 28, 2017 IBM Campaign User's Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 241. This edition applies to

More information

iplanetwebserveruser sguide

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

More information

IBM Cognos Dynamic Query Analyzer Version Installation and Configuration Guide IBM

IBM Cognos Dynamic Query Analyzer Version Installation and Configuration Guide IBM IBM Cognos Dynamic Query Analyzer Version 11.0.0 Installation and Configuration Guide IBM Product Information This document applies to IBM Cognos Analytics ersion 11.0.0 and may also apply to subsequent

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

Service Configuration Guide

Service Configuration Guide Business Service Manager Version 6.1.1 Service Configuration Guide SC23-6041-09 Business Service Manager Version 6.1.1 Service Configuration Guide SC23-6041-09 Note Before using this information and the

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

IBM. IBM i2 Analyze: Backing Up A Deployment. Version 4 Release 1

IBM. IBM i2 Analyze: Backing Up A Deployment. Version 4 Release 1 IBM IBM i2 Analyze: Backing Up A Deployment Version 4 Release 1 Note Before using this information and the product it supports, read the information in Notices on page 11. This edition applies to ersion

More information

Version 10 Release 0 February IBM Marketing Platform Installation Guide IBM

Version 10 Release 0 February IBM Marketing Platform Installation Guide IBM Version 10 Release 0 February 2017 IBM Marketing Platform Installation Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 69. This edition

More information

IBM Systems Director for Windows Planning, Installation, and Configuration Guide

IBM Systems Director for Windows Planning, Installation, and Configuration Guide IBM Systems Director IBM Systems Director for Windows Planning, Installation, and Configuration Guide Version 6.2.1 GI11-8711-06 IBM Systems Director IBM Systems Director for Windows Planning, Installation,

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

IBM Unica Distributed Marketing Version 8 Release 6 May 25, Field Marketer's Guide

IBM Unica Distributed Marketing Version 8 Release 6 May 25, Field Marketer's Guide IBM Unica Distributed Marketing Version 8 Release 6 May 25, 2012 Field Marketer's Guide Note Before using this information and the product it supports, read the information in Notices on page 83. This

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 Security Identity Manager Version 6.0. Installation Guide GC

IBM Security Identity Manager Version 6.0. Installation Guide GC IBM Security Identity Manager Version 6.0 Installation Guide GC14-7695-00 IBM Security Identity Manager Version 6.0 Installation Guide GC14-7695-00 Note Before using this information and the product it

More information

IBM Security Access Manager for Web Version 7.0. Upgrade Guide SC

IBM Security Access Manager for Web Version 7.0. Upgrade Guide SC IBM Security Access Manager for Web Version 7.0 Upgrade Guide SC23-6503-02 IBM Security Access Manager for Web Version 7.0 Upgrade Guide SC23-6503-02 Note Before using this information and the product

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

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

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

ComposerGuideforFlexDevelopment

ComposerGuideforFlexDevelopment IBM Initiate Master Data Serice ComposerGuideforFlexDeelopment Version9Release7 GI13-2154-00 IBM Initiate Master Data Serice ComposerGuideforFlexDeelopment Version9Release7 GI13-2154-00 Note Before using

More information

IBM. Troubleshooting Guide

IBM. Troubleshooting Guide IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Host Integration Serer Agent 6.3.1 Fix Pack 13 Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft

More information

Warehouse Summarization and Pruning Agent Version Fix Pack 1. User's Guide SC

Warehouse Summarization and Pruning Agent Version Fix Pack 1. User's Guide SC Warehouse Summarization and Pruning Agent Version 6.2.3 Fix Pack 1 User's Guide SC23-9767-02 Warehouse Summarization and Pruning Agent Version 6.2.3 Fix Pack 1 User's Guide SC23-9767-02 Note Before using

More information

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13. Troubleshooting Guide IBM

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Active Directory Agent Fix Pack 13. Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Actie Directory Agent 6.3.1 Fix Pack 13 Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft Applications:

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

Netcool Configuration Manager Version Installation and Configuration Guide R2E6 IBM

Netcool Configuration Manager Version Installation and Configuration Guide R2E6 IBM Netcool Configuration Manager Version 6.4.1 Installation and Configuration Guide R2E6 IBM Netcool Configuration Manager Version 6.4.1 Installation and Configuration Guide R2E6 IBM Note Before using this

More information

Product Overview Guide

Product Overview Guide IBM Security Identity Manager Version 6.0 Product Oeriew Guide GC14-7692-00 IBM Security Identity Manager Version 6.0 Product Oeriew Guide GC14-7692-00 Note Before using this information and the product

More information

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Lync Server Agent Version Fix Pack 13. Troubleshooting Guide IBM

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Lync Server Agent Version Fix Pack 13. Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft Applications: Microsoft Lync Serer Agent Version 6.3.1 Fix Pack 13 Troubleshooting Guide IBM IBM Tioli Composite Application Manager for Microsoft

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

IBM. Connecting to IBM i IBM i Access for Web. IBM i 7.1

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

More information

IBM Interact Version 9 Release 0 May 31, User's Guide

IBM Interact Version 9 Release 0 May 31, User's Guide IBM Interact Version 9 Release 0 May 31, 2013 User's Guide Note Before using this information and the product it supports, read the information in Notices on page 97. This edition applies to ersion 9,

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

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

IBM InfoSphere MDM Enterprise Viewer User's Guide

IBM InfoSphere MDM Enterprise Viewer User's Guide IBM InfoSphere Master Data Management Version 11 IBM InfoSphere MDM Enterprise Viewer User's Guide GI13-2661-00 IBM InfoSphere Master Data Management Version 11 IBM InfoSphere MDM Enterprise Viewer User's

More information

IBM Features on Demand. User's Guide

IBM Features on Demand. User's Guide IBM Features on Demand User's Guide IBM Features on Demand User's Guide Note: Before using this information and the product it supports, read the general information in Appendix B, Notices, on page 55.

More information

IBM Tivoli Storage Manager for Linux Version Tivoli Monitoring for Tivoli Storage Manager

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

More information

ImageUltra Builder Version 2.0. User Guide

ImageUltra Builder Version 2.0. User Guide ImageUltra Builder Version 2.0 User Guide ImageUltra Builder Version 2.0 User Guide Note Before using this information and the product it supports, be sure to read Appendix A, Notices, on page 153. Fifth

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