Tivoli System Automation Application Manager

Size: px
Start display at page:

Download "Tivoli System Automation Application Manager"

Transcription

1 Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC

2

3 Tioli System Automation Application Manager Version 3.1 Installation and Configuration Guide SC

4 Note! Before using this information and the product it supports, read the information in Notices on page 217. This edition of the IBM Tioli System Automation Application Manager Installation and Configuration Guide applies to Version 3, Release 1, Modification 0 of IBM Tioli System Automation Application Manager, program number 5724-S92, and to all subsequent releases and modifications of this product until otherwise indicated in new editions. IBM Tioli System Automation Application Manager is the successor to the End-to-End Automation Management component of IBM Tioli System Automation for Multiplatforms V2.3. This edition replaces SC IBM welcomes your comments. A form for readers comments may be proided at the back of this publication, or you may address your comments to the following address: IBM Deutschland Research and Deelopment GmbH Department 3248 Schoenaicher Str Boeblingen Germany FAX (Germany): FAX (Other Countries): (+49) Internet eserdoc@de.ibm.com If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: Title and order number of this book Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusie right to use or distribute the information in any way it beliees appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 2006, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures Tables ii About this guide ix Who should read this guide ix How to use this guide ix Where to find more information ix Conentions used in this guide x Related information x Summary of changes xiii What's new for System Automation Application Manager xiii Part 1. System Automation Application Manager Chapter 1. Oeriew of System Automation Product Family Chapter 2. Installing System Automation Application Manager Product components Installing System Automation Application Manager on AIX, Linux or Windows Installing System Automation Application Manager on z/os Verifying the installation Post-installation tasks Chapter 3. Upgrading from IBM Tioli System Automation release 2.x Upgrading the MSCS adapter Chapter 4. Configuring the end-to-end automation manager Inoking the end-to-end automation manager configuration dialog End-to-end automation manager basic configuration 75 Configuring the end-to-end hardware adapter Configuring high aailability for the end-to-end automation manager Replicating the configuration files Setting up the domain Remoing the domain Validating and storing the automation policy for the end-to-end automation manager Defining the automation policy for the end-to-end automation manager Remoing the automation policy for the end-to-end automation manager Chapter 5. Silent configuration Oeriew Inoking silent configuration Silent mode input properties file Output in silent mode Chapter 6. Installing and uninstalling serice Installing serice Installing serice in a setup for high aailability 113 Uninstalling serice Updating the installation on z/os Chapter 7. Uninstalling System Automation Application Manager Launching the graphical uninstallation program on Windows Launching the graphical uninstallation program on AIX and Linux Using the uninstallation program Uninstalling System Automation Application Manager from z/os Chapter 8. Installing and configuring the Distributed Disaster Recoery feature Installing the Distributed Disaster Recoery feature 119 Configuring the Distributed Disaster Recoery feature Actiating the Distributed Disaster Recoery feature Uninstalling the Distributed Disaster Recoery feature Part 2. Enabling launch-in-context support Chapter 9. Installing and configuring the IBM TEC extension for the System Automation Application Manager Oeriew Prerequisites Installing the IBM TEC extension Configuring the TEC extension for System Automation Application Manager Chapter 10. Setting up Tioli Enterprise Portal launch-in-context support Copyright IBM Corp. 2006, 2009 iii

6 Part 3. Installing and configuring the end-to-end automation adapters Chapter 11. Oeriew Chapter 12. Installing and configuring the HACMP adapter Installing the HACMP adapter Automating the HACMP adapter Configuring the HACMP adapter Verifying the HACMP adapter configuration Controlling the HACMP adapter Chapter 13. Installing and configuring the MSCS adapter Installation and configuration roadmaps Planning and preparing for the MSCS adapter Installing the MSCS adapter Upgrading the MSCS adapter Configuring the MSCS adapter Windows Firewall on Windows Serer Proiding high aailability for the MSCS adapter 170 Verifying the installation and configuration Uninstalling the MSCS adapter Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter. 177 Installing the VCS adapter Automating the VCS adapter Configuring the VCS adapter Verifying the VCS adapter configuration Controlling the VCS adapter Part 4. Appendixes Appendix A. Default directories Appendix B. Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager Appendix C. Troubleshooting the installation of System Automation Application Manager Installation wizard cannot find WebSphere Application Serer on the system Determining the correct DB2 port number DB2 access test hangs DB2 message SQL1035N The database is currently in use. SQLSTATE= Installer cannot detect non-default SOAP port Exceptions appear in file eezinstall.log Cleaning up from a failed installation Procedures for troubleshooting an installation Using the log file collector utility Gathering information for IBM Support Appendix D. Troubleshooting the installation of the HACMP adapter HACMP adapter does not start HACMP adapter terminates Adapter does not connect to the host HACMP adapter log files Appendix E. Troubleshooting the installation of the MSCS adapter MSCS adapter log files MSCS adapter installation fails MSCS Adapter configuration dialog problems occur MSCS adapter start problems MSCS adapter terminates Domain does not join MSCS adapter uninstallation fails Uninstalling the MSCS adapter manually Appendix F. Changing the company logos on the top of a report Appendix G. Considerations about user and group management in WebSphere Application Serer Appendix H. Using IBM Support Assistant Installing IBM Support Assistant and the System Automation Application Manager plug-in Notices Trademarks Index i System Automation Application Manager: Installation and Configuration Guide

7 Figures 1. Oeriew of System Automation product family Components of System Automation Application Manager WebSphere scenario - base WebSphere scenario - HA Configuration of the HACMP adapter Configuration of the VCS adapter Copyright IBM Corp. 2006, 2009

8 i System Automation Application Manager: Installation and Configuration Guide

9 Tables 1. Product CD ersions WebSphere Application Serer upgrade CDs Archies for Windows platforms Archies for AIX platforms Archies for Linux on System x Archies for Linux on POWER Archies for Linux on System z Supported operating systems Disk space requirements on Windows systems Disk space requirements on AIX and Linux systems Database tables Contents of the WebSphere Application Serer upgrade CD or electronic delierable Installation directory and Tioli Common Directory DB2 data for local and remote DB2 setup WebSphere Application Serer installation parameters Installation parameters for IBM Tioli Enterprise Console End-to-end automation domain name WebSphere Application Serer user ID System Automation Administrator user ID Directories on the product CD Additional disk space requirements on z/os systems Installation directory and Tioli Common Directory General installation parameters DB2 data for local and remote DB2 setup WebSphere Application Serer (WAS) installation parameters Installation parameters for RACF user and groups Installation parameters for IBM Tioli Enterprise Console Installation parameters for IBM Tioli Common Reporting Installation parameters for GDPS interaction End-to-end automation domain name WebSphere Application Serer user ID System Automation administrator user ID Job control statements Inbound TCP ports Resources in the automation policy for the end-to-end automation manager Generated input properties files Archies for Windows platforms Archies for AIX platforms Archies for Linux on System x Archies for Linux on POWER Archies for Linux on System z Supported platforms for serer clusters to be managed by SA AM Distributed Disaster Recoery Context used to find a Tioli Enterprise Portal workspace Resources in the HACMP adapter automation policy HACMP adapter command options Microsoft Failoer Cluster default ports Resources in the VCS adapter automation policy VCS adapter control command options Default directories Copyright IBM Corp. 2006, 2009 ii

10 iii System Automation Application Manager: Installation and Configuration Guide

11 About this guide Who should read this guide How to use this guide This guide proides information needed to plan, install, configure, and upgrade IBM Tioli System Automation Application Manager (hereafter System Automation Application Manager). This guide is for planners, installers, and administrators who plan to install and configure System Automation Application Manager. This guide is diided into the following parts: Part 1, System Automation Application Manager, on page 1 describes how to install, uninstall, serice, and configure System Automation Application Manager. Part 2, Enabling launch-in-context support, on page 127 describes how you install and configure the IBM TEC extension for System Automation Application Manager. which enables users to naigate from an eent displayed in the Eent Console of Tioli Enterprise Console to the corresponding resource or domain in the System Automation operations console, and describes how to set up launch-in-context support for Tioli Enterprise Portal (TEP), which enables users to launch TEP workspaces from the System Automation operations console with a single mouse click. Part 3, Installing and configuring the end-to-end automation adapters, on page 135 describes how to install and configure the HACMP, MSCS, and VCS adapters. The Appendixes proide troubleshooting information. Where to find more information In addition to this manual, the IBM Tioli System Automation library contains the following books related to the System Automation Application Manager: IBM Tioli System Automation Application Manager Release Notes, SC IBM Tioli System Automation Application Manager Administrator s and User s Guide, SC IBM Tioli System Automation Application Manager Reference, SC You can download the books at: More information about IBM Tioli System Automation for Multiplatforms can be found in the following books: IBM Tioli System Automation for Multiplatforms Release Notes, SC IBM Tioli System Automation for Multiplatforms Installation and Configuration Guide, SC IBM Tioli System Automation for Multiplatforms Administrator s and User s Guide, SC IBM Tioli System Automation for Multiplatforms Reference, SC Copyright IBM Corp. 2006, 2009 ix

12 You can download the books at: The IBM Tioli System Automation home page contains useful up-to-date information, including support links and downloads for maintenance packages. The IBM Tioli System Automation Application Manager home page is: The IBM Tioli System Automation for Multiplatforms home page is: Conentions used in this guide This guide uses seeral conentions for special terms and actions and operating system commands and paths. Typeface conentions This guide uses the following conentions: Related information Typically, file names, directories, and commands appear in a different font. For example: File name: setup.jar Directory: /etc/hosts Command: eezdmn -reconfig Variables are either italicized, enclosed in brackets, or both. For example: Frequently, ariables are used to indicate a root installation directory: Root installation directory of System Automation Application Manager: <EEZ_INSTALL_ROOT> or EEZ_INSTALL_ROOT WebSphere Application Serer root installation directory: <was_root> or was_root Runtime root directory of Integrated Solutions Console: <isc_runtime_root> or isc_runtime_root Directories are shown with forward slashes (/), unless operating-system specific information is proided. On Windows systems, you should use backward slashes (\) when typing at a command line, unless otherwise noted. Operating-system specific information is proided. For example: AIX, Linux: /opt/ibm/tsamp/eez Windows: C:\Program Files\IBM\tsamp\eez z/os: /local/eez This topic proides information about publications and Web sites related to IBM Tioli System Automation: WebSphere Application Serer publications: The latest ersions of all WebSphere Application Serer publications can be found on the WebSphere Application Serer library Web site at x System Automation Application Manager: Installation and Configuration Guide

13 IBM DB2 publications: DB2 publications can be found on the IBM DB2 UDB Web site at The link to the PDF manuals is aailable in the Other resources section on the Web page. IBM GDPS publications: GDPS publications can be found in the Resources section on the IBM GDPS Web site at: IBM Redbooks publications: The following publications are aailable at: End-to-End Automation with IBM Tioli System Automation for Multiplatforms (SG ) GDPS Family An Introduction to Concepts and Facilities About this guide xi

14 xii System Automation Application Manager: Installation and Configuration Guide

15 Summary of changes What's new for System Automation Application Manager 3.1 The following enhancements and changes are proided in Version 3 Release 1: System Automation Application Manager, formerly the End-to-End Management component of Tioli System Automation for Multiplatforms, is now an independent product. System Automation Application Manager can now be installed on AIX 6.1 Windows Serer 2008 z/os The minimum Red Hat RHEL ersion is now 4.5. The HACMP, MSCS, and VCS adapters can no longer be configured to use the IBM Tioli System Automation operations console in direct access mode. They must now be configured to use System Automation Application Manager. There is a new Distributed Disaster Recoery feature of the System Automation Application Manager, which can be enabled with an additionally priced feature license. A graphical user interface to the Policy Editor has been added. Reports can be produced using the Tioli Common Reporting feature. A silent configuration feature has been added to allow configuration without a GUI. You can now use the SA operations console to moe resources from one node to another. Copyright IBM Corp. 2006, 2009 xiii

16 xi System Automation Application Manager: Installation and Configuration Guide

17 Part 1. System Automation Application Manager Chapter 1. Oeriew of System Automation Product Family Chapter 2. Installing System Automation Application Manager Product components Installing System Automation Application Manager on AIX, Linux or Windows Planning for installation Installing the middleware software Preparing for the installation of System Automation Application Manager Installing System Automation Application Manager using the installation wizard Installing System Automation Application Manager in silent mode Installing System Automation Application Manager on z/os Planning for installation Preparing for the installation of System Automation Application Manager Installing System Automation Application Manager on z/os Verifying the installation Verify the automation manager Verify the automation engine Verify the operations console Post-installation tasks Modify the Lightweight Third Party Authentication (LTPA) settings Modify the HTTP session timeout Configure the number of users who can connect to the automation manager using the operations console Modify the Windows Firewall Security Rules.. 67 Chapter 3. Upgrading from IBM Tioli System Automation release 2.x Upgrading the MSCS adapter Chapter 4. Configuring the end-to-end automation manager Inoking the end-to-end automation manager configuration dialog Using the task launcher Displaying online help End-to-end automation manager basic configuration 75 Domain tab Command shell tab Discoery library adapter tab User credentials tab Security tab Logger tab Saing the basic configuration Configuring the end-to-end hardware adapter Adapter tab Credentials tab Saing the hardware adapter configuration Configuring high aailability for the end-to-end automation manager Domain setup tab Automation manager tab Policy pool tab WebSphere tab DB2 tab Hardware adapter tab Saing the high-aailability configuration Restoring an existing high-aailability configuration Replicating the configuration files Setting up the domain Remoing the domain Validating and storing the automation policy for the end-to-end automation manager Defining the automation policy for the end-to-end automation manager Remoing the automation policy for the end-to-end automation manager Chapter 5. Silent configuration Oeriew Working in silent mode Tasks to be performed manually Inoking silent configuration Configuring MSCS on Windows Serer Silent mode input properties file Editing the input properties file Output in silent mode Chapter 6. Installing and uninstalling serice 109 Installing serice Where to obtain fix packs Archie naming conentions Naming conentions of the update installer location Installation scenarios Usage instructions for the platform-specific archies Steps for installing a product fix pack Installing serice in a setup for high aailability 113 Uninstalling serice Updating the installation on z/os Chapter 7. Uninstalling System Automation Application Manager Launching the graphical uninstallation program on Windows Launching the graphical uninstallation program on AIX and Linux Using the uninstallation program Copyright IBM Corp. 2006,

18 Uninstalling System Automation Application Manager from z/os Chapter 8. Installing and configuring the Distributed Disaster Recoery feature Installing the Distributed Disaster Recoery feature 119 Installation prerequisites Supported hardware and operating systems Packaging Installing the feature license Configuring the Distributed Disaster Recoery feature Configuring the JMS destination for GDPS eents Configuring the hardware adapter Actiating the Distributed Disaster Recoery feature Uninstalling the Distributed Disaster Recoery feature System Automation Application Manager: Installation and Configuration Guide

19 Chapter 1. Oeriew of System Automation Product Family The IBM Tioli System Automation Application Manager works together with other IBM Tioli System Automation products as shown in Figure 1. Figure 1. Oeriew of System Automation product family System Automation Application Manager manages the system as a whole through connections to these other products. The products are linked together by automation adapters. The adapters for IBM Tioli System Automation for Multiplatforms and IBM Tioli System Automation for z/os are packaged with those products. All other automation adapters are packaged with System Automation Application Manager. Copyright IBM Corp. 2006,

20 4 System Automation Application Manager: Installation and Configuration Guide

21 Chapter 2. Installing System Automation Application Manager Product components These components are common to System Automation Application Manager on all supported platforms as shown in Figure 2. The installation procedure on the z/os platform is significantly different to installation on the other platforms and is therefore described separately in the section Installing System Automation Application Manager on z/os on page 59 GDPS Browser Client GDPS Agent(*) Command Shell DLA SDK Integrated Solution Console Operations Console End-to-End Automation Manager Automation J2EE Framework Automation Engine Resource Adapter Automation Database DB2 Automation Engine SA Operator SA Administrator TCR UI Policy Editor WebSphere Application Serer TCR Application First Leel Automation Manager Resource Adapter Automation Policy SA Application Manager Hardware Adapter(*) FS Policy Pool SA Application Manager Node FS Policy Pool Automation Adapter First Leel Automation Manager (*) with Feature: Distributed Disaster Recoery Node First-Leel Automation Domain Node Node Figure 2. Components of System Automation Application Manager For information about the components of System Automation Application Manager please refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide. Installing System Automation Application Manager on AIX, Linux or Windows Planning for installation This section contains the information you need to prepare for the installation of System Automation Application Manager on AIX, Linux or Windows systems. Packaging System Automation Application Manager can be ordered from IBM as a media pack or downloaded from an IBM software distribution download site. Copyright IBM Corp. 2006,

22 Product CD and WebSphere Application Serer upgrade CD: When you order System Automation Application Manager on CD you receie the following CDs: One product CD for each operating system on which the product can be installed. You use the product CD to install System Automation Application Manager. One WebSphere Application Serer upgrade CD for each operating system on which the product can be installed. You use the upgrade CD to bring WebSphere Application Serer to the ersion leel required for System Automation Application Manager. For information about the middleware software CDs that are shipped with System Automation Application Manager, refer to Contents of the middleware software CDs on page 12. Product CD: The following table lists the ersions of the product CDs that are aailable for System Automation Application Manager. To install the product, you use the installation wizard file listed in the right column of the table. Table 1. Product CD ersions Operating system Product CD label Installation wizard file Windows IBM Tioli System Automation Application EEZ3100Windows\Windows\setup.exe Manager V3.1.0 for Windows AIX IBM Tioli System Automation Application Manager V3.1.0 for AIX EEZ3100AIX/AIX/setup.bin Linux on System x Linux on POWER Linux on System z IBM Tioli System Automation Application Manager V3.1.0 for Linux on System x IBM Tioli System Automation Application Manager V3.1.0 for Linux on POWER IBM Tioli System Automation Application Manager V3.1.0 for Linux on System z EEZ3100I386/i386/setup.bin EEZ3100PPC/ppc/setup.bin EEZ3100S390/s390/setup.bin WebSphere Application Serer upgrade CDs: The following table lists the aailable ersions of the WebSphere Application Serer upgrade CDs. Table 2. WebSphere Application Serer upgrade CDs Operating system CD label Windows IBM Tioli System Automation Application Manager V3.1.0 WAS V6.1 upgrade for Windows AIX IBM Tioli System Automation Application Manager V3.1.0 WAS V6.1 upgrade for AIX Linux on System x IBM Tioli System Automation Application Manager V3.1.0 WAS V6.1 upgrade for Linux on System x Linux on POWER IBM Tioli System Automation Application Manager V3.1.0 WAS V6.1 upgrade for Linux on POWER Linux on System z IBM Tioli System Automation Application Manager V3.1.0 WAS V6.1 upgrade for Linux on System z Electronic distribution: You can also obtain System Automation Application Manager and WebSphere Application Serer through electronic distribution. In this case, you can download the delierables from a URL you receie after purchasing the product. 6 System Automation Application Manager: Installation and Configuration Guide

23 Archies: The following tables list the archies that you need for installing the WebSphere Application Serer upgrade and the product itself. Windows: Table 3. Archies for Windows platforms Archie name Description C1A1XML.exe This is the archie you use to install the product. The archie is self-extracting. After extraction, the directory structure is identical to that on the corresponding CD. C1A24ML.exe The self-extracting archie contains the files that you need for installing the WebSphere Application Serer upgrade. After extraction, the directory structure is identical to that on the corresponding CD. AIX: Table 4. Archies for AIX platforms Archie name C1A1YML.bin C1A25ML.bin Description This is the archie you use to install the product. The archie is self-extracting. After extraction, the directory structure is identical to that on the corresponding CD. The self-extracting archie contains the files that you need for installing the WebSphere Application Serer upgrade. After extraction, the directory structure is identical to that on the corresponding CD. Linux on System x: Table 5. Archies for Linux on System x Archie name Description C1A2SML.tar This is the archie you use to install the product. To extract the archie GNU tar 1.13 or later is required. Use the tar -xf command to extract the files to a temporary directory. After extraction, the directory structure is identical to that on the corresponding CD. C1A26ML.tar The archie contains the files that you need for installing the WebSphere Application Serer upgrade. After extraction, the directory structure is identical to that on the corresponding CD. Linux on POWER: Table 6. Archies for Linux on POWER Archie name Description C1A1ZML.tar This is the archie you use to install the product. To extract the archie GNU tar 1.13 or later is required. Use the tar -xf command to extract the files to a temporary directory. After extraction, the directory structure is identical to that on the corresponding CD. C1A28ML.tar The archie contains the files that you need for installing the WebSphere Application Serer upgrade. After extraction, the directory structure is identical to that on the corresponding CD. Linux on System z: Chapter 2. Installing System Automation Application Manager 7

24 Table 7. Archies for Linux on System z Archie name Description C1A20ML.tar This is the archie you use to install the product. For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files to a temporary directory. After extraction, the directory structure is identical to that on the corresponding CD. C1A27ML.tar The archie contains the files that you need for installing the WebSphere Application Serer upgrade. After extraction, the directory structure is identical to that on the corresponding CD. DB2 setup options When planning for the installation of System Automation Application Manager, you must decide how you want to set up DB2 for the database that is required for System Automation Application Manager. You hae the following options: Local DB2 setup The DB2 serer is installed and runs on the same node on which System Automation Application Manager is installed. Remote DB2 setup The DB2 serer is installed and runs on a node other than that on which System Automation Application Manager is installed. In this case, you need to install a DB2 JDBC drier on the System Automation Application Manager node. Product requirements The following sections list the software and hardware requirements for System Automation Application Manager. Supported operating systems: The following table lists the operating systems that are supported for System Automation Application Manager: Table 8. Supported operating systems Operating system IBM System x 1 IBM System i IBM System p IBM System z Windows Serer 2003 Standard Edition (32-bit) x Windows Serer 2003 Enterprise Edition (32-bit) x Windows Serer Standard Edition (32-bit) x Windows Serer Enterprise Edition (32-bit) x AIX (AIX 5L Version 5.3) ML 4 x AIX x SUSE SLES 9 (32-bit) 5 x SUSE SLES 9 (64-bit) 6 x x x SUSE SLES 10 (32-bit) 5 x SUSE SLES 10 (64-bit) 6 x x x Red Hat RHEL 4.5 AS (32-bit) 5 x Red Hat RHEL 4.5 AS (64-bit) 6 x x x Red Hat RHEL 5.0 AS (32-bit) 5 x 8 System Automation Application Manager: Installation and Configuration Guide

25 Table 8. Supported operating systems (continued) Operating system IBM System x 1 IBM System i IBM System p IBM System z Red Hat RHEL 5.0 AS (64-bit) 6 x x x Notes: 1. IBM System x with IA32, EM64T, or AMD64 architecture. Any other systems with IA32, EM64T, or AMD64 architecture are also supported. Systems with IA64 architecture are not supported. All supported operating systems are also supported when running under VMWare. 2. Windows Serer 2008 installed as Serer Core or under Hyper-V is not supported. 3. APAR IY65979 must be installed. 4. AIX 6.1 supports Workload Partition (WPAR) mobility or relocation. In the V3.1 release, System Automation Application Manager do not support domains with nodes that are System WPARs. 5. The following Linux kernel architectures are supported for running with 32-bit: x86 on IBM System x 6. The following Linux kernel architectures are supported for running with 64-bit: ppc64 on IBM System i and IBM System p s390x on IBM System z is supported for some distributions Middleware software requirements: The following middleware software must be installed on the system on which System Automation Application Manager will run, before the component itself can be installed: DB2: A DB2 serer for a local DB2 setup or a DB2 JDBC drier for a remote DB2 setup WebSphere Application Serer (32-bit ersion) DB2 software prerequisites: Before you can install System Automation Application Manager, one of the following IBM DB2 UDB ersions must be installed on the system on which System Automation Application Manager will run: IBM DB2 Version 9.5, which is bundled with System Automation Application Manager, Version 3.1 IBM DB2 UDB Enterprise Serer Edition, Version or higher Software prerequisites for a local DB2 setup: If you are using a local DB2 setup, the end-to-end automation management database and the database tables are created by the installation program during the installation of System Automation Application Manager. Software prerequisites for a remote DB2 setup: Before you can install the automation manager and the operations console, the following software prerequisites must be manually installed: A DB2 JDBC drier must be installed on the System Automation Application Manager node: 1. Copy the DB2 JDBC drier files from the Jaa directory of your DB2 serer to the system where you install System Automation Application Manager. The name of the location/directory is at your discretion. 2. Make the location/directory accessible to WebSphere Application Serer and the System Automation Application Manager installation program. Chapter 2. Installing System Automation Application Manager 9

26 Supported Web browsers: The operations console is the user interface of System Automation Application Manager. It is displayed in a Web browser that connects to the WebSphere Application Serer on which the operations console is running. The Web browser may run on an arbitrary system. The following minimum leels of Web browsers are supported: Microsoft Internet Explorer V6.0 SP1 Mozilla V1.7.8 Firefox V1.5 For information on how the Web browser must be configured, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Configuring your Web browser". Hardware requirements: The following sections describe the hardware requirements for System Automation Application Manager. The description does not coer the hardware requirements that need to be satisfied for installing and running the required middleware software. For more information on hardware requirements for the required middleware software, refer to Installing the middleware software on page 12. Memory: 1.5 GB is required on the serer on which System Automation Application Manager is installed (for WebSphere Application Serer and System Automation Application Manager). TCP/IP connectiity: System Automation Application Manager consists of arious components that may run on one or seeral systems. For example: When you use a local DB2 setup without Websphere Application Serer the automation manager, the operations console, and the DB2 serer run on the same system (single-node setup). When you use a remote DB2 setup, or a local DB2 setup with Websphere Application Serer, System Automation Application Manager and the DB2 serer run on separate systems (multi-node setup). Be sure that TCP/IP connections can be established between the following components: the WebSphere Application Serer that is running the automation J2EE framework, the resource adapters, and the operations console the DB2 serer Disk space requirements: Disk space requirements on Windows systems: The following table lists the disk space requirements for System Automation Application Manager on Windows systems. Note that the table does not include the space required for the installation of the middleware software. Table 9. Disk space requirements on Windows systems Description Default directory Disk space System Automation Application Manager installation directory C:\Program Files\IBM\tsamp\eez 100 MB 10 System Automation Application Manager: Installation and Configuration Guide

27 Table 9. Disk space requirements on Windows systems (continued) Description Default directory Disk space Automation manager and operations console deployed in WebSphere Application Serer C:\Program Files\IBM\WebSphere\AppSerer 50 MB DB2 database C:\DB2 120 MB Temporary disk space needed for installation and installation log and response files The alue of the system ariable %TEMP% Typically, this is: C:\Documents and Settings\Administrator\Local Settings\Temp 125 MB Configuration file directory and policy pool directory of System Automation Application Manager Tioli Common Directory Installer registry C:\Program Files\IBM\tsamp\eez\cfg C:\Program Files\IBM\tsamp\eez\policyPool C:\Program Files\IBM\tioli\common\eez The Zero G Registry resides in the hidden directory: C:\Program Files\Zero G Registry\.com.zerog.registry.xml 1MB 250 MB 10 KB Disk space requirements on AIX and Linux systems: The following table lists the disk space requirements for System Automation Application Manager on AIX and Linux systems. Note that the table does not include the space required for the installation of the middleware software. Table 10. Disk space requirements on AIX and Linux systems Description Default directory Disk space Installation directory of System /opt/ibm/tsamp/eez 205 MB Automation Application Manager Automation manager and operations console deployed in WebSphere Application Serer AIX: /usr/ibm/websphere/appserer Linux: /opt/ibm/websphere/appserer 30 MB DB2 database db2inst1 120 MB Temporary disk space needed for installation and installation log and response files /tmp 125 MB Configuration file directory and policy pool directory of System Automation Application Manager /etc/opt/ibm/tsamp/eez/cfg /etc/opt/ibm/tsamp/eez/policypool Tioli Common Directory /ar/ibm/tioli/common/ 250 MB Installer registry /ar/.com.zerog.registry.xml 5KB 1MB Security concepts The following sections describe the security concepts for System Automation Application Manager. Security considerations: In a local DB2 setup, in which System Automation Application Manager and the external components needed for running (WebSphere Chapter 2. Installing System Automation Application Manager 11

28 Application Serer and DB2) are installed on the same system, you do not need to secure the connections between these components oer SSL. The external connections that will be established between the components listed below, howeer, should be secured oer SSL, especially if the external components are running in different security domains that are separated by firewalls. External connections will be established between the following components (the default port numbers are gien in brackets): The connection from the automation engine to the automation adapters (port 2001). The connection from the automation adapters to the automation engine(port 2002). Note that SSL is not supported for this connection. The connection between the Web browsers in which the operations console is displayed and Integrated Solutions Console (HTTP port 9060, HTTPS port 9043). User management: For information on how user IDs and passwords for end-to-end automation management are managed, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Managing users". Installing the middleware software Depending on the setup type you choose, middleware software has to be installed on one or more systems before System Automation Application Manager can be installed. For information on possible setup types, refer to DB2 setup options on page 8 For information on the required middleware software for each system, refer to Middleware software requirements on page 9 Contents of the middleware software CDs The middleware software CDs that are shipped with the System Automation Application Manager product CDs contain the following software products: IBM DB2 UDB Version 9.1 Enterprise Serer Edition (DB2 serer) The 32-bit ersion of IBM WebSphere Application Serer Base Version 6.1 Notes: 1. IBM Tioli System Automation Application Manager only supports the 32-bit ersion of WebSphere Application Serer. 2. In addition to a WebSphere Application Serer 6.1 CD for eery supported platform, a WebSphere Application Serer upgrade CD is aailable for each supported platform. The upgrade CD is needed for bringing WebSphere Application Serer to the required product leel. 3. Websphere Application Serer 6.1 Network Deployment is not supported. 4. Please note that the IBM Tioli Directory Serer is not contained on the middleware software CDs. Installing a DB2 serer DB2 serer requirements: Use the following publications to find out which requirements need to be met for installing and running a DB2 serer: IBM DB2 UDB - Quick Beginnings for DB2 Serers (GC ) IBM DB2 UDB - Release Notes - Version 9 12 System Automation Application Manager: Installation and Configuration Guide

29 The latest ersions of these publications are aailable on the IBM DB2 UDB Web site: You will find the link to the PDF manuals in the Other resources section on the Web page. In addition, check for the latest system requirements at The DB2 release notes can also be found on the CD labeled IBM DB2 UDB Enterprise Serer Edition Version 9.1 for your platform. Make sure that all requirements for installing and running a DB2 serer are met. Otherwise, System Automation Application Manager may not install or work properly. DB2 serer installation: You can use the DB2 Setup wizard to install the DB2 serer. You will find the DB2 Setup wizard on the CD labeled IBM DB2 UDB Enterprise Serer Edition Version 9.1 for your platform. The typical installation of a single-partition database enironment is recommended. On a Windows system, the following users must be local users: the DB2 administration serer user the fenced user the instance owner user You must create a DB2 instance before you install System Automation Application Manager. Make sure that the DB2 serer has the required ersion leel (see Middleware software requirements on page 9). Make a note of the following information for future reference: The host name of the system where the DB2 serer is installed. The port number of the DB2 instance The port number is displayed on the summary panel of the DB2 Setup wizard. The summary panel appears immediately before the wizard copies the program files. The name of the directory to which the DB2 serer is installed if a local DB2 setup is used The name and password of the instance owner user or of a different user who is authorized to drop and create databases and database tables, and to select, insert, delete, and update table rows. Note: See Chapter 7. Controlling database access in IBM DB2 UDB Administration Guide: Implementation, Version 9.1 (SC ) for information about DB2 serer security concepts and on how to authorize users to perform certain tasks. Post-installation tasks for remote DB2 setup: completed on the DB2 serer system: The following tasks must be Chapter 2. Installing System Automation Application Manager 13

30 Identify the DB2 instance that will hold the databases. Identify the instance owner user ID and password. Identify the host name of the DB2 serer system. Identify the TCP/IP port of the DB2 instance. Create the automation manager database (for information on how to do this, see below). Create the automation manager tables in the database (for information on how to do this, see below). Note: If the database has already been created and tables already exist, you must drop the existing tables before creating the tables. To use a remote database setup, the following JDBC drier files must be copied from the remote database to a directory on the local system where System Automation Application Manager will be installed: db2jcc.jar db2jcc_license_cu.jar The CD IBM Tioli System Automation Application Manager V3.1.0 for your platform contains scripts for creating the required databases and tables. Creating the automation manager database and the database tables: On Windows: Perform the following steps if your DB2 serer runs on a Windows system: 1. Log in with a user ID that has SYSADM priileges on the DB2 instance. 2. On the CD labeled IBM Tioli System Automation Application Manager V3.1.0 for Windows, change the directory to DDL\Script 3. From this directory, run the following two batch files: db2_create_automgr_db.bat <db_name> <instance_owner> <instance_pw> db2_create_reporting_tables.bat <db_name> <instance_owner> <instance_pw> where <db_name> is the desired name of the automation manager database (Example: EAUTODB) <instance_owner> is the instance owner user ID of the DB2 instance (Example: db2admin) <instance_pw> is the password of the instance owner user ID On AIX or Linux: Perform the following steps if your DB2 serer runs under Linux or AIX: 1. Log in as root. 2. On the CD labeled IBM Tioli System Automation Application Manager V3.1.0 for your operating system, change the directory to DDL/Script. 3. From this directory, run the following two shell scripts: db2_create_automgr_db.sh <db_name> <instance_owner> <instance_pwd> <script_directory> db2_create_reporting_tables.sh <db_name> <instance_owner> <instance_pwd> <script_directory> where <db_name> is the desired name of the automation manager database (Example: EAUTODB) <instance_owner> is the instance owner user ID of the DB2 instance (Example: db2inst1) 14 System Automation Application Manager: Installation and Configuration Guide

31 <instance_pwd> is the password of the instance owner user ID <script_directory> directory where the DB2 scripts for Tioli System Automation are located on the CD, which you changed to in step 2 (DDL/Script) Verifying the creation of the remote database: After running the scripts as described in Creating the automation manager database and the database tables on page 14, issue the following commands to erify that the remote database was created correctly: 1. su - db2inst1 2. db2 connect to <db_name> 3. db2 list tables for schema eautousr 4. db2 disconnect <db_name> The output of the list tables command should display the following table names: Table 11. Database tables EEZAUTOMATIONACCESS EEZAUTOMATIONRELATION EEZCOMMONEVENTS EEZDOMAINSUBSCRIPTION EEZOPERATORDOMAINFILTER EEZOPERATORDOMAINPREFERENCES EEZOPERATORHIDDENDOMAIN EEZRESOURCESUBSCRIPTION EEZSAFOSEVENTS Installing WebSphere Application Serer Before you begin: IBM Tioli System Automation Application Manager only supports the 32-bit ersion of WebSphere Application Serer. WebSphere Application Serer 6.1 Network Deployment is not supported. Installing WebSphere Application Serer from the CD "IBM WebSphere Application Serer Base Version 6.1" does not result in the required ersion leel. To obtain the required ersion leel , you must perform the following steps: 1. Install WebSphere Application Serer from the CD "IBM WebSphere Application Serer Base Version 6.1" or from the electronic deliery path from IBM. 2. Install the WebSphere Application Serer UpdateInstaller. 3. Use the UpdateInstaller to install the required fixes into WebSphere Application Serer Augment the application serer of your WebSphere Application Serer installation, or, preferably, augment eery serer profile into which you want to install System Automation Application Manager. These steps are described in the subsequent sections. Chapter 2. Installing System Automation Application Manager 15

