Managing Server Installation and Customization Guide

Transcription

1 IBM Tioli Composite Application Manager for Application Diagnostics Version Managing Serer Installation and Customization Guide SC

2

3 IBM Tioli Composite Application Manager for Application Diagnostics Version Managing Serer Installation and Customization Guide SC

4 Note Before using this information and the product it supports, read the information in Notices on page 339. Edition Notice This 2015 edition applies to Version of IBM Tioli Composite Application Manager for Application Diagnostics and all subsequent releases and modifications until otherwise indicated in new editions. Some images in this document include the ersion number 7.1 but also apply to Version Copyright IBM Corporation 2006, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ix Tables xi About this publication xiii Intended audience xiii Related publications xiii Accessing terminology online xiii Accessing publications online xi Ordering publications xi Accessibility xi Tioli technical training x Support information x Conentions used in this publication x Typeface conentions x Variables for directories xi Where to begin xii Part 1. Introduction Chapter 1. Introduction Oeriew of the Deep Die infrastructure Oeriew of the Data Collector Oeriew of the Managing Serer Subdirectories under the MS_home directory.. 5 Part 2. Managing Serer on Windows 7 Chapter 2. Road map for installing the Managing Serer on the Windows operating system Installing the Managing Serer on seeral hosts.. 10 Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows System and software prerequisites What to do next Required tasks before installation Creating the installation user Custom installation and upgrade: creating the user interface user Existing database enironment: creating the schema user Maximizing font Resolution Host name and IP address for the Managing Serer Installation and configuration of Microsoft Serices for UNIX or Subsystem for UNIX-based Applications Embedded DB2 installation: Uninstalling an existing DB2 enironment on the local computer. 18 Creating an IBM WebSphere Application Serer instance for a Data Collector that is installed on the same computer as the Managing Serer.. 18 Adjusting for ports that are being blocked by your firewall or are being used by other applications (Optional) Gathering information that is required for the installation What to do next Chapter 4. Configuring an existing database enironment to work with the Managing Serer on a Windows operating system Preparing an existing DB2 enironment Installing and configuring the DB2 Client Application Enabler with a remote Relational Database Management System Preparing the remote DB2 Client Application Enabler for use with the Managing Serer Preparing connectiity for the DB2 client with a JDBC Type 2 drier Tuning the DB2 enironment What to do next Preparing an existing local Oracle enironment.. 26 Tuning the Oracle enironment What to do next Preparing an existing remote Oracle database enironment Preparing the remote Oracle enironment Installing JDBC libraries on the local serer Tuning the Oracle enironment What to do next Sample script for configuring existing databases.. 29 Sample SQL script for creating flexible table space in Oracle Chapter 5. Custom installation for the Managing Serer on Windows Notes about the installation Custom installation Postinstallation tasks Importing transaction data from Managing Serer to IBM Rational Performance Tester Enabling Configuration Management Database Discoery Library integration and executing the feature Manually creating database tables Configuring Simplified Chinese as the browser language Setting default browser resolution Network Deployment enironment: erifying and updating the irtual host port number What to do next Copyright IBM Corp. 2006, 2015 iii

6 Chapter 6. Silent installation for the Managing Serer on a Windows operating system Performing a three phase installation with three logins in Windows What to do next Performing a normal silent installation (in one phase) What to do next Executing the silent installation command Requirements for a response file Example of a modified response file template mirroring a Custom installation Example of a modified response file template mirroring a three phase installation (Managing Serer only) Configuration options Chapter 7. Upgrading and updating the Managing Serer on a Windows system 75 Unpacking the update Installing updates Preparing the Enironment Updating the Response File Preparing for the Installation Installing the update Cleaning the Prepared Installation Rolling Back a Failed Installation Uninstalling updates Preparing the Enironment Updating the Response File Preparing for uninstallation Uninstalling the update Cleaning the prepared uninstallation Rolling back a failed uninstallation Displaying installed updates Preparing the Enironment Updating the response file Displaying installed updates Details of configuration file merging Chapter 8. Customization and adanced configuration for the Managing Serer on Windows Creating additional instances of Managing Serer components Adding an additional kernel Adding additional Publish Serers Adding additional Archie Agents Split Managing Serer installation on Windows.. 90 Fine-tuning Managing Serer properties Tuning recommendations for large-scale enironments Enabling method signature tracing Setting up the reports Report Link and PDF feature Trap notification Setting up the Visualization Engine port for notifications Setting up SNMP Configuring a Managing Serer on a host with multiple network interfaces and NATs Adjusting maximum resource settings for the operating system Performance tuning the MSVE Assigning local Publish Serers to local Data Collectors to reduce WAN traffic in a split Managing Serer installation Creating additional users to log in to the ITCAM for Application Diagnostics Managing Serer Changing the user name and password for the database schema user Enabling the feature to launch into the IBM Tioli Enterprise Portal from the ITCAM for Application Diagnostics Managing Serer Using the Managing Serer with a 6.0 Data Collector Changing the IP address or host name of the Managing Serer Making sure that the Managing Serer host name connects to the correct IP address Sustaining large amounts of trace Starting ITCAM for Application Diagnostics automatically upon reboot Enabling a legal banner at login time Windows 2003 Serer: manually configuring the Managing Serer to run as a serice Windows 2003 Serer: unconfiguring the Managing Serer to run as a serice Chapter 9. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on Windows Uninstalling the Managing Serer Silent uninstallation of the Managing Serer on Windows Uninstalling a three phase installation on Windows 116 Manual uninstallation of IBM WebSphere Application Serer Manual uninstallation of IBM DB Part 3. Managing Serer on Unix and Linux Chapter 10. Road map for the Managing Serer on UNIX and Linux. 121 Installing the Managing Serer on seeral hosts 122 Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux. 125 System and software prerequisites What to do next Required tasks before installation Logging in as the root user Custom installation and upgrade: creating the user interface user i ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

7 Permissions for an existing IBM WebSphere Application Serer Existing database enironment: creating the Schema user Network Information Serice enironment: creating the DB2 account users Custom installation: creating the DB2 account users (optional) HP-UX and Solaris: kernel settings for IBM DB2 8.x HP-UX and Solaris: kernel settings for IBM WebSphere Application Serer HP-UX and Solaris with embedded IBM DB2: changing kernel configuration parameters set as formulas to integer alues HP-UX 11.23: enabling the local host alias Maximizing font resolution Host name and IP address for the Managing Serer Solaris: enabling links in LaunchPad Embedded IBM DB2 installation: uninstalling an existing IBM DB2 enironment on the local serer Creating an IBM WebSphere Application Serer instance for a Data Collector installed on the same serer as the Managing Serer Adjusting for ports being blocked by your firewall or being used by other applications (Optional) Gathering information required for the installation What to do next Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux Preparing an existing IBM DB2 enironment Installing and configuring the IBM Data Serer Client Package with a remote Relational Database Management System Preparing the remote IBM DB2 for use with the Managing Serer Preparing local DB2 on an AIX-based serer Preparing connectiity for the DB2 client with a JDBC Type 2 drier Tuning the IBM DB2 enironment What to do next Preparing an existing local Oracle database enironment Procedure What to do next Preparing an existing remote Oracle database enironment Preparing the remote Oracle database enironment Installing JDBC libraries on the local serer What to do next Sample scripts for configuring an existing database 146 Sample SQL script for creating flexible a table space in an Oracle database Chapter 13. Custom installation for the Managing Serer on UNIX and Linux Notes about the installation What to do next Custom installation steps Post-installation tasks Importing transaction data from Managing Serer to IBM Rational Performance Tester Enabling Configuration Management Database Discoery Library integration and executing the feature Manually creating database tables Configuring Simplified Chinese as the browser language Setting default browser resolution Network Deployment enironment: erifying and updating the irtual host port number What to do next Chapter 14. Silent installation for the Managing Serer on UNIX and Linux. 179 UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems What to do next Performing a normal silent installation (in one phase) What to do next Executing the silent installation command Requirements for a response file Example of a modified response file template mirroring a Custom installation Example of a modified response file template mirroring a three phase installation (Managing Serer only) Configuration options list Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems Unpacking the update Installing updates Preparing the Enironment Updating the Response File Preparing for the Installation Installing the update Cleaning Prepared Installation Rolling Back a Failed Installation Uninstalling updates Preparing the Enironment Updating the Response File Preparing for uninstallation Uninstalling the update Cleaning prepared uninstallation Rolling back a failed uninstallation Displaying Installed updates Preparing the Enironment Updating the Response File Contents

8 Displaying Installed updates Details of configuration file merging Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux. 213 Creating additional instances of Managing Serer components Adding an additional Kernel Adding additional Publish Serers Adding additional Archie Agents Split Managing Serer installation in Unix Fine-tuning Managing Serer properties Tuning recommendations for large-scale enironments Enabling method signature tracing Setting up the host Setting up the sender address Setting up the Visualization Engine port for notifications Setting up SNMP Rebuilding the HP-UX kernel Increasing the Linux kernel setting Configuring a Managing Serer on a host with multiple network interfaces and NATs Adjusting maximum resource settings for the operating system Assigning local Publish Serers to local Data Collectors to reduce WAN traffic in a split Managing Serer installation Creating additional users to log in to the ITCAM for Application Diagnostics Managing Serer Changing the user name and password for the database schema user Enabling the feature to launch into the IBM Tioli Enterprise Portal from the ITCAM for Application Diagnostics Managing Serer Using the Managing Serer with a 6.0 Data Collector Changing the IP address or host name of the Managing Serer Making sure that the Managing Serer host name gets resoled to the correct IP address Sustaining large amounts of trace Starting ITCAM for Application Diagnostics automatically upon reboot Setting up the Managing Serer to automatically configure Data Collectors Chapter 17. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on UNIX and Linux Managing Serer Silent uninstallation of the Managing Serer on Linux and UNIX systems Uninstalling a three phase installation on Linux and UNIX systems Manual uninstallation of IBM WebSphere Application Serer i ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide Manual uninstallation of IBM DB Part 4. Appendixes Appendix A. Obtaining installation images Appendix B. Using the LaunchPad interface Appendix C. Setting up security Setting up the user ID and password for the Data Collector with IBM WebSphere Application Serer Global Security enabled Node Authentication Script to run if your SSL certificates hae expired Node Authentication on the Managing Serer 250 Data Collector custom properties file changes 250 Node Authentication-related properties in the Port Consolidator Keystore management and populating certificates Secure Socket Layer communications Password encryption Properties file encryption Enabling Secure Socket Layer at the Data Collector leel Verifying secure communications Enabling priacy filtering Verifying priacy filtering Jaa 2 security in the application serer Running the Data Collector when Jaa 2 security is enabled Script to run if your SSL certificates hae expired 257 Appendix D. Language Packs for Managing Serer Installing a Language Pack on Windows Uninstalling a Language Pack on Windows Installing a Language Pack on Linux and UNIX systems Uninstalling a Language Pack on Linux and UNIX systems Appendix E. Starting and stopping the monitoring enironment Starting the Managing Serer Starting the Managing Serer on Windows Starting the Managing Serer on UNIX and Linux Launching the ITCAM for Application Diagnostics Managing Serer Stopping the Managing Serer Stopping the Managing Serer on Windows Stopping the Managing Serer on UNIX and Linux Tasks for specific Managing Serer components 269

9 Starting Managing Serer components Stopping Managing Serer components Verifying that Managing Serer components are up and running Disabling Data Collectors Re-enabling Data Collectors Restarting the application serer Restarting the application serer in a non-network Deployment enironment Restarting the application serer in a Network Deployment enironment Starting the application serer Starting the application serer in a non-network Deployment enironment Starting the application serer in a Network Deployment enironment Stopping the application serer Stopping the application serer in a non-network Deployment enironment Stopping the application serer in a Network Deployment enironment Starting the Oracle 9i database Starting the Oracle 10g database Appendix F. Maintaining the monitoring enironment Sample cron jobs HTTP serer log files IBM DB2 database tuning Performing database optimization IBM DB2 data maintenance Oracle database optimization Data Trimmer Additional database maintenance Appendix G. IBM Tioli Enterprise Console integration Requirements for integrating with Tioli Enterprise Console Configuring IBM Tioli Enterprise Console Configuring the IBM Tioli Enterprise Console serer Configuring the IBM Tioli Enterprise Console 292 Installing and configuring the IBM Tioli Enterprise Console SNMP Adapter for non-tme 292 Using the Managing Serer IBM Tioli Enterprise Console integration feature Appendix H. BMC Patrol integration 295 Requirements Configuring BMC Patrol Configuring the Patrol EM serer Generating the ITCAM for Application Diagnostics filter engine Defining the ITCAM for Application Diagnostics filter path Installing and configuring the Managing Serer SNMP Adapter Using Patrol EM with ITCAM for Application Diagnostics Appendix I. Managing Serer properties files aa1.properties e.properties dal.properties md.properties kl.properties ps1.properties sam1.properties landing.xml common.xml Appendix J. Using regular expressions Regular expression library Frequently used regular expressions Specifying exclusions with the bang (!) operator (Quality of Serice listening policies only) Appendix K. Setting up single sign-on into Visualization Engine for Tioli Enterprise Portal users Configuring LDAP using IBM Tioli Directory Serer Configuring Tioli Enterprise Portal Serer for single sign-on Configuring the Visualization Engine for single sign-on Configuring Lightweight Third Party Authentication Appendix L. Manually install MSVE 319 Check if the installation of MSVE is correct Appendix M. Accessibility Appendix N. Support information Searching knowledge bases Finding Release Notes Searching the information center on your local system or network Searching the Internet Obtaining fixes Receiing support updates Contacting IBM Software Support Determining the business impact of your problem Describing your problem and gathering background information Submitting your problem to IBM Software Support Index Trademarks Notices Contents ii

10 iii ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

11 Figures 1. Product architecture Copyright IBM Corp. 2006, 2015 ix

12 x ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

13 Tables 1. Default locations for MS_home xi 2. Default locations for DB2_home xi 3. Default locations for DC_home xi 4. Steps for installing the Managing Serer Naigation for creating the schema user Locations for the hosts file Websites with instructions to create an instance of IBM WebSphere Application Serer Default ports Users that must be created before or are created during the Custom installation Location of installation log files Specifying users when installing IBM DB Adanced options for an existing IBM DB Adanced options for an Oracle database IBM WebSphere Application Serer configuration for an existing installation Websites with instructions to create a web serer definition Location of installation log files Configuration options for the Managing Serer on Windows Trace leel settings for installation log files Runtime instances for the default Managing Serer IBM WebSphere Application Serer information entered during installation Configuration options for the Managing Serer on UNIX and Linux Steps for installing the Managing Serer Default temporary directories Typical kernel settings for running IBM WebSphere Application Serer Websites with instructions to create an instance of IBM WebSphere Application Serer Default ports Users that must be created before or are created during the Custom installation How to enable EXTSHM Location of installation log files Exporting the DISPLAY ariable Default temporary directories Location of IBM DB2 installation Specifying adanced options when installing IBM DB Scenarios Adanced options for an existing IBM DB Adanced options for an Oracle database IBM WebSphere Application Serer configuration for an existing installation where VE is installed on the Tioli Enterprise Portal Serer ewas IBM WebSphere Application Serer configuration for an existing installation where the VE is not installed on the Tioli Enterprise Portal Serer ewas Websites with instructions to create a web serer definition Default temporary directories Location of installation log files Configuration options for the Managing Serer on UNIX and Linux Trace leel settings for installation log files Default Managing Serer runtime instances How to export the DISPLAY ariable IBM WebSphere Application Serer information entered during installation Configuration options for the Managing Serer on UNIX and Linux Accessibility of remote installation images Accessibility of remote installation images Starting LaunchPad Naigation to JVM custom properties in the IBM WebSphere Application Serer administratie console Location of the CYND4051I message Classification of the data processed on the CommandAgent channel Launching the user interface Naigating to MS_home/bin Naigating to MS_home/bin Naigating to MS_home/bin Naigation to Custom Serices in the IBM WebSphere Application Serer administratie console Naigation to Generic JVM arguments in the IBM WebSphere Application Serer administratie console Naigation to Custom Serices in the IBM WebSphere Application Serer administratie console Naigation to Generic JVM arguments in the IBM WebSphere Application Serer administratie console Restarting ersion 6 or 7 application serers Restarting ersion 5 application serers Default serer names Starting ersion 6 or 7 application serers Starting ersion 5 application serers Default serer names Stopping ersion 6 or 7 application serers Stopping ersion 5 application serers Default serer names First step in starting the Oracle 9i database Database list commands Manual MSVE installation parameters Copyright IBM Corp. 2006, 2015 xi

14 76. Viewing all or only specific technotes Criteria for assessing the business impact of your problem xii ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

15 About this publication Intended audience Related publications Here is a list of related documents, which also proide useful information: IBM WebSphere Application Serer: Information about IBM WebSphere Application Serer is proided on the following Web site: IBM DB2 : Information about IBM DB2 is proided on the following website: IBM Tioli Enterprise Console : Information about IBM Tioli Enterprise Console is proided on the following website: IBM Tioli Data Warehouse: Information about IBM Tioli Data Warehouse is proided on the following website: com.ibm.tioli.tdwi.doc/toc.xml IBM Tioli Change and Configuration Management Database: Information about IBM Tioli Change and Configuration Management Database is proided on the following website: com.ibm.ccmdb.doc/ccmdb_ic.xml IBM Support Assistant: Information about IBM Support Assistant is proided on the following website: Accessing terminology online The Tioli Software Glossary includes definitions for many of the technical terms related to Tioli software. The Tioli Software Glossary is aailable at the following Tioli software library website: The IBM Terminology website consolidates the terminology from IBM product libraries in one conenient location. You can access the Terminology website at the following Web address: Copyright IBM Corp. 2006, 2015 xiii

16 Accessing publications online Ordering publications The documentation CD contains the publications that are in the ITCAM for Application Diagnostics library. The format of the publications is PDF, HTML, or both. 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 website. Access the Tioli documentation center at the following Web address: 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. All IBM Tioli product documentation can be accessed through the Tioli Documentation Central Wiki page at wikis/display/tiolidoccentral/home. You can order many Tioli publications online at the following website: pbi.cgi You can also order by telephone by calling one of these numbers: In the United States: In Canada: In other countries, contact your software account representatie to order Tioli publications. To locate the telephone number of your local representatie, perform the following steps: 1. Go to the following website: pbi.cgi 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that includes the telephone number of your local representatie. Accessibility 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 additional information, see Appendix M, Accessibility, on page 325. xi ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

17 Tioli technical training Support information For Tioli technical training information, refer to the following IBM Tioli Education website: If you hae a problem with your IBM software, you want to resole it quickly. IBM proides the following ways for you to obtain the support you need: Online Go to the IBM Software Support at the following website: Follow the instructions. IBM Support Assistant The IBM Support Assistant (ISA) is a free local software sericeability workbench that helps you resole questions and problems with IBM software products. The ISA proides quick access to support-related information and sericeability tools for problem determination. To install the ISA software, see the instructions for installing ISA in the Data Collector installation guide. Troubleshooting Guide For more information about resoling problems, see the troubleshooting guide for this product. Further support information For more information about accessing support, see the appendix on Support information. Conentions used in this publication This publication uses seeral conentions for special terms and actions, operating system-dependent commands, and paths. Typeface conentions This publication 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 (examples: titles of publications, diskettes, and CDs Words defined in text (example: a nonswitched line is called a point-to-point line) About this publication x

18 Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictie clause."; letters as letters example: "The LUN address must start with the letter L.") New terms in text (except in a definition list) a iew is a frame in a workspace that contains data. Variables and alues you must proide:... where myname represents... 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 Variables for directories This book refers to the following ariables: Table 1. Default locations for MS_home MS_home: the directory where the Managing Serer is installed. The following table lists the default locations: UNIX and Linux Windows /opt/ibm/itcam/websphere/ms C:\Program Files\IBM\itcam\WebSphere\MS AppSerer_home: the directory where the core products of the application serer are installed. The default is: MS_home/WAS7 Note: If there are multiple application serer installations in the same directory path, the path ends in a directory named after the particular application serer installation. In that case, for example, AppSerer_home is MS_home/WAS7/ appserer_instance. DB2_home: the directory where the IBM DB2 used by the Managing Serer is installed. For embedded installations with the Managing Serer, the following table shows the default locations: Table 2. Default locations for DB2_home UNIX (non-aix) and Linux IBM AIX Windows /opt/ibm/db2/v8.1 /usr/opt/db2_08_01 MS_home/DB2 DC_home: the directory where the Data Collector is installed. The following table shows the default locations for the ITCAM Agent for WebSphere Applications Data Collector: Table 3. Default locations for DC_home Windows UNIX and Linux ITM_HOME\tmaitm6\wasdc\ for example C:\IBM\ITM\TMAITM6\wasdc\ ITM_HOME/lpp263/yn/wasdc/ whereitm_home is: /opt/ibm/itm. For DC_home locations for the ITCAM Agent for J2EE Data Collector, see IBM Tioli Composite Application Manager: Agent for J2EE Data Collector Installation and Configuration Guide. xi ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

19 install_home: on z/os systems, the directory where the Data Collector is installed. The default location is /usr/lpp/itcam/websphere/dc. Note: This directory can be mounted as read only in daily use. config_home: on z/os systems, a read-write directory that is linked by a symbolic link to install_home. This is the directory in which you can modify the configuration of the Data Collector and where the runtime setup script registers its alues. The location of this directory is specified during the SMP/E installation, and its default is /u/itcam61/websphere/dc. Where to begin About this publication xii

20 xiii ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

21 Part 1. Introduction Copyright IBM Corp. 2006,

22 2 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

23 Chapter 1. Introduction IBM Tioli Composite Application Manager (ITCAM) for Application Diagnostics proides real-time monitoring and diagnostics for application serers. It also proides serer management functions, such as starting, stopping, and recycling application serers. The ITCAM for Application Diagnostics uses the Managing Serer infrastructure to proide detailed (deep die) diagnostic information. Oeriew of the Deep Die infrastructure The Deep Die infrastructure of ITCAM for Application Diagnostics has two main components: Data Collectors and the Managing Serer. Figure 1 displays a basic oeriew of how they interact. Figure 1. Product architecture Important: The Managing Serer connects and works with Data Collectors of the current ersion and all preious ersions, starting from ITCAM for WebSphere 6.1 and ITCAM for J2EE 6.1. It can also connect and operate with Data Collectors Copyright IBM Corp. 2006,

24 ersion 6.0 after additional configuration. See Using the Managing Serer with a 6.0 Data Collector on page 104 (on Windows systems) and Using the Managing Serer with a 6.0 Data Collector on page 229 (on Linux and UNIX systems). Oeriew of the Data Collector A Data Collector runs on each monitored application serer, and communicates essential operational data to the Managing Serer. Unique sampling algorithms maintain low CPU and network processor usage while proiding application-specific performance information. The Data Collector for WebSphere Applications is a component of ITCAM Agent for WebSphere Applications, and is installed by the agent installation program. See ITCAM Agent for WebSphere Applications Installation and Configuration Guide. The Data Collector for J2EE is a component of ITCAM Agent for J2EE. See ITCAM Agent for J2EE Data Collector Installation and Configuration Guide. Multiple Data Collectors can work with a single Managing Serer. The communication between Data Collectors and the Managing Serer is independent of platform. Oeriew of the Managing Serer The Managing Serer is a J2EE application. The Managing Serer collects information from, and proides serices to, the Data Collectors in your enironment. The Managing Serer relies on IBM WebSphere Application Serer and IBM DB2 or Oracle database serers, both of which can be installed either with or before installing the Managing Serer itself. The Managing Serer consists of the following components: Kernel The Kernel controls the Managing Serer. The Kernel registers components as they join the Managing Serer, periodically renews connections and registrations with components and Data Collectors, and collects serer and component aailability information. An additional copy of the Kernel can run on a Managing Serer for redundancy and failoer. The Watchdog is a lightweight component that manages a particular Kernel. If the Kernel does not respond, the Watchdog process restarts the Kernel. Each Kernel has its own Watchdog process. The Watchdog process must be on the computer where the Kernel is running. If both the Kernel and Watchdog do not respond, then the Kernel does not restart. You can check the Watchdog status by using the MS_home/bin/wdctl.sh status command. Visualization Engine The Visualization Engine proides the user interface. It can be accessed through Tioli Enterprise Portal, or used as a stand-alone option. The Visualization Engine requires IBM WebSphere Application Serer (Base or Network Deployment, ersion or aboe). A ersion of the WebSphere Application Serer can be installed by the Managing Serer installer. The Visualization Engine can also be installed on the WebSphere Application Serer instance that runs the Tioli Enterprise Portal. 4 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

25 Publish Serer The Publish Serer receies data from the Data Collector and aggregates it based on different needs. Archie Agent The Archie Agent collects data from the Publish Serer and archies it into the database for reporting. Message Dispatcher The Message Dispatcher sends out s about performance reports and trap actions from the Performance Analysis and Reporting and the Trap and Alert Management features. Global Publish Serer (GPS) The Global Publish serer tracks Composite Requests, as they moe from one serer to another. The Managing Serer is designed for scalability and load balancing. There are ways to design an installation across seeral serers. Similarly, the installation of IBM DB2 or Oracle databases used by the Managing Serer can be located on a different serer than the Managing Serer itself. For large-scale deployment, consult IBM Software Support for help in deciding before you attempt to install the Managing Serer. For information about receiing assistance from IBM Software Support, see Contacting IBM Software Support on page 329. Subdirectories under the MS_home directory _jm: contains a JRE used for Managing Serer uninstallation _uninst: contains the uninstall scripts backup: an empty directory resered for backup files for the MSVE WebSphere Application Serer settings bin: contains executable scripts etc: contains configuration files external: insttmp: contains files used for Managing Serer installation jars: contains library files used for Managing Serer installation and uninstallation lib: contains library files for Managing Serer lib6.1: contains libraries for Data Collector 6.1 lib7.1: contains libraries for ITCAM Agent for WebSphere 7.1 (including Data Collector) license: contains Managing Serer license files logs: contains Managing Serer log files generated by the components logiewer: contains JLog related files, including a log iewer (iewer.sh for UNIX and Linux or iewer.bat for Windows) to conert XML log files to text or HTML format file scripts: database scripts used for Managing Serer database installation, uninstallation, and upgrade Chapter 1. Introduction 5

26 6 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

27 Part 2. Managing Serer on Windows Copyright IBM Corp. 2006,

28 8 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

29 Chapter 2. Road map for installing the Managing Serer on the Windows operating system Complete the tasks for preparing to use the Managing Serer in the following order: 1. Verify that your computer meets the system and software prerequisites. See System and software prerequisites on page Install WebSphere Application Serer, which is required for the Managing Serer Visualization Engine. A serer ersion 7 or higher is required. You can download a licensed ersion of WebSphere Application Serer from the same source as the Managing Serer. Important: You can also choose to install the Managing Serer Visualization Engine on the Tioli Enterprise Portal Serer embedded IBM WebSphere Application Serer. If you choose this option, you must specify the IBM Tioli Monitoring home location during installation. From this location, the WebSphere information is automatically collected from the Tioli Enterprise Portal Serer configuration files. Use this option for testing enironments. 3. Choose the installation option that best meets the needs of your enironment: Custom: choose this option if you want to install the Managing Serer using an interactie wizard. Silent: choose a command-prompt interface instead of a graphical user interface to install the software, especially if you want to install one of the following options: Install in a demonstration enironment and then later in a production enironment using similar options You can complete a silent installation in three phases. The first phase installs Managing Serer files. The second phase deploys the Visualization Engine component and registers the configuration in IBM WebSphere Application Serer. In the third phase, you create database tables. You can use this option to install the Managing Serer files without haing to know the IBM WebSphere Application Serer user name and password, or to install the Visualization Engine on a separate host. Important: With both custom and silent installation, you can choose to install a DB2 database enironment for the use of the Managing Serer. This installation is called embedded DB2. Alternatiely, you can use an existing DB2 or Oracle database enironment for the Managing Serer. In this case, ensure that the enironment is fully aailable before installing the Managing Serer. Upgrade or update: choose this option if a preious ersion of the Managing Serer (ITCAM for WebSphere 6.1 or ITCAM for J2EE 6.1) is installed on the target computer. Also, for a new installation, choose this option after installing the Managing Serer ersion 7.1. Important: The remote command-prompt interface installation method is not supported. Often, if a remote command-prompt interface installation is attempted, the installer emits a message prompting you to use a console option in the command-prompt. You can ignore this prompt. Copyright IBM Corp. 2006,

30 4. Complete the tasks that are needed before installing the Managing Serer. See Required tasks before installation on page Access the installation software. See Appendix A, Obtaining installation images, on page Install the Managing Serer. Use one of the following options: Table 4. Steps for installing the Managing Serer Option Procedures to complete Custom 1. If you are using an existing DB2 or Oracle database enironment, Chapter 4, Configuring an existing database enironment to work with the Managing Serer on a Windows operating system, on page Custom installation on page 32 Silent Complete the following procedures to do a silent installation: 1. If you are using an existing DB2 or Oracle database enironment, Chapter 4, Configuring an existing database enironment to work with the Managing Serer on a Windows operating system, on page Chapter 6, Silent installation for the Managing Serer on a Windows operating system, on page 53 Upgrade or update Chapter 7, Upgrading and updating the Managing Serer on a Windows system, on page (optional) Set up security for the Managing Serer. See Appendix C, Setting up security, on page (optional) Perform customizations on the Managing Serer. See Chapter 8, Customization and adanced configuration for the Managing Serer on Windows, on page (optional) Install a language pack. See Appendix D, Language Packs for Managing Serer, on page Install and configure a Data Collector. Refer to one of the following publications: ITCAM Agent for WebSphere Applications Installation and Configuration Guide ITCAM for Application Diagnostics Agent for WebSphere Applications z/os Installation and Configuration Guide IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 11. After you start using this product to monitor your application serers, perform periodic maintenance on the Managing Serer. See Appendix F, Maintaining the monitoring enironment, on page 281. Installing the Managing Serer on seeral hosts To proide load balancing and optimize resource use, you can install the Managing Serer across up to four serers, using any combination of the following methods: You can run the Managing Serer Visualization Engine (user interface component) on a separate serer. In this case, only this host requires a full installation of IBM WebSphere Application Serer. To do this, use the three-phase silent installation process. See Performing a three phase installation with three logins in Windows on page 53. You can use a separate serer for the database management system (DB2 or Oracle). To use a separate serer, first install the database management system. Then, configure the database serer and the future Managing Serer host. See 10 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

31 Chapter 4, Configuring an existing database enironment to work with the Managing Serer on a Windows operating system, on page 23). Finally, use custom or silent installation to install the Managing Serer. You can use a split installation to spread the backend Managing Serer components (Kernel, Publish Serer, Archie Agent) among two hosts. To spread the backend Managing Serer components among two hosts, first install the Managing Serer on one host. Then, create the additional component instances (see Creating additional instances of Managing Serer components on page 87) and perform the split installation procedure to add the second host. See Split Managing Serer installation on Windows on page 90). Chapter 2. Road map for installing the Managing Serer on the Windows operating system 11

32 12 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

33 Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows Seeral prerequisite and preinstallation tasks must be completed before installing the Managing Serer. You must first erify that your computer meets the system and software prerequisites. See System and software prerequisites. System and software prerequisites The software and hardware requirements before installing ITCAM for Application Diagnostics are listed at the following website: knowledgecenter/ssdtfj_ /com.ibm.itcamfad.doc_7101/ prereqs_itcamad.html What to do next See Required tasks before installation. Required tasks before installation Complete the tasks in each of the following sections before you attempt to install the Managing Serer. Creating the installation user You can use the Administrator user as the user for completing the installation, or you can create a user. You must log in as this user to install a Managing Serer. Important: If you use a remote DB2 or Oracle database enironment, the same user must exist or be created on the computer where the DB2 or Oracle database enironment is installed. To create the installation user and the corresponding directory structure, complete the following procedure: 1. Log in as Administrator. 2. Depending on your operating system, create the installation user using the following instructions: For Windows XP, click Start > Control Panel > User Accounts For Windows 2000 Serer, Windows 2003 Serer and Windows 2008, click Start > Programs > Administratie Tools > Computer Management > Local Users and Groups > Users 3. Create the installation user (for example, amuser) and assign a password. You can also use Administrator instead of creating a user. 4. Create the local permissions for the user. The following requirements apply to this user: Cannot include the string ibm. For example, ibmuser Must hae membership in the Administrators group Must hae the priileges Act as part of the Operating System and Log on as a Serice. Copyright IBM Corp. 2006,

34 To erify or add these permissions, complete the following steps: a. Choose one of the following options: For Windows XP, click Control Panel > Administratie Tools > Local Security Policy > Local Policies > User Rights Assignment For Windows 2000 Serer, Windows 2003 Serer, Windows 2008, click Start > Programs > Administratie Tools > Local Security Policy > Security Settings > Local Policies > User Rights Assignment b. Add the user to these properties. Important: Adding the Administrators group to these properties is not enough to ensure the proper permissions. Make sure that this particular user is added to these properties. 5. Create the domain permissions for the user. The user must hae the following domain permissions: Must hae membership in the Domain Administrators group. Must hae the Act as part of the operating system priilege in the Domain security policy on the domain controller. 6. If you are completing an upgrade of the Managing Serer, this installation user must hae read/write priileges to the home directory for the preious ersion of ITCAM for Application Diagnostics. 7. If you chose to use Administrator as the installation user, you must log out of the system and log in again, or reboot your system. Custom installation and upgrade: creating the user interface user During the installation or upgrade, you must enter the user name for the user interface user. This user is a Windows user, who does the following tasks: Logging in to and using the IBM WebSphere Application Serer administratie console. Logging in to and using the ITCAM for Application Diagnostics Managing Serer Visualization Engine. (Although the Visualization Engine has a user management system of its own, the default user has the same user name and password as the product user). Complete the following procedure to create the user interface user: 1. You can choose one of the following options: Use the installation user as the user interface user. See Creating the installation user on page 13. Create a user interface user at this time. Complete the same steps as creating the installation user. (See Creating the installation user on page 13.) 2. When you are using an existing IBM WebSphere Application Serer 8.5.5, configure your user registry. (Authentication is controlled by IBM WebSphere Application Serer 8.5.5, not by the Managing Serer.) Complete the procedure at this website: com.ibm.websphere.base.doc/info/aes/ae/tsec_useregistry.html You must configure one of the following types of user registries: Federated repository Local operating system Stand-alone Lightweight Directory Access Protocol (LDAP) registry Stand-alone custom registry 14 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

35 Existing database enironment: creating the schema user During a custom installation using an existing database enironment, you must enter the name for the schema user. This user owns and can create the database tables for ITCAM for Application Diagnostics. To create a schema user, complete the following procedure: 1. Log in as Administrator. 2. Depending on your operating system, choose one of the following options: Table 5. Naigation for creating the schema user Windows XP Windows 2000 Serer, Windows 2003 Serer, Windows 2008 Start > Control Panel > User Accounts Start > Programs > Administratie Tools > Computer Management > Local Users and Groups > Users 3. Create the schema user. 4. This user must hae sufficient permissions to own and create database tables. Maximizing font Resolution For the English language ersion of the Managing Serer, set the resolution to at least 1024 x 768 with default toolbars. For non-english language ersions of the Managing Serer, set the resolution to 1280 x 1024 pixels. Click Control Panel > Display > Settings, and adjust the resolution if required. Host name and IP address for the Managing Serer The serer that the Managing Serer is installed on must hae a host name and IP address (in addition to using the loopback network connections local host and ). Installation and configuration of Microsoft Serices for UNIX or Subsystem for UNIX-based Applications To support Managing Serer scripts on Windows platforms, a UNIX shell enironment is required. Table 6. Locations for the hosts file If you hae Windows 2003 Serer with Serice Pack 1 (SP1), or an earlier ersion, you must install Microsoft Serices for UNIX (SFU). If you hae Windows 2003 R2 Serer, or a later ersion, you must install Subsystem for UNIX-based Applications (SUA). Installing and Configuring Microsoft Serices for UNIX To install and set up the SFU for the Managing Serer installer, complete the following procedure: 1. Log on as Administrator. 2. Check to see that a hosts file exists in one of the directories: Operating system Windows (except Windows 2000 Serer) Windows 2000 Serer Directory \WINDOWS\system32\driers\etc \WINNT\system32\driers\etc If one does not exist, download Microsoft Serices for UNIX at this website: Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows 15

36 3. Run the SFU setup.exe program. The SFU setup.exe program is prerequisite software. The first window for the installation program opens, displaying the Welcome panel. 4. Click Next. The Customer Information panel is displayed. 5. Verify the user information and click Next. The License and Support Information panel opens. 6. Read the license agreement, click to accept the agreement, and click Next. 7. Select Standard Installation and click Next. A panel that explains that setup needs to change low-leel default security settings is displayed. 8. Click Next. A panel for configuring the User Name Mapping Serer displays. 9. If you are in a Network Information Serice (NIS) enironment, select Network Information Serice. Otherwise, select Password and group files. Click Next. A second panel for configuring the User Name Mapping Serer is displayed. 10. Complete these steps: a. Verify the displayed Windows domain name. b. If you are in an NIS enironment, enter the NIS domain serer names. The NIS serer name is optional if the NIS serer is part of the same subnet as the local computer. c. If you are not in an NIS enironment, leae the fields for the password and group files blank. Click Next. SFU is installed in the C:\SFU directory. Important: If you receie an error message of the type Error! 26000, resole the problem according to instructions at the following location: Extend the system Path ariable to include the SFU utilities: a. Click My Computer > Properties > Adanced > Enironment Variables. b. When the Enironment Variable window opens, look at the lower half of the window (System Variables). Scroll down, select the Path ariable, and click Edit. Important: Be careful not to start typing right away. You must moe the cursor first; otherwise, the entire path ariable is erased. c. Moe the cursor all the way to the right to the end of the ariable statement and type the text: ;C:\SFU\bin;C:\SFU\usr\sbin Important: The statement must begin with a semi-colon (;). 12. Reboot your system. Tip: On Windows Serer 2003 R1, Windows Serices for Unix might not start correctly. In this case, install the fix aailable at the following location: 16 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

37 Installing and Configuring Subsystem for UNIX-based Applications Two steps are required to install and configure Subsystem for UNIX-based Applications (SUA): 1. Turn on the SUA features. 2. Install the Utilities and SDK for Unix-based Applications. Turning on the SUA features The Subsystem for UNIX-based Applications is part of the Windows OS distribution, so installing the subsystem requires no additional CD or download. It is a feature of the base distribution of Windows Serer 2008, Windows Serer 2008/R2, Windows Serer 2003 R2, Windows 7, Windows Vista Ultimate, and Windows Enterprise. To turn on the SUA component, complete the following steps: 1. In the Control Panel, select Programs and Features, then select Turn Windows Features On or Off or Add Features Wizard. SUA features are now added to the Start menu. 2. Scroll through the list presented in the next window and select Subsystem for Unix-based Applications. You might be prompted to enter the Windows OS disc 2 where psxss.exe is located. 3. Restart your computer. Tip: While SUA is part of Windows OS distributions, it is not always installed by default. You might need to install it manually, usually from Windows OS system disc 2. Do the following steps on your Windows system to install SUA: Control Panel > Add or Remoe Programs > Add/Remoe Windows Components on Windows 2003 R2. This example is for Windows Serer 2003 R2 Installing the Utilities and SDK for Unix-based Applications After the SUA feature is turned on, the next step is to download the Utilities and SDK. You can access the link to download the Utilities in either of the following ways: 1. Start >All Programs > Subsystem for Unix-based Applications, the link can be accessed from here. 2. Visit the download site directly: For Windows 2003 R2, details.aspx?familyid=8b4987e6-d960-49a2-bf52-d3fbd654254c For Windows Serer 2008 RTM and Windows Vista, f-a398-efde5758c47f For Windows Serer 2008 R2 and Windows 7, downloads/en/details.aspx?familyid=dc03485b-629b-49a6-b5ef-18617d1a9804 The page that is displayed is important because it outlines the difference between a standard (default) installation and a custom installation. A common error that occurs during Utilities and SDK installation is that users accept the default installation. The default installation does not include the GNU utilities and GNU SDK. To complete a custom installation, take the following steps: 1. In the Utilities and SDK for Subsystem for UNIX-based Applications wizard, click Next. 2. In the User name field, enter your name. If the name of your organization is not displayed in the Organization field, enter the name of your organization. Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows 17

38 3. Read the End User License Agreement. If you accept the terms of the agreement, click I accept the terms in the License Agreement, and then click Next to continue installation. If you click I do not accept the License Agreement (Exit Setup), the installation procedure ends. 4. To install default Utilities and SDK for UNIX-based Applications components in the default directory, click Standard Installation > Next. If you want to specify a different set of components or a different installation location, select Custom Installation, and then click Next. 5. Select the icon next to each component that you want to install, and then click the appropriate option. If you do not want to install a component, click the icon next to the component, and then click Entire feature will not be aailable. When you are finished specifying the components to install, click Next. 6. If you are installing the GNU Software Deelopment Kit (SDK), read the information about the GNU Library General Public License carefully. If you want to install the GNU SDK, click Next to continue installation. If you click Back, you hae another opportunity to select the components to install. 7. To apply these changes, restart your computer. For an oeriew of SUA, see: Embedded DB2 installation: Uninstalling an existing DB2 enironment on the local computer If you hae an existing DB2 enironment on the computer where you want to install the Managing Serer and you want to complete an embedded DB2 installation, you must either uninstall the DB2 enironment or choose another computer on which to install the Managing Serer. Creating an IBM WebSphere Application Serer instance for a Data Collector that is installed on the same computer as the Managing Serer To install the Data Collector on the same computer as the Managing Serer, you must create an IBM WebSphere Application Serer instance for the Data Collector. Follow the instructions at one of the following websites to create an instance of IBM WebSphere Application Serer: Table 7. Websites with instructions to create an instance of IBM WebSphere Application Serer IBM WebSphere Application Serer ersion 6.0.x (non-network Deployment enironment) 6.0.x (Network Deployment enironment) 6.1 (non-network Deployment enironment) 6.1 (Network Deployment enironment) URL com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html 18 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

39 Table 7. Websites with instructions to create an instance of IBM WebSphere Application Serer (continued) IBM WebSphere Application Serer ersion 7.0 (non-network Deployment enironment) 7.0 (Network Deployment enironment) URL com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html Requirement for a separate installation or profile of IBM WebSphere Application Serer You cannot install both the Managing Serer and Data Collector on the same installation and profile of IBM WebSphere Application Serer. Two separate IBM WebSphere Application Serer installations must be performed or two separate profiles within one installations must be created if you want to install both the Managing Serer and Data Collector on the same computer. IBM WebSphere Application Serer can be installed multiple times on the same computer, and a single installation supports multiple profiles. Adjusting for ports that are being blocked by your firewall or are being used by other applications You must specify or accept the defaults for port numbers used by ITCAM for Application Diagnostics, IBM WebSphere Application Serer or databases seeral times during the installation. You must choose one of the following options: Make sure that the ports listed in Table 8 are not blocked by your firewall or being used by other applications. Make a note of which ports are being blocked or used by other applications. Then later, during the installation, make sure that you do not accept a default that includes one of those ports. Consult the documentation for your firewall program to determine which ports are being blocked by your firewall. Run the following command to determine the ports that are already used by applications on your computer: netstat -a Here is a list of the default ports used by the installation: Table 8. Default ports Usage Port number IBM WebSphere Application Serer administratie 9060 console SOAP connector for IBM WebSphere Application Serer 8880 instance used by the Managing Serer DB Oracle 1521 Archie Agent Archie Agent Kernel Codebase 9122 Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows 19

40 Table 8. Default ports (continued) Usage Port number Kernel Remote File Sharing (RFS) 9120 Kernel Remote Method Inocation (RMI) 9118 Message Dispatcher 9106 Polling Agent 9111 Publish Serer Publish Serer Structured Application Monitor 9126 Visualization Engine 80, 9180 Connection between Managing Serer and Data Collector The ports that must be aailable depend on whether the Port Consolidator is enabled. Make the following ports aailable: If the Port Consolidator is enabled: 8800 If the Port Consolidator is not enabled, for each Data Collector that connects to the Managing Serer, one port from each of the following ranges: If you also hae IBM CICS or IBM IMS Data Collectors connecting to the Managing Serer: If you also hae IBM CICS or IBM IMS Data Collectors connecting to the Managing Serer: For more detailed information about enablement of the Port Consolidator, see the appendix in the Data Collector installation and customization guide. (Optional) Gathering information that is required for the installation You can prepare for the installation by gathering information that you must proide during the installation. A good example of the alues that you might hae to proide is located here: Configuration options on page 61. Users that are created before or during the installation The following tables contain lists of users that must be created before, or are created during the Custom installation: Table 9. Users that must be created before or are created during the Custom installation User Description Default Permissions When created Installation User when logging on Administrator Belong to the to perform the Administrators group Managing Serer installation Must hae the priileges: Act as part of the Operating System and Log on as a Serice Preinstallation procedure or can be the default (Administrator). See Creating the installation user on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

41 Table 9. Users that must be created before or are created during the Custom installation (continued) User Description Default Permissions When created DB2 Administration Serer User for DB2 Administration Serer account db2admin Has full DB2 priileges Must hae the following priileges: Act as part of the operating system Debug programs Create token object Lock pages in memory Log on as a serice Increase quotas Replace a process leel token DB2 Instance DB2 instance owner db2inst1 Must hae the following priileges: IBM WebSphere Application Serer User Interface Schema Oracle SQLPlus User that is used to start the IBM WebSphere Application Serer Windows serice and to connect to IBM WebSphere (Optional) User that is used for logging in to and using the ITCAM for Application Diagnostics Managing Serer Existing database enironment only: owns and can create the database tables for ITCAM for Application Diagnostics Existing Oracle enironment only: Oracle SQLPlus user The installation user The installation user None Act as part of the operating system Debug programs Create token object Lock pages in memory Log on as a serice Increase quotas Replace a process leel token Belong to the Administrators group Belong to the Administrators group Must hae the priileges: Act as part of the Operating System and Log on as a Serice Must be able to create database tables Embedded DB2: created during the installation Existing DB2: must exist preiously Embedded DB2: created during the installation Existing DB2: must exist preiously Existing IBM WebSphere Application Serer: must exist preiously Preinstallation procedure or can be the default (the installation user). See Custom installation and upgrade: creating the user interface user on page 14. Preinstallation procedure. See Existing database enironment: creating the schema user on page 15. Must exist preiously Chapter 3. Prerequisites and preinstallation tasks for the Managing Serer on Windows 21

42 Table 9. Users that must be created before or are created during the Custom installation (continued) User Description Default Permissions When created Oracle database administrator Existing Oracle enironment only: Oracle database administrator user Must exist preiously Determining the port number for an existing DB2 instance If you plan to use an existing DB2 enironment, you must know the port number for the DB2 instance before you enter DB2 configuration information during installation of the Managing Serer. To check the port number, complete the following procedure: 1. Open the DB2 Control Center (Start > All Programs > IBM DB2 > General Administration Tools > Control Center). 2. In the left pane, naigate to and right-click one of the aailable instances for the local system. 3. Select Setup Communications. 4. To the right of the TCP/IP choice, click Properties. The port number is listed in the Port Number field. What to do next Do one of the following options: If you are installing DB2 with the Managing Serer, start the installation. Refer to one of the following chapters: Chapter 5, Custom installation for the Managing Serer on Windows, on page 31 Chapter 6, Silent installation for the Managing Serer on a Windows operating system, on page 53 If you are using an existing DB2 or Oracle database enironment with the Managing Serer, configure the database serer to work with the Managing Serer. See Chapter 4, Configuring an existing database enironment to work with the Managing Serer on a Windows operating system, on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

43 Chapter 4. Configuring an existing database enironment to work with the Managing Serer on a Windows operating system You can customize the DB2 or Oracle enironment before you start to install the Managing Serer. Complete these steps only if you are using an existing DB2 or Oracle enironment with your Managing Serer. Otherwise, go directly to one of the installation chapters. See one or more of the following sections: For an existing local or remote DB2 enironment, see Preparing an existing DB2 enironment. For an existing local Oracle enironment, see Preparing an existing local Oracle enironment on page 26. For an existing remote Oracle enironment, see Preparing an existing remote Oracle database enironment on page 27. The existing DB2 or Oracle enironment can exist on the Managing Serer or a remote computer. Preparing an existing DB2 enironment To use an existing local or remote DB2 enironment with the Managing Serer, complete the following procedure. If the DB2 RDBMS serer is remote (that is, not the host on which the Managing Serer is running), perform the following tasks: On the host where the Managing Serer is running, install the DB2 Client Application Enabler. See Installing and configuring the DB2 Client Application Enabler with a remote Relational Database Management System. On the RDBMS host, create the Managing Serer database. See Preparing the remote DB2 Client Application Enabler for use with the Managing Serer on page 24. The following steps apply whether the RDBMS is running on the same host as the Managing Serer or on a different host: If you plan to use the JDBC Type 2 drier, prepare RDBMS connectiity for it; see Preparing connectiity for the DB2 client with a JDBC Type 2 drier on page 25 for more information. You do not hae to do this if you are using the JDBC type 4 drier (which is the default setting). Tune the DB2 enironment. See Tuning the DB2 enironment on page 25. Installing and configuring the DB2 Client Application Enabler with a remote Relational Database Management System Complete these steps only if the DB2 Relational Database Management System (RDBMS) is installed on a separate computer from the client (the Managing Serer). You must install the DB2 Client Application Enabler on the client computer and set up connectiity to DB2. Follow these guidelines: Copyright IBM Corp. 2006,

44 1. Ensure that there is no DB2 Client Application Enabler installation (either complete or partial) on the system. If an installation exists, uninstall it. 2. Customize the options to select Jaa database connectiity (JDBC). A JDBC drier is installed as part of the DB2 Client Application Enabler installation. 3. Ensure that approximately 2 MB are aailable in the selected home directory to accommodate the DB2 Client Application Enabler. Important: For DB2 ersion 10, you need more than 2 MB of disk space. For DB2 ersion 10, the disk space is checked dynamically at client installation time. The disk space required for your product depends on the type of installation you choose and the type of file system you hae. The DB2 Setup wizard proides dynamic size estimates based on the components selected during a compact or custom installation. Remember to include disk space for required software and communication products. Preparing the remote DB2 Client Application Enabler for use with the Managing Serer The following instructions describe how to prepare the DB2 enironment used by the Managing Serer when DB2 Client Application Enabler is installed on a different computer to the Archie Agent (a component of the Managing Serer). Within this section, the serers are referred to as follows: The serer on which the Visualization Engine (Application Monitor) and Archie Agent are installed is the local serer. The serer on which DB2 is installed is the remote serer. Important: In this scenario, you must install the DB2 Client Application Enabler on the local serer. Complete the following procedure to prepare the remote DB2 Client Application Enabler for use with the Managing Serer: 1. Install DB2 Client Application Enabler on the remote serer. Important: On the remote serer, create a user account, for example, amuser It must be the same user as the Managing Serer installation user. See the following section: Creating the installation user on page Log in as the DB2 Instance owner on the remote serer. 3. Create a temporary directory on the remote serer in which to place the DB2 installation scripts. Example: c:\temp 4. Use the FTP feature to copy the file db2-remote-scripts.zip file to the temporary directory that you created. Tip: The db2-remote-scripts.zip file is proided with the Managing Serer distribution in MS_installation_image_directory\base\scripts directory. 5. Extract the db2-remote-scripts.zip file. 6. Run the db2install.bat script. For example: cd c:\temp\db2\bin db2install.bat schema_user schema_password user_interface_user db2_instance_user db2_instance_password DB2ersion databasename where databasename is optional. 24 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

45 The schema_user user owns and can create the database tables for ITCAM for Application Diagnostics. The schema user user is the user you created in Existing database enironment: creating the schema user on page 15. Use the user_interface_user user for logging in and operating the Managing Serer Application Monitor after installation and configuration. This user is also specified during the Managing Serer installation. This is the user that you created in Custom installation and upgrade: creating the user interface user on page 14. If you do not specify the user_interface_user, you must specify the db2_instance_user. The db2_instance_user is the owner of the DB2 instance. The db2_instance_user was created when you installed DB2. For example, db2inst1. If you do not specify the db2_instance_user user, you must specify the user_interface_user. Preparing connectiity for the DB2 client with a JDBC Type 2 drier To prepare connectiity for the DB2 client if the JDBC Type 2 drier is to be used, complete the following procedure. If you plan to use the JDBC Type 2 drier, complete the following procedure, whether the DB2 RDBMS is located on the local serer or on a different (remote) serer. If you plan to use the JDBC type 4 drier (which is the default setting), this procedure is not mandatory. 1. Log in as a user with dba priileges, for example: db2inst1. Tip: For conenience, you might want to log in as root. In the following steps, you are starting a script that prompts for the password multiple times. These multiple prompts can be aoided if you run it as root. 2. Catalog the TCP/IP node pointing to the DB2 RDBMS serer node: db2 catalog tcpip node db2node remote Remote_Serer serer db2_listening_port For example, to connects the client with an RDBMS serer named ghost, which has the node name or alias ims_db2 and uses port 50000: db2 catalog tcpip node ims_db2 remote ghost serer Catalog the database on the node created: db2 catalog db database_name at node db2_node This must be the database name that is used for the Managing Serer. For example, to catalog the octigate database on the ims_db2 node, use the following command: db2 catalog db octigate at node ims_db2 4. Run the following command: db2 terminate Tuning the DB2 enironment Follow the tuning instructions described in the MS_installation_image_directory\ base\etc\db2-readme.txt file. What to do next Select one of the following options: Begin an installation of the Managing Serer with an existing DB2 enironment. Chapter 4. Configuring an existing database enironment to work with the Managing Serer on a Windows operating system 25

46 See Chapter 5, Custom installation for the Managing Serer on Windows, on page 31. Begin a silent installation of the Managing Serer. See Chapter 6, Silent installation for the Managing Serer on a Windows operating system, on page 53. Preparing an existing local Oracle enironment To use an existing local Oracle enironment with the Managing Serer, complete these tasks. Configuration tasks and requirements are used to set up an existing Oracle enironment that can be used to support the Managing Serer. The Oracle configuration tasks sere as a general guide to the basic requirements for setting up the enironment, not as comprehensie instructions. A database administrator might use a different approach. For detailed Oracle information, consult the Oracle documentation. To use an existing Oracle enironment you must create a database file manually. You must also hae a alid user name and password to gie you access to the required database for the Managing Serer. Complete the following procedure to prepare an existing local Oracle enironment: 1. Create an Oracle database with an SID name of octigate, using the following utility: dbca 2. Create sufficient table space for the management repository. Tip: One month of operational data might require a minimum of 10 GB. Your space requirements might ary, depending on your enironment and monitoring configuration. For test purposes, a smaller database (300 MB to 400 MB) is sufficient. 3. Create a user ID and password for the table space for which the user has authority to create and edit tables. 4. Configure a rollback segment using the Oracle default size for rollback segments. 5. Reiew the sample configuration scripts in Sample script for configuring existing databases on page 29 as a guide for creating your own script to configure your enironment. 6. Double-byte character enironments only: If your operating system is enabled for a single-byte character set, it does not automatically accept double-byte character sets. You must enable your Oracle enironment to store monitoring information that comes in double-byte character strings. The following sample command for creation of a database includes the CHARACTER SET UTF8 string (in bold text). This string enables storage of double-byte character sets: CREATE DATABASE 920u MAXINSTANCES 1 MAXLOGHISTORY 1 MAXLOGFILES 5 MAXLOGMEMBERS 3 MAXDATAFILES 100 DATAFILE C:\Oracle\oradata\920u\system01.dbf SIZE 200M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE C:\Oracle\oradata\920u\temp01.dbf 26 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

47 SIZE 10M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED UNDO TABLESPACE "UNDOTBS1" DATAFILE C:\Oracle\oradata\920u\undotbs01.dbf SIZE 50M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED CHARACTER SET UTF8 NATIONAL CHARACTER SET AL16UTF16 LOGFILE GROUP 1 ( C:\Oracle\oradata\920u\redo01.log ) SIZE K, GROUP 2 ( C:\Oracle\oradata\920u\redo02.log ) SIZE K, GROUP 3 ( C:\Oracle\oradata\920u\redo03.log ) SIZE K; Tuning the Oracle enironment For an Oracle Database 10g Standard/Enterprise Editions Release 1 instance, follow the tuning instructions that are described in the MS_installation_image_directory\base\etc\oracle10g-readme.txt file. What to do next Choose one of the following options: Begin an installation of the Managing Serer with an existing Oracle database enironment. See Chapter 5, Custom installation for the Managing Serer on Windows, on page 31. Begin a silent installation of the Managing Serer. See Chapter 6, Silent installation for the Managing Serer on a Windows operating system, on page 53. Preparing an existing remote Oracle database enironment When an Oracle database is installed on a different serer than the Archie Agent (a component of the Managing Serer), you can prepare the Oracle enironment that is used by the Managing Serer. This section describes configuration tasks and requirements for setting up an existing Oracle enironment that can be used to support the Managing Serer. The Oracle database configuration tasks described in this chapter sere as a general guide to the basic requirements for setting up the enironment, not as comprehensie instructions. A database administrator might use a different approach. For detailed Oracle database information, consult the Oracle documentation. To use an existing Oracle database enironment, you must create a database file manually. You must also hae a alid user name and password to gie you access to the required database for the Managing Serer. To use a remote Oracle database enironment with the Managing Serer, you must prepare the Oracle database enironment on the remote serer and install JDBC driers on the local serer. The serers are referred to as follows: Local Serer: The serer on which the Archie Agent is installed. Remote Serer: The serer on which the Oracle database enironment is installed. Preparing the remote Oracle enironment Complete the following procedure to prepare the remote Oracle database enironment: Chapter 4. Configuring an existing database enironment to work with the Managing Serer on a Windows operating system 27

48 1. Create the SID for use by the Managing Serer. Record the name of the SID; you can use the default name, octigate Important: If you use a SID name other than octigate, you must explicitly specify this name when you use a custom or silent installation to install the Managing Serer. 2. Create a temporary directory on the remote serer. Example: c:\temp 3. Use the FTP feature to moe the oracle-remote-scripts.zip file to the temporary directory. Important: The oracle-remote-scripts.zip file is proided with the Managing Serer distribution (in MS_installation_image_directory\base\scripts\). 4. Log in as a user with dba priileges. An example of a dba priilege is: oracle. 5. Extract the oracle-remote-scripts.zip file. 6. Run the following command to set the ORACLE_SID used by the Managing Serer: set ORACLE_SID=octigate If you use an SID name other than octigate, specify that SID name instead. 7. Run the oracleinstall.bat script, which has the following format: cd c:\temp\oracle bin\oracleinstall.bat oracle_sid sqlplus_user sqlplus_password tablespace jdbc_user jdbc_password adminveuser oracle_sid is the SID name that you created. sqlplus_user and sqlplus_password are credentials for Oracle SQL Plus. The user must hae priilege to create table space and users. You can specify the Oracle system user credentials. tablespace is the name of the table space that is created when you run the oracleinstall.bat script. This is the table space that the Managing Serer uses. This table space is remoed if it exists. jdbc_user and jdbc_password are credentials for the JDBC connection to the database. adminveuser is the operating system user that is used for the Visualization Engine component. This user is also the default administratie user in the Visualization Engine user interface. See Custom installation and upgrade: creating the user interface user on page 14. Installing JDBC libraries on the local serer Install the thin JDBC driers on the local serer. Tuning the Oracle enironment For an Oracle Database 10g Standard/Enterprise Editions Release 1 instance, follow the tuning instructions described in the file: MS_installation_image_directory/base/etc/oracle10g-readme.txt. What to do next Choose one of the following options: Begin an installation of the Managing Serer with an existing Oracle enironment. 28 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

49 See Chapter 5, Custom installation for the Managing Serer on Windows, on page 31. Begin a silent installation of the Managing Serer. See Chapter 6, Silent installation for the Managing Serer on a Windows operating system, on page 53. Sample script for configuring existing databases You can use the following sample scripts to configure a database repository for the Managing Serer in a test enironment. Do not use these scripts in a production enironment. The following script is aailable: Sample SQL script for creating flexible table space in Oracle. Sample SQL script for creating flexible table space in Oracle Instead of setting permanently fixed sizes for the table space and temporary data file, the following sample script uses the AUTOEXTEND function to enlarge these items as required. It automatically extends the table space (named $username) 5 MB at a time and the temporary data file 100 KB at a time. #!/bin/ksh if[$#-ne1] then echo "Usage: create_users.sh username" exit 1 fi username=$1 echo "Creating SQL file: /dbs1/create/"$username"_create.sql" touch /dbs1/create/"$username"_create.sql REM REM Execute the following SQL fragment as Oracle RDBMS user "sys": REM create tablespace ts_$username datafile /dbs1/ts_$username.dbf size 30M default storage ( initial 100K next 50K minextents 2 maxextents 120) offline; commit; create tablespace tmp_ts_$username datafile /dbs1/tmp_ts_$username.dbf size 3M default storage ( initial 100K next 50K minextents 2 maxextents 20) TEMPORARY offline; commit; alter tablespace ts_$username online; commit; alter tablespace tmp_ts_$username online; Chapter 4. Configuring an existing database enironment to work with the Managing Serer on a Windows operating system 29

50 commit; create profile profile_$username limit sessions_per_user 10 cpu_per_session unlimited cpu_per_call 6000 logical_reads_per_session unlimited logical_reads_per_call 100 idle_time 30 connect_time 480; commit; create user $username identified by $username default tablespace ts_$username temporary tablespace tmp_ts_$username quota unlimited on ts_$username profile profile_$username; commit; GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO $username identified by $username; commit; ALTER DATABASE DATAFILE /dbs1/ts_$username.dbf AUTOEXTEND ON NEXT 5M; commit; ALTER DATABASE DATAFILE /dbs1/tmp_ts_$username.dbf AUTOEXTEND ON NEXT 100K; commit; 30 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

51 Chapter 5. Custom installation for the Managing Serer on Windows Notes about the installation Table 10. Location of installation log files You can use the custom installation process to install ITCAM for Application Diagnostics using an existing database application and an existing IBM WebSphere Application Serer. You can also install the ersions of IBM DB2 or IBM WebSphere Application Serer that are included as part of the Managing Serer installation, you can specify adanced installation alues (such as existing users and passwords). View the installation notes before you begin. See Notes about the installation for more information. It is recommended that you read through the following list of notes about the installation before you begin: Notes: 1. Installation of IBM DB with the Managing Serer is called an embedded installation. 2. These instructions are written as if you hae downloaded the installation files from the IBM website. If you are installing the Managing Serer from CD-ROMs, additional windows prompting you to insert the required CD-ROMs are displayed. 3. The installer creates log files in the following directories: Managing Serer Embedded IBM DB2 C:\Program Files\IBM\tioli\common\CYN\logs My Documents directory of the installation user\db2log 4. If the installer detects an existing IBM DB2 enironment on this computer, you receie an error message before you can begin the installation. You are instructed to uninstall it from this computer or choose another computer to install the Managing Serer on. You must then exit the installation. 5. If installation of the Managing Serer or embedded IBM DB2 fails during the installation, you must exit the installation and then rerun the installer. The installation program automatically cleans up the installation directories for the components whose installations hae failed. If embedded IBM DB2 or IBM WebSphere Application Serer installations completed successfully, the installations remain intact. 6. The default password for all DB2 users created during an embedded installation is itcam The installer has three types of fields: Prefilled, editable: you can either accept the default that is proided or enter your own alue. Blank: you must enter a alue of your own. Prefilled, noneditable: you cannot change the proided alue. These fields are not mentioned in the steps that follow. Copyright IBM Corp. 2006,

52 Custom installation 8. The Managing Serer distribution includes IBM WebSphere Application Serer and a license is proided. You can download the license from the same site where you download the Managing Serer package. In order to install WAS 8.x, you must also download IBM Installation Manager, if you hae not downloaded it already. After you install IBM Installation Manager, you can use the IBM Installation Manager to install IBM WebSphere Application Serer You do not need to buy a WAS license separately. Complete the following step for a custom installation of the Managing Serer: 1. Log on to the computer (on which themanaging Serer is running) as the installation user, for example, amuser If you did not already create this user, see the following section: Creating the installation user on page If Terminal Serices is enabled on Windows 2003 Serer or Windows 2008 Serer, put the serer into installation mode. Run the following command from a command-prompt: change user /install Ignore the message: Install mode does not apply to a Terminal serer configured for remote administration. 3. Complete one of the following steps to start the installation: If you would like to open a window that inokes the installer, and gies access to prerequisite information, documentation, and support, use LaunchPad: a. Access LaunchPad. See Appendix B, Using the LaunchPad interface, on page 245. b. Click Install ITCAM, To directly start the installation without using LaunchPad, run setup_ms.exe from the directory that contains your installation image: 4. In the Select log path window, enter a location to store log files and click OK. 5. The Welcome window for the installation program is displayed. 32 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

53 Important: If the installation program detects that your computer lacks the basic prerequisites for starting the installation, a failure window opens instead of the Welcome window. Refer to the information displayed to correct the situation and restart the installation. 6. Click Next. The Reiew License Agreement pane is displayed. 7. Select I accept both the IBM and the non-ibm terms and click Next. The CD Install Selection panel is displayed. 8. Complete one of the following options: If you install from an image located on your hard disk, select No and click Next. If you install directly from a CD, select Yes so that the Managing Serer installation image can be copied to a temporary directory on your hard disk. This method clears the CD drie for the rest of the installation disks. Either accept the default temporary directory or browse to a different directory. The Managing Serer installation image requires at least 1 GB of space. Click Next. The Analyze System for Prerequisites panel is displayed. 9. This panel shows the process of analyzing your system for prerequisites and existing ersions of IBM WebSphere Application Serer and IBM DB2. Wait for the installation program to finish its analysis and then click Next. The Choose Installation Type panel is displayed. 10. Select Custom and click Next. The Choose Features panel is displayed. 11. Here are the features that you can select in the Choose Features panel: Managing Serer: This option is the default selection. The Managing Serer is installed in all circumstances. Visualization Engine: Select this feature if you are installing the Managing Serer on this computer. Clear this feature if you are running the installer program for creating database tables for an existing database enironment on this computer and the Managing Serer is being installed on a separate computer. Chapter 5. Custom installation for the Managing Serer on Windows 33

54 Database Tables: Select this feature if you are installing IBM DB2 or creating database tables for an existing database enironment on this computer. Clear this check box if you are using an existing remote database. Select the features you want to install. Click Next. The Choose Destination panel is displayed. 12. You now hae two choices: You can accept the default installation directory path that is in the Directory Name field and the click Next; or, you can change this path by typing or browsing to a different directory and then clicking Next. Important: a. You cannot install the Managing Serer in a directory path that contains non-english language characters. For example, characters from the following languages cannot be used: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters Cyrillic characters b. You must specify an empty directory. c. If you specify a directory that does not exist, the installation program creates the directory. 13. After completing the initial installation steps, the Enter TEPS information panel is displayed. To configure the Tioli Enterprise Portal Serer information, complete one of the following steps: a. To install database tables on the Tioli Enterprise Portal Serer DB2 database, select Install Database Tables on TEPS DB2 Database. 34 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

55 b. To install the Visualization Engine (Application Monitor) on the Tioli Enterprise Portal Serer embedded WebSphere Application Serer, select Install Visualization Engine on TEPS ewas. The Input ITM HOME field is displayed. c. Enter the path for ITM_home. Click Next. The Enter Database Information panel is displayed. 14. If you are installing IBM DB2 with the Managing Serer, complete the following procedure to install IBM DB2: Chapter 5. Custom installation for the Managing Serer on Windows 35

56 a. Select Install DB2. Table 11. Specifying users when installing IBM DB2 Important: If the installer detects an existing IBM DB2 enironment on this computer, you cannot install IBM DB2. To complete an embedded installation of IBM DB2 instead of using an existing database, you must uninstall the database from this computer or choose another computer on which to install the Managing Serer. You must exit the installation. b. In the DB Installation Image Location field, click Browse to select a location for the installation image. Browse to select the setup.exe file, which is commonly in the same directory as the db2 subdirectory. The installer installs IBM DB2 in the MS_home\DB2 directory. c. If you want to specify DB2 user names instead of accepting the defaults, select Show Adanced Options and complete one or more of the following fields: Important: The installation program automatically creates the users. You cannot use a preexisting user. Field Database Administrator User ID Database Administrator Password Database Instance User ID Database Instance Password Specify DB2 Installation Location Description DB2 Administration Serer user: this account has full IBM DB2 priileges. The user ID for the DB2 administration serer user is used to run the DB2 administration serer on your system. Password for DB2 Administration Serer user Database Instance user: the instance owner home directory is where the IBM DB2 instance is created. Password for DB2 Instance user Directory where IBM DB2 is installed. The default is C:\Program Files\IBM\itcam\ WebSphere\MS\DB2 36 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

57 To create user IDs and passwords, follow these guidelines: When creating a user ID, remember the following restrictions: User IDs are limited to 30 characters. User IDs are not case-sensitie. You cannot use USERS, ADMINS, GUESTS, PUBLIC, LOCAL. You cannot begin the user name with IBM, SQL, or SYS. You can use a combination of upper- and lowercase characters. Howeer, they are typically conerted to uppercase in IBM DB2. You can use the numbers 0 through 9. You can use the following special characters: #, $, Examples (These are the defaults): DB2 Administration Serer: dasusr1 DB2 Instance: db2inst1 When you create a password, remember the following rules: The general guidelines are the same as for the user name. Youcanuse1-8characters, without spaces. Do not begin the password with a number or an ampersand (&). Passwords are case sensitie. d. Click Next. 15. If you use an existing ersion of IBM DB2 with the Managing Serer, complete the following procedure to configure an existing IBM DB2 enironment: a. Select Use an Existing Database to configure the existing database. b. In the Database Selection menu, select the Existing IBM DB2 option. c. Local IBM DB2 only: type the name of the user of the IBM DB2 instance in the Database Instance User ID field. Chapter 5. Custom installation for the Managing Serer on Windows 37

58 Table 12. Adanced options for an existing IBM DB2 The name of the IBM DB2 enironment was configured when the IBM DB2 enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. d. Local IBM DB2 only: Type the password for the user that you entered in the preious step. The name of the IBM DB2 enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. Tip: If your passwords hae expired or you want to change the passwords, you must modify your password in MS_home\bin\seten.sh and in the IBM WebSphere data source. e. In the Database Schema User ID field, enter the user name for the IBM DB2 schema, for example, amuser. This user owns and can create the database tables for ITCAM for Application Diagnostics. f. In the Database Schema Password field, enter the password for the IBM DB2 schema. The password was determined when the IBM DB2 enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. Important: If your passwords hae expired or you want to change the passwords, you must modify your password in the MS_home\bin\seten.sh file and in the IBM WebSphere data source. g. Select the JDBC type to use. From the list, you can choose the following JDBC types: Type 2: JDBC type 2 Type 4: JDBC type 4 h. Verify the full path to the required Jaa DataBase Connectiity (JDBC) files or browse to and select the db2cc.jar file. For example, the db2cc.jar file might be located in the following path: c:\program Files\IBM\SQLLIB\ jaa\db2cc.jar. Tip: If IBM DB2 is installed on a remote computer, you can copy the directory containing the JDBC files (db2cc.jar and db2jcc_license_cu.jar) to the local computer, then browse to and select that directory. i. To specify adanced options (such as the location of a remote database), select Show Adanced Options and complete one or more of the following fields: Field Database Host Port Number Database Name Description Type the fully qualified host name or IP address of the computer on which the existing IBM DB2 enironment is installed. Type the port number used by the IBM DB2 instance. This is the port number for the instance identified in Step 15c on page 37. Do not accept the default port assignment (50000) if you hae assigned other applications to use that port number. Tip: You can discoer the correct port number to enter by completing the steps in Determining the port number for an existing DB2 instance on page 22, or you can consult your database administrator for the correct port to enter. Specify the database name. You can use any database name or the default name (octigate). 38 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

59 j. Click Next. Important: The installation program oerrides the current alues for the following parameters in the IBM DB2 serer and changes them: update dbm cfg using authentication serer; update dbm cfg using intra_parallel yes; update dbm cfg using query_heap_sz 2000; update dbm cfg using SHEAPTHRES ; update dbm cfg using FCM_NUM_RQB 768; update dbm cfg using MAXAGENTS 300; The DB2 administrator must make adjustments to ensure proper Data Collector configuration. Refer to the MS_home\etc\dbsettings.sql file for details. 16. To configure an existing Oracle database enironment, complete the following procedure: a. Select Use an Existing Database. b. In the Database Selection field, select Existing Oracle. c. In the SID field, enter the Oracle database system identifier number (SID) The SID is used to identify the Oracle database enironment. To find this alue, see the alue for the ORACLE_SID enironment ariable for the operating system. d. Local Oracle only: IntheDBA User ID field, enter the name of the Oracle database administrator. In the DBA Password field, enter the password for the DBA user ID. The name of the Oracle database administrator and the password were determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. Chapter 5. Custom installation for the Managing Serer on Windows 39

60 Important: If your passwords hae expired or you want to change the passwords, you must modify your password in MS_home\bin\seten.sh and in the IBM WebSphere data source. Note: The DBA User ID and DBA Password fields are only displayed if you selected Database Tables in the Choose Features panel. e. In the Database Schema User ID field, enter the user name for the Oracle database schema, for example, amuser. This user owns and can create the database tables for ITCAM for Application Diagnostics. In the Database Schema Password field, enter the password for the user you entered in the preious step. The database schema user ID and password were determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. Important: If your passwords hae expired or you want to change the passwords, you must modify your password in the MS_home\bin\seten.sh directory and in the IBM WebSphere data source. f. Local Oracle only: erify the full path to the Oracle database home directory. See the Oracle database profile for details. g. Local Oracle only: IntheOracle SQLPlus User field, enter the name of an existing Oracle SQLPlus user, for example,oracle The path was determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. Important: The Oracle SQLPlus User and Oracle SQLPlus User Password fields are only isible if you selected Database Tables in the Choose Features panel. h. Select the JDBC type to use. From the list, you can choose the following JDBC types: Type 2: JDBC type 2 Type 4: JDBC type 4 i. Verify the full path to the required Jaa DataBase Connectiity (JDBC) files or browse to and select the classes12.jar file. This directory contains JDBC libraries. Here is an example of a directory: C:\Program Files\oracle\product\10g\jdbclib\classes12.jar Tip: If an Oracle database is installed on a remote computer, you can copy the directory containing the JDBC files (db2cc.jar and db2jcc_license_cu.jar) to the local computer, then browse to and select that directory. j. To specify adanced options (such as specifying the location of a remote database), select Show Adanced Options and complete one or more of the following fields: 40 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

61 Table 13. Adanced options for an Oracle database Field Database Host Port Number Database Name Description Type the fully qualified host name or IP address of the computer on which the existing Oracle database enironment is installed. Do not include a protocol in the host name. For example, use myserer.ibm.tioli.com, not myserer.ibm.tioli.com Proide a port number in the Port Number field. Do not accept the default port assignment (1521) if you hae assigned other applications to use that port number. Consult your database administrator for the right port to enter. Specify the database name. You can use any database name or the default name (octigate). k. Click Next. 17. After completing the steps to set up your database enironment, the Enter WebSphere Application Serer Information panel is displayed. If you are using an existing WebSphere Application Serer, complete the following procedure: a. Ensure that IBM WebSphere Application Serer is installed on the Managing Serer computer. b. Select Use an existing IBM WebSphere Application Serer. The software searches for an installation of IBM WebSphere Application Serer. It then displays a list of discoered IBM WebSphere Application Serer instances. c. Complete the following steps: Select the IBM WebSphere Application Serer instance on which to install the Managing Serer. If the IBM WebSphere Application Serer instance on which to install the Managing Serer was not detected, you can specify another instance of IBM WebSphere Application Serer by completing the following steps: 1) Select Manually specify an Application Serer Node. 2) In the Application Serer Node Installation Directory field, browse to select the AppSerer_home directory. 3) Select the instance in the refreshed list of discoered IBM WebSphere Application Serer instances. Important: You cannot choose an IBM WebSphere Application Serer instance in a directory path (including profile, cell, node, and serer names) that includes the following non-english language types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters d. Click Next. Chapter 5. Custom installation for the Managing Serer on Windows 41

62 The Existing WebSphere Application Serer Information panel is displayed. e. To specify your IBM WebSphere Application Serer configuration, enter the following information: Table 14. IBM WebSphere Application Serer configuration for an existing installation Field Host Name SOAP Connector Port User Name Password User Interface User What to do Type the fully qualified host name or IP address of the IBM WebSphere Application Serer where the Managing Serer is running. If using Network Deployment, proide the host name of the Deployment Manager instead. Enter the SOAP port setting (The default is 8880). This connector port is used by the IBM WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). The SOAP port is identified in the AppSerer_home\profiles\ profile_name\config\cells\cell_name\nodes\node_name\sererindex.xml file of the instance of IBM WebSphere Application Serer that the Managing Serer uses. If using Network Deployment, proide the SOAP port of the Deployment Manager instead. Type the name of the user that runs IBM WebSphere Application Serer. This user must be a member of the Administrators group. It can be the same as or hae the same permissions as the installation user, as described in Creating the installation user on page 13. Type a user password. To change the default, select Show Adanced Options and enter the name that you want for the user that logs in to and uses the ITCAM for Application Diagnostics Managing Serer. The default is the installation user. If it is different from the installation user, make sure that user has the proper permissions. See Custom installation and upgrade: creating the user interface user on page 14. f. Click Next. The Select WebSphere Application Serer panel is displayed. 42 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

63 g. Naigate to select the serer, and click Next. 18. After completing the steps to set up your IBM WebSphere Application Serer, the Enter Managing Serer Information panel is displayed. Complete the following final installation steps: a. Enter the fully qualified host name or IP address of the serer where you want to install the Managing Serer. If memory resources on one Managing Serer are insufficient for your enironment, consider using a split Managing Serer implementation, for example, if you want the Managing Serer to connect to many Data Collectors (such as 500 or more). See Split Managing Serer installation on Windows on page 90 for instructions on how to install the Managing Serer on two separate computers. Chapter 5. Custom installation for the Managing Serer on Windows 43

64 b. To change the default port numbers used by the Managing Serer components, select Show Adanced Options and edit the alues. Accept each proided alue unless the port number is used already. Click Next. The Generate Response File panel is displayed. c. If you want to install the Managing Serer on this computer, make the selection to install it on this computer. You might not want to install the Managing Serer on this computer if you are performing the installation procedure only to create a response file for a subsequent silent installation. To create a response file for a subsequent silent installation, select Sae the settings in a response file and enter the file path ending with a file name, for example, C:\temp\response.opt A response file is generated only if the GUI installation completes successfully.click Next. The Reiew Installation Information panel is displayed. 44 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

65 Postinstallation tasks d. Read the summary information and click Install to accept it and begin the installation. The Install and Configure Files panel is displayed. e. The installer installs the Managing Serer and (if specified in the preious windows) IBM DB2 or IBM WebSphere Application Serer. Notes: 1) The progress bar might appear stuck at a certain position for a long time during the installation. This is to be expected, especially for embedded IBM DB2 installations. Allow the installation to continue. 2) Depending on the performance of your computer and operating system, installation might take longer than an hour. When the installation in complete, the Reiew Installation Summary panel is displayed. Important: If the summary panel displays one of the following messages, you must install database tables manually: Problems exist in the communication between the Managing Serer and the database. Installation of the database tables failed or is incomplete. In this case, see Manually creating database tables on page 49. f. Read the information in the panel and click Next. The Finish panel is displayed. g. To do postinstallation tasks at this time (recommended), select both Launch the Managing Serer and Launch the User Interface. h. Click Finish. Complete the following post-installation procedure: Chapter 5. Custom installation for the Managing Serer on Windows 45

66 1. Restart the instance of IBM WebSphere Application Serer that is to be used by the Managing Serer. See Restarting the application serer on page If you hae installed a web serer, configure it to forward requests to the Managing Serer by regenerating the web serer plug-in. Complete the following procedure: a. Create a web serer definition. Follow the instructions at one of the following websites: Table 15. Websites with instructions to create a web serer definition IBM WebSphere Application Serer ersion 7.0 (non-network Deployment enironment) 7.0 (Network Deployment enironment) 8.0 (non-network Deployment enironment) 8.0 (Network Deployment enironment) (non-network Deployment enironment) (Network Deployment enironment) URL com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/ae/tpro_instancessaappser.html?lang=en com.ibm.websphere.nd.doc/ae/tpro_instancessaappser.html?lang=en b. In the IBM WebSphere Application Serer administratie console, click Serer > Web serers. c. Select the Web serer check box. d. Click Generate Plug-in. e. Restart the Web serer. 3. If you completed a GUI installation and you did not select Launch the Managing Serer and Launch the User Interface on the last step of the installation, start the Managing Serer and the ITCAM for Application Diagnostics Managing Serer. See Starting the Managing Serer on page If you completed a silent installation or upgrade, start the ITCAM for Application Diagnostics Managing Serer. If you did not enable the option to start the Managing Serer, first start the Managing Serer. See Starting the Managing Serer on page Verify that the Managing Serer components are enabled and running. See Verifying that Managing Serer components are up and running on page Complete the tasks described in each of the following sections, if applicable. 7. If Terminal Serices is enabled on Windows 2000 or Windows 2008 Serer, run the following command from a command prompt: change user /execute Importing transaction data from Managing Serer to IBM Rational Performance Tester Problem Analysis tools in IBM Rational Performance Tester (RPT) can process and analyze transaction data from ITCAM for Application Diagnostics through a web 46 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

67 serice. ITCAM for Application Diagnostics supports RPT ersion 7.x and 8.x. To see ITCAM data in RPT, create application traps with method trace data action in MSVE. For the Managing Serer to work with RPT, complete the following steps: 1. For information about RPT and how to install it, see the following website: 2. If you hae installed the Managing Serer with an existing IBM WebSphere Application Serer 6.1, enable IBM WebSphere Global Security manually: a. Log in to the IBM WebSphere Application Serer administratie console. b. Click Security > Secure administration, applications, and infrastructure > Application security. c. Select Enable Application Security. d. Click Apply. e. Sae your changes. For all existing IBM WebSphere Application Serer installations except ersion 6.1, IBM WebSphere Global Security was automatically enabled during Managing Serer installation. 3. Enable method signature tracing. See Enabling method signature tracing on page 221. In RPT, take the following steps to import transaction data from Managing Serer to RPT: 1. Start IBM Rational Performance Tester Full Eclipse. From the File menu, select Import. 2. In the Select window, select Response Time Breakdown Data and click Next. 3. In the Location window, take the following steps: a. In the Monitoring Serer section, enter MSVE host name in Host field. b. In the Authentication section, enter the MSVE user and password. c. In the Connection section, select Use port and enter the MSVE port number, click Next. 4. In the Constraints window, specify the period for which you want to import data, click Next. 5. In the Trap window, select a trap to see method trace data. Enabling Configuration Management Database Discoery Library integration and executing the feature ITCAM for Application Diagnostics has a feature that can extract releant resources and relationships from ITCAM for Application Diagnostics database to be retrieed and stored by the Configuration Management Database (CMDB), which is the central source of information in the IT Infrastructure Library (ITIL). This feature produces XML files from the monitoring information contained within ITCAM for Application Diagnostics database. The CMDB Discoery Library can then store these XML files in its warehouse of IdML book files. Only CICS/IMS related transaction information is exported into the CMDB. The CMDB documents that are referred to in this section are located at the following website: index.jsp?toc=/com.ibm.ccmdb.doc/ccmdb_ic.xml Chapter 5. Custom installation for the Managing Serer on Windows 47

68 Complete the following procedure to enable and use this feature: 1. Make sure that the computer where the Managing Serer is installed has write access to the file system that contains the CMDB Discoery Library repositories of IdML book files. 2. (optional) Copy the file MS_home\etc\cmdb\TCAMfWAS.zip to a new directory. 3. Extract the file into the current directory. 4. Modify the adapter.properties file to reflect the settings for your Managing Serer. See the comments in the file for instructions for modifying the file. 5. Modify the script in that directory (dladapter.bat) to point to the location of the database JDBC driers (.jar files) for your Managing Serer. 6. Modify the dladapter.bat file to hae the correct Jaa path for the Jaa files on your Managing Serer. 7. From the directory that contains the dladapter.bat file, run the following command: dladapter.bat [-erbose -extremelyverbose] [configfile] The configfile is the full path and file name of the modified adapter.properties configuration file. If you changed the name of the file or saed it to another directory, you must enter a alue for this option. The -erbose option indicates a detailed tracing leel (for debugging). It is the equialent of DEBUG_MID. Do not use this option without the guidance of Leel 3 IBM Software Support. The -extremelyverbose option indicates a detailed tracing leel that requires large amounts of disk space. It is the equialent of DEBUG_MAX. Do not use this option without the guidance of Leel 3 IBM Software Support. Important: a. If you run the script with no options, you can click the file from Windows Explorer to run it. b. The monitoring information must first be aailable in ITCAM for Application Diagnostics database before the Discoery Library Adapter can produce the XML files. 8. Load the XML files from a shared directory into the CMDB serer using the bulk load program. See the Configuration Discoery and Tracking User's guide for information about using the bulk load program. 9. Extract the contents of MS_home\etc\ITCAMSIMRegistration.zip into the CMDB_home/bin directory on the CMDB serer. 10. Register the System Integration Module (SIM) on the CMDB serer. See the instructions in ITCAMSIMRegistration.README file from the unpackaged.zip file. 11. Associate the SIM with a Management Software Systems (MSS): a. Use a web browser on any host to access the CMDB portal. b. Click the small Log In item in the upper-right corner and log in. c. Click the small ISC item in the upper-right toolbar. A welcome window is displayed. d. Under the ITSM System Administration heading, select Configure System Integration Module. A table of Integration Modules (IMs) is displayed. e. Select the radio button next to the ITCAM for WebSphere Application Serer System Integration Module table row, then click Manage SIM to MSS Associations located aboe the table. An MSS table is shown. 48 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

69 f. Select the radio button next to the table row that has the following attributes: ManufacturerName=IBM ProductName=IBM Tioli Composite Application Manager for Websphere+Product Version=6.1 g. Click the Associate SIM to MSS button located aboe the table. 12. View status using the SIM: a. Click the small ISC item in the upper-right toolbar. A welcome window is displayed. b. Under heading Aailability Management, select Determine Business Impact. A search wizard window is displayed. c. In the Aailable Types drop list, select Business Process, then click Search. A table of business processes is displayed. d. Select the /cyanea_one/testware/dsstateful display name from business processes table and click Next. There is a table containing the status for the Data Collector. Manually creating database tables If during the Managing Serer installation, the database tables fail to install, this is indicated by messages in the Managing Serer installation summary panel. The summary information displays one of the following messages: There are problems in the communication between the Managing Serer and the database Installation of the database tables failed or is incomplete The problem occurs when you select Database Tables as a feature to install during a Custom Managing Serer installation. (The only time when you would not select Database Tables as a feature to install is when you are using an existing remote database.) If the Managing Serer files hae been successfully installed, but installation of the necessary database tables has failed, you can manually create the database tables. Manually creating DB2 tables If your database is DB2, complete the following procedure: 1. Extract the db2-remote-scripts.zip file from the MS_installation_image_directory\base\scripts directory into a temporary directory. 2. Run the db2install.bat script. For example: cd c:\temp\db2\bin db2install.bat schema_user schema_password user_interface_user db2 _instance_user db2_instance_password db2_ersion 1. schema_user user owns and can create the database tables for the product. If you installed DB2 with the Managing Serer, this user is the DB2 instance user, which is by default db2inst1 with a password of itcam610. (If you installed DB2 while performing a Custom installation, you can hae specified a different user from the default.) If you are using an existing DB2, this user was specified during the Managing Serer installation. 2. user_interface_user is the user that is used when logging in and operating the Managing Serer's ITCAM for Application Diagnostics Managing Serer after installation and configuration. This alue is the installation user (default) or a Chapter 5. Custom installation for the Managing Serer on Windows 49

70 alue you entered during the Managing Serer installation. If you do not specify this user when running this script, you must specify the db2_instance_user. 3. db2_instance_user is the owner of the DB2 instance. This user was created when you installed DB2. For example,db2inst1 If you do not specify this user, you must specify the user_interface_user. Manually creating Oracle database tables If your database is Oracle, complete the following procedure: 1. Extract the oracle-remote-scripts.zip file from the MS_installation_image_directory\base\scripts directory into a temporary directory. 2. Run the following command to export the ORACLE_SID used by the Managing Serer: export ORACLE_SID=octigate 3. Run the oracleinstall.bat script, which has the following format: cd c:\temp\oracle bin\oracleinstall.bat oracle_sid sqlplus_user sqlplus_password tablespace jdbc_user jdbc_password user_interface_user 1. oracle_sid is used to identify the Oracle database enironment. To find this alue, see the alue for the ORACLE_SID enironment ariable for the operating system. 2. sqlplus_user was determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. 3. tablespace is the name of the table space that is created when you run the oracleinstall.bat script. This is the table space the Managing Serer uses. This table space is remoed if it exists. 4. jdbc_user is the schema user. The schema user is the user that the Managing Serer uses to connect with Oracle, using JDBC. This schema user must exist in the local operating system. The schema user was specified during the Managing Serer installation. 5. user_interface_user is the user that will be used when logging in and operating the Managing Serer's ITCAM for Application Diagnostics Managing Serer after installation and configuration. This alue is the installation user (default) or a alue you specified during the Managing Serer installation. Configuring Simplified Chinese as the browser language If the browser language is set to Simplified Chinese, in the AppSerer_home\ properties\encoding.properties file, edit the property for zh by changing zh=gb2312 to zh=utf-8. Setting default browser resolution To iew the ITCAM for Application Diagnostics Managing Serer Visualization Engine, when the user's language is English, set the default browser resolution to 1024 X 768. For all other languages, set the browser resolution to 1280 X Network Deployment enironment: erifying and updating the irtual host port number For a Network Deployment enironment, you must erify and (if required) update the irtual host port number in the IBM WebSphere Application Serer administratie console. 50 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

71 Complete the following procedure: 1. Find the port number in the following file: AppSerer_home\profiles\ profile_name\config\cells\cell_name\nodes\node_name\sererindex.xml. Look for WC_defaulthost. 2. Log in to the IBM WebSphere Application Serer administratie console. 3. Expand Enironment on the left menu and click Virtual Hosts > default host > Host Aliases. 4. Verify that the port number discoered in Step 1 exists. 5. If it does not, create the port in the irtual hosts file by clicking New and proiding the host name as *. 6. Enter the port number and sae the configuration. What to do next Complete the following procedures: 1. Restart the instance of IBM WebSphere Application Serer that is to be used by the Managing Serer. See Restarting the application serer on page Choose one of the following options: Set up security for the Managing Serer. See Appendix C, Setting up security, on page 247. Complete customizations of the Managing Serer. See Chapter 8, Customization and adanced configuration for the Managing Serer on Windows, on page 87. Install a language pack. See Appendix D, Language Packs for Managing Serer, on page Install and configure a Data Collector. See one of the following publications: IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide IBM Tioli Composite Application Manager for WebSphere (z/os): Data Collector Customization Guide Note: Before configuring a Data Collector on IBM z/os, it must be installed. See the Program Directory for IBM Tioli Composite Application Manager for WebSphere (z/os). IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 4. After you start using this product to monitor your application serers, perform periodic maintenance on the Managing Serer. See Appendix F, Maintaining the monitoring enironment, on page 281. Chapter 5. Custom installation for the Managing Serer on Windows 51

72 52 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

73 Chapter 6. Silent installation for the Managing Serer on a Windows operating system Instead of installing the Managing Serer with a GUI installer, you can use a command-prompt command that uses a response file. This silent installation requires no user interaction. It references a response file that is located on a hard disk in the network, which contains most or all of the specifications for the installation. You might want to use a response file for the following reasons: You can reuse the response file for multiple installations. The response file preseres configuration data for an installation, so that you can identify configuration details at a later date. You usually perform the silent installation by running it once from a command-prompt, but you can also complete a silent installation in three phases. In the first phase, you install the Managing Serer files. The second phase you deploy the ITCAM for Application Diagnostics Managing Serer component and register the configuration in IBM WebSphere Application Serer. In the third phase, you assign database permissions. You can use this option to install the Managing Serer files without haing to know the IBM WebSphere Application Serer user name and password. For the silent installation that is completed in one phase, the configuration options for installing the Managing Serer are listed below. You modify the configuration options either in the response file or at the command-prompt to run the silent installation. Begin this chapter at one of the following sections: If you are completing a silent installation in three phases, see Performing a three phase installation with three logins in Windows. If you are completing a normal silent installation (performed in one phase), see Performing a normal silent installation (in one phase) on page 56. Performing a three phase installation with three logins in Windows You can complete a three phase Managing Serer installation using three different users. The users are: Managing Serer installation: the Managing Serer (MS) installation user. Managing Serer Application Monitoring user interface (Visualization Engine, VE) installation: the WebSphere user. Database instance: the database administrator user. With this process, you can install the Visualization Engine on a separate serer to make more resources aailable for it. You cannot install the Visualization Engine and the other Managing Serer components on the same serer with different users. If you install the Visualization Engine on a separate serer, you only hae to install the WebSphere Application Serer on the Visualization Engine serer and not on Copyright IBM Corp. 2006,

74 the serer where the Managing Serer files were installed (called the main serer in this chapter). Howeer, you must copy the jaa directory from the Visualization Engine serer to the main serer. The following three phases are inoled in this process: First Phase: In this phase, you log on as the Managing Serer installation user and install the Managing Serer files. Second Phase: In this phase, you log on as the WebSphere user, deploy the ITCAM for Application Diagnostics Managing Serer component, and register the configuration in IBM WebSphere Application Serer. Third Phase: In this phase, you log on as the database instance user (DB2 or Oracle) and gie the user write and execute access permission to db2-remote-scripts.tar or the oracle-remote-scripts.tar. The following procedure describes the steps that are inoled in a three phase installation: 1. To prepare for the three phase installation, complete the following steps: a. Ensure that WebSphere Application Serer ersion or higher is installed with Global Security enabled. b. Before installing the Managing Serer, copy the installation image to the serer where you intend to perform the installation. To hold the installation image, create the following directory: Managing_Serer_installation_image_directory. c. Specify configuration options in one of the response file templates Managing_Serer_installation_image_directory/silent/MS_Sample.opt or Managing_Serer_installation_image_directory/silent/MS.opt. For more details, see the following sections: Requirements for a response file on page 58 Example of a modified response file template mirroring a three phase installation (Managing Serer only) on page 60 Configuration options on page 61 Important: If you sae the response file in a location other than Managing_Serer_installation_image_directory/silent, ensure that the directory is readable by the user who is performing the silent installation. 2. To install the Managing Serer components, complete the following steps: a. Log on as the Managing Serer installation user. Ensure that this user has the permission to run Jaa. b. Access the technote at dociew.wss?uid=swg &w=1 and download the itcamfwas.jar. In both the Managing_Serer_installation_image_directory/lib file and Managing_Serer_installation_image_directory/jars directories, back up the original itcamfwas.jar and replace it with the downloaded ersion. c. At a command-prompt, change to the Managing_Serer_installation_image_directory directory. The setup_ms_platform.bin file is located in this directory. d. Run the following installation command: setup_ms.exe -silent [-is:log [log_file_name]] [configuration_option...] -options response_file log_file_name Specifies the path and name of the log file that the silent installer 54 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

75 writes to. The file is created een if it does not yet exist or if no name is specified. If the path contains spaces, place double quotation marks around it. configuration_option Specifies one or more configuration options not included in the response file. See Configuration options on page 61. response_file Specifies the response file you configured in Step 1 on page 54. Indicate the path and name of the file. If the path contains spaces, place double quotation marks around it. Here is an example of an installation command when completing a custom installation: setup_ms.exe -silent -is:log C:\tmp\MSlog.txt -V PORT_KERNEL_RMI01=9133 -options C:\silent\MS_Sample.opt Configuration options that are specified in the response file take precedence oer configuration options that are entered in the command-prompt. For a particular command-prompt configuration option to take effect, you must first nullify that option in the response file by commenting it out with a number sign (#). 3. To install the Visualization Engine on a separate serer, use one of the following options: a. You can use the GUI installer to install the VE. During the feature selection, clear the install database option. See Custom installation on page 32. b. You can use the silent installer to install the VE. In the silent properties file, specify -P dbinstall.actie=false. See Performing a normal silent installation (in one phase) on page 56. Tip: For options 3a and 3b, the installer automatically installs the MS file system. c. You can install the VE manually. First, copy the MS_home (Managing Serer installation) directory from the main serer, where the preious steps were performed, to the same location on the new Visualization Engine serer. Then, follow the instructions in Appendix L, Manually install MSVE, on page 319 to run jacl scripts and configure the WebSphere Application serer. If you installed the Visualization Engine on a separate serer, complete the following additional steps: a. Copy the jaa (JVM) directory from AppSerer_home on the Visualization Engine serer to any location on the main serer. On the main serer, set the JAVA_HOME enironment ariable to the full path to this directory. b. Copy the AppSerer_home\lib directory from the Visualization Engine host to the main serer. Use the same absolute path as used on the Visualization Engine host. c. On the main serer, in the MS_home\bin\seten.sh file, adjust the setting for JAVA_HOME to the location of the copied jaa directory. In the same file, set the WAS_HOME ariable to the absolute path of AppSerer_home on the Visualization Engine host. (This is used to determine the location of the copied lib directory). 4. To gie the DB2 Instance user write and execute access permission to the Managing_Serer_installation_image_directory\base\scripts\db2-remotescripts.tar file, complete the following steps: a. Log on as the DB2 Instance user. Chapter 6. Silent installation for the Managing Serer on a Windows operating system 55

76 b. Create a temporary directory under the DB2 Instance user home directory, copy the db2-remote-scripts.tar file from Managing_Serer_installation_image_directory\base\scripts to this temporary directory and extract it. c. Go to temporary_directory\db2\bin and run the following command as the DB2 Instance user: db2install.bat <DB2inst_username> <db_user> <absolute_path_of_db2scripts_dir> <adminveuser> <databasename> <DB2ersion> <databasename> Note: 1) When prompted for a password, enter the password for the <schema user>. 2) <DB2inst_username> must hae dba priileges. 3) <db_user> owns and can create the database tables for the product. 4) <absolute_path_of_db2scripts_dir> is the absolute directory containing bin/db2install.sh, for example: /home/db2inst1/tmp/db2. 5) <adminveuser> is the user that is used when logging in and operating the Managing Serer Application Monitor (MSVE) after installation and configuration. 6) <databasename> is the Managing Serer Database name which is specified in ITCAM_INSTALL.properties. 5. To gie the Oracle Instance user write and execute access permission to the Managing_Serer_installation_image_directory\base\scripts\oracle-remotescripts.tar file, complete the following steps: a. Log on as the Oracle database instance user. b. Create a temporary directory under the Oracle database home directory, copy the oracle-remote-scripts.tar file from Managing_Serer_installation_image_directory\base\scripts to the temporary directory and extract it. c. Go to temporary_directory\oracle\bin and run the following command as the Oracle System user. oracleinstall.bat oracle_sid sqlplus_user sqlplus_password tablespace jdbc_user jdbc_password adminveuser For example: C:\oracle-remote-scripts\oracle\bin>oracleinstall.bat octigate system zhu88jie octigate system zhu88jie Administrator 6. Restart WebSphere Application Serer as the WebSphere user. 7. Restart Managing Serer as the Managing Serer user. What to do next See Post-installation tasks on page 173. Performing a normal silent installation (in one phase) Start the normal silent installation by reiewing the notes about the installation. Here is a list of notes about the installation: Note: 56 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

77 Table 16. Location of installation log files 1. Copy the installation images to a hard disk. See Appendix A, Obtaining installation images, on page The installer creates log files in the following directories: Managing Serer Embedded IBM DB2 C:\Program Files\IBM\tioli\common\CYN\logs My_Documents_directory_of_the_installation_user\DB2LOG 3. If the installer detects an existing IBM DB2 enironment on this computer, you cannot install IBM DB2. To complete an embedded installation of IBM DB2 instead of use an existing database, you must uninstall it from this computer or choose another computer to install the Managing Serer on before you begin the installation. 4. If installation of the Managing Serer or the embedded IBM DB2 fails during the installation, you must exit the installation and then rerun the installer. The installation program automatically cleans up the installation directories for the components whose installations hae failed. If embedded IBM DB2 installation completed successfully, the installation remain intact. What to do next See Executing the silent installation command. Executing the silent installation command About this task Complete the following procedure to run the silent installation command: Procedure 1. Log on to the computer on which you want to install the Managing Serer as the installation user, for example, amuser. For instructions on how to create this user if it has not already been done, see the following section: Creating the installation user on page If you hae an existing installation of IBM WebSphere Application Serer, start the instance of IBM WebSphere Application Serer that is to be used by the Managing Serer. See Starting the application serer on page If Terminal Serices is enabled on Windows 2003 Serer or Windows 2008 Serer, put the serer into installation mode. Run the following command from a command prompt: change user /install Ignore the message: Install mode does not apply to a Terminal serer configured for remote administration. 4. Specify configuration options in the response file templates and sae the file. You must specify "Custom" as it is the only supported installation type. The sample response file is installation_image_directory/silent/ms_sample.opt or MS.opt. For more details, see the following sections: Requirements for a response file on page 58 Example of a modified response file template mirroring a Custom installation on page 59 Configuration options on page 61 Chapter 6. Silent installation for the Managing Serer on a Windows operating system 57

78 Note: a. Optionally, you can use a response file created by a GUI installer installation. During installation, ensure that in the Generate Response File panel, you select Sae settings in a response file and enter the file path ending with a file name: b. If you sae the response file in a location other than installation_image_directory/silent, ensure that directory is readable by the user performing the silent installation. 5. Use the command-prompt interface to access the directory that contains the installation executable file. The setup_ms.exe file is located in this directory. Type the following installation command and press Enter: setup_ms.exe -silent [-is:log [log_file_name]] [configuration_option...] -options response_file log_file_name Specifies the path and name of the log file that the silent installer writes to. The file is created een if it does not yet exist or if no name is specified. Wrap the path in double quotation marks if it contains spaces. configuration_option Specifies one or more configuration options not included in the response file. See Configuration options on page 61. response_file Specifies the response file you configured in Step 4 on page 57. Indicate the path and name of the file. Wrap the path in double quotation marks if it contains spaces. Here is an example of an installation command used to perform a custom installation: setup_ms.exe -silent -is:log "C:\log\MSlog.txt" -V PORT_KERNEL_RFS01=9125 -options C:\itcam\images\silent\MS_Sample.opt Configuration options specified in the response file take precedence oer configuration options entered in the command-prompt. For a particular command-prompt configuration option to take effect, you must first nullify that option in the response file by commenting it out with a number sign (#). What to do next See Postinstallation tasks on page 45. Requirements for a response file A response file must hae the following characteristics: Contains the configuration options for your installation, which are listed in Configuration options on page 61: The names of the configuration options must follow the uppercase and lowercase conentions shown in Configuration options on page 61, because they are case-sensitie. Each configuration option must exist on a separate line. The configuration options can be sorted in any order. Does not contain the -silent flag, the -options flag, or -is Does not contain null alues. If you do not specify a alue for a configuration option, you must make sure that the line is commented out with a number sign (#) or that the alue string to the right of the equal sign (=) is NULL. 58 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

79 If there are any spaces in the alue string to the right of the equal sign (=), the alue must be enclosed in double quotation marks. It is best to enter the alue between the double quotation marks that are already there in the response file template. Note: When you use a response file to specify options, you can type additional options in the command-prompt. Manually typing configuration options This section lists some reasons to manually type configuration options, instead of including them in the response file: Unique options: to reuse the response file in multiple installations, but some of the options are unique to each installation. Manually type the unique options in the command-prompt during each installation. The response file supplies the alues that are alid only for multiple target computers. Important: If you want to reuse a response file in multiple installations, but some of the options are unique to each installation, nullify those options in the response file by commenting them out with a number sign (#). This is because configuration options specified in the response file take precedence oer options entered in the command-prompt. Make sure that for each of the installations using that response file, the commented-out configuration options are entered in the command-prompt. Password protection: to safeguard the password by manually entering it during each installation. If you record the password in the option (.opt) file, the password is unencrypted and isible to anyone who opens the file. The following example sets one of the passwords on the command-prompt and relies on a response file to proide all other configuration details: setup_ms.exe -silent -V WAS_USER_PWD="tioli" -options C:\IBM\itcam\images\silent\MS_Sample.opt Example of a modified response file template mirroring a Custom installation Here is an example of a response file modified with suitable alues using the MS_Sample.opt file as a template. It corresponds to alues that would be specified if you were doing a Custom installation: -V disableosprereqchecking=true -V LICENSE_ACCEPT_BUTTON=true -V LICENSE_REJECT_BUTTON=false -V IS_SELECTED_INSTALLATION_TYPE=custom -W LogSetting.logLeel=ALL -W LogSetting.consoleOut=false -V LOG_DIR="c:\logs" -P installlocation="c:\ms" -P msfilesinstall.actie=true -P einstall.actie=true -P dbinstall.actie=true -V ITCAM_SYS_USERS="Administrator" -V KERNEL_HOST01=kernalhost.cn.ibm.com -V PORT_ARCHIVE_AGENT1=9129 -V PORT_ARCHIVE_AGENT2=9130 -V PORT_KERNEL_CODEBASE01=9122 -V PORT_KERNEL_RFS01=9120 -V PORT_KERNEL_RMI01=9118 -V PORT_MESSAGE_DISPATCHER=9106 -V PORT_PA=9111 -V PORT_PS=9103 -V PORT_PS2=9104 Chapter 6. Silent installation for the Managing Serer on a Windows operating system 59

80 -V PORT_SAM=9126 -V TEPS_BASED_INSTALL=false -V PRE_WAS_EXISTING=true -V NEW_WAS=false -V EXISTING_WAS=true -V WAS_HOSTNAME=kernalhost.cn.ibm.com -V WAS_BASEDIR="C:\WAS" -V WAS_PROFILEHOME="C:\WAS\profiles\default" -V WAS_PROFILENAME=default -V WAS_ADMIN_CONSOLE_PORT=9060 -V WAS_CELL=kernalhostCell01 -V WAS_NODE=kernalhostNode01 -V WAS_SERVER=serer1 -V WAS_SOAP_PORT=8880 -V WAS_USER="Administrator" -V WAS_USER_PWD="zhu88jie" -V PRE_DB2_EXISTING=true -V NEW_DB=false -V EXISTING_DB=true -V EXISTING_DB2_LOCAL=true -V EXISTING_DB2_REMOTE=false -V JDBC_TYPE=type4 -V DB2_JDBC="C:\Program Files\IBM\SQLLIB\jaa" -V DB2_INST_USER="db2admin" -V DB2_INST_PASSWORD="db2admin" -V DB2_SCHEMA_USER="db2admin" -V DB2_SCHEMA_PASSWORD="db2admin" -V DB2_SERVER=kernalhost.cn.ibm.com -V DB2_INST_PORTNUMBER= V LAUNCH_MS=false Example of a modified response file template mirroring a three phase installation (Managing Serer only) Here is an example of a response file modified with suitable alues using the MS_Sample.opt file as a template. It corresponds to alues that would be specified if you were doing a three phase installation of the Managing Serer without the Visualization Engine. Tip: All WebSphere Application Serer options hae been remoed. -V disableosprereqchecking=true -V LICENSE_ACCEPT_BUTTON=true -V LICENSE_REJECT_BUTTON=false -V IS_SELECTED_INSTALLATION_TYPE=custom -W LogSetting.logLeel=ALL -W LogSetting.consoleOut=false -V LOG_DIR="/ar/ibm/tioli/common/CYN/logs" -P installlocation="/opt/ibm/itcam/websphere/ms" -P msfilesinstall.actie=true -P einstall.actie=false -P dbinstall.actie=false -V ITCAM_SYS_USERS=msadmin -V KERNEL_HOST01=kernalhost01.us.ibm.com -V PORT_ARCHIVE_AGENT1=9129 -V PORT_ARCHIVE_AGENT2=9130 -V PORT_KERNEL_CODEBASE01=9122 -V PORT_KERNEL_RFS01=9120 -V PORT_KERNEL_RMI01=9118 -V PORT_MESSAGE_DISPATCHER=9106 -V PORT_PA=9111 -V PORT_SAM=9126 -V PRE_WAS_EXISTING=true -V NEW_WAS=false -V EXISTING_WAS=true -V WAS_HOSTNAME=was61.us.ibm.com 60 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

81 -V WAS_BASEDIR=/opt/IBM/WebSphere/AppSerer -V PRE_DB2_EXISTING=true -V NEW_DB=false -V EXISTING_DB=true -V EXISTING_DB2_LOCAL=false -V EXISTING_DB2_REMOTE=true -V DB2_INSTALL_LOCATION=/opt/IBM/db2/8.1 -V DB2_JDBC=/opt/IBM/db2/8.1/jaa -V DB2_INST_NAME=db2inst1 -V DB2_INST_USER=db2inst1 -V DB2_INST_PASSWORD=db2inst1 -V DB2_SCHEMA_USER=db2admin -V DB2_SCHEMA_PASSWORD=db2admin -V DB2_INST_HOMEDIR=/home/db2inst1 -V DB2_SERVER=db.us.ibm.com -V DB2_INST_PORTNUMBER= V LAUNCH_MS=true Configuration options This section describes the syntax for specifying configuration options in a response file or on the command-prompt. It proides a list of the possible configuration options for the Managing Serer. The following table lists the options for installing and configuring a Managing Serer on Windows. Table 17. Configuration options for the Managing Serer on Windows Feature or entity the option configures Option Description Installation parameters -V disableosprereqchecking=true false -V LICENSE_ACCEPT_BUTTON=true false -V LICENSE_REJECT_BUTTON=true false Indicates whether the operating-system-leel checking is turned on before the installation. Specifying true means that the program ignores the results of the operating-system-leel checking. Specifying false means that the operating-system-leel checking is turned on before the installation and the program exits if the operating system on the target computer has not met the minimum requirements for the installation. Specify true. Specify false. Optional or required? Required Required Required Chapter 6. Silent installation for the Managing Serer on a Windows operating system 61

82 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V LOG_DIR=alue This specifies the writable directory to which the installation program writes log files. It is useful if the default directory of C:\Program Files\IBM\tioli \common\cyn\logs -V IS_SELECTED_INSTALLATION_TYPE = custom is not writable on your systems. If you set this new option, the installation program uses it as a real log path een if the default log path is writable. Specifies the type of installation. Since ersion the type of installation must be custom. -P installlocation=alue Specifies the path of the installation directory for the installation. If you do not specify this option, the installation program uses the default directory path: C:\Program Files\IBM\itcam \WebSphere\MS Optional or required? Required if C:\Program Files\IBM\tioli\ common\cyn\logs is not writable. Required Optional Important: 1. You cannot install the Managing Serer in a directory path that includes the following types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters 2. The directory that you specify must be empty. 3. If you specify a directory that does not exist, the installation program creates the directory. 62 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

83 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description Optional or required? -P msfilesinstall.actie=true false Specifies whether to install the Managing Serer files. Indicate true or false. Indicate true if you are installing the Managing Serer on this computer. Indicate false if you are running the installer program for creating database tables for an existing database enironment on this computer and the Managing Serer is being installed on a separate computer. Required -P einstall.actie=true false Specifies whether to install the ITCAM for Application Diagnostics Managing Serer with the installation. Indicate true or false. Indicate true if you are installing the Managing Serer on this computer. Indicate false if you are running the installer program for creating database tables for an existing database enironment on this computer and the Managing Serer is being installed on a separate computer. -P dbinstall.actie=true false Specifies whether to install database tables with the installation. Indicate true or false. Indicate true if you are installing IBM DB2 or creating database tables for an existing database enironment on this computer. Indicate false if you are running the installer program for installing the Managing Serer on this computer and you are creating database tables for an existing database enironment on a separate computer. Required Required Attention: Indicate false if you are upgrading the Managing Serer. If you indicate true, the data in the existing database tables is deleted. -V LAUNCH_MS=true false Specifies whether to start the Managing Serer after the installation. Required Chapter 6. Silent installation for the Managing Serer on a Windows operating system 63

84 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -P mswinsr.actie=true false Use this parameter to indicate that you do not want to create a Windows Serice for the Managing Serer during installation. The default alue is true. Message generation Managing Serer settings -W LogSetting.logLeel=alue See Options for monitoring installation messages on page 72. -W LogSetting.consoleOut=true false See Options for monitoring installation messages on page 72. -V ITCAM_SYS_USERS=alue Specifies the user used to log in to the ITCAM for Application Diagnostics Managing Serer. The default is the installation user. -V KERNEL_HOST01=alue Specifies the fully qualified host name of the Managing Serer. -V PORT_ARCHIVE_AGENT1=alue Specifies the port that the Managing Serer uses to connect to Archie Agent 1. The default is V PORT_ARCHIVE_AGENT2=alue Specifies the port that the Managing Serer uses to connect to Archie Agent 2. The default is V PORT_KERNEL_CODEBASE01=alue Specifies the port that the Managing Serer uses to connect to Kernel Codebase 1. The default is V PORT_KERNEL_RFS01=alue Specifies the port that the Managing Serer uses to connect to Kernel Remote File Sharing (RFS) 1. The default is V PORT_KERNEL_RMI01=alue Specifies the port that the Managing Serer uses to connect to Kernel Remote Method Inocation (RMI) 1. The default is V PORT_MESSAGE_DISPATCHER=alue Specifies the port that the Managing Serer uses to connect to the Message Dispatcher. The default is V PORT_PA=alue Specifies the port that the Managing Serer uses to connect to the Polling Agent. The default is Optional or required? Optional Optional Required Optional Required Optional Optional Optional Optional Optional Optional Optional 64 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

85 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V PORT_PS=alue Specifies the port that the Managing Serer uses to connect to Publish Serer 1. The default is IBM WebSphere Application Serer settings -V TEPS_BASED_INSTALL = true false Specifies whether you are installing the Managing Serer based on Tioli Enterprise Portal Serer. Note: Managing Serer Visualization Engine can be installed on Tioli Enterprise Portal Serer embedded WebSphere Application Serer(eWAS). This is not recommended for production use. -V ITM_HOME = alue Specifies the IBM Tioli Monitoring home directory if you choose to install MS based on Tioli Enterprise Portal Serer. -V PORT_SAM=alue Specifies the port that the Managing Serer uses to connect to Structured Application Monitor 1. The default is V PRE_WAS_EXISTING=true false Specifies whether you hae a ersion of IBM WebSphere Application Serer installed on your computer. -V NEW_WAS=true false Specifies whether you are installing a new ersion of IBM WebSphere Application Serer instead of using an existing ersion of IBM WebSphere Application Serer for the Managing Serer installation. -V EXISTING_WAS=true false Specifies whether you are using an existing ersion of IBM WebSphere Application Serer for the Managing Serer installation. Optional or required? Optional Required required if -V TEPS_BASED_ INSTALL=true Optional Optional Required Required Chapter 6. Silent installation for the Managing Serer on a Windows operating system 65

86 com.ibm.websphere.installation.base.doc/ae/cins_was85_base_install_w Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description Optional or required? -V WAS_CDROMDIR=alue Specify the path of the WebSphere Application Serer silent installation response file used by IBM Installation Manager. Detailed information about how to create a WebSphere silent installation response file can be found in WebSphere documentation at: support/knowledgecenter/ SSEQTP_8.5.5/ Required if -V NEW_WAS=true -V WAS_ADMIN_CONSOLE_PORT=alue When you complete the installation of IBM WebSphere Application Serer that comes with ITCAM for Application Diagnostics, you use this option to specify the port used by the IBM WebSphere Application Serer administratie console. The default is Do not use the default if port 9060 is assigned to another serice. -V WAS_HOSTNAME=alue Specifies the fully qualified host name or IP address of the computer where IBM WebSphere Application Serer is installed. Optional Required if -V EXISTING_WAS=true 66 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

87 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V WAS_BASEDIR=alue Specifies the path of the installation directory for IBM WebSphere Application Serer or the directory path of the profile of an existing ersion of IBM WebSphere Application Serer. For example, C:\Program Files\IBM\itcam \WebSphere\MS\WAS61 \AppSerer1 Important: You cannot install or choose a IBM WebSphere Application Serer instance in a directory path (including profile, cell, node, and serer names) that includes the following types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters -V WAS_PROFILEHOME=alue Specifies the path to the profile for the instance of IBM WebSphere Application Serer being used by the Managing Serer. For example, "C:\Program Files\IBM\itcam \WebSphere\MS\WAS61\Base \profiles\default" -V WAS_PROFILENAME=alue Specifies the name of the profile for the instance of IBM WebSphere Application Serer being used by the Managing Serer. For example,default Optional or required? Optional Required Required if -V EXISTING_WAS=true Chapter 6. Silent installation for the Managing Serer on a Windows operating system 67

88 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V WAS_CELL=alue When you use an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of a cell in a IBM WebSphere Application Serer distributed network. A cell is a configuration concept that enables IBM WebSphere Application Serer administrators to logically associate nodes with each another. You can use any of the existing cell names that are defined in the cell directory. For example, hostcell01 -V WAS_NODE=alue When you use an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of a computer that runs an application serer and an administratie serer. Normally, the default node name includes the short host name. For example, on a computer named IBMMACHINE, the node name can be IBMMACHINENode01. -V WAS_SERVER=alue When you use an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of the IBM WebSphere Application Serer where the Managing Serer runs. In a simple installation, this serer might be named serer1. -V WAS_USER=alue Specifies the name of the user that runs IBM WebSphere Application Serer. For an existing IBM WebSphere Application Serer, if IBM WebSphere Global Security is enabled, the user you specify must hae the WebSphere Administrator Role. If IBM WebSphere Global Security is not enabled, the user you specify must hae membership in the Administrators group. This user must not be an LDAP user. Optional or required? Required if -V EXISTING_WAS=true Required if -V EXISTING_WAS=true Required if -V EXISTING_WAS=true Required 68 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

89 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V WAS_USER_PWD=alue Specifies the password of the user that runs IBM WebSphere Application Serer. General database settings -V WAS_SOAP_PORT==alue Specifies the connector port used by theibm WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). The default is V PRE_DB2_EXISTING=true false Specifies whether you hae a ersion of IBM DB2 installed on your computer. -V NEW_DB=true false Specifies whether you are installing a new ersion of IBM DB2 instead of using an existing database for the Managing Serer installation. -V EXISTING_DB=true false Specifies whether you are using an existing database for the Managing Serer installation. -V EXISTING_DB2_LOCAL=true false Specifies whether the existing ersion of IBM DB2 you are using for the Managing Serer installation is installed on the local computer. -V EXISTING_DB2_REMOTE=true false -V EXISTING_ORACLE_LOCAL=true false Specifies whether the existing ersion of IBM DB2 you are using for the Managing Serer installation is installed on a remote computer. Specifies whether the existing ersion of the Oracle database you are using for the Managing Serer installation is installed on the local computer. -V DB2_INSTALL_LOCATION=alue Specifies the full path to where you want IBM DB2 installed. The default is C:\Program Files\IBM\itcam\ WebSphere\MS\DB2 -V DB2_DAS_USER=alue Specifies the name of the DB2 Administration Serer user account. -V EXISTING_ORACLE_REMOTE=true false Specifies whether the existing ersion of the Oracle database you are using for the Managing Serer installation is installed on a remote computer. Optional or required? Required Required Required Required Required Required if -V EXISTING_DB=true Required if -V EXISTING_DB=true Required if -V EXISTING_DB=true Optional Optional Required if -V EXISTING_DB=true Chapter 6. Silent installation for the Managing Serer on a Windows operating system 69

90 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description IBM DB2 settings -V DB2_IMAGE_LOCATION=alue Specifies the path of the installation image location for IBM DB V DB2_DAS_PASSWORD=alue Specifies the password of the IBM DB2 Administration Serer user account. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_DAS_USER=true false If the DB2 Administration Serer user does not exist on the target computer, specify true; otherwise, specify false. -V DB2_INST_NAME=alue Specifies the name of the IBM DB2 instance. -V DB2_INST_USER=alue Specifies the name of the IBM DB2 Instance user. -V DB2_INST_PASSWORD=alue Specifies the password of the IBM DB2 Instance user. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_INST_USER=true false If the IBM DB2 Instance user does not exist on the target computer, specify true; otherwise, specify false. -V DB2_JDBC=alue Specifies the full path to the required Jaa DataBase Connectiity (JDBC) files for IBM DB2. This path must be a directory containing DB2 jdbc drier files, such as db2jcc.jar. -V DB2_SERVER=alue Specifies the fully qualified host name of the IBM DB2 serer. -V DB2_INST_PORTNUMBER=alue Specifies the port used by IBM DB2. The default port is for IBM DB2. -V DB2_SCHEMA_USER=alue Specifies the schema user name. This user owns and can create the database tables for ITCAM for Application Diagnostics. -V DB2_SCHEMA_PASSWORD=alue Specifies the password of the schema user that you specify. Important: The password created for this user during a Typical installation is itcam610. Optional or required? Required if -V EXISTING_DB=true Required if -V NEW_DB=true Required if you are installing or using an IBM DB2 database Optional Required if you are using an existing IBM DB2 database Required if a alue was entered for -V DB2_INST_USER Required if you are installing or using an IBM DB2 database Required if you are using an existing IBM DB2 database Required if you are using an existing IBM DB2 database Optional Required if you are using an existing IBM DB2 database Required if a alue was entered for -V DB2_SCHEMA_ USER 70 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

91 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V DB2_CREATE_SCHEMA_USER=true false If the DB2 schema user does not exist on the target computer, specify true; otherwise, specify false. Oracle settings -V ORACLE_SID=alue Specifies the Oracle database system identifier number. The system identifier is a unique identifier of the Oracle database instance, defined during the Oracle database installation. The oracle database user must hae bash as system shell. -V ORACLE_SERVER=alue Specifies the fully qualified host name or the IP address of the host computer for the Oracle database enironment which contains table space for the management repository. For example, serername.it.company.com shows typical syntax for a fully qualified host name. -V ORACLE_SCHEMA_USER=alue Specifies the schema user name. This user owns and can create the database tables for ITCAM for Application Diagnostics. -V ORACLE_SCHEMA_PASSWORD=alue Specifies the password for the schema user in the Oracle database enironment. -V ORACLE_PORTNUMBER=alue Specifies the port number for the Oracle database. The default port is V ORACLE_DBA_USER=alue Specifies the user name of the Oracle database administrator. -V ORACLE_DBA_PASSWORD=alue Specifies the password of the Oracle database administrator. -V ORACLE_JDBC=alue Specifies the full path to the required Jaa DataBase Connectiity (JDBC) files for the Oracle database. This must be a directory containing Oracle jdbc drier files, such as ojdbc14.jar or classes12.jar. -V ORACLE_HOME=alue Specifies the full path to the Oracle database home directory. Optional or required? Required if you are using an existing IBM DB2 database Required if you are using an Oracle database Required if you are using an Oracle database Required if you are using an Oracle database Required if you are using an Oracle database Optional Required if you are using an existing local Oracle database Required if a alue was entered for -V ORACLE_DBA_ USER Required if you are using an Oracle database Required if you are using an existing local Oracle database Chapter 6. Silent installation for the Managing Serer on a Windows operating system 71

92 Table 17. Configuration options for the Managing Serer on Windows (continued) Feature or entity the option configures Option Description -V ORACLE_SQLPLUS_USER=alue Specifies the user name of an existing Oracle SQLPlus user. This user must hae priileges to create tables in the Oracle database. Optional or required? Required if you are using an existing local Oracle database Syntax of configuration options This section describes the syntax for configuration options for the Managing Serer silent installation. You can use configuration options in the command-prompt or in a response file. There are three flags for configurations options,-p-v and -W. The configuration options accept the following parameters: -P entity_id.dataitem="alue" -V entity_id.dataitem="alue" -W entity_id.dataitem="alue" The entity_id identifies an entity inoled in an installation or configuration, such as the log settings for the installation or configuration. The dataitem is the name of an attribute, such as the installation path or the communications port. The alue specifies the alue for an attribute of an entity inoled in an installation or configuration, such as a specific path like C:\Program Files\IBM\tioli\MS. Options for monitoring installation messages The following two configuration options control the display or logging of installation messages. These options can help you monitor and debug all phases of an installation. -W LogSetting.consoleOut=true false specifies whether to display messages issued by installation or upgrade program on the console. If you use this option with a natie launcher, it must be used in combination with the -is:jaaconsole option. -W LogSetting.logLeel=alue specifies the leel of tracing for the installation log files. The amount of tracing for a specific leel includes the messages for that leel and all messages at a higher seerity. For example, if you choose the WARNING trace leel, the following messages are logged: WARNING,ERROR and FATAL. During the installation, maximum logging is turned on by default. Access the installation log files in the following path: C:\Program Files\IBM\tioli\ common\cyn\logs. Table 18. Trace leel settings for installation log files Option string Description -W LogSetting.logLeel=FATAL Log fatal messages. A fatal message reports an error from which the program cannot recoer. A fatal message is the most seere message. 72 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

93 Table 18. Trace leel settings for installation log files (continued) Option string Description -W LogSetting.logLeel=ERROR Log error messages. An error message reports a serious failure. An error message is less seere than a fatal message. -W LogSetting.logLeel=WARNING Log warning messages. A warning message reports that an abnormal condition has occurred. The condition might or might not require the user to take action. -W LogSetting.logLeel=INFO Log information messages. An information message indicates a condition that is worth noting but does not require the user to take action. -W LogSetting.logLeel=DEBUG_MIN Log debug messages that proide minimal detail. DEBUG_MIN is appropriate for a software trace that is always running. It proides some information about the program state with only minimal affect on performance. DEBUG_MIN is the default setting for installation log files. -W LogSetting.logLeel=DEBUG_MID Log debug messages that proide a medium amount of detail. The DEBUG_MID setting produces a leel of detail between DEBUG_MIN and DEBUG_MAX. -W LogSetting.logLeel=DEBUG_MAX Log debug messages that proide the most detail about program execution. Program performance is not an issue when debugging in this mode. -W LogSetting.logLeel=ALL Enable all message logging. Retrieing installation options from the WebSphere serer configuration files You do not hae to proide all the installation options during the Managing Serer (MS) split installation procedure. Some of these options can be retrieed from the WebSphere serer configuration files. These options are: WAS_HOSTNAME Specifies the fully qualified host name or IP address of the computer where the WebSphere Application Serer is installed. WAS_SOAP_PORT Specifies the connector port that the WebSphere Application Serer uses to send commands using the Simple Object Access Protocol (SOAP). WAS_APP_PORT Specifies the HTTP serice port of the WebSphere application serer. You can access applications installed on the WebSphere application serer through this port. The split Managing Serer installation can retriee the WAS_SOAP_PORT and WAS_HOSTNAME options from the wsadmin.properties file that is located in the WAS_HOME/properties directory. The WAS_APP_PORT option is retrieed from the sererindex.xml file that is located in the WAS_HOME/config/cells/Cellname/nodes/Nodename/ directory. The Managing Serer split installation obtains the information about where to find the WebSphere serer configuration files from its ITCAM_INSTALL.properties file. Complete these steps to make sure that the Managing Serer installation can read these options from the WebSphere serer configuration files: 1. Open the ITCAM_INSTALL.properties file for edition. Chapter 6. Silent installation for the Managing Serer on a Windows operating system 73

94 2. Modify the WAS_PROFILEHOME property. a. Make sure that the property line is uncommented. If it is preceded by a number (#) character delete the character. b. Proide the path to the WebSphere profile home directory in the property line as in the following example: WAS_PROFILEHOME=C:\\WebSphere61ND\\profiles\\AppSr01 Note: You must replace the backslash (\) character in the Windows path with a double backslash (\\). The Linux path must hae the following format:was_profilehome=/opt/ibm/websphere/appserer/profiles/appsr01 3. Sae the ITCAM_INSTALL.properties file and exit editing mode. 74 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

95 Chapter 7. Upgrading and updating the Managing Serer on a Windows system Unpacking the update Installing updates You can use the update installer to upgrade the Managing Serer from Version 6.1 (any fix pack) to Version , and to update the Managing Serer from a preious maintenance leel of Version 7.1 to Version The update installer proides the following functions: A silent command-prompt update installer. Installation and remoal of indiidual or multiple updates (new ersions, fix packs and interim fixes) for the Managing Serer. (Important: while you can remoe fix packs, you cannot use the Update Installer to downgrade from Version 7.x to Version 6.x) Logging, tracking, and prerequisites handling. Important: The Managing Serer Version connects and operates with Data Collectors of the current ersion and all preious ersions starting from ITCAM for WebSphere Version 6.1 and ITCAM for J2EE Version 6.1. The Update Installer is distributed in an update package, which is a TAR file. You can use this package to update from any release of Version 7.0.x or Version 6.1.x of the Managing Serer. Create a temporary directory, put the update package there and extract it. (On Windows systems, you can use the compress utility that is proided with Microsoft Serices for Unix or any third party archie manager that supports the compression format). The update package includes the updates directory that contains the file with the *.update extension. For example: tar xf TIV-ITCAMfAD_SVR-FP0001.tar silentupdate.sh updates/ ITCAM_V71_UpdateInstaller.htm ITCAM_V71_UpdateInstaller.pdf alien.jar configutil.jar silentupdate.bat silentupdate.properties update.jar updates/7.1.0-tiv-itcamfad_svr-fp0001.update TIV-ITCAMfAD_SVR-FP0001.README You can use the update installer to install new ersions, fix packs, and interim fixes for the Managing Serer. You must run the Update Installer on eery host where any components of the Managing Serer are running. In a split Managing Serer installation, run it on both hosts. If the Visualization Engine runs on a separate host, run the Update Copyright IBM Corp. 2006,

96 Installer on the Visualization Engine host and the backend component hosts. If the Database Management Serer (DB2 or Oracle) is on a separate host, you do not hae to run the Update Installer on it. When the Managing Serer is running on more than one host, you must update the database only once. To do this, in the response file, set updatedb=true on one host and updatedb=false on others. Preparing the Enironment Before running the update installer, log on as Administrator or owner of the product directory. If the Visualization Engine is installed on the host, the user for the update installer must hae write permission for the WebSphere Application Serer directory that is used by the Visualization Engine. The update installer requires the Runtime Enironment for the Jaa platform Version 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment that is used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home\bin\seten.sh file. Updating the Response File The update installer is a non-interactie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home). (Optional): If the *.update files are not in the default./updates directory, then set the updates.location property to the directory that contains the *.update files. If you hae unpacked the package and not moed the files, do not set this property. If the Visualization Engine was not installed to the Managing Serer host to be updated, set the updateve property to false. Otherwise, uncomment and set the updateve.washome property to the WAS_PROFILE_HOME of the Visualization Engine application serer. In a split Managing Serer installation, when seeral Managing Serer hosts that use the same database, this database must be updated only once. It is updated with the default property alues, so no change is required on the first host to update. On the second and subsequent hosts to update, set the updatedb property to false. Complete the following steps if the Visualization Engine is installed on the host to be updated: If the Visualization Engine is installed on a WebSphere Network Deployment, use an SOAP connection to install the update. To do this, uncomment and set the following properties in the silentupdate.properties file: updateve.was.soap.host=<host> updateve.was.soap.port=<port> Important: WebSphere Deployment Manager and Node Agent must be in running state. 76 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

97 If WebSphere Security is enabled, uncomment and set the following properties: updateve.was.user=<was USER> updateve.was.password=<was PASSWORD> To retriee the user name and password from *.client.props file set the following property: connection.useclientprops=true For an SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Important: Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. Important: The response file is a Jaa Properties file. You must use two backslashes (\\), for example: product.location=c:\\ibm\\itcam\\websphere\\ms Preparing for the Installation To reduce the Managing Serer downtime, you can use the update installer to prepare the installation while the product is running. This step is optional. In order to prepare for the installation, change to the directory where the update package was unpacked and run the following command: silentupdate.bat prepareinstall If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -prepareinstall my.properties A typical output of the -prepareinstall command is as follows: >silentupdate.bat -prepareinstall Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: prepare install Finished successfully Installing the update To reduce Managing Serer downtime, you can run the -prepareinstall command before installing the update, see Preparing for the Installation. Before installing the update, stop the Managing Serer. Important: If the Managing Serer components are running on seeral hosts, stop the Managing Serer on all hosts, then perform the installation on all hosts. Then, change to the directory where the update package was unpacked and run the following command: Chapter 7. Upgrading and updating the Managing Serer on a Windows system 77

98 silentupdate.bat install If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -install my.properties A typical output of the -install command is as follows: >silentupdate.bat -install Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: install Finished successfully After installation, reiew the configuration files. The Update Installer merges any manual configuration changes, including the split installation, that were made in the preious ersion. For details about this, see Details of configuration file merging on page 83. Then, start the Managing Serer. Cleaning the Prepared Installation If you completed the installation, you do not hae to clean up the preparation. Do not complete this step. If you decide to not install the update after you already run -prepareinstall, then you can clean results of the -prepareinstall command. To do that, change to the directory where the update installer scripts are stored and run the following command: silentupdate.bat cleanprepared If your response file is named differently from the default silentupdate.properties file, then specify it as a parameter: silentupdate.bat -cleanprepared my.properties A typical output of the -cleanprepared command is as follows: >silentupdate.bat -cleanprepared Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: cancel prepared Finished successfully Rolling Back a Failed Installation If the -install command fails and the automatic rollback also fails, you cannot install or uninstall any updates until the rollback is completed. To complete the rollback, do the following tasks: Reiew the update installer log and resole the cause of the rollback failure. Change to the directory where the update installer scripts are stored and run the following command: silentupdate.bat rollback If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -rollback my.properties 78 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

99 Uninstalling updates A typical output of the -rollback command is as follows: >silentupdate.bat -rollback Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: rollback Finished successfully You can use the update installer to uninstall fix packs and interim fixes. The Managing Serer is rolled back to the state before the update. You must run the Update Installer on eery host where any components of the Managing Serer are running. In a split Managing Serer installation, run it on both hosts. If the Visualization Engine is running on a separate host, run the Update Installer on the Visualization Engine host and the back end component hosts. If the Database Management Serer (DB2 or Oracle) is on a separate host, you do not hae to run the Update Installer on it. When the Managing Serer is running on more than one host, you must roll back the database only once. To do this, in the response file, set updatedb=true on one host and updatedb=false on others. Important: The Update Installer does not support rolling back from any release of Version 7.x to Version 6.x. Preparing the Enironment Before running the update installer, log on as Administrator or owner of the product directory. If the Visualization Engine is installed on the host, this user must hae write permission for the WebSphere Application Serer directory that is used by the Visualization Engine. The update installer requires the Runtime Enironment for the Jaa platform Version 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment that is used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home\bin\seten.sh file. Updating the Response File The update installer is a noninteractie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home). Optionally, if the *.update files are not in default./updates directory, then set the updates.location property to the directory that contains the *.update files. (If you hae unpacked the package and not moed the files, do not set this property). Chapter 7. Upgrading and updating the Managing Serer on a Windows system 79

100 If the Visualization Engine was not installed to the Managing Serer host to be updated, set the updateve property to false. Otherwise uncomment and set the updateve.washome property to the WAS_PROFILE_HOME of the Visualization Engine application serer. In a split Managing Serer installation, when seeral Managing Serer hosts that use the same database, this database must be updated only once. It is updated with the default property alues, so no change is needed on the first host to update. On the second and subsequent hosts to update, set the updatedb property to false. Set the uninstall.updates property with the one of possible alues: all uninstall all updates last uninstall the updates installed by the last -install command <comma separated list of updates> -- uninstall the specified updates. The updates are specified by their identifiers as displayed by the -listinstalledupdates command. (Example: , ) Complete the following steps if the Visualization Engine is installed on the host to be updated: If the Visualization Engine is installed on a WebSphere Network Deployment, use SOAP connection to install the update. To do this, uncomment and set the following properties in the silentupdate.properties file: updateve.was.soap.host=<host> updateve.was.soap.port=<port> Important: WebSphere Deployment Manager and Node Agent must be in running state. If WebSphere Security is enabled, uncomment and set the following properties: updateve.was.user=<was USER> updateve.was.password=<was PASSWORD> To retriee user name and password from *.client.props file set the following property: connection.useclientprops=true For a SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. For a SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Important: Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. 80 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

101 Important: The response file is Jaa Properties file. You must use two backslashes (\\), for example: product.location=c:\\ibm\\itcam\\websphere\\ms Preparing for uninstallation To reduce the Managing Serer downtime, you can use the update installer to prepare uninstallation while the product is running. This step is optional. In order to prepare uninstallation, change to the directory where the update package was unpacked and run the following command: silentupdate.bat prepareuninstall If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -prepareuninstall my.properties A typical output of the -prepareuninstall command is: >silentupdate.bat -prepareuninstall Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: prepare uninstall Finished successfully Uninstalling the update To reduce Managing Serer downtime, you can run the -prepareuninstall command before installing the update, see Preparing for uninstallation. Before installing the update, stop the Managing Serer. Important: If the Managing Serer components are running on seeral hosts, stop the Managing Serer on all hosts, then complete the uninstallation on all hosts. Then, change to the directory where the update package was unpacked and run the following command: silentupdate.bat -uninstall If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -uninstall my.properties A typical output of the -uninstall command is: >silentupdate.bat -uninstall Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: uninstall Finished successfully After uninstallation, reiew the configuration files. Changes that were preiously made to these files might be lost. Then, start the Managing Serer. Chapter 7. Upgrading and updating the Managing Serer on a Windows system 81

102 Cleaning the prepared uninstallation If you hae completed the uninstallation, you do not hae to clean up the preparation. Do not complete this step. If you decide to not uninstall after you already run -prepareuninstall then you can clean results of the -prepareuninstall command. In order to do that change to the directory where the update installer scripts are stored and run the following command: silentupdate.bat cleanprepared If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -cleanprepared my.properties A typical output of the -cleanprepared command is: >silentupdate.bat -cleanprepared Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: cancel prepared Finished successfully Rolling back a failed uninstallation Displaying installed updates If the -uninstall command fails and the automatic rollback also fails, you cannot install or uninstall any updates until the rollback is completed successfully. In order to complete the rollback, take the following steps: Reiew the update installer log and resole the cause of the rollback failure. Change to the directory where the update installer scripts are stored and run the following command: silentupdate.bat rollback If your response file is named differently than the default silentupdate.properties, specify it as a parameter: silentupdate.bat -rollback my.properties A typical output of the -rollback command is: >silentupdate.bat -rollback Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: rollback Finished successfully You can use the update installer to display a list of the installed fix packs and interim fixes. Preparing the Enironment Before running the update installer, log on as Administrator or owner of the product directory. Then update the enironment as described in this section. 82 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

103 The update installer requires the Runtime Enironment for the Jaa platform Version 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home\bin\seten.sh file. Updating the response file The update installer is a non-interactie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home) Note: The response file is a Jaa Properties file. Any backward-slashes must be doubled, for example: product.location=c:\\program Files\\IBM\\itcam\\WebSphere\\DC Displaying installed updates To display a list of the installed fix packs and interim fixes, change to the directory where the update package was unpacked and run the following command: silentupdate.bat displayinstalledupdates If your response file is named differently from the default silentupdate.properties, specify it as a parameter: silentupdate.bat -displayinstalledupdates my.properties A typical output of the -displayinstalledupdates command is: >silentupdate.bat -displayinstalledupdates Update installer ersion 7.1.0, build Logging details into C:\IBM\itcam\WebSphere\MS\logs\update\update_ log Action: display installed updates Updates installed 4/20/10 8:52 PM Fix Pack 1 Finished successfully Details of configuration file merging When the Managing Serer is updated from Version 6.1 to 7.1 (any maintenance leel), configuration files are merged to ensure that preious manual configuration changes are presered as fully as possible. This is not completed when a maintenance leel is uninstalled. Also, when updating from a 7.1 maintenance leel to another 7.1 maintenance leel, the configuration files are unchanged. When updating from Version 6.1, the update installer completes the following changes: First, new properties files are created for all components for which were present in older configuration: kl*.properties Chapter 7. Upgrading and updating the Managing Serer on a Windows system 83

104 klwd*.properties ps*.properties aa*.properties sam*.properties log-kl*.properties log-ps*.properties log-aa*.properties log-sam*.properties - Next, properties are migrated from the old configuration files (in the old MS_home/etc directory) into new ones: aa*.properties, excluding ENABLE_DATATRIMMER, MEMORY_DATA_DELETE_TIME, GC_DATA_DELETE_TIME, SR_OVERVIEW_DATA_DELETE_TIME, IMS_THREAD_DATA_DELETE_TIME, WEBSERVER_CHART_DATA_DELETE_TIME aa_deletedata.properties ccmdb-sim.properties cyn-cclog.properties cynlogging.properties excluding CYN.msg.listenerNames, CYN.trc.listenerNames, CYN.trc.leel kl*.properties klwd*.properties excluding kernel.rfs.host=localhost ms.properties pa.properties ps*.properties excluding e.host, e.port sam1.properties e.properties excluding e.framework.pdf log-aa*.properties excluding *.publishserer.*, CYN.handler.snap.conertExceptions log-kl*.properties excluding CYN.handler.snap.conertExceptions log-md.properties excluding CYN.handler.snap.conertExceptions log-ps*.properties excluding CYN.trc.leel, CYN.handler.snap.conertExceptions log-sam*.properties excluding CYN.handler.snap.conertExceptions log-ws.properties xcluding CYN.handler.snap.conertExceptions Log.properties dal/dal.properties (renamed properties are migrated correctly) Scripts (*.sh) in the MS_home directory are oerwritten, except am-start.sh, am-stop.sh, am-status.sh, am-status_codes.sh, and am-forcestop.sh A command is appended to am-start.sh: echo "ITCAM MS started" A command is appended to am-stop.sh: echo "ITCAM MS stopped" The following properties are migrated from the old seten.sh into the new ersion: KERNEL_HOST* PORT_KERNEL_CODEBASE* PORT_KERNEL_RFS* PORT_KERNEL_RMI* 84 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

105 PORT_ARCHIVE_AGENT* PORT_ARCHIVE_AGENT* PORT_MESSAGE_DISPATCHER PORT_PS* PORT_PA* PORT_SAM* KERNEL_INSTANCE PS_INSTANCE AA_INSTANCE HEAP_MIN_SIZE_* HEAP_MAX_SIZE_* LOG_COMMON_DIR CERT_PATH KEYSTR_LOC KEYSTR_PASS KEYSTR_KEYPASS NODE_USERID NODE_IP USE_SSL The update installer does not oerwrite the dal/temaqueryschema.xml file, so all settings in this file remain actie for the new ersion. Chapter 7. Upgrading and updating the Managing Serer on a Windows system 85

106 86 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

107 Chapter 8. Customization and adanced configuration for the Managing Serer on Windows Follow the instructions in this chapter to complete optional customizations and adanced configuration of the Managing Serer. Complete the procedures in each of the following sections, if they apply. Creating additional instances of Managing Serer components By default, the Managing Serer has the following runtime instances. A properties file exists for each of them. Table 19. Runtime instances for the default Managing Serer Component ID Component instance Properties file name kl1 The first instance of the Kernel kl1.properties ps1 The first instance of the Publish Serer ps1.properties ps2 The second instance of the Publish Serer ps2.properties aa1 The first instance of the Archie Agent aa1.properties aa2 The second instance of the Archie Agent aa2.properties md The one instance of the Message Dispatcher md.properties pa The one instance of the Polling Agent pa.properties sam1 The one instance of the Global Publish Serer sam1.properties You can create additional instances of the Kernel, Publish Serer, or Archie Agent. For the Publish Serer and Archie Agent, each instance must hae its own properties file. The simplest way to create another instance of one of these components is to run the product-proided scripts. They make copies of existing properties files and modify the component IDs and the port numbers to unique alues. The scripts also add alues to particular files that require the parameters to be set so that the additional instances can run properly, for example, to the start and stop scripts. You cannot create additional instances for any of the other components that are listed in Table 19. Adding an additional kernel You can add a second kernel instance. More than two kernels are not supported. Complete the following procedure to add an additional kernel to the Managing Serer configuration: 1. Decide which ports to use for the additional kernel. Each kernel requires three ports for operation. Edit the MS_home/bin/seten.sh file and add the following properties: KERNEL_HOST${KERNEL_COUNT}=hostname. For example, KERNEL_HOST02=de-lnx-mycompany PORT_KERNEL_CODEBASE${KERNEL_COUNT}=port_number. For example, Copyright IBM Corp. 2006,

108 PORT_KERNEL_CODEBASE02=9123 PORT_KERNEL_RFS${KERNEL_COUNT}=port_number. For example, PORT_KERNEL_RFS02=9121 PORT_KERNEL_RMI{KERNEL_COUNT}=port_number. For example, PORT_KERNEL_RMI= Edit the MS_home/etc/ms.properties file and set the kernel.hosts property as follows: kernel.hosts=kernel_host01:port_kernel_codebase01: PORT_KERNEL_RFS01:PORT_KERNEL_RMI01,KERNEL_HOST02: PORT_KERNEL_CODEBASE02:PORT_KERNEL_RFS02:PORT_KERNEL_RMI02 For example, de-lnx-mycompany.usca.abc.com:8122:8120:8118, de-lnx-mycompany.usca.abc.com:8123:8121: Increase the heap size if required. See Tuning recommendations for large-scale enironments on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page In MS_home\bin, edit the am-start.sh script according to the number of kernels there are. If there are two kernels, then the am-start.sh script must hae the following commands: amctl.sh wd1 start amctl.sh wd2 start 6. In MS_home\bin, edit the am-stop.sh script according to the number of kernels there are. If there are two kernels, then the am-start.sh script must hae the following commands: amctl.sh wd1 stop amctl.sh wd2 stop Also edit the am-status.sh script in the same directory according to the number of kernels. 7. Start the Managing Serer. See Starting the Managing Serer on page For the Data Collectors connecting to this Managing Serer, restart the instances of the application serers that are being monitored by the Data Collectors. See Restarting the application serer on page 274. Adding additional Publish Serers To add an additional Publish Serer to the Managing Serer configuration, complete the following procedure: 1. Launch a Korn shell window: a. Start > Programs > Windows Serices for UNIX > Korn Shell Important: Do not use an already existing Korn shell. Instead, open a new Korn shell window. b. Change to the C directory, then change to the MS_home/bin directory: cd.. cd.. cd MS_home/bin For example, cd "Program Files/IBM/itcam/MS/bin" 88 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

109 Note: When changing to the MS_home/bin directory, if the file path that you specify contains spaces, place double quotation marks around the path. Use forward instead of backward slashes in the path. 2. Run the following command:./add-ps.sh port_number The port_number is the port number for this added instance of the Publish Serer. If a firewall exists the new port must be opened in the firewall. If you accepted the default port numbers for the Managing Serer components during the installation, see Table 8 on page 19 for a list of the port numbers that are already in use. For details on adjusting ports being blocked by your firewall, see Adjusting for ports that are being blocked by your firewall or are being used by other applications on page Increase the heap size if needed. See Tuning recommendations for large-scale enironments on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page It is recommended to stop Publish Serer for load balancing but it is optional if you want to aoid downtime. 6. When you are finished adding components, start the Managing Serer. See Starting the Managing Serer on page 265. Adding additional Archie Agents To add additional Archie Agents to the Managing Serer configuration, complete the following procedure: 1. Launch a Korn shell window: a. Start > Programs > Windows Serices for UNIX > Korn Shell Important: Do not use an already existing Korn shell. Instead open a new Korn shell window. b. Change to the C directory, then change to the MS_home/bin directory: cd.. cd.. cd MS_home/bin For example, cd "Program Files/IBM/itcam/MS/bin" Important: When changing to the MS_home/bin directory, if the file path that you specify contains spaces, place double quotation marks around the path. Use forward instead of backward slashes in the path. 2. Run the following command:./add-aa.sh port_number Theport_number is the port number for this added instance of the Archie Agent. If you accepted the default port numbers for the Managing Serer components during the installation, see Table 8 on page 19 for a list of the port numbers that are already in use. For details on adjusting ports being blocked by your firewall, see Adjusting for ports that are being blocked by your firewall or are being used by other applications on page Increase the heap size if needed. See Tuning recommendations for large-scale enironments on page 219 Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 89

110 4. If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page When you are finished adding components, start the Managing Serer. See Starting the Managing Serer on page 265. Split Managing Serer installation on Windows The Managing Serer consists of a number of components. See Oeriew of the Managing Serer on page 4 for a description of the Managing Serer components. In a standard installation, all of these components run on the same serer host. You can make more resources aailable for the Managing Serer by installing its components on two serer hosts (this is called a split installation). The serers must hae the same configuration. A split Managing Serer configuration uses increased processing power and memory across multiple serers, increasing performance of the Managing Serer. For optimal performance in a large deployment (oer 100 Data Collectors), consider using a split installation. Important: You can also install the Visualization Engine on a separate host. To do this, use the three step silent installation process; see Performing a three phase installation with three logins in Windows on page 53. The following components of the Managing Serer can hae multiple instances, running on the same serer or across two different serers: Kernel (and Watchdog). Adding additional Kernels, running across two or more serers, helps to aoid a Managing Serer failure if one serer fails. Publish Serer. Adding additional Publish Serers improes load handling and fault tolerance. In a network spanning multiple locations, you can set up at least one Kernel in each location and configure the Kernels to connect Data Collectors, when possible, to the local Publish Serer. Doing this reduces network traffic (see!!!). Archie Agent. Adding additional Archie Agents expands archiing capabilities. The following components must exist as one instance only, running on one serer: Visualization Engine (you can install it on a separate serer, see Performing a three phase installation with three logins in Windows on page 53) Message Dispatcher Global Publish Serer The Message Dispatcher component does not require significant resources; all other components can use processor power and memory heaily. Complete the following procedure to complete a split Managing Serer installation: 1. In adance, prepare a list of Managing Serer component instances to run on eery serer. 2. Install the Managing Serer using custom, or silent installation on one serer. (This serer is called the first serer; the other serer used for the split installation is called the second serer). 3. On the first serer, create all the additional component instances that are to run on eery serer. For example, if you plan to run the Publish Serer on three serers, two instances on each, create six instances of the Publish Serer. See Creating additional instances of Managing Serer components on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

111 4. Configure the Managing Serer on the first serer; do any necessary tuning, including port settings. Ensure that the configuration is working. 5. Install Microsoft Serices for UNIX on the second serer. See Installation and configuration of Microsoft Serices for UNIX or Subsystem for UNIX-based Applications on page Copy the jaa directory from AppSerer_home on the first serer to any location on the second serer. 7. Create a user for the Managing Serer on the second serer. The user name must be the same as the Managing Serer user on the first serer. 8. Copy the Managing Serer installation directory (MS_home) from the first serer to the same location on the second serer. 9. On the second serer, in MS_home\bin\seten.sh, adjust the setting for JAVA_HOME to the location of the jaa directory created in Step If there is no database client installed on the second serer: a. Copy the JDBC directory from the database serer (if you used the embedded DB2 installation the database serer is the first serer) to a location on the second serer. b. In the MS_home\bin\seten.sh file, for the JDBC_DRIVER_JAR property, specify the path where you added the JDBC directory in Step 10a. 11. On both the first and the second serers, in MS_home\bin\seten.sh, configure the am_socket_exportip and am_socket_bindip properties to point to the host name or IP address of the serer host where the file is located. 12. On both the first and the second serers, in MS_home\etc\ms.properties, configure the kernel.hosts property to contain information about both kernels. For example: kernel.hosts=serer1.company.com:9122:9120:9118, serer2.company.com:9122:9120:9118 Note: Keep the port definitions identical on both serers. If the second Managing Serer is behind a different firewall, the port must be opened in the firewall. For details on adjusting ports being blocked by your firewall, see Adjusting for ports that are being blocked by your firewall or are being used by other applications on page On both the first and the second serers, in MS_home\etc\e.properties, adjust the settings for kernel.codebase and kernel.rfs.address to point to the host name or IP address of the serer host where the file is located. 14. On both the first and the second serers, modify the startup script,ms_home\bin\am-start.sh to indicate which components must be started on the serer. You can choose which components run on each serer, but both serers cannot start (or stop) the same component ID. Important: a. You must run the Message Dispatcher on the first serer. b. See Table Table 19 on page 87 for a listing of the component IDs. c. See Oeriew of the Managing Serer on page 4 for a description of the Managing Serer components. d. Only the Watchdog instance (wd1 or wd2) is mentioned in the start/stop/status scripts, because the Watchdog controls the starting, stopping, and status of the kernel. Here are examples of lines from two am-start.sh scripts that complement each other: Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 91

112 From first Managing Serer: ${CYANEA_HOME}/bin/amctl.sh wd1 start #${CYANEA_HOME}/bin/amctl.sh wd2 start ${CYANEA_HOME}/bin/amctl.sh aa1 start #${CYANEA_HOME}/bin/amctl.sh aa2 start ${CYANEA_HOME}/bin/amctl.sh ps1 start #${CYANEA_HOME}/bin/amctl.sh ps2 start ${CYANEA_HOME}/bin/amctl.sh md start ${CYANEA_HOME}/bin/amctl.sh pa start ${CYANEA_HOME}/bin/amctl.sh sam1 start From second Managing Serer: #${CYANEA_HOME}/bin/amctl.sh wd1 start ${CYANEA_HOME}/bin/amctl.sh wd2 start #${CYANEA_HOME}/bin/amctl.sh aa1 start ${CYANEA_HOME}/bin/amctl.sh aa2 start #${CYANEA_HOME}/bin/amctl.sh ps1 start ${CYANEA_HOME}/bin/amctl.sh ps2 start #${CYANEA_HOME}/bin/amctl.sh md start #${CYANEA_HOME}/bin/amctl.sh pa start #${CYANEA_HOME}/bin/amctl.sh sam1 start Important: These examples reflect that a second Kernel was added to the default Managing Serer configuration. 15. On each serer, complete the same modifications to the stop script MS_home\bin\am-stop.sh. 16. On each serer, complete the same modifications to the MS_home\bin\amstatus.sh script. It is a status script, used internally by Windows serices to check the status of Managing Serer components. 17. Start both serers. See Starting the Managing Serer on page 265. Note: When starting or stopping the Managing Serer on seeral serers, start and stop the serer that runs the Visualization Engine first. You can use an automation mechanism to coordinate this process. One such automation mechanism is the use of a remote execution shell. Tip: To query the status of all the components such as Archie Agent, Publish Serer, or Message Dispatcher een if one of the Kernels is not running, complete the optional steps in the next section 18. When all the components are started on both the serers, erify the split Managing Serer configuration in the Visualization Engine. Click Administration > Managing serer > Self Diagnosis. In the component window, the running components and their IP addresses are displayed. Optional steps to query the status of components when one of the Kernels is not running By modifying the scripts on the first and second serer to include information about the Kernel on the other serer, you can still query the status of components een if one of the Kernels is not running. For each of the following files, add the code shown in bold: 1. On the first Managing Serer, add the code shown in bold to the following file: MS_home\bin\psctl.sh RMI_CODEBASE=" ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.publish.jar ${PORT_KERNEL_CODEBASE01}/model.jar ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.probe-intf.jar ${PORT_KERNEL_CODEBASE01}/kernel.common.jar ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

113 ${PORT_KERNEL_CODEBASE02}/model.jar ${PORT_KERNEL_CODEBASE02}/kernel.common.jar" export RMI_CODEBASE SECURITY_POLICY=${CYANEA_HOME_OS}/etc/ps.policy export SECURITY_POLICY KERNEL_CODEBASE=" export KERNEL_CODEBASE KERNEL_RFS_ADDRESS="${KERNEL_HOST01}:${PORT_KERNEL_RFS01} ${KERNEL_HOST02}:${PORT_KERNEL_RFS02}" export KERNEL_RFS_ADDRESS 2. On the first Managing Serer, add the code shown in bold to the following file: MS_home\bin\aactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" archieagent.jar /archieagent.jar" export RMI_CODEBASE 3. On the first Managing Serer, add the code shown in bold to the following file: MS_home\bin\pactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" pollingagent-intf.jar archieagent-intf.jar export RMI_CODEBASE 4. On the first Managing Serer, add the code shown in bold to the following file: MS_home\bin\mdctl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS01=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" messagedispatcher-intf.jar messagedispatcher-intf.jar" export RMI_CODEBASE 5. On the second Managing Serer, add the code shown in bold to the following file: MS_home\bin\psctl.sh RMI_CODEBASE=" ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.publish.jar ${PORT_KERNEL_CODEBASE01}/model.jar ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.probe-intf.jar ${PORT_KERNEL_CODEBASE01}/kernel.common.jar Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 93

114 ${PORT_KERNEL_CODEBASE02}/model.jar ${PORT_KERNEL_CODEBASE02}/kernel.common.jar" export RMI_CODEBASE SECURITY_POLICY=${CYANEA_HOME_OS}/etc/ps.policy export SECURITY_POLICY KERNEL_CODEBASE=" export KERNEL_CODEBASE KERNEL_RFS_ADDRESS="${KERNEL_HOST01}:${PORT_KERNEL_RFS01} ${KERNEL_HOST02}:${PORT_KERNEL_RFS02}" export KERNEL_RFS_ADDRESS 6. On the second Managing Serer, add the code shown in bold to the following file: MS_home\bin\aactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" archieagent.jar export RMI_CODEBASE Fine-tuning Managing Serer properties To best suit your enironment, you can fine-tune the settings in the Managing Serer properties files described in Appendix I, Managing Serer properties files, on page 299. Tuning recommendations for large-scale enironments The following steps are tuning recommendations for when the Managing Serer is used for supporting large-scale enironments or high olumes of request traffic. For example, when there are 250 Data Collectors running at a total of 500 requests per second: Tip: If you plan to deploy more than 100 Data Collectors, or if you intend to use high monitoring leels (L2/ L3) frequently, for example in a deelopment or testing enironment, it is recommended that you use a split Managing Serer installation for better scalability, performance, and reliability. See Split Managing Serer installation on Windows on page 90 for split Managing Serer installation. 1. Increase the maximum heap size settings of the Kernel, Publish Serers, and Global Publish Serer. The Global Publish Serer change is only necessary if you are using the correlation feature in ITCAM for Application Diagnostics. In MS_home/bin/seten.sh, modify the following properties: HEAP_MAX_SIZE_PS=1024 HEAP_MAX_SIZE_KERNEL=512 HEAP_MAX_SIZE_SAM= Increase the maximum heap size used by the ITCAM for Application Diagnostics Managing Serer. Do the following steps: a. Log in to the IBM WebSphere Application Serer administratie console. b. Naigate as follows: 1) Click Serer > Application Serers and select the serer_name. 94 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

115 2) In the Configuration tab, naigate to Serer Infrastructure > Jaa and Process Management > Process Definition > Additional Properties: Jaa Virtual Machine. 3) Modify the maximum heap size of the serer to be Open a Korn shell window. Go to Start > Programs > Windows Serices for UNIX > Korn Shell Important: Do not use an already existing Korn shell. Instead open a new Korn shell window. 4. Change to the C directory, then change to the MS_home/bin directory: cd.. cd.. cd MS_home/bin For example, cd "Program Files/IBM/itcam/MS/bin" Note: When changing to the MS_home/bin directory, if the file path that you specify contains spaces, place double quotation marks around the path. Use forward instead of backward slashes in the path. 5. If you hae not already created an additional instance of the Kernel, follow the instructions at Adding an additional kernel on page Modify heartbeat settings. In MS_home/etc/kl1.properties, modify the following property: contract.duration=60 7. Start one more instance of the Kernel from the MS_home/bin directory:./amctl.sh wd2 start 8. If you hae not already created two additional instances of the Publish Serer, follow the instructions at Adding additional Publish Serers on page Start two more instances of the Publish Serer from the MS_home/bin directory:./amctl.sh ps3 start./amctl.sh ps4 start 10. If you hae not already created two additional instances of the Archie Agent, follow the instructions at Adding additional Archie Agents on page Start two more instances of the Archie Agent from the MS_home/bin directory../amctl.sh aa3 start./amctl.sh aa4 start 12. Increase MAXAPPLS and MAXAGENTS for the database. Complete the following procedure: a. Switch to the database instance user. For example: su - db2inst1 b. Choose one of the following options: If you do not hae a partitioned database, run the following commands: update dbm cfg using MAXAGENTS 500 db2 update db cfg for octigate using maxappls 300 db2stop db2start If you hae a partitioned database, the DBA needs to run the following commands. For example, if you hae a three node partitioned database: Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 95

116 db2 terminate export db_node0 db2 update db cfg for octigate using MAXAPPLS 300 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate export db_node1 db2 update db cfg for octigate using MAXAPPLS 300 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate export db_node2 db2 update db cfg for octigate using MAXAPPLS 300 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate If large amounts of data in the tables affected by the datatrim.sh script, the LOGFILSIZ and LOGSECOND parameters must be increased across all database partition nodes. 13. Set the Remote Method Inocation (RMI) timeout in the Data Collector. The Data Collector sockets are initially set for infinite time out. This setting can make the defensie calls of the Kernel hang and deplete the Kernel if there is a problem with a Data Collector. Set the following property for all Data Collectors in DC_home/runtime/appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties: am.rmisocket.timeout=60000 Enabling method signature tracing Turning on method signature tracing increases performance demand. Increasing method signature length increases hard disk consumption. To enable method signature tracing and (optionally) modify method signature length, complete the following procedure: 1. Before you can enable method signature tracing, the Data Collector connecting to the Managing Serer must be installed and configured. See one of the following publications: IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide IBM Tioli Composite Application Manager for WebSphere (z/os): Data Collector Customization Guide IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 2. In the DC_home/runtime/app_serer_ersion.node_name.serer_name/custom/ toolkit_custom.properties file, uncomment the following line by remoing the number sign (#) at the beginning of the line: am.camtoolkit.gpe.customxml.l3=dc_home/itcamdc/etc/method_entry_exit.xml 3. Set the following property to true: com.ibm.tioli.itcam.toolkit.ai.methodentryexittrace=true 4. (Required only if you are integrating the Managing Serer with IBM Rational Performance Tester) The method signature length is defined in the Archie Agent properties by the TEXTSTRING_LENGTH entry, with a default alue of 60. Increase or decrease the length, as needed, in the Archie Agent properties files (such as aa.properties, aa1.properties and aa2.properties). 5. (Required only if you are integrating the Managing Serer with IBM Rational Performance Tester) If you want to see the method signature from the ITCAM 96 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

117 Setting up the reports for Application Diagnostics Managing Serer (for example, from a drill-down iew), the following line must be added to the Publish Serer properties files (such as ps1.properties and ps2.properties): display_method_signature=true Method signature tracing is only actie when the monitoring is set to MOD Leel 3. ITCAM for Application Diagnostics includes a traps feature that enables you to hae messages sent when certain thresholds are reached. For this feature to work, the SMTP host must be specified. The Performance Analysis and Reporting (PAR) section and the Traps section do not send reports without this step. Complete the following procedure to specify the SMTP host: Edit MS_home/etc/md.properties to specify the correct fully qualified host name or IP address of the SMTP host. (A alid serer is required; contact your Administrator for this information.) Use the following format: smtp.host=aa.bb.cc.dd Substitute the IP address or fully qualified host name of the SMTP host for aa.bb.cc.dd. Attention: If your Managing Serer Visualization Engine is not running on default port 9080, you must set up the Visualization Engine port for notifications. See Setting up the Visualization Engine port for notifications on page 98. Report Link and PDF feature To use this feature, you must specify a alid address to enable the Report Link and PDF feature. Set the e.framework. .sender property in MS_home/etc/e.properties with a alid address on your own SMTP domain. For example: e.framework. .sender=support@usca.ibm.com When you change this property, recycle the Visualization Engine application serer to ensure that all scheduled reports created after this use the new sender address. If you change the address again, deactiate existing scheduled reports and actiate them again using the Performance Analysis->View Saed Reports->Scheduled Reports option, so that the new sender address takes effect for preexisting scheduled reports. Trap notification In order to use this feature, you must set the user.name property in MS_home/etc/ps1.properties and in ps2.properties. By default, the user name is set to IBM_ITCAM. You must change the user name to a alid address in order for notification to be used on all outgoing trap . For example, user.name=support@usca.ibm.com Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 97

118 Setting up the Visualization Engine port for notifications Setting up SNMP If your Managing Serer Visualization Engine is not running on default port 9080 then you might hae to edit the Publish Serer properties files MS_home\etc\ps1.properties and MS_home\etc\ps2.properties. If additional Publish Serer instances exist, you must modify the properties files for them as well: MS_home\etc\ps3.properties,MS_home\etc\ps4.properties and so on. The e.port alue sets the port number that is used in the URL that in included in the . The user is to be able to access the Visualization Engine using this URL; therefore, the port must be set to the Visualization Engine HTTP port. Edit the ariable e.port as follows: e.port=ms_port To set up SNMP alerts, making them aailable in Trap and Alert Management, see the following sections: Appendix G, IBM Tioli Enterprise Console integration, on page 291 Appendix H, BMC Patrol integration, on page 295 Configuring a Managing Serer on a host with multiple network interfaces and NATs The Managing Serer always binds to one network interface (IP address) only, een on a host with multiple network interfaces If the Managing Serer always exposes a specific IP to all Data Collectors, complete the following steps: 1. On the Managing Serer side, in seten.sh (in MS_home/bin), set KERNEL_HOST01 to the IP address of the Managing Serer. You must also set the following parameters: am_socket_bindip=<ipaddress_ms> am_socket_exportip=<ipaddress_ms> 2. On the Managing Serer side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin), add jaa.rmi.serer.hostname to the jaa command-line in the start section of the script. Then set it to IP address of the Managing Serer. 3. You must edit the MS_home/etc/e.properties file kernel.codebase alue to point to the correct IP address. This setting also affects DHCP where you must hardcode the dynamic DNS host name rather than an IP address in the MS_home/etc/e.properties file. 4. In MS_home/etc/ms.properties, you must modify kernel.hosts to indicate the IP address of the Managing Serer: kernel.hosts=<ipaddress_ms>cbsport:rfsport:rmiport By default, the IP address is kernel.hosts=<ipaddress_ms>9122:9120: In addition, if the Managing Serer was installed on multiple serers, make the changes from Steps 1 through 3 on all the serers where the Managing Serer is installed. 6. On the Data Collector side, in the DC_home/runtime/ appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or 98 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

119 DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties file, ensure that the kernel.codebase and kernel.rfs.address properties hae the correct IP address for the Managing Serer. 7. On the Data Collector side, in the DC_home/itcamdc/etc/datacollector.policy file, ensure that the socket permissions (jaa.net.socketpermission) are granted to the right IP address for the Managing Serer. The Managing Serer can also expose different IP addresses to different Data Collectors because of Network Address Translation (NAT), een though it binds to only one IP address on the host. In this case, complete the following procedure: 1. On the Managing Serer side, in seten.sh (in MS_home/bin), set KERNEL_HOST01 to the fully qualified domain name of the Managing Serer (for example qaapp-lnx-s01.usca.ibm.com). 2. On the Managing Serer side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin/), add jaa.rmi.serer.hostname to the jaa command-line in the start section of the script and set it to the fully qualified domain name of the Managing Serer. 3. In addition, if the Managing Serer was installed on multiple serers, make the changes from Steps 1 and 2 on all the serers where the Managing Serer is installed. 4. On the Data Collector side, in the DC_home/runtime/ appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties file, make sure that the kernel.codebase and kernel.rfs.address properties hae the right IP address (or fully qualified host name) for the Managing Serer. 5. On the Data Collector side, in the DC_home/itcamdc/etc/datacollector.policy file, ensure that the socket permissions (jaa.net.socketpermission) are granted to the right IP address (or fully qualified host name) of the Managing Serer. 6. Ensure that on the Data Collector side, the fully qualified host name of the Managing Serer can be resoled to the correct IP address. You can use ping to erify this. Adjusting maximum resource settings for the operating system You can change the ulimit settings to aoid running out of file handles, sockets, or memory. If you receie error messages related to file handles, sockets, or memory, or if you think this is likely to happen, for example if your enironment is running multiple instances of IBM WebSphere Application Serer, you can change the ulimit settings. To change the ulimit settings, complete the following procedure: 1. Log in as Administrator. 2. Click Start > Run then enter regedit. 3. Click HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Serices for UNIX. 4. Complete one of the following options: If a file named MaxOpenFiles exists in that directory, open it. If a file named MaxOpenFiles does not exist in that directory: a. Click Edit > New > DWORD Value. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 99

120 b. Enter MaxOpenFiles for the name. c. Open MaxOpenFiles. 5. Change the base to Decimal. 6. Enter the Value data. The recommended setting is Close Registry Editor. 8. Restart Windows. 9. Log in as either Administrator or the installation user. (See Users that are created before or during the installation on page 20.) 10. Launch a Korn shell window: Start > Programs > Windows Serices for UNIX > Korn Shell. Note: Do not use an already existing Korn shell. Instead, open a new Korn shell window. 11. Verify that the new ulimit setting has been set: ulimit -a Performance tuning the MSVE Increase the MSVE WebSphere JVM maximum heap size when performance is slow for Trap Action History Method Traces If you experience slow response time when loading the Trap Action History Method Trace page in MSVE, increase the MSVE WebSphere JVM heap size. To determine if you want to increase the JVM maximum heap size, take the following steps: 1. On the menu, select Problem Determination -> Trap & Alert Management. 2. Click the Trap Action History link. The TRAP ACTION HISTORY page is displayed. 3. Click Method Trace. If there are many records on the page, the performance can be slow. If so, take steps to increase the MSVE WebSphere JVM heap size. Assigning local Publish Serers to local Data Collectors to reduce WAN traffic in a split Managing Serer installation By default, the Managing Serer kernel assigns Publish Serers to Data Collectors based on Publish Serer aailability, using a round robin algorithm. On a multiple site deployment, this can lead to a Data Collector on one site being assigned to a Publishing Serer on a different site, een if a Publishing Serer on the same site is aailable. This generates significant network traffic between sites and can adersely affect performance. To ensure that a local Publish Serer is assigned to Data Collectors when aailable, you can set up a subnet policy algorithm instead of round robin. In the subnet policy algorithm, each Data Collector is assigned a Publish Serer that resides under the same subnet as the Data Collector. That is, each Data Collector on Site A is assigned a Publish Serer also located on Site A (if such a Publishing Serer is aailable). This type of subnet policy applies only for Data Collector and Publish Serer assignment. It does not apply to Archie Agent, which is still assigned to Publish Serer based on the Round Robin algorithm. 100 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

121 Important: If you hae more than one kernel, all kernels must hae the same policy settings. Currently roundrobin policy for one kernel and subnet policy for another kernel is not supported. Moreoer, all the other properties related to this policy must also be the same in all kernel properties file. You can adjust the policy on all kernels only at the same time. To enable the subnet policy, based on the IP address and host name, complete the following steps. 1. Modify the following parameters in the kl1.properties and kl2.properties files, located in MS_home\etc. a. policy=subnet In the policy parameter, roundrobin means the default algorithm; subnet enables the subnet algorithm. If this property is not specified, the kernel uses the default roundrobin algorithm. b. subnet.policy.autodetect=true or subnet.policy.autodetect=false If subnet.policy.autodetect is set to true, the kernel finds the best matching Publish Serer for a Data Collector based on their IP addresses. The best match is determined by comparing IP addresses of the Data Collector and Publish Serer. At least the first two numbers of the IP address must be the same. For example, if two Publish Serers hae the following addresses: ps1= ps2= For Data Collector on dc1= , ps2 is assigned. For Data Collector on dc2= , ps1 is assigned. For Data Collector on dc3= , there is no match. The kernel falls back to a round robin algorithm, and assigns the first aailable PS, which can be either ps1 or ps2. For subnet.policy.autodetect=true, you do not hae to define any subnet groups. If subnet.policy.autodetect is not specified, true is assumed. If subnet.policy.autodetect is set to false, you must define subnet policy groups. These groups include IP addresses and hostnames of Data Collector and Publish Serer hosts. For example: subnet.policy.group1= *.*, *.*,deapp-lnx-*, subnet.policy.group2= *.*, *,*-lnx-*,serer.company.com... subnet.policy.groupn= *.*,92.82.*.* N can be 1, 2, You can use any numbers from 1 to 100; no particular sequence is required. Eery group can hae as many IP addresses or hostnames as needed, appearing as full alues or masks, separated by commas. Each group must include IP addresses or host names of at least one Data Collector and at least one Publish Serer; otherwise, Data Collectors in this group are assigned to other Publish Serers. Important: In an IP address mask, eery component of the address must be either a number or an asterisk. For example, 192.*.*.2 is a alid mask, but 192.2*.1*3.2 is not a alid mask. The Data Collector is assigned a Publish Serer that falls into the same policy group as the Data Collector. If there are multiple Publish Serers within the same subnet group, the round robin algorithm is used among them. You can specify both 4 byte and 6 byte IP address groups. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 101

122 If you do not specify the groups, or if a Data Collector does not fall into any of the specified groups, or if no Publish Serer is aailable under the same policy group as a Data Collector, the kernel falls back to autodetection, and assign the closest aailable Publish Serer according to the IP address of the Data Collector. It is not necessary that different IP patterns under same policy group reside under the same subnet mask. Note that a Data Collector is assigned to a Publish Serer under the same policy group, but they might be under different subnet masks. It is your responsibility to proide Publish Serers and define the right policy groups to proide for load balancing and aoid inter-site network traffic. For example, the following scenario can hae a major performance affect: 2000 Data Collectors and 6 Publish Serers on Site A 6000 Data Collector and 2 Publish Serers on Site B In this case, the Publish Serers on Site B can get a larger load. It is your responsibility to either change assignment policies or add more Publish Serers to Site B. 2. Uncomment the following property in the kl1.properties and kl2.properties files, located in MS_home\etc: kernel.accept.request.duration=5 You can set a higher alue if you want. The default alue is 3. It is expected that all Managing Serers (kernels) are started within the set number of minutes (by default, 3 minutes; with the uncommented line as quoted, 5 minutes). The kernel waits for this duration before it starts assigning Data Collectors to Publish Serers. If one of the Managing Serers is not started within this time, other kernels assign Data Collectors to Publish Serers without taking the missing Publish Serers into account. This can lead to Data Collectors being assigned to wrong Publish Serers. For example, you can hae two Publish Serers on two different hosts: host1= host2= Data Collectors are also running on both hosts. Suppose you start Managing Serer 1 but wait longer than kernel.accept.request.duration minutes to start the Managing Serer 2. In this case, as the publish serer on host2 is not yet aailable, the kernel assigns the Data Collector on host2 to the Publish Serer on host1. Therefore, you must start all Managing Serers within the duration set in kernel.accept.request.duration. 3. Stop all Managing Serers by using the MS_home/bin/am-stop.sh script. Check if any process has not stopped (and therefore is hanging); in this case, run the MS_home/bin/am-forcestop.sh script. 4. Start all Managing Serers by using the MS_home/bin/am-start.sh script. Tip: You can check the current assignment of Data Collectors to Publish Serers using the Managing Serer Self Diagnosis window. In the Visualization Engine main menu, select Administration > Managing Serer > Self diagnosis; then select eery Publish Serer to iew a list of Data Collector relationships. If any Data Collector is working with the Managing Serer but not displayed in this window for any of the Publish Serers, select Administration > Serer Management > Data Collector Configuration > Configured Data Collectors from 102 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

123 the main menu, then unconfigure the affected Data Collector and configure it again. After this, it will be listed in the Self diagnosis window for one of the Publish Serers. Important: Sometimes, a serer would belong to more than one user-defined policy group according to its host name and IP address. In this case, the following priority rules apply: If the host name belongs to more than one policy group, the group with the lower number takes priority. For example, if the host name fulfills the criteria for both subnet.policy.group2 and subnet.policy.group4, subnet.policy.group2 takes priority. If the IP address belongs to more than one policy group, the more specific definition takes priority. For example, if the address is , subnet.policy.group1 includes *.*, and subnet.policy.group2 includes *, subnet.policy.group2 takes priority. If the IP address or host name belongs to more than one policy group and the definitions are of the same leel of specificity, the group with the lower number takes priority. Creating additional users to log in to the ITCAM for Application Diagnostics Managing Serer As part of the installation and configuration of the serer for the ITCAM for Application Diagnostics Managing Serer, an initial user was set up with the information proided during the installation process. This user is a member of the Windows Administrators group and has full administratie rights and access to the serer for the ITCAM for Application Diagnostics Managing Serer. See the following sections: Custom installation and upgrade: creating the user interface user on page 14 For security purposes, you can add more users to the serer for the ITCAM for Application Diagnostics Managing Serer. See the account management chapter of the IBM Tioli Composite Application Manager: Users Guide or online help. Changing the user name and password for the database schema user The schema user owns and can create database tables for the Managing Serer. To change the user name and password for the schema user, complete the following procedure: 1. Create a local Windows account associated with the new user, new_user_name. Tip: To change the password for the installation user without changing the user name, change the password of the user on the local operating system. 2. Encrypt the new password for the database schema user by completing the following steps: a. From a command line, change to the MS_home/bin directory. b. Enter the following command:./amcrypto.sh -encrypt new_user_pwd Running the script produces an output that is the encrypted ersion of the new_user_pwd. c. Copy this output and use it as the alue you enter for the JDBC_PASSWORD parameter of the seten.sh file, in the next step. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 103

124 3. Modify the MS_home/bin/seten.sh and edit the following parameters: JDBC_USER=new_user_name JDBC_PASSWORD=new_user_pwd 4. Change ownership of the MS_home directory using the following command, if you want to start your processes as the new user. chown -R new_user_name MS_home 5. Log in to the IBM WebSphere Application Serer administratie console where the ITCAM for Application Diagnostics Managing Serer is installed. 6. Expand Resources > JDBC Proiders > (Choose the JDBC Proider for ITCAM for Application Diagnostics) > Data Sources > (Choose the DataSource) > J2C Authentication Data Entries > (Choose the J2C Authentication Data Entries). 7. In the User ID field, type in the new user. 8. In the password field, type in the password corresponding to the new user. 9. Click OK. 10. Sae the changes. 11. Restart the instance of IBM WebSphere Application Serer used by the Managing Serer. See Restarting the application serer on page 274. Enabling the feature to launch into the IBM Tioli Enterprise Portal from the ITCAM for Application Diagnostics Managing Serer You can enable a feature that allows you to go directly from theitcam for Application Diagnostics Managing Serer user interface for the IBM Tioli Enterprise Monitoring Agent, which is called IBM Tioli Enterprise Portal, without launching the portal manually. It is done from the ProblemCenter > Resource page of the ITCAM for Application Diagnostics Managing Serer. You must first modify the MS_home/etc/e.properties file. Enter appropriate alues for the following properties. They are described at e.properties on page 302: tep.hostname tep.port tep.baseurl tep.userid Using the Managing Serer with a 6.0 Data Collector You can use Data Collectors from ITCAM for WebSphere 6.0 or ITCAM for J2EE 6.0 with the current Managing Serer. To do this, complete the following procedure on the Managing Serer. You can complete this procedure only under the following conditions: You still hae an existing ersion 6.0 installation of the Data Collector. You still hae an existing ersion 6.0 of the Managing Serer. Tip: You do not hae to complete this procedure to use a Data Collector from ITCAM for WebSphere 6.1, ITCAM for J2EE 6.1, or ITCAM for Web Resources 6.2 with the current Managing Serer. Complete the following procedure to enable the Managing Serer to communicate with a ersion 6.0 Data Collector: 1. Stop the ersion Managing Serer. See Stopping the Managing Serer on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

125 2. Copy the lib6.0 directory from the 6.0 MS_home directory to the ersion MS_home directory. Do not rename the lib6.0 directory. 3. On each host where the 6.0 Data Collector is installed: a. modify the DC_home/etc/datacollector.properties file to point to the ersion Managing Serer: 1) If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, modify the alues for the host name. Here is an example of the modified parameters: kernel.codebase= kernel.rfs.address=linux-machine1.usa.company.com:9120 linux-machine1.usa.company.com:9121 2) By default, the ersion Managing Serer has only one kernel, while the ersion 6.0 Managing Serer has two. If you do not plan to manually create an additional kernel for the ersion Managing Serer, remoe references to the second listed port for the kernel.codebase and kernel.rfs.address parameters. (By default, the second port is 9123 and 9121, respectiely.) Match what you see in the datacollector.properties file for a Data Collector. The alues in the 6.0 datacollector.properties file match what you see in the datacollector.properties file for a Data Collector. For example, kernel.codebase= /kernel.core.jar /ppe.publish.jar /ppe.publish-intf.jar kernel.rfs.address=linux-machine.usa.company.com:9120 b. If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, modify the permission jaa.net.socketpermission in the DC_home/etc/datacollector.policy file to point to the ersion Managing Serer host name. For example: permission jaa.net.socketpermission "linuxmachine.usa.company.com", "connect,accept,resole"; c. If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, in the DC_home/etc directory, delete node_name.serer_name.datacollector.properties d. If you are not migrating data from the ersion 6.0 Managing Serer to the ersion Managing Serer, in the DC_home/etc directory, delete node_name.serer_name.cyaneagpscounter.txt e. (optional) If you want the Data Collector run time to generate a new set of IDs for Probe and ProbeController, delete the DC_home/etc/ node_name.serer_name.id file. f. If the path for the ersion MS_home is different from the path for the ersion 6.0 MS_home, change the MS_AM_HOME enironment ariable in the WebSphere Application Serer administratie console to point to the ersion Managing Serer installation directory by completing the following steps: 1) Log in to the WebSphere Application Serer administratie console, in the Naigation Pane, select Enironment -> WebSphere Variables. 2) Select the scope of the ariable to add. Most ariables used by the Data Collector are at the serer scope of your monitored serer. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 105

126 3) Change the following enironment ariable to point to the MS_home for the ersion Managing Serer: MS_AM_HOME=MS_home 4) Click Apply or OK. In the Messages dialog box, click Sae. 5) In the Sae to Master Configuration dialog box, complete one of the following procedures: a) If you are under a Network Deployment enironment, select Synchronize changes with Nodes and click Sae. b) If you are not under a Network Deployment enironment, click Sae. 4. Start the ersion Managing Serer. See Launching the ITCAM for Application Diagnostics Managing Serer on page Restart all applications serer instances monitored by the 6.0 Data Collectors. 6. Check the SystemOut.log to erify that the Data Collector has connected to the ersion Managing Serer. You get a message similar to the following: [1/9/08 14:11:34:380 PST] SystemOut O <PPECONTROLLER, 60a8abc2-abcd-dc01-a e , > Successfully joined Kernel linux-machine.usa.company.com: Log in to the Visualization Engine (Application Monitor) user interface and configure the ersion 6.0 Data Collector to be monitored by the ersion Managing Serer by taking the following steps: a. Select Administration -> Serer Management -> Data Collector Configuration -> Unconfigured Data Collectors. b. Check to see that the serer for the Data Collector is listed. c. Apply a configuration to the Data Collector in the Application Monitor user interface. d. Verify that the Data Collector components are enabled and running in the Self-Diagnosis page of the Application Monitor user interface. e. Verify that the Data Collector is communicating with the Managing Serer. 8. (optional) Since the ersion 6.0 Data Collector does not connect to the ersion 6.0 Managing Serer anymore, unconfigure it from the Application Monitor user interface for the ersion 6.0 Managing Serer. Changing the IP address or host name of the Managing Serer These are instructions for changing the IP address or fully qualified host name of a Managing Serer. Furthermore, you must modify the Data Collector. Changing the IP address or fully qualified host name of a Managing Serer without updating the Data Collectors associated with that change disrupts communication and causes policies to fail. To change the IP address or fully qualified host name, complete the following procedure: 1. Stop the Managing Serer. See Stopping the Managing Serer on page Stop the instance of IBM WebSphere Application Serer that is being used by the Managing Serer. Complete the steps in Stopping the application serer on page Change the IP address or fully qualified host name on the Managing Serer. Contact your system administrator on the proper procedure for your system. 4. Change the corresponding system configuration for the Data Collector serer to access the Managing Serer by host name. Contact your system administrator on the proper procedure for your system. 106 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

127 5. Start the instance of IBM WebSphere Application Serer that is being used by the Managing Serer. See Starting the application serer on page Start the Managing Serer. See Starting the Managing Serer on page Reconfigure the Data Collector by running the Configuration Tool. In the process, select Recollect Managing Serer information in the Managing Serer information summary panel. See the IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide. 8. Restart the instance of the application serer that is being monitored by the Data Collector. See Restarting the application serer on page 274. Making sure that the Managing Serer host name connects to the correct IP address The Data Collector obtains the Managing Serer Kernel network address from the Managing Serer. If a host name is specified for the Kernel, it is possible that one of the resoled IP addresses cannot reach the Managing Serer from the Data Collector. If so, the connection to the Data Collector fails with a Connection refused error message. To aoid a failed connection, instead of the host name, specify a alid IP address in themanaging Serer MS_home/bin/seten.sh and MS_home/etc/ms.properties files. Complete the following procedure: 1. To determine IP addresses for a gien Managing Serer host name, issue the following command from the Data Collector serer: nslookup MS_hostname 2. To test basic connectiity, on the Data Collector computer, for each IP address listed in the output from the preious step, issue the following command: ping ip_address 3. On the Managing Serer serer, in the MS_home/bin/seten.sh file, set the following properties to the IP address of the Managing Serer: KERNEL_HOST01 am_socket_bindip am_socket_exportip For example: KERNEL_HOST01= am_socket_bindip= am_socket_exportip= On the Managing Serer serer, in the MS_home/etc/ms.properties file, set the following property, as follows: kernel.hosts=msipaddresscbsport:rfsport:rmiport For example: kernel.hosts= :9122:9120:9118 This solution usually works except when there is a firewall with Network Address Translation (NAT) enabled. In that case, you must make network changes so that all the resoled IP addresses can reach the Managing Serer. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 107

128 Sustaining large amounts of trace If many calls are being traced, and some method data is not displayed in the Visualization Engine, complete the following procedure to configure the Managing Serer to sustain large amounts of trace: 1. Increase the method count limit of the Publish Serer. The Publish Serer maintains the method trace for the requests. The number of method entries or exits in this method trace is limited. By default it is If any request has more method records than this number, the Publish Serer truncates the method trace of a request to limit the total method entry or exit count to the configured alue. By configuring the property Maximum Method Records you can control the number of method entries or exits in the method trace of a request.to increase the limit, change the property Maximum Method Records in the ITCAM for Application Diagnostics Managing Serer. From the top naigation, select Administration > Managing Serer > System Properties. Change the alue of Maximum Method Records to from Increase the Jaa heap size of the Archie Agent. The runtime memory of the Archie Agent must be increased as a potentially bigger method trace from the Publish Serer. Set HEAP_MIN_SIZE_ARCHIVE_AGENT=1024 and HEAP_MAX_SIZE_ARCHIVE_AGENT=2048 in file MS_home/bin/seten.sh to increase the Jaa heap size. 3. Reduce the batch size of the Archie Agent. The Archie Agent tries to batch process a specified number of requests. The default is 20 requests. It hits the limit of the IBM DB2 drier with the large requests. Change REQUESTDATA_BUFFER_THRESHOLD=20 to REQUESTDATA_BUFFER_THRESHOLD=1 in MS_home/etc/aa.properties. 4. Increase the Jaa and JNI stack size of the Archie Agent. Een one large request can hit the IBM DB2 drier limit. To aoid this, add -Xoss8M and -Xss8M in the Jaa startup command in the MS_home/bin/aactl.sh file. ${JAVA_HOME}/bin/jaa -class path $CLASSPATH -Xoss8M -Xss8M 5. Increase the query heap size of the IBM DB2 serer to accommodate the large batch query from the Archie Agent as follows: db2 update dbm cfg using parameter alue For example, db2 update dbm cfg using query_heap_sz 8000 Also, if the composite transaction tracking feature is enabled, increase the heap size of the GPS component. Set the following parameters in MS_home\bin\seten.sh: HEAP_MIN_SIZE_SAM=256 HEAP_MAX_SIZE_SAM=1024 Starting ITCAM for Application Diagnostics automatically upon reboot If you want ITCAM for Application Diagnostics to start automatically upon reboot, you can actiate the appropriate scripts for the components. A person such as a system administrator can create an autostart daemon to start ITCAM for Application Diagnosticss components upon reboot. Here is the suggested sequence for restarting components: 1. IBM DB2 or Oracle (IBM DB2 installation might hae already created this.) 2. HTTP Serer 108 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

129 3. IBM WebSphere Application Serer 4. Managing Serer (The script for starting the Managing Serer is MS_home/bin/am-start.sh.) Enabling a legal banner at login time If you want a legal banner to be shown when you log in to the Visualization Engine, you can enable a property in the e.properties file. To show the following dialog when you log in to the Visualization Engine: Set the legaldepartmentapproed.enable property in MS_home/etc/e.properties file to true as follows: legaldepartmentapproed.enable=true To disable the dialog at login, set the legaldepartmentapproed.enable property to false as follows: legaldepartmentapproed.enable=false Windows 2003 Serer: manually configuring the Managing Serer to run as a serice The Managing Serer on Windows 2003 Serer must be configured to run as a serice. The Managing Serer installer automatically completes this configuration. Howeer, if the Managing Serer was installed before ersion , or if the Windows serice setup is lost for any reason, you can configure it manually. Complete the following procedure to manually configure the Managing Serer to run as a serice: 1. Install Windows Serer 2003 Resource Kit Tools from the following website: 4ae7-96ee-b18c4790cffdDisplayLang=en 2. Create a serice that starts the srany.exe that belongs to Windows Serer 2003 Resource Kit Tools. srany.exe enables any executable file to be run as a Windows serice. The following syntax is to be used for serice creation: path\instsr SericeName path\srany.exe Note: The paths for instsr and srany.exe must be fully qualified and be of 8.3 style. For example: C:\PROGRA~1\WINDOW~4\Tools\instsr am_serice C:\PROGRA~1\WINDOW~4\Tools\srany.exe 3. Configure the created serice using regedit: a. Click Start, and then click Run. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 109

130 b. Enter regedit, and click OK. c. Add a new subkey named Parameters in the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices\newly_created_serice For example: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Serices\am_serice d. Right-click the newly created serice name, select New, and then select Key. e. In the console pane, for the name of the new key, type Parameters. f. To specify the target application, right-click the Parameters subkey, select New, and then select String Value. Type the name of the new entry as Application. g. Right-click Application and then select Modify. h. In the Edit String window, in Value Data, type the full path to the application to be run (the Korn-shell start-up file because the Managing Serer starts on Windows in a Korn-shell enironment), including the full application name and extension. For example: C:\SFU\common\ksh.bat i. Set the start parameters: 1) Right-click the Parameters subkey, select New, and then select String Value. 2) Type the name of the new entry as AppParameters. 3) Right-click AppParameters and then select Modify. 4) In the Edit String window, in Value Data, type the parameters for starting the Managing Serer. For example: -l /de/fs/c/progra~1/ibm/itcam/websph~1/ms/bin/am-start.sh The easiest way to get data for filling in the string alues is to click Start -> Programs -> ITCAMfWS then right-click am-start.sh and select Properties. The alue for the field target contains a space-separated string. Something like: C:\SFU\common\ksh.bat -l/de/fs/c/progra~1/ibm/itcam/websph~1/ms/bin/am-start.sh The first token is the Application (Korn-shell start-up file), and the next two tokens are AppParameters. Note: When copying the tokens for AppParameters, the separating space must be left intact. 4. The serice properties must be set using the Serices Microsoft Management Console (MMC) Snap-in: a. Click Start -> Control Panel -> Administratie Tools -> Serices. b. In the details pane, right-click the added serice and then select Properties. c. In the General tab, ensure that Startup Type is set to Automatic. d. In the Log on tab, select This account and click Browse to choose the account under which the Managing Serer must be run. e. Enter the password. Note: The account must hae the priileges Log on as a serice and Act as part of the Operating System. 110 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

131 f. In the Recoery tab, First failure and Second failure can be set to Restart the serice and Restart serice after. Values can be increased if IBM DB2 serices do not complete starting before they are accessed by the Managing Serer. 5. After configuration is completed, restart the Windows serer. Note: If the Managing Serer is started or stopped directly using the am-start.sh and am-stop.sh commands, the Windows serice does not correctly show the started/stopped status of the Managing Serer. Windows 2003 Serer: unconfiguring the Managing Serer to run as a serice You can unconfigure the Managing Serer to run as a serice using the following procedure: 1. If you hae not already done so, install Windows Serer 2003 Resource Kit Tools from the following website: 4ae7-96ee-b18c4790cffddisplaylang=en Here is the default location of the Windows Serer 2003 Resource Kit Tools installation: C:\Program Files\Windows Resource Kits\Tools 2. Delete the existing serice that starts the srany.exe executable file that belongs to Windows Serer 2003 Resource Kit Tools. srany.exe enables any executable file to be run as a Windows serice. The following syntax is to be used for serice deletion: <path>\instsr <SericeName> remoe For example: C:\PROGRA~1\WINDOW~4\Tools\instsr am_serice remoe Note: 1. The path for instsr must be fully qualified 8.3 style. For example: C:\PROGRA~1\WINDOW~4\Tools\instsr ITCAMfWAS remoe 2. <path> is the location of the Windows Serer 2003 Resource Kit Tools installation. It is to contain the instsr.exe and srany.exe files. 3. <SericeName> is the name of the serice. Chapter 8. Customization and adanced configuration for the Managing Serer on Windows 111

132 112 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

133 Chapter 9. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on Windows This chapter describes how to uninstall the Managing Serer,IBM WebSphere Application Serer and IBM DB2. The recommended order for uninstalling is as follows: 1. Uninstalling the Managing Serer 2. Manual uninstallation of IBM WebSphere Application Serer on page Manual uninstallation of IBM DB2 on page 117 Uninstalling the Managing Serer It is generally recommended that you uninstall Data Collectors before you uninstall the Managing Serer so that the uninstallation program can delete Data Collector registration information from the Managing Serer. See the chapters for uninstalling Data Collectors in one of the following publications: ITCAM Agent for WebSphere Applications Installation and Configuration Guide ITCAM for Application Diagnostics Agent for WebSphere Applications z/os Installation and Configuration Guide About this task Complete the following procedure to uninstall the Managing Serer: Procedure 1. Log on to the computer as the installation user (for example, amuser). The installation user is the user you used to perform the installation. You created the installation user during Creating the installation user on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page If the serer instance of WebSphere Application Serer that is being used by the Managing Serer is stopped, start the WebSphere Application Serer. 4. Back up files from the Managing Serer, or the embedded IBM DB2 installation that you still need. 5. Run the uninstallation program using one of the following options: a. Click Start > Settings > Control Panel > Add Remoe Program > ITCAM for Application DiagnosticsITCAM for Application Diagnostics Managing SererManaging Serer 7.1. Click Remoe to launch the uninstallation program. b. Execute the following command: MS_home\_uninst\uninstaller.exe. On Windows 2008 Serer and Windows 7 use "Run As Administrator" to execute this command. The Welcome panel is displayed. 6. Click Next. The Choose Features to Uninstall panel is displayed. Copyright IBM Corp. 2006,

134 7. Select the features and click Next. The WebSphere Application Serer Unconfiguration panel is displayed. 8. Verify the discoered information in this panel. Select or enter the correct information if it is not correct: Table 20. IBM WebSphere Application Serer information entered during installation Field Host Name SOAP Connector Port What to do Type the fully qualified host name of the IBM WebSphere Application Serer where the Managing Serer was running. Note: If using Network Deployment, proide the host name of the Deployment Manager instead. Enter the SOAP port setting (The default is 8880). This connector port was used by the IBM WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). The SOAP port is identified in the AppSerer_home\profiles\profile_name\config/cells\ cell_name\nodes\node_name\sererindex.xml file of the instance of IBM WebSphere Application Serer that the Managing Serer used. Note: If using Network Deployment, proide the SOAP port of the Deployment Manager instead. User Name Password Type the name of the user running IBM WebSphere. This is the user you use to log in to the IBM WebSphere Application Serer administratie console for the instance of IBM WebSphere Application Serer being used by the Managing Serer. Type the user password. 9. Click Next. The Choose Embedded Components to Uninstall panel is displayed. 10. If you want to uninstall embedded ersions of IBM DB2, select, Embedded DB2 Uninstallation and click Next. Note that when you choose both of these options, you must manually delete the Managing Serer installation folder and some sub folders after the uninstallation completes. The Reiew Uninstallation Information panel is displayed. 11. Verify the information in this panel and click Uninstall to continue the uninstallation. The Uninstall panel is displayed. 12. When the uninstall is complete, the Reiew Uninstallation Summary panel is displayed. 13. Click Next. The Reboot Computer panel is displayed. Select Yes, restart my computer or No, I will restart my computer at a later time, then click Finish. 14. If you selected No, I will restart my computer at a later time, and if you chose not to uninstall IBM WebSphere Application Serer, stop the instance of IBM WebSphere Application Serer that was being used by the Managing Serer and delete the MS_home directory and any subdirectories. 15. If you choose not to remoe DB2, complete one of the following steps: a. Delete the files and subdirectories under MS_home, but leae AppSerer_home and DB2_home intact. b. Manually uninstall IBM DB2 and IBM WebSphere Application Serer (See Manual uninstallation of IBM WebSphere Application Serer on page 117 and Manual uninstallation of IBM DB2 on page 117), then delete the MS_home directory and any subdirectories. 114 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

135 16. If you hae to keep any of the Managing Serer installation log files in the C:\Program Files\IBM\tioli\common\CYN\logs directory, back them up. This directory is a list of installation log files for the Managing Serer: a. msg-install.log b. trace-install.log The log file names might include numeric affixes. 17. Delete the installation log files in the C:\Program Files\IBM\tioli\common\ CYN\logs directory. Silent uninstallation of the Managing Serer on Windows Complete the following procedure to uninstall the Managing Serer: 1. Complete the alues in the response file based on the following table: Table 21. Configuration options for the Managing Serer on UNIX and Linux Option -W LogSettingUninst.logLeel=ALL DEBUG_MAX DEBUG_MID INFO WARN ERROR FATAL OFF -W LogSettingUninst.consoleOut =true false -P msfilesinstall.actieforuninstall =true false -P einstall.actieforuninstall =true false -P dbinstall.actieforuninstall =true false Description Indicates the log leel for the installation and configuration. Indicates that the uninstaller displays messages on screen during the unistallation process. Indicates if the Managing Serer is to be uninstalled. Indicates if the MSVE is to be uninstalled. Indicates if database tables must be uninstalled. Default alue is true. -V FORCE_UNINSTALL=true false Indicates whether the installer checks connectiity to the WebSphere Application Serer. True indicates that the installer does not check connectiity and uninstalls the Managing Serer. False indicates that the uninstaller checks connectiity to the WebSphere Application Serer and uninstallation does not proceed unless connectiity can be established. The WebSphere Application Serer must be running if you set -V FORCE_UNINSTALL=true -V WAS_HOSTNAME= host name Indicates the host name of the WebSphere Application Serer, proide a fully qualified host name or the IP address of the host. -V WAS_USER= user Indicates a user account that has the administrator role required by IBM WebSphere Application Serer. If WebSphere is running with global security enabled, the user you specify must hae the WebSphere Administrator Role. If WebSphere is running without global security enabled, the user you specify must hae membership in the Administrators group on Windows or root priileges on UNIX. This user must not be a LDAP user. Optional or required? Required Optional Required Required Optional Optional Required, not used when-v FORCE_UNINSTALL =false Required, not used when -V FORCE_UNINSTALL =false Chapter 9. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on Windows 115

136 Table 21. Configuration options for the Managing Serer on UNIX and Linux (continued) Option Description -V Indicates the password for the administrator account. -V WAS_SOAP_PORT=8881 Indicates the WebSphere Application Serer Soap Port. -V UNINST_DB2=true false Indicates whether the embedded installed DB2 will be uninstalled. Optional or required? Required, not used when -V FORCE_UNINSTALL =false Required, not used when -V FORCE_UNINSTALL =false Optional, needed if DB2 was installed during typical install mode 2. From a command-prompt, issue the following command: MS_home\_uninst\ uninstaller.exe -silent -options response_file. Tip: A response file template is aailable at the following location: Install_image/silent/MS_uninst.opt Uninstalling a three phase installation on Windows After a successful three phase Managing Serer installation, (see Performing a three phase installation with three logins in Windows on page 53) the splituninstall.bat script is generated in the MS_install_home/_uninst/ directory. If required, perform these steps to uninstall the Managing Serer: 1. Run the following command to uninstall Visualization Engine: <MS_HOME>\_uninst\uninstalle.bat [-password <password>] For example: C:\IBM\itcam\WebSphere\MS\_uninst\uninstalle.bat -password yourpassword Important: WebSphere Application Serer User Password is required by Visualization Engine. 2. Run the following command to uninstall Managing Serer: <MS_HOME>\_uninst\splituninstall.bat For example: For example, C:\IBM\itcam\WebSphere\MS\_uninst\splituninstall.bat To remoe the MS database in DB2, complete the following steps: a. Go to the temporary directory which you created in the DB2 home directory. b. Run the following command as the DB2 instance user: <temporary directory>\db2\bin\db2uninstall.bat <databasename> For example: C:\images\MS\db2\bin\db2uninstall.bat octigate To remoe the MS database in Oracle, complete the following steps: 116 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

137 a. Go to the temporary directory which you created in the DB2 home directory. b. Run the following command as the Oracle database instance user: <temporary directory>\oracle\bin\oracleuninstall.bat <DBA_user> <DBA_password> <install_dir> <tablespace> <jdbc_user> <jdbc_password> <oracle_sid> Manual uninstallation of IBM WebSphere Application Serer If you used a preexisting installation of IBM WebSphere Application Serer, do not uninstall it unless you are sure that it is not being used for other purposes. Complete the following procedure to uninstall IBM WebSphere Application Serer from your serer: 1. Run the uninstallation executable file that is located in a subdirectory in the installation path for the IBM WebSphere Application Serer by using one of the following options: Tip: The uninstallation file might be in a different location if you did not install (embed) IBM IBM WebSphere Application Serer along with the Managing Serer. From a command-line: AppSerer_home\uninstall\uninstall.exe With the Add/Remoe Programs tool: a. Click Start > Settings > Control Panel > Add Remoe Program > IBM IBM WebSphere Application Serer. b. Click Remoe to launch the uninstallation program. 2. Follow the instructions in the uninstallation program windows. See IBM WebSphere Application Serer documentation for further information. 3. Reboot your serer. 4. If the directory still exists, delete the AppSerer_home directory. Manual uninstallation of IBM DB2 If you used a preexisting installation of IBM DB2, do not uninstall it unless you are sure that it is not being used for other purposes. Complete the following procedure to uninstall IBM DB2 from your serer: 1. Consult a DB2 administrator for assistance in remoing the databases, users, and serices that might be associated with the IBM DB2 application. 2. Complete the procedures documented in the IBM DB2 Information Center: a. Go to the IBM DB2 Information Center at the following website: b. Naigate as follows: 1) In the left pane, click Index > U. 2) In the right pane, click uninstalling > DB2 UDB > Windows: Uninstalling DB2 UDB (Windows). Chapter 9. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on Windows 117

138 118 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

139 Part 3. Managing Serer on Unix and Linux Copyright IBM Corp. 2006,

140 120 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

141 Chapter 10. Road map for the Managing Serer on UNIX and Linux Complete the tasks for preparing to use the Managing Serer in the following order: 1. Verify that your computer meets the system and software prerequisites. See System and software prerequisites on page Install WebSphere Application Serer, which is required for the Managing Serer Visualization Engine. A serer ersion 7 or higher is required. You can download a licensed ersion of WebSphere Application Serer from the same source as the Managing Serer. Important: You can also choose to install the Managing Serer Visualization Engine on the Tioli Enterprise Portal Serer embedded IBM WebSphere Application Serer. If you choose this option, you must specify the IBM Tioli Monitoring home location during installation. From this location, the WebSphere information is automatically collected from the Tioli Enterprise Portal Serer configuration files. Use this option for testing enironments. 3. Choose the installation option that best meets the needs of your enironment: Custom: choose this option if you want to install the Managing Serer using an interactie wizard. Silent: choose a command-prompt interface instead of a graphical user interface to install the software, especially if you want to install one of the following options: Install in a demonstration enironment and then later in a production enironment using similar options You can complete a silent installation in three phases. The first phase installs Managing Serer files. The second phase deploys the Visualization Engine component and registers the configuration in IBM WebSphere Application Serer. In the third phase, you create database tables. You can use this option to install the Managing Serer files without haing to know the IBM WebSphere Application Serer user name and password, or to install the Visualization Engine on a separate host. Important: With both custom and silent installation, you can choose to install a DB2 database enironment for the use of the Managing Serer. This installation is called embedded DB2. Alternatiely, you can use an existing DB2 or Oracle database enironment for the Managing Serer. In this case, ensure that the enironment is fully aailable before installing the Managing Serer. Upgrade or update: choose this option if a preious ersion of the Managing Serer (ITCAM for WebSphere 6.1 or ITCAM for J2EE 6.1) is installed on the target computer. Also, for a new installation, choose this option after installing the Managing Serer ersion 7.1. Attention: The remote command-line interface installation method is not supported. Often, if a remote command-line interface installation is attempted, the installer emits a message prompting you to use a console option in the command-line. You can ignore this prompt. Copyright IBM Corp. 2006,

142 4. Complete the necessary tasks before installing the Managing Serer. See Required tasks before installation on page Access the installation software. See Appendix A, Obtaining installation images, on page Install the Managing Serer. Use one of the following options: Table 22. Steps for installing the Managing Serer Option Procedures to perform Custom 1. Chapter 12, Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux, on page Custom installation steps on page 150 Silent 1. Chapter 12, Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux, on page Chapter 14, Silent installation for the Managing Serer on UNIX and Linux, on page 179 Upgrade or update Chapter 15, Upgrading and updating the Managing Serer on Linux and UNIX systems, on page (optional) Set up security for the Managing Serer. See Appendix C, Setting up security, on page (optional) Perform customizations of the Managing Serer. See Chapter 16, Customization and adanced configuration for the Managing Serer on UNIX and Linux, on page (optional) Install a language pack. See Appendix D, Language Packs for Managing Serer, on page Install and configure a Data Collector. Refer to one of the following publications: ITCAM Agent for WebSphere Applications Installation and Configuration Guide ITCAM for Application Diagnostics Agent for WebSphere Applications z/os Installation and Configuration Guide IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 11. After you hae started using this product to monitor your application serers, complete periodic maintenance on the Managing Serer. See Appendix F, Maintaining the monitoring enironment, on page 281. Installing the Managing Serer on seeral hosts To proide load balancing and optimize resource use, you can install the Managing Serer across up to four serers, using any combination of the following methods: You can run the Managing Serer Visualization Engine (user interface component) on a separate serer. In this case, only this host requires a full installation of IBM WebSphere Application Serer. To do this, use the three phase silent installation process; see UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems on page 179. You can use a separate serer for the database management system (DB2 or Oracle). To use a separate serer for the database management system, first install the database management system. Then, configure the database serer and the future Managing Serer host (see Chapter 12, Configuring an existing 122 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

143 database enironment to work with the Managing Serer on UNIX and Linux, on page 139). Finally, use custom or silent installation to install the Managing Serer. You can use a split installation to spread the backend Managing Serer components (Kernel, Publish Serer, Archie Agent) among two hosts. To use a split installation, first install the Managing Serer on one host. Then, create the additional component instances (see Creating additional instances of Managing Serer components on page 213) and perform the split installation procedure to add the second host (see Split Managing Serer installation in Unix on page 215). Chapter 10. Road map for the Managing Serer on UNIX and Linux 123

144 124 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

145 Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux This chapter includes tasks that must be completed before installing the Managing Serer. Begin this chapter by erifying that your computer meets the system and software prerequisites. See System and software prerequisites. System and software prerequisites The software and hardware requirements before installing ITCAM for Application Diagnostics are listed at the following website: com.ibm.itcamfad.doc_7101/prereqs_itcamad.html You can also optionally run the Enironment Checking Utility (ECU) tool to check that the prerequisite packages are installed correctly. For more information about this utility, refer to the following website: What to do next See Required tasks before installation. Required tasks before installation Complete the tasks in each of the following sections before you attempt to install the Managing Serer. Logging in as the root user A non-root user can complete installation of the Managing Serer in a specific scenario only. (See Requirements to install the Managing Serer with a non-root user. ) Apart from this scenario, in order to complete the installation of the Managing Serer, you must log in as the root user. Requirements to install the Managing Serer with a non-root user Normally, use the root user to Managing Serer. If you must use a non-root user to install the Managing Serer, the following requirements must be fulfilled: You must complete a Custom or silent installation with an existing IBM WebSphere Application Serer and existing database. If you are completing a GUI installation, you must run the installation from a command-line. This non-root installation user must be the same user as the user for the existing IBM WebSphere Application Serer. IBM WebSphere Global Security must be enabled for the existing IBM WebSphere Application Serer. Copyright IBM Corp. 2006,

146 Note: You cannot use the local operating system user to enable IBM WebSphere Global Security when performing a Managing Serer installation as a non-root user. If you do so, you cannot start IBM WebSphere Application Serer correctly. Use the user for the existing IBM WebSphere Application Serer to enable IBM WebSphere Global Security. You can also use the LDAP user to enable IBM WebSphere Global Security. When installing the Managing Serer and choosing the features to install, you cannot specify Database Tables. After installation, you must create the tables manually (see Manually creating database tables on page 176). The user must hae read, write, and execute priileges to one of the following system temporary directories. These directories are used by the InstallShield portion of the installation program: Table 23. Default temporary directories Operating system Solaris or HP-UX Linux and all other UNIX platforms Directory /ar/tmp /tmp The user must be able to log to /ar/ibm/tioli. Note: 1. You might hae to create this directory as root and use the shown command to change ownership to the user. 2. The installation program does not need to write to this directory. For a GUI installation, you hae two options: a. Run the installation from a command line with an option to specify the log directory. See Step 6 on page 150 of the GUI installation procedure. b. You can change the log directory after the GUI installer has been started. If you cannot write to the default log directory, the installer displays a panel that lets you specify a writeable log directory. Remember to specify a directory that has read and write priileges. If you complete a silent installation, options to set the log file directory in the command line or response file are aailable. Custom installation and upgrade: creating the user interface user During the installation or upgrade, you are asked to enter the user name for the user interface user. This user is an operating system user, used for the following tasks: Logging in to and using the IBM WebSphere Application Serer administratie console. Logging in to and using the ITCAM for Application Diagnostics Managing Serer Visualization Engine. (While the Visualization Engine has a user management system of its own, the default user has the same user name and password as the product user). Complete the following procedure to create the user interface user: 1. You can choose to do one of the following options: Use the root user, which is the default. 126 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

147 Create a user for the product at this time. This user must hae root priileges. 2. If you are using an existing IBM WebSphere Application Serer 8.5.5, configure your user registry. (Authentication is controlled by IBM WebSphere Application Serer 8.5.5, not by the Managing Serer.) Complete the procedure at the following website: com.ibm.websphere.base.doc/info/aes/ae/tsec_useregistry.html You must configure one of the following types of user registries: Federated repository Local operating system Standalone Lightweight Directory Access Protocol (LDAP) registry Standalone custom registry Permissions for an existing IBM WebSphere Application Serer The user for an existing IBM WebSphere Application Serer that you specify later during the installation must hae root priileges in order to work with the Managing Serer. The user also has the following permissions: Able to create a user or hae permission to designate a preexisting user so you can define the DB2 Administration Serer, DB2 Fenced, and DB2 Instance users Able to define a group name and home directory for new accounts Has full administratie rights to IBM DB2 Existing database enironment: creating the Schema user During a Custom installation using an existing database enironment, you are asked to enter the name for the schema user. This user must hae sufficient permissions to own and create database tables. Create this user. Network Information Serice enironment: creating the DB2 account users If your serer is part of a Network Information Serice (NIS) enironment, during the embedded IBM DB2 installation, you cannot create DB2 user accounts from the installer. You must create users for the DB2 Administration Serer, DB2 Fenced, and DB2 Instance accounts before you begin the installation. When creating these accounts, check that: The passwords hae been set. You can log in to the system with these users. The home directories are accessible. You hae this information aailable when you start the installation of the Managing Serer. Note: If your serer is in an NIS enironment, you must complete a Custom or silent installation. Typical installations are not supported for NIS enironments. Custom installation: creating the DB2 account users (optional) You can create the DB2 Administration Serer, DB2 Fenced, and DB2 Instance accounts before you begin the installation, een if you are completing an embedded installation of IBM DB2. When creating these accounts, make sure that the following conditions are met: Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 127

148 The passwords hae been set. You can log in to the system with these users. The home directories are accessible. You hae this information aailable when you start the installation of the Managing Serer. HP-UX and Solaris: kernel settings for IBM DB2 8.x If you install the Managing Serer on HP-UX or Solaris and hae IBM DB2 8.x as your database, you must modify the operating system kernel settings. Kernel settings for HP-UX See the following website for instructions on modifying kernel settings to support IBM DB2 on HP-UX: com.ibm.db2.udb.doc/start/r htm In the naigation pane, click HP-UX > Modifying kernel parameters. To install IBM DB2 8.x on HP-UX, you must add the kernel settings listed in that website. In the naigation pane, click HP-UX > Recommended kernel configuration parameters. Kernel settings for Solaris on DB2 See the following website for instructions on modifying kernel settings to support IBM DB2 on Solaris: com.ibm.db2.udb.doc/start/t htm To install IBM DB2 8.x on Solaris, you must add the following kernel settings in /etc/system file and reboot your system: For systems with 2 GB -4 GB of physical memory: set msgsys:msginfo_msgmnb = set msgsys:msginfo_msgssz = 32 set msgsys:msginfo_msgseg = set msgsys:msginfo_msgmni = 2560 set msgsys:msginfo_msgtql = 2560 set semsys:seminfo_semmni = 3072 set shmsys:shminfo_shmmax = set shmsys:shminfo_shmmni = 3072 For systems with 4 GB - 16 GB of physical memory: set msgsys:msginfo_msgmnb = set msgsys:msginfo_msgssz = 32 set msgsys:msginfo_msgseg = set msgsys:msginfo_msgmni = 3584 set msgsys:msginfo_msgtql = 3584 set semsys:seminfo_semmni = 4096 set shmsys:shminfo_shmmax = set shmsys:shminfo_shmmni = 4096 All the other kernel tunable parameters that the installation and configuration Guide recommends that you adjust are in the System V Interprocess Communication (IPC) tunables. In Solaris 10 all System V IPC facilities are either automatically configured or can be controlled by resource controls. 128 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

149 The following parameters are still operational but use of the corresponding resource controls is recommended. msgsys:msginfo_msgmnb - process.max-msg-qbytes msgsys:msginfo_msgtql - process.max-msg-messages semsys:seminfo_semopm - process.max-sem-ops semsys:seminfo_semmsl - process.max-sem-nsems shmsys:shminfo_shmmax - project.max-shm-memory shmsys:shminfo_shmmni - project.max-shm-ids msgsys:msginfo_msgmni - project.max-msg-ids semsys:seminfo_semmni - project.max-sem-ids Obsolete parameters can still be included in the /etc/system file on a Solaris 10 system. If so, the parameters are used to initialize the default resource control alues used in preious Solaris releases. You can oerride these control alues by setting the corresponding resource controls. An important difference between the obsolete IPC tunables and resource controls is that the IPC tunables were set on a system-wide basis and the resource controls are set on a per-project or per-process basis allowing for a more flexible tuning of different workloads in the system. HP-UX and Solaris: kernel settings for IBM WebSphere Application Serer If you are installing the Managing Serer on HP-UX or Solaris, you must set the operating system kernel alues to support IBM WebSphere Application Serer. Note: The following instructions are also proided in the chapter for preparing the operating system for product installation in IBM WebSphere Application Serer, Version 6: Installing your application sering enironment. Kernel settings for HP-UX Seeral HP-UX kernel alues are typically too small for IBM WebSphere Application Serer. Complete the following procedure to adjust the kernel alues: 1. Log in to the host serer as root. 2. Determine the physical memory, which you must know to aoid setting certain kernel parameters aboe the physical capacity: a. Start the HP-UX System Administration Manager (SAM) utility: sam This starts a text-based GUI interface. Use tab and arrow keys to moe around in the interface. b. Click Performance Monitors > System Properties > Memory. c. Note the alue for Physical Memory and click OK. 3. Click Kernel Configuration > Tunables. 4. Set maxfiles alue to 8000 and the maxfiles_lim alue to Set new kernel parameter alues: a. For each of the parameters in the following table, complete this procedure: 1) Highlight the parameter to change. 2) Click m. 3) Type the new alue in the Enter Value/Expression field. 4) Click OK. Typical kernel settings for running IBM WebSphere Application Serer are displayed in the following table: Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 129

150 Table 24. Typical kernel settings for running IBM WebSphere Application Serer Parameter Value dbc_max_pct 25 maxdsiz maxdsiz (when running multiple profiles on the same system) maxfiles_lim 8196 (Change this one before maxfiles.) maxfiles 8000 maxssiz maxswapchunks 8192 max_thread_proc 3000 maxuprc 512 maxusers 512 msgmap 2048 msgmax msgmax (when running multiple profiles on the same system) msgmnb msgmnb (when running multiple profiles on the same system) msgmni 50 msgseg msgssz 32 msgtql 2046 nfile nflocks 3000 ninode nkthread 7219 nproc 4116 npty 2024 nstrpty 1024 nstrtel 60 sema 1 semaem semmap 514 semmni 2048 semmns semmnu 1024 semume 200 semmx shmmax shmem 1 shmmni 1024 shmseg 1024 STRMSGSZ ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

151 Important: When IBM WebSphere Application Serer and IBM DB2 are on the same serer, some kernel alues are higher than those alues shown in the preceding table. 6. Click Actions > Process New Kernel. 7. Click Yes on the information panel to confirm your decision to restart the serer. Follow the on-screen instructions to restart your serer and to enable the new settings. 8. Exit from the SAM utility. 9. If you would like to redirect displays to non-hp serers, complete the following steps before running the IBM WebSphere Application Serer installation wizard: a. Issue the following command to obtain information about all the public locales that are accessible to your application: # locale -a b. Choose a alue for your system from the output that is displayed and set the LANG enironment ariable to this alue. Here is an example command that sets the alue of LANG to en_us.iso88591: # export LANG=en_US.iso Reboot your serer, for these changes to take effect. Kernel settings for Solaris on WebSphere Application Serer Seeral Solaris kernel alues are typically too small for IBM WebSphere Application Serer. Complete the following procedure to adjust the kernel alues: 1. Before installing, reiew the serer configuration: sysdef -i The kernel alues are set in the /etc/system file, as shown in the following example. set shmsys:shminfo_shmmax = set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semmni = 1024 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set rlim_fd_cur= Change kernel alues by editing the /etc/system file then rebooting the operating system. For more information about setting up the Solaris system, see the Solaris System Administration documentation at the following website: docs.sun.com/app/docs/prod/solaris.admin.misc For example, the Solaris Tunable Parameters Reference Manual at the following website: Queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni and semmni, must allow for the number of queue managers in the system. All the other kernel tunable parameters that the installation and configuration Guide recommends that you adjust are in the System V IPC (Interprocess Communication) tunables. In Solaris 10 all System V IPC facilities are either automatically configured or can be controlled by resource controls. Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 131

152 The following parameters are still operational but use of the corresponding resource controls is recommended. msgsys:msginfo_msgmnb - process.max-msg-qbytes msgsys:msginfo_msgtql - process.max-msg-messages semsys:seminfo_semopm - process.max-sem-ops semsys:seminfo_semmsl - process.max-sem-nsems shmsys:shminfo_shmmax - project.max-shm-memory shmsys:shminfo_shmmni - project.max-shm-ids msgsys:msginfo_msgmni - project.max-msg-ids semsys:seminfo_semmni - project.max-sem-ids Obsolete parameters can still be included in the /etc/system file on a Solaris 10 system. If so the parameters are used to initialize the default resource control alues used in preious Solaris releases. You can oerride these by setting the corresponding resource controls. An important distinction between the obsolete IPC tunables and resource controls is that the IPC tunables were set on a system-wide basis and the resource controls are set on a per-project or per-process basis allowing for a more flexible tuning of different workloads in the system. HP-UX and Solaris with embedded IBM DB2: changing kernel configuration parameters set as formulas to integer alues If you install the Managing Serer on HP-UX or Solaris, and are planning to install (embed) IBM DB2 at the same time as the Managing Serer installation, change all recommended kernel configuration parameters set as formulas to integer alues. You must reboot your system for these changes to take effect. HP-UX 11.23: enabling the local host alias If you install the Managing Serer on HP-UX 11.23, make sure that local host alias is aailable. Complete the following procedure: 1. Replace the contents of /etc/nsswitch.conf with the contents of /etc/nsswitch.hp_defaults. 2. In the modified /etc/nsswitch.conf file, change the following information: hosts: dns [NOTFOUND=return] nis [NOTFOUND=return] to hosts: dns files Maximizing font resolution For the English language ersion of the Managing Serer, set the resolution to 1024x768 with default toolbars. For non-english language ersions of the Managing Serer, set the resolution to 1280x1024 pixels. Host name and IP address for the Managing Serer The serer on which the Managing Serer is installed must hae a fully qualified host name and IP address (in addition to using the loopback network connections local host and ). Solaris: enabling links in LaunchPad On Solaris, in order to access the links in LaunchPad, you must add the appropriate directories for Netscape and Mozilla to the PATH enironment ariable. Complete one of the following options: If Netscape is your default browser, run this from a command line: export PATH=/usr/dt/bin/:$PATH 132 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

153 If Mozilla is your default browser, run this from a command line: export PATH=/usr/sfw/bin/:$PATH Tip: For a description of the links in LaunchPad, see Appendix B, Using the LaunchPad interface, on page 245. Embedded IBM DB2 installation: uninstalling an existing IBM DB2 enironment on the local serer If you hae an existing IBM DB2 enironment on the serer where you want to install the Managing Serer and you want to install the embedded ersion of DB2, you must either uninstall the IBM DB2 enironment or choose another serer on which to install the Managing Serer. Creating an IBM WebSphere Application Serer instance for a Data Collector installed on the same serer as the Managing Serer If you want to install the Data Collector on the same computer as the Managing Serer, you must create an IBM WebSphere Application Serer instance for the Data Collector. Follow the instructions at one of the following websites to create an instance of IBM WebSphere Application Serer: Table 25. Websites with instructions to create an instance of IBM WebSphere Application Serer IBM WebSphere Application Serer ersion URL 6.0.x (non-network Deployment enironment) 6.0.x (Network Deployment enironment) 6.1 (non-network Deployment enironment) 6.1 (Network Deployment enironment) 7.0 (non-network Deployment enironment) 7.0 (Network Deployment enironment) com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html Requirement for a separate installation or profile of IBM WebSphere Application Serer You cannot install both the Managing Serer and Data Collector on the same installation and profile of IBM WebSphere Application Serer. Two separate IBM WebSphere Application Serer installations must be performed or two separate profiles within one installations must be created if you want to install both the Managing Serer and Data Collector on the same computer. IBM WebSphere Application Serer can be installed multiple times on the same computer, and a single installation supports multiple profiles. Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 133

154 Adjusting for ports being blocked by your firewall or being used by other applications Throughout the installation, you must specify or accept the defaults for port numbers used by ITCAM for Application Diagnostics,IBM WebSphere Application Serer or databases. Complete one of the following options: Make sure that the ports listed in Table 26 are not blocked by your firewall or used by other applications. Make a note of which ports are being blocked or being used by other applications. Then later, during the installation, make sure that you do not accept a default that includes one of those ports. Consult the documentation for your firewall program to determine which ports are being blocked by your firewall. Run the following command to determine which ports are already being used by applications on your computer: netstat -a The following table shows that the default ports enlisted by the installation: Table 26. Default ports Usage Port number IBM WebSphere Application Serer administratie 9060 console SOAP connector for IBM WebSphere Application Serer 8880 instance used by the Managing Serer IBM DB Oracle 1521 Archie Agent Archie Agent Kernel Codebase 9122 Kernel Remote File Sharing (RFS) 9120 Kernel Remote Method Inocation (RMI) 9118 Message Dispatcher 9106 Polling Agent 9111 Publish Serer Publish Serer Structured Application Monitor 9126 Visualization Engine 80, ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

155 Table 26. Default ports (continued) Usage Port number Connection between Managing Serer and Data Collector The ports that must be aailable depend on whether the Port Consolidator is enabled. Make the following ports aailable: If the Port Consolidator is enabled: 8800 If the Port Consolidator is not enabled, for each Data Collector that connects to the Managing Seer, one port from each of the following ranges: If you also hae IBM CICS or IBM IMS Data Collectors connecting to the Managing Serer: If you also hae IBM CICS or IBM IMS Data Collectors connecting to the Managing Serer: Note: For more detailed information about enablement of the Port Consolidator, see the appendix in the Data Collector installation and customization guide. (Optional) Gathering information required for the installation You might want to prepare for the installation by gathering information that you must proide during the installation. A good example of the alues that you might need to proide is located here: Table 42 on page 189. Users created before or during the installation The following table displays lists of users that must be created before or are created during the Custom installations: Important: If your serer is part of a Network Information Serice (NIS) enironment, during the embedded IBM DB2 installation, you are unable to create DB2 user accounts from the installer. You must create users for the DB2 Administration Serer, DB2 Fenced, and DB2 Instance accounts before you begin the installation. See Network Information Serice enironment: creating the DB2 account users on page 127. If your serer is part of an NIS enironment, you must complete a Custom or silent installation. Table 27. Users that must be created before or are created during the Custom installation User Description Default Permissions When created Installation User when logging on to perform the Managing Serer installation Must be root root user not applicable DB2 Administration Serer User for DB2 Administration Serer account db2admin Belongs to the sys group Embedded IBM DB2: created during the installation or can exist preiously Existing IBM DB2: must exist preiously Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 135

156 Table 27. Users that must be created before or are created during the Custom installation (continued) User Description Default Permissions When created DB2 Instance DB2 instance owner db2inst1 Belongs to the sys group Embedded IBM DB2: created during the installation or can exist preiously Existing IBM DB2: must exist preiously DB2 Fenced User for DB2 Fenced db2fenc1 Belongs to the sys group Embedded IBM account DB2: created during the installation or can exist preiously IBM WebSphere Application Serer User Interface Schema Oracle SQLPlus Oracle database administrator User used to start the WebSphere Windows serice and to connect to IBM WebSphere (Optional) User used for logging in to and using the ITCAM for Application Diagnostics Managing Serer Existing database enironment only: own and can create the database tables for ITCAM for Application Diagnostics Existing Oracle enironment only: Oracle SQLPlus user Existing Oracle enironment only: Oracle database administrator user Existing IBM DB2: must exist preiously root root priileges Existing IBM WebSphere Application Serer: must exist preiously root root priileges Preinstallation procedure or can be the default (root). See Custom installation and upgrade: creating the user interface user on page 126. None Must be able to create database tables Preinstallation procedure. See Existing database enironment: creating the Schema user on page 127. Must exist preiously Must exist preiously Determining the port number for an IBM DB2 instance that exists If you plan to use an existing IBM DB2 enironment, you must know the port number for the IBM DB2 instance by the time you enter IBM DB2 configuration information during installation of the Managing Serer. You can check the port number by completing the following steps: 1. If the IBM DB2 enironment is on a remote computer, enter xhost + hostname on the computer where you are sitting. 136 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

157 The hostname is the fully qualified host name of the computer on which the Managing Serer is being installed. 2. Complete one of the following procedures to see the IBM DB2 instance port number: If the DB2 Control Center was installed when installing IBM DB2, use the db2cc command: a. Open the DB2 Control Center and enter the db2cc command from a console window. b. In the left pane, right-click one of the aailable instances for the local system. c. Select Setup Communications. d. Click Properties to the right of the TCP/IP choice. The port number is listed there. If the DB2 Control Center was not installed when installing IBM DB2, enter one of the following commands: netstat -a grep LISTEN cat /etc/serices What to do next Choose one of the following options: If you are installing IBM DB2 with the Managing Serer, start the installation. See one of the following sections: Chapter 14, Silent installation for the Managing Serer on UNIX and Linux, on page 179 Chapter 13, Custom installation for the Managing Serer on UNIX and Linux, on page 149 If you are using an existing IBM DB2 or Oracle database enironment with the Managing Serer, configure the database serer to work with the Managing Serer. See Chapter 12, Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux, on page 139. Chapter 11. Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux 137

158 138 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

159 Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux You can customize the IBM DB2 or Oracle database enironment before you begin installing the Managing Serer. Complete these steps only if you are using an existing IBM DB2 or Oracle database enironment with your Managing Serer; otherwise, go directly to one of the installation chapters. Begin this chapter by referring to one of the following sections: For an existing local or remote IBM DB2 enironment, see Preparing an existing IBM DB2 enironment. For an existing local Oracle database enironment, see Preparing an existing local Oracle database enironment on page 143. For an existing remote Oracle database enironment, see Preparing an existing remote Oracle database enironment on page 144. Preparing an existing IBM DB2 enironment Complete the following procedure if you want to use an existing local or remote DB2 enironment with the Managing Serer. If the DB2 RDBMS serer is remote (that is, not the host on which the Managing Serer is running), complete the following tasks: On the host where the Managing Serer is running, install the DB2 Client Application Enabler. See Installing and configuring the IBM Data Serer Client Package with a remote Relational Database Management System. On the RDBMS host, create the Managing Serer database. See Preparing the remote IBM DB2 for use with the Managing Serer on page 141. If the DB2 RDBMS serer is installed on the host where the Managing Serer is running, and the AIX operating system is used on the host, complete DB2 preparation. See Preparing local DB2 on an AIX-based serer on page 142. The following steps apply whether the RDBMS is running on the same host as the Managing Serer or on a different host: If you plan to use the JDBC Type 2 drier, prepare RDBMS connectiity for it; see Preparing connectiity for the DB2 client with a JDBC Type 2 drier on page 142. You do not need to do this if you are using the JDBC type 4 drier (which is the default setting). Tune the DB2 enironment. See Tuning the IBM DB2 enironment on page 143. Installing and configuring the IBM Data Serer Client Package with a remote Relational Database Management System Complete these steps only if the IBM DB2 Relational Database Management System (RDBMS) is installed on a separate computer from the client (the Managing Serer). You must install the IBM Data Serer Client Package on the client computer and set up connectiity to IBM DB2. Follow these guidelines: Copyright IBM Corp. 2006,

160 1. Ensure that there is no IBM Data Serer Client Package installation (either complete or partial) on the system. If an installation exists, uninstall it. 2. Customize the options to select Jaa database connectiity (JDBC). A JDBC drier is installed as part of the IBM Data Serer Client Package installation. 3. Ensure that approximately 2 MB are aailable in the selected home directory to accommodate the IBM Data Serer Client Package. Note: For IBM DB2 10.1, you need more than 2 MB of disk space. For IBM DB2 10.1, the disk space is checked dynamically at client installation time. The disk space required for your product depends on the type of installation you choose and the type of file system you hae. The DB2 Setup wizard proides dynamic size estimates based on the components selected during a compact or custom installation. Remember to include disk space for required software and communication products. 4. Source the db2profile file (for the Korn or Bourne shell) or the db2cshrc file (for the C shell) to be able to run IBM DB2 commands and utilities such as catalog and connect. The db2profile and db2cshrc files are located in the home directory of the user, under the sqllib subdirectory. Source the appropriate file in the.profile or.cshrc file of each account that must use the IBM DB2 enironment and tools. 5. IBM AIX: To erify the setup of the RDBMS and of the DB2 client, ensure that the following enironment ariables are set correctly: (If you hae sourced the db2profile or db2cshrc file, these ariables are correct.) DB2DIR must point to the directory where the IBM Data Serer Client Package is installed. DB2INSTANCE must be set to the IBM DB2 instance name. This is set during installation of IBM DB2. 6. You must set up connectiity both to the RDBMS serer and to IBM DB2. IBM DB2 commands for setting up connectiity are issued from the client system. You must run these commands een when IBM DB2 is running on the same computer that hosts the Managing Serer. Here are some examples: The following example command connects the client with an RDBMS serer named ghost, which has the node name or alias ims_db2 and uses port 50000: db2 catalog tcpip node ims_db2 remote ghost serer The following example command connects the client to a database named timsde with the alias ims_de, located on the serer whose node name or alias is ims_db2: db2 catalog database timsde as ims_de at node ims_db2 7. Run the following command: db2 terminate 8. Proide extra shared memory segments for IBM DB2 connections on IBM AIX. By default, 32- bit applications cannot attach more than 11 shared memory segments per process, of which a maximum of 10 can be used for local IBM DB2 connections. Use the EXTSHM (extended shared memory) functionality to ensure that enough shared memory segments are aailable for IBM DB2 connections. The EXTSHM functionality is aailable for IBM DB2 7.2 (which is the result of installation of IBM DB2 7.1 Fix PACK 3 or for later ersions of IBM DB2. If you do not proide enough shared memory segments, you might see the following error message: SQL1224N A database agent could not be started to serice a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE= ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

161 Table 28. How to enable EXTSHM Enable EXTSHM as follows: In IBM DB2 client sessions When starting the IBM DB2 Serer On IBM DB2 EE export EXTSHM=ON export EXTSHM=ON db2set DB2ENVLIST=EXTSHM db2start EXTSHM=ON export EXTSHM You also add these lines to the sqllib/userprofile file. Preparing the remote IBM DB2 for use with the Managing Serer The following instructions describe how to prepare the DB2 enironment used by the Managing Serer when DB2 is installed on a different computer to the Archie Agent (a component of the Managing Serer). 1. Install IBM DB2 on the remote serer. Note: On the remote serer, a user account, for example, amuser must be created. This user must also be created on the serer where the Managing Serer is being installed. 2. Log in as the DB2 Instance user on the remote serer. 3. Create a temporary directory on the remote serer in which to place the database installation scripts. Example: /tmp. 4. FTP the file db2-remote-scripts.tar to the temporary directory you created. Note: The db2-remote-scripts.tar file is proided with the Managing Serer distribution in MS_installation_image_directory/base/scripts/. 5. Extract the db2-remote-scripts.tar file. 6. Run the db2install.sh file as the DB2 Instance user. You also need the password for the schema user. cd /tmp/db2/bin sh db2install.sh db_username schema_user absolute path installation dir user_interface_user DB2ersion databasename Notes: a. db_username must hae dba priileges, for example, db2inst. b. schema_user owns and can create the database tables for ITCAM for Application Diagnostics. This is the user you created in Existing database enironment: creating the Schema user on page 127. When you run the script you are prompted for a password. c. The absolute path installation directory is a db2 subdirectory in the temporary directory containing the installation scripts, for example, /tmp/db2. d. user_interface_user is the user that will be used when logging in and operating the Managing Serer Application Monitor after installation and configuration. This user is also specified during the Managing Serer installation. This is the user you created in Custom installation and upgrade: creating the user interface user on page 126. Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux 141

162 e. The db2install.sh script inokes the scripts db2configuration.sh and db2createschema.sh. The db2configuration.sh script inokes the script dbsettings.sql, and the db2createschema.sh script inokes the am-db2.sql script. Preparing local DB2 on an AIX-based serer You do not hae to complete the following steps if a remote IBM DB2 is used or if a loopback node has been created for using TCP/IP communication instead of shared memory communication. If the Managing Serer is AIX-based and it uses a local IBM DB2 enironment, proceed according to the following steps: 1. Make sure that the IBM DB2 instance can be accessed remotely. You must specify the TCP/IP port while creating the IBM DB2 instance. 2. Edit the file db2_instance_home/sqllib/userprofile to include the following lines: EXTSHM=ON export EXTSHM 3. Log in as the DB2 Instance user (for example, db2inst1): su - db2inst1 4. As the DB2 Instance user, issue the following commands: db2stop force db2set DB2ENVLIST=EXTSHM db2start Preparing connectiity for the DB2 client with a JDBC Type 2 drier Complete the following procedure to prepare connectiity for the DB2 client if the JDBC Type 2 drier is to be used. If you plan to use the JDBC Type 2 drier, complete the following procedure, whether the DB2 RDBMS is located on the local serer or on a different (remote) serer. If you are using the JDBC type 4 drier (which is the default setting), this procedure is not mandatory. 1. Log in as a user with dba priileges, for example: db2inst1. Tip: For conenience purposes, you might want to log in as root. In the following steps, the script that you are executing prompts you for the password multiple times. These multiple prompts can be aoided if you run it as root. 2. Catalog the TCP/IP node pointing to the DB2 RDBMS serer node: db2 catalog tcpip node db2node remote Remote_Serer serer db2_listening_port For example, to connects the client with na RDBMS serer named ghost, which has the node name or alias ims_db2 and uses port 50000: db2 catalog tcpip node ims_db2 remote ghost serer Catalog the database on the node created: db2 catalog db database_name at node db2_node This must be the database name that is used for the Managing Serer. For example, to catalog the octigate database on the ims_db2 node, use the following command: db2 catalog db octigate at node ims_db2 4. Run the following command: 142 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

163 db2 terminate Tuning the IBM DB2 enironment Follow the tuning instructions described in the file: MS_installation_image_directory/ base/etc/db2-readme.txt. What to do next Complete one of the following options: Begin an installation of the Managing Serer with an existing IBM DB2 enironment. See Chapter 13, Custom installation for the Managing Serer on UNIX and Linux, on page 149. Begin a silent installation of the Managing Serer. See Chapter 14, Silent installation for the Managing Serer on UNIX and Linux, on page 179. Preparing an existing local Oracle database enironment Complete these tasks if you want to use an existing local Oracle database enironment with the Managing Serer. This section describes configuration tasks and requirements for setting up an existing Oracle database enironment that can be used to support the Managing Serer. The Oracle database configuration tasks described in this chapter sere as a general guide to the basic requirements for setting up the enironment, not as comprehensie instructions. A database administrator might use a different approach. For detailed Oracle information, consult the Oracle documentation. To use an existing Oracle database enironment, you must create a database file manually. You must also hae a alid user name and password to enable access to the required database for the Managing Serer. Procedure Complete the following procedure to prepare an existing local Oracle database enironment: 1. Create an Oracle database with an SID name of octigate, using utility: dbca Important: For the Solaris operating system, make sure that the UNIX sqlplus user (oracle) database enironment ariables are defined in a users_home_dir/.profile file (if using ksh or sh) and.bash_profile (if using bash). For example: /export/home/oracle/.profile 2. Create sufficient table space for the management repository. Important: One month of operational data might require a minimum of 10 GB. Your space requirements might ary, depending on your enironment and monitoring configuration. For test purposes, a smaller database (300 MB to 400 MB) is sufficient. 3. Create a user ID and password for the table space for which the user has authority to create and edit tables. Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux 143

164 4. Configure a rollback segment using the Oracle database default size for rollback segments. 5. Reiew the sample configuration scripts in Sample scripts for configuring an existing database on page 146 as a guide for creating your own script to configure your database. 6. (Double-byte character enironments only) If your operating system is enabled for a single-byte character set, it does not automatically accept double-byte character sets. You must enable your Oracle database enironment to store monitoring information that comes in double-byte character strings. The following sample command for creation of a database includes the CHARACTER SET UTF8 string (in bold text). This string enables storage of double-byte character sets: CREATE DATABASE 920u MAXINSTANCES 1 MAXLOGHISTORY 1 MAXLOGFILES 5 MAXLOGMEMBERS 3 MAXDATAFILES 100 DATAFILE C:\Oracle\oradata\920u\system01.dbf SIZE 200M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE C:\Oracle\oradata\920u\temp01.dbf SIZE 10M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED UNDO TABLESPACE "UNDOTBS1" DATAFILE C:\Oracle\oradata\920u\undotbs01.dbf SIZE 50M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED CHARACTER SET UTF8 NATIONAL CHARACTER SET AL16UTF16 LOGFILE GROUP 1 ( C:\Oracle\oradata\920u\redo01.log ) SIZE K, GROUP 2 ( C:\Oracle\oradata\920u\redo02.log ) SIZE K, GROUP 3 ( C:\Oracle\oradata\920u\redo03.log ) SIZE K; 7. For Solaris, the sqplplus user must use an sh shell and ariables must be defined in the.profile file. To erify this, run the following command, which returns your sqlplus path: su - sqlplus_user(oracle) -c "which sqlplus" 8. For an Oracle 10g instance, follow the described in the file: MS_installation_image_directory/base/etc/oracle10g-readme.txt. What to do next Complete one of the following options: Begin an installation of the Managing Serer with an existing Oracle database enironment. See Chapter 13, Custom installation for the Managing Serer on UNIX and Linux, on page 149. Begin a silent installation of the Managing Serer. See Chapter 14, Silent installation for the Managing Serer on UNIX and Linux, on page 179. Preparing an existing remote Oracle database enironment The following instructions describe how to prepare the Oracle database enironment used by the Managing Serer when an Oracle database is installed on a different serer than the Archie Agent (a component of the Managing Serer). This section describes configuration tasks and requirements for setting up an existing Oracle database enironment that can be used to support the Managing Serer. The Oracle database configuration tasks described in this chapter sere as a general guide to the basic requirements for setting up the enironment, not as 144 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

165 comprehensie instructions. A database administrator might use a different approach. For detailed Oracle database information, consult the Oracle database documentation. To use an existing Oracle database enironment you must create a database file manually. You must also hae a alid user name and password to gie you access to the required database for the Managing Serer. To use a remote Oracle database enironment with the Managing Serer, you must prepare the Oracle database enironment on the remote serer and install JDBC driers on the local serer. Within this section, the serers are referred to as follows: The serer on which the Visualization Engine (Application Monitor) and Archie Agent are installed is the local serer. The serer on which the Oracle database enironment is installed is the remote serer. Preparing the remote Oracle database enironment Complete the following procedure to prepare the remote Oracle database enironment: 1. Create the SID for use by the Managing Serer. Record the name of the SID; you can use the default name,octigate Attention: If you use a SID name other than octigate, you must explicitly specify this name when installing the Managing Serer using custom or silent installation. 2. Create a temporary directory on the remote serer. Example: /tmp. 3. ftp the file oracle-remote-scripts.tar to the temporary directory. Note: The oracle-remote-scripts.tar file is proided with the Managing Serer distribution (in MS_installation_image_directory/base/scripts/). 4. Log in as a user with dba priileges. For example: oracle. 5. Extract the oracle-remote-scripts.tar file. 6. Run the following command to export the ORACLE_SID used by the Managing Serer: export ORACLE_SID=octigate If you are using a SID name other than octigate, specify that SID name instead. 7. Run the oracleinstall.sh script, which has the following format: cd /tmp/oracle sh bin/oracleinstall.sh sqlplus_user sqlplus_password tablespace schema_user schema_password adminveuser oracle_sid is the SID name you hae created. sqlplus_user and sqlplus_password are credentials for Oracle SQL Plus. The user must hae priilege to create table space and users. You can specify the Oracle database system user credentials. Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux 145

166 tablespace is the name of the table space that is created when you run the oracleinstall.sh script. This is the table space used by the Managing Serer. This table space is remoed if it exists. schema_user and schema_password are the login and password of the user that the Managing Serer uses to connect with Oracle, using JDBC. This same login and password must be used during the Managing Serer installation. This schema user must exist in the local operating system. adminveuser is the operating system user that is used for the Visualization Engine component. This user is also the default administratie user in the Visualization Engine user interface. See Custom installation and upgrade: creating the user interface user on page For Solaris, the sqlplus user must use an sh shell and ariables must be defined in the.profile file. To erify this, run the following command, which returns your sqlplus path: su - sqlplus_user(oracle) -c "which sqlplus" 9. For an Oracle 10g instance, follow the described in the file: MS_installation_image_directory/base/etc/oracle10g-readme.txt. Installing JDBC libraries on the local serer Install the thin JDBC driers on the local serer. After you prepare the Oracle database on the remote serer and install the JDBC driers on the local serer, you can proceed with the installation of the Managing Serer, described in Chapter 13, Custom installation for the Managing Serer on UNIX and Linux, on page 149. What to do next Complete one of the following options: Begin an installation of the Managing Serer with an existing Oracle database enironment. See Chapter 13, Custom installation for the Managing Serer on UNIX and Linux, on page 149. Begin a silent installation of the Managing Serer. See Chapter 14, Silent installation for the Managing Serer on UNIX and Linux, on page 179. Sample scripts for configuring an existing database You can use the following sample scripts to configure a database repository for the Managing Serer in a test enironment. Do not use these scripts in a production enironment. The following script is aailable: Sample SQL script for creating flexible a table space in an Oracle database. Sample SQL script for creating flexible a table space in an Oracle database Instead of setting permanently fixed sizes for the table space and temporary data file, the following sample script uses AUTOEXTEND to enlarge these items as needed. It autoextends the table space (named $username) 5 MB at a time and the temporary data file 100 KB at a time. #!/bin/ksh if[$#-ne1] then echo "Usage: create_users.sh username" 146 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

167 fi exit 1 username=$1 echo "Creating SQL file:/dbs1/create/"$username"_create.sql" touch /dbs1/create/"$username"_create.sql REM REM Execute the following SQL fragment as Oracle RDBMS user "sys": REM create tablespace ts_$username datafile /dbs1/ts_$username.dbf size 30M default storage ( initial 100K next 50K minextents 2 maxextents 120) offline; commit; create tablespace tmp_ts_$username datafile /dbs1/tmp_ts_$username.dbf size 3M default storage ( initial 100K next 50K minextents 2 maxextents 20) TEMPORARY offline; commit; alter tablespace ts_$username online; commit; alter tablespace tmp_ts_$username online; commit; create profile profile_$username limit sessions_per_user 10 cpu_per_session unlimited cpu_per_call 6000 logical_reads_per_session unlimited logical_reads_per_call 100 idle_time 30 connect_time 480; commit; create user $username identified by $username default tablespace ts_$username temporary tablespace tmp_ts_$username quota unlimited on ts_$username profile profile_$username; commit; GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO $username identified by $username; commit; Chapter 12. Configuring an existing database enironment to work with the Managing Serer on UNIX and Linux 147

168 ALTER DATABASE DATAFILE /dbs1/ts_$username.dbf AUTOEXTEND ON NEXT 5M; commit; ALTER DATABASE DATAFILE /dbs1/tmp_ts_$username.dbf AUTOEXTEND ON NEXT 100K; commit; 148 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

169 Chapter 13. Custom installation for the Managing Serer on UNIX and Linux Notes about the installation Table 29. Location of installation log files The Custom installation process enables you to install ITCAM for Application Diagnostics using an existing database application and an existing IBM WebSphere Application Serer. You can also install the ersions of IBM DB2 or IBM WebSphere Application Serer that are included as part of the Managing Serer installation. You can specify adanced installation alues, such as existing users and passwords. Installation of either IBM WebSphere Application Serer or IBM DB with the Managing Serer is called an embedded installation. Begin this chapter by iewing installation notes. See Notes about the installation Here are notes about the installation: Notes: 1. These instructions are written as if you hae downloaded the installation files from the IBM website. If you are installing the Managing Serer from CD-ROMs, additional windows prompting you to insert the required CD-ROMs are displayed. 2. By default, the installer creates log files in the following directories: Managing Serer Embedded IBM DB2 /ar/ibm/tioli/common/cyn/logs Note: A log.properties file is also created under /etc/ibm/tioli/common/ cfg. Files in the format: /tmp/db2setup.* 3. If the installer detects an existing IBM DB2 enironment on this serer, you receie an error message before you can begin the installation. You are instructed to uninstall it from this serer or choose another serer to install the Managing Serer on. You must then exit the installation. 4. If installation of the Managing Serer or embedded IBM DB2 fails during the installation, you must exit the installation and then rerun the installer. The installation program automatically cleans up the installation directories for the components whose installations hae failed. If the embedded IBM DB2 installation completed successfully, the installations remain intact. 5. The default password created for all DB2 users created during an embedded installation is itcam The three types of fields in the installer are: Prefilled, editable: you can either accept the default that is proided or enter your own alue. Blank: you must enter a alue of your own. Prefilled, noneditable: you cannot change the proided alue. These fields are not mentioned in the steps that follow. Copyright IBM Corp. 2006,

170 7. The Managing Serer distribution includes IBM WebSphere Application Serer and a license is proided. You can download the license from the same site where you download the Managing Serer package. In order to install WAS 8.x, you must also download IBM Installation Manager, if you hae not downloaded it already. After you install IBM Installation Manager, you can use the IBM Installation Manager to install IBM WebSphere Application Serer You do not need to buy a WAS license separately. What to do next See Custom installation steps. Custom installation steps Table 30. Exporting the DISPLAY ariable Complete the following custom installation steps: 1. If you are running the installation from a remote computer, enter xhost + hostname on the remote computer. The hostname is the fully qualified host name of the computer on which the Managing Serer is being installed. 2. Log in as the root user on the computer on which the Managing Serer is being installed. If you would like to install the Managing Serer as a non-root user, see Requirements to install the Managing Serer with a non-root user on page 125 for the requirements. 3. Export the DISPLAY ariable. Complete one of the following options: If you are running the installation from a remote computer Enter export DISPLAY=local_machine:0.0 Where local_machine is the fully qualified host name of the computer where you are sitting. If you are running the installation from the computer where the Managing Serer is being installed Enter export DISPLAY=localhost: Export the LANG ariable. Run the following command: export LANG=en_US.UTF-8 5. If you hae an existing installation of IBM WebSphere Application Serer, start the instance of IBM WebSphere Application Serer that is to be used by the Managing Serer. See Starting the application serer on page Complete one of the following options to start the installation: a. If you would like to open a window that inokes the installer, and gies access to prerequisite information, documentation, and support, use LaunchPad. For details on how to access LaunchPad, see Appendix B, Using the LaunchPad interface, on page 245 b. To directly start the installation without using LaunchPad or to auto-generate a response file for a silent installation, run the executable file for your operating system from the directory that contains your installation image: setup_ms_platform.bin. 7. The first window that is displayed is the Select log path window. Enter a location to store log files and click OK: 150 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

171 Table 31. Default temporary directories 8. The Welcome panel is displayed. Important: If the installation program detects that your computer does not match the basic prerequisites for starting the installation, a failure window opens instead of the Welcome panel. Refer to the information in the window to correct the situation and restart the installation. For more details on prerequisites, see Chapter 11, Prerequisites and pre-installation tasks for the Managing Serer on UNIX and Linux, on page Note the following installation points: The InstallShield portion of the installation program writes to one of the following system temporary directories by default: Operating system Solaris or HP-UX Linux and all other UNIX platforms Directory /ar/tmp /tmp If you do not want the InstallShield portion of the installer to write to this directory, run the executable file directly with the following option: -is:tempdir tmp_dir. For example:./setup_ms_platform.bin -is:temp_dir /opt/ibm/tmp The temp_dir is the directory you want the InstallShield portion of the installation program to write to. The user for the installation must hae read, write, and execute priileges to this directory. The installation program writes to the following log directory by default: /ar/ibm/tioli/common/cyn/logs If you do not want the installer to write to this directory, run the executable file directly with the following option: -V LOG_DIR=log_dir. For example:./setup_ms_platform.bin -V log_dir=/opt/ibm/log The log_dir is the directory you want the installer to write to. The user for the installation must hae read and write priileges to this directory. If you are trying to run the installation program on HP-UX directly from a CD, and the installation program does not start, complete the following steps: Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 151

172 Clean up the temporary directory for the InstallShield portion of the installation program. For example, for HP-UX the default temporary directory for the InstallShield portion of the installation program is /ar/tmp, so run the following commands: rm -fr /ar/tmp/ismp* rm -fr /ar/tmp/istemp* Specify the Jaa home when running the executable file to run the installation program. For example, if the CD-ROM drie is /mnt/cdrom, run the following command:./setup_ms_platform.bin -is:jaahome /mnt/cdrom/jaa/jre If you are installing the Managing Serer on HP-UX from a Windows computer using a Windows terminal emulation program, run the executable file from the directory that contains your installation image in the following way:./setup_ms_platform.bin -is:jaahome Jaa_home Jaa_home specifies the home directory for the Jaa Virtual Machine. For example, if you can find the Jaa file in /opt/jaa1.3/bin/jaa, Jaa_home is /opt/jaa Select I accept both the IBM and the non-ibm terms and click Next. The CD Install Selection panel is displayed. 11. Choose one of the following options: If you are installing from an image located on your hard disk, select No and click Next. If you are installing directly from a CD, select Yes so that the Managing Serer installation image can be copied to a temporary directory on your hard disk clearing the CD-ROM drie for the rest of the required installation disks. The Managing Serer installation image requires at least 1 GB of space. In addition, either accept the default temporary directory or browse to a different directory. Click Next. The Analyze System for Prerequisites panel is displayed. Important: The system checks if you are running the installation as the root user. If you are not, you cannot complete the installation 12. Wait for the installation program to finish its analysis and then click Next. The Choose Installation Type panel is displayed. 152 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

173 13. Select Custom and click Next. The Choose Features panel is displayed. 14. Select the features and click Next. The following descriptions explain which features you must select: Managing Serer: this option is selected by default. The Managing Serer is installed in all circumstances. Visualization Engine: Select this feature if you are installing the Managing Serer on this serer. Do not select if you are running the installer program for creating database tables for an existing database enironment on this serer and the Managing Serer is being installed on a separate serer. If this feature is selected, Managing Serer is automatically enabled. You cannot install the Visualization Engine without installing necessary Managing Serer files. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 153

174 Database Tables: Select this feature if you are installing IBM DB2 or creating database tables for an existing database enironment on this serer. Do not select this feature if you are using an existing remote database. If this feature is selected, Managing Serer is automatically selected. You cannot create database tables without installing necessary Managing Serer files. If you are not running the installation as the root user, the "Database Tables" option is disabled and you cannot select it. Important: Clear Database Tables if you are upgrading the Managing Serer. If you hae Database Tables selected, the data in the existing database tables is deleted. Click Next. The Choose Destination panel is displayed. 15. Click Next to accept the default installation directory path in the Directory Name field, or you can change this path by entering a different directory. Important: a. You cannot install the Managing Serer in a directory path that contains non-english language characters, for example: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters Cyrillic characters b. The directory that you specify must be empty. c. If you specify a directory that does not exist, the installation program creates the directory. 154 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

175 Click Next. The Enter TEPS Information panel is displayed. 16. Complete the following steps to configure the Tioli Enterprise Portal Serer information: a. If you would like to install database tables on the Tioli Enterprise Portal Serer DB2 database, select Install Database Tables on TEPS DB2 Database. b. If you would like to install the Visualization Engine on the Tioli Enterprise Portal Serer embedded WebSphere Application Serer, select Install Visualization Engine on TEPS ewas c. The Input ITM HOME field is displayed, enter the path for ITM_home Click Next. The Enter Database Information panel is displayed. 17. Complete the following steps to install IBM DB2: Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 155

176 a. Select Install DB2. b. Important: If the installer detects an existing IBM DB2 enironment on this serer, you cannot install IBM DB2. To complete an embedded installation of IBM DB2 instead of use an existing database, you must uninstall it from this serer or choose another serer to install the Managing Serer on. You must then exit the installation. Browse to select the db2setup file, which is commonly in the same directory as the db2 subdirectory. Table 32. Location of IBM DB2 installation Note: The installer installs IBM DB2 in one of the following directories: Linux and UNIX (non-aix) AIX, HP-UX or Solaris /opt/ibm/db2/v10.1 /opt/ibm/db2/v10.1 c. If you want to customize IBM DB2 options instead of accept the defaults, select Show Adanced Options and complete one or more of the following procedures: Table 33. Specifying adanced options when installing IBM DB2 Note: 1) On UNIX and Linux, you can use a preexisting user. The installation creates the user account with the name you specify unless it exists. 2) If this serer is part of a Network Information Serice (NIS) enironment, you cannot create DB2 user accounts from the installer. Create these accounts before starting the Managing Serer installation. See Network Information Serice enironment: creating the DB2 account users on page 127. IBM DB2 option to customize DB2 Administration Serer User Procedure If you would like to specify a DB2 Administration Serer user, complete the following procedure: 1. Click Edit DAS. A window for specifying the DB2 Administration Serer user opens. 2. Select Yes to create user, or select No to use an existing user. 3. Specify the DB2 Administration Serer user name. 4. Specify the password for the DB2 Administration Serer user. 5. If you are creating a user, specify the group name for the DB2 Administration Serer user. Note: The group must exist on the system. It is not created during the installation. 6. If you are creating a user, specify the home directory for the DB2 Administration Serer user. 7. Click OK. This account has full IBM DB2 priileges. The user ID for the DB2 administration serer user is used to run the DB2 administration serer on your system. 156 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

177 Table 33. Specifying adanced options when installing IBM DB2 (continued) DB2 Instance User If you would like to specify a DB2 Instance user, complete the following procedure: 1. Click Edit DBI. A window for specifying the DB2 Instance user opens. 2. Select Yes to create a user, or select No to use an existing user. 3. Specify the name of the IBM DB2 instance. 4. Specify the name of the DB2 Instance user. 5. Specify the password for the DB2 Instance user. 6. If you are creating a user, specify the group name for the DB2 Instance user. Note: The group must exist on the system. It is not created during the installation. 7. If you are creating a user, specify the home directory for the DB2 Instance user. 8. Click OK. The instance owner home directory is where the IBM DB2 instance is created. DB2 Fence User If you would like to specify a DB2 Fence user, complete the following procedure: 1. Click Edit DBF. A window for specifying the DB2 Fence user opens. 2. Select Yes to create a user, or select No to use an existing user. 3. Specify the DB2 Fence user name. 4. Specify the password for the DB2 Fence user. 5. If you are creating a user, specify the group name for the DB2 Fence user. Note: The group must exist on the system. It is not created during the installation. 6. If you are creating a user, specify the home directory for the DB2 Fence user. 7. Click OK. This account has priileges to administer IBM DB2. The DB2 Fence user is used to run user-defined functions (UDFs) and stored procedures outside of the address space used by the IBM DB2 enironment. DB2 Port Number DB2 Installation Location To specify the IBM DB2 port number, enter the port number in the text box. To specify the directory where IBM DB2 is to be installed, enter the path in the text box. Here are the default locations: Linux and UNIX (non-aix): /opt/ibm/db2/v8.1 IBM AIX: /usr/opt/db2_08_01 Here are the guidelines for entering the information: When entering a user ID: User IDs are limited to 30 characters. User IDs are not case-sensitie. You cannot use USERS, ADMINS, GUESTS, PUBLIC, LOCAL. You cannot begin the user name with SQL, SYS, or IBM. You can use a combination of upper- and lowercase characters. Howeer, sometimes they are conerted to uppercase in IBM DB2. You can use the numbers 0 through 9. You can use the following special #, or $. Examples (These are the defaults): DB2 Administration Serer: dasusr1 DB2 Fenced: db2fenc1 DB2 Instance: db2inst1 When entering a password: The general guidelines are the same as for the user name. You can use one to eight characters, without spaces. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 157

178 Do not begin the password with a number or an ampersand (&). Passwords are case-sensitie. When entering a group name: This string can hae one to eight characters, without spaces, and can be a combination of upper- and lowercase characters. Examples: DB2 Administration Serer: dasadm1 DB2 Fenced: db2fadm1 DB2 Instance: db2iadm1 When entering a home directory: This string can hae one to 64 characters, without spaces. Note: A DB2 connection problem can occur due to the difference between bit applications (Web Application Serer or Managing Serer) and between bit DB2 instances. If the installer is using 32 bit JVM, in some cases it cannot connect to DB2 to erify the connection. If the JVM for the Web Application Serer and Managing Serer is 32 bit, the local DB2 instance must also be 32 bit. If the JVM for the Web Application Serer and Managing Serer is 64 bit, the local DB2 instance must also be 64 bit. Refer to the following case headings to identify the scenarios releant to you work enironment. Table 34. Scenarios Header Case 1: The Managing Serer database is created on a 32 bit DB2 instance and JVM for the Managing Serer and WebSphere Application Serer is created on a 32 bit instance. Header The Managing Serer installer can check the DB2 connection during installation. To do this you must set the DB2 enironment ariables before launching the installer. When the installation is complete you must set the DB2 enironment ariables again before launching the Managing Serer installer and the WebSphere Application Serer. Use the following command lines to set the DB2 enironment ariables: For Bourne or Korn shell use this command:.insthome/sqllib/db2profile For C shell use this command: source INSTHOME/sqllib/db2cshrc Note: INSTHOME is the path of db2 instance home. 158 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

179 Table 34. Scenarios (continued) Header Header Case 2: The Managing Serer database is created on a 64 bit DB2 instance and JVM for Managing Serer and WebSphere Application Serer is created on a 64 bit instance. The Managing Serer installer cannot check the DB connection during installation. If you are using a Solaris platform you must make the following changes to allow the managing serer run in 64 bit mode. 1. Edit seten.sh in MS_home/bin. 2. Change JAVA_CMD=jaa to JAVA_CMD="jaa -d64". Then you must set the DB2 enironment ariables before you launch the Managing Serer and WebSphere Application Serer. Use the following command lines to set the DB2 enironment ariables: For Bourne or Korn shell use this command:.insthome/sqllib/db2profile For C shell use this command: source INSTHOME/sqllib/db2cshrc Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 159

180 Table 34. Scenarios (continued) Header Header Case 3: Managing Serer database is created on a 32 bit DB2 instance and JVM for the Managing Serer and WebSphere Application Serer is created on a 64 bit instance. The Managing Serer installer cannot check the DB connection during installation. Complete the following steps to resole this issue: 1. Create a 64 bit DB2 instance on the systems where the Managing Serer and the WebSphere Application Serer are installed. 2. Catalog the Managing Serer database on the 64 bit DB2 instance. (Refer to the DB2 manual for more information). 3. Configure the Managing Serer and the WebSphere Application Serer to connect to the cataloged database on the 64 bit instance. 4. On a Solaris platform, you must complete the following steps so the Managing Serer can run in 64 bit mode: a. Edit seten.sh in MS_home/bin b. Change JAVA_CMD=jaa to JAVA_CMD="jaa -d64". 5. Then to launch the Managing Serer and the WebSphere Application Serer, you must set the DB2 enironment ariables for the 64 bit instance. 6. Use the following command lines to set DB2 enironment ariables: a. For Bourne or Korn shell use this command:.inst64home/sqllib/db2profile b. For C shell use this command: source INST64HOME/sqllib/db2cshrc Note: INST64HOME is the path of 64 bit db2 instance home. Example (case 3): The Managing Serer database name is: MSDB (which is created on the 32 bit DB2 instance "db2int32"). The Managing Serer Host is: MSHOST 1. Create a 64 bit DB2 instance "db2int64" on MSHOST. 2. Catalog the Managing Serer database on the 64 bit DB2 instance. The alias name is MSDB_on_int Modify the Managing Serer database connection settings: a. Edit seten.sh in MS_home/bin b. JAVA_CMD=jaa --> JAVA_CMD="jaa -d64" c. JDBC_DRIVER_URL=jdbc:db2:MSDB --> JDBC_DRIVER_URL=jdbc:db2:MSDB_on_int64 d. JDBC_USER and JDBC_PASSWORD 4. Modify the WebSphere data source setting: a. Open the WebSphere Administration Console, naigate to Resources -> JDBC -> Data sources -> ITCAMDataSource. b. Change the database name to MSDB_on_int64. c. Modify user name and password of JAAS - J2C Authentication data. 160 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

181 Table 34. Scenarios (continued) Header Case 4: Managing Serer database is created on a 64 bit DB2 instance and JVM of Managing Serer and WebSphere Application Serer is created on a 32 bit instance. Header The managing seer installer cannot check the DB connection during installation. 1. Create a 32 bit DB2 instance on the system where the Managing Serer and the WebSphere Application Serer are installed. 2. Catalog the Managing Serer database on the 32 bit DB2 instance. 3. Configure the Managing Serer and the WebSphere Application Serer to connect the cataloged database on the 32 bit instance. 4. Before launching the Managing Serer and the WebSphere Application Serer, you must set the DB2 enironment ariables of the 32 bit instance. Use the following command lines to set the DB2 enironment ariables: For Bourne or Korn shell use this command:.inst64home/sqllib/db2profile For C shell use this command: source INST64HOME/sqllib/db2cshrc Note: INST32HOME is the path of 32 bit DB2 instance home. 18. If you are using an existing DB2 database, complete the following steps: a. Select Use an Existing Database to start the configuration of the existing database. b. In the Database Selection fields, select the Existing IBM DB2. c. Local IBM DB2 only: IntheDatabase Instance User ID field, enter the name of the user of the IBM DB2 instance In the Database Instance Password field, enter the password for the database instance user. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 161

182 Table 35. Adanced options for an existing IBM DB2 The database instance user ID and password were determined when the IBM DB2 enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. Note: If your passwords hae expired or you want to change them, you must modify your password in MS_home/bin/seten.sh and in the IBM WebSphere data source. d. In the Database Schema User ID field, enter the name of the user of the DB2 schema, for example, amuser. This user owns and can create the database tables for ITCAM for Application Diagnostics. In the Database Schema Password field type the password for the schema user. The database schema user ID and password were determined when the IBM DB2 enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. Note: If your passwords hae expired or you want to change them, you must modify your password in MS_home/bin/seten.sh and in the IBM WebSphere data source. e. From the JDBC type field, select one of the following options: Type 2 - JDBC type 2 Type 4 - JDBC type 4 f. Verify the full path to the required Jaa DataBase Connectiity (JDBC) files or browse to and select the db2cc.jar file. For example, these files might be located in the following path: /usr/db2inst1/sqllib/jaa/db2cc.jar. Note: If IBM DB2 is installed on a remote computer, you can copy the subdirectory containing the JDBC files to the local serer, then browse to and select that directory. g. If you would like to specify adanced options, such as the location of a remote database, select Show Adanced Options and complete one or more of the following fields: Field Database Host Port Number Database Name Description Type the fully qualified host name or IP address of the computer on which the existing IBM DB2 enironment is installed. This adanced option is aailable only if you hae selected JDBC type 4. Type the port number used by the IBM DB2 instance. Tip: You can discoer the correct port number to enter by completing the steps in Determining the port number for an IBM DB2 instance that exists on page 136, or you can consult your database administrator for the correct port to enter. This adanced option is aailable only if you hae selected JDBC type 4. Specify the database name. You can use any database name or the default name (octigate). h. Click Next. Note: The installation program oerrides the current alues for the following parameters in the IBM DB2 serer and changes them: 162 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

183 update dbm cfg using authentication serer; update dbm cfg using intra_parallel yes; update dbm cfg using query_heap_sz 2000; update dbm cfg using SHEAPTHRES ; update dbm cfg using FCM_NUM_RQB 768; update dbm cfg using MAXAGENTS 300; The DB2 administrator must make adjustments to ensure proper Data Collector configuration. Refer to the MS_home/etc/dbsettings.sql file for details. 19. Complete the following procedure to configure an existing Oracle database enironment: a. Select Use an Existing Database to start the configuration of the existing database. b. In the Database Selection field, select Existing Oracle. c. Enter the Oracle database system identifier number (SID) in the SID field. The SID is used to identify the Oracle database enironment. To find this alue, see the alue for the ORACLE_SID enironment ariable for the operating system. d. Local Oracle only: IntheDBA User ID field, enter the name of the Oracle database administrator In the DBA Password field, enter the password for the Oracle database administrator. The database administrator and password were determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. If your passwords hae expired or you want to change them, you must modify your password in MS_home/bin/seten.sh and in the IBM WebSphere data source. Note: The DBA User ID and DBA Password fields are only isible if you selected Database Tables in the Choose Features panel. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 163

184 e. In the Database Schema User ID field, enter the name of the user of the Oracle schema, for example, amuser). This user owns and can create the database tables for ITCAM for Application Diagnostics. In the Database Schema Password field, enter the password for the user.reenter the Oracle database schema password in the Verify Password field to make sure that you entered it correctly. The database schema user ID and password were determined when the Oracle enironment was configured before starting the Managing Serer installation. If you do not know them, consult your database administrator. If your passwords hae expired or you want to change them, you must modify your password in MS_home/bin/seten.sh and in the IBM WebSphere data source. f. Local Oracle only: erify the full path to the Oracle database home directory. See the Oracle database profile for details. g. Local Oracle only: type the name of an existing Oracle SQLPlus user in the Oracle SQLPlus User field. For example,oracle This user was determined when the Oracle database enironment was configured before starting the Managing Serer installation. If you do not know this alue, consult your database administrator. Note: The Oracle SQLPlus User and Oracle SQLPlus User Password fields are only isible if you selected Database Tables in the Choose Features panel. h. Select the JDBC type to use. From the list, you can choose the following JDBC types: Type 2 - JDBC type 2 Type 4 - JDBC type 4 Note: If you are using an Oracle database type 2 JDBC drier, you must run the following commands to set the Oracle database enironment ariables before launching the Managing Serer installer and again before launching the Managing Serer and the WebSphere Application Serer. Use the following commands to set the Oracle database enironment ariables: ORACLE_HOME=<ORACLE HOME> export ORACLE_HOME LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib export LD_LIBRARY_PATH i. Verify the full path to the required Jaa DataBase Connectiity (JDBC) files or browse to and select the classes12.jar file. This is a directory which contains JDBC libraries. This is an example: /opt/oracle/product/10g/jdbc/lib/ojdbc14.jar Tip: If the Oracle database is installed on a remote computer, you can copy the subdirectory containing the JDBC files to the local serer, then browse to and select that directory. j. To specify adanced options (such as specifying the location of a remote database), select Show Adanced Options and complete one or more of the following fields: 164 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

185 Table 36. Adanced options for an Oracle database Field Database Host Port Number Database Name Description Type the fully qualified host name or IP address of the computer on which the existing Oracle database enironment is installed. Do not include a protocol in the host name. For example, use myserer.ibm.tioli.com, not Proide a port number in the Port Number field. Do not accept the default port assignment (1521) if you hae assigned other applications to use that port number. Note: Consult your database administrator for the right port to enter. Specify the database name. You can use any database name or the default name (octigate). k. Click Next. 20. After completing the steps to set up your database enironment, the Enter WebSphere Application Serer Information panel is displayed. Complete the following procedure to configure an existing IBM WebSphere Application Serer: a. Ensure that IBM WebSphere Application Serer is installed on the Managing Serer computer. b. Select Use an existing IBM WebSphere Application Serer. The software searches for an installation of IBM WebSphere Application Serer. It then displays a list of discoered IBM WebSphere Application Serer instances. c. Complete the following steps: Select the IBM WebSphere Application Serer instance on which to install the Managing Serer. If the IBM WebSphere Application Serer instance on which to install the Managing Serer was not detected, you can specify another instance of IBM WebSphere Application Serer by completing the following steps: 1) Select the Manually specify an application serer node. 2) Browse to and select the AppSerer_home directory. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 165

186 3) Select the instance in the refreshed list of discoered IBM WebSphere Application Serer instances. Important: You cannot choose a IBM WebSphere Application Serer instance in a directory path (including profile, cell, node, and serer names) that includes the following types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters d. Click Next. If you selected Install Visualization Engine on TEPS ewas in the Enter TEPS Information panel, the Existing WebSphere Application Serer Information panel is displayed. The following table describes the fields in this panel: Table 37. IBM WebSphere Application Serer configuration for an existing installation where VE is installed on the Tioli Enterprise Portal Serer ewas Field Host Name What to do Type the fully qualified host name or IP address of the IBM WebSphere Application Serer where the Managing Serer runs. Note: If using Network Deployment, proide the host name of the Deployment Manager instead. 166 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

187 Table 37. IBM WebSphere Application Serer configuration for an existing installation where VE is installed on the Tioli Enterprise Portal Serer ewas (continued) Field What to do SOAP Connector Port Enter the SOAP port setting (The default is 8880). This connector port is used by the IBM WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). User Name The SOAP port is identified in the AppSerer_home/profiles/ profile_name/config/cells/cell_name/nodes/node_name/ sererindex.xml file of the instance of IBM WebSphere Application Serer that the Managing Serer uses. Note: If using Network Deployment, proide the SOAP port of the Deployment Manager instead. If Global Security is enabled on the WebSphere Application Serer, type the user name of WebSphere Application Serer Administrator. This user is the user that logs in to the WebSphere Administration console. If Global Security is not enabled on the WebSphere Application Serer, type the user name of your local Operating System. The Managing Serer uses this user to enable Global Security on the WebSphere Application Serer. For this to happen, the WebSphere Application Serer must be launched by the root user,ibm WebSphere Application Serer. Note: This user must hae the same types of permissions as described in the following section: Permissions for an existing IBM WebSphere Application Serer on page 127. e. If you selected Install Visualization Engine on TEPS ewas in the Enter TEPS Information panel, theexisting WebSphere Application Serer Information panel is displayed. The following table describes the fields in this panel: Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 167

188 Table 38. IBM WebSphere Application Serer configuration for an existing installation where the VE is not installed on the Tioli Enterprise Portal Serer ewas Field Host Name SOAP Connector Port What to do Type the fully qualified host name or IP address of the IBM WebSphere Application Serer where the Managing Serer runs. Tip: If using Network Deployment, proide the host name of the Deployment Manager instead. Enter the SOAP port setting (The default is 8880). This connector port is used by the IBM WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). The SOAP port is identified in the AppSerer_home/profiles/profile_name/config/cells/ cell_name/nodes/node_name/sererindex.xml file of the instance of IBM WebSphere Application Serer that the Managing Serer uses. Tip: If using Network Deployment, proide the SOAP port of the Deployment Manager instead. User Name Password User Interface User If Global Security is enabled on the WebSphere Application Serer, type the user name of WebSphere Application Serer Administrator. This user is the user that logs in to the WebSphere Administration console. If Global Security is not enabled on the WebSphere Application Serer, type the user name of your local Operating System. The Managing Serer uses this user to enable Global Security on the WebSphere Application Serer. For this to happen, the WebSphere Application Serer must be launched by the root user,ibm WebSphere Application Serer Important: This user must hae the same types of permissions as described in the following section: Permissions for an existing IBM WebSphere Application Serer on page 127. Type a user password. To change the default, select Show Adanced Options and enter the name that you want for the user for logging in to and using the ITCAM for Application Diagnostics Managing Serer. Important: The default is the root user. If it is different from the root user, make sure that user has root priileges. Note: If you are using a non-root user to install the Managing Serer, the User Interface User field is disabled, and the User Interface User is the same as the user name of WebSphere Application Serer Administrator. You can change the name after installation. Note: If you are using a non-root user to install the Managing Serer, you must enable WebSphere Global security or you receie a message similar to the following: 'CYNCR9703E The global security of the WAS profile selected is disabled. For a non-root user the WAS profile must enable global security.' 21. Click Next. The Select WebSphere Application Serer panel is displayed. Naigate to select the serer, and click Next. 168 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

189 22. After completing the steps to set up your IBM WebSphere Application Serer, the Enter Managing Serer Information panel is displayed. Complete the following steps: a. Enter the fully qualified host name or IP address of the serer where you want to install the Managing Serer. If memory resources on one Managing Serer are insufficient to support your enironment, for example, if you would like to hae it connect to many Data Collectors (such as 500 or more), create a second Managing Serer that is different from the first Managing Serer. See Split Managing Serer installation in Unix on page 215 for instructions on how to install the Managing Serer on two separate serers. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 169

190 b. If you would like to change the default port numbers used by the Managing Serer components, select Show Adanced Options and edit the alues. Accept each proided alue unless the port number has been used already. c. Click Next. The Generate Response File panel is displayed. d. If you would like to install the Managing Serer on this computer, select Install the Managing Serer on this computer. Tip: You might not want to install the Managing Serer on this computer if you are completing the installation procedure only to create a response file for a subsequent silent installation. To create a response file for a subsequent silent installation, select Sae the settings in a response file and enter the file path ending with a file name. For example: /temp/response.opt A response file is only generated if the GUI installation completes successfully. e. Click Next. The Reiew Installation Information panel is displayed. 170 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

191 f. Read the summary information and click Install to accept it and begin the installation. The Install and Configure Files panel is displayed. The progress bar might appear as stuck at a certain position for a long time during the installation. This is to be expected, especially for embedded IBM DB2 installation. Allow the installation to continue. Depending on the performance of your serer and operating system, installation can take longer than an hour. g. When the installation finishes, the Reiew Installation Summary is displayed Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 171

192 Important: If the summary panel displays one of the following messages, you must install database tables manually: There are problems in the communication between the Managing Serer and the database. Installation of the database tables failed or is incomplete. In this case, see Manually creating database tables on page 49. h. Read the information in the panel and click Next. The Finish panel is displayed. i. If you would like to complete post-installation tasks at this time (recommended), select Launch the Managing Serer and Launch the User Interface. j. Click Finish. 172 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

193 Post-installation tasks Complete the following steps: 1. If you used a non-root user to install the Managing Serer, modify the user profile to add the following system ariables: Add MS_home/lib/LUMClient.jar to the CLASSPATH system ariable. Add MS_home/lib to the LIBPATH and LD_LIBRARY_PATH system ariables. 2. Restart the instance of IBM WebSphere Application Serer that is used by the Managing Serer. See Restarting the application serer on page If you hae installed a web serer, set it up to forward requests to the Managing Serer by regenerating the web serer plug-in. Complete the following procedure: a. Create a web serer definition. Follow the instructions at one of the following websites: Table 39. Websites with instructions to create a web serer definition IBM WebSphere Application Serer ersion 7.0 (non-network Deployment enironment) 7.0 (Network Deployment enironment) 8.0 (non-network Deployment enironment) 8.0 (Network Deployment enironment) (non-network Deployment enironment) (Network Deployment enironment) URL com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/info/aes/ae/tpro_instancessaappser.html com.ibm.websphere.nd.doc/info/ae/ae/tpro_instancessaappser.html com.ibm.websphere.base.doc/ae/tpro_instancessaappser.html?lang=en com.ibm.websphere.nd.doc/ae/tpro_instancessaappser.html?lang=en b. In the IBM WebSphere Application Serer administratie console, go to Serer > Web serers. c. Select the Web serer check box. d. Click Generate Plug-in. e. Restart the web serer. 4. If you completed a GUI installation and you did not make the selections in Step 22i on page 172 of the final installation steps, start the Managing Serer and the ITCAM for Application Diagnostics Managing Serer. See Starting the Managing Serer on page If you completed a silent installation or upgrade, start the ITCAM for Application Diagnostics Managing Serer. If you did not enable the option to start the Managing Serer, first start the Managing Serer. See Starting the Managing Serer on page Verify that the Managing Serer components are enabled and running. See Verifying that Managing Serer components are up and running on page Complete the tasks described in each of the following sections, if applicable. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 173

194 Importing transaction data from Managing Serer to IBM Rational Performance Tester Problem Analysis tools in IBM Rational Performance Tester (RPT) can process and analyze transaction data from ITCAM for Application Diagnostics through a web serice. ITCAM for Application Diagnostics supports RPT ersion 7.x and 8.x. To see ITCAM data in RPT, create application traps with method trace data action in VE. For the Managing Serer to work with RPT, complete the following steps: 1. For information about RPT and how to install it, see the following website: 2. If you hae installed the Managing Serer with an existing IBM WebSphere Application Serer 8.5.5, enable IBM WebSphere Global Security manually: a. Log in to the IBM WebSphere Application Serer administratie console. b. Go to Security > Secure administration, applications, and infrastructure > Application security. c. Select Enable Application Security. d. Click Apply. e. Sae your changes. For all existing IBM WebSphere Application Sererinstallations except ersion 6.1, IBM WebSphere Global Security was automatically enabled during Managing Serer installation. 3. Enable method signature tracing. See Enabling method signature tracing on page 221. In RPT, take the following steps to import transaction data from Managing Serer to RPT: 1. Start IBM Rational Performance Tester - Full Eclipse, from the File menu select Import. 2. In the Select window, select Response Time Breakdown Data and click Next. 3. In the Location window, take the following steps: a. In the Monitoring Serer section, enter VE host name in Host field. b. In the Authentication section, enter the VE user and password. c. In the Connection section, select Use port and enter the VE port number, click Next. 4. In the Constraints window, specify the time for which you want to import data, click Next. 5. In the Trap window, select a trap to see method trace data. Enabling Configuration Management Database Discoery Library integration and executing the feature ITCAM for Application Diagnostics has a feature that can extract releant resources and relationships from the ITCAM for Application Diagnostics database. These resources and relationships are retrieed and stored by the Configuration Management Database (CMDB), which is the central source of information in the IT Infrastructure Library (ITIL). This feature produces XML files from the monitoring information contained within theitcam for Application Diagnostics database. The CMDB Discoery Library can then store these XML files in its warehouse of IdML book files. 174 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

195 Only CICS/IMS related transaction information is exported into the CMDB. Complete the following procedure to enable and use this feature: 1. Ensure that the serer where the Managing Serer is installed has write access to the file system that contains the CMDB Discoery Library repositories of IdML book files. 2. (optional) Copy the MS_home/etc/cmdb/TCAMfWAS.zip file to a new directory. 3. Extract the file into the current directory. 4. Modify the adapter.properties file to reflect the settings for your Managing Serer. See the comments in the file for instructions for modifying the file. 5. Modify the script in that directory (dladapter.sh) to point to the location of the database JDBC driers (.jar files) for your Managing Serer. 6. Modify dladapter.sh to hae the correct Jaa path for the Jaa files on your Managing Serer. Enabling the feature Complete the following procedure to enable this feature: 1. Ensure that the serer where the Managing Serer is installed has write access to the file system that contains the CMDB Discoery Library repositories of IdML book files. 2. (optional) Copy the MS_home/etc/cmdb/TCAMfWAS.zip file to a new directory. 3. Extract the file into the current directory. 4. Modify the adapter.properties file to reflect the settings for your Managing Serer. See the comments in the file for instructions for modifying the file. 5. Modify the script in that directory (dladapter.sh) to point to the location of the database JDBC driers (.jar files) for your Managing Serer. 6. Modify dladapter.sh to hae the correct Jaa path for the Jaa files on your Managing Serer. Executing the Discoery Library Adapter Script Complete the following procedure to run the Discoery Library Adapter script: From the directory that contains the dladapter.sh file, run the following command:./dladapter.sh [-erbose -extremelyverbose] [configfile] The configfile is the full path and file name of the modified adapter.properties configuration file. If you changed the name of the file or saed it to another directory, you must enter a alue for this option. The -erbose option indicates a detailed tracing leel (for debugging). It is the equialent of DEBUG_MID. Do not use this option without the guidance of Leel 3 IBM Software Support. The -extremelyverbose option indicates a detailed tracing leel that requires large amounts of disk space. It is the equialent of DEBUG_MAX. Do not use this option without the guidance of Leel 3 IBM Software Support. Note: 1. If you run the script without any options, you can click the file from Windows Explorer to run it. Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 175

196 2. The monitoring information must first be aailable in the ITCAM for Application Diagnostics database before the Discoery Library Adapter can produce the XML files. Manually creating database tables If during the Managing Serer installation, installation of the database tables fails, the failure is indicated by messages in the Managing Serer installation summary panel. The summary information displays one of the following messages: There are problems in the communication between the Managing Serer and the database. Installation of the database tables failed or is incomplete. The problem occurs when you select Database Tables as a feature to install during a Custom Managing Serer installation, during Step 14 on page 153. (The only time when you would not select Database Tables as a feature to install is when you are using an existing remote database.) If the Managing Serer files hae been successfully installed, but installation of the necessary database tables has failed, you can manually create the database tables. Manually creating DB2 tables If your database is DB2, complete the following procedure: 1. Extract the db2-remote-scripts.tar file from the MS_installation_image_directory/ base/scripts directory into a temporary directory. 2. Run the db2install.sh file as the DB2 Instance user. You also need the password for the schema user. For example, cd /tmp/db2/bin sh db2install.sh db_username schema_user absolute_path_installation_dir user_interface_user DB2ersion databasename Note: 1. db_username is the database administratie user who can execute DB2 commands and create tables. If you installed DB2 with the Managing Serer, this is the DB2 instance user, which is by default db2inst1 with a password of itcam schema_user owns and can create the database tables for the product. If you installed DB2 with the Managing Serer, this is the DB2 instance user, which is by default db2inst1. When you run the script you are prompted for a password. 3. absolute_path_installation_directory the directory containing the /bin/db2install.sh files. For example,/tmp/db2 4. user_interface_user is the user that is used when logging in and operating the Managing Serer's ITCAM for Application Diagnostics Managing Serer after installation and configuration. This alue is the installation user (default) or a alue you specified during the Managing Serer installation. Manually creating Oracle database tables If your database is Oracle, complete the following procedure: 1. Extract the oracle-remote-scripts.tar file from the MS_installation_image_directory/base/scripts directory into a temporary directory. 2. Run the following command to export the ORACLE_SID used by the Managing Serer: 176 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

197 export ORACLE_SID=octigate 3. Run the oracleinstall.sh script, which has the following format: cd /tmp/oracle sh bin/oracleinstall.sh dba_user dba_password tablespace schema_user schema_password user_interface_user Note: 1. dba_user must be the owner of the Oracle database hierarchy. For example: system. 2. tablespace is the name of the table space that is created when you run the oracleinstall.sh script. This is the table space the Managing Serer uses. This table space is remoed if it exists. 3. schema_user is the user that the Managing Serer uses to connect with Oracle, using JDBC. This schema user must exist in the local operating system. This user was specified during the Managing Serer installation. 4. user_interface_user is the user that is used when logging in and operating the Managing Serer ITCAM for Application Diagnostics Managing Serer after installation and configuration. This alue is the installation user (default) or a alue you specified during the Managing Serer installation. Configuring Simplified Chinese as the browser language When the browser language is set to Simplified Chinese, make the following change: in AppSerer_home/properties/encoding.properties, edit the property for zh by changing zh=gb2312 to zh=utf-8. Setting default browser resolution To iew the ITCAM for Application Diagnostics Managing Serer, if the user's language is English, set the default browser resolution to 1024X768. For all other languages, set the browser resolution to 1280X1024. Network Deployment enironment: erifying and updating the irtual host port number For a Network Deployment enironment, you must erify and (if required) update the irtual host port number in the IBM WebSphere Application Serer administratie console. Complete the following steps: 1. Find the port number in the following file: AppSerer_home\profiles\ profile_name\config\cells\cell_name\nodes\node_name\sererindex.xml. Look for WC_defaulthost. 2. Log in to the IBM WebSphere Application Serer administratie console. 3. Expand Enironment on the left menu and click Virtual Hosts > default host > Host Aliases. 4. Verify that the port number discoered in Step 1 exists. 5. If it does not, create the port in the irtual hosts file by clicking New and proiding the host name as *. 6. Enter the port number and sae the configuration. What to do next Complete the following steps: 1. Restart the instance of IBM WebSphere Application Serer that is used by the Managing Serer. See Restarting the application serer on page Complete any of the following options: Chapter 13. Custom installation for the Managing Serer on UNIX and Linux 177

198 (optional) Set up security for the Managing Serer. See Appendix C, Setting up security, on page 247. (optional) Complete customizations of the Managing Serer. See Chapter 16, Customization and adanced configuration for the Managing Serer on UNIX and Linux, on page 213. (optional) Install a language pack. See Appendix D, Language Packs for Managing Serer, on page Install and configure a Data Collector. See one of the following publications: IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide IBM Tioli Composite Application Manager for WebSphere (z/os): Data Collector Customization Guide Note: Before configuring a Data Collector on IBM z/os, it must be installed. See the Program Directory for IBM Tioli Composite Application Manager for WebSphere (z/os). IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 4. After you hae started using this product to monitor your application serers, perform periodic maintenance on the Managing Serer. See Appendix F, Maintaining the monitoring enironment, on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

199 Chapter 14. Silent installation for the Managing Serer on UNIX and Linux This chapter describes how to use a command-line command pointing to a response file instead of a GUI installer to install the Managing Serer. Installation through the response file without user interaction is called silent installation. The installation program references a response file located on a hard disk in the network, which contains most or all of the specifications for the installation. You can use a response file for the following reasons: You can reuse the response file for multiple installations. The response file preseres configuration data for an installation, so that you can identify configuration details at a later date. You usually complete the silent installation by running it once from a command line, but you can also complete a silent installation in three phases. The first phase installs Managing Serer files, the second phase deploys the ITCAM for Application Diagnostics Managing Serer component and registers the configuration in IBM WebSphere Application Serer, and in the third phase you assign database permissions. You can use this option to install the Managing Serer files without haing to know the IBM WebSphere Application Serer user name and password. For the silent installation completed in one phase, this chapter lists the configuration options for installing the Managing Serer. You modify the configuration options either in the response file or at the command line to run the silent installation. Begin this chapter at one of the following sections: If you are completing a silent installation in three phases, see UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems. If you are completing a normal silent installation (completed in one phase), see Performing a normal silent installation (in one phase) on page 184. UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems The three phase install instructions supplied for preious ersions are no longer alid. The new updated instructions enable the user to use the normal (one phase) installer to achiee the three phase install capabilities. You can complete a three phase Managing Serer installation using three different logins. The logins are: Managing Serer installation - this login is the Managing Serer (MS) installation user. Managing Serer Application Monitoring user interface (Visualization Engine, VE) installation - this login is the WebSphere user. Database instance - this login is the database administrator user. Copyright IBM Corp. 2006,

200 With this process, you can install the Visualization Engine on a separate serer, to make more resources aailable for it. You cannot install the Visualization Engine and the other Managing Serer components on the same serer with different logins. Howeer, you can run (not install) MS and VE on the same serer with two different users. To do this, install MS and VE with the same non-root user initially, and then change the user of the MS file system. Refer to the section Running the Managing Serer and the Visualization Engine on the same host with two different non-root user names on page 183 for further instructions. If you install the Visualization Engine on a separate serer, the WebSphere Application Serer must only be installed on the Visualization Engine serer and not on the serer where the Managing Serer files were installed (called the main serer in this chapter). Howeer, you must copy the jaa directory from the Visualization Engine serer to the main serer. The following three phases are inoled: First Phase - in this phase, you log in as the Managing Serer installation user and install the Managing Serer files. Second Phase - in this phase, you log in as the WebSphere user, deploy the ITCAM for Application Diagnostics Managing Serer component, and register the configuration in IBM WebSphere Application Serer. Third Phase - in this phase, you log in as the database instance user (DB2 or Oracle) and gie the user write and execute access permission to db2-remote-scripts.tar or the oracle-remote-scripts.tar. The following procedure describes the steps inoled in a three phase installation: 1. Complete the following steps to prepare for the three phase installation: a. Ensure WebSphere Application Serer ersion or higher is installed with Global Security Enabled. b. Before installing Managing Serer, copy the installation image to the serer where you are completing the installation. Create the following directory to hold the installation image: Managing_Serer_installation_image_directory. c. Specify configuration options in one of the response file templates Managing_Serer_installation_image_directory/silent/MS_Sample.opt or Managing_Serer_installation_image_directory/silent/MS.opt. For more information, see the following sections: Requirements for a response file on page 186 Example of a modified response file template mirroring a three phase installation (Managing Serer only) on page 188 Configuration options list on page 189 Attention: If you sae the response file in a location other than Managing_Serer_installation_image_directory/silent, ensure that the directory is readable by the user performing the silent installation. 2. Complete the following steps to install the Managing Serer components: a. Log in as the Managing Serer installation user. Ensure that this user has the permission to run JAVA. The user must also hae read, write, and execute priileges to one of the following system temporary directories. 180 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

201 Table 40. Default temporary directories Operating system Solaris or HP-UX Linux and all other UNIX platforms Directory /ar/tmp /tmp The user must be able to log to /ar/ibm/tioli. You might hae to create this directory as root and use the chown command to change ownership to the user. The installation program does not write to this directory; only the Managing Serer itself uses it. You can also use response file options to alter the log file directory location. b. Access the technote at dociew.wss?uid=swg &w=1 and download the file itcamfwas.jar. In both the Managing_Serer_installation_image_directory/lib and Managing_Serer_installation_image_directory/jars locations, back up the original itcamfwas.jar and replace it with the downloaded ersion. c. In the command-line interface, change to the Managing_Serer_installation_image_directory directory. The setup_ms_platform.bin file is located in this directory. d. Run the following installation command:./setup_ms_platform.bin -silent [-is:log [log_file_name]] [-is:tempdir temp_dir] [configuration_option...] -options response_file log_file_name Specifies the path and name of the log file that the silent installer writes to. The file is created een if it does not yet exist or if no name is specified. The user for the installation must hae read and write priileges to the directory where this file is located. temp_dir Specifies the path and name of the temporary directory that the InstallShield portion of the silent installer writes to. The user for the installation must hae read, write, and execute priileges to this directory. configuration_option Specifies one or more configuration options not included in the response file. See Configuration options list on page 189. response_file Specifies the response file you configured in Step 1 on page 180. Indicate the path and name of the file. Here is an example of an installation command when performing a custom installation:./setup_ms_platform.bin -silent -is:log /opt/tmp/mslog.txt -V PORT_KERNEL_RMI01=9133 -options /opt/silent/ms_sample.opt Configuration options specified in the response file take precedence oer options entered in the command line. For a particular command-line configuration option to take effect, you must first nullify that option in the response file by commenting it out with a number sign (#). 3. You can use one of the following options to install the Visualization Engine on a separate serer. Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 181

202 a. You can use the GUI installer to install the VE. During the feature selection, uncheck the install database option. See Post-installation tasks on page 173. b. You can use the silent installer to install the VE. In the silent properties file, specify -P dbinstall.actie=false. See Performing a normal silent installation (in one phase) on page 184. Tip: For options 3a and 3b, the installer automatically installs the MS file system. c. You can install the VE manually. First, copy the MS_home (Managing Serer installation) directory from the main serer, where the preious steps were performed, to the same location on the new Visualization Engine serer. Then, follow the instructions in Appendix L, Manually install MSVE, on page 319 to run jacl scripts and configure the WebSphere Application serer. If you hae installed the Visualization Engine on a separate serer, perform the following additional steps: a. Copy the jaa (JVM) directory from AppSerer_home on the Visualization Engine serer to any location on the main serer. On the main serer, set the JAVA_HOME enironment ariable to the full path to this directory. b. Copy the AppSerer_home/lib directory from the Visualization Engine host to the main serer. Use the same absolute path as used on the Visualization Engine host. c. On the main serer, in the file MS_home/bin/seten.sh, adjust the setting for JAVA_HOME to the location of the copied jaa directory. In the same file, set the WAS_HOME ariable to the absolute path of AppSerer_home on the Visualization Engine host. (This setting is used to determine the location of the copied lib directory). 4. To gie the DB2 Instance user write and execute access permission to Managing_Serer_installation_image_directory/base/scripts/db2-remotescripts.tar, complete the following steps: a. Log in as the DB2 Instance user. b. Create a temporary directory under the DB2 Instance user home directory, copy the db2-remote-scripts.tar file from Managing_Serer_installation_image_directory/base/scripts to this temporary directory and extract it. c. Go to temporary_directory/db2/bin and run the following command as the DB2 Instance user:./db2install.sh <DB2inst_username> <db_user> <absolute_path_of_db2scripts_dir> <adminveuser> <databasename> <DB2ersion> <databasename> Note: 1) When prompted for a password, enter the password for the <schema user>. 2) <DB2inst_username> must hae dba priileges. 3) <db_user> owns and can create the database tables for the product. 4) <absolute_path_of_db2scripts_dir> is the absolute directory containing bin/db2install.sh, for example: /home/db2inst1/tmp/db2. 5) <adminveuser> is the user that is used when logging in and operating the Managing Serer Application Monitor (MSVE) after installation and configuration. 182 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

203 6) <databasename> is the Managing Serer Database name which is specified in ITCAM_INSTALL.properties. 5. To gie the Oracle database Instance user write and execute access permission to Managing_Serer_installation_image_directory/base/scripts/oracleremote-scripts.tar, complete the following steps: a. Log in as the Oracle database instance user. b. Create a temporary directory under the Oracle database home directory, copy the oracle-remote-scripts.tar file from Managing_Serer_installation_image_directory/base/scripts to the temporary directory and extract it. c. For the Oracle database user, go to <temporay directory>/oracle/bin and run the following command as the Oracle System user../oracleinstall.sh oracle_sid sqlplus_user sqlplus_password tablespace jdbc_user jdbc_password adminveuser For example: /opt/oracle-remote-scripts/oracle/bin$./oracleinstall.sh octigate system zhu88jie octigate system zhu88jie Administrator 6. Restart WebSphere Application Serer as the WebSphere user. 7. Restart Managing Serer as the Managing Serer user. Running the Managing Serer and the Visualization Engine on the same host with two different non-root user names You must install the Managing Serer and the Visualization Engine on a host using one user name. Howeer, you can run them with two different non-root user names. To do this, complete the following procedure: 1. Install the MS and the VE using the same non-root user name, for example wasuser. You can use any installation method to achiee this result. See REQUIREMENTS_LINK. The VE runs under this user name. 2. Apply any fix packs that you need to apply. 3. Create another user that runs the Managing Serer components. For example,msuser 4. Change the owner of the Managing Serer directory to the new user: chown msuser MS_home 5. The Managing Serer installation user and the WebSphere user must hae the following permissions: The Managing Serer installation user must hae read and execute permission to the WebSphere installation directory. The WebSphere user must hae read, write, and execute permission to the Managing Serer installation image directory. The WebSphere user must hae read and write permission to the Managing Serer Log directory. To assign these permissions, complete the following steps: a. To assign the Managing Serer installation user read and execute permission to the WebSphere installation directory, use the following command: chmod -R 755 <WebSphere DIR> b. To assign the WebSphere user read, write and execute permission to the Managing Serer installation image directory (excluding the bin directory), use the following command: Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 183

204 If both users are in the same group, use the following commands: chmod 770 <MS DIR> chmod -R 770 <Sub directories MS DIR> If both users are in different groups, use the following commands: chmod 777 <MS DIR> chmod -R 777 <Sub directories MS DIR> When assigning permissions to the Managing Serer installation image sub directories, remember to exclude the bin directory. c. To assign the WebSphere user read and write permission to the Managing Serer Log directory, use the following command: If both users are in the same group chmod -R 760 <MS log DIR> If both users are in different groups: chmod -R 766 <MS log DIR> 6. Restart Managing Serer as the Managing Serer user. 7. Restart WebSphere Application Serer as the WebSphere user. Attention: If you decide to apply any Fix Packs later, you must reassign ownership of all files back to the original user (wasuser). In this case, after applying the Fix Packs, complete Step 4 on page 183 again. What to do next See Post-installation tasks on page 173. Performing a normal silent installation (in one phase) Table 41. Location of installation log files Start the normal silent installation by reiewing the notes about the installation. Notes: 1. Copy the installation images to a hard disk. See Appendix A, Obtaining installation images, on page If the serer is part of a Network Information Serice (NIS) enironment, you cannot create DB2 user accounts from the installer. Create these accounts before starting the Managing Serer installation. If you are in an NIS enironment and did not create the users yet, complete the instructions in Network Information Serice enironment: creating the DB2 account users on page By default, the installer creates log files in the following directories: Managing Serer Embedded IBM DB2 /ar/ibm/tioli/common/cyn/logs Note: A log.properties file are created under /etc/ibm/tioli/common/cfg. Files in the format: /tmp/db2setup.* 4. If the installer detects an existing IBM DB2 enironment on this serer, you cannot install IBM DB2. If you want to complete an embedded installation of IBM DB2 instead of use an existing database, you must uninstall it from this serer or choose another serer to install the Managing Serer on before you begin the installation. 184 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

205 5. If installation of the Managing Serer or embedded IBM DB2 fails during the installation, you must exit the installation and then rerun the installer. The installation program automatically cleans up the installation directories for the components whose installations hae failed. If embedded IBM DB2 installation completed successfully, the installations remain intact. What to do next See Executing the silent installation command. Executing the silent installation command About this task Complete the following procedure to run the silent installation command: Procedure 1. Log on to the computer (on which you want to install the Managing Serer) as the root user. If you want to install the Managing Serer as a non-root user, see Requirements to install the Managing Serer with a non-root user on page If you hae an existing installation of IBM WebSphere Application Serer, start the instance of IBM WebSphere Application Serer that is used by the Managing Serer. 3. Specify configuration options in one of the response file templates and sae the file. You must specify "Custom" as it is the only supported installation type. The sample response file is installation_image_directory/silent/ MS_Sample.opt or MS.opt. For more information, see the following sections: Requirements for a response file on page 186 Example of a modified response file template mirroring a Custom installation on page 187 Configuration options list on page 189 Note: a. Optionally, you can use a response file created by a GUI installer installation. Ensure during installation, that in the Generate Response File panel, you select Sae settings in a response file and enter the file path ending with a file name: b. If you sae the response file in a location other than installation_image_directory/silent, ensure that directory is readable by the user performing the silent installation. 4. Use the command-line interface to access the directory that contains the installation executable file. The setup_ms_platform.bin file is located in this directory. Type the following installation command and press Enter../setup_MS_platform.bin -silent [-is:log [log_file_name]] [-is:tempdir temp_dir] [configuration_option...] -options response_file log_file_name Specifies the path and name of the log file that the silent installer writes to. The file is created een if it does not yet exist or if no name is specified. The user for the installation must hae read and write priileges to this directory. temp_dir Specifies the path and name of the temporary directory that the Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 185

206 InstallShield portion of the silent installer writes to. The user for the installation must hae read, write, and execute priileges to this directory. configuration_option Specifies one or more configuration options not included in the response file. See Configuration options list on page 189. response_file Specifies the response file you configured in Step 3 on page 185. Indicate the path and name of the file. Here is an example of an installation command when performing a custom installation:./setup_ms_platform.bin -silent -is:log /opt/tmp/mslog.txt -V PORT_KERNEL_RMI01=9133 -options /opt/silent/ms_sample.opt Configuration options specified in the response file take precedence oer options entered in the command line. For a particular command-line configuration option to take effect, you must first nullify that option in the response file by commenting it out with a number sign (#). What to do next See Post-installation tasks on page 173. Requirements for a response file A response file must hae the following characteristics: Contains the configuration options for your installation, which are listed in Configuration options list on page 189: The names of the configuration options must follow the uppercase and lowercase conentions shown in Configuration options list on page 189, because they are case-sensitie. Each configuration option must exist on a separate line. The configuration options can be sorted in any order. Does not contain null alues. If you do not specify a alue for a configuration option, you must ensure that line is commented out with a number sign (#), or that the alue string to the right of the equal sign (=) is NULL. Does not contain the -silent flag, the -options flag, or -is If there are any spaces in the alue string to the right of the equal sign (=), the alue must be enclosed in double quotation marks. It is best to enter the alue between the double quotation marks that are already in the response file template. Note: When you use a response file to specify options, you can type additional options in the command line. Manually typing configuration options This section lists some reasons to manually type configuration options, instead of including them in the response file: Unique options: to reuse the response file in multiple installations, but some of the options are unique to each installation. Manually type the unique options in the command line during each installation. The response file supplies the alues that are alid only for multiple target computers. 186 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

207 Note: If you want to reuse a response file in multiple installations, but some of the options are unique to each installation, nullify those options in the response file by commenting them out with a number sign (#). This is because configuration options specified in the response file take precedence oer those entered in the command line. Make sure that for each of the installations using that response file, the commented-out configuration options are entered in the command line. Password protection: to safeguard the password by manually entering it during each installation. If you record the password in the option (.opt) file, the password is unencrypted and isible to anyone who opens the file. The following example sets one of the passwords on the command line and relies on a response file to proide all other configuration details:./setup_ms_platform.bin -silent -V WAS_USER_PWD="tioli" -options /opt/ibm/itcam/images/silent/ms_sample.opt Example of a modified response file template mirroring a Custom installation This is an example of a response file modified with suitable alues using the MS_Sample.opt file as a template. It corresponds to alues that are specified if you complete a Custom installation: -V disableosprereqchecking=true -V LICENSE_ACCEPT_BUTTON=true -V LICENSE_REJECT_BUTTON=false -V IS_SELECTED_INSTALLATION_TYPE=custom -W LogSetting.logLeel=ALL -W LogSetting.consoleOut=false -V LOG_DIR="/ar/ibm/tioli/common/CYN/logs" -P installlocation="/opt/ibm/itcam/websphere/ms" -P msfilesinstall.actie=true -P einstall.actie=true -P dbinstall.actie=true -V ITCAM_SYS_USERS=root -V KERNEL_HOST01=kernalhost01.us.ibm.com -V PORT_ARCHIVE_AGENT1=9129 -V PORT_ARCHIVE_AGENT2=9130 -V PORT_KERNEL_CODEBASE01=9122 -V PORT_KERNEL_RFS01=9120 -V PORT_KERNEL_RMI01=9118 -V PORT_MESSAGE_DISPATCHER=9106 -V PORT_PA=9111 -V PORT_SAM=9126 -V PRE_WAS_EXISTING=true -V NEW_WAS=false -V EXISTING_WAS=true -V WAS_HOSTNAME=was61.us.ibm.com -V WAS_BASEDIR=/opt/IBM/WebSphere/AppSerer -V WAS_PROFILEHOME=/opt/IBM/WebSphere/AppSerer/V6/Base/profiles/default -V WAS_PROFILENAME=default -V WAS_ADMIN_CONSOLE_PORT=9060 -V WAS_CELL=hostCell01 -V WAS_NODE=hostNode01 -V WAS_SERVER=serer1 -V WAS_SOAP_PORT=8880 -V WAS_USER=root -V WAS_USER_PWD=rootpasd -V PRE_DB2_EXISTING=true -V NEW_DB=false -V EXISTING_DB=true -V EXISTING_DB2_LOCAL=true -V EXISTING_DB2_REMOTE=false -V DB2_INSTALL_LOCATION=/opt/IBM/db2/8.1 Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 187

208 -V DB2_JDBC=/opt/IBM/db2/8.1/jaa -V DB2_DAS_USER=db2admin -V DB2_DAS_PASSWORD=db2admin -V DB2_CREATE_DAS_USER=false -V DB2_DAS_GROUPNAME=dasadm1 -V DB2_DAS_HOMEDIR=/home/db2admin -V DB2_FENCE_USER=db2fenc1 -V DB2_FENCE_PWD=db2fenc1 -V DB2_CREATE_FENCE_USER=false -V DB2_FENCE_GROUPNAME=db2fgrp1 -V DB2_FENCE_HOMEDIR=/home/db2fenc1 -V DB2_INST_NAME=db2inst1 -V DB2_INST_USER=db2inst1 -V DB2_INST_PASSWORD=db2inst1 -V DB2_CREATE_INST_USER=false -V DB2_INST_GROUPNAME=dasadm1 -V DB2_SCHEMA_USER=db2admin -V DB2_SCHEMA_PASSWORD=db2admin -V DB2_INST_HOMEDIR=/home/db2inst1 -V DB2_SERVER=db.us.ibm.com -V DB2_INST_PORTNUMBER= V LAUNCH_MS=true Example of a modified response file template mirroring a three phase installation (Managing Serer only) Here is an example of a response file modified with suitable alues using the MS_Sample.opt file as a template. It corresponds to alues that would be specified if you were doing a three phase installation of the Managing Serer without the Visualization Engine. Tip: All WebSphere Application Serer options hae been remoed. -V disableosprereqchecking=true -V LICENSE_ACCEPT_BUTTON=true -V LICENSE_REJECT_BUTTON=false -V IS_SELECTED_INSTALLATION_TYPE=custom -W LogSetting.logLeel=ALL -W LogSetting.consoleOut=false -V LOG_DIR="/ar/ibm/tioli/common/CYN/logs" -P installlocation="/opt/ibm/itcam/websphere/ms" -P msfilesinstall.actie=true -P einstall.actie=false -P dbinstall.actie=false -V ITCAM_SYS_USERS=msadmin -V KERNEL_HOST01=kernalhost01.us.ibm.com -V PORT_ARCHIVE_AGENT1=9129 -V PORT_ARCHIVE_AGENT2=9130 -V PORT_KERNEL_CODEBASE01=9122 -V PORT_KERNEL_RFS01=9120 -V PORT_KERNEL_RMI01=9118 -V PORT_MESSAGE_DISPATCHER=9106 -V PORT_PA=9111 -V PORT_SAM=9126 -V PRE_WAS_EXISTING=true -V NEW_WAS=false -V EXISTING_WAS=true -V WAS_HOSTNAME=was61.us.ibm.com -V WAS_BASEDIR=/opt/IBM/WebSphere/AppSerer -V PRE_DB2_EXISTING=true -V NEW_DB=false -V EXISTING_DB=true -V EXISTING_DB2_LOCAL=false -V EXISTING_DB2_REMOTE=true -V DB2_INSTALL_LOCATION=/opt/IBM/db2/ ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

209 -V DB2_JDBC=/opt/IBM/db2/8.1/jaa -V DB2_INST_NAME=db2inst1 -V DB2_INST_USER=db2inst1 -V DB2_INST_PASSWORD=db2inst1 -V DB2_SCHEMA_USER=db2admin -V DB2_SCHEMA_PASSWORD=db2admin -V DB2_INST_HOMEDIR=/home/db2inst1 -V DB2_SERVER=db.us.ibm.com -V DB2_INST_PORTNUMBER= V LAUNCH_MS=true Configuration options list This section describes the syntax for specifying configuration options in a response file or on the command line and proides a list of the possible configuration options for the Managing Serer. The following table lists the options for configuration of a Managing Serer. Table 42. Configuration options for the Managing Serer on UNIX and Linux Feature or entity the option configures Option Description Installation parameters -V disableosprereqchecking=true false Indicates whether the operating-system-leel checking is turned on before the installation. Specifying true means that the program ignores the results of the operating-system-leel checking. Specifying false means that the operating-system-leel checking is turned on before the installation and the program exits if the operating system on the target serer has not met the minimum requirements for the installation. -V LICENSE_ACCEPT_BUTTON=true Specify true. false -V LICENSE_REJECT_BUTTON=true Specify false. false -V LOG_DIR=alue This specifies the writable directory to which the installation program writes log files. This is useful if the following default directory is not writable on your systems: /ar/ibm/tioli/common/cyn/logs Optional or required? Required Required Required Required if /ar/ibm/tioli/ common/cyn/logs is not writable. -V IS_SELECTED_INSTALLATION_TYPE = custom If you set this new option, the installation program uses it as real log path een if the default log path is writable. Specifies the type of installation. Since ersion the type of installation must be custom. Required Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 189

210 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -P installlocation=alue Specifies the path of the installation directory for the installation. If you do not specify this option, the installation program uses the default directory path: /opt/ibm/itcam/websphere/ms Note: 1. You cannot install the Managing Serer in a directory path that includes the following types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters 2. The directory that you specify must be empty. 3. If you specify a directory that does not exist, the installation program creates the directory. -P msfilesinstall.actie=true false Specifies whether to install the Managing Serer files. Indicate true or false. Indicate true if you are installing the Managing Serer on this serer. Indicate false if you are running the installer program to create database tables for an existing database enironment on this serer and the Managing Serer is being installed on a separate serer. -P einstall.actie=true false Specifies whether to install the ITCAM for Application Diagnostics Managing Serer with the installation. Indicate true or false. Indicate true if you are installing the Managing Serer on this serer. Indicate false if you are running the installer program to create database tables for an existing database enironment on this serer and the Managing Serer is being installed on a separate serer. Optional or required? Optional Required Required 190 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

211 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description Optional or required? -P dbinstall.actie=true false Required Specifies whether to install database tables with the installation. Indicate true or false. Indicate true if you are installing IBM DB2 or creating database tables for an existing database enironment on this serer. Indicate false if you are running the installer program for the purpose of installing the Managing Serer on this serer and you are creating database tables for an existing database enironment on a separate serer. Message generation Managing Serer settings Attention: Indicate false if you are upgrading the Managing Serer. If you indicate true, the data in the existing database tables are deleted. -V LAUNCH_MS=true false Specifies whether to start the Managing Serer after the installation. -W LogSetting.logLeel=alue See Options for monitoring installation messages on page W LogSetting.consoleOut=true false See Options for monitoring installation messages on page V ITCAM_SYS_USERS=alue Specifies the user used to log into the ITCAM for Application Diagnostics Managing Serer. The default is the installation user. -V KERNEL_HOST01=alue Specifies the fully qualified host name of the Managing Serer. -V PORT_ARCHIVE_AGENT1=alue Specifies the port that the Managing Serer uses to connect to Archie Agent 1. The default is V PORT_ARCHIVE_AGENT2=alue Specifies the port that the Managing Serer uses to connect to Archie Agent 2. The default is V PORT_KERNEL_CODEBASE01=alue Specifies the port that the Managing Serer uses to connect to Kernel Codebase 1. The default is V PORT_KERNEL_RFS01=alue Specifies the port that the Managing Serer uses to connect to Kernel RFS 1. The default is Required Optional Required Optional Required Optional Optional Optional Optional Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 191

212 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description Optional or required? -V PORT_KERNEL_RMI01=alue Specifies the port that the Managing Serer uses to connect to Kernel Remote Method Inocation (RMI) 1. The default is Optional IBM WebSphere Application Serer settings -V PORT_MESSAGE_DISPATCHER=alue Specifies the port that the Managing Serer uses to connect to the Message Dispatcher. The default is V PORT_PA=alue Specifies the port that the Managing Serer uses to connect to the Polling Agent. The default is V PORT_PS=alue Specifies the port that the Managing Serer uses to connect to Publish Serer 1. The default is V PORT_SAM=alue Specifies the port that the Managing Serer uses to connect to Structured Application Monitor 1. The default is V PRE_WAS_EXISTING=true false Specifies whether you hae a ersion of IBM WebSphere Application Serer installed on your serer. -V NEW_WAS=true false Specifies whether you are installing a new ersion of IBM WebSphere Application Serer instead of using an existing ersion of IBM WebSphere Application Serer for the Managing Serer installation. -V EXISTING_WAS=true false Specifies whether you are using an existing ersion of IBM WebSphere Application Serer for the Managing Serer installation. -V WAS_CDROMDIR=alue Specify the path of the WebSphere Application Serer silent installation response file used by IBM Installation Manager. Detailed information about how to create a WebSphere silent installation response file can be found in WebSphere documentation at: knowledgecenter/sseqtp_8.5.5/ Optional Optional Optional Optional Optional Required Required Required if -V NEW_WAS=true com.ibm.websphere.installation.base.doc/ae/cins_was85_base_install_win ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

213 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V WAS_ADMIN_CONSOLE_PORT =alue When you perform the installation of IBM WebSphere Application Serer that comes with ITCAM for Application Diagnostics, you use this to specify the port used by the IBM WebSphere Application Serer administratie console. The default is Do not use the default if port 9060 is assigned to another serice. -V WAS_HOSTNAME=alue Specifies the fully qualified host name or IP address of the serer where IBM WebSphere Application Serer is installed. -V WAS_BASEDIR=alue Specifies the path of the installation directory for IBM WebSphere Application Serer 7.0 or the directory path of the profile of an existing ersion of IBM WebSphere Application Serer. For example, /opt/ibm/itcam/websphere /MS/WAS61 Note: You cannot install or choose a IBM WebSphere Application Serer instance in a directory path (including profile, cell, node, and serer names) that includes the following types of characters: Traditional Chinese Simplified Chinese Japanese Korean Spanish special characters German special characters Portuguese Brazilian special characters French special characters Italian special characters -V WAS_PROFILEHOME=alue Specifies the path to the profile for the instance of IBM WebSphere Application Serer being used by the Managing Serer. For example, /opt/ibm/websphere/appserer/v6/ Base/profiles/ default -V WAS_PROFILENAME=alue Specifies the name of the profile for the instance of IBM WebSphere Application Serer being used by the Managing Serer. For example, default. Optional or required? Optional Required if -V EXISTING_WAS=true Optional Required Required if -V EXISTING_WAS=true Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 193

214 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V WAS_CELL=alue When you are using an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of a cell in a IBM WebSphere Application Serer distributed network. A cell is a configuration concept that enables IBM WebSphere Application Serer administrators to logically associate nodes with each another. You can use any of the existing cell names that are defined in the cell directory. For example, hostcell01. -V WAS_NODE=alue When you are using an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of a computer that runs an application serer and an administratie serer. Normally, the default node name includes the short host name. For example, on a computer named IBMMACHINE, the node name could be IBMMACHINENode01. -V WAS_SERVER=alue When you are using an existing installation of IBM WebSphere Application Serer software, you use this flag to specify the name of the IBM WebSphere Application Serer where the Managing Serer runs. In a simple installation this serer might be named serer1. -V WAS_USER=alue Specifies the name of the user that will run IBM WebSphere Application Serer. For an existing IBM WebSphere Application Serer, if IBM WebSphere Global Security is enabled, the user you specify must hae the WebSphere Administrator Role; if IBM WebSphere Global Security is not enabled, the user you specify must hae membership in the Administrators group. This user must not be an LDAP user. -V WAS_USER_PWD=alue Specifies the password of the user that runs IBM WebSphere Application Serer. Optional or required? Required if -V EXISTING_WAS=true Required if -V EXISTING_WAS=true Required if -V EXISTING_WAS=true Required Required 194 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

215 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V WAS_SOAP_PORT==alue Specifies the connector port that the IBM WebSphere Application Serer uses to send commands using the Simple Object Access Protocol (SOAP). The default is General database settings IBM DB2 settings -V TEPS_BASED_INSTALL = true false Specifies whether you are installing the MS based on ITM TEPS. Note: Managing Serer Visualization Engine could be installed on ITM TEPS embeded WebSphere Application Serer(eWAS). This is not recommended for production use. -V ITM_HOME = alue Specifies the ITM home directory if you choose to install MS based on ITM TEPS. -V PRE_DB2_EXISTING=true false Specifies whether you hae a ersion of IBM DB2 installed on your serer. -V NEW_DB=true false Specifies whether you are installing a new ersion of IBM DB2 instead of using an existing database for the Managing Serer installation. -V EXISTING_DB=true false Specifies whether you are using an existing database for the Managing Serer installation. -V EXISTING_DB2_LOCAL=true false -V EXISTING_DB2_REMOTE=true false -V EXISTING_ORACLE_LOCAL=true false -V EXISTING_ORACLE_REMOTE=true false Specifies whether the existing ersion of IBM DB2 you are using for the Managing Serer installation is installed on the local serer. Specifies whether the existing ersion of IBM DB2 you are using for the Managing Serer installation is installed on a remote serer. Specifies whether the existing ersion of Oracle database you are using for the Managing Serer installation is installed on the local serer. Specifies whether the existing ersion of Oracle database you are using for the Managing Serer installation is installed on a remote serer. -V DB2_IMAGE_LOCATION=alue Specifies the path of the installation image location for IBM DB Optional or required? Required Required Required if -V TEPS_BASED_ INSTALL=true Required Required Required Required if -V EXISTING_DB=true Required if -V EXISTING_DB=true Required if -V EXISTING_DB=true Required if -V EXISTING_DB=true Required if -V NEW_DB=true Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 195

216 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V DB2_INSTALL_LOCATION=alue Specifies the full path to where you want IBM DB2 installed. The default is one of the following: Linux and UNIX (non-aix): /opt/ibm/db2/v10.1 AIX, HP-UX or Solaris: opt/ibm/db2/v10.1 -V DB2_DAS_USER=alue Specifies the name of the DB2 Administration Serer user account. -V DB2_DAS_PASSWORD=alue Specifies the password of the DB2 Administration Serer user account. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_DAS_USER=true false If the DB2 Administration Serer user does not exist on the target serer, specify true; otherwise, specify false. -V DB2_DAS_GROUPNAME=alue Specifies the group name of the DB2 Administration Serer user account. Note: The group must already exist on the system. It is not created during the installation. -V DB2_DAS_HOMEDIR=alue Specifies the home directory of the DB2 Administration Serer user account. -V DB2_FENCE_USER=alue Specifies the user name of the DB2 Fenced user account. -V DB2_FENCE_PWD=alue Specifies the password of the DB2 Fenced user account. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_FENCE_USER=true false If the DB2 Fenced user does not exist on the target serer, specify true; otherwise, specify false. -V DB2_FENCE_GROUPNAME=alue Specifies the group name of the DB2 Fenced user account. Note: The group must already exist on the system. It is not created during the installation. -V DB2_FENCE_HOMEDIR=alue Specifies the home directory of the DB2 Fenced user account. -V DB2_INST_NAME=alue Specifies the name of the IBM DB2 instance. Optional or required? Optional Optional Required if a alue was entered for -V DB2_DAS_USER Required if you are installing or using an IBM DB2 database Required if a alue was entered for -V DB2_DAS_USER Required if a alue was entered for -V DB2_DAS_USER Optional Required if a alue was entered for -V DB2_FENCE_USER Required Required if a alue was entered for -V DB2_FENCE_USER Required if a alue was entered for -V DB2_FENCE_USER Optional 196 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

217 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V DB2_INST_USER=alue Specifies the name of the DB2 Instance user. Oracle settings -V DB2_INST_PASSWORD=alue Specifies the password of the DB2 Instance user. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_INST_USER=true false If the DB2 Instance user does not exist on the target serer, specify true; otherwise, specify false. -V DB2_INST_GROUPNAME=alue Specifies the group name of the DB2 Instance user. Note: The group must already exist on the system. It is not created during the installation. -V DB2_INST_HOMEDIR=alue Specifies the home directory of the DB2 Instance user. -V DB2_JDBC=alue Specifies the full path to the required Jaa DataBase Connectiity (JDBC) files for IBM DB2. This must be a directory containing IBM DB2 jdbc drier files, such as db2jcc.jar. -V DB2_SERVER=alue Specifies the fully qualified host name of the IBM DB2 serer. -V DB2_INST_PORTNUMBER=alue Specifies the port used by IBM DB2. The default port is for IBM DB2. -V DB2_SCHEMA_USER=alue Specifies the schema user name. This user owns and can create the database tables for ITCAM for Application Diagnostics. -V DB2_SCHEMA_PASSWORD=alue Specifies the password of the schema user that you specify. Note: The password created for this user during a Typical installation is itcam610. -V DB2_CREATE_SCHEMA_USER=true false If the DB2 Schema user does not exist on the target serer, specify true; otherwise, specify false. -V ORACLE_SID=alue Specifies the Oracle database system identifier number. This is a unique identifier of the Oracle database instance, defined during the Oracle database installation. The oracle database user must hae bash as system shell. Optional or required? Required if you are using an existing IBM DB2 database Required if a alue was entered for -V DB2_INST_USER Required if you are installing or using an IBM DB2 database Required if a alue was entered for -V DB2_INST_USER Required if a alue was entered for -V DB2_INST_USER Required if you are using an existing IBM DB2 database Required if you are using an existing IBM DB2 database Optional Required if you are using an existing IBM DB2 database Required if a alue was entered for -V DB2_SCHEMA_ USER Required if you are using an existing IBM DB2 database Required if you are using an Oracle database Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 197

218 Table 42. Configuration options for the Managing Serer on UNIX and Linux (continued) Feature or entity the option configures Option Description -V ORACLE_SERVER=alue Specifies the fully qualified host name or the IP address of the host computer for the Oracle database enironment, which contains table space for the management repository. For example, serername.it.company.com Optional or required? Required if you are using an Oracle database shows typical syntax for a fully qualified host name. -V ORACLE_SCHEMA_USER=alue Specifies the schema user name. This user owns and can create the database tables for ITCAM for Application Diagnostics. -V ORACLE_SCHEMA_PASSWORD= alue Specifies the password for the schema user in the Oracle database enironment. -V ORACLE_PORTNUMBER=alue Specifies the port number for the Oracle database. The default port is V ORACLE_DBA_USER=alue Specifies the user name of the Oracle database administrator. -V ORACLE_DBA_PASSWORD=alue Specifies the password of the Oracle database administrator. -V ORACLE_JDBC=alue Specifies the full path to the required Jaa DataBase Connectiity (JDBC) files for Oracle. This must be a directory containing Oracle database jdbc drier files, such as ojdbc14.jar or classes12.jar. -V ORACLE_HOME=alue Specifies the full path to the Oracle database home directory. -V ORACLE_SQLPLUS_USER=alue Specifies the user name of an existing Oracle SQLPlus user. This user must hae priileges to create tables in Oracle. Required if you are using an Oracle database Required if you are using an Oracle database Optional Required if you are using an existing local Oracle database Required if a alue was entered for -V ORACLE_DBA_ USER Required if you are using an Oracle database Required if you are using an existing local Oracle database Required if you are using an existing local Oracle database Syntax of configuration options This section describes the syntax for configuration options for the Managing Serer silent installation. You can use configuration options in the command line or in a response file. The three flags for configurations options are -P,-V and -W. 198 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

219 The configuration options accept the following parameters: -P entity_id.dataitem="alue" -V entity_id.dataitem="alue" -W entity_id.dataitem="alue" The entity_id identifies an entity inoled in an installation or configuration, such as the log settings for the installation or configuration. The dataitem is the name of an attribute, such as the installation path or the communications port. The alue specifies the alue for an attribute of an entity inoled in an installation or configuration, such as a specific path like /opt/ibm/itcam/websphere/ms. Options for monitoring installation messages The following two configuration options control the display or logging of installation messages. These options help you to monitor and debug all phases of an installation. -W LogSetting.consoleOut=true false specifies whether to display messages issued by installation or upgrade program on the console. If you use this option with a natie launcher, it must be used in combination with the -is:jaaconsole option. -W LogSetting.logLeel=alue specifies the leel of tracing for the installation log files. The amount of tracing for a specific leel includes the messages for that leel and all messages at a higher seerity. For example, if you choose the WARNING trace leel, the following messages are logged: WARNING, ERROR, and FATAL. During the installation maximum logging is turned on by default. Access the installation log files in the following default path: /ar/ibm/tioli/ common/cyn/logs. Table 43. Trace leel settings for installation log files Option string Description -W LogSetting.logLeel=FATAL Log fatal messages. A fatal message reports an error from which the program cannot recoer. A fatal message is the most seere message. -W LogSetting.logLeel=ERROR Log error messages. An error message reports a serious failure. An error message is less seere than a fatal message. -W LogSetting.logLeel=WARNING Log warning messages. A warning message reports that an abnormal condition has occurred. The condition might or might not require the user to take action. -W LogSetting.logLeel=INFO Log information messages. An information message indicates a condition that is worth noting but does not require the user to take action. -W LogSetting.logLeel=DEBUG_MIN Log debug messages that proide minimal detail. DEBUG_MIN is appropriate for a software trace that is always running. It proides some information about the program state with only minimal impact to performance. DEBUG_MIN is the default setting for installation log files. -W LogSetting.logLeel=DEBUG_MID Log debug messages that proide a medium amount of detail. The DEBUG_MID setting produces a leel of detail between DEBUG_MIN and DEBUG_MAX. Chapter 14. Silent installation for the Managing Serer on UNIX and Linux 199

220 Table 43. Trace leel settings for installation log files (continued) Option string Description -W LogSetting.logLeel=DEBUG_MAX Log debug messages that proide the most detail about program execution. Program performance is usually not an issue when debugging in this mode. -W LogSetting.logLeel=ALL Enable all message logging. Retrieing installation options from the IBM WebSphere serer configuration files You do not hae to proide all the installation options during the Managing Serer (MS) split installation procedure. Some of them can be retrieed from the IBM WebSphere serer configuration files. For more information, see the Retrieing installation options from the IBM WebSphere serer configuration files section in the Silent installation for the Managing Serer on Windows chapter. 200 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

221 Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems Unpacking the update Installing updates You can use the update installer to upgrade the Managing Serer from Version 6.1 (any fix pack) to Version , and to update the Managing Serer from a preious maintenance leel of Version 7.1 to Version The update installer proides the following functions: A silent command-line update installer. Installation and remoal of indiidual or multiple updates (new ersions, fix packs, and interim fixes) for the Managing Serer. (Important: while you can remoe fix packs, you cannot use the Update Installer to downgrade from Version 7.x to Version 6.x) Logging, tracking, and prerequisites handling. Important: The Managing Serer Version connects and operate with Data Collectors of the current ersion and all preious ersions starting from ITCAM for WebSphere Version 6.1 and ITCAM for J2EE Version 6.1. The Update Installer is distributed in an update package, which is a TAR file. You can use this package to update from any release of Version 7.0.x or 6.1.x ersion of the Managing Serer. Create a temporary directory, put the update package there and extract it. The update package includes the updates directory that contains the file with the *.update extension. For example: tar xf TIV-ITCAMfAD_SVR-FP0001.tar silentupdate.sh updates/ ITCAM_V71_UpdateInstaller.htm ITCAM_V71_UpdateInstaller.pdf alien.jar configutil.jar silentupdate.bat silentupdate.properties update.jar updates/7.1.0-tiv-itcamfad_svr-fp0001.update TIV-ITCAMfAD_SVR-FP0001.README You can use the update installer to install new ersions, fix packs and interim fixes for the Managing Serer. You need to run the Update Installer on eery host where any components of the Managing Serer are running. In a split Managing Serer installation, run it on both hosts. If the Visualization Engine is running on a separate host, run the Update Installer on the Visualization Engine host and the backend component hosts. If the Database Management Serer (DB2 or Oracle) is on a separate host, you do not need to run the Update Installer on it. Copyright IBM Corp. 2006,

222 When the Managing Serer is running on more than one host, you hae to update the database only once. To do this, in the response file, set updatedb=true on one host and updatedb=false on others. Preparing the Enironment Before running the update installer, login as root or owner of the product directory. If the Visualization Engine is installed on the host, the user for the update installer must hae write permission for the WebSphere Application Serer directory that is used by the Visualization Engine. The update installer requires the Runtime Enironment for the Jaa platform ersion 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment that is used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home/bin/seten.sh file. Updating the Response File The update installer is a non-interactie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home) (Optiona)l: If the *.update files are not in the default./updates directory, then set the updates.location property to the directory that contains the *.update files. (If you hae unpacked the package and not moed the files, do not set this property). If the Visualization Engine was not installed to the Managing Serer host to be updated, set the updateve property to false. Otherwise, uncomment and set the updateve.washome property to the WAS_PROFILE_HOME of the Visualization Engine application serer. In a split Managing Serer installation, when seeral Managing Serer hosts that use the same database, this database must be updated only once. It is updated with the default property alues, so no change is required on the first host to update. On the second and subsequent hosts to update, set the updatedb property to false. Complete the following steps if the Visualization Engine is installed on the host to be updated: If the Visualization Engine is installed on a WebSphere Network Deployment, use an SOAP connection to install the update. To do this, uncomment and set the following properties in the silentupdate.properties file: updateve.was.soap.host=<host> updateve.was.soap.port=<port> Important: WebSphere Deployment Manager and Node Agent must be in running state. If WebSphere Security is enabled, uncomment and set the following properties: updateve.was.user=<was USER> updateve.was.password=<was PASSWORD> 202 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

223 To retriee user name and password from *.client.props file set the following property: connection.useclientprops=true For an SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Important: Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. Preparing for the Installation To reduce the Managing Serer downtime, you can use the update installer to prepares the installation while the product is running. This step is optional. In order to prepare installation, change to the directory where the update package was unpacked and run the following command:./silentupdate.sh -prepareinstall If your response file is named differently from the default silentupdate.properties, specify it as a parameter: Linux and UNIX systems:./silentupdate.sh -prepareinstall my.properties A typical output of the -prepareinstall command is as follows: #./silentupdate.sh -prepareinstall Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: prepare install Finished successfully Installing the update To reduce Managing Serer downtime, you can run the -prepareinstall command before installing the update, see Preparing for the Installation. Before installing the update, stop the Managing Serer. Attention: If the Managing Serer components are running on seeral hosts, stop the Managing Serer on all hosts, then perform the installation on all hosts. Then, change to the directory where the update package was unpacked and run the following command:./silentupdate.sh -install If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -install my.properties Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems 203

224 A typical output of the -install command is as follows: #./silentupdate.sh -install Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: install Finished successfully After installation, reiew the configuration files. The Update Installer merges any manual configuration changes (including split installation) that were made in the preious ersion. For details, see Details of configuration file merging on page 209. Then, start the Managing Serer. Cleaning Prepared Installation If you hae completed the installation, you do not hae to clean up the preparation. Do not complete this step. If you decide to not install the update after you already run -prepareinstall then you can clean results of the -prepareinstall command. In order to do that change to the directory where the update installer scripts are stored and run the following command:./silentupdate.sh cleanprepared If your response file is named differently from the default silentupdate.properties, then specify it as a parameter:./silentupdate.sh -cleanprepared my.properties A typical output of the -cleanprepared command is: #./silentupdate.sh -cleanprepared Update installer ersion 7.1.0, build /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: cancel prepared Finished successfully Rolling Back a Failed Installation If the -install command fails and the automatic rollback also fails, you cannot install or uninstall any updates until the rollback is completed successfully. In order to complete the rollback, do the following: Reiew the update installer log and resole the cause of the rollback failure. Change to the directory where the update installer scripts are stored and run the following command:./silentupdate.sh rollback If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -rollback my.properties A typical output of the -rollback command is: #./silentupdate.sh -rollback Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: rollback Finished successfully 204 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

225 Uninstalling updates You can use the update installer to uninstall fix packs and interim fixes. The Managing Serer is rolled back to the state before the update. You need to run the Update Installer on eery host where any components of the Managing Serer are running. In a split Managing Serer installation, run it on both hosts. If the Visualization Engine is running on a separate host, run the Update Installer on the Visualization Engine host and the backend component hosts. If the Database Management Serer (DB2 or Oracle) is on a separate host, you do not need to run the Update Installer on it. When the Managing Serer is running on more than one host, you need to roll back the database only once. To do this, in the response file, set updatedb=true on one host and updatedb=false on others. Important: The Update Installer does not support rolling back from Version 7.x to Version 6.x. Preparing the Enironment Before running the update installer, login as root or owner of the product directory. If the Visualization Engine is installed on the host, this user must hae write permission for the WebSphere Application Serer directory used by the Visualization Engine. The update installer requires the Runtime Enironment for the Jaa platform Version 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment that is used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home/bin/seten.sh file. Updating the Response File The update installer is a non-interactie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home). Optionally, if the *.update files are not in default./updates directory, then set the updates.location property to the directory that contains the *.update files. (If you hae unpacked the package and not moed the files, do not set this property). If the Visualization Engine was not installed to the Managing Serer host to be updated, set the updateve property to false. Otherwise uncomment and set the updateve.washome property to the WAS_PROFILE_HOME of the Visualization Engine application serer. In a split Managing Serer installation, when seeral Managing Serer hosts that use the same database, this database must be updated only once. It is updated with the default property alues, so no change is needed on the first host to update. On the second and subsequent hosts to update, set the updatedb property to false. Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems 205

226 Set the uninstall.updates property with the one of possible alues: all uninstall all updates last uninstall the updates installed by the last -install command <comma separated list of updates> -- uninstall the specified updates. The updates are specified by their identifiers as displayed by the -listinstalledupdates command. (Example: , ) Perform the following steps if the Visualization Engine is installed on the host to be updated: If the Visualization Engine is installed on a WebSphere Network Deployment, use SOAP connection to install the update. For that uncomment and set the following properties in the silentupdate.properties file: updateve.was.soap.host=<host> updateve.was.soap.port=<port> Important: WebSphere Deployment Manager and Node Agent must be in running state. If WebSphere Security is enabled, uncomment and set the following properties: updateve.was.user=<was USER> updateve.was.password=<was PASSWORD> To retriee user name and password from *.client.props file set the following property: connection.useclientprops=true For a SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. For a SOAP connection, the user name and password are retrieed from the soap.client.props file. (RMI connections are not supported by the update installer). Important: Do not set connection.useclientprops=true if user name and password are not specified in the soap.client.props file, it can lead to a hang of the update installer. If you specify user and password information in the silentupdate.properties file and set connection.useclientprops=true, the silentupdate.properties file information oerrides the information in the soap.client.props file. Preparing for uninstallation To reduce the Managing Serer downtime, you can use the update installer to prepare uninstallation while the product is running. This step is optional. In order to prepare uninstallation, change to the directory where the update package was unpacked and run the following command:./silentupdate.sh -prepareuninstall 206 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

227 If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -prepareuninstall my.properties A typical output of the -prepareuninstall command is: #./silentupdate.sh -prepareuninstall Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: prepare uninstall Finished successfully Uninstalling the update To reduce Managing Serer downtime, you can run the -prepareunnstall command before installing the update, see Preparing for uninstallation on page 206. Before installing the update, stop the Managing Serer. Important: if the Managing Serer components are running on seeral hosts, stop the Managing Serer on all hosts, then perform the uninstallation on all hosts. Then, change to the directory where the update package was unpacked and run the following command:./silentupdate.sh -uninstall If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -uninstall my.properties A typical output of the -uninstall command is: #./silentupdate.sh -uninstall Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: uninstall Finished successfully After uninstallation, reiew the configuration files. Changes that were preiously made to these files can be lost. Then, start the Managing Serer. Cleaning prepared uninstallation If you hae performed the uninstallation, you do not need to clean up the preparation. Do not complete this step. If you decide to not uninstall after you already run -prepareuninstall then you can clean results of the -prepareuninstall' command. In order to do that change to the directory where the update installer scripts are stored and run the following command:./silentupdate.sh cleanprepared If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -cleanprepared my.properties Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems 207

228 A typical output of the -cleanprepared command is: #./silentupdate.sh -cleanprepared Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: cancel prepared Finished successfully Rolling back a failed uninstallation Displaying Installed updates If the -uninstall command fails and the automatic rollback also fails, you cannot install or uninstall any updates until the rollback is completed successfully. In order to complete the rollback, do the following: Reiew the update installer log and resole the cause of the rollback failure. Change to the directory where the update installer scripts are stored and run the following command:./silentupdate.sh rollback If your response file is named differently then the default silentupdate.properties then specify it as a parameter:./silentupdate.sh -rollback my.properties A typical output of the -rollback command is: #./silentupdate.sh -rollback Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: rollback Finished successfully You can use the update installer to display a list of the installed fix packs and interim fixes. Preparing the Enironment Before running the update installer, login as root or owner of the product directory. Then update the enironment as described in this section. The update installer requires the Runtime Enironment for the Jaa platform ersion 1.4 or higher. Define the JAVA_HOME enironment ariable to point to the Runtime Enironment used by the Managing Serer. If the Visualization Engine is installed on the host, this is the jaa directory within the WebSphere Application Serer directory. Otherwise, this is the alue of JAVA_HOME set in the MS_home/bin/seten.sh file. Updating the Response File The update installer is a noninteractie silent installer that works based on the response file. The default name of the response file is silentupdate.properties; it is located in the update installer directory. Update the response file as follows: Set the product.location property to the correct Managing Serer installation directory (MS_home) 208 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

229 Displaying Installed updates To display a list of the installed fix packs and interim fixes change to the directory where the update package was unpacked and run the following command:./silentupdate.sh -displayinstalledupdates If your response file is named differently from the default silentupdate.properties, specify it as a parameter:./silentupdate.sh -displayinstalledupdates my.properties A typical output of the -displayinstalledupdates command is: #./silentupdate.sh -displayinstalledupdates Update installer ersion 7.1.0, build Logging details into /opt/ibm/itcam/websphere/ms/logs/update/update_ log Action: display installed updates Updates installed 4/20/10 8:52 PM Fix Pack 1 Finished successfully Details of configuration file merging When the Managing Serer is updated from Version 6.1 to 7.1 (any maintenance leel), configuration files are merged to ensure that preious manual configuration changes are presered as fully as possible. This is not performed when a maintenance leel is uninstalled. Also, when updating from a 7.1 maintenance leel to another 7.1 maintenance leel, the configuration files are unchanged. When updating from Version 6.1, the update installer performs the following changes: First, new properties files are created for all components for which were present in older configuration: kl*.properties klwd*.properties ps*.properties aa*.properties sam*.properties log-kl*.properties log-ps*.properties log-aa*.properties log-sam*.properties - Next, properties are migrated from the old configuration files (in the old MS_home/etc directory) into new ones: aa*.properties, excluding ENABLE_DATATRIMMER, MEMORY_DATA_DELETE_TIME, GC_DATA_DELETE_TIME, SR_OVERVIEW_DATA_DELETE_TIME, IMS_THREAD_DATA_DELETE_TIME, WEBSERVER_CHART_DATA_DELETE_TIME aa_deletedata.properties ccmdb-sim.properties cyn-cclog.properties Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems 209

230 cynlogging.properties excluding CYN.msg.listenerNames, CYN.trc.listenerNames, CYN.trc.leel kl*.properties klwd*.properties excluding kernel.rfs.host=localhost ms.properties pa.properties ps*.properties excluding e.host, e.port sam1.properties e.properties excluding e.framework.pdf log-aa*.properties excluding *.publishserer.*, CYN.handler.snap.conertExceptions log-kl*.properties excluding CYN.handler.snap.conertExceptions log-md.properties excluding CYN.handler.snap.conertExceptions log-ps*.properties excluding CYN.trc.leel, CYN.handler.snap.conertExceptions log-sam*.properties excluding CYN.handler.snap.conertExceptions log-ws.properties xcluding CYN.handler.snap.conertExceptions Log.properties dal/dal.properties (renamed properties are migrated correctly) Scripts (*.sh) in the MS_home directory are oerwritten, except am-start.sh, am-stop.sh, am-status.sh, am-status_codes.sh, and am-forcestop.sh A command is appended to am-start.sh: echo "ITCAM MS started" A command is appended to am-stop.sh: echo "ITCAM MS stopped" The following properties are migrated from the old seten.sh into the new ersion: KERNEL_HOST* PORT_KERNEL_CODEBASE* PORT_KERNEL_RFS* PORT_KERNEL_RMI* PORT_ARCHIVE_AGENT* PORT_ARCHIVE_AGENT* PORT_MESSAGE_DISPATCHER PORT_PS* PORT_PA* PORT_SAM* KERNEL_INSTANCE PS_INSTANCE AA_INSTANCE HEAP_MIN_SIZE_* HEAP_MAX_SIZE_* LOG_COMMON_DIR CERT_PATH KEYSTR_LOC KEYSTR_PASS KEYSTR_KEYPASS NODE_USERID 210 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

231 NODE_IP USE_SSL The update installer does not oerwrite the dal/temaqueryschema.xml file, so all settings in this file remain actie for the new ersion. Chapter 15. Upgrading and updating the Managing Serer on Linux and UNIX systems 211

232 212 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

233 Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux You can customize your configuration of the Managing Serer. If they apply, complete the procedures in each of the following sections. Creating additional instances of Managing Serer components By default, the Managing Serer has the following runtime instances. Each instance has a properties file. Table 44. Default Managing Serer runtime instances Component ID Component instance Properties file name kl1 The first instance of the Kernel kl1.properties ps1 The first instance of the Publish Serer ps1.properties ps2 The second instance of the Publish Serer ps2.properties aa1 The first instance of the Archie Agent aa1.properties aa2 The second instance of the Archie Agent aa2.properties md The one instance of the Message Dispatcher md.properties pa The one instance of the Polling Agent pa.properties sam1 The one instance of the Global Publish Serer sam1.properties You can create additional instances of the Kernel, Publish Serer, or Archie Agent. For the Publish Serer and Archie Agent, each instance must hae its own properties file. The simplest way to create another instance of one of these components is to run the product-proided scripts. They make copies of existing properties files and modify the component IDs and the port numbers to unique alues. The scripts also add alues to particular files that require the parameters to be set in order for the additional instances to run properly, for example, to the start and stop scripts. You cannot create additional instances for any of the other components listed in Table 44. Adding an additional Kernel You can add a second kernel instance. More than two kernels are not supported. Complete the following procedure to add an additional Kernel to the Managing Serer configuration: 1. Decide which ports to use for the additional Kernel. Each Kernel requires three ports for operation. Edit the MS_home/bin/seten.sh file and add the following properties: KERNEL_HOST${KERNEL_COUNT}=hostname. For example, KERNEL_HOST02=de-lnx-mycompany PORT_KERNEL_CODEBASE${KERNEL_COUNT}=port_number. For example, PORT_KERNEL_CODEBASE02=9123 Copyright IBM Corp. 2006,

234 PORT_KERNEL_RFS${KERNEL_COUNT}=port_number. For example, PORT_KERNEL_RFS02=9121 PORT_KERNEL_RMI{KERNEL_COUNT}=port_number. For example, PORT_KERNEL_RMI= Edit the MS_home/etc/ms.properties file and set the kernel.hosts property as follows: kernel.hosts=kernel_host01:port_kernel_codebase01:port_kernel_rfs01: PORT_KERNEL_RMI01,KERNEL_HOST02:PORT_KERNEL_CODEBASE02: PORT_KERNEL_RFS02:PORT_KERNEL_RMI02 For example, de-lnx-mycompany.usca.abc.com:8122:8120:8118, de-lnx-mycompany.usca.abc.com:8123:8121: Increase the heap size if needed. See Tuning recommendations for large-scale enironments on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page In MS_home/bin, edit the am-start.sh script according to the number of kernels there are. If there are two kernels, then the am-start.sh script must hae the following commands: amctl.sh wd1 start amctl.sh wd2 start 6. In MS_home/bin, edit the am-stop.sh script according to the number of kernels there are. If there are two kernels, then the am-start.sh script must hae the following commands: amctl.sh wd1 stop amctl.sh wd2 stop Also edit the am-status.sh script in the same directory according to the number of kernels. 7. If you are finished adding additional components, start the Managing Serer. See Starting the Managing Serer on page For the Data Collectors connecting to this Managing Serer, restart the instances of the application serers that are being monitored by the Data Collectors. See Restarting the application serer on page 274. Adding additional Publish Serers Complete the following procedure to add an additional Publish Serer to the Managing Serer configuration: 1. From a command line, in MS_home/bin, run the following command:./add-ps.sh port_number The port_number is the port number for this added instance of the Publish Serer. If a firewall exists, the new port needs to be opened in the firewall. If you accepted the default port numbers for the Managing Serer components during the installation, see Table 26 on page 134 for a list of the port numbers that are already in use. For details on adjusting ports being blocked by your firewall, see Adjusting for ports being blocked by your firewall or being used by other applications on page Increase the heap size if required. See Tuning recommendations for large-scale enironments on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

235 4. It is recommended that you stop Publish Serer for load balancing, but it is optional if you want to aoid downtime. 5. If you hae finished adding components, start Starting the Managing Serer on page 265. Adding additional Archie Agents Complete the following procedure to add additional Archie Agents to the Managing Serer configuration: 1. From a command line, in MS_home/bin, run the following command:./add-aa.sh port_number The port_number is the port number for this added instance of the Archie Agent. If you accepted the default port numbers for the Managing Serer components during the installation, see Table 26 on page 134 for a list of the port numbers that are already in use. 2. Increase the heap size if required. See Tuning recommendations for large-scale enironments on page If it is not already stopped, stop the Managing Serer. See Stopping the Managing Serer on page If you are finished adding components, start the Managing Serer. See Starting the Managing Serer on page 265. Split Managing Serer installation in Unix The Managing Serer consists of a number of components. See Oeriew of the Managing Serer on page 4 for a description of the Managing Serer components. In a standard installation, all of these components run on the same serer host. You can make more resources aailable for the Managing Serer by installing its components on two serer hosts (this is called a split installation). The serers must hae the same configuration. A split Managing Serer configuration uses increased processing power and memory across multiple serers, increasing performance of the Managing Serer. For optimal performance in a large deployment (oer 100 Data Collectors), consider using a split installation. Important: You can also install the Visualization Engine on a separate host. To do this, use the three step silent installation process; see UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems on page 179. The following components of the Managing Serer can hae multiple instances, running on the same serer or across two different serers: Kernel (and Watchdog). Adding additional Kernels, running across two or more serers, helps to aoid a Managing Serer failure if one serer fails. Publish Serer. Adding additional Publish Serers improes load handling and fault tolerance. In a network spanning multiple locations, you can set up at least one Kernel in each location and configure the Kernels to connect Data Collectors, when possible, to the local Publish Serer. Doing this reduces network traffic (see!!!). Archie Agent. Adding additional Archie Agents expands archiing capabilities. The following components must exist as one instance only, running on one serer (you do not hae to run them all on the same serer): Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 215

236 Visualization Engine (you can install it on a separate serer, see UPDATED: Performing a three phase Managing Serer installation with three logins on Linux and UNIX systems on page 179) Message Dispatcher Global Publish Serer The Message Dispatcher component does not require significant resources; all other components can use processor power and memory heaily. Complete the following procedure to perform a split Managing Serer installation: 1. In adance, prepare a list of Managing Serer component instances run on eery serer. 2. Install the Managing Serer using custom or silent installation on one serer. (This serer is called the first serer; the other serer used for the split installation is called the second serer). 3. On the first serer, create all the additional component instances that are to run on eery serer. For example, if you are planning to run the Publish Serer on three serers, two instances on each, create six instances of the Publish Serer. See Creating additional instances of Managing Serer components on page Configure the Managing Serer on the first serer; complete any necessary tuning, including port settings. Ensure that the configuration is working. 5. Copy the jaa directory from AppSerer_home on the first serer to any location on the second serer. 6. Create a user for the Managing Serer on the second serer. The user name must be the same as the Managing Serer user on the first serer. 7. Copy the Managing Serer installation directory (MS_home) from the first serer to the same location on the second serer. 8. On the second serer, in MS_home/bin/seten.sh, adjust the setting for JAVA_HOME to the location of the jaa directory created in Step If there is no database client installed on the second serer: a. Copy the JDBC directory from the database serer (if you used embedded DB2 installation the database serer is the first serer) to a location on the second serer. b. In the MS_home/bin/seten.sh file, for the JDBC_DRIVER_JAR property, specify the path where you added the JDBC directory in Step 9a. 10. On the first and the second serers, in MS_home/bin/seten.sh, configure the am_socket_exportip and am_socket_bindip properties to point to the host name or IP address of the serer host where the file is located. 11. On the first and the second serers, in MS_home/etc/ms.properties, configure the kernel.hosts property to contain information about both kernels. For example: kernel.hosts=serer1.company.com:9122:9120:9118, serer2.company.com:9122:9120:9118 Note: Keep the port definitions the same on both serers. If the second Managing Serer is behind a different firewall, the port must be opened in the firewall. For details on adjusting ports being blocked by your firewall, see Adjusting for ports that are being blocked by your firewall or are being used by other applications on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

237 12. On the first and the second serers, in MS_home\etc\e.properties, adjust the settings for kernel.codebase and kernel.rfs.address to point to the host name or IP address of the serer host where the file is located. 13. On the first and the second serers, modify the startup script,ms_home\bin\amstart.sh to indicate which components must be started on the serer. You can choose which components run on each serer, but both serers cannot start (or stop) the same component ID. Important: a. You must run the Message Dispatcher on the first serer. b. See Table Table 44 on page 213 for a listing of the component IDs. c. See Oeriew of the Managing Serer on page 4 for a description of the Managing Serer components. d. Only the Watchdog instance (wd1 or wd2) is mentioned in the start/stop/status scripts, because the Watchdog controls the starting, stopping, and status of the kernel. Here are examples of lines from two am-start.sh scripts that complement each other: From first Managing Serer: ${CYANEA_HOME}/bin/amctl.sh wd1 start #${CYANEA_HOME}/bin/amctl.sh wd2 start ${CYANEA_HOME}/bin/amctl.sh aa1 start #${CYANEA_HOME}/bin/amctl.sh aa2 start ${CYANEA_HOME}/bin/amctl.sh ps1 start #${CYANEA_HOME}/bin/amctl.sh ps2 start ${CYANEA_HOME}/bin/amctl.sh md start ${CYANEA_HOME}/bin/amctl.sh pa start ${CYANEA_HOME}/bin/amctl.sh sam1 start From second Managing Serer: #${CYANEA_HOME}/bin/amctl.sh wd1 start ${CYANEA_HOME}/bin/amctl.sh wd2 start #${CYANEA_HOME}/bin/amctl.sh aa1 start ${CYANEA_HOME}/bin/amctl.sh aa2 start #${CYANEA_HOME}/bin/amctl.sh ps1 start ${CYANEA_HOME}/bin/amctl.sh ps2 start #${CYANEA_HOME}/bin/amctl.sh md start #${CYANEA_HOME}/bin/amctl.sh pa start #${CYANEA_HOME}/bin/amctl.sh sam1 start Important: These examples reflect that a second Kernel was added to the default Managing Serer configuration. 14. On each serer, complete the same modifications to the stop script, MS_home\bin\am-stop.sh. 15. On each serer, complete the same modifications to the MS_home\bin\amstatus.sh script. It is a status script, used internally by Windows serices to check the status of Managing Serer components. 16. Start both serers. See Starting the Managing Serer on page 265. Note: When starting or stopping Managing Serers, first start the first Managing Serer. You can use an automation mechanism to coordinate this process. One such automation mechanism is the use of a remote execution shell. Tip: To query the status of all the components such as Archie Agent, Publish Serer, or Message Dispatcher een if one of the Kernels is not running, complete the optional steps in the next section Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 217

238 17. Once all the components are started on both the serers, erify the split Managing Serer configuration in the Visualization Engine. Select Administration > Managing serer > Self Diagnosis. In the component panel, the running components and their IP addresses displays. Optional steps to query the status of components when one of the Kernels is not running By modifying the scripts on the first and second Managing Serer to include information about the Kernel on the second Managing Serer, you can still query the status of components, een if one of the Kernels is not running. For each of the following files, add the code shown in bold: 1. On the first Managing Serer, add the code shown in bold to the following file: MS_home/bin/edit psctl.sh RMI_CODEBASE=" ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.publish.jar ${PORT_KERNEL_CODEBASE01}/model.jar ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.probe-intf.jar ${PORT_KERNEL_CODEBASE01}/kernel.common.jar ${PORT_KERNEL_CODEBASE02}/model.jar ${PORT_KERNEL_CODEBASE02}/kernel.common.jar" export RMI_CODEBASE SECURITY_POLICY=${CYANEA_HOME_OS}/etc/ps.policy export SECURITY_POLICY KERNEL_CODEBASE=" export KERNEL_CODEBASE KERNEL_RFS_ADDRESS="${KERNEL_HOST01}:${PORT_KERNEL_RFS01} ${KERNEL_HOST02}:${PORT_KERNEL_RFS02}" export KERNEL_RFS_ADDRESS 2. On the first Managing Serer, add the code shown in bold to the following file: MS_home/bin/edit aactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" archieagent.jar /archieagent.jar" export RMI_CODEBASE 3. On the first Managing Serer, add the code shown in bold to the following file: MS_home/bin/edit pactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" pollingagent-intf.jar archieagent-intf.jar export RMI_CODEBASE 218 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

239 4. On the first Managing Serer, add the code shown in bold to the following file: MS_home/bin/i mdctl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS01=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" messagedispatcher-intf.jar messagedispatcher-intf.jar" export RMI_CODEBASE 5. On the second Managing Serer, add the code shown in bold to the following file: MS_home/bin/i psctl.sh RMI_CODEBASE=" ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.publish.jar ${PORT_KERNEL_CODEBASE01}/model.jar ${KERNEL_HOST01}:${PORT_KERNEL_CODEBASE01}/ppe.probe-intf.jar ${PORT_KERNEL_CODEBASE01}/kernel.common.jar ${PORT_KERNEL_CODEBASE02}/model.jar ${PORT_KERNEL_CODEBASE02}/kernel.common.jar" export RMI_CODEBASE SECURITY_POLICY=${CYANEA_HOME_OS}/etc/ps.policy export SECURITY_POLICY KERNEL_CODEBASE=" export KERNEL_CODEBASE KERNEL_RFS_ADDRESS="${KERNEL_HOST01}:${PORT_KERNEL_RFS01} ${KERNEL_HOST02}:${PORT_KERNEL_RFS02}" export KERNEL_RFS_ADDRESS 6. On the second Managing Serer, add the code shown in bold to the following file: MS_home/bin/edit aactl.sh CODEBASE_ADDRESS01=$KERNEL_HOST01:$PORT_KERNEL_CODEBASE01 CODEBASE_ADDRESS02=$KERNEL_HOST02:$PORT_KERNEL_CODEBASE02 KERNEL_CODEBASE=" export KERNEL_CODEBASE RFS_ADDRESS="$KERNEL_HOST01:$PORT_KERNEL_RFS01 $KERNEL_HOST02:$PORT_KERNEL_RFS02" export RFS_ADDRESS RMI_CODEBASE=" archieagent.jar export RMI_CODEBASE Fine-tuning Managing Serer properties To best suit your enironment, you can fine-tune the settings in the Managing Serer properties files described in Appendix I, Managing Serer properties files, on page 299. Tuning recommendations for large-scale enironments Here are the tuning recommendations for when the Managing Serer is used to support large-scale enironments or high olumes of request traffic; for example, when there are 250 Data Collectors running at a total of 500 requests per second: Note: If you plan to deploy more than 100 Data Collectors, or if you intend to use high monitoring leels (L2/ L3) frequently, for example in a deelopment or testing enironment, it is recommended that you use a split Managing Serer Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 219

240 installation for better scalability, performance, and reliability. See Split Managing Serer installation in Unix on page 215 for split Managing Serer installation. 1. Increase the maximum heap size settings of the Kernel, Publish Serers, and Global Publish Serer. The Global Publish Serer change is only necessary if you use the correlation feature in ITCAM for Application Diagnostics. In MS_home/bin/seten.sh, modify the following properties: HEAP_MAX_SIZE_PS=1024 HEAP_MAX_SIZE_KERNEL=512 HEAP_MAX_SIZE_SAM= Increase the maximum heap size used by the ITCAM for Application Diagnostics Managing Serer. Complete the following steps: a. Log in to the IBM WebSphere Application Serer administratie console. b. Naigate as follows: 1) Click Serer > Application Serers and select the serer_name. 2) In the Configuration tab, naigate to Serer Infrastructure > Jaa and Process Management > Process Definition > Additional Properties: Jaa Virtual Machine. c. Modify the maximum heap size of the serer to If you hae not already created an additional instance of the Kernel, complete the instructions at Adding an additional Kernel on page Modify heartbeat settings. In MS_home/etc/kl1.properties, modify the following property: contract.duration=60 5. Start one more instance of the Kernel: MS_home/bin/amctl.sh wd2 start 6. If you hae not already created two additional instances of the Publish Serer, complete the instructions at Adding additional Publish Serers on page Start two more instances of the Publish Serer: MS_home/bin/amctl.sh ps3 start MS_home/bin/amctl.sh ps4 start 8. If you hae not already created two additional instances of the Archie Agent, complete the instructions at Adding additional Archie Agents on page Start two more instances of the Archie Agent MS_home/bin/amctl.sh aa3 start MS_home/bin/amctl.sh aa4 start 10. Increase MAXAPPLS and MAXAGENTS for the database. Complete the following procedure: a. Switch to the database instance user. For example: su - db2inst1 b. Complete one of the following options: If you do not hae a partitioned database, run the following commands: update dbm cfg using MAXAGENTS 500 db2 update db cfg for octigate using maxappls 300 db2stop db2start If you hae a partitioned database, the DBA must run the following commands. For example, if you hae a three node partitioned database: db2 terminate export db_node0 db2 update db cfg for octigate using MAXAPPLS ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

241 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate export db_node1 db2 update db cfg for octigate using MAXAPPLS 300 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate export db_node2 db2 update db cfg for octigate using MAXAPPLS 300 db2 update db cfg for octigate using MAXAGENTS 500 db2 terminate If you hae large amounts of data in the tables affected by the datatrim.sh script, the LOGFILSIZ and LOGSECOND parameters must be increased across all database partition nodes. 11. Set the Remote Method Inocation (RMI) timeout in the Data Collector. The Data Collector sockets are initially set for infinite time out. This setting can make the defensie calls of the Kernel hang and can deplete the Kernel if there is a problem with a Data Collector. Set the following property for all Data Collectors in DC_home/runtime/ appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties: am.rmisocket.timeout=60000 Enabling method signature tracing Note that turning on method signature tracing increases performance demands and that increasing method signature length increases hard disk consumption. To enable method signature tracing and (optionally) modify method signature length, complete the following steps: 1. Before you can enable method signature tracing, the Data Collector connecting to the Managing Serer must be installed and configured. See one of the following publications: IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide IBM Tioli Composite Application Manager for WebSphere (z/os): Data Collector Customization Guide IBM Tioli Composite Application Manager for J2EE: Data Collector Installation and Customization Guide 2. Set Monitoring Leel (MOD) to In the DC_home/runtime/app_serer_ersion.node_name.serer_name/custom/ toolkit_custom.properties file, uncomment the following line by remoing the number sign (#) at the beginning of the line: am.camtoolkit.gpe.customxml.l3=dc_home/itcamdc/etc/method_entry_exit.xml 4. Set the following property to true: com.ibm.tioli.itcam.toolkit.ai.methodentryexittrace=true 5. (Required only if you are integrating the Managing Serer with IBM Rational Performance Tester) The method signature length is defined in the Archie Agent properties by the TEXTSTRING_LENGTH entry, with a default alue of 60. Increase or decrease the length, as needed, in the Archie Agent properties files (such as aa.properties, aa1.properties, and aa2.properties). 6. (Required only if you are integrating the Managing Serer with IBM Rational Performance Tester) To see the method signature from the ITCAM for Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 221

242 Setting up the host Application Diagnostics Managing Serer (for example, from a drill-down iew), the following line must be added to the Publish Serer properties files (such as ps1.properties and ps2.properties): display_method_signature=true The ITCAM for Application Diagnostics includes a traps feature that enables you to hae messages sent when certain thresholds are reached. For this feature to work correctly, the SMTP host must be specified. Important: The Performance Analysis & Reporting (PAR) section and the Traps section do not send reports unless this step is completed. To do this, edit the file: MS_home/etc/md.properties Then specify the correct IP address or fully qualified host name of the SMTP host. (A alid serer is required; contact your Administrator for this information) for property as: smtp.host=aa.bb.cc.dd Substitute the IP address or fully qualified host name of the SMTP host for aa.bb.cc.dd. Important: If your Managing Serer Visualization Engine is not running on default port 9080, you must set up the Visualization Engine port for notifications. See Setting up the Visualization Engine port for notifications. Setting up the sender address The user must specify a alid address to enable the Report Link and PDF feature. Set e.framework. .sender" property in MS_home/etc/ e.properties with a alid address on your own SMTP domain, for example: e.framework. .sender=support@usca.ibm.com Setting up the Visualization Engine port for notifications If your Managing Serer Visualization Engine is not running on default port 9080 then you might hae to edit the Publish Serer properties files MS_home/etc/ps1.properties and MS_home/etc/ps2.properties. If additional Publish Serer instances exist, you must modify the properties files for them as well: MS_home/etc/ps3.properties,MS_home/etc/ps4.properties and so on. The e.port alue sets the port number that is used in the URL that is included in the . The user is to be able to access the Visualization Engine using this URL; therefore, the port must be set to the Visualization Engine HTTP port. Edit the ariable e.port as follows: e.port=ms_port 222 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

243 Setting up SNMP Rebuilding the HP-UX kernel To set up SNMP alerts and make them aailable in Trap and Alert Management, see the following sections: Appendix G, IBM Tioli Enterprise Console integration, on page 291 Appendix H, BMC Patrol integration, on page 295 The maxdsiz and maxdsiz_64bit kernel parameters limit the data segment size of a process in HP-UX. To generate a Jaa heap dump, the parameters must be set to at least 1.6 times the size of the Jaa heap size in the application serer. To configure HP-UX to proide a Jaa heap dump, complete the following procedure: 1. Use kmtune to set the parameters maxdsiz and maxdsiz_64bit to at least 1.6 times the size of the Jaa heap size in the application serer. 2. Rebuild the kernel. 3. Reboot the node. Note: Refer to the HP-UX documentation for details on how to configure the kernel memory parameters. Increasing the Linux kernel setting Red Hat Intel/Linux Managing Serer: if you are using a Linux Managing Serer, you must change the msgmni kernel ariable. You can issue (as root), the following command to set it to sysctl w kernel.msgmni =1024 To check the current setting, use the following command: ipcs -l Configuring a Managing Serer on a host with multiple network interfaces and NATs The Managing Serer always binds to one network interface (IP address) only, een on a host with multiple network interfaces If the Managing Serer always exposes a specific IP to all Data Collectors, complete the following steps: 1. On the Managing Serer side, in seten.sh (in MS_home/bin), set KERNEL_HOST01 to the IP address of the Managing Serer. You must also set the following parameters: a. am_socket_bindip=<ipaddress_ms> b. am_socket_exportip=<ipaddress_ms> 2. On the Managing Serer side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin), add jaa.rmi.serer.hostname to the jaa command line in the start section of the script and set it to IP address of the Managing Serer. Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 223

244 3. You must edit the MS_home/etc/e.properties kernel codebase of the file alue to point to the right IP address. This edit also affects DHCP where you must hardcode the dynamic DNS host name rather than an IP address in the MS_home/etc/e.properties file. 4. In MS_home/etc/ms.properties, you must modify kernel.hosts to indicate the IP address of the Managing Serer: kernel.hosts=<ipaddress_ms>cbsport:rfsport:rmiport By default, this IP address is kernel.hosts=<ipaddress_ms>9122:9120: In addition, if the Managing Serer is installed on multiple serers, make the changes from Steps 1 on page 223 through 3 on all the serers where the Managing Serer is installed. 6. On the Data Collector side, in the DC_home/runtime/ appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties file, make sure that the kernel.codebase and kernel.rfs.address properties hae the right IP address for the Managing Serer. 7. On the Data Collector side, in the DC_home/itcamdc/etc/datacollector.policy file, make sure that the socket permissions (jaa.net.socketpermission) are granted to the right IP address for the Managing Serer. The Managing Serer can also expose different IP addresses to different Data Collectors because of Network Address Translation (NAT), een though it binds to only one IP address on the host. In this case, complete the following procedure: 1. On the Managing Serer side, in seten.sh (in MS_home/bin), set KERNEL_HOST01 to the fully qualified domain name of the Managing Serer (for example qaapp-lnx-s01.usca.ibm.com). 2. On the Managing Serer side, in wdctl.sh, klctl.sh and psctl.sh (in MS_home/bin), add jaa.rmi.serer.hostname to the jaa command line in the start section of the script and set it to the fully qualified domain name of the Managing Serer. 3. In addition, if the Managing Serer is installed on multiple serers, make the changes from Steps 1 and 2 on all the serers where the Managing Serer is installed. 4. On the Data Collector side, in the DC_home/runtime/ appserer_ersion.node_name.serer_name/ appserer_ersion.node_name.serer_name.datacollector.properties or DC_home/runtime/app_serer_ersion.node_name.serer_name/ datacollector.properties file, make sure that the kernel.codebase and kernel.rfs.address properties hae the right IP address (or fully qualified host name) for the Managing Serer. 5. On the Data Collector side, in the DC_home/itcamdc/etc/datacollector.policy file, make sure that the socket permissions (jaa.net.socketpermission) are granted to the right IP address (or fully qualified host name) of the Managing Serer. 6. Ensure that on the Data Collector side, the fully qualified host name of the Managing Serer can be resoled to the correct IP address. You can use ping to erify this. 224 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

245 Adjusting maximum resource settings for the operating system You can change the ulimit settings to aoid running out of file handles, sockets, or memory. If you receie error messages related to file handles, sockets, or memory, or if you think this is likely to happen, for example if your enironment is running multiple instances of IBM WebSphere Application Serer, complete the following steps: 1. Log in as root. 2. Enter a new ulimit alue. For example, to set the maximum number of open file descriptors, use the command: ulimit -n alue The recommended alue is Attention: Some ulimit settings can affect system stability. 3. Verify that the new ulimit alue has been set: ulimit -a Assigning local Publish Serers to local Data Collectors to reduce WAN traffic in a split Managing Serer installation By default, the Managing Serer kernel assigns Publish Serers to Data Collectors based on Publish Serer aailability, using a round robin algorithm. On a multiple site deployment, this can lead to a Data Collector on one site being assigned to a Publishing Serer on a different site, een if a Publishing Serer is aailable on the same site. This generates significant network traffic between sites and can adersely affect performance. To ensure that a local Publish Serer is assigned to Data Collectors when aailable, you can set up a subnet policy algorithm instead of round robin. In the subnet policy algorithm, each Data Collector is assigned a Publish Serer. This Publish Serer resides under the same subnet as the Data Collector; that is, each Data Collector on Site is assigned a Publish Serer also located on Site A (if such a Publishing Serer is aailable). This type of subnet policy applies only for Data Collector and Publish Serer assignment; it does not apply to Archie Agent, which is still assigned to Publish Serer based on the Round Robin algorithm. Attention: If you hae more than one kernel, all kernels must hae the same policy settings. Roundrobin policy for one kernel and subnet policy for another kernel are currently not supported. Moreoer, all the other properties related to this policy also must be the same in all kernel properties files. You can adjust the policy on all kernels only at the same time. To enable the subnet policy, based on the IP address and hostname, complete the following steps. 1. Modify the following parameters in the kl1.properties and kl2.properties files, located in MS_home/etc. a. policy=subnet In the policy parameter, roundrobin means the default algorithm; subnet enables the subnet algorithm. If this property is not specified, the kernel uses the default roundrobin algorithm. Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 225

246 b. subnet.policy.autodetect=true or subnet.policy.autodetect=false If subnet.policy.autodetect is set to true, the kernel finds the best matching Publish Serer for a Data Collector based on their IP addresses. The best match is determined by comparing IP addresses of the Data Collector and Publish Serer. At least the first two numbers of the IP address must be the same. For example, if two Publish Serers hae the following addresses: ps1= ps2= For Data Collector on dc1= , ps2 is assigned. For Data Collector on dc2= , ps1 is assigned. For Data Collector on dc3= , there is no match. The kernel falls back to a round robin algorithm, and assign the first aailable PS, which could be either ps1 or ps2. For subnet.policy.autodetect=true, you do not need to define any subnet groups. If subnet.policy.autodetect is not specified, true is assumed. If subnet.policy.autodetect is set to false, you must define subnet policy groups. These groups include IP addresses and hostnames of Data Collector and Publish Serer hosts. For example: subnet.policy.group1= *.*, *.*,deapp-lnx-*, subnet.policy.group2= *.*, *,*-lnx-*,serer.company.com... subnet.policy.groupn= *.*,92.82.*.* N can be 1, 2, You can use any numbers from 1 to 100; no particular sequence is required. Eery group can hae as many IP addresses or hostnames as needed, as full alues or masks, separated by commas. Each group must include IP addresses or hostnames of at least one Data Collector and at least one Publish Serer; otherwise, Data Collectors in this group are assigned to other Publish Serers. Attention: In an IP address mask, eery component of the address must be either a number or an asterisk. For example, 192.*.*.2 is a alid mask, but 192.2*.1*3.2 is not. The Data Collector is assigned a Publish Serer that falls into the same policy group as the Data Collector. If multiple Publish Serers are within the same subnet group, the round robin algorithm is used among them. You can specify both 4 byte and 6 byte IP address groups. If you do not specify the groups, or if a Data Collector does not fall into any of the specified groups, or if there is no Publish Serer aailable under the same policy group as a Data Collector, the kernel falls back to autodetection and assigns the closest aailable Publish Serer according to the IP address of the Data Collector. It is not necessary that different IP patterns under same policy group reside under the same subnet mask. Note that a Data Collector is assigned to a Publish Serer under the same policy group, but they might be under different subnet masks. It is your responsibility to proide Publish Serers and define the right policy groups to proide for load balancing and aoid inter-site network traffic. For example, the following scenario could hae a major performance impact: 2000 Data Collectors and 6 Publish Serers on Site A 6000 Data Collector and 2 Publish Serers on Site B 226 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

247 In this case, the Publish Serers on Site B can get a larger load. It is your responsibility to either change assignment policies or add more Publish Serers to Site B. 2. Uncomment the following property in the kl1.properties and kl2.properties files, located in MS_home/etc: kernel.accept.request.duration=5 You can set a higher alue if you want. The default alue is 3. It is expected that all Managing Serers (kernels) are started within the set number of minutes (by default, 3 minutes; with the uncommented line as quoted, 5 minutes). The kernel waits for this duration before it starts assigning Data Collectors to Publish Serers. If one of the Managing Serers is not started within this time, other kernels start assigning Data Collectors to Publish Serers without taking the missing Publish Serers into account; this can lead to Data Collectors being assigned to wrong Publish Serers. For example, you can hae two Publish Serers on two different hosts: host1= host2= Data Collectors are also running on both hosts. Suppose you start Managing Serer 1 but wait longer than kernel.accept.request.duration minutes to start the Managing Serer 2. In this case, as the publish serer on host2 is not yet aailable, so the kernel assigns the Data Collector on host2 to the Publish Serer on host1. Therefore, you must start all Managing Serers within the duration set in kernel.accept.request.duration. 3. Stop all Managing Serers by using the MS_home/bin/am-stop.sh script. Check if any process has not stopped (and therefore is hanging); in this case, run the MS_home/bin/am-forcestop.sh script. 4. Start all Managing Serers by using the MS_home/bin/am-start.sh script. Tip: You can check the current assignment of Data Collectors to Publish Serers using the Managing Serer Self Diagnosis window. In the Visualization Engine main menu, select Administration > Managing Serer > Self diagnosis; then select eery Publish Serer to iew a list of Data Collector relationships. If any Data Collector is working with the Managing Serer but is not displayed in this window for any of the Publish Serers, select Administration > Serer Management > Data Collector Configuration > Configured Data Collectors from the main menu. Then unconfigure the affected Data Collector and configure it again. After you hae configured it again, it is listed in the Self diagnosis window for one of the Publish Serers. Important: Sometimes, a serer belongs to more than one user-defined policy group according to its hostname and IP address. In this case, the following priority rules apply: If the hostname belongs to more than one policy group, the group with the lower number takes priority. For example, if the hostname fulfills the criteria for both subnet.policy.group2 and subnet.policy.group4, subnet.policy.group2 takes priority. If the IP address belongs to more than one policy group, the more specific definition takes priority. For example, if the address is , subnet.policy.group1 includes *.*, and subnet.policy.group2 includes *, subnet.policy.group2 takes priority. Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 227

248 If the IP address or hostname belongs to more than one policy group and the definitions are of the same leel of specificity, the group with the lower number takes priority. Creating additional users to log in to the ITCAM for Application Diagnostics Managing Serer As part of the installation and configuration of the serer for the ITCAM for Application Diagnostics Managing Serer, an initial user was set up with the information proided during the installation process. This user has root priileges and full rights and access to the serer for the ITCAM for Application Diagnostics Managing Serer. See one of the following sections: Custom installation and upgrade: creating the user interface user on page 126 For security purposes, to add more users to the serer for the ITCAM for Application Diagnostics Managing Serer, see the account management chapter of the IBM Tioli Composite Application Manager: Users Guide or online help. Changing the user name and password for the database schema user The schema user owns and can create the database tables for the Managing Serer. To change the user name and password for the schema user, complete the following procedure: 1. Create a local UNIX or Linux account associated with the new user, new_user_name. Note: To change the password for the installation user without changing the user name, change the password of the user on the local operating system. 2. Encrypt the new password for the database schema user by completing the following steps: a. From a command line, change to the MS_home/bin directory. b. Enter the following command:./amcrypto.sh -encrypt new_user_pwd Running the script produces an output that is the encrypted ersion of the new_user_pwd. c. Copy this output and use it as the alue you enter for the JDBC_PASSWORD parameter of the seten.sh file, in the next step. 3. Modify the MS_home/bin/seten.sh and edit the following parameters: JDBC_USER=new_user_name JDBC_PASSWORD=new_user_pwd 4. Change ownership of the MS_home directory using the following command, if you want to start your processes as the new user. chown -R new_user_name:new_group_name MS_home 5. Log in to the IBM WebSphere Application Serer administratie console where the ITCAM for Application Diagnostics Managing Serer is installed. 6. Expand Resources > JDBC Proiders > (Choose the JDBC Proider for ITCAM for Application Diagnostics) > Data Sources > (Choose the DataSource) > J2C Authentication Data Entries > (Choose the J2C Authentication Data Entries). 7. In the User ID field, type in the new user. 8. In the password field, type in the password corresponding to the new user. 228 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

249 9. ClickOK. 10. Sae the changes. 11. Restart the instance of IBM WebSphere Application Serer used by the Managing Serer. See Restarting the application serer on page 274. Enabling the feature to launch into the IBM Tioli Enterprise Portal from the ITCAM for Application Diagnostics Managing Serer You can enable a feature that allows you to go directly into theitcam for Application Diagnostics Managing Serer user interface for the IBM Tioli Enterprise Monitoring Agent, which is called IBM Tioli Enterprise Portal, without launching the portal manually. This is done from the ProblemCenter > Resource page of the ITCAM for Application Diagnostics Managing Serer. You must first modify the MS_home/etc/e.properties file. Enter appropriate alues for the following properties. They are described at e.properties on page 302: tep.hostname tep.port tep.baseurl tep.userid Using the Managing Serer with a 6.0 Data Collector You can use Data Collectors from ITCAM for WebSphere 6.0 or ITCAM for J2EE 6.0 with the current Managing Serer. To do this, complete the following procedure on the Managing Serer. 1. You can complete this procedure only under the following conditions: You still hae an existing ersion 6.0 installation of the Data Collector. You still hae an existing ersion 6.0 of the Managing Serer. Important: You do not hae to complete this procedure to use a Data Collector from ITCAM for WebSphere 6.1, ITCAM for J2EE 6.1, or ITCAM for Web Resources 6.2 with the current Managing Serer. Complete the following procedure to enable the Managing Serer to communicate with a ersion 6.0 Data Collector: 2. Stop the ersion Managing Serer. See Stopping the Managing Serer on page Copy the lib6.0 directory from the 6.0 MS_home directory to the ersion MS_home directory. Do not rename the lib6.0 directory. 4. On each host where the 6.0 Data Collector is installed: a. modify the DC_home/etc/datacollector.properties file to point to the ersion Managing Serer: 1) If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, modify the alues for the host name. Here is an example of the modified parameters: kernel.codebase= kernel.rfs.address=linux-machine1.usa.company.com:9120 linux-machine1.usa.company.com:9121 Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 229

250 2) By default, the ersion Managing Serer has only one kernel, while the ersion 6.0 Managing Serer has two. If you do not plan to manually create an additional kernel for the ersion Managing Serer, remoe references to the second listed port for the kernel.codebase and kernel.rfs.address parameters. (By default, the second port is 9123 and 9121.) Match what you would see in the datacollector.properties file for a Data Collector. The alues in the 6.0 datacollector.properties file matches what you would see in the datacollector.properties file for a Data Collector. For example, kernel.codebase= /kernel.core.jar /ppe.publish.jar /ppe.publish-intf.jar kernel.rfs.address=linux-machine.usa.company.com:9120 b. If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, modify the permission jaa.net.socketpermission in the DC_home/etc/datacollector.policy file to point to the ersion Managing Serer host name. For example: permission jaa.net.socketpermission "linuxmachine.usa.company.com", "connect,accept,resole"; c. If the ersion Managing Serer is on a different computer than the ersion 6.0 Managing Serer, in the DC_home/etc directory, delete node_name.serer_name.datacollector.properties d. If you are not migrating data from the ersion 6.0 Managing Serer to the ersion Managing Serer, in the DC_home/etc directory, delete node_name.serer_name.cyaneagpscounter.txt e. (optional) If you want the Data Collector run time to generate a new set of IDs for Probe and ProbeController, delete the DC_home/etc/ node_name.serer_name.id file. f. If the path for the ersion MS_home is different from the path for the ersion 6.0 MS_home, change the MS_AM_HOME enironment ariable in the WebSphere Application Serer administratie console to point to the ersion Managing Serer installation directory by completing the following steps: 1) Log in to the WebSphere Application Serer administratie console. In the Naigation Pane, select Enironment -> WebSphere Variables. 2) Select the scope of the ariable to add. Most ariables used by the Data Collector are at the serer scope of your monitored serer. 3) Change the following enironment ariable to point to the MS_home for the ersion Managing Serer: MS_AM_HOME=MS_home 4) Click Apply or OK. In the Messages dialog box, click Sae. 5) In the Sae to Master Configuration dialog box, do one of the following: a) If you are under a Network Deployment enironment, select Synchronize changes with Nodes and click Sae. b) If you are not under a Network Deployment enironment, click Sae. 5. Start the ersion Managing Serer. See Starting the Managing Serer on page Check the SystemOut.log to erify that the Data Collector has connected to the ersion Managing Serer. You receie a message similar to the following: [1/9/08 14:11:34:380 PST] SystemOut O <PPECONTROLLER, 60a8abc2-abcd-dc01-a e , > Successfully joined Kernel linux-machine.usa.company.com: ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

251 7. Log in to the Visualization Engine (Application Monitor) user interface and configure the ersion 6.0 Data Collector to be monitored by the ersion Managing Serer by taking the following steps: a. Select Administration -> Serer Management -> Data Collector Configuration -> Unconfigured Data Collectors. b. Check to see that the serer for the Data Collector is listed. c. Apply a configuration to the Data Collector in the Application Monitor user interface. d. Verify that the Data Collector components are enabled and running in the Self-Diagnosis page of the Application Monitor user interface. e. Verify that the Data Collector is communicating with the Managing Serer. 8. (Optional) Because the ersion 6.0 Data Collector does not connect to the ersion 6.0 Managing Serer anymore, unconfigure it from the Application Monitor user interface for the ersion 6.0 Managing Serer. Changing the IP address or host name of the Managing Serer Here are the instructions for changing the IP address or fully qualified host name of a Managing Serer. You must modify the Data Collector. Changing the IP address or fully qualified host name of a Managing Serer without updating the Data Collectors associated with that change disrupts communication and causes policies to fail. Complete the following procedure to change the IP address or fully qualified host name: 1. Stop the Managing Serer. See Stopping the Managing Serer on UNIX and Linux on page Stop the instance of IBM WebSphere Application Serer that is being used by the Managing Serer. Complete the steps in Stopping the application serer on page Change the IP address or fully qualified host name on the Managing Serer. Contact your system administrator on the proper procedure for your system. 4. Change the corresponding system configuration for the Data Collector serer to access the Managing Serer by host name. Contact your system administrator on the proper procedure for your system. 5. If you are using a local DB2 database, update the DB2 nodes with the correct hostname/nodename. 6. Update the ITCAM data source in the WebSphere administration console with the correct hostname. 7. In the MS_home/bin/seten.sh file, update the JDBC_DRIVER_URL ariable with the correct host name. 8. Start the instance of IBM WebSphere Application Serer that is being used by the Managing Serer. See Starting the application serer on page Start the Managing Serer. See Starting the Managing Serer on page Reconfigure the Data Collector by running the Configuration Tool. In the process, select Recollect Managing Serer information in the Managing Serer information summary panel. See the IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide. 11. Restart the instance of the application serer that is being monitored by the Data Collector. See Restarting the application serer on page 274. Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 231

252 Making sure that the Managing Serer host name gets resoled to the correct IP address The Data Collector obtains the Managing Serer Kernel network address from the Managing Serer. If a host name is specified for the Kernel, it is possible that one of the resoled IP addresses cannot reach the Managing Serer from the Data Collector, and the connection to the Data Collector. It then fails with a Connection refused error message. To aoid a failed connection, instead of the host name, specify a alid IP address for the Managing Serer in the MS_home/bin/seten.sh and MS_home/etc/ ms.properties files. Complete the following procedure: 1. To determine IP addresses for a gien Managing Serer host name, issue the following command from the Data Collector serer: nslookup MS_hostname 2. To test basic connectiity, on the Data Collector serer, for each IP address listed in the output from the preious step, issue the following command: ping ip_address 3. On the Managing Serer serer, in the MS_home/bin/seten.sh file, set the following properties to the IP address of the Managing Serer: KERNEL_HOST01 am_socket_bindip am_socket_exportip For example: KERNEL_HOST01= am_socket_bindip= am_socket_exportip= On the Managing Serer serer, in the MS_home/etc/ms.properties file, set the following property, as follows: kernel.hosts=msipaddresscbsport:rfsport:rmiport For example: kernel.hosts= :9122:9120:9118 This solution usually works except when there is a firewall with Network Address Translation (NAT) enabled. In that case, you must make network changes so that all the resoled IP addresses can reach the Managing Serer. Sustaining large amounts of trace If many calls are being traced, and if some method data is not displayed in the Visualization Engine, complete the following procedure to configure the Managing Serer to sustain large amounts of trace: 1. Increase the method count limit of the Publish Serer. The Publish Serer maintains the method trace for the requests. The number of method entry or exits in the method trace is limited. The default number is If any request has more method records than 10000, the Publish Serer truncates the method trace request in order to limit the total method entry or exit count to the configured alue. By configuring the property Maximum Method Records, you can control the number of method entry or exits in the method trace of a request.to increase the limit, change the property Maximum Method Records in the ITCAM for Application Diagnostics Managing Serer. 232 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

253 From the top naigation click Administration > Managing Serer > System Properties. Change the alue of Maximum Method Records to from Increase the Jaa heap size of the Archie Agent. The runtime memory of the Archie Agent must be increased as a potentially bigger method trace from the Publish Serer. Set HEAP_MIN_SIZE_ARCHIVE_AGENT=1024 and HEAP_MAX_SIZE_ARCHIVE_AGENT=2048 in file MS_home/bin/seten.sh to increase the Jaa heap size. 3. Reduce the batch size of the Archie Agent. The Archie Agent tries to batch process a specified number of requests. The default is 20 requests. It hits the limit of the IBM DB2 drier with the large requests. Change REQUESTDATA_BUFFER_THRESHOLD=20 to REQUESTDATA_BUFFER_THRESHOLD=1 in MS_home/etc/aa.properties. 4. Increase the Jaa and JNI stack size of the Archie Agent. Een one large request can hit the IBM DB2 drier limit. To preent this, add -Xoss8M and -Xss8M in the Jaa startup command in the MS_home/bin/aactl.sh file. ${JAVA_HOME}/bin/jaa -class path $CLASSPATH -Xoss8M -Xss8M 5. Increase the query heap size of the IBM DB2 serer to accommodate the large batch query from the Archie Agent as follows: db2 update dbm cfg using parameter alue For example, db2 update dbm cfg using query_heap_sz 8000 If the composite transaction tracking feature is enabled, increase the heap size of the GPS component. Set the following parameters in MS_home/bin/seten.sh: HEAP_MIN_SIZE_SAM=256 HEAP_MAX_SIZE_SAM=1024 Starting ITCAM for Application Diagnostics automatically upon reboot If you want ITCAM for Application Diagnostics to start automatically upon reboot, you can actiate the appropriate scripts for the components. A user, such as a system administrator, can create an autostart daemon to start ITCAM for Application Diagnostics components upon reboot. Here is the suggested sequence to restart components: 1. IBM DB2 or Oracle database 2. Web Serer (if installed) 3. IBM WebSphere Application Serer 4. Managing Serer (The script for starting the Managing Serer is MS_home/bin/am-start.sh.) Setting up the Managing Serer to automatically configure Data Collectors The Managing Serer automatically applies a default configuration to all Data Collectors. The default configuration is determined by the am.ms.autoconfiguredc property in the kl1.properties file. By default this alue is set to true. Chapter 16. Customization and adanced configuration for the Managing Serer on UNIX and Linux 233

254 You might not want to configure all data collectors automatically. If so, you can configure each Data Collector by changing the dc.autoconfigure property in the dc.properties file to false. The Managing Serer am.ms.autoconfiguredc property oerrides the dc.autoconfigure property. For example, if the am.ms.autoconfiguredc property is set to false, this setting oerrides any Data Collectors that hae a dc.autoconfigure property set to true so that no Data Collectors are automatically configured. To change the Data Collector autoconfiguration default from true to false, take the following steps: 1. In the MS_home/etc/kl1.properties file, set am.ms.autoconfiguredc=false. 2. In the same properties file, set the db.config.name property to the type of application serer that is monitored by all new Data Collectors that connect to the Managing Serer. The following is a list of alues: j2ee=default1 CICS=default2 ims=default3 tomcat=default4 netweaer=default5 jboss=default6 WL=default7 J2SE=default8 oracle=default9 WASCE=default10 WS=default11 default* is the CONFIG name in the DB CONFIG table for configurations already populated. If a platform is not specified in this property, it is configured to default1, which is the J2EE default configuration. 3. Restart the Managing Serer. For information about oerriding autoconfiguration for a particular Data Collector, see Oerriding Data Collector autoconfiguration in the Distributed Data Collector Installation and Customization Guide. 234 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

255 Chapter 17. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on UNIX and Linux Managing Serer This chapter describes how to uninstall the Managing Serer,IBM WebSphere Application Serer and IBM DB2. The recommended order for uninstalling is as follows: 1. Managing Serer 2. Manual uninstallation of IBM WebSphere Application Serer on page Manual uninstallation of IBM DB2 on page 239 It is generally recommended that you uninstall Data Collectors before you uninstall the Managing Serer so that the uninstallation program can delete Data Collector registration information from the Managing Serer. See the chapters for uninstalling Data Collectors in one of the following publications: IBM Tioli Composite Application Manager for WebSphere: Distributed Data Collector Installation and Customization Guide IBM Tioli Composite Application Manager for WebSphere (z/os): Data Collector Configuration and Customization Guide About this task Table 45. How to export the DISPLAY ariable Complete the following procedure to uninstall the Managing Serer: Procedure 1. If running the uninstallation from a remote computer, enter xhost + hostname on the computer where you are sitting. The hostname is the fully qualified host name of the computer on which the Managing Serer is installed. 2. Log in as the root user on the computer on which the Managing Serer is installed. 3. Export the DISPLAY ariable. Complete one of the following options: If running the uninstallation from a remote computer Enter export DISPLAY=local_machine:0.0 Where local_machine is the fully qualified host name of the computer where you are sitting. If running the uninstallation from the computer where the Managing Serer is installed Enter export DISPLAY=localhost: Export the LANG ariable. Run the following command: export LANG=en_US.UTF-8 5. If it is not already stopped, stop the Managing Serer. Copyright IBM Corp. 2006,

256 6. If the serer instance of WebSphere Application Serer that is being used by the Managing Serer is stopped, start the WebSphere Application Serer. 7. Back up files from the Managing Serer and embedded IBM DB2 installations (including log files) that you still need. 8. Run the uninstallation program with the following file: MS_home/_uninst/ uninstaller.bin. The Welcome panel is displayed. 9. Click Next. The Choose Feature to Uninstall panel is displayed. 10. Select the features and click Next. The WebSphere Application Serer Unconfiguration panel is displayed. 11. Verify the information in this panel. Select or enter the correct information if it is not correct: Table 46. IBM WebSphere Application Serer information entered during installation Field Host Name SOAP Connector Port What to do Type the fully qualified host name of the IBM WebSphere Application Serer where the Managing Serer was running. Note: If using Network Deployment, proide the host name of the Deployment Manager instead. Enter the SOAP port setting (The default is 8880). This connector port was used by the IBM WebSphere Application Serer to send commands using the Simple Object Access Protocol (SOAP). The SOAP port is identified in the AppSerer_home/profiles/profile_name/config/cells/ cell_name/nodes/node_name/sererindex.xml file of the instance of IBM WebSphere Application Serer that the Managing Serer uses. Tip: If using Network Deployment, proide the SOAP port of the Deployment Manager instead. User Name Password Type the name of the user running WebSphere. This is the user used to log in to the IBM WebSphere Application Serer administratie console for the instance of IBM WebSphere Application Serer being used by the Managing Serer. Type the user password. Click Next. The Choose Embedded Components to Uninstall panel is displayed. 12. If you want to uninstall embedded ersions of IBM WebSphere Application Serer and IBM DB2, select Embedded DB2 Uninstallation, or both, and click Next. Note that when you choose both of these options, must manually delete the Managing Serer installation folder and some sub folders after the uninstallation completes. The Reiew Uninstallation Information is displayed. 13. Verify the information in this panel and click Uninstall to continue the uninstallation. 14. When the uninstallation panel is complete, the Finish panel is displayed. 15. If you choose not to uninstall IBM WebSphere Application Serer, stop the instance of IBM WebSphere Application Serer that was being used by the Managing Serer. Delete the MS_home directory and any subdirectories. 16. If you choose not to uninstall DB2, complete one of the following options: Delete the files and subdirectories under MS_home, but leae AppSerer_home and DB2_home intact. Manually uninstall IBM DB2 and IBM WebSphere Application Serer (See Manual uninstallation of IBM WebSphere Application Serer on page ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

257 and Manual uninstallation of IBM DB2 on page 117), then delete the MS_home directory and any subdirectories. 17. If you want to keep any of the Managing Serer installation log files in the /ar/ibm/tioli/common/cyn/logs directory (or another directory you specified as the log directory), back them up. Here is a list of installation log files for the Managing Serer: msg-install.log trace-install.log The log file names might include numeric affixes. 18. Delete the installation log files in the /ar/ibm/tioli/common/cyn/logs directory. Silent uninstallation of the Managing Serer on Linux and UNIX systems Complete the following procedure to uninstall the Managing Serer: 1. Complete the alues in the response file based on the following table: Table 47. Configuration options for the Managing Serer on UNIX and Linux Option -W LogSettingUninst.logLeel=ALL DEBUG_MAX DEBUG_MID INFO WARN ERROR FATAL OFF -W LogSettingUninst.consoleOut =true false -P msfilesinstall.actieforuninstall =true false -P einstall.actieforuninstall =true false -P dbinstall.actieforuninstall =true false Description Indicates the log leel for the installation and configuration. Indicates that the uninstaller displays messages on screen during the unistallation process. Indicates if the Managing Serer is uninstalled. Indicates if the MSVE is uninstalled. Indicates if database tables must be uninstalled. Default alue is true. -V FORCE_UNINSTALL=true false Indicates whether the installer checks connectiity to the WebSphere Application Serer. True indicates that the installer does not check connectiity and uninstalls the Managing Serer. False indicates that the uninstaller checks connectiity to the WebSphere Application Serer and uninstallation does not proceed unless connectiity can be established. The WebSphere Application Serer must be running if you set -V FORCE_UNINSTALL=true -V WAS_HOSTNAME= host name Indicates the host name of the WebSphere Application Serer, proide a fully qualified host name or the IP address of the host. Optional or required? Required Optional Required Required Optional Optional Required, not used when-v FORCE_UNINSTALL =false Chapter 17. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on UNIX and Linux 237

258 Table 47. Configuration options for the Managing Serer on UNIX and Linux (continued) Option Description -V WAS_USER= user Indicates a user account that has the administrator role required by IBM WebSphere Application Serer. If WebSphere is running with global security enabled, the user you specify must hae the WebSphere Administrator Role. If WebSphere is running without global security enabled, the user you specify must hae membership in the Administrators group on Windows or root priileges on UNIX. This user must not be an LDAP user. -V WAS_USER_PWD=1tc@m123 Indicates the password for the administrator account. -V WAS_SOAP_PORT=8881 Indicates the WebSphere Application Serer Soap Port. -V UNINST_DB2=true false Indicates whether the embedded installed DB2is uninstalled. Optional or required? Required, not used when -V FORCE_UNINSTALL =false Required, not used when -V FORCE_UNINSTALL =false Required, not used when -V FORCE_UNINSTALL =false Optional. Required if DB2 was installed during embedded DB2 installation 2. Type the following uninstallation command./uninstaller.bin -silent -options response_file Note: There is a response file template aailable at the following location: Install_image/silent/MS_uninst.opt Uninstalling a three phase installation on Linux and UNIX systems After a successful three phase Managing Serer installation the splituninstall.sh script is generated in the MS_install_home/_uninst/ directory. If required, perform these steps to uninstall the Managing Serer: 1. Run the following command to uninstall Visualization Engine: <MS_HOME>/_uninst/uninstalle.sh [-password <password>] For example: /opt/ibm/itcam/websphere/ms/_uninst/splituninstall.sh -password yourpassword Note: WebSphere Application Serer User's Password is required by Visualization Engine. 2. Run the following command to uninstall Managing Serer: <MS_HOME>/_uninst/splituninstall.sh 3. For example: For example, /opt/ibm/itcam/websphere/ms/_uninst/splituninstall.sh To remoe the MS database in DB2, complete the following steps: a. Go to the temporary directory which you created in the DB2 home directory. 238 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

259 b. Run the following command as the DB2 instance user: <temporary directory>/db2/bin/db2uninstall.sh <DB2inst_username> <databasename> 4. For example: /opt/ibm/itcam/websphere/ms/_uninst/db2uninstall.sh db2inst1 octigate To remoe the MS database in Oracle, complete the following steps: a. Go to the temporary directory which you created in the DB2 home directory. b. Run the following command as the Oracle database instance user: <temporary directory>/oracle/bin/oracleuninstall.sh <sqlplus_user> <system_user> <system_password> <install_dir> <tablespace> <schema_user> <schema_password> <oracle_sid> Manual uninstallation of IBM WebSphere Application Serer If you used a preexisting installation of IBM WebSphere Application Serer, do not uninstall it unless you are sure that it is not being used for other purposes. Complete the following procedure to uninstall IBM WebSphere Application Serer from your serer: 1. Run the uninstallation executable file, which is located in a subdirectory in the installation path for IBM WebSphere Application Serer. For example: /opt/websphere/appserer1/uninstall/uninstall.bin Note: The uninstallation file might be in a different location if you did not install (embed) IBM WebSphere Application Serer along with the Managing Serer. 2. Follow the instructions in the uninstallation program windows. See IBM WebSphere Application Serer documentation for further information. 3. Reboot your serer. 4. If the directory still exists, delete the AppSerer_home directory. Manual uninstallation of IBM DB2 If you used a preexisting installation of IBM DB2, do not uninstall it unless you are sure that it is not being used for other purposes. Complete the following procedure to uninstall IBM DB2 from your serer: 1. Consult a DB2 administrator for assistance in remoing the databases, users, and serices that might be associated with the IBM DB2 application. 2. Complete the procedures documented in the IBM DB2 Information Center: a. Go to the IBM DB2 Information Center at the following website: b. Naigate as follows: 1) In the left pane, click Index > U. 2) In the right pane, click uninstalling > DB2 UDB > Windows: Uninstalling DB2 UDB (Windows) > Related Tasks: Uninstalling DB2 UDB (UNIX). Chapter 17. Uninstalling the Managing Serer,IBM WebSphere Application Serer and IBM DB2 on UNIX and Linux 239

260 240 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

261 Part 4. Appendixes Copyright IBM Corp. 2006,

262 242 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

263 Appendix A. Obtaining installation images To obtain images that are ready for the installation, you can either download the images from the Web or use the images on the CDs. Using installation files from the Web Complete the following procedure to obtain installation images from the Web: 1. You can go directly to the IBM Passport Adantage website to purchase and download the software. Go to the following website: software/passportadantage 2. Download the installation software from the Web. You need a password to access the software download site from IBM. Contact your IBM sales representatie to receie your user ID and password and website address for IBM Passport Adantage of the IBM Software Group. Contact IBM Sales for more information. No fee is charged for this distribution option. 3. Choose a directory or directories in which to store the installation images. The directory must be accessible to the computers on which you are installing the component. For a remote installation, complete one of the following options: Table 48. Accessibility of remote installation images UNIX and Linux Windows Mount the remote directory on the target computer. Map the remote directory to the target computer in Windows Explorer. 4. Choose a directory or directories in which to store the installation images. The directory must be accessible to the computers on which you are installing the component. For a remote installation, complete one of the following options: Table 49. Accessibility of remote installation images Linux Windows Mount the remote directory on the target computer. Map the remote directory to the target computer in Windows Explorer. 5. Expand the software packages into the directory or directories. Using installation files from CDs You can use the CDs in either of the following ways: Copy the contents of the CDs to a hard drie and a directory or directories to hold the installation images. Run an installation from CDs. Launch the installation program from the CD-ROM drie of your computer. Note: In a CD-based installation of the Managing Serer, the installation program copies installation files to a temporary directory on your hard disk. The installation program then starts on your computer, prompting you at certain times for the CDs that contain enablement software, such as IBM WebSphere Application Serer or IBM DB2. These images require at least 1 G of space. Copyright IBM Corp. 2006,

264 244 ITCAM for Application Diagnostics: Managing Serer Installation and Customization Guide

265 Appendix B. Using the LaunchPad interface Use the LaunchPad interface to complete the following actiities: Install ITCAM for Application Diagnostics View prerequisite information Access the ITCAM for Application Diagnostics information center and this guide Access the IBM Tioli Software website, from which you can access support resources Complete the following procedure to use the LaunchPad: 1. Start LaunchPad. Choose one of the following options: Table 50. Starting LaunchPad UNIX and Linux 1. Access the directory or CD-ROM where the installation files are located. 2. Type launchpad.sh and press Enter. Note: A non-root user must hae /tmp execute permission to start launchpad.sh Windows 1. Browse to the directory or CD-ROM where the installation files are located. 2. Launch the launchpad.bat file. The LaunchPad window opens, displaying the Welcome panel. 2. Depending on what you want to do, click of the following buttons: Installation Prerequisites: opens a browser and accesses the prerequisites web page Installation Guide: opens a browser and accesses this installation guide Product Support: opens a browser and accesses the IBM Product Support website Copyright IBM Corp. 2006,