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

Transcription

1 IBM Tioli Serice Leel Adisor Getting Started Version 2.1 SC

2

3 IBM Tioli Serice Leel Adisor Getting Started Version 2.1 SC

4 Fourth Edition (September 2004) This edition applies to Version 2.1 of IBM Tioli Serice Leel Adisor (program number 5724 C40) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2002, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Preface ii Who should read this guide ii Publications ii IBM Tioli Serice Leel Adisor library... ii IBM DB2 Uniersal Database Enterprise Edition library ix Tioli Data Warehouse library ix Warehouse Enablement Packs ix IBM WebSphere Application Serer library...ix SLM Administratie Console Information....x Related publications x Accessing Publications Online x Ordering publications x Accessibility xi Tioli technical training xi Contacting IBM Software Support xi Determine the business impact of your problem xii Describe your problem and gather background information xii Submit your problem to IBM Software Support xii Searching knowledge bases xiii Obtaining fixes xiii Updating support information xi Participating in newsgroups xi Conentions used in this guide x Typeface conentions x Operating system-dependent ariables and paths xi Chapter 1. Introduction What is IBM Tioli Serice Leel Adisor?....1 How IBM Tioli Serice Leel Adisor Works...2 IBM Tioli Serice Leel Adisor in the Enterprise.3 Inside IBM Tioli Serice Leel Adisor The SLM Serer SLM Reports SLM Administration Serer IBM Tioli Serice Leel Adisor Databases....6 The Central Data Warehouse Database The SLM Database The SLM Measurement Data Mart Chapter 2. Planning Decisions Components of an SLM Deployment Tioli Data Warehouse Components Warehouse Packs IBM Tioli Serice Leel Adisor Components.12 Deploying the SLM Solution in Your Enterprise 12 Deployment Options Selecting Port Numbers Coexistence with Other DB2 Database Applications 24 Information to Gather Before Installing Information for All Installations Additional Information for Single System Installations Additional Information for Distributed Installations Planning for Warehouse Packs Chapter 3. Prerequisite Software Upgrading From Preious Versions Considerations for Installing DB2 Uniersal Database Reading the Documentation Installing DB2 Serer or Client Considerations for Databases Installing DB2 Uniersal Database on UNIX Systems Installing DB2 Uniersal Database on Red Hat Connecting a Database on DB2 7.2 Serer to a DB2 8.1 Client Updating the JDBC Leel for DB2 Uniersal Database Configuring the Database Manager to use Extended Shared Memory Considerations for Installing Tioli Data Warehouse 43 Considerations for Configuring an Enironment with Multiple Central Data Warehouse Databases 43 Upgrading Tioli Enterprise Data Warehouse 1.1 to Fix Pack Installing Source Application Warehouse Packs..44 Installing IBM WebSphere Application Serer...45 Considerations for Installing IBM WebSphere Application Serer Chapter 4. Installing IBM Tioli Serice Leel Adisor Before Installing IBM Tioli Serice Leel Adisor 49 Starting the LaunchPad Creating Databases Step 1. Select the Databases to be Created Step 2. Specify Whether Databases are Local or Remote Step 3. Creating the Databases Step 4. Checking Database Creation Logs and Tables Step 5. Creating a Temporary Database and Tablespace for Databases on z/os Systems...60 Installing the IBM Tioli Serice Leel Adisor Product Step 1. Select the Language for the Installation. 62 Step 2. Accept the Software License Agreement 62 Step 3. Specify the Tioli Common Directory.. 63 Step 4. Select Installation Options Step 5. Specify the Destination Directory Step 6. Select SLM Installation Options Step 7. Verify Prerequisite Software Step 8. Configure for SLM Database Access Step 9. Specify Additional Serer Configuration 69 Copyright IBM Corp. 2002, 2004 iii

6 Step 10. Specify Eent Notification Methods.. 71 Step 11. Define SLM Administrator Authority and SLM Reports Access Step 12. Decide Whether or not to Compile JaaSerer Page Files Step 13. Optionally Configure Language Support Installation Step 14. Confirm Your Installation Options Step 15. Complete the Installation Additional Installation Tasks Chapter 5. Additional Installation Tasks 87 Regenerating Web Serer Plug-in Configurations..87 Configuring ODBC Data Sources Configuring ODBC Data Sources for Distributed Enironments Additional ODBC Data Source Configuration Methods Verifying ODBC Configuration Installing the Target Warehouse Enablement Pack.89 Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment Installing the Target Warehouse Pack for the Tioli Enterprise Data Warehouse 1.1 Enironment Configuring the User ID and Password Enabling Data Collection for Source Applications 95 Configuring for Multiple Central Data Warehouses Configuring Target ETL Table Translation Information for SLM Databases on z/os Configuring ETLs for Production Mode Running the Registration ETL and Process ETL 103 Registering Warehouse Data Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor Configuring Source ETL Table Translation Information for the SLM Database on z/os Operating Systems Configuring for Eent Notification Configuring for Notification by SNMP Configuring for Notification by Tioli Enterprise Console Verifying Notification Methods Installing Language Support Viewing Reports in Double Byte Character Languages Associating System Users with IBM Tioli Serice Leel Adisor Roles Restarting the WebSphere Application Serer Chapter 6. Startup and Shutdown Procedures Starting the IBM Tioli Serice Leel Adisor Solution Starting IBM WebSphere Application Serer..115 Starting the IBM HTTP Serices Starting the WebSphere Administratie Console 116 Starting the SLM Serer Starting the SLM Administratie Console Starting the SLM Reports Console Shutting Down the IBM Tioli Serice Leel Adisor Solution Shutting Down the SLM Administratie Console 119 Shutting Down the SLM Reports Console Shutting Down the SLM Serer Stopping IBM HTTP Serices Stopping IBM WebSphere Application Serer 120 Chapter 7. Uninstalling IBM Tioli Serice Leel Adisor Considerations Before Uninstalling Running the Uninstallation Program Uninstalling the Target and Source Warehouse Packs Uninstalling SLM Databases Uninstalling the Databases Remoing ODBC Datasources Appendix A. A Quick Start Installation Example Installation Assumptions Planning Worksheets for this Installation Step 1. Installing DB2 Uniersal Database Serer 130 Step 2. Installing IBM WebSphere Application Serer Upgrading WebSphere to Version Enabling WebSphere Security Step 3. Installing Crystal Enterprise Step 4. Installing Tioli Data Warehouse Step 5. Installing Source Application Warehouse Packs Step 6. Creating Databases for IBM Tioli Serice Leel Adisor Step 7. Installing IBM Tioli Serice Leel Adisor 135 Step 8. Configuring ODBC Data Sources Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Step 10. Configuring the User ID and Password 137 Step 11. Enabling Data Collection for Source Applications Step 12. Configuring ETLs for Production Mode 138 Step 13. Running the Registration and Process ETLs Step 14. Registering Warehouse Data Step 15. Additional Optional Configuration Step 16. Restarting WebSphere Application Serer 139 Accessing the SLM Administratie Console Accessing SLM Reports Appendix B. A Two-Machine Distributed Installation Example The Warehouse Machine The SLM Machine Installation Assumptions Planning Worksheets for this Installation Step 1. Installing DB2 Uniersal Database Serer 145 Step 2. Installing Crystal Enterprise Step 3. Installing Tioli Data Warehouse i IBM Tioli Serice Leel Adisor: Getting Started

7 Step 4. Installing Source Application Warehouse Packs Step 5. Installing IBM WebSphere Application Serer Upgrading WebSphere to Version Enabling WebSphere Security Step 6. Creating Databases for IBM Tioli Serice Leel Adisor Step 7. Installing IBM Tioli Serice Leel Adisor 149 Step 8. Configuring ODBC Data Sources Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Step 10. Configuring the User ID and Password 151 Step 11. Enabling Data Collection for Source Applications Step 12. Configuring ETLs for Production Mode 152 Step 13. Running the Registration and Process ETLs Step 14. Registering Warehouse Data Step 15. Additional Optional Configuration Step 16. Restarting WebSphere Application Serer 153 Accessing the SLM Administratie Console Accessing SLM Reports Appendix C. A Three-Machine Distributed Installation Example Installation Assumptions Appendix D. A Four-Machine Distributed Installation Example The Warehouse Machine The Crystal Machine The Database Machine The SLM Machine Installation Assumptions Planning Worksheets for this Installation Step 1. Installing DB2 Uniersal Database Serer and Client Step 2. Installing Crystal Enterprise Step 3. Installing Tioli Data Warehouse Step 4. Installing Source Application Warehouse Packs Step 5. Installing IBM WebSphere Application Serer Upgrading WebSphere to Version Enabling WebSphere Security Step 6. Creating Databases for IBM Tioli Serice Leel Adisor Step 7. Installing IBM Tioli Serice Leel Adisor 167 Step 8. Configuring ODBC Data Sources Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Step 10. Configuring the User ID and Password 170 Step 11. Enabling Data Collection for Source Applications Step 12. Configuring ETLs for Production Mode 170 Step 13. Running the Registration and Process ETLs Step 14. Registering Warehouse Data Step 15. Additional Optional Configuration Step 16. Restarting WebSphere Application Serer 171 Accessing the SLM Administratie Console Accessing SLM Reports Appendix E. Database Creation Tables 173 Tables Created in dyk_cat Tables Created in dyk_dm Appendix F. Manually Creating ODBC Data Sources Editing the Script Files Using the Windows Control Panel Administratie Tool Using DB2 Commands Creating ODBC Data Sources for Remote SLM Databases on z/os Operating Systems Verifying ODBC Configuration Appendix G. Installation Hints and Tips Starting a DB2 Command Prompt Starting a DB2 Command Prompt on Windows Systems Sourcing the db2profile on UNIX Verifying the Root User Authority in a DB2 enironment Ensuring User Rights Authority for Database Creation Ensuring fully qualified hostnames On AIX systems On Linux systems On Solaris systems On HP systems On Microsoft Windows NT systems On Windows 2000 systems Mounting the CD-ROM on UNIX Systems Checking the ersion of an existing DB2 installation Verifying your DB2 Uniersal Database Installation 189 Updating the JDBC Leel for DB Verifying the JDBC Leel Updating the JDBC Leel Manually Configuring the Database Manager to use Extended Shared Memory Installing Tioli Enterprise Data Warehouse 1.1 Fix Pack Resoling port conflicts Creating Distributed SLM Databases Manually Creating SLM Databases on Windows Systems 192 Creating SLM Databases on UNIX Systems Checking Database Creation Log Files Modifying Configuration Parameters After Creating Databases Connecting a DB2 7.2 Database with a DB2 8.1 Client Performing a Silent Installation of IBM Tioli Serice Leel Adisor Contents

8 Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor Tasks to Complete Before Upgrading IBM Tioli Serice Leel Adisor Running the IBM Tioli Serice Leel Adisor Upgrade Program Tasks to Complete After Upgrading IBM Tioli Serice Leel Adisor Step 1. Verify database upgrade and complete manually if needed Step 2. Install the new SLM Administration Serer Option Step 3. Migrate users from the preious ersion 208 Step 4. Ensure the correct ersion of the db2jaa.zip file is being used Step 5. Install the Target Warehouse Pack Step 6. Configure warehouse pack user ID and password Step 7. Manually run special ETL upgrade steps 211 Step 8. Schedule target ETLs and promote to production mode Step 9. Restore customization of JSP Files Step 10. Update notification configuration, if needed Step 11. Recreate filtering and sorting preferences for Manage pages Step 12. Optionally install language support Step 13. Search the log file for a single date message Step 14. Search the log file for unsupported time zone message Step 15. Check Quarterly Dates Step 16. Restart the serers Appendix I. IBM Tioli Business Systems Management solution Integration Designing Your Solution Understanding the Product Set Products in the Business Impact Management Layer Products in the Eent Correlation and Automation Layer Products in the Monitoring Systems and Applications Layer Appendix J. Notices Trademarks Index i IBM Tioli Serice Leel Adisor: Getting Started

9 Preface Who should read this guide Publications IBM Tioli Serice Leel Adisor : Getting Started proides information about the IBM Tioli serice leel management (SLM) software solution, and proides step-by-step instructions for installing and configuring IBM Tioli Serice Leel Adisor, including references to the installation procedures for supporting applications. This document is written for systems administrators and IBM support personnel who plan to install, configure, and integrate IBM Tioli Serice Leel Adisor and its supporting applications in the enterprise enironment. You should be familiar with planning, installing, and configuring distributed systems management software, and be somewhat familiar with the business objecties associated with Tioli s serice leel management solution. You should also be familiar with the following topics: Knowledge of IBM DB2 Uniersal Database Enterprise Edition software, in the areas of installing and configuring serers and clients, creating multiple instances, cataloging databases, and performing backup and restore operations to protect your database resources. The IBM data warehouse strategy, including installation and configuration of Tioli Data Warehouse. Supported IBM Tioli software applications that are enabled for putting data into the Tioli Data Warehouse (see the Release Notes for information on supported IBM Tioli software applications) Familiarity with installing and configuring the extract, transform, and load (ETL) processes, proided in warehouse enablement packs that are associated with the applications that put data into Tioli Data Warehouse. IBM WebSphere Application Serer, in the areas of installing, configuring, and starting and stopping the WebSphere Application Serer and the WebSphere Administratie Console The z/os enironment, if you plan to create and maintain SLM databases on a z/os operating system HTML concepts for customizing Jaa Serer Pages (JSP files) to generate Web-based reports This section lists publications in the IBM Tioli Serice Leel Adisor library and other related documents. It also describes how to access Tioli publications online, and how to order Tioli publications. IBM Tioli Serice Leel Adisor library Product information for using IBM Tioli Serice Leel Adisor is found in the /tsladocs directory on the IBM Tioli Serice Leel Adisor Publications CD (or electronic media), in PDF and HTML formats. Inserting the Publications CD into a Copyright IBM Corp. 2002, 2004 ii

10 machine using the Windows operating system automatically launches the Tioli Software Information Center, from which you can access any of the aailable documentation in softcopy form. The following documents are aailable in the IBM Tioli Serice Leel Adisor library: A Read Me First document that proides a starting point to help you become oriented with the set of IBM products that support the oerall SLM solution, and some quick instructions on what documentation to refer to as you begin your installation of IBM Tioli Serice Leel Adisor and its supporting applications. Release Notes, SC This document proides late-breaking information, such as problems and workarounds, and patch aailability. Getting Started, SC This document introduces you to IBM Tioli Serice Leel Adisor and proides information about planning, installing, and configuring IBM Tioli Serice Leel Adisor to run in your Tioli enterprise enironment. Managing Serice Leel Agreements, SC This document proides information about creating and managing schedules, offerings, customers, and realms, and associating these elements with selected resources in your enterprise enironment to deelop serice leel agreements (SLAs) between your organization and customers who depend on your enterprise for agreed upon leels of serice. This document is designed to be used by administrators, serice offering specialists, and serice leel agreement specialists who are responsible for creating and managing SLAs. SLM Reports, SC This document proides information about generating and iewing Web-based SLM reports for IBM Tioli Serice Leel Adisor, based on the ealuation and trend analysis results of the data that is extracted from the Tioli Data Warehouse database. Additional information is proided so that you or your customer can integrate SLM reports into the customer Web site, including examples of how you can customize arious display features. Administrator s Guide, SC This document proides information about the administratie tasks you can perform using IBM Tioli Serice Leel Adisor to configure your SLM enironment, and perform arious administratie functions that support IBM Tioli Serice Leel Adisor, such as backup and restore operations, and user definition and authorization. Command Reference, SC This document proides information on command line interface (CLI) commands aailable for displaying certain conditions and states inside IBM Tioli Serice Leel Adisor, and for performing arious configuration tasks using the scmd command. Additional utilities that proide other specific functions are also described. Messages, SC This document proides information on messages that might be displayed while using the IBM Tioli Serice Leel Adisor product. It proides additional explanations for messages and instructions on what to do to recoer from errors. Troubleshooting, SC This document proides information on resoling problems that you might encounter during installation and configuration, as well as resoling iii IBM Tioli Serice Leel Adisor: Getting Started

11 administratie problems that might arise during typical operation of the product. Information about message and trace logging is also proided. Online user assistance for IBM Tioli Serice Leel Adisor The online user assistance proides integrated online help topics for all IBM Tioli Serice Leel Adisor administratie tasks that are performed using the SLM Administratie Console. Online user assistance is displayed in the Task Assistant portion of the SLM Administratie Console. Specific information about performing IBM Tioli Serice Leel Adisor tasks is documented only in this online user assistance. When new products are installed that run in the SLM Administratie Console, corresponding online help topics are also installed and integrated into the existing information base. In addition, refer to the following IBM Tioli Serice Leel Adisor Web site for support information and software updates on IBM Tioli Serice Leel Adisor and supported warehouse packs and downloadable interim fix software: IBM DB2 Uniersal Database Enterprise Edition library The publications required to support IBM DB2 are aailable on the IBM DB2 Uniersal Database Enterprise Edition CD, or from this IBM Web site: Tioli Data Warehouse library IBM Tioli Serice Leel Adisor requires Tioli Data Warehouse to be installed in your enterprise, to sere as the data repository for Tioli performance and aailability monitoring applications that proide data for serice leel management. See the following documentation on the Tioli Data Warehouse documentation CD included with IBM Tioli Serice Leel Adisor: Installing and Configuring Tioli Data Warehouse Enabling an Application for Tioli Data Warehouse Tioli Data Warehouse Release Notes Warehouse Enablement Packs Warehouse enablement packs (also referred to as warehouse packs) are the interfaces that load and transform data collected by source applications into Tioli Data Warehouse, and from Tioli Data Warehouse to other target applications that use the data to generate reports and perform analyses. Refer to the Release Notes for IBM Tioli Serice Leel Adisor for the online location of the latest warehouse pack information. IBM WebSphere Application Serer library IBM Tioli Serice Leel Adisor uses IBM WebSphere Application Serer as the basis for the SLM Administration Serer and SLM Reports functions. Getting Started proides introductory information on installing IBM WebSphere Application Serer and integrating it with IBM Tioli Serice Leel Adisor. See the official documentation proided on the IBM WebSphere Application Serer product media included with IBM Tioli Serice Leel Adisor for additional information, and also refer to the latest IBM WebSphere Application Serer product information online at the following Web site: Preface ix

12 SLM Administratie Console Information IBM Tioli Serice Leel Adisor proides the SLM Administratie Console, a Web-based Administration Serer graphical user interface (GUI) that runs in the IBM WebSphere enironment, from which you can create and manage schedules, offerings, customers, realms, and SLAs. Information on the use of the SLM Administratie Console and tasks related to creating and managing SLAs are described in detail in Managing Serice Leel Agreements. User assistance for the SLM Administratie Console is aailable in the Task Assistant online help function. Related publications The following documents also proide useful information: The Tioli Software Glossary includes definitions for many of the technical terms related to Tioli software. The Tioli Software Glossary is aailable, in English only, at the following Web site: Access the glossary by clicking the Glossary link on the left pane of the Tioli software library window. Accessing Publications Online Ordering publications In addition to the Publications CD that is shipped with IBM Tioli Serice Leel Adisor, you can also access these publications online. IBM posts publications for this and all other Tioli products, as they become aailable and wheneer they are updated, to the Tioli software information center Web site. Access the Tioli software information center by first going to the Tioli software library at the following Web address: Scroll down and click the Product manuals link. In the Tioli Technical Product Documents Alphabetical Listing window, click the IBM Tioli Serice Leel Adisor link to access the product library at the Tioli software information center. Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper. You can order many Tioli publications online at the following Web site: You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, see the following Web site for a list of telephone numbers: x IBM Tioli Serice Leel Adisor: Getting Started

13 Accessibility Tioli technical training Accessibility features help users with a physical disability, such as restricted mobility or limited ision, to use software products successfully. With this product, you can use assistie technologies to hear and naigate the interface.you can also use the keyboard instead of the mouse to operate all features of the graphical user interface. For Tioli technical training information, refer to the following IBM Tioli Education Web site: Contacting IBM Software Support IBM Software Support proides assistance with product defects. 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 following Passport Adantage Web page and click How to Enroll: By phone: For the phone number to call in your country, go to the following IBM Software Support Web site and click the name of your geographic region: techsupport.serices.ibm.com/guides/contacts.html 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 sales representatie or an IBM Business Partner. For more information about support for eserer software products, go to the IBM Technical Support Adantage Web page: If you are not sure what type of software maintenance contract you need, call IBMSERV ( ) in the United States or, from other countries, go to the contacts page of the following IBM Software Support Handbook on the Web and click the name of your geographic region for phone numbers of people who proide support for your location: techsupport.serices.ibm.com/guides/contacts.html Follow the steps in this topic to contact IBM Software Support: 1. Determine the business impact of your problem. 2. Describe your problem and gather background information. 3. Submit your problem to IBM Software Support. Preface xi

14 Determine the business impact of your problem 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 you are reporting. Use the following criteria to decide on an appropriate seerity leel for your problem: Seerity 1 Seerity 2 Seerity 3 Seerity 4 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. Significant business impact: The program is usable but is seerely limited. Some business impact: The program is usable with less significant features (not critical to operations) unaailable. Minimal business impact: The problem causes little impact on operations, or a reasonable circumention to the problem has been implemented. Describe your problem and gather background information When explaining 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 the problem be recreated? If so, what steps led to the failure? Hae any changes been made to the system? (For example, hardware, operating system, networking software, and so on.) Are you currently using a workaround for this problem? If so, please be prepared to explain it when you report the problem. Submit your problem to IBM Software Support You can submit your problem in one of two ways: Online: Go to the Submit and track problems page on the IBM Software Support site ( Enter your information into the appropriate problem submission tool. 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 the problem be recreated? If so, what steps led to the failure? Hae any changes been made to the system? (For example, hardware, operating system, networking software, and so on.) Are you currently using a workaround for this problem? If so, please be prepared to explain it when you report the problem. 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 for you to implement until the APAR is resoled and a fix is deliered. IBM publishes resoled APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions. xii IBM Tioli Serice Leel Adisor: Getting Started

15 For more information about problem resolution, see Searching knowledge bases and Obtaining fixes. Searching knowledge bases If you hae a problem with your IBM software, you want it resoled quickly. Begin by searching the aailable knowledge bases to determine whether the resolution to your problem is already documented. Search the information center on your local system or network IBM proides extensie documentation that can be installed on your local machine or on an intranet serer. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents. Tip: Update your information center with the latest support information. Search the Internet If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resole your problem. To search multiple Internet resources for your product, expand the product folder in the naigation frame to the left and select Support on the Web. From this topic, you can search a ariety of resources including: IBM technotes IBM downloads IBM Redbooks IBM DeeloperWorks Forums and newsgroups Google Obtaining fixes A product fix might be aailable to resole your problem. You can determine what fixes are aailable for your IBM software product by checking the product support Web site: 1. Go to the IBM Software Support Web site ( 2. Under Products A - Z, select your product name. This opens a product-specific support site. 3. Under Self help, follow the link to All Updates, where you will find a list of fixes, fix packs, and other serice updates for your product. For tips on refining your search, click Search tips. 4. Click the name of a fix to read the description and optionally download the fix. To receie weekly notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the upper-right corner of the page. 2. If you hae already registered, skip to the next step. If you hae not registered, click register in the upper-right corner of the support page to establish your user ID and password. 3. Sign in to My support. Preface xiii

16 4. On the My support page, click Edit profiles in the left naigation pane, and scroll to Select Mail Preferences. Select a product family and select the appropriate boxes for the type of information you want. 5. Click Submit. 6. For notification for other products, repeat Steps 4 and 5. For more information about types of fixes, see the Software Support Handbook ( Updating support information Information centers typically include one or more support information plug-ins. These plug-ins add IBM technotes and other support documents to the information center. The following steps describe how to update your support information plug-ins: Participating in newsgroups 1. Go to the IBM Software Support Web site ( 2. Under Products A - Z, select your product name. This opens a product-specific support site. 3. Under Search support for this product, type the keyword phrase: com.ibm.support. Select the Download check box, and click Submit. 4. Check the search results for updates to support information plug-ins. All support information plug-ins follow the naming conention, com.ibm.support.product.doc. If an update is aailable, select it from the list and iew the download instructions. 5. Sae the attached zip file to a temporary location on your hard drie. 6. Unzip the downloaded file, making sure that you retain the subfolders. 7. From the location where you unzipped the file, copy the support information plug-in folder to your Eclipse plug-ins folder. For example, if your IBM software product is installed at c:\ibm\websphere\, copy the updated plug-in folder (com.ibm.support.product.doc) to c:\ibm\websphere\eclipse\plugins. 8. To see the updated support information, start the information center (or shut it down and restart it), and expand the Support information node in the naigation tree. User groups proide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet, and are aailable using standard news reader programs. These groups are primarily intended for user-to-user communication, and are not a replacement for formal support. If you use Mozilla as your browser, complete the following instructions to access a newsgroup: 1. Open a Mozilla browser window. 2. From the Edit menu, click Preferences. The Preferences window is displayed. 3. In the Category iew, click Mail & Newsgroups to display the Mail & Newsgroups settings. 4. Select the Use Mozilla mail as the default mail application check box. 5. Click OK. 6. Close your Mozilla browser and then open it again. xi IBM Tioli Serice Leel Adisor: Getting Started

17 7. Cut and paste the newsgroup address of a product into the browser Address field, and press Enter to open the newsgroup. If you use Microsoft Internet Explorer as your browser, complete the following instructions to access a newsgroup: 1. Open an Internet Explorer browser. 2. From the Tools menu, click Internet Options. 3. On the Internet Options window, click the Programs tab. 4. In the Newsgroups list, click the Down Arrow and then click Outlook Express. 5. Click OK. 6. Close your Internet Explorer browser and then open it again. 7. Cut and paste the newsgroup address of a product into the browser Address field, and press Enter to open the newsgroup. You can find information on Tioli Data Warehouse by accessing the following newsgroup: news://news.software.ibm.com/ibm.software.tioli.enterprise-data-warehouse You can find information on IBM Tioli Serice Leel Adisor by accessing the following newsgroup: news://news.software.ibm.com/ibm.software.tioli.serice-leel-adisor You can find information on IBM DB2 by accessing the following newsgroup: news://news.software.ibm.com/ibm.software.db2 You can find information on IBM WebSphere Application Serer by accessing the following newsgroup: news://news.software.ibm.com/ibm.software.websphere.application-serer Conentions used in this guide This guide uses seeral conentions for special terms and actions, operating system-dependent commands and paths, and margin graphics. Typeface conentions This guide uses the following typeface conentions: Bold Italic Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Citations (titles of books, diskettes, and CDs) Words defined in text Emphasis of words (words as words) New terms in text (except in a definition list) Variables and alues you must proide Preface x

18 Monospace Examples and code examples File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Operating system-dependent ariables and paths This guide uses the UNIX operating system conention for specifying enironment ariables and for directory notation. When using the Windows operating system command line, replace $ariable with % ariable% for enironment ariables and replace each forward slash (/) with a backslash ( \) in directory paths. The names of enironment ariables are not always the same in Windows and UNIX operating systems. For example, %TEMP% in Windows systems is equialent to $tmp in UNIX systems. Note: If you are using the bash shell on a Windows system, you can use the UNIX conentions. xi IBM Tioli Serice Leel Adisor: Getting Started

19 Chapter 1. Introduction As today s enterprise marketplace shifts away from custom in-house business application solutions to more off-the-shelf applications, the Internet has become a ehicle for serice deliery within the enterprise as well as externally. At the same time, more focus is being placed on increasing productiity and managing costs in the enterprise, enabling the information technology (IT) infrastructure to contribute more to the oerall success of the business. What is IBM Tioli Serice Leel Adisor? IBM Tioli Serice Leel Adisor proides serice leel management (SLM) capabilities for enterprise organizations that need to measure, manage, and report on aailability and performance aspects of their internal IT infrastructure. With IBM Tioli Serice Leel Adisor, you can more quickly and efficiently obtain information to help you manage network and application serices. You can maintain productiity and customer satisfaction, minimize reenue impact, manage costs, and improe planning by assuring offered serices. IBM Tioli Serice Leel Adisor offers easy to use interfaces, quick and easy customization of features, and default alues where appropriate. The SLM solution proided by IBM Tioli Serice Leel Adisor also inoles a number of additional IBM applications: IBM DB2 Uniersal Database Enterprise Edition (DB2), which proides the database support for long term storage of measurement data used by IBM Tioli Serice Leel Adisor. Tioli Data Warehouse, which uses the DB2 warehouse functions to establish the central data repository used in the Tioli SLM solution. Tioli performance and aailability monitoring applications store their measurement data in Tioli Data Warehouse, and at some later time this data is sent to the local databases used by IBM Tioli Serice Leel Adisor. The data is then ealuated and analyzed, with reports and notifications issued to supporting personnel to assist in managing agreed upon leels of serice. Warehouse enablement packs (also known as warehouse packs), that are associated with each Tioli application that puts data into, or takes data out of, the Tioli Data Warehouse central data warehouse database. Warehouse packs typically include one or more sets of specialized ETL routines that extract the data, transform it into a usable format, and then load it to another database for further processing. Each source application that is configured for writing data to the central data warehouse must hae an associated warehouse pack. IBM Tioli Serice Leel Adisor has its own warehouse pack as well, which includes ETL routines both for collecting data from the central data warehouse and writing data back into the central data warehouse for possible use by other applications. IBM WebSphere Application Serer, used by IBM Tioli Serice Leel Adisor as the operating enironment not only for its administratie user interface, but also for its reporting interface, is used to iew generated reports resulting from the ealuation and trend analysis of the collected measurement data. Reports are generated using customizable Jaa serlets that can be integrated directly into your company s Web site, proiding ready access to serice leel management data from a Web browser. Copyright IBM Corp. 2002,

20 Getting Started describes how these applications work together in support of Tioli s SLM solution for your enterprise enironment, and guides you through the related planning, installation and configuration procedures. How IBM Tioli Serice Leel Adisor Works The serice leel management capabilities of IBM Tioli Serice Leel Adisor complement the performance and aailability measurement functions of other Tioli products, such as Tioli Monitoring for Transaction Performance - Web Transaction Performance. Tioli Monitoring for Transaction Performance - Web Transaction Performance measures the response time of a Web site, breaking a serice into associated sub-applications that complete a serice transaction. IBM Tioli Serice Leel Adisor relies on the monitoring and measuring functions of this and other Tioli applications to gather data through their own facilities. This performance and aailability data is written by the monitoring applications to the Tioli Data Warehouse database, a centralized repository where large amounts of raw data are summarized and stored. IBM Tioli Serice Leel Adisor can then use its built in data collector interface to extract and analyze this data, determine long term trends, and generate reports of iolations or trends toward iolations of guaranteed leels of serice. See the Administrator s Guide or Managing Serice Leel Agreements for information on how IBM Tioli Serice Leel Adisor interacts with Tioli Data Warehouse, and refer to the documentation accompanying the Tioli Data Warehouse installation media. Figure 1. IBM Tioli Serice Leel Adisor analyzes performance and aailability data from multiple source applications that store their data in Tioli Data Warehouse. With IBM Tioli Serice Leel Adisor you can manage the information collected by monitoring applications against serice leel agreements (SLAs) associated with your internal enterprise customers, which might be a department or diision in your organization, or some other consumer of serices proided by your enterprise. Analysis of the data collected, identification of trends in serice leels, and generated reports can be associated with a specific enterprise customer. 2 IBM Tioli Serice Leel Adisor: Getting Started

21 IBM Tioli Serice Leel Adisor in the Enterprise IBM Tioli Serice Leel Adisor resides in the firewall protected, secure back office layer of your enterprise. Other Tioli applications responsible for performance and aailability monitoring might reside elsewhere in your enterprise enironment. The monitoring data they collect is stored in their local databases, completely separated from IBM Tioli Serice Leel Adisor. These applications and their associated databases are referred to as source applications and source databases. At certain scheduled interals this data is moed from the source databases into the Tioli Data Warehouse database, a centralized repository also located in the secure back office layer of your enironment, that holds all of the performance and aailability monitoring data of interest from the arious source applications. IBM Tioli Serice Leel Adisor uses Tioli Data Warehouse as the source for all of its data to be analyzed for guaranteeing leels of serice in your enterprise IT infrastructure. IBM Tioli Serice Leel Adisor supports a Web application serer enironment running in the back office layer of the enterprise, as shown in Figure 2 on page 4. User interfaces are accessible through a Web browser, requiring no additional client footprint. This deployment scheme proides the easiest and most secure model for IBM Tioli Serice Leel Adisor, and is suitable when integrating with other enironments. Chapter 1. Introduction 3

22 Figure 2. IBM Tioli Serice Leel Adisor is deployed in the secure back office layer of the enterprise. Placing IBM Tioli Serice Leel Adisor in the secure back office layer of the enterprise with Tioli Data Warehouse eliminates the need to define a security infrastructure. Communication with less secure layers is done oer HTTP. Inside IBM Tioli Serice Leel Adisor Figure 3 on page 5, shows the following main functional units of IBM Tioli Serice Leel Adisor: The SLM Serer, which proides most of the serice leel management function for managing serice leel agreements, scheduling the frequency and times when data is collected and ealuated, performing the ealuation and analysis of the data, and notification if iolations or trends toward iolations of SLAs are detected. The SLM Reports, which are standard Jaa-based report serlets that can be integrated into a customer s Web site using JaaSerer Pages (JSP files). These report serlets summarize the results of the ealuation and analysis, proiding information in table and graph form that you can customize. The SLM Administration Serer, that proides the role-based administratie user interface within a WebSphere enironment for administratie and customer serice related tasks. 4 IBM Tioli Serice Leel Adisor: Getting Started

23 Figure 3. IBM Tioli Serice Leel Adisor includes the SLM Serer, the SLM Administration Serer, and the SLM Reports Serer. These three functional units of IBM Tioli Serice Leel Adisor can all exist on the same machine, or can reside on three separate machines in your enterprise, including different geographical regions, spanning multiple time zones. The SLM Serer The SLM Serer performs the main functions necessary for serice leel management, including: Processing SLAs Scheduling and performing ealuation and trend analysis of measurement data Storing the results of the analysis Notification of iolations or trends toward iolations of SLAs SLM Reports The report serlets use the functions of the IBM WebSphere Application Serer to obtain SLA results data and generate summary reports in the form of tables and graphs that can be displayed in a Web browser. These serlets can be used by the enterprise to create customized web pages for customers, displaying results of ealuation and trend analyses, such as: Actual leel of serice proided Number of SLA iolations Trends toward future iolations See SLM Reports for more information on customizing report serlets to integrate into a Web site, and to learn more about the sample JSP files that come with IBM Tioli Serice Leel Adisor. Chapter 1. Introduction 5

24 SLM Administration Serer The SLM Administration Serer proides a Web-based interface in a WebSphere enironment for: Creating offerings and SLAs Specifying schedules and defining peak times and other schedule states (such as standard, prime, off hours, and others) for arying leels of serice Specifying how often ealuation and trend analysis should be performed Specifying breach alues for metrics associated with offerings Managing actie SLAs See Managing Serice Leel Agreements for more information on the administratie user interface and the tasks that you can perform using IBM Tioli Serice Leel Adisor. IBM Tioli Serice Leel Adisor Databases IBM Tioli Serice Leel Adisor depends on three main databases for its operation: The central data warehouse database from Tioli Data Warehouse The SLM Database The SLM Measurement Data Mart The Central Data Warehouse Database The central data warehouse database component of Tioli Data Warehouse seres as the main repository for historical data that is used by applications such as IBM Tioli Serice Leel Adisor. Tioli Data Warehouse is the source for resource related data, and is where the arious Tioli performance and aailability monitoring applications send their data for long term storage. See the Administrator s Guide and Managing Serice Leel Agreements for more information about this database. Getting Started proides basic installation and configuration information for this database. Refer to the Tioli Data Warehouse documentation included with IBM Tioli Serice Leel Adisor for more detailed installation and configuration details. The SLM Database The SLM Database seres seeral purposes: The SLM Database contains information from Tioli Data Warehouse that defines possible combinations of resources and metrics that are aailable to the customer to be used in SLAs. It contains a list of unique resources, resource types, and metric types that exist in Tioli Data Warehouse. This information is referenced during the creation of offerings. See Managing Serice Leel Agreements for information on creating offerings and SLAs. The SLM Database also contains information specific to the definition and management of schedules, offerings, customers, realms, and SLAs. Details about these objects that are created and managed using IBM Tioli Serice Leel Adisor are stored in the SLM Database. The SLM Database also stores the results of the analysis and trend ealuation processes, when serice leel objecties (SLOs) are compared to expected results. From this information, the customer can iew summarized reports that indicate how well their agreed upon leels of serice are being maintained. 6 IBM Tioli Serice Leel Adisor: Getting Started

25 The SLM Measurement Data Mart The SLM Measurement Data Mart is the database containing a subset of the measurement data from Tioli Data Warehouse that is of interest to IBM Tioli Serice Leel Adisor in the ealuation and reporting of SLA conformance. It is updated on a regular basis with the latest metric data from Tioli Data Warehouse. Chapter 1. Introduction 7

26 8 IBM Tioli Serice Leel Adisor: Getting Started

27 Chapter 2. Planning Decisions Before installing IBM Tioli Serice Leel Adisor into your enterprise enironment, you need to consider the hardware requirements, the physical locations of where you want to install the arious functional pieces of IBM Tioli Serice Leel Adisor, and their dependencies on the other Tioli and IBM applications which support the Tioli serice leel management (SLM) solution. IBM Tioli Serice Leel Adisor and all of its supporting applications can be installed on a single machine in your enterprise, or across multiple machines with certain dependencies. Components of an SLM Deployment IBM Tioli Serice Leel Adisor is designed to run in a number of different configurations, depending on how the system is used, and which components need to be scaled or isolated. Note: For this discussion, the term component is used to describe one of the logical entities within the IBM Tioli Serice Leel Adisor installation that can be installed by itself on a physical machine or with one or more other logical entities on the same physical machine. You can install all of the components of a IBM Tioli Serice Leel Adisor installation on a single physical machine, or you can distribute them in arious combinations across multiple machines in your enterprise. Installing on a single physical machine is only recommended for use in an ealuation enironment, and is not recommended for use in a typical production enironment. See the following appendices for different installation examples of minimum recommended entry leel configurations: Appendix A, A Quick Start Installation Example, on page 127 Appendix B, A Two-Machine Distributed Installation Example, on page 141 Appendix C, A Three-Machine Distributed Installation Example, on page 155 Appendix D, A Four-Machine Distributed Installation Example, on page 157 Before you can install IBM Tioli Serice Leel Adisor, you must hae a clear understanding of the major components of both Tioli Data Warehouse and IBM Tioli Serice Leel Adisor, because the distribution of some of their components is interdependent. Tioli Data Warehouse Components If you hae not already done so, you should first read and become thoroughly familiar with Installing and Configuring Tioli Data Warehouse, specifically the information in the Oeriew and Planning chapters, which discuss the arious major components of Tioli Data Warehouse, and information that you need to know to determine how to distribute the arious components of Tioli Data Warehouse in your enironment. How you deploy Tioli Data Warehouse in your enironment might affect your decisions on distributing the components of IBM Tioli Serice Leel Adisor. You should also refer to the Tioli Data Warehouse Release Notes for additional information on hardware prerequisites, and specific database and operating system support. Copyright IBM Corp. 2002,

28 DB2 Uniersal Database must be installed on all machines in your enterprise where you plan to locate one or more components of Tioli Data Warehouse or IBM Tioli Serice Leel Adisor. Note that both Tioli Data Warehouse and IBM Tioli Serice Leel Adisor support some common and some different ersions of DB2 Uniersal Database. Depending on which ersion of DB2 Uniersal Database you install in your enironment, you might or might not be able to install certain components of IBM Tioli Serice Leel Adisor and Tioli Data Warehouse on the same machine. In brief, this documentation discusses the following major components of Tioli Data Warehouse: Tioli Data Warehouse control serer The control serer manages communication between the other main components of Tioli Data Warehouse, and also controls the ETL processes that moe and transform data between the arious source applications and Tioli Data Warehouse, as well as the data between Tioli Data Warehouse and IBM Tioli Serice Leel Adisor. The control serer must be installed on a Windows operating system, and uses the following DB2 Uniersal Database components: The DB2 Serer The Data Warehouse Center, a component that automates data warehouse processing The warehouse agent, part of DB2 Warehouse Manager The warehouse logger The warehouse serer Central data warehouse This is a DB2 database that acts as the central data repository containing the historical data for your enterprise. Tioli and other third party applications that are installed throughout your enterprise can store their data in the central data warehouse database. IBM Tioli Serice Leel Adisor then obtains a subset of that data from the central data warehouse and stores it locally for ealuation and trend analysis. The system where the central data warehouse is installed is called the central data warehouse serer. If you are using Tioli Data Warehouse 1.2, you can configure more than one central data warehouse to proide data to IBM Tioli Serice Leel Adisor. See Considerations for Configuring an Enironment with Multiple Central Data Warehouse Databases on page 43 for more information. Data marts Data marts are separate DB2 databases that contain a subset of the historical data from the central data warehouse. Tioli Data Warehouse creates its own data mart for use with its own reporting interface. The machine where this data mart resides is called the data mart serer. IBM Tioli Serice Leel Adisor does not use this data mart. The installation process for IBM Tioli Serice Leel Adisor includes the creation of its own set of data mart databases, where data from the central data warehouse that is of interest to IBM Tioli Serice Leel Adisor is stored for local ealuation and analysis. Report interface This release of IBM Tioli Serice Leel Adisor supports Tioli 10 IBM Tioli Serice Leel Adisor: Getting Started

29 Enterprise Data Warehouse ersion 1.1 and Tioli Data Warehouse ersion 1.2. Each ersion of Tioli Data Warehouse proides its own unique reporting interface: Tioli Enterprise Data Warehouse Version 1.1 uses the Web console interface of the IBM Console, part of Tioli Presentation Serices. The installation of Tioli Enterprise Data Warehouse ersion 1.1 includes the installation of Tioli Presentation Serices. If you already hae a supported ersion of Tioli Presentation Serices installed in your enterprise, you must install the Tioli Enterprise Data Warehouse ersion 1.1 report interface on that same machine. Although Tioli Presentation Serices is supported on both UNIX and Windows operating systems, it is recommended that you install this report interface on a Windows system where possible. Tioli Data Warehouse ersion 1.2 uses the reporting functions proided with Crystal Reports. Refer to the Tioli Data Warehouse 1.2 documentation for more information on Crystal Reports. IBM Tioli Serice Leel Adisor does not use these reporting interfaces, but has its own reporting interface which is used to generate reports from the local ealuation and trend analysis of metric data obtained from the central data warehouse and stored in the IBM Tioli Serice Leel Adisor data marts. These main components of Tioli Data Warehouse might be distributed on one or more different machines in your enironment, similar to the following typical configuration: The control serer on a Windows serer machine running DB2 Serer The central data warehouse and data marts together on a large database serer machine (Windows or UNIX system), running DB2 Serer The report interface on a third system, running DB2 Client or DB2 Serer. If this serer is also on a Windows operating system, you might consider installing it on the same system as the control serer, reducing the configuration to two machines. Warehouse Packs A warehouse pack, the part of a Tioli performance and aailability monitoring application that proides warehouse functionality, can be proided on the installation media for the product, on a separate CD, or in a collection of warehouse packs. If a warehouse pack is included on a CD with other product installation code, the warehouse pack information is located in a separate subdirectory named either tedw_apps or tedw_apps_etl. Warehouse packs proide the ETL functionality between the source applications in the enterprise and Tioli Data Warehouse, moing and transforming data from arious Tioli and other third party source applications, and storing it in the central data warehouse. These source ETLs come with each warehouse-enabled source application, and you can install them using the installation programs and procedures proided with Tioli Data Warehouse. IBM Tioli Serice Leel Adisor also proides its own set of warehouse packs, containing both target ETLs and a source ETL that moes and transforms data between the central data warehouse and the local data marts used by IBM Tioli Serice Leel Adisor to ealuate metric data and analyze the data for trends and Chapter 2. Planning Decisions 11

30 iolations of serice leel agreements. The installation of the IBM Tioli Serice Leel Adisor warehouse packs also uses the warehouse pack installation program proided with Tioli Data Warehouse. All warehouse packs, for IBM Tioli Serice Leel Adisor and source applications, must be installed on the system containing the control serer component of Tioli Data Warehouse. IBM Tioli Serice Leel Adisor Components The following components of IBM Tioli Serice Leel Adisor were introduced in Chapter 1, Introduction, on page 1: SLM Serer SLM Reports SLM Administration Serer SLM Database SLM Measurement Data Mart In addition, the warehouse packs that proide the ETL functionality between the central data warehouse and the SLM Database and SLM Measurement Data Mart are installed in the Tioli Data Warehouse control serer, along with other warehouse packs for source applications. It is possible for all of these components of IBM Tioli Serice Leel Adisor to be installed on a single machine, or distributed on multiple machines in your enterprise. Taking adantage of the Tioli Data Warehouse enironment that are already installed and configured in preious steps, you might choose to install arious components of IBM Tioli Serice Leel Adisor on the same systems where Tioli Data Warehouse components are installed. As you plan your installation, remember that where you install components of IBM Tioli Serice Leel Adisor might be limited to specific machines and supported ersions of DB2 Uniersal Database, Tioli Data Warehouse, and IBM WebSphere Application Serer that you hae installed in your enterprise enironment. Deploying the SLM Solution in Your Enterprise The arious components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor, along with supporting applications (DB2 Uniersal Database, IBM WebSphere Application Serer, and the warehouse packs) combine together to create the oerall SLM solution for your enterprise. The Tioli Data Warehouse components that are of interest to IBM Tioli Serice Leel Adisor are the central data warehouse serer and the control serer. For purposes of this discussion, we ignore the Tioli Data Warehouse data marts and report interface, because they are not actie parts of the SLM solution. Howeer, you might choose to locate your SLM Database and SLM Measurement Data Mart on the same system as the Tioli Data Warehouse data marts. These components are present in the oerall solution, but they are not considered in the deployment examples that follow. Combining the arious functions of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor, the oerall SLM solution includes the following components: Tioli Data Warehouse control serer Central data warehouse serer SLM Administration Serer 12 IBM Tioli Serice Leel Adisor: Getting Started

31 SLM Serer SLM Report Serer SLM Database SLM Measurement Data Mart Each of the indiidual components is shown in Figure 4, and is described in the following sections. Figure 4. The components of an IBM Tioli Serice Leel Adisor deployment. The Tioli Data Warehouse Control Serer The Tioli Data Warehouse control serer includes the control serer and the management of the source and target ETLs, running DB2 Serer on a Windows operating system. The warehouse packs for source ETLs are installed on this same machine from the warehouse pack installation media, and the IBM Tioli Serice Leel Adisor target ETLs (referred to later in this document as the Registration ETL, Process ETL and Purge ETL) are installed on this machine from the IBM Tioli Serice Leel Adisor installation media. Note: The warehouse packs and target ETLs must be installed on the same physical machine as the control serer. The control serer is supported only on certain Windows operating systems (see the Release Notes for details). If the central data warehouse serer is also on a Chapter 2. Planning Decisions 13

32 supported Windows operating system, you might prefer to install these two components on the same physical machine, to reduce the amount of ETL processing traffic across the network between two separate machines in your enterprise. The Central Data Warehouse Serer The central data warehouse serer contains the central data warehouse (and typically the Tioli Data Warehouse data mart serer on the same machine), running DB2 Serer on a Windows or UNIX operating system. The Tioli Data Warehouse performance and aailability schema, or data model, is installed on this DB2 database to configure the central data warehouse for storing data from the arious source applications. Though other components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor can reside on this same machine, you might prefer to keep the central data warehouse on a separate machine to ease its management and maintenance. The SLM Serer The SLM Serer component of IBM Tioli Serice Leel Adisor runs with DB2 Serer or DB2 Client on a Windows or UNIX operating system. The SLM Serer proides the serice leel functionality of IBM Tioli Serice Leel Adisor. Functions support offering and SLA creation, scheduling of ealuation and trend analysis of measurement data from Tioli Data Warehouse, managing customers and SLAs, and notifying support personnel and other applications when serice leel agreements are iolated or trends indicating a potential iolation are detected. The SLM Serer is installed from the IBM Tioli Serice Leel Adisor installation media, and can be installed on its own machine or with other components on the same machine. If the SLM Serer is installed on a machine different from the SLM Database and SLM Measurement Data Mart databases, then you must install a DB2 client or DB2 Serer on the machine with the SLM Serer. See the Release Notes for recommended hardware requirements and supported operating systems for the SLM Serer. The SLM Administration Serer The SLM Administration Serer contains the administratie user interface component of IBM Tioli Serice Leel Adisor. It proides support for all administratie tasks in IBM Tioli Serice Leel Adisor and is an integral part of the Tioli user interface architecture. This distributed, deice-independent, and operating system independent interface is installed in a WebSphere enironment and can be displayed in a Web browser. The SLM Administration Serer is installed as part of the IBM Tioli Serice Leel Adisor installation process. The SLM Administration Serer runs in the IBM WebSphere Application Serer enironment. See the Release Notes for recommended hardware requirements, supported operating systems, and supported ersions of IBM WebSphere Application Serer for the SLM Administration Serer. The SLM Administration Serer can be installed on the same machine as other components, or on a separate machine. If the SLM Administration Serer is installed on a machine different from where the SLM Database and SLM 14 IBM Tioli Serice Leel Adisor: Getting Started

33 Measurement Data Mart are located, then you must install and configure a DB2 Client or DB2 Serer on the machine containing the SLM Administration Serer. Web Browser Requirements: The SLM Administration Serer requires one of the following Web browsers running in your enterprise: Internet Explorer Mozilla Refer to the Release Notes for information on supported Web browser ersions. Also, see Deploying SLM Reports and SLM Administration Serer in WebSphere. The SLM Reports Serer The SLM Reports Serer contains the SLM Reports component of IBM Tioli Serice Leel Adisor and is used to support the report serlets that are proided with IBM Tioli Serice Leel Adisor. These Jaa-based report serlets are used by customers to integrate tables and graphs of serice leel management reports into their company Web sites for iewing in a Web browser. The SLM Reports Serer runs in the IBM WebSphere Application Serer enironment. See the Release Notes for recommended hardware requirements, supported operating systems, and supported ersions of IBM WebSphere Application Serer for the SLM Reports Serer. If the SLM Reports are installed on a machine different from the SLM Database and the SLM Measurement Data Mart databases, then you need to install a DB2 Client or DB2 Serer on the machine with SLM Reports. Deploying SLM Reports and SLM Administration Serer in WebSphere: If you do not already hae a supported ersion of IBM WebSphere Application Serer installed in your enterprise, you can install the ersion of IBM WebSphere Application Serer that is shipped with IBM Tioli Serice Leel Adisor and then optionally upgrade to another supported ersion by downloading the installation media from the WebSphere Web site (see the Release Notes for details). Note: You can install these components on separate WebSphere serers, but it is recommended that you install both SLM Reports and the SLM Administration Serer in the same WebSphere application serer for ease in future upgrades. For any supported ersion of IBM WebSphere Application Serer, IBM Tioli Serice Leel Adisor automatically integrates the SLM Administration Serer and SLM Reports components into the WebSphere enironment during installation. If a supported Network Deployment ersion of IBM WebSphere Application Serer is installed, howeer, you must install these components on the machine, or WebSphere node, where the target application serer is located, and not on the machine where the deployment manager is located. Refer to the official documentation for IBM WebSphere Application Serer for additional recommendations on hardware requirements and supported operating systems. The SLM Application Database Serer The SLM Application Database Serer is the database serer that contains the SLM Database and the SLM Measurement Data Mart databases used by IBM Tioli Serice Leel Adisor. Depending on your deployment, these databases can be created on the same machine as the central data warehouse, located in the same Chapter 2. Planning Decisions 15

34 DB2 instance, or they can be created in their own DB2 instance, separate from the central data warehouse, on one or two machines, for scalability, aailability, and performance considerations. These DB2 databases run on either a Windows, UNIX, or z/os based DB2 Serer machine. This ersion of IBM Tioli Serice Leel Adisor supports the installation of its SLM databases on a machine haing a one of the supported ersions of DB2 Uniersal Database installed (see the Release Notes for details). In general, IBM Tioli Serice Leel Adisor supports the same ersions of DB2 Uniersal Database as supported by Tioli Data Warehouse. If you want to install the SLM Database and SLM Measurement Data Mart on a different ersion of DB2 Uniersal Database, you must install them with the following restrictions: Tioli Data Warehouse must be installed using a local agent on the Data Warehouse Center. The SLM databases must be installed on a separate machine from Tioli Data Warehouse. A DB2 7.2 client (at the supported ersion) must be installed on the machine where the SLM databases are located. In a DB2 production enironment you might prefer to set up a separate instance of DB2 Uniersal Database for both the SLM Database and SLM Measurement Data Mart to start and stop these databases for setup and configuration purposes, without disrupting another database serer instance. By creating the two SLM databases in a DB2 instance separate from other instances on different DB2 management systems, the IBM Tioli Serice Leel Adisor solution performs better and is better protected from data loss. The installation and configuration procedures for the IBM Tioli Serice Leel Adisor databases requires starting, stopping, and terminating the instance, thereby shutting down any applications connected to that instance. See the official DB2 documentation for more information on creating and managing multiple instances of DB2 Uniersal Database. Implementing a distributed enironment for the indiidual databases adds a leel of complexity to the creation and configuration of the databases and the Tioli SLM solution. Consult with your database administrator to determine the best solution for IBM Tioli Serice Leel Adisor. For each IBM Tioli Serice Leel Adisor database you create, a minimum amount of space is initially required to hold the database tables. Approximately the same amount of memory is also required. See the Release Notes for IBM Tioli Serice Leel Adisor for recommended hardware and storage requirements, and supported operating systems for SLM databases. Refer also to the official documentation for DB2 Uniersal Database for additional recommendations on hardware requirements. SLM Databases on a z/os Operating System If you plan to install IBM Tioli Serice Leel Adisor in a Tioli Data Warehouse 1.2 enironment, you can optionally create the SLM Database and SLM Measurement Data Mart on a z/os operating system. You might want to do this if you hae a central data warehouse located on a z/os system, though there are no technical restrictions as to where you can locate the two SLM databases. The SLM databases can be located either on a distributed or z/os operating system, and the 16 IBM Tioli Serice Leel Adisor: Getting Started

35 associated target ETLs can extract component type and measurement data from a central data warehouse on either a distributed or z/os operating system. If your Tioli Data Warehouse 1.2 enironment is configured for multiple central data warehouse databases, you only need to configure IBM Tioli Serice Leel Adisor for a multiple central data warehouse enironment if you actually plan to extract data from more than one central data warehouse. If all of your measurement data of interest is located in one central data warehouse, then your IBM Tioli Serice Leel Adisor configuration can ignore any other central data warehouses in the enironment. When you create z/os databases using the IBM Tioli Serice Leel Adisor LaunchPad, you hae the flexibility to choose the database name, and can also specify the tablespace name, storage group name, and the sizes of the target tablespaces, by proiding the following information during database creation: Location (a combination of domain and subsystem names, for example, TVT1064DB71, where TVT1064 is the domain system name and DB71 is one of the DB2 subsystems ) Bufferpool Storage Group name Storage VCat name Storage Volume (you must specify the name of an existing storage olume) Tablespace name (the encoding is the same as the default encoding for the location) UTF8 Tablespace name (the name for the UTF-8 encoded tablespaces) Primary tablespace size Secondary tablespace size You are prompted for this information during the database creation process when you run the LaunchPad installation program for IBM Tioli Serice Leel Adisor. It is assumed that you are familiar with performing the following tasks: Obtaining a TSO user ID Getting a DB2 7.2 for z/os subsystem installed and operational Bringing up TSO to issue DB2 commands and other ISPF commands Knowledge of specific ISPF commands that are used Enabling buffer pools Managing (purging) DB2 logs See your system administrator for assistance in these areas if needed. When creating databases in a z/os enironment, the default database names are DYKCAT and DYKDM, compared to DYK_CAT and DYK_DM in a distributed enironment. Underscore characters are not alid for z/os database names. Deployment Options You can deploy the arious components of IBM Tioli Serice Leel Adisor in different ways according to your enterprise needs and capabilities. Both Tioli Data Warehouse and IBM Tioli Serice Leel Adisor offer many possible combinations of deployment options. You should plan your DB2 installation and the deployment for Tioli Data Warehouse first, because you install those first, and then decide how best to fit IBM Tioli Serice Leel Adisor into the resulting enironment. Chapter 2. Planning Decisions 17

36 A Widely Distributed SLM Deployment A widely distributed SLM solution deployment consists of all (or nearly all) components existing on different machines in your enterprise. This is essentially the deployment suggested in Figure 4 on page 13, with each shaded box in the figure representing a different physical machine. Note that this configuration could be distributed een further by locating the Tioli Data Warehouse data marts and IBM Tioli Serice Leel Adisor databases on separate machines. When considering a widely distributed deployment, be aware of the following information: The source and target ETLs (warehouse packs) must be installed on the same physical machine as the Tioli Data Warehouse control serer, which must be on a supported Windows operating system. The SLM Administration Serer and SLM Reports must be installed on the same physical machine as IBM WebSphere Application Serer, and are installed after IBM WebSphere Application Serer has been installed. You can install each of these SLM components on separate machines, but IBM WebSphere Application Serer must be installed on both machines. If the control serer and the central data warehouse are installed on different machines, the measurement data from source applications that is processed by the source ETLs must trael oer the network from the control serer to the central data warehouse serer machine. Your enterprise should hae the capability to handle large amounts of data transfer between these machines. To aoid this additional load on your network, consider installing the control serer and central data warehouse on the same machine, or, if you do not want to locate your databases on a Windows operating system, you can install a remote agent on the machine where the central data warehouse is located. Refer to the documentation for Tioli Data Warehouse for any additional considerations regarding deployment and operation of the data warehouse enironment. Minimum SLM Deployment For ery small production enironments, you might prefer to install all three of the IBM Tioli Serice Leel Adisor installation features on one machine, with all of the databases on the same machine, as shown in Figure 5 on page 19. When considering a minimum deployment, be aware of the following information: The central data warehouse should reside in a separate DB2 instance from the SLM Database and the SLM Measurement Data Mart application databases. You might prefer to keep warehouse databases separate from application databases, for improed performance and better protection against data loss. With DB2 Uniersal Database you can hae multiple instances on the same physical machine. Because the control serer is only supported on certain Windows operating systems, your single machine deployment is only supported on those operating systems. For the special case where you install IBM WebSphere Application Serer in a Tioli Enterprise Data Warehouse ersion 1.1 enironment (that is, you choose to not upgrade or install Tioli Data Warehouse 1.2), Tioli Presentation Serices (installed as part of Tioli Enterprise Data Warehouse ersion 1.1) and IBM WebSphere Application Serer both use the same IBM HTTP Serer port number 18 IBM Tioli Serice Leel Adisor: Getting Started

37 (80) and IBM HTTP Administration port (8008) by default. For this single machine deployment, you must manually reconfigure one of these applications to use a different set of ports. Figure 5. A minimum SLM Deployment on a single machine. Mid-Sized Deployments There are a number of different possible mid-sized deployments, depending on the requirements of the enterprise. In general, almost any combination of components can be installed alone or with other components. In addition to the restrictions described preiously for minimum and maximum deployments, consider the following recommendations as you plan for a mid-sized deployment: In general, in all but the smallest of production enironments, the central data warehouse should be on a separate physical DB2 serer from the SLM databases to ease in database management, improe performance, and minimize disruption to other applications when the DB2 instance is terminated or shut down for configuration or maintenance. If the central data warehouse is installed on a Windows NT (for Tioli Enterprise Data Warehouse ersion 1.1 only) or Windows 2000 operating system, the control serer can be installed on the same machine. Chapter 2. Planning Decisions 19

38 Because the SLM Administration Serer and SLM Reports options are both installed in a WebSphere enironment, you might prefer to install them on a single WebSphere machine. This also makes it easier to upgrade IBM Tioli Serice Leel Adisor in the future. Unless there is a reason for the SLM Administration Serer or SLM Reports options to be installed on a separate machine from the SLM Serer, you might prefer to install both of these options on the same machine as where the SLM Serer is located. One possible mid-sized deployment based on these considerations is shown in Figure 6, using three separate machines. Figure 6. A sample mid-sized deployment. In a more compact mid-sized deployment, as shown in Figure 7 on page 21, all three components of IBM Tioli Serice Leel Adisor are installed on the same machine. 20 IBM Tioli Serice Leel Adisor: Getting Started

39 Figure 7. Another sample mid-sized deployment. Selecting Port Numbers Additional Deployment Considerations When you install IBM Tioli Serice Leel Adisor, you are gien the option to install the SLM Serer, the SLM Administration Serer, and the SLM Reports on the same physical machine or on multiple machines. In general, installing these options on the same machine helps to centralize the logging information in one place, and also shortens the backup and restore processes. If these options are installed on multiple machines, associated logging information is located on each machine. Backup and restore procedures must be repeated on each machine where an installed SLM option is located. If you install in a distributed enironment, you should install the SLM Serer, the SLM Database, the SLM Measurement Data Mart, and the Central Data Warehouse database of Tioli Data Warehouse on machines that reside in the same time zone, for simplicity. If these components are located on machines in different time zones, you might experience some performance degradation. If you are deploying either the SLM Administration Serer or SLM Reports components of IBM Tioli Serice Leel Adisor in a Tioli Enterprise Data Warehouse ersion 1.1 enironment on a machine that includes Tioli Presentation Serices, you might need to resole IBM HTTP Serer and IBM HTTP Administration port conflicts between Tioli Presentation Serices and IBM WebSphere Application Serer. See Resoling port conflicts on page 192 for details. You must allocate port numbers for Tioli Data Warehouse and for IBM Tioli Serice Leel Adisor for the following purposes: Chapter 2. Planning Decisions 21

40 Communication between the control serer and other components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor installed on different machines Communication among the arious components of IBM Tioli Serice Leel Adisor and its SLM databases, if they are distributed on multiple systems Communication with IBM WebSphere Application Serer in support of the SLM Reports and the SLM Administration Serer components of IBM Tioli Serice Leel Adisor Refer to the Planning chapter of Installing and Configuring Tioli Data Warehouse for specific information on port numbers used by Tioli Data Warehouse. Table 1 through Table 6 on page 24 list the default port numbers that are used by IBM Tioli Serice Leel Adisor. You can choose to accept these defaults or you can specify alternate unused port numbers during the installation process. If you plan to install the SLM Reports or SLM Administration Serer components of IBM Tioli Serice Leel Adisor on the same system where Tioli Presentation Serices is installed, you might hae to resole a port conflict between Tioli Presentation Serices, which might be in use by other applications, and IBM WebSphere Application Serer, which is installed as a prerequisite to installing SLM Reports and the SLM Administration Serer. Both Tioli Presentation Serices and IBM WebSphere Application Serer use the same default port numbers for the IBM HTTP Serer Port (80) and IBM HTTP Administration Port (8008). You should either plan to select a different set of unused ports during the installation of Tioli Data Warehouse, or plan to modify the ports used by IBM WebSphere Application Serer after installation. Table 1. Default port numbers used by IBM Tioli Serice Leel Adisor for Tioli Presentation Serices (with Tioli Enterprise Data Warehouse ersion 1.1) Default port number Name of port in Tioli Data Warehouse InstallShield wizard 1 80 IBM HTTP Serer Port 8008 IBM HTTP Administration Port 8008 IBM HTTP Administration Port Description Used by Tioli Presentation Serices HTTP Serer for HTTP communications Used by Tioli Presentation Serices for HTTP Administration Used by IBM WebSphere Application Serer for HTTP Administration Can this default be changed? Yes, during the installation of the report interface component of Tioli Data Warehouse or by editing the properties file manually after installation 2 Yes, during the installation of the report interface component of Tioli Data Warehouse or by editing the properties file manually after installation 2 Yes, after installing IBM WebSphere Application Serer by editing the properties file 2 1 Refer to Installing and Configuring Tioli Data Warehouse for additional ports used during installation. 2 You only need to modify this port number if there is a conflict between Tioli Presentation Serices (with Tioli Enterprise Data Warehouse ersion 1.1) and IBM WebSphere Application Serer on the same system. 22 IBM Tioli Serice Leel Adisor: Getting Started

41 Table 2. Default port numbers used by IBM Tioli Serice Leel Adisor for IBM WebSphere Application Serer (with SLM Reports and SLM Administration Serer) Default port number Name of port used by WebSphere installation process 80 IBM HTTP Serer Port 8008 IBM HTTP Administration Port Description Used by IBM WebSphere Application Serer for HTTP communications Used by IBM WebSphere Application Serer for HTTP Administration Can this default be changed? Yes, after installing IBM WebSphere Application Serer by editing the properties file 1 Yes, after installing IBM WebSphere Application Serer by editing the properties file 1 1 You only need to modify this port number if there is a conflict between Tioli Presentation Serices (with Tioli Enterprise Data Warehouse ersion 1.1) and IBM WebSphere Application Serer on the same system. Table 3. Default port numbers used by IBM Tioli Serice Leel Adisor for the SLM Database and SLM Measurement Data Mart DB2 databases Default port number Name of port used in installation scripts DB2 Communication port Description Used by DB2 Uniersal Database for communication with remote databases. This alue is assumed in the installation scripts and ODBC datasource creation scripts, and is specified during installation of SLM components. Can this default be changed? Yes, by editing the fields in the installation panel before creating SLM databases, and by editing the ODBC script files before running them to create ODBC datasources. Table 4. Default port numbers used by IBM Tioli Serice Leel Adisor for the SLM Database and SLM Measurement Data Mart DB2 databases Default port number Name of port used in installation scripts DB2 Communication port Description Used by DB2 Uniersal Database for communication with remote databases. This alue is assumed in the installation scripts and ODBC datasource creation scripts, and is specified during installation of SLM components. Can this default be changed? Yes, by editing the fields in the installation panel before creating SLM databases, and by editing the ODBC script files before running them to create ODBC datasources. Chapter 2. Planning Decisions 23

42 Table 5. Default port numbers used by IBM Tioli Serice Leel Adisor for the SLM Serer, SLM Administration Serer and SLM Reports components of IBM Tioli Serice Leel Adisor Default port number Name of port used in InstallShield wizard 9980 SLM Serer Communication Port 80 SLM Administration Serer and SLM Reports Communication Port 9990 Command Line Interface Port Description This is the port used for communication between the SLM Serer and other components. This is the default port specified when bringing up the SLM Administratie Console or SLM Reports console in your Web browser. This is the port used for communication with the Command Line Interface. Can this default be changed? Yes, this port number can be set during IBM Tioli Serice Leel Adisor installation. When components of IBM Tioli Serice Leel Adisor are installed on separate machines, this port number must be the same on all machines. This port number is set to the default alue when you regenerate the HTTP plug-in configuration as part of the installation procedure. This is the only port number supported by WebSphere Application Serer for use with the SLM Administratie Console and SLM Reports console. Yes, this port can be set during IBM Tioli Serice Leel Adisor installation. Table 6. Default port numbers used by IBM Tioli Serice Leel Adisor for eent notification Default port number Name of port used in InstallShield wizard 162 SNMP Trap Destination Port 5529 Tioli Enterprise Console Eent Serer Port (Windows only) Description This is the SNMP Trap destination port used by the SNMP Trap option for eent notification. This is the port that the Tioli Enterprise Console Eent Serer listens to for eents. Can this default be changed? Yes, but you must manually set this port number to another alue before running the IBM Tioli Serice Leel Adisor installation program. Consult your SNMP documentation for details. Yes, but you must manually set this port number to another alue before running the IBM Tioli Serice Leel Adisor installation program. Consult your Tioli Enterprise Console documentation for details. Coexistence with Other DB2 Database Applications Tioli Data Warehouse uses the following databases: 24 IBM Tioli Serice Leel Adisor: Getting Started

43 TWH_MD The control database on the control serer TWH_CDW The central data warehouse database TWH_MART The data mart database IBM Tioli Serice Leel Adisor uses the following databases: DYK_CAT The SLM Database (on z/os operating systems, this database is named DYKCAT) DYK_DM The SLM Measurement Data Mart (on z/os operating systems, this database is named DYKDM) If you are installing IBM Tioli Serice Leel Adisor in an existing DB2 instance, make sure that databases with these names do not already exist. Information to Gather Before Installing The following tables can be used as a set of worksheets to help you gather the information you need when you install IBM Tioli Serice Leel Adisor and the supporting applications. Information for All Installations Fill out Table 7 for all installations of IBM Tioli Serice Leel Adisor. Table 7. Information for all installations Information needed Do you want to install to a single system or to a distributed system? Do you want IBM Tioli Serice Leel Adisor to proide support for languages other than English? Why you need to know Determines which checklist to refer to after completing this checklist. Refer to the checklists in the following tables: For single system installations, use Table 8 on page 30. For distributed installations, use Table 9 on page 30 and Table 10 on page 32. If so, select the language support that you want to include during the installation of IBM Tioli Serice Leel Adisor. Record your information here Chapter 2. Planning Decisions 25

44 Table 7. Information for all installations (continued) Information needed Can each system proide fully qualified hostnames? Does each system hae the required hardware and software prerequisites, including patch leels? Did you check the Web site for the most current information about prerequisites and required serice? Is DB2 Uniersal Database installed on all target systems? Why you need to know This function is required for all systems where components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor are installed. Refer to Ensuring fully qualified hostnames on page 186 for details on ensuring fully qualified hostnames. It is difficult to debug installation problems that result from missing prerequisites. Refer to the Release Notes for IBM Tioli Serice Leel Adisor for information on hardware and software prerequisites and patch leels. It is difficult to debug installation problems that result from missing prerequisites. Refer to Release Notes for IBM Tioli Serice Leel Adisor for the location of the Web site. If it is, check the ersion and configuration of DB2 Uniersal Database to assure a successful installation of IBM Tioli Serice Leel Adisor, and also check for database name conflicts (see Coexistence with Other DB2 Database Applications on page 24 If not, install it as described in Considerations for Installing DB2 Uniersal Database on page 38, referring to specific DB2 installation information in the Tioli Data Warehouse documentation as needed. You might also need to upgrade DB2 Uniersal Database to a supported ersion. See the Release Notes for specific information on supported upgrade ersions. Record your information here 26 IBM Tioli Serice Leel Adisor: Getting Started

45 Table 7. Information for all installations (continued) Information needed Is Tioli Data Warehouse already installed in your enterprise? Is IBM WebSphere Application Serer already installed in your enterprise? Do you plan to enable WebSphere security? If you are installing the SLM Administration Serer or SLM Reports on this machine, what user name will you want to specify for SLM Administrator authority or to access SLM Reports? Why you need to know If it is, check the ersion and configuration to assure a successful installation of IBM Tioli Serice Leel Adisor. If not, install it as described in Considerations for Installing Tioli Data Warehouse on page 43, referring to specific installation information in the Tioli Data Warehouse documentation as needed. If it is, check the ersion and configuration to assure a successful installation of IBM Tioli Serice Leel Adisor. You might need to upgrade to a supported ersion. If not, install it AFTER installing DB2 Uniersal Database and Tioli Data Warehouse, as described in Installing IBM WebSphere Application Serer on page 45. If you enable WebSphere security, you are prompted for a alid user name and password that has WebSphere administrator authority when you install IBM Tioli Serice Leel Adisor. During the installation of IBM Tioli Serice Leel Adisor, you are prompted for the user name that will be assigned the role of SLM Administrator, if you are installing the SLM Administration Serer. If you are installing SLM Reports on this machine, this user name will be gien access to that console as well. Record your information here Chapter 2. Planning Decisions 27

46 Table 7. Information for all installations (continued) Information needed If installing on a UNIX system, are you the root user? Why you need to know These are required in order to run the installation program. Record your information here If installing on a Windows system, do you hae Administrator priileges? Target directory for the Tioli Common Directory Destination directory where you plan to install IBM Tioli Serice Leel Adisor If IBM Tioli Serice Leel Adisor is the first Tioli application to be installed on this machine, the Tioli Common Directory is created for Tioli applications to place logs and message files in a common location. If it is not the first Tioli application installed, the installation wizard detects the location for you. You are prompted for this during the installation process. Typically the installation directory for IBM Tioli Serice Leel Adisor is specified in the following form: For Windows: C:\Program Files\TSLA For UNIX: /opt/tsla 28 IBM Tioli Serice Leel Adisor: Getting Started

47 Table 7. Information for all installations (continued) Information needed If you are installing into a Tioli Enterprise Data Warehouse 1.1 enironment, on what machines is Tioli Presentation Serices installed? If you are installing into a Tioli Data Warehouse 1.2 enironment, this question does not apply. If you plan to enable eent notification, which techniques are you using: SNMP trap TEC Eent If you selected eent notification, specify the following parameters: SMTP Serer hostname One or more addresses to send eent information to Optionally, one or more addresses to be included in the CC-List for the If you selected SNMP Trap eent notification, specify the following parameters: Fully qualified destination hostname of the receiing SNMP management station SNMP Trap destination port number (default is 162) Optionally, the community name of the trap serice Why you need to know Though IBM Tioli Serice Leel Adisor does not use Tioli Presentation Serices, if Tioli Presentation Serices is installed on the same machine where you plan to install IBM WebSphere Application Serer in support of the SLM Reports or SLM Administration Serer, you might need to resole port conflicts, making sure that port numbers used by Tioli Presentation Serices and IBM WebSphere Application Serer for IBM HTTP Serer and IBM HTTP Administration are unique. Default alues for both products are: IBM HTTP Serer: 80 IBM HTTP Administration: 8008 You need to specify additional installation information if one or more of these types of eent enablement are enabled. This information is used in constructing the s to be sent with eent information to personnel responsible for monitoring and managing eent notifications. This information defines where SNMP trap eents are to be sent for handling. Record your information here Chapter 2. Planning Decisions 29

48 Table 7. Information for all installations (continued) Information needed If you selected Tioli Enterprise Console Eent notification, specify the following parameters: Hostname where the eent serer is installed If the eent serer is on a Windows-based machine, the port number the system listens to for eents (default is 5529) Why you need to know This information defines where Tioli Enterprise Console eents are to be sent for handling. Record your information here Additional Information for Single System Installations Fill out Table 8 for single system installations of IBM Tioli Serice Leel Adisor. Table 8. Additional information for single-system installations Information needed Fully qualified hostname of the system to install on User name and password to access the existing DB2 instance on the system Why you need to know Refer to Ensuring fully qualified hostnames on page 186 for information on ensuring fully qualified hostnames. Get the DB2 user name and password from the person who installed or administers the database. Record your information here Additional Information for Distributed Installations Fill out Table 9 and Table 10 on page 32 for distributed installations of IBM Tioli Serice Leel Adisor. Table 9 includes connection information for components installed on other systems. This information is not required if components are installed on the same system. Table 10 on page 32 includes connection information for the SLM Administration Serer and SLM Reports when installed on systems different from where the SLM Serer is located Table 9. Additional information for distributed installations Remote component SLM Serer Information needed Fully qualified hostname DB2 user ID and password for the existing DB2 instance on the serer machine where the SLM databases are located Database port number (default is 50000) Record your information here 30 IBM Tioli Serice Leel Adisor: Getting Started

49 Table 9. Additional information for distributed installations (continued) Remote component SLM Administration Serer SLM Reports SLM Database Information needed Fully qualified hostname DB2 user ID and password for the existing DB2 instance on the serer machine where the SLM databases are located Database port number (default is 50000) Fully qualified hostname DB2 user ID and password for the existing DB2 instance on the serer machine where the SLM databases are located Database port number (default is 50000) Fully qualified hostname DB2 user ID and password for the existing DB2 instance on the machine where the SLM Database is installed (the SLM Database and SLM Measurement Data Mart should be created in the same DB2 instance) Database port number (default is 50000) If the database is located on a z/os operating system, additional information is needed, including: Location Bufferpool Storage Group Storage VCat Storage Volume Tablespace name UTF8 Tablespace name Tablespace Size Primary Tablespace Size Secondary Record your information here Chapter 2. Planning Decisions 31

50 Table 9. Additional information for distributed installations (continued) Remote component SLM Measurement Data Mart Information needed Fully qualified hostname DB2 user ID and password for the existing DB2 instance on the machine where the SLM Measurement Data Mart will be installed (the SLM Database and SLM Measurement Data Mart should be created in the same DB2 instance) Database port number (default is 50000) If the database is located on a z/os operating system, additional information is needed, including: Location Bufferpool Storage Group Storage VCat Storage Volume Tablespace name UTF8 Tablespace name Tablespace Size Primary Tablespace Size Secondary Record your information here Table 10. Additional information for distributed installations for SLM Administration Serer and SLM Reports when installed on systems different from where the SLM Serer is located Information needed If you are installing the SLM Administration Serer or the SLM Reports component on a different system from the SLM Serer, specify the following parameters: Fully qualified hostname of the system where the SLM Serer is installed The SLM Serer communication port (default is 9980) Why you need to know This information is needed for the SLM Administration Serer and SLM Reports components of IBM Tioli Serice Leel Adisor to communicate with the SLM Serer when it is installed on a remote system. Record your information here Planning for Warehouse Packs The warehouse packs for the source and target ETLs for IBM Tioli Serice Leel Adisor are included on the installation media for IBM Tioli Serice Leel Adisor. 32 IBM Tioli Serice Leel Adisor: Getting Started

51 You use the warehouse pack installation program proided with the Tioli Data Warehouse installation to install the IBM Tioli Serice Leel Adisor warehouse packs, after the installation of the IBM Tioli Serice Leel Adisor product has completed successfully. See Installing the Target Warehouse Enablement Pack on page 89 and Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105 for more information. Warehouse packs for other source applications that write data into Tioli Data Warehouse are installed using the procedures documented in the enablement guide that accompanies the warehouse pack. Chapter 2. Planning Decisions 33

52 34 IBM Tioli Serice Leel Adisor: Getting Started

53 Chapter 3. Prerequisite Software Before installing IBM Tioli Serice Leel Adisor, you must already hae successfully installed and configured the following prerequisite supporting applications: IBM DB2 Uniersal Database Enterprise Edition (DB2 Uniersal Database) The minimum supported ersion of DB2 Uniersal Database is ersion 7.2 with Fix Pack 8 or Fix Pack 10, plus an additional special fix. The ersion with Fix Pack 10 is the ersion of DB2 Uniersal Database that is shipped with Tioli Data Warehouse 1.2. If you hae a preious ersion of DB2 Uniersal Database installed, you must upgrade to at least this leel on eery computer where a component of Tioli Data Warehouse 1.2 is located, or where components of IBM Tioli Serice Leel Adisor 2.1 are located. For computers that will only hae components of IBM Tioli Serice Leel Adisor installed, you can use additional supported ersions of DB2 Uniersal Database, but you might also need to perform additional configuration steps to communicate between the different ersions of DB2 Uniersal Database across multiple computers. If you are installing IBM Tioli Serice Leel Adisor databases on a z/os operating system, erify that you hae a supported ersion of DB2 Uniersal Database for z/os installed. See the Release Notes for information about supported ersions of DB2 Uniersal Database for these distributed enironments. Tioli Data Warehouse IBM Tioli Serice Leel Adisor can operate with either of the following ersions of Tioli Data Warehouse: An existing ersion of Tioli Enterprise Data Warehouse ersion 1.1, upgraded to at least the Fix Pack 3 leel Tioli Data Warehouse 1.2 If you hae Tioli Enterprise Data Warehouse ersion 1.1 already installed, and do not want to upgrade to Tioli Data Warehouse ersion 1.2, your existing ersion must be upgraded to at least the Fix Pack 3 leel to operate with this ersion of IBM Tioli Serice Leel Adisor. You can download this required upgrade from the Tioli Data Warehouse support Web site if needed. If you want to take adantage of the latest functions of Tioli Data Warehouse, you must upgrade to, or install ersion 1.2. Tioli Data Warehouse ersion 1.2 includes the integration of Crystal Enterprise software, which is used for Tioli Data Warehouse reporting functions. If you hae a preious ersion of Tioli Enterprise Data Warehouse installed that uses the built in reporting interface with the IBM Console, reports are automatically conerted to the Crystal Enterprise format. This ersion of IBM Tioli Serice Leel Adisor does not use Crystal Enterprise software for its reporting interface, though you might want to use it with other applications that take adantage of the Tioli Data Warehouse reporting function. Crystal Enterprise software is required to be installed as part of the installation of Tioli Data Warehouse 1.2. Source Application Warehouse Enablement Packs After you successfully install Tioli Data Warehouse, you should install and configure any source application warehouse packs that enable source applications to write data into Tioli Data Warehouse. Consult your source application documentation for the enablement guide that includes the Copyright IBM Corp. 2002,

54 procedures for installing warehouse packs. Also refer to Installing and Configuring Tioli Data Warehouse for additional information on warehouse packs. IBM WebSphere Application Serer This release of IBM Tioli Serice Leel Adisor might require you to upgrade an existing installed ersion of IBM WebSphere Application Serer to the minimum supported leel. If you do not hae an existing supported ersion of IBM WebSphere Application Serer, you can install the base ersion that is proided with IBM Tioli Serice Leel Adisor, and upgrade to the minimum supported ersion by downloading the upgrade software from the IBM WebSphere support Web site. See the Release Notes for IBM Tioli Serice Leel Adisor for additional information about supported ersions of IBM WebSphere Application Serer on specific supported operating systems. Installation procedures for DB2 Uniersal Database, Tioli Data Warehouse, and Crystal Enterprise are fully documented in Installing and Configuring Tioli Data Warehouse. Follow the instructions proided there to install these applications in either a single-system quick start deployment, or in a more complex distributed enironment across multiple machines. For production enironments you should follow the distributed installation procedures, placing your serers and databases on Windows, UNIX, and z/os operating systems as needed for your enterprise. The quick start installation is designed for demonstration, educational or test usage, or for small enterprises that do not plan to capture and analyze large amounts of data. You can install een more sophisticated distributed installations, with multiple central data warehouse and data mart databases, and optionally install remote warehouse agent software that speeds data transfer and reduces the workload on the control serer for Tioli Data Warehouse. Installation procedures for IBM WebSphere Application Serer are aailable with the product, as well as on the WebSphere support Web site. See IBM WebSphere Application Serer library on page ix for details, and refer to Installing IBM WebSphere Application Serer on page 45 for additional considerations. Seeral example configurations and installation scenarios are described in the appendices in this document. You might want to refer to these sample installation scenarios for guidance as you plan your own installation. Do not attempt to install IBM Tioli Serice Leel Adisor until you successfully hae completed the following steps: 1. Read through the planning information, complete the arious worksheets that apply to your enironment, and decide how you will distribute the serers and databases that are part of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor. 2. Install DB2 serer or client software on each system where you plan to locate the arious components of Tioli Data Warehouse, Crystal Enterprise, and IBM Tioli Serice Leel Adisor. Table 11 on page 37 specifies which components of Tioli Data Warehouse, Crystal Enterprise, and IBM Tioli Serice Leel Adisor can run on a DB2 client or the full DB2 Uniersal Database serer, and supported operating system types. Refer to the Release Notes for these products for specific supported operating system ersions. 36 IBM Tioli Serice Leel Adisor: Getting Started

55 Table 11. Supported operating systems and DB2 components for a distributed installation Component Supported operating system 1 DB2 components required For Crystal Enterprise: Crystal Enterprise serer Windows DB2 Uniersal Database or a DB2 Client For Tioli Data Warehouse: Control serer Windows DB2 Uniersal Database Central data warehouse Windows, AIX, Solaris Operating Enironment, z/os DB2 Uniersal Database, DB2 Warehouse Manager 2 Data mart databases Windows, AIX, Solaris, z/os DB2 Uniersal Database, DB2 Warehouse Manager 2 Warehouse agent sites Windows, AIX, Solaris DB2 Uniersal Database, DB2 Warehouse Manager 2 For IBM Tioli Serice Leel Adisor: SLM Serer SLM Administration Serer SLM Reports Windows, AIX, Solaris, Linux, HP Windows, AIX, Solaris, Linux, HP Windows, AIX, Solaris, Linux, HP DB2 Uniersal Database or a DB2 Client DB2 Uniersal Database or a DB2 Client DB2 Uniersal Database or a DB2 Client SLM Database Windows, AIX, Solaris, z/os DB2 Uniersal Database SLM Measurement Data Mart Windows, AIX, Solaris, z/os DB2 Uniersal Database 1 See the Release Notes for each application for complete details about supported operating system ersions and prerequisites. 2 DB2 Warehouse Manager is required only on remote computers where you are creating a warehouse agent site. To install DB2 Uniersal Database on UNIX systems, refer to IBM DB2 Uniersal Database for UNIX Quick Beginnings, and for a more adanced installation on Windows systems, see IBM DB2 Uniersal Database Enterprise - Extended Edition for Windows Quick Beginnings. UNIX operating systems might need to be tuned to run DB2 Uniersal Database. If the operating system is not tuned correctly, sporadic connection failures and other misleading errors might occur. Refer to information about updating configuration parameters in these manuals for more information. Note: IBM Tioli Serice Leel Adisor also requires that all databases be enabled for log roll-forward which is used in the backup recoery procedure. 3. Install Tioli Data Warehouse components, either on a single system (quick start installation) or distributed across multiple systems. Note: Part of the installation of Tioli Data Warehouse includes data mart databases, which are not used by IBM Tioli Serice Leel Adisor. The installation of IBM Tioli Serice Leel Adisor includes its own data mart databases, installed separately from this installation of Tioli Data Warehouse. 4. After successfully installing Tioli Data Warehouse, install the source ETL (warehouse packs) for each Tioli performance and aailability application that will be writing measurement data to the central data warehouse. These Chapter 3. Prerequisite Software 37

56 warehouse packs are installed on the same machine as the control serer, which uses the Data Warehouse Center component of DB2 Uniersal Database. Installation and configuration procedures for the warehouse packs are included on the warehouse pack installation media. 5. Verify that the operational data that is collected by the source applications is being successfully written into the warehouse, and that source ETLs are scheduled and running properly. Completing the aboe steps ensures that when you do install IBM WebSphere Application Serer and IBM Tioli Serice Leel Adisor and its associated databases and warehouse pack software, alid serice leel agreements can be created and useful data can be extracted from the warehouse database and analyzed for IBM Tioli Serice Leel Adisor reports. Upgrading From Preious Versions You might already hae preious ersions of DB2 Uniersal Database, Tioli Data Warehouse, IBM WebSphere Application Serer, IBM Tioli Serice Leel Adisor databases, or warehouse packs installed in your enterprise. You might also be running on an operating system that is no longer supported for this release (for example, you might need to upgrade from Windows NT to Windows 2000, because Windows NT is no longer supported in this release). In some cases you might need to upgrade or upgrade to a more recent supported ersion for proper operation of IBM Tioli Serice Leel Adisor. Refer to the Release Notes to information on supported operating system ersions, and see Appendix H, Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor, on page 199 for information on specific ersions of prerequisites needed, then plan to upgrade your existing installation as needed. As you upgrade operating systems and prerequisite software in preparation for installing IBM Tioli Serice Leel Adisor, be aware of other applications on your machines that might also depend on specific ersions of the operating system or upgraded prerequisite applications, and plan your upgrade accordingly. Considerations for Installing DB2 Uniersal Database Before you install DB2 Uniersal Database on any system, you should hae a clear understanding of the distribution of systems within your enterprise that contain the major components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor. Both Tioli Data Warehouse and IBM Tioli Serice Leel Adisor require DB2 Uniersal Database to be installed on all machines where these products are installed, in either single-system or distributed configurations. If you already hae Tioli Data Warehouse installed in your enterprise enironment, you hae installed DB2 Uniersal Database on eery machine where one or more components of Tioli Data Warehouse are located. When you later install IBM Tioli Serice Leel Adisor components into this enironment, you can choose to locate one or more components of IBM Tioli Serice Leel Adisor on these same machines, or on additional machines in a more distributed configuration. If you choose to install IBM Tioli Serice Leel Adisor on additional machines, you must also install DB2 Uniersal Database on these machines to communicate with Tioli Data Warehouse. You can follow the same procedures for installing DB2 Uniersal Database on these machines as documented in Installing and Configuring Tioli Data Warehouse. 38 IBM Tioli Serice Leel Adisor: Getting Started

57 Reading the Documentation If you hae not already done so, be sure to read and become thoroughly familiar with the information in the Oeriew and Planning chapters of Installing and Configuring Tioli Data Warehouse, which discuss the arious major components of Tioli Data Warehouse, and information that you need to know to determine how to distribute the arious components of Tioli Data Warehouse in your enironment. As you read this information, also keep in mind the arious installation features of IBM Tioli Serice Leel Adisor, so they can readily integrate into your established warehouse enironment. In particular, be sure to read and understand the following topics: Completing the planning worksheets for your deployment Making sure that you log on to the computer with sufficient authority Verifying that each computer that includes components of Tioli Data Warehouse, IBM Tioli Serice Leel Adisor, and Crystal Enterprise is configured to proide unique fully qualified hostnames rather than a short name Procedures for mounting CD-ROM deices on UNIX systems Procedures for starting a DB2 command prompt on Windows systems, or sourcing a db2profile on UNIX systems Procedure for determining the leel of DB2 Uniersal Database that is currently installed Some of this information is described in Appendix B of Installing and Configuring Tioli Data Warehouse. Additional useful information can be found in the DB2 Quick Beginnings document for the operating system on which you are installing. In addition to the aboe documentation, you should already hae read Chapter 2, Planning Decisions, on page 9 in this document and completed the planning checklists to make sure you hae all of the information you need to perform the installation for IBM Tioli Serice Leel Adisor. Also, for conenience, additional hints and tips can be found in Appendix G, Installation Hints and Tips, on page 183. Installing DB2 Serer or Client Table 11 on page 37 specifies which components of Tioli Data Warehouse and IBM Tioli Serice Leel Adisor can run on a DB2 client or serer, and supported operating system types. Refer to the Release Notes for both products for specific supported operating system ersions. For the case where you hae Tioli Enterprise Data Warehouse 1.1 components installed on machines where you do not plan to upgrade to ersion 1.2 and you do not plan to install a component of IBM Tioli Serice Leel Adisor 2.1, the existing DB2 ersion on these machines should still be upgraded to at least Fix Pack 8 plus the special fix, to take adantage of additional security features that are aailable. For the case where you hae different supported ersions of DB2 Uniersal Database installed on multiple machines (for example, DB2 7.2 with Fix Pack 8 plus the special fix on machines with Tioli Data Warehouse components, and DB2 8.1 on machines with IBM Tioli Serice Leel Adisor components), you must perform additional steps to define a local agent to communicate between these machines. Using Table 11 on page 37, for a single system installation, or for components requiring a DB2 Serer in a distributed enironment, when you run the DB2 Chapter 3. Prerequisite Software 39

58 Uniersal Database installation program, install the DB2 Serer by selecting the DB2 Enterprise Edition installation option. For components in a distributed enironment that can run on a DB2 Client, you can select any of the following installation options: DB2 Enterprise Edition DB2 Application Deelopment Client DB2 Administration Client (this is the smallest client) Note: The run-time client is not supported. If you are installing DB2 Uniersal Database on a Windows system where you plan to install the SLM Serer option of IBM Tioli Serice Leel Adisor, be sure to reboot the machine after the installation of DB2 Uniersal Database is complete. Considerations for Databases Depending on how you want to deploy the IBM Tioli Serice Leel Adisor SLM databases (the SLM Database and SLM Measurement Data Mart), you might need to install DB2 on one or more additional machines, or create multiple DB2 instances on one or more machines, or set up a serer-client configuration between machines. Consult the DB2 documentation for information on installing and configuring DB2 Uniersal Database in these circumstances. Possible configurations might include the following options: If you plan to locate the SLM Database and SLM Measurement Data Mart together on a separate machine from the central data warehouse, install DB2 Uniersal Database on both machines. If you plan to locate the SLM Database and SLM Measurement Data Mart on the same machine where the central data warehouse is installed, but with the two SLM databases together in a separate instance of DB2 Uniersal Database, install DB2 Uniersal Database on that machine and create two DB2 instances, one for the central data warehouse and the other for the two SLM databases. If you plan to locate the SLM Database and SLM Measurement Data Mart on the central data warehouse machine, but each in their own instance of DB2, create those instances on that machine. Although it is possible to create the two SLM databases each in their own separate DB2 instance, it is not recommended. The preferred configuration is to hae these two databases in the same DB2 Uniersal Database instance. Consult the DB2 Uniersal Database documentation for additional configuration steps if needed. If you plan to locate the SLM Database and SLM Measurement Data Mart on two separate machines, install DB2 Uniersal Database on each of those machines. These two databases should be created on the same machine in a single DB2 Uniersal Database instance. If you must split them into separate machines, consult the DB2 Uniersal Database documentation for additional configuration steps if needed. Installing Databases on z/os or OS/390 You can locate either or both of the SLM databases on distributed or z/os operating systems. In general if you hae a central data warehouse located on a z/os operating system, and you plan to extract data from this central data warehouse to use with IBM Tioli Serice Leel Adisor, you might prefer to also locate the SLM databases on a z/os operating system as well, though this is not a requirement. If you plan to operate in a multiple central data warehouse enironment, and plan to extract data from multiple central data warehouses, on either distributed or z/os operating systems or both, you can locate the SLM databases on any operating system (though, again, you might prefer to locate them 40 IBM Tioli Serice Leel Adisor: Getting Started

59 on a z/os operating system if one of the central data warehouses of interest is located on a z/os operating system as well). When accessing DB2 databases remotely on OS/390 or z/os operating systems through a distributed configuration, you must hae DB2 Connect installed so that the administration client can access the database. DB2 Connect is used to connect to databases running on OS/390 and z/os operating systems, and is included with the IBM DB2 Uniersal Database Enterprise Serer Edition and IBM DB2 Uniersal Database Enterprise Edition. It is not installed as part of any DB2 client or administration client software. When installing databases on z/os or OS/390 operating systems, consider the following restrictions: To install the SLM Database or SLM Measurement Data Mart on an OS/390 or z/os operating system from a remote Windows or UNIX machine, you must first install IBM DB2 Uniersal Database Enterprise Edition on the remote Windows or UNIX machine. The libraries required to create and connect to a DB2 database on a z/os or OS/390 operating system are included in IBM DB2 Uniersal Database Enterprise Edition. After the databases hae been created on a z/os or OS/390 operating system, install IBM Tioli Serice Leel Adisor in a distributed configuration. Install the SLM Serer, SLM Administration Serer, and SLM Reports options on any machine that has either DB2 Connect installed or IBM DB2 Uniersal Database Enterprise Edition installed. Installing DB2 Uniersal Database on UNIX Systems To install DB2 Uniersal Database on UNIX systems, refer to IBM DB2 Uniersal Database for UNIX Quick Beginnings, and for a more adanced installation on Windows systems, see IBM DB2 Uniersal Database Enterprise - Extended Edition for Windows Quick Beginnings. UNIX operating systems might need to be tuned to run DB2 Uniersal Database. If the operating system is not tuned correctly, sporadic connection failures and other misleading errors might occur. Refer to information about updating configuration parameters in these manuals for more information. Installing DB2 Uniersal Database on Red Hat 3.0 To successfully install DB2 Uniersal Database on Red Hat 3.0 operating systems, be sure to complete the following steps before running the db2setup installation program: 1. Install the appropriate IBM Deeloper Kit for Linux, ersion 1.4.1, obtained from the following Web site: 2. If you are installing DB2 Uniersal Database ersion 8.1.4, set the following enironment ariables: export DB2USELOCALJRE=TRUE export JAVA_HOME=<path to 14x JVM> Then run the db2setup installation program from this command window. 3. If you are installing the ersion of DB2 Uniersal Database that is proided with IBM Tioli Serice Leel Adisor, complete the following steps: a. Copy the installation image from the CD to your local hard drie b. Delete the db2/linux/jaa directory c. Create a symbolic link called jaa to Jaa 14x. For example: Chapter 3. Prerequisite Software 41

60 ln -s /opt/ibmjaa2-141 <db2image dir>/db2/linux/jaa d. Verify that the DISPLAY ariable is properly exported e. Start the db2setup installation program. Connecting a Database on DB2 7.2 Serer to a DB2 8.1 Client In general, to create remote databases on a DB2 serer from a DB2 client, both client and serer machines must be at the same DB2 leel. If you are planning a distributed installation of IBM Tioli Serice Leel Adisor, with SLM databases (DYK_CAT or DYK_DM) installed on a DB2 serer machine at ersion 7.2 with Fix Pack 8 (plus the associated special fix), and the SLM Serer on a separate DB2 client machine at ersion 8.1, you must perform some manual configuration steps to enable communication between these two different supported ersions of DB2 Uniersal Database. See Connecting a DB2 7.2 Database with a DB2 8.1 Client on page 196 for the procedure. Note: This additional configuration must be completed before installing IBM Tioli Serice Leel Adisor. You cannot create remote DB2 databases on a DB2 ersion 8 serer from a DB2 ersion 7 client (nor can you create remote DB2 databases on a DB2 ersion 7 serer from a DB2 ersion 8 client). If you want to create remote DB2 databases, the DB2 ersion on both the serer and client must be the same. See the Release Notes for both IBM Tioli Serice Leel Adisor and IBM DB2 Uniersal Database Enterprise Edition (ersion 8) for more information. Updating the JDBC Leel for DB2 Uniersal Database By default, ersion 7.2 of the DB2 Uniersal Database database management system serer uses the JDBC 1.1 driers for JDBC applications. IBM Tioli Serice Leel Adisor requires DB2 Uniersal Database to use the JDBC 2.0 driers. If the DB2 serer uses different leels of the JDBC drier than the clients, unpredictable results occur and IBM Tioli Serice Leel Adisor might encounter database errors. IBM Tioli Serice Leel Adisor automatically updates the JDBC leel to JDBC 2.0 during the installation procedure. For those machines in a distributed installation that hae Tioli Data Warehouse components but not IBM Tioli Serice Leel Adisor, you might need to manually update the JDBC leel to 2.0 if you are using IBM DB2 ersion 7. Note: This does not apply to Linux on z/os operating systems. To erify the JDBC leel or to manually update the JDBC leel, see Updating the JDBC Leel for DB2 on page 189. Configuring the Database Manager to use Extended Shared Memory To aoid problems with DB2 Uniersal Database exhausting its shared memory segments on AIX systems, configure the database manager to use extended shared memory. This is especially important if the SLM databases reside on the same machine with any of the installation options of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Administration Serer, or SLM Reports). To configure for extended shared memory, see Configuring the Database Manager to use Extended Shared Memory on page IBM Tioli Serice Leel Adisor: Getting Started

61 Considerations for Installing Tioli Data Warehouse The installation and configuration of Tioli Data Warehouse 1.2 is fully documented in Installing and Configuring Tioli Data Warehouse. This document includes procedures for installing and configuring the arious components of Tioli Data Warehouse on a single system or distributed across multiple systems, including the following components: The Crystal Enterprise serer, used for Tioli Data Warehouse reporting functions. This ersion of IBM Tioli Serice Leel Adisor uses its own reporting interface for generating reports of iolations and trends, but Crystal Enterprise must still be installed in your enterprise before Tioli Data Warehouse 1.2 is installed. The Tioli performance and aailability schema, or data model, to configure the Tioli Data Warehouse database for use by the source applications and IBM Tioli Serice Leel Adisor. The control serer, the central data warehouse, and the data mart database. You can create multiple central data warehouse databases and data mart databases. Complete the procedures for installing Tioli Data Warehouse in any of the following configurations: Installing a quick start deployment to install all components of Tioli Data Warehouse on a single machine for educational purposes or ery small production deployments Installing in a distributed enironment that does not use remote agents Installing in a distributed enironment that uses remote agents Note: In each of these installation procedures, there is a step for creating an ODBC connection from the Crystal Enterprise serer to the data marts. This step is only needed if you are setting up Tioli Data Warehouse for source applications that hae reporting data marts. This step is not needed for IBM Tioli Serice Leel Adisor, and can be skipped. Considerations for Configuring an Enironment with Multiple Central Data Warehouse Databases If you are planning to use Tioli Data Warehouse 1.2, you can configure more than one central data warehouse to proide data to IBM Tioli Serice Leel Adisor (this is not alid for Tioli Enterprise Data Warehouse 1.1, which only supports a single central data warehouse). If you are planning to use more than one central data warehouse to proide component and measurement data to IBM Tioli Serice Leel Adisor, keep in mind the following considerations: Tioli Data Warehouse 1.2 proides a utility that you can use to add additional central data warehouse databases to the enironment (if not already created). The additional central data warehouse databases hae database names such as TCDW1 or TCDW2, and associated ODBC data source names hae names such as TWH_CDW1 or TWH_CDW2, and so on. You need to use the twh_configwep utility to configure the IBM Tioli Serice Leel Adisor target ETL to extract data from more than one central data warehouse. This is described in more detail in Configuring for Multiple Central Data Warehouses on page 99. IBM Tioli Serice Leel Adisor proides two target warehouse packs, one for Tioli Enterprise Data Warehouse 1.1, and the other for Tioli Data Warehouse 1.2. Only the target warehouse pack for Tioli Data Warehouse 1.2 includes support for multiple central data warehouse databases. Chapter 3. Prerequisite Software 43

62 The documentation for Tioli Data Warehouse 1.2 contains detailed information about the number of supported central data warehouse databases you can configure for any supported distribution scenario. In general, Tioli Data Warehouse 1.2 supports up to four central data warehouses, including a maximum of one central data warehouse in a z/os enironment. See the Tioli Data Warehouse documentation for more information. Any particular source application that is writing data to Tioli Data Warehouse 1.2 can write data to only one central data warehouse in a multi-central data warehouse enironment. If there is one central data warehouse that is configured on a z/os operating system, and if you plan to extract data from that central data warehouse for use with IBM Tioli Serice Leel Adisor, you might prefer to locate the two SLM databases on a z/os operating system as well, though this is not a requirement. If you are planning to extract component and measurement data from multiple central data warehouses, with one central data warehouse on a z/os operating system and one to three central data warehouses in a distributed enironment, you can locate the SLM databases on either a z/os or a distributed operating system. When obtaining measurement data from more than one central data warehouse, performance might be a concern, due to arious factors, including: Target ETLs take more time to run Processing of the data after the ETLS hae completed take longer because there is more data to process SLM databases might require additional disk space Upgrading Tioli Enterprise Data Warehouse 1.1 to Fix Pack 3 If you hae Tioli Enterprise Data Warehouse 1.1 installed, and do not want to take adantage of the new functions proided by ersion 1.2, you must still upgrade Tioli Enterprise Data Warehouse 1.1 at least to the Fix Pack 3 leel to operate with IBM Tioli Serice Leel Adisor 2.1. Refer to Installing Tioli Enterprise Data Warehouse 1.1 Fix Pack 3 on page 191 for information on applying this fix pack. Note: If you also plan to upgrade your installation of DB2 Uniersal Database to a later fix pack leel, be sure to complete the DB2 Uniersal Database upgrade before upgrading Tioli Enterprise Data Warehouse to the latest fix pack. If you upgrade DB2 Uniersal Database after installing this fix pack, you must manually copy <DB2_Dir>/SQLLIB/bin/jaa12/db2jaa.zip into <TWH_DIR>/tools/bin/ directory, where <DB2_Dir> is the location where DB2 Uniersal Database was installed, and <TWH_DIR> is the directory where Tioli Enterprise Data Warehouse was installed. Installing Source Application Warehouse Packs After successfully installing Tioli Data Warehouse, you can install the source ETL (warehouse packs) for each Tioli performance and aailability application that is writing measurement data to the central data warehouse. These warehouse packs are installed on the same machine as the control serer, which uses the Data Warehouse Center component of DB2 Uniersal Database. Installation and configuration procedures for the warehouse packs are included on the warehouse pack installation media. 44 IBM Tioli Serice Leel Adisor: Getting Started

63 See Installing and Configuring Tioli Data Warehouse for details on installing and configuring warehouse packs for each of the Tioli applications that are enabled for Tioli Data Warehouse. Installing IBM WebSphere Application Serer IBM Tioli Serice Leel Adisor uses IBM WebSphere Application Serer as the platform for its administratie serer and for handling report serlets that a customer uses to integrate SLA reports into a company Web site. Refer to the Release Notes for IBM Tioli Serice Leel Adisor for information on specific supported ersions. You must hae a supported ersion of IBM WebSphere Application Serer installed on the machines where you plan to install the SLM Administration Serer and the SLM Reports components of IBM Tioli Serice Leel Adisor. If you do not hae IBM WebSphere Application Serer installed in your enterprise, you can install the ersion that is included with IBM Tioli Serice Leel Adisor, but you must also upgrade your installation to the minimum supported ersion of IBM WebSphere Application Serer by obtaining the latest fix pack software from the WebSphere support Web site. To install the ersion of IBM WebSphere Application Serer that is shipped with IBM Tioli Serice Leel Adisor, refer to the documentation proided with the WebSphere installation media, in particular the Getting Started installation document for IBM WebSphere Application Serer. Additional installation information is aailable online at the following Web site: Considerations for Installing IBM WebSphere Application Serer When installing IBM WebSphere Application Serer, consider the information in the following sections. Upgrade to the Minimum Supported Version Install IBM WebSphere Application Serer using the installation media included with IBM Tioli Serice Leel Adisor, and then upgrade to the minimum supported ersion using the procedures in the IBM WebSphere Application Serer documentation. Installing IBM Tioli Serice Leel Adisor in a Network Deployment Enironment The installation of IBM Tioli Serice Leel Adisor (described fully in Chapter 4, Installing IBM Tioli Serice Leel Adisor, on page 49) includes two components, the SLM Administration Serer and SLM Reports, that are each installed into the WebSphere Application Serer enironment. In a typical installation, you might hae a single WebSphere node machine running a single target application serer, into which you install both the SLM Administration Serer and SLM Reports options. Alternatiely, you might hae multiple application serers configured on a single WebSphere node machine, in which case you might install the SLM Administration Serer into one application serer and SLM Reports into a second application serer on the same node. In this case the IBM Tioli Serice Leel Adisor Chapter 3. Prerequisite Software 45

64 installation program senses that you hae more than one application serer on the target node machine, and prompts you to select the target application serer for the option being installed. In a more distributed WebSphere enironment, you might hae a collection of node machines that you manage together in a cell, using a deployment manager in a Network Deployment enironment. In this case you might install the SLM Administration Serer and the SLM Reports options into any target application serers on any node in the cell. Figure 8 shows a typical cell in a Network Deployment enironment. Figure 8. Node machines, each with one or more application serers, are grouped in a cell and managed by a Deployment Manager node in a typical WebSphere Network Deployment package. As you install and configure your WebSphere enironment, keep in mind the following information on installing the SLM Administration Serer and SLM Reports options of IBM Tioli Serice Leel Adisor: In a typical installation, install both SLM Reports and SLM Administration Serer in the same application serer on the same node. 46 IBM Tioli Serice Leel Adisor: Getting Started

65 You can install each option into a separate application serer. Each option can only be deployed to a single application serer. You cannot install SLM Reports, for example, into more than one application serer. When you install onto a node that has multiple application serers, you are prompted to select a target serer on which to install the option. Both SLM Reports and SLM Administration Serer options hae dependencies on files that are installed on the target node machine. Because of this dependency, these options cannot be deployed to a serer that resides on a node on a different machine. In this case you must uninstall the option and install it again on the other machine. If the application serer on which you plan to deploy the SLM Administration Serer or SLM Reports options is on a node that has been federated (incorporated into a cell) using a Network Deployment configuration of WebSphere, then the IBM Tioli Serice Leel Adisor installation program must be run on the physical machine or node where the target application serer is located. Deploying these options to an application serer cluster is not supported. HTTP session object persistence is not supported. The basic installation referred to in this document is limited to installing the SLM Administration Serer and SLM Reports together in a single IBM WebSphere Application Serer enironment. If you want to pursue the installation of these components in a multiple application serer enironment, consult the IBM WebSphere Application Serer documentation for information on the Network Deployment ersion of IBM WebSphere Application Serer, and on creating and controlling multiple serers in this enironment. Resoling Port Conflicts If you are installing IBM WebSphere Application Serer into a Tioli Enterprise Data Warehouse 1.1 enironment that includes Tioli Presentation Serices, you should ensure that Tioli Presentation Serices and IBM HTTP serices hae been stopped, and then resole port conflicts that can arise with the IBM HTTP Serer and IBM HTTP Administration ports between Tioli Presentation Serices and IBM WebSphere Application Serer installed on the same machine. See Resoling port conflicts on page 192 for more information. Enabling WebSphere Security After installing IBM WebSphere Application Serer and upgrading to the minimum supported ersion, you should enable WebSphere security. With WebSphere security enabled, you can manage access to the SLM Administratie Console and SLM Reports console by authorizing user names and passwords to access these Web pages through sign on pages. Consult the IBM WebSphere Application Serer documentation for details on enabling WebSphere security. Configuring WebSphere for a Non-English Enironment If you are installing IBM WebSphere Application Serer in a non-english language enironment, you must configure IBM WebSphere Application Serer to use UTF-8 encoding by completing the following steps: 1. Set the client.encoding.oerride property by completing the following steps: For supported ersions of IBM WebSphere Application Serer: a. From the WebSphere Administratie Console tree iew, click Serers -> Application Serers. b. From the Application Serers list that is displayed, click the serer (for example, serer1). Chapter 3. Prerequisite Software 47

66 c. From the Configuration tab that is displayed, scroll down to the Additional Properties table and click Process Definition d. From the Process Definition window that is displayed, scroll down to the Additional Properties table and click Jaa Virtual Machine e. From the Jaa Virtual Machine window that is displayed, scroll down to the Additional Properties table and click Custom Properties f. From the Custom Properties window that is displayed, click New to create a new custom property. g. In the Configuration tab that is displayed, type the following parameter alues: Name: client.encoding.oerride Value: UTF-8 h. Click Apply. i. Click Sae in the tool bar at the top of the WebSphere Administratie Console to sae your changes. j. In the Sae to Master Configuration window that is displayed, click Sae again. k. Stop and restart the WebSphere Application Serer. 48 IBM Tioli Serice Leel Adisor: Getting Started

67 Chapter 4. Installing IBM Tioli Serice Leel Adisor At this point in the installation process it is assumed that you hae successfully installed all of the supporting applications discussed in Chapter 3, Prerequisite Software, on page 35. The installation of IBM Tioli Serice Leel Adisor includes these main procedures. which are performed using the LaunchPad proided with IBM Tioli Serice Leel Adisor: 1. Create the SLM Database and SLM Measurement Data Mart DB2 databases. 2. Run the IBM Tioli Serice Leel Adisor installation wizard to perform the installation. Before Installing IBM Tioli Serice Leel Adisor Before installing IBM Tioli Serice Leel Adisor, answer the following questions: Are you reinstalling IBM Tioli Serice Leel Adisor? If so, you must first uninstall any existing ersion before performing a reinstallation, unless you are upgrading from a preious ersion or if you are restoring the SLM Serer option from a backup. See Chapter 7, Uninstalling IBM Tioli Serice Leel Adisor, on page 121 for more information. Are you upgrading IBM Tioli Serice Leel Adisor from a preious ersion? If you currently hae a preious ersion of IBM Tioli Serice Leel Adisor installed in your enterprise enironment, refer to Appendix H, Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor, on page 199 for information on upgrading your enironment to work with this ersion of IBM Tioli Serice Leel Adisor. Is the db2jaa.zip file included in your CLASSPATH system ariable? The installation program uses this file to set up your DB2 enironment (see Verifying the JDBC Leel on page 189). To erify this, complete the following tasks: On Windows 2000 operating systems, click Start > Settings > Control Panel > System to display the System Properties dialog. Click the Adanced tab and click Enironment Variables. Under System ariables, examine the CLASSPATH ariable and erify that <DB2_instance_directory>/sqllib/jaa/db2jaa.zip is included in the path. On UNIX operating systems, source the db2profile locally, by naigating to the <db2_instance_directory>/sqllib directory, where <db2_instance_directory> is the database instance directory, and issuing the following command:. db2profile Note: On some Windows systems, you might also hae a user ariable named CLASSPATH, in addition to the system ariable of the same name. The user ariable oerrides the system ariable settings, so een if you include the db2jaa.zip file in the system CLASSPATH ariable, it might not be recognized by the installation program. You can resole this problem by adding %CLASSPATH%; to the front of the user CLASSPATH ariable, to attach the system ariable settings to the front of the user ariable settings. Copyright IBM Corp. 2002,

68 Are you planning to install the SLM Administration Serer or SLM Reports component on this machine? If so, one of the supported ersions of IBM WebSphere Application Serer must already be installed (and optionally started) on this machine. Note: If IBM WebSphere Application Serer is not already started when you begin the installation program, you are prompted to start it before the installation can continue. Other than starting the serer as directed, do not modify any IBM WebSphere Application Serer configuration settings while IBM Tioli Serice Leel Adisor is being installed (for example, enabling or disabling WebSphere security, or configuring for multiple serers). All IBM WebSphere Application Serer installation and configuration must be completed before beginning the installation of IBM Tioli Serice Leel Adisor. Are you planning an incremental installation? If you are planning to install the SLM Serer, SLM Administration Serer, or SLM Reports component of IBM Tioli Serice Leel Adisor into a machine that already has one or more of these components installed, you must perform the installation to a different directory. You can only reinstall an option into the same directory where it was preiously installed if you are performing a restoration of that option. See the Administrator s Guide for information on the restoration process for IBM Tioli Serice Leel Adisor. Is the system configured to return fully qualified hostnames? The machines on which you install the SLM Serer, SLM Administration Serer, and SLM Reports must be configured so that their hostnames resole to fully qualified names. See Ensuring fully qualified hostnames on page 186 for information on configuring your machine to resole to fully qualified hostnames. Do you hae sufficient authority to install? On UNIX systems, you must be the root user and be a member of a DB2 administrator group to run the installation program. On Windows systems, you must hae Administrator s priileges to run the installation program. See Verifying the Root User Authority in a DB2 enironment on page 184 for more information on performing this task. Are you installing on a Linux operating system? If so, be sure to set the kernel parameter MSGMNI to handle shared memory segments. See the DB2 Uniersal Database documentation for more information on configuring this parameter. Are you installing on a Red Hat Enterprise Linux ersion 3.0 operating system? If so, before installing IBM Tioli Serice Leel Adisor, you must apply the following filesets, depending on the specific type of Red Hat Enterprise Linux operating system in your enironment: For Red Hat Enterprise Linux ersion 3.0 for xseries, apply the following filesets: - compat-gcc compat-libstdc compat-libstdc++-deel compat-glibc-7.x compat-gcc-c compat-db rpm rpm-build This fileset also applies to Intel -based machines. For Red Hat Enterprise Linux ersion 3.0 for pseries, apply the following fileset: 50 IBM Tioli Serice Leel Adisor: Getting Started

69 - rpm rpm-build For Red Hat Enterprise Linux ersion 3.0 for S/390 (z/vm and VM/ESA ), apply the following filesets: - compat-db compat-pwdb compat-libstdc rpm rpm-build You can install a later release of any of these filesets. Are you installing remotely? Remote installations are not supported. The installation program must be run on the machine where the components are installed. Are you planning to create SLM databases on a remote z/os machine by running the installation program from a UNIX machine? If so, the UNIX machine where you run the installation program must hae the Serer ersion of DB2 Uniersal Enterprise Edition installed. You cannot run the installation program in this case on a machine that only has a DB2 client installed, because certain files are needed in the DB2 Serer installation for remote database creation in the z/os enironment. If you are creating DB2 databases, hae you erified that the database names do not already exist in the local or remote DB2 Uniersal Database system directory? You might experience problems if you attempt to create databases using names that already exist in the local or remote directory. Before creating databases, use the db2 list database directory command on your local and remote machine to erify that the database names that you intend to use, for example, DYK_CAT and DYK_DM, are unique. Are you running Lightweight Directory Access Protocol (LDAP) or another directory serice in your enironment? If so, erify that the directory serice is started before attempting the installation. If the directory serice is not running, the installation wizard might not be able to erify that WebSphere Application Serer is started. Starting the LaunchPad To start the IBM Tioli Serice Leel Adisor LaunchPad program, complete the following steps: 1. Insert the IBM Tioli Serice Leel Adisor product CD into the CD-ROM drie. If you are on a UNIX system, source the db2profile, and mount the CD. 2. Start the installation program from the CD mount directory by entering the appropriate command for your operating system, as shown in Table 12: Table 12. InstallShield script file names for each supported operating system. Operating system Microsoft Windows UNIX (Sun Solaris, IBM AIX, Linux, HP) Command LaunchPad.bat./LaunchPad.sh Note: You might see warning messages when you first launch the installation program. These messages can be ignored. Chapter 4. Installing IBM Tioli Serice Leel Adisor 51

70 The LaunchPad program is started, and you are first prompted for the language for the installation, with the current locale being displayed as the default, as shown in Figure 9. Select your installation language from the drop down list proided, and click OK to continue, or click Cancel to stop the installation. Figure 9. Select the language for the installation of IBM Tioli Serice Leel Adisor The main page of the LaunchPad is then displayed as shown in Figure 10.. From this starting page you can create SLM databases, install the IBM Tioli Serice Leel Adisor product, and upgrade users from preious ersions of IBM Tioli Serice Leel Adisor to the current ersion. Note: Do not attempt to stop the installation program by using the Close button (X) in the upper right corner of the installation wizard window. Click Cancel to halt the installation. Figure 10. The IBM Tioli Serice Leel Adisor LaunchPad main page. Creating Databases Before installing the IBM Tioli Serice Leel Adisor product, you must create the SLM databases that you will use. From the LaunchPad, click Create Databases to start the Database Creation Wizard. A welcome page is displayed. Click Next to continue. (Throughout the Database Creation Wizard, click Next to continue, click Back to return to the preious step, or click Cancel to cancel the procedure and return to the main page of the LaunchPad.) This wizard guides you through the steps described in the following sections to create the SLM databases. 52 IBM Tioli Serice Leel Adisor: Getting Started

71 Step 1. Select the Databases to be Created The first page of the Database Creation Wizard prompts you to select which of the two SLM databases are to be created on this machine, as shown in Figure 11. Figure 11. Select which of the SLM databases are to be created. By default, both the SLM Database and the SLM Measurement Data Mart check boxes are cleared. Select both check boxes to create both databases on this machine now, or select one check box to create one database at a time, or if you plan to create the other database on another machine, or if the other database is already created. When you hae made your selection, click Next to continue. Step 2. Specify Whether Databases are Local or Remote On the pages that follow, for each database that you selected to create, you can specify whether the database is to be created locally (on this machine) or remotely (on another machine in your enterprise enironment), as shown in Figure 12 on page 54. Chapter 4. Installing IBM Tioli Serice Leel Adisor 53

72 Figure 12. Specify whether the database is to be created locally or remotely. If you select the Local radio button and click Next, you are then asked for the following additional database connection information, as shown in Figure 13: Figure 13. Specify local database connection information. The name of the database. The Database Name field contains the default name of the database (dyk_cat for the SLM Database, or dyk_dm for the SLM Measurement Data Mart), but you can change the name. Specify unique database names: Verify that the database name does not already exist on the local DB2 Uniersal Database system directory. The DB2 user ID and password for the local machine If you select the Remote radio button and click Next, you are then asked if the database will be created on a remote machine that is running on a z/os or OS/ IBM Tioli Serice Leel Adisor: Getting Started

73 operating system, as shown in Figure 14. Select the appropriate radio button and click Next to continue. Figure 14. Specify whether the SLM Database will be created on an z/os operating system The wizard then prompts you for the following remote connection information for the database, as shown starting in Figure 15 on page 56 (if the database will be created on a z/os operating system, the wizard asks for some additional information for that enironment): Note: If you are creating remote databases on a remote z/os machine by running the installation program from a UNIX machine, the UNIX machine where you run the installation program must hae the Serer ersion of DB2 Uniersal Enterprise Edition installed. You cannot run the installation program in this case on a machine that only has a DB2 client installed, because certain files are needed in the DB2 Serer installation for remote database creation in the z/os enironment. Chapter 4. Installing IBM Tioli Serice Leel Adisor 55

74 Figure 15. Specify remote database connection information (part 1 of 2). If you are creating the database on a z/os operating system: Storage Group This is a user-supplied name, with a maximum of 8 characters. Storage Volume This name must already be defined in the z/os enironment. You must enter the name of an existing storage olume, with a maximum of 6 characters. Storage Vcat This is a user-supplied name, with a maximum of 8 characters. Buffer pool name This is the buffer pool that is enabled for these databases. The field contains the default alue of bp16k0. Accept this default if this is a alid name for your enabled buffer pool, or change this entry to another name. Tablespace Name This is a user-supplied name. Encoding is the same as the default encoding for the location. Note: Be sure to sae this tablespace name. You need it again for additional configuration steps (see Configuring Target ETL Table Translation Information for SLM Databases on z/os on page 100). Tablespace Size Primary 56 IBM Tioli Serice Leel Adisor: Getting Started

75 This is the primary size for the tablespace, and is typically set to a default alue of Tablespace Size Secondary This is the secondary size for the tablespace, and is typically set to a default alue of UTF8 Tablespace Name This is a user-supplied name for the UTF-8 encoded tablespace. Note: Be sure to sae this tablespace name. You need it again for additional configuration steps (see Configuring Target ETL Table Translation Information for SLM Databases on z/os on page 100). Location The location name appears on your z/os console after starting DB2 Uniersal Database. It should be a combination of your domain and subsystem names (for example, if your domain name is XYZ1234 and one of the DB2 subsystems is DB71, the Location would be XYZ1234DB71). The name of the database. The Database Name field contains the default name of the database (dyk_cat for the SLM Database, or dyk_dm for the SLM Measurement Data Mart), but you can optionally change the name. Specify unique database names: Verify that the database name does not already exist on the local or remote DB2 Uniersal Database system directory. If you are creating a database (for example, the SLM Database, with database dyk_cat) on a remote system, you might experience problems if the local machine (where you are running the LaunchPad program) already has a DB2 catalog entry for this database name, dyk_cat. Use the db2 list database directory command to erify that the database name that you specify is not already cataloged before you attempt to create it here. If you are creating these databases on a z/os operating system: Specify a name without underscore characters (_), such as DYKCAT or DYKDM. These characters are not alid in a z/os operating system. This name is only used as a local alias to the z/os database. If you hae DB2 Uniersal Database ersions of DYK_CAT and DYK_DM databases created locally (een if they are uncataloged), you must drop these local databases before you can create databases on a z/os operating system. The DB2 user ID and password On a z/os operating system, the specified user ID must hae sysadmin authority to create databases. The hostname of the remote database serer. This is the fully qualified hostname of the machine where the database is to be located, for example, mymachine.raleigh.ibm.com. See Ensuring fully qualified hostnames on page 186 for information on configuring your machines to resole to fully qualified hostnames. This can also be a alid IP address. The port number or serice name for the remote database serer instance. This field contains the default port alue of 5027, but you can change this alue. Note: Be sure to get the correct port number from your database administrator, especially when databases are located remotely on a z/os operating system. An incorrect port number might result in a database catalog error, preenting connection to the database and requiring manual uncataloging the database entry. The name of the remote database instance. Typically, for UNIX operating systems it might be specified as db2inst1, or for a Windows operating system it Chapter 4. Installing IBM Tioli Serice Leel Adisor 57

76 might be db2. This field is not used for the z/os enironment. Consult with your database administrator for more information if needed. Figure 16. Specify remote database connection information (part 2 of 2). When you hae completed the specification of input for the database creation, click Next to continue. The Database Creation Wizard then attempts to connect to the database to erify if the database already exists in a directory on the local machine (where the LaunchPad is running). If this check is successful, a message is displayed (see Figure 17 on page 59 ) informing you that the database already exists, and you are asked if you want to drop the database and recreate it. Note: Een if you are creating the database on a remote system, you might receie the message in Figure 17 on page 59 if a preious catalog of the database name exists on the local machine where the LaunchPad is running. 58 IBM Tioli Serice Leel Adisor: Getting Started

77 Figure 17. The database already exists. Specify whether or not to drop it and recreate it. If you click Yes, the database is dropped and recreated. Note: If you drop and recreate the database, you lose any data that is currently in the database, unless you hae preiously made a backup copy. If you click No, a confirmation message is displayed. Click Back to modify your input to the wizard, or click Cancel to quit the Database Creation Wizard and return to the main page of the LaunchPad. If you specify to create more than one database, you are also prompted for this same information for that database. Step 3. Creating the Databases The database creation wizard presents you with a summary page, as shown in Figure 18: Figure 18. Confirm your database creation selection in the summary page. Confirm your selection and click Next to begin the database creation. It might take a minute or two to complete. Chapter 4. Installing IBM Tioli Serice Leel Adisor 59

78 When completed, the wizard displays a results page indicating if the creation process was successful, similar to Figure 19. Figure 19. The databases were created successfully. Click Finish to exit the Database Creation Wizard and return to the main page of the LaunchPad. Step 4. Checking Database Creation Logs and Tables After the Database Creation Wizard has completed processing, you can check the database creation logs for error messages, and examine the list of database tables that were created. These logs are placed, by default, in the temporary folder for your system (see the %TEMP% enironment ariable for Windows operating systems, or the /tmp ariable for UNIX operating systems). For each database created, the following log files are created, where <Database_Name> is the name of the database, such as dyk_cat or dyk_dm: <Database_Name>_dbinst_err.log <Database_Name>_dbinst_out.log <Database_Name>_erify.log <Database_Name>_erify_err.log Compare the contents of the <Database_Name>_erify.log file to the table lists in Appendix E, Database Creation Tables, on page 173. If your table information does not match the information in the appendix, check the database creation log files for error messages. After you identify and correct the error, run the Database Creation Wizard again. Note: The database creation logs write oer any existing log information rather than append to existing log information. Step 5. Creating a Temporary Database and Tablespace for Databases on z/os Systems If you created the SLM Database or the SLM Measurement Data Mart on a z/os system, you need to create a temporary database and tablespace for the component path build process to succeed. You might already hae a temporary database set up (consult your database administrator for assistance), but if not, complete the following steps to create a temporary database dyktemp and tablespace on the z/os system where the SLM Database and SLM Measurement Data Mart are located: 60 IBM Tioli Serice Leel Adisor: Getting Started

79 1. From a distributed DB2 client, such as the SLM Serer machine where the DYK databases are cataloged to the remote z/os machine, open a DB2 command prompt. 2. Issue the following command to connect to the z/os location, where <db2userid> and <db2password> are a user ID and password to access the database: db2 connect to dykcat user <db2userid> using <db2password> 3. Issue the following command to create the dyktemp temporary database: db2 create database dyktemp as temp 4. Create a tablespace for use within the temporary database by issuing the following command: db2 create tablespace sdutemp in dyktemp segsize 32 bufferpool bp8k0 5. Issue the following command to disconnect from the z/os location: db2 disconnect dykcat You only need to create this temporary database and tablespace once, not each time that DYK databases are created. Installing the IBM Tioli Serice Leel Adisor Product After creating the SLM databases, you can install the IBM Tioli Serice Leel Adisor product software from the installation product CD using the following basic steps: 1. Select the language to use for the installation. 2. Accept the terms in the Software License Agreement. 3. Specify a location for the Tioli Common Directory if it does not already exist on this machine, or confirm the location if it already exists. 4. Decide whether to install the IBM Tioli Serice Leel Adisor product, or to install language support, or both during this installation. 5. Specify a destination directory for your installation. 6. Select one or more of the IBM Tioli Serice Leel Adisor installation options to install on your machine. If you are installing IBM Tioli Serice Leel Adisor in a distributed enironment, install the SLM Serer component first. If you install these IBM Tioli Serice Leel Adisor installation options on multiple machines, or for an incremental installation, you must repeat the installation process for each machine. Similarly, if you install multiple options on the same machine, with each option in its own directory, you must repeat the installation process for each directory. 7. Verify that the necessary prerequisite software has been installed for the options you selected (this is done automatically by the installation wizard). If you hae WebSphere security enabled and you are installing either the SLM Administration Serer or SLM Reports option, the wizard erifies your WebSphere user name and password information and checks the status of the IBM WebSphere Application Serer. If you hae more than one application serer enabled, you can select the target serer from a list of aailable serers. 8. Specify the connection information for the two DB2 application databases (the SLM Database and the SLM Measurement Data Mart) that were created for IBM Tioli Serice Leel Adisor. 9. Specify port numbers for serer communication and command line interface ports. Chapter 4. Installing IBM Tioli Serice Leel Adisor 61

80 10. Decide how you want to be notified of SLA iolations and trends (using SNMP traps, Tioli Enterprise Console eents, or ), and configure eent escalation methods that you select. 11. Specify a user name for Administrator authority (if the SLM Administration Serer is installed on this machine) as well as access to SLM Reports (if the SLM Reports option is installed on this machine). 12. Specify whether to compile JaaSerer Page Files during installation or later. Note: Throughout the installation wizard, you can click Next to continue to the next step, or click Back to return to the preiously displayed page, or click Cancel to quit the installation process. The InstallShield wizard erifies the database connections, and then installs all the needed files to your machine in your specified destination. Some initial configuration automatically takes place. A log file is generated to log problems if they occur. Note: The log file, tracetsla2.1install.log, located in the Tioli Common Directory under <Tioli_Common_Dir>/DYK/logs/install is not created until files are written to disk. If the installation is canceled early, this log file is located in the temporary directory for your system instead of the Tioli Common Directory. Error information in this log file should be sent to Tioli customer support to assist in diagnosing problems. You can also perform a silent installation of the IBM Tioli Serice Leel Adisor product. See Performing a Silent Installation of IBM Tioli Serice Leel Adisor on page 197 for more information. The steps inoled in running the installation wizard are described in the following sections. Step 1. Select the Language for the Installation From the main page of the LaunchPad, click Install Product to start the InstallShield wizard. You are first prompted for the language for the installation, with English as the default, as shown in Figure 20. Select the installation language from the drop down list proided, and click OK to continue, or click Cancel to stop the installation. Figure 20. Select the language for the installation of IBM Tioli Serice Leel Adisor A welcome screen is displayed. Click Next to continue. Step 2. Accept the Software License Agreement The Software License Agreement page is displayed, as shown in Figure 21 on page 63. Read the terms in the license agreement as presented in the scrollable window, and, if you agree to abide by those terms, select the I accept the terms in the 62 IBM Tioli Serice Leel Adisor: Getting Started

81 license agreement radio button, and then click Next to continue. You are not allowed to continue with the installation if you do not accept the terms in the license agreement. Figure 21. You must accept the terms in the Software License Agreement to install the software. Checking for a Valid Installation operating system At this point the wizard erifies that you are attempting to install the product on a supported operating system. If it detects a problem, the following message is displayed: DYKIN0080E You are attempting to install on an unsupported platform. Cancel this installation and consult the Release Notes for information on supported operating systems before attempting to install the product again. Step 3. Specify the Tioli Common Directory IBM Tioli Serice Leel Adisor stores message and trace log files and failure data under a common parent directory, called the Tioli Common Directory. Centralizing the location of log files makes it easier for you to locate them, inestigate problems, and report information to Tioli Customer Support. Upon installation, each product creates a new directory within the Tioli Common Directory to contain product specific log and failure data. The directory is named by the three-letter product identifier. For IBM Tioli Serice Leel Adisor, this directory is located at <Tioli_Common_Dir>/DYK. If IBM Tioli Serice Leel Adisor is the first Tioli product that is installed on this machine, the installation wizard creates the Tioli Common Directory for use by IBM Tioli Serice Leel Adisor and other Tioli products that are installed in the future. Chapter 4. Installing IBM Tioli Serice Leel Adisor 63

82 The installation wizard checks to see if the Tioli Common Directory is already established on this system. If it is not already created on this machine, the wizard displays the page shown in Figure 22. Figure 22. Specifying the location of the Tioli Common Directory. The default location for the Tioli Common Directory is displayed for UNIX operating systems as /usr/ibm/tioli/common, or, for Windows operating systems, as <ProgramFiles>\ibm\tioli\common. The <ProgramFiles> ariable refers to the default location of your program files, for example, C:\Program Files. You can find the setting for your system by examining the ProgramFilesDir attribute, stored in the Windows registry located in HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion. You can accept this default location, or if you prefer to locate the Tioli Common Directory in a different location, you can modify this dialog. After specifying the location for the Tioli Common Directory, click Next to continue. If the Tioli Common Directory was preiously created on this machine, the wizard detects it and display where it found the location. In this case, you are not permitted to change the location of the Tioli Common Directory in this window, because other Tioli applications might be using it. No action is required, just click Next to continue with the installation. Step 4. Select Installation Options The hostname of the machine on which you are installing is obtained by the wizard, and after a moment, a page is displayed as shown in Figure 23 on page 65 prompting you to specify whether to install the IBM Tioli Serice Leel Adisor product, install language support, or both. If you want to install language support by itself, IBM Tioli Serice Leel Adisor must hae been preiously installed. Select the appropriate check boxes and then click Next to continue. 64 IBM Tioli Serice Leel Adisor: Getting Started

83 Figure 23. Select installation of the product, language support, or both. Step 5. Specify the Destination Directory A page is displayed prompting you to specify a destination directory for where you want IBM Tioli Serice Leel Adisor to be installed, as shown in Figure 24. Figure 24. Specify a destination directory for IBM Tioli Serice Leel Adisor. A default location is displayed in the Directory Name field. You can use this default location, or replace it with another destination directory. If the directory does not exist it is created for you. Note: Do not use the following characters in the destination path: Chapter 4. Installing IBM Tioli Serice Leel Adisor 65

84 : *? < >! # % ^ Double-byte characters Characters with special accent marks, such as an umlaut You can also click Browse to naigate to the destination directory if it already exists. After you hae specified the destination directory, click Next to continue. Note: There is a known problem with this Browse function on Solaris operating systems. To aoid this problem, accept the default directory or type in your destination directory in the Directory Name field proided. Step 6. Select SLM Installation Options Depending on your deployment, you can install one or more of the following main options of IBM Tioli Serice Leel Adisor on a single machine, or distributed across multiple machines: The SLM Serer (If you are installing the arious components of IBM Tioli Serice Leel Adisor in a distributed enironment, install the SLM Serer on its target machine first before installing other IBM Tioli Serice Leel Adisor options on other machines.) SLM Reports, which must be installed on the machine designated as your SLM Report serer, where a supported ersion of IBM WebSphere Application Serer was installed. If you hae IBM WebSphere Application Serer installed, this installation option automatically integrates the report serlets into the WebSphere enironment. The SLM Administration Serer, which also must be installed on a machine where a supported ersion of IBM WebSphere Application Serer is installed. You can install this option on a different machine, if IBM WebSphere Application Serer is also installed in that machine. If you are installing on a machine that has more than one application serer, you will be prompted to select which application serer to install on (see Figure 27 on page 68). If you are installing on a WebSphere node machine that is part of a Network Deployment cell, see Installing IBM Tioli Serice Leel Adisor in a Network Deployment Enironment on page 45 for additional considerations. 66 IBM Tioli Serice Leel Adisor: Getting Started

85 Figure 25. Select one or more installation options for the current machine. Select one or more check boxes corresponding to the IBM Tioli Serice Leel Adisor options that you are installing on the current machine, as shown in Figure 25. You can select any combination of the three options to install. After you select one or more of the SLM options to install on this machine, click Next to continue. Installing SLM Options Incrementally If you install one or two main options of IBM Tioli Serice Leel Adisor and later restart the installation program to install another option on the same machine, note that you cannot install into the same directory as the preiously installed options. You must specify a different directory name (see Step 5. Specify the Destination Directory on page 65 ) for each option that you incrementally install. Step 7. Verify Prerequisite Software The wizard erifies that the prerequisites are installed before continuing. Various messages appear on the wizard page as the wizard runs through its checking procedure. If you are installing either the SLM Administration Serer or SLM Reports options into a WebSphere enironment on this machine, and if you enabled WebSphere security, the wizard prompts you for the user name and password that you use to sign on to the WebSphere Administratie Console, as shown in Figure 26 on page 68. Chapter 4. Installing IBM Tioli Serice Leel Adisor 67

86 Figure 26. The wizard erifies your WebSphere user name and password for proper authority. If you hae more than one WebSphere application serer defined, the wizard prompts you to select the serer on which to install the SLM Administration Serer and SLM Reports components, similar to Figure 27. The wizard then erifies the status of the selected serer and ensures that it is started. Figure 27. Select the target WebSphere application serer on which to install, if you hae more than one application serer defined. If you hae Tioli Presentation Serices installed on this machine, the wizard informs you of this, and if you upgraded Tioli Data Warehouse to ersion 1.2, you might choose to uninstall Tioli Presentation Serices later, if you are not using it for any other applications on this machine. When completed, the wizard continues with the next step. Step 8. Configure for SLM Database Access The next set of pages in the installation wizard prompts you to proide database connection information for the SLM Database and the SLM Measurement Data 68 IBM Tioli Serice Leel Adisor: Getting Started

87 Mart. There might be circumstances, howeer, when this part of the installation wizard is not included in the installation flow. For example, if you installed the SLM Serer component on this machine, and then at a later time install the SLM Reports component in another directory on the same machine, the installation wizard reads the database connection information from the location where the SLM Serer was installed, and does not display the pages described in this step. If database connection information is needed by the installation wizard, a page similar to Figure 28 is first displayed, asking whether the SLM Database is installed on this machine (local) or on another (remote) system elsewhere in your enterprise. Figure 28. Specify whether the SLM Database is installed locally or remotely. This example assumes that you indicated that the SLM Database is installed locally on this system. After you click Next, you are prompted for additional connection information, similar to the information proided when the database was first created (see Step 2. Specify Whether Databases are Local or Remote on page 53 for details on specifying connection information for databases created locally or remotely). The installation program prompts you for the necessary information for both the SLM Database and the SLM Measurement Data Mart. After entering your connection information, click Next to continue. Using the database connection information that you proided, the installation program attempts to connect to each database. If the attempt is successful, the installation continues. If the attempt fails, look in the tracetsla2.1install.log file in your system temporary directory for SQL error messages to determine why the installation program did not connect with the database. Correct any problems found with the databases, and start the IBM Tioli Serice Leel Adisor installation again. Step 9. Specify Additional Serer Configuration When you install the SLM Serer, you are prompted for some additional configuration information as shown in Figure 29 on page 70: Chapter 4. Installing IBM Tioli Serice Leel Adisor 69

88 Figure 29. Specifying additional serer configuration information. The SLM Serer Communication Port. The default alue of 9980 is proided. You can replace this with a different port number. Command Line Interface Port. The default alue of 9990 is proided. You can replace this with a different port number. Specify whether or not you want your command line interface (CLI) commands to be password protected. If you select this option, CLI commands that are issued are password protected and must be entered by specifying an additional parameter, p <password>, along with the regular CLI command. For example, the scmd log help command would hae to be specified as: scmd -p <password> log help This is useful if you want to restrict use of CLI commands to certain personnel. If you want to enable password protection, select the check box proided and specify the initial alue of <password> that must be gien with each CLI command. Passwords must be from 6-16 characters in length. Note: Do not use double-byte characters, umlauted characters, or other characters with special accent marks in the CLI password. See the Command Reference for details about password protection for CLI commands. If you are installing the SLM Administration Serer or SLM Reports on a machine different from where the SLM Serer is installed, you are prompted to specify the hostname of the machine on which the SLM Serer is located, and the SLM Serer Communication Port, as shown in Figure 30 on page 71. This must be the same port alue that you entered when the SLM Serer component was installed (the default alue of 9980, or the port number that was specified if this default was not taken). 70 IBM Tioli Serice Leel Adisor: Getting Started

89 Figure 30. Specify information for communicating remotely with the SLM Serer. Step 10. Specify Eent Notification Methods When IBM Tioli Serice Leel Adisor ealuates measurement data and detects iolations or trends toward potential iolations of serice leel agreements, eent notices can be sent out in seeral different ways to alert support personnel, enabling them to take immediate correctie action to maintain agreed upon leels of serice. Figure 31 on page 72 shows the notification options that you can select. If you want eent notification to occur, you can select one or more of the following methods for sending eent information: SNMP Trap Tioli Enterprise Console Eent Chapter 4. Installing IBM Tioli Serice Leel Adisor 71

90 Figure 31. Select one or more eent notification methods. If you want to enable eent notification, select one or more of the check boxes. After you make your selections, click Next to proide additional configuration information for each of your selected notification methods. Notification by SNMP Trap If you select the SNMP Trap option for eent notification, the configuration window shown in Figure 32 is displayed. Figure 32. Configuring the SNMP Trap notification method. When you select this notification option, you are be prompted to proide the following information: 72 IBM Tioli Serice Leel Adisor: Getting Started

91 Destination Host Name This is the fully qualified hostname of the destination machine acting as the receiing SNMP management station for SNMP traps, for example, mymachine.raleigh.ibm.com. Destination Port This is the SNMP Trap destination port number. A default alue of 162 is proided. Specify a different port number if needed. Community Name This is an optional field containing the SNMP trap serice community name. A default alue of public is proided. Specify the aboe information, or accept the proided default alues, and click Next to continue. Notification by Tioli Enterprise Console Eent If you select the Tioli Enterprise Console eent option for eent notification, the configuration window shown in Figure 33 is displayed. Figure 33. Configuring the Tioli Enterprise Console eent notification method. When you select this notification option, you are prompted to proide the following information: Eent Serer Host Name This is the fully qualified hostname where the Tioli Enterprise Console eent serer is installed, such as TECMachine.raleigh.ibm.com. Eent Serer Port If the eent serer is installed on a Windows machine, enter the port number that the eent serer uses to listen on for eents. The typical port alue is See the Tioli Enterprise Console eent serer configuration for the correct port number. If the eent serer is installed on a UNIX machine, leae this field blank. After you enter the required information, click Next to continue. Chapter 4. Installing IBM Tioli Serice Leel Adisor 73

92 Notification by You can select this notification method if you want to send messages to one or more addresses when an eent occurs. You must specify the SMTP Serer hostname to handle the messages, and also a To-List of addresses, separated by commas, as the target where the message is sent. You can also specify an optional CC-List of additional addresses to be copied on the message. You can either accept the default messages that are proided, or you can customize the messages. After you select this notification option, a page similar to Figure 34 is displayed. Figure 34. Configuring the eent notification method (part 1 of 2) Proide the following information: SMTP Serer Host Name This is the fully qualified hostname of the SMTP Serer to handle the messages. This is a required field. Note: To aoid the possibility of incorrect characters in receied s, the system to which you send notifications must be capable of handling characters in the UTF-8 character set. To-List Addresses This is one or more addresses, separated by commas, for the people you want to notify. This is a required field. No error checking is performed on the addresses entered. CC-List Addresses This is one or more addresses, separated by commas, for additional people you want to copy on the message. This might be resered for superisory personnel or other people who might not deal directly with the iolation or trend information but who want to stay informed. No error checking is performed on the addresses entered. 74 IBM Tioli Serice Leel Adisor: Getting Started

93 After you hae specified the SMTP Serer name and the addresses to send notifications, click Next to continue configuring notification. Continuing with the configuration of the notification method, a second window is displayed as shown in Figure 35.. Figure 35. Configuring the eent notification method (part 2 of 2) Specify the following parameters: Subject Line This is a subject line for the message. A default subject line is proided, both as an acceptable generic subject that you can use, as well as an example for you to copy if you want to customize your own subject line: SLO $EentType Note that ariables are permitted in the alue, preceded by the dollar sign ($) character. Violation Message This is the text of the message that is sent when a serice leel agreement (SLA) iolation is detected. A default message is proided, both as an acceptable generic message that you can use, as well as an example for you to copy if you want to customize your own message wheneer a iolation occurs: NOTICE: A metric iolation has been detected. The details are as follows: Customer Name: <customer_name> SLA ID: <SLA_ID> SLA Name: <SLA_name> Other Affected SLAs: <affected_slas> Schedule State: <schedule_state> Resource: <resource_name> Chapter 4. Installing IBM Tioli Serice Leel Adisor 75

94 Metric Violated: <metric_name> Units: <units> Ealuation End Date: <ealuation_end_date> Violation Details: <iolation_details> You can use this generic default message or replace it with your own message. Variables are permitted in the text, preceded by a dollar sign ($) character. Trend Message This is the text of the message that is sent when a trend toward a potential iolation is detected. A default message is proided, both as an acceptable generic message that you can use, as well as an example for you to copy if you want to customize your own message wheneer a trend occurs: NOTICE: A trend toward a potential metric iolation has been detected. The details are as follows: Customer Name: <customer_name> SLA Number: <SLA_number> SLA Name: <SLA_name> Other Affected SLAs: <affected_slas> Schedule State: <schedule_state> Resource: <resource_name> Metric Predicted to be Exceeded: <metric_name> Units: <units> Trend Projection: <trend_projection_details> Analysis Period: <analysis_period> Total Samples: <total_samples> You can use this generic default message or replace it with your own message. Variables are permitted in the text, preceded by a dollar sign ($) character. Trend Canceled Message This is the text of the message that is sent when a preiously identified trend toward a iolation no longer exists. A default message is proided, both as an acceptable generic message that you can use, as well as an example for you to copy if you want to customize your own message wheneer a trend is canceled: NOTICE: A preiously reported trend that had projected a future metric iolation has been CANCELED. The metric associated with the following information is no longer trending toward a iolation: Customer Name: <customer_name> SLA ID: <SLA_ID> SLA Name: <SLA_name> Other Affected SLAs: <affected_slas> Schedule State: <schedule_state> Resource: <component_name> Metric Name: <metric_name> 76 IBM Tioli Serice Leel Adisor: Getting Started You can use this generic default message or replace it with your own message. Variables are permitted in the text, preceded by a dollar sign ($) character.

95 See the scmd escalate configure CLI command in the Command Reference for details on the ariables you can include in messages. You can use this command to reconfigure these messages at a later time. When you hae completed specifying your eent notification messages, click Next to continue. Step 11. Define SLM Administrator Authority and SLM Reports Access A page in the wizard is displayed, as shown in Figure 36 prompting you for a user name that can sere multiple purposes, depending on which components of IBM Tioli Serice Leel Adisor are installed on this machine. Figure 36. Specify a user name for SLM Administrator authority or access to SLM Reports If the SLM Administration Serer is installed on this machine, this user name is designated as the SLM Administrator, giing it Administrator authority to access all tasks in the IBM Tioli Serice Leel Adisor console. If SLM Reports are installed on this machine, this user name is authorized to sign on to the SLM Reports console. If WebSphere security is enabled, this user name must already exist in the WebSphere User Registry. Enter the user name in the field proided, and click Next to continue. Step 12. Decide Whether or not to Compile JaaSerer Page Files If you are installing the SLM Administration Serer on this machine, a page is displayed in the installation wizard, similar to Figure 37 on page 78 asking if you want to compile the JSP files for the SLM Administration Serer. If you select Yes, these files are compiled during the installation, and the installation process takes Chapter 4. Installing IBM Tioli Serice Leel Adisor 77

96 some more time to complete. If you select No, these files can be manually compiled later, or they are compiled automatically as needed. Figure 37. Decide whether or not to compile JSP Files during installation. The default is to not compile these files during installation. Accept this default or select Yes to compile the files during installation, and click Next to continue. If you choose to compile these files at some later time, you can run a WebSphere supported script, JspBatchCompiler.bat, located at <WebSphere_Dir>/bin. The command syntax is as follows: JspBatchCompiler -enterpriseapp.name <name> [-webmodule.name <name>] [-cell.name <name>] [-node.name <name>] [-serer.name <name>] [-filename <jsp name>] [-keepgenerated <true false>] [-erbose <true false>] [-deprecation <true false>] You might issue this command similar to the following example, where SLMAdmin is the name of the enterprise application, and mymachine is the name of the system, and other defaults were assumed to hae been taken during WebSphere installation: JspBatchCompiler -enterpriseapp.name SLMAdmin -cell.name mymachine -node.name mymachine Refer to your WebSphere documentation for more information on using this compile tool. 78 IBM Tioli Serice Leel Adisor: Getting Started

97 Step 13. Optionally Configure Language Support Installation If you selected the Install Language Support check box in Step 4. Select Installation Options on page 64, at this time you are prompted for the path and file name for the Language Support source file to install. The default language support source file that is shipped with IBM Tioli Serice Leel Adisor is displayed in the Language Support source file field as shown in Figure 38. Confirm this selection or specify an alternate language support source file, and then click Next to continue. Figure 38. Specify the language support source file to install. For each of the three SLM installation options that you selected in Step 6. Select SLM Installation Options on page 66 to install on this machine, you now can select one or more languages for which you want to install support. A menu of aailable languages is displayed for each SLM installation option, similar to Figure 39 on page 80. Chapter 4. Installing IBM Tioli Serice Leel Adisor 79

98 Figure 39. Select one or more languages for each SLM installation option on this machine. Select one or more check boxes for the language support to install for each SLM installation option, and then click Next to continue. A confirmation window is displayed, showing the languages that you selected for each SLM installation option. Confirm your selections once more and click Next to continue. Step 14. Confirm Your Installation Options A confirmation page prompts you to confirm your intention to install the arious IBM Tioli Serice Leel Adisor options on this machine, similar to Figure 40 on page IBM Tioli Serice Leel Adisor: Getting Started

99 Figure 40. Confirm your installation selections to initiate the installation. Click Next to proceed with the installation, or click Back to return to preious pages and modify your selections, or press Cancel to quit the installation. Step 15. Complete the Installation The installation of IBM Tioli Serice Leel Adisor starts, and a progress indicator is displayed, similar to Figure 41. Any messages are logged to the tracetsla2.1install.log file, located in the Tioli Common Directory. Figure 41. The progress indicator status bar tracks the installation progress. To cancel the installation, click Cancel. Otherwise, wait for the installation to complete. If you are installing the SLM Reports option, the installation progress indicator might stay at 99% for seeral minutes while the configuration is being performed. A message is displayed as shown in Figure 42 on page 82 indicating that the IBM WebSphere HTTP plug-in configuration needs to be regenerated before attempting to bring up the SLM Administratie Console or SLM Reports. If you preiously made manual changes to your HTTP plug-in configuration that you want to Chapter 4. Installing IBM Tioli Serice Leel Adisor 81

100 presere, you should make a backup of these changes before you regenerate the plug-in configuration. Figure 42. You will need to regenerate the configuration for your WebSphere HTTP plug-in before bringing up the SLM Administratie Console or SLM Reports Console. The message asks if you want to regenerate the plug-in configuration now. You can either select the Yes radio button to perform the plug-in regeneration automatically, or you can select No and complete this step later, following the procedure in Regenerating Web Serer Plug-in Configurations on page 87, which you need to complete along with other configuration steps after completing this installation. When installing in a WebSphere Network Deployment enironment: When you are installing SLM Reports or SLM Administration Serer options into a WebSphere applications serer that has been federated into a Network Deployment cell the plug-in must be manually regenerated. Select an option and click Next to continue. If you chose to regenerate the plug-in configuration now, the wizard completes that task before continuing. When the installation completes successfully for the SLM Reports component, a message is displayed as shown in Figure 43 on page 83. Click Next to continue. 82 IBM Tioli Serice Leel Adisor: Getting Started

101 Figure 43. After the SLM Reports installation completes successfully, a message is displayed. When the installation completes successfully for the SLM Administration Serer component, a message is displayed as shown in Figure 44. Click Next to continue. Figure 44. After the SLM Administration Serer installation completes successfully, a message is displayed. A message is displayed (see Figure 45 on page 84) indicating that the WebSphere Application Serer needs to be restarted. You can optionally hae the wizard restart the WebSphere Application Serer at this time, or restart it manually later. Select the Yes, restart serer1 check box to restart the serer, and click Next to continue. Chapter 4. Installing IBM Tioli Serice Leel Adisor 83

102 Figure 45. Optionally select the check box to hae the WebSphere Administration Serer restarted by the wizard. Additional Installation Tasks If you select to hae the WebSphere Application Serer restarted, that step occurs at this time. Wait for the serer to be restarted. When completed, another page is displayed, indicating that the SLM Serer will shut down before proceeding. Click Next to continue. If you select the option to install language support, that installation occurs at this time and you should receie a message stating that it installed successfully. Click Next to continue. Click Finish to exit the installation program and return to the main page of the LaunchPad. If you did not install all three IBM Tioli Serice Leel Adisor installation options on this machine, you must repeat this installation process on the other machines, installing each of the three options in your enterprise enironment. Be sure to select the correct installation option for each machine. After you are finished with the IBM Tioli Serice Leel Adisor LaunchPad, click Exit LaunchPad to close the LaunchPad window. There are a few more steps you need to perform to configure your enironment for IBM Tioli Serice Leel Adisor. See Chapter 5, Additional Installation Tasks, on page 87 for details. Complete Post-Install tasks before creating SLAs: Do not begin to create offerings and SLAs until you hae completed the configuration steps in Chapter 5, Additional Installation Tasks, on page 87 that apply to your enironment, including enabling source applications and completing the initial running of the Registration ETL. In addition, be aware that some internal processing takes place to initialize the SLM Serer and SLM Database for creating offerings and SLAs, 84 IBM Tioli Serice Leel Adisor: Getting Started

103 and you should wait at least 30 minutes after the Registration ETL is initially run before attempting to create offerings and SLAs, otherwise you might receie errors. Chapter 4. Installing IBM Tioli Serice Leel Adisor 85

104 86 IBM Tioli Serice Leel Adisor: Getting Started

105 Chapter 5. Additional Installation Tasks After you complete the installation of IBM Tioli Serice Leel Adisor as described in Chapter 4, Installing IBM Tioli Serice Leel Adisor, on page 49, there are seeral required and optional installation tasks you need to complete to configure your enironment for IBM Tioli Serice Leel Adisor: Required procedures: Regenerate the Web serer plug-in configuration for new applications added to IBM WebSphere Application Serer (if you installed the SLM Administration Serer or SLM Reports components of IBM Tioli Serice Leel Adisor on this machine and you chose to not regenerate the plug-in configuration during the installation process). Configure ODBC data sources for the SLM databases that you created. Install the target warehouse enablement pack for IBM Tioli Serice Leel Adisor. Configure the ETLs for moing data from the central data warehouse into the local SLM databases for ealuation and analysis by IBM Tioli Serice Leel Adisor. Optional procedures: Install the source warehouse enablement pack for IBM Tioli Serice Leel Adisor, for writing IBM Tioli Serice Leel Adisor information back into the central data warehouse for possible use by other applications. Additional configuration and erification of your selected eent notification method ( , SNMP trap, or Tioli Enterprise Console Eent). Install additional language support. Associate system users with IBM Tioli Serice Leel Adisor roles. After all required and optional procedures hae been completed, you must stop and restart the WebSphere Application Serer. These tasks are described in the sections that follow. Regenerating Web Serer Plug-in Configurations If you installed the SLM Administration Serer or SLM Reports options of IBM Tioli Serice Leel Adisor on this machine, you must instruct the IBM WebSphere Application Serer plug-in to regenerate its configuration. Note: If you selected to regenerate the plug-in configuration during the installation process, you can skip this task. See Figure 42 on page 82. You should regenerate the plug-in configuration after completing any of the following tasks: Installing or remoing an enterprise application Adding or remoing serlets and mappings from a particular application Manually changing the configuration for the plug-in, a irtual host or a transport Failure to regenerate the plug-in after introducing a new application likely results in a 404 File Not Found error when a user tries to access the new Web application. Copyright IBM Corp. 2002,

106 For IBM Tioli Serice Leel Adisor, because you installed the SLM Administration Serer or SLM Reports options to IBM WebSphere Application Serer, if you attempt to open the SLM Administratie Console or SLM Reports console without regenerating the plug-in, the Web browser fails to locate and display the proper Web page. Note: There might be manual configuration changes already in the plug-in file. Regenerating the plug-in configuration can oerwrite manual configuration changes that you might want to presere first. Before performing this task, refer to the documentation concerning Configuring Web serer plug-ins in the WebSphere Information Center, and backup your configuration file before regenerating the plug-in. After regeneration, you need to manually restore the manual configuration changes. To regenerate the plug-in configuration, you can do either of the following tasks before restarting the WebSphere Application Serer: Bring up the WebSphere Administratie Console and use the Update Web Serer Plugin Configuration page. Naigate to <WAS_Dir>/bin directory, where <WAS_Dir> is the location where IBM WebSphere Application Serer was installed, and run the GenPluginCfg script. As an alternatie to regenerating the plug-in, you can also manually edit the configuration file to add the serlet contexts for IBM Tioli Serice Leel Adisor to the file. Refer to the WebSphere Information Center for more information. Configuring ODBC Data Sources Before installing the warehouse enablement pack for IBM Tioli Serice Leel Adisor, including the Registration ETL and the Process ETL, you must create and configure the ODBC data sources on the machine where the Data Warehouse Center is located and where the Registration and Process ETLs will be located. This information tells the Data Warehouse Center on which machines the Tioli Data Warehouse database, the SLM Database, and SLM Measurement Data Mart are located, to manage data transfer between the warehouse and SLM application databases. Configuring ODBC Data Sources for Distributed Enironments If your two SLM databases are located on distributed systems (that is, on operating systems other than z/os), two scripts are proided to automatically create the ODBC data sources for these two databases: The dyk_cat_odbc.bat script creates an ODBC data source named DYK_CAT for the SLM Database. The dyk_dm_odbc.bat script creates an ODBC data source named DYK_DM for the SLM Measurement Data Mart. These scripts assume the following default alues: The SLM Database default name is dyk_cat The SLM Measurement Data Mart default name is dyk_dm The DB2 communication port default alue is The ODBC data source aliases are created with the default alias names DYK_CAT and DYK_DM. 88 IBM Tioli Serice Leel Adisor: Getting Started

107 To configure ODBC data sources for distributed SLM databases using these scripts, complete the following steps: 1. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie on the machine where the Data Warehouse Center is located. 2. Open a DB2 command window (click Start > Run and enter the command: db2cmd). 3. Naigate to the <CD-Rom>\database\scripts\w32-ix86\ directory and issue the following command to create the ODBC data source for the SLM Database: dyk_cat_odbc.bat <fully_qualified_machine_name> In this command, <fully_qualified_machine name> is the fully qualified machine name of the local or remote DB2 serer where the SLM Database is located. For example: dyk_cat_odbc.bat UserABC.raleigh.ibm.com 4. Similarly, issue the following command to create the ODBC data source for the SLM Measurement Data Mart: dyk_dm_odbc.bat <fully_qualified_machine_name> In this command, <fully_qualified_machine name> is the fully qualified machine name of the local or remote DB2 serer where the SLM Measurement Data Mart is located. For example: dyk_dm_odbc.bat UserABC.raleigh.ibm.com Additional ODBC Data Source Configuration Methods You might want to configure your ODBC data sources for the SLM databases without using these script files, if any of the following conditions are applicable: You want to use other alues than the default alues that are proided in these scripts You prefer to create the ODBC data sources manually You want to configure ODBC data sources for SLM databases that are located remotely on z/os operating systems. See Appendix F, Manually Creating ODBC Data Sources, on page 177 for additional information on configuring ODBC data sources. Verifying ODBC Configuration You can erify that these ODBC data sources were successfully configured on the machine where the Data Warehouse Center is located by clicking Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC), and selecting the System DSN tab. The resulting list of ODBC data sources that is displayed should include entries for the default alias names DYK_CAT and DYK_DM. Installing the Target Warehouse Enablement Pack IBM Tioli Serice Leel Adisor includes a warehouse enablement pack that uses two target ETLs to moe and transform data from the Tioli Data Warehouse central data warehouse database to its application databases: The Registration ETL moes component type information from the central data warehouse to the SLM Database, where it is used during offering and SLA creation. The Process ETL moes measurement data from the central data warehouse to the SLM Measurement Data Mart, where it is ealuated for serice leel iolations and trends toward iolations by IBM Tioli Serice Leel Adisor. Chapter 5. Additional Installation Tasks 89

108 A third target ETL, the Purge ETL, is aailable to purge old data from the SLM Measurement Data Mart to preent the database from becoming too large oer time. These target ETLs are installed on the machine where the control serer is located. There are two ersions of the target ETL that you can install, one that is designed to operate with Tioli Data Warehouse 1.2, and the other designed to operate with Tioli Enterprise Data Warehouse 1.1, if you do not choose to upgrade Tioli Data Warehouse to ersion 1.2. Installing and configuring the target warehouse pack and configuring the ETLs inoles completing the following steps, which are described in the sections that follow: 1. Install the IBM Tioli Serice Leel Adisor target warehouse pack: For the Tioli Data Warehouse 1.2 based target warehouse pack, run the separate warehouse pack installation program included with Tioli Data Warehouse 1.2. For the Tioli Enterprise Data Warehouse 1.1 based target warehouse pack, run the Tioli Enterprise Data Warehouse 1.1 installation program and use the Application Only installation option. 2. Configure the warehouse target user ID and password for the SLM Database and the SLM Measurement Data Mart. For the Tioli Enterprise Data Warehouse 1.1 based target warehouse pack, you must also configure the source user ID and password for these databases. This is handled automatically for the Tioli Data Warehouse 1.2 based target warehouse pack. 3. Enable data collection for all source applications that are writing data of interest to Tioli Data Warehouse before running the IBM Tioli Serice Leel Adisor target Registration ETL and Process ETL. 4. Schedule the Registration ETL and Process ETL to run at regular interals, and schedule the Purge ETL to purge old data periodically from the SLM Measurement Data Mart. 5. Promote the ETLs to production mode. 6. Optionally run the Registration and Process ETLs to moe data into the SLM Database and SLM Measurement Data Mart if you do not want to wait for the scheduled run time. 7. Optional: Register applications with IBM Tioli Serice Leel Adisor if you do not want to wait for the automatic registration to occur after the Registration ETL has run. This installation procedure references files used and databases created during the installation of Tioli Data Warehouse. Refer to the Tioli Data Warehouse installation documentation for more information. Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment The installation of Tioli Data Warehouse 1.2 includes a separate warehouse pack installation program for installing source and target warehouse packs. The following steps install the Registration ETL, Process ETL, and Purge ETL into the Data Warehouse Center on the DB2 serer machine where the control serer is installed (refer to the installation procedures in Installing and Configuring Tioli Data Warehouse for additional information). 90 IBM Tioli Serice Leel Adisor: Getting Started

109 To install the IBM Tioli Serice Leel Adisor DYK target warehouse pack, complete the following steps: 1. The warehouse pack installation program is included in the installation of Tioli Data Warehouse ersion 1.2. You can start the warehouse pack installation program by doing either of the following steps: Click Start -> Programs -> Tioli Data Warehouse -> Install a Warehouse Pack. From a command prompt, naigate to %TWH_TOPDIR%\install\bin, where %TWH_TOPDIR% is the directory in which Tioli Data Warehouse was installed (for example, C:\TDW12), and run the twh_wepinstall.bat script. 2. On the Welcome window, click Next to continue. 3. A window is displayed indicating the location of the Tioli Common Directory and associated log files for this program. Click Next to continue. 4. The installation program searches for aailable databases and other information it needs, and after a few moments a window is displayed from which you can create a list of warehouse packs to be installed. Click Add to add a warehouse pack to the list. 5. On the next window, click Browse to naigate to the location of the twh_install_props.cfg file. For this IBM Tioli Serice Leel Adisor target warehouse pack, the file is located on the IBM Tioli Serice Leel Adisor installation CD at: <CD_Drie>\tedw_apps_etl\dyk\twh_install_props.cfg. Select this file and click OK. Select the correct directory: There is a second directory, \tedw_apps_etl\dy1 that contains the.cfg file for the source warehouse pack for IBM Tioli Serice Leel Adisor (see Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105). Be sure to select the correct (\dyk) directory for the target warehouse pack. 6. You are returned to the preious window with the file selected in the File Name field. Click Next to continue. 7. The installation program then reads the properties file information and displays another page, identifying the central data warehouse for which the warehouse pack is configured, and the fully qualified hostname of the warehouse agent site that runs the central data warehouse ETL. Change this information as needed, or accept the defaults as presented. Click Next to continue. 8. The list of warehouse packs to install is then displayed, and you should see the IBM Tioli Serice Leel Adisor warehouse pack name listed. The ersion of the warehouse pack (for example, ) is also displayed, along with type and leel information. You can continue to add additional warehouse packs to the list, such as the IBM Tioli Serice Leel Adisor source warehouse pack (see Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105). To edit or remoe the warehouse pack from the list, you can select the radio button next to the warehouse pack name and click Edit or Remoe. When you are finished adding, editing, or remoing warehouse packs in the installation list, click Next to continue. 9. A summary window is displayed, specifying the warehouse packs that will be installed. Confirm your selections and click Install to begin the installation, or click Back to make changes, or Cancel to cancel the installation. 10. The installation takes a few minutes. When the installation completes, a window is displayed showing the status of the installation for each warehouse Chapter 5. Additional Installation Tasks 91

110 pack that you installed. You might see seeral warning messages, but the left-hand column should contain the word Success. Click Finish to exit the installer. After installing the target warehouse pack, there are additional configuration steps to complete. Proceed to Configuring the User ID and Password on page 93 to continue this installation process. Installing the Target Warehouse Pack for the Tioli Enterprise Data Warehouse 1.1 Enironment The installation program used to install Tioli Enterprise Data Warehouse 1.1 is also used to install warehouse packs in the Tioli Enterprise Data Warehouse 1.1 enironment, using the Application installation only option of the installation wizard. The following steps install the Registration ETL, Process ETL, and Purge ETL into the Data Warehouse Center on the DB2 serer machine where the control serer is installed (refer to the installation procedures in Installing and Configuring Tioli Enterprise Data Warehouse for additional information). To install the IBM Tioli Serice Leel Adisor DYK target warehouse pack for Tioli Enterprise Data Warehouse 1.1, complete the following steps: 1. Insert the Tioli Enterprise Data Warehouse 1.1 product CD to start the installation program. 2. On the Welcome window, click Next to continue. 3. Click Application installation only from the installation dialog and click Next to continue. 4. You are prompted to erify the fully qualified hostname of the local machine. The input field should contain your local machine hostname by default. Verify this information and modify it if needed. Click Next to continue. 5. Enter your local DB2 user name and password. Click Next to continue. 6. You are prompted to enter the path to the installation media for the application packages. The Registration ETL and Process ETL are located on the IBM Tioli Serice Leel Adisor product CD. To specify the DYK application package, complete the following steps: Remoe the Tioli Data Warehouse product CD and insert the IBM Tioli Serice Leel Adisor product CD. Click Browse and naigate to the following directory, where <Install_CD> is the drie letter of the CD-ROM drie: <Install_CD>:\tedw_apps_etl_1.1\dyk\ Select this directory. 7. On the Application Package Directory Name window, erify that the directory name is specified as <CD_ROM>:\tedw_apps_etl_1.1\dyk\, where <CD_ROM> is the CD-ROM drie letter. 8. Leae the Now radio button selected to erify the source directory, and click Next to continue. 9. On the Additional Applications Packages window, erify that the Yes, install application packages check box is not selected, and click Next to continue. 10. On the feature summary dialog showing your selections, confirm your selections and click Install to begin the installation. The installation takes a few minutes. When the installation completes, you should receie the following message: CDWIA0000I Installation of the application packages completed successfully. 92 IBM Tioli Serice Leel Adisor: Getting Started

111 After installing the target warehouse pack, there are additional configuration steps to complete. Continue with the next section, Configuring the User ID and Password to continue this installation process. Configuring the User ID and Password After installing the target warehouse pack, you must configure the user ID and password for the SLM Database and the SLM Measurement Data Mart. For the Tioli Data Warehouse 1.2 enironment, you only need to configure the target user ID and password. For the Tioli Enterprise Data Warehouse 1.1 enironment, you must configure the target and source user ID and password for each database. To configure the user ID and password for the SLM Database and the SLM Measurement Data Mart databases, complete the following steps: 1. Bring up the DB2 Control Center by clicking Start > Programs > IBM DB2 > Control Center 2. From the DB2 Control Center, launch the Data Warehouse Center by clicking Tools > Data Warehouse Center. 3. You are prompted to log into the Data Warehouse Center. Before you do, you can click Adanced and erify that TWH_MD appears in the Control Database field (this step should hae already been completed during installation of Tioli Data Warehouse). If not (it might be initially set to DWCTRLDB), change this field to TWH_MD. 4. Log into the Data Warehouse Center using your DB2 username and password. If you cannot log in: You might need to restart the Warehouse Logger and the Warehouse Serer serices from the Serices control panel to reconnect to the TWH_MD database. 5. In the left pane of the Data Warehouse Center, expand the Warehouse Targets folder, as shown in Figure 46. Figure 46. Display Warehouse Targets in the Data Warehouse Center. 6. To configure the user ID and password for the two DYK target databases, complete the following steps: a. Highlight the DYK_DYK_CAT_Target entry under the expanded Warehouse Targets folder and then from the toolbar at the top click Selected > Chapter 5. Additional Installation Tasks 93

112 Properties, or alternatiely, right-click the entry and click Properties to launch the Properties dialog, as shown in Figure 46 on page 93. b. In the Properties window, click the Database tab, as shown in Figure 47. Figure 47. Select the Database tab to configure user ID and password for this warehouse target. c. Enter the DB2 user ID and password information for the database (the database name matches one of the ODBC data sources that you configured. See Configuring ODBC Data Sources on page 88 for details.) and click OK, as shown in Figure 48. Figure 48. Enter the DB2 user ID and password (twice) for this warehouse target. d. Repeat the aboe steps for the DYK_DYK_DM_Target entry under the Warehouse Targets folder. 94 IBM Tioli Serice Leel Adisor: Getting Started

113 7. If you are configuring for the Tioli Enterprise Data Warehouse 1.1 enironment, repeat the preious steps for the DYK_TWH_CDW_Source entry under the Warehouse Sources folder. When finished, close the Data Warehouse Center and Control Center windows. Enabling Data Collection for Source Applications By default, the Registration ETL and Process ETL do not collect any data from the Tioli Data Warehouse database until one or more source applications are added to the SLM enironment and enabled for data collection. Only data types from source applications that are part of the SLM enironment and that are enabled are recognized by IBM Tioli Serice Leel Adisor during offering and SLA creation. Displaying Source Applications that are in the SLM Enironment There are some source applications that were added to the SLM enironment by default, but are not yet enabled for data collection. You can display a list of source applications that were added by completing the following steps: 1. Open a command prompt and naigate to the location where you installed IBM Tioli Serice Leel Adisor (for example, C:\TSLA) 2. Initialize the SLM enironment by issuing the following command: For Windows systems: slmen For UNIX systems:../slmen Prepare the SLM enironment: The slmen command is used to prepare the SLM enironment for the issuing of scmd commands. You must run this command at least once, from the directory where you installed IBM Tioli Serice Leel Adisor, before issuing any scmd commands. Note: 3. At the command prompt, issue the following command: scmd etl getapps 4. You should receie output similar to the following example: Measurement Source Code: BWM Application Name: Tioli Monitoring for Transaction Performance - Web Transaction Performance Flag: N Measurement Source Code: APF Application Name: IBM Tioli Monitoring for Transaction Performance - Enterprise Transaction Performance Flag: N Measurement Source Code: DMN Application Name: Distributed Monitoring Classic Edition Flag: N (...and others) The measurement source code specifies the code name for the source application that is to be enabled. The Flag that specifies whether or not the source application is enabled for data collection, and has a alue of Y (yes) or N (no). Initially these Chapter 5. Additional Installation Tasks 95

114 source applications were added to the SLM enironment, but are not yet enabled for data collection. Only after they are enabled, by haing their Flag alue set to Y, the Registration ETL and Process ETL are able to transfer data for that source application from Tioli Data Warehouse to IBM Tioli Serice Leel Adisor for ealuation. Enabling Existing Source Applications for Data Collection You can use another command, scmd etl enable, to enable these source applications for data collection. For example, to enable IBM Tioli Monitoring for Web Infrastructure: Apache HTTP Serer (with measurement source code GWA), issue the following command: scmd etl enable GWA You should receie a message stating that the application is enabled. If you then issue the scmd etl getapps command again, you should see that the alue of the enable flag is set to Y for this application. When the Registration ETL is next run, data type information for IBM Tioli Monitoring for Web Infrastructure: Apache HTTP Serer is collected for use by IBM Tioli Serice Leel Adisor, and the Process ETL collects measurement data related to this application. Applications proiding state transition data using the Tioli Common Data Model, such as Tioli Monitoring for Transaction Performance - Web Transaction Performance (measurement source code BWM) and Tioli Enterprise Console (measurement code EC1), should also enable the MODEL1 measurement source code for IBM Tioli Serice Leel Adisor. In this case, issue two separate enable commands, similar to the following example: scmd etl enable BWM scmd etl enable MODEL1 Consult the warehouse pack implementation guide for each source application for additional information on what measurement source codes to enable for proper metric information and data collection in IBM Tioli Serice Leel Adisor. Refer also to Finding the Measurement Source Code for an Application on page 98. Enabling Support for Transaction Success Rate Deried Metrics If you plan to create SLAs based on transaction success rate, the metric is a deried metric that must be registered in IBM Tioli Serice Leel Adisor from special measurement groups. These measurement groups are created to group measurement types that support sample count data and error count data. These groups can then be detected by the IBM Tioli Serice Leel Adisor registration process and the appropriate deried metric can be registered. An optional script can be run to group the measurement types that are currently known to support sample count and error count. This includes measurement types for Tioli Web Serices Manager (measurement source code BWM) and Tioli Application Performance Management (measurement source code APF). The specific measurement types that are included in these groups are shown in Table 13 on page 97: 96 IBM Tioli Serice Leel Adisor: Getting Started

115 Table 13. Measurement types that support sample count and error count. Application Measurement Type Description Tioli Web Serices Manager (BWM) Round Trip Time Round Trip Response Time Tioli Application Performance Management (APF) Serice Time Page Render Time Response Time Backend Serice Response Time Page Render Response Time Transaction Response Time To group these measurement types for proper registration in IBM Tioli Serice Leel Adisor, complete the following steps: 1. On the machine where the Tioli Data Warehouse 1.2 control serer is located, open a DB2 command window (Start > Programs > IBM DB2 > Command Window, or Start > Run > db2cmd). 2. Naigate to the <TWH_Dir>\apps\dyk\210120\misc folder, where <TWH_Dir> is the location where Tioli Data Warehouse 1.2 was installed, for example, C:\TWH Issue the following command to run the addsamerrgroups.bat script: addsamerrgroups.bat <CDW ODBC Name> <db2userid> <db2password> In this command, include alues for the following arguments: CDW ODBC Name This is the ODBC name of the central data warehouse that is modified with the new measurement type groupings. This command supports a central data warehouse located on a distributed or z/os operating system. db2userid This is the user name for the database administratie user with authority to access the specified central data warehouse. db2password This is the password for the specified database administratie user. 4. This utility only needs to run one time to create these new measurement groups. Enabling Additional Ealuation Frequencies Most typical source applications write measurement data to the Tioli Data Warehouse database as often as once per day. You might also hae one or more source applications that write measurement data more than once per day, for example, eery hour, or eery four hours. In this case, you might also want to perform ealuations more often than once per day. When you create an offering (described in the Managing Serice Leel Agreements document), part of that process inoles configuring how often ealuations are performed. By default you can choose to ealuate on a monthly, weekly, or daily frequency. If you want to perform ealuations more than once per day, you must run the scmd mem showhourlyfrequencyinterals CLI command to enable the following additional ealuation frequencies for selection during the offering creation process: Eery Hour Chapter 5. Additional Installation Tasks 97

116 Eery 2 Hours Eery 3 Hours Eery 4 Hours Eery 6 Hours Eery 8 Hours Eery 12 Hours You should consult with your SLM Administrator to erify that the measurement data in which you are interested is being written to the warehouse database at the specified frequency. To enable additional ealuation frequencies, complete the following steps: 1. On the computer where the SLM Serer is located, open a Command Prompt window, and naigate to <TSLA_Dir>, the directory where IBM Tioli Serice Leel Adisor was installed (for example, C:\TSLA). 2. Initialize the CLI command enironment by issuing the following command: slmen 3. Issue the following command to enable additional ealuation frequency settings: scmd mem showhourlyfrequencyinterals enable See the Command Reference document for additional information about this and other CLI commands. Adding new Source Applications to the SLM Enironment If you know the measurement source code for your source application, you can add it to the SLM enironment and enable it for data collection by issuing the scmd etl addapplicationdata command. For example, to enable IBM Tioli Monitoring for Operating Systems, whose measurement source code is AMY, issue the following command: scmd etl addapplicationdata AMY "IBM Tioli Monitoring for Operating Systems" This command adds the source application to the SLM enironment and sets the enable flag to Y (eliminating the need for you to issue the scmd etl enable command for this source application). Finding the Measurement Source Code for an Application If you do not know the measurement source code for an application that you want to enable for data collection, check the implementation guide that accompanies the warehouse enablement pack for source applications that put data into Tioli Data Warehouse. This document contains a Measurement Source (Msrc) Table. Find this table and locate the Msrc_Cd column to determine the measurement source code for your application. A list of supported source applications and their measurement codes is aailable on the IBM Tioli Serice Leel Adisor Support Web site: /IBMTioliSericeLeelAdisor.html From this Web page, you can search for references to the text string, measurement source code. In the search results, locate the link titled, Finding the Measurement Source Code to Enable a Source Application, for additional information about supported source applications and their measurement source codes. 98 IBM Tioli Serice Leel Adisor: Getting Started

117 Disabling Source Applications to Preent Data Collection If you later decide to disable a source application for which you do not want to collect data, you can issue the scmd etl disable command. For example, to disable IBM Tioli Monitoring for Transaction Performance - Enterprise Transaction Performance, whose measurement source code is APF, issue the command: scmd etl disable APF This changes the alue of the enable flag to N and disables the source application from further data collection, until you enable it again with the scmd etl enable command. Refer to the Command Reference for details on these and other CLI commands. Configuring for Multiple Central Data Warehouses Your Tioli Data Warehouse 1.2 enironment might be configured to include more than one central data warehouse (refer to Installing and Configuring Tioli Data Warehouse for details on creating multiple central data warehouses). In addition to TWH_CDW, which is automatically created when Tioli Data Warehouse is installed, these additional central data warehouse databases hae names such as TCDW1, and TCDW2, with corresponding ODBC data source names such as TWH_CDW1, and TWH_CDW2. If you hae multiple central data warehouse databases in your enironment for which you want to obtain measurement data, complete the following additional steps to configure the IBM Tioli Serice Leel Adisor target warehouse pack (only for use with Tioli Data Warehouse 1.2) to handle multiple central data warehouse databases: 1. From a command prompt, naigate to %TWH_TOPDIR%\tools\bin, where %TWH_TOPDIR% is the directory in which Tioli Data Warehouse 1.2 was installed (for example, C:\TDW12). 2. Run the twh_configwep.bat script to configure the IBM Tioli Serice Leel Adisor target ETLs to extract data from more than one central data warehouse. The syntax of the command is as follows: twh_configwep.bat -u <db2userid> -p <db2password> -f add -c <configfile> In this command, <db2userid> and <db2password> are the DB2 user ID and password authorized for access to the Control Center, and <configfile> is the configuration file, for example, dyk_mcdw.cfg, that specifies the central data warehouse parameters needed to add a central data warehouse to the warehouse pack. For example, suppose you want to add a second central data warehouse named TCDW1 (with an ODBC data source name of TWH_CDW1) and a third central data warehouse named TCDW2 (with an ODBC data source name of TWH_CDW2) to the target warehouse pack. You would create a configuration file such as dyk_mcdw.cfg, containing the following lines: # ADD TWO CENTRAL DATA WAREHOUSE DATABASES TO THE WAREHOUSE PACK # WAREHOUSE PACK PRODUCT CODE AVA_CODE=DYK # ADD THE SECOND CENTRAL DATA WAREHOUSE TDW_CDW1_ODBC_DS_NAME=TWH_CDW1 # ADD THE THIRD CENTRAL DATA WAREHOUSE TDW_CDW2_ODBC_DS_NAME=TWH_CDW2 Sae this configuration file and specify its name and location when you run the twh_configwep script. Chapter 5. Additional Installation Tasks 99

118 The twh_configwep script should return a successful completion message, but you can erify that the DYK warehouse pack is properly configured to extract data from the additional central data warehouse by issuing the following command: twh_configwep.bat -u <db2userid> -p <db2password> -f list The output of this command should show that the central data warehouse being added is associated with the DYK warehouse pack. 3. After running the twh_configwep script successfully, complete the following steps to add some additional extract-control records to one of the tables in the target central data warehouse that is being added and configured: a. From the command prompt, naigate to %TWH_TOPDIR%\apps\dyk\210120\cdw\dml. b. Issue the following command: execsql2 -n dyk_cdw_data -s <ODBC_CDW> -u <db2userid> -p <db2password> In the aboe command, <ODBC _CDW> is the ODBC name (not the database name) of the additional central data warehouse for which the DYK warehouse pack is being configured, and <db2userid> and <db2password> are the alid DB2 Uniersal Database user ID and password that hae authority to connect to the specified ODBC datasource. c. Examine the contents of the TWG.EXTRACT_CONTROL table in the central data warehouse that is being added. There are 4 records added to this table that are needed by the DYK warehouse pack. After connecting to the central data warehouse, issue the following query: select count(*) from TWG.EXTRACT_CONTROL where EXTCTL_TARGET LIKE DYK% A result of 4 indicates that the execsql2 command was successful. A result of 0 indicates that the command failed. See Appendix A in Installing and Configuring Tioli Data Warehouse for more information on the twh_configwep utility. Configuring Target ETL Table Translation Information for SLM Databases on z/os If you are using Tioli Data Warehouse 1.2 and located your SLM databases on a z/os operating system, before running the target ETL for the first time, you must first run a script to configure the database translation information that the target ETL processes use. Failure to complete this step might result in failures during ETL processing. Note: If your SLM databases are not located in a z/os operating system, you can skip this task. To configure this database information, complete the following steps: 1. Verify that the target warehouse pack installed successfully. 2. On the machine where the Tioli Data Warehouse 1.2 control serer is located, open a Command Prompt window. 3. Naigate to the <TWH_Dir>\apps\dyk\210120\misc folder, where <TWH_Dir> is the location where Tioli Data Warehouse 1.2 was installed, for example, C:\TWH12 4. Issue the following command to run the dyk_translate.bat script: 100 IBM Tioli Serice Leel Adisor: Getting Started

119 dyk_translate.bat <catdb> <cattbspace> <catutbspace> <dmdb> <dmtbspace> <dmutbspace> In this command, include alues for the following arguments: catdb This is the name of the SLM Database as defined in DB2 for z/os, for example, DYKCAT. cattbspace This is the name of the default tablespace in the SLM Database that you defined in the Tablespace Name field during creation of the SLM Database on a z/os operating system. Refer to Figure 15 on page 56 for this information. catutbspace This is the name of the default UTF-8 encoded tablespace in the SLM Database that you defined in the UTF8 Tablespace Name field during creation of the SLM Database on a z/os operating system. Refer to Figure 15 on page 56 for this information. dmdb This is the name of the SLM Measurement Data Mart as defined in DB2 for z/os, for example, DYKDM. dmtbspace This is the name of the default tablespace in the SLM Measurement Data Mart that you defined in the Tablespace Name field during creation of the SLM Measurement Data Mart on a z/os operating system. Refer to Figure 15 on page 56 for this information. dmutbspace This is the name of the default UTF-8 encoded tablespace in the SLM Measurement Data Mart that you defined in the UTF8 Tablespace Name field during creation of the SLM Measurement Data Mart on a z/os operating system. Refer to Figure 15 on page 56 for this information. The result of this command is to store the database and tablespace name information in <TWH_Dir>\apps\translate\dyk_my.translate for use by the target ETL processes. You can iew this file in a text editor to erify that this information was stored successfully. Configuring ETLs for Production Mode Before you can run the ETLs, you must configure them by completing the following steps: 1. Defining a schedule for when the ETLs will be automatically run. 2. Promote the mode of the ETLs from deelopment or test mode to production mode. Scheduling ETLs To schedule the ETLs to run automatically, complete the following steps: 1. From the left pane of the Data Warehouse Center window, expand the Subject Areas folder. Under the Subject Areas folder, you should see one branch of the tree with the prefix DYK. Expand this branch of the tree and then expand the Processes folder to show the indiidual ETL processes for IBM Tioli Serice Leel Adisor: The Registration ETL: DYK_m05_Populate_Registration_Datamart_Process The Process ETL: Chapter 5. Additional Installation Tasks 101

120 DYK_m10_Populate_Measurement_Datamart_Process The Purge ETL (see Scheduling the Purge ETL ): DYK_m15_Purge_Measurement_Datamart_Process 2. In the left pane, highlight one of these DYK processes in the Processes folder and then click Selected > Schedule from the options bar at the top of the window, or right-click the process name and click Schedule from the context menu that is displayed, to launch the Schedule wizard. 3. In the Schedule wizard, create a schedule by configuring the interal, frequency, day, and start and end time, from the aailable selection and drop down lists. Notes: a. As you schedule the ETLs to run, consider the following restrictions: The source applications put their collected data into the warehouse database according to unique schedules defined for their enironment. Be sure to allow enough time for the source application ETLs to complete before running the Registration and Process ETLs. The Registration ETL must be scheduled to run after the last source ETL completes processing, and must complete its processing to moe data type information from the warehouse to the SLM Database (dyk_cat) before the Process ETL is run. The Process ETL must be scheduled to run after the Registration ETL has completed processing. See Chapter 1 of the Administrator s Guide for an oeriew of the source and target ETLs and their relationship to each other. b. If you plan to schedule the ETL to run immediately, configure the start time for at least seeral minutes from the current time so you can complete these steps and promote the ETLs to production mode. After a schedule has been defined, you can always select it later and run it on demand instead of waiting for the set time to expire. 4. Click Add to add the schedule to the list. 5. Click OK when you are finished. 6. Repeat this scheduling procedure for each of the three DYK processes as needed. A fourth ETL: There is a fourth ETL, called DYK_m00_Initialize_Process that is not scheduled, but is only run once during an upgrade from a preious ersion of IBM Tioli Serice Leel Adisor. See Appendix H, Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor, on page 199 for the use of this ETL. Scheduling the Purge ETL Similar to the scheduling of the Registration and Process ETLs to production mode, you also must schedule the Purge ETL, DYK_m15_Purge_Measurement_Datamart_Process. You can think of this ETL as an extension of the Process ETL, as it purges old data from the SLM Measurement Data Mart (DYK_DM) database (data that was originally loaded by the Process ETL). This helps preent the SLM Measurement Data Mart from getting too large oer time. To schedule this ETL, use the same procedure as described in Configuring ETLs for Production Mode on page IBM Tioli Serice Leel Adisor: Getting Started

121 You can schedule this ETL to run at any time to control the remoal of old data. By default, the data remains in the SLM Measurement Data Mart for 63 days. You can iew the current expiration setting by issuing the scmd etl getdataexpiration command, and you can modify this alue by using the scmd etl setdataexpiration <number_of_days> command. When this ETL runs, it reads this alue and purges the SLM Measurement Data Mart of any measurement data records that are older than the configured expiration date. See the Command Reference for details on these and other scmd commands. Promoting ETLs to Production Mode After scheduling the ETLs to run automatically, promote them to production mode by completing the following steps: 1. For each process in the Processes folder, highlight the process in the left pane and notice (in the right pane of the Data Warehouse Center) all of the steps of the process that are displayed with the step number embedded in the step name in the form *_s<nnn>_*, where <nnn> is the step number. For example, for the Process ETL, these steps are displayed in the right pane as follows: DYK_m10_s010_Populate_SLM_AVL_Msmts DYK_m10_s020_Populate_SLM_Tot_Msmts DYK_m10_s030_Populate_SLM_MMA_Msmts DYK_m10_s040_Update_Extract_Control DYK_m10_s050_Record_Proc_History You can scroll horizontally in this display to iew the Mode column, and see that these processes are in one of three possible modes: Deelopment, Test, or Production. All of the steps that hae the prefix DYK and that are in Deelopment or Test mode must be promoted to Production mode for the ETL to run properly as scheduled. 2. Highlight all of these steps at the same time in the right pane, and promote them to production mode by clicking Selected > Mode > Production from the menu bar at the top of the window, or right-click the highlighted steps and select Mode > Production from the context menu that appears. 3. Repeat these steps for each of the three DYK processes in the Processes folder. After completing the aboe steps, the ETLs are in production mode, and are run according to the scheduled dates and times that you specified. You can also issue commands to run these ETLs at any time. Running the Registration ETL and Process ETL Depending on when you set the schedule for running the Registration ETL and Process ETL, you can either wait for the scheduled time and date to elapse for the ETL to be run automatically, or you can run the ETL immediately. When to run the ETLs: The Registration ETL and Process ETL should not be run until after the SLM Serer is installed and you hae enabled all source applications for which you want data to be collected. See the scmd etl enable and scmd etl addapplicationdata commands in the Command Reference for details on enabling source application data. If you hae databases on OS/390 or z/os systems: After installing, but before running any of the ETLs in the IBM Tioli Serice Leel Adisor target (DYK) or Chapter 5. Additional Installation Tasks 103

122 source (DY1) warehouse packs, you must run a script to configure the ETL processes to use the tablespace names that were chosen when the databases were created. Before running any ETLs in the target (DYK) warehouse pack, see Configuring Target ETL Table Translation Information for SLM Databases on z/os on page 100. Before running any ETLs in the source (DY1) warehouse pack, see Configuring Source ETL Table Translation Information for the SLM Database on z/os Operating Systems on page 106. If you choose to run the ETLs immediately, note that the Registration ETL must be run and all processing completed before running the Process ETL, otherwise errors occur in the data collection. From the Data Warehouse Center, you can monitor the progress of the ETLs by clicking Warehouse > Work in Progress and examining the Work in Progress window. You can find the ETLs scheduled to be run by looking in the Status column for Scheduled. You can run that ETL immediately by right-clicking it and clicking Run Now. The names of the processes are as follows: Registration: DYK_m05_Populate_Registration_Datamart_Process Process: DYK_m10_Populate_Measurement_Datamart_Process Purge: DYK_m15_Purge_Measurement_Datamart_Process The Work in Progress window displays each step as it runs, changing the status appropriately. When the status for all of the ETL steps is Successful, the ETL has completed. Run the Registration and Process ETLs in this order: 1. Open the Work In Progress window and select the scheduled entry that contains DYK_m05_s010_Populate_Reg_Datamart. 2. Right-click the entry and select Run Now. 3. Wait for all steps to complete and erify that all steps ran successfully before proceeding to the next step. 4. On the Work In Progress window, select the scheduled entry that contains DYK_m10_s010_Populate_SLM_AVL_Msmts 5. Right-click the entry and click Run Now. 6. Wait for all steps to complete and erify that all steps were successful. Registering Warehouse Data After you add and enable all of the source applications and run the Registration ETL at least once, the source applications are automatically registered with IBM Tioli Serice Leel Adisor approximately ten minutes after the Registration ETL has completed. You can register the source applications immediately by issuing the following command after the Registration ETL is completed: scmd sdc registerwarehousedata 104 IBM Tioli Serice Leel Adisor: Getting Started

123 Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor In addition to the target warehouse pack that includes the Registration and Process ETLs for collecting data from Tioli Data Warehouse (see Installing the Target Warehouse Enablement Pack on page 89) and the Purge ETL for remoing old data from the SLM Measurement Data Mart, IBM Tioli Serice Leel Adisor also proides a source warehouse pack that can be optionally installed to write IBM Tioli Serice Leel Adisor data back into the central data warehouse of Tioli Data Warehouse 1.2, for possible use by other applications. This is not required for a typical IBM Tioli Serice Leel Adisor installation, but might be useful if you hae other applications designed to use ealuation results from IBM Tioli Serice Leel Adisor. There might be certain limitations in using this source warehouse pack. Be sure to read the documentation accompanying this source warehouse pack for additional information before installing it. To install this source warehouse pack, open a Command Prompt window and complete the following steps: Note: This installation procedure assumes that the SLM Database (DYK_CAT) is already created, and that an ODBC data source with an alias name of DYK_CAT is already created on the Tioli Data Warehouse control serer where this warehouse pack is to be installed. You might hae specified an alias name different than DYK_CAT for the SLM Database. The procedures below assume that the alias name is DYK_CAT. 1. The warehouse pack installation program is included in the installation of Tioli Data Warehouse ersion 1.2. You can start the warehouse pack installation program by doing either of the following steps: Click Start -> Programs -> Tioli Data Warehouse -> Install a Warehouse Pack From a command prompt, naigate to %TWH_TOPDIR%\install\bin, where %TWH_TOPDIR% is the directory in which Tioli Data Warehouse 1.2 was installed (for example, C:\TDW12), and run the twh_wepinstall.bat script. 2. On the Welcome window, click Next to continue. 3. A window is displayed indicating the location of the Tioli Common Directory and associated log files for this program. Click Next to continue. 4. The installation program searches for aailable databases and other information it needs, and after a few moments a window is displayed from which you can create a list of warehouse packs to install. Click Add to add a warehouse pack to the list. 5. On the next window click Browse to naigate to the location of the twh_install_props.cfg file. For this IBM Tioli Serice Leel Adisor source warehouse pack, the file is located on the IBM Tioli Serice Leel Adisor installation CD at: <CD_Drie>\tedw_apps_etl\dy1\twh_install_props.cfg. Select this file and click OK. Select the correct directory: There is a second directory, \tedw_apps_etl\dyk that contains the.cfg file for the target warehouse pack for IBM Tioli Serice Leel Adisor (see Installing the Target Warehouse Enablement Pack on page 89 ). Be sure to select the correct (\dy1) directory for the source warehouse pack. Chapter 5. Additional Installation Tasks 105

124 6. You are returned to the preious window with the file selected in the File Name field. Click Next to continue. 7. The next window prompts you for the name of the central data warehouse to use as the target for the ETL. This should be TWH_CDW, or another name if you hae multiple central data warehouses configured. It also asks for the warehouse agent site hostname. This should match the fully qualified machine hostname. You can also specify the scheduled time for when this ETL is run each day. Accept the default alues in these fields or change the alues, and click Next to continue. 8. At this point, you might receie a warning about an ODBC data source already existing for DYK_CAT. If you receie this warning, you can ignore it and click Next to continue. 9. On the next window, select the DYK_CAT radio button and then click Edit. 10. Enter your user ID and password information for DYK_CAT and click Next to continue. 11. After a connection to the data source is erified by the warehouse pack installer, you are returned to the data source properties window. Click Next at the bottom of the window. 12. A summary window is displayed, specifying the warehouse packs that will be installed. Confirm your selections and click Install to begin the installation, or click Back to make changes, or Cancel to cancel the installation. 13. The installation takes a few minutes. When the installation completes, a window is displayed showing the status of the installation for each warehouse pack that you installed. You might see seeral warning messages, but the left-hand column should contain the word Success. Click Finish to exit the installer. After the installation, the warehouse sources and targets should already be configured with the DB2 user ID and password information and no further configuration should be necessary. The ETL is in production mode. Configuring Source ETL Table Translation Information for the SLM Database on z/os Operating Systems If you are using Tioli Data Warehouse 1.2 and located your SLM Database (DYKCAT) on a z/os operating system, before running the source ETL for the first time you must first run a script to configure the database translation information that the source ETL processes uses. Failure to complete this step might result in failures during ETL processing. Note: If your SLM Database is not located on a z/os operating system, you can skip this task. To configure this database information, complete the following steps: 1. Verify that the source warehouse pack installed successfully. 2. On the machine where the Tioli Data Warehouse 1.2 control serer is located, open a Command Prompt window 3. Naigate to the <TWH_Dir>\apps\dy1\210120\misc folder, where <TWH_Dir> is the location where Tioli Data Warehouse 1.2 was installed, for example, C:\TWH Issue the following command to run the dy1_translate.bat script: dy1_translate.bat <catdb> <cattbspace> <catutbspace> In this command, include alues for the following arguments: 106 IBM Tioli Serice Leel Adisor: Getting Started

125 catdb Configuring for Eent Notification This is the name of the SLM Database as defined in DB2 for z/os, for example, DYKCAT. cattbspace This is the name of the default tablespace in the SLM Database that you defined in the Tablespace Name field during creation of the SLM Database on a z/os operating system. Refer to Figure 15 on page 56 for this information. catutbspace This is the name of the default UTF-8 encoded tablespace in the SLM Database that you defined in the UTF8 Tablespace Name field during creation of the SLM Database on a z/os operating system. Refer to Figure 15 on page 56 for this information. The result of this command is to store the database and tablespace name information in <TWH_Dir>\apps\translate\dy1_my.translate for use by the source ETL processes. You can iew this file in a text editor to erify that this information was stored successfully. During the installation of IBM Tioli Serice Leel Adisor, you could specify the method by which eent notification occurs (see Step 10. Specify Eent Notification Methods on page 71). Depending on which method you selected, refer to the following sections for additional configuration steps for eent notification. Configuring for Notification by SNMP If you specified the SNMP Eent method for eent notification, you can load the MIB definitions file located in the <SLM_Install_Dir>/escalate directory, where <SLM_Install_Dir> is the directory where IBM Tioli Serice Leel Adisor is installed. Configuring for NetView To configure for SNMP traps that are forwarded to a NetView AIX serer, run the following script file, located in <SLM_Install_Dir>/escalate, in the machine where NetView AIX is installed:./slmaddtrapsunix.sh To reerse this operation, you can run the following script:./slmremoetrapsunix.sh To configure for SNMP traps that are forwarded to a NetView NT serer, run the following script file in the machine where NetView NT is installed: slmaddtrapswin.bat To reerse this operation, you can run the following script: slmremoetrapswin.bat Note that these script files are for use with NetView in an English language enironment. These are sample files that are proided to illustrate how traps that are sent by IBM Tioli Serice Leel Adisor could be formatted for reception on NetView running on a UNIX or Windows operating system. These files are not translated. If your trap reception operating system is not NetView (for example, if you are using a Microsoft Windows trap receier, HP Open View, or some other Chapter 5. Additional Installation Tasks 107

126 product as your central trap repository) and if it is not installed on an English language system, then you must customize these scripts to match your enironment. Configuring for Notification by Tioli Enterprise Console If you selected the Tioli Enterprise Console Eent method for eent notification, you need to import, load, and compile the SLM Class Definition file SLM.baroc, and optionally apply the sample rule file, slm.rls, that is proided with this installation of IBM Tioli Serice Leel Adisor. The rule defined in slm.rls correlates each trend or cancel eent request receied at the serer with preious eents that hae a matching metric name, schedule state, SLA name, and component name, and closes the corresponding eents. Another rule, slmdropparenteents.rls, can be loaded to the Tioli Enterprise Console serer to drop the tiered SLA eents. This sample rule set is proided to drop SLO iolation eents, trend eents, and trend cancel eents for parent SLAs (or top leel SLAs in a tiered SLA hierarchy). Eents with a non-blank alue in the Component SLA slot are identified as an eent for a parent SLA. This rule is only applicable if the scmd escalate parentslasescalation command has been issued to enable escalation for parent SLA eents. These files are located in the <SLM_Install_Dir>/escalate directory, where <SLM_Install_Dir> is the directory where IBM Tioli Serice Leel Adisor is installed. You must manually delete any preious ersion from the Tioli Enterprise Console graphical user interface before applying the new ersions of these files. See Chapter 3, Rules Bases and Rule Base Administration in the Tioli Enterprise Console Rule Builder s Guide to apply these files to your Tioli Enterprise Console enironment. Note: When adding rules files to the Tioli Enterprise Console rules base, be sure to add them before any inactie files, otherwise they are also treated as inactie. Verifying Notification Methods Regardless of which method of eent escalation and notification you selected ( , SNMP trap, or Tioli Enterprise Console eent), the IBM Tioli Serice Leel Adisor installation program does not check for configuration errors such as an address that is entered incorrectly. You can perform some basic erification of the notification method by issuing the following CLI command: scmd escalate test This command sends a test eent through each enabled method ( , SNMP trap, or Tioli Enterprise Console eent), and you must erify that the designated recipient successfully receied the test eent notification. If the test eent is not receied, you should check SMTP serer names, addresses, and port numbers to erify that the serer is working correctly. You can use the scmd escalate enable command to enable or disable eent notification methods, specifying the following escalation parameters: 108 IBM Tioli Serice Leel Adisor: Getting Started The addresses and SMTP serer name

127 Tioli Enterprise Console Serer name and port number SNMP destination, port, and community name Installing Language Support You can also use the scmd escalate customize command to make changes or corrections to subject lines and messages that are sent for eent notification. You can also use the scmd escalate update command to add or remoe addresses in the TO and CC lists, and change the SMTP serer name. See the Command Reference for information on scmd escalate test, scmd escalate enable, scmd escalate update , and other CLI commands. You might hae installed language support when IBM Tioli Serice Leel Adisor was initially installed (see Step 4. Select Installation Options on page 64), but if not, you can install additional language support for IBM Tioli Serice Leel Adisor after all of the initial installation options are successfully installed. If the SLM Serer, SLM Administration Serer and SLM Reports are installed on different machines, this installation procedure must be performed on each machine. Note: On UNIX systems, you must be the root user to run the installation program. On Windows systems, you must hae Administrator s priileges to run the installation program. You can install language support for any of the following languages: ja: Japanese ko: Korean de: German fr: French it: Italian es: Spanish zh_cn: Simplified Chinese zh_tw: Traditional Chinese pt_br: Brazilian Portuguese To install language support after the initial installation is complete, complete the following steps: 1. Verify that all of the IBM Tioli Serice Leel Adisor installation options are successfully installed. 2. Insert the IBM Tioli Serice Leel Adisor product CD into the local machine and start the IBM Tioli Serice Leel Adisor installation wizard LaunchPad (see Starting the LaunchPad on page 51). 3. From the main page of the LaunchPad, click Install product and follow the prompts until you get to Step 4. Select Installation Options on page 64. On this page of the wizard, only select the Install Language Support check box, and click Next to continue. Chapter 5. Additional Installation Tasks 109

128 Figure 49. Use the IBM Tioli Serice Leel Adisor LaunchPad to install language support. 4. A language support source file is included with IBM Tioli Serice Leel Adisor, and the next window displays the location of that file as the default source file to use. If you hae a different language support source file to install, specify it in the Language Support source file field, or use the Browse button to naigate to the file. After you hae selected the file to install, click Next to continue. 5. For each IBM Tioli Serice Leel Adisor installation option (SLM Serer, SLM Reports, or SLM Administration Serer), select the check boxes corresponding to the language support you want to install. Any languages that are already installed for each feature are marked as installed. If you select a language that is already installed, it is oerwritten. After you hae finished selecting the languages to be installed for each option, click Next to continue. 110 IBM Tioli Serice Leel Adisor: Getting Started

129 Figure 50. Select the languages that you want to install for each option. 6. A summary window is displayed for you to confirm your language selections. Click Next to continue. 7. The selected language files are then installed. If the SLM Serer is currently running, the program automatically shuts it down before continuing. 8. When the installation completes, a message indicating a successful installation is displayed. Click Finish to close the wizard and return to the main page of the LaunchPad. Messages or errors related to installing language support are written to the tracetsla2.1install.log in the Tioli Common Directory, under /DYK/logs/install. For SLM Reports, restart the WebSphere Application Serer after language support is installed. Viewing Reports in Double Byte Character Languages If you plan to iew SLM reports in double byte character languages, you must install the Worldtype font into the IBM WebSphere enironment. You can install the font proided on the IBM Tioli Serice Leel Adisor Documentation CD, or you can install your own font. Chapter 5. Additional Installation Tasks 111

130 The font proided with IBM Tioli Serice Leel Adisor is located on the Publications CD in the \fonts directory. The font file is named tnrwt_j.ttf. To install this font, complete the following steps: 1. Stop the IBM WebSphere Application Serer on the machine where the SLM Reports feature of IBM Tioli Serice Leel Adisor is installed. 2. Copy the Worldtype font into <WebSphere_Dir>\AppSerer\jaa\jre\lib\fonts, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer was installed. 3. Restart the IBM WebSphere Application Serer. If SLM Reports is installed on a Solaris operating system, you must also complete the following additional steps: 1. Edit the web.xml file, located at the following directory: <WebSphere_Dir>\AppSerer\config\cells\ <node_name>\applications\slmreport.ear\deployments \SLMReport\SLMReport.war\WEB-INF 2. In the web.xml file, locate the following lines of code: <init-param id="initparam_ "> <param-name>tsla.reportchartfontface</param-name> <param-alue></param-alue> </init-param> 3. Add the font to the <param-alue></param-alue> line. If you use the font file proided on the Documentation CD, the result will be similar to the following example: <init-param id="initparam_ "> <param-name>tsla.reportchartfontface</param-name> <param-alue>times New Roman WT J</param-alue> </init-param> 4. Sae the edited web.xml file. 5. Stop and then restart the IBM WebSphere Application Serer. Associating System Users with IBM Tioli Serice Leel Adisor Roles IBM Tioli Serice Leel Adisor uses a role based user interface to manage users and the tasks for which they are authorized. After you install IBM Tioli Serice Leel Adisor, when WebSphere security is enabled, you must sign on to the SLM Administratie Console with an authorized user name and password. This user name must already be associated with a specific role that determines the tasks that are aailable to you in the portfolio of the SLM Administratie Console. If WebSphere security is not enabled, the SLM Administratie Console is displayed with no user sign on page, and the user is assumed to be the default user name that was specified during installation, with SLM Administrator authority (see Step 11. Define SLM Administrator Authority and SLM Reports Access on page 77). For more information on associating system users with IBM Tioli Serice Leel Adisor roles, refer to the Administrator s Guide or consult your SLM Administrator. Restarting the WebSphere Application Serer After completing the installation and configuration of IBM Tioli Serice Leel Adisor as described in this chapter, stop and restart the WebSphere Application Serer (or, if you configured multiple application serers, stop and restart each serer). 112 IBM Tioli Serice Leel Adisor: Getting Started

131 To stop the WebSphere Application Serer, refer to Stopping IBM WebSphere Application Serer on page 120. To start the WebSphere Application Serer, refer to Starting IBM WebSphere Application Serer on page 115. After the WebSphere Application Serer has started successfully, you can access the SLM Administratie Console and SLM Reports. See Starting the SLM Administratie Console on page 117 and Starting the SLM Reports Console on page 118 for details. Chapter 5. Additional Installation Tasks 113

132 114 IBM Tioli Serice Leel Adisor: Getting Started

133 Chapter 6. Startup and Shutdown Procedures You can use the following procedures to start and shut down IBM Tioli Serice Leel Adisor, and IBM WebSphere Application Serer, referred to elsewhere in this document. IBM Tioli Serice Leel Adisor can be started and stopped as a local serice on supported Windows operating systems. On UNIX operating systems, shell scripts are aailable for startup and shutdown. Note: IBM Tioli Serice Leel Adisor starts automatically on all operating systems after installation and each time the system is restarted. Starting the IBM Tioli Serice Leel Adisor Solution The following sections describe the startup procedures: Starting IBM WebSphere Application Serer Starting the IBM HTTP Serices on page 116 Starting the WebSphere Administratie Console on page 116 Starting the SLM Serer on page 117 Starting the SLM Administratie Console on page 117 Starting the SLM Reports Console on page 118 Starting IBM WebSphere Application Serer Start the IBM WebSphere Application Serer by doing any one of the following tasks: For Windows systems, click Start > Programs > IBM WebSphere > Application Serer 5.1 > Start the Serer For Windows systems, from a command prompt, naigate to the <WebSphere_Dir>\bin directory, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer was installed, for example, C:\WebSphere\Appserer, and run either of the following commands: If WebSphere security is not enabled: startserer <serer> If WebSphere security is enabled: startserer <serer> -username <user> -password <password> If you hae more than one serer configured, you can issue multiple commands, similar to the following examples (assuming WebSphere security is enabled): startserer <serer> -username <user> -password <password> startserer <serer> -username <user> -password <password> For UNIX systems, complete the following steps: 1. Verify that the DISPLAY enironment ariable has been set to a alid XSerer display. This is important if you hae IBM WebSphere Application Serer running on a UNIX machine without a dedicated console attached to the system. If the DISPLAY enironment ariable is not set correctly, reports are not displayed. 2. Source the db2profile file locally, by naigating to the <db2_instance_directory>/sqllib directory, where <db2_instance_directory> is Copyright IBM Corp. 2002,

134 the home directory of the database administrator who created the DB2 instance, and issue the following command:. db2profile 3. Naigate to the <WebSphere_Dir>/bin directory, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer is installed, for example, /usr/websphere/appserer, and issue either of the following commands: If WebSphere security is not enabled:./startserer.sh <serer> If WebSphere security is enabled:./startserer.sh <serer> -username <user> -password <password> Wait for the serer to become actie (in the log file <WebSphere_Dir>/AppSerer/logs/<serer>/SystemOut.log, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer is installed, check for the following line: open for e-business Additional methods of starting the IBM WebSphere Application Serer are documented in the IBM WebSphere Application Serer documentation. Starting the IBM HTTP Serices Start the IBM HTTP Serer and IBM HTTP Administration serices if they are not already started by completing the following steps: For Windows systems, you can start these from the Serices control panel or by issuing the following commands from a command prompt: net start "ibm http serer" net start "ibm http administration" For UNIX systems: 1. From a command prompt, naigate to the <HTTP_Dir>/bin directory, where <HTTP_Dir> is the location where the IBM HTTP Serer was installed. Default locations for <HTTP_Dir> are as follows: For AIX systems, <HTTP_Dir> = /usr/httpserer For Solaris systems, <HTTP_Dir> = /opt/ibmhttpd For Linux systems, <HTTP_Dir> = /opt/ibmhttpserer For HP systems, <HTTP_Dir> = /opt/ibmhttpserer 2. Issue the following commands:./apachectl start./adminctl start Starting the WebSphere Administratie Console At a command prompt, start the WebSphere Administratie Console by completing the following steps: For Windows systems, click Start > Programs > IBM WebSphere > Application Serer 5.1 > Administratie Console. For UNIX systems, bring up a Web browser and type the following address: Sign on to the console using your authorized user ID and password. 116 IBM Tioli Serice Leel Adisor: Getting Started

135 Starting the SLM Serer Start the SLM Serer: For Windows systems, the SLM Serer is automatically started as a serice at the end of the installation process, and when the system is restarted. To manually start the SLM Serer, complete either of the following tasks: From the Serices control panel, erify that the IBM Tioli Serice Leel Adisor serice is not started. If it is not started, right-click IBM Tioli Serice Leel Adisor, and click Start from the context menu. From a command prompt, enter the following command: net start In the list of applications that are displayed, look for IBM Tioli Serice Leel Adisor. If it is not in the list, issue the following command to start IBM Tioli Serice Leel Adisor: net start tslm For UNIX systems, the SLM Serer is automatically started at the end of the installation process, and when the system is restarted. To manually start the SLM Serer, complete the following steps: 1. To determine whether the SLM Serer is started, issue the following command: ps -efl grep slm_start (For Solaris, the command is ps -ef) If you see a process that calls the slm_start.sh script, then this serice is started. Otherwise this serice is not started. 2. If the slm_start.sh script is not found, naigate to the <SLM_Serer_Install_Dir>/bin directory, where <SLM_Serer_Install_Dir> is the location where the SLM Serer is installed, and run the following script (note this is not the same as the slm_start.shscript):./slm_serice_start.sh For the AIX operating system, do not use the startsrc -s tslm command to start the SLM Serer. If you do, the installation program cannot automatically stop the serice during uninstallation or upgrade operations. On all operating systems, the standard output and standard error logs for the SLM Serer are located in the Tioli Common Directory as tslmout.txt and tslmerr.txt, respectiely. On AIX operating systems, additional log files, tslmsubsysout.txt and tslmsubsyserr.txt are created in the <SLM_Serer_Install_Dir>/log directory, when the subsystem is started. Starting the SLM Administratie Console To start the SLM Administratie Console, complete the following steps: 1. Open your Web browser and type the following location: In this location, enter alues for the following parameters: Fully_Qualified_Machine_Name This is the fully qualified name of the machine on which the SLM Administration Serer is installed, for example, mymachine.raleigh.ibm.com. Port This is the port number (the default is 80). Chapter 6. Startup and Shutdown Procedures 117

136 For example, if the SLM Administration Serer is installed on the machine named mymachine.raleigh.ibm.com, and the default port of 80 is configured, the Web browser location is entered as follows: 2. If WebSphere security is enabled, a Sign On window is displayed, prompting you for your user ID and password. You can sign on using the user name that was specified as the SLM Administrator during the installation of IBM Tioli Serice Leel Adisor (see Step 11. Define SLM Administrator Authority and SLM Reports Access on page 77) or any alid user name that has been associated with an SLM Administrator role. See the Administrator s Guide for more information on creating users and associating roles. From the SLM Administratie Console that is displayed, you can do tasks such as creating and managing schedules, offerings, customers, realms and SLAs, renaming resources, and managing iolations, depending on your assigned user role. In addition to the functions proided on the SLM Administratie Console, you can issue certain command line interface (CLI) commands from the machine on which you installed the SLM Serer. With these commands you can do arious configuration tasks and examine certain internal alues. See the Command Reference for details on the aailable CLI commands that you can run. Starting the SLM Reports Console You can iew Web-based reports on the results of SLA ealuations performed by IBM Tioli Serice Leel Adisor from your Web browser. To start the SLM Reports Console, complete the following steps: 1. Open your Web browser and type the following location: In this location, enter alues for the following parameters: Fully_Qualified_Machine_Name This is the fully qualified hostname of the machine on which the SLM Reports is installed. Port This is the port number (the default is 80). For example, if SLM Reports is installed on the machine named mymachine.raleigh.ibm.com, and the default port of 80 is configured, the Web browser location is entered as follows: 2. If WebSphere security is enabled, a Sign On window is displayed, prompting you for your user ID and password. Sign on with a alid user name and password assigned by your SLM Administrator. See the Administrator s Guide for additional information of creating and authorizing users for access to SLM Reports. From the SLM Report Console that is displayed, you can iew and print summary reports on iolations and trends, and you can examine more detailed reports and data to help determine the root cause of problems related to your SLAs. See the SLM Reports document for more information on doing these tasks. 118 IBM Tioli Serice Leel Adisor: Getting Started

137 Shutting Down the IBM Tioli Serice Leel Adisor Solution The following sections describe the shutdown procedures: Shutting Down the SLM Administratie Console Shutting Down the SLM Reports Console Shutting Down the SLM Serer Stopping IBM HTTP Serices Stopping IBM WebSphere Application Serer on page 120 Shutting Down the SLM Administratie Console Click the Sign Off icon (located in the top right corner of the SLM Administratie Console) and then close your Web browser to shut down the SLM Administratie Console. Shutting Down the SLM Reports Console Click Logoff and then close your Web browser to shut down the SLM Reports console. Shutting Down the SLM Serer The state information used for trend calculation is cleared when the SLM Serer is stopped. To minimize the impact of clearing state information on predicting new trends and canceling existing trends, stop the SLM Serer only when necessary. Shut down the SLM Serer by completing the following steps: For Windows systems: 1. Select the Serices administration tool (click Start > Settings > Control Panel > Administratie Tools > Serices). 2. Stop the SLM Serer by completing either of the following steps: From the Serices administration tool, right-click IBM Tioli Serice Leel Adisor and click Stop from the context menu. From a command prompt, issue the following command: net stop tslm For UNIX systems, naigate to the <SLM_Serer_Install_Dir>/bin directory, where <SLM_Serer_Install_Dir> is the location where the SLM Serer is installed, and issue the following command to run the slm_serice_stop.sh script:./slm_serice_stop.sh On all operating systems, the standard output and standard error logs for the SLM Serer are located in the Tioli Common Directory as tslmout.txt and tslmerr.txt, respectiely. On AIX operating systems, additional log files, tslmsubsysout.txt and tslmsubsyserr.txt are created in the <SLM_Serer_Install_Dir>/log directory when the subsystem is started. Stopping IBM HTTP Serices Stop the IBM HTTP Serer and IBM HTTP Administration serices by completing the following steps: For Windows systems, you can stop these serices from the Serices control panel or by issuing the following commands from a command prompt: net stop "ibm http serer" net stop "ibm http administration" Chapter 6. Startup and Shutdown Procedures 119

138 For UNIX systems, complete the following steps: 1. From a command prompt, naigate to the <HTTP_Dir>/bin directory, where <HTTP_Dir> is the location where the IBM HTTP Serer is installed. Default locations for <HTTP_Dir> are as follows: For AIX systems, <HTTP_Dir> = /usr/httpserer For Solaris systems, <HTTP_Dir> = /opt/ibmhttpd For Linux systems, <HTTP_Dir> = /opt/ibmhttpserer For HP systems, <HTTP_Dir> = /opt/ibmhttpserer 2. Issue the following commands:./apachectl stop./adminctl stop Stopping IBM WebSphere Application Serer Stop IBM WebSphere Application Serer by completing either of the following tasks: For Windows systems, from a command prompt, naigate to <WebSphere_Dir>\bin, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer is installed, for example, C:\WebSphere\Appserer. Issue the following command, where <serer> is the name of the application serer, such as serer1: stopserer <serer> This command assumes that WebSphere security is not enabled. If you hae multiple serers started, such as serer1 and serer2, issue multiple commands: stopserer serer1 stopserer serer2 If WebSphere security is enabled, you must also supply an authorized user name and password to shut down the serer: stopserer serer1 -username <user> -password <password> For UNIX systems, from a command prompt, naigate to the <WebSphere_Dir>/bin directory, where <WebSphere_Dir> is the directory where IBM WebSphere Application Serer was installed, such as /usr/websphere/appserer, and issue the following command (assuming WebSphere security is not enabled):./stopserer.sh serer1 If you hae multiple serers started, issue multiple commands, one for each serer, similar to the following example:./stopserer.sh serer1./stopserer.sh serer2 If WebSphere security is enabled, you must also supply an authorized user name and password to shut down the serer, similar to the following example:./stopserer.sh serer1 -username <user> -password <password> You can find additional methods of stopping the IBM WebSphere Application Serer in the documentations for IBM WebSphere Application Serer. 120 IBM Tioli Serice Leel Adisor: Getting Started

139 Chapter 7. Uninstalling IBM Tioli Serice Leel Adisor Uninstall IBM Tioli Serice Leel Adisor by completing the following general procedure: Verify that the WebSphere Application Serer is started. If your enironment uses a directory serice, such as Lightweight Directory Access Protocol (LDAP), for managing users, it must be up and running. Stop the SLM Serer. Run the uninstallation program on each machine where the SLM Administration Serer, SLM Reports, and the SLM Serer are installed. Select the language support option if you only want to uninstall language support separately. Uninstall the target warehouse pack (and, if installed, the optional source warehouse pack) for IBM Tioli Serice Leel Adisor. Drop SLM Database (DYK_CAT) and SLM Measurement Data Mart (DYK_DM) databases. Remoe ODBC data sources for these databases. Manually remoe miscellaneous files. In addition to uninstalling IBM Tioli Serice Leel Adisor, you might also want to uninstall the entire SLM solution, performed by completing the following general procedure: Uninstall source application warehouse packs Uninstall IBM WebSphere Application Serer (if not being used by other applications) Uninstall Tioli Data Warehouse (if not being used by other applications) Uninstall Tioli Presentation Serices (if using Tioli Enterprise Data Warehouse 1.1 and not being used by other applications) Uninstall source applications (if no longer being used without Tioli Data Warehouse) Uninstall DB2 Uniersal Database (if not being used by other applications) Refer to the documentation that is proided with these applications for more information on uninstallation. Considerations Before Uninstalling As you prepare to uninstall IBM Tioli Serice Leel Adisor, keep in mind the following information: You might hae the three installation options of IBM Tioli Serice Leel Adisor (the SLM Serer, SLM Administration Serer, and SLM Reports) all on the same machine, or on different machines in your enterprise enironment. Be sure to run the uninstallation procedures for each installed option on the appropriate machines. If multiple installation options of IBM Tioli Serice Leel Adisor are located in the same directory on the same machine, all installation options in that directory are uninstalled at the same time. Copyright IBM Corp. 2002,

140 If multiple installation options are located on the same machine but in different directories (which you can do if you run the installation program twice on the same machine, specifying a different installation directory for each installation option), then the uninstallation process must be run against each directory in turn where the installation options are located. The uninstallation program might not be able to remoe all of the files in the IBM Tioli Serice Leel Adisor installation directories. If you are uninstalling from an HP operating system, you might also see warnings that not all JRE files could be deleted. In these cases you must manually delete these files, and then delete the directories. If you hae WebSphere Security enabled, you need to supply the user ID and password that you use to log in to the WebSphere Administratie Console before you can perform the uninstallation. Running the Uninstallation Program To uninstall the IBM Tioli Serice Leel Adisor options using the uninstallation program, complete the following steps: 1. Optionally erify that the WebSphere Application Serer is started (the uninstallation wizard erifies if it is already started before proceeding with the uninstallation). Refer to Starting IBM WebSphere Application Serer on page 115 for details. Note: If you use a directory serice such as LDAP in your enironment, it must be started so that the uninstallation wizard can erify that the application serer is started. 2. Optionally shut down the SLM Serer (the uninstallation wizard automatically shuts down the serer if it is still running, before proceeding with the uninstallation). See ( Shutting Down the SLM Serer on page 119). If you use the Serices Control Panel on Windows systems, be sure to close the Serices control panel window so that the IBM Tioli Serice Leel Adisor serice is completely uninstalled. 3. From a command prompt, naigate to the directory where IBM Tioli Serice Leel Adisor is installed (for example, /usr/tsla or C:\TSLA), and run the uninstallation script: For Windows systems: uninstall.bat For UNIX systems:./uninstall.sh 4. You are prompted to select the language to be used for the uninstallation wizard. Select the language that you want to use, and click OK to continue. 5. At the Welcome window for the uninstallation wizard, click Next to continue. 6. If you hae WebSphere Security enabled, you must enter a alid user ID and password that you use to log on to the WebSphere Administratie Console. Enter the user ID and password in the fields proided and click Next to continue. 7. The user ID and password you entered are erified. The WebSphere Application Serer is erified to be started (and if it is not, you are prompted to start it before continuing). 8. If you do not hae language support installed, proceed to step 10 on page 123. If you do hae language support installed, you can select to either uninstall 122 IBM Tioli Serice Leel Adisor: Getting Started

141 only the language support option, or uninstall both the IBM Tioli Serice Leel Adisor product and any installed language support. Select the option and click Next to continue. 9. If you choose to uninstall language support only, you can then select which of the installed languages you want to remoe, for each of the installation options of IBM Tioli Serice Leel Adisor. After making your selections, click Next to continue. 10. A summary window is displayed showing your uninstallation choices. Confirm your selected choices and click Next to continue. 11. The SLM Serer is automatically shut down during the uninstallation. You might receie a prompt asking you to confirm before the SLM Serer is shut down. Click Next to continue. 12. The SLM Serer is then stopped and the uninstallation is performed. If you are only uninstalling language support, or if you are uninstalling on multiple distributed machines, the SLM Serer is automatically restarted when the uninstallation is completed. 13. If you receie an error or warning message stating that not all files could be remoed, naigate to the directory where IBM Tioli Serice Leel Adisor was installed and manually delete any remaining files. You can optionally delete the directory itself. 14. After the uninstallation is complete, reboot the system. If you are uninstalling IBM Tioli Serice Leel Adisor on multiple machines, run the uninstallation program on each machine where an installation option is located. If you hae problems with uninstalling IBM Tioli Serice Leel Adisor, see the Troubleshooting document for additional information on manually uninstalling the IBM Tioli Serice Leel Adisor product. Uninstalling the Target and Source Warehouse Packs The detailed procedure for uninstalling warehouse packs from Tioli Data Warehouse is located in Uninstalling warehouse packs in Installing and Configuring Tioli Data Warehouse. Reiew that procedure as needed. In summary, uninstall the Registration and Process ETLs by completing the following steps: With Tioli Enterprise Data Warehouse 1.1 installed: 1. Naigate to <TEDW_Dir>/install/bin, where <TEDW_Dir> is the installation location for Tioli Enterprise Data Warehouse 1.1, and use Wordpad or another text editor to edit the twh_app_deinstall.cfg file. 2. Change the following lines in the file: APPLICATION_TO_DELETE=DYK DB2PASS=<db2_password> COPT_CTRL_DB2PASS=<db2_password> COPT_CDW_DB2PASS=<db2_password> COPT_MART_DB2PASS=<db2_password> Note: The <db2_password> alues entered must be applicable to the local DB2 administrator for the systems on which the control serer, data mart serer, and central data warehouse serer are located. 3. Sae your changes to this file. 4. Open a command prompt and naigate to <TEDW_Dir>/install/bin 5. Issue the bash command to launch a bash shell. Chapter 7. Uninstalling IBM Tioli Serice Leel Adisor 123

142 6. Issue the following command on the control serer machine:./twh_app_deinstall.sh -c twh_app_deinstall.cfg 7. The Command Prompt window displays the progress of the uninstallation. After a few minutes, the following message should be displayed: TEDW Deinstallation Successfully Completed!!! 8. Type exit to leae the bash shell and close the Command Prompt window. With Tioli Data Warehouse 1.2 installed: 1. This ersion of Tioli Data Warehouse proides a separate warehouse pack uninstallation program. To start this program, you can complete either of the following steps: Click Start > Programs > Tioli Data Warehouse > Uninstall a Warehouse Pack Open a Command Prompt window, naigate to <TDW_Dir>\install\bin, where <TDW_Dir> is the installation location where Tioli Data Warehouse 1.2 is installed, and run the twh_wepuninstall.bat script. 2. On the Welcome page, click Next to continue. 3. The program searches for aailable warehouse packs to uninstall. The DYK target ETL warehouse pack for IBM Tioli Serice Leel Adisor should be found (and the DY1 source ETL warehouse pack, if you installed this optional warehouse pack) and displayed. Select the DYK check box (and the DY1 check box, if it is displayed) and click Next to continue. 4. A confirmation window is displayed. Click Uninstall to start the uninstallation process. 5. After the uninstallation completes, a window is displayed indicating that the uninstallation was successful. Click Finish to close the wizard. 6. Check the DB2 Warehouse Center and erify that it does not show any DYK (or DY1) processes: a. Click Start -> Programs -> IBM DB2 -> Control Center b. Click Tools -> Data Warehouse c. Log in with your DB2 user ID and password d. Click Subject Areas in the left pane and erify that there are no processes in the folder with a DYK (or DY1) prefix. Also click Warehouse Sources and Warehouse Targets and erify that there are no sources or targets with a DYK (or DY1) prefix listed. e. Close the Data Warehouse Center and Control Center windows. Uninstalling SLM Databases To uninstall the SLM Database and the SLM Measurement Data Mart used by IBM Tioli Serice Leel Adisor, use the drop command to uninstall the DB2 databases, and remoe the related ODBC datasources. If you are only uninstalling the databases to recreate them later, for example, due to a change of the schema in the database, the Create Databases task in the LaunchPad for IBM Tioli Serice Leel Adisor can optionally uninstall these existing databases for you prior to being recreated. If you want to uninstall the databases manually, follow the procedures in the following section. Note: If you use the LaunchPad to uninstall and recreate databases, any preious data in the databases will be lost, unless you back up the databases first. 124 IBM Tioli Serice Leel Adisor: Getting Started

143 Uninstalling the Databases To uninstall the DYK_CAT and DYK_DM databases, complete the following steps on the DB2 serer machine where the databases reside: 1. Start up a DB2 Command Line Processor window by completing the following steps: For Windows systems, select Start > Run and issue the following command: db2cmd For UNIX systems, log in as the DB2 instance owner, naigate to the <db2_instance_dir>/sqllib directory, where <db2_instance_dir> is the DB2 instance directory, and issue one of the following commands: For bash, Bourne, or Korn shells:. db2profile For C shell: source db2cshrc 2. List the database directories by issuing the following command: db2 list database directory You should see entries for DYK_CAT and DYK_DM databases (unless you selected different names for these databases at creation time). 3. Disconnect all applications that are using the database instance by issuing the following commands: db2stop force db2start 4. If your databases are on a remote z/os machine, connect to the remote location, where <user_name> and <password> are the DB2 user name and password that you specified during DB2 installation, by issuing the following command: db2 connect to <name> user <user_name> using <password> If you experience problems running this command, refer to the DB2 Uniersal Database documentation for troubleshooting information. 5. Uninstall the databases by issuing the following commands: db2 drop database dyk_cat db2 drop database dyk_dm If you experience difficulty uninstalling the databases, refer to the DB2 documentation for troubleshooting information. 6. If your databases were located on a remote z/os operating system, issue the following commands: db2 connect reset db2 uncatalog database dykcat db2 uncatalog database dykdm db2 uncatalog dcs database dykcat db2 uncatalog dcs database dykdm db2 uncatalog node dykcat db2 uncatalog node dykdm 7. If any of the databases fail to uninstall successfully, you might need to uncatalog them as well by issuing the following command, where <name> is the name of the database to be uncataloged: db2 uncatalog database <name> Remoing ODBC Datasources To remoe ODBC datasources related to the DYK_CAT and DYK_DM databases, complete the following steps: Chapter 7. Uninstalling IBM Tioli Serice Leel Adisor 125

144 1. Select Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC) 2. Select the System DSN tab. 3. Highlight the DYK_CAT entry in the System Data Sources table and click Remoe. 4. Highlight the DYK_DM entry in the System Data Sources table and click Remoe. 126 IBM Tioli Serice Leel Adisor: Getting Started

145 Appendix A. A Quick Start Installation Example The following procedure is a consolidated set of steps to perform a sample IBM Tioli Serice Leel Adisor solution installation that you can use for demonstrations, or as an educational or test platform. This installation might also be used in a production enironment by companies that do not plan to hae many users concurrently analyzing data and that do not need to capture and analyze large amounts of data in the central data warehouse. This example installation procedure takes all aailable default alues. The deployment consists of a single Windows 2000 machine aailable in your enterprise that contains all components of DB2 Uniersal Database, Crystal Enterprise, Tioli Data Warehouse, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor. Figure 51 shows the deployment of this sample installation. Figure 51. A single-machine deployment for quick installation This single machine installation must be on a Windows operating system, because the control serer component of Tioli Data Warehouse is only supported on a Windows operating system. See the Release Notes for the list of supported Windows operating systems that you can use for this installation. Copyright IBM Corp. 2002,

146 Installation Assumptions The machine is set up as a DB2 serer machine. All of the databases, including the two databases for IBM Tioli Serice Leel Adisor, are installed in a single DB2 instance. All components of Tioli Data Warehouse 1.2, IBM WebSphere Application Serer 5.1, and all three installation options of IBM Tioli Serice Leel Adisor 2.1 are installed on this machine, with both the SLM Administration Serer and the SLM Reports options on the same WebSphere serer. Warehouse packs are also installed on this machine because the control serer component of Tioli Data Warehouse is installed on this machine. This installation procedure is based on the following assumptions: You hae familiarized yourself with the product by reading the oeriew and planning chapters, and hae reiewed the installation procedures before starting the installation. You hae completed the planning worksheets as needed for the installation, collecting the following necessary information that you need to specify during the installation: Fully qualified machine names Authorized user names and passwords for DB2 Uniersal Database, Crystal Enterprise, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor Selected port numbers for communication Selected target installation directory paths Selected database names Usually you can use default alues for these items when they are proided during installation. The machine is configured to meet all hardware and software prerequisite requirements defined in the Tioli Data Warehouse and IBM Tioli Serice Leel Adisor Release Notes and other documentation, including the following prerequisites: Supported hardware and operating system serice leels are applied. Adequate temporary disk space is aailable. The machine is configured to return fully qualified hostnames. The machine is configured to automatically start from the product CD. A supported Web browser is installed on the machine. You hae adequate authority to perform the installation (Administrator authority on Windows systems), with the necessary roles and priileges assigned to the user name with which you use for the installation (see Ensuring User Rights Authority for Database Creation on page 184 for more information). Any preious installation of Tioli Data Warehouse or IBM Tioli Serice Leel Adisor has been completely remoed from the machine. This sample installation does not include an upgrade from a preious ersion of these applications. You hae aailable the required installation media for the SLM solution, including the following items: IBM DB2 Uniersal Database Enterprise Edition installation media, included with Tioli Data Warehouse 1.2 Crystal Enterprise Professional 9 installation media, included with Tioli Data Warehouse 1.2 Tioli Data Warehouse 1.2 installation media 128 IBM Tioli Serice Leel Adisor: Getting Started

147 IBM WebSphere Application Serer 5.1 installation media Optionally, the IBM WebSphere Application Serer fix pack to upgrade to ersion (downloaded from the product support Web site to a temporary directory on your machine) IBM Tioli Serice Leel Adisor 2.1 installation media, including the source (DY1) and target (DYK) warehouse packs for installing with Tioli Data Warehouse 1.2 One or more source application warehouse packs that are installed and configured with their associated source applications to write data into Tioli Data Warehouse You are familiar with basic operations, such as starting a DB2 command prompt before issuing DB2 commands (see Starting a DB2 Command Prompt on page 183), naigating the Windows operating system, running scripts, and issuing other commands from a command window. No additional language support is needed for this installation (English language only). The installation procedure consists of the following major steps, which are described in more detail in the remaining sections of this appendix: 1. Install IBM Uniersal Database Enterprise Edition serer software. 2. Install IBM WebSphere Application Serer. Because you are installing to a single machine in this example, you need to hae a web serer installed on your system before installing Tioli Data Warehouse. This example assumes that your single machine does not already hae a Web serer, and the installation of WebSphere Application Serer installs one for you as part of the process. For purposes of this sample installation, install only a single application serer, serer1. After installing the ersion 5.1 that is supplied with this release, you can optionally upgrade the installation to a supported fix pack leel. This sample installation is upgraded to ersion WebSphere security is enabled for this sample installation. 3. Install Crystal Enterprise Professional Install all components of Tioli Data Warehouse. For purposes of this sample installation, install only one central data warehouse. 5. Install and configure source application warehouse packs as needed. The specific steps to install and configure the arious source applications and their associated warehouse packs for writing data into the central data warehouse are not included here, because they are specific to each source application. See Warehouse Enablement Packs on page ix to find information on currently aailable warehouse packs. Verify measurement data in the central data warehouse: At this point in the oerall process you should be able to collect local measurement data with your installed source applications, and run scheduled source application ETLs from your installed warehouse packs to write data into Tioli Data Warehouse. You should erify that this part of the SLM enironment operates properly before continuing with this installation. 6. Create the SLM Database and SLM Measurement Data Mart on the local machine, using default names and other settings. 7. Install all components of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Administration Serer, and SLM Reports). 8. Create ODBC datasources for the SLM Database and SLM Measurement Data Mart. Appendix A. A Quick Start Installation Example 129

148 9. Install the IBM Tioli Serice Leel Adisor source and target warehouse packs. 10. Configure user IDs and passwords. 11. Perform additional configuration steps to enable the flow of data between Tioli Data Warehouse and IBM Tioli Serice Leel Adisor and schedule the ETLs to run. Completing the aboe steps configures your single-machine SLM solution for receiing and processing data from one or more source applications that will write data into the central data warehouse. Planning Worksheets for this Installation Refer to Installing and Configuring Tioli Data Warehouse for the following planning worksheets that apply to this installation: Planning worksheet for a Crystal Enterprise serer Planning worksheets for a quick start deployment Planning worksheet for installing warehouse packs In addition to the aboe planning information, refer to the following planning worksheets for IBM Tioli Serice Leel Adisor: Table 7 on page 25 Table 8 on page 30 Step 1. Installing DB2 Uniersal Database Serer Install the DB2 serer software by following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the following sections: Step 1: Preparing the enironment For this installation, use the following assumptions: Log on to the Windows system with a user name that has Administrator authority (you might need to get this from your system administrator). The user name db2admin and password db2admin are created for DB2 database access, and do not already exist on the system. Use this user ID and password wheneer you are prompted for them throughout the installation (or make up your own and substitute them in this procedure). The machine is configured to return fully qualified hostnames (erify this using the documented procedure for Windows systems in this section). The fully qualified hostname for this machine is of the form: mymachine.mylocation.mycompany.com Step 2: Installing and configuring DB2 Uniersal Database For this installation, use the following assumptions: You are not reusing an existing instance of DB2 Uniersal Database. You are installing DB2 Uniersal Database using the installation media proided with Tioli Data Warehouse 1.2. The system is configured to automatically start the setup.exe installation program located in the root directory. You specify the DB2 user name as db2admin (the default) and the password also as db2admin. 130 IBM Tioli Serice Leel Adisor: Getting Started

149 You do not need to complete Step 3: Installing a DB2 client for Crystal Enterprise because, for this sample installation, Crystal Enterprise will be installed on this same machine, and can use the DB2 serer function that you install for communicating with the Tioli Data Warehouse data mart. After the installation of DB2 Uniersal Database is complete, reboot the machine before continuing. Step 2. Installing IBM WebSphere Application Serer This procedure installs IBM WebSphere Application Serer, Version 5.1, that ships with IBM Tioli Serice Leel Adisor. After installing this base ersion, you can optionally upgrade the installation to a supported fix pack leel. See Upgrading WebSphere to Version on page 132 for more information. If you hae a preious ersion of IBM WebSphere Application Serer already installed, consult the accompanying documentation for additional installation and upgrade information. See the Release Notes for information on specific supported ersions of IBM WebSphere Application Serer. To install WebSphere Application Serer 5.1, complete the following steps. If you experience any problems during this installation, refer to the install documentation for IBM WebSphere Application Serer. 1. Insert the Windows ersion of the WebSphere Application Serer 5.1 product CD and run the LaunchPad.bat program. Select the language for the LaunchPad, and then on the main LaunchPad window that displays, click Install the product. 2. On the Language window for the installation wizard, select the language and click OK to continue. 3. On the Welcome window, click Next to continue. 4. Reiew and accept the Software License Agreement that is displayed, by selecting the I accept the terms in the license agreement radio button, and click Next to continue. 5. From the setup type selection window, select the Full radio button to install eerything you need. Click Next to continue. 6. On the next window, accept the default target installation directories that are displayed. Click Next to continue. 7. On the next window, erify that the node name and the fully qualified hostname that are displayed are correct for this machine, or enter the correct alues and click Next to continue. 8. On the next window, accept the default serices check boxes that are selected. Also erify that the user ID is specified, or enter your own, and enter a alid password for that user ID. Click Next to continue. 9. On the summary window that is displayed, erify the installation options that you specified, and click Next to continue. 10. The installation begins and files are copied to your machine. After seeral minutes, the installation completes. You are presented with registration options to register the product. After making your selection, click Next to continue. 11. Click Finish to exit the installation wizard. 12. The WebSphere Application Serer - First Steps console is displayed. Select Start the Serer from the aailable options. After a short time, you should see Appendix A. A Quick Start Installation Example 131

150 the following message, indicating that the WebSphere Application Serer is started (note that a 4-digit process ID xxxx is also assigned and included with the message): ADMU3000I: Serer serer1 is open for e-business, process id is xxxx Upgrading WebSphere to Version The Release Notes specifies seeral supported ersions of IBM WebSphere Application Serer. This sample installation upgrades IBM WebSphere Application Serer to ersion by applying the appropriate fix pack, following these steps: 1. Naigate to C:\Program Files\WebSphere\AppSerer and create a new folder called update. 2. Naigate to the following Web site: 3. On the Web page, search for the WebSphere Application Serer 5.1 Cumulatie Fix Select and download the Windows ersion of the compressed package to the update folder. 5. On the Web page, click Readme and follow the instructions that are displayed to install this fix pack. 6. Restart the IBM WebSphere Application Serer (see Starting IBM WebSphere Application Serer on page 115). 7. Delete the original downloaded compressed file to free up space on your hard drie. Enabling WebSphere Security There are arious options aailable to you to enable WebSphere security. The following example procedure addresses one basic ersion of enabling security, alid only for an installation using a local operating system user registry. For more detailed information on WebSphere security, see the IBM WebSphere Application Serer documentation. To enable WebSphere security support for an installation using a Local OS user registry, complete the following steps: 1. Start the WebSphere Application Serer. Refer to Starting IBM WebSphere Application Serer on page Start the WebSphere Administratie Console. Refer to Starting the WebSphere Administratie Console on page Enable local operating system authentication by completing the following steps: a. In the left pane of the WebSphere Administratie Console, expand the Security branch of the naigation tree. b. Under Security, expand the User Registries branch. c. Click Local OS. d. In the Serer User ID and Password fields, enter the default user ID (db2admin) and password (db2admin) that has Administrator priileges for your local operating system. Note: The Serer User ID must hae Administrator priileges and cannot be the same as the machine hostname. If this user ID matches the machine name, you will receie errors when you attempt to enable security. e. Click OK. 132 IBM Tioli Serice Leel Adisor: Getting Started

151 f. Click Sae at the top of the page to sae your changes (you might need to click Sae in more than one place to completely sae your changes). 4. Enable WebSphere Security by completing the following steps: a. In the naigation tree, under Security, click Global Security. b. In the General Properties Table, select the Enabled check box. c. Verify that the check box for Enforce Jaa 2 Security is already selected. d. Scroll down to Actie User Registry, and erify that Local OS is selected. e. Scroll to the bottom and click OK. f. Click Sae at the top of the page to sae your changes (you might need to click Sae in more than one place to completely sae your changes). 5. Stop and restart the WebSphere Application Serer (you might need to restart your system if the changes do not take effect by only restarting the WebSphere Application Serer. If so, be sure to start the WebSphere Application Serer after the system is restarted.). Note: After restarting the serer, WebSphere security is enabled, and the commands to stop WebSphere Application Serer will also include specifying a alid user name and password. You can still start the serer without haing to specify a user name and password. 6. Log on to the WebSphere Administratie Console. The sign-on page now prompts you for both a alid user name and a password. Enter the user name and password that you proided in step 3d on page 132. Step 3. Installing Crystal Enterprise Install the Crystal Enterprise software by following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the section, Step 4: Installing Crystal Enterprise. For this installation, use the following assumptions: You are not upgrading an existing installation of Crystal Enterprise. You are using the installation CD for Crystal Enterprise proided with Tioli Data Warehouse. You are installing Crystal Enterprise on the same computer as Tioli Data Warehouse. MSDE and Microsoft SQL Serer are not already installed. For the Default SQL Administrator (sa) password, specify a password of your choice, such as sapw001. Specify the default Crystal Enterprise user name of Administrator and leae the password blank (by default). After you complete this installation procedure for Crystal Enterprise, see the reference to additional configuration steps that you might need to complete if the Web serer on your machine is IBM HTTP Serer. You might need to complete these steps if you plan to install warehouse packs for applications that make use of Crystal Enterprise for reports. IBM Tioli Serice Leel Adisor does not use Crystal Enterprise for its reporting function, so this is not needed for IBM Tioli Serice Leel Adisor. If you do not intend to install warehouse packs that proide Crystal Reports, you do not hae to complete these additional steps. Appendix A. A Quick Start Installation Example 133

152 Step 4. Installing Tioli Data Warehouse Install Tioli Data Warehouse by following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the following sections: Step 5: Installing the control serer and creating databases For this installation, use the following assumptions: Accept the default location for the Tioli Common Directory. Accept the default for the installation directory for Tioli Data Warehouse. Specify the DB2 user name db2admin and password db2admin that you defined preiously. For the Crystal Enterprise serer in this sample installation, enter the fully qualified machine name for this machine, in the form of mymachine.mylocation.mycompany.com. For the Crystal Enterprise user name, specify the default name of Administrator. Leae the password field blank. Step 6: Specifying the control database for the DB2 Data Warehouse Center For this step, when you log on to the Data Warehouse Center, specify the DB2 user name db2admin and password db2admin for the control serer. Step 7: Creating an ODBC connection from the Crystal Enterprise serer to the data marts Because Crystal Enterprise is installed on the same machine where all components of Tioli Data Warehouse will be located, you do not hae to complete this section. All you need to do is reboot the machine. Step 8: Completing the Installation Follow the instructions and recommendations in this section to complete the installation of Tioli Data Warehouse. Step 5. Installing Source Application Warehouse Packs After installing DB2 Uniersal Database, WebSphere Application Serer, Crystal Enterprise Professional 9, and Tioli Data Warehouse, you should install and configure any source application warehouse packs to write data into the central data warehouse database. Specific installation procedures are aailable in the implementation guide that accompanies each source application warehouse pack. Consult your Tioli Data Warehouse and warehouse pack documentation for more information. Complete the installation and configuration of this part of your warehouse enironment (Tioli Data Warehouse, source applications, and their associated warehouse pack ETLs) so that they are operating properly before proceeding to install IBM Tioli Serice Leel Adisor. This ensures that data is aailable in the central data warehouse for extraction and ealuation by IBM Tioli Serice Leel Adisor. Step 6. Creating Databases for IBM Tioli Serice Leel Adisor This installation procedure creates the two databases used by IBM Tioli Serice Leel Adisor, the SLM Database (DYK_CAT) and the SLM Measurement Data Mart (DYK_DM). In this sample installation, these databases are created in the same DB2 instance as the Tioli Data Warehouse databases. 134 IBM Tioli Serice Leel Adisor: Getting Started

153 To create these two databases, complete the following steps: 1. Verify that the db2jaa.zip file is included in your CLASSPATH system ariable. See Before Installing IBM Tioli Serice Leel Adisor on page 49 for information on this and other items to check before installing. 2. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie. 3. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. 4. Verify the language for the installation (English) and click OK to continue. 5. On the main window of the LaunchPad, click Create Databases. 6. On the Welcome window of the Create Databases Wizard, click Next to continue. 7. On the next window, select both the SLM Database and the SLM Measurement Data Mart check boxes. Click Next to continue. 8. On the next window, for the SLM Database, erify that the Local radio button is selected, and click Next to continue. 9. On the next window, confirm that the default name for the SLM Database, dyk_cat, is specified, and the default alue for user ID, db2admin, is specified. In the password field, enter the default alue db2admin, and click Next to continue. 10. On the next window, for the SLM Measurement Data Mart, erify that the Local radio button is selected, and click Next to continue. 11. On the next window, confirm that the default name for the SLM Measurement Data Mart, dyk_dm, is specified, and the default alue for user ID, db2admin, is specified. In the password field, enter the default alue db2admin, and click Next to continue. 12. Confirm your selections on the summary window and click Next to continue. 13. The databases are created. After you receie the final completion message, click Finish to close the Database Creation Wizard and return to the main window of the LaunchPad. You can optionally check the database creation logs for error messages. See Step 4. Checking Database Creation Logs and Tables on page 60 for more information. Step 7. Installing IBM Tioli Serice Leel Adisor Install the SLM Serer, SLM Administration Serer, and the SLM Reports options of IBM Tioli Serice Leel Adisor by completing the following steps: 1. Verify that the IBM WebSphere Application Serer is started (if not, you are prompted later to start the serer before the installation can continue). 2. If the LaunchPad for IBM Tioli Serice Leel Adisor is not started, start it by completing the following steps: Insert the IBM Tioli Serice Leel Adisor product CD. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. Verify the language for the installation (English) and click OK to continue. 3. On the main window of the LaunchPad, click Install Product. 4. Verify the language for the installation (English) and click OK to continue. 5. On the Welcome window, click Next to continue. 6. On the Software License Agreement window, select the I accept the terms in the license agreement radio button and click Next to continue. Appendix A. A Quick Start Installation Example 135

154 7. On the next window, accept the default location for the Tioli Common Directory and click Next to continue. 8. On the next window, erify that the Install IBM Tioli Serice Leel Adisor check box is selected, and click Next to continue (for this sample installation you are not installing the optional language support). 9. On the next window, accept the default directory name where IBM Tioli Serice Leel Adisor is being installed, and click Next to continue. 10. On the next window, erify that the check boxes for all three options (SLM Serer, SLM Administration Serer, and SLM Reports) are selected. Click Next to continue. 11. Prerequisite software is erified on this machine before continuing the installation. 12. Because you enabled WebSphere security, on the next window you are prompted to enter a alid user name and password for WebSphere access. Enter a alid user name and password that you defined when you enabled WebSphere security and click Next to continue. The user name and password are then erified, and the status of the WebSphere Application Serer is erified before continuing. 13. If you had not preiously started the IBM WebSphere Application Serer, the next window asks if you want to start the serer. Select the check box to start the serer and wait for it to complete before continuing. 14. On the next window, erify that the Local radio button is selected for the location of the SLM Database (DYK_CAT), and click Next to continue. 15. On the next window, accept the defaults that are presented in the fields, but in the Password field, enter the DB2 password db2admin. Click Next to continue. 16. On the next window, erify that the Local radio button is selected for the location of the SLM Measurement Data Mart (DYK_DM), and click Next to continue. 17. On the next window, accept the defaults that are in the fields, but in the Password field, enter the DB2 password db2admin. Click Next to continue. 18. On the next window, accept the defaults for SLM Serer Communication Port and the Command Line Interface Port configuration and click Next to continue. Leae the remaining fields blank (do not enable password protection for CLI commands). 19. On the next window, for purposes of this sample installation, you do not hae to select any options for SLA eent notification. To set up SLA notification, see Step 10. Specify Eent Notification Methods on page 71, otherwise click Next to continue. 20. On the next window (or after configuring for eent notification), you are prompted for a alid user name for SLM Administrator authority and SLM Reports access. Enter db2admin for this user name, and click Next to continue. 21. On the next window, accept the default to not compile JaaSerer Page files, and click Next to continue. 22. On the feature summary window, click Next to proceed with the installation. Wait for completion. 23. After the installation and configuration completes, you are asked if you want to regenerate the IBM WebSphere HTTP plug-in configuration. Verify that the Yes radio button is selected, and click Next to continue. 24. Additional windows are displayed with configuration and startup information for the SLM Reports and SLM Administration Serer components installed on this machine. Click Next to continue. 136 IBM Tioli Serice Leel Adisor: Getting Started

155 25. You are asked if you want to restart the WebSphere Application Serer. Select the check box and click Next. Wait for the serer to be restarted (approximately one minute). If for some reason the serer did not restart automatically, manually restart the WebSphere Application Serer by following the procedure in Step 16. Restarting WebSphere Application Serer on page Click Finish to close the wizard and return to the main page of the LaunchPad. Step 8. Configuring ODBC Data Sources To configure ODBC data sources for the SLM Database and SLM Measurement Data Mart, complete the following steps: 1. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie. 2. Click Start > Run and type the following command to open a DB2 command window: db2cmd. 3. Naigate to <CD-ROM>\database\scripts\w32-ix86\, where <CD-ROM> is the CD-ROM drie letter. 4. Run the dyk_cat_odbc.bat script to create an ODBC data source connection for the SLM Database, specifying the fully qualified hostname of the machine, similar to the following example: dyk_cat_odbc.bat mymachine.mylocation.mycompany.com 5. Similarly, run the dyk_dm_odbc.bat script to create an ODBC data source connection for the SLM Measurement Data Mart: dyk_dm_odbc.bat mymachine.mylocation.mycompany.com 6. Verify that these ODBC data sources are successfully configured by clicking Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC), and selecting the System DSN tab. The resulting list of ODBC data sources that is displayed should include entries for the default alias names DYK_CAT and DYK_DM. Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Tioli Data Warehouse 1.2 proides a separate installation program to install warehouse packs. Install the DYK target warehouse pack for IBM Tioli Serice Leel Adisor by following the procedure documented in Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment on page 90. Step 10. Configuring the User ID and Password To configure the user ID and password for the target ETLs, complete the following steps: 1. To start the DB2 Control Center click Start > Programs > IBM DB2 > Control Center and click Tools > Data Warehouse Center. 2. On the login window, before logging in, click Adanced and erify that the control database is set to TWH_MD. If it is not, edit this field and change it to this alue. 3. Log in to the Data Warehouse Center with the default user name db2admin and password db2admin. 4. In the left pane of the Data Warehouse Center, expand the Warehouse Targets folder. Appendix A. A Quick Start Installation Example 137

156 5. In the Warehouse Targets folder, right-click the DYK_DYK_CAT_Target entry and select Properties from the context menu. Then select the Database tab, and enter the default user name db2admin and password db2admin. Click OK when done. 6. In the Warehouse Targets folder, right-click the DYK_DYK_DM_Target entry and select Properties from the context menu. Then select the Database tab, and type the default user name db2admin and password db2admin. Click OK when done. Step 11. Enabling Data Collection for Source Applications You need to enable source applications for which you want to collect and ealuate data in IBM Tioli Serice Leel Adisor. Only data from enabled source applications is transferred from Tioli Data Warehouse to IBM Tioli Serice Leel Adisor and accepted for ealuation and analysis. Follow the instructions for enabling data for source applications in Enabling Data Collection for Source Applications on page 95. Step 12. Configuring ETLs for Production Mode Follow the instructions for configuring ETLs for production mode as discussed in Configuring ETLs for Production Mode on page 101. Step 13. Running the Registration and Process ETLs If you hae data in the central data warehouse for source applications that you enabled, either wait for the scheduled run of the Registration and Process ETLs or run them on demand. To run the ETLs manually, follow the procedures in Running the Registration ETL and Process ETL on page 103. Step 14. Registering Warehouse Data After the Registration ETL has run at least one time, either wait approximately minutes for the data to be registered with IBM Tioli Serice Leel Adisor, or register the data yourself. See Registering Warehouse Data on page 104 for details. Step 15. Additional Optional Configuration If you selected eent notification, you might need to perform a few additional configuration steps. See Configuring for Eent Notification on page 107 for more information. In this sample installation you did not install the source warehouse pack for IBM Tioli Serice Leel Adisor. To install this warehouse pack, see the procedures in Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105. In this sample installation you did not install additional language support. To install language support, see the procedures in Installing Language Support on page 109. Also see Installing and Configuring Tioli Data Warehouse for information on installing language support for Tioli Data Warehouse. 138 IBM Tioli Serice Leel Adisor: Getting Started

157 Step 16. Restarting WebSphere Application Serer You need to stop and restart the WebSphere Application Serer, but because you enabled WebSphere security, you cannot stop the WebSphere Application Serer without proiding the authorized user name and password. You can stop and restart the WebSphere Application Serer by completing the following steps: 1. Open a command prompt window. 2. Naigate to C:\Program Files\WebSphere\Appserer\bin, the location where WebSphere Application Serer is installed. 3. Issue the following command: stopserer serer1 -username db2admin -password db2admin 4. Wait for the serer to be stopped. 5. Issue the following command to restart the serer: startserer serer1 Note: You do not need to specify the user name and password to start the serer. See Starting IBM WebSphere Application Serer on page 115 for alternatie start-up procedures. 6. Wait for the open for e-business message to be displayed. Accessing the SLM Administratie Console Accessing SLM Reports After the WebSphere Application Serer has restarted, access the SLM Administratie Console by opening your Web browser and naigating to the following Web site, where <Fully_Qualified_Machine_Name> is the fully qualified machine name (where you installed the SLM Administration Serer): If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. See Managing Serice Leel Agreements for information about using the SLM Administratie Console to create and manage your SLAs. You can also access the SLM Reports user interface by naigating to the following Web site, where <Fully_Qualified_Machine_Name> is the fully qualified machine name of this machine (where you installed SLM Reports): If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. See SLM Reports for information about using the reporting interface of IBM Tioli Serice Leel Adisor to iew results of the ealuation and analysis of reported data by IBM Tioli Serice Leel Adisor. Appendix A. A Quick Start Installation Example 139

158 140 IBM Tioli Serice Leel Adisor: Getting Started

159 Appendix B. A Two-Machine Distributed Installation Example The following procedure is a consolidated set of steps to perform a sample IBM Tioli Serice Leel Adisor solution installation that you can use as an entry-leel production enironment. This sample installation procedure takes all aailable default alues. The deployment consists of two Windows machines aailable in your enterprise that contain all components of DB2 Uniersal Database, Crystal Enterprise, Tioli Data Warehouse, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor. Figure 52 shows the deployment of this sample distributed installation. Figure 52. A two-machine distributed deployment The Warehouse Machine For this sample installation, we refer to the two machines as the Warehouse machine and the SLM machine. The Warehouse machine has the following characteristics: The operating system must be one of the supported Windows operating systems because the control serer component of Tioli Data Warehouse is only supported on a Windows operating system. For this sample installation a Windows 2000 operating system is used. See the Release Notes for the list of supported Windows operating systems that you can use for this installation. Copyright IBM Corp. 2002,

160 The SLM Machine Installation Assumptions The machine is set up as a DB2 serer machine because the control serer, central data warehouse and data mart components of Tioli Data Warehouse require the DB2 serer function. Crystal Enterprise Professional 9 is installed on this machine. All components of Tioli Data Warehouse 1.2 are installed on this machine. Warehouse packs are installed on this machine because the control serer component of Tioli Data Warehouse is installed on this machine. The SLM machine has the following characteristics: The operating system can be any supported Windows, AIX, or Solaris operating system. For this sample installation a Windows 2000 operating system is used. See the Release Notes for the list of supported operating systems that you can use for this installation. The machine is set up as a DB2 serer machine because the SLM Database and SLM Measurement Data Mart require the DB2 serer function. Because this is a distributed installation with the source (central data warehouse) database on one machine and target databases (the SLM Database and SLM Measurement Data Mart) on a different machine, you could create an agent site on this machine, but for simplicity, this sample installation uses the default local agent on the Warehouse machine. Because you are not creating an agent site on this machine, and you are using the default local agent that runs on the control serer, you do not hae to install any Tioli Data Warehouse software on this machine. IBM WebSphere Application Serer is installed on this machine to support the SLM Administration Serer and SLM Reports components of IBM Tioli Serice Leel Adisor. For simplicity, both of these components are installed on a single WebSphere application serer, using the default name serer1. WebSphere security is enabled. All components (SLM Serer, SLM Administration Serer, and SLM Reports) and data mart databases (SLM Database and SLM Measurement Data Mart) for IBM Tioli Serice Leel Adisor are installed on this machine. You create ODBC data sources for the SLM Database and the SLM Measurement Data Mart on the Warehouse machine. Source and target warehouse packs for IBM Tioli Serice Leel Adisor are installed on the Warehouse machine, where the control serer is located. This installation procedure is based on the following assumptions: You hae familiarized yourself with the product by reading the oeriew and planning chapters, and hae reiewed the installation procedures before starting the installation. You hae completed the planning worksheets as needed for the installation, collecting the following necessary information that you need to specify during the installation: Fully qualified machine names 142 IBM Tioli Serice Leel Adisor: Getting Started Authorized user names and passwords for DB2 Uniersal Database, Crystal Enterprise, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor Selected port numbers for communication

161 Selected target installation directory paths Selected database names Usually you can use default alues for these items when they are proided during the installation. The machines are configured to meet all hardware and software prerequisite requirements defined in the Tioli Data Warehouse and IBM Tioli Serice Leel Adisor Release Notes and other documentation, including the following prerequisites: Supported hardware and operating system serice leels hae been applied. Adequate temporary disk space is aailable. The machines are configured to return fully qualified hostnames. The machines are configured to automatically start from the product CD. A supported Web browser is installed on each machine. You hae adequate authority to perform the installation (Administrator authority on Windows systems), with the necessary roles and priileges assigned to the user name that you use for the installation (see Ensuring User Rights Authority for Database Creation on page 184 for more information). Any preious installation of Tioli Data Warehouse or IBM Tioli Serice Leel Adisor has been completely remoed from the machines. This sample installation does not include an upgrade from a preious ersion of these applications. You hae aailable the required installation media for the SLM solution, including the following items: IBM DB2 Uniersal Database installation CD, included with Tioli Data Warehouse 1.2 Use the same ersion on both machines: This sample installation assumes that both the Warehouse machine and SLM machine hae the same ersion of DB2 Uniersal Database installed. Adanced configurations, in which other supported ersions of DB2 Uniersal Database are installed with additional configuration steps to enable different ersions to communicate among themseles are not considered in this sample installation. Crystal Enterprise Professional 9 installation media, included with Tioli Data Warehouse 1.2 Tioli Data Warehouse 1.2 installation media IBM WebSphere Application Serer 5.1 installation media Optionally, the IBM WebSphere Application Serer 5.1 Cumulatie Fix Pack 5 to upgrade to ersion (downloaded from the product support Web site to a temporary directory on your machine) IBM Tioli Serice Leel Adisor 2.1 installation media, which includes the source (DY1) and target (DYK) warehouse packs for installing with Tioli Data Warehouse 1.2 One or more source application warehouse packs that are installed and configured with their associated source applications to write data into Tioli Data Warehouse You are familiar with basic operations, such as starting a DB2 command prompt before issuing DB2 commands (see Starting a DB2 Command Prompt on page 183), naigating the Windows operating system, running scripts, and issuing other commands from a command window. No additional language support is needed for this installation (English language only). Appendix B. A Two-Machine Distributed Installation Example 143

162 The installation procedure consists of the following major steps, which are described in more detail in the remaining sections of this appendix: 1. Install IBM DB2 Uniersal Database Enterprise Edition serer software on both machines. 2. Install Crystal Enterprise 9 on the Warehouse machine. 3. Install all components of Tioli Data Warehouse on the Warehouse machine. For purposes of this sample installation, install only one central data warehouse. 4. Install and configure source application warehouse packs on the Warehouse machine as needed. The specific steps to install and configure the arious source applications and their associated warehouse packs for writing data into the central data warehouse are not included here, because they are specific to each source application. See Warehouse Enablement Packs on page ix to find information on currently aailable warehouse packs. Verify measurement data in the central data warehouse: At this point in the oerall process you should be able to collect local measurement data with your installed source applications, and run scheduled source application ETLs from your installed warehouse packs to write data into Tioli Data Warehouse. You should erify that this part of the SLM enironment operates properly before continuing with this installation. 5. Install IBM WebSphere Application Serer on the SLM machine. For purposes of this sample installation, install only a single application serer, serer1. After installing the ersion 5.1 that is shipped with IBM Tioli Serice Leel Adisor, you can optionally upgrade the installation to a supported fix pack leel. This sample installation is upgraded to ersion WebSphere security is enabled for this sample installation. 6. Create the SLM Database and the SLM Measurement Data Mart on the SLM machine, using default names and other settings. 7. Install all components of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Administration Serer, and SLM Reports) on the SLM machine. 8. Create ODBC datasources for the SLM Database and SLM Measurement Data Mart on the Warehouse machine. 9. Install the IBM Tioli Serice Leel Adisor source and target warehouse packs on the Warehouse machine. 10. Configure user IDs and passwords on the Warehouse machine. 11. Perform additional configuration steps to enable the flow of data between Tioli Data Warehouse and IBM Tioli Serice Leel Adisor and schedule the ETLs to run. Completing the aboe steps configures your two-machine SLM solution for receiing and processing data from one or more source applications that write data into the central data warehouse. Planning Worksheets for this Installation Refer to Installing and Configuring Tioli Data Warehouse for the following planning worksheets that apply to this installation: Planning worksheet for a Crystal Enterprise serer Planning worksheets for a quick start deployment. This set of worksheets applies because you are installing all components of Tioli Data Warehouse and 144 IBM Tioli Serice Leel Adisor: Getting Started

163 Crystal Enterprise on a single machine, regardless of the existence of the SLM machine in the oerall two machine distributed SLM solution for this sample installation. Planning worksheet for installing warehouse packs. In addition to the aboe planning information, you should also refer to the following planning worksheets for IBM Tioli Serice Leel Adisor: Table 7 on page 25. Table 8 on page 30. This table refers to single-system installations, meaning that all components of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Administration Serer, SLM Reports, SLM Database, and SLM Measurement Data Mart) are installed on the same machine, regardless of the existence of the Warehouse machine in the oerall two machine distributed SLM solution for this sample installation. For other configurations, where components of IBM Tioli Serice Leel Adisor are distributed across more than one machine, you should refer to procedures related to distributed installations in this document. Step 1. Installing DB2 Uniersal Database Serer Install the DB2 serer software on both the Warehouse machine and the SLM machine, following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the following sections: Step 1: Preparing the enironment For this installation, use the following assumptions: Log on to each Windows system with a user name that has Administrator authority (you might need to get this from your system administrator). You do not hae to use the same user name for both systems. The user name db2admin and password db2admin are created for DB2 database access on both machines, and do not already exist on either machine. You do not hae to use the same user name and password for both machines, but this sample installation uses db2admin for the user ID and password on both machines for simplicity. Use this user ID and password wheneer you are prompted for them throughout the installation (or make up your own and substitute them in this procedure). The machines are configured to return fully qualified hostnames (erify this using the documented procedure for Windows operating systems in this section). The fully qualified hostname for each machine is of the form: mymachine.mylocation.mycompany.com For purposes of this sample installation, assume that the fully qualified hostnames are as follows: - For the Warehouse machine: tdwcdw1.raleigh.ibm.com - For the SLM machine: tslaslm1.raleigh.ibm.com Step 2: Installing and configuring DB2 Uniersal Database For this installation, use the following assumptions: You are not reusing an existing instance of DB2 Uniersal Database. You are installing DB2 Uniersal Database using the installation media proided with Tioli Data Warehouse 1.2. Appendix B. A Two-Machine Distributed Installation Example 145

164 The systems are configured to automatically start the setup.exe installation program located in the root directory. You specify the DB2 user name as db2admin (the default) and the password also as db2admin on both systems. Be sure to complete these steps for both the Warehouse machine and the SLM machine. You do not need to complete Step 3: Installing a DB2 client for Crystal Enterprise because, for this sample installation, Crystal Enterprise is installed on the Warehouse machine, and can use the DB2 Serer function that you install on that machine for communicating with the Tioli Data Warehouse data mart. After the installation of DB2 Uniersal Database is complete, reboot the SLM machine before continuing. Step 2. Installing Crystal Enterprise Install the Crystal Enterprise software on the Warehouse machine by following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the section, Step 4: Installing Crystal Enterprise. For this installation, use the following assumptions: You are not upgrading an existing installation of Crystal Enterprise. You are using the installation CD for Crystal Enterprise proided with Tioli Data Warehouse. You are installing Crystal Enterprise on the same computer as Tioli Data Warehouse. MSDE and Microsoft SQL Serer are not already installed. For the Default SQL Administrator (sa) password, specify a password of your choice, such as sapw001. Specify the default Crystal Enterprise user name of Administrator and leae the password blank (by default). At the end of this installation procedure is a reference to additional configuration steps that you might need to complete if the Web serer on your machine is IBM HTTP Serer. You might need to complete these steps if you plan to install warehouse packs for applications that make use of Crystal Enterprise for reports. IBM Tioli Serice Leel Adisor does not use Crystal Enterprise for its reporting function, so this is not needed for IBM Tioli Serice Leel Adisor. If you do not intend to install warehouse packs that proide Crystal Reports, you do not hae to complete these additional steps. Step 3. Installing Tioli Data Warehouse Install Tioli Data Warehouse on the Warehouse machine by following the procedures for Installing a quick start deployment in Installing and Configuring Tioli Data Warehouse, completing the steps in the following sections: 146 IBM Tioli Serice Leel Adisor: Getting Started Step 5: Installing the control serer and creating databases For this installation, use the following assumptions: Accept the default location for the Tioli Common Directory. Accept the default for the installation directory for Tioli Data Warehouse. Specify the DB2 user name db2admin and password db2admin that you defined preiously.

165 For the Crystal Enterprise serer in this sample installation, enter the fully qualified machine name for the Warehouse machine: tdwcdw1.raleigh.ibm.com For the Crystal user name, specify the default name of Administrator. Leae the password field blank. Step 6: Specifying the control database for the DB2 Data Warehouse Center For this step, when you log on to the Data Warehouse Center, specify the DB2 user name db2admin and password db2admin for the control serer. Step 7: Creating an ODBC connection from the Crystal Enterprise serer to the data marts Because Crystal Enterprise is installed on the same machine where all components of Tioli Data Warehouse will be located, you do not hae to complete this section. All you need to do is reboot the machine. Step 8: Completing the Installation Follow the instructions and recommendations in this section to complete the installation of Tioli Data Warehouse. Step 4. Installing Source Application Warehouse Packs After installing DB2 Uniersal Database, Crystal Enterprise Professional 9, and Tioli Data Warehouse on the Warehouse machine, you should install and configure any source application warehouse packs to write data into the central data warehouse database. Specific installation procedures are aailable in the implementation guide that accompanies each source application warehouse pack. Consult your Tioli Data Warehouse and warehouse pack documentation for more information. You should complete the installation and configuration of this part of your warehouse enironment (Tioli Data Warehouse, source applications, and their associated warehouse pack ETLs) so that they are operating properly before continuing to install IBM WebSphere Application Serer and IBM Tioli Serice Leel Adisor. This ensures that data is aailable in the central data warehouse for extraction and ealuation by IBM Tioli Serice Leel Adisor. Step 5. Installing IBM WebSphere Application Serer This procedure installs IBM WebSphere Application Serer, Version 5.1, that ships with IBM Tioli Serice Leel Adisor. After installing this base ersion on the SLM machine, you can then optionally upgrade this installation to ersion See Upgrading WebSphere to Version on page 132 for more information. If you hae a preious ersion of IBM WebSphere Application Serer already installed, consult the accompanying documentation for additional installation and upgrade information. See the Release Notes for information on specific supported ersions of IBM WebSphere Application Serer. To install WebSphere Application Serer 5.1, complete the following steps. If you experience any problems during this installation, refer to the install documentation for IBM WebSphere Application Serer. 1. Insert the Windows ersion of the WebSphere Application Serer 5.1 product CD in the CD-ROM of the SLM machine and run the LaunchPad.bat program. Select the language for the LaunchPad, and then on the main LaunchPad window that displays, click Install the product. Appendix B. A Two-Machine Distributed Installation Example 147

166 2. On the Language window for the installation wizard, select the language and click OK to continue. 3. On the Welcome page, click Next to continue. 4. Reiew and accept the Software License Agreement that is displayed, by selecting the I accept the terms in the license agreement radio button, and click Next to continue. 5. From the setup type selection window, select the Full radio button to install eerything you need. Click Next to continue. 6. On the next window, accept the default target installation directories that are displayed. Click Next to continue. 7. On the next window, erify that the node name and the fully qualified hostname that are displayed are correct for this machine, or enter the correct alues and click Next to continue. 8. On the next window, accept the default serices check boxes that are selected. Also erify that the user ID is specified, or enter your own, and enter a alid password for that user ID. Then click Next to continue. 9. On the summary window that is displayed, erify the installation options that you specified, and click Next to continue. 10. The installation begins and files are copied to the SLM machine. After seeral minutes, the installation completes. You are presented with registration options to register the product. After making your selection, click Next to continue. 11. Click Finish to exit the installation wizard. 12. The WebSphere Application Serer - First Steps console is displayed. Select Start the Serer from the aailable options. After a short time, you should see the following message, indicating that the WebSphere Application Serer is started (note that a 4-digit process ID xxxx is also assigned and included with the message): ADMU3000I: Serer serer1 is open for e-business, process id is xxxx Upgrading WebSphere to Version The Release Notes specifies seeral supported ersions to which you can upgrade the base installation of IBM WebSphere Application Serer. This sample installation upgrades IBM WebSphere Application Serer to ersion by applying the appropriate fix pack, following the steps outlined in Upgrading WebSphere to Version on page 132. Enabling WebSphere Security Follow the procedure in Enabling WebSphere Security on page 132 to enable WebSphere security on the SLM machine. When you specify the Serer user ID and password, use db2admin. Step 6. Creating Databases for IBM Tioli Serice Leel Adisor This installation procedure creates the two databases used by IBM Tioli Serice Leel Adisor, the SLM Database (DYK_CAT) and the SLM Measurement Data Mart (DYK_DM), on the SLM machine. In this sample installation, these databases are created in the same DB2 instance. To create these two databases, complete the following steps: 148 IBM Tioli Serice Leel Adisor: Getting Started

167 1. Verify that the db2jaa.zip file is included in your CLASSPATH system ariable on the SLM machine. See Before Installing IBM Tioli Serice Leel Adisor on page 49 for information on this and other items to check before installing. 2. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the SLM machine. 3. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. 4. Verify the language for the installation (English) and click OK to continue. 5. On the main page of the LaunchPad, click Create Databases. 6. On the Welcome page of the Create Databases Wizard, click Next to continue. 7. On the next window, select both the SLM Database and SLM Measurement Data Mart check boxes. Click Next to continue. 8. On the next window, for the SLM Database, erify that the Local radio button is selected, and click Next to continue. 9. On the next window, confirm that the default name for the SLM Database, dyk_cat, is specified, and the default alue for user ID, db2admin, is specified. In the password field, enter the default alue db2admin, and click Next to continue. 10. On the next window, for the SLM Measurement Data Mart, erify that the Local radio button is selected, and click Next to continue. 11. On the next window, confirm that the default name for the SLM Measurement Data Mart, dyk_dm, is specified, and the default alue for user ID, db2admin, is specified. In the password field, enter the default alue db2admin, and click Next to continue. 12. Confirm your selections on the summary window and click Next to continue. 13. The databases are created. After you receie the final completion message, click Finish to close the Database Creation Wizard and return to the main window of the LaunchPad. You can optionally check the database creation logs for error messages. See Step 4. Checking Database Creation Logs and Tables on page 60 for more information. Step 7. Installing IBM Tioli Serice Leel Adisor Install the SLM Serer, SLM Administration Serer, and the SLM Reports options of IBM Tioli Serice Leel Adisor on the SLM machine by completing the following steps: 1. Verify that the IBM WebSphere Application Serer is started (if not, you are prompted later to start the serer before the installation can continue). 2. If the LaunchPad for IBM Tioli Serice Leel Adisor is not already started, start it by completing the following steps: Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the SLM machine. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. Verify the language for the installation (English) and click OK to continue. 3. On the main page of the LaunchPad, click Install Product. 4. Verify the language for the installation (English) and click OK to continue. 5. On the Welcome window, click Next to continue. Appendix B. A Two-Machine Distributed Installation Example 149

168 6. On the Software License Agreement window, select the I accept the terms in the license agreement radio button and click Next to continue. 7. On the next window, accept the default location for the Tioli Common Directory and click Next to continue. 8. On the next window, erify that the Install IBM Tioli Serice Leel Adisor check box is selected, and click Next to continue (for this sample installation you are not installing the optional language support). 9. On the next window, accept the default directory name where IBM Tioli Serice Leel Adisor is being installed, and click Next to continue. 10. On the next window, erify that the check boxes for all three options (SLM Serer, SLM Administration Serer, and SLM Reports) are selected. Click Next to continue. 11. Prerequisite software is erified on this machine before continuing the installation. 12. Because you enabled WebSphere security, on the next window you are prompted to enter a alid user name and password for WebSphere access. Enter a alid user name and password that you defined when you enabled WebSphere security and click Next to continue. The user name and password are then erified, and the status of the WebSphere Application Serer is erified before continuing. 13. If you had not preiously started the IBM WebSphere Application Serer, the next window asks if you want to start the serer. Select the check box to start the serer and wait for it to complete before continuing. 14. On the next window, erify that the Local radio button is selected for the location of the SLM Database (DYK_CAT), and click Next to continue. 15. On the next window, accept the defaults that are presented in the fields, but in the Password field, enter the DB2 password db2admin. Click Next to continue. 16. On the next window, erify that the Local radio button is selected for the location of the SLM Measurement Data Mart (DYK_DM), and click Next to continue. 17. On the next window, accept the defaults that are presented in the fields, but in the Password field, enter the DB2 password db2admin. Click Next to continue. 18. On the next window, accept the defaults for SLM Serer Communication Port and the Command Line Interface Port configuration and click Next to continue. Leae the remaining fields blank (do not enable password protection for CLI commands). 19. On the next window, for this sample installation, you do not hae to select any options for SLA eent notification. To set up SLA notification, see Step 10. Specify Eent Notification Methods on page 71, otherwise click Next to continue. 20. On the next window (or after configuring for eent notification), you are prompted for a alid user name for SLM Administrator authority and SLM Reports access. Enter db2admin for this user name, and click Next to continue. 21. On the next window, accept the default to not compile JaaSerer Page files, and click Next to continue. 22. On the feature summary window, click Next to proceed with the installation. Wait for completion. 23. After the installation and configuration completes, you are asked if you want to regenerate the IBM WebSphere HTTP plug-in configuration. Verify that the Yes radio button is selected, and click Next to continue. 150 IBM Tioli Serice Leel Adisor: Getting Started

169 24. Additional windows are displayed with configuration and startup information for the SLM Reports and SLM Administration Serer components installed on this machine. Click Next to continue. 25. You are asked if you want to restart the WebSphere Application Serer. Select the check box and click Next. Wait for the serer to be restarted (approximately one minute). If for some reason the serer did not restart automatically, you can manually restart the WebSphere Application Serer by following the procedure in Step 16. Restarting WebSphere Application Serer on page Click Finish to close the wizard and return to the main page of the LaunchPad. Step 8. Configuring ODBC Data Sources To configure ODBC data sources for the SLM Database and SLM Measurement Data Mart, complete the following steps on the Warehouse machine: 1. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the Warehouse machine. 2. Click Start > Run and type the following command to open a DB2 command window: db2cmd. 3. Naigate to <CD-ROM>\database\scripts\w32-ix86\, where <CD-ROM> is the CD-ROM drie letter. 4. Run the dyk_cat_odbc.bat script to create an ODBC data source connection for the SLM Database, specifying the fully qualified hostname of the SLM machine where the database is located, similar to the following example: dyk_cat_odbc.bat tslaslm1.raleigh.ibm.com 5. Similarly, run the dyk_dm_odbc.bat script to create an ODBC data source connection for the SLM Measurement Data Mart, located on the SLM machine: dyk_dm_odbc.bat tslaslm1.raleigh.ibm.com 6. Verify that these ODBC data sources are successfully configured by clicking Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC), and selecting the System DSN tab. The resulting list of ODBC data sources that is displayed should include entries for the default alias names DYK_CAT and DYK_DM. Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Tioli Data Warehouse 1.2 proides a separate installation program to install warehouse packs on the Warehouse machine. Install the DYK target warehouse pack for IBM Tioli Serice Leel Adisor by following the procedure documented in Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment on page 90. Step 10. Configuring the User ID and Password To configure the user ID and password for the target ETLs, complete the following steps on the Warehouse machine: 1. To start the DB2 Control Center, click Start > Programs > IBM DB2 > Control Center and click Tools > Data Warehouse Center. Appendix B. A Two-Machine Distributed Installation Example 151

170 2. On the login window, before logging in, click Adanced and erify that the control database is set to TWH_MD. If it is not, edit this field and change it to this alue. 3. Log in to the Data Warehouse Center with the default user name db2admin and password db2admin. 4. In the left pane of the Data Warehouse Center, expand the Warehouse Targets folder. 5. In the Warehouse Targets folder, right-click the DYK_DYK_CAT_Target entry and select Properties from the context menu. Then select the Database tab, and enter the default user name db2admin and password db2admin. Click OK when done. 6. In the Warehouse Targets folder, right-click the DYK_DYK_DM_Target entry and select Properties from the context menu. Then select the Database tab, and enter the default user name db2admin and password db2admin. Click OK when done. Step 11. Enabling Data Collection for Source Applications You need to enable source applications for which you want to collect and ealuate data in IBM Tioli Serice Leel Adisor. Only data from enabled source applications is transferred from Tioli Data Warehouse to IBM Tioli Serice Leel Adisor and accepted for ealuation and analysis. Follow the instructions for enabling data for source applications on the SLM machine in Enabling Data Collection for Source Applications on page 95. Step 12. Configuring ETLs for Production Mode Follow the instructions for configuring ETLs for production mode on the Warehouse machine as discussed in Configuring ETLs for Production Mode on page 101. Step 13. Running the Registration and Process ETLs If you hae data in the central data warehouse for source applications that you enabled, either wait for the scheduled run of the Registration and Process ETLs or run them on demand. To run the ETLs manually on the Warehouse machine, follow the procedures in Running the Registration ETL and Process ETL on page 103. Step 14. Registering Warehouse Data After the Registration ETL has run at least one time, either wait approximately minutes for the data to be registered with IBM Tioli Serice Leel Adisor, or register the data yourself on the SLM machine. See Registering Warehouse Data on page 104 for details. Step 15. Additional Optional Configuration If you selected eent notification, you might need to perform a few additional configuration steps on the SLM machine. See Configuring for Eent Notification on page 107 for more information. In this sample installation you did not install the source warehouse pack for IBM Tioli Serice Leel Adisor. To install this warehouse pack on the Warehouse 152 IBM Tioli Serice Leel Adisor: Getting Started

171 machine, see the procedures in Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105. In this sample installation you did not install additional language support. To install language support for IBM Tioli Serice Leel Adisor, see the procedures in Installing Language Support on page 109. Also see Installing and Configuring Tioli Data Warehouse for information on installing language support for Tioli Data Warehouse on the Warehouse machine. Step 16. Restarting WebSphere Application Serer You need to stop and restart the WebSphere Application Serer on the SLM machine, but because you enabled WebSphere security, you are not allowed to stop the WebSphere Application Serer without proiding the authorized user name and password. You can stop and restart the WebSphere Application Serer by completing the following steps: 1. Open a command prompt window. 2. Naigate to C:\Program Files\WebSphere\Appserer\bin, the location where IBM WebSphere Application Serer was installed on the SLM machine. 3. Issue the following command: stopserer serer1 -username db2admin -password db2admin 4. Wait for the serer to be stopped. 5. Issue the following command to restart the serer: startserer serer1 Note: You do not need to specify the user name and password to start the serer. See Starting IBM WebSphere Application Serer on page 115 for alternatie start-up procedures. 6. Wait for the open for e-business message to be displayed. Accessing the SLM Administratie Console Accessing SLM Reports After the WebSphere Application Serer has restarted, access the SLM Administratie Console by opening your Web browser and naigating to the following Web site, specifying the fully qualified hostname for the SLM machine (where the SLM Administration Serer is installed): If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. See Managing Serice Leel Agreements for information about using the SLM Administratie Console to create and manage your SLAs. You can also access the SLM Reports user interface by naigating to the following Web site, specifying the fully qualified hostname for the SLM machine, where you installed SLM Reports: If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. Appendix B. A Two-Machine Distributed Installation Example 153

172 See SLM Reports for information about using the reporting interface of IBM Tioli Serice Leel Adisor to iew results of the ealuation and analysis of reported data by IBM Tioli Serice Leel Adisor. 154 IBM Tioli Serice Leel Adisor: Getting Started

173 Appendix C. A Three-Machine Distributed Installation Example The following procedure is a consolidated set of steps to perform a sample IBM Tioli Serice Leel Adisor solution installation that can be used as an entry-leel production enironment. These procedures take all aailable defaults. The deployment consists of three Windows 2000 machines aailable in your enterprise, that contain all components of DB2 Uniersal Database, Crystal Enterprise Professional 9, Tioli Data Warehouse, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor. Figure 53 shows the deployment of this sample distributed installation scenario. Figure 53. A three-machine distributed deployment For this sample installation, the three machines are referred to as the Warehouse machine, the Crystal machine, and the SLM machine. This configuration is essentially identical to the two-machine configuration in Appendix B, A Two-Machine Distributed Installation Example, on page 141, with the following exceptions: The Crystal Enterprise serer is located on a separate Windows machine from the Warehouse machine. For this scenario, assume that the Crystal machine is on a Windows 2000 operating system. A DB2 client must be installed on the Crystal machine to communicate with the data mart database on the Warehouse machine. Crystal Enterprise is installed on the Crystal machine. Copyright IBM Corp. 2002,

174 Installation Assumptions Because Crystal Enterprise is installed on a different machine than Tioli Data Warehouse, an ODBC data source connection is needed for Crystal Enterprise to communicate with the Tioli Data Warehouse data mart. This installation procedure is based on the same assumptions and procedural steps as specified in Appendix B, A Two-Machine Distributed Installation Example, on page 141, with the following exceptions: Install DB2 Client software on the Crystal machine after installing DB2 Serer on the Warehouse and SLM machines. See Step 3: Installing a DB2 client for Crystal Enterprise in Chapter 4, Installing a quick start deployment of Installing and Configuring Tioli Data Warehouse. For this sample installation, it is assumed that you continue to specify the DB2 user name as db2admin and DB2 password as db2admin on the Crystal machine, similar to the Warehouse and SLM machines. Install Crystal Enterprise Professional 9 on the Crystal machine instead of on the Warehouse machine. During the installation of Tioli Data Warehouse on the Warehouse machine, you need to specify on the Crystal Enterprise Connection page the fully qualified hostname of the Crystal machine where Crystal Enterprise is located. For this sample installation the Crystal machine hostname is of the form: crystal.raleigh.ibm.com After installing Tioli Data Warehouse on the Warehouse machine, follow Step 7: Creating an ODBC connection from the Crystal Enterprise serer to the data marts in Installing and Configuring Tioli Data Warehouse. Because the Crystal Enterprise serer is on a stand-alone system and no other Tioli Data Warehouse components are installed on the Crystal machine, use the twh_create_datasource command to create the ODBC data source on the Crystal Enterprise machine, by completing the following steps: 1. On the Crystal machine, open a DB2 command prompt. 2. Run the twh_create_datasource command from the \disk1\tools directory of the Tioli Data Warehouse installation media: twh_create_datasource DB2UDB 0 TWH_MART TWH_MART tdwcdw1.raleigh.ibm.com db2admin db2admin In this command the fully qualified hostname of the Warehouse machine, where the data mart is located, was specified, along with the default port number (50000) and DB2 user ID and password. 3. Reboot the Crystal machine after creating the ODBC data source. Copy the Crystal documentation to a location on the Crystal machine. Completing the aboe steps will configure your three-machine SLM solution for receiing and processing data from one or more source applications that will write data into the central data warehouse. 156 IBM Tioli Serice Leel Adisor: Getting Started

175 Appendix D. A Four-Machine Distributed Installation Example The following procedure is a consolidated set of steps to perform a sample IBM Tioli Serice Leel Adisor solution installation that can be used in a production enironment. This sample installation procedure takes all aailable defaults. The deployment consists of three Windows 2000 machines and one UNIX machine aailable in your enterprise, that contain all components of DB2 Uniersal Database, Crystal Enterprise Professional 9, Tioli Data Warehouse, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor. Figure 54 shows the deployment of this moderately distributed installation. Figure 54. A four-machine distributed deployment For this sample installation, we refer to the four machines as the Warehouse machine, the SLM machine, the Crystal machine, and the Database machine. This configuration is an expansion of the three-machine configuration described in Appendix C, A Three-Machine Distributed Installation Example, on page 155, but for this installation, the central warehouse database and data mart for Tioli Data Warehouse, along with the SLM Database and SLM Measurement Data Mart databases for IBM Tioli Serice Leel Adisor, are all located on a separate UNIX database serer machine. This might be a more typical configuration for production leel enironments, with databases located on larger machines that hae the capacity for storing the large amount of data transferred oer time. In fact, you might hae the arious databases distributed among multiple large serer Copyright IBM Corp. 2002,

176 The Warehouse Machine The Crystal Machine The Database Machine class machines in your enterprise, possibly creating remote agent sites to more efficiently handle the transfer of data between the central data warehouse and the data marts. For simplicity, this sample installation locates all of the databases on a single machine. From the perspectie of a pure Tioli Data Warehouse installation, this is considered a distributed installation, because the central data warehouse and data mart are located on a different machine from the control serer. Similarly, from the perspectie of a pure IBM Tioli Serice Leel Adisor installation, the SLM Database and SLM Measurement Data Mart are located on a different machine than the SLM Serer, SLM Administration Serer, and SLM Reports components, resulting in a distributed installation of IBM Tioli Serice Leel Adisor. This configuration requires a few more steps to be performed in the installation and configuration procedures, to establish communication between the arious machines in this distributed installation. The Warehouse machine has the following characteristics: The operating system must be one of the supported Windows operating systems because the control serer component of Tioli Data Warehouse is only supported on a Windows operating system. For this sample installation a Windows 2000 operating system is used. See the Release Notes for the list of supported Windows operating systems that you can use for this installation. The machine is set up as a DB2 serer machine because the control serer for Tioli Data Warehouse requires the DB2 serer function. The control serer for Tioli Data Warehouse is installed on this machine, and a distributed installation is performed using the Tioli Data Warehouse installation program, specifying the Database machine as the target for the central data warehouse and data mart components. Warehouse packs are installed on this machine because the control serer component of Tioli Data Warehouse is installed on this machine. The Crystal machine has the following characteristics: The operating system must be one of the supported Windows operating systems. For this sample installation a Windows 2000 operating system is used. See the documentation accompanying Tioli Data Warehouse for more information about the supported operating systems that you can use for this installation. A DB2 client must be installed on the Crystal machine to communicate with the data mart database on the Database machine. Crystal Enterprise Professional 9 is installed on this machine. Because Crystal Enterprise is installed on a different machine than the Tioli Data Warehouse data mart component, an ODBC data source connection is needed for Crystal Enterprise to communicate with the Tioli Data Warehouse data mart on the Database machine. The Database machine has the following characteristics: 158 IBM Tioli Serice Leel Adisor: Getting Started

177 The SLM Machine The operating system can be any supported Windows, UNIX (AIX or Solaris), or z/os operating system. For this sample installation an AIX operating system is used. See the Release Notes for the list of supported operating systems that you can use for this installation. The machine is set up as a DB2 serer machine, because the databases require the DB2 serer function. An ODBC connection is established between the Crystal machine and this machine to enable Crystal Enterprise to communicate with the data mart as part of the reporting function for Tioli Data Warehouse. This is not used by IBM Tioli Serice Leel Adisor, but might be used by other applications in your enterprise that get reports from Crystal Enterprise. The central data warehouse and data mart databases for Tioli Data Warehouse are installed on this machine. You create these when you run the installation program for Tioli Data Warehouse on the Warehouse machine. As part of that procedure, you specify the hostname of this Database machine where the central data warehouse and data mart is to be located, and the installation program creates the databases on this machine. The SLM Database and SLM Measurement Data Mart for IBM Tioli Serice Leel Adisor are also installed on this machine. You create these as remote databases (from the perspectie of the SLM Serer on the SLM machine) when you run the installation program for IBM Tioli Serice Leel Adisor on the SLM machine. During the installation of the SLM Serer, the connection between the SLM Serer on the SLM machine and these databases on the Database machine is erified. You need to create ODBC data sources for the SLM Database and the SLM Measurement Data Mart on the Warehouse machine. Because both the central data warehouse and the data marts will all be located on this Database machine, you do not need to create an agent site to manage the data. Special programs in Tioli Data Warehouse recognize that the data is on the same computer, and transfer the data from the central data warehouse to the data marts without the use of a warehouse agent. The SLM machine has the following characteristics: The operating system can be any supported Windows or UNIX operating system. For this sample installation a Windows 2000 operating system is used. See the Release Notes for the list of supported operating systems that you can use for this installation. Because the SLM Database and SLM Measurement Data Mart are located on a separate machine, you can install either DB2 client or DB2 serer software on this SLM machine. For simplicity, this installation installs a DB2 client. IBM WebSphere Application Serer will be installed on this machine to support the SLM Administration Serer and SLM Reports components of IBM Tioli Serice Leel Adisor. For simplicity both of these components are installed in a single serer (serer1) WebSphere enironment. WebSphere security is enabled. All components (SLM Serer, SLM Administration Serer, and SLM Reports) of IBM Tioli Serice Leel Adisor are installed on this machine. During the installation, you refer to the SLM Database and SLM Measurement Data Mart as remote databases (on a machine other than where the SLM Serer is located) and refer to the Database machine as the location for these databases. Connections to the databases on the Database machine are created and erified. Appendix D. A Four-Machine Distributed Installation Example 159

178 Installation Assumptions Source and target warehouse packs for IBM Tioli Serice Leel Adisor are installed on the Warehouse machine, where the control serer is located. This installation procedure is based on the following assumptions: You hae familiarized yourself with the product by reading the oeriew and planning chapters, and hae reiewed the installation procedures before starting the installation. You hae completed the planning worksheets as needed for the installation, collecting the following necessary information that you need to specify during the installation: Fully qualified machine names Authorized user names and passwords for DB2 Uniersal Database, Crystal Enterprise Professional 9, IBM WebSphere Application Serer, and IBM Tioli Serice Leel Adisor Selected port numbers for communication Selected target installation directory paths Selected database names Usually you can use default alues for these items when they are proided. The machines are configured to meet all hardware and software prerequisite requirements defined in the Tioli Data Warehouse and IBM Tioli Serice Leel Adisor Release Notes and other documentation, including: Supported hardware and operating system serice leels hae been applied. Adequate temporary disk space is aailable. The machines hae been configured to return fully qualified hostnames. The machines are configured to automatically start from the product CD. A supported Web browser is installed on each machine. You hae adequate authority to perform the installation (for example, Administrator authority on Windows systems, or root user authority on UNIX systems), with the necessary roles and priileges assigned to the user name that you use for the installation (see Ensuring User Rights Authority for Database Creation on page 184 for more information). Any preious installation of Tioli Data Warehouse or IBM Tioli Serice Leel Adisor has been completely remoed from the machines. This sample installation does not include an upgrade from a preious ersion of these applications. You hae aailable the required installation media for the SLM solution, including: IBM DB2 Uniersal Database installation CD, included with Tioli Data Warehouse 1.2 Use the same ersion on all machines: This sample installation assumes that all four machines hae the same ersion of DB2 Uniersal Database installed. Adanced configurations, in which other supported ersions of DB2 Uniersal Database are installed with additional configuration steps to enable different ersions to communicate among themseles are not considered in this sample installation. Crystal Enterprise Professional 9 installation media, included with Tioli Data Warehouse 1.2 Tioli Data Warehouse 1.2 installation media 160 IBM Tioli Serice Leel Adisor: Getting Started

179 IBM WebSphere Application Serer 5.1 installation media Optionally, the IBM WebSphere Application Serer 5.1 Cumulatie Fix Pack 5 to upgrade to ersion (downloaded from the product support Web site to a temporary directory on your machine) IBM Tioli Serice Leel Adisor 2.1 installation media, which includes the source (DY1) and target (DYK) warehouse packs for installing with Tioli Data Warehouse 1.2 One or more source application warehouse packs that are installed and configured with their associated source applications to write data into Tioli Data Warehouse You are familiar with basic operations, such as starting a DB2 command prompt before issuing DB2 commands (see Starting a DB2 Command Prompt on page 183). No additional language support is needed for this installation (English only). The installation procedure consists of the following major steps, which are described in more detail in the remaining sections of this appendix: 1. Install IBM DB2 Uniersal Database serer software on the Warehouse machine and the Database machine, and install IBM DB2 Uniersal Database client software on the Crystal and SLM machines. 2. Install Crystal Enterprise 9 on the Crystal machine 3. Install the control serer component of Tioli Data Warehouse on the Warehouse machine, and create the central data warehouse and data mart for Tioli Data Warehouse on the Database machine. For this sample installation, install only one central data warehouse and one data mart. Because Crystal Enterprise is installed on a stand-alone system and no other Tioli Data Warehouse components are installed on the Crystal machine, you need to create an ODBC connection between the Crystal machine and the data mart for Tioli Data Warehouse on the Database machine. 4. Install and configure source application warehouse packs on the Warehouse machine as needed. The specific steps to install and configure the arious source applications and their associated warehouse packs for writing data into the central data warehouse are not included here, because they are specific to each source application. See Warehouse Enablement Packs on page ix to find information on currently aailable warehouse packs. Verify measurement data in the central data warehouse: At this point in the oerall process you should be able to collect local measurement data with your installed source applications, and run scheduled source application ETLs from your installed warehouse packs to write data into Tioli Data Warehouse. You should erify that this part of the SLM enironment operates properly before continuing with this installation. 5. Install IBM WebSphere Application Serer on the SLM machine. For purposes of this sample installation, install only a single application serer, serer1. After installing the base ersion, you can optionally upgrade the installation to a supported fix pack leel. This sample installation is upgraded to ersion WebSphere security is enabled for this sample installation. 6. Create the SLM Database and SLM Measurement Data Mart on the Database machine. You create these databases by running the LaunchPad program on the SLM machine, and specifying these databases as remote databases with respect to the location of the SLM Serer on the SLM machine. You will need to specify connection information to the Database machine for DB2 Uniersal Database to create and catalog these databases properly. Appendix D. A Four-Machine Distributed Installation Example 161

180 7. Install all components of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Administration Serer, and SLM Reports) on the SLM machine. 8. Create ODBC datasources for the SLM Database and SLM Measurement Data Mart on the Warehouse machine. 9. Install the IBM Tioli Serice Leel Adisor source and target warehouse packs on the Warehouse machine. 10. Configure user IDs and passwords on the Warehouse machine. 11. Perform additional configuration steps to enable the flow of data between Tioli Data Warehouse and IBM Tioli Serice Leel Adisor and schedule the ETLs to run. Completing the aboe steps configures your four-machine SLM solution for receiing and processing data from one or more source applications that write data into the central data warehouse. Planning Worksheets for this Installation Refer to Installing and Configuring Tioli Data Warehouse for the following planning worksheets that apply to this installation: Planning worksheet for a Crystal Enterprise serer Planning worksheets for a distributed deployment without remote agent sites Planning worksheet for installing warehouse packs In addition to the aboe planning information, you should also refer to the following planning worksheets for IBM Tioli Serice Leel Adisor: Table 7 on page 25 Table 9 on page 30 Table 10 on page 32 Step 1. Installing DB2 Uniersal Database Serer and Client Install the DB2 Uniersal Database serer software on both the Warehouse (Windows) machine and the Database (AIX) machine, and install the DB2 Uniersal Database client software on the Crystal (Windows) and SLM (Windows) machines, following the procedures for Installing Tioli Data Warehouse in a distributed deployment that does not use remote agent sites in Installing and Configuring Tioli Data Warehouse, completing the following steps for each machine: Step 1: Preparing the enironment For this installation, use the following assumptions for each machine: Log on to the Windows machines with a user name that has Administrator authority (you might need to get this from your system administrator). Follow the procedures for AIX operating systems for the Database machine. The user name db2admin and password db2admin are created for database access on all machines, and do not already exist on any of the four machines. You do not hae to use the same user name and password on all of the machines, but for simplicity in this sample installation, they are the same on all four machines. Use this user ID and password wheneer you are prompted for them throughout the installation (or make up your own and substitute them in this procedure). The machines are configured to return fully qualified hostnames (erify this using the documented procedures for Windows and AIX operating systems as appropriate in this section). 162 IBM Tioli Serice Leel Adisor: Getting Started

181 The machines in this sample installation hae the following fully qualified hostnames: - For the Warehouse machine: tdwctrl.raleigh.ibm.com - For the Crystal machine: crystal.raleigh.ibm.com - For the Database machine: dbtdwsla.raleigh.ibm.com - For the SLM machine: tsla.raleigh.ibm.com Step 2: Installing and configuring IBM DB2 Uniersal Database Enterprise Edition For this installation scenario, use the following assumptions: You are not reusing an existing instance of DB2 Uniersal Database. You are installing DB2 Uniersal Database using the installation media proided with Tioli Data Warehouse 1.2. The systems are configured to automatically start the setup.exe installation program located in the root directory. You specify the DB2 user name as db2admin (the default) and the password also as db2admin on all systems For the Warehouse machine, follow the procedures documented in the section, Installing IBM DB2 Uniersal Database Enterprise Edition on Windows systems. For the Database machine, follow the procedures documented in the section, Installing IBM DB2 Uniersal Database Enterprise Edition on AIX systems. Step 3: Installing a DB2 client for Crystal Enterprise serer For both the Crystal and the SLM machines, follow the procedures documented in this section to install a DB2 client on these two Windows machines. After the installation of DB2 Uniersal Database is complete, reboot the SLM machine before continuing. Step 2. Installing Crystal Enterprise Install the Crystal Enterprise software on the Crystal machine by following the procedures for Installing Tioli Data Warehouse in a distributed deployment that does not use remote agent sites in Installing and Configuring Tioli Data Warehouse, completing the steps in the section, Step 4: Installing Crystal Enterprise serer. For this installation scenario, use the following assumptions: You are not upgrading an existing installation of Crystal Enterprise. You are using the installation media for Crystal Enterprise proided with Tioli Data Warehouse. MSDE and Microsoft SQL Serer are not already installed. For the Default SQL Administrator (sa) password, specify a password of your choice, such as sapw001. Specify the default Crystal user name of Administrator and leae the password blank (by default). At the end of this installation procedure is a reference to additional configuration steps that you might need to complete if the Web serer on your machine is IBM HTTP Serer. You might need to complete these steps if you plan to install warehouse packs for applications that make use of Crystal Enterprise for reports. IBM Tioli Serice Leel Adisor does not use Crystal Enterprise for its reporting function, so this is not needed for IBM Tioli Serice Leel Adisor. If you do not intend to install warehouse packs that proide Crystal Reports, you do not hae to complete these additional steps. Appendix D. A Four-Machine Distributed Installation Example 163

182 Step 3. Installing Tioli Data Warehouse Install the control serer component of Tioli Data Warehouse on the Warehouse machine, and the central data warehouse and data mart components of Tioli Data Warehouse on the Database machine by following the procedures for Installing Tioli Data Warehouse in a distributed deployment that does not use remote agent sites in Installing and Configuring Tioli Data Warehouse, completing the steps in the following sections: Step 5: Installing the control serer and creating databases For this sample installation, use the following assumptions: Run the Tioli Data Warehouse installation program on the Warehouse machine. Accept the default location for the Tioli Common Directory. Select the Custom or distributed installation type. Accept the default for the installation directory for Tioli Data Warehouse. In the Connection to Local Control Serer window, specify the DB2 user name db2admin and password db2admin that you defined preiously. In the Central Data Warehouses window, specify the following information for the Database machine where the central data warehouse is to be located: - Host Location: Remote host - Host Name: dbtdwsla.raleigh.ibm.com - DB2 Port Number: Database Type: DB2 UDB - DB2 User ID: db2admin - Password: db2admin In the Data Marts window, specify this same information to indicate where the data mart for Tioli Data Warehouse is to be located. For the Crystal Enterprise serer in this sample installation, enter the fully qualified machine name for the Crystal machine: crystal.raleigh.ibm.com For the Crystal user name, specify the default name of Administrator. Leae the password field blank. Step 6: Specifying the control database for the DB2 Data Warehouse Center For this step, when you log on to the Data Warehouse Center, specify the DB2 user name db2admin and password db2admin for the control serer. Step 7: Creating an ODBC connection from the Crystal Enterprise serer to the data marts Because the Crystal Enterprise serer is on a stand-alone system and no other Tioli Data Warehouse components are installed on the Crystal machine, use the twh_create_datasource command to create the ODBC data source on the Crystal Enterprise machine: 1. On the Crystal machine, open a DB2 command prompt. 2. Run the twh_create_datasource command from the \disk1\tools directory of the Tioli Data Warehouse installation media: twh_create_datasource DB2UDB 0 TWH_MART TWH_MART dbtdwsla.raleigh.ibm.com db2admin db2admin In this command the fully qualified hostname of the Database machine, where the data mart is located, is specified, along with the default port number (50000) and DB2 user ID and password. 164 IBM Tioli Serice Leel Adisor: Getting Started

183 3. Reboot the Crystal machine after creating the ODBC data source. Step 8: Completing the Installation Follow the instructions and recommendations in this section to complete the installation of Tioli Data Warehouse. Step 4. Installing Source Application Warehouse Packs After installing DB2 Uniersal Database, Crystal Enterprise, and Tioli Data Warehouse, you should install and configure any source application warehouse packs to write data into the central data warehouse database. All warehouse packs are installed on the Warehouse machine (where the control serer is located). Specific installation procedures are aailable in the implementation guide that accompanies each source application warehouse pack. Consult your Tioli Data Warehouse and warehouse pack documentation for more information. You should complete the installation and configuration of this part of your warehouse enironment (Tioli Data Warehouse, source applications, and their associated warehouse pack ETLs) so that they are operating properly before continuing to install IBM WebSphere Application Serer and IBM Tioli Serice Leel Adisor. This ensures that data is aailable in the central data warehouse for extraction and ealuation by IBM Tioli Serice Leel Adisor. Step 5. Installing IBM WebSphere Application Serer This procedure installs IBM WebSphere Application Serer, Version 5.1, that ships with IBM Tioli Serice Leel Adisor. After installing the base 5.1 ersion on the SLM machine, you can optionally upgrade this installation to at least ersion See Upgrading WebSphere to Version on page 132 for more information. If you hae a preious ersion of IBM WebSphere Application Serer already installed, consult the accompanying documentation for additional installation and upgrade information. See the Release Notes for information on specific supported ersions of IBM WebSphere Application Serer. To install Websphere Application Serer 5.1, complete the following steps. If you experience any problems during this installation, refer to the install documentation for IBM WebSphere Application Serer. 1. Insert the Windows ersion of the WebSphere Application Serer 5.1 product CD in the CD-ROM of the SLM machine and run the LaunchPad.bat program. Select the language for the LaunchPad, and then on the main LaunchPad window that displays, click Install the product. 2. On the Language window for the installation wizard, select the language and click OK to continue. 3. On the Welcome window, click Next to continue. 4. Reiew and accept the Software License Agreement that is displayed, by selecting the I accept the terms in the license agreement radio button, and click Next to continue. 5. From the setup type selection window, select the Full radio button to install eerything you need. Click Next to continue. 6. On the next window, accept the default target installation directories that are displayed. Click Next to continue. 7. On the next window, erify that the node name and the fully qualified hostname that are displayed are correct for this machine, or enter the correct alues and click Next to continue. Appendix D. A Four-Machine Distributed Installation Example 165

184 8. On the next window, accept the default serices check boxes that are selected. Also erify that the user ID is specified, or enter your own, and enter a alid password for that user ID. Then click Next to continue. 9. On the summary window that is displayed, erify the installation options you hae selected, and click Next to continue. 10. The installation begins and files are copied to the SLM machine. After seeral minutes, the installation completes. You are presented with registration options to register the product. After making your selection, click Next to continue. 11. Click Finish to exit the installation wizard. 12. The WebSphere Application Serer - First Steps console is displayed. Select Start the Serer from the aailable options. After a short time, you should see the following message, indicating that the WebSphere Application serer is started (note that a 4-digit process ID xxxx is also assigned and included with the message): ADMU3000I: Serer serer1 is open for e-business, process id is xxxx Upgrading WebSphere to Version The Release Notes specifies seeral acceptable ersions to which you can upgrade the base installation of IBM WebSphere Application Serer. This sample installation upgrades IBM WebSphere Application Serer to ersion by applying the appropriate fix pack, following the steps outlined in Upgrading WebSphere to Version on page 132. See the Readme file that accompanies the fix pack installation in the...\update\docs directory for more information. Enabling WebSphere Security Follow the procedure in Enabling WebSphere Security on page 132 to enable WebSphere security on the SLM machine. When you specify the Serer user ID and password, use db2admin. Step 6. Creating Databases for IBM Tioli Serice Leel Adisor This installation procedure creates the two databases used by IBM Tioli Serice Leel Adisor, the SLM Database (DYK_CAT) and the SLM Measurement Data Mart (DYK_DM) on the Database machine. In this sample installation, these databases are created in the same DB2 instance. These databases are created by running the IBM Tioli Serice Leel Adisor LaunchPad.bat program on the SLM machine to create the databases on the Database machine as remote databases with respect to the location of the SLM Serer, which is installed in the SLM machine. To create these two databases as remote databases, complete the following steps: 1. Verify that the db2jaa.zip file is included in your CLASSPATH system ariable on the SLM machine (see Before Installing IBM Tioli Serice Leel Adisor on page 49 for information on this and other items to check before installing). 2. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the SLM machine. 3. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. 4. Verify the language for the installation (English) and click OK to continue. 166 IBM Tioli Serice Leel Adisor: Getting Started

185 5. On the main window of the LaunchPad, click Create Databases. 6. On the Welcome window of the Create Databases Wizard, click Next to continue. 7. On the next window, select both the SLM Database and SLM Measurement Data Mart check boxes. Click Next to continue. 8. On the next window, for the SLM Database, erify that the Remote radio button is selected, and click Next to continue. 9. On the next window, you are asked if the SLM Database will be created on a system running on a z/os or OS/390 operating system. Verify that the No radio button is selected, and click Next to continue. 10. On the next window, specify the following information indicating that the SLM Database is to be created remotely on the Database machine: Database Name: dyk_cat User ID: db2admin Password: db2admin Database Serer Host Name: dbtdwsla.raleigh.ibm.com Database Serer Instance Port Number: Remote Database Instance: db2inst1 Click Next to continue. 11. On the next window, for the SLM Measurement Data Mart, erify that the Remote radio button is selected, and click Next to continue. 12. On the next window, you are asked if the SLM Measurement Data Mart will be created on a system running on a z/os or OS/390 operating system. Verify that the No radio button is selected, and click Next to continue. 13. On the next window, specify the following information indicating that the SLM Measurement Data Mart is to be created remotely on the Database machine: Database Name: dyk_dm User ID: db2admin Password: db2admin Database Serer Host Name: dbtdwsla.raleigh.ibm.com Database Serer Instance Port Number: Remote Database Instance: db2inst1 Click Next to continue. 14. Confirm your selections on the summary window and click Next to continue. 15. The databases are created. After you receie the final completion message, click Finish to close the Database Creation Wizard and return to the main page of the LaunchPad. You can optionally check the database creation logs for error messages. See Step 4. Checking Database Creation Logs and Tables on page 60 for more information. Step 7. Installing IBM Tioli Serice Leel Adisor Install the SLM Serer, SLM Administration Serer, and the SLM Reports options of IBM Tioli Serice Leel Adisor on the SLM machine by completing the following steps: 1. Verify that the IBM WebSphere Application Serer has been started (if not, you are prompted later to start the serer before the installation can continue). Appendix D. A Four-Machine Distributed Installation Example 167

186 2. If the LaunchPad for IBM Tioli Serice Leel Adisor is not already started, start it by completing the following steps: Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the SLM machine. From the root directory of the product CD, run the LaunchPad.bat script to start the LaunchPad. Verify the language for the installation (English) and click OK to continue. 3. On the main window of the LaunchPad, click Install Product. 4. Verify the language for the installation (English) and click OK to continue. 5. On the Welcome window, click Next to continue. 6. On the Software License Agreement window, select the I accept the terms in the license agreement radio button and click Next to continue. 7. On the next window, accept the default location for the Tioli Common Directory and click Next to continue. 8. On the next window, erify that the Install IBM Tioli Serice Leel Adisor check box is selected, and click Next to continue (for this sample installation you are not installing the optional language support). 9. On the next window, accept the default directory name where IBM Tioli Serice Leel Adisor is being installed, and click Next to continue. 10. On the next window, erify that the check boxes for all three options (SLM Serer, SLM Administration Serer, and SLM Reports) are selected. Click Next to continue. 11. Prerequisite software is erified on this machine before continuing the installation. 12. Because you enabled WebSphere security, on the next page you are prompted to enter a alid user name and password for WebSphere access. Enter a alid user name and password that you defined when you enabled WebSphere security and click Next to continue. The user name and password are then erified, and the status of the WebSphere Application Serer is erified before continuing. 13. If you had not preiously started the IBM WebSphere Application Serer, the next page asks if you want to start the serer. Select the check box to start the serer and wait for it to complete before continuing. 14. On the next window, erify that the Remote radio button is selected for the location of the SLM Database (DYK_CAT), and click Next to continue. 15. On the next window, erify or reenter the information that you proided when you originally created the SLM Database (see step 10 on page 167). Click Next to continue. 16. On the next window, erify that the Remote radio button is selected for the location of the SLM Measurement Data Mart (DYK_DM), and click Next to continue. 17. On the next window, erify or reenter the information that you proided when you originally created the SLM Measurement Data Mart (see step 13 on page 167). Click Next to continue. 18. On the next window, accept the defaults for SLM Serer Communication Port and the Command Line Interface Port configuration and click Next to continue. Leae the remaining fields blank (do not enable password protection for CLI commands). 168 IBM Tioli Serice Leel Adisor: Getting Started

187 19. On the next window, for this sample installation, you do not hae to select any options for SLA eent notification. To set up SLA notification, see Step 10. Specify Eent Notification Methods on page 71, otherwise click Next to continue. 20. On the next window (or after configuring for eent notification), you are prompted for a alid user name for SLM Administrator authority and SLM Reports access. Enter db2admin for this user name, and click Next to continue. 21. On the next window, accept the default to not compile JaaSerer Page files, and click Next to continue. 22. On the feature summary window, click Next to proceed with the installation. Wait for completion. 23. After the installation and configuration completes, you are asked if you want to regenerate the IBM WebSphere HTTP plug-in configuration. Verify that the Yes radio button is selected, and click Next to continue. 24. Additional windows are displayed with configuration and startup information for the SLM Reports and SLM Administration Serer components installed on this machine. Click Next to continue. 25. You are asked if you want to restart the WebSphere Application Serer. Select the check box and click Next. Wait for the serer to be restarted (approximately one minute). If for some reason the serer did not restart automatically, you can manually restart the WebSphere Application Serer by following the procedure in Step 16. Restarting WebSphere Application Serer on page Click Finish to close the wizard and return to the main page of the LaunchPad. Step 8. Configuring ODBC Data Sources To configure ODBC data sources for the SLM Database and SLM Measurement Data Mart, complete the following steps on the Warehouse machine: 1. Insert the IBM Tioli Serice Leel Adisor product CD in the CD-ROM drie of the Warehouse machine. 2. Click Start > Run and type the following command to open a DB2 command window: db2cmd. 3. Naigate to <CD-ROM>\database\scripts\w32-ix86\, where <CD-ROM> is the CD-ROM drie letter. 4. Run the dyk_cat_odbc.bat script to create an ODBC data source connection for the SLM Database, specifying the fully qualified hostname of the Database machine where the SLM Database is located similar to the following example: dyk_cat_odbc.bat dbtdwsla.raleigh.ibm.com 5. Similarly, run the dyk_dm_odbc.bat script to create an ODBC data source connection for the SLM Measurement Data Mart, located on the Database machine: dyk_dm_odbc.bat dbtdwsla.raleigh.ibm.com 6. Verify that these ODBC data sources are successfully configured by clicking Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC), and selecting the System DSN tab. The resulting list of ODBC data sources that is displayed should include entries for the default alias names DYK_CAT and DYK_DM. Appendix D. A Four-Machine Distributed Installation Example 169

188 Step 9. Installing the IBM Tioli Serice Leel Adisor Target Warehouse Pack Tioli Data Warehouse 1.2 proides a separate installation program to install warehouse packs on the Warehouse machine. Install the DYK target warehouse pack for IBM Tioli Serice Leel Adisor by following the procedure documented in Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment on page 90. Step 10. Configuring the User ID and Password To configure the user ID and password for the target ETLs, complete the following steps on the Warehouse machine: 1. To start the DB2 Control Center, click Start > Programs > IBM DB2 > Control Center) and click Tools > Data Warehouse Center. 2. On the login window, before logging in, click Adanced and erify that the control database is set to TWH_MD. If it is not, edit this field and change it to this alue. 3. Log in to the Data Warehouse Center with the default user name db2admin and password db2admin. 4. In the left pane of the Data Warehouse Center, expand the Warehouse Targets folder. 5. In the Warehouse Targets folder, right-click the DYK_DYK_CAT_Target entry and select Properties from the context menu. Then select the Database tab, and enter the default user name db2admin and password db2admin. Click OK when done. 6. In the Warehouse Targets folder, right-click the DYK_DYK_DM_Target entry and select Properties from the context menu. Then select the Database tab, and enter the default user name db2admin and password db2admin. Click OK when done. Step 11. Enabling Data Collection for Source Applications You need to enable source applications for which you want to collect and ealuate data in IBM Tioli Serice Leel Adisor. Only data from enabled source applications will be transferred from Tioli Data Warehouse to IBM Tioli Serice Leel Adisor and accepted for ealuation and analysis. Follow the instructions for enabling data for source applications on the SLM machine in Enabling Data Collection for Source Applications on page 95. Step 12. Configuring ETLs for Production Mode Follow the instructions for configuring ETLs for production mode on the Warehouse machine as discussed in Configuring ETLs for Production Mode on page 101. Step 13. Running the Registration and Process ETLs If you hae data in the central data warehouse for source applications that you hae enabled, either wait for the scheduled run of the Registration and Process ETLs or run them on demand. To run the ETLs manually on the Warehouse machine, follow the procedures in Running the Registration ETL and Process ETL on page IBM Tioli Serice Leel Adisor: Getting Started

189 Step 14. Registering Warehouse Data After the Registration ETL has run at least one time, either wait approximately minutes for the data to be registered with IBM Tioli Serice Leel Adisor, or register the data yourself on the SLM machine. See Registering Warehouse Data on page 104 for details. Step 15. Additional Optional Configuration If you selected eent notification, you might need to perform a few additional configuration steps on the SLM machine. See Configuring for Eent Notification on page 107 for more information. In this sample installation you did not install the source warehouse pack for IBM Tioli Serice Leel Adisor. To install this warehouse pack on the Warehouse machine, see the procedures in Installing the Source Warehouse Pack for IBM Tioli Serice Leel Adisor on page 105. In this sample installation you did not install additional language support. To install language support for IBM Tioli Serice Leel Adisor, see the procedures in Installing Language Support on page 109. Also see Installing and Configuring Tioli Data Warehouse for information on installing language support for Tioli Data Warehouse on the Warehouse machine. Step 16. Restarting WebSphere Application Serer You need to stop and restart the WebSphere Application Serer on the SLM machine, but because you enabled WebSphere security, you are not allowed to stop the WebSphere Application Serer without proiding the authorized user name and password. You can stop and restart the WebSphere Application Serer by completing the following steps: 1. Open a command prompt window. 2. Naigate to C:\Program Files\WebSphere\Appserer\bin, the location where IBM WebSphere Application Serer was installed on the SLM machine. 3. Issue the following command: stopserer serer1 -username db2admin -password db2admin 4. Wait for the serer to be stopped. 5. Issue the following command to restart the serer: startserer serer1 Note: You do not need to specify the user name and password to start the serer. See Starting IBM WebSphere Application Serer on page 115 for alternatie start-up procedures. 6. Wait for the open for e-business message to be displayed. Accessing the SLM Administratie Console After the WebSphere Application Serer has restarted, access the SLM Administratie Console by opening your Web browser and naigating to the following Web site, specifying the fully qualified hostname for the SLM machine, where you installed the SLM Administration Serer: Appendix D. A Four-Machine Distributed Installation Example 171

190 Accessing SLM Reports If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. See Managing Serice Leel Agreements for information about using the SLM Administratie Console to create and manage your SLAs. You can also access the SLM Reports user interface by naigating to the following Web site, specifying the fully qualified hostname for the SLM machine, where you installed SLM Reports: If WebSphere security is enabled, you will hae to sign on with a alid user name (db2admin) and password (db2admin) to proceed. See SLM Reports for information about using the reporting interface of IBM Tioli Serice Leel Adisor to iew results of the ealuation and analysis of reported data by IBM Tioli Serice Leel Adisor. 172 IBM Tioli Serice Leel Adisor: Getting Started

191 Appendix E. Database Creation Tables The following table information is created when you successfully create the SLM Database (dyk_cat) and SLM Measurement Data Mart (dyk_dm) using the LaunchPad (see Creating Databases on page 52). Compare your table information in the table erification logs (the log files are located in your <TEMP> temporary directory (for example, C:\temp), and named dyk_cat_erify.log and dyk_dm_erify.log) to the following tables to erify that the databases were created successfully. If the table information does not match, check the database creation output log file for any errors that might hae occurred while performing any of the following tasks: Dropping of a database Database creation Database connection Tables Created in dyk_cat Database object creation, such as tables, indexes, and constraints After you identify and correct the error, run the Create Databases option from the LaunchPad again. Note: In the sample table for dyk_cat_dbinst, the table schema name is assumed to be the default alue, DB2ADMIN, but your table should contain the schema name as defined in the $DB2USER ariable. For comparison purposes with your table erification logs, look at the names in the TABNAME column, and also compare the total number of files created. TABNAME ACCOUNT ADJ_HISTORY ADJ_RESULT ADJ_VIOLATION AGREEMENT_VIOL ATTRIBUTE_FILTER ATTRIBUTE_SET BASE_ELMT_PROPS CONFIGURATION CONSUMER CONSUMER_REALM CUSTOM_BASE_METRIC CUSTOM_METRIC CUSTOM_METRIC_VIEW CUST_ORDER DYK_CAT_VERSION ELMT_MPROP_VIEW ELMT_MPRP_OFF_VIEW ELMT_PROP ELMT_PROP_VIEW HIST_METRIC_VALUE HIST_OFFRG_ELMT HIST_SCHEDULE HIST_SCHED_AUX HIST_SCHED_STATE HIST_SLA HIST_SLA_OC Copyright IBM Corp. 2002,

192 HIST_SLA_TIER HIST_SVC_OFFRG ID_GENERATOR METRIC METRIC_DEF METRIC_DEF_VIEW MONITORING_RESULT MSCHED_VIEW OFFERING_ORDER OFFRG_DEF_VIEW OFFRG_ELMT OFFRG_ELMT_LCLE OFFRG_ELMT_PROPS OFFRG_PROP OFFRG_PROP_SHOWSUB OFFRG_PROP_VIEW ORDER_DEF_VIEW ORDER_ELMT ORDER_ELMT_PROPS ORDER_PROP ORDER_PROP_VIEW OUTAGE PROP_DEF PROP_DEF_VIEW QUARTER_DATE REALM REP_METRIC RESOURCE RESULTVIEW SCHEDULE SCHEDULE_HIERARCHY SCHEDULE_LCLE SCHEDULE_MILESTONE SCHEDULE_PERIOD SCHEDULE_STATE SCHED_STATE_VIEW SCOPE_PROP_VIEW SCOPE_SE_VIEW SCP_PROP_SPEC_VIEW SD_TXN SO_LISTENER SPEC_DEF SVC_ELMT SVC_ELMT_MANAGER SVC_OFFRG SVC_OFFRG_LCLE SVC_OFFRG_VIEW SVC_SCOPE TABLE_LOCK TREND TRENDVIEW USER_INFO VIOLATIONVIEW ATTRDOM ATTRRUL ATTRTYP CDW_INFO COMP COMPATTR COMPPATH COMPRELN COMPTYP COMP_DEL COMP_MAP COMP_NM_MAP CUR_COMP CUR_COMP2 174 IBM Tioli Serice Leel Adisor: Getting Started

193 Tables Created in dyk_dm EFFECTED_COMPPATH EXTRACT_FILTER EXTRACT_LOG HISTORY HIST_COMP_MAP HIST_MSMTTYP_MAP JRE_TMZON MAP_DELTA MGRP MGRPMBR MGRPTYP MSMTRUL MSMTTYP MSMTTYP_MAP MSRC MUNIT MUNITCAT RELNRUL RELNTYP RENAME_CTRL TRANSLATED_TERM 115 record(s) selected. DB20000I The SQL DISCONNECT command completed successfully. TABNAME COMP_MAP DATA_EXP DYK_DM_VERSION ENABLED_APPS EVALUATOR_TABLE EXP_LOG EXP_LOG_LT EXTRACT_LOG EXT_AVL EXT_MMA EXT_PCH EXT_TOT HISTORY MSMTTYP_MAP MSMT_AVL MSMT_MMA MSMT_PCH MSMT_TOT 18 record(s) selected. DB20000I The SQL DISCONNECT command completed successfully. Appendix E. Database Creation Tables 175

194 176 IBM Tioli Serice Leel Adisor: Getting Started

195 Appendix F. Manually Creating ODBC Data Sources Editing the Script Files IBM Tioli Serice Leel Adisor proides scripts to automatically create ODBC data sources for the SLM Database and the SLM Measurement Data Mart on Windows and UNIX operating systems (see Configuring ODBC Data Sources on page 88). If you did not use the defaults when you created the databases, or if you want to create ODBC data sources using a different alias, you can edit these script files to change these parameters before running the scripts. If you do not want to use the automated scripts to create ODBC data sources, you can create them manually by using one of two methods: Using the Data Sources administratie tool on the Windows Control Panel Issuing DB2 commands from a command prompt If you need to create ODBC data sources for remote SLM databases on a z/os operating system, see Creating ODBC Data Sources for Remote SLM Databases on z/os Operating Systems on page 180. To edit the script files to create ODBC data sources with parameters other than the default alues, complete the following steps: 1. Copy the \database\scripts\w32-ix86 directory from the IBM Tioli Serice Leel Adisor product CD to a local or system drie. 2. Locate these script files at the temporary location. 3. Use your preferred text editor to make the appropriate modifications to the parameters in the script files. 4. Sae the edited files in your temporary location. 5. Open a DB2 command prompt by clicking Start > Run and issuing the command: db2cmd. 6. At the DB2 command prompt, naigate to your temporary location where the edited script files are located. 7. Issue the following command to create the ODBC data source for the SLM Database: dyk_cat_odbc.bat <fully_qualified_machine_name> In this command, <fully_qualified_machine name> is the fully qualified machine name of the local or remote DB2 serer where the database is located. For example: dyk_cat_odbc.bat UserABC.raleigh.ibm.com 8. Similarly, issue the following command to create the ODBC data source for the SLM Measurement Data Mart: dyk_dm_odbc.bat <fully_qualified_machine_name> Using the Windows Control Panel Administratie Tool If you want to configure data sources using the Data Sources administratie tool on the Windows Control Panel, complete the following steps: Copyright IBM Corp. 2002,

196 1. Click Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC). 2. Select the System DSN tab. 3. Click Add. 4. From the list of driers, select IBM DB2 ODBC Drier and click Finish. 5. Type the name of the data source that you are defining. Table 14 shows the default data source names for the Tioli Data Warehouse database and the SLM databases. Note: The installation procedure for Tioli Data Warehouse should hae already configured the ODBC data source for Tioli Data Warehouse. It is included here as another example. Table 14. Databases and their data source and alias names Database Data Source Name Data Source Alias Tioli Data Warehouse twh_cdw TWH_CDW SLM Database dyk_cat DYK_CAT SLM Measurement Data Mart dyk_dm DYK_DM Using DB2 Commands 6. If the actual database is on the same machine as the machine on which you are configuring the data source, or if it was defined preiously for a different data source, then select the alias from the drop-down list and click OK. Use the same name for the alias as the data source name, as shown in Table If the database resides on a machine other than the machine on which you are defining the ODBC data source, and is not in the drop-down list, complete the following steps: a. Type the data source name and click Add to launch the Add Database wizard. b. Select Manually configure a connection to a database and click Next. c. Select TCP/IP as the protocol and click Next. d. Enter the fully qualified hostname where the database resides and enter the port number (typically for DB2 Uniersal Database), and click Next. e. Enter the database name (the alias is automatically filled in) and click Finish. The data source is defined. Repeat this procedure for each data source (see Table 14) that you are defining. To create ODBC data sources manually using DB2 commands, complete the following steps: 1. Open a DB2 Command Line Processor window: For Windows systems, click Start > Programs > IBM DB2 > Command Line Processor. For UNIX, source the db2profile. 2. Issue the following command to catalog the node where the database resides: db2 catalog tcpip node <node> remote <serer> serer In this command, <node> is the node name for the database, such as CAT_ODBC for the SLM Database, or DM_ODBC for the SLM Measurement 178 IBM Tioli Serice Leel Adisor: Getting Started

197 Data Mart, and <serer> is the fully qualified machine name of the system where the database is located, for example, mymachine.raleigh.ibm.com. After this command completes successfully you should receie a DB20000I completion message. 3. Issue the following command to test the connection by attaching to the node: db2 attach to <node> user <userid> using <password> In this command, <node> is the node name for the database, <userid> is the DB2 user ID for the database (for example, db2admin), and <password> is the DB2 password that is associated with <userid>. You should receie attachment information for the database instance, such as the instance serer, authorization ID, and local instance alias. 4. Issue the following command to detach from the node: db2 detach 5. Issue the following command to catalog the database: db2 catalog database <database> at node <node> authentication serer In this command, <database> is the default name of the database (for example, DYK_CAT for the SLM Database, and DYK_DM for the SLM Measurement Data Mart), and <node> is the node name for the database. After this command completes successfully, you should receie a DB20000I completion message. 6. Issue the following command to test the connection to the data mart: connect to <database> user <userid> using <password> In this command, <database> is the default name of the database, <userid> is the DB2 user ID for the database, and <password> is the DB2 password that is associated with <userid>. After this command completes successfully, you should receie a DB20000I completion message. 7. Issue the following command to catalog the ODBC data source: catalog system odbc data source <database> In this command, <database> is the default name of the database. After this command completes successfully, you should receie a DB20000I completion message. To create an ODBC data source for the SLM Database (DYK_CAT), located on the system named mymachine.raleigh.ibm.com, using default port number 50000, the node name CAT_ODBC, and the DB2 Uniersal Database user ID and password of db2admin, issue the following commands at a DB2 command prompt: db2 catalog tcpip node CAT_ODBC remote mymachine.raleigh.ibm.com serer db2 attach to CAT_ODBC user db2admin using db2admin db2 detach db2 catalog database DYK_CAT at node CAT_ODBC authentication serer connect to DYK_CAT user db2admin using db2admin catalog system odbc data source DYK_CAT To create an ODBC data source for the SLM Measurement Data Mart (DYK_DM), located on the system named mymachine.raleigh.ibm.com, using default port number 50000, the node name DM_ODBC, and the DB2 Uniersal Database user ID and password of db2admin, issue the following commands at a DB2 command prompt: db2 catalog tcpip node DM_ODBC remote mymachine.raleigh.ibm.com serer db2 attach to DM_ODBC user db2admin using db2admin db2 detach db2 catalog database DYK_DM at node DM_ODBC authentication serer connect to DYK_DM user db2admin using db2admin Appendix F. Manually Creating ODBC Data Sources 179

198 catalog system odbc data source DYK_DM Creating ODBC Data Sources for Remote SLM Databases on z/os Operating Systems To create ODBC data sources when the remote SLM database is located on a z/os operating system, complete the following steps: 1. Click Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC). 2. Select the System DSN tab. 3. Click Add. 4. From the list of driers, select IBM DB2 ODBC Drier and click Finish. 5. Enter the name of the data source that you are defining, typically DYK_CAT for the SLM Database, or DYK_DM for the SLM Measurement Data Mart (see Table 14 on page 178) and click Add to start the Add Database Wizard. 6. On the Source tab of the Add Database Wizard screen, select Manually configure a connection to a database and then click Next to continue. 7. On the Protocol tab, complete the following steps: Click TCP/IP. Click The database physically resides on a host or AS/400 system. (This choice appears after you choose TCP/IP in the preious step). Click Next to continue. 8. On the TCP/IP tab, complete the following steps: Enter the hostname (or IP address) of the z/os operating system host. Enter the port number (the z/os TCPPORT alue that appears in the DSNL004I message on the remote host when DDF is started). Click Next. 9. On the Database tab, complete the following steps: Type the DB2 Uniersal Database for OS/390 LOCATION alue for Database name (the LOCATION alue appears on the DSNL004I message on the remote host when DDF is started). Enter the database name in the Database alias field. Click Next. 10. On the ODBC tab, click Next. 11. On the Node Options tab, complete the following steps: Verify that the default setting, Configure node options (Optional) is selected. Verify that the Operating system field contains the default alue MVS /ESA,OS/390. Click Next. 12. On the Security Options tab, complete the following steps: Click Configure security options (Optional). Verify that the default setting, Host or AS/400 authentication (DCS) is selected. Click Next. 13. On the Host or AS/400 Options tab, complete the following steps: Click Configure host or AS/400 options (Optional). 180 IBM Tioli Serice Leel Adisor: Getting Started

199 Verify that the default setting, Disconnect if client generates an interrupt (INTERRUPT_ENABLED) is selected. Click Finish. 14. A confirmation message is displayed, indicating that the ODBC datasource was added. Click Close. 15. Return to the ODBC Source Administrator window and select DYK_CAT or DYK_DM, then click Configure. 16. Click Yes. Verifying ODBC Configuration 17. Type the user ID and password to access the database and click OK. 18. You should receie a confirmation message that the connect completed successfully. Click OK. 19. Add the user ID and password to the CLI/ODBC Settings and click OK. 20. Click OK to close the ODBC Source Administrator window. Verify that these ODBC data sources were successfully configured by clicking Start > Settings > Control Panel > Administratie Tools > Data Sources (ODBC), and then clicking the System DSN tab. The resulting list of ODBC data sources that is displayed should include entries for the alias names that you specified (if different from the default alues of DYK_CAT and DYK_DM). Appendix F. Manually Creating ODBC Data Sources 181

200 182 IBM Tioli Serice Leel Adisor: Getting Started

201 Appendix G. Installation Hints and Tips This appendix contains supplementary information about tasks that are done by users installing and configuring IBM Tioli Serice Leel Adisor and its prerequisite software. It contains the following topics: Starting a DB2 Command Prompt on Windows Systems Sourcing the db2profile on UNIX Verifying the Root User Authority in a DB2 enironment on page 184 Ensuring User Rights Authority for Database Creation on page 184 Ensuring fully qualified hostnames on page 186 Mounting the CD-ROM on UNIX Systems on page 188 Checking the ersion of an existing DB2 installation on page 188 Verifying your DB2 Uniersal Database Installation on page 189 Updating the JDBC Leel for DB2 on page 189 Configuring the Database Manager to use Extended Shared Memory on page 190 Installing Tioli Enterprise Data Warehouse 1.1 Fix Pack 3 on page 191 Resoling port conflicts on page 192 Creating Distributed SLM Databases Manually on page 192 Connecting a DB2 7.2 Database with a DB2 8.1 Client on page 196 Performing a Silent Installation of IBM Tioli Serice Leel Adisor on page 197 Starting a DB2 Command Prompt Before you can issue DB2 commands in a Windows or UNIX enironment, you must first set up the DB2 command session enironment. For Windows systems, issue the db2cmd command to begin a DB2 command prompt. For UNIX systems, source the db2profile. There are many references to these setup procedures throughout the documentation. Starting a DB2 Command Prompt on Windows Systems To start a DB2 command prompt on Windows systems, complete the following steps: 1. From your desktop, click Start > Run. 2. In the Run window that is displayed, type the command: db2cmd Sourcing the db2profile on UNIX Before you can issue DB2 commands on UNIX systems, you must first set up the enironment by sourcing the db2profile. To set up your enironment for issuing DB2 commands, complete the following steps: 1. While logged in as root, naigate to the DB2 instance owner directory <DB2_instance_dir>/sqllib 2. Issue one of the following commands: For bash, Bourne, or Korn shells: Copyright IBM Corp. 2002,

202 . db2profile For C shell: source db2cshrc Verifying the Root User Authority in a DB2 enironment On UNIX systems, erify that the root user has the proper authority (SYSADM) in DB2. To erify that the root user belongs to the proper group, complete the following steps: 1. Source the db2profile (see Sourcing the db2profile on UNIX on page 183). 2. Issue the following command to see which system group name is defined as the SYSADM control group: db2 get dbm cfg grep SYSADM_GROUP The output of the preious command should be similar to the following example: SYSADM group name(sysadm_group) = DB2GROUP 3. Record the name of the SYSADM_GROUP (DB2GROUP in the preious example), for reference in the following steps. 4. Issue the following command to erify that root is a member of that group: groups root 5. If root is not a member of that group, add the root user to the group listed in step 3 using the user administration tools for your operating system. If the SYSADM_GROUP field is blank: Use the user administration tools for your operating system to create a system group that includes both the instance owner and the root user. Log in as the DB2 instance owner and add this group to the database manager configuration by issuing the following command: db2 update dbm cfg using SYSADM_GROUP <new_group_name> In this command, <new_group_name> is the name of the group that you created to contain the instance owner and the root user. Ensuring User Rights Authority for Database Creation When you create DB2 databases on Windows systems, if you specify a user name that already exists, the user name and password that you use must hae sufficient authority. The user name and password must hae the following characteristics: It must be defined locally. On Windows systems, create a new user by completing the following steps: 1. Click Start > Settings > Control Panel > Administratie Tools > Computer Management. 2. Expand the System Tools branch in the tree iew, and then expand the Local Users and Groups branch. Right-click on Users and click New User. 3. On the New User window that is displayed, type the user name, password, and other information, and click Create. The new user name is added to the list of users. It must belong to the Administrators Group. On Windows systems, add a new user to the Administrators group by completing the following steps: 1. Click Start > Settings > Control Panel > Administratie Tools > Computer Management. 184 IBM Tioli Serice Leel Adisor: Getting Started

203 2. Expand the System Tools branch in the tree iew, and then expand the Local Users and Groups branch. Click Groups. 3. From the list of group names that is displayed, right-click on Administrators and click Add to Group from the window that is displayed. 4. On the Administrators Properties window that is displayed, click Add. 5. In the Select Users or Groups window that is displayed, scroll down the list and highlight the user name, and click Add, then click OK. 6. You are returned to the Administrators Properties window, which should now show the user name added to the Members list. Click OK to return to the list of group names. It must hae, among its arious user rights, the following adanced user rights: Act as part of the operating system Create a token object Increase quotas Replace a process leel token On Windows systems, check and modify user rights for the specified user name by completing the following steps: 1. Click Start > Settings > Control Panel > Administratie Tools > Local Security Policy. 2. Expand the Local Policies branch in the tree iew, and click User Rights Assignment. 3. A list of user rights is displayed. Locate Act as part of the operating system in the list. Under the Local Setting column, the users or user groups to which this user right has been assigned are listed. Verify that the Administrators group is listed as being assigned to this user right. If the group is not assigned to this user right, complete the following steps: a. Double-click the user right, or right-click on the user right and select Security from the window that is displayed. b. On the Local Security Policy Setting window that is displayed, click Add. c. In the Select Users or Groups window that is displayed, scroll down the list and highlight the Administrators group, click Add, then click OK. d. You are returned to the Local Security Policy Setting window, which should now show the Administrators group added to the Assigned To list. Click OK to return to the list of user rights. e. Select each of the other user rights as needed and repeat these steps to erify or assign the user right to the Administrators group. If you specify a user name that does not already exist on the system, DB2 Uniersal Database creates the user for you with the correct user rights automatically. A typical DB2 user name and password might be created as follows, with both the user name and the password identical for simplicity (for security reasons you might choose to create more random and secure names and passwords): User name: db2admin Password: db2admin User names must follow the DB2 naming conentions, which are summarized in Appendix B of Installing and Configuring Tioli Data Warehouse. Appendix G. Installation Hints and Tips 185

204 Remember the DB2 user name and password that you create: You need it to install Tioli Data Warehouse and IBM Tioli Serice Leel Adisor components on this system. For a distributed installation, you do not hae to use the same user name and password for each DB2 installation. Ensuring fully qualified hostnames Your operating system must be configured to proide IBM Tioli Serice Leel Adisor with a fully qualified computer name, or hostname, instead of a short name. This is especially important in enironments with many different operating systems. To ensure that a system is configured to proide a fully qualified hostname, complete the steps in the following sections. On AIX systems The default domain name search order is as follows: 1. Domain Name System (DNS) serer 2. Network Information Serice (NIS) 3. Local /etc/hosts file If the /etc/resol.conf file does not exist, the /etc/hosts file is used. If only the /etc/hosts file is used, the fully qualified computer name must be the first one that is listed after the IP address. Verify that the /etc/resol.conf file exists and contains the appropriate information, such as: domain mydiision.mycompany.com nameserer If NIS is installed, the /etc/irs.conf file oerrides the system default. It contains the following information: hosts = bind, local If the NSORDER enironment ariable is set, it oerrides all of the preceding files. It contains the following information: export NSORDER=bind, local On Linux systems Verify that the /etc/resol.conf file exists and contains the appropriate information, such as: domain mydiision.mycompany.com nameserer A short name is used if the /etc/nsswitch.conf file contains a line that begins as follows and if the /etc/hosts file contains the short name for the computer: hosts: files To correct this, follow these steps: 1. Change the line in the /etc/nsswitch.conf file (if it exists) to: hosts: dns nis files 2. Stop the network serice. 3. Restart the network serice. 186 IBM Tioli Serice Leel Adisor: Getting Started

205 On Solaris systems Verify that the /etc/resol.conf file exists and contains the appropriate information, such as: domain mydiision.mycompany.com nameserer A short name is used if the /etc/nsswitch.conf file contains a line that begins as follows and if the /etc/hosts file contains the short name for the computer: hosts: files To correct this, follow these steps: 1. Change the line in the /etc/nsswitch.conf file to: hosts: dns nis files 2. Enter the following command to stop the inet serice: /etc/init.d/inetsc stop 3. Enter the following command to restart the inet serice: /etc/init.d/inetsc start On HP systems Verify that the /etc/resol.conf file exists and contains the appropriate information, such as: search mydiision.mycompany.com nameserer The domain keyword should be used only if you do not want other domains to be searched. Using the domain keyword might cause resolution of partially qualified hostnames to fail. Verify that the appropriate /etc/nsswitch.conf file exists and contains a line that begins as follows: hosts: dns [NOTFOUND=continue] nis files Stop and restart the network serice. On Microsoft Windows NT systems To erify that a primary domain name system (DNS) suffix is set, follow these steps: 1. From the Windows task bar, click Start > Settings > Control Panel. 2. In the Control Panel window, double-click Network. 3. Click the Protocols tab. 4. Select the TCP/IP protocol and then click Properties. 5. Click the DNS tab. 6. Ensure that the field Domain contains a domain suffix. If it does not, type the suffix, click OK, and restart the computer when prompted. On Windows 2000 systems To erify that a primary domain name system (DNS) suffix is set, follow these steps: 1. On the desktop, right-click My Computer. 2. Click Properties. Appendix G. Installation Hints and Tips 187

206 3. Click the Network Identification tab. 4. Ensure that the field Full Computer Name contains a fully qualified domain name. If it does not, follow these steps: a. Click Properties. b. Click More. c. In the field Primary DNS suffix for this computer, type the primary DNS suffix, and restart the computer when prompted. Mounting the CD-ROM on UNIX Systems Mount the CD-ROM deice by inserting the product CD and completing the following steps: 1. Issue one of the following commands appropriate to your operating system: For AIX systems, issue the following command, where <mount_dir> is the mount directory: mount -r cdrfs /de/cd0 <mount_dir> For Solaris systems, the CD is automatically mounted on /cdrom/cdrom0. For Linux systems, issue the following command: mount /mnt/cdrom 2. Change to the mounting directory. Refer to Installing and Configuring Tioli Data Warehouse for additional details on mounting the CD-ROM for supported UNIX systems. Checking the ersion of an existing DB2 installation To use an existing ersion of DB2 client or serer, erify that it is at one of the supported leels as specified in the Release Notes. To determine the ersion of DB2 Uniersal Database that you hae installed, complete the following steps: 1. Start a DB2 command prompt. 2. At the command prompt, issue the following command: db2leel The db2leel command returns a block of information that includes the leel identifier and an informational token. For example, the informational token for the base DB2 product as well as DB2 with arious fix pack ersions are shown in Table 15. Table 15. DB2 ersion information for base DB2 and fix packs. Informational Token DB2 Version DB2 7.1.x.40 Base DB2 7.2 DB2 7.1.x.51 DB2 7.2 with fix pack 4 DB2 7.1.x.55 DB2 7.2 with fix pack 5 DB2 7.1.x.60 DB2 7.2 with fix pack 6 DB2 7.1.x.nn (where nn = 65, 66, 67, or 68) DB2 7.2 with fix pack 7 DB2 7.1.x.72 DB2 7.2 with fix pack 8 DB2 7.1.x.75 DB2 7.1.x.88 DB2 7.2 with fix pack 8 plus an additional fix DB2 7.2 with fix pack 10a 188 IBM Tioli Serice Leel Adisor: Getting Started

207 Table 15. DB2 ersion information for base DB2 and fix packs. (continued) Informational Token DB2 8.1.x.40 DB2 Version DB2 8.1 with fix pack 4a If you hae a ersion of DB2 Uniersal Database prior to 7.1.x.75, you must upgrade it at least to this leel before continuing. Refer to Installing and Configuring Tioli Data Warehouse for information on upgrading your existing DB2 ersion to at least 7.1.x.75. For more information on obtaining this ersion of DB2 Uniersal Database, see Appendix B in Installing and Configuring Tioli Data Warehouse. Verifying your DB2 Uniersal Database Installation After installing DB2 Uniersal Database, perform a connection test by completing the following steps (either from a DB2 command prompt on Windows systems or from a UNIX enironment where the db2profile has been sourced): 1. Issue the following command to list local databases: db2 list database directory 2. In most cases, the command lists at least one database, een in new installations. If the command does not list any databases, create a temporary database by issuing the following command, where <name> is a database name of your choosing: db2 create database <name> 3. Issue the following command to test for a local connection, where <name> is your database name, and <user_name> and <password> are the DB2 user name and password that you specified during DB2 installation: db2 connect to <name> user <user_name> using <password> If this command is successful, DB2 is installed and ready for remote connections. If you experience difficulty, refer to the DB2 documentation for troubleshooting information. Updating the JDBC Leel for DB2 By default, the DB2 database management system serer uses the JDBC 1.1 driers for JDBC applications. IBM Tioli Serice Leel Adisor requires DB2 Uniersal Database to use the JDBC 2.0 driers. If the DB2 serer uses different leels of the JDBC drier than the clients, unpredictable results occur and IBM Tioli Serice Leel Adisor might encounter database errors. IBM Tioli Serice Leel Adisor automatically updates the JDBC leel to JDBC 2.0 during the installation procedure. For those machines in a distributed installation that hae Tioli Enterprise Data Warehouse 1.1 components but not IBM Tioli Serice Leel Adisor in a DB2 7 enironment, you might need to manually update the JDBC leel to 2.0. Verifying the JDBC Leel To determine if you are running DB2 Uniersal Database at the required JDBC 2.0 leel, complete the following steps, depending on your operating system: For Windows systems, check the size of the db2jaa.zip file, located in the <DB2_DIR>/jaa directory, where <DB2_DIR> is the location where DB2 Uniersal Database is installed. If the size is approximately 1347 KB, then the JDBC leel is 2.0. If the size of the db2jaa.zip file is approximately 1132 KB, Appendix G. Installation Hints and Tips 189

208 then the JDBC leel is 1.0 and you must run the usejdbc2 command to upgrade to JDBC 2.0. See Updating the JDBC Leel Manually. For UNIX, log in as the instance owner and source the db2profile script, and check the CLASSPATH enironment ariable by issuing the following command: echo $CLASSPATH If the CLASSPATH includes the string <DB2_Instance_Dir>/sqllib/jaa12/db2jaa.zip, where <DB2_Instance_Dir> is the home of the instance of the SLM databases, then the JDBC leel is properly set to 2.0. If the CLASSPATH includes the string <DB2_Instance_Dir>/sqllib/jaa/db2jaa.zip, then the JDBC leel is 1.0, and you must run the usejdbc2 command to upgrade to JDBC 2.0. See Updating the JDBC Leel Manually.. Updating the JDBC Leel Manually If the JDBC leel was not properly updated, manually update the JDBC leel by completing the following steps, depending on your operating system: For Windows systems, naigate to the <DB2_DIR>/jaa12 directory, where <DB2_DIR> is the location where DB2 Uniersal Database is installed, and issue the following command: usejdbc2 This command copies the appropriate ersion of db2jaa.zip into the <DB2_DIR>/jaa directory. For UNIX systems, add the following line to the <DB2_Instance_Dir>/sqllib/userprofile script, where <DB2_Instance_Dir> is the home of the DB2 instance where the SLM databases are located:. <DB2_Instance_Dir>/sqllib/jaa12/usejdbc2 If the userprofile script does not exist, create it and add the aboe line to the script file. Verify that the JDBC leel was correctly updated by following the instructions in Verifying the JDBC Leel on page 189. Configuring the Database Manager to use Extended Shared Memory To aoid problems with DB2 Uniersal Database exhausting its shared memory segments on AIX systems, you should configure the database manager to use extended shared memory. This is especially important if the SLM databases reside on the same machine with any of the installation options of IBM Tioli Serice Leel Adisor (SLM Serer, SLM Task Driers, or SLM Reports). To enable this support for extended shared memory, complete the following steps: 1. Add EXTSHM=ON to the /etc/enironment file. 2. From a DB2 command prompt, run the following command: db2set DB2ENVLIST=EXTSHM 3. Add the following lines to sqllib/userprofile: EXTSHM=ON export EXTSHM 4. Reboot the machine to put the changes into effect. For more information, see the DB2 documentation for configuration of shared memory, and consult the WebSphere online documentation for configuring for extended shared memory. 190 IBM Tioli Serice Leel Adisor: Getting Started

209 Installing Tioli Enterprise Data Warehouse 1.1 Fix Pack 3 This procedure is only used if you hae a current installation of Tioli Enterprise Data Warehouse 1.1 in your enterprise and do not want to upgrade to ersion 1.2. If you keep ersion 1.1, it must be upgraded to at least the Fix Pack 3 leel to operate with IBM Tioli Serice Leel Adisor. To obtain the fix pack, naigate to the Tioli Data Warehouse support Web site: /TioliDataWarehouse.html Under the Self help section, click Search all Downloads, and then scroll down the displayed list of aailable packages and select Tioli Enterprise Data Warehouse 1.1 Fix Pack 3 (1.1-TDW-FP03) link. Scroll to the bottom of the new window that is displayed and sae the 1.1-TDW-FP03 package to a temporary location on your machine, such as C:\1.1-TDW-FP03. Before installing the fix pack, be sure to read the README file that comes with the fix pack, for information on known defects, problems and work-arounds that you might need to consider. To install the fix pack, complete the following general steps (these are described in further detail in the README. If you hae any problems, consult the README for more information): 1. Naigate to C:\1.1-TDW-FP03 and unpack the file using an appropriate decompression utility. 2. Naigate to where you unpacked the file and find the \1.1-TDW-FP03 directory. Open this folder and run setup.bat. Note: This does not install the fix pack at this time, but merely copies a configuration file, twh_core_patcher.cfg to your %TEMP% directory. 3. Naigate to your %TEMP% directory and edit the twh_core_patcher.cfg configuration file using your preferred text editor. Edit the file at the following lines: PS_HOME=C:/PS C:/PS is the default directory where you installed Tioli Presentation Serices during the installation of Tioli Enterprise Data Warehouse 1.1. Be sure to use a forward slash character (/) in this path specification, otherwise the installation might fail. DB2PASS=<db2password> COPT_CTRL_DB2PASS=<db2password> COPT_CDW_DB2PASS=<db2password> COPT_MART_DB2PASS=<db2password> 4. Sae and close this configuration file. 5. From the \1.1-TDW-FP03 directory, run the setup.bat script a second time to perform the installation of the fix pack. 6. The installation should complete after a few minutes. Appendix G. Installation Hints and Tips 191

210 Resoling port conflicts You might need to resole port conflicts between IBM WebSphere Application Serer and Tioli Presentation Serices if you are planning the following configuration: You are installing into an existing enironment that is using Tioli Enterprise Data Warehouse ersion 1.1 (which uses Tioli Presentation Serices). You do not plan to upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2 (which does not use Tioli Presentation Serices) or you do upgrade to ersion 1.2, but Tioli Presentation Serices is still in use by other applications in your enironment. You plan to install IBM WebSphere Applications Serer to support either the SLM Administration Serer or SLM Reports components on the same machine where Tioli Presentation Serices is installed. Both Tioli Presentation Serices and IBM WebSphere Application Serer install a copy of IBM HTTP Serer, and use the same default port numbers for IBM HTTP Serer (80) and IBM HTTP Administration (8008). When you install IBM WebSphere Application Serer, change the port numbers from these default alues to unused alues, for example: IBM HTTP Serer: 81 IBM HTTP Administration: 8009 You can find out which ports are already in use on your machine by issuing the netstat -a or netstat -an command. If you need to modify the port settings for IBM WebSphere Application SererWebSphere after installing, you can edit the following files: IBMHttpSerer/conf/httpd.conf, change port 80 to 81 or another unused port number. IBMHttpSerer/conf/admin.conf, change port 8008 to 8009 or another unused port number. Creating Distributed SLM Databases Manually Usually you use the Create Databases function in the LaunchPad for IBM Tioli Serice Leel Adisor to create the SLM Database (DYK_CAT) and the SLM Measurement Data Mart (DYK_DM) on distributed systems. Howeer, if you hae problems or prefer to create these databases manually, you can run the database scripts, (dyk_cat_dbinst or dyk_dm_dbinst), on the machine where you want the databases installed. These scripts are alid only for creating databases on distributed operating systems. You cannot use these scripts to create remote databases on z/os operating systems. For databases on z/os operating systems, you must use the Create Databases function on the LaunchPad. Creating SLM Databases on Windows Systems To create the SLM databases on Windows systems, complete the following steps: 1. Catalog the databases on the machine where the databases are installed. 2. Insert the IBM Tioli Serice Leel Adisor installation CD in the CD ROM drie of the machine. 3. Start a DB2 command prompt window. 192 IBM Tioli Serice Leel Adisor: Getting Started

211 4. Naigate to <CD_DRIVE>:\database\scripts\w32-ix86, where <CD_DRIVE> is the drie letter of your CD ROM. 5. Run the dyk_cat_dbinst script to create the SLM Database, as follows: dyk_cat_dbinst <database name> <user ID> <password> <territory> <local> <drop> In this command, the arguments are specified as follows: <database name> The database name that was cataloged, such as DYK_CAT. You can change the name of the database, howeer keep this default database name unless it presents a problem or conflict. This database name is used in a number of locations, and you must find and change each instance during installation and configuration. If you select a different name, bear in mind that database names in DB2 Uniersal Database are limited to 8 characters. If you do change this name, note the new name and keep it handy for when you install and configure IBM Tioli Serice Leel Adisor. <user ID> The DB2 user ID <password> The DB2 password for the specified DB2 user ID <territory> The DB2 territory. This should always be specified as us <local> If the database is being created locally (on this machine), this alue should be yes. If the database is being created remotely (on another machine in your enterprise), this alue should be no. <drop> If the database already exists and you want the script to drop and then recreate it, this alue should be yes. If you do not want to drop the database, this alue should be no. For example, to create the SLM Database named DYK_CAT locally, dropping any existing database first, run the script and pass the following parameters: dyk_cat_dbinst dyk_cat db2admin db2admin us yes yes 6. Similarly, run the dyk_dm_dbinst script to create the SLM Measurement Data Mart, as follows: dyk_dm_dbinst <database name> <user ID> <password> <territory> <local> <drop> For example, to create the SLM Measurement Data Mart named DYK_DM remotely (assume it has already been cataloged on the remote machine), dropping any existing database first, run the script, passing the parameters as follows: dyk_dm_dbinst dyk_dm db2admin db2admin us no yes Creating SLM Databases on UNIX Systems To create the SLM databases on UNIX systems, complete the following steps: 1. Catalog the databases on the machine where the databases will be installed. 2. Insert the IBM Tioli Serice Leel Adisor installation CD in the CD ROM drie of the machine. 3. Source the DB2 profile. Appendix G. Installation Hints and Tips 193

212 4. Naigate to <CD_DRIVE>:/database/scripts/unix, where <CD_DRIVE> is the drie letter of your CD ROM. 5. Run the dyk_cat_dbinst.sh script to create the SLM Database, as follows: dyk_cat_dbinst <database name> <user ID> <password> <territory> <local> <drop> In this command, the arguments are specified as follows: <database name> The database name that was cataloged, such as DYK_CAT. You can change the name of the database, howeer keep this default database name unless it presents a problem or conflict. This database name is used in a number of locations, and you must find and change each instance during installation and configuration. If you select a different name, bear in mind that database names in DB2 Uniersal Database are limited to 8 characters. If you do change this name, note the new name and keep it handy for when you install and configure IBM Tioli Serice Leel Adisor. <user ID> The DB2 user ID <password> The DB2 password for the specified DB2 user ID <territory> The DB2 territory. This should always be specified as us. <local> If the database is being created locally (on this machine), this alue should be yes. If the database is being created remotely (on another machine in your enterprise), this alue should be no. <drop> If the database already exists and you want the script to drop and then recreate it, this alue should be yes. If you do not want to drop the database, this alue should be no. For example, to create the SLM Database named DYK_CAT locally, dropping any existing database first, run the script, passing the parameters as follows: dyk_cat_dbinst.sh dyk_cat db2admin db2admin us yes yes 6. Similarly, run the dyk_dm_dbinst.sh script to create the SLM Measurement Data Mart, as follows: dyk_dm_dbinst.sh <database name> <user ID> <password> <territory> <local> <drop> For example, to create the SLM Measurement Data Mart named DYK_DM remotely (assume it has already been cataloged on the remote machine), dropping any existing database first, run the script, passing the parameters as follows: dyk_dm_dbinst.sh dyk_dm db2admin db2admin us no yes Checking Database Creation Log Files The database creation scripts create separate log files to capture all of the database creation messages and a list of tables that are created for each database. You can check these log files and table lists after the scripts complete processing, to erify that the databases were created successfully. If you are running these scripts on a Windows operating system, the default location of these log files is in the system temporary folder (see the %TEMP% enironment ariable on Windows systems, or 194 IBM Tioli Serice Leel Adisor: Getting Started

213 the /tmp ariable on UNIX systems). To change the location of the log files, edit the LOGFILE_NAME and VER_LOGFILE_NAME parameters located at the top of the Windows database creation scripts. On UNIX systems, the interactie scripts prompt you for the log directory, and if the log directory does not already exist, the script offers to create it for you before continuing. If you choose to hae the scripts create the log directory for you, the DB2 instance owner must hae sufficient file permissions to create the directory in the location. The database creation log files dyk_cat_dbinst_err.log or dyk_dm_dbinst_err.log might contain errors indicating that the database could not be created. These log files are located in the temporary directory for your system. Modifying Configuration Parameters After Creating Databases When you run the database creation scripts, certain configuration parameters are set to default alues by using DB2 update commands. You might want to modify some of these configuration parameters to tailor these databases to your enironment. Table 16 identifies the arious database parameters, along with their default alues for each SLM database, that are set by the script files. These configuration parameters affect the operation of both the database and the instance to which it belongs. These alues were chosen for the databases to run efficiently in a default IBM Tioli Serice Leel Adisor enironment. To change any of these alues, contact your Database Administrator for alues appropriate to your enironment. Table 16. SLM Database Configuration Parameters Parameter name logfilsiz logprimary logsecond applheapsz Default alue 2500 for SLM Database 2500 for SLM Measurement Data Mart 3 for SLM Database 10 for SLM Measurement Data Mart 2 for SLM Database 40 for SLM Measurement Data Mart 2048 for SLM Database 4096 for SLM Measurement Data Mart Configuration type Database Database Database Database Parameter description The size of the primary and secondary log files, which determines the number of log records that can be written before a new log file is required. The number of primary logs used for recoery. These logs are allocated when the database is created. The number of secondary log files used for database recoery. These logs are only allocated as needed when space in the primary log files runs out. The amount of priate memory aailable to be used for an application agent or subagent. Appendix G. Installation Hints and Tips 195

214 Table 16. SLM Database Configuration Parameters (continued) Parameter name Default alue Configuration type Parameter description maxappls 200 for SLM Database 200 for SLM Measurement Data Mart Database The maximum number of concurrent applications allowed to connect to the database. maxagents 500 for SLM Database 500 for SLM Measurement Data Mart Instance The maximum number of database manager agents aailable for applications. numdb 10 for SLM Database Instance The maximum number of concurrently actie databases. 10 for SLM Measurement Data Mart If you examine the database creation script files, you see the DB2 update commands that are issued to set these parameters. You can issue your own commands to change these settings. For more information on these and other database configuration parameters, refer to IBM DB2 Uniersal Database Administration Guide: Performance, Chapter 13, Configuring DB2. Connecting a DB2 7.2 Database with a DB2 8.1 Client If you hae a distributed installation of IBM Tioli Serice Leel Adisor, it is possible for you to hae one or both of the SLM databases on a DB2 serer machine at a supported 7.2 ersion (for example, 7.1.x.75) communicating with the SLM Serer on a DB2 client machine at a supported 8.1 ersion (this ersion of IBM DB2 is supported on IBM Tioli Serice Leel Adisor 2.1 but not on Tioli Data Warehouse 1.2. See the Release Notes for more information on supported ersions of DB2 Uniersal Database). To connect a DB2 7.2 database to a DB2 8.1 client, complete the following steps: 1. On the DB2 7.2 serer machine, create or catalog the DYK_CAT or DYK_DM database. 2. On the DB2 7.2 serer machine, open a DB2 command line prompt, naigate to <DB2_Dir>\bin (where <DB2_Dir> is the directory where DB2 Uniersal Database was installed, for example, C:\Program Files\SQLLIB on Windows systems, or /opt/ibm/db2/v7.1 on UNIX systems) and issue the following command: db2upd7.exe -d <database> -u <db2_user> -p <db2_pass> For this command, <database> is the name of the database, for example, DYK_CAT or DYK_DM, and <db2_user> and <db2_pass> are the DB2 user ID and password for accessing the database. This command enables the TCP connection to that database only, from a machine with a supported ersion of DB2 Uniersal Database IBM Tioli Serice Leel Adisor: Getting Started

215 3. Shutdown and then restart DB2 Uniersal Database by issuing the following commands: db2stop force db2start 4. On the DB2 8.1 client machine, open a DB2 command line prompt, and create or catalog the DYK_CAT or DYK_DM database. Then connect to that database by issuing the command: db2 connect to <database> user <db2_user> using <db2_pass> 5. On the DB2 8.1 client machine, naigate to the following location: For Windows systems, naigate to <DB2_Dir>\bnd (where <DB2_Dir> is the directory where DB2 was installed, for example, C:\Program Files\SQLLIB). For UNIX systems, naigate to /opt/ibm/db2/v8.1/bnd. 6. In the DB2 command line window, issue the following commands: db2 bind db2clipk.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clpcs.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clpnc.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clprr.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clprs.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clpur.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC db2 bind db2clist.bnd ACTION REPLACE BLOCKING ALL GRANT PUBLIC 7. You can bring up the DB2 Control Center (click Start > Programs > IBM DB2 > Control Center) and iew the remote databases and tables associated with the databases. Performing a Silent Installation of IBM Tioli Serice Leel Adisor Usually you use the LaunchPad to install the IBM Tioli Serice Leel Adisor product (see Installing the IBM Tioli Serice Leel Adisor Product on page 61), but you can also perform a silent installation. A sample response file named SilentInstall.rsp is located in the root directory of the IBM Tioli Serice Leel Adisor installation CD. You can copy this file from the CD to a temporary location and edit this file, following the instructions in the embedded comments in the file. You might want to refer to the procedure in Installing the IBM Tioli Serice Leel Adisor Product on page 61 to understand how the parameters specified in the response file are used in the installation flow. To perform a silent installation using an edited SilentInstall.rsp file, complete the following steps: 1. Verify that the WebSphere Administration Serer is started. 2. Open a command prompt. 3. Naigate to the root directory of the IBM Tioli Serice Leel Adisor installation CD and locate the install.bat script (or install.sh script for UNIX systems). 4. Issue the following command: For Windows systems: install.bat -options <response_file> -silent For UNIX systems:./install.sh -options <response_file> -silent Appendix G. Installation Hints and Tips 197

216 In this command, <response_file> is the fully qualified name of the edited response file to run, including the temporary path location of the edited file. 5. Check the installation logs as usual for errors and correct as needed. Alternatiely, you can perform an installation using the installation wizard user interface and record the flow into a target response file by issuing the following command: For Windows systems: install.bat -options-record <response file> For UNIX systems:./install.sh -options-record <response file> Note that in this command the -options-record parameter is specified as a single parameter (no blank spaces). The <response file> parameter is the target where responses are recorded for later use in a future silent installation. Refer to the sample SilentInstall.rsp file for additional information on the arious installation options. After the silent installation completes successfully, you should delete or sae offline the SilentInstall.rsp file if it contains sensitie information, such as user IDs and passwords. 198 IBM Tioli Serice Leel Adisor: Getting Started

217 Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor If you hae a preious installation of IBM Tioli Serice Leel Adisor, there are a number of tasks you need to complete to upgrade your SLM Solution enironment to be compatible with IBM Tioli Serice Leel Adisor ersion 2.1. The general procedure for upgrading your SLM solution to operate with IBM Tioli Serice Leel Adisor ersion 2.1 includes the following steps: 1. Prepare the enironment for upgrading IBM Tioli Serice Leel Adisor. 2. Run the IBM Tioli Serice Leel Adisor installation program, which includes special functions for upgrading from a preious ersion of IBM Tioli Serice Leel Adisor. 3. Complete additional upgrade tasks after running the IBM Tioli Serice Leel Adisor installation program. In addition to upgrading the arious components of IBM Tioli Serice Leel Adisor to the latest leels, upgrades might be needed to the base operating system, DB2 database support, Tioli Data Warehouse, and IBM WebSphere Application Serer. Table 17 shows a comparison of the SLM solution enironments between IBM Tioli Serice Leel Adisor ersion 1.1, ersion 1.2, ersion 1.2.1, and ersion 2.1. Refer to the Release Notes for IBM Tioli Serice Leel Adisor for information on specific supported ersions of these applications. If you are upgrading from an enironment with IBM Tioli Serice Leel Adisor Fix Pack 1 installed (represented in this document as Version 1.1.1), the enironment is already updated with Tioli Enterprise Data Warehouse 1.1 Fix Pack 1 and DB2 7.2 Fix Pack 6 (or later), so these tasks do not need to be performed again. Table 17. Considerations for upgrading IBM Tioli Serice Leel Adisor SLM Solution Component Hardware Platform Operating System IBM DB2 Uniersal Database Enterprise Edition Your current ersion of IBM Tioli Serice Leel Adisor: Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version When you upgrade to IBM Tioli Serice Leel Adisor ersion 2.1, note the following considerations: Preiously supported hardware platforms are still supported. See the IBM Tioli Serice Leel Adisor Release Notes for details on supported hardware platforms. Seeral preiously supported operating systems are no longer supported. See the IBM Tioli Serice Leel Adisor Release Notes for details on supported operating systems. The minimum supported DB2 ersion 7.2 with Fix Pack 5 must be upgraded to at least ersion 7.2 with Fix Pack 8 (plus the associated special fix), resulting in an informational token of DB Copyright IBM Corp. 2002,

218 Table 17. Considerations for upgrading IBM Tioli Serice Leel Adisor (continued) SLM Solution Component Tioli Data Warehouse Crystal Enterprise Your current ersion of IBM Tioli Serice Leel Adisor: Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 When you upgrade to IBM Tioli Serice Leel Adisor ersion 2.1, note the following considerations: Preious ersions of IBM Tioli Serice Leel Adisor support only Tioli Enterprise Data Warehouse ersion 1.1. IBM Tioli Serice Leel Adisor 2.1 also supports Tioli Enterprise Data Warehouse ersion 1.1, but proides additional function and features when operating with Tioli Data Warehouse 1.2. While it is not required, it is recommended that you upgrade to Tioli Data Warehouse 1.2 to take adantage of the latest enhancements. If you do not upgrade to Tioli Data Warehouse ersion 1.2, you must at least upgrade Tioli Enterprise Data Warehouse ersion 1.1 to Fix Pack 3. Tioli Enterprise Data Warehouse ersion 1.1 proided its own report interface for generating reports on data in the warehouse databases, but Tioli Data Warehouse ersion 1.2 incorporates Crystal Enterprise software in its reporting function. If you upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, you must also install Crystal Enterprise software as a prerequisite. WebSphere Application Serer Source application warehouse enablement packs IBM Tioli Serice Leel Adisor DYK Warehouse Pack (Target ETLs) Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Note that IBM Tioli Serice Leel Adisor ersion 2.1 does not depend on Crystal Enterprise software for its reporting function. Howeer, you might hae other applications that extract data from Tioli Data Warehouse that require Crystal Enterprise in your enironment. WebSphere Application Serer Standard Edition (SE), Adanced Edition (AE) and Adanced Edition Single Serer (AES) are no longer supported. You must upgrade WebSphere Application Serer to a supported ersion for your operating system. See the Release Notes for details. There should be no impact to source application warehouse packs by upgrading to IBM Tioli Serice Leel Adisor ersion 2.1. If you upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, warehouse packs that were designed for Tioli Enterprise Data Warehouse ersion 1.1 should still be supported, but you should refer to the documentation for Tioli Data Warehouse as well as your warehouse pack enablement guide for further information. You might want to upgrade warehouse packs to their latest supported ersion. You need to uninstall preious ersions of this target warehouse pack and install the latest ersion that is proided with IBM Tioli Serice Leel Adisor ersion IBM Tioli Serice Leel Adisor: Getting Started

219 Table 17. Considerations for upgrading IBM Tioli Serice Leel Adisor (continued) SLM Solution Component IBM Tioli Serice Leel Adisor DY1 Warehouse Pack (Source ETL) SLM Database and SLM Measurement Data Mart SLM Serer SLM Task Driers SLM Reports Your current ersion of IBM Tioli Serice Leel Adisor: Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version When you upgrade to IBM Tioli Serice Leel Adisor ersion 2.1, note the following considerations: This is a new source warehouse pack proided with this ersion of IBM Tioli Serice Leel Adisor that writes ealuation results back into Tioli Data Warehouse. You can optionally install this warehouse pack if you hae additional applications that can extract this data from the warehouse. Database tables and formats are automatically updated to ersion 2.1 by the IBM Tioli Serice Leel Adisor upgrade process. This ersion of IBM Tioli Serice Leel Adisor also supports creating these databases on a z/os operating system, but you must delete existing databases and create them new in the z/os enironment. This component is automatically updated to ersion 2.1 by the IBM Tioli Serice Leel Adisor upgrade process. For distributed installations, this component must be upgraded before SLM Reports and SLM Task Driers. This component is replaced in IBM Tioli Serice Leel Adisor ersion 2.1 with the new SLM Administration Serer, which is installed as a separate step after the upgrade of the SLM Task Driers has completed. The IBM Console interface, supported with Tioli Presentation Serices, is replaced in this ersion with the SLM Administratie Console, a WebSphere based interface that proides better usability and streamlined function. The SLM Task Driers component is first upgraded by the upgrade process to presere existing user information, and after the SLM Administration Serer is later installed, this user information is upgraded into the WebSphere local user registry. If you need to upgrade WebSphere Application Serer from a preious ersion to a currently supported ersion, you should uninstall any preious ersion of SLM Reports before upgrading WebSphere. When the IBM Tioli Serice Leel Adisor installation program is run, the updated ersion of this component is installed. If you are using WebSphere Network Deployment, see Installing IBM Tioli Serice Leel Adisor in a Network Deployment Enironment on page 45 for more information. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 201

220 Table 17. Considerations for upgrading IBM Tioli Serice Leel Adisor (continued) SLM Solution Component User customized files Message and trace logs Language Pack Your current ersion of IBM Tioli Serice Leel Adisor: Version 1.1 (or 1.1.1) Version 1.2 Version Version 1.1 (or 1.1.1) Version 1.2 Version 2.1 Version 1.1 (or 1.1.1) Version 1.2 Version When you upgrade to IBM Tioli Serice Leel Adisor ersion 2.1, note the following considerations: Existing ersions of these files are copied and renamed. You need to customize the ersion 2.1 files again to maintain customization, referring to the renamed files as needed. slm.rls file for Tioli Enterprise Console Eent notification SNMP Trap formats (ersion 1.1 of these files must be uninstalled and new files installed) SLM Report customized JSP files for reports During the IBM Tioli Serice Leel Adisor upgrade process, these files are upgraded automatically. No action is required. Version 1.1 log files are located in arious places in the SLM Solution enironment. The Tioli Common Directory is used for all log files in IBM Tioli Serice Leel Adisor ersion 2.1. Any ersion 1.1 files are untouched. The Tioli Common Directory continues to be used for all log files in IBM Tioli Serice Leel Adisor ersion 2.1. If used, any preious ersion is uninstalled automatically if language support is selected for installation as part of running the installation program as part of a product upgrade. In performing the upgrade of your SLM Solution enironment to ersion 2.1, the assumption is made that there are no changes to the distribution of Tioli Data Warehouse or IBM Tioli Serice Leel Adisor components. All components in the current enironment are expected to remain on their existing machines in the ersion 2.1 enironment. If you choose to uninstall existing components and reinstall them on different machines in your enterprise, for example, to consolidate components onto fewer machines, or to distribute components on additional machines, then you should treat this as a new installation and follow the documented procedures for backing up and uninstalling the existing enironment, and installing the new distributed enironment as a new installation. Tasks to Complete Before Upgrading IBM Tioli Serice Leel Adisor Before running the IBM Tioli Serice Leel Adisor installation program to perform the upgrade of IBM Tioli Serice Leel Adisor components to ersion 2.1, complete the following steps: 1. Before performing any upgrade operation, be sure to refer to the IBM Tioli Serice Leel Adisor support Web site for additional upgrade information and instructions. See the Release Notes for this Web site location. 2. Backup the entire SLM Solution, using the documented procedures. This includes backing up and saing any customized files you might hae, for eent notification or SLM Report customization of JSP files. Refer to the 202 IBM Tioli Serice Leel Adisor: Getting Started

221 backup procedures in the Administrator s Guide for IBM Tioli Serice Leel Adisor and Installing and Configuring Tioli Data Warehouse. 3. Verify that you hae enough temporary disk space. The IBM Tioli Serice Leel Adisor installation program uses approximately 300 KB of space under %TEMP% on Windows systems, or under /tmp on UNIX systems. 4. Leae actie the SLM Serer and any WebSphere Application Serer that is being used for SLM Reports and the SLM Administration Serer. The upgrade process automatically shuts down and restarts these serers at the appropriate times. 5. Verify that the existing DYK target ETLs are taken out of production mode, to eliminate the possibility of the ETLs running during an upgrade. 6. When considering the upgrade of the target warehouse pack for IBM Tioli Serice Leel Adisor, you hae the following options: If you do not plan to upgrade Tioli Enterprise Data Warehouse ersion 1.1 to ersion 1.2, you must still uninstall any existing target warehouse pack in preparation for installing the new target warehouse pack for IBM Tioli Serice Leel Adisor 2.1, using the Tioli Enterprise Data Warehouse 1.1 installation program and procedures. If you do upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, you might want to continue to use a Tioli Enterprise Data Warehouse 1.1 based target warehouse pack. In this case you must uninstall any existing Tioli Enterprise Data Warehouse 1.1 based target warehouse pack in preparation for installing the new Tioli Enterprise Data Warehouse 1.1 based target warehouse pack for IBM Tioli Serice Leel Adisor 2.1, using the separate warehouse pack uninstallation program proided with Tioli Data Warehouse 1.2. If you do upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, typically you need to upgrade to a Tioli Data Warehouse 1.2 based target warehouse pack. In this case you do not hae to uninstall an existing target warehouse pack. Later, when you install the Tioli Data Warehouse 1.2 based target warehouse pack for IBM Tioli Serice Leel Adisor, it is installed on top of any existing target warehouse pack. See Uninstalling the Target and Source Warehouse Packs on page 123 for more information. 7. Upgrade your operating system if necessary. Refer to the Release Notes for information on supported operating systems. Be sure to install any required fix packs or patches to bring the operating system up to the supported leel. Consider also other applications on this machine that depend on specific ersions of the operating system, and erify that they also operate properly after performing the upgrade. 8. Upgrade DB2 Uniersal Database as needed to at least the minimum supported leel. Be sure to upgrade DB2 Uniersal Database on all serer and client machines where you hae distributed components of the SLM solution. 9. Upgrade Tioli Enterprise Data Warehouse to at least the minimum supported leel. If you are not planning to upgrade Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, you must at least upgrade ersion 1.1 to the Fix Pack 3 leel. Refer to the Tioli Enterprise Data Warehouse Fix Pack 3 Readme and the Tioli Data Warehouse support Web site for more information. If you are upgrading to Tioli Data Warehouse 1.2, you might hae to install Crystal Enterprise software if you do not already hae a supported ersion in your enironment. Refer to Installing and Configuring Tioli Data Warehouse for details on installing Crystal Enterprise software as a prerequisite to installing Tioli Data Warehouse 1.2. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 203

222 10. If you need to upgrade IBM WebSphere Application Serer to a supported ersion, first remoe the SLM Reports component, following the instructions in your documentation, and then upgrade IBM WebSphere Application Serer to the required ersion. Later, when you run the IBM Tioli Serice Leel Adisor installation program to perform the upgrade, the latest ersion SLM Reports is installed. (If you attempt to upgrade IBM WebSphere Application Serer before remoing SLM Reports, you receie errors. You can still remoe SLM Reports after a failed WebSphere Application Serer upgrade attempt and perform the upgrade again.) Back up customized JSP Files: If you hae any customized JSP files for SLM Reports, these files should already be manually backed up during the documented backup procedure for IBM Tioli Serice Leel Adisor. 11. For this ersion of IBM Tioli Serice Leel Adisor, you must upgrade your ersion of WebSphere Application Serer to the minimum supported leel. See the Release Notes for information on upgrading WebSphere Application Serer to at least this minimum supported leel. Refer to the official IBM WebSphere Application Serer support Web site for product downloads, as well as installation and upgrade information for the supported ersions of IBM WebSphere Application Serer. Running the IBM Tioli Serice Leel Adisor Upgrade Program After you complete the steps in the preious section, you should be ready to run the IBM Tioli Serice Leel Adisor installation program to perform the upgrade of the components of IBM Tioli Serice Leel Adisor to ersion 2.1. If you hae SLM components (the SLM Serer, SLM Reports, and SLM Task Driers) installed on multiple machines, or in multiple directories, you must run the installation program on each machine and for each directory that contains a component of IBM Tioli Serice Leel Adisor. Upgrade the SLM Serer first: For a distributed installation of IBM Tioli Serice Leel Adisor, upgrade the SLM Serer component before upgrading the SLM Reports or SLM Task Driers components, and erify that the upgrade of the SLM databases was completed successfully before you attempt to use the upgraded ersion of IBM Tioli Serice Leel Adisor. To upgrade IBM Tioli Serice Leel Adisor components using the installation program, complete the following steps: 1. Important: On Windows operating systems, erify that the Serices control panel is closed before starting the IBM Tioli Serice Leel Adisor installation program. If this panel is left open, the upgrade can fail with unpredictable results. You must restore your system from your last backup and perform the upgrade again. 2. Start the IBM Tioli Serice Leel Adisor installation program as if you were performing a new installation (see Starting the LaunchPad on page 51). Only those installation program pages needed for the upgrade are displayed. 3. When prompted, type the directory where one or more SLM components are installed on this machine. The installation program then determines which components are installed in that directory on this machine, and upgrades them. The installation program performs the following upgrade tasks: 204 IBM Tioli Serice Leel Adisor: Getting Started

223 Creates the Tioli Common Directory if not already created. Log files for ersion 2.1 are stored in the Tioli Common Directory under the \DYK subdirectory for IBM Tioli Serice Leel Adisor. Passwords that were stored in the database for preious ersions are encrypted if they hae not already been encrypted. If the SLM Serer option is installed on this machine: The SLM Database and SLM Measurement Data Mart are automatically upgraded to ersion 2.1 as part of the upgrade of the SLM Serer component. Upgrading the SLM databases inoles multiple steps: Changes to the databases are committed after each successful step. If any errors are encountered during a database upgrade, an error page is displayed, giing you the option to retry or skip the database upgrade process. If you do not retry the database upgrade at this time, the upgrade of other SLM components continues, but you must complete the upgrade of the databases manually. If you are upgrading from IBM Tioli Serice Leel Adisor ersion 1.1, files that were located in the <SLM_Install_Dir>/tec directory for IBM Tioli Serice Leel Adisor are moed to <SLM_Install_Dir>/escalate for ersion 2.1. These files include the slm.baroc file and slm.rls file (which is renamed to slm.rls.bak), among other files. Where possible, the installation program remoes the /tec directory. If the SLM Reports option is installed on this machine, SLM reports for ersion 2.1 are automatically integrated into WebSphere Application Serer. If the SLM Task Driers option is installed on this machine, the Tioli Presentation Serices user information is saed in the SLM Database for later use when you migrate users (see Step 3. Migrate users from the preious ersion on page 208). After presering the user information, the SLM Task Driers option is uninstalled. This option is replaced in ersion 2.1 by installing the SLM Administration Serer option in a separate directory (see Step 2. Install the new SLM Administration Serer Option on page 207). Follow the rest of the installation program prompts and complete the upgrade of IBM Tioli Serice Leel Adisor. Repeat this procedure for each machine in your distributed enironment as needed. Tasks to Complete After Upgrading IBM Tioli Serice Leel Adisor After running the IBM Tioli Serice Leel Adisor installation program to upgrade SLM components to ersion 2.1, complete the procedures in the sections that follow. If you experience problems during an upgrade, check the log files located in the \DYK subdirectory of the Tioli Common Directory, and see the Troubleshooting document for assistance. Step 1. Verify database upgrade and complete manually if needed The upgrade of SLM databases is accomplished by running a succession of automated scripts. Changes to the databases are committed after each script is completed successfully. Depending on which prior ersion of IBM Tioli Serice Leel Adisor you are upgrading from, you need to check arious log files to erify that each successie script completed successfully. If, during a database Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 205

224 upgrade (while running the installation program) you encounter errors, you need to examine the arious logs to determine which script failed, and then run that script again, as well as any additional scripts not yet run to complete the database upgrade. You can also check the sladbupdate.log file, in the \DYK\logs\install folder of the Tioli Common Directory, for the status of the database upgrade scripts that are run. Table 18 shows which log files you should examine depending on the ersion of IBM Tioli Serice Leel Adisor that you are upgrading from. Table 18. Log files that should be examined for successful database upgrade...if you are upgrading from IBM Tioli Serice Leel Adisor Version: Examine these log files sladbupdate_stderr.log 1.1 or X sladbupdate_stdout.log sla121dbupdate_stderr.log sla121dbupdate_stdout.log X X sla1211dbupdate_stderr.log X X X sla1211dbupdate_stdout.log sla121100dbupdate_stderr.log X X X X sla121100dbupdate_stdout.log sla21dbupdate_stderr.log X X X X sla21dbupdate_stdout.log These log files are located in the \DYK\logs\install folder of the Tioli Common Directory. For each stdout log file, look for errorleel n, where n is an integer. If you find an error leel of 4 or greater, then the associated upgrade script failed. Check the accompanying error log for details, and correct any problems that you encounter before attempting to run the script again. To run a script again, complete the following steps: 1. Edit the script file and replace the DB2 password field with your alid DB2 password information. 2. Sae the edited script file. 3. On Windows systems, start a DB2 command prompt; on UNIX systems, source the db2profile. 4. Run the script file again. The script files to be edited and run are shown in Table 19 on page 207 are located in the \bin directory where IBM Tioli Serice Leel Adisor is installed: 206 IBM Tioli Serice Leel Adisor: Getting Started

225 Table 19. Edit and run the following database upgrade scripts starting with the first failing script in the sequence. Database upgrade log where first fail is found Scripts to run in consecutie order: Windows systems UNIX systems sladbupdate_stdout.log 1. sladbupdate.bat 2. sla121dbupdate.bat 3. sla1211dbupdate.bat 4. sla121100dbupdate.bat 5. sla21dbupdate.bat sla121dbupdate_stdout.log 1. sla121dbupdate.bat 2. sla1211dbupdate.bat 3. sla121100dbupdate.bat 4. sla21dbupdate.bat sla1211dbupdate_stdout.log 1. sla1211dbupdate.bat 2. sla121100dbupdate.bat 3. sla21dbupdate.bat sla121100dbupdate_stdout.log 1. sla121100dbupdate.bat 2. sla21dbupdate.bat 1. sladbupdate.sh 2. sla121dbupdate.sh 3. sla1211dbupdate.sh 4. sla121100dbupdate.sh 5. sla21dbupdate.sh 1. sla121dbupdate.sh 2. sla1211dbupdate.sh 3. sla121100dbupdate.sh 4. sla21dbupdate.sh 1. sla1211dbupdate.sh 2. sla121100dbupdate.sh 3. sla21dbupdate.sh 1. sla121100dbupdate.sh 2. sla21dbupdate.sh sla21dbupdate_stdout.log 1. sla21dbupdate.bat 1. sla21dbupdate.sh Check the logs again after running each script to erify that it completed successfully before running the next script. The database upgrade is complete when all scripts complete successfully. Step 2. Install the new SLM Administration Serer Option IBM Tioli Serice Leel Adisor 2.1 replaces the preious SLM Task Driers option with the new SLM Administration Serer, which operates in the WebSphere enironment, along with SLM Reports. When you ran the IBM Tioli Serice Leel Adisor installation program to perform the initial upgrade, the program uninstalls the SLM Task Driers option in preparation for being replaced by the SLM Administration Serer. At this time you must run the IBM Tioli Serice Leel Adisor installation program a second time to separately install the new SLM Administration Serer component into a separate directory. To install the SLM Administration Serer, complete the following steps: 1. Verify that WebSphere Application Serer is installed on the machine where you plan to install the SLM Administration Serer. If WebSphere Application Serer is not already started, the installation program detects it and gies you the option to start the serer at the appropriate time. 2. Following the standard procedure, insert the IBM Tioli Serice Leel Adisor installation CD into the target machine and start the LaunchPad. 3. From the LaunchPad, select the Install Program option as usual. 4. Follow the on-screen prompts in the installation wizard, but be sure to specify a target directory that is different from the directory where existing components of IBM Tioli Serice Leel Adisor are installed. For example, if your current IBM Tioli Serice Leel Adisor installation is located in C:\TSLA, then specify a different directory for the SLM Administration Serer, such as C:\SLMAdmin. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 207

226 5. On the installation features selection page, select only the SLM Administration Serer option. 6. Follow the on-screen prompts as needed to compete the installation of the SLM Administration Serer. Step 3. Migrate users from the preious ersion Use the Migrate Users option in the IBM Tioli Serice Leel Adisor LaunchPad to migrate existing users that were created to access SLM Reports and the administratie interface (either the current SLM Administratie Console or the IBM Console) in preious ersions of IBM Tioli Serice Leel Adisor. This migration process takes Tioli Presentation Serices user information that was presered during the upgrade of the SLM Task Driers from the preious ersion of IBM Tioli Serice Leel Adisor (see Running the IBM Tioli Serice Leel Adisor Upgrade Program on page 204), along with the reports information in the user table, and performs the following tasks: Creates the user in the local user store Maps the user to the IBM WebSphere Application Serer roles corresponding to those assigned in Tioli Presentation Serices. When using this migration process, keep in mind the following restrictions: If a reports user is not selected for the migration, it is remoed from the user information table. This utility only supports local operating system WebSphere user registries (no Lightweight Directory Access Protocol (LDAP) or custom registries). Distributed user stores such as NIS, DFS, and Windows Domains are not supported. A user defined in an unsupported user registry cannot be migrated. The WebSphere Application Serers associated with SLM Reports and the SLM Administration Serer must be restarted after users are migrated so that the new security information is applied and users are mapped to roles. User passwords are only set in the user registry for users that do not already exist. User passwords are neer changed in the user registry. User names and passwords that are greater than 255 characters are skipped and are not shown as eligible to be upgraded. For AIX and HP systems, user names greater than 8 characters are not migrated, due to restrictions on those operating systems. For user names that fail the migration, add them manually using the scmd report adduser CLI command. Any errors encountered during user creation are written to a log file in the Tioli Common Directory. Errors might be generated in situations where the user cannot be created because of password restrictions or other external factors. The log file also seres as an audit by producing messages indicating the success or failure of each indiidual user. Logs are generated for both the extraction and the creation processes. The log file names are of the form traceusermigx.log and msgusermigx.log where x is an integer. To start the user upgrade process on the machine (or machines) where you installed the SLM Administration Serer and the SLM Reports options, from the main page of the LaunchPad, click Migrate Users. The user upgrade process guides you through the following steps: 1. A Welcome screen is displayed. Click Next to continue. 2. If the SLM Administration Serer and SLM Reports are installed into different directories on this machine, you are prompted to select either the SLM Reports 208 IBM Tioli Serice Leel Adisor: Getting Started

227 feature, for upgrading report users, or the SLM Administration Serer feature, for upgrading SLM Administratie Console users. If you are upgrading both types of users, you must run this user upgrade process twice, once for each feature. Select either radio button and click Next to continue. 3. If WebSphere security is enabled, you are prompted for a alid user name and password for WebSphere access. Enter the user name and password and click Next to continue. 4. You are prompted for an aailable WebSphere Application Serer name. The default alue of serer1 is displayed. Accept this default or specify another serer name, then click Next to continue. 5. A list of users that are eligible to be upgraded is displayed. Clear the check box for the users that you do not want to be upgraded, and click Next to continue. Note: The report user specified during the upgrade of the SLM Reports feature is included in the list of users to be upgraded. This is expected. 6. User IDs that already exist in the local registry are checked, and you are prompted to erify that the selected user names are the same users in the user registry, and not an unintended conflict with another existing user name. Clear the check box next to any user names that might be in conflict with existing user names in the registry and click Next to continue. 7. A summary page is displayed, showing which user IDs will be upgraded. Click Next to continue. 8. The selected users are upgraded in the local registry. When finished, a message is displayed. Click Finish to complete the user upgrade process and return to the LaunchPad. If the SLM Administration Serer and SLM Reports are installed on separate machines, you must perform this upgrade on both machines. Using the User Upgrade Dump Utility If you cannot or do not want to use the user upgrade function in the IBM Tioli Serice Leel Adisor LaunchPad, you can choose to use the user upgrade dump utility, userdump. This utility dumps all user upgrade information to a flat text file. It is intended to be used when you are upgrading unsupported user registries such as LDAP or custom WebSphere user registries. The utility is located with other IBM Tioli Serice Leel Adisor utilities in the <TSLA_Dir>/bin directory, and requires the same enironmental setup procedures as other utilities. See the Command Reference for more information. Step 4. Ensure the correct ersion of the db2jaa.zip file is being used If you are not upgrading Tioli Enterprise Data Warehouse 1.1 to ersion 1.2, and you upgraded your DB2 installation by installing a Fix Pack after upgrading Tioli Enterprise Data Warehouse 1.1 to Fix Pack 3, you must manually copy the db2jaa.zip file, located in <DB2_Dir>/SQLLIB/bin/jaa12/, into the <TWH_Dir>/tools/bin directory, replacing the existing copy of db2jaa.zip to ensure that you are using the correct ersion of this file. You must complete this step before installing the target warehouse pack for IBM Tioli Serice Leel Adisor 2.1. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 209

228 Step 5. Install the Target Warehouse Pack Install the target warehouse pack for IBM Tioli Serice Leel Adisor ersion 2.1. Install one of the following target warehouse packs: A target warehouse pack for the Tioli Enterprise Data Warehouse 1.1 enironment. In this case, use the Tioli Enterprise Data Warehouse 1.1 installation program and procedures to install this warehouse pack. See Installing the Target Warehouse Pack for the Tioli Enterprise Data Warehouse 1.1 Enironment on page 92. for details. A target warehouse pack for the Tioli Data Warehouse 1.2 enironment. In this case, use the separate warehouse pack installation program proided with the installation of Tioli Data Warehouse 1.2 to install this target warehouse pack. See Installing the Target Warehouse Pack for the Tioli Data Warehouse 1.2 Enironment on page 90. for details. Note: If you are upgrading in an enironment with more than one central data warehouse, you can use the Warehouse pack installation program to choose from the existing central data warehouse databases. Be sure to choose the same central data warehouse that was used prior to installing this new warehouse pack to preent problems with data that already exists in the IBM Tioli Serice Leel Adisor databases. Do not run the old warehouse pack ETLs after an upgrade!: After you complete the upgrade of the DYK target warehouse pack, the old warehouse pack should hae been completely uninstalled or replaced by the latest ersion. Before running the new ETLs, howeer, you should erify that the correct ersion was installed. To erify the ersion of the upgraded warehouse pack, complete the following steps: 1. Bring up the DB2 Control Center by clicking Start > Programs > IBM DB2 > Control Center 2. From the DB2 Control Center, launch the Data Warehouse Center by clicking Tools > Data Warehouse Center. 3. Log into the Data Warehouse Center using your DB2 username and password. 4. In the left pane of the Data Warehouse Center, expand the Subject Areas folder. 5. Locate the entry starting with DYK_. The correct ersion of the target ETL is installed if this entry matches one of the following ersions: For the target warehouse pack for the Tioli Data Warehouse 1.2 enironment: DYK_IBMTioliSericeLeelAdisor_ _Subject_Area For the target warehouse pack for the Tioli Enterprise Data Warehouse 1.1 enironment: DYK_IBMTioliSericeLeelAdisor_ _Subject_Area If you do not see the correct ersion for the warehouse pack that you installed, it is possible that an error occurred during installation, or you did not complete the upgrade of the warehouse pack as instructed. Do not run the target ETL until you resole any problems. If you run the old ETL after completing this upgrade procedure, the SLM Database will be left in an unusable state. You must then restore your SLM enironment from your backup and begin the upgrade procedure again. 210 IBM Tioli Serice Leel Adisor: Getting Started

229 Step 6. Configure warehouse pack user ID and password Configure the user ID and password for the target warehouse pack, using the appropriate procedures for Tioli Enterprise Data Warehouse 1.1 (see Getting Started documentation for your preious ersion of IBM Tioli Serice Leel Adisor) or Tioli Data Warehouse 1.2 enironments (see Configuring the User ID and Password on page 93). Step 7. Manually run special ETL upgrade steps If you installed the Tioli Data Warehouse 1.2 based target warehouse pack as a result of upgrading from a preious release of IBM Tioli Serice Leel Adisor, or as a result of upgrading from the Tioli Enterprise Data Warehouse 1.1 based target warehouse pack, you must perform the following additional manual steps once: 1. Stop the SLM Serer. 2. Ensure that there is no other actiity to the IBM Tioli Serice Leel Adisor databases: Verify that the WebSphere Application Serer used for the SLM Administration Serer and SLM Reports is stopped. Verify that the DB2 Control Center is stopped. Verify that none of the other IBM Tioli Serice Leel Adisor target ETL processes are scheduled to run (moe them from production mode to test mode if necessary). 3. Manually run the following two steps in the DYK_m00_Initialize_Process: DYK_m00_s010_Initialize_DYK_CAT DYK_m00_s020_Initialize_DYK_DM Manually run the following steps in the Registration and Process ETLs once before running either ETL process in its entirety: DYK_m05_s020_Update_Extract_Control (in the Registration ETL) DYK_m10_s040_Update_Extract_Control (in the Process ETL) Step 8. Schedule target ETLs and promote to production mode Schedule the ETLs and promote them to production mode, using the appropriate procedures for Tioli Enterprise Data Warehouse 1.1 (see Getting Started documentation for your preious ersion of IBM Tioli Serice Leel Adisor) or Tioli Data Warehouse 1.2 (see Configuring ETLs for Production Mode on page 101. Step 9. Restore customization of JSP Files If you customized JSP files, be sure to also customize JSP files again for ersion 2.1, referring to the preious ersion of JSP files that you backed up as needed. When you complete these steps, restart the WebSphere Application Serer. Restoring User Authorization for Portal Pages You might hae user names authorized to access certain portal pages (JSP files) that are no longer alid for this upgraded ersion of IBM Tioli Serice Leel Adisor. When users attempt to sign on with these old portal pages, they might receie an error message: DYKRP0051I You are not authorized to iew this page. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 211

230 Change the portal page assigned to users by using the scmd report changeuser CLI command, for example: scmd report changeuser -name George -iew 1 -page report.jsp?fsd=r7d Use the scmd report listuser command to list user names and portal pages to which they are assigned, and change user authorization as needed. See the Administrator s Guide for more information about managing users and authorizing them to access reports, and see the Command Reference for more information about these and other CLI commands. Step 10. Update notification configuration, if needed If you had configured for eent notification using , the substitution ariable names hae changed for IBM Tioli Serice Leel Adisor ersion 2.1. You should examine your subject lines and message text that uses substitution ariables and then test and update these notifications as needed. See Notification by on page 74 for more information. Also see Problems with Message Content in Troubleshooting for additional help with configuring eent notification using . If you are upgrading from IBM Tioli Serice Leel Adisor ersion 1.1 and had configured for eent notification using SNMP traps, you must remoe the traps formatted for the preious ersion and install the traps formatted for ersion 2.1. See Configuring for Notification by SNMP on page 107 for details. If you are upgrading from IBM Tioli Serice Leel Adisor ersion 1.1 and had configured for eent notification using Tioli Enterprise Console Eents, files that were located in the <SLM_Install_Dir>/tec directory for IBM Tioli Serice Leel Adisor ersion 1.1 hae been moed to <SLM_Install_Dir>/escalate for ersion 2.1. These include the slm.baroc file and slm.rls file (which is renamed to slm.rls.bak), and others. If you had customized the slm.rls file for ersion 1.1, you should refer to slm.rls.bak and the class definition information in slm.baroc to customize your slm.rls file again for ersion 2.1 before applying it. Step 11. Recreate filtering and sorting preferences for Manage pages Filter and sorting preferences on Manage pages of the SLM Administratie Console are lost when upgrading to IBM Tioli Serice Leel Adisor 2.1. You must recreate your filter and sorting preferences manually by launching appropriate Manage page and use the aailable table actions to define your preferences. Sae your preferences by closing the Manage page, clicking the Close (X) button for the Manage page in the work area. Step 12. Optionally install language support Install any language packs needed for ersion 2.1, following the documented installation procedure in Installing Language Support on page 109. Step 13. Search the log file for a single date message The ffdc log file is located in <Tioli Common Directory>\DYK\ffdc\<yyyymmdd>\SLMSerer. Search for the following message in the log file: Unable to conert the following single dates to GMT: 212 IBM Tioli Serice Leel Adisor: Getting Started

231 If the ffdc log file does not exist, or you do not find this message, skip this step and proceed to Step 14. Search the log file for unsupported time zone message. If you find this message in the log, it is followed by additional information as illustrated in the following example: Unable to conert the following single dates to GMT: ScheduleName = Business Schedule 1 ScheduleID = 1013 PeriodID = 0 StartTime = 1:00 EndTime = 5:00 Unsupported TimeZone = DEF GMT Preious [Date = 8/10/04] [DateNumber = ] GMT Current [Date = 8/11/04] [DateNumber = ] GMT Next [Date = 8/12/04] [DateNumber = ] The IBM Tioli Serice Leel Adisor upgrade program attempts to conert single dates in schedule periods that were defined with the preious release of IBM Tioli Serice Leel Adisor to date formats for the current release of IBM Tioli Serice Leel Adisor. These messages occur for dates that could not be automatically conerted. For the listed dates, you must decide on what date is correct for this conersion. For each message displayed aboe, do the following steps: 1. From the message decide which of the three dates is correct for that schedule period. If you need more information about the schedule to help you decide, open the SLM Administratie Console and View the schedule. To open the SLM Administratie Console, start the WebSphere Application Serer associated with the SLM Administration Serer if it is not already started. Note: Een if the date is displayed correctly in the SLM Administratie Console, you must continue and finish the following steps. 2. Open a DB2 command prompt window on the SLM Serer machine. 3. Naigate to the <SLM_Install_Dir>/bin directory and issue the following command specifying the information taken from the message: For Windows systems: updatesingledate <SLM Database DB Name> <DB2 Userid> <DB2 Password> <Schedule ID> <Schedule Period ID> <Date Number> For UNIX systems:../updatesingledate <SLM Database DB Name> <DB2 Userid> <DB2 Password> <Schedule ID> <Schedule Period ID> <Date Number> Step 14. Search the log file for unsupported time zone message The ffdc log file is located in <Tioli Common Directory>\DYK\ffdc\<yyyymmdd>\SLMSerer. Search for the following message in the log file: Unsupported Timezones currently in use by this serer. If the ffdc log file does not exist, or you do not find this message, skip this step and proceed to Step 15. Check Quarterly Dates on page 214. Appendix H. Upgrading From Preious Versions of IBM Tioli Serice Leel Adisor 213

232 If you find this message in the log, it is followed by a list of time zone IDs that are in schedule periods that were defined using the preious release of IBM Tioli Serice Leel Adisor but are not supported in the current SLM Serer operating enironment. SLA ealuations might not be accurate unless you choose a supported similar time zone and specify it for these schedule periods. Complete the following steps: 1. Issue the following CLI command to display a list of supported time zone IDs: scmd som displaytimezones See the Command Reference for information on running CLI commands. 2. Choose a time zone ID from the list that has the same GMT offset as the unsupported time zone. 3. From a DB2 command prompt window on the SLM Serer machine, naigate to the <SLM_Install_Dir>/bin directory and issue the following command, specifying the appropriate old and new time zone keys: For Windows systems: updatetimezone <SLM Database DB Name> <DB2 Userid> <DB2 Password> <Old Timezone> <New Timezone> For UNIX systems:../updatetimezone <SLM Database DB Name> <DB2 Userid> <DB2 Password> <Old Timezone> <New Timezone> Step 15. Check Quarterly Dates You should check your quarterly date setting in the SLM Administratie Console to erify that they are correct for your enironment. To check your quarterly date settings, do the following steps: 1. Open the SLM Administratie Console. Note: You might need to first start the WebSphere application serer associated with the SLM Administration Serer if it is not already started. 2. From the portfolio click Customize Schedules. 3. Click Quarterly Dates. 4. If the dates are not correct for your enironment, change them, then click OK. Step 16. Restart the serers When finished, restart the SLM Serer and restart the WebSphere application serers associated with SLM Reports and the SLM Administration Serer. 214 IBM Tioli Serice Leel Adisor: Getting Started

233 Appendix I. IBM Tioli Business Systems Management solution One of your most difficult tasks in business systems management is choosing products that align IT resources with your business priorities. In an enironment that includes resources from multiple endors running on multiple platforms, understanding the status of a particular IT resource is only a small part of the big picture. To maximize the business alue of your IT inestments, you must also see how each resource affects the applications and business processes that it supports. The Tioli business systems management solution is a model that helps you understand the components of integrated business systems and then identify the Tioli products that meet those management needs. This layered model shown in Figure 55 supports real-time, predictie management of your enterprise. Business Impact Management Define your resources as they relate to business systems Eent Correlation and Automation Synthesize raw data from monitoring applications Determine root causes of problems Capture and analyze historical trends Monitoring Systems and Applications Capture and filter raw data Generate eents for eent correlation and automation layer Automate based on autonomic model Figure 55. Tioli business systems management model Integration Implementing a comprehensie business systems management solution requires careful consideration of the roles of each product as well as the integration between the products. The products in the monitoring systems and applications layer proide the information that you need to understand critical problems. These products use built-in best practice definitions to define problem signatures that reflect the behaior of a set of related metrics oer time. The products in this layer can also proide automation as part of the autonomic model, using automation at the source to attempt to fix a problem before it becomes critical. After the problem is considered critical, an eent is generated and sent to the eent correlation and automation layer. When the condition is resoled, an eent is also sent to clear the initial eent. The products in the eent correlation and automation layer analyze the raw data from the monitoring layer. In the eent correlation and automation layer, effectie business management products correlate problem signatures with the systems on which these business-significant eents occurred, to determine the root cause of the problem. These tools might also suppress related eents and actiate automation to determine the root cause or to sole the problem. When a problem found in this Copyright IBM Corp. 2002,

234 Designing Your Solution layer has an impact on your business, the eent is forwarded to the business impact layer. An associated clearing eent should be sent to indicate the end of the impact. Products in the business impact management layer define your resources as they relate to business systems. Using products in this layer, you can interpret business-significant eents receied from the eent correlation and automation layer and display them in the context of the affected business system. For example, when the parameters of a serice leel agreement are exceeded, a product in the eent correlation and automation layer generates an eent. The business impact of this eent is understood and assigned by product in the business impact management layer. Then, through the use of products that capture and analyze historical trends in this data, you can monitor compliance to serice leel agreements and generate the appropriate reports summarizing this business data. The way that you design and implement your solution is critical. To design an effectie business systems management solution, think in terms of the following high-leel steps. 1. Designing the solution. First, identify the components of your systems, both z/os and distributed resources. What products are currently managing these resources? Are they effectie? Do they identify the business impact of system eents? 2. Identify the users and scenarios. Next, define the types and number of users and the work flows or scenarios associated with each user set. If you do not know what your users are doing, or should be doing, you cannot design an effectie solution. 3. Install and configure the products from the monitoring systems and applications layer. The products in this step are your eent sources. Defining these eent-generating products ensures that critical eents are forwarded to the eent correlation and automation layer, along with appropriate clearing eents. 4. Install and configure the products in the eent correlation and automation layer. The products in this step are your eent interpreters and filters. Defining this layer at this time ensures that all critical eents are correlated to their root causes and that business-significant eents are identified and can be forwarded to the business management impact layer. 5. Define a common data warehouse repository. An effectie business management solution cannot operate within the boundaries of a single product. All Tioli products in this model support the Tioli Data Warehouse as a common data repository. With all data in the same repository, cross-product reports that use the Crystal Reports interface can be written to show relationships among sets of data from different products. 6. Install and configure the products from the business impact management components. 216 IBM Tioli Serice Leel Adisor: Getting Started

235 Understanding the Product Set With this strong foundation built, you can now install and configure the products in the business impact management layer. Use the scenarios and user profiles deeloped in Step 2 to identify the appropriate business systems and definitions. The Tioli business systems management solution offers products that fulfill the functions described in the model. Figure 56 shows the products associated with each layer. Figure 56. Tioli business systems management model with products added These products are explained by layer in the following information. Products in the Business Impact Management Layer The following products support functions performed in the business impact management layer. IBM Tioli Business Systems Manager IBM Tioli Business Systems Manager manages z/os and distributed systems and proides a business systems management paradigm for applications management. Using the business systems management paradigm, you can manage groups of related applications that underpin and enable critical business functions, such as enterprise resource planning, customer relationship management, and on demand enironments. Mission-critical business systems present a unique management challenge. They typically span host and distributed enironments, are comprised of many interconnected application components, both commercial and custom, and rely on dierse middleware, databases, and supporting platforms. IBM Tioli Business Systems Manager gies you a single point of management and control and proides end-to-end business systems management to organize related components and gie business context to management decisions. IBM Tioli Business Systems Manager proides a unique configurable business iew that enables management and control of the multiple integrated software components required to delier a specific business serice. The product achiees this alue by using a tool called the business system. Using a business system, the IT staff can iew IT resources in the context of critical business serices, prioritize actions based on business impact, and make intelligent trade-offs. A business Appendix I. IBM Tioli Business Systems Management solution 217

236 system proides a business context for IT, enables greater accountability to business user needs, and improes the ability to prioritize issues and optimize actions. The product also shows and allows the manipulation of the relationships between applications, so that your IT staff can easily spot inefficiencies and problems and quickly diagnose the root cause of complex failure scenarios, thereby increasing aailability of critical business systems. In summary, IBM Tioli Business Systems Manager helps your business in the following ways. Proides a unique configurable business system iew that allows management and control of multiple integrated software components required to delier a specific business serice Automatically discoers and builds graphical iews of applications Supports manually grouped managed resources in containers that represent a business iew Dynamically adjusts the business system iew for components added, modified, or deleted Proide multiendor enablement of mainframe and distributed systems management data for true end-to-end serice leel management IBM Tioli Serice Leel Adisor IBM Tioli Serice Leel Adisor proides serice leel management capabilities for proiders of IT serices. It is designed to simplify the definition of serice offerings according to the terms of a serice leel agreement, associating the serice leel agreement with one or more clients. It then automates ealuating serice leel agreements by correlating any monitored metrics stored in a built-in database using IBM Tioli Data Warehouse. IBM Tioli Serice Leel Adisor proides alerts and historical reports of serice leel agreement iolations and trends toward iolation. Proiders of IT serices who need to measure, manage, and report on the business impact of their internal IT infrastructure can leerage existing performance and aailability or business process applications. Using IBM Tioli Serice Leel Adisor, you can manage the information collected by these applications against serice leel agreements and internal serice leel objecties. The goal is to proide predictie serice leel management on any appropriate IBM and Tioli or independent software application for true end-to-end business impact management. The eents and reports from IBM Tioli Serice Leel Adisor can help you manage costs, justify expense, improe internal customer satisfaction, and measure the business impact of problems with your enterprise IT infrastructure in terms of reenue, productiity, and contribution to business success. In summary, IBM Tioli Serice Leel Adisor helps your business in the following ways: Takes a proactie approach to serice leel management using a patent-pending trend analysis algorithm Integrates with IBM Tioli Data Warehouse to consolidate and report on systems management data Proides multiendor enablement of mainframe and distributed systems management data for true end-to-end serice leel management 218 IBM Tioli Serice Leel Adisor: Getting Started

237 IBM Tioli Data Warehouse IBM Tioli Data Warehouse is an embedded technology that proides the backbone repository for all historical systems management data and the basis for all Tioli reporting solutions. As the amount of management data gathered continues to grow, the data is not being used effectiely for IT business-releant decisions. IBM Tioli Data Warehouse soles this problem by being the central data store where historical data from all management applications is aggregated and correlated. This data is used by the following types of products: High-alue predictie management applications such as IBM Tioli Serice Leel Adisor Reporting and independent software business intelligence tools, including offerings from the IBM DB2 family, Brio, Business Objects, Crystal Decisions, and Cognos All Tioli products The objectie of the IBM Tioli Data Warehouse is to proide a consistent historical reporting infrastructure and interface for all Tioli applications to use. The warehouse leerages a proen warehouse schema and DB2 technology. IBM Tioli Data Warehouse includes restricted-use license ersions of IBM DB2 Uniersal Database Enterprise Serer Edition and IBM DB2 Warehouse Manager. The IBM Tioli Data Warehouse technology proides an open and published data warehouse infrastructure so that you can moe beyond application-based data stores, to cross-application and business-based trending and analysis. Products in the Eent Correlation and Automation Layer The following products support functions performed in the eent correlation and automation layer. IBM Tioli Enterprise Console The IBM Tioli Enterprise Console product proides cross-system, root-cause problem analysis through processing of eents generated from arious sources, such as the IBM Tioli Monitoring product, simple network management protocol (SNMP), or custom adapters. By creating rules based on incoming eents, multiple eents from different sources can be combined into a single eent. The NetView Integrated TCP/IP Serices Component, a part of the IBM Tioli Enterprise Console product, discoers TCP/IP networks, displays network topologies, correlates and manages eents and SNMP traps, monitors network health, and gathers performance data. The NetView Integrated TCP/IP Serices Component meets the needs of managers of large networks by proiding the scalability and flexibility to manage mission-critical enironments. The IBM Tioli Enterprise Console proides sophisticated, automated problem diagnosis and resolution to improe system performance and reduce support costs. Recent enhancements focus on time to alue and ease of use with preconfigured best practices to simplify and accelerate deployment. The auto-discoery feature makes it easier for you to understand the enironment and process eents appropriately. The Web console proides a more isual understanding of eents and also proides remote access to eents and console operations. In summary, the IBM Tioli Enterprise Console deliers the following features: A Web console that proides improed isualization of eents, as well as access from any browser Appendix I. IBM Tioli Business Systems Management solution 219

238 Preconfigured rules that proide best-practices eent management Auto-discoery and problem diagnosis to increase operator responsieness and efficiency Integrated network management that extends your ability to reach and diagnosis problems for end-to-end management of your IT enironment Comprehensie management that accepts eents from non-tioli products or systems IBM Tioli NetView for z/os IBM Tioli NetView for z/os proides a comprehensie set of tools for maintaining complex, multiendor, multiplatform networks and systems from a single point of control. NetView for z/os proides management functions that work together with other products or can function alone. NetView for z/os is a program for managing networks and systems through graphical display and automation. It reduces manual resource definition and complex automation setup through production-ready automation and extends centralized management into multiple non-sna network enironments. NetView for z/os can be used in an enterprise as a centralized manager, a mid-leel manager, or a z/os management endpoint. NetView for z/os also proides the base automation capabilities for the z/os platform that is used by the IBM Tioli System Automation for z/os product. IBM Tioli System Automation for z/os IBM Tioli System Automation for z/os plays an important role in building an end-to-end autonomic computing solution. The unique functions of Tioli System Automation for z/os can help customers with a single z/os system and or with multiple parallel sysplex clusters to ease management, reduce costs, and increase aailability. Tioli System Automation for z/os is designed to automate input and output, processor and system operations, and includes predefined automation for the IMS, CICS, IBM Tioli Workload Scheduler, and DB2 products. In summary, System Automation for z/os deliers the following features: Easier operation and automation, including easier naigation through the dependency graphs and the ability to fill or oerwrite start and stop requests with customer chosen defaults Automation of z/vm guest systems (including the Linux operating system) for better control oer if and how groups are moed to images within a sysplex, improed reliability, and easier identification of the owner of a resource in case of a problem Health and performance monitoring so that you can define and manage monitors, such as IBM Tioli Monitoring, that run inside IBM Tioli NetView for z/os or can be accessed from this product, and trigger actions and update compound status when monitor status changes More powerful automation for simplified and fast inter-system communication and a remote command facility using SNA or TCP/IP, with support for NetView Management Console performance enhancements and WebSphere high-aailability automation Products in the Monitoring Systems and Applications Layer The following products support functions performed in the monitoring systems and applications layer. 220 IBM Tioli Serice Leel Adisor: Getting Started

239 IBM Tioli Monitoring At the heart of the Tioli monitoring space is the IBM Tioli Monitoring product. IBM Tioli Monitoring is an application that applies preconfigured, automated best practices to the monitoring of IT resources. Its main purpose is to apply best practices locally at the managed system to determine whether a problem situation exists, and if so, local automated actions are started to resole or bypass the problem, or initiate procedures for collecting problem determination information. In summary, IBM Tioli Monitoring proides the following features: Automated best practices so that you can leerage prepackaged system administration expertise proided through predefined thresholds, persistence checking, and automated correctie actions A workbench so you can leerage your own best practices knowledge to create new resource models with a simple wizard-drien solution so you can expand monitoring capabilities beyond preconfigured resource models A health console that you can use to iew both real-time and recent historical data for any serer using a Web browser A foundation for application, database, and middleware monitoring that leerages adanced technology and extends monitoring capabilities across the IBM Tioli Monitoring components for applications, databases, and middleware IBM Tioli Monitoring Components IBM Tioli Monitoring on its own is a powerful technology, but the real alue of this product is the monitoring best practices knowledge that is shipped in the form of resource models. While the ability to build and customize resource models is seen as a ery important function, you might prefer to use that capability for extending existing resource models and pay for prebuilt monitoring solutions rather than inest in the skills and the time required to build them in-house. Tioli products contain monitoring solutions for specific applications or middleware. The IBM Tioli Monitoring for Databases product, for example, contains DB2 UDB, Oracle, and other components. The current set of components includes: IBM Tioli Monitoring for Databases (Oracle, DB2 UDB, Informix, Microsoft SQL Serer) IBM Tioli Monitoring for Messaging and Collaboration (Lotus Notes ) IBM Tioli Monitoring for Web Infrastructure (WebSphere, Weblogic, Apache, IIS, iplanet) IBM Tioli Monitoring for Business Integration (WebSphere MQ, WebSphere MQSI) IBM Tioli Monitoring for Applications (SAP, mysap.com, Siebel) IBM Tioli Monitoring for Operating Systems, part of the base IBM Tioli Monitoring product package (for Solaris, AIX, HP-UX, Windows, Linux, or OS/400 ) IBM Tioli Monitoring for Transaction Performance IBM Tioli Monitoring for Transaction Performance is focused on monitoring transactions across multiple systems. By collecting application resource measurement data from applications, the product can determine the location of performance problems. IBM Tioli Monitoring for Transaction Performance monitors both the end-to-end performance as perceied by end users of applications and the performance of the Appendix I. IBM Tioli Business Systems Management solution 221

240 steps that make up the transaction. This data is used to monitor and manage against serice leel agreements and can be extracted to the IBM Tioli Data Warehouse for reporting, capacity planning and further analysis. IBM Tioli Monitoring for Network Performance IBM Tioli Monitoring for Network Performance Version 2.1 allows IBM z/os operators to understand how TCP/IP protocol behaior on their monitored critical systems is affecting application performance. By distributing network monitors to all of your z/os images (across a sysplex, or your entire enironment) and consolidating collected information into a single database, it is easy for network system programmers and operators to get information about the entire enironment from a single location to compare notes or gain understanding of oerall performance within the data center. Integrated reporting using the IBM Tioli Data Warehouse allows isibility of historical trending data as well as enabling integrated reporting of z/os TCP/IP data with other information. Because System Network Architecture (SNA) is still critical in many customer enironments, IBM Tioli Monitoring for Network Performance includes Tioli NetView Performance Monitor (NPM) Version 2.7, proiding performance information for SNA networks. Customers using both tools hae performance coerage for both SNA and the TCP/IP enironments. IBM Tioli Monitoring for Network Performance Version 2.1 monitors, records, and interactiely reports network performance and utilization for TCP/IP resources in an enterprise enironment. It enables the timely analysis of performance-related metrics such as response time, traffic flow, and system workload, which can assist network tuning, problem determination, and alidation of serice leel agreements. IBM Tioli Monitoring for Network Performance enables you to specify threshold and rearm alues for generating eents when specific performance metrics indicate a problem in your network. Eents can be displayed on the IBM Tioli Enterprise Console and by IBM Tioli NetView for z/os. Tioli Monitoring for Network Performance meets your daily tactical needs as well as your long-term strategic systems management goals, proiding an effectie way to gain control of mission-critical network resources, performance issues, and workload distributions. 222 IBM Tioli Serice Leel Adisor: Getting Started

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

242 IBM can use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (I) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information might be aailable, subject to appropriate terms and conditions, including in some cases payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments might ary significantly. Some measurements might hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement might hae been estimated through extrapolation. Actual results might ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM s future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating systems. You can copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating system for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. 224 IBM Tioli Serice Leel Adisor: Getting Started

243 Trademarks IBM, the IBM logo, DB2, Lotus, Rational, Tioli, the Tioli logo, WebSphere, AIX, AS/400, CICS, DB2 Connect, DB2 Uniersal Database, DFS, eserer, IMS, Informix, iseries, MVS/ESA, NetView, OS/390, OS/400, Passport Adantage, pseries, Redbooks, S/390, Tioli Enterprise, Tioli Enterprise Console, VM/ESA, xseries, z/os, and z/vm are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a trademark of Linus Toralds in the United States, other countries, or both. Other company, product, or serice names may be trademarks or serice marks of others. Appendix J. Notices 225