32 WebSphere Application Serer requirements: Check the following publication to find out which requirements need to be met for installing and running WebSphere Application Serer Base: The ReadMe file, which is aailable on the product CD "IBM WebSphere Application Serer Base Version 6.1". The "Getting started" topics in the Information Center for IBM WebSphere Application Serer, Version 6.1. An IBM WebSphere Application Serer Getting started document is also aailable on the product CD for your platform, where it is also referred to as Installation Guide. Make sure that all requirements for installing and running WebSphere Application Serer are met. Otherwise, System Automation Application Manager may not work properly. The latest ersions of all WebSphere Application Serer publications can be found at In addition, check for the latest system requirements at Installing WebSphere Application Serer : You can use the WebSphere Application Serer installation wizard to install WebSphere Application Serer. The WebSphere Application Serer installation wizard can be started from the WebSphere Application Serer LaunchPad. You will find the LaunchPad on the CD labeled IBM WebSphere Application Serer Version 6.1 for your platform or from the electronic delierable for your platform (see Product CD and WebSphere Application Serer upgrade CD on page 6). The typical installation is recommended. Upgrading WebSphere Application Serer 6.1: Before you can install System Automation Application Manager ersion 3.1, you must upgrade WebSphere Application Serer 6.1 to leel , upgrade the WebSphere Jaa ersion to Jaa 5 Serice Release 6 and install the Adanced Edition of Integrated Solutions Console 7.1. To do so, you use the WebSphere Application Serer upgrade CD for your platform or from the electronic delierable for your platform (see Product CD and WebSphere Application Serer upgrade CD on page 6). The contents of the CD or the electronic delierable are listed in the following table. To install the packages from the CD or the electronic delierable, you first install the UpdateInstaller (see Installing the UpdateInstaller on page 17) and use it to install the remaining packages (see Installing the updates on page 17). 16 System Automation Application Manager: Installation and Configuration Guide

33 Table 12. Contents of the WebSphere Application Serer upgrade CD or electronic delierable Directory Contents Fixes The following update packages: WS-WAS-<your_platform>-FP pak Upgrades WebSphere Application Serer to leel WS-WASSDK-<your_platform>-FP pak Upgrades the Jaa ersion of WebSphere Application Serer to Jaa 5 Serice Release WS-WASFeature-FEISCAE7100.pak Installs the Adanced Edition of Integrated Solutions Console 7.1 README The readme file README.txt. Upgrade The UpdateInstaller zip file for your platform. Installing the UpdateInstaller: To install the UpdateInstaller perform these steps: 1. Unpack the update installer zip file for your platform to a temporary directory. Unzipping creates the directories JDK and UpdateInstaller. 2. Change to the UpdateInstaller directory. 3. On Linux and AIX use the command ls -al to check that the file install has execute permission. If the execute permission is not correctly set use the command chmod +x install to set it. 4. Inoke the file install to install the UpdateInstaller. When installed, the UpdateInstaller is located in the following directory by default: AIX: /usr/ibm/websphere/updateinstaller/update.sh Linux::/opt/IBM/WebSphere/UpdateInstaller/update.sh Windows: C:\Program Files\IBM\WebSphere\UpdateInstaller\update.bat 5. Optional: Delete the temporary directory. Installing the updates: You can install all updates with one inocation of the UpdateInstaller. If for any reason the UpdateInstaller does not install Fix Pack 15 first, remoe the installed packages and install Fix Pack 15 first. Augmenting the application serer of your WebSphere Application Serer installation: You need to augment the application serer of your WebSphere Application Serer installation, or, preferably, augment eery serer profile into which you want to install System Automation Application Manager. To do so, issue the following command (the example assumes that the profile name is AppSr01 and the serer name is serer1): <was_home>/bin/manageprofiles.sh -augment -templatepath <was_home>/profiletemplates/iscae71 -profilename AppSr01 -serername serer1 If the default path is used, <was_home> stands for: AIX: /usr/ibm/websphere/appserer/bin Linux: /opt/ibm/websphere/appserer Windows: C:\Program Files\IBM\WebSphere\AppSerer Considerations about user and group management: If you intend to configure WebSphere Application Serer to use a security product in read-only mode so that Chapter 2. Installing System Automation Application Manager 17

34 the WebSphere administratie interfaces to manage users and groups cannot be used, see Appendix G, Considerations about user and group management in WebSphere Application Serer, on page 213 for more information. Preparing for the installation of System Automation Application Manager Collecting the information you need to proide during installation On AIX, Linux and Windows systems the installation of System Automation Application Manager is wizard-drien. The wizard guides you through the installation and prompts you for installation and configuration parameters. The following tables list the parameters you need to specify on the installation wizard panels, in the order in which they must be specified. Make sure that you specify all required parameters on the installation wizard panels and that your entries are correct. The installation wizard does not erify that your entries are correct and complete during the installation. Installation directory and Tioli Common Directory: following table must always be specified. The parameters listed in the Table 13. Installation directory and Tioli Common Directory Parameter Description Default Installation directory name The directory to which the installable features are installed. In this guide, this directory is referred to as EEZ_INSTALL_ROOT. When specifying a directory other than the default, obsere the following restrictions: Windows: The directory name has to consist of the platform-specific path separator character and alphanumeric characters (A..Z, a..z, 0..9). The colon character is allowed only once, immediately following the drie letter. For example, C:\<directory_name> is allowed, but C:\<directory_name>:<directory_name> is not allowed. The space character and the underscore character (_) are allowed. AIX, Linux: The directory name has to consist of the platform-specific path separator character and alphanumeric characters (A..Z, a..z, 0..9). The underscore character (_) is allowed. The space and colon characters are not allowed. Windows: C:\Program Files\IBM\tsamp\eez AIX, Linux: /opt/ibm/tsamp/eez 18 System Automation Application Manager: Installation and Configuration Guide

35 Table 13. Installation directory and Tioli Common Directory (continued) Parameter Description Default Tioli Common Directory The Tioli directory for storing sericeability information. During installation, you are only prompted for input when no Tioli Common Directory is found on the system. In the Tioli Common Directory, the subdirectory eez is created for storing product-specific data. In this guide, this directory is referred to as Tioli_Common_Directory. When specifying a directory other than the default, obsere the following restrictions: Windows: The directory name has to consist of the platform-specific path separator character and alphanumeric characters (A..Z, a..z, 0..9). The colon character is allowed only once, immediately following the drie letter. For example, C:\<directory_name> is allowed, but C:\<directory_name>:<directory_name> is not allowed. The space character and the underscore character (_) are allowed. AIX, Linux: The directory name has to consist of the platform-specific path separator character and alphanumeric characters (A..Z, a..z, 0..9). The underscore character (_) is allowed. The space and colon characters are not allowed. Windows: C:\Program Files\IBM\tioli\common AIX, Linux: /ar/ibm/tioli/common Installation parameters for DB2: Note: When you hae a local DB2 setup but do not want the installation wizard to create the end-to-end automation management database and the database tables, just select the radio button for remote DB2 setup (IBM DB2 UDB on different system (remote)) on the Database Serer window of the installation wizard. If you make this selection, the installation wizard will neither create the database nor any tables and you are free to set up the database manually as you would for remote setup. The parameters listed in the following table must be specified. Chapter 2. Installing System Automation Application Manager 19

36 Table 14. DB2 data for local and remote DB2 setup Parameter Description Default DB2 UDB directory The installation location of the DB2 client directory. The location is detected on your system and displayed as the default directory. DB2 instance host name DB2 instance port number Database instance owner name If you are using a local DB2 setup, you use the DB2 client that is part of the DB2 serer installation. In this case, you need to specify the DB2 serer directory. Remote DB2 setup: The host name of the DB2 instance in which the automation manager and operations console databases are located. The port number of the DB2 instance in which the automation manager and operations console databases are located. Note: When you install System Automation Application Manager on AIX or Linux systems the installation wizard can retriee the alid DB2 instance port number automatically. If you choose not to use this function, or are installing on Windows systems, the port number will be displayed in the entry field on the corresponding installation wizard panel. This is the default port number that is assigned to DB2 during the installation of DB2. Howeer, if this port is not free, a different port number is assigned automatically, which is why you need to check if the default port number is correct. How you determine the correct port number is described in Determining the correct DB2 port number on page 199. The instance owner user ID of the DB2 instance in which the automation manager and operations console databases are located. In a local DB2 setup, this user ID will be used for creating the databases and tables. In a remote DB2 setup, the database and the tables must hae already been created. The installation program does no change to DB2 and neither creates a DB nor tables. The user ID will be used by WebSphere Application Serer to connect to the automation manager and operations console databases and to select, insert, delete, and update rows in tables Windows: db2admin AIX, Linux: db2inst1 20 System Automation Application Manager: Installation and Configuration Guide

37 Table 14. DB2 data for local and remote DB2 setup (continued) Parameter Description Default Database instance owner password DB2 UDB JDBC drier path on local system Automation manager database Backend ersion The password for the instance owner user ID of the DB2 instance in which the automation manager and operations console databases are located. For remote DB2 setup only: Path to the directory where the files DB2 JDBC are located. Automation manager database for use by WebSphere Application Serer. In a local DB2 setup, a database with this name will be created in the DB2 instance related to the specified instance owner. In a remote DB2 setup, a database with this name must already exist in the remote DB2 instance. Version of the back end DB2: ZOSUDB81: DB2 UDB V8.1 - running on z/os ZOSUDB91: DB2 UDB V9.1 - running on z/os DIST: DB2 UDB - running on distributed system No default alue is proided EAUTODB If an automation manager database (EAUTODB) from an earlier installation already exists, the database will be dropped without warning during the installation of System Automation Application Manager. To presere the data from the earlier installation, you can export the data before starting the installation and import it during the installation. For information on exporting the data from the database, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page 197. DB2_OPTN_UDB WebSphere Application Serer installation parameters: The parameters listed in the following table are detected during the installation of System Automation Application Manager. Note that WebSphere Application Serer administratie security must be enabled before you install System Automation Application Manager. Table 15. WebSphere Application Serer installation parameters Parameter Description Default WebSphere Application Serer directory WebSphere Application Serer (WAS) profile name WebSphere Application Serer (WAS) serer name The installation location of WebSphere Application Serer. There must be exactly one installation of WebSphere Application Serer on your system. The WebSphere Application Serer profile to be used for the automation manager and the operations console. The serer to be used for the automation manager. The location is detected on your system and displayed as the default directory. All existing profiles are detected on your system and displayed in a single-choice list. The serer name is detected on your system and displayed as default alue. Chapter 2. Installing System Automation Application Manager 21

38 Table 15. WebSphere Application Serer installation parameters (continued) Parameter Description Default WAS Admin User ID The user ID of the WebSphere No default alue is proided. Application Serer administrator. WAS Admin User Password The password of WebSphere Application Serer administrator user ID. No default alue is proided. IBM Tioli Enterprise Console connection configuration data: Optionally, you can use Tioli Enterprise Console for monitoring end-to-end automation management eents. The parameters listed in the following table are only required if you will be utilizing Tioli Enterprise Console for end-to-end automation management. Table 16. Installation parameters for IBM Tioli Enterprise Console Parameter Description Default TEC host name The name of the host where the Tioli Enterprise Console serer localhost is installed. TEC serer port number The port number for the Tioli Enterprise Console serer 5529 For more information about utilizing Tioli Enterprise Console for end-to-end automation management, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using Tioli Enterprise Console with System Automation Application Manager" Name of the end-to-end automation domain: Table 17. End-to-end automation domain name Parameter Description Default Automation domain name The name of the end-to-end automation domain represented by this instance of the automation engine. The domain name must be unique and may not be used for any other automation domain. The characters used for the domain name are limited to the following ASCII characters: A Z, a z, 0 9,. (period), and _ (underscore). FriendlyE2E WebSphere Application Serer user ID for the end-to-end automation engine The end-to-end automation engine requires a WebSphere Application Serer user ID to access the J2EE framework. The user ID is created during the installation of System Automation Application Manager. In the installation wizard on AIX, Linux and Windows systems you need to specify the user ID and the password. Table 18. WebSphere Application Serer user ID Parameter Description Default User ID WebSphere Application Serer user ID for the end-to-end eezdmn automation engine. Password Password of the user ID 22 System Automation Application Manager: Installation and Configuration Guide

39 System Automation Administrator user ID During the installation of System Automation Application Manager, the initial Tioli System Automation administrator user is created in WebSphere Application Serer and authorized for all tasks and actions that can be performed from the System Automation operations console. In the installation wizard you need to specify the data listed in the following table: Table 19. System Automation Administrator user ID Parameter Description Default User ID User ID of the System Automation operations console eezadmin administrator Password Password of the user ID none First and last name of the user User name none What the installation media contains System Automation Application Manager can be ordered from IBM as a media pack or downloaded as an Electronic Software Distribution (ESD) image from an IBM software distribution download site. There are multiple CDs for each supported platform. This is what the CD labeled IBM Tioli System Automation Application Manager V3.1.0 for <operating_system_name> contains: The files for launching the installation wizard The readme file Directories containing the files required to install components that are embedded into the System Automation Application Manager installation. These are: Table 20. Directories on the product CD Directory Content README For example, copyright notices and license agreements license License key DDL Scripts for creating DB2 databases and tables when remote DB2 setup is used ECExtension setup.jar <PLATFORM>¹ Product installer and files needed for installing the product DOCS Documentation Note: 1. <PLATFORM> is one of the following: AIX PPC (Linux on POWER) Windows i386 (Linux on System x) S390 (Linux on System z) Languages supported by System Automation Application Manager In addition to English, System Automation Application Manager supports the following languages: Chapter 2. Installing System Automation Application Manager 23

40 German Spanish French Italian Japanese Korean Brazilian Portuguese Simplified Chinese Traditional Chinese Installation prerequisites The following prerequisites must be satisfied before you can start the installation wizard for System Automation Application Manager: The 32-bit ersion of WebSphere Application Serer must be installed as described in Installing WebSphere Application Serer on page 15. No other WebSphere Application Serer product installation must exist on the system. A DB2 serer must be installed as described in Installing a DB2 serer on page 12. The DB2 serer instance must be running and accepting client connections. For more information on setting up the DB2 enironment refer to IBM DB2 UDB Administration Guide: Implementation. If an automation manager database (EAUTODB) from an earlier installation already exists, for example, if you are upgrading from IBM Tioli System Automation 2.2 to 3.1, in which case you need to uninstall the older ersion before installing the new, the database will be dropped without warning during the installation of System Automation Application Manager. To presere the data from the earlier installation, you can export the data before starting the uninstallation, and import it during the installation. For information on exporting the data before uninstalling, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page 197. In the current Red Hat 5 distributions, the SElinux enironment is switched on by default. It must be switched off for System Automation Application Manager to work properly. The user ID that is used to run the installer for System Automation Application Manager must hae administrator authority. On Linux and AIX, this user ID is typically root. On Windows this is the built-in local Administrator user account of the system. When installing System Automation Application Manager to an AIX or Linux system, you must ensure that an X Window session is aailable for displaying the graphical installation wizard panels. On Windows Serer 2008 you must install, configure, run and use the operations console with the built-in local Administrator user account of the system. If User Account Control (UAC) is actie on the system (this is the default alue) you must keep the default settings: User Account Control: Admin Approal Mode for the Built-in Administrator account disabled User Account Control: Detect application installations and prompt for eleation enabled. 24 System Automation Application Manager: Installation and Configuration Guide

41 Installing System Automation Application Manager using the installation wizard This section describes how to install System Automation Application Manager. For the installation, you use a graphical installation program, the so-called installation wizard. The required steps are described below. On the panels of the installation wizard, enter the data you hae collected using the lists in section Collecting the information you need to proide during installation on page 18. Make sure that you specify all required parameters on the installation wizard panels and that your entries are correct. The installation wizard does not erify that your entries are correct and complete during the installation. Notes: 1. The installation wizard panels in this section show an installation on an AIX system. The wizard panels that are displayed during the installation on other operating systems are ery similar. Make sure to conform to the conentions of your platform when specifying directory locations and file names. 2. In this section, only those panels are depicted on which user actions are required. 3. The installation comprises these phases: a. In the pre-installation phase, you specify the installation parameters. b. The installation phase begins when you click the Install button on the last pre-installation panel. In this phase, all files are installed to the disk. c. The configuration step, in which the necessary WebSphere Application Serer and DB2 configuration is performed. The configuration step can be canceled at any time. The installation can be resumed by simply calling the installer again. To install System Automation Application Manager, perform these steps: 1. Make sure that all installation prerequisites are met (refer to Installation prerequisites on page 24). 2. Insert the following CD into the CD drie: IBM Tioli System Automation Application Manager V3.1.0 There are multiple CDs. Be sure to use the one for your platform. If you are using electronic distribution switch to the appropriate archie. 3. Change to the directory that contains the installation program. For the location of the directory, refer to Packaging on page Launch the installation wizard by starting the following program from the current working directory: Windows: setup.exe To generate a response file for use in a silent installation, use the following command to launch the wizard: setup.exe -Dpreparesilent=true AIX, Linux: setup.bin To generate a response file for use in a silent installation, use the following command to launch the wizard: setup.bin -Dpreparesilent=true Chapter 2. Installing System Automation Application Manager 25

42 When the installation wizard is ready, the initial wizard window appears: 5. Select the language in which the text on the wizard panels is to appear and click OK. The language in which System Automation Application Manager is installed is deried from the system's locale setting. 6. The next panel displayed is the Introduction panel. Read the information on this panel and click Next to proceed. 7. The Software License Agreement follows. Carefully read the terms of the license agreement, and also make sure to read the non-ibm terms by clicking the Read non-ibm terms button. 26 System Automation Application Manager: Installation and Configuration Guide

43 To accept the terms of the license agreement, select I accept both the IBM and the non-ibm terms and click Next. 8. Specify the directory where you want to install System Automation Application Manager or accept the default location. Click Next. 9. If the installation program detected a Tioli Common Directory on your system, for example, because a Tioli product is already installed, the directory must also be used for System Automation Application Manager. In this case, the entry field on the panel is write-protected. If the installation program did not detect a Tioli Common Directory on your system, accept the default location or specify the directory to which the Tioli log files are to be written. Click Next. Chapter 2. Installing System Automation Application Manager 27

44 10. Select the DB2 setup type you are using and click Next. Which panel appears next, depends on the type of DB2 setup you selected: Local DB2 setup: Proceed with step 11. Remote DB2 setup: Proceed with step 14 on page This panel only appears when you are using a local DB2 setup. Specify the database name or accept the default name and click Next. Note that an existing EAUTODB will be dropped automatically without warning (for information on presering existing data, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page 197). 28 System Automation Application Manager: Installation and Configuration Guide

45 12. This panel only appears when you are using a local DB2 setup. Specify the name and password of the DB2 instance owner and click Next. 13. This panel only appears when you are using a local DB2 setup. In the field DB2 instance port number, the alid port number must be specified: If the DB2 port number was retrieed automatically, the alid port number is displayed in the field. If the DB2 port number was not retrieed automatically, the default port number (50000) is displayed. The actual DB2 port number may differ from the default, because a different port number is assigned automatically during DB2 installation if the default port is not free. Before you accept the default alue, ensure that it is correct, or specify the alid port number. Chapter 2. Installing System Automation Application Manager 29

46 Click Next and proceed with step 16 on page 31. Note: After you click Next, the installation program checks whether the database can be accessed with the alues you specified on the panel. If you want to skip the check, select the check box on the panel. 14. This panel only appears when you are using a remote DB2 setup. Specify the database name (see Post-installation tasks for remote DB2 setup on page 13), select the DB2 Backend ID type that matches the remote DB2 database platform and ersion that has to be used by this installation of SA Application Manager, and click Next. 15. This panel only appears when you are using a remote DB2 setup. 30 System Automation Application Manager: Installation and Configuration Guide

47 Specify the path to the DB2 UDB JDBC drier or click Choose to select the directory (see Post-installation tasks for remote DB2 setup on page 13), and specify the name and password of the database instance owner. Click Next. 16. If you want to import existing data into the new end-to-end automation database, select the Import data check box and specify the fully qualified directory name in which the exported data is located. For information on how to export data from an existing end-to-end automation database in such a way that it is ready for import, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page The installation directory of WebSphere Application Serer is detected on your system and displayed. Click Next. Chapter 2. Installing System Automation Application Manager 31

48 18. The existing WebSphere Application Serer profiles are detected on your system and displayed. Select the profile you want to use and click Next. 19. Specify the end-to-end automation domain name you want to use or accept the default name and click Next. Note: Accept the default domain name ( FriendlyE2E ) if you want to use the sample System Automation Application Manager enironment to familiarize yourself with end-to-end automation management and the operations console. For more information, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Getting started". 32 System Automation Application Manager: Installation and Configuration Guide

49 20. If you want to use Tioli Enterprise Console to display end-to-end automation management eents: Select Enable TEC serer connection In the field TEC host name, specify the host name of the console serer. In the field TEC serer port number, specify the port number of the console serer: Windows: Accept the default alue that is displayed in the field (5529) AIX/Linux: Set the alue to 0 Click Next. Note: You can also enable the connection from the WebSphere Application Serer administratie console after the installation of System Automation Application Manager is complete. This is described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide, in the section "Using Tioli Enterprise Console with System Automation Application Manager". Chapter 2. Installing System Automation Application Manager 33

50 21. To enable report data collection tick the box in the next panel. 22. If the System Automation Application Manager Distributed Disaster Recoery feature is supported on this platform this panel appears. 34 System Automation Application Manager: Installation and Configuration Guide

51 If you want to connect the Automation Manager to GDPS: Select Enable GDPS serer connection In the field GDPS serer host name, specify the TCP/IP host name of the GDPS controlling system (also known as the K system ). In the field GDPS serer port number, specify the TCP port number configured for the NetView Eent/Automation Serice (E/AS) address space that is running on the GDPS controlling system. If you want to enable a connection to a backup GDPS controlling system: Select Enable GDPS backup serer connection In the field GDPS serer host name, specify the TCP/IP host name of your backup GDPS controlling system. In the field GDPS serer port number, specify the TCP port number configured for the NetView Eent/Automation Serice (E/AS) address space that is running on the backup GDPS controlling system. Click Next. Note: You can also enable or modify the GDPS connection from the WebSphere Application Serer administratie console after the installation of System Automation Application Manager is complete. This is described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide, in the section "Configuring the JMS destination for GDPS eents after installation". 23. Specify the WebSphere Application Serer user ID and password for the end-to-end automation engine. The automation engine will use the credentials for accessing the J2EE framework that runs in WebSphere Application Serer. Chapter 2. Installing System Automation Application Manager 35

52 24. Specify the user ID, password, and the first and last name of the System Automation administrator. Do not use cut-and-paste to enter the password and the password confirmation, rather, directly type in the password and the password confirmation. Note: You are recommended not to choose the same name for both the System Automation administrator user ID and the WAS administrator user ID, as this will lead to problems if you later uninstall IBM Tioli System Automation Application Manager. For example, specifying eezadmin or wasadmin for both users is not recommended. Click Next. 36 System Automation Application Manager: Installation and Configuration Guide

53 25. When you hae specified all the required information on the wizard panels, a summary panel appears. As the installation wizard will not check the aailable space, be sure to erify that sufficient space is aailable in the file system. Click Install to start the installation. The installation can take one or two hours to complete. 26. While the component is being installed and configured, a number of information panels inform you of the progress. 27. When the installation of System Automation Application Manager is complete, the Installation Complete panel appears. Click Done to close the installation wizard. For information on erifying the installation, refer to Verifying the installation on page 63. Chapter 2. Installing System Automation Application Manager 37

54 Installing System Automation Application Manager in silent mode You can install System Automation Application Manager in silent mode, using a response file you generated in a wizard-drien installation (see Installing System Automation Application Manager using the installation wizard on page 25. After the wizard-drien installation is complete, you will find the response file install.properties in the following directory: <EEZ_INSTALL_ROOT>/install Note that this file is always generated, een if you did not specify the option -Dpreparesilent=true when you inoked the installation wizard. Howeer, install.properties files created without the -Dpreparesilent=true option cannot be used for silent installation. To perform a silent installation, perform these steps: 1. Copy the response file install.properties file to the system on which you want to perform the silent installation. 2. To start the installation, issue this command: Windows: setup.exe -i silent -f <fully_qualified_properties_file_name> AIX, Linux: setup.bin -i silent -f <fully_qualified_properties_file_name> Installing System Automation Application Manager on z/os Planning for installation This chapter contains the information you need to prepare for the installation of System Automation Application Manager on z/os. System Automation Application Manager for z/os is distributed ia tape and is installed using SMP/E. The prerequisite list and the detailed installation instructions can be found in the Program Directory shipped with the tape. Product components The component structure of System Automation Application Manager on z/os is the same as on other platforms and is described in Product components on page 5. Product requirements The following sections list the software and hardware requirements for System Automation Application Manager for z/os. Supported operating systems: z/os 1.7 or later is required. Middleware software requirements: The following middleware software must be installed on the system on which System Automation Application Manager for z/os will run, before the component itself can be installed: DB2: A DB2 serer for a local DB2 setup or a DB2 JDBC drier for a remote DB2 setup WebSphere Application Serer ISC AE 7.1. This component can be downloaded from URL 38 System Automation Application Manager: Installation and Configuration Guide

55 z/os System Image Supported Websphere Topologies on z/os: This section describes possible topologies of the installation of System Automation Application Manager on z/os. System Automation Application Manager running in base WebSphere setup: This scenario describes one way of configuring WebSphere Application Serer for z/os in a similar manner to WebSphere Base on distributed platforms. One application serer instance is setup on one z/os System Image as an 'unmanaged serer', in which the System Automation Application Manager is installed together with the operations console policy editor and the reporting feature. Cell CR Daemon Node End-to-end Automation Manager App serer CR SR Browser client MQ Db2 TCR Automation engine CICS Hardware adapter Command shell HFS Figure 3. WebSphere scenario - base The Automation Engine (eezdmn), Hardware Adapter and End-to-End command shell are installed on the same z/os system, together with some required TCR components. In this scenario the Browser Client is connecting to the Application Serer instance to open the operations console or to edit policies. The Application Serer is not managed by any deployment manager. Chapter 2. Installing System Automation Application Manager 39

56 You can install the System Automation Application Manager in this way by choosing the setup option BASE in the ATVDOPTS member controlling the generation of the post installation jobs. System Automation Application Manager running as highly aailable in a mixed WebSphere setup: This scenario describes how to install the System Automation Application Manager on more than one z/os system image, for example to make it highly aailable with the help of System Automation for z/os. The System Automation Application Manager does not support WebSphere clustering, so if you want to keep high aailability and install the System Automation Application Manager on more than one z/os system image you must choose the base WebSphere setup and install the System Automation Application Manager on each system image. A deployment manager cannot be used to administer these unmanaged serers. Administration must be performed separately on each z/os system image. On each system you must define a cell to host one application serer for the Application Manager. In this scenario the browser client connects to the application serer, and not to the deployment manager, in order to open the SA operations console. Figure 4. WebSphere scenario - HA Although the System Automation Application Manager only supports a base WebSphere setup, if you choose to make it highly aailable it is still possible to hae an ND setup for other managed application serers running other JEE workload on different system images, as shown in Figure 4. Supported Web browsers: The operations console is the user interface of System Automation Application Manager. It is displayed in a Web browser that connects to the WebSphere Application Serer on which the operations console is running. The Web browser may run on an arbitrary system. 40 System Automation Application Manager: Installation and Configuration Guide

57 The following minimum leels of Web browsers are supported: Microsoft Internet Explorer V6.0 SP1 Mozilla V1.7.8 Firefox V1.5 For information on how the Web browser must be configured, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Configuring your Web browser". Hardware requirements: The following sections describe the hardware requirements for System Automation Application Manager for z/os. The description does not coer the hardware requirements that need to be satisfied for installing and running the required middleware software. TCP/IP connectiity: System Automation Application Manager consists of arious components that may run on one or seeral systems. For example: When you use a local DB2 setup without Websphere Application Serer the automation manager, the operations console, and the DB2 serer run on the same system (single-node setup). When you use a remote DB2 setup, or a local DB2 setup with Websphere Application Serer, System Automation Application Manager and the DB2 serer run on separate systems (multi-node setup). Be sure that TCP/IP connections can be established between the following components: the WebSphere Application Serer that is running the automation J2EE framework, the resource adapters, and the operations console the DB2 serer Maximum number of serer instances:: For System Automation Application Manager you cannot run multiple WebSphere Application Serer instances in parallel. To erify the configuration, open the WebSphere administratie console and naigate to Serers > Application serers > serer1. On the Configuration tab go to the Serer Infrastructure area and select Jaa and Process Management > Serer Instance. Ensure that the checkbox Multiple Instances Enabled is not selected, and that the alues for both Minimum Number of Instances and Maximum Number of Instances are set to 1. Disk space requirements: The installation disk space requirements for System Automation Application Manager on z/os systems are listed in the Program Directory supplied with the installation tape. In addition seeral directories are created post-installation. The following table lists the disk space requirements for these directories. Table 21. Additional disk space requirements on z/os systems Description Default directory Disk space Installation directory of System Automation Application Manager /local/eez Note: This directory name can be chosen during installation. 10 MB Tioli Common Directory /ar/ibm/tioli/common/ 300 MB Configuration file directory of System Automation Application Manager /etc/eez Note: This directory name can be chosen during installation. 10 MB Chapter 2. Installing System Automation Application Manager 41

58 DB2 setup options When planning for the installation of System Automation Application Manager, you must decide how you want to set up DB2 for the database that is required for System Automation Application Manager. You hae the following options: Local DB2 setup The DB2 serer is installed and runs on the same node on which System Automation Application Manager is installed. Remote DB2 setup The DB2 serer is installed and runs on a node other than that on which System Automation Application Manager is installed. In this case, you need to install a DB2 JDBC drier on the System Automation Application Manager node. Regardless of the DB2 setup option you use, perform the following actions: 1. Make sure all stored procedures and tables for JDBC support are installed to DB2 as described in the DB2 for z/os Installation Guide. These stored procedures and tables are usually installed during DB2 installation. If you hae omitted to install them, you need to customize and run the DB2 installation Job DSNTIJMS. 2. Bind the DB2 packages that are used at the database serer and grant EXECUTE authority on the packages to PUBLIC by using the DB2Binder utility as described in the DB2 for z/os Installation Guide. Security concepts The following sections describe the security concepts for System Automation Application Manager. Security considerations: In a local DB2 setup, in which System Automation Application Manager and the external components needed for running (WebSphere Application Serer and DB2) are installed on the same system, you do not need to secure the connections between these components oer SSL. The external connections that will be established between the components listed below, howeer, should be secured oer SSL, especially if the external components are running in different security domains that are separated by firewalls. External connections will be established between the following components (the default port numbers are gien in brackets): The connection from the automation engine to the automation adapters (port 2001). The connection from the automation adapters to the automation engine (port 2002). Note that SSL is not supported for this connection. The connection between the Web browsers in which the operations console is displayed and Integrated Solutions Console (HTTP port 9060, HTTPS port 9043). User management: For information on how user IDs and passwords for end-to-end automation management are managed, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Managing users". 42 System Automation Application Manager: Installation and Configuration Guide

59 Preparing for the installation of System Automation Application Manager Collecting the information you need to proide during installation On z/os the installation of System Automation Application Manager is drien by an Install Options file. You must add the installation and configuration parameters to the Install Options file using an editor. This file is then used by the installation process to propagate the parameters to the installation jobs. You are recommended to sae the original file. The following tables list the parameters you can specify in the Install Options file. Parameters marked with Y in the column Req are required; the others are optional. CR in this table means that this parameter is conditionally required if some other parameter is set to a specific alue. Installation directory: be specified. The parameters listed in the following table must always Table 22. Installation directory and Tioli Common Directory Parameter Req Name Description Default Installation directory prefix EEZ_PREFIX_RUNTIME The high leel qualifier of the directory to which the installable features are installed. The installation directory path (runtime path) will be generated by using the contents of this option appended by a fixed product section /eez. This generated path name will be used as the mount point for your runtime HFS specified in the option JCL_NAME_RUNTIME_HFS. Using the default alue will generate a default runtime path of /local/eez. /local In this guide, this directory is referred to as EEZ_INSTALL_ROOT. SMP/E Installation directory prefix EEZ_PREFIX_SMPE Specify with this option the prefix which was used during the SMP/E installation of the product. / Target directory of links to application manager commands The SMP/E installation path will be generated by appending a fixed product section /usr/lpp/eez to the alue of this option. Y EEZ_PATH_BIN Location for symbolic links to all binaries required by the Application Manager. This must be a directory in the user's path. Example: /local/bin none Chapter 2. Installing System Automation Application Manager 43

60 Table 22. Installation directory and Tioli Common Directory (continued) Parameter Req Name Description Default Directory of application manager configuration files Automation Manager Host Name EEZ_PREFIX_CONFIG Specify with this option the prefix used to create the configuration path structure of the product. The Configuration path name will be generated by using the contents of this option EEZ_PREFIX_CONFIG appended by a fixed product section /etc/eez. This is the location of product configuration and properties files. Using the default alue of option EEZ_PREFIX_CONFIG will generate a default configuration path of /etc/eez. Y EEZ_NAME_HOST Specify with this option the name of the system hosting the application manager. Example: "tstsaam.boeblingen.de.ibm.com" / none General installation parameters: installation on z/os. These parameters can be used to tailor the Table 23. General installation parameters Parameter Req Name Description Default SBPXEXEC Prefix JCL_PREFIX_SBPXEXEC Use this option to specify the installation prefix of the z/os system data set SBPXEXEC. SYS1 Installation parameters for DB2: must be specified. The parameters listed in the following table Table 24. DB2 data for local and remote DB2 setup Parameter Req Name Description Default DB2 database name Y DB2_NAME_DATABASE Name of the database in the DB2 uniersal data source profile. Using the DB2 administration utility this is the alue you find under the description DB2 location none 44 System Automation Application Manager: Installation and Configuration Guide

61 Table 24. DB2 data for local and remote DB2 setup (continued) Parameter Req Name Description Default DB2 program name DB2_NAME_PROGRAM Name of the DB2 program to execute SQL statements. DB2 proides sample programs that many users find helpful as productiity aids. These programs are shipped as source code, so you can modify them to meet your needs. DSNTIAD is a sample dynamic SQL program that is written in assembler language. With this program, you can execute any SQL statement that can be executed dynamically except a SELECT statement. For more information see DB2 Uniersal Database for z/os Utility Guide and Reference. DSNTIAD DB2 plan name CR DB2_NAME_PLAN Name of the DB2 plan. This parameter is required if DB2_OPTN_UDB=ZOSUDBxx DB2 storage group name DB2_NAME_STOGROUP Name of a storage group on the current serer to allocate table spaces and index spaces from identified olumes. DB2 dataset qualifier CR DB2_NAME_VCAT Identifies the integrated catalog facility catalog for the storage group. You must define an alias if the name of the integrated catalog facility catalog is longer than 8 characters. Select a alue for DB2_NAME_VCAT that is not used by other DB2 subsystems. Using the DB2 administratie Utility you can find a list of VCAT alues if you select option DB2 system catalog, then option Storage groups. This parameter is required if DB2_OPTN_UDB=ZOSUDBxx. none EEZGROUP none Example: "DSN821" DB2 olume name DB2_NAME_VOLUMES Defines the olumes to create a DB2 storage group. DB2 buffer pool name CR DB2_NAME_BUFFERPOOL This parameter is required if DB2_OPTN_UDB=ZOSUDBxx. ( * ) none Example: "BP2" Chapter 2. Installing System Automation Application Manager 45

62 Table 24. DB2 data for local and remote DB2 setup (continued) Parameter Req Name Description Default DB2 steplib CR DB2_DSN_STEPLIB Use this option to specify the MVS load library of the DB2 SQL interface program DSNTIAD. This parameter is only required if your DB2 is running on a z/os System (Option DB2_OPTN_UDB=ZOSUDBxx), and the program could not be fetched from the LINKLIST concatenation. Specify either the data set name of the steplib or the keyword LLA. none Example: "SYS1.V810.SDSNLOAD" DB2 UDB directory Y DB2_PATH_INSTALL The installation location of the DB2 client directory. none DB2 instance host name DB2 instance port number If you are using a local DB2 setup, use the DB2 client that is part of the DB2 serer installation. In this case you must specify the DB2 serer directory. Example: "/local/db2/db28/jcc/ classes" Y DB2_NAME_HOST The host name of the DB2 instance in which the automation manager and operations console databases are located. Example: "tstsaam.boeblingen.de.ibm.com" Y DB2_PORT_NUMBER The port number of the DB2 instance in which the automation manager and operations console databases are located. Using the DB2 administratie utility this is the alue you find with description IP-Port. Example: "5130" none none 46 System Automation Application Manager: Installation and Configuration Guide

63 Table 24. DB2 data for local and remote DB2 setup (continued) Parameter Req Name Description Default Database instance owner name Y DB2_USER_INSTANCE The instance owner user ID of the DB2 instance in which the automation manager and operations console databases are located. In a local DB2 setup, this user ID will be used for creating the databases and tables. In a remote DB2 setup, the database and the tables must hae already been created. The installation program makes no change to DB2 and creates neither a database nor tables. none Database instance owner password This user ID will be used by WebSphere Application Serer to connect to the automation manager and operations console databases and to select, insert, delete and update rows in tables. Y DB2_PWRD_INSTANCE The password for the instance owner user ID of the DB2 instance in which the automation manager and operations console databases are located. DB2 Subsystem ID CR DB2_NAME_DSN_SYSTEM Using the DB2 administratie utility this is the alue of your chosen DB2 subsystem ID (SSID). none The parameter is required if DB2_OPTN_UDB=ZOSUDBxx. Example: "SDT1" Chapter 2. Installing System Automation Application Manager 47

64 Table 24. DB2 data for local and remote DB2 setup (continued) Parameter Req Name Description Default Automation manager database DB2_NAME_EAUTODB Automation manager database for use by WebSphere Application Serer. In a local DB2 setup, a database with this name will be created in the DB2 instance related to the specified instance owner. In a remote DB2 setup, a database with this name must already exist in the remote DB2 instance. Backend ersion Y DB2_OPTN_UDB Version of the back end DB2: ZOSUDB81: DB2 UDB V8.1 - running on z/os ZOSUDB91: DB2 UDB V9.1 - running on z/os DIST: DB2 UDB - running on distributed system EAUTODB If an automation manager database (EAUTODB) from an earlier installation already exists, the database will be dropped without warning during the installation of System Automation Application Manager. To presere the data from the earlier installation, you can export the data before starting the installation and import it during the installation. For information on exporting the data from the database, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page 197. none WebSphere Application Serer installation parameters: Note that WebSphere Application Serer security must be enabled before you install System Automation Application Manager. 48 System Automation Application Manager: Installation and Configuration Guide

65 Table 25. WebSphere Application Serer (WAS) installation parameters Parameter Req Name Description Default WAS topology Y WAS_TYPE_SETUP Specify the WAS topology you hae choosen to install the automation manager. Use the keyword BASE for an unmanaged application serer setup. none Note: Only BASE is supported in the current release. WAS security setup WAS configuration group WAS administration with surrogate Y WAS_TYPE_SECURITY Specify the current realm definition of the WAS User account repository. You can specify either LOCAL, LDAP, FEDERATED or CUSTOM. It is possible to check the current setting by using the WebSphere Administratie Console and naigating to Security -> Security administration, application and infrastructure -> current realm definition. Example: "LOCAL" Y WAS_GROUP_CONFIG Specify the RACF group name of your WebSphere configuration group. Example: "WSCFG1" Y WAS_OPTN_SURROGAT This option specifies how to run the System Automation Application Manager installation jobs. Most of these jobs use the wsadmin.sh script. Depending on your WebSphere enironment, you may prefer to run the installation jobs using user wsadmin granted with SAF Class SURROGAT authorization (BPX.SRV.user). With WAS 6.1 or later there is no longer a need for the user WSADMIN. You can install the product from a user ID which has accepted the CA Certificate or a user ID within the WAS Key Ring. Specify the alue true to use SAF SURROGAT authorization to use switch user (su), or false not to use the su command. Cell name Y WAS_NAME_CELL The WAS cell to be used for the automation manager. none none none none Certificate name Example: "csaam" Y WAS_NAME_CERTIFICATE Specify the name of the WebSphere self-signed CA certificate. This name was specified during the WebSphere configuration. none Example: "WebSphereCA" Keyring Y WAS_NAME_KEYRING The name of the WAS keyring as defined during installation Example: "WASKeyring.NSAAM" Node name Y WAS_NAME_NODE_E2E The WAS node to be used for the automation manager. Example: "nsaam" Profile name WAS_NAME_PROFILE The WAS profile to be used for the automation manager and the operations console. Serer name WAS_NAME_SERVER The WAS serer to be used for the automation manager. none none default serer1 Chapter 2. Installing System Automation Application Manager 49

66 Table 25. WebSphere Application Serer (WAS) installation parameters (continued) Parameter Req Name Description Default Installation directory Y WAS_PATH_INSTALL The installation location of WAS. none Example: "/local/websphere/v6r1/ap/appserer" Bootstrap port WAS_PORT_BOOTSTRAP The port of the WAS serer to be used as 2809 bootstrap for the automation manager. Administrator Y WAS_USER_ADMIN The user ID of the WAS administrator. none user ID Administrator user password Y WAS_PWRD_ADMIN The password of the WAS administrator user ID. none RACF user ID creation data: The parameters listed in following table are required to create arious user IDs and groups with RACF. You can specify new or existing user and group IDs here. Later on you will create sample jobs you can submit to create the new user and group IDs as well as other related security attributes. If the job contains definition which are already known to RACF (like users or groups) then these statements must be remoed from the job in order to aoid errors. In any case you need to erify the RACF definitions that are generated before submitting the job. The specification of existing user and group IDs is required because this information is referenced by arious other jobs. The following RACF parameters correspond to the groups that are listed, as described in the chapter Managing users in IBM Tioli System Automation Application Manager Administrator s and User s Guide. RACF parameter RACF_GROUP_ADMIN RACF_GROUP_CONFIG RACF_GROUP_OPERATOR RACF_GROUP_MONITOR RACF_GROUP_ACCESS Group EEZAdministratorGroup EEZConfiguratorGroup EEZOperatorGroup EEZMonitorGroupand EEZEndToEndAccessGroup Table 26. Installation parameters for RACF user and groups Parameter Req Name Description Default RACF owner of resources Y RACF_OWNER_RESOURCES RACF group name or user name which will be used as resource Owner of resources belonging to System Automation Application Manager. This name could be any existing RACF group or RACF user defined in your security enironment. Example: GEEZ none 50 System Automation Application Manager: Installation and Configuration Guide

67 Table 26. Installation parameters for RACF user and groups (continued) Parameter Req Name Description Default RACF owner of groups Y RACF_OWNER_GROUPS RACF group name or user name which will be used as the owner of groups belonging to System Automation Application Manager. This name could be any existing RACF group or RACF user defined in your security enironment. none RACF superior group name RACF SA Application Manager admin group RACF SA Application Manager admin group OGID RACF SA Application Manager configurator group RACF SA Application Manager configurator group OGID RACF SA Application Manager operator group RACF SA Application Manager operator group OGID RACF SA Application Manager monitor group RACF SA Application Manager monitor group OGID Example: GEEZ Y RACF_GROUP_SUPERIOR RACF group name which will be used as superior group defining the required RACF groups of System Automation Application Manager. This group name must be an existing RACF group defined in your security enironment. Example: GEEZ Y RACF_GROUP_ADMIN RACF group name of System Automation Application Manager ADMINISTRATOR group. Example: "GEEZADM" Y RACF_GROUP_ADMIN_OGID RACF group name of System Automation Application Manager ADMINISTRATOR group unique OMVS group ID. Example: "9501" Y RACF_GROUP_CONFIG RACF group name of System Automation Application Manager CONFIGURATOR group. Example: "GEEZCONF" Y RACF_GROUP_CONFIG_OGID RACF group name of System Automation Application Manager CONFIGURATOR group unique OMVS group ID. Example: "9502" Y RACF_GROUP_OPERATOR RACF group name of System Automation Application Manager OPERATOR group. Y Example: "GEEZOPER" RACF_GROUP_OPERATOR_OGID RACF group name of System Automation Application Manager OPERATOR group unique OMVS group ID. Example: "9503" Y RACF_GROUP_MONITOR RACF group name of System Automation Application Manager MONITOR group. Example: "GEEZMON" Y RACF_GROUP_MONITOR_OGID RACF group name of System Automation Application Manager MONITOR group unique OMVS group ID. Example: "9504" none none none none none none none none none Chapter 2. Installing System Automation Application Manager 51

68 Table 26. Installation parameters for RACF user and groups (continued) Parameter Req Name Description Default RACF SA Application Manager access group RACF SA Application Manager access group OGID RACF SA Application Manager user group RACF SA Application Manager user group OGID RACF group name of product System Automation Application Manager RACF group name of product System Automation Application Manager OGID RACF installation ID Y RACF_GROUP_ACCESS RACF group name of System Automation Application Manager ACCESS group. Example: "GEEZE2E" Y RACF_GROUP_ACCESS_OGID RACF group name of System Automation Application Manager ACCESS group unique OMVS group ID. Example: "9505" Y RACF_GROUP_USERS RACF group name of System Automation Application Manager USERS group. Example: "GEEZUSER" Y RACF_GROUP_USERS_OGID RACF group name of System Automation Application Manager USERS group unique OMVS group ID. Example: "9510" Y EEZ_OWNER_GROUP This group will be used during the installation of System Automation Application Manager as the group owner of all created paths and files. Example: "GEEZOWN" Y EEZ_OWNER_GROUP_OGID OGID to be used for EEZ_OWNER_GROUP. Example: "9500" Y RACF_USER_INSTALL Name of a RACF user ID or a RACF group. The product will be installed under the control of this installation ID. Normally this is your own user ID, an installation user ID for this product or a function group you are connected to. none none none none none none none IBM Tioli Enterprise Console connection configuration data: Optionally, you can use Tioli Enterprise Console for monitoring end-to-end automation management eents. The parameters listed in the following table are only required if you will use Tioli Enterprise Console for end-to-end automation management. Table 27. Installation parameters for IBM Tioli Enterprise Console Parameter Req Name Description Default TEC enable connection Y TEC_OPTN_ACTIVATE Specify the option for the TEC Serer Connection. Specify true to enable this option or false to disable it. TEC host name CR TEC_NAME_HOST The name of the host where the Tioli Enterprise Console serer is installed. This parameter is required when setting TEC_OPTN_ACTIVATE to "true". Example: "tecsr1" none none 52 System Automation Application Manager: Installation and Configuration Guide

69 Table 27. Installation parameters for IBM Tioli Enterprise Console (continued) Parameter Req Name Description Default TEC serer port number TEC_PORT_NUMBER The port number for the Tioli Enterprise Console serer For more information about utilizing Tioli Enterprise Console for end-to-end automation management, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using Tioli Enterprise Console with System Automation Application Manager" IBM Tioli Common Reporting configuration data: Tioli Common Reporting is used by the SA Application Manager to create and isualize reporting data of automation actions. Table 28. Installation parameters for IBM Tioli Common Reporting Parameter Req Name Description Default Tioli Common Reporting Y TCR_OPTN_INSTALL Specify this option to create the TCR installation jobs. none installation Note: Only true is supported in the current option release. Tioli Common Reporting admin group Y TCR_GROUP_ADMIN Specify the group name of the reporting administrator group. If your WAS user account repository is set to LOCAL this group is a RACF group. none Tioli Common Reporting admin group OGID Tioli Common Reporting iewer group Tioli Common Reporting iewer group OGID Example: "GTCRADM" Y TCR_GROUP_ADMIN_OGID Specify here the unique OMVS group ID for TCR_GROUP_ADMIN. Example: "9520" Y TCR_GROUP_VIEWER Specify the group name of the reporting iewer group. If your WAS user account repository is set to LOCAL this group is a RACF group. Example: "GTCRVIEW" Y TCR_GROUP_VIEWER_OGID Specify here the OGID for TCR_GROUP_VIEWER. Example: "9521" none none none Configuration data for enabling communication with GDPS: Parameters in this section are only required if you choose to install the Distributed Disaster Recoery feature. Een after specifying these options and running the generated jobs you are still required to purchase and enroll the license to enable the Distributed Disaster Recoery feature. Table 29. Installation parameters for GDPS interaction Parameter Req Name Description Default GDPS installation option GDPS_OPTN_ACTIVATE Specify the option for the GDPS Serer Connection interaction. Use the alue true to enable a GDPS connection; use false to disable it. false Chapter 2. Installing System Automation Application Manager 53

70 Table 29. Installation parameters for GDPS interaction (continued) Parameter Req Name Description Default GDPS serer connection CR GDPS_NAME_HOST Specify the hostname for the GDPS K-System connection. This is only required if you specified GDPS_OPTN_ACTIVATE=true none GDPS serer connection port GDPS backup serer connection GDPS backup serer hostname GDPS backup serer connection port GDPS_PORT_NUMBER Example: "boexdr1" Specify the port for connection to the GDPS K-System. CR GDPS_OPTN_BKUP Specify the option for the backup GDPS serer connection. Use the alue true to enable a GDPS backup connection; use false to disable. CR GDPS_NAME_HOST_BKUP Specify the hostname for the backup GDPS K-System connection. This is only required if you specified GDPS_OPTN_BKUP=true GDPS_PORT_NUMBER_BKUP Specify the port for connection to the GDPS Backup K-System false none 5529 Name of the end-to-end automation domain: Table 30. End-to-end automation domain name Parameter Req Name Description Default Automation domain name E2E_NAME_DOMAIN The name of the end-to-end automation domain represented by this instance of the automation engine. The domain name must be unique and may not be used for any other automation domain. The characters used for the domain name are limited to the following ASCII characters: A Z, a z, 0 9,. (period), and _ (underscore). FriendlyE2E WebSphere Application Serer user ID for the end-to-end automation engine The end-to-end automation engine requires a WebSphere Application Serer user ID to access the J2EE framework. The user ID is created during the installation of System Automation Application Manager. In the Install Options file you need to specify the user ID, the password, and the OMVS UID for this user. Table 31. WebSphere Application Serer user ID Parameter Req Name Description Default User ID EEZ_USER_DAEMON WebSphere Application Serer user ID for the end-to-end automation engine. EEZDMN The automation engine will use the credentials for accessing the J2EE framework that runs in WebSphere Application Serer. Password Y EEZ_PWRD_DAEMON Password of the user ID none OMVS UID Y EEZ_USER_DAEMON_OUID OMVS UID for this user ID System Automation Application Manager: Installation and Configuration Guide

71 System Automation administrator user ID During the installation of System Automation Application Manager, the initial Tioli System Automation administrator user is created in WebSphere Application Serer and authorized for all tasks and actions that can be performed from the System Automation operations console. In the Install Options file you need to specify the data listed in the following table: Table 32. System Automation administrator user ID Parameter Req Name Description Default User ID EEZ_USER_ADMIN User ID of the System Automation operations EEZADMIN console administrator Password Y EEZ_PWRD_ADMIN Password of the user ID none OMVS UID Y EEZ_USER_ADMIN_OUID OMVS UID for this user ID 9401 Job control statements Specify the job control statements to run the post installation jobs. The options JCL_JOBCARD_1, JCL_JOBCARD_2 and JCL_JOBCARD_3 are used to create a job card alid for execution on your post installation driing system. The other options control job processing. The alues entered for all options must adhere to MVS JCL conentions. Chapter 2. Installing System Automation Application Manager 55

72 Table 33. Job control statements Parameter Req Name Description Default Job Card no. 1 Y JCL_JOBCARD_1 Use this option to define the first line of the job card including the required JCL JOB statement. Within this line you can specify a alid jobname and accounting information. If you want to define a static job card for each of the installation jobs use syntax 1 below. If you want to define a ariable jobcard containing parts of the submitted member name in the jobname you can use syntax 2. Syntax 1: //job_name JOB 'account_info', Example: //SAAMINST JOB 'SAAM-Inst.', Syntax 2: //prefix<#s:e> JOB 'account_info', where: //prefix jobname prefix <# starts the conention s: starting offset of submitted member name e> ending offset of submitted member name Example: //SAAM<#5:8> JOB 'SAAM-INST.', none if used with member ATVEI110 would generate job name SAAMI110. Job Card no. 2 JCL_JOBCARD_2 Use this option to define the second line of the job card including the CLASS, MSGCLASS, and MSGLEVEL parameters. // CLASS=A, MSGCLASS=X, MSGLEVEL=(1,1) 56 System Automation Application Manager: Installation and Configuration Guide

73 Table 33. Job control statements (continued) Parameter Req Name Description Default Job Card no. 3 JES control statement JCL_JOBCARD_3 JCL_JES_1 Use this option to define the third line of the job card including the NOTIFY and REGION parameters. Note: Most of the installation programs require a region size greater than 128 MB. For this reason the job region size should always be defined with REGION=0M. Do not change this alue, as otherwise the programs will end with unpredictable results. This parameter can be used to specify JES2 or JES3 control statements. Examples: JES2: /*JOBPARM SYSAFF=xxxx // REGION=0M, NOTIFY=&SYSUID //* JES3: //*MAIN SYSTEM=xxxx JES node of DB2 location JCL_XEQ_DB2 This parameter can be used to identify the network node where the installation jobs for the DB2 setup should be run. //* Job comment line no. 1 Job comment line no. 2 Job comment line no. 3 Prefix of SMPE data sets JCL_COMMENT_1 JCL_COMMENT_2 JCL_COMMENT_3 Example: /*ROUTE XEQ=TSTSAAM Free for customer use. Example:// * Free for customer use. Example://* - Install SAAM z/os V3.1 Date yy.mm.dd Free for customer use. Example:// * Y JCL_PREFIX_SMPE Specify the prefix of the target SMPE data sets used while running the SMPE installation jobs. Example:SAAM.V310 //* //* //* none Chapter 2. Installing System Automation Application Manager 57

74 Table 33. Job control statements (continued) Parameter Req Name Description Default Prefix of SAAM work data sets Name of SAAM runtime HFS data set Storage class name Proclib Name Y JCL_PREFIX_WORK Specify a prefix which will be used to create temporary work data sets required only during the installation process. You are recommended to use a different alue to that used in option JCL_PREFIX_SMPE and the name of the runtime HFS specified in option JCL_NAME_RUNTIME_HFS. Example:SAAM.WORK Y JCL_NAME_RUNTIME_HFS Specify the name of the SAAM runtime HFS data set. This will be allocated and mounted when the post installation jobs are run. This HFS data set is required for the execution of SAAM. You are recommended to update your parmlib member BPXPRMyy to automatically mount this HFS during IPL. The mount point of this HFS will be generated by appending a fixed product section to the alue of option EEZ_PREFIX_RUNTIME and. Example:SAAM.RUNTIME.HFS Y JCL_STORCLAS_RUNTIME Specify the SMS storage class which will be used to create runtime data sets required for the execution of the product. Check this option with your SMS storage administrator. Example:SC#SAAM Y JCL_PROCLIB_STC Specify a proclib in your proclib concatenation to hold the sample started tasks. Example:USER.PROCLIB none none none none What the installation media contains System Automation Application Manager for z/os is distributed on tape. The contents of the tape are listed in the Program Directory distributed with the tape. Languages supported by System Automation Application Manager In addition to English, System Automation Application Manager supports the following languages: German 58 System Automation Application Manager: Installation and Configuration Guide

75 Spanish French Italian Japanese Korean Brazilian Portuguese Simplified Chinese Traditional Chinese Installing System Automation Application Manager on z/os The preparation consists of the following steps: 1. Create a work copy of the Install Options file. 2. Edit the work copy of the Install Options file that defines the arious installation and customization settings. These settings are then used to update the installation jobs so that you do not need to modify these jobs yourself. 3. Create a work copy of sample job ATVEI Edit and submit the work copy of sample job ATVEI100. This job allocates the INSTJCL data set and customizes the rest of the installation jobs. 5. Submit the installation jobs created in step 4, in the order gien in Submit the installation jobs on page 60. Note: The user ID under which these jobs are submitted must hae UID 0. Create a work copy of the Install Options file The Install Options file is supplied as member ATVDOPTS in the sample data set shipped with SMP/E DDDEF name TATVSAMP. Create a work copy of Member ATVDOPTS into a data set that meets your requirements. For example, you can use the work data set created to run the SMP/E installation jobs. Do not change the SMP/E managed Member ATVDOPTS in the data set that belongs to the SMP/E DDDEF TATVSAMP. Edit the work copy of the Install Options file You define arious settings that ary from installation to installation in the Install Options file. Typical examples are ports used to communicate with the SA Application manager, user IDs and passwords, installation path settings, DB2 settings and so on. These settings are then propagated into the sample JCL streams by the ATVRPREP REXX script. The Install Options file contains comprehensie documentation on the purpose of the parameters, their syntax and alue range. Note: The Install Options file contains the passwords in readable format. Therefore access to this file should be restricted. The following rules apply when coding the Install Options File. An asterisk (*) or hash character (#) indicates a comment line. Each install option is defined as a keyword=alue pair. No comment can be specified on the keyword=alue line. There may be one or more blank characters before and/or after the equals sign (=). Leading and trailing blanks will be remoed from the specified alue, but embedded blanks will be presered. If an option is specified more than once the first occurrence is the one used. Continuation lines must be marked by blank and plus characters ( +) at the end of the line. For example: Chapter 2. Installing System Automation Application Manager 59

76 EEZ_PATH_PE=/local/WebSphere/V6R2/AP/AppSerer + /systemapps/isclite.ear As well as the install options described in Collecting the information you need to proide during installation on page 18, some options exclusie to z/os are required. Check the comments in the deliered Install Options file for details and further instructions. Create a work copy of sample job ATVEI100 Create a work copy of sample job ATVEI100 into a data set that meets your requirements. For example, you can use the work data set created to run the SMP/E installation jobs. Do not change the SMP/E managed Member ATVEI100 in the data set that belongs to the SMP/E DDDEF TATVSAMP. Edit and submit the work copy of sample job ATVEI100 Edit the work copy of sample job ATVEI100 to update the job statements, and submit it. This job allocates the INSTJCL partitioned dataset to contain the JCL used for the arious customization actiities. It then copies the sample jobs into this dataset and inokes the ATVRPREP script (ia TSO batch inocation) to update the jobs with the specified installation options. The script alidates the arious parameters specified in the Install Options file and propagates the install options into the JCL, shell scripts and property files, preparing jobs to carry out the arious customization steps. Notes: 1. This job and all other jobs submitted during the installation should complete with a return code of 0 (zero). If any job completes with a return code other than 0 examine the output of the job for details. Jobs can generally be resubmitted after the error is corrected. Some jobs, howeer, cannot be resubmitted directly as changes made by them must be undone first. In these cases auxilliary jobs are proided to back out the changes. 2. As well as the installation jobs, the INSTJCL library also contains jobs for applying serice and uninstalling the product, and should be retained for these purposes. Edit and copy the sample procedures ATVEZDMN, ATVEZGPA and ATVEZHWA Check the comments in the headings of these procedures for any required changes. These procedure must then be copied from the INSTJCL PDS into the PROCLIB concatenation chain. Sample job ATVEH160 is proided for this purpose. Submit the installation jobs The generated jobs can be submitted without change. You may edit them if required, for example to gie them unique job names and to enable job chaining. They should be submitted in the following order: 1. ATVER100 This job sets up the necessary security definitions. Notes: a. Before rerunning this job run sample job ATVER10C to undo the definitions set up in the preious job. b. The user ID this job is submitted under requires special RACF security authority. This job executes the security commands required for System Automation Application Manager. 60 System Automation Application Manager: Installation and Configuration Guide

77 c. Reiew this job with your security administrator and, where required, modify the job before submitting. For example, if you hae specified user IDs that are already authorized, remoe the ADDUSER commands for these users from the job. d. The commands in this job are written for RACF. If you use another security product these commands must be translated into the appropriate syntax for your product before submitting. 2. ATVER110 This job sets up the necessary security definitions. It is intended to define function groups, connect users to the function groups, and define EJBROLE resources in the IBM Security Serer RACF. Notes: a. This job is only required to run if your WAS user account repository is set to the local operating system. Otherwise the first step will end with a return code of 04 and all the following steps will be flushed. b. Before rerunning this job run sample job ATVER11C to undo the definitions set up in the preious job. c. The user ID this job is submitted under requires special security authority. This job executes the security commands required for System Automation Application Manager. d. Reiew this job with your security administrator and, where required, modify the job before submitting. For example, if you hae specified user IDs that are already authorized, remoe the ADDUSER commands for these users from the job. e. The commands in this job are written for RACF. If you use another security product these commands must be translated into the appropriate syntax for your product before submitting. f. To actiate the new defined EJBROLE resources WebSphere Application Serer must be recycled. 3. ATVED100 This creates the necessary DB2 table space and associated tables. The job creates the tables listed in Table 11 on page 15, and the associated index entries. Notes: a. This step is not required if you are using a remote DB2. b. Make sure that DB2 is actie before submitting the job ATVED100 c. Before rerunning this job run job ATVED10C to cleanup the table space and tables defined by the preious run. d. The user ID under which this job is submitted must hae DB2 SYSADM authority. 4. ATVEH160 This copies the PROCLIB members into the installation PROCLIB. 5. ATVEI110 This job: creates the arious configuration directories, creates runtime HFS and customized script files, creates the symbolic links, sets the file owner, group owner and permission flags, and creates the TIVOLI_COMMON_DIRECTORY if this does not already exist. Chapter 2. Installing System Automation Application Manager 61

78 6. ATVEH180 This checks that WebSphere is properly set up and that the ISC component is installed. 7. ATVEW100 This deploys and configures the Common Eent Infrastructure (CEI). Note: If the CEI is already deployed, do not deploy it again. Furthermore, do not disable eent persistence in this case. 8. ATVEW120 This installs the JMS proider. 9. ATVEW130 This sets up the SA Application Manager.baroc and load_classes files. 10. ATVEW140 This configures the JDBC. 11. ATVEW150 This sets up the default messaging. 12. ATVEW160 This sets up Naming and WAS configuration. 13. ATVEW170 This sets up the J2C connections and connection factories. Note: Before the next step the serer on which End-to-End Automation is to be installed must be started. (In a Network Deployment enironment this is not the same as the WebSphere Application Serer administration serer.) 14. ATVEA100 This job: deploys the System Automation Application Manager EJBs, deploys the System Automation Application Manager Operations Console, deploys the Policy editor, defines the System Automation Application Manager role mappings, and sets the group ownership of files. Note: Use sample job ATVEH120 to check if the System Automation Application Manager was successfully deployed. Then log on to the WAS administratie UI to erify the status. If the application EEZEAR has started successfully there is a green arrow at the right of the entry which corresponds to the application. If there is a red 'X' behind the application EEZEAR the application has not yet started. Check that the System Automation Application Manager Integration Module was successfully deployed by starting application EEZIMEAR. Use sample job "ATVEH170" to do this. Then go to the administratie UI to erify the status. If the application EEZIMEAR has started successfully there is a green arrow at the right of the entry which corresponds to the application. If there is a red 'X' behind the application EEZIMEAR the application has not yet started. 15. ATVEA140 This installs the System Automation Application Manager licenses. 16. ATVEA System Automation Application Manager: Installation and Configuration Guide

79 Verifying the installation This deploys System Automation Application Manager for Distributed Disaster Recoery. 17. ATVET100 This job: prepares the TCR installation, creates the TCR directories, and sets the file owner, group owner, and other attributes. 18. ATVET110 This job: deploys the TCR application in WebSphere, creates the required shared libraries for TCR, starts the TCR application, sets up the TCR internal JNDI datasource for the TCR cloudscape database, and adds the TCR install location as a WebSphere JVM property. Note: After this step WebSphere Application Serer must be recycled. 19. ATVET140 This imports the System Automation Application Manager reports. Verify the automation manager To erify that the automation manager was installed successfully, complete the tasks described in the following sections. Verify the end-to-end automation database Perform these steps to erify that the end-to-end automation database and the database tables were created successfully on AIX, Linux or Windows: 1. Ensure that DB2 is running. 2. Open the DB2 Control Center. 3. Naigate to Databases and expand the folder. 4. Expand EAUTODB. 5. Click Tables. The tables listed in Table 11 on page 15 should be shown. Perform these steps to erify that the end-to-end automation database and the database tables were created successfully on z/os: 1. Ensure that DB2 is running. 2. Inoke the DB2 Administration Tool from within TSO. 3. Select the DB2 that is hosting the SA Application Manager tables. 4. Inoke the DB2 System Catalog function (option 1) 5. Naigate to Databases (option D). 6. Select EAUTODB (or whateer name you hae chosen) and specify option T. 7. The tables listed in Table 11 on page 15 should be shown. Verify the automation J2EE Framework Perform these steps to erify that the automation J2EE framework was installed successfully on AIX, Linux, Windows or z/os: Chapter 2. Installing System Automation Application Manager 63

80 1. In a Web browser window, specify the following address to display the Login panel of Integrated Solutions Console: The default ISC port is On the login panel, enter the user ID and password of the WebSphere Application Serer administrator user. 3. Naigate to Applications > Enterprise Applications. The list of installed applications must contain the entry EEZEAR. Verify that DB2 accepts WebSphere Application Serer requests Perform the following task to erify that DB2 accepts WebSphere Application Serer requests: 1. In a Web browser window, specify the following address to display the Login panel of Integrated Solutions Console: The default port is On the login panel, enter the user ID and password of the WebSphere Application Serer administrator user. 3. Naigate to Resources > JDBC > Data sources > EAUTODBDS. Click Test connection to erify that DB2 accepts WebSphere Application Serer requests. If the test is successful, the following message comes up: Test connection for data source EAUTODBDS was successful. If the test fails, check if the DB2 port number specified for EAUTODB is correct (for more information, refer to the "Troubleshooting" appendix in the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section WebSphere Application Serer cannot connect to DB2. Verify the automation engine Perform these steps to erify that the automation engine was installed successfully: 1. If you are using a z/os system, log in to USS on the system on which the automation manager is installed with the user ID authorized for this purpose (the default is eezdmn). 2. Issue the command eezdmn -help. If the installation of the automation engine has been successful the list of aailable command options is displayed. Note: You can also use any of the other eezdmn command options to erify the installation of the automation engine. As long as you do not receie an exception, any message you receie erifies that the automation engine is installed correctly. For a complete list of the eezdmn command options, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using the command-line interface of the automation engine". Verify the operations console Perform the following steps to erify that the operations console was installed successfully: 1. In a Web browser window, specify the following address to display the Login panel of the Integrated Solutions Console: 64 System Automation Application Manager: Installation and Configuration Guide

81 The default ISC port is On this panel enter the System Automation administrator user ID. The default user ID is eezadmin. Click Log in. 3. On the Welcome page of Integrated Solutions Console, click the entry for Tioli System Automation Application Manager. 4. When the Welcome page of System Automation Application Manager is displayed, the installation was successful. 5. Open the operations console. Chapter 2. Installing System Automation Application Manager 65

82 Post-installation tasks When you hae erified the installation of System Automation Application Manager, you need to perform a number of post-installation tasks: You should create and authorize additional users as described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide. To get System Automation Application Manager operational, you must create and actiate an automation policy. This is described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide. You must enable the end-to-end automation manager to access the first-leel automation domains referenced in the automation policy. To do this, you must specify the user credentials for the first-leel domains on the User credentials tab of the configuration dialog. Inoking the end-to-end automation manager configuration dialog on page 73 describes how you launch the configuration dialog. For detailed information about the User credentials tab, refer to the online help of the configuration dialog. Modify the Lightweight Third Party Authentication (LTPA) settings After the installation of System Automation Application Manager, you should check whether the LTPA settings are appropriate for your enironment. During installation, the following LTPA parameters are automatically set in WebSphere Application Serer: LTPA Password is set to the password of the Integrated Solutions Console administrator user ID LTPA Timeout for forwarded credentials between serers is set to 120 minutes LTPA Timeout is a security-related timeout. Because this timeout is absolute, a user will be logged out and forced to log in to Integrated Solutions Console again when the LTPA timeout is reached een if the user is working with the operations console at the time. To change the LTPA settings (for example, password and timeout) you use the WebSphere Application Serer administratie console. On the administratie console, select Security > Secure administration, applications, and infrastructure > Authentication mechanisms and expiration. Modify the HTTP session timeout After the installation of System Automation Application Manager, you should check whether the setting of the HTTP session timeout is appropriate for your enironment. The HTTP session time is an actiity timeout. The alue to which the HTTP session timeout is set defines after how many minutes of inactiity a user is logged out automatically. During installation, the HTTP session timeout is set to 30 minutes. To change the alue, you use the WebSphere Application Serer administratie console. 66 System Automation Application Manager: Installation and Configuration Guide

83 On the administratie console, select Serers > Application serers > serer1 > Container Settings > Session Management: Configure the number of users who can connect to the automation manager using the operations console During the installation of System Automation Application Manager, a default alue (30) is set that defines how many users can simultaneously connect to the automation manager using the System Automation operations console. You can change the current setting by changing the Maximum connections alue for the EEZTopicConnectionFactory from Integrated Solutions Console (Resources >JMS > Topic connection factories > EEZTopicConnectionFactory > Connection pools). If Maximum connections is set to 0, the number of concurrent connections that can be established is allowed to grow infinitely. If the specified number of maximum connections is reached, the next connection attempt using the operation console will bring up the following error message: EEZU0011E: Unable to set up the eent path between the operations console and the management serer: CWSIAD005E: The JCA runtime failed to allocate a connection. Modify the Windows Firewall Security Rules This task is only necessary when you hae installed System Automation Application Manager on Windows Serer After the installation of System Automation Application Manager you must ensure that inbound and outbound TCP traffic with the different Application Manager components is allowed. Ports for communication with the Integrated Solution Console, as well as ports to receie status change eents from other automation domains, must be opened in the Windows firewall with adanced security. It is assumed that you do not block the outbound connections to the other automation domains. Chapter 2. Installing System Automation Application Manager 67

84 The following ports hae to be opened for inbound TCP traffic: Table 34. Inbound TCP ports Name Default Description Eent port number 2002 This is the port opened by the automation engine in order to receie (EIF-) eents from other automation domains. This port is configured with cfgeezdmn. ISC Port 9060 This is the port to which you direct your Web browser in order to open the SA operations console or the WebSphere Administratie console. This port can be configured using the WebSphere Administration Console by changing the alue for WC_adminhost. Secure ISC Port 9043 This is the port which is used to open an https connection to the same Integrated Solution Console. This port can be configured using the WebSphere Administration Console by changing the alue for WC_adminhost_secure. To correctly set up these firewall rules follow this procedure: Open "Start -> Administratie Tools -> Windows Firewall with Adanced Security". Select "Windows Firewall with Adanced Security" in the tree iew. Ensure that "Outbound connections that do not match a rule are allowed" is set. In the menu bar open "Action -> New Rule...". Select "Custom" to create a new Custom rule and press "Next >". Select "This program path" and browse for the program jaa.exe of the WebSphere Application serer profile you created for installation of the SA Application Manager. For example: C:\Program Files\ibm\websphere\appserer1\jaa\bin\jaa.exe. Select the "Customize..." button and ensure that the radio button "Apply to all programs and serices" is selected. Select "OK" to close this dialog. Select "Next >" in the window where you specified the JVM to continue with the wizard. Specify "TCP" as protocol type and "Specific Ports" as local ports. In the field below enter the list of ports in Table 34 separated by commas. For example, if you are using the default ports, you must specify 2002, 9060, For "Remote Port" select "All Ports' in order not to block the outbound traffic. 68 System Automation Application Manager: Installation and Configuration Guide

85 Select "Next >". Specify "Any IP address" for both local and remote IP addresses. Select "Next >". Ensure that Allow the connection is selected on this wizard panel. Select "Next >". This rule should apply to all scopes: "Domain", "Priate" and "Public". Select "Next >". Enter a name such as "SA Application Manager (TCP-In)". The optional description may be used as an aide-memoire such as This allows connection to the SA Application Manager Jaa irtual machines. It is required to use the ISC Web based consoles and allows the automation engine to receie eents from the automation adapters running on other automation domains. Select "Finish". Chapter 2. Installing System Automation Application Manager 69

86 70 System Automation Application Manager: Installation and Configuration Guide

87 Chapter 3. Upgrading from IBM Tioli System Automation release 2.x To upgrade from release 2.1 or 2.2 of IBM Tioli System Automation to release 3.1 of System Automation Application Manager, release 2.1 or 2.2 must be uninstalled and release 3.1 installed. This implies that in order to presere data, some additional steps hae to be performed. Although you do not need to uninstall release 2.3 of IBM Tioli System Automation before upgrading to release 3.1 of System Automation Application Manager, it is still needed to perform some additional steps in order to presere data. To presere the data from the earlier installation, export the data before starting the update installation, and import it after the installation of release 3.1. For information on exporting the data, see Appendix B, Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1, on page 197. If you hae configured WebSphere Application Serer to use a security product in read-only mode so that the WebSphere administratie interfaces to manage users and groups cannot be used, perform the following tasks before you upgrade: 1. Modify the functional user ID that is used by the end-to-end automation engine for accessing the WebSphere Application Serer (default user ID name: eezdmn ) such that it is no longer a member of the user group that is associated with the user role EEZOperator (default group name: EEZOperatorGroup). Instead, it must become a member of the user group that is associated with the user role EEZAdministrator (default group name: EEZAdministratorGroup). 2. System Automation Application Manager 3.1 integrates with IBM Tioli Common Reporting (TCR). The TCR component defines two user roles and creates by default two associated user groups during installation. Create user groups that are associated with the following roles, and include user IDs to those groups as needed: a. User role reportadministrator (by default, TCR maps this role to user group reportadministrator) b. User role reportviewer (by default, TCR maps this role to user group reportviewer) 3. Before you start the upgrade installation to System Automation Application Manager 3.1, temporarily enable the WebSphere administratie interfaces to manage users and groups. Refer to Appendix: Considerations about user and group management in WebSphere Application Serer for more information. Once the upgrade installation has been completed, you may again disable the WebSphere administratie interfaces to manage users and groups. If you configured the end-to-end component of SA for Multiplatforms 2.3 to send end-to-end automation eents to the Tioli Enterprise Console (TEC), then start the end-to-end automation configuration tool (cfgeezdmn) and enable the checkbox Enable TEC eent generation after you upgraded to System Automation Application Manager 3.1. Copyright IBM Corp. 2006,

88 Upgrading the MSCS adapter To upgrade an installation including highly aailable MSCS adapter resources from release 2.3 to release 3.1, you must reconfigure these in the Cluster Administrator as this serice has been renamed from SA MP MSCS Adapter to SA AM MSCS Adapter in ersion System Automation Application Manager: Installation and Configuration Guide

89 Chapter 4. Configuring the end-to-end automation manager This chapter proides an oeriew of how you use the end-to-end automation manager configuration dialog to perform the following tasks: Change the basic configuration of the end-to-end automation manager (see End-to-end automation manager basic configuration on page 75). Configure high aailability for the end-to-end automation manager (see Configuring high aailability for the end-to-end automation manager on page 89). Note: You need an X11 serer to use the end-to-end automation manager configuration dialog. You can also configure the end-to-end automation manager in silent mode using an input properties file. The configuration dialog is not aailable on z/os so the silent configuration is the only supported method on this system. See Inoking silent configuration on page 103 for more details. Inoking the end-to-end automation manager configuration dialog Before you begin: The user ID you use to inoke the dialog must meet the following requirements: The user ID must be in same group as the user ID you used for installing System Automation Application Manager. On z/os this is user eezadmin.the group permissions for the cfgeezdmn script must be set to EXECUTE. The user ID must hae write access to the following directory: Windows: <EEZ_INSTALL_ROOT>/cfg AIX, Linux, z/os: /etc/<eez_install_root>/cfg Perform the following step to inoke the configuration dialog: 1. Log in on the system where System Automation Application Manager is installed. 2. Enter the following command: cfgeezdmn The configuration dialog task launcher is displayed (see Using the task launcher ). Using the task launcher The task launcher appears when you inoke the configuration dialog as described in Inoking the end-to-end automation manager configuration dialog. Copyright IBM Corp. 2006,

90 1 Basic configuration Click Configure to open the end-to-end automation manager configuration dialog. On the dialog tabs, you specify basic configuration parameters. For more information, see End-to-end automation manager basic configuration on page Hardware adapter configuration Click Configure to open the System Automation Application Manager hardware adapter configuration dialog. Use this dialog to configure the hardware adapter host and the hardware access credentials that the hardware adapter uses. For more information, see Configuring the end-to-end hardware adapter on page 84. Note: This option is only enabled if the Distributed Disaster Recoery feature is installed on supported platforms. 3 High-aailability configuration You perform the tasks in this section to proide high aailability for the end-to-end automation manager. You actiate the task buttons by selecting Enable the high aailability configuration tasks. Note that on Windows and z/os operating systems, high-aailability configuration is not supported and all tasks are disabled. For more information, see Configuring high aailability for the end-to-end automation manager on page 89. Displaying online help The following sections proide an oeriew of the end-to-end automation manager configuration tasks. More detailed information is aailable in the online help. To launch the online help, click Help on a dialog tab: 74 System Automation Application Manager: Installation and Configuration Guide

91 End-to-end automation manager basic configuration The initial configuration of the end-to-end automation manager is performed during the installation of System Automation Application Manager. To browse or change the properties you can use the end-to-end automation manager configuration dialog or silent configuration. You should neer manually edit the configuration properties files in which the configuration parameters are stored. The following sections describe the basic configuration tabs of the end-to-end automation manager configuration dialog. To open the configuration dialog, perform these steps: 1. Inoke the configuration dialog (see Inoking the end-to-end automation manager configuration dialog on page 73). 2. On the task launcher, click Configure in the "End-to-end automation manager basic configuration" area. The basic configuration notebook appears (see Domain tab on page 76). The tabs of the notebook are described in the following sections. Post-configuration tasks: After changing any of the configuration properties, you must perform the following tasks: Actiate the new settings by reconfiguring the automation engine. To do so, inoke the command eezdmn with the option -reconfig. For command details, see the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Using the command line interface of the automation engine". Chapter 4. Configuring the end-to-end automation manager 75

92 If your end-to-end automation manager is configured for high aailability, you must replicate the configuration files to the other nodes of the IBM Tioli System Automation domain that proides the high aailability. If you changed the hardware adapter configuration, you need to actiate the new settings by reconfiguring the hardware adapter. To do so, inoke the command eezhwadapter with the option -reconfig. For command details see the IBM Tioli System Automation Application Manager Administrator s and User s Guide section Using the command-line interface of the hardware adapter. For a change in the domain name, host name, port numbers, or policy pool location on the Domain tab to become effectie, the automation engine must be restarted using the commands eezdmn -shutdown and eezdmn -start. If you are using the Distributed Disaster Recoery feature, the hardware adapter must also be restarted using the commands eezhwadapter -stop and eezhwadapter -start. Domain tab Use the tab to browse or change the configuration properties of the end-to-end automation domain. Use the following to configure the settings of the end-to-end automation domain and the host where the end-to-end automation manager is running: Domain name The name of the end-to-end automation domain. The name in this field must be the same as the XML element <AutomationDomainName> in each of the domain's automation policy files. Only the following ASCII characters can be used for the domain name: A Z, a z, 0 9,. (period), and _ (underscore). Host name or IP address Name or IP address of the system that hosts the end-to-end automation manager. 76 System Automation Application Manager: Installation and Configuration Guide

93 WAS bootstrap port number The bootstrap port of the WebSphere Application Serer instance that hosts the end-to-end automation manager. Command line request port number The port on which the automation engine receies command-line interface requests. Eent port number The port on which the EIF message conerter listens for eents from the first-leel automation domains. The port number specified here must match the port number specified as eent port number for the end-to-end automation manager host when configuring automation adapters on first-leel automation domains. For SA for z/os, this is the eent port specified in the adapter configuration parameter eif-send-to-port in the adapter plug-in properties file. Enable report data collection Select this checkbox if you want to collect reporting data in the System Automation Application Manager s DB2 database. Enable TEC eent generation Select this checkbox if you want the end-to-end-automation manager to send eents for the end-to-end automation domain to the Tioli Enterprise Console. Policy pool The fully qualified name of the directory that contains the XML automation policy files for the end-to-end automation domain. Only automation policy files that are aailable in this directory can be actiated. Note: For a change in the policy pool location to become effectie, the automation engine must be restarted using eezdmn -shutdown and eezdmn -start. Chapter 4. Configuring the end-to-end automation manager 77

94 Command shell tab The end-to-end automation manager requires authentication when a user inokes the end-to-end automation manager command shell by entering the eezcs command. By default, users are always prompted for their user credentials. On the Command shell tab you hae the choice between these authentication modes: Read user credentials from stdin In this mode, users must always specify their user credentials in the shell window. Prompt for user authentication In this mode, users are always prompted for their credentials by an X11 dialogue unless they specify them when they inoke the command shell. Use specified user credentials In this mode, a shared user ID is used for authentication, which preents users from being prompted for their credentials when they inoke the command shell. You specify the shared user ID and the corresponding password in the fields User ID and Password. Note that only the following ASCII characters can be used for the user ID: A Z, a z, 0 9, and _ (underscore). To change the password, click Change. Discoery library adapter tab System Automation Application Manager proides a Discoery Library Adapter (DLA) to export the currently actie System Automation Application Manager resource topology to an Identity Markup Lanugage (IdML) discoery book. Use the tab to configure the location where the DLA stores IdML books. 78 System Automation Application Manager: Installation and Configuration Guide

95 IdML book directory The absolute path to the directory where the DLA should store IdML books. Local/remote directory Select whether the IdML book directory is located on the computer where the DLA is running or on a remote system. Local IdML book directory The IdML book directory is located on the computer where the DLA is running. Remote IdML book directory The IdML book directory is located on a remote system. Hostname The hostname of the remote system where the IdML book directory is located. This field is only enabled if you select the remote IdML book directory radio button. User ID The logon user ID that is used by the DLA to store IdML books on the remote system. This field is only enabled if you select the remote IdML book directory radio button. Password The logon password that is used by the DLA to store IdML books on the remote system. This field and the Change button are only enabled if you select the remote IdML book directory radio button. Use the Change button to display a dialog that prompts you to specify and confirm the password. User credentials tab Use the User credentials tab to browse or change the user credentials of the end-to-end automation manager. The automation manager uses these credentials to Chapter 4. Configuring the end-to-end automation manager 79

96 authenticate itself. The characters used for all credentials entered on this tab are limited to the following ASCII characters: A Z, a z, 0 9, and _ (underscore). Fields on the User credentials tab: WAS access user ID The user ID that is used to access the WebSphere Application Serer instance that hosts the end-to-end automation manager. WAS access user password The password for the WAS access user ID. Click Change to change the password. Generic user ID The user ID the automation manager uses to authenticate itself to a first-leel automation domain when no credentials are specified for the domain in Credentials for accessing specific first-leel automation domains. Generic password The password for the generic user ID. Click Change to change the password. Credentials for accessing specific first-leel automation domains Click Add to specify a user ID that is alid for the domain. The user ID need not be root but it should be authorized to perform operations on resources in the first-leel automation domain that the end-to-end automation manager supports, for example, bringing an automated resource online. The Remoe and Change buttons let you create and modify the credentials for a first-leel automation domain. For more details, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "How requests against resource references are processed". 80 System Automation Application Manager: Installation and Configuration Guide

97 Security tab Use the Security tab to browse and change the configuration properties for the SSL connection to the first-leel automation domains. Fields on the Security tab: Truststore The fully qualified file name of the truststore file that is used for SSL. The truststore path name must follow the same naming rules as the Installation Directory Name (see Table 22 on page 43). The file name may contain multiple period characters. Click Browse to select a file. Keystore The fully qualified file name of the keystore file that is used for SSL. The keystore path name must follow the same naming rules as the Installation Directory Name (see Table 22 on page 43). The file name may contain multiple period characters. Click Browse to select a file. Keystore password The password of the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Note: If the truststore is in a different file than the keystore, the passwords for the files must be identical. Certificate alias The alias name of the certificate to be used by the serer. The characters used for the certificate alias are limited to the following ASCII characters: A Z, a z, 0 9, and _ (underscore). Logger tab Use the Logger tab to specify the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Chapter 4. Configuring the end-to-end automation manager 81

98 On the Logger tab, you can perform the following tasks: Change the settings temporarily Perform these steps after ensuring that the automation engine is running: 1. Make the required changes on the tab. 2. Click Apply. Results: The new settings take effect immediately. They are not stored in the properties file. If the automation engine is not running, you receie an error message. Note: Temporary changes are not supported in z/os. Change the settings permanently Perform these steps: 1. Make the required changes on the tab. 2. Click Sae. Results: The settings in the properties file are updated. To change the settings immediately Click Apply and then Sae Reert to the permanent settings If you changed the settings temporarily, perform the following steps to reert to the permanent settings defined in the properties file, or when you are unsure which settings are currently actie: 1. Inoke the configuration dialog and open the Logger tab. The Logger tab displays the alues that are currently set in the properties file. 2. Click Apply to actiate the settings. 82 System Automation Application Manager: Installation and Configuration Guide

99 Results: The settings take effect immediately. Controls and fields on the Logger tab: Maximum log/trace file size The file size in kilobytes. Message logging leel: Note: On z/os only the trace file size is configurable. The message log file size is 1024 KB and can not be changed. Error Warning Information Logs messages on the error leel. Logs messages on the error and warning leels. Logs messages on the error, warning and informational leels. Trace logging leel: Off Minimum Medium Maximum Collects no trace information. Collects trace information on the error leel. Collects trace information on the error and warning leels. Proides the message and trace logs and collects additional information on the error, warning, and informational leel. First failure data capture (FFDC) settings: Recording leel: Off Collects no FFDC information. Minimum Proides the message and trace logs and collects additional information on the error leel. Medium Proides the message and trace logs and collects additional information on the error and warning leel. Maximum Proides the message and trace logs and collects additional information on the error, warning, and informational leel. Disk space: Maximum disk space Specifies the maximum disk space in bytes used by FFDC traces which are written into the FFDC trace directory. The default space is byte (10MB). Space exceeded policy Select what to do if the maximum disk space is exceeded. Message IDs: Filter mode Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. Message ID list: Specifies the message IDs which trigger the tracing of the FFDC data. Wildcard characters can be used (for example, *E for tracing all error messages). Chapter 4. Configuring the end-to-end automation manager 83

100 Saing the basic configuration To sae your changes to the end-to-end automation manager properties files, click Sae on the configuration dialog. Upon completion, the Configuration Update Status window appears, showing the list of configuration files that were updated: If you hae configured high aailability for the end-to-end automation manager, you must replicate the properties files to the other nodes in the IBM Tioli System Automation domain (see Replicating the configuration files on page 96). Configuring the end-to-end hardware adapter Notes: 1. Configuration of the hardware adapter is only enabled if you hae installed the Distributed Disaster Recoery feature of System Automation Application Manager, because this feature is a prerequisite for using the hardware adapter. 2. The Distributed Disaster Recoery feature (and thus also configuring it) is aailable only on z/os and Linux on System z. 3. For more details see the IBM Tioli System Automation Application Manager Administrator s and User s Guide. Configuring the System Automation Application Manager hardware adapter consists of the following: 1. Configuring the hardware adapter host using the Adapter tab 2. Configuring the hardware access credentials that are used by the hardware adapter using the Credentials tab After changing any of the configuration properties, you must perform the following tasks: Actiate the new settings by reconfiguring the hardware adapter. To do so, inoke the command eezhwadapter -reconfig. For command details, see the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Using the command line interface of the hardware adapter. 84 System Automation Application Manager: Installation and Configuration Guide

101 If your end-to-end automation manager is configured for high aailability, you must replicate the configuration files to the other nodes of the IBM Tioli System Automation domain that proides the high aailability. For a change in the request port number on the Adapter tab to become effectie, the hardware adapter must be restarted with commands eezhwadapter -stop and eezhwadapter -start. Adapter tab Use this tab to configure the settings of the host where the hardware adapter is running. This is the same host system on which the Websphere Application Serer that hosts the end-to-end automation manager is located. Thus you do not need to explicitly specify a host name or IP address on this tab. Field on the Adapter tab: Request port number The number of the port to which the hardware adapter listens for requests from the end-to-end management host. The default port is Credentials tab Use this tab to configure the hardware access credentials that are used by the System Automation Application Manager hardware adapter. The Credentials tab displays the following lists: Hardware defined in disaster recoery policies This list shows all the hardware entities that are currently defined in the disaster recoery policies that are stored in the policy pool. Chapter 4. Configuring the end-to-end automation manager 85

102 Compare the hardware units in this list with the hardware units in the hardware access credentials list on the right of the tab. Make sure that the credentials list contains at least one entry for each defined hardware unit in the list on the left. Use the Refresh button to refresh the content of the list. If disaster recoery policies hae been added, remoed or modified while you hae been using the configuration dialog, the refresh action updates the recoery policy hardware list to its current status. Configured hardware access credentials This list shows all the hardware entities for which you hae currently defined credentials that are used by the hardware adapter to access those hardware units. A dash ( - ) in the Slot column indicates the hardware box itself. Each hardware unit that is defined in a disaster recoery policy must also be specified in the credentials list. Howeer, you may decide to explicitly omit the actual credentials for selected hardware units. In this case the User ID column remains empty. Use the Add missing button to update the hardware access credentials list by adding entries for all hardware units that are defined in disaster recoery policies, but do not yet hae credentials defined for them. Use the Add button to display the Add Hardware Access Credentials dialog that lets you add a hardware unit with its credentials to the list of hardware access credentials. For more details, see Adding credentials. Use the Remoe button to remoe the selected hardware unit from the list of hardware access credentials. You should only remoe hardware units that are not defined in any disaster recoery policy. Use the Change button to display the Change Hardware Access Credentials dialog that lets you change the user ID and password for the selected hardware unit. For more details, see Changing credentials on page 88. Adding credentials Use this dialog to define access credentials for hardware units that hae not yet been defined in a disaster recoery policy. 86 System Automation Application Manager: Installation and Configuration Guide

103 Fields on the Add Hardware Access Credentials dialog: Box The name of the hardware box for which you want to define credentials. The name of the hardware box is mandatory. Slot The name of the slot in the hardware box for which you want to define credentials. If the hardware box does not contain any slots or you want to define credentials just to access the box itself, leae this field empty. User ID The user ID that is used by the end-to-end hardware adapter to access the specified hardware unit. Password The password that is used by the end-to-end hardware adapter to access the specified hardware unit. Password confirmation Identical to the alue specified in the Password field. Used to confirm password correctness. SNMP Priacy password If the hardware adapter uses SNMP to communicate to a hardware box, you need to add a priacy password to the credentials for that hardware box if SNMP is set up with encrypted communication. Do not specify an SNMP priacy password if you are defining credentials for a slot in a hardware box. Priacy password confirmation Identical to the alue specified in the SNMP Priacy password field. Used to confirm password correctness. Because the definition of access credentials for hardware units is optional, you can leae the user ID and password fields empty. Een if you define access credentials for a hardware box that is accessed by the hardware adapter ia SNMP, you can still choose to omit the SNMP priacy password. Chapter 4. Configuring the end-to-end automation manager 87

104 Clicking the OK button adds the hardware unit and the credentials that you hae specified to the hardware access credentials list on the Hardware Adapter Configuration tab and closes this dialog. Clicking the Cancel button closes this dialog without adding the specified hardware unit and credentials. Changing credentials Use this dialog to change the user ID and password for a selected hardware unit. The entry fields in this dialog are primed with the alues of the selected hardware unit. The name of the box and slot of the selected hardware unit are displayed in the corresponding output fields. Fields on the Change Hardware Access Credentials dialog that you can update: User ID The user ID that is used by the end-to-end hardware adapter to access the selected hardware unit. Password The password that is used by the end-to-end hardware adapter to access the selected hardware unit. Password confirmation Identical to the alue specified in the Password field. Used to confirm password correctness. SNMP Priacy password If the hardware adapter uses SNMP to communicate to a hardware box, you need to add a priacy password to the credentials for that hardware box if SNMP is set up with encrypted communication. Priacy password confirmation Identical to the alue specified in the SNMP Priacy password field. Used to confirm password correctness. Note: SNMP priacy passwords can only be specified for hardware boxes. Therefore the priacy password fields are not shown on this dialog if you are changing credentials for a slot in a hardware box. 88 System Automation Application Manager: Installation and Configuration Guide

105 Because the definition of access credentials for hardware units is optional, you can leae the user ID and password fields empty. Een if you define access credentials for a hardware box that is accessed by the hardware adapter ia SNMP, you can still choose to omit the SNMP priacy password. Use the Clear credentials button to easily remoe all specified credentials for the selected hardware unit. Clicking the OK button changes the credentials for the hardware unit that you selected in the hardware access credentials list on the Credentials tab are changed and closes this dialog. Clicking the Cancel button closes this dialog without changing the selected hardware unit credentials. Saing the hardware adapter configuration To sae your changes to the end-to-end automation manager properties files, click Sae on the Hardware Adapter Configuration tab. Upon completion, the Configuration Update Status window appears, showing the list of configuration files that were updated. If you hae configured high aailability for the end-to-end automation manager, you must replicate the properties files to the other nodes in the IBM Tioli System Automation domain (see Replicating the configuration files on page 96). Actiate the new settings by reconfiguring the hardware adapter. To do so, inoke the command eezhwadapter with the option -reconfig. For command details see the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Using the command line interface of the hardware adapter. For a change in the request port number on the Adapter tab to become effectie, the hardware adapter must be restarted with the commands eezhwadapter -stop and eezhwadapter -start. Configuring high aailability for the end-to-end automation manager For the platforms on which high aailability is possible see "High-aailability configuration" under Using the task launcher on page 73. Notes: 1. Requests to the end-to-end automation manager are lost when a failoer is performed, as these requests are not persistent. 2. Configuring high aailability uses IBM Tioli System Automation for Multiplatforms which must be installed on both nodes. 3. For the steps needed see the IBM Tioli System Automation Application Manager Administrator s and User s Guide, section "Making System Automation Application Manager highly aailable. The following sections describe the high aailability configuration tabs of the end-to-end automation manager configuration dialog. Domain setup tab Use this tab to specify the parameters required for setting up the IBM Tioli System Automation domain which you are using to proide high aailability for the end-to-end automation manager. The specified parameters will be used to Chapter 4. Configuring the end-to-end automation manager 89

106 create the IBM Tioli System Automation domain in the Setup domain task. Fields on the tab: Domain name The name of the IBM Tioli System Automation domain. To prime the field with the currently defined domain name, click Query domain. The domain status (Online or Offline) is displayed to the right of the field. Network tie breaker IP address The IP address that is used to set up a network tie breaker. Leae the field empty if you are setting up a three-node IBM Tioli System Automation domain or if you want to use a different type of tie breaker for a two-node domain. In this case, no network tie breaker will be defined. To prime the field with the currently defined alue, click Query domain. Note that when you use Query domain to fill this field, the first defined tiebreaker of type EXEC will be chosen Node list The table lists the nodes of the IBM Tioli System Automation domain. If the domain is online, clicking Query domain will populate the table with the nodes that are online in the domain. Table columns: Defined node The name of the node. Automate on node Indicates whether the end-to-end automation manager is to be automated on the node, in which case it will be included in the automation policy. Network interface The name of the network interface on this node. Possible actions on the tab: 90 System Automation Application Manager: Installation and Configuration Guide

107 Determining the sequence in which automation selects the node on which the end-to-end automation manager may run You specify the preferred failoer sequence by changing the position of the nodes in the list. To moe a node to a different position, select the node from the list and click Up or Down. Adding, changing, and remoing nodes To change the list of nodes in the automation policy, use the corresponding buttons: Add Opens a window for specifying the settings for the node that is to be added to the automation policy. Change To modify the settings for a node, select the node, click Change, and modify the settings in the windows that appears. Remoe To remoe a node from the automation policy, select the node, and click Remoe. Automation manager tab Use this tab to configure the resources that are used to automate the end-to-end automation manager. Fields on the tab: Automated resources prefix The prefix that precedes the names of the resources and groups in the end-to-end automation manager automation policy. The prefix is restricted to ASCII characters. If you hae defined the current automation policy using the old prefix alue, you must perform the following steps to change the prefix: 1. Remoe the current automation policy. 2. Change the prefix on this tab. 3. Define the automation policy again. IP address The irtual IP address that is shared by all nodes in the IBM Tioli System Automation domain and that is set for the IBM.SericeIP resource in the Chapter 4. Configuring the end-to-end automation manager 91

108 end-to-end automation manager automation policy. The irtual IP address must be authorized by your network administrator. To prime the field with the currently defined alue, click Query domain. Netmask The netmask address that is set for the IBM.SericeIP resource in the end-to-end automation manager automation policy. Request the address from your network administrator. To prime the field with the currently defined alue, click Query domain. Policy pool tab Use this tab to specify the parameters required for automating the file system that holds the policy pool. The data is used to create the corresponding file system resource in the automation policy. The policy pool must reside on a file system that is shared by all nodes in the IBM Tioli System Automation domain. When the automation policy is actie, it will be mounted at the specified mount point on the node where the end-to-end automation manager is running. Fields on the Policy pool tab: File system type The type of the policy pool file system to be automated, for example, "jfs", "jfsz", "ext2". To prime the field with the currently defined alue, click Query domain. Mount point The mount point of the policy pool file system. Click Browse to select a directory. If the domain is online, you can click Query domain to prime the field with the currently defined alue. Deice name The deice name of the policy pool file system. Click Browse to select a deice. If the domain is online, you can click Query domain to prime the field with the currently defined alue. WebSphere tab The tab displays the parameters required for automating the instance of WebSphere Application Serer that hosts the end-to-end automation manager. The 92 System Automation Application Manager: Installation and Configuration Guide

109 data is used to create the corresponding resource in the automation policy. The parameters are set by the installer at installation time. Usually, you will not hae to change any of the alues. Notes: 1. The installation parameters must be identical on all nodes of the IBM Tioli System Automation domain for the automation policy to work. For example, the path to the profile directory, the Application serer port, and the Application serer name must be identical on all nodes. 2. To ensure that IBM Tioli System Automation can stop WebSphere Application Serer, you must add the WebSphere administrator user ID and its password to the WAS SOAP client properties file. The file is located at /<was_home>/ profiles/appsr01/properties/soap.client.props. The corresponding entries in this file must look like this: com.ibm.soap.loginuserid=<was-admin> com.ibm.soap.loginpassword=<password> You can encrypt this password within the properties file by using the WAS PropFilePasswordEncoder utility. Input parameters for this utility are the properties file path and the password identifier. Example: /opt/ibm/websphere/appserer1/profiles/appsr01/bin/propfilepasswordencoder.sh /opt/ibm/websphere/appserer1/profiles/appsr01/properties/soap.client.props com.ibm.soap.loginpassword Fields on the WebSphere tab: Application serer name The name of the WebSphere Application Serer instance that hosts the end-to-end automation manager. Application serer port The number of the WebSphere Application Serer port that is used by the end-to-end automation manager. Profile directory The directory in which the WebSphere Application Serer profile for System Automation Application Manager is located. Click Browse to naigate to the directory. Click Browse to select a directory. Chapter 4. Configuring the end-to-end automation manager 93

110 DB2 tab The tab displays the parameters used for automating the DB2 instance that hosts the System Automation Application Manager database (EAUTODB). The parameters are set by the installer at installation time. Usually, you will not hae to change any of the alues. Note that the installation parameters must be identical on all nodes of the IBM Tioli System Automation domain for the automation policy to work. For example, the installation directory, the instance owner user ID, and the instance owner mount point must be identical on all nodes. Controls on the DB2 tab: Automate DB2 Select the check box to enable the entry fields on the tab. Installation directory Specify the DB2 installation directory or click Browse to select a directory. Instance owner user ID Type the user ID of the owner of the DB2 instance that hosts the EAUTODB database. Instance owner mount point Type the mount point of the DB2 instance that hosts the EAUTODB database or click Browse to select a directory. Hardware adapter tab This tab indicates whether a resource for the hardware adapter will be included in the end-to-end automation manager automation policy that makes the hardware adapter highly aailable. A resource for the hardware adapter will only be included in the automation policy if you hae installed the Distributed Disaster Recoery feature of System Automation Application Manager, because this feature is a prerequisite for using the hardware adapter. 94 System Automation Application Manager: Installation and Configuration Guide

111 Saing the high-aailability configuration To sae your entries, click Sae on the configuration dialog. Upon completion, the Configuration Update Status window appears, showing the list of configuration files that were updated. To ensure that the configuration properties are set correctly on all nodes of the domain, you must replicate the configuration files as described below. Restoring an existing high-aailability configuration To restore a domain configuration from a defined end-to-end automation high aailability policy, you can use the Query domain button on the configuration dialog. This retriees information on most of fields in configuration notebook: On the Domain tab: domain name and status (online/offline) list of nodes and network interfaces IP address of the defined network tiebreaker (een it is not the currently actie tie breaker, if more than one EXEC tiebreaker is defined, the address of first one) On the Automation Manager tab: IP address and netmask of the IBM.SericeIP resource starting with resource name prefix (for example, eez- ). These alues are deried from the currently actie policy, because they are defined only if Define policy is performed and remoed if Remoe policy is performed. On the Policy Pool tab: File system type, mount point and deice name of the IBM.AgFileSystem starting with resource name prefix (for example, eez- ). These alues are deried from the currently actie policy, because they are defined only if Define policy is performed and remoed if Remoe policy is performed. Chapter 4. Configuring the end-to-end automation manager 95

112 Replicating the configuration files Setting up the domain If you hae configured high aailability for the end-to-end automation manager, you must replicate the configuration files to the other nodes in the IBM Tioli System Automation domain wheneer you hae made changes to the basic or high-aailability configuration. To perform the task, click Replicate on the configuration task launcher. The Replicate Configuration Files window is displayed. Use this window to distribute (replicate) the configuration files to the remaining nodes in the IBM Tioli System Automation domain: 1. Select the configuration files you want to replicate or click Select all to select all configuration files in the list. 2. Select the nodes to which the files are to be propagated. If all nodes can be accessed with the same user credentials, click Select all. This is the easiest way to ensure that the configuration is identical on all nodes. 3. Under Target node login, type the user ID and password for the replication target nodes. 4. Start the replication by clicking Replicate. Replication may take a while. While the files are being replicated, the Replicate button is indented and grayed-out. When the replication is complete, the replication status of each configuration file is displayed. After replication you must ensure that the alue specified for the Host name or IP address on the 'Domain' tab of the end-to-end automation manager basic configuration still matches the system on all nodes in the domain. You are recommended to use the irtual IP address specified in the IP address field of the automation manager tab of Configuring high aailability for the end-to-end automation manager. You hae to adapt the Host name or IP address on the Domain tab of the end-to-end automation manager basic configuration on each node in the domain after the replication is completed. Use this task to set up the domain in which the end-to-end automation manager is to be automated. If you will be automating the end-to-end automation manager in a new IBM Tioli System Automation domain, you must perform this task before you inoke the high-aailability configuration task Define policy. To perform the task, click Set up domain on the configuration task launcher. The following window appears, showing the nodes that will make up the domain (the local node and the remote node or nodes, which were specified on the Domain setup tab). 96 System Automation Application Manager: Installation and Configuration Guide

113 Remoing the domain Two actions are performed to set up the domain: 1. Prepare the remote node or nodes for joining the domain To prepare the nodes, specify the user credentials for accessing the nodes. If all nodes can be accessed with the same user credentials, select Use credentials also for remaining nodes. To perform the cluster setup, click Prepare. Upon completion, a message box is displayed. 2. Define the domain To complete the domain setup, the following commands are performed on the local node: preprpnode - prepares the local node for joining the domain mkrpdomain - creates the domain definition using the domain name and the nodes that were specified on the Domain setup tab startrpdomain - brings the domain online Note that IBM Tioli System Automation must be installed on all nodes that are to be included in the new domain. If other IBM Tioli System Automation domains currently exist, they should be offline. Upon completion, a message box is displayed. In order to be able to remoe the peer domain definition from all nodes, the domain must be online to the local node. To remoe the domain definition from all nodes in the domain, click Remoe domain on the task launcher. This inokes the rmrpdomain command. Validating and storing the automation policy for the end-to-end automation manager You can alidate the end-to-end automation manager automation policy as you hae configured it in the end-to-end automation manager high-aailability configuration window by clicking Validate&Store policy on the configuration dialog task launcher. This task also stores the automation policy in XML format in a file. Upon completion the result of the alidation is displayed, including the name of the file where the XML policy is stored. Note: This requires IBM Tioli System Automation for Multiplatforms ersion 3.1 or higher. This task has the following main purposes: Chapter 4. Configuring the end-to-end automation manager 97

114 1. Validating the policy. This allows you to check whether the definitions that you made in the policy configuration window are alid and consistent. 2. Inspecting the generated file. This enables you to check which resources will be defined if you use the Define policy task to actiate the configured policy. If you are using IBM Tioli System Automation to also automate your own applications, the end-to-end automation policy elements are added as a delta to your currently actie policy. You may therefore want to ealuate whether those additional policy elements might hae any impact on your actie policy. 3. Modifying the stored policy and manually actiating it. This allows you to apply modifications to the policy or extend it beyond what you can define using the policy configuration task. Note that each inocation of the Validate&Store policy or Define policy task will oerwrite the XML policy file. You should therefore copy or rename the file before modifying it. If you want to actiate a modified policy, you must use the sampolicy command. See the IBM Tioli System Automation for Multiplatforms Reference manual for details. You are recommended to use the update option -u in this case in order not to stop or remoe any resource outside of the automation policy for the End-to-End Automation manager. The XML policy file contains inclusions of other XML policy files. These included files are not oerwritten by an inocation of the Validate&Store policy or Define policy task. If you want to make changes to any included file, you should first copy and rename it and then change the corresponding include-tag to refer to the renamed file. Note: This function is only supported if IBM Tioli System Automation for Multiplatforms ersion 3.1 or higher is used to make the End-to-End Automation manager highly aailable. If earlier ersions are used, thevalidate&store policy button is disabled. Defining the automation policy for the end-to-end automation manager Clicking Define policy on the configuration dialog task launcher will create the resources with the resource name as described in the table below. Note that if automated resources with the same name exist, they will be changed. If you specified, for example, the resource-/group prefix name eez on the Automation manager tab, the resource group eez-srdb2-rg and the resources and relationships shown in the following table will be created. Notes: 1. Be aware that changing one of these policy elements from outside this dialog, for example by using a console command or the sampolicy command, may cause a failure of the remoe policy or the define policy task. 2. Actiating or deactiating a policy for IBM Tioli System Automation using the sampolicy command may remoe existing definitions for the end-to-end automation policy. For example, the definition of one of the resources in the table below may be remoed when a new policy for IBM Tioli System Automation is actiated. It is therefore recommended that you first sae the currently actie policy using the sampolicy -s command, edit the XML output file, and finally use the command sampolicy -u to update the actie policy with the changed XML output file. When editing the policy, you must make sure that all definitions for 98 System Automation Application Manager: Installation and Configuration Guide

115 end-to-end automation are presered and that none of your changes has an undesired effect on the currently actie end-to-end automation policy. For details, see the description of the sampolicy command in the IBM Tioli System Automation for Multiplatforms Reference. Table 35. Resources in the automation policy for the end-to-end automation manager. Resource name Resource class Description eez-srdb2-rg IBM.ResourceGroup The top-leel group that comprises all automated resources eez-sr-rg IBM.ResourceGroup The group that comprises all resources except of the DB2 related resources eez-db2-rg IBM.ResourceGroup The group that comprises all DB2 resources eez-was-rg IBM.ResourceGroup The group that comprises all WebSphere Application Serer resources eez-engine-rg IBM.ResourceGroup The group that comprises all automation manager resources eez-hwa-rg IBM.ResourceGroup The resource group that comprises the hardware adapter resources eez-gdpsagent-rg IBM.ResourceGroup The resource group that comprises the command receier for Distributed Disaster Recoery resources eez-ip IBM.SericeIP The irtual IP address used for the WebSphere Application Serer eez-was-as IBM.Application The WebSphere Application serer eez-engine IBM.Application The end-to-end automation manager eez-shared-mount IBM.AgFileSystem The policy-pool for the automation manager; only defined when the policy pool is not harested by the StorageRM eez-db2-rs IBM.Application The DB2 serer eez-db2-rs_mount IBM.Application The DB2 filesystem eez-hwa-rs IBM.Application The end-to-end hardware adapter eez-gdpsagent-rs IBM.Application The command receier for Distributed Disaster Recoery db2-rs-dependson-db2-rs_mount IBM.ManagedRelationship Dependency from DB2 serer on the filesystem eez-was-as-dependson-db2-rs IBM.ManagedRelationship Dependency from WebSphere Application Serer on DB2 eez-shared-mount-stopsafter-engine IBM.ManagedRelationship Dependency from the policy pool on the automation manager, only defined if the policy pool is not harested by the StorageRM eez-engine-startsafter-shared-mount IBM.ManagedRelationship Dependency from the automation manager on the policy pool eez-engine-startafter-was-as IBM.ManagedRelationship Dependency from the automation manager on the WebSphere application serer Chapter 4. Configuring the end-to-end automation manager 99

116 Table 35. Resources in the automation policy for the end-to-end automation manager. (continued) Resource name Resource class Description eez-was-as-startsafter-ip IBM.ManagedRelationship Dependency from the WebSphere application serer on the irtual IP address eez-ip-dependson-niequ IBM.ManagedRelationship Dependency from the irtual IP address on the network interface hwa-startsafter-eez-engine IBM.ManagedRelationship Dependency from hardware adapter on the automation manager gdpsagent-dependson-eez-was-as IBM.ManagedRelationship Dependency from the command receier on the WebSphere application serer eez-niequ IBM.Equialency The aailable network interfaces on each node nettb IBM.TieBreaker Tie-Breaker defined, if IP address is specified on the domain setup page Remoing the automation policy for the end-to-end automation manager Clicking Remoe policy on the configuration dialog task launcher will remoe the resources described in the preceding table. All the resources are first stopped and then remoed. Actiating or deactiating a policy for IBM Tioli System Automation using the sampolicy command may remoe existing definitions for the end-to-end automation policy. For example, the definition of one of the resources listed in the table aboe may be remoed when a new policy for IBM Tioli System Automation is actiated. Therefore, it is recommended that you first sae the currently actie policy using the sampolicy -s command, edit the XML output file, and finally use the command sampolicy -u to update the actie policy with the changed XML output file. When editing the policy, you must make sure that all definitions for end-to-end automation are presered and that none of your changes has an undesired effect on the currently actie end-to-end automation policy. For detailed information, see the description of the sampolicy command in the IBM Tioli System Automation for Multiplatforms Reference. 100 System Automation Application Manager: Installation and Configuration Guide

117 Chapter 5. Silent configuration Oeriew This chapter proides an oeriew of the silent mode of the end-to-end automation manager configuration dialog and the tasks that you can perform in silent mode. Using the configuration tool in silent mode allows you to configure the end-to-end automation manager and the end-to-end automation adapters without inoking the configuration dialog. This means that, for example, when configuring an AIX, Linux, or z/os system, you do not need to hae an X Window session aailable. You can use the configuration tool in silent mode to configure the following components: The end-to-end automation manager (including the automation policy and hardware adapter) The HACMP end-to-end automation adapter The MSCS end-to-end automation adapter The VCS end-to-end automation adapter You configure these components by editing configuration parameter alues in an associated properties file. The parameter alues in each properties file correspond directly to the alues that you enter in the configuration dialog. See the following for more details about the configuration parameters: Chapter 4, Configuring the end-to-end automation manager, on page 73 Chapter 12, Installing and configuring the HACMP adapter, on page 139 Chapter 13, Installing and configuring the MSCS adapter, on page 155 Chapter 14, Installing and configuring the VERITAS Cluster Serer adapter, on page 177 You must first inoke the configuration tool to generate silent mode input properties files before you actually perform a configuration update. Working in silent mode To use the configuration tool in silent mode, you need to follow these steps for each component that you want to configure: 1. Generate or locate the silent mode input properties file, see Silent mode input properties file on page Edit the parameter alues in the file, see Editing the input properties file on page Inoke the configuration tool in silent mode to update the target configuration files, see Inoking silent configuration on page If the configuration tool does not complete successfully, deal with any errors that are reported (see Output in silent mode on page 106) and re-inoke the configuration tool. Copyright IBM Corp. 2006,

118 Tasks to be performed manually After configuration has completed successfully, you might also need to manually perform some of the tasks that are inoked in dialog mode by clicking the corresponding push button in one of the launchpad windows. If you hae configured high aailability for the end-to-end automation manager, you might also need to manually perform the following: 1. Replicate the configuration files. You must replicate the configuration files to the other nodes in the IBM Tioli System Automation domain wheneer you hae made changes to the end-to-end automation manager configuration. To do this, you must run the configuration tool in silent mode with identical input properties files on each system. 2. One of the tasks that are described in Chapter 4, Configuring the end-to-end automation manager, on page 73. As an alternatie to using the dialog functions there are scripts aailable that you can launch to perform those tasks. Set up the domain. To perform this tasks, do the following: a. Issue the preprpnode command on all nodes that you specified when configuring the end-to-end automation manager high-aailability, except the node where you ran the configuration tool in silent mode. b. Inoke the script eezautomate -createdomain <config-dir>/ eezautomate.properties on the local node to perform all remaining actions to set up the cluster. Remoe the domain. Inoke the script eezautomate -deletedomain <config-dir>/ eezautomate.properties to remoe the IBM Tioli System Automation cluster to make the end-to-end automation manager highly aailable. Validate and store the automation policy for the end-to-end automation manager. Inoke the script eezautomate -V -checkpolicy <config-dir>/ eezautomate.properties to alidate the end-to-end automation manager automation policy as you hae configured it. Define a configured automation policy. Inoke the script eezautomate -actiatepolicy <config-dir>/ eezautomate.properties to define the end-to-end automation manager resources and related dependent resource according to the alues that you specified when configuring the end-to-end automation manager high-aailability. Remoe a configured automation policy. Inoke the script eezautomate -deactiatepolicy <config-dir>/ eezautomate.properties to remoe the end-to-end automation manager resources and related dependent resource that matches the alues that you specified when configuring the end-to-end automation manager high-aailability. 3. If you hae made one of the end-to-end automation adapters highly aailable in an HACMP, MSCS, or VCS cluster, you might also need to replicate the corresponding adapter configuration files to the other nodes in the HACMP, MSCS, or VCS cluster. To do this, you must run the configuration tool in silent mode for the respectie adapter with identical input properties files on each node of the cluster. 102 System Automation Application Manager: Installation and Configuration Guide

119 Inoking silent configuration 4. If you hae made one of the end-to-end automation adapters highly aailable in an HACMP or VCS cluster, you might also need to manually perform one of the following: a. Define the automation policy. Inoke the script mkhacadpter -p for the HACMP adapter and the script mkcsadpter -p for the VCS adapter to define the resources according to the alues that you specified when configuring the adapter automation policy. b. Remoe the automation policy. Inoke the script mkhacadpter -r for the HACMP adapter and the script mkcsadpter -r for the VCS adapter to remoe the resources that match the alues that you specified when configuring the adapter automation policy. Because silent configuration is simply an alternatie to the configuration dialog, silent mode is inoked using the same command. For each component you specify the option -s after the command to inoke the configuration tool. You inoke silent configuration for each component as follows: The end-to-end automation manager Before you begin: The user ID you use to inoke the configuration tool in silent mode must meet the following requirements: The user ID must be in same group as the user ID you used for installing System Automation Application Manager. The group permissions for cfgeezdmn.sh must be set to EXECUTE. The user ID must hae read-write permissions on the following directory: Windows: <EEZ_INSTALL_ROOT>/cfg AIX, Linux, and z/os: /etc/<eez_install_root>/cfg Perform the following steps to inoke silent configuration: 1. Log in on the system where System Automation Application Manager is installed. 2. Enter the following commands: a. To configure the end-to-end automation manager: Windows: cfgeezdmn.bat -s AIX, Linux, and z/os: cfgeezdmn -s b. To configure the end-to-end automation manager hardware adapter: Windows: cfgeezdmn.bat -s -h AIX, Linux, and z/os: cfgeezdmn -s -h c. To configure the automation policy to make the end-to-end automation manager highly aailable: Windows: cfgeezdmn.bat -s -a AIX, Linux, and z/os: cfgeezdmn -s -a The HACMP end-to-end automation adapter To use the HACMP adapter configuration tool in silent mode you must either be logged in to the system with the user ID root or you must hae write access to the directory /etc/opt/ibm/tsamp/eez/hac/cfg. Chapter 5. Silent configuration 103

120 Issue the following command to inoke the configuration tool in silent mode: cfghacadapter -s The MSCS end-to-end automation adapter To inoke the configuration tool in silent mode, issue the following command: cfgmscsadapter.bat -s The file is located in the adapter installation directory, in the subdirectory bin. The default directory is C:\Program Files\IBM\tsamp\eez\mscs\bin Note: There are further considerations on Windows Serer See Configuring MSCS on Windows Serer The VCS end-to-end automation adapter To use the VCS adapter configuration tool in silent mode, you must either be logged in on the system with the user ID root or hae write access to the directory /etc/opt/ibm/tsamp/eez/cs/cfg. Issue the following command to inoke the configuration tool in silent mode: cfgcsadapter -s Configuring MSCS on Windows Serer 2008 All MSCS adapter configuration tasks must be performed with a domain user account satisfying these two requirements: 1. The domain user account must be member in the local Administrators group on all systems where the MSCS adapter serice is planned to run. 2. The domain user account must be granted full control access oer the Microsoft Serer Cluster or Failoer Cluster. On Windows Serer 2008, the silent configuration program must be started with Administrator priileges. Otherwise the configuration program is unable to write changed configuration files to the right location. Use the following procedure to obtain a command prompt with Administrator priileges which can be used to run the silent configuration program: 1. In the Windows Start menu, select All Programs -> Accessories. 2. Right-click the entry named Command Prompt. 3. In the context menu for Command Prompt, select the entry Run as administrator. Silent mode input properties file You generate silent mode input properties files from the alues that are currently defined in the corresponding target configuration files. The adantages of this are: It allows you to generate properties files immediately after installation and before you perform any customization If you customize with the configuration dialog and in silent mode, you can first generate an up-to-date input file before applying changes in silent mode You can easily recoer from the accidental deletion of the silent mode input properties file 104 System Automation Application Manager: Installation and Configuration Guide

121 To generate a silent mode input properties file, use one of the following options when you inoke silent configuration: -g Generate the input properties file only if it does not already exist. -gr Generate the input properties file and replace it if it already exists. Depending on the target configuration, Table 36 shows the silent input properties files that are generated if the -g or -gr option is specified. Table 36. Generated input properties files Component Target configuration Silent input properties file The end-to-end automation manager cfgeezdmn -s -g -gr <config_dir>/ silent.eezengine.properties The end-to-end automation manager hardware adapter The end-to-end automation manager automation policy cfgeezdmn -s -h -g -gr <config_dir>/ silent.eezhwadapt.properties cfgeezdmn -s -a -g -gr <config_dir>/silent.eezauto.properties HACMP adapter cfghacadapter -s -g -gr <config_dir>/ silent.hacadapter.properties MSCS adapter cfgmscsadapter -s -g -gr <config_dir>/ silent.mscsadapter.properties VCS adapter cfgcsadapter -s -g -gr <config_dir>/ silent.csadapter.properties Editing the input properties file The input properties files that are generated for each of the components contain configuration parameter keyword-alue pairs. To make it as easy as possible to switch between modes and to minimize errors when editing the properties file, the structure, terminology and wording that is used in the silent mode properties file is identical to the structure, terminology and wording of the configuration dialog. The names of tabs (for example, Domain) on the configuration dialog are used as identifiers in the properties file, for example: # ============================================================================== #... Domain Each field name on the configuration dialog (for example, Domain name) is contained in the properties file, followed by a brief description and the keyword for that field, for example: # #... Domain name # The name of the end-to-end system automation domain. Ensure that this # domain name is unique in the set of all automation domains you are # working with. The name has to match the DomainName attribute of all # policies which are intended to be actiated on this end-to-end # automation domain. # The maximum length of the domainname is 64 characters. domain-name=friendlye2e # To edit the properties file, simply locate the keywords whose alues you want to change and oerwrite the alue. Chapter 5. Silent configuration 105

122 Output in silent mode If you set the alue of a keyword to blank or comment out the keyword, the alue that is currently defined in the target configuration file remains unchanged. Notes: 1. If a keyword is specified seeral times, the alue of the last occurrence in the file is used. 2. Each alue must be specified on one single line. Inoking the configuration tool in silent mode leads to output that closely matches the output that is displayed by the configuration dialog and consists of the following: No update This occurs if: All parameters in all target configuration files already match the specified silent input parameters No errors were detected when checking the silent input parameters Howeer, if additional information is aailable or any warning conditions were detected, the information and warnings are reported. 106 System Automation Application Manager: Installation and Configuration Guide

123 Successful completion This indicates that: At least one of the target configuration files was updated (all configuration files and their update status are listed) No errors were detected when checking the silent input parameters Howeer, if additional information is aailable or any warning conditions were detected, the information and warnings are reported. Unsuccessful completion This indicates that: No target configuration file was updated Any errors that were detected when checking the silent input parameters are reported Chapter 5. Silent configuration 107

124 Silent input properties file generation This indicates that: No target configuration file was updated Target configuration alues are used to generate the input file 108 System Automation Application Manager: Installation and Configuration Guide

125 Chapter 6. Installing and uninstalling serice z/os serice Note: The next two sections describe installing and uninstalling serice on distributed systems. To update the installation on z/os refer to Updating the installation on z/os on page 114. Installing serice Installing serice means applying correctie serice fix packs to release of IBM Tioli System Automation Application Manager or upgrading the software release leel from release In this documentation, the serice fix packs that you use for updating System Automation Application Manager are referred to as product fix packs. Note: For some product fix packs, specific interim fixes or fix packs for WebSphere Application Serer are required. In such a case, these fixes are aailable at the location from which you download the product fix pack. They must be installed before the product fix pack is installed. Detailed instructions for installing the fixes are proided in the release notes. Product fix packs and interim fixes are deliered as: Self-extracting archies for Windows and AIX Archies in TAR-format for Linux Where to obtain fix packs Read the release notes to find out which fix packs are required for a release update. The release notes are aailable on the IBM Tioli System Automation home page at: On the page, click Technical Documentation to display the list of aailable documentation. The archies can be downloaded from the IBM Tioli System Automation support site at: Archie naming conentions Naming conention for product fix pack archies: TIV-SAE2E-<platform>-FP<fix_pack_number>.<archie_type> Naming conention for WebSphere Application Serer interim fix archies: TIV-SAWAS-<platform>-FP<fix_pack_number>.<archie_type> where <platform> represents the platform on which System Automation Application Manager is installed Copyright IBM Corp. 2006,

126 <fix_pack_number> represents the fix pack number <archie_type> represents the platform-specific file extension of the archie Example: This is the tar archie that is used to install product fix pack 1 for System Automation Application Manager 3.1 on Linux on POWER platforms: TIV-SAE2E-PPC-FP0001.tar Naming conentions of the update installer location The location at which you find the update wizard program for installing the product fix pack after unpacking an archie has the following syntax: EEZ31<mf>E2E<platform>/<platform>/<update_wizard_file> where <mf> represents modification leel and fix leel. For example, for fix pack 3101, the directory is named EEZ3101. <platform> represents the platform on which System Automation Application Manager is installed <update_wizard_file> represents the update wizard program you use to install the product fix pack Example: This is where you find the update wizard after the Linux on POWER archie for fix pack 1 for System Automation Application Manager 3.1 is unpacked: EEZ3101E2EPPC/ppc/ Installation scenarios Starting with the update installer for System Automation Application Manager , the installer supports two additional installation scenarios: Allow System Automation Application Manager to use a WebSphere Application Serer that is set up to use a standalone user registry. This means that WebSphere uses the user registry product for user authentication and user authorization only. In this scenario, the interfaces proided by WebSphere to list, create, modify or delete user IDs must not be used by the System Automation Application Manager installer. As a consequence, the steps related to user ID management that would otherwise be performed by the System Automation Application Manager installer hae to be configured manually before the System Automation Application Manager installer is inoked. Allow omitting all installer steps that are related to the automation database. This installer feature is required when an installation that is set up for high aailability has to be migrated to System Automation Application Manager or higher. As a consequence, the steps required for upgrading the automation database hae to be performed manually before the SA Application Manager installer is inoked. Usage instructions for the platform-specific archies These are the archies for applying serice to System Automation Application Manager. 110 System Automation Application Manager: Installation and Configuration Guide

127 Windows Table 37. Archies for Windows platforms Archie name TIV-SAE2E-WIN-FP<fix_pack_number>.exe TIV-SAWAS-WIN-FP<fix_pack_number>.exe Description The archie is self-extracting. This is where you find the update installer program after unpacking the product fix pack archie: EEZ31<mf>E2EWindows/Windows/setup.exe The archie is self-extracting. For information about installing WebSphere Application Serer interim fixes, refer to the release notes. AIX Table 38. Archies for AIX platforms Archie name TIV-SAE2E-AIX-FP<fix_pack_number>.bin TIV-SAWAS-AIX-FP<fix_pack_number>.bin Description The archie is self-extracting. This is where you find the update installer program after unpacking the product fix pack archie: EEZ31<mf>E2EAIX/AIX/setup.bin The archie is self-extracting. For information about installing WebSphere Application Serer interim fixes, refer to the release notes. Linux on System x Table 39. Archies for Linux on System x Archie name TIV-SAE2E-I386-FP<fix_pack_number>.tar TIV-SAWAS-I386-FP<fix_pack_number>.tar Description For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files. This is where you find the update installer program after unpacking the product fix pack archie: EEZ31<mf>E2EI386/i386/setup.bin For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files. For information about installing WebSphere Application Serer interim fixes, refer to the release notes. Linux on POWER Table 40. Archies for Linux on POWER Archie name TIV-SAE2E-PPC-FP<fix_pack_number>.tar Description For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files. This is where you find the update installer program after unpacking the product fix pack archie: EEZ31<mf>E2EPPC/ppc/setup.bin Chapter 6. Installing and uninstalling serice 111

128 Table 40. Archies for Linux on POWER (continued) Archie name TIV-SAWAS-PPC-FP<fix_pack_number>.tar Description For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files. For information about installing WebSphere Application Serer interim fixes, refer to the release notes. Linux on System z Table 41. Archies for Linux on System z Archie name TIV-SAE2E-S390-FP<fix_pack_number>.tar TIV-SAWAS-S390-FP<fix_pack_number>.tar Description For extracting the archie, GNU tar 1.13 or later is required. Use the tar -xf command to extract the files. This is where you find the update installer program after unpacking the product fix pack archie: EEZ31<mf>E2ES390/s390/setup.bin For information about installing WebSphere Application Serer interim fixes, refer to the release notes. Steps for installing a product fix pack Before you begin: Product fix packs are always cumulatie. Release must be installed before any product fix pack can be installed. To install a product fix pack, you must hae administrator authority on Windows or root authority on other platforms. To install a product fix pack, perform the following steps: 1. Check the release notes to find out which archies are required. 2. Download the archies from the System Automation Application Manager support site: Archies for WebSphere Application Serer fixes: Follow the download instructions proided in the release notes. Archies for product fix packs: Typically, one archie is proided for each platform. Download the archie to a temporary directory. 3. If fixes for WebSphere Application Serer must be installed, unpack and install the fixes as described in the release notes. 4. Unpack the product fix pack archie to a temporary directory. For information about how to unpack the archie for your platform, refer to Usage instructions for the platform-specific archies on page Before performing the subsequent steps, check the release notes for additional or deiating installation instructions. 6. Change to the directory in which the update wizard program is located. For information on where to find the update wizard program, refer to Usage instructions for the platform-specific archies on page Launch the update wizard. When the wizard is launched successfully, the Welcome panel appears. 8. Follow the instructions on the wizard panels to install the product fix pack. 112 System Automation Application Manager: Installation and Configuration Guide

129 Installing serice in a setup for high aailability If you made your installation of System Automation Application Manager highly aailable by using IBM Tioli System Automation for Multiplatforms (as described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide, Chapter 14: Making System Automation Application Manager highly aailable ), perform the following steps to install serice for System Automation Application Manager. The instructions assume that System Automation Application Manager is currently running on node 1 but not on node Stop node 2 within the SA MP domain (ia command stoprpnode). It is important to stop the node and not just to exclude it (since if you exclude node 2, the resources are still monitored, and if the resources on node 2 become online due to the maintenance on node 2 they will be stopped automatically on both nodes). 2. Run the System Automation Application Manager x update installer on node 2. a. In case of remote DB2 setup, and if no other application uses the JDBC drier on this node, perform the following step: After you are done with the panel IBM DB2 Uniersal Database on remote system and clicked Next, temporarily rename the JDBC drier directory on node 2 in the file system, so that the WebSphere Application Serer cannot find it. This ensures that there is no way for System Automation Application Manager 3.1 on node 2 to connect to the remote database manager during update installation. Note: You can determine the JDBC drier directory in the WebSphere administratie console. Open Enironment > WebSphere Variables and inspect the ariable DB2_JDBC_DRIVER_PATH. b. On the panel High Aailability, select Yes in order to skip all steps related to the automation database. 3. In case of remote DB2 setup, perform the following step: Rename the JDBC drier directory back to its original name. 4. To start node 2 type startrpnode. 5. Moe the end-to-end automation manager to node 2 (either by moing the application, or by excluding node 1). 6. Verify that System Automation Application Manager x has been properly installed (for example by inspecting the System Automation Application Manager operations console, and in particular the ersion number on the Welcome page). 7. To stop node 1 type stoprpnode. 8. Run the System Automation Application Manager x update installer on node 1, obsering the instructions described in step In case of remote DB2 setup perform the following step: Rename the JDBC drier directory back to its original name. 10. To start node 1 type startrpnode. 11. In case node 1 was excluded during step 5, include it again. Uninstalling serice Uninstalling serice is only supported by uninstalling the complete System Automation Application Manager as described in Chapter 7, Uninstalling System Automation Application Manager, on page 115, and reinstalling to the leel required. Chapter 6. Installing and uninstalling serice 113

130 Updating the installation on z/os An update to a z/os installation is supplied as a PTF. This should be applied using SMP/E. After it has been applied check the installation notes sent as ++HOLD data with the PTF. If a new Install Options file is proided by the PTF this file must be merged with the file used for the initial installation, and sample job "ATVEI100" must be resubmitted to update the JCL for the rest of the installation jobs. Any or all of the following jobs must then be run, as specified in the installation notes. Check the ++HOLD data for the correct sequence to run them in. ATVEW170 This sets up the J2C connections and connection factories. Note: This job is only required if new or changed *.RAR files hae to be processed. ATVEM130 This deploys the SA Application Manager EJBs. Note: This job is only required if there are new or changed EEZEAR parts. ATVEM120 This deploys the Integration Module. Note: This job is only required if there are new or changed EEZIMEAR parts. ATVEM100 This deploys the GUI. Note: This job is only required if there are new or changed files in the Operations Console. ATVEM110 This deploys the Policy Editor. Note: This job is only required if there are new or changed files in the Policy Editor. ATVEM140 This redeploys the TCR function in Websphere. Note: This job is only required if serice for TCR has to be applied. ATVEM150 This redeploys the EIF TEC feature option for System Automation Application Manager. ATVEW130 This sets up the SA Application Manager.baroc and load_classes files. Note: This job is only required if new or changed TEC messages are shipped with the update. 114 System Automation Application Manager: Installation and Configuration Guide

131 Chapter 7. Uninstalling System Automation Application Manager Uninstalling System Automation Application Manager from z/os Note: This section describes uninstalling System Automation Application Manager on distributed systems. To uninstall the product from z/os refer to Uninstalling System Automation Application Manager from z/os on page 118. This section describes how to uninstall System Automation Application Manager. An uninstallation program is proided that remoes the components that were installed by the installation wizard. Note: Uninstall System Automation Application Manager before uninstalling WebSphere Application Serer. Launching the graphical uninstallation program on Windows To launch the uninstallation program on Windows, you can either issue the command <EEZ_INSTALL_ROOT>/uninstall/uninstall.exe at a command prompt or perform the following steps: 1. Open Add or Remoe Programs (Start > Control Panel > Add or Remoe Programs). 2. On the Add or Remoe Programs panel, select System Automation Application Manager and click Change/Remoe. This brings up the initial panel of the uninstallation program. Launching the graphical uninstallation program on AIX and Linux To launch the uninstallation program on AIX and Linux, enter the following command in a shell: <EEZ_INSTALL_ROOT>/uninstall/uninstall This brings up the initial panel of the uninstallation program. Using the uninstallation program Before you begin: Before starting the uninstallation of System Automation Application Manager, make sure that the automation engine is stopped. Refer to "Using the command-line interface of the automation engine in the IBM Tioli System Automation Application Manager Administrator s and User s Guide. During uninstallation, a number of panels may appear prompting you to confirm that specific files are to be deleted. Make sure that the files should be deleted before confirming the deletion. Perform the following steps to uninstall System Automation Application Manager: Copyright IBM Corp. 2006,

132 1. Launch the uninstallation program as described in the sections aboe. 2. Read the information on the first wizard panel and click Next. 3. Specify whether Common Eent Infrastructure should be deinstalled and click Next. 4. In the fields on this panel, type the requested information and click Next. 116 System Automation Application Manager: Installation and Configuration Guide

133 5. The Start Deinstallation panel appears, confirming that the preparations for uninstalling System Automation Application Manager and, should you hae opted to deinstall it, the Common Eent Infrastructure are complete. Click Uninstall to start the uninstallation. 6. Some information panels are displayed while the uninstallation program checks your system for the information it needs for the uninstall. The following figure shows an example. 7. When the uninstallation is complete, a summary window is displayed. To exit the installation program, click Done. Chapter 7. Uninstalling System Automation Application Manager 117

134 Note: If problems were encountered during the unconfiguration step, an error panel appears before the actual uninstallation step (in which the files are remoed from the disk). In such a case, do this: a. On the error panel, click Sae installation log files. b. Only if you want to remoe all installed file, click Next. Otherwise, click Cancel to be able to perform correctie actions and then rerun the uninstallation Uninstalling System Automation Application Manager from z/os The JCL members generated during the installation process include jobs for deinstallation. These jobs should be submitted in the following order: 1. ATVED10C This job deletes the DB2 tables and table space. 2. ATVEU100 This un-deploys the SA Application Manager from Websphere. 3. ATVEU110 This remoes the arious directories used by the SA Application Manager. 4. ATVEU120 This unmounts and remoes run-time HFS. 5. ATVEU130 This deletes preiously defined procedures from the PROCLIB. Note: This job is only required if the procedures hae preiously been copied to the Installation PROCLIB by the job ATVEH ATVER11C This job remoes the function groups and EJBROLE resource definitions created by job ATVER ATVER10C This remoes the security definitions. 118 System Automation Application Manager: Installation and Configuration Guide

135 Chapter 8. Installing and configuring the Distributed Disaster Recoery feature The following topics describe how to install and configure the Distributed Disaster Recoery feature of System Automation Application Manager. Installing the Distributed Disaster Recoery feature Installation prerequisites The Distributed Disaster Recoery feature is only aailable on z/os and Linux on System z. Before you can install the Distributed Disaster Recoery feature license you must install the System Automation Application Manager base product. Supported hardware and operating systems The following table shows the distributed serer hardware and the operating system release leels that must be in place on serer clusters to be managed by System Automation Application Manager Distributed Disaster Recoery: Table 42. Supported platforms for serer clusters to be managed by SA AM Distributed Disaster Recoery Operating system: System x 1 System z System p System i z/os 1.7 or higher 2 X SUSE SLES 9 X X 4 (32 bit 3 ) SUSE SLES 9 (64 bit 3 ) SUSE SLES 10 (32 bit 3 ) SUSE SLES 10 (64 bit 3 ) Red Hat RHEL 4.5 AS (32 bit 3 ) Red Hat RHEL 4.5 AS (64 bit 3 ) Red Hat RHEL 5.0 AS(32 bit 3 ) Red Hat RHEL 5.0 AS (64 bit 3 ) X X 4 X X X 4 X 4 X 4 X 4 X 4 X X X X X X X X X X AIX X 6 AIX X 6 Copyright IBM Corp. 2006,

136 Table 42. Supported platforms for serer clusters to be managed by SA AM Distributed Disaster Recoery (continued) Operating system: System x 1 System z System p System i z/os 1.7 or higher 2 X AIX X 8 Notes: 1. xseries (except Intel IA64 based serers) and any other 32-bit Intel based serer, or AMD Opteron based serer (64-bit), or Intel EM64T based serer (64 bit). 2. With SA z/os 3.1 or higher. 3. With SA MP 2.3 FP4 or higher. 4. SP1 must be installed. 5. With SA MP 2.3 only, FP4 is required as a minimum. 6. Requires C++ Runtime Library for AIX ersion , which is included in PTFs U and U With SA MP 3.1 or higher. 8. AIX 6.1 supports Workload Partition (WPAR) mobility or relocation. In SA MP 3.1, RSCT does not support domains with nodes that are System WPARs. Packaging The code of the Distributed Disaster Recoery feature is shipped as part of the System Automation Application Manager product, but you can not exploit the corresponding functionality unless you hae installed a separate license to enable this code. You receie the license when you order the Distributed Disaster Recoery feature. The name of the license file is eez31_ddr.lic. This is where you find the license file: CD If you install the Distributed Disaster Recoery feature from the CD IBM Tioli System Automation Application Manager Distributed disaster recoery the license file is aailable in the directory EEZ3100FeatDDR/ license. Electronic distribution If you obtain the Distributed Disaster Recoery feature through electronic distribution you will find the license in the file C1A29ML.txt. Rename or copy this file to eez31_ddr.lic. Installing the feature license Use the eezdmn command to install the license. The license file must be accessible from the system where the System Automation Application Manager is installed. Transfer the file eez31_ddr.lic in text mode to a location where it will be accessible when you inoke eezdmn. Use the following command to install the license: eezdmn -instcert <license file location>/eez31_ddr.lic To erify that the feature license has been successfully installed, issue the command eezdmn -help The output should be in the form: 120 System Automation Application Manager: Installation and Configuration Guide

137 IBM Tioli System Automation end-to-end automation engine Version: , NO_APAR Features: SA AM for Distributed Disaster Recoery Usage:... The Distributed Disaster Recoery feature should be listed after Features: on the third or subsequent lines of the command output. For more information on the eezdmn command refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using the command-line interface of the automation engine". Configuring the Distributed Disaster Recoery feature The are two steps in the configuration of the Distributed Disaster Recoery feature: 1. Configuring the JMS destination for GDPS eents 2. Configuring the hardware adapter Configuring the JMS destination for GDPS eents If you hae not actiated or configured a GDPS serer connection or a GDPS backup serer connection during the installation of System Automation Application Manager, you must do so now by performing the following steps in the Integrated Solutions Console: 1. Actiate the Common Eent Infrastructure (CEI) serice when the application serer is started: a. Click Serers > Application serers > <serer_name> > Container Serices > Common Eent Infrastructure Serice b. Select the check box Enable serice at serer startup c. Sae the Master configuration and restart the WebSphere Application Serer. 2. Configure the GDPS serer connection when the application serer is started: a. Click Resources > JMS > Queue connection factories (all scopes) > GDPSQueueConnectionFactory > Custom properties b. Set SererLocation to your GDPS serer name Chapter 8. Installing and configuring the Distributed Disaster Recoery feature 121

138 c. Set SererPort to the port the GDPS serer is listening to. Typically, this is port d. Sae your changes to the Master configuration. 3. Optionally, configure the GDPS backup serer connection: a. Click Resources > JMS > Queue connection factories (all scopes) > GDPSBackupQueueConnectionFactory > Custom properties b. Set SererLocation to your GDPS backup serer name c. Set SererPort to the port the GDPS backup serer is listening to. Typically, this is port d. Sae your changes to the Master configuration. 4. Configure the eent groups for the GDPS serer connection: a. Click Serice integration > Common Eent Infrastructure > Eent serice > Eent serices > Default Common Eent Infrastructure eent serer > Eent groups > TEC eents for GDPSQueueConnectionFactory b. Set Eent selector string to = "IBM Tioli System Automation Application Manager DR"]] 122 System Automation Application Manager: Installation and Configuration Guide

139 c. Sae your changes to the Master configuration. 5. Optionally, configure the eent groups for the GDPS backup serer connection: a. Click Serice integration > Common Eent Infrastructure > Eent serice > Eent serices > Default Common Eent Infrastructure eent serer > Eent groups > TEC eents for GDPSBackupQueueConnectionFactory b. Set Eent selector string to = "IBM Tioli System Automation Application Manager DR Backup"]] c. Sae your changes to the Master configuration. 6. Restart the WebSphere Application Serer. The steps aboe can also be used to modify the destination for GDPS eents. To disable eent forwarding to GDPS, perform the following steps in the Integrated Solutions Console: 1. Disable eent forwarding for the GDPS serer connection: a. Click Serice integration > Common Eent Infrastructure > Eent serice > Eent serices > Default Common Eent Infrastructure eent serer > Eent groups > TEC eents for GDPSQueueConnectionFactory b. Set Eent selector string to c. Sae your changes to the Master configuration. 2. Optionally, disable eent forwarding for the GDPS backup serer connection: a. Click Serice integration > Common Eent Infrastructure > Eent serice > Eent serices > Default Common Eent Infrastructure eent serer > Eent groups > TEC eents for GDPSBackupQueueConnectionFactory b. Set Eent selector string to c. Sae your changes to the Master configuration. 3. Restart the WebSphere Application Serer. These steps can also be used to selectiely disable or enable eent forwarding to GDPS or TEC. For example, you can enable eent forwarding for the GDPS serer connection and disable it for the GDPS backup serer connection: Chapter 8. Installing and configuring the Distributed Disaster Recoery feature 123

140 Ensure you use the correct Eent selector strings: To disable eent forwarding always use To enable eent forwarding use: for TEC eents for TECQueueConnectionFactory: = "IBM Tioli System Automation Application Manager"]] for TEC eents for GDPSQueueConnectionFactory: = "IBM Tioli System Automation Application Manager DR"]] for TEC eents for GDPSBackupQueueConnectionFactory: = "IBM Tioli System Automation Application Manager DR Backup"]] Configuring the hardware adapter Use the end-to-end automation management configuration utility to configure the hardware adapter host and the hardware access credentials which the hardware adapter uses. For more information see Configuring the end-to-end hardware adapter on page 84. Actiating the Distributed Disaster Recoery feature After you hae completed all the installation and configuration tasks described aboe you must restart the automation engine to enable usage of the Distributed Disaster Recoery feature functionality. The commands for this are: eezdmn shutdown eezdmn start For more information on the eezdmn command refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using the command-line interface of the automation engine". 124 System Automation Application Manager: Installation and Configuration Guide

141 Uninstalling the Distributed Disaster Recoery feature There is no specific uninstallation of the Distributed Disaster Recoery feature. It is uninstalled implicitly when the System Automation Application Manager product is uninstalled. Chapter 8. Installing and configuring the Distributed Disaster Recoery feature 125

142 126 System Automation Application Manager: Installation and Configuration Guide

143 Part 2. Enabling launch-in-context support Chapter 9. Installing and configuring the IBM TEC extension for the System Automation Application Manager Oeriew Prerequisites Installing the IBM TEC extension Configuring the TEC extension for System Automation Application Manager Adapting the configuration file to your enironment Defining a custom button for the Jaa ersion of the TEC Eent Console (Jaa Swing Client) and the TEC eent iewer embedded in TEP Defining a custom button for the Web ersion of the TEC Eent Console Chapter 10. Setting up Tioli Enterprise Portal launch-in-context support Copyright IBM Corp. 2006,

144 128 System Automation Application Manager: Installation and Configuration Guide

145 Chapter 9. Installing and configuring the IBM TEC extension for the System Automation Application Manager Oeriew Prerequisites The IBM Tioli Enterprise Console (TEC) extension for System Automation Application Manager (IBM TEC Extension) allows naigating from a displayed eent in the Eent Console of Tioli Enterprise Console (TEC Eent Console) to the corresponding resource or domain in the System Automation operations console. Example usage scenario: 1. An operator sees an eent in the TEC Eent Console that shows that a Tioli System Automation resource failed. 2. The operator selects the eent and starts the System Automation operations console for this eent. 3. The System Automation operations console automatically naigates to the resource specified in the eent. 4. The operator analyzes the error by checking, for example, the resource status and dependencies. The IBM TEC Extension can be used for all TEC Eent Console setups: Jaa ersion of the TEC Eent Console TEC Web console TEC eent iewer embedded in the Tioli Eent Portal (TEP) running using the desktop client interface running using the browser client interface To install and use the IBM TEC Extension for System Automation Application Manager, the following prerequisites must be met: TEC ersion TEC 3.8 or later TEC eent forwarding To exploit launch-in-context support from the TEC to the System Automation operations console, Tioli System Automation eents must be sent to the TEC, which is why you must enable TEC eent forwarding for System Automation Application Manager in your enironment: You can set up TEC eent forwarding during the installation of the component (see IBM Tioli Enterprise Console connection configuration data on page 22) or at any time after the installation is complete (this is described in the IBM Tioli System Automation Application Manager Administrator s and User s Guide, chapter "Using Tioli Enterprise Console with System Automation Application Manager"). Web browser is required for the Jaa ersion of the TEC Eent Console If the Jaa ersion of the TEC Eent Console is to be used to launch to the SA operations console, a Web browser (Mozilla, Firefox, or Internet Explorer) must be installed on the system where the eent console runs. Copyright IBM Corp. 2006,

146 Installing the IBM TEC extension For the TEC Web console client, no installation steps are required. You can directly progress to the configuration steps described in Configuring the TEC extension for System Automation Application Manager. You only need to perform the installation steps described in this chapter if you are using the Jaa ersion of the TEC Eent Console or the TEC eent iewer embedded in TEP: When you are using the Jaa ersion of the TEC Eent Console, the IBM TEC Extension for System Automation Application Manager needs to be installed on the system where the TEC Eent Console runs. When you are using the TEC eent iewer embedded in the TEP and the TEP is started using the browser client interface, the IBM TEC Extension for System Automation Application Manager needs to be installed on the system where the browser runs. To install the IBM TEC Extension on AIX, Linux or Windows perform these steps: 1. Insert the System Automation Application Manager product CD into the CD drie of the system where the TEC serer is running. 2. Open a command prompt (Windows) or a command shell (Linux, AIX). 3. Change to the directory ecext on the product CD or in the electronic distribution directory structure. 4. Start the installation program, using this command: jaa jar setup.jar 5. Follow the installation instructions. To install the IBM TEC Extension on z/os perform these steps: 1. Find the installer in SMPE_INSTALL_ROOT/install/tec_ext_installer. 2. FTP the installer in binary mode to the location where it will be installed. 3. Open a command prompt. 4. Change to the directory at the chosen location. 5. Start the installation program, using this command: jaa jar setup.jar 6. Follow the installation instructions. Configuring the TEC extension for System Automation Application Manager To enable the launch-in-context feature, complete the following steps: 1. Optional: Adapt the configuration file isc.properties to your enironment 2. Define a custom button for the TEC Eent Console See the following sections for a more detailed description of these steps. Adapting the configuration file to your enironment This is an optional configuration step. You can use the configuration file isc.properties to configure the host name and port of Integrated Solutions Console. The file is generated by the installer. If you 130 System Automation Application Manager: Installation and Configuration Guide

147 want to change the alues specified at the installation, you can change the content of the configuration file. Depending on the TEC Eent Console setup, this file is located in the following directory: TEC Eent Console is installed as a Jaa Swing client or TEC eent iewer embedded in TEP The file resides in the same directory where the IBM TEC Extension for System Automation Application Manager is installed. TEC Web console client The file can be found in the directory <was_root>/profiles/ <serer_name>/tioli/eez Example of a configuration file: isc.serer = e2eserer1 isc.port = 9060 isc.serer is the hostname where the ISC runs which hosts the Tioli System Automation operations console. isc.port is the port that is used to access the ISC. Defining a custom button for the Jaa ersion of the TEC Eent Console (Jaa Swing Client) and the TEC eent iewer embedded in TEP Perform these steps: 1. Open the Jaa ersion of the TEC Eent Console. 2. Select Windows > Configuration. Naigate to the console where you want to define the button. Right click Properties. 3. Select the Custom Button entry from the list on the left side of the panel. 4. Click Create Button. 5. Enter a label for the button, for example, Launch SA Console, and the location of EEZLaunchSA. The syntax of the script is: For Windows: <path>eezlaunchsa.bat [<jaa home>] Example: "C:\Program Files\IBM\TECExtension\EEZLaunchSA.bat" C:\IBM\tec_console\jre\bin\ For AIX and Linux <path>eezlaunchsa.sh [<jaa home>] where <path> is the directory in which the TEC Extension for System Automation was installed and the optional parameter <jaa home> is the Jaa home directory where the file jaa.exe can be found. This parameter must end with a / (slash) (Linux and AIX) or with \ (backslash) (Windows). Jaa 1.3 or higher is required. If the path contains blanks it must be enclosed in quotes ( ). 6. Ensure that you hae enabled Eent selection required for button action. Defining a custom button for the Web ersion of the TEC Eent Console For the definition of a Web custom button, the Jaa ersion of the TEC Eent Console is required. Chapter 9. Installing and configuring the IBM TEC extension for the System Automation Application Manager 131

148 To define the button, do this: 1. Open the Jaa ersion of the TEC Eent Console. 2. Select Windows > Configuration. Naigate to the console where you want to define the button. Right click Properties. 3. Select the Web Custom Button entry from the list on the left side of the panel. 4. Click Create Button. 5. Enter a label for the button, for example, Launch SA Console, and the URL of the Serlet: where <isc_serer> is the name of the host where the ISC runs which hosts the Tioli System Automation operations console and <isc_port> is the port that is used to access the ISC. Example: 6. Ensure that you hae enabled Eent selection required for button action. 132 System Automation Application Manager: Installation and Configuration Guide

149 Chapter 10. Setting up Tioli Enterprise Portal launch-in-context support If you are using both the System Automation operations console and Tioli Enterprise Portal (TEP) for resource monitoring and management, you can set up launch-in-context support for Tioli Enterprise Portal. Launch-in-context support enables users to launch Tioli Enterprise Portal workspaces from the System Automation operations console with a single mouse click. When Tioli Enterprise Portal launch-in-context support is configured, a hyperlink becomes aailable on the General page for first-leel automation domains and nodes on the System Automation operations console, allowing users to open the corresponding Tioli Enterprise Portal work spaces with a single mouse click. For launch-in-context support to work properly, a corresponding workspace must be aailable in Tioli Enterprise Portal. This also means that the corresponding ITM agents for the objects that are displayed in the SA operations console must be installed, for example, the operating system agent for a displayed system, or the cluster agent for a MSCS cluster, or the corresponding agent for a z/os sysplex. The context that is used to find a Tioli Enterprise Portal workspace is as follows: Table 43. Context used to find a Tioli Enterprise Portal workspace Selected object in the SA operations console Context passed during launch Object searched for to find TEP workspace z/os domain Sysplex name managed_system_name=sysplex_name:* non-z/os first-leel automation domain Domain name managed_system_name=domain_name:* z/os system Node name smfid=node_name non-z/os Node name hostname=node_name system In particular, you hae to ensure the following: For a non-z/os domain, the first part of the managed system name as displayed in the TEP must match the domain name as configured for the automation adapter of this domain For a z/os system, the system name must be identical to the SMFID For a non-z/os system, the host name that is used in the TEP must match the node name as displayed in the SA operations console. Here is a description how to change the host name that is used in the TEP: 1. Stop the OS Monitoring agent on the managed system. 2. When the corresponding entry in the TEP naigator goes offline, select the entry, right-click and select Clear offline entry from the context menu. The entry should disappear. Copyright IBM Corp. 2006,

150 3. Open the configuration file for the monitoring agent, which is located in the following path: install_dir/config/en.config Add the following line: CTIRA_SYSTEM_NAME=<nodename> where <nodename> is the node name exactly as it is presented in the SA operations console. For Windows systems: Add the CTIRA_SYSTEM_NAME ariable to the file KNTENV, which is located in install_dir/tmaitm6. 4. Restart the OS Monitoring agent on the managed system. The system should appear in the TEP naigator with the new name. To set up launch-in-context support for Tioli Enterprise Portal, complete the following steps in Integrated Solutions console (EEZAdministrator priileges are required): 1. Open Integrated Solution Console. 2. In the naigation tree, click IBM Tioli System Automation > Settings > Tioli Enterprise launch-in-context support. 3. In the fields on the page that appears, do this: Enable launch-in-context support for Tioli Enterprise Portal Select to enable launch-in-context support. Serer name Specify the name of the serer on which Tioli Enterprise Portal runs. Port number Specify the port number of the serer on which Tioli Enterprise Portal runs. The default port number is Click OK to sae the configuration. Note: If the operations console is displayed while the TEP configuration is changed, select "Menu -> Refresh all" to pick up the changed settings in the current instance of the Operations Console. 134 System Automation Application Manager: Installation and Configuration Guide

151 Part 3. Installing and configuring the end-to-end automation adapters Chapter 11. Oeriew Chapter 12. Installing and configuring the HACMP adapter Installing the HACMP adapter Packaging Installation prerequisites Using SMIT to install the adapter Automating the HACMP adapter Configuring the HACMP adapter Inoking the HACMP adapter configuration dialog Configuring the HACMP adapter Replicating the HACMP adapter configuration files to other nodes in the domain Defining the HACMP adapter automation policy Remoing the HACMP adapter automation policy Verifying the HACMP adapter configuration Controlling the HACMP adapter Packaging Installation prerequisites Using the installation wizard to install the VCS adapter Automating the VCS adapter Configuring the VCS adapter Inoking the VCS adapter configuration dialog 179 Configuring the VCS adapter Replicating the VCS adapter configuration files to other nodes in the domain Defining the VCS adapter automation policy 190 Remoing the VCS adapter automation policy 191 Verifying the VCS adapter configuration Controlling the VCS adapter Chapter 13. Installing and configuring the MSCS adapter Installation and configuration roadmaps Roadmap for highly aailable adapters Roadmap for adapters that are not highly aailable Planning and preparing for the MSCS adapter Packaging Installation prerequisites Planning and preparing for high aailability Installation directories Preparing the user account Installing the MSCS adapter Using the installation wizard to install the MSCS adapter Installing the adapter in silent mode Upgrading the MSCS adapter Configuring the MSCS adapter Inoking the MSCS adapter configuration dialog 160 Configuring the MSCS adapter Replicating the configuration files to other nodes Windows Firewall on Windows Serer Proiding high aailability for the MSCS adapter 170 MSCS high aailability on Windows Serer MSCS high aailability on Windows Serer Verifying the installation and configuration Uninstalling the MSCS adapter Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter Installing the VCS adapter Copyright IBM Corp. 2006,

152 136 System Automation Application Manager: Installation and Configuration Guide

153 Chapter 11. Oeriew System Automation Application Manager can be used to automate the operation of resources within heterogeneous enironments (called first leel automation domains) that each hae a local automation technology of their own. Each first-leel domain is connected to the end-to-end automation manager or an operations console by an end-to-end automation adapter. The purpose of an automation adapter is to Monitor resources within its first-leel automation domain Propagate resource attribute changes to the end-to-end automation manager. Start and stop resources within the first-leel automation domain by request of the end-to-end automation manager or an operator. Proide information for resources that are aailable within the first-leel automation domain. The end-to-end automation adapter uses the Tioli Eent Integration Facility (EIF) to communicate with the end-to-end automation manager. The following chapters describe how you install and configure the automation adapters that are shipped with System Automation Application Manager: Chapter 12, Installing and configuring the HACMP adapter, on page 139 describes how you install and configure the HACMP adapter Chapter 13, Installing and configuring the MSCS adapter, on page 155 describes how you install and configure the MSCS adapter Chapter 14, Installing and configuring the VERITAS Cluster Serer adapter, on page 177 describes how you install and configure the VCS adapter Copyright IBM Corp. 2006,

154 138 System Automation Application Manager: Installation and Configuration Guide

155 Chapter 12. Installing and configuring the HACMP adapter Installing the HACMP adapter The following topics describe how to install and configure the HACMP adapter. Packaging The HACMP adapter is shipped with System Automation Application Manager. The name of the installp package you use for installing the adapter is hac.adapter. This is where you find the installation package: CD: You install the adapter from the CD "Tioli System Automation Application Manager V3.1.0 Automation Adapters all platforms". The installation package is aailable in the installation source directory EEZ3100Adapters/EEZ3100HACMP/ AIX. Electronic distribution: If you obtain System Automation Application Manager through electronic distribution, you use the following archie to install the HACMP adapter: Delierable name: C1A21ML.bin Installation source directory: EEZ3100Adapters/EEZ3100HACMP/AIX Installation prerequisites Note that the HACMP adapter can only be connected to System Automation Application Manager or the End-to-End Automation Management component of IBM Tioli System Automation for Multiplatforms V2.2 or V2.3. The system on which you are installing the adapter must meet the following installation prerequisites: Required minimum HACMP release leel: (PTF5) The HACMP adapter must not run on a node in the RSCT peer domain. If the node on which the adapter is to run preiously was an RSCT peer domain node, the following actions must be taken prior to installing the adapter: 1. The enironment ariable CT_MANAGEMENT_SCOPE, which may be set to 2 for the RSCT peer domain, must be unset. 2. The RSCT peer domain must be stopped using the command: stoprpdomain <domain-name>. The 32-bit ersion of Jaa 1.4 or Jaa 5 SR5 must be installed. SSL/SSH packages must be installed and the sshd subsystem must be running to be able to complete the Replication task of the adapter configuration Using SMIT to install the adapter You will find the package in the directory on the CD or in the electronic delierable as described in Packaging. Package name: hac.adapter. Use the SMIT interface to install the adapter. The HACMP adapter installation directory is /opt/ibm/tsamp/eez/hac Copyright IBM Corp. 2006,

156 Note: Do not change the installation directory or the configuration directory (/etc/opt/ibm/tsamp/eez/hac/cfg). Otherwise, the HACMP adapter cannot be run because it relies on fixed paths. After installing the adapter it must be configured as described in the remaining sections of this chapter. Automating the HACMP adapter If the HACMP cluster consists of more than one node, the HACMP adapter must be automated for the following reasons: The host using the adapter must be able to reach the adapter always through the same serice IP without reconfiguration. If the node on which the adapter runs goes down or the HACMP cluster serices on that node are stopped, the adapter must moe to another aailable node in the cluster to resume the connection with the host using the adapter. For more information about automating HACMP adapters using the adapter configuration dialog, see Automation tab on page 145. Configuring the HACMP adapter The following figure shows in which enironments the HACMP adapter can work and what needs to be configured for the adapter. 140 System Automation Application Manager: Installation and Configuration Guide

157 Figure 5. Configuration of the HACMP adapter You must configure the adapter for end-to-end automation management using System Automation Application Manager. For more information on end-to-end automation management, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide. You can also configure the HACMP adapter in silent mode using an input properties file. See Inoking silent configuration on page 103 for more details. Inoking the HACMP adapter configuration dialog The HACMP adapter can be configured with the cfghacadapter utility. The cfghacadapter utility is an X-Windows application and must be used from a workstation with X-Windows serer capabilities. This could be one of your cluster nodes, if the X11 optional feature is installed on that node. To use the HACMP adapter configuration dialog you, must be logged in to the system with the user ID root or you must hae write access to the directory /etc/opt/ibm/tsamp/eez/hac/cfg. Issue the cfghacadapter command to inoke the configuration dialog. The main panel of the dialog is displayed: Chapter 12. Installing and configuring the HACMP adapter 141

158 The dialog lets you perform the following tasks: 1. Configure the HACMP adapter. 2. Replicate the HACMP adapter configuration files to other nodes. 3. Define the HACMP adapter automation policy to create the resources required to automate the adapter. 4. Remoe the HACMP adapter automation policy. Configuring the HACMP adapter On the main panel of the configuration dialog, click Configure to display the configuration tabs that are described in the following sections. In the following description, the term Host using the adapter is used to refer to the end-to-end automation manager host. 142 System Automation Application Manager: Installation and Configuration Guide

159 Adapter tab On the Adapter tab, you can configure the adapter host. Fields and controls on the Adapter tab: Automation adapter host: Host name or IP address Host name or serice IP label of the node where the adapter runs. On initial inocation, the field contains the alue the command hostname would return. If you are automating the adapter, leae the alue unchanged. The alue will be updated automatically with the alue you specify in the field Serice IP label on the Automation tab (see Automation tab on page 145). Request port number The port on which the adapter listens for requests from the host using the adapter. The default port is Clicking Adanced lets you specify the adapter runtime behaior: Adapter stop delay The number of seconds by which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You may need to increase the alue on slow systems. Valid alues are 3 through 60. Remote contact actiity interal The time period, in seconds, after which the adapter will stop if it was not contacted by the host using the adapter, which periodically contacts the adapter to check if it is still running. The Chapter 12. Installing and configuring the HACMP adapter 143

160 default alue is 360. If a alue other than 0 is specified, the interal must be a multiple of the check interal. When the alue is set to 0, the adapter continuously runs and neer stops. Initial contact retry interal The time period, in minutes, within which the adapter will attempt to contact the host using the adapter until it succeeds or the specified time has elapsed. The default alue is 0, which means that the adapter will attempt to contact the host using the adapter indefinitely. EIF reconnect attempt interal The time period, in seconds, that the adapter will wait before it attempts to reestablish the connection to the host using the adapter after the connection was interrupted. The default alue is 30. Host using adapter tab Use the Host using adapter tab to determine which host the adapter connects to and to specify the required information. The HACMP adapter must be configured to connect to an end-to-end automation manager host. Fields on the Host using adapter tab: Configure the System Automation Application Manager host: Host name or IP address The name or IP address of the host on which the end-to-end 144 System Automation Application Manager: Installation and Configuration Guide

161 automation manager runs. The port number specified here must match the port number specified as eent port number when configuring the domain of the end-to-end automation manager. Eent port number The port to which the end-to-end automation manager listens for eents from the HACMP adapter. The default port is Automation tab This tab lets you configure the adapter automation policy. This allows you to make the end-to-end automation adapter highly aailable, meaning that if the node on which the adapter runs breaks down, the adapter will be restarted on another node in the domain. Note: All nodes where the adapter can run must be accessible using the same user ID and password. Fields and controls on the Automation tab: Automate adapter in first-leel automation domain Select this check box (see also Automating the HACMP adapter on page 140). Query domain If the configuration dialog runs on a node in the HACMP cluster, click Query domain to query the current automation policy from the HACMP cluster. If the automation policy for the adapter is not yet defined but the cluster is up, at least all nodes that are online are shown in the Defined nodes table. This table proides the following information: Defined node The list of defined nodes. Automate on node Chapter 12. Installing and configuring the HACMP adapter 145

162 Indicates if the adapter is automated on this node. The buttons at the bottom of the table let you perform the following tasks: Up Moes the selected node one position up in the node sequence. The position determines the order in which automation selects the node on which the adapter may run. Down Moes the selected node one position down in the node sequence. The position determines the order in which automation selects the node on which the adapter may run. Add Displays the Add node for adapter automation panel which lets you define the name of the node to be added and determine if the node is to be added to automation of the adapter. Remoe Remoes the selected node from the list. This means that the adapter must not be started on that node. Change Displays the Change node for adapter automation panel which lets you change the name of the node and add or remoe the node from automation of the adapter. HACMP root directory Shows the root directory where HACMP is installed. Automated resources prefix The prefix that is used to compose the names of the resource group, application, and application monitor in the automation policy. The resource names will appear in the resource table on the operations console. The prefix can be changed. Use no more than a total of 28 alphanumeric characters and underscores. Do not use a leading numeric. Resered words are not allowed (see the "List of Resered Words" in the HACMP Administration Guide, SC ). Note that if the HACMP adapter policy has been defined using the current prefix, you must remoe this policy before changing the prefix. For more information about defining the adapter automation policy, refer to Defining the HACMP adapter automation policy on page 151. Serice IP label The Serice IP label is an entry in /etc/hosts that represents a serice IP label. It must be different from the host name of any node in the HACMP cluster. It should be requested from the network administrator as a "serice IP label" or "alias" for all nodes in the HACMP cluster and must hae been created (for example, using the SMIT interface) before you inoke the configuration dialog. The HACMP adapter will listen on the serice IP label for requests from the host using the adapter, regardless on which node it runs. 146 System Automation Application Manager: Installation and Configuration Guide

163 Security tab The security tab lets you configure the security for the interface between the HACMP adapter and the System Automation Application Manager host. Fields and controls on the Security tab: Select the Enable SSL check box if you want to use the Secure Socket layer (SSL) protocol. If checked, the following entry fields must be completed. Truststore Name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore password Password of the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Keystore alias Note: If the truststore is in different file than keystore, the passwords for the files must be identical. Alias name of the certificate to be used by the serer. If not specified, the keystore file must contain only one entry which is the one to be used. The Enforce user authentication check box enables user authentication with the Pluggable Access Module (PAM). This check box is selected by default. It should only be deselected for test purposes when user authentication is not required. PAM Serice The name of an entry in file /etc/pam.conf that determines which Chapter 12. Installing and configuring the HACMP adapter 147

164 check are made to authenticate a user. The default alue is su, which checks users as if they were trying to execute the command su. Logger tab Use the Logger tab to specify the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Note that the Logger tab always displays the alues that are currently set in the configuration file. On the Logger tab, you can perform the following tasks: Change the settings permanently Perform these steps: 1. Make the required changes on the tab. 2. Click Sae. Results: The settings in the configuration file are updated. You must restart the adapter for the changes to take effect. Change the settings temporarily Perform these steps: 1. Make the required changes on the tab. 2. Click Apply. Results: The new settings take effect immediately. They are not stored in the configuration file. If the adapter is not running, you receie an error message. 148 System Automation Application Manager: Installation and Configuration Guide

165 Reert to the permanent settings If you changed the settings temporarily, perform the following steps to reert to the permanent settings defined in the configuration file, or when you are unsure which settings are currently actie for the adapter: 1. Inoke the configuration dialog and open the Logger tab. The Logger tab displays the alues that are currently set in the configuration file. 2. Click Apply to actiate the settings. Results: The settings take effect immediately. If the adapter is not running, you receie an error message. Controls and fields on the Logger tab: Maximum log/trace file size The maximum file size in kilobytes that each log file can reach before it rolls oer. Message logging leel: Error Warning Information Logs messages on the error leel. Logs messages on the error and warning leels. Logs messages on the error, warning and informational leels. Trace logging leel: Off Minimum Medium Maximum Collects no trace information. (Not recommended.) Collects trace information on the error leel. Only seere error situations are traced. This is the default setting. Collects trace information on the error and warning leels. Proides the message and trace logs and collects additional information on the error, warning, and informational leel. Required for testing and problem determination. First failure data capture (FFDC) settings: Recording leel: Off Collects no FFDC information. Minimum Proides the message and trace logs and collects additional information on the error leel. Medium Proides the message and trace logs and collects additional information on the error and warning leel. Maximum Proides the message and trace logs and collects additional information on the error, warning, and informational leel. Disk space: Maximum disk space Specifies the maximum disk space in bytes used by FFDC traces which are written to the FFDC trace directory. The default space is byte (10MB). Space exceeded policy Select what to do if the maximum disk space is exceeded: Chapter 12. Installing and configuring the HACMP adapter 149

166 Ignore Issue warnings, but do not enforce the FFDC disk space quota. Auto-delete Automatically delete FFDC files, oldest first, until the directory is below the limit. This is the default setting. Message IDs: Filter mode Message ID list Suspend Halt further FFDC actions until the directory is manually cleaned up. Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. Specifies the message IDs that are to trigger tracing, depending on the filter mode. Wildcards, for example, *E (for all error messages), are allowed. Saing the configuration Click Sae on the configuration dialog to sae your changes to the adapter configuration files. Upon completion, the Configuration update status panel appears, showing the list of configuration files that were updated. Notes: 1. If the serice IP label specified on the Automation tab does not match the host specified on the Adapter tab, you are prompted for input. On the panel that appears, click the button Adapter automation. 2. When entries are missing or a alue you hae entered is out of range (for example, a port number), an error message is displayed. 3. If you made changes on the Automation tab, a message appears reminding you to launch the Define automation policy task. 4. If not noted otherwise, you must restart the adapter for the changes to become effectie. 150 System Automation Application Manager: Installation and Configuration Guide

167 Replicating the HACMP adapter configuration files to other nodes in the domain After configuring an HACMP adapter on a node, you use the Replicate function to propagate the changes to the other nodes in the HACMP cluster. To use the Replicate function, go to the main panel of the configuration dialog and click Replicate. The Replicate configuration files panel is displayed: Use this window to distribute (replicate) the HACMP adapter configuration itself or configuration updates to the remaining nodes in the HACMP cluster: 1. Select the configuration files you want to replicate or click Select all to select all configuration files in the list. 2. If the user ID and password you specified are alid on all nodes, you can click Select all below the list of replication target nodes. This ensures that the adapter configuration is identical on all nodes. 3. Enter the user ID and password for the target nodes you want to replicate the files to. 4. Start the replication by clicking Replicate. Replication may take a while. While the files are being replicated, the Replicate button is indented and grayed-out. When the replication is complete, the replication status of each configuration file is displayed. Defining the HACMP adapter automation policy If definitions for the automation of the HACMP adapter hae been made, clicking Define on the main panel of the configuration dialog will create the resources with the resource name (Resource-/group prefix) as described on page 146. Note that if automated resources with the same name already exist, they are remoed before the new resources are created. If you used the default resource name prefix, the following resources will be defined or queried: Table 44. Resources in the HACMP adapter automation policy Resource class Resource name Description IBM.HacmpResourceGroup hacadapter_rg The resource group that comprises all automated resources. IBM.HacmpApplication hacadapter Commands: hacadapter start, hacadapter stop IBM.HacmpAppMonitor hacadapter_mon Command: hacstatus Chapter 12. Installing and configuring the HACMP adapter 151

168 Table 44. Resources in the HACMP adapter automation policy (continued) Resource class Resource name Description IBM.HacmpSericeIP <serice_ip_label> alue The label of the serice IP on which the host using the adapter accesses the adapter.this alue is not defined but just queried and, therefore, not remoed. When you click Define, the button may stay indented for minutes until the resources hae been remoed, the cluster is synchronized, the new resources are created, and the cluster is synchronized again. The dialog will not repaint after it has been coered and uncoered. Eentually, the results of the commands are displayed in a pop-up window. Remoing the HACMP adapter automation policy You typically use the Remoe function before you change the name prefix of the automated resources (see page 146). When the adapter is automated and you deselect the check box Automate adapter in system automation domain on the Automation tab, you receie a message reminding you to remoe the automated resources for the adapter. Clicking Remoe on the main panel of the configuration dialog will remoe the resources shown in Table 44 on page 151. If the HACMP adapter is still running, it is stopped before the automated resources are remoed. When you click Remoe, the button may stay indented for minutes until resources hae been remoed and the cluster has been synchronized. Eentually, the results of the commands are displayed in a pop-up window. Verifying the HACMP adapter configuration You can use the clstat command to erify that the HACMP adapter is running: 1. Open a terminal session on the nodes on which the HACMP adapter may run. 2. In each session, type /usr/es/sbin/cluster/clstat 3. The status screen depicted below should be displayed: Resource Group: hacadapter_rg (if the prefix is hacadapter ) in State: On line Interface: p57067ha (in the example configuration) associated with the serice IP label of the same name in State: UP 152 System Automation Application Manager: Installation and Configuration Guide

169 clstat - HACMP Cluster Status Monitor Cluster: hacp57067 ( ) Mon Feb 20 14:15:16 MET 2006 State: UP Nodes: 2 SubState: STABLE Node: p570sa06 State: UP Interface: p570sa06 (0) Address: State: UP Interface: p57067ha (0) Address: State: UP Resource Group: hacadapter_rg State: On line Node: p570sa07 State: UP Interface: p570sa07 (0) Address: State: UP ************************ f/forward, b/back, r/refresh, q/quit ********* Controlling the HACMP adapter Table 45. HACMP adapter command options Command Description hacadapter status hacadapter start hacadapter stop You use the hacadapter command to start, stop, and monitor the adapter. Checks if the adapter is running and returns the RSCT return code for its operational state (OpState): 0 Unknown. The adapter status cannot be determined. 1 Online. The adapter is running. 2 Offline. The adapter is not running. Starts the adapter if it is not running: If the adapter is automated, the command requests HACMP cluster serices to start the adapter on the preferred node. The command returns when the clrgmoe command completed. If the adapter is not automated, it is started on the node where the command was issued. The exit code is 0 if the command was successful. Stops the adapter if it is running: If the adapter is automated, the command requests HACMP cluster serices to stop the adapter on the node where it is currently actie. The command returns when the clrgmoe command completed. If the adapter is not automated, it is stopped on the node where the command was issued. The exit code is 0 if the command was successful. Chapter 12. Installing and configuring the HACMP adapter 153

170 154 System Automation Application Manager: Installation and Configuration Guide

171 Chapter 13. Installing and configuring the MSCS adapter The following topics describe how to install and configure the MSCS adapter. Installation and configuration roadmaps Before you install the MSCS adapter, you must decide whether you want to make the adapter highly aailable, which is strongly recommended. The roadmaps proided in this section gie an oeriew of the steps you need to perform to install and configure the adapter depending on your high-aailability decision. Roadmap for highly aailable adapters If you are making your adapter highly aailable, which is highly recommended, perform the following steps: 1. Plan and prepare for the installation and configuration of the MSCS adapter (see Planning and preparing for the MSCS adapter on page 156). 2. Use the installation wizard to install the adapter on one node in the cluster and generate a response file (see Using the installation wizard to install the MSCS adapter on page 159). 3. To ensure that uniform installation parameters are used, use the response file to install the adapters on the remaining nodes. Response-file drien installation can be performed in silent mode (see Installing the adapter in silent mode on page 160) or in interactie mode using the installation wizard (see Using the installation wizard to install the MSCS adapter on page 159). 4. Configure the adapter on one of the cluster nodes using the adapter configuration dialog (see Configuring the MSCS adapter on page 160). 5. To ensure that uniform configuration parameters are used, replicate the adapter configuration files to the remaining nodes (see Replicating the configuration files to other nodes on page 168). 6. Create the MSCS resources needed for making the adapter highly aailable. 7. Verify the installation and configuration (see Verifying the installation and configuration on page 176). Roadmap for adapters that are not highly aailable If you are not making your adapter highly aailable, perform the following steps: 1. Plan and prepare for the installation and configuration of the MSCS adapter (see Planning and preparing for the MSCS adapter on page 156). 2. Use the installation wizard to install the adapter on a cluster node (see Using the installation wizard to install the MSCS adapter on page 159). Copyright IBM Corp. 2006,

172 3. Configure the adapter using the adapter configuration dialog (see Configuring the MSCS adapter on page 160). 4. Verify the installation and configuration (see Verifying the installation and configuration on page 176). Planning and preparing for the MSCS adapter Packaging The MSCS adapter is shipped with System Automation Application Manager. This is where you find the installation file: CD: You install the adapter from the CD "Tioli System Automation Application Manager V Automation Adapters all platforms". This is where you find the installation wizard file (setup.exe) on the CD: EEZ3100Adapters\EEZ3100MSCS\Windows\setup.exe Electronic distribution: If you obtain System Automation Application Manager through electronic distribution, you use the following archie to install the MSCS adapter: C1A22ML.exe To extract the archie, run the executable. The resulting directory structure is identical to that on the CD. This is where you find the installation wizard file (setup.exe) when you hae extracted the archie: EEZ3100Adapters\EEZ3100MSCS\Windows\setup.exe Installation prerequisites Note that the MSCS adapter can only be connected to System Automation Application Manager or the End-to-End Automation Management component of IBM Tioli System Automation for Multiplatforms V2.2 or later. The system on which you are installing the adapter must meet the following installation prerequisites: Windows Serer 2003 Enterprise Edition (32-bit) with Serice Pack 1 or later Windows Serer 2008 Enterprise Edition (32-bit) System must be an MSCS node 64 MB RAM is required for running the MSCS adapter serice 40 MB RAM is required for running the adapter configuration dialog Disk space requirements: 140 MB for MSCS adapter installation Typically, 6 MB is sufficient during normal operation, howeer, up to 250 MB may be required for serice-related files in the Tioli Common Directory (log files, FFDC files) Planning and preparing for high aailability Making the MSCS adapter highly aailable using MSCS is highly recommended but not required. To prepare for making an adapter highly aailable, do this: Obtain a irtual IP address: 156 System Automation Application Manager: Installation and Configuration Guide

173 The MSCS adapter will use this IP address for incoming connections MSCS will make the irtual IP address aailable on the appropriate MSCS node If desired, obtain a network name: If you specify the network name in the MSCS adapter configuration, the name will be published to the System Automation Application Manager serer. The System Automation Application Manager serer will use this network name for connecting to the MSCS adapter MSCS will associate this network name with the irtual IP address on the DNS serer that is configured in the Microsoft Windows domain Installation directories For the MSCS adapter installation directory and the Tioli Common Directory, the following restrictions apply: The MSCS adapter installation directory name must not include the DBCS space character. The SBCS space character is supported. Tioli Common Directory: When specifying a directory other than the default, obsere the following restrictions: The directory name has to consist of the platform-specific path separator character and alphanumeric characters (A..Z, a..z, 0..9). The colon character is allowed only once, immediately following the drie letter. For example, C:\<directory_name> is allowed, but C:\<directory_name>:<directory_name> is not allowed. The space character and the underscore character (_) are allowed. Preparing the user account For the installation and operation of the MSCS adapter, a special purpose domain user account with local administratie rights must be defined in the domain. This domain user account must be a member of the local Administrators group on all nodes of the cluster the adapter will manage. Before you install the MSCS adaptor you must perform the following steps: Create a special purpose domain user account which will run the MSCS adapter serice later on. This user is referred to as SAAMAdapter hereon. Grant SAAMAdapter full control permission oer the Microsoft Serer Cluster / failoer cluster to be managed with the MSCS adapter: Open Cluster Administrator / Failoer Cluster Management and naigate to this serer cluster / failoer cluster. Right-click this failoer cluster and select the Properties context menu entry. In the Properties window select the Security / Cluster Permissions tab. On the Security / Cluster Permissions tab select the Add... button. In the Select Users, Computer, or Groups window specify the SAAMAdapter user account and select the OK button. On the Security / Cluster Permissions tab select the added domain user account in the Group or user names list. Specify Allow on the Full Control entry in the Permissions for... list. Select the OK button. Chapter 13. Installing and configuring the MSCS adapter 157

174 Installing the MSCS adapter Log into each system where you want to install the MSCS adapter, using an account with administratie rights on the system. Use the local group policy editor to grant the SAAMAdapter user account the right Log on as a serice : Open the Start menu and select menu entry Run.... In the Run window, specify gpedit.msc in the Open input field and select the OK button. In the Local Group Policy Editor window, select the entry in the tree iew: Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. In the Local Group Policy Editor window the list iew now shows a list of user rights. Double-click the right Log on as a serice. In the Log on as a serice Properties window select the Add User or Group... button. In the Select Users, Computer, or Groups window specify the SAAMAdapter user account. Select the OK button. In the Log on as a serice Properties window select the OK button. Close the Local Group Policy Editor window. Log into each system where you want to install the MSCS adapter using an account with administratie rights on the system. Use the local users and groups editor to make the SAAMAdapter user account a member of the local Administrators group: Open the Start menu and select the menu entry Run.... In the Run window specify lusrmgr.msc in the Open input field and select the OK button. In the Local Users and Groups window select the Groups entry in the tree iew. In the Groups window right-click the Administrators group in the list iew and select the Add to Group... context menu entry. In the Administrators Properties window select the Add... button. In the Select Users, Computer, or Groups window specify the SAAMAdapter user account. Select the OK button. In the Administrators Properties window select the OK button. Close the Local Users and Groups window. You hae the following options to install an MSCS adapter: You use the installation wizard to install the adapter. You generate a response file when you use the installation wizard on a node. You can then use the response file in one of two ways to install the adapter on other nodes: You launch the installation wizard using the response file as input. The alues in the response file will appear in the fields on the wizard panels and can be changed. You can install the adapter in silent mode on the remaining nodes of the cluster if you are making the adapter highly aailable, in which case the alues in the response file apply to all nodes. 158 System Automation Application Manager: Installation and Configuration Guide

175 Using the installation wizard to install the MSCS adapter This section describes how you install the MSCS adapter using the installation wizard. For information on silent mode, see Installing the adapter in silent mode on page 160. Perform the following steps to install the adapter: 1. Log in with the domain user account prepared in Preparing the user account on page Launch the installation wizard. You hae the following options: To launch the installation wizard without generating a response file, use the file: setup.exe When you launch the wizard in this way, the alues that are displayed on the wizard panels are either default alues or alues that were detected on your system. To launch the installation wizard, generating a response file, use the following command: setup.exe -Dpreparesilent=true This is the response file that is generated: <install_root>/install/install.properties When you launch the wizard in this way, the alues that are displayed on the wizard panels are either default alues or alues that were detected on your system. When you hae launched the wizard, click Next on the Welcome panel to display the license agreement. 3. Select I accept both the IBM and the non-ibm terms. to agree to the license agreement. Click Next. The Installation directory panel is displayed. 4. Specify the directory where you want to install the adapter or accept the default location. Click Next to display the Tioli Common Directory panel. 5. If the installation program did not detect a Tioli Common Directory on your system, accept the default location or specify a different directory. If a Tioli Common Directory was detected on your system, the directory is displayed and cannot be changed. Click Next to display the Microsoft Cluster Adapter serice user panel. 6. Specify the domain user account prepared in Preparing the user account on page 157 and the password. Click Next to display the summary panel. 7. Check the alues on the summary panel and click Install to start the installation. 8. While the adapter is being installed, a progress panel is displayed. Chapter 13. Installing and configuring the MSCS adapter 159

176 When the installation is complete, an installation summary panel is displayed, on which you can erify the success of the installation. If problems occur, check the applicable installation log files for more information. Click Finish to close the installation wizard. Installing the adapter in silent mode This section describes how you install the adapter in silent mode, using a response file you generated during wizard-drien installation. For information on how to generate a response file and how to use it as input for a wizard-drien installation, see Using the installation wizard to install the MSCS adapter on page 159. Upgrading the MSCS adapter To install the MSCS adapter in silent mode, use the following command: setup.exe -i silent -f <response_file_name> Notes: 1. Response files contain password information and should be deleted when they are no longer needed. 2. The silent installation will only be successful if the wizard-drien installation where the response file was generated completed successfully without errors. You can upgrade an already installed MSCS adapter to the current ersion by running the installation as described in Installing the MSCS adapter on page 158. If you upgrade from IBM Tioli System Automation for Multiplatforms 2.2 or 2.3 MSCS adapter to System Automation Application Manager 3.1 or higher, and hae made the MSCS adapter highly aailable using MSCS, you need to update the MSCS resource of type Generic Serice used for controlling the MSCS adapter Windows serice. The new serice name to be controlled is SA AM MSCS Adapter. Configuring the MSCS adapter You use the adapter configuration dialog to configure your MSCS adapter. If your MSCS adapter is highly aailable, you always configure the adapter on one node and replicate the configuration file to the remaining cluster nodes as described in Replicating the configuration files to other nodes on page 168. You must configure the adapter for end-to-end automation management using the end-to-end automation manager. For more information on end-to-end automation management, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide. You can also configure the MSCS adapter in silent mode using an input properties file. See Inoking silent configuration on page 103 for more details. Inoking the MSCS adapter configuration dialog To inoke the configuration dialog, issue the following command: cfgmscsadapter The file is located in the adapter installation directory, in the subdirectory bin. The default directory is 160 System Automation Application Manager: Installation and Configuration Guide

177 C:\Program Files\IBM\tsamp\eez\mscs\bin Note: On Windows Serer 2008, the configuration dialog must be started with Administrator priileges. Otherwise the configuration program is unable to write changed configuration files to the right location. Use the following procedure to obtain a command prompt with Administrator priileges which can be used to run the configuration dialog: 1. Log on with the domain user account prepared in section Preparing the user account on page In the Windows Start menu, select All Programs -> Accessories. 3. Right-click the entry named Command Prompt. 4. In the context menu for Command Prompt, select the entry Run as administrator. The main panel of the configuration dialog is displayed: The dialog lets you perform the following tasks: 1. Configure the MSCS adapter. 2. Replicate the MSCS adapter configuration files to other nodes. 3. Define the MSCS adapter automation policy to create the resources required to automate the adapter. 4. Remoe the MSCS adapter automation policy. Configuring the MSCS adapter On the main panel of the configuration dialog, click Configure to display the configuration tabs that are described in the following sections. In the following description, the term Host using the adapter is used to refer to the end-to-end automation manager host. Chapter 13. Installing and configuring the MSCS adapter 161

178 Adapter tab On the Adapter tab, you can configure the adapter host. Fields and controls on the Adapter tab: Automation adapter host: Host name or IP address If the MSCS adapter is highly aailable, specify the network name or IP address you obtained as described in Planning and preparing for high aailability on page 156. If the MSCS adapter is not highly aailable, specify the IP address or host name of the system on which the adapter is running. Request port number Specify the number of the port on which the adapter listens for eents from host using the adapter. The default port is Automation domain The domain name is the name by which the Microsoft Serer Clustering (MSCS) cluster is known to the host using the adapter. The domain name must be unique within the scope of automation domains that connect to an end-to-end automation manager or a System Automation operations console. You hae the following options to specify the domain name: It is recommended that you use the MSCS cluster name as domain name. This option is selected by default. You must keep this setting if you want to use Tioli Enterprise Portal launch-in-context support, which allows you to launch 162 System Automation Application Manager: Installation and Configuration Guide

179 Tioli Enterprise Portal work spaces from the System Automation operations console, because Tioli Enterprise Portal will not recognize any other domain name. If you cannot use the MSCS cluster name as domain name, for example, because it would not be unique, you can specify a domain name for the Microsoft Serer Clustering (MSCS) cluster. Clicking Adanced lets you specify the adapter runtime behaior: Adapter stop delay The number of seconds by which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You may need to increase the alue on slow systems. Valid alues are 3 through 60. Remote contact actiity interal The time period, in seconds, after which the adapter will stop if it was not contacted by the host using the adapter, which periodically contacts the adapter to check if it is still running. The default alue is 360. If a alue other than 0 is specified, the interal must be a multiple of the check interal. When the alue is set to 0, the adapter continuously runs and neer stops. Initial contact retry interal The time period, in minutes, within which the adapter will attempt to contact the host using the adapter until it succeeds or the specified time has elapsed. The default alue is 0, which means that the adapter will attempt to contact the host using the adapter indefinitely. EIF reconnect attempt interal The time period, in seconds, that the adapter will wait before it attempts to reestablish the connection to the host using the adapter after the connection was interrupted. The default alue is 30. Host using adapter tab Use the Host using adapter tab to determine which host the adapter connects to and to specify the required information. The MSCS adapter must be configured to connect to a System Automation Application Manager host. Chapter 13. Installing and configuring the MSCS adapter 163

180 Fields on the Host using adapter tab: Configure the end-to-end automation manager host: Host name or IP address The name or IP address of the host on which the end-to-end automation manager runs. The port number specified here must match the port number specified as eent port number when configuring the domain of the end-to-end automation manager. Eent port number The port on which the end-to-end automation manager listens for eents from the MSCS adapter. The default port is Security tab Use the Security tab to configure security for the interface between the MSCS adapter and the System Automation Application Manager host. 164 System Automation Application Manager: Installation and Configuration Guide

181 Select the Enable SSL check box if you want to use the Secure Socket layer (SSL) protocol. If checked, the following fields must be completed: Truststore Name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore password Password of the keystore file. It is required if a keystore file was specified. Click Change to change the password. Keystore alias Note: If the truststore is in different file than keystore, the passwords for the files must be identical. Alias name of the certificate to be used by the serer. If not specified, the keystore file must contain only one entry which is the one to be used. User authentication It is recommended that you select the corresponding check box to enforce authentication of the user ID on behalf of which the host using the adapter requests operations from the MSCS adapter. Logger tab Use the Logger tab to specify the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Note that the Logger tab always displays the alues that are currently set in the configuration file. Chapter 13. Installing and configuring the MSCS adapter 165

182 On the Logger tab, you can perform the following tasks: Change the settings permanently Perform these steps: 1. Make the required changes on the tab. 2. Click Sae. Results: The settings in the configuration file are updated. You must restart the adapter for the changes to take effect. Change the settings temporarily Perform these steps after ensuring that the adapter is running: 1. Make the required changes on the tab. 2. Click Apply. Results: The new settings take effect immediately. They are not stored in the configuration file. If the adapter was not running, you receie an error message. Reert to the permanent settings If you changed the settings temporarily, perform the following steps to reert to the permanent settings defined in the configuration file, or when you are unsure which settings are currently actie for the adapter: 1. Inoke the configuration dialog and open the Logger tab. The Logger tab displays the alues that are currently set in the configuration file. 2. Click Apply to actiate the settings. Results: The settings take effect immediately. If the adapter is not running, you receie an error message. 166 System Automation Application Manager: Installation and Configuration Guide

183 Controls and fields on the Logger tab: Maximum log/trace file size The file size in kilobytes. Message logging leel: Error Warning Information Logs messages on the error leel. Logs messages on the error and warning leels. Logs messages on the error, warning and informational leels. Trace logging leel: Off Minimum Medium Maximum Collects no trace information. Collects trace information on the error leel. Collects trace information on the error and warning leels. Proides the message and trace logs and collects additional information on the error, warning, and informational leel. First failure data capture (FFDC) settings: Recording leel: Off Collects no FFDC information. Minimum Proides the message and trace logs and collects additional information on the error leel. Medium Proides the message and trace logs and collects additional information on the error and warning leel. Maximum Proides the message and trace logs and collects additional information on the error, warning, and informational leel. Disk space: Maximum disk space Specifies the maximum disk space in bytes used by FFDC traces which are written into the FFDC trace directory. The default space is byte (10MB). Space exceeded policy Select what to do if the maximum disk space is exceeded. Message IDs: Filter mode Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. Message ID list: Specifies the message IDs which trigger the tracing of the FFDC data. Wildcards like *E, meaning all error messages, are allowed. Saing the configuration Click Sae to sae your settings to the adapter configuration files. Upon completion, the configuration update status panel appears, showing the list of configuration files that were updated. Notes: 1. When entries are missing or a alue you hae entered is out of range (for example, a port number), an error message is displayed. Chapter 13. Installing and configuring the MSCS adapter 167

184 2. If not noted otherwise, you must restart the adapter for the changes to become effectie. Replicating the configuration files to other nodes If your MSCS adapter is highly aailable, you must replicate the configuration files to the other cluster nodes. Open the main panel of the adapter configuration dialog and click Replicate. The following window is displayed: Use this window to distribute (replicate) the MSCS adapter configuration itself or configuration updates to other nodes in the RSCT cluster: 1. Select the configuration files you want to replicate, or click Select all below the configuration file list to select all files in the list. 2. Click Select all below the list of replication target nodes. This ensures that the adapter configuration is identical on all nodes. 3. In the Target node login section, specify a local or domain user ID that is alid on all target nodes. For a local user ID, the specified password must be alid on all target nodes. Domain user IDs must be specified in the form <user_id>@<domain_name>. 4. Click Replicate to start the replication. Replication may take a while. While the files are being replicated, the Replicate button is indented and grayed-out. When the replication is complete, the replication status of each configuration file is displayed. 168 System Automation Application Manager: Installation and Configuration Guide

185 Windows Firewall on Windows Serer 2008 On Windows Serer 2008, the Windows Firewall with Adanced Security is enabled by default, so all incoming TCP network communication not explicitly allowed by rules is blocked. This inhibits the MSCS adapter. Firewall rules must be defined to allow the TCP network communication required by the MSCS adapter. To set up the Windows Firewall with Adanced Security, perform these steps on each node of the Microsoft Failoer Cluster: 1. Select "Start > Administratie Tools > Windows Firewall with Adanced Security". 2. In the "Windows Firewall with Adanced Security" window, open the item "Windows Firewall with Adanced Security on Local Computer" in the tree iew. 3. Select item Inbound Rules in the tree iew. Define all inbound rules required by System Automation Application Manager. 4. Select item Outbound Rules in the tree iew. Define all outbound rules required by System Automation Application Manager. To define an Inbound Rule in the Windows Firewall with Adanced Security, perform these steps: 1. Click New Rule... from Actions. 2. Select Custom to define a custom rule. Click Next. 3. Select All Programs. Click Next. 4. Select the desired Protocol type. 5. For protocol type TCP, set Local port to Specific Ports, specify the desired local port, and keep the setting All Ports for Remote port. Click Next. 6. Click Next. 7. Select Allow the connection. Click Next. 8. Select all network locations: Domain, Priate, and Public. Click Next. 9. Specify a name and a description for the rule. Click Finish. By default, the new rule is automatically enabled. To define an Outbound Rule in the Windows Firewall with Adanced Security, perform these steps: 1. Click New Rule... from Actions. 2. Select Custom to define a custom rule. Click Next. 3. Select All Programs. Click Next. 4. Select the desired Protocol type. 5. For protocol type TCP, set Remote port to Specific Ports, specify the desired remote port, and keep the setting All Ports for Local port. Click Next. 6. Click Next. 7. Select Allow the connection. Click Next. 8. Select all network locations: Domain, Priate, and Public. Click Next. 9. Specify a name and a reasonable description for the rule. Click Finish. By default, the new rule is automatically enabled. Chapter 13. Installing and configuring the MSCS adapter 169

186 The following rules must be defined and enabled as described aboe on all nodes of the Microsoft Failoer Cluster. The rules contain the default ports after installation. If you change any of the ports, you need to adapt the rules. Table 46. Microsoft Failoer Cluster default ports Name Direction Default port Protocol IBM Tioli SA AM MSCS Adapter (TCP-In) Inbound 2001 TCP IBM Tioli SA AM MSCS Adapter (TCP-Out) Outbiund 2002 TCP Proiding high aailability for the MSCS adapter The procedure for this depends on the serer operating system in use. For Windows Serer 2008 see MSCS high aailability on Windows Serer 2008 on page 175. MSCS high aailability on Windows Serer 2003 Perform the following steps: 1. Open the Microsoft Cluster Administrator. Launch the Cluster Application Wizard from the File menu. On the Welcome panel, click Next. The following panels are displayed: 2. You are recommended to select Create a new irtual serer to create or assign dedicated resources (for example the irtual IP address) to the MSCS adapter serice resources. Click Next. The following panel is displayed: 170 System Automation Application Manager: Installation and Configuration Guide

187 3. Define a new group or identify an existing group representing the MSCS adapter as irtual serer. In the following steps, this group is referred to as the "irtual serer group". You should choose the group containing the quorum resource. If you choose a different group, this group should only contain resources for making the MSCS adapter serice highly aailable. Click Next. The Resource Group Name panel is displayed: Chapter 13. Installing and configuring the MSCS adapter 171

188 4. On the Resource Group Name panel, specify a group name and a description. Click Next. The Virtual Serer Access Information panel is displayed: 5. On the Virtual Serer Access Information panel, specify a alid new network name under which the MSCS adapter will be reachable. You must ensure that the operations console or automation manager to which the MSCS adapter will connect is able to resole this network name. If you do not want to use a network name for the MSCS adapter, specify a dummy name here and remoe it later. Specify a alid IP address on which the MSCS adapter can be reached. You must ensure that the operations console or automation manager to which the MSCS adapter will connect is able to reach the irtual IP address. Do not specify the IP address shown in the screen capture, as it belongs to the priate IP address space. If the MSCS adapter is highly aailable, specify the network name or IP address you obtained as described in Planning and preparing for high aailability on page 156. Click Next to display the Adanced Properties panel: 172 System Automation Application Manager: Installation and Configuration Guide

189 6. Click Adanced Properties to iew or modify the properties of the selected MSCS group or resource. The default settings are appropriate for most cases, but should be checked for correctness and completeness. Click Next to continue. 7. On the Create Application Cluster Resource panel specify a cluster resource for your application. Click Next to continue. 8. On the Application Resource panel select Generic Serice from the drop-down list. An MSCS resource of type Generic Serice is used to make the serice highly aailable as the MSCS adapter runs as a Windows serice. Click Next to display the following panel: Chapter 13. Installing and configuring the MSCS adapter 173

190 9. Specify an adapter name and a description. 10. Click Adanced Properties and open the Dependencies page. 174 System Automation Application Manager: Installation and Configuration Guide

191 11. On the Dependencies page: If you want to define a network name for the MSCS adapter, add a dependency on the Network Name resource. If you do not want to define a network name for the MSCS adapter, add a dependency on the IP Address resource. 12. Display the Generic Serice Parameters panel and type the serice name "SA AM MSCS Adapter" in the Serice name field. Leae the Start parameters field empty and click Next. 13. The Registry Replication panel is displayed. No entries are required. Click Next. 14. On the completion panel erify that the configuration settings are correct and click Finish to sae the configuration. 15. If you do not want to use a network name for the MSCS adapter you can delete it now using the Cluster Administrator: MSCS high aailability on Windows Serer 2008 Perform the following steps: 1. Open the Microsoft Failoer Cluster Management Console. In the tree iew select the failoer cluster in which you want the configure high aailability of the MSCS adapter. Click Configure a Serice or Application... under Actions. The High Aailability Wizard opens. Depending on your system s settings, the Before You Begin panel may be displayed. If so click Next. 2. On the Select Serice or Application panel, select the Generic Serice resource type and click Next. 3. On the Select Serice panel, select the SA AM MSCS Adapter serice from the list of installed serices. The MSCS adapter must hae been installed successfully on all failoer cluster nodes before. Click Next. Chapter 13. Installing and configuring the MSCS adapter 175

192 4. On the Client Access Point panel, specify a alid new network name under which the MSCS adapter will be reachable. It must be ensured that the automation manager to which the MSCS adapter will connect is able to resole this network name. If you do not want to use a network name for the MSCS adapter, specify a dummy name here and remoe it later. Specify a alid IP address on which the MSCS adapter can be reached. You must ensure that the automation manager to which the MSCS adapter will connect is able to reach this irtual IP address. Use the network name or IP address you obtained as described in Planning and preparing for high aailability on page 156. Click Next. 5. On the Select Storage panel do not select any storage olumes, as the MSCS adapter does not require any. Click Next. 6. On the Replicate Registry Settings panel do not specify any registry keys, as the MSCS adapter does not require any. Click Next. 7. On the Confirmation panel, check that all settings are correct. If so click Next. If not click Preious to correct the settings. 8. On the Summary panel, click Finish. Verifying the installation and configuration Perform the following steps to erify that the adapter is installed and configured correctly: The adapter is highly aailable: 1. Start the MSCS adapter using MSCS and check if the domain joins. 2. Fail the adapter oer to all MSCS nodes and check if the domain joins. The adapter is not highly aailable: Uninstalling the MSCS adapter Start the MSCS adapter using the Serices plug-in from the Microsoft Management Console and check if the domain joins. Perform the following steps: 1. Make sure that the MSCS adapter serice is stopped before starting the uninstallation. Note that MSCS may try to restart or fail the MSCS adapter serice oer to another MSCS node if you stop the serice manually. If the MSCS adapter serice is highly aailable, you must take the MSCS adapter group offline. 2. Open the Windows Control Panel and use Add or Remoe Programs to uninstall the adapter. 176 System Automation Application Manager: Installation and Configuration Guide

193 Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter Installing the VCS adapter The following topics describe how to install and configure the VERITAS Cluster Serer adapter (VCS adapter) on Solaris/SPARC. Packaging The VCS adapter is shipped with System Automation Application Manager. The name of the binary file you use for installing the adapter is install.bin. This is where you find the installation package: CD: You install the adapter from the CD "Tioli System Automation Application Manager V Automation Adapters all platforms". The installation package is aailable in the installation source directory EEZ3100Adapters/EEZEEZ3100VCS/ Solaris. Electronic distribution: If you obtain System Automation Application Manager through electronic distribution, you use the following archie to install the VCS adapter: Delierable name: C1A23ML.bin Installation source directory: EEZ3100Adapters/EEZ3100VCS/Solaris Installation prerequisites Note that the VCS adapter can only be connected to System Automation Application Manager or the End-to-End Automation Management component of IBM Tioli System Automation for Multiplatforms V2.3. The system on which you are installing the adapter must meet the following installation prerequisites: Solaris 10 on RISC processors 64 MB of free RAM Minimum color depth: 8-bit (256 colors) Minimum screen resolution: 640 x 480 Using the installation wizard to install the VCS adapter You use an installation wizard to install the VCS adapter on Solaris/SPARC systems. Perform the following steps: 1. Log in as root on the system where you want to install the VCS adapter. 2. Launch the installation wizard using the file setup.bin. On the panel that appears, click OK to display the license agreement. The language is detected automatically or you can select it on the first panel. Copyright IBM Corp. 2006,

194 Automating the VCS adapter Configuring the VCS adapter 3. Select I accept both the IBM and the non-ibm terms to agree to the license agreement. Click Next. The Introduction panel is displayed. After installing the adapter it must be configured as described in the remaining sections of this chapter. If the VCS Solaris/SPARC cluster consists of more than one node, the VCS adapter must be automated for the following reasons: The host using the adapter must be able to reach the adapter always through the same serice IP without reconfiguration. If the node on which the adapter runs goes down or the VCS cluster serices on that node are stopped, the adapter must moe to another aailable node in the cluster to resume the connection with the host using the adapter. For more information about automating VCS adapters using the adapter configuration dialog, see Automation tab on page 183. The following figure shows in which enironments the VCS adapter can work and what needs to be configured for the adapter. 178 System Automation Application Manager: Installation and Configuration Guide

195 Figure 6. Configuration of the VCS adapter You must configure the adapter for end-to-end automation management using System Automation Application Manager. For more information on end-to-end automation management, refer to the IBM Tioli System Automation Application Manager Administrator s and User s Guide. You can also configure the VCS adapter in silent mode using an input properties file. See Inoking silent configuration on page 103 for more details. Inoking the VCS adapter configuration dialog The VCS adapter can be configured with the cfgcsadapter utility. Notes: 1. The cfgcsadapter utility is an X-Windows application and must be used from a workstation with X-Windows serer capabilities. This can be one of your cluster nodes if the X11 optional feature is installed on that node. 2. The 32-bit ersion of Jaa 1.4 or Jaa 5 SR5 must be installed. 3. SSL/SSH packages must be installed and the sshd subsystem must be running to be able to complete the Replication task of the adapter configuration 4. To use the VCS adapter configuration dialog, you must either be logged in on the system with the user ID root or hae write access to the directory /etc/opt/ibm/tsamp/eez/cs/cfg. Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 179

196 To open the configuration dialog, issue the command cfgcsadapter. The main panel of the dialog is displayed: The dialog lets you perform the following tasks: 1. Configure the VCS adapter. 2. Replicate the VCS adapter configuration files to other nodes. 3. Define the VCS adapter automation policy to create the resources required to automate the adapter. 4. Remoe the VCS adapter automation policy. Configuring the VCS adapter On the main panel of the configuration dialog, click Configure to display the configuration tabs that are described in the following sections. In the following description, the term Host using the adapter is used to refer to an end-to-end automation manager host. 180 System Automation Application Manager: Installation and Configuration Guide

197 Adapter tab Selecting the adapter tab lets you configure the adapter host. Fields and controls on the Adapter tab: Automation adapter host: Host name or IP address Host name or serice IP label of the node where the adapter runs. On initial inocation, the field contains the alue the command hostname would return. If you are automating the adapter, leae the alue unchanged. The alue will be updated automatically with the alue you specify in the field Adapter IP address on the Automation tab (see Automation tab on page 183). Request port number The port on which the adapter listens for requests from the host using the adapter. The default port is Automation domain: The domain name is the name by which the VCS cluster is known to the host using the adapter. The domain name must be unique within the scope of automation domains that connect to the end-to-end automation manager. You hae the following options to specify the domain name: It is recommended that you use the VCS cluster name as the domain name. This option is selected by default. You must keep this setting if you want to use Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 181

198 Tioli Enterprise Portal launch-in-context support, which allows you to launch Tioli Enterprise Portal work spaces from the System Automation operations console, because Tioli Enterprise Portal will not recognize any other domain name. If you cannot use the VCS cluster name as a domain name, for example, because it would not be unique, you can specify a domain name for the VCS cluster. Clicking Adanced lets you specify the adapter runtime behaior: Adapter stop delay The number of seconds by which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You may need to increase the alue on slow systems. Valid alues are 3 through 60. Remote contact actiity interal The time period, in seconds, after which the adapter will stop if it was not contacted by the host using the adapter, which periodically contacts the adapter to check if it is still running. The default alue is 360. If a alue other than 0 is specified, the interal must be a multiple of the check interal. When the alue is set to 0, the adapter continuously runs and neer stops. Initial contact retry interal The time period, in minutes, during which the adapter will attempt to contact the host using the adapter until it succeeds or the specified time has elapsed. The default alue is 0, which means that the adapter will attempt to contact the host using the adapter indefinitely. EIF reconnect attempt interal The time period, in seconds, that the adapter will wait before it attempts to reestablish the connection to the host using the adapter after the connection was interrupted. The default alue is 30. Host using adapter tab Use the Host using adapter tab to determine which host the adapter connects to and to specify the required information. The VCS adapter must be configured to connect to an end-to-end automation manager host. 182 System Automation Application Manager: Installation and Configuration Guide

199 Fields on the Host using adapter tab: Configure the System Automation Application Manager host: Host name or IP address The name or IP address of the host on which the end-to-end automation manager runs. The port number specified here must match the port number specified as eent port number when configuring the domain of the end-to-end automation manager. Eent port number The port on which the end-to-end automation manager listens for eents from the VCS adapter. The default port is Automation tab This tab lets you configure the adapter automation policy. This allows you to make the VCS adapter highly aailable. Note: All nodes where the adapter can run must be accessible using the same user ID and password. Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 183

200 Fields and controls on the Automation tab: Automate adapter in first-leel automation domain Select this check box ( see also Automating the VCS adapter on page 178). Query domain If the configuration dialog runs on a node in the VCS cluster, click Query domain to query the current automation policy from the VCS cluster. If the automation policy for the adapter is not yet defined but the cluster is up, at least all nodes that are online are shown in the Defined nodes table. This table proides the following information: Defined node The list of defined nodes. Automate on node Indicates if the adapter is automated on this node. The buttons at the bottom of the table let you perform the following tasks: Up Moes the selected node one position up in the node sequence. The position determines the order in which automation selects the node on which the adapter may run. Down Moes the selected node one position down in the node sequence. The position determines the order in which automation selects the node on which the adapter may run. Add 184 System Automation Application Manager: Installation and Configuration Guide

201 Displays the Add node for adapter automation panel which lets you define the name of the node to be added and determine if the node is to be added to automation of the adapter. Remoe Remoes the selected node from the list. This means that the adapter must not be started on that node. Change Displays the Change node for adapter automation panel which lets you change the name of the node and add or remoe the node from automation of the adapter. Automated resources prefix The prefix that is used to compose the names of the resource group, application, and application monitor in the automation policy. The resource names will appear in the resource table on the operations console. The prefix can be changed. It is restricted to ASCII characters; the following characters cannot be used: " (double quote), ' (single quote), ; (semicolon), $ (dollar), / (slash) Note that if the VCS adapter policy has been defined using the current prefix, you must remoe this policy before changing the prefix. For more information about defining the adapter automation policy, refer to Defining the VCS adapter automation policy on page 190. Adapter IP address Regardless on which node it runs, the end-to-end automation adapter uses this address to listen for requests and receie requests from the host using the adapter. You must obtain this IP address from your network administrator. The IP address must not be an actual host address or localhost. Netmask The netmask that is used in the adapter automation policy. Request a alue from your network administrator. Network interface The network interface that is used in the adapter automation policy. The adapter can be reached on this network interface through the specified IP address. Click Query to display the Select network interface dialog, which lets you select one of the network interfaces that are currently defined on the node where the configuration dialog runs. Note: When you click Sae after specifying an IP address in the field Adapter IP address, the following message may be displayed: Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 185

202 The message informs you that the IP addresses on the Adapter and Automation tabs differ and asks you to confirm that the IP address on the Adapter tab is to be updated with the alue you specified on the Automation tab. Click Yes to confirm the change. Security tab The security tab lets you configure the security for the interface between the VCS adapter and the System Automation Application Manager host. Fields and controls on the Security tab: Secure Socket Layer (SSL) for transport: Select the Enable SSL check box if you want to use the Secure Socket layer (SSL) protocol. If checked, the following entry fields must be completed. Truststore Name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore password Password of the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Keystore alias Note: If the truststore is in different file than keystore, the passwords for the files must be identical. Alias name of the certificate to be used by the serer. If not specified, the keystore file must contain only one entry which is the one to be used. 186 System Automation Application Manager: Installation and Configuration Guide

203 User authentication: It is recommended that you select the corresponding check box to enforce authentication of the user ID on behalf of which the host using the adapter requests operations from the VCS adapter. PAM Serice The name of an entry in file /etc/pam.conf that determines which checks are made to authenticate a user. The default alue is su, which checks users as if they were trying to execute the command su. Logger tab Use the Logger tab to specify the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Note that the Logger tab always displays the alues that are currently set in the configuration file. On the Logger tab, you can perform the following tasks: Change the settings permanently Perform these steps: 1. Make the required changes on the tab. 2. Click Sae. Results: The settings in the configuration file are updated. You must restart the adapter for the changes to take effect. Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 187

204 Change the settings temporarily Perform these steps: 1. Make the required changes on the tab. 2. Click Apply. Results: The new settings take effect immediately. They are not stored in the configuration file. If the adapter is not running, you receie an error message. Reert to the permanent settings If you changed the settings temporarily, perform the following steps to reert to the permanent settings defined in the configuration file, or when you are unsure which settings are currently actie for the adapter: 1. Inoke the configuration dialog and open the Logger tab. The Logger tab displays the alues that are currently set in the configuration file. 2. Click Apply to actiate the settings. Results: The settings take effect immediately. If the adapter is not running, you receie an error message. Controls and fields on the Logger tab: Maximum log/trace file size The maximum file size in kilobytes that each log file can reach before it rolls oer. Message logging leel: Error Warning Information Logs messages on the error leel. Logs messages on the error and warning leels. Logs messages on the error, warning and informational leels. Trace logging leel: Off Minimum Medium Maximum Collects no trace information. (Not recommended.) Collects trace information on the error leel. Only seere error situations are traced. This is the default setting. Collects trace information on the error and warning leels. Proides the message and trace logs and collects additional information on the error, warning, and informational leel. Required for testing and problem determination. First failure data capture (FFDC) settings: Recording leel: Off Collects no FFDC information. Minimum Proides the message and trace logs and collects additional information on the error leel. Medium Proides the message and trace logs and collects additional information on the error and warning leel. Maximum Proides the message and trace logs and collects additional information on the error, warning, and informational leel. 188 System Automation Application Manager: Installation and Configuration Guide

205 Disk space: Maximum disk space Specifies the maximum disk space in bytes used by FFDC traces which are written to the FFDC trace directory. The default space is byte (10MB). Space exceeded policy Select what to do if the maximum disk space is exceeded: Ignore Issue warnings, but do not enforce the FFDC disk space quota. Auto-delete Automatically delete FFDC files, oldest first, until the directory is below the limit. This is the default setting. Suspend Halt further FFDC actions until the directory is manually cleaned up. Message IDs: Filter mode Message ID list Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. Specifies the message IDs that are to trigger tracing, depending on the filter mode. Wildcards, for example, *E (for all error messages), are allowed. Saing the configuration Click Sae on the configuration dialog to sae your changes to the adapter configuration files. Upon completion, the Configuration update status panel appears, showing the list of configuration files that were updated. Notes: 1. If the Adapter IP address specified on the Automation tab does not match the host specified on the Adapter tab, you are prompted for input. On the panel that appears, click the button Adapter automation. 2. When entries are missing or a alue you hae entered is out of range (for example, a port number), an error message is displayed. 3. If you made changes on the Automation tab, a message appears reminding you to launch the Define automation policy task. 4. If not noted otherwise, you must restart the adapter for the changes to become effectie. Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 189

206 Replicating the VCS adapter configuration files to other nodes in the domain After configuring an VCS adapter on a node, you use the Replicate function to propagate the changes to the other nodes in the VCS cluster. To use the Replicate function, go to the main panel of the configuration dialog and click Replicate. The Replicate configuration files panel is displayed: Use this window to distribute (replicate) the VCS adapter configuration itself or configuration updates to the remaining nodes in the VCS cluster: 1. Select the configuration files you want to replicate or click Select all to select all configuration files in the list. 2. If the user ID and password you specified are alid on all nodes, you can click Select all below the list of replication target nodes. This ensures that the adapter configuration is identical on all nodes. 3. Enter the user ID and password for the target nodes you want to replicate the files to. 4. Start the replication by clicking Replicate. Replication may take a while. While the files are being replicated, the Replicate button is indented and grayed-out. When the replication is complete, the replication status of each configuration file is displayed. Defining the VCS adapter automation policy If definitions for the automation of the VCS adapter hae been made, clicking Define on the main panel of the configuration dialog will create the resources with 190 System Automation Application Manager: Installation and Configuration Guide

207 the resource name (Resource-/group prefix) as described on page 185. Note that if automated resources with the same name already exist, they are remoed before the new resources are created. If you used the default resource name prefix, the following resources will be defined or queried: Table 47. Resources in the VCS adapter automation policy Resource class Resource name Description IBM.VCS.ResourceGroup csadapter-rg The resource group that comprises all automated resources Application csadapter-rs Commands: csadapter start, csadapter stop IP csadapter-ip The irtual IP address on which the host using the adapter accesses the adapter. When you click Define, the button may stay indented for minutes until the resources hae been remoed, the cluster is synchronized, the new resources are created, and the cluster is synchronized again. The dialog will not repaint after it has been coered and uncoered. Eentually, the results of the commands are displayed in a pop-up window. Remoing the VCS adapter automation policy You typically use the Remoe function before you change the name prefix of the automated resources (see page 185). When the adapter is automated and you deselect the check box Automate adapter in system automation domain on the Automation tab, you receie a message reminding you to remoe the automated resources for the adapter. Clicking Remoe on the main panel of the configuration dialog will remoe the resources shown in Table 47. If the VCS adapter is still running, it is stopped before the automated resources are remoed. When you click Remoe, the button may stay indented for minutes until resources hae been remoed and the cluster has been synchronized. Eentually, the results of the commands are displayed in a pop-up window. Verifying the VCS adapter configuration You can use the hastatus command to erify that the VCS adapter is running: 1. Open a terminal session on the nodes on which the VCS adapter may run. 2. In each session, type /opt/vrts/bin/hastatus 3. A status screen similar to the following is displayed, showing the status of the member resources of the resource group csadapter-rg: Chapter 14. Installing and configuring the VERITAS Cluster Serer adapter 191

208 sasun01:~ # hastatus attempting to connect... connectedgroup resource system message csadapter-rg sasun01 OFFLINE csadapter-rg sasun02 ONLINE csadapter-rs sasun01 OFFLINE csadapter-rs sasun02 ONLINE csadapter-ip sasun01 OFFLINE csadapter-ip sasun02 ONLINE Controlling the VCS adapter You use the csadapter command to start, stop, and monitor the adapter. Table 48. VCS adapter control command options Command Description csadapter status Checks if the adapter is running. Aailable return codes: 0 Unknown. The adapter status cannot be determined. 1 Online. The adapter is running. csadapter start csadapter stop 2 Offline. The adapter is not running. Starts the adapter if it is not running: If the adapter is automated, the command requests VCS to start the adapter on the preferred node. If the adapter is not automated, it is started on the node where the command was issued. The exit code is 0 if the command was successful. Stops the adapter if it is running: If the adapter is automated, the command requests VCS to stop the adapter on the node where it is currently actie. If the adapter is not automated, it is stopped on the node where the command was issued. The exit code is 0 if the command was successful. 192 System Automation Application Manager: Installation and Configuration Guide

209 Part 4. Appendixes Copyright IBM Corp. 2006,

210 194 System Automation Application Manager: Installation and Configuration Guide

211 Appendix A. Default directories The following table lists the default directory paths for which ariables are used in this guide. The paths in your enironment may differ, for example, if you changed the default path during the installation of the application or component. Table 49. Default directories Variable used in this guide <DB2_install_location> Default path Windows: C:\Program Files\IBM\SQLLIB AIX: /usr/opt/db2_09_01 <EEZ_CONF_ROOT> Linux: /opt/ibm/db2/v9.1 Windows: C:\Program Files\IBM\tsamp\eez\cfg AIX, Linux: /etc/opt/ibm/tsamp/eez/cfg <EEZ_INSTALL_ROOT> z/os: /etc/eez/cfg Windows: C:\Program Files\IBM\tsamp\eez AIX, Linux: /opt/ibm/tsamp/eez z/os: /local/eez <hacmp_adapter_install_root> <hacmp_adapter_conf_root> <mscs_adapter_install_root> <mscs_adapter_conf_root> <Tioli_Common_Directory> The configuration properties files are located in the directory <EEZ_CONF_ROOT>. AIX: /opt/ibm/tsamp/eez/hac AIX: /etc/opt/ibm/tsamp/eez/hac/cfg Windows: C:\Program Files\IBM\tsamp\eez\mscs Windows: C:\Program Files\IBM\tsamp\eez\mscs\cfg Windows: C:\Program Files\IBM\tioli\common AIX, Linux, Solaris, z/os: /ar/ibm/tioli/common <was_root> The path to the Tioli Common Directory is specified in the properties file log.properties. The file log.properties is located in the following directory: Windows: C:\Program Files\IBM\tioli\common\cfg AIX, Linux, Solaris, z/os: /etc/ibm/tioli/common/cfg Windows: C:\Program Files\IBM\WebSphere\AppSerer AIX: /usr/ibm/websphere/appserer <cs_adapter_install_root> <cs_adapter_conf_root> Linux: /opt/ibm/websphere/appserer Solaris: /opt/ibm/tsamp/eez/cs Solaris: etc/opt/ibm/tsamp/eez/cs/cfg Copyright IBM Corp. 2006,

212 196 System Automation Application Manager: Installation and Configuration Guide

213 Appendix B. Presering user data during the upgrade from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1 The upgrade from IBM Tioli System Automation for Multiplatforms to System Automation Application Manager 3.1 requires migrating WebSphere Application Serer to WebSphere Application Serer 6.1, and since the installer technology has changed from InstallShield to InstallAnywhere, the upgrade effectiely means that you need to uninstall IBM Tioli System Automation for Multiplatforms 2.2 and install System Automation Application Manager 3.1 as a new product. The uninstallation step includes the remoal of the automation database (default name: EAUTODB). Among other data, this database contains information about the automation domain topology and the operator preferences. To presere the data, you need to export the data before uninstalling IBM Tioli System Automation for Multiplatforms 2.x to be able to import it during the installation of System Automation Application Manager. Similarly, you need to export the data before upgrading from IBM Tioli System Automation for Multiplatforms 2.x to System Automation Application Manager 3.1. System Automation Application Manager 3.1 proides scripts that assist you in exporting and importing the data. These scripts are designed for local databases. If you hae a remote DB2 setup you must run these scripts directly on the system where the automation database resides. To export the data, perform the following steps before uninstalling IBM Tioli System Automation for Multiplatforms 2.2: 1. Stop the WebSphere Application Serer to ensure that the automation manager does not lock any data in the database. 2. Change to the DDL/Script directory on the product CD and run the following script to export the data: Windows: db2_export_automgr_from_2200.bat <db_name> <instance_owner> <instance_pwd> <export_to_dir> AIX, Linux:./db2_export_automgr_from_2200.sh <db_name> <instance_owner> <instance_pwd> <export_to_dir> These are the required parameters: <db_name> - Name of the IBM Tioli System Automation for Multiplatforms database. Typically, this is EAUTODB. <instance_owner> - Database instance owner userid. <instance_pwd> <export_to_dir> - Database instance owner password. - Absolute path name of the directory where the exported tables should be stored. Ensure that the <instance_owner> user ID has write access to this directory. All of these parameters are required. 3. Then, uninstall IBM Tioli System Automation for Multiplatforms 2.2 and start the installation of System Automation Application Manager 3.1. If the automation database is local, on the Import Data installation wizard panel select Import data to the automation database and specify the <export_to_dir> directory where the exported tables are stored. If the automation database is remote, complete the System Automation Application Manager 3.1 installation Copyright IBM Corp. 2006,

214 and then run the script db2_import_automgr_to_2300.bat or db2_import_automgr_to_2300.sh directly on the remote system to import the preiously exported data. The use of db2_import_automgr_to_2300 is analogous to the usage of db2_export_automgr_from_2200. Note that this script is unchanged from release 2.3 of IBM Tioli System Automation for Multiplatforms. Notes: 1. Do not use the backup and restore functionality proided by DB2 to back up and restore the automation database, as this preseres the complete database layout. 2. The DB2 export utility that is used by the automation data export script creates seeral warning messages with message ID SQL3100W. This warning message may be ignored. For further information about this message, refer to the DB2 documentation. 3. Een if the data import step during installation of System Automation Application Manager 3.1 fails, the installation completes. After System Automation Application Manager 3.1 has been installed, open the Operations Console to check if the data were imported successfully. If the data were not imported successfully, you can check the installation log file, correct the error, and start the import again by using the import scripts proided by System Automation Application Manager in the DDL/Script directory on the product CD. The import scripts hae a syntax analogous to the export scripts. 198 System Automation Application Manager: Installation and Configuration Guide

215 Appendix C. Troubleshooting the installation of System Automation Application Manager Use this section for troubleshooting problems you experience when installing or configuring System Automation Application Manager. Installation wizard cannot find WebSphere Application Serer on the system WebSphere Application Serer must be installed on the system before System Automation Application Manager can be installed. If the installation wizard of System Automation Application Manager does not detect WebSphere Application Serer on the system, although you did install it, the WebSphere Application Serer installation may be damaged. You can specify the location manually. If WebSphere Application Serer is found it will be used, if possible. Determining the correct DB2 port number When you install System Automation Application Manager on AIX or Linux systems, the installation wizard can retriee the alid DB2 instance port number automatically. If you opt not to use this function, or on Windows systems, the port number will be displayed in the entry field on the corresponding installation wizard panel, which is the default port number that is assigned to DB2 during the installation of DB2. Howeer, if the port is not free, a different port number is assigned automatically, which is why you need to check if the default port number is correct. This is how you can determine the correct DB2 port number: All operating systems: The port number is displayed in the summary panel that appears when the DB2 installation is complete. You can also determine the port number in this way: 1. Log on as the instance user (for example, db2inst1) 2. Issue the command db2 get dbm cfg 3. Go to the following line: TCP/IP Serice name (SVCENAME) = db2c_db2 the string after (SCVENAME) = is the DB2 instance port. If the string is numeric, for example, 50000, it is the instance port number. If the string is not numeric, for example, db2c_db2, look for a string similar to db2c_db /tcp in this file: AIX/Linux: /etc/serices Windows: C:\WINDOWS\SYSTEM32\DRIVERS\ETC\SERVICES z/os: /etc/serices Copyright IBM Corp. 2006,

216 DB2 access test hangs If the attempt to access the database does not return (an indeterminate dialog is shown for a ery long time), the test may be hung. The DB2 password may be expired. To resole the problem, perform these steps: 1. End the installer. Because Cancel is not enabled at this point, you must end the installer using the Task manager (on Windows systems) or the kill command (on UNIX systems). If the installer is killed, files in the system temporary directory remain on the system. If desired, you can manually delete the files in the following way: AIX/Linux: Delete the directories dirs /tmp/<xxxxxx>.tmp and /tmp/install.dir.<xxxxxx>> (where <xxxxxx> is an arbitrary number) Windows: Delete the directory C:\Documents and Settings\Administrator\ Local Settings\temp\Ixxxxxxx (where <xxxxxx> is an arbitrary number) 2. Check if the DB2 password is expired. 3. Renew the DB2 password. 4. Restart the installation. DB2 message SQL1035N The database is currently in use. SQLSTATE=57019 This message may be receied after an error during installation. To correct it you restart DB2 and drop database EAUTODB manually before resuming the installation. It may be necessary to use the force option to close DB2. Installer cannot detect non-default SOAP port If the default SOAP port settings are changed in the WebSphere Administrator Console, the installer cannot detect these. This causes an error panel to be displayed with the message that the cell could not be retrieed. Changing the SOAP port ia the Websphere Administrator Console does not update the alue used by the wsadmin.sh command. This will cause all commands which use wsadmin.sh and a SOAP connection to fail. A quick workaround for this problem is to manually edit the file /opt/ibm/websphere/appserer/profiles/appsr01/properties/ wsadmin.properties and change the alue com.ibm.ws.scripting.port= by hand. The recommended solution is to change the default ports of WebSphere using an Ant script. Please refer to the official WebSphere manual or InfoCenter for further information. In the InfoCenter search for the item Updating ports in an existing profile. Using the Ant script aoids the problem as it correctly updates the SOAP Port for wsadmin.sh. Exceptions appear in file eezinstall.log Any NoClassDefFoundError exceptions that appear in the eezinstall.log file after the file EEZEAR was deployed can be ignored. Note: In the last step of the install process the intermediate log is copied to the subfolder install in the user install directory. This copy omits the messages from the installer finish process ( 3 or 4 lines). If these lines are required the 200 System Automation Application Manager: Installation and Configuration Guide

217 Cleaning up from a failed installation original install log should be read. This log file can be found in the tmp directory with a name of the form: install.dir.xxxxxxxx. Installation can be canceled at any time. To recoer from this situation, just run the installer again. Installation was canceled or failed before the installation was started: no cleanup is necessary Installation was canceled or failed during the installation phase: Run the uninstaller to clean up files that were installed on disk. Installation was canceled during the configuration phase: Installation can be resumed. If the system has to be cleaned up again, rerun the installer, and then run the uninstaller to undo all configuration steps and to remoe all installed files from disk. Installation failed during the configuration phase: Correctie actions may be needed before installation can be resumed. You can also perform an uninstallation. If uninstall rather than resume is desired, the script uninstall.sh can be used to reert the configuration changes that hae already been made. The installation log must be used to determine which changes were made and must be reerted. Afterwards, uninstall can be called to remoe the files from the disk. Uninstall can be run with option -Dforce=true to be able to proceed een if errors are reported in the pre-uninstall phase. To just recoer the files if the product was uninstalled but the unconfiguration was not successful and the files are needed to manually perform the remaining unconfiguration steps: Run the installer with the option -Dfilesonly=true in this case, only the files are installed; no configuration is performed Be sure to undo the configuration changes that were made during the installation before uninstalling. Otherwise, the configuration changes will be retained and the scripts to remoe them are already uninstalled. Procedures for troubleshooting an installation If the installation fails, the installation wizard displays an error message. When an error occurs, immediately archie the installation log files (see Using the log file collector utility on page 202). This ensures that the original log files are retained, which is important should you need to contact IBM Support, and you can use the archie for your own troubleshooting actiities. An error occurred in the pre-installation phase If an error occurs in the pre-installation phase, that is, before the Install button was clicked, click the button Sae installation log files to collect all installation log files. The zip file will be created at the location specified. An error occurred in the installation phase Typically, errors only occur in the installation phase if insufficient disk space is aailable. An error occurred in the configuration phase: Click Finish to finish the installation, then change to <EEZ_INSTALL_ROOT>/ Appendix C. Troubleshooting the installation of System Automation Application Manager 201

218 Using the log file collector utility install and run the log file collector utility. The log zip will be created in the same directory. For details see Using the log file collector utility. When an error occurs, use the log file collector utility to collect the log files that were written during the installation. The utility generates an archie that you can use for your own troubleshooting actiities and send to IBM Support if you cannot resole the error. Perform these steps to run the log file collector utility: 1. Change the directory to <EEZ_INSTALL_ROOT>/install. 2. Issue the following command: Windows: collectinstallerlogs.bat AIX/Linux: collectinstallerlogs.sh The command can be inoked with the option -D to copy all logs (in case Jaa is not aailable). The directory tree created can then be packed manually. The name of the file that is created by the utility is eezinstallerlogs_<timestamp>.zip. On AIX and Linux you can inoke the command with the option tar to use tar rather than jar for packing. The resulting archie has the following directory structure: - EEZ_logs - cfg: configuration files (for the automation engine, etc.) - logs: eezinstall.log, etc. - sh / bat: scripts used by installer (Linux/AIX: sh; Windows: bat) - WAS_logs - logs: general WAS serer logs - <serer name>: logs for the selected WebSphere Application Serer Gathering information for IBM Support If you cannot resole an installation problem, send the installation log file archie to IBM support (see Using the log file collector utility ). 202 System Automation Application Manager: Installation and Configuration Guide

219 Appendix D. Troubleshooting the installation of the HACMP adapter Use this section for troubleshooting problems you experience when installing or configuring the HACMP adapter. HACMP adapter does not start HACMP adapter terminates Possible causes: HACMP leel is lower than To check, use: lslpp l cluster.es.serer.utils Cluster serices hae not been started Start the serices using smitty: hacmp > C-SPOC > Manage... Cluster serices terminated while the HACMP adapter was running If the adapter is automated, it should restart automatically on next priority node where cluster serices run. Adapter attempts to start but terminates again This may indicate that the adapter has not been configured correctly. Adapter does not connect to the host Make sure the firewall allows connections in both directions. Check with netstat: whether the adapter listens on the request port (default port is 2001): netstat -an -f inet grep 2001 Output should be similar to: tcp :2001 :::* LISTEN whether the end-to-end automation manager listens on the eent port (default port is 2002): AIX: netstat -an -f inet grep 2002 Linux: netstat -ant grep 2002 and examine the output directly, since there is no grep command. Windows: netstat -an and examine the output directly, since there is no grep command. z/os: netstat -an Output should be similar to: Copyright IBM Corp. 2006,

220 HACMP adapter log files tcp :2002 :::* LISTEN Howeer, with netstat you cannot check if tcp session creation is allowed or rejected by a firewall. To check if a tcp session can be created, use these approaches: Try to open a session with telnet to port 2001 from the end-to-end automation management host using this command: telnet <adapter-address> 2001 Try to open a session with telnet to port 2002 from the first-leel automation domain to System Automation Application Manager using this command: telnet <e2e-host> 2002 If the connections cannot be set up using telnet a firewall may be blocking the sessions, or other network problems, such as routing problems, may exist. Increasing the trace logging leel If your trace is not detailed enough to analyze a problem and the problem can be recreated, it may be useful to increase the trace logging leel: 1. Inoke the adapter configuration dialog using cfghacadapter. 2. On the main panel of the configuration dialog, click Configure. 3. Select the Logger tab. 4. Set the Trace logging leel to Maximum. 5. Click Apply. The new setting takes effect immediately. For more information about the Logger tab, see Logger tab on page 148. Log file locations The HACMP adapter log files are located in the Tioli Common Directory: Default location: /ar/ibm/tioli/common HACMP adapter-specific subdirectory structure in the Tioli Common Directory: eez/ffdc Contains the First Failure Data Capture files (if the FFDC recording leel is not set to Off in the adapter configuration dialog) eez/logs Contains the HACMP adapter trace file: - traceflatadapter.log 204 System Automation Application Manager: Installation and Configuration Guide

221 Appendix E. Troubleshooting the installation of the MSCS adapter MSCS adapter log files Use this section for troubleshooting problems you experience when installing or configuring the MSCS adapter. This is where the adapter log files are located: Tioli Common Directory Default location: C:\Program Files\IBM\tioli\common MSCS adapter-specific subdirectory structure in Tioli Common Directory: eez\ffdc Contains the First Failure Data Capture files (if the FFDC recording leel is not set to Off in the adapter configuration dialog) eez\logs Contains the MSCS adapter log files: - msgmscsadapter.log - tracemscsadapter.log (if trace logging leel is not set to Off) - eentmscsadapter.log (if trace logging leel is not set to Off) The default adapter installation directory is C:\Program Files\IBM\tsamp\eez\ mscs. Subdirectories and files used for troubleshooting: The file data\eez.release.information.txt is created in the adapter installation directory when the MSCS adapter is started. It contains information about serice applied to the MSCS adapter and about the configuration settings used. The installation log files are located in the subdirectory /install/logs. MSCS adapter installation fails If the installation wizard indicates a problem, check the installer output and the following files for error messages: The log files in the subdirectory /install/logs. IBM Tioli System Automation Application Manager MSCS Adapter_install_log.log. mscsinstall_<date_time>.log MSCS Adapter configuration dialog problems occur A problem occurs using the adapter configuration dialog Problem determination: The file cfgmscsadapter.bat contains a command for launching the configuration dialog The file contains a duplicate of this command which enables diagnostic output (option -DEBUG) The Apply button on the Logger tab cannot be clicked Possible cause: The MSCS adapter is not running. Copyright IBM Corp. 2006,

222 Configuration files cannot be replicated Possible causes: The MSCS cluster is not aailable. The cluster contains only a single node. Replication fails with the message "Login on target node failed" Possible cause: The domain user ID was not specified in the correct format, which is <user_id>@<domain_name>. MSCS adapter start problems MSCS adapter terminates MSCS adapter does not start Problem determination: The application eent log should contain the message The serice SA AM MSCS Adapter has been started. In the configuration file cfg\mscs.serice.properties, uncomment the property serice-log-file, restart the serice, and inestigate the resulting file. Ensure to comment the property again before returning to normal operation. Make sure that the correct user credentials are used for the SA AM MSCS Adapter Windows serice. Re-enter the password for the serice on the Log On tab of the serice properties iew, and restart the serice. The SA AM Adapter Serice reports the status 'Started' for some seconds and then stops Startup should be completed within 60 seconds. Refresh the iew to see the actual status. Problem determination: Inestigate the MSCS adapter log file msgmscsadapter.log. If no error messages can be found, increase the trace logging leel to "Maximum" and proide all logs to IBM support. The file msgmscsadapter.log contains the message EEZA0061E, indicating that the adapter failed to bind to a socket Possible reason if the MSCS adapter serice is made highly aailable using MSCS: The network name or irtual IP address used for the "Automation adapter host" is not aailable during adapter startup Possible solution: Check the spelling of the network name or irtual IP address in the adapter configuration dialog. Check that there are appropriate "Network Name" and "IP Address" resources defined in MSCS, and that they are working properly. Check that the MSCS adapter serice resource has a dependency on the "Network Name" and "IP Address" resources in MSCS. The MSCS adapter serice stops and the log files contain no related error messages. In particular, message EEZA0104I does not appear in the MSCS adapter log file msgmscsadapter.log. The message indicates that the MSCS adapter was successfully stopped. 206 System Automation Application Manager: Installation and Configuration Guide

223 Problem determination: 1. Search for jaacore.*.txt files in the subdirectory lib. 2. Use Windows tool drwtsn32 to configure dump capturing. Use the following settings: Domain does not join 3. Try to recreate the MSCS adapter termination. 4. Proide the data to IBM support. The MSCS domain does not join within two minutes and the MSCS adapter serice is no longer running Problem determination: Inestigate the MSCS adapter log file msgmscsadapter.log. If no problems can be found, increase the trace logging leel to "Maximum" and proide all logs to IBM support. The MSCS domain does not join within two minutes but the MSCS adapter serice is running Problem determination and possible causes: An inalid host name or IP address is specified for the System Automation Application Manager serer. Appendix E. Troubleshooting the installation of the MSCS adapter 207

Installation and Configuration Guide

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

More information

System Automation Application Manager Version 4.1. Installation and Configuration Guide IBM SC

System Automation Application Manager Version 4.1. Installation and Configuration Guide IBM SC System Automation Application Manager Version 4.1 Installation and Configuration Guide IBM SC34-2702-01 System Automation Application Manager Version 4.1 Installation and Configuration Guide IBM SC34-2702-01

More information

Tivoli System Automation for Multiplatforms

Tivoli System Automation for Multiplatforms Tivoli System Automation for Multiplatforms Version 2.3 Installation and Configuration Guide SC33-8273-02 Tivoli System Automation for Multiplatforms Version 2.3 Installation and Configuration Guide SC33-8273-02

More information

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

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

More information

Tivoli System Automation Application Manager

Tivoli System Automation Application Manager Tivoli System Automation Application Manager Version 3.1 Release Notes (December 2009) SC33-8422-06 Tivoli System Automation Application Manager Version 3.1 Release Notes (December 2009) SC33-8422-06

More information

IBM Operational Decision Manager Version 8 Release 5. Installation Guide

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

More information

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

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

More information

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

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

More information

High Availability Policies Guide

High Availability Policies Guide Tioli System Automation for Multiplatforms High Aailability Policies Guide Version 4 Release 1 SC34-2660-03 Tioli System Automation for Multiplatforms High Aailability Policies Guide Version 4 Release

More information

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

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

More information

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

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

More information

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

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

More information

Managing Server Installation and Customization Guide

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

More information

License Administrator s Guide

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

More information

Installation and Setup Guide

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

More information

Tivoli System Automation Application Manager

Tivoli System Automation Application Manager Tivoli System Automation Application Manager Version 3.1 Release Notes (July 2009) SC33-8422-05 Tivoli System Automation Application Manager Version 3.1 Release Notes (July 2009) SC33-8422-05 Note! Before

More information

Solutions for BSM Version 1.1. Solutions for BSM Guide

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

More information

IBM Security Identity Manager Version 6.0. Installation Guide GC

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

More information

Tivoli IBM Tivoli Advanced Catalog Management for z/os

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

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

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

More information

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

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

More information

Tivoli System Automation for Multiplatforms

Tivoli System Automation for Multiplatforms Tioli System Automation for Multiplatforms Version 2.1 Release Notes (December 2006) SC33-8214-07 Tioli System Automation for Multiplatforms Version 2.1 Release Notes (December 2006) SC33-8214-07 Note!

More information

IBM Tivoli Storage Manager for Windows Version Installation Guide

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

More information

IBM Tivoli Storage Manager for Windows Version 7.1. Installation Guide

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

More information

Tivoli Tivoli Provisioning Manager

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

More information

IBM Agent Builder Version User's Guide IBM SC

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

More information

Tivoli Identity Manager

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

More information

Tivoli Tivoli Intelligent ThinkDynamic Orchestrator

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

More information

Tivoli System Automation for Multiplatforms

Tivoli System Automation for Multiplatforms Tioli System Automation for Multiplatforms Version 2.1 Release Notes (July 2006) SC33-8214-05 Tioli System Automation for Multiplatforms Version 2.1 Release Notes (July 2006) SC33-8214-05 Note! Before

More information

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

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

More information

Tivoli Tivoli Provisioning Manager

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

More information

Deployment Overview Guide

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

More information

Tivoli Monitoring: Windows OS Agent

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

More information

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

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

More information

WebSphere MQ Configuration Agent User's Guide

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

More information

Installation and Setup Guide

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

More information

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

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

More information

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

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

More information

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide

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

More information

Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Server

Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Server Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Serer ii Installing and Configuring IBM Case Manager with FileNet P8 Platform on a Single Serer Contents Installing with

More information

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

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

More information

Installing and Configuring Tivoli Enterprise Data Warehouse

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

More information

Authorization C API Developer Reference

Authorization C API Developer Reference IBM Security Access Manager for Web Version 7.0 Authorization C API Deeloper Reference SC23-6515-02 IBM Security Access Manager for Web Version 7.0 Authorization C API Deeloper Reference SC23-6515-02

More information

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

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

More information

IBM. Installing and configuring. Version 6.4

IBM. Installing and configuring. Version 6.4 IBM Installing and configuring Version 6.4 ii Installing and configuring Contents Installing and configuring....... 1 Planning for installation.......... 1 Premium feature actiation......... 1 Installation

More information

IBM i Version 7.2. Security Service Tools IBM

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

More information

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

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

More information

IBM Tivoli Storage Manager for AIX Version Tivoli Monitoring for Tivoli Storage Manager

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

More information

High Availability Guide for Distributed Systems

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

More information

Troubleshooting Guide

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

More information

Planning and Installation

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

More information

WebSphere Message Broker Monitoring Agent User's Guide

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

More information

Web Security Developer Reference

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

More information

Tivoli IBM Tivoli Advanced Catalog Management for z/os

Tivoli IBM Tivoli Advanced Catalog Management for z/os Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring Agent Planning and Configuration Guide SC23-9820-00 Tioli IBM Tioli Adanced Catalog Management for z/os Version 2.2.0 Monitoring

More information

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

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

More information

Internet Information Server User s Guide

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

More information

Tivoli Storage Manager FastBack Installation and User's Guide

Tivoli Storage Manager FastBack Installation and User's Guide Tioli Storage Manager FastBack Version 6.1.1.0 Tioli Storage Manager FastBack Installation and User's Guide SC23-8562-05 Tioli Storage Manager FastBack Version 6.1.1.0 Tioli Storage Manager FastBack Installation

More information

Installation and Configuration Guide

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

More information

Tivoli Storage Manager for Enterprise Resource Planning

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

More information

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

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

More information

Tivoli IBM Tivoli Advanced Audit for DFSMShsm

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

More information

IBM Security Identity Manager Version Installation Topics IBM

IBM Security Identity Manager Version Installation Topics IBM IBM Security Identity Manager Version 6.0.0.13 Installation Topics IBM IBM Security Identity Manager Version 6.0.0.13 Installation Topics IBM ii IBM Security Identity Manager Version 6.0.0.13: Installation

More information

System i and System p. Capacity on Demand

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

More information

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

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

More information

IBM. Installing. IBM Emptoris Suite. Version

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

More information

Performance Tuning Guide

Performance Tuning Guide IBM Security Access Manager for Web Version 7.0 Performance Tuning Guide SC23-6518-02 IBM Security Access Manager for Web Version 7.0 Performance Tuning Guide SC23-6518-02 Note Before using this information

More information

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

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

More information

Data Protection for Microsoft SQL Server Installation and User's Guide

Data Protection for Microsoft SQL Server Installation and User's Guide IBM Tioli Storage Manager for Databases Version 6.4 Data Protection for Microsoft SQL Serer Installation and User's Guide GC27-4010-01 IBM Tioli Storage Manager for Databases Version 6.4 Data Protection

More information

DocumentationcorrectionsforIBMTivoli Storage Productivity Center V4.2

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

More information

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

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

More information

Installation and Configuration Guide

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

More information

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

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

More information

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

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

More information

Problem Determination Guide

Problem Determination Guide IBM Tioli Storage Productiity Center Problem Determination Guide Version 4.1 GC27-2342-00 IBM Tioli Storage Productiity Center Problem Determination Guide Version 4.1 GC27-2342-00 Note: Before using this

More information

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

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

More information

High Availability Guide for Distributed Systems

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

More information

IBM Tivoli Asset Discovery for Distributed Version Installation Guide GI

IBM Tivoli Asset Discovery for Distributed Version Installation Guide GI IBM Tioli Asset Discoery for Distributed Version 7.2.1 Installation Guide GI11-8749-01 IBM Tioli Asset Discoery for Distributed Version 7.2.1 Installation Guide GI11-8749-01 Installation Guide This edition

More information

Connectivity Guide for Oracle Databases

Connectivity Guide for Oracle Databases IBM InfoSphere DataStage and QualityStage Version 9 Release 1 Connectiity Guide for Oracle Databases SC19-3842-01 IBM InfoSphere DataStage and QualityStage Version 9 Release 1 Connectiity Guide for Oracle

More information

IMSConnectorforJava User s Guide and Reference

IMSConnectorforJava User s Guide and Reference IMS Connect IMSConnectorforJaa User s Guide and Reference Version1Release2Modification2 IMS Connect IMSConnectorforJaa User s Guide and Reference Version1Release2Modification2 Note! Before using this

More information

iplanetwebserveruser sguide

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

More information

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

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

More information

Data Protection for IBM Domino for UNIX and Linux

Data Protection for IBM Domino for UNIX and Linux IBM Tioli Storage Manager for Mail Version 7.1 Data Protection for IBM Domino for UNIX and Linux Installation and User's Guide IBM Tioli Storage Manager for Mail Version 7.1 Data Protection for IBM Domino

More information

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

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

More information

Guide for the Dynamic RDBMS Stage

Guide for the Dynamic RDBMS Stage IBM InfoSphere Information Serer Version 11 Release 3 Guide for the Dynamic RDBMS Stage SC19-4348-00 IBM InfoSphere Information Serer Version 11 Release 3 Guide for the Dynamic RDBMS Stage SC19-4348-00

More information

Tivoli Business Systems Manager

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

More information

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

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

More information

Web Services Security Management Guide

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

More information

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

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

More information

IBM Workplace Collaboration Services Installation and Upgrade Guide

IBM Workplace Collaboration Services Installation and Upgrade Guide IBM Workplace Collaboration Serices Installation and Upgrade Guide Version 2.5 G210-1961-00 IBM Workplace Collaboration Serices Installation and Upgrade Guide Version 2.5 G210-1961-00 Note Before using

More information

WebSEAL Installation Guide

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

More information

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

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

More information

Netcool Configuration Manager Version Installation and Configuration Guide R2E6 IBM

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

More information

Tivoli Application Dependency Discovery Manager Version 7.3. Installation Guide IBM

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

More information

Tivoli Storage Manager for Mail

Tivoli Storage Manager for Mail Tioli Storage Manager for Mail Version 6.1 Data Protection for Microsoft Exchange Serer Installation and User s Guide SC23-9796-00 Tioli Storage Manager for Mail Version 6.1 Data Protection for Microsoft

More information

IBM Tivoli Directory Server. System Requirements SC

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

More information

Monitor Developer s Guide

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

More information

Version 10 Release 0 February IBM Marketing Platform Installation Guide IBM

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

More information

IBM Cognos Dynamic Query Analyzer Version Installation and Configuration Guide IBM

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

More information

Product Overview Guide

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

More information

IBM Security Role and Policy Modeler Version 1 Release 1. Planning Guide SC

IBM Security Role and Policy Modeler Version 1 Release 1. Planning Guide SC IBM Security Role and Policy Modeler Version 1 Release 1 Planning Guide SC22-5407-03 IBM Security Role and Policy Modeler Version 1 Release 1 Planning Guide SC22-5407-03 October 2012 This edition applies

More information