Installation and Configuration Guide

Size: px
Start display at page:

Download "Installation and Configuration Guide"

Transcription

1 System Automation Application Manager Version 4.1 Installation and Configuration Guide SC

2

3 System Automation Application Manager Version 4.1 Installation and Configuration Guide SC

4 Edition Notices Before using this information and the product it supports, read the information in Notices on page 273 This edition of IBM Tioli System Automation Application Manager, Installation and Configuration Guide applies to Version 4 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. 220 D Boeblingen Federal Republic of 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 IBM Corporation 2006, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii Tables ix About this book xi Who should read this guide xi Where to find more information xi Conentions used in this guide xii ISO xii Related information xii How to obtain publications xiii How to reach us by xiii What's new in this release x Chapter 1. Planning Planning for System Automation Application Manager Packaging Prerequisites Preparing for installation Planning for the Agentless Adapter Packaging Prerequisites Planning for high aailability Planning for Distributed Disaster Recoery Packaging Prerequisites Preparing for installation Planning for the HACMP adapter Packaging Prerequisites Automating the HACMP adapter Behaior of the HACMP adapter Planning for the FOC adapter Roadmap Packaging Prerequisites Planning and preparing for an highly aailable FOC adapter Behaior of the FOC adapter Planning for the VCS adapter Packaging Prerequisites Automating the VCS adapter Behaior of the VCS adapter for Solaris/SPARC 33 Planning for an end-to-end automation policy The scope of end-to-end automation policies.. 34 Identifying cluster-spanning dependencies Default directories Disaster recoery policy definition worksheets Chapter 2. Installing Installing the middleware software Contents of the middleware software DVDs.. 43 Installing a DB2 serer Installing Jazz for Serice Management Installing System Automation Application Manager 50 Using the installation wizard Installing in silent mode Upgrading to release Verifying the installation Post-installation tasks Upgrading from a Try and Buy ersion to a full product ersion Uninstalling Installing fix packs Obtaining fix packs Archie naming conentions Naming conentions of the update installer location Usage instructions for the platform-specific archies Installing a product fix pack Installing fix packs in a setup for high aailability Uninstalling fix packs Installing for high aailability Installing for Distributed Disaster Recoery Installing the prerequisite software on both sites 72 Installing and configuring System Automation for Multiplatforms Installing System Automation Application Manager on the first site Configuring System Automation Application Manager on the first site Setting up DB2 HADR Installing System Automation Application Manager on the second site Configuring System Automation Application Manager on the second site Creating tools for the replication of policy and credential files Configuring all end-to-end automation adapters with two System Automation Application Manager hosts Configuring high aailability and contact retry interal of all end-to-end automation adapters.. 77 Installing the remote Agentless Adapter Using the installation wizard to install the remote Agentless Adapter Installing the remote Agentless Adapter in silent mode Uninstalling the remote Agentless Adapter Installing and uninstalling serice for the remote Agentless Adapter Installing the HACMP adapter Using SMIT to install the adapter Verifying the HACMP adapter installation Uninstalling the HACMP adapter Copyright IBM Corp. 2006, 2014 iii

6 Installing the FOC adapter Installing the Failoer Cluster Command Interface optional feature Using the installation wizard to install the FOC adapter Installing the FOC adapter in silent mode Upgrading the FOC adapter Verifying the FOC adapter installation Uninstalling the FOC adapter Installing the VCS adapter Using the installation wizard Installing the VCS adapter in silent mode Verifying the VCS adapter installation Uninstalling the VCS adapter Chapter 3. Configuring Inoking the configuration dialog Using the cfgeezdmn command Using the task launcher Configuring System Automation Application Manager Domain tab Command Shell tab Discoery Library Adapter tab OSLC tab User Credentials tab Eent Publishing tab Security tab Logger tab Saing the common configuration Refreshing the application manager common configuration Configuring System Automation Application Manager in silent mode Configuring an alternate end-to-end automation host Configuring Agentless Adapters Configuring the local Agentless Adapter Configuring remote Agentless Adapters Controlling Agentless Adapters Configuring Agentless Adapters in silent mode 117 Configuring high aailability High aailability options with DB Actiating the high aailability policy Configuring the high aailability policy Replicating the configuration files Setting up the domain Remoing the domain Validating and storing the automation policy 128 Defining the automation policy Remoing the automation policy Configuring high aailability in silent mode High aailability policy using System Automation for Multiplatforms Notes and restrictions Configuring high aailability for a disaster recoery setup on two sites Configuring the high aailability policy for a disaster recoery setup Other high aailability configuration tasks Configuring high aailability for a disaster recoery setup in silent mode High aailability policy using System Automation for Multiplatforms Notes and restrictions Configuring Distributed Disaster Recoery Configuring the destination for GDPS eents 141 Configuring the GDPS agent Configuring synchronous communication with GDPS Configuring the hardware adapter Refreshing the actie hardware adapter configuration Testing the hardware adapter Configuring the hardware adapter in silent mode Configuring the TPC-R domain Refreshing the TPC-R domain settings Testing the TPC-R domain configuration Configuring the TPC-R domain in silent mode 152 Configuring the HACMP adapter Inoking the HACMP adapter configuration dialog Configuring the HACMP adapter settings Replicating the configuration files to other nodes in the domain Defining the HACMP adapter automation policy Remoing the HACMP adapter automation policy Configuring the HACMP adapter in silent mode 162 Controlling the HACMP adapter Configuring the FOC adapter Inoking the FOC adapter configuration dialog 163 Configuring the FOC adapter settings Replicating the configuration files to other nodes in the domain Configuring the FOC adapter in silent mode 169 Proiding high aailability for the FOC adapter 170 Configuring the VCS adapter Inoking the VCS adapter configuration dialog 171 Configuring the VCS adapter settings Replicating the configuration files to other nodes in the domain Defining the VCS adapter automation policy 180 Remoing the VCS adapter automation policy 181 Configuring the VCS adapter in silent mode Controlling the VCS adapter Configuring in silent mode Working in silent mode Performing tasks manually Inoking silent configuration Silent mode input properties file Editing the input properties file Output in silent mode Configuration properties files Configuration properties files of the System Automation Application Manager Configuration properties files of the HACMP adapter i Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

7 Configuration properties files for the VCS Solaris adapter Configuration properties files of the FOC adapter Chapter 4. Integrating Eent consoles IBM Tioli Netcool/OMNIbus Tioli Enterprise Console Enabling eent generation in System Automation Application Manager Enabling eent filtering Tioli Business Serice Manager (TBSM) Integrating with System Automation Application Manager Prerequisites Configuring TBSM Configuring the Discoery Library Toolkit Integrating System Automation resources in TBSM Customizing TBSM iews to add information from System Automation Configuring Tioli Business Serice Manager launch-in-context support Tioli Monitoring and Tioli Composite Application Manager Prerequisites Tioli Monitoring oeriew Integrating with System Automation Application Manager Creating a Tioli Monitoring situation to trigger an automated restart zenterprise Hardware Management Console Setting up the Hardware Management Console 253 Obtaining the Hardware Management Console certificate Firewall considerations Working with the discoery library adapter eezdla options quick reference eezdla options Chapter 5. Securing Security concepts Security tab Securing the connection to end-to-end adapters using SSL Generating Keystore and Truststore with SSL public and priate keys Enabling SSL security in the Application Manager configuration Enabling SSL security in FLA adapter configurations Optional: Enforcing usage of SSL for all FLA domains Securing communication with the zenterprise Hardware Management Console Managing the security setup for Agentless Adapters Managing user credentials to access single nodes with Agentless Adapters Managing SSH public keys Using IBM Support Assistant Installing IBM Support Assistant and the Tioli System Automation for Multiplatforms plug-in Notices Trademarks Index Contents

8 i Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

9 Figures 1. Oeriew of System Automation product family 2 2. Installation wizard: Required RAM information dialog Examples for resource references to resources and resource groups Example for end-to-end automation groups that are distributed oer different platforms Installation wizard: Select your language Application Manager tab of the Automation Manager Configuration dialog Non-Clustered Nodes tab of the Automation Manager Configuration dialog Virtual Serer / HW Management tab of the Application Manager Configuration dialog Storage Replication tab of the Application Manager Configuration dialog High Aailability tab of the Application Manager Configuration dialog Change Passwords tab of the Application Manager Configuration dialog Maintaining configurations for multiple Agentless Adapters End-to-end high-aailability scenario with a shared database file system End-to-end high-aailability scenario with a remote database file system Resource groups, resources, and their relationships Resource groups, resources and their relationships Configuration of the HACMP adapter HACMP Adapter: Automation Adapter Configuration Dialog Main panel of the FOC Automation Adapter Configuration dialog Configuration of the VCS adapter VCS Automation Adapter Configuration dialog Warning message: Inconsistent IP Addresses Sample configuration of launch entry Modifying menu entries that are displayed in the Tools menu TBSM basic architecture Identification Fields tab Tree template editor Oeriew of the IBM Tioli Monitoring infrastructure Application Manager Local Agentless Adapter Configuration Agent attributes which can be added as additional attributes Perform an SA Application Manager command shell command as action for an Tioli Monitoring situation Keystore and Truststore generation using SSL Authentication with the Agentless Adapter on a remote node SSH key exchange oeriew Copyright IBM Corp. 2006, 2014 ii

10 iii Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

11 Tables 1. System Automation Application Managerproduct DVDs Archie files of the electronic delierable 3 3. Supported operating systems for System Automation Application Manager Supported operating systems for non-clustered nodes managed by the Agentless Adapter Disk space requirements Installation directory and Tioli Common Directory DB2 data for local and remote DB2 setup WebSphere Application Serer installation parameters Installation parameters End-to-end automation domain name WebSphere Application Serer user ID System Automation Administrator user ID Directories on the product DVD Remote Agentless Adapter product DVD Archie files of the electronic delierable Supported operating systems for Distributed Disaster Recoery Supported operating systems of managed clusters using GDPS for storage replication Supported operating systems of managed clusters using TPC-R for storage replication Supported enironments Distributed Disaster Recoery with GDPS Supported enironments Distributed Disaster Recoery with TPC-R Supported operating systems for the HACMP adapter Supported operating systems for the FOC adapter Supported operating systems for the VCS adapter Default directories Worksheet to define disaster recoery topology Worksheet to define disaster recoery hardware Worksheet to define disaster recoery workload Database tables Archies for AIX platforms Archies for Linux on System x Archies for Linux on System z Recommended end-to-end adapter and J2EE framework settings in a DR setup Archies for applying serice to remote Agentless Adapter Resources in the automation policy for the end-to-end automation manager Resources in the high aailability policy for a disaster recoery setup Resources in the HACMP adapter automation policy Resources in the VCS adapter automation policy Generated input properties files System Automation Application Manager eent class types alerts.status: Common System Automation status attributes used in resource status change eents alerts.status: Resource, domain, eent identification alerts.status: Other attributes used in resource status change eents alerts.status: Domain status change eents Existing rules file fields for System Automation eents Compound State to OMNIbus seerity mapping EIF seerity to OMNIbus seerity mapping Eent Seerity to TBSM State Mapping Text-based incoming status rules for TBSM Launch-in-context action parameters eezdla return codes Command line options for the discoery library adapter Copyright IBM Corp. 2006, 2014 ix

12 x Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

13 About this book Who should read this guide This guide proides information needed to plan, install, configure, and upgrade System Automation Application Manager (from here on referred to as System Automation Application Manager) and the automation adapters for the following clustering products: High Aailability Cluster Multi-Processing / PowerHa (from here on referred to as HACMP ) Microsoft Cluster Serer / Failoer Cluster (from here on referred to as MSCS) VERITAS Cluster Serer (from here on referred to as VCS. This guide is for planners, installers, and administrators who plan to install and configure System Automation Application Manager. Where to find more information The Tioli System Automation library contains the following books, including this one, describing System Automation Application Manager: IBM Tioli System Automation Application Manager Administrator's and User's Guide, SC IBM Tioli System Automation Application Manager Installation and Configuration Guide, SC IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide, SC You can download the books at: More information about Tioli System Automation for Multiplatforms can be found in the following books: IBM Tioli System Automation for Multiplatforms Administrator's and User's Guide, SC Tioli System Automation for Multiplatforms Installation and Configuration Guide, SC Tioli System Automation for Multiplatforms Reference, SC Tioli System Automation for Multiplatforms HIgh Aailability Policies Guide, SC 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: Copyright IBM Corp. 2006, 2014 xi

14 The IBM Tioli System Automation for Multiplatforms home page is: The IBM Tioli System Automation for z/os home page is: Conentions used in this guide ISO 9000 Related information This guide uses seeral conentions for special terms and actions and operating system commands and paths. Typeface conentions This guide uses the following conentions: Typically, file names, directories, and commands appear in a different font. For example: File name: setup.jar Directory: /etc/hosts Command: eezdmn -start 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 ISO 9000 registered quality systems were used in the deelopment and manufacturing of this product. This topic proides information about publications and Web sites related to 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 xii Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

15 How to obtain publications How to reach us by IBM DB2 publications: DB2 publications can be found on the IBM DB2 for Linux, Unix and Windows Web site at Information_Management/DB2_for_Linux,_UNIX_and_Windows The link to the PDF manuals is aailable in the Documentation -> Product Documentation 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 (SG ) IBM Tioli Common Reporting (TCR) publications: TCR publications can be found on the IBM Tioli Common Reporting Web site at: IBM TotalStorage Productiity Center for Replication (TPC-R) publications: TPC-R publications can be found on the TotalStorage Productiity Center for Replication Web site at: IBM Support Assistant (ISA): ISA Publications are aailable on the IBM Support Assistant Web site at: The Tioli System Automation publications are also aailable (alid at the time of release) at these Web sites: If you would like to contact us by , send your comments to About this book xiii

16 xi Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

17 What's new in this release Get a quick oeriew about the new features of System Automation Application Manager ersion 4.1. New DASH user interface for the operations console The System Automation operations console is completely redesigned, based on Jazz for Serice Management and Dashboard Application Serices Hub. Key enhancements are: More flexible and dynamic iews Create your own dashboards based on Dashboard Application Serices Hub capabilities. Customize predefined dashboards, for example change widget layout or configure displayed columns. The predefined dashboard Domain and Automation Health proides a graphical status oeriew and drill down capabilities for more details. Use the predefined dashboard Explore Automation Nodes to explore all domains and nodes that are connected to System Automation Application Manager and drill down to the hosted resources. The predefined dashboard Operate End-to-End Resources displays automated resources and a graphical iew of resource relationships. You can now allow user requests against multiple resources at a time You can allow priorities on requests. The isualization of different group types is improed. Performance of System Automation operations console is improed. Serer group The serer group is a new policy element, designed to group resources together, which hae to react to dynamic load requirements by adding members if needed. The serer group introduces automatic failoer capabilities for its members and allows to dynamically start and stop spare member by modifying the aailability target of the serer group. Copyright IBM Corp. 2006, 2014 x

18 xi Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

19 Chapter 1. Planning Planning for System Automation Application Manager before introducing its software into your enterprise system helps ensure that the system you implement meets your needs and adapts to your existing infrastructure. This topic describes how to plan for System Automation Application Manager, including assessing your current infrastructure. Planning for System Automation Application Manager Prepare the installation of System Automation Application Manager on AIX or Linux systems. Check out first if you meet all required prerequisites, before you start your installation. 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 SA User Web browser 1 SA Application Manager highly aailable installed Systems 3 SA Application Manager component or bundled Adapter Other product component (with SA Application Manager Adapter) MS Failoer Cluster with SA Application Manager MSCS Adapter HACMP/ PowerHA Cluster with SA Application Manager HAC Adapter Veritas CS Cluster with SA Application Manager VCS Adapter Single Node Systems attached as Remote Endpoints to Agentless Adapter SA Application Manager remotely installed Agentless Adapter Systems SA for Multiplatforms Cluster with SA Application Manager SAM Adapter SA z/os Sysplex with SA Application Manager ING Adapter High Aailability / Automation Clusters Systems with ITM / ITCAM agents attached to TEMS ITM / ITCAM TEMS Figure 1. Oeriew of System Automation product family Planning for the Agentless Adapter on page 18 Decide if you want to install the Agentless Adapter local or remote. Planning for the FOC adapter on page 27 If you are already using Microsoft Failoer Cluster (FOC) for an existing high aailability cluster, System Automation Application Manager proides the FOC adapter to integrate resources that are managed by FOC into an end-to-end automation enironment. Planning for the HACMP adapter on page 25 If you are already using IBM High Aailability Cluster Multiprocessing for an existing high aailability cluster, System Automation Application Manager proides the HACMP adapter to integrate resources that are managed by HACMP into an end-to-end automation enironment. Planning for the VCS adapter on page 32 If you are already using Veritas Cluster Serer (VCS) for an existing high aailability cluster, System Automation Application Manager proides the VCS adapter to integrate resources that are managed by VCS into an end-to-end automation enironment. 2 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

21 Packaging You can order System Automation Application Manager as a media pack or download the electronic delierable from an IBM software distribution download site. The URL for the electronic distribution is sent after purchasing the product. Media shipment There is a separate DVD for each supported operating system. The following table lists the ersions of the product DVDs that are aailable for System Automation Application Manager. To install the product, use the installation wizard file listed in the right column of the table. Table 1. System Automation Application Managerproduct DVDs Operating system Product DVD label Installation wizard file AIX Tioli System Automation Application Manager 4.1 for AIX EEZ4100AIX/AIX/ setup.bin Linux on System x Linux on System z Tioli System Automation Application Manager 4.1 for Linux on System x Tioli System Automation Application Manager 4.1 for Linux on System z EEZ4100I386/i386/ setup.bin EEZ4100S390/s390/ setup.bin For information about the middleware software DVDs that are shipped with System Automation Application Manager, refer to Contents of the middleware software DVDs on page 43. Electronic distribution Each supported operating system has a separate electronic delierable. The following tables list the archies that you need to install System Automation Application Manager. Table 2. Archie files of the electronic delierable Operating system Archie name Description AIX CIVE0ML.bin The archie is self-extracting. Linux on System x CIVE1ML.tar 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. Linux on System z CIVE3ML.tar 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 extracting the archie, the directory structure is identical to the directory structure on the corresponding DVD. Prerequisites Make sure you fulfill the software and hardware requirements for System Automation Application Manager. Supported operating systems System Automation Application Manager supports arious ersions of AIX and Linux operating systems. The following table lists the operating systems that are supported for System Automation Application Manager. If you want to exploit the Distributed Disaster Recoery functionality, refer to the following tables: Chapter 1. Planning 3

22 Table 16 on page 21, Supported operating systems for Distributed Disaster Recoery Table 17 on page 21, Supported operating systems of managed clusters using GDPS for storage replication Table 18 on page 22, Supported operating systems of managed clusters using TPC-R for storage replication The list of operating systems in the following table is supported by the local Agentless Adapter as well as by remote Agentless Adapters. Table 3. Supported operating systems for System Automation Application Manager Operating system IBM System x 1 Power Systems IBM System z SUSE Linux Enterprise Serer 10 (64 bit) X X SUSE Linux Enterprise Serer 11 (64 bit) X X Red Hat RHEL Linux 5 (64 bit) 3 X X Red Hat RHEL Linux 6 (64 bit) X X AIX X AIX X The following Serice Pack or technology leels are supported, unless one of the notes below indicates a more specific minimum requirement. Serice Pack leels of the listed supported SUSE ersions or higher. Serice Pack leels of the listed Red Hat ersion or higher. Technology leels of the listed AIX ersions or higher. Note: 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. All listed Linux operating systems running under the Red Hat Enterprise Virtualization Hyperisor (RHEV-H) KVM ersion 5.4 or higher are also supported. Howeer, the lie migration functionality proided by this hyperisor is not supported. 2. System Automation Application Manager does not support AIX Workload Partitions (WPAR) mobility or relocation. 3. The supported minimum leel is Red Hat Enterprise Linux 5.6 Installing prerequisites Before you start to install System Automation Application Manager, check if all prerequisites are installed or configured. The following prerequisites must be satisfied before you can start the installation wizard for System Automation Application Manager: Jazz for Serice Management including the 32-bit ersion of WebSphere Application Serer and the Dashboard Application Serices Hub must be 4 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

23 installed as described in Installing Jazz for Serice Management on page 47. No other WebSphere Application Serer product installation must exist on the system. Global security must be enabled. Jaa 2 security must be disabled, otherwise the installation fails. Jaa 2 security is not supported. A DB2 serer must be installed as described in Installing a DB2 serer on page 43. The DB2 serer instance must be running and accepting client connections. For more information about setting up the DB2 enironment, refer to IBM DB2 Administration Guide: Implementation. A Korn shell must be installed and accessible using /usr/bin/ksh. A Korn shell is required for the system where the Application Manager serer is installed as well as for each system where a remote Agentless Adapter is installed. The local Agentless Adapter that is installed as part of System Automation Application Manager requires the 32-bit ersion of the pluggable authentication module (PAM). In the current RHEL 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. This user ID is typically "root". Seeral 32-bit libraries must be installed on each SLES 10.3 and SLES 11 system, een if a 64-bit kernel is running, before System Automation Application Manager can be installed. These libraries are contained in the following RPM Package Manager packages: xorg-x11-libs-32bit glibc-32bit libstdc bit (SLES 10.3) libstdc bit (SLES11) Seeral 32-bit libraries must be installed on each Red Hat 6 system, een if a 64-bit kernel is running, before System Automation Application Manager can be installed. The libraries are contained in the following RPM Package Manager packages: libgcc glibc-2.12 libstdc compat-libstdc Supported operating systems for non-clustered nodes managed by the Agentless Adapter The Agentless Adapter manages non-clustered nodes on arious ersions of Windows, AIX, Linux, Solaris, z/os, and HP-UX operating systems. Remote applications managed by the Agentless Adapter ia remote protocols such as SSH can be located on one of the following supported operating systems: Chapter 1. Planning 5

24 Table 4. Supported operating systems for non-clustered nodes managed by the Agentless Adapter Operating system IBM System x 1, 2 Power Systems 2 IBM System z 2 Other platforms 2 32 bit 64 bit Windows Serer 2000 x Windows Serer 2003 x x IA64 Windows XP x Windows Vista x x IA64 Windows Serer 2008 R1 x x IA64 Windows Serer 2008 R2 x IA64 Windows 7 x x Windows 8 x Windows Serer 2012 x Windows Embedded POSReady x x Windows Embedded Standard x x Windows Embedded Enterprise x x AIX 5.2 x AIX 5.3 (AIX 5L Version 5.3) ML 4 x AIX 6.1 x AIX 7.1 x SUSE Linux Enterprise Serer 8 x x x x SUSE Linux Enterprise Serer 9 x x x x IA64 SUSE Linux Enterprise Serer 10 x x x x IA64 SUSE Linux Enterprise Serer 11 x x x x IA64 SLED 10 x x SLED 11 x x Red Hat RHEL Linux 3 AS x x x x Red Hat RHEL Linux 4 AS x x x x IA64 Red Hat RHEL Linux 5 x x x x IA64 Red Hat RHEL Linux 6 x x x x IA64 Red Hat Desktop 5.0 x x Red Hat Desktop 6.0 x x SOLARIS 8 x x SPARC SOLARIS 9 x x SPARC SOLARIS 10 x x SPARC z/os V1.6, V1.7, V1.8, V1.9, V1.10, V1.11, V1.12, V x HP-UX 11i (32 bit) PA-RISC, IA64 Note: 1. IBM System x with IA32, EM64T, or AMD64 architecture. 6 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

25 Any other systems with IA32, EM64T, or AMD64 architecture are also supported. All supported operating systems are also supported when running under VMware. 2. Secure communications with targets, using SSH Protocol (SSH ersion 2), requires the use of OpenSSH or higher AIX targets: OpenSSH 4.7 Sun targets: SSH 1.1 z/os targets: OpenSSH package proided by IBM Ported Tools for z/os SSH packages from other endors, or earlier ersions, are not supported. 3. z/os targets require z/os UNIX System Serices (USS) and IBM Ported Tools for z/os (OpenSSH) to be installed. Documentation for OpenSSH can be found here: The IBM Ported Tools document is the authoritatie source for information describing how to set up OpenSSH on z/os. OpenSSH is supported on z/os 1.4 and higher. Perform the following steps to set up the SSH serer: Run COMMON.JCL(OPENSSH). Add SSHD JOBNAME SSHD5 ; SSH Serer to the AUTOLOG section of USER.PARMLIB(TCPPROF2) Add 22 TCP SSHD5 ; SSH Serer to the PORT section of USER.PARMLIB(TCPPROF2) Edit /etc/ssh/sshd_config, uncomment the UsePriilegeSeparation parameter and change it to no. Re-IPL, the serer should be started by TCP/IP. Browse /tmp/syslogd/ auth.log and check for a message stating sshd : Serer listening on port 22. to erify if the serer is started. Supported ersions of IBM Tioli Monitoring (ITM) You can use the Agentless Adapter to integrate resources which are monitored by IBM Tioli Monitoring or by IBM Tioli Composite Application Manager. These Tioli Monitoring managed resources are integrated by using existing Tioli Monitoring agents. The Agentless Adapter retriees monitoring information from Tioli Monitoring Agents and performs start and stop operations ia these agents. The supported IBM Tioli Monitoring ersions for this feature are: The following types of Tioli Monitoring agents can be integrated: Application agents (also referred to as non-os agents) and custom agents OS agents System Automation Application Manager proides predefined templates for the integration of the following agents: Apache Web Serer WebSphere Application Serer Chapter 1. Planning 7

26 DB2 Custom agents built with the Tioli Monitoring Agent Builder Linux OS Agent UNIX OS Agent Middleware software requirements Install all required middleware software before you start to install System Automation Application Manager. 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 setup or a DB2 JDBC drier for a remote setup. WebSphere Application Serer (32-bit ersion, Jaa 7 enabled) Jazz for Serice Management including Dashboard Application Serices Hub 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. DB2 software prerequisites Before you can install System Automation Application Manager, IBM DB2 must be installed on the system where the database of System Automation Application Manager is hosted. For a new DB2 installation, you can install IBM DB2 for Linux, UNIX, and Windows Enterprise Serer Edition Version 10.1 (64-bit), which is bundled with Jazz for Serice Management and with System Automation Application Manager ersion 4.1. If you plan to use additional features of Jazz for Serice Management that require a database (e.g., the registry serices), use a ersion of IBM DB2 that is supported by Jazz for Serice Management, for example Enterprise Serer Edition Version 10.1 (64-bit). If you plan to use the database installation to use with System Automation Application Manager only, you can use the following database ersions as well: IBM DB2 for Linux, UNIX, and Windows Workgroup Serer Edition 10.1 (64-bit) or higher IBM DB2 10 for z/os or higher Local DB2 setup No additional prerequisites are required for a local DB2 setup. If you are using a local DB2 setup, the end-to-end automation 8 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

27 management database and the database tables are created by the installation program during the installation of System Automation Application Manager. Remote DB2 setup Manual install steps are required for a remote DB2 setup. Before you can install System Automation Application Manager, the following software prerequisites must be manually installed: A DB2 JDBC drier must be installed on the System Automation Application Manager node. WebSphere Application Serer IBM Tioli System Automation Application Manager only supports the 32-bit ersion of WebSphere Application Serer. Make sure that WebSphere Application Serer is configured to run with Jaa 7. The following application serers are supported: WebSphere Application Serer ersion and future releases, modifications, and fix packs. WebSphere Application Serer ersion 8.5 Network Deployment is not supported. 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 DVD "IBM WebSphere Application Serer Base Version 8.5". The "Getting started" topics in the Information Center for IBM WebSphere Application Serer, Version 8.5. An IBM WebSphere Application Serer Getting started document is also aailable on the product DVD 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 Jazz for Serice Management The following Jazz for Serice Management components are at least required for the System Automation Application Manager serer: Jazz for Serice Management extension for IBM WebSphere 8.5, ersion 1.1 IBM Dashboard Application Serices Hub, ersion IBM WebSphere Application Serer ersion or higher is supported. You can choose to install WebSphere Application Serer when installing Jazz for Serice Management, or you can use an existing supported WebSphere Application Serer instance. Note: Only the 32-bit ersion of the IBM WebSphere SDK for Jaa is supported. You can find the latest requirements report for IBM Dashboard Application Serices Hub on the following web page: System requirements report for IBM Dashboard Application Serices Hub Chapter 1. Planning 9

28 Jazz for Serice Management Version documentation Supported Web browsers System Automation Application Manager has a web-based user interface. It is displayed in a Web browser that connects to the Dashboard Application Serices Hub on which the System Automation Application Manager dashboards are running. The Web browser can run on any system. The following ersions of Web browsers are supported: Microsoft Internet Explorer V9 Microsoft Internet Explorer V10 Firefox Extended Support Release (ESR) 17 Firefox Extended Support Release (ESR) 24 For updated information about the support of later browser ersions, check the Software Product Compatibility Report for System Automation Application Manager on the following site: prodguid/1r0/clarity/index.jsp. Hardware requirements Make sure your systems proide the required hardware requirements to install DB2. The hardware requirements listed below refer to the installation of DB2. For more information on hardware requirements for the required middleware software, refer to Installing the middleware software on page 43. Memory: Make sure you hae enough memory aailable on the serer to install System Automation Application Manager. The required memory (RAM) is 4 GB or more to install WebSpehere Application Serer and System Automation Application Manager on the same serer. If you start to install System Automation Application Manager, a memory check is automatically processed. In case the serer proides less than 4 GB operational memory, a warning is displayed. In silent installation mode, the warning is written into the log and the installer is stopped. You can start the installation with the command line option -Dskipmemtest=true but you may consider to use the installation wizard instead. 10 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

29 Figure 2. Installation wizard: Required RAM information dialog Note: Check if it is required to increase the heap size. For more information, refer to Modifying aailable heap size on page 65. TCP/IP connectiity: It is required to install seeral products to run System Automation Application Manager. Some of these products require TCP/IP connections. You can install DB2, WebSphere Application Serer and System Automation Application Manager on one serer or on different serers, depending on your architecture. For example: Local DB2 setup: Websphere Application Serer, System Automation Application Manager, and the DB2 serer run on the same system. Remote DB2 setup: Websphere Application Serer and System Automation Application Manager run on the same system, while the DB2 serer runs on another system. 1. Local DB2 setup: Websphere Application Serer, System Automation Application Manager, and the DB2 serer run on the same system. 2. Remote DB2 setup: the Websphere Application Serer and System Automation Application Manager run on the same system, while the DB2 serer runs on another system. Proide TCP/IP connections between the following products and System Automation Application Manager components: WebSphere Application Serer and the resource adapters WebSphere Application Serer and the operations console System Automation Application Manager and the DB2 serer Disk space requirements: Check if you hae all the required disk, file, directory, and registry space to install System Automation Application Manager. Chapter 1. Planning 11

30 The following disk space requirements must be met to install System Automation Application Manager. Note: The table does not include the space required to install the middleware software. Table 5. Disk space requirements Description Default directory Disk space Installation directory of System /opt/ibm/tsamp/eez/ 700 MB Automation Application Manager WebSphere Application Serer (where automation manager and operations console are deployed) AIX: /usr/ibm/websphere/appserer/ Linux: /opt/ibm/websphere/appserer/ 100 MB DB2 database ~db2inst1 120 MB Temporary disk space needed for installation and installation log and response files Configuration file directory and policy pool directory of System Automation Application Manager /tmp/ Note: Make sure your /tmp directory has fie times the size of the installation file setup.bin. /etc/opt/ibm/tsamp/eez/cfg/ /etc/opt/ibm/tsamp/eez/policypool/ Tioli Common Directory /ar/ibm/tioli/common/ 40 MB Installer registry /ar/ 1MB 1GB 1MB Preparing for installation Collect all the required information like configuration parameters and user IDs, before you start your installation. Collecting the information The graphical installation of System Automation Application Manager is wizard-drien. Make sure that you specify all required parameters on the installation wizard panels and that your entries are correct. 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. Installation directory and Tioli Common Directory: If you want to use different directory names other than the default names, make sure you are a aware of restrictions. The parameters listed in the following table must always be specified. 12 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

31 Table 6. Installation directory and Tioli Common Directory Parameter Description Default Installation directory name The directory to which the installable features are installed. /opt/ibm/tsamp/eez In this guide, this directory is referred to as EEZ_INSTALL_ROOT. When specifying a directory other than the default, obsere the following restrictions: Tioli Common Directory 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. 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 (only possible if no Tioli Common Directory already exists on the system), obsere the following restrictions: /ar/ibm/tioli/common 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. Installation parameters for DB2: Make sure you hae all required parameters aailable that are required to install DB2 on a local or remote serer. The parameters listed in the following table must be specified. Chapter 1. Planning 13

32 Table 7. DB2 data for local and remote DB2 setup Parameter Description Default DB2 directory Local DB2 setup: The installation location of the DB2 Database Manager. The location is detected on your system and displayed as the default directory. DB2 JDBC drier path on local system 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. For remote DB2 setup only: Path to the directory where the files DB2 JDBC are located. 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: The installation wizard can retriee the alid DB2 instance port number automatically. If you choose not to use this function, 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 Tioli System Automation Application Manager, Reference and Problem Determination Guide. 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 db2inst1 14 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

33 Table 7. DB2 data for local and remote DB2 setup (continued) Parameter Description Default Database instance owner password Automation manager database The password for the instance owner user ID of the DB2 instance in which the automation manager and operations console databases 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. No default alue is proided EAUTODB Backend ersion 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 V9.1 - running on z/os DIST: DB2 LUW- running on distributed system 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: WebSphere Application Serer administratie security must be enabled before you install System Automation Application Manager. Table 8. WebSphere Application Serer installation parameters Parameter Description Default WebSphere Application Serer directory WebSphere Application Serer (WAS) profile name WebSphere Application Serer (WAS) serer name WAS Admin User ID WAS Admin User Password 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 user ID of the WebSphere Application Serer administrator. The password of WebSphere Application Serer administrator user ID. 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. No default alue is proided. No default alue is proided. Chapter 1. Planning 15

34 Eent console connection configuration data: Make sure you hae the required installation parameters aailable, if you want to utilize OMNIbus for end-to-end automation management eents. System Automation Application Manager can send EIF eents about state changes of automated resources to IBM Tioli Netcool/OMNIbus (OMNIbus). Table 9. Installation parameters Parameter Description Default Host Name The name of the host where the OMNIbus Probe for Tioli EIF is localhost installed. Port Number The port number for the OMNIbus Probe for Tioli EIF For more information about utilizing OMNIbus for end-to-end automation management, refer to IBM Tioli Netcool/OMNIbus on page 196. Name of the end-to-end automation domain: Be aware of the naming rules for the end-to-end automation domain name. Table 10. End-to-end automation domain name Parameter Description Default Automation domain name The domain name must be unique and may not be used for any other automation domain. The domain name must contain a maximum of 64 characters. The characters used for the domain name are limited to the following ASCII characters: A Z, a z, 0 9,. (period), and _ (underscore). FriendlyE2E Obtaining the WebSphere Application Serer user ID 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 you need to specify the user ID and the password. Table 11. 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 <none> Obtaining the 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. 16 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

35 In the installation wizard you need to specify the data listed in the following table: Table 12. 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> Table 13. Directories on the product DVD Installation media 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 DVDs for each supported platform. This is what the DVD labeled System Automation Application Manager V4.1 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: Directory README license DDL ECExtension <PLATFORM>¹ DOCS Content For example, copyright notices and license agreements License key Scripts for creating DB2 databases and tables when remote DB2 setup is used setup.jar Product installer and files needed for installing the product Documentation Note: <PLATFORM> is one of the following: AIX i386 (Linux on System x) s390 (Linux on System z) Supported languages System Automation Application Manager supports English and a set of other languages. In addition to English, System Automation Application Manager supports the following languages: German Spanish French Italian Japanese Chapter 1. Planning 17

36 Korean Brazilian Portuguese Simplified Chinese Traditional Chinese Planning for the Agentless Adapter Decide if you want to install the Agentless Adapter local or remote. Installation for the local Agentless Adapter and remote Agentless Adapters is performed in different ways. The local Agentless Adapter is automatically installed together with the System Automation Application Manager product as described in Installing System Automation Application Manager on page 50. You can install remote Agentless Adapters on systems other than the system where the Application Manager is installed. Only one instance of the Agentless Adapter can be installed on any remote node on AIX or Linux systems. For more information, refer to System Automation Application Manager Administrator's and User's Guide. Packaging The remote Agentless Adapter is shipped with System Automation Application Manager. You can order System Automation Application Manager as a media pack or download the electronic delierable from an IBM software distribution download site. The URL for the electronic distribution is sent after purchasing the product. Media shipment Install the remote Agentless Adapter from the DVD Tioli System Automation Application Manager Remote Clients all platforms. This DVD contains the installation wizards for all supported platforms. To install the adapter, use the installation wizard file listed in the right column of the following table. Table 14. Remote Agentless Adapter product DVD Operating system Windows AIX Linux on System x Linux on POWER Linux on System z Installation wizard file EEZ4100Remote/Windows/ALAdapt/setup.exe EEZ4100Remote/AIX/ALAdapt/setup.bin EEZ4100Remote/I386/ALAdapt/setup.bin EEZ4100Remote/PPC/ALAdapt/setup.bin EEZ4100Remote/S390/ALAdapt/setup.bin Electronic distribution There is a separate electronic delierable for each supported operating system. The following tables list the archies that you need to install the remote Agentless Adapter. Table 15. Archie files of the electronic delierable Operating system Archie name Description Windows CIVE8ML.exe The archie is self-extracting. 18 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

37 Table 15. Archie files of the electronic delierable (continued) Operating system Archie name Description AIX CIVE7ML.bin The archie is self-extracting. Linux on System x CIVE9ML.tar 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. Linux on POWER CIVF0ML.tar 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. Linux on System z CIVF1ML.tar 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 extracting the archie, the directory structure is identical to the directory structure on the corresponding DVD. Prerequisites You can install the remote Agentless Adapter only on operating systems that are supported by System Automation Application Manager. Planning for high aailability The operating system ersions that are supported by the remote Agentless Adapter are identical to the operating systems ersions that are supported by System Automation Application Manager in general. Refer to Supported operating systems on page 3 for the corresponding list. The Agentless Adapter requires the 32-bit ersion of the pluggable authentication module (PAM) on all operating systems other than Windows. Proide and configure the necessary prerequisites before you start to install you high aailability setup. The following prerequisites must be met, if you want your system to be highly aailable: Either 2 or 3 nodes must be part of the System Automation for Multiplatforms domain. System Automation for Multiplatforms must be installed on all nodes with a minimum leel of 3.1 or 2.3. If you use V2.3, the Distributed Disaster Recoery feature components are not part of the policy. Make sure all prerequisites of the respectie System Automation for Multiplatforms ersion that you are using are met. Check the System Automation for Multiplatforms documentation for further details. IBMStorageRM must be installed on all nodes. On Linux, the default installation includes IBMStorageRM. If you use System Automation for Multiplatforms V2.3 on AIX, IBMStorageRM is optionally. A irtual IP address must be aailable for the WebSphere Application Serer. See the Host name or IP address field on the Domain tab of the Automation Manager Common Configuration dialog. To start the dialog, enter cfgeezdmn on the command prompt. For more information, see Domain tab on page 97. A shared olume must be aailable for the System Automation Application Manager policy pool. See the Policy pool location field on the Domain tab of Chapter 1. Planning 19

38 the Automation Manager Common Configuration dialog. To start the dialog, enter cfgeezdmn on the command prompt. For more information, see Domain tab on page 97. If you want to include DB2 in your high aailability policy, a shared olume must be aailable for the DB2 database. See the DB2 tab in configuration dialog cfgeezdmn. If you want to include the System Automation Application Manager Agentless Adapter in your high aailability policy, proide a shared olume for its policy pool. See the Policy pool location field in Adapter tab on page 107. Enable the following ports in the firewall software for the communication between Agentless Adapter and target non-clustered nodes: UNIX SSH protocol ssh 22/TCP Windows WIN protocol Direct hosted "NetBIOS-less" SMB traffic uses ports microsoft-ds 445/TCP microsoft-ds 445/UDP For NetBIOS oer TCP (NBT) enable the following ports nbname 137/UDP nbname 137/TCP nbdatagram 138/UDP nbsession 139/TCP System Automation Application Manager must be installed on all nodes including the middleware (DB2, WebSphere Application Serer). Installation parameters for DB2 and the WebSphere Application Serer must be the same on all nodes to allow these applications to moe to another node seamlessly. These parameters are: 1. WAS - Application serer name 2. WAS - Application serer port 3. WAS - Profile directory 4. DB2 installation directory 5. DB2 instance owner user ID 6. DB2 instance owner mount point Planning for Distributed Disaster Recoery Distributed Disaster Recoery is shipped with System Automation Application Manager. Packaging The Distributed Disaster Recoery functionality is installed as part of the System Automation Application Manager installation. If you wish to exploit the Distributed Disaster Recoery functionality, you are not required to install additional programs. Prerequisites The supported operating systems depend on the storage replication technology that you are planning to use. 20 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

39 The functionality proided by the Distributed Disaster Recoery feature is aailable on the operating systems listed in Supported hardware and operating systems. Supported hardware and operating systems Hardware and operating system prerequisites ary depending on the storage replication technology, that is used: Distributed Disaster Recoery with GDPS, or Distributed Disaster Recoery with TPC-R. The following tables show the operating system platforms that are supported by the Distributed Disaster Recoery feature. Distributed Disaster Recoery The supported operating systems for Distributed Disaster Recoery are listed in Table 16 Distributed Disaster Recoery with GDPS If you use Geographically Dispersed Parallel Sysplex (GDPS) for storage replication, the supported operating systems for clusters that are managed by the Distributed Disaster Recoery feature are listed in Table 17. Distributed Disaster Recoery with TPC-R If you use Tioli Storage Productiity Center for Replication (TPC-R) for storage replication, the supported operating systems for clusters that are managed by the Distributed Disaster Recoery feature are listed in Table 18 on page 22. Table 16. Supported operating systems for Distributed Disaster Recoery Operating system: System x Power Systems System z SUSE Linux Enterprise Serer 10 (64 bit) TPC-R GDPS SUSE Linux Enterprise Serer 11 (64 bit) TPC-R GDPS Red Hat RHEL 5.0 AS (64 bit) TPC-R GDPS Red Hat RHEL 6.0 AS (64 bit) TPC-R GDPS AIX 6.1 TPC-R AIX 7.1 TPC-R Table 17. Supported operating systems of managed clusters using GDPS for storage replication Operating system: System x Power Systems System z SUSE Linux Enterprise Serer 10 (64 bit) SUSE Linux Enterprise Serer 11 (64 bit) Red Hat RHEL 5.0 AS (64 bit) Red Hat RHEL 6.0 AS (64 bit) AIX 6.1 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2, HACMP 1 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 SA MP, Agentless Adapter 2 Chapter 1. Planning 21

40 Table 17. Supported operating systems of managed clusters using GDPS for storage replication (continued) Operating system: System x Power Systems System z AIX 7.1 SA MP, Agentless Adapter 2, HACMP 1 Note: 1. Non-stretched clusters: IBM Tioli System Automation for Multiplatforms Stretched clusters: HACMP 2. Agentless Adapter represents the non-clustered nodes managed by the Agentless Adapter that is part of the System Automation Application Manager product. The operating systems listed in Supported operating systems for non-clustered nodes managed by the Agentless Adapter on page 5 are supported. Howeer, GDPS storage replication is not generally supported for these additional operating systems (but this is dependent upon your own testing actiities). Table 18. Supported operating systems of managed clusters using TPC-R for storage replication Operating system: System x Power Systems System z SUSE Linux Enterprise Serer 10 (64 bit) SUSE Linux Enterprise Serer 11 (64 bit) Red Hat RHEL 5.0 AS (64 bit) Red Hat RHEL 6.0 AS (64 bit) AIX 6.1 AIX 7.1 SA MP SA MP SA MP SA MP SA MP SA MP SA MP SA MP SA MP, HACMP SA MP, HACMP The operating systems of managed clusters correlate with the operating systems that are supported by the end-to-end automation adapters. Automation adapters are used to integrate the corresponding first leel automation domains into the end-to-end automation enironment. In Table 17 on page 21 and Table 18, SA MP represents the end-to-end automation adapter that is part of the System Automation for Multiplatforms product. For more specific information, refer to the operating system support table in Table 3 on page 4. HACMP represents the High Aailability Cluster Multi-Processing (HACMP) end-to-end automation adapter that is part of System Automation Application Manager. For more specific information about the operating system details refer to Prerequisites on page 25. Supported GDPS enironments You can use only specific ersions of the Distributed Disaster Recoery feature in combination with GDPS. The following ersions for Distributed Disaster Recoery with GDPS are supported. 22 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

41 Table 19. Supported enironments Distributed Disaster Recoery with GDPS Characteristic Supported enironment Mirroring technique PPRC controlled by GDPS (for non-stretched clusters) AIX LVM (for stretched clusters) Hardware Blade Center for System p and System x with Management Module (MM) serice processors. Other hardware is supported by a script exit. GDPS/PPRC is a software prerequisite for Distributed Disaster Recoery. For details of the prerequisites for GDPS/PPRC, refer to systems/z/ adantages/gdps/getstarted/gdpspprc.html. If you are planning to implement a setup with a System Automation Application Manager on both sites, additional prerequisites apply. To support this setup, a special type of System Automation Application Manager high aailability policy is required. Refer to Planning for high aailability on page 19 for detailed planning information regarding the application manager high-aailability policy, with the following exceptions: Only a single node in the high aailability cluster is required A irtual IP address is not required A shared olume for the policy pool is not required You must include DB2 as local EAUTODB. A shared olume for the database is not required, and the database must be on a local disk using DB2 HADR for replication. You must configure and actiate the high aailability policy on both sites. Supported TotalStorage Productiity Center for Replication (TPC-R) enironments You can use only specific ersions of the Distributed Disaster Recoery feature in combination with TPC-R. The following enironments for Distributed Disaster Recoery with TotalStorage Productiity Center (TPC-R) for Replication are supported. Table 20. Supported enironments Distributed Disaster Recoery with TPC-R Characteristic Supported enironment Mirroring technique Metro Mirror Failoer or Failback sessions controlled by TPC-R System Automation Application Manager V3.2.2 supports the following TotalStorage Productiity Center for Replication ersions: TotalStorage Productiity Center for Replication V and higher PTFs TPC-R V or later (for example 4.1.2) and PTFs Note: 1. TotalStorage Productiity Center for Replication is no longer maintained, and is therefore not supported. Chapter 1. Planning 23

42 2. If you receie an error message that contains the message number of System Automation Application Manager EEZI0063E, refer to the latest release notes to determine which serice leel is required. Preparing for installation Proide and configure the necessary prerequisites before you start to install your Distributed Disaster Recoery setup. Before you can use Distributed Disaster Recoery, check the following: For a setup with System Automation Application Manager on both sites, you can configure a specific single-node Application Manager high aailability policy that requires DB2 HADR. For this setup you must hae a corresponding DB2 HADR license. Secure Shell (ssh) is set up correctly: In the USS of the GDPS K System, an ssh client must be set up. For more information on how to set up OpenSSH in USS, see IBM Ported Tools for z/os User's Guide, SA , which is aailable from serers/eserer/zseries/zos/unix/port_tools.html). Public key authentication must be used in order to aoid the specification of a password in GDPS The disaster recoery policy is aailable and actiated, refer to Deeloping a disaster recoery policy in the IBM Tioli System Automation Application Manager Administrator's and User's Guide. The GDPS agent must be configured, see Configuring the GDPS agent on page 141 The GDPS agent must be started, refer to Controlling the GDPS agent in the IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide. The hardware adapter and credentials must be configured, see Configuring the hardware adapter on page 142. The hardware adapter must be started, refer to Controlling Adapter Commands, and the eezhwadapter command in the IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide. GDPS DCM must be set up. In particular, erify that: The NetView Eent/Automation Serice (E/AS) is configured: the default name for the address space is IHSAEVNT The TCP/IP definition contains the port used by the NetView Eent/Automation Serice DCM is enabled in the SA z/os policy The GDPS K System and System Automation Application Manager hae exchanged the ssh keys for ssh communication For general GDPS information, see GDPS Family An Introduction to Concepts and Facilities (SG ) and the GDPS Web site at systems/z/adantages/gdps/. 24 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

43 Planning for the HACMP adapter If you are already using IBM High Aailability Cluster Multiprocessing for an existing high aailability cluster, System Automation Application Manager proides the HACMP adapter to integrate resources that are managed by HACMP into an end-to-end automation enironment. Packaging The HACMP adapter is shipped with System Automation Application Manager. You can order System Automation Application Manager as a media pack or download the electronic delierable from an IBM software distribution download site. The URL for the electronic distribution is sent after purchasing the product. Media shipment You install the HACMP adapter from the DVD Tioli System Automation Application Manager Automation Adapters all platforms. Onthe DVD, you can find the installation package hac.adapter in the installation source directory EEZ4100Adapters/EEZ4100HACMP/AIX Electronic distribution The name of the archie file of the electronic delierable for the HACMP adapter is CIVE4ML.bin To extract the archie, run the executable. After extracting the archie, you can find the installation package hac.adapter in the same directory as on the HACMP adapter DVD. Prerequisites Make sure you proide the required prerequisites, before you install the HACMP adapter. The system on which you are installing the adapter must meet the following installation prerequisites: Required minimum HACMP release leel: or higher (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 Serice Release 5 or higher must be installed. SSL or SSH packages must be installed and the sshd subsystem must be running to be able to complete the Replication task of the adapter configuration Supported operating systems: Chapter 1. Planning 25

44 Table 21. Supported operating systems for the HACMP adapter Operating System Power Systems AIX 5.3 (AIX 5L Version 5.3) ML 4 AIX 6.1 AIX 7.1 x x x Note: Make sure that the ersion of your adapter is not higher than the ersion of System Automation Application Manager. Automating the HACMP adapter It is required to automate the HACMP adapter, if your HACMP cluster has more than one node. 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 156. Behaior of the HACMP adapter Make sure you are familiar with the HACMP adapter behaior to be able exploit the features and adantages. Before you install and use the HACMP adapter, makes sure you are familiar with the behaior of the HACMP adapterf : HACMP clusters are not request- but command-drien. Commands for bringing resources and groups online or offline are performed but not retained as persistent goals. No list of preiously issued commands is aailable, and commands preiously issued against a group or resource cannot be canceled. The latest command issued against a group or resource determines whether it should be online or offline. Commands issued by operators hae the same priority as commands issued by the end-to-end automation manager. HACMP resources and groups cannot be suspended from automation by an end-to-end automation operator. HACMP groups hae no "real" desired state. HACMP performs online and offline commands on HACMP groups by propagating them to member resources. HACMP groups only act as containers and reflect the state of the contained HACMP resources. If some of the HACMP resources in a group were brought online and others offline, the group is in a mixed state - it is not clear whether the desired state of the group is online or offline. HACMP clusters do not hae a policy concept as known by end-to-end automation. For this reason, the Policy Information page for HACMP domains does not show reasonable information. If HACMP groups are referenced in a SA AM start dependency then the HACMP application monitoring mode "startup" or "both" is required to ensure the correct SA AM automation behaior. 26 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

45 Planning for the FOC adapter If you configure dependencies between HACMP resource groups in the HACMP cluster, the applications in these HACMP resource groups are started sequentially. If the monitoring mode "startup" or "both" is used the sequential start sequence does not get affected. To ensure a smooth execution, you can configure seeral HACMP application monitors. One of these HACMP application monitors is configured to check the application startup for the application that is included in the HACMP resource group with a reference from SA AM. This ensures that the application in the HACMP resource group starts successfully before other dependent SA AM resources are started. If you are already using Microsoft Failoer Cluster (FOC) for an existing high aailability cluster, System Automation Application Manager proides the FOC adapter to integrate resources that are managed by FOC into an end-to-end automation enironment. Roadmap Before you install the FOC adapter, you must decide whether you want to make the adapter highly aailable. The roadmap proides an oeriew of the steps you need to perform to install and configure the adapter depending on your high-aailability decision. Roadmap to install a highly aailable FOC adapter Check the roadmap to install and configure FOC adapters that are highly aailable. If you want your FOC adapter to be highly aailable, perform the following steps: 1. Plan and prepare for the installation and configuration of the FOC adapter. For more information, refer to Planning and preparing for an highly aailable FOC adapter on page 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 FOC adapter on page 84). 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 FOC adapter in silent mode on page 85) or in interactie mode using the installation wizard (see Using the installation wizard to install the FOC adapter on page 84). 4. Configure the adapter on one of the cluster nodes using the adapter configuration dialog (see Configuring the FOC adapter on page 163). 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 in the domain on page 169). 6. Create the WSFC resources needed for making the adapter highly aailable. 7. Verify the installation and configuration (see Verifying the FOC adapter installation on page 85). Roadmap to install a FOC adapter Check the roadmap to install and configure FOC adapters that are not highly aailable. To install and configure your FOC adapter without high aailability, perform the following steps: Chapter 1. Planning 27

46 1. Plan and prepare for the installation and configuration of the FOC adapter (see Planning and preparing for an highly aailable FOC adapter on page 30). 2. Use the installation wizard to install the adapter on a cluster node (see Using the installation wizard to install the FOC adapter on page 84). 3. Configure the adapter using the adapter configuration dialog (see Configuring the FOC adapter on page 163). 4. Verify the installation and configuration (see Verifying the FOC adapter installation on page 85). Packaging The FOC adapter is shipped with System Automation Application Manager. You can order System Automation Application Manager as a media pack or download the electronic delierable from an IBM software distribution download site. The URL for the electronic distribution is sent after purchasing the product. Media shipment You install the FOC adapter from the DVD Tioli System Automation Application Manager Automation Adapters all platforms. Onthe DVD, you can find the installation wizard setup.exe in the installation source directory EEZ4100Adapters/EEZ4100MSCS\Windows Electronic distribution The name of the archie file of the electronic delierable for the FOC adapter is CIVE5ML.exe To extract the archie, run the executable. After extracting the archie, you can find the installation wizard setup.exe in the same directory as on the FOC adapter DVD. Prerequisites Make sure you proide the required prerequisites, before you install the FOC adapter. The Failoer Cluster Command Interface feature is required to configure the FOC adapter. Starting with Windows Serer 2012 system, this feature is not installed anymore per default as part of the Failoer Cluster installation. The system on which you are installing the adapter must meet the following installation prerequisites: Any of the Windows Serer ersions listed in Table 22 on page 29. System must be a Microsoft Failoer Cluster node. 64 MB RAM is required for running the FOC adapter serice. 40 MB RAM is required for running the adapter configuration dialog. Disk space requirements: 140 MB for FOC adapter installation 28 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

47 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) Supported operating systems for the FOC adapter FOC adapter run on Windows Serer 2012 only. Table 22. Supported operating systems for the FOC adapter Operating System Windows Serer 2012 R1 Enterprise Edition (64 bit) Windows Serer 2012 R2 Enterprise Edition (64 bit) System x x x Note: Make sure that the ersion of your adapter is not higher than the ersion of System Automation Application Manager. Installation directories for the FOC adapter Make sure you install the FOC adapter into the right directory using the right wording. For the FOC adapter installation directory and the Tioli Common Directory, the following restrictions apply: The FOC 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 FOC adapter, a domain user account with local administratie rights must be defined in the domain. The domain user account must be a member of the local administrators group on all nodes of the cluster the adapter will manage. Use this user account for the FOC adapter only. Before you install the FOC adapter you must perform the following steps: Create a domain user account which will run the FOC adapter serice later on. This user is referred to as SAAMAdapter hereon. Grant SAAMAdapter full control permission oer the Microsoft Failoer Cluster to be managed with the FOC adapter: Open Failoer Cluster Management and naigate to this failoer cluster. Right-click this failoer cluster and select the Properties context menu entry. Chapter 1. Planning 29

48 Select the Cluster Permissions tab and click the Add...button. In the Select Users, Computer, or Groups window specify the SAAMAdapter user account and select the OK button. On the 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 and click OK. Log into each system where you want to install the FOC 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... Specify gpedit.msc in the Open input field and click OK. 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 list iew a list of user rights is shown. Double-click on the right Log on as a serice and select the Add User or Group...button. Specify the SAAMAdapter user account and click OK. In the Log on as a serice Properties window click the OK. Close the Local Group Policy Editor window. Log into each system where you want to install the FOC 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 menu entry Run... Specify lusrmgr.msc in the Open input field and click OK. In the Local Users and Groups window select the Groups entry in the tree iew. 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 and click OK. In the Administrators Properties window click OK. Close the Local Users and Groups window. Planning and preparing for an highly aailable FOC adapter You need a irtual IP address to proide an highly aailable FOC adapter. If you want your FOC adapter to be highly aailable, perform the following steps: Obtain a irtual IP address: The FOC adapter will use this IP address for incoming connections Microsoft FOC will make the irtual IP address aailable on the appropriate Microsoft FOC node If desired, obtain a network name: If you specify the network name in the FOC 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 FOC adapter 30 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

49 Microsoft FOC will associate this network name with the irtual IP address on the DNS serer that is configured in the Microsoft Windows domain Behaior of the FOC adapter To make sure your system runs well using an FOC adapter, more information is proided to better understand the behaior of the FOC adapter in combination with System Automation Application Manager. Before you install and use the FOC adapter, consider the following aspects: The FOC adapter runs as a Windows serice. This serice logs on with the user account you specify during installation. All interactions with Microsoft FOC are performed on behalf of this user account. If authentication is enforced in the FOC adapter configuration you must specify an arbitrary alid user account with credentials in order to establish a session with the adapter. The user account and password combination is checked on the system where the FOC adapter you are trying to contact is currently running. For this reason you can define and use a Windows domain user account for this purpose. When being prompted for the user account name you must specify the user account in a way which uniquely describes its scope, for example to show which domain the user account belongs to. For domain user accounts you can specify the user account as domain\user or user@domain. Neertheless, the FOC adapter performs all operations on the Microsoft FOC cluster on behalf of the user account used by the System Automation Application Manager FOC adapter serice to log on. Microsoft FOC clusters are not request- but command-drien. Commands for bringing resources and groups online or offline are performed but not retained as persistent goals. No list of preiously issued commands is aailable, and commands preiously issued against a group or resource cannot be canceled. The latest command issued against a group or resource determines whether it should be online or offline. Commands issued by operators hae the same priority as commands issued by the end-to-end automation manager. Microsoft FOC resources and groups cannot be suspended from automation by an end-to-end automation operator. Microsoft FOC groups hae no "real" desired state. Microsoft FOC performs online and offline commands on Microsoft FOC groups by propagating them to member resources. Microsoft FOC groups only act as containers and reflect the state of the contained Microsoft FOC resources. If some of the Microsoft FOC resources in a group were brought online and others offline, the group is in a mixed state - it is not clear whether the desired state of the group is online or offline. Microsoft FOC clusters do not hae a policy concept as known by end-to-end automation. For this reason, the Policy Information page for Microsoft FOC domains does not show reasonable information. Microsoft FOC does not monitor resources which are not expected to be online. Example: A file share resource has two different cluster nodes as possible owners. If the file share is currently defined and working (that is, online) on the first node, Microsoft FOC does not monitor the state of the file share on the second cluster node. Microsoft FOC will not notice a manual definition of the file share on the second node. Chapter 1. Planning 31

50 The FOC adapter does not work around this monitoring approach and is thus not able to reliably report resources offline states. Microsoft FOC groups reject offline commands in the following cases: The group contains the quorum resource. The group contains the FOC adapter serice resource (if the adapter is made highly aailable). Microsoft FOC resources reject offline commands in the following cases: The resource is the quorum resource and the quorum resource directly or indirectly depends on the resource to be taken offline. The resource is the FOC adapter serice resource (if the adapter is made highly aailable). If the FOC adapter serice resource directly or indirectly depends on the resource to be taken offline (if the adapter is made highly aailable). Microsoft FOC nodes reject exclude commands if the adapter is made highly aailable and the group that contains the FOC adapter serice resource is located on the node. In this case, message EEZZ0012E appears indicating that the group in question cannot be taken offline without impacting the FOC adapter. Planning for the VCS adapter If you are already using Veritas Cluster Serer (VCS) for an existing high aailability cluster, System Automation Application Manager proides the VCS adapter to integrate resources that are managed by VCS into an end-to-end automation enironment. Packaging The VCS adapter is shipped with System Automation Application Manager. You can order System Automation Application Manager as a media pack or download the electronic delierable from an IBM software distribution download site. The URL for the electronic distribution is sent after purchasing the product. Media shipment You install the VCS adapter from the DVD Tioli System Automation Application Manager Automation Adapters all platforms. Onthe DVD, you can find the installation package install.bin in the installation source directory EEZ4100Adapters/EEZEEZ4100VCS/Solaris Electronic distribution The name of the archie file of the electronic delierable for the VCS adapter is CIVE6ML.zip To extract the archie, run the executable. After extracting the archie, you can find the installation package install.bin in the same directory as on the VCS adapter DVD. 32 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

51 Prerequisites Make sure you proide the required prerequisites and operating system, before you install the VCS adapter. The system on which you are installing the adapter must meet the following installation prerequisites: Solaris 10 on SPARC processors running VCS 4.1 or MB of free RAM Supported operating systems: Table 23. Supported operating systems for the VCS adapter Operating System Solaris 10 (64 bit) Sun SPARC x Note: Make sure that the ersion of your adapter is not higher than the ersion of System Automation Application Manager. Automating the VCS adapter If the VCS cluster consists of more than one node, the VCS adapter must be automated. It is required to automate the VCS adapter, if the VCS cluster consists of more than one node, 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 175. Behaior of the VCS adapter for Solaris/SPARC To make sure your system runs well using an VCS adapter, more information is proided to better understand the behaior of the VCS adapter in combination with System Automation Application Manager. Before you install and use the VCS adapter, make sure to be familiar with the behaior of the VCS adapter for Solaris/SPARC: VCS Global (Remote) clusters are not supported. VCS Global Serice Groups are not supported. VCS clusters are not request- but command-drien. Commands for bringing resources and groups online or offline are performed but not retained as persistent goals. No list of preiously issued commands is aailable, and commands that were preiously issued against a group or resource cannot be canceled. The latest command that was issued against a group or resource determines whether it should be online or offline. Commands issued by operators hae the same priority as commands issued by the end-to-end automation manager. Chapter 1. Planning 33

52 VCS resources and groups can be suspended from automation by an end-to-end automation operator. VCS groups hae no "real" desired state. VCS performs online and offline commands on VCS groups by propagating them to member resources. VCS groups only act as containers and reflect the state of the contained VCS resources. If some of the VCS resources in a group were brought online and others offline, the group is in a mixed state - it is not clear whether the desired state of the group is online or offline. VCS clusters do not hae a policy concept as known by end-to-end automation. This is why the Policy Information page for VCS domains does not show reasonable information. Planning for an end-to-end automation policy Before you define your own end-to-end automation policy, check the examples and identify cluster-spanning dependencies. The scope of end-to-end automation policies End-to-end automation management ersus first-leel automation. Find out, when to use which concept. As described in Tioli System Automation Application Manager, Administrator s and User s Guide, end-to-end automation management is not intended to take oer the role of first-leel automation products. The main focus of first-leel automation products is to ensure high aailability of applications within a cluster of systems. This task must remain as close as possible to the resources for which high aailability is to be ensured. The scope of end-to-end automation policies starts where local first-leel automation capabilities end - on the border of a first-leel automation cluster. Consequently, end-to-end automation policies should only define cluster-spanning relationships and groups. The following examples proide some information on what you must consider when defining resource references for first-leel automation resources. Example 1 Example 2 Example 3 Ref 1 Ref 2 Ref 3 Grp A Grp B Res X Grp A Grp B Res X Grp A Grp B Res X Figure 3. Examples for resource references to resources and resource groups. The examples show three resource references that were created for resources or resource groups that are hosted by a first-leel-automation domain. These examples are described in the following topics. 34 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

53 Example 1 This example illustrates why it is not desirable to create resource references pointing to resources that are members of first-leel automation groups if the integrity of first-leel automation is to be ensured. For this scenario, assume that: Resource reference "Ref 1" references an actual resource which is a member of the first-leel automation domain group "Grp A". In the end-to-end automation policy, the desired state Online is defined for resource reference "Ref 1". In the first-leel automation policy, the desired state Offline is defined for both "Grp A" and "Grp B". When the end-to-end automation policy is actiated, the end-to-end automation manager issues an Online request against the first-leel automation resource that is referenced by "Ref 1". The first-leel automation manager receies the request. If the referenced resource is offline, it will try to start the application. If the referenced resource is started due to the request from the end-to-end automation manager, the obsered state of "Grp A" changes accordingly. "Grp A" has been defined to be offline. This goal cannot be accomplished by the first-leel automation manager because the request on the group member has a higher priority and will be fulfilled. As a result, the compound state of "Grp A" changes, indicating that a problem has occurred. The same is true for "Grp B". An additional problem occurs because of the dependency between "Grp A" and the first-leel automation resource "Res X". The administrator who created the first-leel automation policy may hae assumed that the relationship to "Res X" would always be ealuated before a member of "Grp A" is started. In such a scenario, howeer, this is not the case and the dependency will not be honored. Example 2 In example 2, resource reference "Ref 2" refers to "Grp A" which is hosted by the same first-leel automation domain. This has the following two adantages oer the constructs in Example 1: 1. All members of "Grp A" will be started or stopped in accordance with the desired group behaior. After the completion of the request from the end-to-end automation manager, "Grp A" changes to a normal end state and no problem will be indicated on the operations console. 2. The relationship to "Res X" will be ealuated when the request is send to "Grp A". This ensures that all required actions will be performed by the first-leel automation manager as defined by the administrator of the policy. Only one problem remains: First-leel automation cannot reach the desired state defined in the policy for "Grp B". Howeer, in certain circumstances, referencing "Grp A" may reflect the desired behaior within in the scope of end-to-end automation. In such a case, the operator must understand that "Grp B" is in a problem state because end-to-end automation needed to start a member of this group in order to accomplish an end-to-end business goal. Example 3 The two examples aboe cause undesired behaior. This is not the case in this scenario, where "Ref 3" references the outermost (or top-leel) resource group defined in the first-leel automation policy. Chapter 1. Planning 35

54 In this scenario, "Ref 3" references the outermost (or top-leel) resource group defined in the first-leel automation policy. No matter what desired state has been defined for "Ref 3", the first-leel automation manager will act according to the request it receies from the end-to-end automation manager and all of the constructs defined in the first-leel automation policy will remain in a satisfactory state. Identifying cluster-spanning dependencies Identify first-leel automation resources that hae cluster-spanning relationships. Such resources are candidates for being referenced in the end-to-end automation policy. Two kinds of dependencies can be expressed in the constructs of an end-to-end automation policy: 1. Grouping concept: defines the general structure of resources and resource groups 2. Relationship concept: represents runtime dependencies between resources and resource groups The following topics describe how you can find groups and relationships among automated resources that are hosted by different first-leel automation domains. Grouping of resources An enterprise application consists of multiple resources (for example applications and IP addresses) that can belong to different business tiers and areas of responsibility. In order to automate resources effectiely, the grouping concept is introduced in end-to-end and first-leel automation. Resources need to be restructured from a technical and organizational point of iew. Decisions to make: Which of the resources that are automated by different first-leel automation domains need to be aailable at the same time? Consider these resources to be grouped in collection groups. Which of the resources that are automated by different first-leel automation domains can act as alternaties for other resources in case these fail? Consider these resources to become members of choice groups. Which resources should be grouped together to ensure that their state can be easily monitored? For example, a group could comprise all resources that will be monitored by the same operator een if the resources are hosted by different first-leel automation domains. These resources can also be grouped in collection groups, howeer this also implies that these resources are started and stopped together and hae the same desired state. Organizing resources in groups has the following benefits: Groups are logical containers that can be controlled as one logical instance. Groups organize the automated resources in a hierarchical structure. A group can be composed of resource references and other end-to-end automation groups. The possibility of nesting groups allows you to structure complex enironments into seeral layers. By encapsulating resources and nested groups within groups, you can organize your automated resources in a hierarchical structure that seres as the logical basis for an end-to-end automation policy. 36 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

55 Resources can be gathered in groups according to logical, technical, security, or responsibility criteria. For example: A resource group can be made up of resource references that reference all resources in an SAP enironment A group can include all resources that hae the same owner Figure 4. Example for end-to-end automation groups that are distributed oer different platforms End-to-end automation groups can be platform-spanning. This means that resource references for resources that are hosted by different first-leel domains can be gathered in one group. The resource references that refer to a DB2 group on a first-leel z/os sysplex can be gathered in a group together with the application "App", which is physically hosted on an AIX cluster. Relationships Relationships represent dependencies between resources or groups. A relationship exists between a source and a target. Source and target can be either resource references or groups. For example, a relationship A StartAfter B ensures that resource A can only start when resource B is online. Decisions to make: Which automated resource on a specific first-leel automation domain needs which other resource on another automation domain in order to run? What are typical tasks for an operator to start or stop applications in order to start or stop some solution? Are workflow documents aailable which describe the sequence in which applications need to be started or stopped? How does an operator apply maintenance to specific applications? Are documents aailable that describe in which sequence an operator must shut down applications? In case of an unexpected failure of some critical applications on a first-leel automation domain, do other applications on other automation domains need to be stopped as well? Chapter 1. Planning 37

56 Default directories Before you define a policy, you need to identify the relationships between the resources. When you identify the relationships that need to be defined in the policy, you should list the relationship information in the following sequence: Source resource First-leel automation domain name Target resource First-leel automation domain name Relationship type The following example describes when a ForcedDownBy relationship between two resources is required. Resource A and Resource B hae the following states: Resource A has the default desired state Online. Resource B has the default desired state Offline. You need to define a ForcedDownBy relationship between source resource Resource A and target resource Resource B (Resource A ForcedDownBy Resource B) if you want to achiee the following behaior: Wheneer Resource B is started, for example, due to an operator request, this should not hae any effect on Resource A. Wheneer Resource B was online and is stopping, for example, after it was started due to an operator's Online request and the request is canceled, or when Resource B fails while it is offline, Resource A must be bounced, that is, it has to be stopped and restarted again, for example, to allow Resource A to synchronize with Resource B. During the installation, default directories are used to install System Automation Application Manager. Default directories are defined in ariables. Check out all used ariables and their related default directory. 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 24. Default directories Variable used in this guide <EEZ_CONFIG_ROOT> <EEZ_INSTALL_ROOT> <hacmp_adapter_install_root> <hacmp_adapter_conf_root> <mscs_adapter_install_root> Default path /etc/opt/ibm/tsamp/eez/cfg /opt/ibm/tsamp/eez The configuration properties files are located in the directory <EEZ_CONFIG_ROOT>. AIX: /opt/ibm/tsamp/eez/hac AIX: /etc/opt/ibm/tsamp/eez/hac/cfg Windows: C:\Program Files\IBM\tsamp\eez\mscs 38 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

57 Table 24. Default directories (continued) Variable used in this guide Default path <mscs_adapter_conf_root> Windows: C:\Program Files\IBM\tsamp\eez\mscs\cfg <Tioli_Common_Directory> /ar/ibm/tioli/common <was_root> <cs_adapter_install_root> <cs_adapter_conf_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 /etc/ibm/tioli/common/cfg. AIX: /usr/ibm/websphere/appserer Linux: /opt/ibm/websphere/appserer Solaris: /opt/ibm/tsamp/eez/cs Solaris: /etc/opt/ibm/tsamp/eez/cs/cfg Disaster recoery policy definition worksheets Print out and use these worksheets to collect the information required for creating a disaster recoery policy. If you need to define more cluster sets, hardware boxes, slots, or nodes print out more copies of the appropriate worksheet. Table 25. Worksheet to define disaster recoery topology Site 1 Index 1 Name Site 2 Index 2 Name Cluster set Cluster set Cluster set Cluster set ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup ClusterSetName Domain Name Site 1 Domain Name Site 2 Chapter 1. Planning 39

58 Table 25. Worksheet to define disaster recoery topology (continued) Cluster set ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup Cluster set ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup Cluster set ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup Cluster set ClusterSetName Domain Name Site 1 Domain Name Site 2 WorkloadSetup Table 26. Worksheet to define disaster recoery hardware. Reuse this table for each site. Name of Site1 / Site2: Hardware Box Hardware Box Name Slot 1 Slot 2 Slot 3 Slot 4 SNMPAgent (If mechanism="snmp") Name Name PowerOff mechanism PowerOn mechanism Name PowerOff mechanism PowerOn mechanism Name PowerOff mechanism PowerOn mechanism Name PowerOff mechanism PowerOn mechanism Host Port AuthProtocol PriProtocol SericeProcessorType Script / SNMP Script / SNMP Script / SNMP Script / SNMP Script / SNMP Script / SNMP Script / SNMP Script / SNMP MD5 / SHA / None DES / AES / None MM 40 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

59 Table 26. Worksheet to define disaster recoery hardware (continued). Reuse this table for each site. Name of Site1 / Site2: Node Node Node Node Node Slot 1 Name PowerOff mechanism Script / SNMP PowerOn mechanism Script / SNMP Slot 2 Name PowerOff mechanism Script / SNMP PowerOn mechanism Script / SNMP Slot 3 Name PowerOff mechanism Script / SNMP PowerOn mechanism Script / SNMP Slot 4 Name PowerOff mechanism Script / SNMP PowerOn mechanism Script / SNMP SNMPAgent (If mechanism="snmp") Host Port AuthProtocol MD5 / SHA / None PriProtocol DES / AES / None SericeProcessorType MM Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Chapter 1. Planning 41

60 Table 26. Worksheet to define disaster recoery hardware (continued). Reuse this table for each site. Name of Site1 / Site2: Node Name Site index 1/2 Domain name Class SYS / IBM.HacmpNode / IBM.PeerNode / VCS.System / MSCS.Node HardwareDeice Box Slot Table 27. Worksheet to define disaster recoery workload Business-critical workload: Resource name Cluster set name Discretionary workload: Resource name Cluster set name Site index Business-critical workload must be able to run on either site in a cluster set, so you do not need to collect an associated domain name with this worksheet. 42 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

61 Chapter 2. Installing Installing System Automation Application Manager inoles preparation to ensure that your system meets the prerequisite requirements, then installing the required software. 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 the required middleware software for each system, refer to Middleware software requirements on page 8. Contents of the middleware software DVDs The middleware software DVDs that are shipped with the System Automation Application Manager product DVDs contain the following software products: IBM DB2 Enterprise Serer Edition Restricted ersion 10.1 IBM WebSphere Application Serer Base ersion Note: 1. IBM Tioli System Automation Application Manager only supports the 32-bit ersion of WebSphere Application Serer. 2. Websphere Application Serer ersion 8.5 Network Deployment is not supported. 3. Note that the IBM Tioli Directory Serer is not contained on the middleware software DVDs. IBM Jazz for Serice Management ersion 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 - Quick Beginnings for DB2 Serers (GC ) IBM DB2 - Release Notes - Version 10 The latest ersions of these publications are aailable on the IBM DB2 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 Copyright IBM Corp. 2006,

62 The DB2 release notes can also be found on the DVD labeled IBM DB2 Database for Linux, UNIX, and Windows Version 10.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. The DB2 Setup wizard is on the DVD labeled IBM DB2 Database for Linux, UNIX, and Windows ersion 10.1 for your platform. You can use the typical installation of a single-partition database enironment. On Windows, you may consider to set the startup type of the DB2 serice to Automatic. On a Windows system, the following users must be local users: DB2 administration serer user Fenced user Instance owner user 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 8) On a 64-bit operating system, the following link must exist in the home directory of the DB2 instance owner: /home/<db2 instance name>/sqllib/lib64/libdb2tsa.so If this link does not exist, use the following command to create the link: ln -s /home/<db2 instance name>/sqllib/lib64/libdb2tsa.so.1 /home/<db2 instance name>/sqllib/lib64/libdb2tsa.so Make a note of the following information for future reference: Host name of the system where the DB2 serer is installed. 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. Name of the directory to which the DB2 serer is installed if a local DB2 setup is used. 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: For information about DB2 ersion 10.1 serer security concepts and on how to authorize users to perform certain tasks, go to infocenter/db2luw/10r1/index.jsp. JDBC drier installation for a remote DB2 setup Depending on which operating system the remote DB2 is installed, you need the following files: DB2 for Linux, AIX, and Windows: db2jcc.jar 44 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

63 db2jcc_license_cu.jar: License file for DB2 for Linux, AIX, and Windows You can find these files in the <DB2_install_home>/sqllib/jaa directory. DB2 for z/os db2jcc.jar db2jcc_license_cisuz.jar: License file for DB2 for z/os You can find these files in the subdirectory classes or jcc/classes of the DB2 JDBC installation directory in the HFS. Note: The IBM DB2 drier for JDBC and SQLJ needs to be installed separately, after you hae installed DB2 for z/os. You hae the following options to install the JDBC drier: Create a new folder. Copy the files listed aboe into this folder. Point the installer to the directory as described in Using the installation wizard on page 50. Use the WebSphere JDBC drier: Copy the appropriate.jar files into the directory <was_home>/uniersaldrier/lib, if not already aailable. Point the installer to the directory as described in Using the installation wizard on page 50. Use the DB2 runtime client JDBC drier: Point the installer to the directory with the appropriate.jar files as described in Using the installation wizard on page 50. Preinstallation tasks for a remote DB2 setup The following tasks must be completed on the DB2 serer system: 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, install a JDBC drier. The DVD System Automation Application Manager ersion 4.1 for your platform contains scripts for creating the required databases and tables. Creating the automation manager database and the database tables: 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 DVD labeled System Automation Application Manager ersion 4.1, change the directory to DDL\Script 3. From this directory, run the following batch files: db2_create_automgr_db.bat <db_name> <instance_owner> <instance_pw> db2_create_reporting_tables.bat <db_name> <instance_owner> <instance_pw> <script_directory> where Chapter 2. Installing 45

64 <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 <script_directory> is the directory where the DB2 scripts for Tioli System Automation are located on the DVD, which you changed to in step 2 (DDL\Script) AIX or Linux: Perform the following steps if your DB2 serer runs under Linux or AIX: 1. Log in as root. 2. On the DVD labeled System Automation Application Manager ersion 4.1 for your operating system, change the directory to DDL/Script. 3. From this directory, run the following shell scripts: z/os 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) <instance_pwd> is the password of the instance owner user ID <script_directory> is the directory where the DB2 scripts for Tioli System Automation are located on the DVD, which you changed to in step 2 (DDL/Script) If you hae a DB2 serer system that runs on z/os, adjust and run the following jobs. They are proided on the DVD labeled System Automation Application Manager ersion 4.1 for your operating system, in directory DDL/DB2. ATVED100 This job creates a DB2 table space, tables, and index entries. ATVED10C This job deletes the objects created by job ATVED100. Follow the instructions within the jobs to adjust them to your enironment. Note: 1. Make sure that DB2 is actie before submitting the jobs. 2. Before rerunning job ATVED100 run job ATVED10C to cleanup the table space and tables defined by the preious run. 46 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

65 3. The user ID under which these jobs are submitted must hae DB2 SYSADM authority. 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 45, issue the following commands to erify that the remote database was created correctly: 1. Log on as DB2 instance owner. 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 28. Database tables EEZAUTOMATIONACCESS EEZAUTOMATIONRELATION EEZCOMMONEVENTS EEZDOMAINSUBSCRIPTION EEZOPERATORDOMAINFILTER EEZOPERATORDOMAINPREFERENCES EEZOPERATORHIDDENDOMAIN EEZPERSISTENTREQUEST EEZRESOURCESUBSCRIPTION EEZSAFOSEVENTS Installing Jazz for Serice Management Before you install or update Jazz for Serice Management, refer to the technotes for Jazz for Serice Management. Technotes proide information about late-breaking issues, limitations, and workarounds. Check technotes referring to issues in Jazz for Serice Management ersion : Jazz for Serice Management technotes Jazz for Serice Management installation Follow the steps described in this topic to install Jazz for Serice Management. To install Jazz for Serice Management ersion 1.1 and WebSphere Application Serer ersion , proceed as follows: 1. Create a common directory to store the extracted Jazz for Serice Management installation media, referred to as the JazzSM_Image_Home/directory. Restriction: Ensure that the path to the common root directory does not contain any spaces or special characters. 2. Extract the contents of the following delierable into this directory: Jazz for Serice Management ersion 1.1 including Installation Manager: AIX: JSM_1.1_LAUNCHPAD_FOR_AIX.zip Linux: JSM_1.1_LAUNCHPAD_FOR_LINUX.zip Chapter 2. Installing 47

66 Linux on System z: JSM_1.1_LAUNCHPAD_FOR_LINUX_Z.zip WebSphere Application Serer ersion : AIX: WAS_V _FOR_JAZZSM_AIX_ML.zip Linux: WAS_V _FOR_JAZZSM_LINUX_ML.zip Linux on System z: WAS_V _FOR_JAZZSM_LINUX_Z_ML.zip 3. Install Jazz SM Serices using Installation Manager: a. Browse to the JazzSM_Image_Home/im.platform_name/ directory and run the install command, for example:./install b. The Installation Manager window opens. Select the following packages to be installed: 1) IBM Installation Manager Version ) IBM WebSphere Application Serer Version ) IBM WebSphere SDK Jaa Technology Edition Version ) Jazz for Serice Management extension for IBM WebSphere 8.5 Version 1.1 5) IBM Dashboard Application Serices Hub Version 3.1 c. Click Next. The Installation Manager > Licenses panel opens. Reiew and accept the License Agreements. d. Click Next and specify the directories used by the Installation Manager. e. Click Next and specify the installation directories for WebSphere Application Serer and Jazz for Serice Management. f. Click Next. The Installation Manager > Features languages panel opens. g. Accept the default translated languages that are selected in the Translations Supported by All Packages panel. Click Next. The Installation Manager > Features panel opens. h. On the Features panel, expand IBM WebSphere Application Serer > IBM WebSphere SDK for Jaa Technology Edition 6 and select IBM 32-bit WebSphere SDK for Jaa. i. Click Next and specify the configuration for your WebSphere Application Serer installation. Here you define the WebSphere administratie user ID. j. Click Next. The Installation Manager > Summary panel opens. k. Reiew the software packages to be installed and their installation directories. Click Install to start the installation. l. When the installation has successfully completed, a success panel is displayed. You can now click Finish to close the Installation Manager. 4. Install Jazz for Serice Management fix pack ersion : a. Extract the contents of the following package into a temporary directory referred to as the JazzSM_FP_Home directory: TIV-JazzSM-multi-FP002.zip b. Start the Installation Manager. Naigate to the installation directory of Installation Manager and run the command IBMIM, for example: /opt/ibm/installationmanager/eclipse/ibmim c. Set up the fix pack repository preference. 1) Select File > Preferences. 2) In the Preferences > Repositories panel, click Add Repository. 3) Click Browse and browse to the following location and file: JazzSM_FP_Home/JazzSMFPRepository/disk1/diskTag.inf 48 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

67 4) Click OK. Note: It is also recommended to deselect the check box Search serice repositories during installation and updates, if you do not hae Internet connectiity from your target system. d. Click OK to close the Preferences > Repositories panel. e. On the Installation Manager home page, click Update. The Installation Manager > Update Packages window opens. f. Select the following package: Core serices in Jazz for Serice Management. Click Next. g. Ensure that the following component is selected for update: IBM Dashboard Application Serices Hub ersion Click Next. The Update Packages > Licenses panel opens. h. Accept the license agreement and click Next. The Update Packages > Features panel opens. i. Click Next. j. Specify your WebSphere administrator user ID and password and click Validate... to alidate your credentials. Then click Next. k. On the Summary panel click Update to start the installation of the Dashboard Application Serices Hub fix pack. The update takes approximately 30 minutes. l. After the installation a success panel is displayed. Click Finish to close the Installation Manager. 5. Important: Actiate the 32-bit ersion of Jaa 7 for the WebSphere Application Serer profile:./managesdk.sh -enableprofile -sdkname 1.7_32 -profilename JazzSMProfile -enableserers JazzSMProfile is the profile name used for Jazz for Serice Management. Default name: JazzSMProfile. Note: More information about configuring Jaa 7 is proided at the following links: Find out how to install and configure Jaa 7 at the IBM Education Assistant -WebSphere software. Check the Jaa SDK Upgrade Policy for the IBM WebSphere Application Serer before applying fixes to WebSphere Application Serer, in order to ensure that the fix matches to the installed Jaa ersion. The page Verify Jaa SDK ersion shipped with IBM WebSphere Application Serer fix packs describes which ersion of WebSphere Application Serer corresponds to which Jaa SDK leel. You are now ready to install System Automation Application Manager using its own installer. Post-installation tasks for Jazz for Serice Management Jazz for Serice Management defines default alues for the time interals within the browser polls for new content. These default alues are higher than the alues that are required by System Automation to ensure timely isualization when an automation resource changes its state. During initial installation of System Automation Application Manager, the timeout alues are adjusted automatically. But when serice for Jazz for Serice Management is installed afterwards, the original default alues are restored. Chapter 2. Installing 49

68 Perform the following steps after installing serice for Jazz for Serice Management: 1. Open file /opt/ibm/jazzsm/ui/properties/actiemqbroker.properties. 2. Ensure that each of the following properties are set to 5 seconds: ActieMQBroker.timeout=5 ActieMQBroker.pollDelay=5 ActieMQBroker.pollErrorDelay=5 3. Sae the file and restart WebSphere Application Serer. Installing System Automation Application Manager If you finalized your planning steps to install System Automation Application Manager, start with the installation. You hae 2 options to install. You can either use the wizard or install in silent mode. Using the installation wizard This topic describes how to install System Automation Application Manager. For the installation, you use a graphical installation program, the installation wizard. The required steps are described in the following paragraphs. 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. If the graphical installation program cannot be started, the installer automatically switches to console mode. The console mode is not supported, and can't be used for the installation of the product. If the console mode is started, please check whether all required libraries are installed on the machine, as documented in Installing prerequisites on page 4. On the panels of the installation wizard, enter the data you collected using the lists proided in Collecting the information on page 12. Make sure that you specify all required parameters on the installation wizard panels and that your entries are correct. Note: 1. The wizard panels that are displayed during the installation are similar on different operating systems. Make sure to enter platform-specific information when specifying directory locations and file names. 2. In this topic, only those panels are depicted on which user actions are required. 3. The installation comprises these phases: a. In the preinstallation phase, you specify the installation parameters. b. The installation phase begins when you click the Install button on the last preinstallation 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: 50 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

69 1. Make sure that all installation prerequisites are met (refer to Installing prerequisites on page 4). 2. Insert the following DVD into the DVD drie: System Automation Application Manager <platform> There are multiple DVDs. 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 Start the installation by launching the installation wizard using setup.bin. For more information about how to install in silent mode, see Installing in silent mode on page 55 When the installer unpacks its contents, the initial wizard window is displayed: Figure 5. Installation wizard: Select your language 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 locale setting. 6. The next panel displayed is the "Introduction" panel. On this panel, you can see the aailable installation options: perform an initial installation, resume a canceled or failed installation, or perform an update installation. Read the information on this panel and click Next to proceed. 7. The Software License Agreement panel is displayed. 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. To accept the terms of the license agreement, select I accept both the IBM and the non-ibm terms and click Next. 8. On the Installation Directory panel, specify the directory where you want to install System Automation Application Manager or accept the default location. Click Next. 9. If the installation program detects a Tioli Common Directory on your system, for example, because a Tioli product is already installed, the directory must Chapter 2. Installing 51

70 also be used for System Automation Application Manager. In this case, the Tioli Common Directory panel is not displayed. If the installation program does 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. 10. On the High Aailability panel, select the high aailability setup that you require. Click I want to install on a single serer (not highly aailable) if you do not want a high aailability scenario. The steps that follow determine the changes that are made to the end-to-end automation manager. The option Yes is automatically selected. Click I want to create a highly aailable SAAM setup with two or more serers if you want a high aailability scenario. No changes are made to the end-to-end automation manager database and the WebSphere Application Serer is not started after the installation. Choose Yes if you hae no database already installed on the cluster that is used by another system. Choose No if you hae a database installed on the cluster that is used by another system. Click Next. 11. On the Database Serer panel, select the DB2 setup type you are using and click Next. Which panel is displayed next, depends on the type of DB2 setup you selected: Local DB2 setup: Proceed with step 12. Remote DB2 setup: Proceed with step 13 on page 53. Remote DB2 on z/os setup: Proceed with step 14 on page The "IBM DB2 on local system" panel is displayed only if you are using a local DB2 setup. a. Specify the database name or accept the default name and click Next. Note that any existing database with the name you specify is dropped automatically without warning b. Specify the installation directory of your local DB2 installation and the name and password of the DB2 Instance owner, and then click Next. c. 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 is displayed. DB2 port numbers often differ from the default, depending on the DB2 setup that you configured. Ensure that your setting is correct before you proceed. Click Next and proceed with step 15 on page 53. 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. Continue with 15 on page Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

71 13. The "IBM DB2 Database on remote system" panel is displayed only if you are using a remote DB2 setup. a. Specify the database name (see Preinstallation tasks for a remote DB2 setup on page 45) and click Next b. Specify the path to the DB2 JDBC drier or click Choose to select the directory (see JDBC drier installation for a remote DB2 setup on page 44 and Preinstallation tasks for a remote DB2 setup on page 45), and specify the name and password of the database instance owner. Click Next. Note: The installation wizard checks the contents of the defined directory and displays an error message if it does not contain a JDBC drier with a alid license c. In the field DB2 serer host name, type the fully qualified host name of the system where the DB2 serer is installed. In the field DB2 serer port, the port number of the DB2 serer must be specified. Enter port number of your DB2 on z/os database. To skip the access test, select the Skip DB2 access check box. Click Next. 14. The "IBM DB2 Database on remote system on z/os" panel is displayed only if you are using a remote DB2 on z/os setup. a. Enter the location information of the database that runs on z/os and the schema name of the database. Click Next b. Specify the path to the DB2 JDBC drier or click Choose to select the directory, and specify the name and password of the database instance owner. Click Next c. In the DB2 serer host name field, type the fully qualified host name of the system where the DB2 serer is installed. In the DB2 serer port field, specify the port number of the DB2 serer. Enter port number On the "User and Group Administration" panel, specify whether your WebSphere has administratie access to users and groups. Typically, this is the case in setups with federated user repositories where you can manage users and groups ia the WebSphere administratie console. Click No if you are using a standalone external repository (such as LDAP) and cannot access the users and groups settings within the WebSphere administratie console. In this case, the installer does not make any changes to users and groups: they need to be set up manually before the installation, as described in the WebSphere documentation. For more information, refer to your WebSphere administrator. 16. The installation directory of WebSphere Application Serer is detected on your system and displayed on the WebSphere Application Serer panel. a. Click Next. b. Specify a WebSphere Application Serer administratie account and password. You can also choose another serer. Select the profile you want to use and click Next. 17. On the Automation Domain Name panel, 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. Chapter 2. Installing 53

72 You can change the settings once your are done with the installation. For more information, see Domain tab on page If you want to use Tioli Netcool/OMNIbus to display end-to-end automation management eents: Select Enable EIF eent forwarding to OMNIbus In the Host Name field, specify the host name of the OMNIbus Probe for Tioli EIF. In the Port Number field, specify the port number of the OMNIbus Probe for Tioli EIF. The default port number is 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. 19. If System Automation Application Manager Distributed Disaster Recoery with GDPS is supported on this platform, the GDPS panel is displayed. 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 modify the GDPS connection after the installation of System Automation Application Manager is completed. For more information, refer to Configuring the destination for GDPS eents on page On the "System Automation Functional user ID" panel, specify the functional user ID and password for the end-to-end automation manager. Do not use cut and paste to enter the password and the password confirmation. Type in directly the password and the password confirmation. This functional user ID is needed for seeral purposes: The end-to-end automation engine uses the credentials to access the J2EE framework that runs on the WebSphere Application Serer. The J2EE framework uses the credentials to access JMS, as defined in the WebSphere Application Serer JAAS authentication alias EEZJMSAuthAlias. The J2EE framework uses the credentials for all asynchronous internal work that is associated with the EEZAsync role, as defined in the EEZEAR application's User RunAs role mapping. Note: Do not choose the same name for both the System Automation functional user ID and the WebSphere Application Serer administrator user 54 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

73 ID, as this may lead to problems if you later uninstall System Automation Application Manager. For example, do not specify wasadmin for both users. 21. On the "System Automation Administration user ID " panel, specify the user ID and password of the System Automation administrator. Click Next. 22. When you specified all the required information on the wizard panels, the Pre-Install Summary panel is displayed. The installer checks for disk aailability. If the disk space requirements are not met, installation is not possible. Click Install to start the installation. The installation can take up to two hours to complete. 23. While the component is being installed and configured, information panels display the progress. 24. When the installation of System Automation Application Manager is complete, the Installation Complete panel is displayed. Click Done to close the installation wizard. For information about erifying the installation, refer to Verifying the installation on page 62. Installing in silent mode You can install System Automation Application Manager Version using a graphical interface (Installation Shield wizard) or in silent mode. The silent installation is run by using a preiously created silent input properties file. You can generate the install.properties input file in two ways: 1. Run a wizard-based graphical installation using setup.bin or setup.exe with the -Dpreparesilent=true option. When the installation procedure completes, the install.properties file is created in the <EEZ_INSTALL_ROOT>/install subdirectory of the product installation path. When an update installation is performed, the file is read to obtain the parameters and alues needed for the update process. If this file is not found, the update installation fails. If you want to perform a silent installation of System Automation Application Manager on more than one system, you can take the install.properties file which was generated during a graphical installation, and use it on other systems of the same type. You might need to replace system-specific parameters in the file to customize it for the target system. 2. You can prepare an install.properties file without performing a complete installation on the target system. The first part of the installation procedure gathers all the necessary parameters needed to generate the install.properties file. You do this by starting the graphical installer on the target system with the options -Dpreparesilent=true and -Dpropertiesfileonly=true. With these options, the installation procedure stops before the product files are copied to the product directory. The install.properties file is created and stored in directory /tmp. If you want the file to be created in a specific path, you can optionally specify -Dpropertiesfilepath=<fully_qualified_path>. If the specified path is incorrect, the file is saed in the default temporary directory on the system. For example, if you want the file to be saed to /ar/mydir, use the following command: setup.exe -Dpreparesilent=true -Dpropertiesfileonly=true -Dpropertiesfilepath=/ar/mydir Chapter 2. Installing 55

74 Note: The option -Dpropertiesfilepath=<fully_qualified_path> can be used only if -Dpreparesilent=true and -Dpropertiesfileonly=true are also specified. You can use the install.properties file for a silent installation only if the -Dpreparesilent=true option is specified. To run a silent installation, perform these steps: 1. Copy the input properties file install.properties to the system on which you want to perform the silent installation. 2. Edit the install.properties file and make sure that it contains all your system-specific parameters, such as host names, directories, and so on. Password parameters in the install.properties file do not contain any alues. You must add the passwords manually to the file, or else the installation fails. 3. To start the installation, enter the following command depending on the platform you use: setup.bin -f <fully_qualified_properties_file_name> If the input file install.properties is found, silent installation starts. If the file is not found, the wizard-drien installation starts. Upgrading to release 4.1 To upgrade from any preious ersion to ersion 4.1, proceed as follows: 1. Export your data. For more information, see Exporting the content of the automation database on page Store the customized user role mappings. For more information, refer to Storing the user role mappings for WebSphere application EEZEAR on page On AIX only: Run the slibclean command. For more information, refer to Upgrading on AIX on page If you are upgrading from release or 3.2.1, reiew the additional information in Upgrading from release or on page Uninstall any preious ersion of System Automation Application Manager. 6. If you are not using a local DB2 installation, upgrade the automation database: If you are upgrading from release or 3.2.1, reiew the additional information in Upgrading the automation database from ersion or on page Install the middleware software required by System Automation Application Manager ersion If high aailability is configured for System Automation Application Manager, perform the additional preinstallation steps described in Upgrading the high aailability policy on page Install System Automation Application Manager ersion If high aailability is configured for System Automation Application Manager, perform the additional postinstallation steps described in Upgrading the high aailability policy on page Import your data. For more information, see Exporting the content of the automation database on page 57. Once the preious ersion of System Automation Application Manager is uninstalled, all configuration files are presered in directory <EEZ_CONFIG_ROOT>, 56 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

75 for example /etc/opt/ibm/tsamp/eez/cfg. After ersion 4.1 is installed, System Automation Application Manager ersion 4.1 uses the configuration files saed in <EEZ_CONFIG_ROOT>. If you are using the cfgeezdmn configuration utility in silent mode to configure the application manager common settings, make sure that you generate a new silent input properties file on the new release leel. The application manager common settings are configured in silent mode by launching the cfgeezdmn utility using the options -s -e. Before performing any silent configuration, generate a new input properties file by launching the cfgeezdmn utility using the options -s-e[-g -gr ]. Exporting the content of the automation database If you decide to drop and recreate the automation database, use the scripts described in this topic. These scripts export the data from the automation database before you drop the database, and import them back into the automation database once it is recreated. In addition, future upgrades of System Automation Application Manager can require changes of the layout of tables contained in the automation database. In this scenario, export the data contained in the automation database prior to the upgrade, and import the data back into the automation database after the upgrade to preent data loss. System Automation Application Manager proides scripts that assist you to export and import data. These scripts are designed for local databases managed by DB2 for distributed platforms. If you hae a remote DB2 setup you must directly run these scripts on the system where the automation database resides. If you use DB2 for z/os, the scripts can not be used directly, but they can sere as a blueprint for your database administrators in order to create export and import procedures that are appropriate for your enironment. Export data To export the data, perform the following steps : 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 DVD and run the following script to export the data:./db2_export_automation_db.sh <db_name> <instance_owner> <instance_pwd> <export_to_dir> If you use a remote DB2 located on a Windows system, run the corresponding.bat file from the DDL/Script directory on that remote system: db2_export_automation_db.bat <db_name> <instance_owner> <instance_pwd> <export_to_dir> These are the required parameters: <db_name> - Name of the System Automation Application Manager 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. Chapter 2. Installing 57

76 3. Reiew the messages created by the script, including the messages contained in the export log file located in the "logs" subdirectory of the <export_to_dir> directory. For more information about how to import the content of the automation database, refer to Importing the content of the automation database on page 61. Note: 1. The export and import scripts are needed if an upgrade requires a change of the database layout. In this case, 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. It is not generally required to export and import the data when the System Automation Application Manager is upgraded. In most cases, changes of the automation database layout are performed without the need to drop and recreate the database tables. For more information, see Upgrading to release 4.1 on page The DB2 export utility that is used by the automation data export script creates seeral warning messages with message ID SQL3100W. This warning message can be ignored. For further information about this message, refer to the DB2 documentation. 3. For general information about the EXPORT and IMPORT commands proided by IBM DB2, refer to the DB2 documentation. Storing the user role mappings for WebSphere application EEZEAR Store the role mappings before you uninstall a preious ersion as part of the upgrade process to release 4.1, if the default role mappings for the user roles defined within the EEZEAR application are changed. You can retriee the role mappings using one of the following tools: WebSphere administratie console 1. Log on to the WebSphere administratie console as a WebSphere administrator. 2. Naigate to Applications > Enterprise Applications > EEZEAR > Security role to user/group mapping. 3. Take notes for all existing mappings. wsadmin scripting 1. Change to the /bin subdirectory of the WAS profile, e.g., /opt/ibm/websphere/appserer/profiles/appsr01/bin 2. On UNIX systems, enter../setupcmdline.sh On Windows systems, enter setupcmdline.bat 3. Enter the wsadmin command./wsadmin.sh -username <wasadmin_id> -password <wasadmin_pwd> -lang jython -c "jaa.lang.system.out.println(adminapp.iew( EEZEAR, [ -MapRolesToUsers ]))" 4. Take notes for all existing mappings, or redirect the output into a file. After installing release 4.1, log on to the WebSphere administratie console. 1. Naigate to the Security role to user/group mapping for EEZEAR. 2. Adjust the mappings to the alues that you noted in bullet 4 of the wsadmin scripting list aboe. 3. Sae the changes. 58 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

77 4. Restart the WebSphere application serer. Upgrading on AIX On AIX, execute the following command after the automation engine (eezdmn) has been stopped and before the installation is started: # /usr/sbin/slibclean Upgrading from release or This section describes what you must obsere when migrating from release or to release 4.1. To upgrade from release or to release 4.1 of System Automation Application Manager, uninstall release or and install release 4.1 as described in Upgrading to release 4.1 on page 56. Additional installation steps Before you uninstall release or as part of the upgrade process, consider the following questions: 1. Are you using the Agentless Adapter? Open the configuration utility using the cfgeezdmn command. If the Enable Agentless Adapter configuration check box on the configuration utility launchpad window is selected, you are using the Agentless Adapter. 2. Did you configure to use SSL for the communication with all first-leel automation domains? Click Configure for the Application Manager common configuration on the configuration utility launchpad window and select the Security tab. Check if the Enforce use of SSL for all first-leel automation domains check box is selected. Some modifications hae been introduced with release that hae to be considered when migrating from release or directly to release 4.1. If the answer to both questions is 'yes', perform the following migration steps after installing System Automation Application Manager ersion 4.1: Prior to release 4.1 of System Automation Application Manager, Agentless Adapter domains were not included when SSL was enforced for communication between the end-to-end automation manager and first-leel automation domains. Starting with release 4.1, this applies also for Agentless Adapter domains. In release 4.1, the configuration of the Agentless Adapter has been extended to configure also SSL for data transport between the automation manager and the adapter. You can either configure SSL or deselect the Enforce use of SSL for all first-leel automation domains check box in the Application Manager common configuration. Refer to Configuring System Automation Application Manager on page 96 for a description of the configuration utility. If you decide to configure SSL for data transport between the automation manager and the Agentless Adapter, see also Securing the connection to end-to-end adapters using SSL on page 260. Using remote Agentless Adapters Prior to System Automation Application Manager release there was only one Agentless Adapter that was installed on the Application Manager serer host. From Fix pack , and specifically release 3.2.2, introduces the remote Chapter 2. Installing 59

78 Agentless Adapters. The Agentless Adapter included with releases prior to System Automation Application Manager ersion is now referred to as the local Agentless Adapter. The SSL enforcement option mentioned in the preceding paragraphs applies to both the local Agentless Adapter and the new remote Agentless Adapters, but the migration action described in the preious topics applies only to the local Agentless Adapter. If you configure remote Agentless Adapters on a system with System Automation Application Manager ersion 4.1, you cannot distribute this configuration to a system where a remote Agentless Adapter of ersion is installed. You must upgrade the remote Agentless Adapter system to ersion 4.1 before you distribute the configuration. Upgrading the automation database from ersion or You must create a new database table EEZNODE in the automation database. Existing database tables are not affected. To create the new table, run the appropriate script for your enironment as described below: In a Windows enironment: In the <EEZ_INSTALL_ROOT>\install directory or in the DDL/Script directory on the product DVD, run: db2_run_sql.bat <db_name> <instance_owner> <instance_pwd> createnodetable.sql In a Unix enironment: In the <EEZ_INSTALL_ROOT>/install directory or in the DDL/Script directory on the product DVD, run: db2_run_sql.sh <db_name> <instance_owner> <instance_pwd> createnodetable.sql Note: The db2_run_sql script searches for the SQL file in the../db2 directory. If the automation database is located on a z/os serer, proceed as follows: Reiew ATVEM200, on how to create the EEZNODE table. Upgrading the high aailability policy If high aailability is configured for System Automation Application Manager, upgrade the automation policy. Perform the following steps: Preinstallation steps 1. Perform the update of the automation database as described in Upgrading the automation database from ersion or Exclude the node: samctrl -u a <node>. 3. Stop the first node in the cluster: stoprpnode <node>. Use the installation wizard to install System Automation Application Manager on this node. Make sure to specify that your are performing the installation in a high aailability scenario. Select No, all database installation steps hae been performed prior to this installation in order to preent any database access during the upgrade process. Postinstallation steps 60 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

79 1. Restart the node: startrpnode <node>. 2. Include the node: samctrl -u d <node>. 3. Run the configuration dialog cfgeezdmn on the upgraded node. 4. Verify the alues for configuring high aailability are correct. Sae your changed in case you had any. Click Define policy in order to upgrade the policy. Note: This does not affect any other resources defined in the end-to-end high aailability policy. Repeat this procedure for all other nodes. Importing the content of the automation database If you decide to drop and recreate the automation database, use the scripts described in this topic. These scripts export the data from the automation database before you drop the database, and import them back into the automation database once it is recreated. In addition, future upgrades of System Automation Application Manager can require changes of the layout of tables contained in the automation database. In this scenario, export the data contained in the automation database prior to the upgrade, and import the data back into the automation database after the upgrade to preent data loss. System Automation Application Manager proides scripts that assist you to export and import data. These scripts are designed for local databases managed by DB2 for distributed platforms. If you hae a remote DB2 setup you must directly run these scripts on the system where the automation database resides. If you use DB2 for z/os, the scripts can not be used directly, but they can sere as a blueprint for your database administrators in order to create export and import procedures that are appropriate for your enironment. For more information about how to export the content of the automation database, refer to Exporting the content of the automation database on page 57. Import data To import the data, perform the following steps: 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 DVD and run the following script to export the data:./db2_import_automation_db.sh <db_name> <instance_owner> <instance_pwd> <import_from_dir> If you use a remote DB2 located on a Windows system, run the corresponding.bat file from the DDL/Script directory on that remote system: db2_export_automation_db.bat <db_name> <instance_owner> <instance_pwd> <import_from_dir> These are the required parameters: <db_name> - Name of the System Automation Application Manager database. Typically, this is EAUTODB. <instance_owner> - Database instance owner userid. <instance_pwd> - Database instance owner password. <import_from_dir>- 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. Chapter 2. Installing 61

80 3. Reiew the messages created by the script, including the messages in that are contained in the import log file that is contained in the "logs" subdirectory of the <import_from_dir> directory. Note: 1. The export and import scripts are needed if an upgrade requires a change of the database layout. In this case, 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. It is not generally required to export and import the data when the System Automation Application Manager is upgraded. In most cases, changes of the automation database layout are performed without the need to drop and recreate the database tables. For more information, see Upgrading to release 4.1 on page The DB2 export utility that is used by the automation data export script creates seeral warning messages with message ID SQL3100W. This warning message can be ignored. For further information about this message, refer to the DB2 documentation. 3. For general information about the EXPORT and IMPORT commands proided by IBM DB2, refer to the DB2 documentation. Verifying the installation This topic describes the tasks you should complete in order to erify that the automation manager, automation engine, and operations console hae been installed successfully. Verifying the automation manager To erify that the automation manager was installed successfully, complete the tasks described in the following topics. Verifying 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: Procedure 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 28 on page 47 should be shown. Results 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. 62 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

81 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 28 on page 47 should be shown. Verifying the automation J2EE Framework: To erify that the automation J2EE framework was installed successfully on AIX or Linux: 1. In a Web browser window, specify the following address to display the Login panel of the Dashboard Application Serices Hub: The default IBM Dashboard Application Serices Hub 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. Verifying 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 the Dashboard Application Serices Hub: The default IBM Dashboard Application Serices Hub 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 Tioli System Automation Application Manager, Reference and Problem Determination Guide. Verifying the automation engine To erify that the automation engine was installed successfully, proceed as follows: 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 Tioli System Automation Application Manager, Reference and Problem Determination Guide. Chapter 2. Installing 63

82 Verifying 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 Dashboard Application Serices Hub: The default IBM Dashboard Application Serices Hub 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 the IBM Dashboard Application Serices Hub, click the entry for Tioli System Automation Application Manager. 4. When the Welcome page is displayed, click on System Automation Application Manager. 5. Select one of the Tioli System Automation dashboards. The installation is successful if the selected dashboard opens. 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 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 as described in 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 configuration dialog on page 89 describes how you launch the configuration dialog. For detailed information about the User credentials tab, refer to the online help of the configuration dialog. Modifying 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 Dashboard Application Serices Hub administrator user ID LTPA Timeout for forwarded credentials between serers is set to 1440 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 the Dashboard Application 64 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

83 Serices Hub 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. In the administratie console, select Security > Secure administration, applications, and infrastructure > Authentication mechanisms and expiration. Configuring the number of users 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 in the WebSphere administratie 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 operations console will display 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. Modifying aailable heap size After the installation of System Automation Application Manager, modify the heap size settings of the WebSphere Application Serer to the following recommended alues: Minimum heap size: 768 MB Maximum heap size: 1024 MB Perform the following steps to increase the JVM heap size: 1. Log on to the WebSphere administratie console. 2. Go to Serers > Application Serers > serer1 > Serer Infrastructure > Jaa and Process Management > Process Definition > Additional Properties > Jaa Virtual Machine. 3. Enter 1024 for the Maximum Heap Size and 768 for the Minimum Heap Size to aoid OutOfMemoryErrors. Refer to the WebSphere Application Serer online documentation for more information about how to determine the optimum alue for the maximum heap size, depending on the aailable physical memory. 4. Sae your changes. Restart WebSphere Application Serer for the changes to take effect. Upgrading from a Try and Buy ersion to a full product ersion If you hae installed the Try and Buy ersion of IBM Tioli System Automation Application Manager and decided to purchase the full product ersion, the you Chapter 2. Installing 65

84 will receie another copy of the installation media. The installation media contains the license file for the full license. The license file is located in the license subdirectory. Extract the license file from the installation medium and perform the license upgrade by issuing the following command: eezdmn -instcert <fully qualified license_file_name> After upgrading the license, check if any updates for IBM Tioli System Automation Application Manager are already aailable and install the latest serice leel. Uninstalling Use the uninstallation program to uninstall System Automation Application Manager. This topic describes how to uninstall System Automation Application Manager. An uninstallation program is proided that remoes the components that are installed by the installation wizard. Note: Uninstall System Automation Application Manager before uninstalling WebSphere Application Serer. Using the graphical uninstallation program Before you begin: During uninstallation, a number of panels are displayed, prompting you to confirm that specific files are to be deleted. Check the files carefully before confirming the deletion. If you changed the user repository settings of WebSphere Application Serer to an external user repository after the installation of System Automation Application Manager, the following change is required: Change the ariable EXTERNAL_USER_REP_ACTIVATE in file <EEZ_INSTALL_ROOT>/ uninstall/installariables.properties to false: EXTERNAL_USER_REP_ACTIVATE=false. This preents users and groups from being deleted in the WebSphere Application Manager in a subsequent uninstallation process. Perform the following steps to uninstall System Automation Application Manager: 1. Launch the uninstallation program by entering the following command in a shell: <EEZ_INSTALL_ROOT>/uninstall/uninstall This starts the uninstallation wizard. 2. Read the information on the first wizard panel and click Next. 3. Proide the requested information for the WebSphere Application Serer: WebSphere Application Serer Admin user ID and password WebSphere Application Serer - serer name WebSphere Application Serer profile name Click Next. 66 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

85 Installing fix packs 4. The Start Uninstallation panel is displayed. The preparations to uninstall System Automation Application Manager are complete. Click Uninstall to start the uninstallation. 5. Some information panels are displayed while the uninstallation program checks your system for the information needed for the uninstall. 6. When the uninstallation is complete, a summary window is displayed. To exit the installation program, click Done. 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, perform the following steps: a. On the error panel, click Sae installation log files. b. Click Next if you want to remoe all installed files. Otherwise, click Cancel to perform correctie actions and then rerun the uninstallation. Uninstallation in silent mode If you installed System Automation Application Manager in silent mode, the uninstallation must be silent too. The password parameter in the generated installariables.properties file in the uninstall subdirectory does not hae a corresponding alue. Before starting the uninstallation in silent mode, you must enter this password manually, otherwise the silent uninstallation fails. Perform the following steps: Procedure 1. Edit the installariables.properties file in the uninstall subdirectory. 2. Locate the password parameter by searching for WAS_ADMIN_PWD=, and specify the password. 3. To start the uninstallation, go to the uninstall subdirectory and issue the uninstall command. Installing serice means applying correctie serice fix packs to release 4.1 of IBM Tioli System Automation Application Manager or upgrading the software release leel from release 4.1. In this documentation, the serice fix packs that you use for updating System Automation Application Manager are referred to as product fix packs. Product fix packs and interim fixes are deliered as: Self-extracting archies for AIX Archies in TAR-format for Linux The serice installation process is also used to upgrade System Automation Application Manager from ersion or ersion to ersion The process described applies for this upgrade as well as for the installation of fix packs. Differences in the archie names are described where applicable. 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. Chapter 2. Installing 67

86 Obtaining fix packs Read the release notes to find out which fix packs are required for a release update. The fix packs are aailable on the IBM Tioli System Automation support page at: Tioli_System_Automation_Application_Manager Click Downloads to display all aailable fix packs. Click View all download links. Click Documentation to display the list of aailable documentation. Click Troubleshooting to find all related APARs. The archies can be downloaded from the IBM Tioli System Automation support site at: /IBMTioliSystemAutomationforLinux.html Archie naming conentions Use the DVDs and archies listed in Packaging on page 3 to upgrade IBM Tioli System Automation from ersion 3.2 to ersion Naming conention for product fix pack archies: TIV-SAAM-<platform>-FP<fix_pack_number>.<archie_type> where <platform> represents the platform on which System Automation Application Manager is installed <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 on Linux on System x platforms: TIV-SAAM-LinuxI386-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: EEZ41<mf><platform>/<platform>/<update_wizard_file> where <mf> represents modification leel and fix leel. For example, for fix pack , the directory is named EEZ4101. <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 System x archie for fix pack 1 for System Automation Application Manager 4.1 is unpacked: EEZ4101I386/i386/ 68 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

87 Usage instructions for the platform-specific archies These are the archies for applying serice to System Automation Application Manager. AIX Table 29. Archies for AIX platforms Archie name TIV-SAAM-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: EEZ32<mf>AIX/AIX/setup.bin TIV-SAAMW-AIX-FP<fix_pack_number>.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 30. Archies for Linux on System x Archie name TIV-SAAM-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: EEZ32<mf>I386/i386/setup.bin TIV-SAAMW-I386-FP<fix_pack_number>.tar 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 31. Archies for Linux on System z Archie name TIV-SAAM-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: EEZ32<mf>S390/s390/setup.bin TIV-SAAMW-S390-FP<fix_pack_number>.tar For information about installing WebSphere Application Serer interim fixes, refer to the release notes. Chapter 2. Installing 69

88 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. You must hae root authority. 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. Installing fix packs in a setup for high aailability If you made your installation of System Automation Application Manager highly aailable by using System Automation for Multiplatforms as described in Configuring high aailability on page 117, 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 2. Procedure 1. Exclude node 2, then stop node 2 within the System Automation for Multiplatforms domain using the command stoprpnode. It is important to stop the node and not just to exclude it. If you exclude node 2, the resources are still monitored. 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 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: 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 70 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

89 System Automation Application Manager on node 2 to connect to the remote database manager during update installation. 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 I want to create or update a highly aailable SA AM setup with two or more serers and No, all database installation steps hae been performed prior to this installation. 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. Then start node 2 using startrpnode and include node 2 again. 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 is 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 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 fix packs Installing for high aailability Uninstalling serice is only supported by uninstalling the complete System Automation Application Manager as described in Uninstalling on page 66, and reinstalling to the leel required. If you want to make System Automation Application Manager highly aailable using System Automation for Multiplatforms, you need to install System Automation Application Manager on an additional node. The following steps make sure that you keep your existing configuration and data, if you install System Automation Application Manager on an additional node. There are two scenarios: 1. You hae one existing node and you want to install System Automation Application Manager on the second additional node. Both nodes are located in a high aailability cluster with System Automation for Multiplatforms. 2. You hae two existing nodes in a high aailability System Automation for Multiplatforms cluster. You want to install System Automation Application Manager on one additional node. All three nodes are located in a high aailability cluster. To install System Automation Application Manager on an additional node, perform the following steps: Chapter 2. Installing 71

90 1. Install System Automation Application Manager V3.2.2 on the additional node. Make sure to select I want to create a highly aailable SAAM setup with two or more serers on the high aailability panel in the installation wizard. 2. Potentially, do an update installation to System Automation Application Manager V4.1.x in order to match the fix pack leel of the System Automation Application Manager installation on node Configure high aailability for the end-to-end automation manager as described in Actiating the high aailability policy on page 119. Installing for Distributed Disaster Recoery Find out what to do, if you plan to implement a setup with a System Automation Application Manager on two GDPS sites. In this configuration, System Automation Application Manager is moed automatically by GDPS if the K-System master moes. Installing the prerequisite software on both sites Install all necessary System Automation Application Manager prerequisites on the nodes of both sites. The order in which you install them is not important, but you must ensure that the software ersions, fix pack leels, and installation paths on both sites are the same. All configuration settings such as administrator ID and password, ports, DB2 instance, must be identical on both sites. See also Installing the middleware software on page 43. Installing and configuring System Automation for Multiplatforms Install System Automation for Multiplatforms on both sites. When the installation completes, create a single-node domain which is used to automate System Automation Application Manager, the WebSphere Application Serer, and DB2 HADR: 1. Prepare the cluster node by using the preprpnode command 2. Create the one-node peer domain by using the mkrpdomain command 3. Start the domain by using the startrpdomain command 4. Set up trace file spooling and adjust the ulimits to suit your needs For details on the installation and configuration, refer to the System Automation for Multiplatforms documentation listed in Where to find more information on page xi. Installing System Automation Application Manager on the first site You can select either of the two sites for your first System Automation Application Manager installation. The first site must be installed as an initial installation in a high aailability setup with local EAUTODB created during installation. Run your installation of System Automation Application Manager with the following options: Install in a high aailability setup, by selecting I want to create a highly aailable SA AM setup with two or more serers, and Yes for the installation on the first node. Select IBM DB2 on same system (local) and complete the required fields for this setup. 72 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

91 In the GDPS configuration section of the installation wizard, select Enable GDPS serer connection and Enable GDPS backup serer connection and specify the hostname and port number of the GDPS K-Systems of both sites. For more information, refer to Installing System Automation Application Manager on page 50. Configuring System Automation Application Manager on the first site You must use the following settings to associate the System Automation Application Manager with the GDPS site and to set up the high aailability policy: Start the cfgeezdmn configuration utility. On the Application Manager tab of the launchpad window, click Configure. The configuration dialog is displayed In the Domain tab, click Alternate host In the Define Alternate End-to-end Automation Host dialog box, specify the alternate site hostname of your other site, select Use GDPS to control the end-to-end automation manager site and select the correct GDPS site of the alternate host. On the High Aailability tab of the launchpad window, select Enable the high-aailability configuration tasks, and click Configure In the Select Application Manager High Aailability Setup window, click Configure the Applications Manager single node high-aailability policy for a disaster recoery setup, and click OK In the Command shell tab, select Use specified user credentials and proide the user credentials. Specify all the required information for this type of high aailability policy and sae your settings. Refer to Configuring System Automation Application Manager on page 96 and Configuring high aailability on page 117. Setting up DB2 HADR You must set up DB2 HADR for the application manager EAUTODB which was created during the installation of the first System Automation Application Manager. Stop the System Automation Application Manager. You must make the database aailable as Primary at the site where the second System Automation Application Manager is going to be installed. For more information about how to perform the setup, refer to the corresponding DB2 documentation. Perform the following sequence of steps. The user ID performing these commands must be the DB2 instance owner. 1. Stop the System Automation Application Manager on the first site. Ensure that the DB2 instance is started on both sites 2. Configure log shipping on the EAUTODB using the following commands, and substituting the alues of the tags between <>: db2 update database configuration for <DB name> using LOGRETAIN recoery db2 update database configuration for <DB name> using LOGINDEXBUILD ON Chapter 2. Installing 73

92 where: <DB name> is the name of the EAUTODB 3. Set up HADR using the following commands: db2 update db cfg for <DB name> using HADR_LOCAL_HOST <Hostname 1> HADR_REMOTE_HOST <Hostname 2> HADR_LOCAL_SVC <Port 1> HADR_REMOTE_SVC <Port 2> HADR_REMOTE_INST <DB instance name> HADR_TIMEOUT 120 HADR_SYNCMODE <Sync mode> HADR_PEER_WINDOW 0 Where: <DB name> is the name of the EAUTODB. <Hostname 1> is the hostname of the node where the EAUTODB was created. <Hostname 2> is the hostname of the node at the other site where System Automation Application Manager is going to be installed.system Automation Application Manager <Port 1> the port that is used for transaction log shipping on the node where the EAUTODB was created. The transmission protocol is HTTP and the default port number is5005 <Port 2> is the port that is used for transaction log shipping on the node at the other site (Site 2). The default is 5005 <DB instance name> is the instance name of EAUTODB on both sites. <Sync mode> choose between SYNC, NEARSYNC, and SUPERASYNC Note: The following steps are required during the initial installation of the DR setup. They are also required if the EAUTODB cannot be automatically reintegrated after a disaster. This problem occurs after a System Automation Application Manager toggle in which the EAUTODBs on both sites were modified without replicating the changes to the other site. You must perform the following steps to transfer the database to the other site: 4. Create a directory on both nodes owned by the DB2 instance owner that belongs to the DB2 administrators group. This directory is for your backup. 5. Back up the database using the following command on the first site, replacing the alues of the tags as indicated: db2 backup <DB name> to <Backup folder> Where: <DB name> is the name of the EAUTODB. <Backup folder> is the directory you created to store the backup 6. Transfer the generated backup file to the DB2 host at the other site. On that site restore the backup by using the following command: db2 restore db <DB name> from <Backup folder> replace history file Where: <DB name> is the name of the EAUTODB. <Backup folder> is the directory you created to store the backup 7. On the second site, you must adjust the HADR settings accordingly. The local host name must be exchanged with the remote host name. Use the following command, replacing the tags as indicated: db2 update db cfg for <DB name> using HADR_LOCAL_HOST <Hostname 1> HADR_REMOTE_HOST <Hostname 2> 74 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

93 Where: <DB name> is the name of the EAUTODB. <Hostname 1> is the DB2 host name on the second site where System Automation Application Manager is going to be installed. <Hostname 2> is the DB2 host name on the first site. 8. Start HADR at the standby database first. This is the site where the System Automation Application Manager remains offline. If you set up HADR the first time during System Automation Application Manager installation, the standby site is the site where System Automation Application Manager is already installed. Use the following command: db2 start hadr on database <DB name> as standby Where: <DB name> is the name of the EAUTODB. 9. Start HADR at the primary database. This is the site where System Automation Application Manager is going to be installed: db2 start hadr on database <DB name> as primary Where: <DB name> is the name of the EAUTODB. 10. Verify that the DB2 HADR is set up correctly on both sites. Use the following command on each site: db2pd -hadr -db <DB name> Check the output and erify that the HADR role is Standby at the site where System Automation Application Manager is already installed and Primary at the site where it is going to be installed. The HADR state on both sides must be Peer. Installing System Automation Application Manager on the second site Install System Automation Application Manager on the second site with the following options: Install in a high aailability setup, by selecting I want to create a highly aailable SA AM setup with two or more serers, and No as this is not the installation on the first node. Select IBM DB2 on same system (local) and complete the required fields for this setup. In the GDPS configuration section of the installation wizard, select Enable GDPS serer connection and Enable GDPS backup serer connection and specify the hostname and port number of the GDPS K-Systems of both sites. For more information, refer to Installing System Automation Application Manager on page 50. Configuring System Automation Application Manager on the second site You configure the second System Automation Application Manager in the same way as described for the first site you installed. All settings must be identical for both System Automation Application Manager installations, except for the GDPS Chapter 2. Installing 75

94 site of the alternate System Automation Application Manager host. You can configure either using the graphical mode or the silent configuration utility. Refer to Configure System Automation Application Manager for the graphical configuration. If you want to use the silent configuration utility, perform the following steps: 1. On the site where System Automation Application Manager is already configured, create the silent properties input file for the application manager common configuration using the following command: cfgeezdmn -s -e -gr 2. Transfer the silent properties input file from the first site to the host of the second site where you are now configuring System Automation Application Manager. 3. Adjust the settings for hostname, alternate hostname, and GDPS site location of the alternate hostname. 4. Perform a silent configuration on the second site: cfgeezdmn -s -e Creating tools for the replication of policy and credential files The System Automation Application Manager policies and stored credentials must always be synchronized. Replication of configuration changes to the other site is not performed automatically by System Automation Application Manager, but has to be done manually by the operator each time the configuration on one site is updated. To simplify this task, you can install or deelop a tool that copies the System Automation Application Manager policy pool and the dif properties files with the FLA domain credentials to the other site. You can customize the following example script with your site-specific information: #!/bin/sh scp r /etc/opt/ibm/tsamp/eez/policypool/ root@<hostname_at_other_site>: /etc/opt/ibm/tsamp/eez/policypool/ scp /etc/opt/ibm/tsamp/eez/cfg/eez.automation.engine.dif.properties root@<hostname_at_other_site>:/etc/opt/ibm/tsamp/eez/cfg Configuring all end-to-end automation adapters with two System Automation Application Manager hosts Eery first-leel automation adapter or remote Agentless Adapter connected to System Automation Application Manager must hae the capability of switching its eent target if the actie System Automation Application Manager moes to the other site. For this to be possible, you must ensure that the ersion of the adapters you install supports the System Automation Application Manager site switch. Furthermore, both System Automation Application Manager host names should be defined as alternate targets on each system. The required adapter ersions are: Version or higher for all adapters that are part of the System Automation Application Manager product System Automation for Multiplatforms ersion or higher for the System Automation for Multiplatforms adapter. System Automation for z/os 3.4 or higher for the z/os adapter. To configure the alternate System Automation Application Manager hostname, start the configuration utility for the corresponding adapter, click Configure, and 76 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

95 specify the alternate end-to-end automation management host name on the Host Using Adapter tab of the configuration dialog. For more information, refer to the specific sections on the adapter configurations in Chapter 3, Configuring, on page 89. The configuration for the System Automation for Multiplatforms adapter is described in IBM Tioli System Automation for Multiplatforms Installation and Configuration Guide, SC For the system Automation for z/os adapter, there is no configuration utility. Refer to the System Automation for z/os documentation for information about how to apply this configuration in this enironment. Configuring high aailability and contact retry interal of all end-to-end automation adapters If a disaster occurs, end-to-end adapters might fail and the two sites might experience protracted communication problems. In such a situation, the System Automation Application Manager and the end-to-end adapters of the other site cannot communicate. All adapters and the J2EE framework must be configured so that the adapters can try repeatedly to establish the connection to the J2EE framework. The J2EE framework must not remoe preiously connected domains before they can be reached again. It is recommended to set up the adapters as highly aailable resources. The following table lists the recommended settings of the end-to-end adapters and the J2EE framework. See also IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide, Chapter 4, "Modifying the enironment ariables for the automation Jaa EE Framework. For details about configuring adapters, refer to Chapter 3, Configuring, on page 89. Table 32. Recommended end-to-end adapter and J2EE framework settings in a DR setup End-to-end adapter is highly Configuration option aailable J2EE framework enironment ariable "com.ibm.eez.aab.domainremoal-hour" In the Adanced dialog in the Adapter configuration tabs: "Remote contact actiity interal" In the Adanced dialog in the Adapter configuration tabs: "initial contact retry interal" End-to-end adapter is not highly aailable 48 (default) a alue (default) 0 (retry foreer) 0 (default) 0 (retry foreer) Installing the remote Agentless Adapter You can install the remote Agentless Adapter using the wizard or in silent mode. Chapter 2. Installing 77

96 Using the installation wizard to install the remote Agentless Adapter Use an installation wizard to install the remote Agentless Adapter on AIX, Linux, or Windows systems. The installation wizard files are located either on the product DVD or in the directory that is created as a result of extracting the electronic delierable archie file for the respectie operating system as listed in Packaging on page 18. Perform the following steps: Procedure 1. Log on to the system where you want to install the remote Agentless Adapter with a user ID that has administrator authority. This user ID is typically root. On Windows, this is the built-in local administrator user account of the system. If User Account Control (UAC) is actie on the system, which is the default, make sure that the following default settings are actie: User Account Control: Admin Approal Mode for the Built-in Administrator account is disabled and User Account Control: Detect application installations and prompt for eleation is enabled. 2. Launch the installation wizard. On the first panel, click OK to display the Welcome panel. The language is detected automatically on your computer or you can select it on the Welcome panel. To launch the installation wizard to generate a response file, use the following command: <installation_wizard> -Dpreparesilent=true. The following response file is generated: <install_root>\install\install.properties. 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 to display the installation directory panel. 4. On Linux you can not change the default installation directory. On Windows you can specify a directory or leae the default alue. 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. On Linux, the default directory can not be changed. If a Tioli Common Directory was detected on your system, the directory is displayed and can not be changed. Click Next to display the preinstall summary. 6. After reiewing the displayed information, click Install to start the installation process. While the adapter is being installed, a progress panel is displayed. 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 Done to close the installation wizard. Related information: Configuring remote Agentless Adapters on page 113 Installing the remote Agentless Adapter in silent mode Use a response file which is generated during the wizard-drien installation to install the remote Agentless Adapter in silent mode. 78 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

97 For information on how to generate a response file, refer to Using the installation wizard to install the remote Agentless Adapter on page 78. Copy the generated response file to the system where you want to install the remote Agentless Adapter in silent mode. If you want to perform a silent installation, you need the same authorization as described for using the installation wizard in graphical mode. If you want to perform the remote Agentless Adapter installation on multiple systems with identical installation settings, copy the response file to each system and run the installation wizard in silent mode. Note: Response files contain password information. Delete the response files when they are no longer required. Procedure To install the remote Agentless Adapter in silent mode, use the following command: <installation_wizard> -i silent -f <response_file_name> Uninstalling the remote Agentless Adapter An uninstallation program is proided to remoe the adapter that was installed by the installation wizard. If you want to uninstall the remote Agentless Adapter, you need the same authorization as described in Using the installation wizard to install the remote Agentless Adapter on page 78 for an initial installation. During uninstallation, you may be prompted to confirm that specific files are to be deleted. Make sure the right files are listed before you confirm the deletion. To determine the current status of the adapter, use the following command: eezaladapter status If the adapter is still running, stop the adapter before starting the uninstallation: eezaladapter stop For more information about the eezaladapter command, refer to Tioli System Automation Application Manager, Reference and Problem Determination Guide. Procedure 1. To launch the uninstallation program, enter the following command in a shell: <EEZ_INSTALL_ROOT>/uninstall/uninstall. This opens the initial panel of the uninstallation program. 2. The uninstallation program is launched in the same language as used for the installation. After the uninstallation program is launched, the uninstallation wizard starts. Perform the following steps: a. On the Welcome panel, click Next to display the pre-uninstallation summary. b. After reiewing the displayed information click Uninstall to start the uninstallation process. c. The wizard remoes the remote Agentless Adapter from your system. No configuration files will be remoed. When the uninstallation is completed, Chapter 2. Installing 79

98 the uninstallation summary is displayed. If problems occur, check the applicable installation log files for more information. Click Done to close the uninstallation wizard. 3. To perform a silent uninstallation, no response file is necessary. To launch the silent uninstallation, use the following command: <installation_wizard> -i silent. Installing and uninstalling serice for the remote Agentless Adapter Installing serice means applying correctie serice fix packs to release 4.1 of the IBM Tioli System Automation Application Manager remote Agentless Adapter. The serice fix packs that you use for updating a remote Agentless Adapter are referred to as product fix packs. Product fix packs and interim fixes are deliered as: Self-extracting archies for AIX and Windows Archies in TAR-format for Linux Where to obtain fixes Read the release notes to find out which fix packs are required for a release update. The fix packs are aailable on the IBM Tioli System Automation support page at: Tioli/Tioli_System_Automation_Application_Manager Perform the following steps: 1. Click Downloads to display all aailable fix packs. 2. Click View all download links. 3. Click Documentation to display the list of aailable documentation. 4. Click Troubleshooting to find all related APARs. The archies can be downloaded from the IBM Tioli System Automation support site at: IBMTioliSystemAutomationforLinux.html Archie naming conentions The archies to upgrade a remote Agentless Adapter from ersion 4.1 hae the following syntax: TIV-SAAMR-<platform>-FP<fix_pack_number>.<archie_type> <platform>: Represents the platform on which the remote Agentless Adapter is installed. <fix_pack_number>: Represents the fix pack number. <archie_type>: Represents the platform-specific file extension of the archie. This is the tar archie that is used to install product fix pack 1 for the remote Agentless Adapter on Linux on POWER platforms: TIV-SAAMR-PPC-FP0001.tar Naming conentions of the update installer location 80 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

99 Naming conentions of the update installer location After the Linux on POWER archie for fix pack 1 for the remote Agentless Adapter 4.1 is unpacked, you can find the update wizard in the following directory: EEZ4101Remote/PPC/ALAdapt/ Usage instructions for the platform-specific archies These are the archies for applying serice to the remote Agentless Adapter. Table 33. Archies for applying serice to remote Agentless Adapter Operating system Archie name Description Windows AIX Linux on System x Linux on POWER Linux on System z TIV-SAAMR-Windows- <fix_pack_number>.exe TIV-SAAMR-AIX- FP<fix_pack_number>.bin TIV-SAAMR-I386- FP<fix_pack_number>.tar TIV-SAAMR-PPC- FP<fix_pack_number>.tar TIV-SAAMR-S390- FP<fix_pack_number>.tar The archie is self-extracting. This is where you find the update installer program after unpacking the product fix pack archie: EEZ41<mf>Remote\Windows\ALAdapt\setup.exe The archie is self-extracting. This is where you find the update installer program after unpacking the product fix pack archie: EEZ41<mf>Remote\AIX\ALAdapt\setup.bin 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: EEZ41<mf>Remote\I386\ALAdapt\setup.bin 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: EEZ41<mf>Remote\PPC\ALAdapt\setup.bin 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: EEZ41<mf>Remote\S390\ALAdapt\setup.bin Installing a product fix pack Before you begin, be aware of the following: Product fix packs are always cumulatie. Release 4.1 must be installed before any product fix pack can be installed. To install a product fix pack, you must hae root authority. 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 for product fix packs from the System Automation Application Manager support site to a temporary directory. Chapter 2. Installing 81

100 3. 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. 5. 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. The same authorization is required as described in Using the installation wizard to install the remote Agentless Adapter on page Follow the instructions on the wizard panels to install the product fix pack. The steps that you hae to perform are the same as described for the initial installation. Uninstalling serice Installing the HACMP adapter If you want to uninstall serice you need to uninstall the complete remote Agentless Adapter as described in Uninstalling the remote Agentless Adapter on page 79. Then you can reinstall to the leel required. Find out how to install the HACMP adapter using SMIT and how you can erify your installation. Using SMIT to install the adapter You will find the package in the directory on the DVD or in the electronic delierable as described in Packaging on page 25. Package name: hac.adapter. Use the SMIT interface to install the adapter. The HACMP adapter installation directory is /opt/ibm/tsamp/eez/hac 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 Configuring the HACMP adapter on page 152. Verifying the HACMP adapter installation 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 82 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

101 Interface: p57067ha (in the example configuration) associated with the serice IP label of the same name in State: UP clstat - HACMP Cluster Status Monitor Cluster: hacp57067 ( ) Mon Feb 20 14:15:16 MET 2011 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 ********* Uninstalling the HACMP adapter Installing the FOC adapter To uninstall the HACMP adapter, perform the following steps: 1. Stop the HACMP adapter by using the hacadapter -stop command. 2. Use the SMIT interface to uninstall the adapter. The package name is hac.adapter. You can install the FOC adapter either using the wizard or in silent mode. Make sure you erify your installation. Generate a response file when you use the installation wizard on a node. 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. Installing the Failoer Cluster Command Interface optional feature The Failoer Cluster Command Interface feature is required to configure the FOC adapter. Starting with Windows Serer 2012 system, this feature is not installed anymore per default as part of the Failoer Cluster (FOC) installation. The cluster.exe executable which is part of the feature is required by the cfgmscsadapter utility. If you are planning to use the FOC adapter, make sure that the Failoer Cluster Command interface feature is installed on all nodes of the failoer cluster. The feature is located in the hierarchy of installable features as follows: > Remote Serer Administration Tools > Feature Administration Tools Chapter 2. Installing 83

102 > Failoer Clustering Tools > Failoer Cluster Command Interface Using the installation wizard to install the FOC adapter This topic describes how you install the FOC adapter using the installation wizard. For information on silent mode, see Installing the FOC adapter in silent mode on page 85. The installation wizard files are located either on the product DVD or in the directory that is created by extracting the archie file. You can find the archie file names for the respectie operating system in the topic Packaging on page 28. 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. Launch the installation wizard to generate a response file. Enter the command: setup.exe -Dpreparesilent=true You can find the response file in the following directory: <install_root>\install\install.properties 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 Failoer Cluster adapter serice user panel. 6. Specify the domain user account prepared in Preparing the user account on page 29 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. When the installation is complete, an installation summary panel is displayed, on which you can erify the success of the installation. 84 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

103 If problems occur, check the applicable installation log files for more information. Click Finish to close the installation wizard. Installing the FOC adapter in silent mode This topic 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 FOC adapter on page 84. To install the FOC adapter in silent mode, use the following command: setup.exe -i silent -f <response_file_name> Note: 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. Upgrading the FOC adapter You can upgrade an already installed FOC adapter to the current ersion by running the installation as described in Installing the FOC adapter on page 83. Verifying the FOC adapter installation Perform the following steps to erify that the adapter is installed and configured correctly: The adapter is highly aailable: 1. Start the FOC adapter using Microsoft FOC and check if the domain joins. 2. Fail the adapter oer to all Microsoft FOC nodes and check if the domain joins. The adapter is not highly aailable: Start the FOC adapter using the Serices plug-in from the Microsoft Management Console and check if the domain joins. Uninstalling the FOC adapter Perform the following steps: 1. Make sure that the FOC adapter serice is stopped before starting the uninstallation. Note that Microsoft FOC may try to restart or fail the FOC adapter serice oer to another Microsoft FOC node if you stop the serice manually. If the FOC adapter serice is highly aailable, you must take the FOC adapter group offline. Chapter 2. Installing 85

104 Installing the VCS adapter 2. Open the Windows Control Panel and use Add or Remoe Programs to uninstall the adapter. You can install the VCS adapter using the wizard or in silent mode. Make sure you erify your installation. Using the installation wizard 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 install.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. To launch the installation wizard, generating a response file, use the following command: install.bin -Dpreparesilent=true This is the response file that is generated: <install_root>\install\install.properties 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 Configuring the VCS adapter on page 170. Installing the VCS adapter in silent mode This topic describes how to install the adapter in silent mode, using a response file 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, refer to Using the installation wizard. To install the VCS adapter in silent mode, use the following command: install.bin -i silent -f <response_file_name> Note: 1. Response files contain password information. Delete the response files when they are no longer required. 2. The silent installation is successful if the wizard-drien installation completed successfully without errors on the system where the response file was generated. 86 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

105 Verifying the VCS adapter installation 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: 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 Uninstalling the VCS adapter To uninstall the VCS adapter, perform the following steps: 1. Stop the VCS adapter by using the cscadapter -stop command. 2. Open a shell and naigate to /opt/ibm/tsamp/eez/cs/uninstall_vcs_adapter 3. Inoke the script Uninstall VCS Adapter to uninstall the adapter. Chapter 2. Installing 87

106 88 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

107 Chapter 3. Configuring After you hae installed System Automation Application Manager and the components that you require, complete additional configuration tasks to fully prepare your infrastructure enironment. This topic proides an oeriew of how you use the System Automation Application Manager configuration dialog to change the common configuration of System Automation Application Manager, to configure components of the Distributed Disaster Recoery feature, and to configure System Automation Application Manager to be highly aailable. Note: You need an X11 serer to use the application manager configuration dialog. You need the 32 bit ersion of the X11 installation packages to run the configuration dialog. On some Linux operating system platforms those packages are contained on the distribution media, but are not part of the standard installation. Make sure that the 32 bit ersion of the X11 installation packages are actually installed. You can also configure the application manager in silent mode using an input properties file. If an X11 serer is not aailable, silent configuration is the only supported method on this system. See Inoking silent configuration on page 183 for more details. Inoking the configuration dialog You can use the cfgeezdmn command or the task launcher to inoke the configuration dialog. Note: The 32 bit ersion of the X11 serer installation is required to use the configuration dialog. On some Linux operating system platforms those packages are contained on the distribution media, but are not part of the standard installation. Make sure that the 32 bit ersion of the X11 installation packages are actually installed. Using the cfgeezdmn command The cfgeezdmn command configures arious settings of the end-to-end automation engine, the Agentless Adapter, and the SA Jaa EE framework. The command offers a graphical user interface to specify parameters, which are stored in arious property files required by the System Automation Application Manager components. Most parameters configured with this command control the behaior of the System Automation Application Manager components and do not need to be changed frequently. In addition, the cfgeezdmn command is used to add or change user IDs and passwords which are used by the automation engine to contact other automation domains. Before you begin: Copyright IBM Corp. 2006,

108 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. The group permissions for the cfgeezdmn script must be set to EXECUTE. The user ID must hae write access to the following directory: /etc/opt/ibm/tsamp/eez/cfg Perform the following step to inoke the configuration dialog: 1. Log in on the system where System Automation Application Manager is installed. 2. Run the 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 configuration dialog on page 89. The configuration tasks that can be launched are structured in the following groups: Application Manager common configuration Agentless Adapter for non-clustered nodes configuration Virtual Serer and Hardware Management configuration Storage Replication configuration Application Manager high-aailability configuration More detailed information about all configuration tasks is aailable in the online help. To launch the online help, click Help in the menu bar of the configuration dialog. Application Manager tab Use the Application Manager tab for common configurations for the System Automation Application Manager. 90 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

109 Figure 6. Application Manager tab of the Automation Manager Configuration dialog Controls and fields on the Application Manager tab: Application Manager common configuration: Configure Click Configure in the Application Manager common configuration section to open the Application Manager common settings dialog. Here you can specify configuration settings that are common for different components of System Automation Application Manager. For more information, see Configuring System Automation Application Manager on page 96. Refresh Click Refresh in the Application Manager common configuration section of this tab to update certain configuration settings of the actie, running Application Manager application. For more information, see Refreshing the application manager common configuration on page 105. Non-Clustered Nodes tab Use the Non-Clustered Nodes tab to configure Agentless Adapters. Chapter 3. Configuring 91

110 Figure 7. Non-Clustered Nodes tab of the Automation Manager Configuration dialog Controls and fields on the Non-Clustered Nodes tab: Local Agentless Adapter configuration: Enable local Agentless Adapter configuration Select this check box to enable the local Agentless Adapter configuration. This will hae the following effects: The local Agentless Adapter configuration button is enabled. Configuration files of the local Agentless Adapter are updated if they are affected by changes that you apply to the Application Manager common configuration. If you hae configured Application Manager high-aailability, the corresponding resources will be included into the Application Manager automation policy. Refer to Configuring high aailability on page 117 for more information on configuring high-aailability the Application Manager. The configuration dialog will remember the enable/disable status of the local Agentless Adapter configuration across multiple inocations. Note: This check box applies only to the local Agentless Adapter, but not to any remote Agentless Adapter. Configure Click Configure in the Application Manager local Agentless Adapter configuration section of this tab to open the Application Manager Agentless Adapter configuration dialog. For more information, refer to Configuring the local Agentless Adapter on page 107. Remote Agentless Adapter configuration: Configure Click Configure in the Application Manager remote Agentless Adapter configuration section of this tab to open the Application Manager remote 92 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

111 Agentless Adapter configuration dialog. For more information, refer to Configuring remote Agentless Adapters on page 113 Virtual Serer / HW Management tab Use the Virtual Serer / HW Management tab to configure the hardware adapter. Access the zenterprise Hardware Management Console (HMC) for irtual serer management. Manage hardware for distributed disaster recoery with Geographically Dispersed Parallel Sysplex (GDPS). Note: The tasks on this tab are only enabled on a limited set of operating system platforms. For more information, see Supported hardware and operating systems on page 21. Figure 8. Virtual Serer / HW Management tab of the Application Manager Configuration dialog Controls and fields on the Virtual Serer / HW Management tab: Configure Click Configure in the Application Manager hardware adapter configuration section of this tab to open the 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 hardware adapter on page 142. Refresh Click Refresh in the Application Manager hardware adapter configuration section of this tab to trigger a reload of changed hardware access credentials into an actie, running hardware adapter. For more information, see Refreshing the actie hardware adapter configuration on page 147. Test Click Test in the Application Manager hardware adapter configuration section of this tab to test the hardware adapter functionality as far as Chapter 3. Configuring 93

112 possible without powering on or off the remote hardware systems. For more information, see Testing the hardware adapter on page 148. Storage Replication tab Use the Storage Replication tab to configure the Tioli Storage Productiity Center for Replication (TPC-R) domain to manage storage replication. Note: The tasks on this tab are only enabled on a limited set of operating system platforms. For more information, see Supported hardware and operating systems on page 21. Figure 9. Storage Replication tab of the Application Manager Configuration dialog Controls and fields on the Storage Replication tab: Configure Click Configure in the TPC-R domain configuration section of this tab to open the TPC-R domain configuration dialog. Use this dialog to configure the settings of the TPC-R domain and the user credentials to access the corresponding TPC-R serers. For more information, see Configuring the TPC-R domain on page 149. Refresh Click Refresh in the TPC-R domain configuration section of this tab to trigger a reload of the TPC-R domain settings by the actie, running application manager application and recycling any actie session with a TPC-R serer in order to pick up changed user credentials. For more information, see Refreshing the TPC-R domain settings on page 152. Test Click Test in the TPC-R domain section of this tab to test the currently configured TPC-R domain properties. For more information, see Testing the TPC-R domain configuration on page 152. High Aailability tab Use the High Aailability tab to configure the System Automation Application Manager high aailability policy. 94 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

113 Figure 10. High Aailability tab of the Application Manager Configuration dialog You perform the tasks in this topic to proide high aailability for System Automation Application Manager. You actiate the task buttons by selecting the Enable the high aailability configuration tasks check box. For more information, see Configuring high aailability on page 117. Change Passwords tab Use the Change Passwords tab to change the passwords for any of the user credentials that are defined in the System Automation Application Manager configuration. You can use this tab as a shortcut to manage passwords rather than launching arious configuration tasks, especially if you hae to change multiple or een all credentials at the same time. Figure 11. Change Passwords tab of the Application Manager Configuration dialog Chapter 3. Configuring 95

114 Controls and fields on the Change Passwords tab: The list on this tab contains entries for all credentials that can be configured for System Automation Application Manager. Component This column shows all components that contain user credentials as part of their configuration. If multiple credentials can be configured for a component, there is one list entry showing the same component for each user ID. User ID This column shows the user IDs that are currently configured for the respectie credentials. If <not configured> is shown, either the complete component is currently not configured or the corresponding credentials are currently not configured, because they are optional. Description This column explains the purpose of the corresponding credentials. Change password Use the Change password button to display a dialog that prompts you to specify and confirm the password for the selected user ID. Note that a password change will not actually change any password on the affected system, but only in one of the configuration files. After you hae successfully changed a password, the resulting message will indicate the updated configuration file. Configuring System Automation Application Manager The initial configuration of System Automation Application Manager is performed during the installation of the product. To browse or change the properties you can use the System Automation Application Manager configuration dialog or silent configuration. You should neer manually edit the configuration properties files in which the configuration parameters are stored. The following topics describe the common configuration tabs of the System Automation Application Manager configuration dialog. To open the configuration dialog, perform these steps: 1. Inoke the configuration dialog (see Inoking the configuration dialog on page 89). 2. On the task launcher, click Configure in the Application Manager common configuration section on the Common tab. The common configuration dialog opens. Refer to Domain tab on page 97. Post-configuration tasks: After changing any of the configuration properties, you must perform the following tasks: Some configuration settings can be dynamically actiated by launching the Refresh task on the Common tab of the task launcher. If System Automation Application Manager is configured for high aailability, you must replicate the configuration files to the other nodes of the System Automation for Multiplatforms cluster that proides the high aailability. 96 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

115 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 hardware adapter of the Distributed Disaster Recoery feature, it must also be restarted using the commands eezhwadapter -stop and eezhwadapter -start. Domain tab Use the Domain tab to configure the of the end-to-end automation domain and the host where the end-to-end automation manager is running. Controls and fields on the Domain tab: 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). The maximum number of characters for a alid automation domain name is 64. Host name or IP address Name or IP address of the system that hosts the end-to-end automation manager. Alternate Host Click to configure an alternate end-to-end automation host, and follow the procedure described in Configuring an alternate end-to-end automation host on page 105. 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 the System Automation for z/os adapter, this is the eent port specified in the adapter configuration parameter eif-send-to-port in the adapter plug-in properties file. 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. Command Shell tab Use the Command Shell tab to configure authentication settings for using the Application Manager command shell. Controls and fields on the Command Shell tab: Chapter 3. Configuring 97

116 User authentication for inoking the command shell: 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. 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 using the -u and -p options. 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. Note: If you hae configured the hardware adapter to manage hardware for distributed disaster recoery with GDPS, you must specify credentials in the user ID and password fields independent from the selected authentication mode. This ensures correct authentication when the hardware adapter internally uses the command shell in this setup. User authentication for inoking commands against first-leel automation (FLA) domains: When the command shell is used to issue FLA domain commands, an additional authentication is required to access FLA domains. You hae the choice between these authentication modes: Read FLA domain access credentials from stdin In this mode, users must always specify the FLA domain access credentials in the command shell window using the -du and -dp options. Use FLA domain credentials as specified under "User credentials" In this mode, users may omit FLA domain access credentials in the command shell window if credentials are defined for the respectie domain on the "User credentials" tab (see User Credentials tab on page 100). Discoery Library Adapter tab Use the Discoery Library Adapter tab to configure the location where the Discoery Library Adapter (DLA) stores IdML books. System Automation Application Manager proides a DLA to export the currently actie System Automation Application Manager resource topology to an Identity Markup Language (IdML) discoery book. Controls and fields on the Discoery Library Adapter tab: IdML book directory The absolute path to the directory where the DLA should store IdML books. The Browse button that you can use to select a directory is only enabled if you select the local IdML book directory radio button. 98 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

117 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 host name 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. OSLC tab Use the OSLC tab to configure the settings to use the Open Serices for Lifecycle Collaboration (OSLC) serices proided by System Automation Application Manager. Controls and fields on the Eent Publishing tab: Enable resource registration using OSLC serices Select this check box if you want to use the Application Manager OSLC serices. If the check box not selected, the other fields on this tab are disabled. Host name or IP address The host where the OSLC administration and registry serer that is used by the Application Manager is located. Port number The port number used to communicate between the end-to-end automation management serer and the OSLC administration and registry serer. User ID The user ID that is used to logon to the OSLC administration and registry serer. Password The password that is used to logon to the OSLC administration and registry serer. Click Change to change the password. Truststore The name of the truststore file used for Secure Sockets Layer (SSL) communication with the OSLC serer. Click Browse to select a file. Chapter 3. Configuring 99

118 Truststore password The password of the truststore file. Click Change to change the password. User Credentials tab Use the User Credentials tab to configure the user credentials of the end-to-end automation manager. The automation manager uses these credentials to 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). Controls and fields on the User Credentials tab: Functional user ID The end-to-end automation engine uses the functional user ID to access the automation J2EE framework running in WebSphere Application Serer. The automation J2EE framework uses the same user ID to access JMS and to perform asynchronous tasks. Functional password The password for the functional 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 the Credentials for accessing specific FLA domains table. 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. The Validate button lets you alidate the user ID and password that you specified for the currently-selected domain. The domain is contacted, and the alidation is performed on the system where the end-to-end automation adapter (that manages the domain) is currently running. For more details, refer to Tioli System Automation Application Manager, Administrator s and User s Guide. Eent Publishing tab Use the Eent Publishing tab to configure settings to publish EIF eents to Tioli Netcool/Omnibus or to Geographically Dispersed Parallel Sysplex (GDPS). Controls and fields on the Eent Publishing tab: OMNIbus eent publishing Enable OMNIbus EIF eent publishing Select this check box if you want EIF eents to be sent to the host where 100 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

119 the OMNIbus Probe for Tioli EIF is running. If the check box is not selected, all fields for OMNIbus eent publishing on this tab are disabled. Note: For compatibility reasons, alternatiely a TEC serer and port may still be configured. Eent serer Host name or IP address The host name or IP address of the host where the OMNIbus Probe for Tioli EIF is running. You can specify up to eight alues, separated by commas. The first location is the primary eent serer. All other locations are secondary serers used in the order specified and when the primary serer is down. Port number The port number on which the OMNIbus Probe for Tioli EIF is listening to EIF eents. Eent filter Publish EIF eents caused by: Automation domain eents Select this check box if you want EIF eents for application manager automation domain eents to be sent to the eent serer. Otherwise domain eents are filtered out. Adding and remoing requests Select this check box if you want EIF eents for adding and remoing requests to be sent to the eent serer. Otherwise eents for adding and remoing requests will be filtered out. Resource status changes Select this check box if you want EIF eents related to resource status changes to be sent to the eent serer. Otherwise all resource status change eents will be filtered out. If you choose resource status change eents to be published, use one of the radio buttons below this check box to select the status change seerity for which eents should be published. Defining additional filters: The eent filters that you can enable or disable on this tab are the predefined filters that are shipped with System Automation Application Manager. If you want to define additional filters, modify manually the corresponding configuration properties file: /opt/ibm/tsamp/eez/cfg/eez.publisher.omnibus.properties Do not edit predefined filters in this file, only add new filters. If you want to edit a predefined filter, add a new filter and disable the predefined filter. If configuration changes are applied by the cfgeezdmn configuration utility, any filters that you hae added will be presered. GDPS eent publishing Hardware management with GDPS is enabled Chapter 3. Configuring 101

120 Note: If you hae not enabled configuration of the hardware adapter for distributed disaster recoery with GDPS, all fields to configure GDPS eent settings are disabled. Host name or IP address If you use the System Automation Application Manager hardware adapter to manage hardware for distributed disaster recoery with GDPS, define the GDPS eent serer. Proide the host name or IP address of the GDPS eent serer. Port number The port number on which the GDPS eent serer is listening to EIF eents. Enable a backup GDPS eent serer Optionally, you can also configure a backup eent serer (Host name or IP address) and port. Select this check box if you want to configure a backup GDPS eent serer. Specify the backup seer host name or IP address and port number in the entry fields that get enabled when you select the check box. For more information about configuration of the hardware adapter for distributed disaster recoery with GDPS refer to Configuring the hardware adapter on page 142. Security tab Use the Security tab to configure the properties for the SSL connection to the first-leel automation domains. Controls and fields on the Security tab: Truststore The fully qualified file name of the truststore file that is used for SSL. Click Browse to select a file. Keystore The fully qualified file name of the keystore file that is used for SSL. 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). Enforce use of SSL for all first-leel automation domains Select this check box if you want to enforce that all first-leel automation domains must be properly configured for using SSL at the transport layer before they may successfully connect to the end-to-end automation manager. If not selected, first-leel automation domains may or may not be configured for using SSL on an indiidual basis. For more information, see Securing the connection to end-to-end adapters using SSL on page Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

121 Logger tab Use the Logger tab to configure message logging, tracing and FFDC options for different components of System Automation Application Manager. The settings apply to the following components: End-to-end automation engine End-to-end automation manager command shell Discoery library adapter Agentless Adapter (if its configuration is enabled) Hardware adapter (if it is configured) 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 on the system where this dialog resides, an error message occurs. 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. 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: Error Logs messages on the error leel. Warning Logs messages on the error and warning leels. Information Logs messages on the error, warning and informational leels. Chapter 3. Configuring 103

122 Trace logging leel: Off Collects no trace information. Minimum Collects trace information on the error leel. Medium Collects trace information on the error and warning leels. Maximum 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 bytes (10 MB). 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). Saing the common configuration To sae your changes to the System Automation Application Manager common configuration properties files, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. If you hae configured high aailability for System Automation Application Manager, you must replicate the properties files to the other nodes in the System Automation for Multiplatforms cluster (see Replicating the configuration files on page 126). 104 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

123 Refreshing the application manager common configuration Clicking Refresh on the "Common" tab of the configuration dialog task launcher triggers a couple of configuration settings being reloaded by the end-to-end automation engine without the need to recycle it. Use this task in the following cases: After changing the credentials for accessing specific first-leel automation domains on the "User credentials" tab of the System Automation Application Manager common configuration. To clear the list of first-leel automation domains that cannot be accessed anymore due to fatal access errors. For more information refer to Tioli System Automation Application Manager, Administrator s and User s Guide. After making any other changes to the System Automation Application Manager common configuration, you must restart the automation engine using the commands eezdmn -shutdown and eezdmn -start. Configuring System Automation Application Manager in silent mode You can configure System Automation Application Manager in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration tasks: Configuring Application Manager common settings Refreshing the Application Manager common configuration. Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. Configuring an alternate end-to-end automation host The definition of an alternate end-to-end automation host is optional. If you want to configure a disaster recoery setup using two different sites for System Automation Application Manager, the end-to-end automation manager can run on either site. To enable such a setup, you must define the host of System Automation Application Manager on the alternate site. Click Alternate Host on the Domain tab. In the dialog that opens, you must specify the hostname or IP address of the WebSphere Application Serer hosting the automation manager application on the alternate site. If you are running on a Linux for System z operating system, you can select to use Geographically Dispersed Parallel Sysplex (GDPS) to control on which site the end-to-end automation host is located. In this case, you must also select the GDPS site where the local and the alternate end-to-end automation hosts are located. When you are configuring an alternate end-to-end automation host, proceed as follows: 1. Specify the host names that you use in this configuration in a reciprocal way for the application manager common configuration on the alternate site: Specify the local end-to-end automation hostname of this configuration as alternate hostname for the configuration on the alternate site. Chapter 3. Configuring 105

124 Specify the alternate hostname of this configuration as local end-to-end automation hostname for the configuration on the alternate site. 2. If you are using GDPS to control on which site the actie end-to-end automation host is located, select the complementary GDPS site for the application manager common configuration on the alternate site. If you selected the alternate host to be on GDPS Site1 in this dialog, select the alternate host to be on GDPS Site2 in the application manager common configuration on the alternate site and ice ersa. 3. Specify both the local and the alternate end-to-end automation hostname on the Host Using Adapter tab in the configuration of all end-to-end automation adapters, including remote Agentless Adapters. When an Application Manager site is switched, this setting ensures that the adapters smoothly switch to the new actie end-to-end automation manager instance as the target for sending eents. 4. If there is an Application Manager site switch, there might be a relatiely long period where end-to-end automation adapters cannot communicate with either end-to-end automation host. To ensure that adapters continue to contact the System Automation Application Manager, configure appropriate alues for "Remote contact actiity interal" and "Initial contact retry interal" in the adanced settings in the configuration of all end-to-end automation adapters. Modify the adanced settings by clicking Adanced on the Adapter tab in the adapter configurations. For information on these settings, refer to Installing for Distributed Disaster Recoery on page 72. Configuring Agentless Adapters You can configure and use either the local Agentless Adapter or one or multiple remote Agentless Adapters or a combination of both. Configuration of both local and remote Agentless Adapters is performed on the system where the System Automation Application Manager serer is installed using the cfgeezdmn configuration utility. After completing the configuration for one instance of the remote Agentless Adapter, this configuration is distributed to the corresponding adapter host. Figure 12 on page 107 shows how configurations for Agentless Adapters are maintained using the cfgeezdmn configuration utility. 106 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

125 System Automation Application Manager cfgeezdmn configuration utility Configuration files - Agentless Adapter - Remote clients - remote.client1 - remote.client2 read Local Agentless Adapter distribute distribute remote.client2 remote.client1 Configuration files - Agentless Adapter Configuration files - Agentless Adapter read read ALA Domain1 ALA Domain2 Remote Agentless Adapter Remote Agentless Adapter ALA Domain3 ALA Domain4 ALA Domain5 ALA Domain6 ALA Domain7 Figure 12. Maintaining configurations for multiple Agentless Adapters. Configuring the local Agentless Adapter The System Automation Application Manager local Agentless Adapter configuration dialog helps you to configure the local Agentless Adapter settings. To open the configuration dialog, click Configure in the Local Agentless Adapter configuration section on the Application Manager tab of the task launcher panel. Adapter tab Use the Adapter tab to configure the parameters of the host system on which the adapter is running and the parameters required for the Agentless Adapter policy. Controls and fields on the Adapter tab: Request port number Specify the number of the port on which the Agentless Adapter listens for requests from the end-to-end management host. The default port is If you configured the hardware adapter, make sure that the port numbers of the Agentless Adapter and the hardware adapter are different. Policy pool location Specify the qualified path name of the directory that contains the Agentless Adapter policies. These policies define resources on non-clustered nodes. The resources are managed by the Agentless Adapter. Click Browse to select a directory. Chapter 3. Configuring 107

126 Automation domain list The table lists automation domain names. Each domain represents a set of resources on nodes that are not clustered and managed by the Agentless Adapter. A domain name must match the domain name alue defined in the policy file. This policy file defines the corresponding set of resources. Add, Remoe or Rename domains To change the list of domains, use the corresponding buttons: Add Click Add to open a dialog. Specify the domain name that you want to add to the list. Remoe Select a domain from the list and click Remoe. Rename Select the domain name you want to rename and click Rename. A dialog opens. Enter the new name. Click Adanced. A dialog opens to specify the adapter runtime behaior: Adapter stop delay Defines the time measured in seconds within which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You can increase the alue on slow systems. The alue ranges between 3 through 60 seconds. Remote contact actiity interal Defines the time after which the automation adapter stops if there is no communication with the end-to-end automation management host. Setting this parameter to 0 means that the adapter continues to run and neer stops. The default alue is 360 seconds. If you configured application manager high aailability, see Configuring high aailability on page 117. It is recommended that you specify a alue greater than 0. In this case, the adapter is part of the high aailability policy and it is restarted automatically. The adapter then tries to contact the end-to-end automation management host again, using the alue specified in the Initial contact retry interal parameter. If your adapter is not configured for high aailability, specify 0 so that the adapter waits until it is contacted again by the end-to-end automation management host. Initial contact retry interal Defines the time measured in minutes, within which the adapter attempts to contact the end-to-end automation management host until it succeeds or the specified time elapses. The default alue is 0, where 0 means the adapter attempts to contact the end-to-end automation management host indefinitely. The alue range is minutes. Enable EIF eent caching Select this check box to actiate eent caching. EIF reconnect attempt interal Defines the time that the adapter waits before it attempts to reestablish the connection to the end-to-end automation management host after the connection is interrupted. The default alue is 30 seconds. The alue ranges seconds. 108 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

127 User Credentials tab Use the User Credentials tab to configure credentials of the Agentless Adapter. These credentials are used to access remote nodes hosting remote resources that are managed by the Agentless Adapter. These credentials are not required for ITM resources that are managed by the Agentless Adapter. Credentials for ITM resources are configured on the Tioli Monitoring tab. For details about how to configure these credentials, refer to Tioli Monitoring tab on page 110. Controls and fields on the User Credentials tab: Configure the user IDs and passwords that the Agentless Adapter uses to access remote nodes hosting resources that are managed by the Agentless Adapter. For more information, refer to Securing the connection to end-to-end adapters using SSL on page 260. Generic user ID Enter a generic user ID to access all non-clustered nodes for which no specific credentials are defined in the list Credentials for accessing specific non-clustered nodes below. Generic credentials are optional. If you want to remoe already configured generic credentials, leae the user ID field empty. Generic password Enter your password. Click Change to change the password. Credentials for accessing specific non-clustered nodes Define user credentials for each non-clustered node for which the generic credentials do not apply. The list shows all currently defined user credentials and their related node names. Add Click Add to define a new user ID and password to access remote nodes. More than one user credential per node is allowed. Remoe Select an entry in the list. Click Remoe to remoe the selected entry from the list. Modify Select an entry in the list. Click Modify to edit the node name, user ID, or password. Note: 1. If an IP6 host name is specified as node name, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address as node name instead of the host name. Use the tools proided by the operating system to check the DNS lockup records. For example, on LINUX use the command host -a <ip6_hostname> to check the DNS lookup records. You may decide to use SSH public and priate keys for user authentication between Agentless Adapter and remote non-clustered nodes on the Security tab. In this case do not define specific credentials for any pair of node name and user ID for which you want to use the SSH key authentication approach. Chapter 3. Configuring 109

128 Tioli Monitoring tab Use the Tioli Monitoring tab to configure the integration of Tioli Monitoring and IBM Tioli Composite Application Manager (ITCAM) resources by defining settings and credentials to access the Tioli Monitoring SOAP Serer. Controls and fields on the Monitoring tab: Enable integration of ITM/ITCAM resources Select this check box if you want to integrate ITM/ITCAM resources in a policy for a domain that is managed by the local Agentless Adapter. Selecting this option enables all controls on this tab pane. Configure settings to access the Tioli monitoring SOAP serer Host name or IP address Specify the name or the IP address of the host where the hub monitoring serer that hosts the SOAP serice is running. SOAP serer port number Specify serice point port number of the SOAP serer hosted by the hub monitoring serer. The default number for a non SSL port is The default number for an SSL port is You must specify the number of an SSL port if you selected the check box to use Secure Socket Layer (SSL) for communication with the SOAP serer. SOAP alias of hub Specify the alias name of the hub monitoring serer to which a SOAP request is routed. The request is routed to the hub monitoring serer which is on the same system as the SOAP serer. In this configuration, you must specify SOAP as the alias. If you want to route the SOAP request to a remote hub, specify the alias name of this remote hub. This alias must be preiously defined to the SOAP serer in the ITM/ITCAM SOAP serer configuration. Use SSL for communication with the SOAP serer Select this check box if the Agentless Adapter must use Secure Socket Layer (SSL) for communication with the SOAP serer. If you select this option, you must specify the number of an SSL port in the SOAP serer port field. The https protocol is used for communication. Configure credentials for accessing the Tioli monitoring SOAP serer For each user ID that is specified for an ITM/ITCAM resource in an Agentless Adapter policy, you must define the user s credentials in the list of specific credentials for accessing the SOAP serer. When no user ID for the ITM/ITCAM resources is specified in the policy, the generic user credentials are used. Generic user ID Specify the generic user ID that is used to access the ITM/ITCAM resources for which a user ID was omitted in the Agentless Adapter policy. If you specified a user ID for all ITM/ITCAM resources in the Agentless Adapter policies, this field is not used. Generic Password Specify the password of the generic user ID. This field is mandatory only if you supplied a generic user ID. Specific credentials for accessing the Tioli Monitoring SOAP serer Define each user ID that you specified for an ITM/ITCAM resource in an Agentless Adapter policy. Use the following push buttons: 110 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

129 Add To define a new user ID and password to access the SOAP Serer. Remoe To remoe an entry from the list. Select a user ID and click this button. Modify To edit the user ID or password, select an entry from the list and click this button. Note: You can define the SOAP serer security setup to accept a user ID with an empty password. For example, if you want to use the Agentless Adapter in a test enironment, you can specify the user ID for the corresponding ITM/ITCAM resource in the Agentless Adapter policy without defining it in the list of specific credentials to access the SOAP serer. In this case, the Agentless Adapter attempts to access the ITM/ITCAM resource with the user ID defined in the policy and an empty password. Security tab Use the Security tab to configure the settings for user authentication and secure data transport. You can configure the following settings: Secure Sockets Layer (SSL) for data transport: Configure Secure Sockets Layer (SSL) for data transport between the Agentless Adapter and the automation manager host. If you hae configured Application Manager high-aailability, the end-to-end automation manager and the Agentless Adapter will run on different systems. In this case you may want to configure the corresponding SSL settings to secure the data transport between those systems. Usage of the Pluggable Access Module (PAM) for user authentication: Configure user authentication between the automation manager and the Agentless Adapter with the Pluggable Access Module (PAM). User authentication with SSH public and priate keys: Configure user authentication between the Agentless Adapter and remote non-clustered nodes with SSH public and priate keys. This applies only to remote resources which are accessed using a remote execution protocol. It does not apply to ITM resources defined in the Agentless Adapter policy, because for ITM resources an existing ITM security infrastructure is reused. The user ID that you specify for a remote resource in an Agentless Adapter automation policy is used to determine how authentication is performed on the remote node where that resource resides. The Agentless Adapter separately authenticates each user ID that is specified for a remote resource in the Agentless Adapter policy. The adapter authenticates those users on remote nodes in the following sequence: 1. The user ID that is specified for a remote resource in the Agentless Adapter automation policy is defined in the Credentials for accessing specific non-clustered nodes list on the User Credentials tab: The Agentless Adapter uses the password that is associated with that specific user ID. 2. The user ID that is specified for a remote resource in the Agentless Adapter automation policy is defined as Generic user ID for non-clustered nodes on the User Credentials tab: The Agentless Adapter uses the password that is associated with that generic user ID. 3. For the user ID that is specified for a remote resource in the Agentless Adapter automation policy, user authentication is performed using SSH public and priate keys. In this case, check Enable user authentication with SSH public and priate keys and specify the SSH priate key file and passphrase. Chapter 3. Configuring 111

130 Controls and fields on the Security tab: Enable SSL for data transport between the automation manager and the Agentless Adapter Check this check box to enable the Secure Sockets Layer (SSL) protocol. For more information, refer to Securing the connection to end-to-end adapters using SSL on page 260. This enables the following entry fields. Truststore Enter the name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Enter the password for the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Note: Passwords must be identical if truststore and keystore are located in two different files. Certificate alias Enter the alias name of the certificate that is used by the serer. If not specified, the keystore file must contain only one entry which is the one to be used. Configure user authentication between the Automation Manager and the Agentless Adapter with the Pluggable Access Module (PAM). Enforce user authentication between the automation manager and the Agentless Adapter Click the check box to enable user authentication with Pluggable Access Module (PAM). If not checked, user authentication is bypassed. PAM serice The alue of the PAM serice depends on the operating system on which the Agentless Adapter runs: For SUSE Linux distributions specify a file in the directory /etc/pam For Red Hat Enterprise Linux distributions specify an entry in the file pam.d For AIX specify an entry in the file /etc/pam.conf The PAM serice determines which checks are made to perform user authentication. Examples for PAM serice names are sshd for Linux, or login for AIX. You may also use any other alue that you hae already defined as a PAM serice. Enable user authentication with SSH public and priate keys Check this check box to use SSH keys for authentication. Use SSH keys for user IDs that hae no generic or specific access credentials defined on the User Credentials tab. SSH priate key file Enter the fully qualified name of the SSH priate key file that is generated by the ssh-keygen utility. The default names of files that are generated by ssh-keygen are id_dsa or id_rsa. Ensure that the user ID under which the Agentless Adapter is running has read access for this file. Click Browse... to select a file. Priate key passphrase Enter the passphrase that you used to generate the SSH priate key file with the ssh-keygen utility. Click Change to change the passphrase. The 112 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

131 passphrase is optional, because you can omit it when using the ssh-keygen utility. Click Change to remoe a passphrase. Leae all entry fields in the dialog empty and select OK. Saing the local Agentless Adapter configuration To sae your changes to the System Automation Application Manager Agentless Adapter configuration properties files, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. If high aailability is configured for System Automation Application Manager, replicate the properties files to the other nodes in the System Automation for Multiplatforms cluster. For more information, see Replicating the configuration files on page 126. Configuring remote Agentless Adapters The System Automation Application Manager remote Agentless Adapter configuration dialog helps you to configure remote Agentless Adapter settings. To open the configuration dialog, click Configure in the Remote Agentless Adapter configuration section on the Application Manager tab of the task launcher panel. Remote Agentless Adapter configuration window Use the remote Agentless Adapter configuration window to maintain the configurations for one or multiple remote Agentless Adapter instances. The list of remote Agentless Adapter configurations shows one entry for each currently configured remote Agentless Adapter instance: Remote Agentless Adapter Host The host name of the node where the remote Agentless Adapter is installed. Configuration Directory If the remote Agentless Adapter is installed on a Unix system, the configuration directory is /etc/opt/ibm/tsamp/eez/rala/cfg. If the remote Agentless Adapter is installed on a Windows system, the configuration directory is <INSTALL_ROOT>\cfg. <INSTALL_ROOT> is the directory that you specified during the installation of the Agentless Adapter on the Windows system. Configuration Complete The configuration complete alue indicates whether the configuration for the corresponding remote Agentless Adapter instance has been completed or not. No: Initial alue after you added a new configuration. Yes: After you hae successfully completed the Configure task for the adapter instance. Note: You can distribute only completed configurations to the remote host. Click Add to add a configuration for another remote Agentless Adapter instance. A dialog opens to specify the remote node name of the host and select whether the remote host is a Windows system or not. For a Windows system, specify also the Chapter 3. Configuring 113

132 configuration directory. After you hae completed the dialog, the new configuration will be added to the list with the configuration complete alue "No". Click Remoe to remoe the selected configuration from the list. All configuration files related to that configuration will be deleted on the system where the configuration utility runs. If you hae distributed the configuration already, the configuration files on the remote host will not be deleted. Click Configure to open the configuration dialog for the selected configuration. For more information, refer to Configuring a remote Agentless Adapter instance. Click Distribute to distribute the selected configuration. For more information, refer to Distributing a remote Agentless Adapter configuration on page 116. Configuring a remote Agentless Adapter instance The content of the configuration dialog tabs and the semantics of the fields are the same as described in Configuring the local Agentless Adapter on page 107. Below you can find the description of tabs or fields that are unique for a remote Agentless Adapter configuration. To open the configuration dialog, select the entry you want to configure and click Configure in the remote Agentless Adapter configuration window. Post-configuration tasks Distribute the remote Agentless Adapter configuration to the corresponding remote Agentless Adapter host. For more information, refer to Distributing a remote Agentless Adapter configuration on page 116. If System Automation Application Manager is configured for high aailability, replicate the configuration files to the high aailability nodes of the IBM Tioli System Automation of Multiplatforms cluster. For more information, refer to Replicating the configuration files on page 126. Adapter tab Refer to Adapter tab on page 107 for a description of this tab content and the semantics of the fields on the tab. There are two differences compared to the Adapter tab for the local Agentless Adapter: Host name or IP address Host name or IP address of the node where the adapter runs. The default alue is the remote Agentless Adapter host name that you specified for this adapter instance in the remote Agentless Adapter configuration window. If you want to change this alue, for example to an IP address, make sure that the new alue refers to the host where this adapter instance is installed. Request port number The disclaimer regarding the hardware adapter does not apply to remote Agentless Adapters. User Credentials tab Refer to User Credentials tab on page 109 for a description of this tab content and the semantics of the fields on the tab. There are no differences compared to the User Credentials tab of the local Agentless Adapter. 114 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

133 Tioli Monitoring tab Refer to Tioli Monitoring tab on page 110 or a description of this tab content and the semantics of the fields on the tab. There are no differences compared to the Tioli Monitoring tab of the local Agentless Adapter. Security tab Refer to Security tab on page 111 for a description of this tab content and the semantics of the fields on the tab. The only difference compared to the Security tab for the local Agentless Adapter is the motiation to configure SSL for data transport between the automation manager and the Agentless Adapter. The end-to-end automation manager and the local Agentless Adapter run on different systems only if you hae configured Application Manager high-aailability. Remote Agentless Adapters always run on different systems. Logger tab The Logger tab is only aailable for remote Agentless Adapters. The local Agentless Adapter uses the logger settings that are defined in the Application Manager common configuration. 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: The Logger tab always displays the alues that are currently set in the configuration file. Controls and fields on the Logger tab: Maximum log/trace file size File size measured in kilobytes. Message logging leel: Error Logs messages on the error leel. Warning Logs messages on error and warning leel. Information Logs messages on error, warning, and informational leel. Trace logging leel: Off Collects no trace information. Minimum Collects trace information on error leel. Medium Collects trace information on error and warning leel. Maximum Proides message and trace logs and collects additional information on error, warning, and informational leel. First failure data capture (FFDC) settings: Recording leel: Off Collects no FFDC information. Chapter 3. Configuring 115

134 Minimum Proides message and trace logs and collects additional information on error leel. Medium Proides message and trace logs and collects additional information on error and warning leel. Maximum Proides message and trace logs and collects additional information on error, warning, and informational leel. Disk space: Maximum disk space Specifies maximum disk space measured in bytes used by FFDC traces which are written into the FFDC trace directory. The default space is bytes (10MB). Space exceeded policy Select what to do if 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 EEZA*E, meaning all adapter error messages, are allowed. Saing the remote Agentless Adapter configuration To sae your changes to the System Automation Application Manager remote Agentless Adapter configuration properties files, click Sae in the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. Note: The configuration files are located in a subdirectory of the standard configuration directory. The name of the subdirectory is the remote Agentless Adapter host name that you hae specified for this adapter instance in the remote Agentless Adapter configuration window. If high aailability is configured for System Automation Application Manager, replicate the properties files to the other nodes in the IBM Tioli System Automation for Multiplatforms cluster. For more information, refer to Replicating the configuration files on page 126. Distributing a remote Agentless Adapter configuration Use the System Automation Application Manager remote Agentless Adapter configuration distribution dialog to distribute the configuration files for a remote Agentless Adapter instance to the remote host where that adapter instance is installed. To open the configuration distribution dialog, select the entry you want to distribute and click Distribute in the remote Agentless Adapter configuration window. Proide the following input in the "remote Agentless Adapter configuration distribution" dialog 116 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

135 Remote host login user ID and password The credentials that are used to access the remote Agentless Adapter host. The specified user ID must hae write access to the configuration directory on the remote host that you hae defined for this configuration. Recycle remote Agentless Adapter after configuration distribution Check if you want the Agentless Adapter to be stopped and restarted on the remote host after the configuration distribution has been executed. This will make sure that the remote Agentless Adapter runs with the changed configuration alues. The remote Agentless Adapter is recycled only if the distribution of all configuration files completed successfully and if the adapter is currently running. Click OK to distribute the configuration. Upon completion, the Configuration distribution status window opens to show the list of configuration files that are distributed. If you selected Recycle the remote Agentless Adapter after configuration distribution, you will be informed about the result of the recycle attempt and the current status of the adapter on the remote host. Controlling Agentless Adapters Use the eezaladapter command to start, stop, and monitor Agentless Adapters. To control the local Agentless Adapter, run the command on the Application Manager serer system. To control the remote Agentless Adapters, run the command on the respectie remote host. For more information about the eezaladapter command, refer to Tioli System Automation Application Manager, Reference and Problem Determination Guide. Configuring Agentless Adapters in silent mode Configuring high aailability You can configure Agentless Adapters in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration tasks: Configuring the local Agentless Adapter Configuring remote Agentless Adapters Adding, remoing and distributing remote Agentless Adapter configurations Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. In this topic you learn how to make System Automation Application Manager highly aailable (HA) using System Automation for Multiplatforms. The System Automation Application Manager HA policy can be used to make all components needed to run System Automation Application Manager highly aailable. These components are: DB2 (optional) if running on a local machine WebSphere Application Serer System Automation Application Manager end-to-end automation manager Chapter 3. Configuring 117

136 System Automation Application Manager hardware adapter for the Distributed Disaster Recoery feature, if used System Automation Application Manager GPDS agent for the Distributed Disaster Recoery feature, if used System Automation Application Manager local Agentless Adapter, if used For all components System Automation for Multiplatforms resources and corresponding relationships will be defined. There are at least three IP addresses defined: One indiidual IP address for both nodes. One serice IP address for the cluster. Use the serice IP address once the cluster is started as the target address to open the Web-based operations console. You can use the serice IP address as target address to configure automation adapters as well. Thus the resources can be started in the proper order and are able to completely fail oer to another node if eer one resource fails on a node. The backup node can take oer the complete System Automation Application Manager workload because all nodes hae the same setup. All resources must run on the same node, except the local Agentless Adapter. Note: To configure high aailability, System Automation for Multiplatforms must be installed on all nodes. Topic Configuring the high aailability policy on page 120 describes the high aailability configuration tabs of the System Automation Application Manager configuration dialog. To open the configuration dialog, click Configure on the High Aailability tab of the task launcher panel. Post-configuration tasks: To ensure that the configuration properties are set correctly on all nodes of the System Automation for Multiplatforms domain, you must replicate the configuration files as described below. High aailability options with DB2 Scenario with shared DB2 database file system Figure 13 shows how the arious components are distributed in an end-to-end high aailability solution with a shared database: Actie node 1 Standby node 2 DB Manager DB Manager J2EE Framework DB file system J2EE Framework Automation Engine Automation Engine Figure 13. End-to-end high-aailability scenario with a shared database file system In this case, there are independent DB2 database managers on node 1 and node 2. Only one of them can be actie at a gien time. The sharing of data occurs ia a 118 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

137 shared disk. The node that has the actie DB2 manager has the shared disk mounted, whereas the other node does not hae the shared disk mounted at that time. This behaior is controlled by the end-to-end high aailability policy. Scenario with commonly used remote DB2 database Figure 14 shows how the arious components are distributed in an end-to-end high aailability solution with a remote database: Actie node 1 DB node Standby node 2 JDBC Drier DB Manager JDBC Drier J2EE Framework J2EE Framework Automation Engine Automation Engine DB file system Figure 14. End-to-end high-aailability scenario with a remote database file system In this case, there is an independent DB2 database manager on the DB node. Both System Automation Application Manager installations on node 1 and node 2 use the same remote database. This ariant is also supported by the end-to-end high aailability policy. Actiating the high aailability policy Perform the following steps to make System Automation Application Manager highly aailable: 1. Ensure all prerequisites are met. For more information, see Planning for high aailability on page Run the configuration dialog cfgeezdmn as described below to configure: a. The end-to-end automation manager. b. The System Automation Application Manager hardware adapter, if used. c. The System Automation Application Manager Agentless Adapter, if used. 3. Ensure that System Automation Application Manager works correctly when running independently on each node. Start each application on one node only and erify they work correctly. Then stop all applications on this node and repeat on the other node. 4. Stop all applications on all nodes before you actiate the System Automation Application Manager high aailability policy the first time by using the configuration dialog "Define policy" task. 5. Run the configuration dialog cfgeezdmn as described below to configure the automation policy for the end-to-end automation manager: a. Configure b. Replicate c. Set up domain only needed if no System Automation for Multiplatforms domain exists yet. Chapter 3. Configuring 119

138 d. Define policy The System Automation Application Manager high aailability policy is now actiated on the System Automation for Multiplatforms domain. Configuring the high aailability policy Click Configure on the High Aailability tab of the task launcher panel to open the high aailability policy configuration dialog. Domain Setup tab Use the Domain Setup tab to configure the parameters required for setting up the System Automation for Multiplatforms domain which you are using to proide high aailability for System Automation Application Manager. The specified parameters will be used to create the System Automation for Multiplatforms domain in the setup domain task. Controls and fields on the Domain Setup tab: Domain name The name of the System Automation for Multiplatforms 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 System Automation for Multiplatforms 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 System Automation for Multiplatforms 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 System Automation Application 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: Determining the sequence in which automation selects the node on which System Automation Application 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. 120 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

139 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. Modify To change the settings for a node, select the node, click Modify, and change the settings in the windows that is displayed. Remoe To remoe a node from the automation policy, select the node, and click Remoe. If you add or modify a node and you hae already defined a System Automation for Multiplatforms domain, specify a node name that is listed when you run the lsrpnode RSCT command. The result of the lsrpnode command is also used to prime the nodes list on the Domain Setup tab when you click the Query Domain button. Automation Manager tab Use the Automation Manager tab to configure the resources that are used to automate the end-to-end automation manager. Controls and fields on the Automation Manager tab: Automated resources prefix The prefix that precedes the names of the resources and groups in the 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 ersion Select which IP ersion you want to use for the irtual IP address in the end-to-end automation manager automation policy. Select IP4 and specify a alid ersion 4 IP address and a netmask. The netprefix field will be disabled. Select IP6 and specify a alid ersion 6 or mixed mode IP address and a netprefix. The netmask field will be disabled. Select Both and specify a alid ersion 4 as well as a alid ersion 6 or mixed mode IP address. Specify also a netmask as well as a netprefix. Note: The IP address that is used to make the automation manager highly aailable must be identical to the IP address that you specify on the Domain tab in the SA Application Manager common configuration (described in Domain tab on page 97): If you select IP4 as IP ersion, this is the ersion 4 IP address that you specify below. Otherwise, it is the ersion 6 IP address. Chapter 3. Configuring 121

140 If the automation manager is made highly aailable, you must also use the corresponding IP address in the configuration of each first-leel automation adapter as the IP address for the end-to-end automation management host. If you are using remote Agentless Adapters, it is implicitly used as IP address for the end-to-end automation management host. If this is a ersion 6 IP address, each system where a first leel automation adapter or a remote Agentless Adapter runs must proide IP ersion 6 communication capabilities. Click Query domain to automatically match the IP ersion with the defined IP address or addresses. IP4 address The irtual IP ersion 4 address that is shared by all nodes in the IBM Tioli System Automation domain and that is set for the ersion 4 IBM.SericeIP resource in the end-to-end automation manager automation policy. The irtual IP address must be authorized by your network administrator. The IP4 address is required if you select IP4 or Both as IP ersion. Otherwise this field is disabled. To prime the field with the currently defined alue, click Query domain. IP6 address The irtual IP ersion 6 address that is shared by all nodes in the IBM Tioli System Automation domain and that is set for the ersion 6 IBM.SericeIP resource in the automation manager automation policy. The irtual IP address must be authorized by your network administrator. The IP6 address is required if you select IP6 or Both as IP ersion. Otherwise this field is disabled. To prime the field with the currently defined alue, click Query domain. Netmask Enter the netmask that is set for the IBM.SericeIP resource in the automation manager automation policy. Request the address from your network administrator. The netmask is required if you select IP4 or Both as IP ersion. Otherwise this field is disabled. To prime the field with the currently defined alue, click Query domain. Netprefix Enter the netprefix that is used to define the IBM.SericeIP resource in the automation manager automation policy. Specify a numeric alue in the range between 0 and 128 to define how many bits of the IP address are portioned for the network part of that address. The netprefix is required if you selected IP6 or Both as IP ersion. Otherwise this field is disabled. To prime the field with the currently defined alue, click Query domain. Policy Pools tab Use the Policy Pool tab to configure the parameters required to automate the file system where the policy pools are located. The data is used to create the corresponding file system resources in the automation policy. The policy pools must reside on a file system that are shared by all nodes in the System Automation for Multiplatforms domain. When the automation policy is actie, they are mounted at the specified mount points. Controls and fields on the Policy Pools tab: Automation resources for the Application Manager policy pool: 122 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

141 Specify the parameters to define the policy pool where the end-to-end automation policies of the Application Manager reside. 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. Automation resources for the local Agentless Adapter policy pool: Specify the same set of parameters as for the Application Manager policy pool to define the policy pool where the Agentless Adapter policies reside. The fields for the Agentless Adapter policy pool are only enabled if Enable Agentless Adapter configuration is checked on the Application Manager tab of the task launcher panel, see Using the task launcher on page 90. Due to the AntiAffinity relationship in the high aailability policy, the automation manager and the Agentless Adapter run on different nodes. Therefore the policy pools of both components cannot be shared. In particular, the mount points for both policy pools must be different. WebSphere tab Use the WebSphere tab to configure the parameters required for automating the instance of WebSphere Application Serer that hosts the end-to-end automation manager. The data is used to create the corresponding resource in the automation policy and to monitor, start, and stop the WebSphere Application Serer. Most of the parameters are set by the installer at installation time. Controls and 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 SOAP port The number of the WebSphere Application Serer port that is used by the end-to-end automation manager. The name of this port in the WebSphere administratie console is SOAP_CONNECTOR_PORT. 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. User ID The WebSphere administrator user ID that is used to stop the WebSphere Application Serer. Chapter 3. Configuring 123

142 Password The WebSphere administrator password that is used to stop the WebSphere Application Serer. Click Change to change the password. The WebSphere administrator credentials are stored in the file properties/soap.client.props. This file is located in the profile directory. DB2 tab Use the DB2 tab to configure 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 directory, the instance owner user ID, and the instance owner mount point must be identical on all nodes of the System Automation for Multiplatforms domain for the automation policy to work. Controls and fields on the DB2 tab: Automate DB2 Select the check box to enable the entry fields on the tab. If you are using a remote DB2 database, do not select the check box. In this case the DB2 instance must not be included in the automation policy. Installation directory Specify the DB2 installation directory or click Browse to select a directory. Instance owner user ID Specify the user ID of the owner of the DB2 instance that hosts the EAUTODB database. Instance owner mount point Specify the mount point of the DB2 instance that hosts the EAUTODB database or click Browse to select a directory. Hardware Adapter tab The Hardware Adapter tab proides an indication of whether resources for the hardware adapter will be included in the application manager high-aailability policy. Including the resources for the hardware adapter will also make the hardware adapter highly aailable when you sae the configuration and perform the define policy task the next time. Note that you cannot actiely change the selection states of the radio buttons or check boxes on this panel. They correspond to the current configuration status of the hardware adapter. If you hae configured the hardware adapter, either for accessing the zenterprise HMC or for distributed disaster recoery with GDPS, the corresponding resource that represents the hardware adapter executable will be included in the automation policy. If you hae configured the hardware adapter for distributed disaster recoery with GDPS, a resource for the GDPS agent of the Application Manager will also be included in the automation policy. Agentless Adapter tab This tab indicates if a resource is included in the System Automation Application Manager automation policy to make the local Agentless Adapter highly aailable. 124 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

143 A resource for the local Agentless Adapter is included in the automation policy only if you hae checked Enable Local Agentless Adapter configuration on the Application Manager tab of the task launcher panel. For more information, refer to Using the task launcher on page 90. Note that you cannot actiely change the selection state of the radio buttons in this tab. They display the current configuration status of the local Agentless Adapter. Saing the high-aailability configuration To sae your entries, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. To ensure that the configuration properties are set correctly on all nodes of the System Automation for Multiplatforms domain, you must replicate the configuration files as described in Replicating the configuration files on page 126. Retrieing information on an actie high-aailability configuration To restore a domain configuration from a defined System Automation Application Manager high aailability policy, you can use the Query domain button on the configuration dialog. This function retriees information from most fields in the 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 if 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 or net prefix 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 Pools tab: File system type, mount point and deice name of the IBM.AgFileSystem 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. If you checked Enable local Agentless Adapter configuration on the Application Manager tab of the task launcher panel and the local Agentless Adapter is part of the currently actie policy, the same information is displayed for the file system where the Agentless Adapter policy pool is located. On the Hardware Adapter tab: If there is a mismatch between the current Hardware Adapter configuration status and the Hardware Adapter resources in the currently actie policy, a Chapter 3. Configuring 125

144 warning is displayed on this tab. An example of such a mismatch is if the Hardware Adapter is not configured, but Hardware Adapter resources are defined in the actie policy. On the Agentless Adapter tab: If there is a mismatch between the current local Agentless Adapter configuration status and the Agentless Adapter resources in the currently actie policy, a warning is displayed on this tab. An example of such a mismatch is if the local Agentless Adapter is configured, but no Agentless Adapter resource is defined in the actie policy. Synchronizing the irtual IP address and host name of the end-to-end automation domain If the Application Manager is configured to be highly aailable, the irtual IP address that you define for the automation manager must be identical to the alue that you configure for the host name of the end-to-end automation manager. The host name is defined in the Host name or IP address field on the Domain tab of the Application Manager common configuration dialog. You can sae the high aailability configuration only if both alues are identical. If you select IP4 as IP ersion, the specified irtual ersion 4 IP address is used, otherwise the specified irtual ersion 6 IP address is used. Enforcing the irtual IP address being used also for the end-to-end automation manager host name makes sure that the end-to-end automation manager can be contacted by any first-leel automation domain. On which system in the high aailability cluster the automation manager currently is actie is not releant. The host name that is configured as the end-to-end automation management host for each end-to-end automation adapter must also hae the same irtual IP address defined. The end-to-end automation management host is defined in the adapter configuration dialogs in the Host name or IP address field on the Host using adapter tab. For the System Automation for z/os automation adapter, you can find the alue of the eif-send-to-hostname parameter in the adapter properties configuration file. Replicating the configuration files If you hae configured high aailability for System Automation Application Manager, you must replicate the configuration files to the other nodes in the System Automation for Multiplatforms domain wheneer you hae made changes to the Application Manager, disaster recoery, or high-aailability configuration. To perform the task, click Replicate on the "High aailability" tab of 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 System Automation for Multiplatforms domain: 1. Select the configuration files you want to replicate or click Select all to select all configuration files in the list. 126 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

145 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. If you hae configured at least one remote Agentless Adapter instance, check the Include remote Agentless Adapter configurations for replication box. The configuration files of all currently configured remote Agentless Adapter instances will also be replicated, although they are not contained in the list of replication source files. 5. 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. Setting up the domain Use this task to set up the domain in which System Automation Application Manager is to be automated. If you will be automating System Automation Application Manager in a new System Automation for Multiplatforms 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 High aailability tab of the configuration task launcher. The Set up Domain dialog opens, 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). If you click Prepare in the Set Up Domain dialog, two actions are performed: 1. Prepare the remote node or nodes for joining the domain If you configured the System Automation for Multiplatforms domain to consist of a single node, this action is skipped and only the domain definition is performed. 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, another 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 -starts the domain (state online) Note that System Automation for Multiplatforms must be installed on all nodes that are to be included in the new domain. If other System Automation for Multiplatforms domains currently exist, they should be offline. Upon completion, a message box is displayed. Chapter 3. Configuring 127

146 Remoing the domain In order to be able to remoe the IBM Tioli System Automation for Multiplatforms 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 "High aailability" tab of the task launcher. This inokes the rmrpdomain command. Validating and storing the automation policy You can alidate the System Automation Application Manager automation policy as you hae configured it in the System Automation Application Manager high-aailability configuration window by clicking Validate&Store policy on the "High aailability" tab of 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. This task has the following main purposes: 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 for Multiplatforms to also automate your own applications, the 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, use the sampolicy command. You can use the update option -u in this case in order not to stop or remoe any resource outside the scope of the System Automation Application Manager automation policy. 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 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. 128 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

147 Defining the automation policy Click Define policy on the High Aailability tab of the configuration dialog task launcher. This creates the resources with the names as described in Table 34 on page 131. Note: If automated resources with the same name exist, their attributes will be modified according to the currently configured alues. If you specified for example, the resource- or group prefix name eez- on the Automation Manager tab, the resource group eez-rg and the resources and relationships shown in the following table will be created. Note: 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 System Automation for Multiplatforms using the sampolicy command may remoe existing definitions for the System Automation Application Manager automation policy. For example, the definition of one of the resources in Table 34 on page 131 may be remoed when a new policy for System Automation for Multiplatforms is actiated. You can first sae the currently actie policy using the sampolicy -s command, and then 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 System Automation Application Manager automation are presered and that none of your changes has an undesired effect on the currently actie System Automation Application Manager automation policy. For details, see the description of the sampolicy command in the IBM Tioli System Automation for Multiplatforms Reference.. Remoing the automation policy Clicking Remoe policy on the "High aailability" tab of 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 System Automation for Multiplatforms using the sampolicy command may remoe existing definitions for the System Automation Application Manager automation policy. For example, the definition of one of the resources listed in Table 34 on page 131 may be remoed when a new policy for System Automation for Multiplatforms is actiated. You can first sae the currently actie policy using the sampolicy -s command, and then 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 System Automation Application Manager automation are presered and that none of your changes has an undesired effect on the currently actie System Automation Application Manager automation policy. For detailed information, see the description of the sampolicy Chapter 3. Configuring 129

148 command in the System Automation for Multiplatforms Reference. Configuring high aailability in silent mode You can configure Application Manager high aailability in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration task: Configuring the automation policy for the automation manager Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. The following configuration tasks can be performed only by using the configuration dialogs or manually: Replicating the configuration files Setting up and remoing the domain Validating and storing the automation policy Defining and remoing the automation policy If you do not wish to use the configuration dialogs, refer to Performing tasks manually on page 182 for a detailed description of the tasks you can perform manually. High aailability policy using System Automation for Multiplatforms The following figure shows the System Automation for Multiplatforms high aailability policy that makes System Automation Application Manager high aailable. You can find all components inoled and its relationships and dependencies. 130 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

149 eez-ala-rg Agentless adapter StopAfter StartAfter StartAfter Policy pool AntiAffinity eez-rg eez-sr-rg eez-was-rg eez-engine-rg WebSphere Application Serer Virtual IP address End-to-end automation manager StartAfter Policy pool Start After eez-db2-rg DependsOn DependsOn StartAfter DB2 serer DependsOn DB2 mount point GDPS agent Hardware adapter Figure 15. Resource groups, resources, and their relationships The eez- prefix is the default alue and can get configured in the configuration dialog. Once the top leel group eez-rg is actiated by the operator, all applications are started in the correct sequence. All resources are automatically online. Table 34. Resources in the automation policy for the end-to-end automation manager Resource name Resource class Description eez-ala-rg IBM.ResourceGroup The resource group that comprises the Agentless Adapter resources. eez-rg IBM.ResourceGroup The top-leel group that comprises all automated resources except for Agentless Adapter resources. This top leel group always exists. eez-sr-rg IBM.ResourceGroup The group that comprises the automation manager and the WebSphere Application Serer resource. Chapter 3. Configuring 131

150 Table 34. Resources in the automation policy for the end-to-end automation manager (continued) Resource name Resource class Description 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-ip6 IBM.SericeIP The irtual IP6 address used for the WebSphere Application Serer. eez-niequ IBM.Equialency The aailable network interfaces on each node. eez-ala-rs IBM.Application Agentless Adapter eez-was-as IBM.Application WebSphere Application Serer eez-engine IBM.Application End-to-end automation manager eez-db2-rs IBM.Application DB2 serer eez-db2-rs_mount IBM.Application DB2 file system eez-hwa-rs IBM.Application End-to-end hardware adapter eez-gdpsagent-rs IBM.Application Command receier for distributed disaster recoery. eez-ala-mount IBM.AgFileSystem The policy-pool for the Agentless Adapter; only defined when the policy pool is not harested by the StorageRM. 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-ala-mount-stopsafter-alars IBM.ManagedRelationship Dependency of the Agentless Adapter policy pool on the Agentless Adapter. 132 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

151 Table 34. Resources in the automation policy for the end-to-end automation manager (continued) Resource name Resource class Description IBM.ManagedRelationship Dependency of the Agentless Adapter on the Agentless Adapter policy pool. ala-rs-startsafter-eez-was-as IBM.ManagedRelationship Dependency of the Agentless Adapter on the Websphere Application Serer using the startafter relationship. ala-rs-antiaffinity-eez-engine IBM.ManagedRelationship Dependency of the Agentless Adapter on the automation manager using the AntiAffinity relationship. eez-engine-antiaffinity-ala-rs IBM.ManagedRelationship Dependency of the automation manager on the Agentless Adapter. eez-ala-rs-startsafter-alamount db2-rs-dependson-db2- rs_mount eez-was-as-dependson-db2- rs IBM.ManagedRelationship IBM.ManagedRelationship IBM.ManagedRelationship IBM.ManagedRelationship Dependency of the DB2 serer on the file system. Dependency of the WebSphere Application Serer on DB2. Dependency of the policy pool on the automation manager. Dependency of the automation manager on the policy pool. eez-engine-startsafter-was-as IBM.ManagedRelationship Dependency of the automation manager on the WebSphere Application Serer. eez-was-as-startsafter-ip IBM.ManagedRelationship Dependency of the WebSphere Application Serer on the irtual IP address. eez-ip-dependson-niequ IBM.ManagedRelationship Dependency of the irtual IP address on the network interface. hwa-startsafter-eez-engine IBM.ManagedRelationship Dependency of hardware adapter on the automation manager. eez-shared-mount-stopsafterengine eez-engine-startsaftershared-mount gdpsagent-dependson-eezengine IBM.ManagedRelationship Dependency of the command receier on the automation manager. nettb IBM.TieBreaker Tie-Breaker defined, if IP address is specified on the domain setup page. Chapter 3. Configuring 133

152 Notes and restrictions Do not manually change any of the resources which are part of the System Automation Application Manager HA policy, for example by using a command such as chrsrc or chrel, because if you do the "Define/Remoe" policy task of the configuration dialog may not work. If you must change any policy elements use the "Validate&Store" task of the configuration dialog, copy the created policy, and make your changes within the copied policy. You can then actiate this changed policy using the sampolicy command with the update option -u. Because requests for end-to-end resources are persistent, requests are not lost when the end-to-end automation manager is moed to another node. For each first-leel automation domain that is connected to the highly aailable System Automation Application Manager, start the adapter configuration tool. Verify that on the Host Using Adapter page the Host name or IP address is set to the irtual IP address that is defined in the HA policy. This ensures that the first-leel automation adapter communicates properly with the System Automation Application Manager. This setup is independent of the node the System Automation Application Manager is started from. Test the System Automation Application Manager HA setup. For example, initiate a failoer of the System Automation Application Manager and erify that all attached end-to-end and first-leel domains can be operated from the operations console. Verify that eents are receied from each domain. The automation engine and the Agentless Adapter are supposed to run on different nodes, which is implemented by an AntiAffinity relationship in the policy. Therefore the policy pools of both components can not be shared. The mount points for both policy pools must be different. If you modify the configuration of the WebSphere Application Serer, for example changing security settings, trace settings, or deploying other applications, repeat the same configuration changes on both nodes in the high aailability cluster. Operator credentials that are used for authentication against first-leel automation domains can be stored in the Dashboard Application Serices Hub credential ault. The credential ault is not shared between the nodes in the high aailability cluster. Therefore, after a failoer of the WebSphere Application Serer, operators hae to enter their credentials again to access a first-leel automation domain. Operators can specify the number of isible rows that are displayed in the operations console. These preferences are stored in the directory <WAS_ROOT>/profiles/AppSr01/Tioli/EEZ which is not shared between the nodes in the high aailability cluster. Therefore, after a failoer of the WebSphere Application Serer, operators hae to specify preferences on the second system again if they hae been changed and differ from the default. Configuring high aailability for a disaster recoery setup on two sites In a disaster recoery setup with two sites, you can configure a System Automation Application Manager high aailability policy to control the site switch in a GDPS enironment. You can define a two-site disaster recoery setup with a System Automation Application Manager installed on each site where the actie application manager is automatically moed by Geographically Dispersed Parallel Sysplex (GDPS) if the K-System master moes. For this setup, a special type of System Automation 134 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

153 Application Manager high aailability (HA) policy is required. The HA policy enables GDPS to control the site switch of the System Automation Application Manager and keeps the EAUTODB database synchronized on both sites. Restriction: This type of System Automation Application Manager HA policy is aailable only on the Linux for System z operating system platform. The configuration of the HA policy for a disaster recoery setup differs from the regular HA policy for the following characteristics: Single Node: The HA policy for a disaster recoery setup is based on a one-node System Automation for Multiplatforms cluster. Only the hostname of that node is required, instead of a list of two or three nodes needed for the regular HA policy. A irtual IP address is not needed because the application manager cannot moe to another node within the cluster. DB2: Unlike the regular HA policy, where inclusion of DB2 is optional, the HA policy for a disaster recoery setup requires the installation of DB2 on the application manager node. DB2 thus becomes an unconditional part of the policy. GDPS agent: The GDPS agent is included in the regular HA policy only if the hardware adapter is configured to manage hardware for distributed disaster recoery with GDPS. In the HA policy for a disaster recoery setup, the GDPS agent is always included. In this configuration GDPS is used to control on which site the System Automation Application Manager is actie. Shared file systems for policy pools: No resources for shared file systems are included in the HA policy for a disaster recoery setup. A shared policy pool is not required in a single-node cluster. For information about configuring the regular HA policy, see Configuring high aailability on page 117. Configuring the high aailability policy for a disaster recoery setup Click Configure on the High Aailability tab of the task launcher panel to open the high aailability policy configuration dialog. If you are running on a Linux for System z operating system platform, you can select the disaster recoery setup type of the HA policy in addition to the regular HA policy. These options are shown in the following dialog: If you are running on a Linux for System z operating system platform, the Select Application Manager High-Aailability Setup dialog opens which lets you select which type HA policy you want to configure. The dialog offers two options: Configure the Application Manager high-aailability policy for a System Automation for Multiplatforms cluster. Select this option to configure the regular HA policy. When you click OK, the dialog described in Configuring high aailability on page 117 is displayed. Follow the procedure in that section to perform the policy configuration. Configuring the Application Manager single node high aailability policy for a disaster recoery setup Chapter 3. Configuring 135

154 Select this option to configure the HA policy for a disaster recoery setup. Click OK to proceed with the configuration. This option requires the prerequisites listed below. If these prerequisites are not satisfied, this option might be disabled. In this case, a message listing the missing configuration prerequisite is displayed in the dialog. 1. You must configure an alternate end-to-end automation management host. Specify the hostname of the other GDPS site as alternate hostname in the application manager common configuration. If this prerequisite is listed as not satisfied, refer to Configuring System Automation Application Manager on page 96, Domain tab on page Configuration of the local Agentless Adapter with the HA policy for a disaster recoery setup is not supported. You must not configure the local Agentless Adapter. If this prerequisite is listed as not satisfied, clear the corresponding check box on the task launcher panel. Refer to Using the task launcher on page 90, Non-Clustered Nodes tab on page 91. Domain Setup tab Use the Domain Setup tab to configure the parameters for setting up the System Automation for Multiplatforms domain. You use this domain to proide high aailability for System Automation Application Manager. The parameters are used to create the System Automation for Multiplatforms domain. Controls and fields on the Domain Setup tab: Domain Name Specify the name of the System Automation for Multiplatforms domain. To fill in 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. Node Name Specify the name of the System Automation for Multiplatforms node that identifies the single-node domain. If you hae already defined a System Automation for Multiplatforms domain, specify the node name that is listed as output of the lsrpnode command on that node. If the domain is online, click Query domain to fill in the field with the node of the domain. Automated resources prefix Specify the prefix used for the names of the resources and groups in the HA policy. Only ASCII characters are supported. If you 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. WebSphere tab This tab is identical to the WebSphere tab in the regular HA policy configuration. Refer to Configuring the high aailability policy on page 120, WebSphere tab on page Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

155 DB2 tab Use the DB2 tab to configure the parameters used for automating the DB2 instance that hosts the System Automation Application Manager database. These parameters are set at installation time. Usually, you are not required to change any of these alues. Controls and fields on the DB2 tab: Installation directory The DB2 installation directory. Click Browse to select a different directory. Instance owner user ID The user ID of the owner of the DB2 instance hosting the System Automation Application Manager database. Automation database name The name of the System Automation Application Manager database. Hardware Adapter tab This tab is similar to the Hardware Adapter tab of the regular HA policy configuration with the exception that there is no distinction between resources for the hardware adapter and resources for the GDPS agent. This tab displays the status of the hardware adapter resource only, because the GDPS agent is always included in the HA policy for a disaster recoery setup. Saing the high-aailability configuration To sae your entries, click Sae on the configuration dialog. Upon completion, the Configuration Update Status window is displayed. This window displays the list of updated configuration files. Retrieing information about an actie high aailability configuration To retriee information about a domain configuration from a defined System Automation Application Manager high aailability policy, use the Query domain button on the configuration dialog. This function populates the fields in the configuration notebook with the following information: On the Domain Setup tab: domain name and status (online/offline) node name On the Hardware Adapter tab: If there is a mismatch between the current hardware adapter configuration status and the hardware adapter resources in the currently actie policy, a warning is displayed in this tab. An example of such a mismatch is if the hardware adapter is not configured, but hardware adapter resources are defined in the actie policy. Other high aailability configuration tasks On the High Aailability tab of the task launcher panel, you can launch seeral other configuration tasks. For each task, see the referenced sections in Configuring high aailability on page 117 as detailed below: Replicating the configuration files If you configured the HA policy for a disaster recoery setup, the Replicate button on the task launcher panel is disabled. This task is not Chapter 3. Configuring 137

156 aailable for policies in a single-node cluster because there is no other node to which the configuration can be replicated. Setting up the domain You can perform this task for a HA policy in a disaster recoery setup, with the exception that no other cluster nodes must be prepared, because the policy is in a single-node cluster. To perform this task, refer to Setting up the domain on page 127. Remoing the domain To perform this task refer to Remoing the domain on page 128. Validating and storing the automation policy To perform this task refer to Validating and storing the automation policy on page 128. Defining the automation policy To perform this task refer to Defining the automation policy on page 129. Remoing the automation policy To perform this task refer to Remoing the automation policy on page 129. Configuring high aailability for a disaster recoery setup in silent mode You can configure System Automation Application Manager high aailability for a disaster recoery setup in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration task: Configuring the automation policy for a disaster recoery setup for the automation manager For more information, refer to Configuring in silent mode on page 181. The following configuration tasks can be performed only by using the configuration dialogs or manually: Setting up and remoing the domain. Validating and storing the automation policy. Defining and remoing the automation policy. If you do not want to use the configuration dialogs, refer to Performing tasks manually on page 182 for a detailed description of the tasks you can perform manually. High aailability policy using System Automation for Multiplatforms The following figure shows the System Automation for Multiplatforms high aailability policy for a disaster recoery setup. System Automation Application Manager becomes highly aailable, including the disaster recoery setup components. The table below shows all inoled relationships and dependencies. 138 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

157 Figure 16. Resource groups, resources and their relationships The resources of the single-node System Automation Application Manager high aailability policy for a disaster recoery setup are described in the following table. The eez- prefix is the default alue and can be set in the configuration dialog. Table 35. Resources in the high aailability policy for a disaster recoery setup Resource Name Resource class Description eez-rg IBM.ResourceGroup The resource group that comprises all System Automation Application Manager resources except DB2 eez-db2-rg IBM.ResourceGroup The resource group that comprises all DB2 resources eez-sr-rg IBM.ResourceGroup The resource group that comprises the automation manager and the WebSphere Application Serer resources eez-engine-rg IBM.ResourceGroup The resource group that comprises all automation manager resources eez-was-rg IBM.ResourceGroup The resource group that comprises all WebSphere Application Serer resources eez-gdpsagent-rg IBM.ResourceGroup The resource group that comprises the gdpsagent resources eez-hwa-rg IBM.ResourceGroup The resource group that comprises the hardware adapter resources Chapter 3. Configuring 139

158 Table 35. Resources in the high aailability policy for a disaster recoery setup (continued) eez-hadp-prim-equ IBM.Equialency The resource controlling the DB2 HADR role eez-startam-equ IBM.Equialency The resource controlling the System Automation Application Managerstate eez-was-as IBM.Application WebSphereApplication Serer eez-engine IBM.Application System Automation Application Manager automation manager eez-db2-rs IBM.Application DB2 serer eez-gdpsagent-rs IBM.Application gdpsagent eez-hwa-rs IBM.Application Hardware adapter eez-hadr-prim IBM.Application DB2 HADR role eez-startam IBM.Application System Automation Application Manager state eez-was-as-dependson-db2- rs eez-was-as_startsafter_eezstartam-equ IBM.ManagedRelationship IBM.ManagedRelationship Dependency of WebSphere Application Serer on DB2 Dependency of WebSphere Application Serer on the System Automation Application Manager state hwa-startsafter-eez-engine IBM.ManagedRelationship Dependency of the hardware adapter on the System Automation Application Manager eez-was-as_do_eez-hadrprim-equ eez-engine-startsafter-wasas gdpsagent-dependson-eezengine IBM.ManagedRelationship IBM.ManagedRelationship IBM.ManagedRelationship Dependency of WebSphere Application Serer on DB2 HADR role Dependency of the System Automation Application Manageron WebSphere Application Serer Dependency of the gdpsagent on the System Automation Application Manager Notes and restrictions When you configure high aailability for a disaster recoery setup on two sites, the following notes and restrictions apply: Do not manually change any of the resources which are part of the System Automation Application Manager HA policy, using chrsrc or chrel commands. Using these commands might cause errors in the Define or Remoe policy tasks of the configuration dialog. If you must change any policy elements, use the Validate & Store task of the configuration dialog, copy the created policy, and make your changes within the copied policy. You can then actiate this changed policy using the sampolicy command with the update option -u. Perform the configuration of the HA policy for a disaster recoery setup also on the other GDPS site. 140 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

159 Eery first-leel automation adapter or remote Agentless Adapter that is connected to the System Automation Application Manager must be able to switch its eent target if the actie System Automation Application Manager moes to the other site. In the configurations of all adapters, you must specify the System Automation Application Manager host names of both sites as the end-to-end automation management host and the alternate end-to-end automation management host. Refer to Installing for Distributed Disaster Recoery on page 72 for more information about this configuration step. Configuring Distributed Disaster Recoery To configure the Distributed Disaster Recoery feature, you need to configure the JMS destination for GDPS eents, the hardware adapter, and the TPC-R domain. Configuring the destination for GDPS eents If a GDPS serer connection or a GDPS backup serer connection is not actiated or configured during the installation of System Automation Application Manager, perform the following steps: 1. To configure the primary GDPS serer, edit the configuration file <EEZ_CONFIG_ROOT>/eez.publisher.gdps.properties a. Set the SererLocation property to the hostname of the primary GDPS serer. b. Set the SererPort property to the port number of the primary GDPS serer (typically, this is 5529). 2. Optionally: To configure the backup GDPS serer, edit the configuration file <EEZ_CONFIG_ROOT>/eez.publisher.gdpsbackup.properties analogously. 3. Restart WebSphere Application Serer, or refresh the end-to-end automation manager configuration using the end-to-end automation configuration tool. The steps aboe can also be used to modify the destination for GDPS eents. Configuring the GDPS agent To configure the GDPS agent specify the user ID and password for the end-to-end automation manager command shell in the end-to-end automation manager configuration dialog (cfgeezdmn) in the Command shell tab. The default user ID is eezadmin. Set up logging and tracing for the GDPS agent as follows: 1. The GDPS agent uses the logger to make entries in the system log. 2. The priority used is user.error for error messages and user.debug for debug information. Make sure these entries are logged at the right place using the system log configuration (syslog.conf or corresponding configuration file). Chapter 3. Configuring 141

160 Configuring synchronous communication with GDPS GDPS communicates with the end-to-end automation manager ia synchronous calls that are receied by the GPDS agent. As soon as commands are passed successfully to the automation engine they are acknowledged by the GPDS agent. To ensure that the communication between GDPS and the GDPS agent is encrypted without needing to configure a password in GDPS, Secure Shell (ssh) is used for secure communication. To ensure that an ssh client (in this case, OpenSSH in USS) is set up correctly in the USS of the GDPS K System you need to: 1. Set up the OpenSSH client configuration file 2. Set up public key authentication to aoid the specification of a password in GDPS. The priate key must be proided in the home directory of the USS user that is used to send the command ia ssh in the directory $home/.ssh/. Note also that an entry of the host key in $home/.ssh/known_hosts improes security against IP, DNS, and routing spoofing. On the end-to-end serer system, the public key must be appended to the file <user>/.ssh/authorized_keys. For more information on how to set up OpenSSH in USS, see IBM Ported Tools for z/os User's Guide, SA , which is aailable from jct03004c/serers/eserer/zseries/zos/unix/port_tools.html). Configuring the hardware adapter 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 adapter to access the zenterprise Hardware Management console (HMC) for irtual serer management using the zenterprise HMC Access tab. Note: This configuration is aailable on operating systems that are supported by System Automation Application Manager. 3. Configuring the hardware adapter to manage hardware for distributed disaster recoery with Geographically Dispersed Parallel Sysplex (GDPS), using the DR Hardware Credentials tab. Note: This configuration is supported only on Linux on System z. To open the configuration dialog, click Configure in the hardware adapter configuration section on the High Aailability tab of the task launcher panel. Post-configuration tasks: After changing any of the configuration properties, you must perform the following tasks: If you hae configured the hardware adapter to manage hardware for distributed disaster recoery with GDPS, actiate any new or changed hardware 142 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

161 access credentials by launching the Refresh task in the hardware adapter section of the Virtual Serer / HW Management tab of the task launcher (see Refreshing the actie hardware adapter configuration on page 147. If you hae configured the hardware adapter to access the zenterprise (HMC) for irtual serer management, reconnect to the HMC by launching the Refresh task. In both cases, you may alternatiely restart the hardware adapter by using the following commands: eezhwadapter -stop to stop the adapter, and eezhwadapter -start to actiate the changed configuration settings. 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. Test the hardware adapter by launching the Test task in the hardware adapter section on the Virtual Serer / HW Management tab of the task launcher (see Testing the hardware adapter on page 148). If System Automation Application Manager is configured for high aailability, you must replicate the configuration files to the other nodes of the System Automation for Multiplatforms cluster that proides the high aailability. For more information, see Replicating the configuration files on page 126. Adapter tab Use the Adapter 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 Specify the number of the port to which the hardware adapter listens for requests from the end-to-end management host. The default port is zenterprise HMC Access tab Use the zenterprise HMC Access tab to configure thesystem Automation Application Manager hardware adapter to access the zenterprise Hardware Management Console (HMC) for irtual serer management. Controls and fields on the zenterprise HMC Access tab: Manage irtual serers using the zenterprise HMC Select this check box if you want to use the hardware adapter to manage irtual serers using the zenterprise HMC. If you select this check box, the actions that are related to connecting to the zenterprise HMC will be performed when you launch the Refresh or Test tasks in the hardware adapter section on the Virtual Serer / HW Management tab of the task launcher. If this check box is not selected, the refresh and test actions that establish the connection to the zenterprise HMC are not performed and all dialog elements on this pane are disabled. Configure settings of the zenterprise HMC: Domain name The name of the zenterprise HMC domain. The name you specify in this field must be unique in the set of all automation domains you are working with. Chapter 3. Configuring 143

162 HMC host name or IP address The hostname (either the short name or the fully qualified name) or the IP address (either IP ersion 4 or IP ersion 6) of the host where the zenterprise HMC serer is installed. Configure functional user credentials to access the zenterprise HMC: The functional user credentials are used by the automation J2EE framework to access the zenterprise HMC serer through the hardware adapter. If you select the Use functional user credentials for authentication button, these credentials are also used for each user request to access the zenterprise HMC through the hardware adapter. Functional user ID Specify the functional user ID for the automation J2EE framework Functional password Specify the password of the functional user ID for the automation J2EE framework. Click Change to change the current password. Configure the mode of authentication for accessing the zenterprise HMC: Enforce user authentication for all user interfaces If you select this button, credentials must be aailable or explicitly defined for each user who wants access to the zenterprise HMC through the hardware adapter. This applies for all user interfaces that support access to the zenterprise HMC through the hardware adapter. Use functional user credentials for authentication in command shell, enforce user authentication for all user interfaces If you select this button, credentials of the functional user ID described aboe are used by the J2EE automation framework and for each user request to access the zenterprise HMC through the hardware adapter using the eezcs command. Credentials must be aailable or explicitly defined for each user who wants to access the zenterprise HMC through any other user interface, for example, the operations console. Use functional user credentials for authentication for all other user interfaces If you select this button, credentials of the functional user ID described aboe are used by the J2EE automation framework and for each user request to access the zenterprise HMC through the hardware adapter. This applies for all user interfaces that support access to the zenterprise HMC through the hardware adapter. Configure Secure Sockets Layer (SSL) for communication with the zenterprise HMC: Truststore Specify the name of the truststore file used for SSL. Click Browse to select the truststore file. Truststore password Specify the password of the truststore file. Click Change to change the current password. Note: The steps for creating a trustsore and importing the zhmc certificate are described in zenterprise Hardware Management Console on page Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

163 DR Hardware Credentials tab Use the DR Hardware Credentials tab to configure the hardware access credentials that are used by the System Automation Application Manager hardware adapter. Controls and fields on the DR Hardware Credentials tab Manage hardware for distributed disaster recoery with GDPS Select this check box if you want to use the adapter to manage hardware for distributed disaster recoery with GDPS. If you select this check box, the actions related to the configured hardware access credentials are performed when you launch the Refresh or Test tasks in the hardware adapter section on the Virtual Serer / HW Management tab of the task launcher. If you do not select this check box, the refresh and test actions are not performed and all buttons related to modifying the contents of the hardware lists on this pane are disabled. Note: The configuration of hardware access credentials is aailable only on a subset of the supported platforms for the hardware adapter. If you run the configuration on an operating system platform that is not supported by this configuration task, the check box is disabled. 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 146. Adding credentials: Use this dialog to define access credentials for hardware units that hae not yet been defined in a disaster recoery policy. 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. Chapter 3. Configuring 145

164 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. 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. 146 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

165 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. 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 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 hardware adapter configuration files, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. If you hae configured high aailability for System Automation Application Manager, you must replicate the properties files to the other nodes in the System Automation for Multiplatforms cluster (see Replicating the configuration files on page 126). Refreshing the actie hardware adapter configuration When you click Refresh in the hardware adapter section of the Virtual Serer / HW Management tab of the configuration dialog task launcher, the actions performed depend on the functionality you configured for the hardware adapter: If you configured the adapter to manage hardware for distributed disaster recoery with GDPS, new or changed hardware access credentials are automatically reloaded by the hardware adapter, without the need to restart it. If you apply any changes to the configuration of the hardware access credentials, you must always request a refresh. If you configured the hardware adapter to manage irtual serers using the zenterprise HMC, no refresh function is aailable. Chapter 3. Configuring 147

166 Note: If you hae changed any other settings of the System Automation Application Manager configuration, you must restart the hardware adapter using the commands eezhwadapter -stop and eezhwadapter -start to make those changes become actie. Testing the hardware adapter When you click Test in the hardware adapter section on the Virtual Serer / HW Management tab of the configuration dialog task launcher, the actions performed depend on the functionality you configured for the hardware adapter. If you configured the adapter to manage hardware for distributed disaster recoery with GDPS, the hardware access credentials are tested without actually powering on or off the target hardware systems. Use this task after you configure the hardware access credentials. The hardware adapter must be running and a disaster recoery policy must be loaded. The test task performs the following actions: Checks whether credentials are specified for boxes and slots and issues warnings if credentials are missing. Checks whether hardware management tasks for powering on and off are present for each slot and issues warnings if tasks are missing. Checks whether the working directories for script execution exist and can be read and raises exceptions if this is not the case. Executes each script defined in the disaster recoery policy with the test option and raises exceptions if errors are found. Executes each SNMP task as a GET operation. This reads the power status of the node from SNMP and raises exceptions if errors are found. If any warnings or exceptions are issued, the corresponding messages are collected and presented in a dialog. Note: Some aspects of the disaster recoery setup cannot be tested without actually powering on and off systems. For example, for SNMP, the user ID might be authorized to read the power status of the node, but not to change it. The test option of the scripts may succeed while normal operation may fail. For this reason, real fire-drill tests are required for the hardware adapter. If you configured the hardware adapter to manage irtual serers using the zenterprise HMC, the connectiity to the zenterprise serer is tested. The following actions are performed: The configured host name or IP address used by the interface to connect to the zenterprise HMC are erified The ersions of the zmanager communication interface used by the Application Manager and the zenterprise HMC are checked for compatibility Logon to zmanager using the configured functional credentials Logoff from zmanager The zenterprise HMC test function can be performed een if the hardware adapter is not up and running. You must always use the test function after you change the functional credentials that are used to access the zenterprise HMC, or its host name or IP address. 148 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

167 If you configured the hardware adapter to be used for both tasks, both test functions will be performed in the sequence described aboe. Configuring the hardware adapter in silent mode You can configure the hardware adapter in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration tasks: Configuring the hardware adapter Refreshing the actie hardware adapter configuration Testing the hardware adapter Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. Configuring the TPC-R domain To open the configuration dialog, click Configure on the Storage Replication tab of the task launcher panel. Post-configuration tasks: After modifying any of the configuration properties, you must actiate new or modified TPC-R domain settings by launching the Refresh task in the TPC-R domain section on the Storage Replication tab of the task launcher. TPC-R Domain configuration window Use this window to configure the settings for the TPC-R domain and the user credentials to access the corresponding TPC-R serers. List of TPC-R domain settings This list shows the currently defined TPC-R domain and its properties. Use the Add button to display the Add TPC-R Domain dialog that lets you add a TPC-R domain with the settings of the corresponding TPC-R serers and the user credentials to access those serers. For more details, see Adding TPC-R domain. Note: With the current release of System Automation Application Manager, the configuration of only one TPC-R domain is supported. Use the Modify button to display the Change TPC-R Domain Settings dialog that lets you change the settings of the TPC-R serers that are associated with the domain and the user credentials to access those serers. For more details, see Changing TPC-R domain settings on page 151. Adding TPC-R domain: Use this dialog to add a TPC-R domain with the settings of the corresponding TPC-R serers and the user credentials to access those serers. Chapter 3. Configuring 149

168 Fields on the Add TPC-R Domain dialog: Domain name The host name of the new domain that you want to add. TPC-R serer one settings Hostname or IP address The name or IP address of the TPC-R serer one that is used for this domain. Communication port number The port number that is used by System Automation Application Manager to communicate with the TPC-R serer one. The default port number is Web-GUI port number The secure port number that is used to access the Web-GUI of the TPC-R on serer one. It is used by System Automation Application Manager to proide launch-in-context capabilities from the System Automation Operations Console to the TPC-R GUI. The default port is Use the following URL to erify the port number: If the TPC-R serer one is up and running, the welcome screen of TPC-R opens. TPC-R serer two settings Hostname or IP address The host name or IP address of the TPC-R serer two that is used for this domain. The serer two host name or IP address is optional. Communication port number The port number that is used by System Automation Application Manager to communicate with TPC-R serer two. The default port number is The serer two port number is optional. Web-GUI port number The secure port number that is used to access the Web-GUI of TPC-R on serer two. It is used by System Automation Application Manager to proide launch-in-context capabilities from the System Automation Operations Console to the TPC-R GUI. The default port is The serer two GUI port number is optional. Use the following URL to erify the port number: If the TPC-R serer two is up and running, the welcome screen of TPC-R opens. Credentials for accessing TPC-R serers User ID The user ID that is used by System Automation Application Manager to access the specified TPC-R serer one. If you hae specified also a serer two, the same user ID is used to access both serers. 150 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

169 This user ID is required for TPC-R. Make sure to configure the TPC-R user ID role Operator for all replication sessions that are managed with System Automation Application Manager using replication references. You can assign this role in the Tioli Storage Productiity Center for Replication. Password The password that is used by System Automation Application Manager to access the specified TPC-R serer. If you hae specified also a serer two, the same password is used to access both serers. Password confirmation Identical alue as specified in the password field to confirm password correctness. Port numbers must match what you hae defined for the TPC-R configuration in: <TPC_R_INSTALL_DIR>/eWAS/profiles/CSM/properties/rmserer.properties Parameters: communications.port = <PORT_NUMBER> WC_defaulthost_secure = <GUI_PORT_NUMBER> on the respectie TPC-R serer. Because definition of a serer two is optional, you can leae the corresponding serer host name name and port fields empty, but if you specify a serer two host name or IP address, you must also specify the port numbers. Click OK to add the domain and the settings that you hae specified to the domain list on the TPC-R Domain Configuration window and closes this dialog. Click Cancel to close this dialog without adding the specified TPC-R domain. Changing TPC-R domain settings: Use the Modify TPC-R Domain Settings dialog to change the settings for a selected TPC-R domain. The entry fields in this dialog are primed with the alues of the selected domain. See Adding TPC-R domain on page 149 for a description of the fields, with the exception of the domain name which cannot be changed and is displayed as an output field. Saing the TPC-R domain configuration To sae your changes to the TPC-R configuration files, click Sae in the TPC-R domain configuration. window. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. If you hae configured high aailability for System Automation Application Manager, you must replicate the properties files to the other nodes in the System Automation for Multiplatforms cluster (see Replicating the configuration files on page 126). Chapter 3. Configuring 151

170 Refreshing the TPC-R domain settings Click Refresh in the TPC-R section on the Storage Replication tab of the configuration dialog task launcher to trigger that the TPC-R domain configuration settings are reloaded into the running system. Repeat this procedure after any changes made to the TPC-R domain properties or credentials. The domain properties to define the TPC-R serer one and serer two host and ports that are currently stored in the end-to-end automation database are refreshed with the alues that are stored in the corresponding TPC-R configuration file. The currently actie sessions with any TPC-R serer are recycled to pick up a fresh copy of the access credentials from the configuration file. Testing the TPC-R domain configuration Click Test in the Storage Replication tab of the configuration dialog task launcher to trigger that the currently defined TPC-R domain configuration settings are alidated. You can walk through the following steps, if you change any of the TPC-R domain configuration properties: Test the configuration settings that are currently stored in the configuration files. This requires that the TPC-R serer(s) is (are) set up according to the configuration settings in those configuration files. If the test was successful, refresh the currently actie configuration with the changed configuration alues. The test task performs the following actions for the defined TPC-R domain: Establish a connection to the TPC-R serer one host Establish a connection to the TPC-R serer two host if a serer two is configured. Validate the defined user credentials for accessing TPC-R serer one. Validate the defined user credentials for accessing TPC-R serer two if a serer two is configured. Configuring the TPC-R domain in silent mode You can configure the TPC-R domain in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration tasks: Configuring the TPC-R domain Refreshing the actie TPC-R domain configuration Testing the TPC-R domain configuration Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. Configuring the HACMP adapter You can configure the HACMP adapter using the configuration dialog or inoking silent configuration. 152 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

171 The following figure shows in which enironments the HACMP adapter can work and what needs to be configured for the adapter. WebSphere Application Serer End-to-end management Eent port 2002 Host name or serice IP label Request port ip1 EIF 2001 HACMP adapter RSCT/HACMP HACMP cluster nodes Node-1 RSCT/HACMP Node-2 Figure 17. Configuration of the HACMP adapter You must configure the adapter for end-to-end automation management using System Automation Application Manager. You can also configure the HACMP adapter in silent mode using an input properties file. See Inoking silent configuration on page 183 for more details. Inoking the HACMP adapter configuration dialog The cfghacadapter command inokes the HACMP adapter configuration dialog, configures the HACMP adapter in silent mode, or generates an input properties file for silent configuration. The HACMP adapter can be configured with the cfghacadapter utility, which can run in two different modes. Graphical mode: You can use an X-Windows application 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. Chapter 3. Configuring 153

172 Silent mode: This mode does not require X-Windows serer capabilities. 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: Figure 18. HACMP Adapter: Automation Adapter Configuration Dialog The dialog lets you perform the following tasks: Click Configure to open the configuration dialog for the HACMP adapter. For more information, see Configuring the HACMP adapter settings. Click Replicate to replicate the HACMP adapter configuration files to other nodes. For more information, see Replicating the configuration files to other nodes in the domain on page 161. Click Define to define the HACMP adapter automation policy to create the resources required to automate the adapter. For more information, see Defining the HACMP adapter automation policy on page 161. Click Remoe to remoe the HACMP adapter automation policy. For more information, see Remoing the HACMP adapter automation policy on page 162. Configuring the HACMP adapter settings Learn how to configure the HACMP adapter using the configuration dialog. 154 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

173 On the main panel of the configuration dialog, click Configure to display the configuration tabs. In the following description, the term Host using the adapter is used to refer to the end-to-end automation manager host. Adapter tab Use the Adapter tab to configure the parameters of the automation adapter host. Controls and fields on the Adapter tab: 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 156). Request port number Specify the port number on which the adapter listens for requests from the end-to-end automation management host. The default port is Click Adanced to specify the adapter runtime behaior: Adapter stop delay Define the time measured in seconds within which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You can increase the alue on slow systems. The alue ranges between 3 through 60 seconds. Remote contact actiity interal Define the time measured in seconds, after which the adapter will stop if it was not contacted by the end-to-end automation management host, 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 Define the time measured in minutes, within which the adapter will attempt to contact the end-to-end automation management host 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. Enable EIF eent caching Select this check box to actiate eent caching. EIF reconnect attempt interal Define the time measured in seconds, that the adapter will wait before it attempts to reestablish the connection to the end-to-end automation management host after the connection was interrupted. The default alue is 30 seconds. Chapter 3. Configuring 155

174 Host Using Adapter tab Use the Host Using Adapter tab to configure the end-to-end automation manager host the adapter connects to. Fields on the Host using adapter tab: Host name or IP address The name or IP address of the host on which the end-to-end automation manager runs. Alternate host A alue for this field is optional. If you hae configured a disaster recoery setup with two different sites for the System Automation Application Manager, the end-to-end automation manager may run on either site. To support such a setup, also specify the host name or IP address of the second site. In case of an Application Manager site switch, this will ensure that the adapter switches seamlessly to the new actie end-to-end automation manager instance as the target for sending eents. Eent port number The port to which the end-to-end automation manager listens for eents from the HACMP adapter. 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. The default port is Note: If the communication between the end-to-end automation adapter and the end-to-end automation management host uses IP6, then the following restrictions apply. For the communication from the adapter to the host using the adapter: 1. If an IP6 host name is specified in the configuration of the end-to-end automation management host, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the end-to-end automation management host. For the communication from the end-to-end automation management host to the adapter: 1. If an IP6 host name is specified in the configuration of the adapter host, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the adapter host. Use the command host -n -a <ip6_hostname> to check the DNS lookup records. Automation tab Use the Automation tab to 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. Controls and fields and controls on the Automation tab: 156 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

175 Automate adapter in first-leel automation domain Select this check box (see also Automating the HACMP adapter on page 26). 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 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 161. 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 Chapter 3. Configuring 157

176 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. Security tab Use the Security tab to configure security settings for the interface between the HACMP adapter and the System Automation Application Manager host. Controls and fields on the Security tab: Secure Sockets Layer (SSL) protocol for data transport: Enable SSL Check this check box to enable the Secure Sockets Layer (SSL) protocol. For more information, see Securing the connection to end-to-end adapters using SSL on page 260. This enables the following entry fields. Truststore Enter the name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Enter the name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore password Enter the password of the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Note: Passwords must be identical if truststore and keystore are located in two different files. Certificate alias Enter the 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 with Pluggable Access Module (PAM): Enforce user authentication Click the check box to enable user authentication with Pluggable Access Module (PAM). If not checked, user authentication is bypassed. You can select the corresponding check box to enforce authentication of the user ID on behalf of which the end-to-end automation management host requests operations from the HACMP adapter. PAM serice The PAM serice file /etc/pam.conf determines which checks are made to perform user authentication. 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 configure the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. 158 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

177 Note: 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. 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 Logs messages on the error leel. Warning Logs messages on the error and warning leels. Information Logs messages on the error, warning and informational leels. Trace logging leel: Off Collects no trace information. Minimum Collects trace information on the error leel. Only seere error situations are traced. This is the default setting. Medium Collects trace information on the error and warning leels. Chapter 3. Configuring 159

178 Maximum 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 bytes (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 Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. 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 HACMP adapter configuration To sae your changes to the adapter configuration files, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. Note: 160 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

179 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 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. Replicating the configuration files to other nodes in the domain After configuring an HACMP adapter on a node, you can 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. Use the Replication Configuration Files 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 Automated resources prefix on page 157. 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 36. 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 Chapter 3. Configuring 161

180 Table 36. Resources in the HACMP adapter automation policy (continued) Resource class Resource name Description IBM.HacmpAppMonitor hacadapter_mon Command: hacadapter status 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. When processing is complete, 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 Automated resources prefix on page 157). 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 36 on page 161. 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 popup window. Configuring the HACMP adapter in silent mode You can configure the HACMP adapter in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration task: Configuring the HACMP adapter Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. The following configuration tasks can be performed only by using the configuration dialogs or manually: Replicating the HACMP adapter configuration files Defining and remoing the HACMP adapter automation policy If you do not wish to use the configuration dialogs, refer to Performing tasks manually on page 182 for a detailed description of the tasks you can perform manually. 162 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

181 Controlling the HACMP adapter Configuring the FOC adapter You use the hacadapter command to start, stop, and monitor the adapter. For a description of the hacadapter command options, refer to IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide Use the adapter configuration dialog to configure your FOC adapter. If your FOC adapter is highly aailable, configure the adapter on one node and replicate the configuration files to the remaining cluster nodes. Inoking the FOC adapter configuration dialog The cfgmscsadapter command inokes the FOC adapter configuration dialog, configures the FOC adapter in silent mode, or generates an input properties file for silent configuration. 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 C:\Program Files\IBM\tsamp\eez\mscs\bin Note: On Windows Serer 2012, 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 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: Chapter 3. Configuring 163

182 Figure 19. Main panel of the FOC Automation Adapter Configuration dialog Click Configure to open a configuration dialog. For more information, see Configuring the FOC adapter settings. Click Replicate to replicate the configuration files to the other nodes. For more information, see Replicating the configuration files to other nodes in the domain on page 169 Configuring the FOC adapter settings On the main panel of the configuration dialog, click Configure to display the configuration tabs. In the following description, the term Host using the adapter is used to refer to the end-to-end automation manager host. Adapter tab Use the Adapter tab to configure the parameters of the host system on which the adapter is running and the parameters required for the automation domain. Controls and fields on the Adapter tab: Automation adapter host Host name or IP address If the FOC adapter is highly aailable, specify the network name or IP address you obtained as described in Planning and preparing for an highly aailable FOC adapter on page 30. If the FOC 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 requests from the end-to-end automation management host. The default port is Automation domain 164 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

183 The domain name is the name by which the Microsoft FOC cluster is known to the end-to-end automation management host. 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: You can use the Microsoft FOC 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 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 Microsoft FOC cluster name as domain name, for example, because it would not be unique, you can specify a domain name for the Microsoft FOC cluster. Click Adanced to specify the adapter runtime behaior: Adapter stop delay Define the time period measured in seconds within which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You can increase the alue on slow systems. The alue ranges between 3 through 60 seconds. Remote contact actiity interal Define the time period measured in seconds, after which the adapter will stop if it was not contacted by the end-to-end automation management host, 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 Define the time period measured in minutes, within which the adapter will attempt to contact the end-to-end automation management host 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. Enable EIF eent caching Select this check box to actiate eent caching. EIF reconnect attempt interal Define the time period measured in seconds for the adapter to reestablish the connection to the end-to-end automation management host after the connection is interrupted. The default alue is 30 seconds. Host Using Adapter tab Use the Host Using Adapter tab to configure the end-to-end automation manager host the adapter connects to. Fields on the Host using adapter tab: Host name or IP address The name or IP address of the host on which the end-to-end automation manager runs. Alternate host A alue for this field is optional. If you hae configured a disaster recoery setup with two different sites for the System Automation Application Chapter 3. Configuring 165

184 Manager, the end-to-end automation manager may run on either site. To support such a setup, also specify the host name or IP address of the second site. In case of an Application Manager site switch, this will ensure that the adapter switches to the new actie end-to-end automation manager instance as the target for sending eents. Eent port number The port on which the end-to-end automation manager listens for eents from the FOC adapter. 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. The default port is Note: If the communication between the end-to-end automation adapter and the end-to-end automation management host uses an IP6 IP ersion, then the following restrictions apply. For the communication from the adapter to the host using the adapter: 1. If an IP6 host name is specified in the configuration of the end-to-end automation management host, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the end-to-end automation management host. For the communication from the end-to-end automation management host to the adapter: 1. If an IP6 host name is specified in the configuration of the adapter host, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the adapter host. Use the command nslookup <hostname> [<dns serer>] to check the DNS lookup records. Security tab Use the Security tab to configure security settings for the interface between the FOC adapter and the System Automation Application Manager host. Controls and fields on the Security tab: Secure Sockets Layer (SSL) protocol for data transport: Enable SSL Check this checkbox to enable the Secure Sockets Layer (SSL) protocol. for more information, refer to Securing the connection to end-to-end adapters using SSL on page 260. This enables the following entry fields. Truststore Enter the name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Enter the name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. 166 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

185 Keystore password Enter the password of the keystore file. It is required if a keystore file was specified. Click Change to change the password. Note: If the truststore is in different file than keystore, the passwords for the files must be identical. Keystore alias 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 You can select the corresponding check box to enforce authentication of the user ID on behalf of which the end-to-end automation management host requests operations from the FOC adapter. Logger tab Use the Logger tab to configure the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Note: 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 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. Controls and fields on the Logger tab: Maximum log/trace file size The file size in kilobytes. Chapter 3. Configuring 167

186 Message logging leel: Error Logs messages on the error leel. Warning Logs messages on the error and warning leels. Information Logs messages on the error, warning and informational leels. Trace logging leel: Off Collects no trace information. Minimum Collects trace information on the error leel. Medium Collects trace information on the error and warning leels. Maximum 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 bytes (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. 168 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

187 Saing the FOC adapter configuration To sae your settings to the adapter configuration files, click Sae. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. Note: 1. When entries are missing or a alue you entered is out of range (for example, a port number), an error message is displayed. 2. If not noted otherwise, you must restart the adapter for the changes to become effectie. Replicating the configuration files to other nodes in the domain If your FOC 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. Use the Replicate Configuration Files window to distribute (replicate) the FOC adapter configuration itself or configuration updates to other nodes in the Microsoft FOC 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. Configuring the FOC adapter in silent mode You can configure the FOC adapter in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration task: Configuring the FOC adapter Refer to Configuring in silent mode on page 181 for a detailed description of the silent mode configuration tasks. Chapter 3. Configuring 169

188 The following configuration task can be performed only by using the configuration dialogs or manually: Replicating the FOC adapter configuration files If you do not wish to use the configuration dialogs, refer to Performing tasks manually on page 182 for a detailed description of the tasks you can perform manually. Proiding high aailability for the FOC adapter Configuring the VCS adapter 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 FOC 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 FOC adapter must hae been installed successfully on all failoer cluster nodes before. Click "Next". 4. On the "Client Access Point" panel, specify a alid new network name under which the FOC adapter will be reachable. It must be ensured that the automation manager to which the FOC adapter will connect is able to resole this network name. If you do not want to use a network name for the FOC adapter, specify a dummy name here and remoe it later. Specify a alid IP address on which the FOC adapter can be reached. You must ensure that the automation manager to which the FOC 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 an highly aailable FOC adapter on page 30. Click "Next". 5. On the "Select Storage" panel do not select any storage olumes, as the FOC adapter does not require any. Click "Next". 6. On the "Replicate Registry Settings" panel do not specify any registry keys, as the FOC 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". You can configure the VCS adapter using the configuration dialog or inoking silent configuration. The following figure shows in which enironments the VCS adapter can work and what needs to be configured for the adapter. 170 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

189 WebSphere Application Serer End-to-end management Eent port 2002 Host name or serice IP label Request port Ip EIF SSL 2001 VCS adapter VERITAS Cluster Serer VCS cluster nodes Node-1 VERITAS Cluster Serer Figure 20. Configuration of the VCS adapter Node-2 You must configure the adapter for end-to-end automation management using System Automation Application Manager. You can also configure the VCS adapter in silent mode using an input properties file. See Inoking silent configuration on page 183 for more details. Inoking the VCS adapter configuration dialog The cfgcsadapter command inokes the VCS adapter configuration dialog, configures the VCS adapter in silent mode, or generates an input properties file for silent configuration. The VCS adapter can be configured with the cfgcsadapter utility. Note: 1. The GUI mode of 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. On systems without X-Windows Serer capability the usage of the silent mode is aailable. Chapter 3. Configuring 171

190 2. The 32-bit ersion of Jaa 1.4 or Jaa 5 Serice Release 5 or higher 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. To open the configuration dialog, issue the command cfgcsadapter. The main panel of the dialog is displayed: Figure 21. VCS Automation Adapter Configuration dialog Click Configure to open the configuration dialog. For more information, see Configuring the VCS adapter settings on page 173 Click Replicate to replicate the configuration files to other nodes. For more information, see Replicating the configuration files to other nodes in the domain on page 180 Click Define to define the VCS adapter automation policy. This automation policy creates the resources to automate the adapter. For more information, see Defining the VCS adapter automation policy on page 180 Click Remoe to remoe the VCS adapter automation policy. For more information, see Remoing the VCS adapter automation policy on page Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

191 Configuring the VCS adapter settings On the main panel of the configuration dialog, click Configure to display the configuration tabs. In the following description, the term Host using the adapter is used to refer to an end-to-end automation manager host. Adapter tab Use the Adapter tab to configure the parameters of the automation adapter host. Controls and field 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 175). Request port number Specify the port number 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 end-to-end automation management host. 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: Use the VCS cluster name You can 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 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. Specify a 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. Click Adanced. A dialog opens to specify the adapter runtime behaior: Adapter stop delay Define the time measured in seconds within which the adapter stop is delayed to allow the adapter to properly delier the domain leae eent. The default alue is 5. You can increase the alue on slow systems. The alue ranges between 3 through 60 seconds. Chapter 3. Configuring 173

192 Remote contact actiity interal The time period, in seconds, after which the adapter will stop if it was not contacted by the end-to-end automation management host, 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 Define the time measured in minutes, within which the adapter will attempt to contact the end-to-end automation management host 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. Enable EIF eent caching Select this check box to actiate eent caching. EIF reconnect attempt interal Define the time for the adapter to reestablish the connection to the end-to-end automation management host after the connection is interrupted. The default alue is 30 seconds. Host Using Adapter tab Use the Host Using Adapter tab to configure the end-to-end automation manager host the adapter connects to. Fields on the Host using adapter tab: Host name or IP address The name or IP address of the host on which the end-to-end automation manager runs. Alternate host A alue for this field is optional. If you hae configured a disaster recoery setup with two different sites for the System Automation Application Manager, the end-to-end automation manager may run on either site. To support such a setup, also specify the host name or IP address of the second site. In case of an Application Manager site switch, this will ensure that the adapter switches seamlessly to the new actie end-to-end automation manager instance as the target for sending eents. Eent port number The port on which the end-to-end automation manager listens for eents from the VCS adapter. 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. The default port is Note: If the communication between the end-to-end automation adapter and the end-to-end automation management host uses an IP6 IP ersion, then the following restrictions apply. For the communication from the adapter to the host using the adapter: 1. If an IP6 host name is specified in the configuration of the end-to-end automation management host, the DNS serer must be configured to return IP6 records only. 174 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

193 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the end-to-end automation management host. For the communication from the end-to-end automation management host to the adapter: 1. If an IP6 host name is specified in the configuration of the adapter host, the DNS serer must be configured to return IP6 records only. 2. If the DNS serer is configured to return IP4 and IP6 records, only the IP4 address is used. In case you want to use IP6, explicitly specify the IP6 address instead of the host name in the configuration of the adapter host. Use the command nslookup <hostname> [<dns serer>] to check the DNS lookup records. Automation tab Use the Automation tab to configure the adapter automation policy. This allows you to make the end-to-end automation adapter highly aailable. 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. Controls and fields on the Automation tab: Automate adapter in first-leel automation domain Select this check box (see also Automating the VCS adapter on page 33). 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 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 Chapter 3. Configuring 175

194 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 180. 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 end-to-end automation management host. 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: Figure 22. Warning message: Inconsistent IP Addresses 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. 176 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

195 Security tab Use the Security tab to configure the security settings for the interface between the VCS adapter and the System Automation Application Manager host. Controls and fields on the Security tab: Secure Sockets Layer (SSL) protocol for data transport: Enable SSL Check this checkbox to enable the Secure Sockets Layer (SSL) protocol. For more information, see Securing the connection to end-to-end adapters using SSL on page 260. This enables the following entry fields. Truststore Enter the name of the truststore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore Enter the name of the keystore file used for SSL. The file name may contain multiple period characters. Click Browse to select a file. Keystore password Enter the password for the keystore file. The password is required if a keystore file was specified. Click Change to change the password. Note: Passwords must be identical if truststore and keystore are located in two different files. Certificate alias Enter the alias name of the certificate that is used by the serer. If not specified, the keystore file must contain only one entry which is the one to be used. User authentication with Pluggable Access Module (PAM): Enforce user authentication Click the check box to enable user authentication with Pluggable Access Module (PAM). If not checked, user authentication is bypassed. You can select the corresponding check box to enforce authentication of the user ID on behalf of which the end-to-end automation management host requests operations from the VCS adapter. PAM serice The PAM serice file /etc/pam.conf determines which checks are made to perform user authentication. 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 configure the settings for logging, tracing, and First Failure Data Capture. You can change the settings permanently or temporarily. Note: 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. Chapter 3. Configuring 177

196 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. 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 Logs messages on the error leel. Warning Logs messages on the error and warning leels. Information Logs messages on the error, warning and informational leels. Trace logging leel: Off Collects no trace information. Minimum Collects trace information on the error leel. Only seere error situations are traced. This is the default setting. Medium Collects trace information on the error and warning leels. Maximum 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. 178 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

197 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 bytes (10 MB). 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 Initiates the tracing of FFDC data depending on the message IDs listed in Message ID list. 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 VCS adapter configuration To sae your changes to the adapter configuration files, click Sae on the configuration dialog. Upon completion, a configuration update status window is displayed, showing which configuration files were updated. If errors occurred during the update, the corresponding error messages are also displayed. Note: 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 3. Configuring 179

198 Replicating the 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. Use the Replicate Configuration Files 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 the resource name (Resource-/group prefix) as described on page Automated resources prefix on page 176. 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 37. 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. When processing is complete, the results of the commands are displayed in a popup window. 180 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

199 Remoing the VCS adapter automation policy You typically use the Remoe function before you change the name prefix of the automated resources (see page Automated resources prefix on page 176). 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 37 on page 180. 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 popup window. Configuring the VCS adapter in silent mode You can configure the VCS adapter in silent mode as an alternatie to using the configuration dialogs. You can use the silent mode to perform the following configuration task: Configuring the VCS adapter Refer to Configuring in silent mode for a detailed description of the silent mode configuration tasks. The following configuration tasks can be performed only by using the configuration dialogs or manually: Replicating the VCS adapter configuration files Defining and remoing the VCS adapter automation policy If you do not wish to use the configuration dialogs, refer to Performing tasks manually on page 182 for a detailed description of the tasks you can perform manually. Controlling the VCS adapter Configuring in silent mode You use the csadapter command to start, stop, and monitor the adapter. For a description of the csadapter command options, refer to IBM Tioli System Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide Using the configuration tool in silent mode allows you to configure System Automation Application Manager and the end-to-end automation adapters without inoking the configuration dialogs. If you use the silent configuration mode, 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: Chapter 3. Configuring 181

200 System Automation Application Manager (including Agentless Adapter, high-aailability and Distributed Disaster Recoery feature configuration) The HACMP end-to-end automation adapter The FOC 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. 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 187) and re-inoke the configuration tool. Performing tasks 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 System Automation Application 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 System Automation for Multiplatforms cluster wheneer you hae made changes to the configuration of one of the System Automation Application Manager components. To do this, you must run the configuration tool in silent mode with identical input properties files on each system. 2. Some of the tasks that are described in Configuring high aailability on page 117. 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 these tasks, do the following: a. Issue the preprpnode command on all nodes that you specified when configuring the System Automation Application Manager high-aailability, except the node where you ran the configuration tool in silent mode. 182 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

201 b. Inoke the script eezha -createdomain <EEZ_CONFIG_ROOT>/ eezautomate.properties on the local node to perform all remaining actions to set up the cluster. Remoe the domain. Inoke the script eezha -deletedomain <EEZ_CONFIG_ROOT>/ eezautomate.properties to remoe the System Automation for Multiplatforms cluster to make System Automation Application Manager highly aailable. Validate and store the automation policy for System Automation Application Manager. Inoke the script eezha -V -checkpolicy <EEZ_CONFIG_ROOT>/ eezautomate.properties to alidate the System Automation Application Manager automation policy as you hae configured it. Define a configured automation policy. Inoke the script eezha -actiatepolicy <EEZ_CONFIG_ROOT>/ eezautomate.properties to define the resources of the System Automation Application Manager automation policy according to the alues that you specified when configuring System Automation Application Manager high-aailability. Remoe a configured automation policy. Inoke the script eezha -deactiatepolicy <EEZ_CONFIG_ROOT>/ eezautomate.properties to remoe the resources of the System Automation Application Manager automation policy that match the alues that you specified when configuring System Automation Application Manager high-aailability. If you hae made one of the end-to-end automation adapters highly aailable in an HACMP, FOC, or VCS cluster, you might also need to replicate the corresponding adapter configuration files to the other nodes in the HACMP, FOC, 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. 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: 1. Define the automation policy. Inoke the script mkhacadapter -p for the HACMP adapter and the script mkcsadapter -p for the VCS adapter to define the resources according to the alues that you specified when configuring the adapter automation policy. 2. Remoe the automation policy. Inoke the script mkhacadapter -r for the HACMP adapter and the script mkcsadapter -r for the VCS adapter to remoe the resources that match the alues that you specified when configuring the adapter automation policy. Inoking silent configuration 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: Chapter 3. Configuring 183

202 System Automation Application 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: /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 perform configuration tasks for the System Automation Application Manager common configuration: cfgeezdmn -s -e [-r] b. To configure the System Automation Application Manager local Agentless Adapter: cfgeezdmn -s -eu c. To configure remote System Automation Application Manager Agentless Adapters: cfgeezdmn -s -ru -o host [-ra [-w configdir ] -rr -rd -u userid -p password] d. To configure the hardware adapter: cfgeezdmn -s -eh [-r -t] e. To configure the TPC-R domain: cfgeezdmn -s -et [-r -t] f. To configure the automation policy to make System Automation Application Manager highly aailable: cfgeezdmn -s -ea [-ad] Use option -ad to configure the high aailability policy for a two-site disaster recoery setup. If you do not specify -ad, the regular high aailability policy is configured. This option is supported only on Linux for System z. 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. Issue the following command to inoke the configuration tool in silent mode: cfghacadapter -s The FOC 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 184 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

203 C:\Program Files\IBM\tsamp\eez\mscs\bin 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 For more information about the cfgeezdmn, cfghacadapter, cfgmscsadapter, and cfgcsadapter commands, refer to Tioli System Automation Application Manager, Reference and Problem Determination Guide. 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 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. -l location The input properties file for silent configuration is located in the directory that is specified with location. If-l is omitted, the input properties file is located in the default directory <EEZ_CONFIG_ROOT>. Depending on the operation system, <EEZ_CONFIG_ROOT> is etc/opt/ibm/tsamp/eez/cfg. Depending on the target configuration, Table 38 shows the silent input properties files that are generated if the -g or -gr option is specified. Table 38. Generated input properties files Component Target configuration Silent input properties file System Automation Application Manager (common) cfgeezdmn -s -e -g -gr <EEZ_CONFIG_ROOT>/ silent.eezcommon.properties Local Agentless Adapter cfgeezdmn -s -e -g -gr -l location cfgeezdmn -s -eu -g -gr cfgeezdmn -s -eu -g -gr -l location location/silent.eezcommon.properties <EEZ_CONFIG_ROOT>/ silent.eezaladapt.properties location/silent.eezaladapt.properties Chapter 3. Configuring 185

204 Table 38. Generated input properties files (continued) Component Target configuration Silent input properties file Remote Agentless Adapter <EEZ_CONFIG_ROOT>/ cfgeezdmn -s -ru -o host -g -gr silent.remotealadapt.properties Hardware adapter TPC-R domain cfgeezdmn -s -ru -o host -g -gr -l location cfgeezdmn -s -eh cfgeezdmn -s -eh cfgeezdmn -s -et cfgeezdmn -s -et -g -gr -g -gr -l location -g -gr System Automation Application Manager high-aailability cfgeezdmn -s -ea -g -gr HACMP adapter FOC adapter VCS adapter -g -gr -l location location/silent.remotealadapt.properties <EEZ_CONFIG_ROOT>/ silent.eezhwadapt.properties location/silent.eezhwadapt.properties <EEZ_CONFIG_ROOT>/ silent.eeztpcr.properties location/silent.eeztpcr.properties <EEZ_CONFIG_ROOT>/ silent.eezauto.properties cfgeezdmn -s -ea -g -gr -l location location/silent.eezauto.properties cfgeezdmn -s -ea -ad -g -gr cfgeezdmn -s -ea -ad -g -gr -l location cfghacadapter -s cfghacadapter -s cfgmscsadapter -s cfgmscsadapter -s cfgcsadapter -s cfgcsadapter -s -g -gr -g -gr -l location -g -gr -g -gr -l location -g -gr -g -gr -l location <EEZ_CONFIG_ROOT>/ silent.eezautodr.properties location/silent.eezautodr.properties <EEZ_CONFIG_ROOT>/ silent.hacadapter.properties location/silent.hacadapter.properties <EEZ_CONFIG_ROOT>\ silent.mscsadapter.properties location\silent.mscsadapter.properties <EEZ_CONFIG_ROOT>/ silent.csadapter.properties location/silent.csadapter.properties If you update configuration settings in silent mode, the silent properties file is used as input for the update task. If you want the configuration utility to retriee the input file from a location other than in the <EEZ_CONFIG_ROOT> directory, use the -l location option. 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. 186 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

205 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. 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. Note: 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. Output in silent mode Inoking the configuration tool in silent mode leads to output that closely matches the output that is displayed in interactie mode in the update status dialogs after clicking Sae, or in the message boxes. The silent mode output falls into one of the following categories: No update There are no configuration updates to be saed. All parameters in all target configuration files already match the specified silent input parameters. No errors were detected when checking the silent input parameters. If additional information is aailable or any warning conditions are detected, the information and warnings are reported. If warnings are reported, the configuration tool issues return code "1" rather than "0". You may need to obsere this when inoking silent configuration programmatically, for example within a shell script. Successful completion At least one of the target configuration files is updated and all configuration files and their update status are listed. No errors are detected when checking the silent input parameters. If additional information is aailable or any warning conditions are detected, the information and warnings are reported. If warnings are reported, the configuration tool issues return code "1" rather than "0". You may need to obsere this when inoking silent configuration programmatically, for example within a shell script. Chapter 3. Configuring 187

206 Unsuccessful completion No target configuration file is updated. Any errors that are detected when checking the silent input parameters are reported. The configuration tool terminates issuing return code "2". Tasks that do not update configuration files The output for all "Refresh" and "Test" configuration tasks is a corresponding task completion message. Silent input properties file generation Values from the target configuration files are used to generate the input file. No target configuration file is updated. Fatal error Error messages indicating the reason for the error are reported. The configuration tool terminates issuing a return code greater than "2". Configuration properties files You can configure the properties files of System Automation Application Manager, HACMP, WSFC, and VCS adapter. Configuration properties files of the System Automation Application Manager This topic proides a short description of the configuration properties files of the System Automation Application Manager. During the installation of the System Automation Application Manager, the properties in the files are set to alues that allow you to work with the sample end-to-end automation domain as described in Tioli System Automation Application Manager, Administrator s and User s Guide. To change the alues of the properties, you use the cfgeezdmn configuration utility of the System Automation Application Manager. This ensures that the files are not corrupted during manual editing and that the change history in the files is updated wheneer a property is changed. It also ensures that dependencies between parameter alues in different properties files are obsered. The configuration properties files of the System Automation Application Manager are located in the following directory: <EEZ_CONFIG_ROOT> Typically, this is /etc/opt/ibm/tsamp/eez/cfg The following list describes the properties files that are changed when you modify a property alue using the cfgeezdmn configuration utility: eezautomate.properties The properties in this file are used to configure the end-to-end automation policy. This policy can be actiated on a System Automation for Multiplatforms domain to make the System Automation Application Manager highly aailable. The configuration properties specify, for example, the name of the System Automation for Multiplatforms domain, the location of the WebSphere profiles and the DB2 installation directory. eez.automation.engine.properties The properties in this file are used to configure exactly one instance of the 188 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

207 automation engine. The configuration properties specify, for example, the name of the end-to-end automation domain and the location of the policy pool directory. eez.automation.engine.dif.properties The domain identification file of the automation engine contains the user IDs and the corresponding passwords that the end-to-end automation engine uses to authenticate itself to first-leel automation domains and to the WebSphere Application Serer JMS Proider. eez.publisher.omnibus.properties The properties in this file are used to configure settings to publish EIF eents to Tioli Netcool/Omnibus. The configuration properties specify, for example, the serer and port of the OMNIbus Probe for Tioli EIF and eent filters. eez.fla.ssl.properties This file contains the configuration properties for the SSL connection to the first-leel automation domains. eezjlog.properties The properties in this file determine which information is written to the log and trace files of the automation engine. sas.eezcs.properties The properties in this file determine whether users of the end-to-end automation command shell must specify their user credentials to use the command shell. sas.eezdmn.properties The properties in this file determine how the end-to-end automation engine and the discoery library adapter access the WebSphere Application Serer (WAS) and the automation J2EE framework. eez.dla.properties The properties in this file determine where the IdML books created by the discoery library adapter are stored. eez.hwadapter.properties The properties in this file are used to configure the hardware adapter. The configuration properties include, for example, the host and port the hardware adapter listens on, and the host and port of the automation engine it communicates with. eez.hwadapter.plugin.properties The properties in this file are used to configure credentials for the hardware deices when you configure distributed disaster recoery with GDPS. eez.hwadapter.zent-1.plugin.properties The properties in this file are used to configure the settings to access the zenterprise Hardware Management Console (HMC) for irtual serer management. eez.aladapter.properties The properties in this file are used to configure the local Agentless Adapter. For example, the host and port the Agentless Adapter listens on, or the host and port of the automation engine it communicates with. eez.aladapter.dif.properties The properties in this file are used to configure the user IDs and the corresponding passwords that the local Agentless Adapter uses to access Chapter 3. Configuring 189

208 remote non-clustered nodes. The resources that the Agentless Adapter starts, stops, and monitors reside on those remote nodes. eez.aladapter.ssh.properties The properties in this file are used to configure security settings related to SSH priate keys. SSH keys can be configured for user authentication on remote non-clustered nodes as an alternatie to configure credentials in the eez.aladapter.dif.properties file for the local Agentless Adapter. eez.aladapter.ssl.properties The properties in this file are used to configure Secure Sockets Layer (SSL) for transport between the automation manager and the local Agentless Adapter. eez.aladapter.jaas.properties This file contains the configuration of the LoginModule that is used for user authentication between the automation manager and the local Agentless Adapter. eez.aladapter.plugin.properties The properties in this file are used to configure settings that are unique for the local Agentless Adapter. For example, the location of the XML policy pool. eez.aladapter.plugin.<domain>.properties The For each local Agentless Adapter domain, a domain specific copy of eez.aladapter.plugin.properties is created. eez.tpcr.domain.properties The properties in this file are used to configure settings of the Tioli Storage Productiity Center for Replication (TPC-R) domain that is used by the System Automation Application Manager to integrate storage replication sessions into end-to-end automation policies. <remote_node>/eez.aladapter.properties <remote_node>/eez.aladapter.dif.properties <remote_node>/eez.aladapter.ssh.properties <remote_node>/eez.aladapter.ssl.properties <remote_node>/eez.aladapter.jaas.properties <remote_node>/eez.aladapter.plugin.properties <remote_node>/eez.aladapter.plugin.<domain>.properties These files are stored for each remote Agentless Adapter instance in a subdirectory for the node on which the remote Agentless Adapter is installed. <remote_node>/eez.aladapter.jlog.properties The properties in this file determine which information is written to the log and trace files of an instance of the remote Agentless Adapter. Configuration properties files of the HACMP adapter This topic proides a short description of the configuration properties files of the HACMP adapter. To change the alues of the properties, you use the cfghacadapter configuration utility of the HACMP adapter. This ensures that the files are not corrupted during manual editing and that the change history in the files is updated wheneer a property is changed. It also ensures that dependencies between parameter alues in different properties files are obsered. 190 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

209 The configuration properties files are located in the following directory: <hacmp_adapter_conf_root> Typically, this is /etc/opt/ibm/tsamp/eez/hac/cfg The following list describes the properties files that are changed when you modify a property alue using the cfghacadapter configuration utility. hac.adapter.properties The properties in this file are used to configure the HACMP adapter. For example the host and port on which the HACMP adapter listens or the host and port of the automation engine, with which the HACMP adapter communicates. hac.adapter.jaas.properties This file contains the configuration of the LoginModule that is used for user authentication between the automation manager and the HACMP adapter. hac.adapter.jlog.properties The properties in this file determine which information is written to the log and trace files of an instance of the HACMP adapter. hac.adapter.plugin.properties The properties in this file are used to configure settings that are unique for the HACMP adapter. hac.adapter.ssl.properties The properties in this file are used to configure Secure Sockets Layer (SSL) for transport between the automation manager and the HACMP adapter. hac.adapter.conf This file describes the automation configuration to make the HACMP adapter highly aailable. Configuration properties files for the VCS Solaris adapter This topic proides a short description of the configuration properties files of the VCS Solaris adapter. To change the alues of the properties, you use the cfgcsadapter configuration utility of the VCS Solaris adapter. This ensures that the files are not corrupted during manual editing and that the change history in the files is updated wheneer a property is changed. It also ensures that dependencies between parameter alues in different properties files are obsered. The configuration properties files are located in the following directory: <cs_adapter_conf_root> Typically, this is /etc/opt/ibm/tsamp/eez/cs/cfg The following list describes the properties files that are changed when you modify a property alue using the cfgcsadapter configuration utility: cs.adapter.properties The properties in this file are used to configure the VCS Solaris adapter. Chapter 3. Configuring 191

210 For example the host and port on which the VCS Solaris adapter listens or the host and port of the automation engine, with which the VCS Solaris adapter communicates. cs.adapter.jaas.properties This file contains the configuration of the LoginModule that is used for user authentication between the automation manager and the VCS Solaris adapter. cs.adapter.jlog.properties The properties in this file determine which information is written to the log and trace files of an instance of the VCS Solaris adapter. cs.adapter.plugin.properties The properties in this file are used to configure settings that are unique for the VCS Solaris adapter. cs.adapter.ssl.properties The properties in this file are used to configure Secure Sockets Layer (SSL) for transport between the automation manager and the VCS Solaris adapter. cs.adapter.conf This file describes the automation configuration to make the VCS Solaris adapter highly aailable. Configuration properties files of the FOC adapter This topic proides a short description of the configuration properties files of the FOC adapter. To change the alues of the properties, you use the cfgmscsadapter configuration utility of the FOC adapter. This ensures that the files are not corrupted during manual editing and that the change history in the files is updated wheneer a property is changed. It also ensures that dependencies between parameter alues in different properties files are obsered. The configuration properties files are located in the following directory: <mscs_adapter_conf_root> Typically, this is C:\Program Files\IBM\tsamp\eez\mscs\cfg The following list describes the properties files that are changed when you modify a property alue using thecfgmscsadapter configuration utility: mscs.adapter.properties The properties in this file are used to configure the FOC adapter. For example the host and port on which the FOC adapter listens or the host and port of the automation engine, with which the FOC adapter communicates. mscs.adapter.jlog.properties The properties in this file determine which information is written to the log and trace files of an instance of the FOC adapter. mscs.adapter.plugin.properties The properties in this file are used to configure settings that are unique for the FOC adapter. 192 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

211 mscs.adapter.ssl.properties The properties in this file are used to configure Secure Sockets Layer (SSL) for transport between the automation manager and the FOC adapter. Chapter 3. Configuring 193

212 194 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

213 Chapter 4. Integrating Eent consoles System Automation Application Manager integrates with a set of Tioli applications to extend its existing functionality. The integration scenarios require specific configurations to meet your infrastructure needs. Find out how to configure System Automation Application Manager to work together with other Tioli applications. Integration scenarios: Eent Consoles Forwarding System Automation eents to IBM Tioli Netcool/OMNIbus Configuring launch-in-context from OMNIbus to the SA Operations Console Forwarding system automation eents to IBM Tioli Enterprise Console Configuring launch-in-context from Tioli Enterprise Console to the SA Operations Console Tioli Business Serice Manager (TBSM) Populating TBSM iews with information from System Automation resources and eents Import end-to-end automation management resources into TBSM using the System Automation Application Manager Library Adapter (DLA) Configuring launch-in-context from TBSM to the SA Operations Console and ice ersa. IBM Tioli Monitoring, and IBM Tioli Composite Application Manager Integrating applications which are monitored by ITM or ITCAM in an Agentless Adapter domain Automating ITM resources in an end-to-end context Configuring launch-in-context from the SA Operations console to the Tioli Enterprise Portal (TEP). System Automation Application Manager sends EIF eents to Tioli Netcool/OMNIbus (OMNIbus). OMNIbus is a rule-based eent management application that uses a central serer to process incoming eents. For compatibility reasons, alternatiely a Tioli Enterprise Console (TEC) serer or any other serer that is capable to process EIF eents may also be configured. Eent sources: Tioli applications Tioli partner applications Customer applications Network management Relational database systems For System Automation Application Manager an eent is generated and forwarded to the TEC or OMNIbus eent console in the following cases: Copyright IBM Corp. 2006,

214 The configuration of System Automation Application Manager or the state of an automated resource changes, which is contained in the end-to-end automation policy. Problems are encountered If you want to use System Automation eents with Tioli Business Serice Manager (TBSM), forward the eents to OMNIbus. System Automation Application Manager can produce the following types of eents: Table 39. System Automation Application Manager eent class types Eent Class / Alert Group SystemAutomation_Resource_Status_Change SystemAutomation_Resource_Configuration_Change SystemAutomation_Relationship_Configuration_Change SystemAutomation_Domain_Status_Change SystemAutomation_Request_Configuration_Change SystemAutomation_Request_Status_Change Description Status of an automated resource changed. A new automated resource is added or an existing resource is deleted or modified. A new relationship is added or an existing relationship is deleted or modified. The domain status changed. For example: The automation manager or the automation adapter of the domain starts or stops. A new automation policy is actiated. A new request is issued against an automated resource or an existing request is canceled. A GDPS command is completed. Only used in the Distributed Disaster Recoery with GDPS feature. The following topics describe how to set up System Automation Application Manager and the eent consoles to enable eent forwarding to either TEC or OMNIbus. IBM Tioli Netcool/OMNIbus This topic describes how to set up IBM Tioli Netcool/OMNIbus to forward System Automation eents to the OMNIbus eent console and how to set up launch-in-context support for OMNIbus. This OMNIbus set up is also a prerequisite for the integration of System Automation Application Manager with Tioli Business Serice Manager. Prerequisites As System Automation Application Manager and IBM Tioli System Automation for Multiplatforms use Tioli Eent Integration Facility (EIF) eents for communication, the following components are required: IBM Tioli Netcool/OMNIbus (OMNIbus) OMNIbus Probes Library for Nonnatie Base OMNIbus Probe for Tioli EIF (EIF Probe). This probe can receie EIF eents sent from System Automation and forward them to the ObjectSerer. The following minimum ersions are required: OMNIbus Probe for Tioli EIF V.9.0 IBM Tioli Netcool/OMNIbus Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

215 Note: If you are running IBM Tioli Netcool/OMNIbus V7.2.1, install Interim Fix 3 ( IF0003). If you are running IBM Tioli Netcool/OMNIbus V7.3 or higher, no additional fix packs are required. Install and set up these components according to the documentation aailable in the OMNIbus Information Center: display/tiolidoccentral/omnibus. Enironment ariables: $NCHOME Refers to the Netcool Home Directory into which the packages are installed. Default directory under Linux: /opt/ibm/tioli/netcool. $OMNIHOME The $OMNIHOME ariable is used to proide legacy support for scripts, third-party applications, and probes that continue to use the $OMNIHOME enironment ariable. $OMNIHOME refers to $NCHOME/omnibus. Eent fields in OMNIbus database The OMNIbus alerts.status table will be extended with the following new columns to hold System Automation specific information. They will be filled in the SA specific OMNIbus rules file when processing an eent. Table 40. alerts.status: Common System Automation status attributes used in resource status change eents Attribute Name Type Description SADesiredState archar(16) Desired State reflecting the automation goal of an automated resource. Possible alues: Online Offline NoChange This means the automation goal of the resource cannot be changed by an operator SAObseredState archar(16) Current Obsered State of an automated resource Possible alues: Unknown Online Offline Starting Stopping NotApplicable Note: Corresponds to c_status_obsered in TEC eent. SAOperationalState archar(255) List of Operational State alues giing more fine-grained information about the current state of the resource. For a list of possible alues, see the SystemAutomation.baroc file. Note: Corresponds to c_status_operational in TEC eent. SACompoundState archar(16) Compound State indicating whether the resource is working as desired or has encountered an error. Possible alues: Ok Warning Error Fatal Note: Corresponds to c_status_compound in TEC eent. Chapter 4. Integrating 197

216 Table 41. alerts.status: Resource, domain, eent identification SADomainName archar(64) Name of the Automation Domain. Part of the resource key to identify a resource. Note: Corresponds to sa_domain_name in TEC eents SAResourceName archar(255) Name of the resource. This is a compound resource name consisting of the resource name itself concatenated with the resource class and optionally the resource node. The order of the name parts and the separator character depends on the sending System Automation product. For SA MP and SA AM: <class_name>:<resource_name>:<node_name> For SA z/os: <resource_name>:<class_name>:<node_name> Note: <node_name> is only set if it exists. For System Automation Application Manager resource references, the node name contains the name of the referenced first leel automation domain. Corresponds to sa_resource_name in TEC eents. SAEentReason archar(255) Eent reasons. One eent can hae multiple eent reasons in TEC eent. Examples for eent reasons: StatusCommonObseredChanged ConfigurationDeleted PreferredMemberChanged Note: Corresponds to sa_eent_reason in TEC eents. SAReferencedResource archar(255) For end-to-end resource references, this contains the referenced resource key. Table 42. alerts.status: Other attributes used in resource status change eents SAExludedFromAutomation archar(16) Flag indicating if the resource is excluded from automation (i.e. automation is suspended). Used in resource status change eents. Possible alues: NotExcluded Excluded Note: Corresponds to sa_flag_excluded in TEC eents. SADesiredRole archar(16) Desired role. Used for replication references indicating the desired storage replication direction (SA AM only). Used in resource status change eents. Note: Corresponds to sa_role_desired in TEC eents. SAObseredRole archar(16) Obsered role. Used for replication references indicating the obsered storage replication direction (SA AM only). Used in resource status change eents. Note: Corresponds to sa_role_obsered in TEC eents. Table 43. alerts.status: Domain status change eents SADomainState archar(16) Status of Automation Domain. Possible alues: Online Offline Unknown Note: Corresponds to sa_domain_state in TEC eents. 198 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

217 Table 43. alerts.status: Domain status change eents (continued) SACommunicationState archar(32) This state reflects the connection and aailability state of the domain. Only sent by SA AM. Used in domain status change eents. Possible alues: Ok AsyncTimeout AsyncMissedEent SyncFailed SyncFailedAndAsyncMissedEent SyncFailedAndAsyncTimeout DomainHasLeft Note: Corresponds to sa_communication_state in TEC eents. Beside the new fields for System Automation eents, the following existing fields will be set in the rules file for System Automation eents during eent processing. Table 44. Existing rules file fields for System Automation eents Attribute Name Description Manager Descriptie name of the probe that collected and forwarded the alarm to the ObjectSerer. Agent Node AlertGroup AlertKey Seerity Summary Serice Identifier Value for SA eents: tioli_eif on <hostname>. Descriptie name of the manager that generated the eent. Value for System Automation Application Manager eents: IBM Tioli System Automation Application Manager. Identifies the hostname from which the eent comes from. Identifies the type of eent issued by System Automation. See Table 39 on page 196 for a list of possible eent classes. Descriptie key that indicates the resource that triggered the eent. For resource eents, it contains the resource key formatted as System Automation source token, e.g. EEZResourceKey,DN={FriendlyE2E},NN={},RN={DB2},RC={ChoiceGroup}. For domain eents, it contains the domain name formatted as System Automation Source Token, e.g. EEZDomain,DN={FriendlyE2E} Indicates the eent seerity leel. For resource eents, the compound state of the resource determines the seerity leel. The color of the eent in the eent list is controlled by the seerity alue: 0: Clear 1: Indeterminate 2: Warning 3: Minor 4: Major 5: Critical See Compound state to seerity mapping on page 200. Text summary describing the eent. Name of the serice affected by this eent. Corresponds to field SAResourceName. Identifier which uniquely identifies the problem source and controls ObjectSerer deduplication. The ObjectSerer uses deduplication to ensure that eent information generated from the same source is not duplicated in the eent list. Repeated eents are identified using the Identifier attribute and stored as a single eent to reduce the amount of data in the ObjectSerer. For System Automation eents, the Identifier field is set to AlertKey + ":" + AlertGroup. Therefore, the eent console displays always the last eent of the same resource and AlertGroup. Chapter 4. Integrating 199

218 Table 44. Existing rules file fields for System Automation eents (continued) Attribute Name Description Class The unique class for System Automation eents. Value is (Tioli System Automation). ExtendedAttr Holds name-alue pairs of additional internal System Automation specific attributes, for which no dedicated column exists in the alerts.status table. In addition to these attributes which are stored in the OMNIbus alerts.status table, extra information is written to the alerts.details table. For example, for domain eents the product name and ersion of the automation product corresponding to the domain are stored in the alerts.details table. Compound state to seerity mapping For eents that contain a SACompoundState alue, for example all resource state change eents, the following table is used: Table 45. Compound State to OMNIbus seerity mapping SA Compound State OMNIbus Seerity field Fatal 5 (Critical) Error 4 (Major) Warning 3 (Minor) OK 1 (Indeterminate) For other eents that do not contain the SACompoundState alue, for example request eents or domain eents, the EIF seerity field is used to determine the OMNIbus seerity. Table 46. EIF seerity to OMNIbus seerity mapping EIF Seerity OMNIbus Seerity field 60 (FATAL) 5 (Critical) 50 (CRITICAL) 5 (Critical) 40 (MINOR) 4 (Major) 30 (WARNING) 3 (Minor) 20 (HARMLESS) 2 (Warning) Else 1 (Indeterminate) Note: The EIF Seerity alue of the original EIF eent can be found in the ExtendedAttr field of an eent. Configuring OMNIbus to process System Automation eents Updating the OMNIbus database: The OMNIbus ObjectSerer database includes the alerts.status table which contains all fields that are shown and selected by an eent list. For System Automation eents, the additional columns described in Eent fields in OMNIbus database on page 197 hae to be created in the alerts.status table. 200 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

219 The sa_db_update.sql file creates the new columns in the alert.status table. The eent class used for eents from Tioli System Automation is created as well. Tioli System Automation uses the eent class for its eents. The class is used to associate tools like the launch-in-context tool, to a specific type of eent. Enter the following command on the OMNIbus serer: UNIX $OMNIHOME/bin/nco_sql -serer NCOMS -username root < sa_db_update.sql Windows: %NCHOME%\bin\redist\isql -S NCOMS -U root < sa_db_update.sql Enter your password when prompted. You can find the file sa_db_update.sql on the System Automation Application Manager product DVD in the directory /integration. Note: The eent class is predefined in OMNIbus Version or higher. If you run the sa_db_update.sql script using OMNIbus Version 7.3.1, you receie the following error message: ERROR=Attempt to insert duplicate row on line 2 of statement insert into alerts.conersions alues ( Class87725, Class,87725, Tioli System Automation );... You can ignore this error message. Verify that the SA specific columns and eent class has been successfully added to OMNIbus: 1. Open the Netcool/OMNIbus Administrator window using the nco_config command. 2. From the Netcool/OMNIbus Administrator window, select the System menu button. 3. Click Databases. The Databases pane opens. 4. Select the alerts.status table. The alerts.status table pane opens. 5. Verify that the following columns are listed: a. SACompoundState b. SADesiredState c. SAObseredState d. SAOperationalState e. SADomainName f. SAResourceName g. SAReferencedResource h. SAEentReason i. SAExludedFromAutomation j. SADesiredRole k. SAObseredRole l. SADomainState m. SACommunicationState 6. From the Netcool/OMNIbus Administrator window, select the Visual menu button. Chapter 4. Integrating 201

220 7. Click Classes. The Classes pane opens. 8. Verify that the class with ID and label Tioli System Automation is listed in the table. Enable rules file for System Automation: An OMNIbus rules file defines how the probe processes eent data to create an alert. For each alert, the rules file also creates an identifier that uniquely identifies the problem source. The probe for Tioli EIF uses a standard rules file named tioli_eif.rules. System Automation Application Manager ships the System Automation specific rules file tioli_eif_sa.rules. This file needs to be included within the default tioli_eif.rules using an include statement. The rules file tioli_eif_sa.rules processes an EIF eent receied by the probe for Tioli EIF if the eent field source contains the alue SystemAutomation. The default tioli_eif.rules file is located on the system where the probe for Tioli EIF is installed in the following directory: Windows: %OMNIHOME%\probes\<os_dir>\tioli_eif.rules UNIX: $OMNIHOME/probes/<os_dir>/tioli_eif.rules Perform the following steps to enable the tioli_eif_sa.rules file: 1. Copy the file tioli_eif_sa.rules, which is located in the /integration directory on the System Automation Application Manager product DVD to the system where the OMNIbus probe for Tioli EIF is installed. As a target directory choose the directory where the tioli_eif.rules file is located. 2. Enable the shipped rules file tioli_eif_sa.rules. Edit the tioli_eif.rules file that is used in the probe for Tioli EIF and add an include statement for the tioli_eif_sa.rules file. The content of the tioli_eif.rules looks different depending on the type of OMNIbus installation you hae: a. If you use a standalone OMNIbus installation: Open tioli_eif.rules file in a text editor and add the include statement after the switch($source) block: : else { switch($source) { case "dummy case statement": ### This will preent syntax errors in case no includes are added below. } include "tioli_eif_tpc.rules" include "tioli_eif_tsm.rules" # Uncomment the following line when using TADDM integration # This rules file is aailable in OMNIbus 7.3 and newer only # include "tioli_eif_taddm.rules" default: # Comment out the following line when not receiing eents from TEC include "tioli_eif_default.rules" } include "tioli_eif_sa.rules" b. If you integrate with Tioli Business Serice Manager (TBSM) and use the OMNIbus ersion packaged with TBSM: Open the tioli_eif.rules file in a text editor and add the include statement in the block where the predefined rules files are included. Search 202 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

221 for the line # Include customer rules which would oerride any preious rules. and add the include statement for tioli_eif_sa.rules before this line: : : ### ### Handle TEC Eents ### include "tec_eent.rules" ### ### Handle Z Eents ### # include "zos_eent.rules" ### ### Handle Z user defined eents. ### # include "zos_eent_user_defined.rules" ### ### Handle Z identity assignement. ### # include "zos_identity.rules" ### ### Handle EE( Eent Enablement) eents. ### # include "tioli_eif_ee.rules" include "tioli_eif_sa.rules" # Include customer rules which would oerride any preious rules. # include "customer_oerride.rules" : : 3. Stop the EIF probe. On Windows: Select Control Panel > Administratie Tools > Serices. In the list of serices, double-click the EIF probe, then click Stop. On UNIX: Enter the following command on the command line $OMNIHOME/bin/nco_pa_stop -process <probe_name> 4. Restart the EIF probe. On Windows: In the list of serices, double-click OMNIbus EIF Probe, then click Start On UNIX: Enter the following command on the command line: $OMNIHOME/bin/nco_pa_start -process <probe_name> Note: 1. You can test your changes in the rules file using the syntax checking tool nco_p_syntax deliered with the OMNIbus serer. Use the root rules file tioli_eif.rules. Included files are checked automatically. Example: $OMNIHOME/probes/nco_p_syntax -rulesfile $OMNIHOME/probes/linux2x86/tioli_eif.rules 2. If you want the Probe to be forced to read again the rules file without loosing eents, enter the following command: kill -HUP <pid> Chapter 4. Integrating 203

222 pid is the probe process ID. You can determine the pid using the nco_pa_status command. Configuring Tioli Netcool/OMNIbus launch-in-context The launch-in-context support for System Automation Application Manager naigates from an eent that is displayed in the OMNIbus actie eent list to the corresponding resource or domain in the System Automation operations console. Example usage scenario: 1. Application failure is detected by System Automation and a corresponding eent is forwarded to OMNIbus. 2. An operator sees an error eent in the OMNIbus actie eent list that indicates that an automated application has failed. 3. For further analysis, he selects the eent and clicks on a menu entry to launch the operations console. 4. A new browser window is opened and connects to the Dashboard Application Serices Hub which automatically launches the operations console. 5. The System Automation operations console automatically naigates to the application that caused the error eent and selects it. 6. The operator now sees all detailed status information, relationships, etc. as they are proided by System Automation. Creating a launch-in-context tool: Create a launch-in-context tool which launches the SA Operations Console from the eent managed by the ObjectSerer: 1. Login to the Tioli Integrated Portal (TIP) hosting the OMNIbus Web GUI as tipadmin. 2. Naigate to Administration -> Eent Management Tools -> Tool Creation. 3. Select Create Tool. 4. Select CGI/URL as Type. 5. Enter the URL EEZIscUrlBuilderSerlet. ISC_HOST is the system where the System Automation Application Manager operations console is running. ISC_PORT is the secure port for the Dashboard Application Serices Hub hosting the System Automation operations console. 6. Click the Fields: Show button and select the following fields that should be passed as context arguments to the URL: SADomainName SAResourceName Summary 7. Select Method: GET 8. Select Open In -> Specific Window and type a window name, for example SystemAutomation. So that launches from OMNIbus always use the same window to open the SA Operations Console. 9. In the Access Criteria section, select the Class tab and choose the Tioli System Automation class from the list of aailable eent classes. This ensures that the launch-in-context tool is only aailable for eents of System 204 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

223 Automation. Figure 23. Sample configuration of launch entry Note: If you hae more than one System Automation Application Manager installation, define a launch-in-context tool for each installed instance. 10. Click Sae to sae the new launch-in-context tool. Defining the menu entry: After the launch-in-context tool has been defined, you can configure the menu entry to display the launch-in-context tool. To add the new launch-in-context tool to the actie eent list tools menu, perform the following steps: 1. Naigate to: Administration -> Eent Management Tools -> Menu Configuration -> tools -> Modify 2. Select the new launch-in-context tool from the Aailable items list and add it to the list of Current items. 3. Click Sae to store the modified configuration of the tools menu. Chapter 4. Integrating 205

224 Figure 24. Modifying menu entries that are displayed in the Tools menu Tioli Enterprise Console This topic describes how to set up the Tioli Enterprise Console to forward System Automation eents to the TEC and how to set up launch-in-context support for the TEC. Prerequisites 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 Web browser If you use the Jaa ersion of the TEC Eent Console to launch to the SA operations console, make sure a Web browser like Mozilla, Firefox, or Internet Explorer is installed on the system where the eent console runs. Configuring TEC to process System Automation eents The programming language Basic Recorder of Objects in C (BAROC) is used to define the structure of eents and their properties. These definitions are stored in files with the extension.baroc. The baroc file for System Automation eents is 206 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

225 called SystemAutomation.baroc and is located in directory <EEZ_CONFIG_ROOT> after the installation. To prepare TEC to use with System Automation Application Manager, perform the following step: 1. Import, compile, load, and actiate the TEC baroc file SystemAutomation.baroc in the TEC serer. For more information refer to IBM Tioli Enterprise Console Rule Builder's Guide, GC Configuring Tioli Enterprise Console launch-in-context support The IBM Tioli Enterprise Console (TEC) extension for System Automation Application Manager (IBM TEC Extension) allows to naigate from an eent that is displayed 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 Installing the TEC extension: For the TEC Web console client, no installation steps are required. You can directly progress to the configuration steps described in Enabling launch-in-context feature on page 208. You only need to perform the installation steps described in this topic 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. Chapter 4. Integrating 207

226 To install the IBM TEC Extension on AIX, Linux or Windows perform these steps: 1. Insert the System Automation Application Manager product DVD into the DVD 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 DVD or in the electronic distribution directory structure. 4. Start the installation program, using this command: jaa jar setup.jar 5. Follow the installation instructions. Enabling launch-in-context feature: To enable the launch-in-context feature, complete the following steps: Jaa TEC Eent Console 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: &ltpath>eezlaunchsa.bat [&ltjaa home>] Example: "C:\Program Files\IBM\TECExtension\EEZLaunchSA.bat" C:\IBM\tec_console\jre\bin\ For AIX and Linux: &ltpath>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). 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. Web TEC Eent Console For the definition of a Web custom button, the Jaa ersion of the TEC Eent Console is required. 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. 208 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

227 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 Dashboard Application Serices Hub runs which hosts the Tioli System Automation operations console and <isc_port> is the port that is used to access the System Automation operations console. Example: 6. Ensure that you hae enabled Eent selection required for button action. Enabling eent generation in System Automation Application Manager If you want to send System Automation eents to OMNIbus, enable eent forwarding in System Automation Application Manager. If you hae not actiated or configured the EIF eent generation and forwarding function during the installation of System Automation Application Manager, you can do so by performing the following steps: 1. Start the end-to-end automation configuration tool (cfgeezdmn). On the Eent Publishing page, proceed as follows: a. Select the check box Enable EIF eent generation to OMNIbus b. Enter the OMNIbus eent serer host name. c. Enter the OMNIbus eent serer port number. d. Sae the configuration.. 2. Restart the WebSphere Application Serer and the end-to-end automation engine (eezdmn) or click the Refresh button to refresh the actie Application Manager common configuration. Enabling eent filtering When you use the eent console of the Tioli Enterprise Console (TEC) or IBM Tioli Netcool/OMNIbus products to display eents, all end-to-end automation eents are sent to the eent console by default. To limit the scope of eents that are forwarded to the eent console, use the Eent Publishing tab of the end-to-end automation configuration tool to achiee the following goals: Controlling automation domain leel eents that are sent to the eent console. Controlling eents for adding and remoing automation requests that are sent to the eent console. Chapter 4. Integrating 209

228 Controlling resource status change eents that are sent to the eent console. There are three options for sending resource status change eents: Send all resource state changes. Use this option if eent correlation is used in the eent console: If only eents with a high seerity alue are sent, then the eent console cannot automatically clear errors that are based on eents that hae been sent preiously. Send only resource state changes with warning or fatal seerity. Send only resource state changes with fatal seerity. For more information about the Eent Publishing tab of the end-to-end automation configuration tool, refer to Eent Publishing tab on page 100. Tioli Business Serice Manager (TBSM) TBSM deliers real-time information that you need in order to respond to alerts effectiely, to be in line with business requirements, and optionally to meet serice-leel agreements (SLAs). TBSM tools help you to build a serice model that you integrate with IBM Tioli Netcool /OMNIbus alerts or optionally with data from an SQL data source. The TBSM Data serer analyzes IBM Netcool/OMNIbus ObjectSerer eents or SQL data for matches against the incoming-status rules you configured for your serice models. If the matching data changes the serice status, the status of the TBSM serice model changes accordingly. When a serices status changes, TBSM sends corresponding serice eents back to the ObjectSerer. The Discoery Library Toolkit creates TBSM serice objects which use data from Discoery Library Adapter (DLA) books or from the IBM Tioli Application Dependency Discoery Manager. The TBSM console proides a graphical user interface (GUI). It runs in the Tioli Integrated Portal (TIP) and logically links serices and business requirements within the serice model. The serice model proides an operator with a iew of how an enterprise performs at a certain moment in time or did perform oer a certain time period. The following figure shows the basic architecture of TBSM: 210 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

229 Historical data Tioli Intergrated Portal TBSM Dashboard Serer Data for serice models, custom charts, iews, nearterm history metric, and marker data (Time Window Analyzer) Databases Sources for EIF eents Eent Pump for z/os OMNIbus Web GUI Serice model data Discoery data Discoery Library Toolkit Tioli Application Dependency Discoery Manager Discoery Library Books Tioli Enterprise Console NetView Tioli Data Warehouse TBSM Common Agent TBSM Data Serer Eents Netcool/OMNIbus ObjectSerer Eents EIF Probe EIF eents IBM Tioli Monitoring User data Eent sources Eents IBM Tioli System Automation User Repository LDAP or ObjectSerer Probes Monitors OMEGAMON TBSM components OMNIbus components Netcool/ Impact ITCAM for Internet Serice Monitoring ITCAM Other components Figure 25. TBSM basic architecture Main components: Tioli Integrated Portal Tioli Integrated Portal enables the interaction and secure passing of data between Tioli products through a common portal. You can launch arious applications within the same dashboard iew to inestigate different aspects of your managed enterprise. Tioli Netcool/OMNIbus TBSM monitors the Tioli Netcool/OMNIbus ObjectSerer for incoming eents. The ObjectSerer collects eents from probes, monitors, and other applications such as IBM Tioli Monitoring. You use TBSM to create serice models that respond to the data receied in the incoming eents. For example, the incoming eent data can change the status of a serice or start the tracking of a potential SLA iolation. Tioli Netcool/Webtop (OMNIbus web GUI) Netcool/Webtop is the browser console for Netcool/OMNIbus and TBSM uses Netcool/Webtop components to display eents that are related to serice models. The Actie Eent List (AEL) and Serice Details portlet in TBSM are Netcool/Webtop components, and are installed as part of TBSM. The Tioli Integrated Portal also includes Netcool/Webtop components. TBSM dashboard serer The TBSM dashboard serer manages the display of the TBSM console and communicates with the TBSM data serer. This interaction between the different TBSM components facilitates to create and isualize serice models using connected TBSM consoles. Users working with the console iew mainly only parts of the serice model. Therefor the dashboard serer acquires and maintains status of serices from the data serer. TBSM data serer The TBSM data serer monitors the ObjectSerer and external databases for data that affect the status of the serices. These serices are configured in the TBSM console or with the RAD shell command-line tool. The serer Chapter 4. Integrating 211

230 calculates the status of these serices by applying rules to the external data. Your serice models and the rules are stored in the TBSM database. Integrating with System Automation Application Manager Business applications typically consist of different middleware components, are multi-tiered, and run on heterogeneous platforms. Tioli Business Serice Manager (TBSM) proides health information about the multi-tiered application. TBSM also monitors serice leel agreements (SLA) based on information coming from numerous sources. Netcool/OMNIbus is used to collect all eents that are related to the business application landscape and TBSM uses these eents to determine the status of the business applications. System Automation for Multiplatforms automates start or stop dependencies in business application landscapes, proides common operating, automatic recoery in failure situations, and gets an aggregated aailability status. System Automation for Multiplatforms and System Automation for z/os make indiidual components of the business application highly aailable, for instance a critical database. System Automation Application Manager can be used to integrate with TBSM in the following ways: Data from System Automation eents can be used to enrich TBSM serice iews. System Automation Application Manager deliers a TBSM serice template containing pre-configured rules how to map states from System Automation to TBSM serice instances. The integration of System Automation Application Manager resources with TBSM can be automated and simplified using the Discoery Library Adaptor (DLA). With this approach System Automation Application Manager resources are automatically imported into a TBSM serice model and related TBSM status rules are automatically assigned. System Automation Application Manager eents are automatically matched with the right TBSM serice instances without manual configuration. Launch-in-context from a TBSM serice iew to the SA Operations Console and ice ersa allows an operator to easily see the information about a specific application from both products. For example, with this capability TBSM can be used to monitor the health of a business application and an operator can use the launch-in-context capability to switch to the SA Operations Console in order to start or stop this business application. Prerequisites Before you begin, install and configure the following products and test your installation: Enable eent forwarding to OMNIbus for System Automation Application Manager eents Configuring OMNIbus to process System Automation eents on page 200. If you want to include System Automation for Multiplatforms resources in TBSM serice trees, enable eent forwarding to OMNIbus for System Automation for Multiplatforms eents, refer to the System Automation for Multiplatforms Information Center. Tioli Business Serice Manager (TBSM) V4.2.1 or higher Update the Netcool OMNIbus ObjectSerer schema for TBSM. 212 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

231 If you hae an existing OMNIbus serer, import the schema files tbsm_db_update.sql and ClearSericeDeps.auto. If OMNIbus is installed with TBSM, the TBSM installer performs the required schema updates. You can find TBSM specific product information in the IBM Tioli Business Serice Manager Information Center. For more information about the installation of the product, refer to index.jsp?topic=/com.ibm.tioli.itbsm.doc/welcome.htm. Configuring TBSM In order to simplify the process for defining and configuring serices in TBSM, serice templates can be defined for serices instances with common behaior. Rather than define each of the serices and their dependencies indiidually, one template can be created for a type of serice and then be assigned to applicable serices. Serice instances represent actual serices that are assigned a template. The template defines how a serice responds to incoming data and the status of other serices. Serices of the same type should be assigned to a common template. This allows to use the same template rules to ealuate the status of multiple serices. When you assign a template to a serice, you tag the serice with the template. Templates eliminate the necessity of creating the same rules for a serice type more than once. System Automation Serice Template for TBSM System Automation Application Manager proides a TBSM Serice Template that is used for System Automation resources which are displayed in a TBSM serice tree. The Serice Template is named EEZ_SystemAutomationResource. It proides An Incoming Status Rule named SACompoundState which uses state change eents coming from System Automation resources to determine the oerall state of serices Text-based Incoming Status Rules, which export the System Automation Obsered State and other System Automation specific states of a resource, so that they can be used in TBSM Views. For more information refer to Customizing TBSM iews to add information from System Automation on page 222. Additional properties that allow launch-in-context to the System Automation Operations Console. For more information, refer to Configuring Tioli Business Serice Manager launch-in-context support on page 226. The EEZ_SystemAutomationResource Serice Template contains an incoming status rule named SACompoundState which determines the oerall state of a serice. If the Serice Template has been assigned to a specific serice instance, resource state change eents coming from System Automation will influence the oerall state of the serice. Eents are associated with a serice instance if the AlertKey in the eent matches the AlertKey defined as identifier for the serice instance. TBSM has three aailable oerall states: Bad, Marginal, and Good. The following mapping is defined in the SACompoundState rule to map resource state change eents from System Automation to an oerall TBSM state for a serice instance: Chapter 4. Integrating 213

232 Table 47. Eent Seerity to TBSM State Mapping Eent Seerity TBSM State 5 (Critical) Bad (Red) 4 (Major) Bad (Red) 3 (Minor) Marginal (Yellow) 1 (Indeterminate) Good (Green) Since there is a one-to-one mapping from a resource s compound state to the eent seerity, the System Automation compound state directly determines the TBSM state. For more information about the mapping of compound state to eent seerity, refer to Compound state to seerity mapping on page 200. Defining a System Automation serice template in TBSM The EEZ_SystemAutomationResource template is required to use System Automation eents in TBSM, import the EEZ_SystemAutomationResource template into TBSM as follows: 1. Copy the file EEZ_SystemAutomationResource.radsh from the /integration directory of the System Automation Application Manager product DVD to a temporary directory where the TBSM data serer is installed. 2. Open a command prompt on the TBSM data serer system. Change to the directory to which you hae copied EEZ_SystemAutomationResource.radsh and issue the following command: UNIX: cat EEZ_SystemAutomationResource.radsh $TBSM_HOME/bin/rad_radshell Windows: type EEZ_SystemAutomationResource.radsh %TBSM_HOME%\bin\rad_radshell The serice template proided by System Automation is now defined in TBSM. Defining trigger in Netcool/OMNIbus In the OMNIbus ObjectSerer, a new state change eent for a resource replaces the preious eent. This is called eent deduplication. By default, TBSM only processes a de-duplicated eent when the alue of the Seerity field changed. In these cases, TBSM processes the de-duplicated eents and updates the serice status accordingly. A status change is possible for a SA resource which updates status fields used in the text-based incoming status rules which are contained in the EEZ_SystemAutomationResource serice template. But the seerity alue does not change because the compound state of the resource does not change. Define a trigger in OMNIbus, to ensure that TBSM updates the serices in these cases as well. The sa_db_tbsm_update.sql file is used to define the trigger named update_tbsm_serice_on_sa_eents in OMNIbus. This trigger ensures that TBSM reprocesses eents if one of the states that are used in the text-based incoming status rules changes, een if the seerity alue does not change. Wheneer you want to use the text-based incoming status rules included in the EEZ_SystemAutomationResource serice template, create this trigger definition. 214 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

233 Enter the following command on the OMNIbus serer to define the trigger: UNIX: $OMNIHOME/bin/nco_sql -serer NCOMS -username root < sa_db_tbsm_update.sql Windows: %NCHOME%\bin\redist\isql -S NCOMS -U root < sa_db_tbsm_update.sql Enter password when prompted. sa_db_tbsm_update.sql is shipped with System Automation Application Manager and can be found in the directory /integration on the product DVD. Configuring the Discoery Library Toolkit 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 Language (IdML) discoery book. For more information, refer to Working with the discoery library adapter on page 256. You can use the Discoery Library Toolkit of TBSM to create TBSM serice models from such an IdML book. Using the Discoery Library Adapter automates the following tasks: Import the System Automation Application Manager resources into the serice model of TBSM. The new serice instances show the grouping hierarchy defined in the end-to-end automation policy. Assign the System Automation Serice Template containing the incoming status rules to the TBSM serices Match System Automation Application Manager eents with the TBSM serice instance without manual configuration. Define the launch-in-context parameters of a serice instance to enable launching to the SA Operations Console in context of the serice instance. IdML Books are XML files in the Identity Markup Language (IdML) format. These XML files conform to the IBM Common Data Model (CDM) and can be generated by a ariety of systems and applications. They are used by the Discoery Library Toolkit to discoer resources and relationships in a gien enironment. This topic describes how you can set up the Discoery Library Toolkit to enable TBSM to discoer a serice tree based on the actie System Automation Application Manager resource topology. Make sure the following products are installed and configured, before an IdML book generated by System Automation Application Manager can be imported into TBSM: Install the Discoery Library Toolkit of TBSM. Configure TBSM to work with the Discoery Library Toolkit. Ensure that BSM_Templates.radsh and EEZ_SystemAutomationResource.radsh hae been run and that the templates and policies hae been added to your TBSM configuration. For more information, refer to infocenter/tiihelp/3r1/index.jsp?topic=/com.ibm.tioli.itbsm.doc/ welcome.htm. Chapter 4. Integrating 215

234 To correctly manage the data from System Automation Application Manager, modify the following XML control files on the TBSM serer: Define a template mapping for the EEZ_SystemAutomationResource template in the CDM_TO_TBSM4x_MAP_Templates.xml file. Define an Eent Identification Rule for System Automation eents in the EentIdentifierRules.xml file. Make sure that importing of relationships except of group relationships is disabled by specifying a rule in CDM_TO_TBSM4x_MAP.xml. You can find the three xml customization files in the directory $TBSM_HOME/XMLToolkit/xml. Defining template mapping To automatically assign the EEZ_SystemautomationResource template to the imported serice instances while the IdML book is imported, perform the following configuration steps: 1. Open the CDM_TO_TBSM4x_MAP_Templates.xml file in an text editor. 2. Search for the line <template primary= BSM_BusinessSerice >. 3. Add <othertemplate name= EEZ_SystemAutomationResource /> to the XML element. The added line is marked in bold: <template primary= BSM_BusinessSerice > <othertemplate name= SCR_RetrieeDependentObjectsTemplate /> <othertemplate name= SCR_SericeComponentRawStatusTemplate /> <othertemplate name= EEZ_SystemAutomationResource /> <cdmclass name= cdm:sys.businesssystem /> <cdmclass name= cdm:process.businessserice /> </template> This change will automatically assign the EEZ_SystemAutomationResource serice template to all serices of class cdm:sys.businesssystem that are imported using the DLA toolkit. Customizing TBSM dependency generation The System Automation Application Manager DLA toolkit stores group and other relationships like start or stop dependencies into the IdML book. Group relationship are stored using the relation type cdm:federates, whereas non-group relationships like start or stop dependencies are stored using the relation type cdm:uses. If you want to only import the group hierarchy but not the non-group relationships with the group relationships into the serice model of TBSM, you hae to disable the generation of dependencies for the relation type cdm:uses. This simplifies the graphical representation of the resulting serice graph in TBSM. Perform the following steps to disable the generation of dependencies between serice instances for non-group relations: 1. Open the CDM_TO_TBSM4x_MAP.xml file in an text editor. 2. Add the following line within the <RelationshipInfo> tag: <class type= cdm:uses isdependency= false priority= medium source= cdm:sys.businesssystem target= cdm:sys.businesssystem /> After you added this line, the DLA toolkit no longer generates dependencies between imported serice instances for the non-group relationship type cdm:uses. 216 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

235 Customizing eent identification To associate any eent with a serice instance imported from an IdML book, identification fields are required. If an eent is receied that has a matching field name and alue as the serice instance, the eent is applied to the instance. Status rules proided by System Automation use the AlertKey field for serice identification. All System Automation eents hae an AlertKey field set with an unique source token alue which represents a resource key. The resources contained in a IdML book created by System Automation Application Manager contain a source token attribute as well. Define a policy to match System Automation eents coming with the corresponding serice instance by setting the AlertKey field to the source token alue of the resource. The generation of TBSM serices identification field alue pairs is implemented by defining rules in the EentIdentifierRules.xml file. 1. Open the EentIdentifierRules.xml file in an text editor. 2. Add the following policy and mapping elements to this file: <Policy name="systemautomationapplicationmanager"> <Rule name="sourcetokenasalertkey" field="alertkey"> <Token keyword="sourcetoken" alue= IBM Tioli System Automation Application Manager /> </Rule> </Policy> <Mapping policy="systemautomationapplicationmanager" class="cdm:sys.businesssystem" /> When importing a resource of class cdm:sys.businesssystem this policy sets the AlertKey field for all status rules of the corresponding serice to the System Automation Application Manager source token alue. As a result, each TBSM serice instance created from a System Automation Application Manager IdML book has a unique AlertKey field alue. Wheneer TBSM detects an eent with this AlertKey field alue, it checks the eent for status information for the associated serice. After you entered the changes to the XML control files, restart the TBSM Discoery Library Toolkit serice to actiate the changes. Integrating System Automation resources in TBSM This topic describes how you can add System Automation resources to a TBSM serice tree. For resources which are contained in the end-to-end automation policy, you can make use of the DLA to automatically import these resources into TBSM. This is described in Importing resources automatically on page 218. If you want to add System Automation resources to TBSM which are not part of the end-to-end automation policy, for example resources managed by System Automation for Multiplatforms, you hae to manually create a serice instance in TBSM and then assign the System Automation Serice Template. This is described in Assigning manually the serice template to a serice instance on page 220. You also do this if you want to enrich serice instances which already exist in a TBSM serice tree with information from System Automation eents. Chapter 4. Integrating 217

236 Importing resources automatically Generating a System Automation Application Manager IdML book: Use the command eezdla to create IdML books for System Automation Application Manager. Perform the following steps: 1. Log on to the system on which the automation manager runs. 2. Enter eezdla. The created IdML book is stored at the location which you configured on the Discoery Library Adapter tab in the end-to-end configuration tool. On the same tab you can configure to copy the IdML book to a remote TBSM serer. Naming conentions: Names of IdML books that are created by System Automation Application Manager start with the application code EEZ, followed by the host name of the system on which the automation manager is installed and an UTC timestamp. Example: EEZ3210.e2esr1.friendly.com T Z.refresh.xml Importing a System Automation Application Manager IdML book into TBSM: If the Discoery Library toolkit serice is running, it automatically consumes IdML books aailable in a specific directory on the TBSM serer. You can configure the specific directory using the Discoery Library toolkit. The default directory for the location of IdML books is: $TBSM_HOME/discoery/dlbooks The System Automation Application Manager DLA can either be configured to automatically sae its IdML books in that directory on the TBSM serer or the resulting IdML book needs to be manually copied to that location. The discoery library toolkit serice consumes the IdML book from System Automation Application Manager and populates the serice component registry with System Automation Application Manager resources. The processing of the IdML book can be alidated by checking the msggtm_xt.log file for a message that is similar to the following: GTMCL5290I: Book EEZ3210.p720sa02.boeblingen.de.ibm.com T Z. refresh.xml processed successfully. The default directory for the location of the log file is: UNIX: $TBSM_HOME/XMLtoolkit/log Windows: %TBSM_HOME%\XMLtoolkit\log Note: The DLA Toolkit serice can be started in the following way: UNIX: Start the Discoery Library Toolkit daemon by running the tbsmrdr_start.sh script in the $TBSM_HOME/XMLtoolkit/bin directory. The daemon is added to the etc/init.d directory and is automatically restarted if you restart the TBSM host. 218 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

237 Windows: Start the Discoery Library Toolkit serice from the Serices window or by issuing the net start ASICRToolkitSc command. Verifying imported serices: You can use the following procedure to erify that the serice instances are imported correctly into the Serice Component Registry : 1. Select Administration > Serice Administration in the Tioli Integrated Portal console task list. 2. Select Serice Component Repository from the pull-down menu in the Serice Naigation portlet. 3. Expand Component Repository > Business Serices. The imported end-to-end automation domains and resources are displayed below the Business Serices entry. You can expand the domains and resource groups to erify that the group hierarchy has been created correctly. 4. Expand the end-to-end automation domain corresponding to the IdML Book which has been imported. Select one of the contained top-leel resources. 5. Select the Edit Serice tab in the Serice Editor portlet to edit the serice. 6. Select the Templates tab and erify that the serice template EEZ_SystemAutomationResource is listed in the Selected Templates list. 7. Select the Identification Fields tab and erify that for the incoming status rules of the EEZ_SystemAutomationResource template, the AlertKey field has a alue corresponding to the resource s source token. For example EEZResourceKey,DN={E2E_Domain},NN={},RN={Online Trading Application},RC={ResourceGroup} 8. Select the Additional tab and erify that the sourcecontactinfo and sourcetoken attributes for System Automation Application Manager are set correctly. 9. If the serices hae been imported correctly, a resource status eent of System Automation Application Manager influences the TBSM state displayed in the serice tree. You can test this, for example by stopping a group member defined in the end-to-end automation domain using the SA Operations Console. The group should then show a Warning state in TBSM based on the compound state changes of the group. Adding imported serices to a serice model: Once the System Automation Application Manager IdML book is processed and the serice component registry (SCR) is populated, the objects created in the SCR can be used to create a business serice in TBSM depending upon the requirement of the serice model: 1. Select Administration > Serice Administration in the Tioli Integrated Portal console task list. 2. In the Serice Naigation portlet, create a new top-leel serice instance as container for the imported System Automation serices. Or select an existing serice instance as parent of the new System Automation resources. 3. Select the Edit Serice tab in the Serice Editor portlet to edit this serice. 4. Select the Dependents tab and click the Add from Serice Component Repository button. The Serice Tree window opens. 5. Expand Component Registry > Business Serices > <your end-to-end automation domain>. Chapter 4. Integrating 219

238 6. Select the top-leel resource groups that you want to add to your serice model. They will be added as children of the container serice that you created in step When you hae finished adding serices, close the Serice Tree popup window and sae the serice instance. Assigning manually the serice template to a serice instance If you want to add System Automation resources to TBSM which are not part of the end-to-end automation policy, for example resources managed by System Automation for Multiplatforms, create manually a serice instance in TBSM and then assign the System Automation Serice Template. You also do this if you want to enrich serice instances which already exist in a TBSM serice tree with information from System Automation eents. A serice template consists of rules that can be applied for serice instances. A template can be used for more than one instance. If you want to assign the EEZ_SystemAutomationResource template to a serice, you can tag the serice with the template. Proceed as follows: 1. Tag serices using the EEZ_SystemAutomationResource template to make the defined incoming status rules aailable to these serices. a. In the Serice Naigation portlet, select the Serice Name for which you want to assign the System Automation specific serice template EEZ_SystemAutomationResource. b. Select the Edit Serice tab in the Serice Editor to edit the serice. c. Select the Templates tab. You can see the following two lists: Aailable Templates: Displays all templates which you hae the permission to assign to the selected serice instance. Selected Templates: Displays all templates assigned to the serice. d. To assign the System Automation template to a serice, select the EEZ_SystemAutomationResource template from the Aailable Templates list. Click the arrow button >> to moe the template to the Selected Templates list. 2. Configure the Identification Field alues for this serice. TBSM uses the Identification Fields to map incoming eents to a serice instance. a. Select the Edit Serice tab. b. Select the Identification Fields tab which proides the rules defined in the EEZ_SystemAutomationResource template and the identification field alues required to map an eent to the selected serice instance. 220 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

239 Figure 26. Identification Fields tab The rules contained in the EEZ_SystemAutomationResource template use the AlertKey eent attribute as identifier. By default, the alue for each identification field is the alue entered in the Serice Name field. c. Enter the correct AlertKey attribute alue that corresponds to the selected serice. The AlertKey must contain the unique System Automation resource key formatted as CDM SourceToken. The structure is defined like this: EEZResourceKey,DN={DomainName},NN={NodeName},RN={ResourceName}, RC={ResourceClass} You may consider to open one of the eents of the resource and copy and paste the AlertKey alue from the eent to aoid typing errors. Examples for alid AlertKey alues: 1) Resource: SA MP constituent or fixed resource Domain: DB2Cluster Displayed by lssam as: IBM.Application:db2-rs:saxb32c AlertKey: EEZResourceKey,DN={DB2Cluster},NN={saxb32c},RN={db2- rs}, RC={IBM.Application} 2) SA MP moe group (floating resource) Domain: DB2Cluster Displayed by lssam as: IBM.Application:db2-rs AlertKey: EEZResourceKey,DN={DB2Cluster},NN={},RN={db2- rs},rc={ibm.application} 3) SA MP resource group Domain: DB2Cluster Displayed by lssam as: IBM.ResourceGroup:DB2 AlertKey: EEZResourceKey,DN={DB2Cluster},NN={},RN={DB2}, RC={IBM.ResourceGroup} 4) Resource: SA AM resource group Chapter 4. Integrating 221

240 Domain: E2E_Domain Displayed by the Operations Console as: Online Trading Application AlertKey: EEZResourceKey,DN={E2E_Domain},NN={},RN={Online Trading Application}, RC={ResourceGroup} 5) Resource: SA AM resource reference Domain: E2E_Domain Displayed by the Operations Console as: DB2 and the referenced resource is located in the first-leel automation domain DB2Cluster AlertKey: EEZResourceKey,DN={E2E_Domain},NN={DB2Cluster},RN={DB2}, RC={ResourceReference} Note: The referenced first-leel automation domain must be used as node name of the AlertKey (NN={FLA-Domain}) 6) Resource: SA AM choice group Domain: E2E_Domain Displayed by the Operations Console as: DB2 CG AlertKey: EEZResourceKey,DN={E2E_Domain},NN={},RN={DB2 CG},RC={ChoiceGroup} d. Click the Additional tab for the serice instance. The tab shows the additional attributes defined for this serice instance. The attribute IBM_Tioli_System_Automation_Application_Manager_sourceToken is used for the launch-in-context action that supports launching from TBSM to the SA Operations Console. e. Oerwrite the attribute alue for IBM_Tioli_System_Automation_Application_Manager_sourceToken to contain the SA source token that corresponds to this serice instance. This is the same alue that has been specified for the AlertKey attributes on the Identification tab. f. Click Sae to apply your changes. Wheneer new System Automation state change eents are receied for the serice which match the specified AlertKey, TBSM will now process the incoming status rules and potentially change the oerall state of the serice based on the eent seerity. Customizing TBSM iews to add information from System Automation The EEZ_SystemAutomationResource Serice Template contains text-based Incoming Status Rules which retriee the System Automation Obsered State and other System Automation specific states of a resource. This information can be used in TBSM Views in order to enrich serice instances with information coming from System Automation. The following text-based incoming status rules are aailable: 222 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

241 Table 48. Text-based incoming status rules for TBSM Rule Name SAObseredStateValue SADesiredStateValue SAOperationalStateValue SACompoundStateValue SAExcludedFromAutomationValue Description Retriees the field SAObseredState from a resource status change eent. Possible alues: Unknown Online Offline Starting Stopping NotApplicable Retriees the field SADesiredState from a resource status change eent. Possible alues: Online Offline NoChange (i.e. the resource s automation goal cannot be changed by an operator) Retriee the field SAOperationalStateValue from a resource status change eent. List of Operational State alues giing more fine-grained information about the current state of the resource. For a list of possible alues, see the SystemAutomation.baroc file. Retriee the field SACompoundStateValue from a resource status change eent. Compound State indicating whether the resource is working as desired or has encountered an error. Possible alues: Ok Warning Error Fatal Retriee the field SAExcludedFromAutomationValue from a resource status change eent. Flag indicating if the resource is excluded from automation (i.e. automation is suspended). Possible alues: NotExcluded Excluded You can modify the columns of custom trees displayed in TBSM in the Serice Naigation portlet Serice Tree portlet The default Serice Naigation portlet has three columns: State Time Eents Chapter 4. Integrating 223

242 You can modify, delete, and add tree columns with the Tree Template Editor. The Tree Template Editor is aailable from the Serices toolbar in the Serice Naigation portlet. You can add a new tree template to the Serice Naigation portlet. For each custom column, use the Tree Template Editor to specify the rule data you want to display in the column. Adding columns: This capability can be used to add columns for any of the proided text-based incoming status rules defined by the EEZ_SystemAutomationResource template. For example, you can define a column which displays the current Obsered State coming from System Automation for each serice instance that has the EEZ_SystemAutomationResource template assigned. Perform the following steps: 1. Click the Tree Template Editor button in the toolbar of the Serice Naigation portlet. 2. Select the tree template you want to modify in the Tree Template Name drop-down list. 3. Click the Add New Tree Column button in the Column Configuration section. 4. Type the name you want to use in the blank field for the new column, for example Aailability State. 5. Adjust the column position and width as appropriate 6. In the Serice Template Selection section, select the EEZ_SystemAutomationResource template. 7. In the Serice Template Rule Mapping, select the EEZ_SystemAutomationResource template in the Actie Template list. 8. For each rule that you want to display in a serice tree column, select the Display check box and choose a column from the drop-down box to display the output alue. In this example, select the Display check box for the and choose the Aailability State column from the drop-down box of that row. 9. Click OK to sae the changes to the tree template. The following figure shows a screen capture of the tree template editor. A new column Aailability State is added showing the System Automation Obsered State: 224 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

243 Figure 27. Tree template editor To iew the updated Serices Tree, refresh the Serice Naigation portlet. The new column now occurs showing the output of the incoming status rule that you hae selected. Note: You hae to create new resource status change eents in order to update the state information displayed in TBSM. Old eents are not processed again. Using the TBSM policy editor: Optionally, you can format column alues using the TBSM policy editor. For example, display the SA Obsered State alues in different colors. Proceed as follows: 1. Click the Tree Template Editor button in the toolbar of the Serice Naigation portlet. 2. Choose the tree template you want to modify from the Tree Template Name drop-down list. Chapter 4. Integrating 225

244 3. Click on the Edit Policy... button to open the policy that displays column alues. The policy named GetTreeColumnValue is opened in the policy editor: 4. Modify the policy. The following code snippet is as an example on how to change the color of the text-based output alues. In this example, it is assumed that a column named Aailability State has been defined showing the output of the SAObseredState Rule. Depending on the alue of the obsered state, the policy snippet returns the alue in a different color: if (columnname = Aailability State ) { if (alue = Unknown ) { VALUE = <font color="blue"> <b>unknown</b></font> ; } if (alue = Online ) { VALUE = <font color="green"> <b>online</b></font> ; } if (alue = Offline ) { VALUE = <font color="red"> <b>offline</b></font> ; } if (alue = Stopping ) { VALUE = <font color="blue"> <b>stopping</b></font> ; } if (alue = Starting ) { VALUE = <font color="blue"> <b>starting</b></font> ; } } 5. Sae the modified policy Configuring Tioli Business Serice Manager launch-in-context support You can define a launch-in-context entry for a TBSM serice tree that enables you to launch the SA Operations Console in context of the currently selected serice instance. Refer to From TBSM to System Automation on page 227 for more information. You can also set up launch-in-context support to launch from a resource displayed in the SA Operations Console to the TBSM Web user interface. Refer to From System Automation to TBSM for more information. From System Automation to TBSM You can set up launch-in-context support to launch from a resource displayed in the SA Operations Console to the TBSM Web user interface. This launch-in-context support enables users to launch the Serice Aailability Workspace of the Tioli Integrated Portal and automatically select the corresponding serice instance in the TBSM Serice Viewer with a single mouse click. When TBSM launch-in-context support is configured, a hyperlink becomes aailable in the System Automation operations console on the General page of those resources that are contained in an end-to-end automation domain. This hyperlink naigates to the corresponding serice instance in the TBSM Serice Viewer. Note: The TBSM launch-in-context support is only aailable for resources which hae been imported into TBSM using the Discoery Library Toolkit. 226 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

245 Perform the following steps to configure TBSM launch-in-context support for the SA Operations Console: Procedure 1. Logon to the Dashboard Application Serices Hub on the system where System Automation Application Manager is installed. 2. Naigate to Tioli System Automation -> Settings -> TBSM Launch-in-Context Configuration 3. Select to enable launch-in-context support in the Enable launch-in-context support for TBSM. 4. Specify the name of the serer on which the Tioli Integrated Portal runs, which hosts the TBSM Web GUI, in the Serer name used to connect to Tioli Integrated Portal field. 5. Specify the secure port number of the serer on which Tioli Integrated Portal runs in the Port number used to connect to Tioli Integrated Portal. The default port number is Click OK to sae the configuration Results Note: If the operations console is displayed while the TBSM launch-in-context configuration is changed, select Menu -> Refresh all to pick up the changed settings in the current instance of the Operations Console. From TBSM to System Automation The launch-in-context action uses the following attributes of a serice that must be stored in a serice s additional attributes in order to be able to perform the launch: IBM_Tioli_System_Automation_Application_Manager_sourceContactInfo This attribute contains the launch URL including the hostname and the port number of the System Automation Application Manager. IBM_Tioli_System_Automation_Application_Manager_sourceToken This attribute contains the unique source token attribute as defined by the System Automation Application Manager DLA. It represents the resource key identifying the System Automation resource corresponding to this serice instance. For example: EEZResourceKey,DN={FriendlyE2E},NN={},RN={DR_Portal},RC={ResourceGroup} For System Automation Application Manager resources contained in an end-to-end automation policy which are imported using the Discoery Library Toolkit, both attributes are automatically filled with the right alues when importing the DL book into TBSM. If the resource is manually created without the DLA Toolkit or for SA MP resources (for which no DLA exists), these attributes must be manually created in a serice s additional attributes if Launch-in-Context to SA is to be exploited. Specify the sourcetoken field for each serice instance that has not been imported ia Discoery Library Toolkit. Refer to Assigning manually the serice template to a serice instance on page 220 for more information. Chapter 4. Integrating 227

246 The sourcecontactinfo field can be specified in the EEZ_SystemAutomationResource Serice Template because it contains generic information which is alid for all System Automation resources. The additional attribute IBM_Tioli_System_Automation_Application_Manager_sourceContactInfo contains the URL of the System Automation Application Manager host to which the launch-in-context action will connect. If you want to use launch-in-context for serices which hae been manually tagged with the EEZ_SystemAutomationResource template, you need to manually adapt the URL in the Serice Template. This is not required if you only hae serices that are imported using the Discoery Library Toolkit. Follow these steps to adapt the EEZ_SystemAutomationResource template for Launch-in-Context: 1. Select Templates from the Serice Naigation drop down menu. 2. Select the EEZ_SystemAutomationResource template in the Serice Naigation portlet 3. Click the Edit Template tab in the Serice Editor to edit the template 4. From the Edit Template tab, click the Additional tab. 5. The parameter IBM_Tioli_System_Automation_Application_Manager_sourceContactInfo has the default alue: Replace <SA_ISC_Hostname> with the correct hostname of the system where the System Automation Application Manager operations console is running. Also change the port number if required. 6. Click Sae to apply your changes Defining launch-in-context action: This topic describes how to define a new launch-in-context action for a custom serice iew in TBSM, which will appear in the context menu of a serice instance. Create a new iew definition. The View Definitions feature of TBSM allows you to change the isual content that is displayed in your Serice Editor or Viewer portlet and change the alues that appear in the isual elements. In addition it allows to define actions. Actions are the options aailable to you as the result of clicking, double clicking, or right-clicking a serice in the Serice Editor. You cannot modify the pre-defined View Definitions, therefore you hae to create a new View Definition to be able to define a new action: 1. Select Serices from the Serice Naigation drop down menu. 2. Click a serice in the Serice Naigation portlet. The default iew definition for the serice model opens in the Serice Editor or Viewer. 3. In the View Serice tab, select the iew definition you want to work with from the View Definition drop-down list. 4. Click the Edit View Definition button. The Edit View Definition window opens. 5. To create a iew definition, click Sae as New. The Sae As window opens. 6. Type the name of your iew definition in the Sae as New field and click OK. 228 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

247 A new launch-in-context action needs to be defined to the new iew definition. Add the System Automation launch-in-context action to the System Automation specific serice template EEZ_SystemAutomationResource, so that the launch-in-context action is only aailable to serices tagged with this template: 1. In the View Definition drop-down list, select your View Definition and click the Edit View Definition button to reopen the Edit View Definition window. 2. Click the Actions tab in the Edit View Definition window. The Actions tab opens. 3. Select the EEZ_SystemAutomationResource template from the Serice Template drop-down list. 4. To add a new action, click the Edit button next to the Edit Action selection list. The Edit Canas Action window opens. 5. Define a new Action using the following parameters: Table 49. Launch-in-context action parameters Attribute Action Name Action Display Name Action Description Action URL Action Frame Value ShowSAResource Show Serice in SA Operations Console Launch the serice in the Tioli System Automation Operations Console IBM_Tioli_System_Automation_Application_Manager_ sourcecontactinfo?sourcetoken= URLEncode(IBM_Tioli_ System_Automation_Application_Manager_sourceToken) SystemAutomation 6. Click OK 7. Add the new action to the context menu. You hae two options: a. If you want the launch menu entry to be isible only for serices that hae the EEZ_SystemAutomationResource template assigned as primary template, select the EEZ_SystemAutomationResource template from the Serice Template drop-down list. b. If you want the launch menu entry to be always isible for all kinds of serices, click on the Set Defaults button. Note: If you hae assigned the EEZ_SystemAutomationResource to serices that hae been tagged with a different primary template, you hae to use option b) to be able to use the launch-in-context action for these serices. 8. To add the new action as a right-click action, click the New button to add a new row to the right click menu options action list. A blank row is added to the Actions list. 9. Select the new action from the drop-down list. 10. Click Apply to sae the action. 11. Click OK to close the Edit View Definition window. Exporting SA specific additional attributes for use in LiC Action: By default, TBSM proides a set of attributes to use for actions. The following attributes are not aailable to use for launch-in-context actions: IBM_Tioli_System_Automation_Application_Manager_sourceContactInfo Chapter 4. Integrating 229

248 IBM_Tioli_System_Automation_Application_Manager_sourceToken To make the actions aailable, you need to edit the.xml file for the iew definition. Add an fieldtopasstomodelexpr tag for each attribute that you want to use in the action. Page Exporting SA specific additional attributes for use in LiC Action on page 229 proides an example for a fieldtopasstomodelexpr tag. The following directory contains the xml files that configure iew definitions: UNIX: $TBSM_DATA_SERVER_HOME/a/xmlconfig Windows: %TBSM_DATA_SERVER_HOME%\a\xmlconfig View definition xml files hae the following format: ViewDefinition_<ViewDefName>.xml ViewDefName is the name of the iew definition in the TBSM console. For example, the name of the file for a custom iew definition called MyView is: ViewDefinition_MyView.xml To enable the launch-in-context action, add the following elements to the <datatypemapping> element in the iew definition xml file: <fieldtopasstomodelexpr modelfield="ibm_tioli_system_automation_application_manager_sourcecontactinfo"> IBM_Tioli_System_Automation_Application_Manager_sourceContactInfo</fieldToPassToModelExpr> <fieldtopasstomodelexpr modelfield="ibm_tioli_system_automation_application_manager_sourcetoken"> IBM_Tioli_System_Automation_Application_Manager_sourceToken</fieldToPassToModelExpr> This will make the two attributes aailable to use in the launch-in-context action. Note: You hae to restart the Tioli Integrated Portal Serer to actiate this change in TBSM. Tioli Monitoring and Tioli Composite Application Manager The Tioli Monitoring (Tioli Monitoring) and Tioli Composite Application Manager (ITCAM) family proides aailability and performance monitoring of essential system resources and applications on a wide ariety of operating systems and platforms. System Automation Application Manager can be used to control and automate resources, which are monitored by Tioli Monitoring or ITCAM. System Automation Application Manager integrates with Tioli Monitoring and ITCAM by using existing Tioli Monitoring resource instrumentation (Tioli Monitoring agents). The System Automation Application Manager retriees monitoring information from Tioli Monitoring agents and executes start and stop operations using Tioli Monitoring agents. Software components, which were only monitored by Tioli Monitoring can be resources that are managed by System Automation Application Manager. Tioli Monitoring resources can be automated members of complex business applications within System Automation Application Manager policies. Tioli Monitoring deliers a wide ariety of agents that can integrate with System Automation Application Manager: Application agents (also referred to as non-os agents), including custom agents OS agents 230 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

249 SA Application Manager proides predefined templates for the integration of the following agents: Apache web Serer WebSphere Application Serer DB2 Custom agents, which are built by the Tioli Monitoring Agent Builder Linux OS agent UNIX OS agent Create resource definitions for Tioli Monitoring resources based on these templates. For a complete oeriew, and about the adantages of the Tioli Monitoring integration, refer to IBM Tioli System Automation Application Manager Administrator's and User's Guide, Integrating with Tioli Monitoring and Tioli Composite Application Manager". Prerequisites Supported Tioli Monitoring ersions for this feature are: IBM Tioli Monitoring 6.1, 6.2.1, and Tioli Monitoring oeriew The following illustration gies an oeriew of a typical Tioli Monitoring management infrastructure with all its components in order to introduce terms that are used later in this document. For a more detailed description of this infrastructure, refer to the Tioli Monitoring documentation. Figure 28. Oeriew of the IBM Tioli Monitoring infrastructure The IBM Tioli Monitoring architecture is a multi-tiered client/serer enironment consisting of the following four main components that monitor mission critical systems throughout the enterprise: Chapter 4. Integrating 231

250 The Tioli Enterprise Portal (TEP) Client is a presentation interface that is browser or desktop (thick client) based and is used to iew and monitor the enterprise. The Tioli Enterprise Portal Serer proides the core presentation layer for retrieal, manipulation, analysis, and pre-formatting of data. The portal serer retriees data from the hub Tioli Enterprise Monitoring Serer monitoring serer in response to user actions at the portal client, and sends the data back to the portal client for presentation. The portal serer also proides presentation information to the portal client so that it can render the user interface iews suitably. The Tioli Enterprise Monitoring Serer acts as a collection and control point for alerts receied from the agents, and collects their performance and aailability data. The monitoring serer also manages the connection status of the agents. Large-scale enironments usually include a number of monitoring serers to distribute the load. One of the monitoring serers is designated the hub monitoring serer, and the remaining serers are termed remote monitoring serers, often called RTEMS. The hub monitoring serer also proides a SOAP interface which can be used to query Tioli Monitoring data and issue commands ia Tioli Monitoring agents on the endpoints. The SOAP interface is also used for the integration of SA Application Manager with Tioli Monitoring to retriee monitoring information from the agents and to perform start and stop commands on the endpoints. The Tioli Enterprise Monitoring Agents (TEMA) are installed on the systems or subsystems you want to monitor. These agents collect data from monitored, or managed, systems, and distribute this information to a monitoring serer. Tioli Data Warehouse which is used for storing historical data collected from agents in the enironment. To store data in this database, you must install the Warehouse Proxy agent. To perform aggregation and pruning functions on the data, you must also install the Summarization and Pruning agent. The Data Warehouse component is not required for the SA Application Manager integration. The Tioli Enterprise Monitoring Agents (TEMA) can be of the following types: Application agents (non-os agents) that monitor the aailability and performance of systems, subsystems, and applications. Those agents often include predefined commands to start and stop the managed application. An example of an application agent is IBM Tioli Composite Application Manager Agent for WebSphere Applications, which monitors WebSphere Application Serer instances. You can also create your own application agents ia the Agent Builder, a set of tools for creating custom agents. Using the Agent Builder, you can quickly create, modify, and test an agent to collect and analyze data about the state and performance of different resources, such as disks, memory, CPU, or applications. Operating system (OS) agents that monitor the aailability and performance of the operating systems (computers). An example of an OS agent is the Monitoring Agent for Linux OS, which monitors end points running a Linux operating system. Eery Tioli Monitoring agent has a two letter product code uniquely identifying the agent type. Some examples are: HT IBM Tioli Composite Application Manager Agent for Web Serers UD IBM Tioli Composite Application Manager Agent for DB2 232 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

251 YN IBM Tioli Composite Application Manager Agent for WebSphere Applications LZ Linux Monitoring Agent NT IBM Tioli Monitoring for Windows Serers UX UNIX OS Monitoring Agent Custom agents hae a product code within the resered range System Automation Application Manager uses the Agentless Adapter to integrate with the Tioli Monitoring infrastructure. For more information about the Agentless Adapter, see IBM Tioli System Automation Application Manager Administrator's and User's Guide, "Product Oeriew, Concepts and components, Using the Agentless Adapter to access Tioli Monitoring Resources. For information about starting and stopping Tioli Monitoring managed resources, see IBM Tioli System Automation Application Manager Administrator's and User's Guide, " Starting and Stopping Tioli Monitoring managed Resources". For information about monitoring resources managed by Tioli Monitoring, see IBM Tioli System Automation Application Manager Administrator's and User's Guide, "Administering, Defining Tioli Monitoring (ITM) Resources". Integrating with System Automation Application Manager The integration of Tioli Monitoring managed applications into System Automation end-to-end management: is a step by step process. The required steps are: 1. Use the configuration dialog cfgeezdmn to configure connectiity to the hub Tioli Enterprise Monitoring Serer, define a domain, and add users that can access the Tioli Monitoring SOAP serer. 2. Create a System Automation Tioli Monitoring resource in the Agentless Adapter policy. For an application agent for which a template is proided, create a new Tioli Monitoring resource based on this template. Refer to System Automation Application Manager Reference and Problem Determination Guide for a list of aailable agents. Definitions are already made for the resource and only minimal modifications are required to adapt the resource to your enironment, for example, modify the managed system name to match your target endpoint. For other agents, gather the following information to create a new System Automation Tioli Monitoring resource definition in the Agentless Adapter policy: Managed System Name of the agent Attribute group and name of the attribute that is used for monitoring. Mapping of the attribute alues to the common System Automation obsered state The command that must be used for starting and stopping the managed application 3. Actiate the Agentless Adapter policy using the operations console. Test that the defined Tioli Monitoring resource can be started and stopped and that it displays the correct obsered state. Chapter 4. Integrating 233

252 4. Add the Tioli Monitoring resource to the Application Manager end-to-end automation policy by creating a resource reference that refers to the Tioli Monitoring resource that is defined in the Agentless Adapter domain. 5. Actiate the modified Application Manager end-to-end automation policy. These steps are explained in detail in Configuring the Agentless Adapter for Tioli Monitoring Integration. Configuring the Agentless Adapter for Tioli Monitoring Integration You must perform a sequence of configuration steps to enable the Agentless Adapter to access the Tioli Monitoring Tioli Enterprise Monitoring Serer SOAP serer to control and monitor Tioli Monitoring resources. These resources are defined in the adapter automation policy. Use the cfgeezdmn configuration dialog. Log in to the system on which you installed the SA Application Manager, and perform the sequence of configuration steps described in the following topics: Procedure 1. Configuring the Agentless Adapter 2. Creating Agentless Adapter domains for Tioli Monitoring resources on page Configuring the properties to access the Tioli Monitoring SOAP serer on page Configuring user credentials to access the monitored resources on page Actiating the configuration changes on page 238 Configuring the Agentless Adapter: If you already configured an Agentless Adapter instance (local or remote) and you want to use it to monitor and control Tioli Monitoring resources, you can skip this step. Otherwise refer to Configuring Agentless Adapters on page 106 for instructions on how to configure an Agentless Adapter. If you want to use multiple Agentless Adapter instances to control Tioli Monitoring resources, you must perform the tasks that are described in the following sections for each of those Agentless Adapter instances. You can define multiple domains for one Agentless Adapter, which eliminates the need to use more than one Agentless Adapter instance. Use the cfgeezdmn configuration utility to perform the following steps: Procedure 1. Open the configuration dialog using the cfgeezdmn command. The task launcher of the configuration dialog is displayed. 2. Select the Non-clustered Nodes tab. 3. If you want to enable the integration of Tioli Monitoring resources for the local Agentless Adapter, click the Configure button for the local Agentless Adapter. If you want to enable the integration of Tioli Monitoring resources 234 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

253 for a remote Agentless Adapter, click Configure for remote Agentless Adapters and select the remote Agentless Adapter instance that you want to configure. The Agentless Adapter configuration dialog opens: Figure 29. Application Manager Local Agentless Adapter Configuration Creating Agentless Adapter domains for Tioli Monitoring resources: To create Agentless Adapter domains for Tioli Monitoring resources perform these steps: Procedure 1. Open the Agentless Adapter configuration as described in Configuring the Agentless Adapter on page On the Adapter tab of the configuration dialog, click Add. Choose a domain name in the dialog that is displayed, for example ITMDomain, and click OK. The Chapter 4. Integrating 235

254 new domain is displayed in the domain list of the configuration window. If you want to define multiple domains to contain Tioli Monitoring resources, use this dialog to define them. Configuring the properties to access the Tioli Monitoring SOAP serer: Complete the following steps to configure the connection between the Agentless Adapter and the Tioli Monitoring SOAP serer. The configuration changes must be applied to the Agentless Adapter instance (local or remote) determined in the preceding tasks. Procedure 1. Open the Agentless Adapter configuration as described in Configuring the Agentless Adapter on page Click on the Tioli Monitoring tab: 236 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

255 3. On the Tioli Monitoring tab, select Enable integration of ITM/ITCAM resources and specify the alues for the Tioli Monitoring SOAP serer configuration: Host name or IP address Specify the name or the IP address of the host where the hub monitoring serer that hosts the SOAP serice is running. SOAP serer port number Specify serice point port number of the SOAP serer hosted by the hub monitoring serer. The default number for a non-ssl port is The default number for an SSL port is If you selected to use Secure Socket Layer (SSL) for communication with the SOAP serer, you must specify a alid SSL port number. SOAP alias of hub Specify the alias name of the hub monitoring serer to which a SOAP request is routed. The request is routed to the hub monitoring serer which is on the same system as the SOAP serer. In this configuration, you must specify SOAP as the alias. If you want to route the SOAP request to a remote hub, specify the alias name of the remote hub. This alias must be preiously defined to the SOAP serer in the Tioli Monitoring SOAP serer configuration. Use SSL for communication with the SOAP serer Select this option if the Agentless Adapter uses Secure Socket Layer (SSL) for communication with the SOAP serer. If you select this option, you must specify a alid SSL port number in the SOAP serer port field. The https protocol is used for communication. Configuring user credentials to access the monitored resources: Any start / stop command or monitor query against an Tioli Monitoring agent is translated into a SOAP request to the Tioli Monitoring SOAP Serer on the hub monitoring serer. For each SOAP request, the Agentless Adapter authenticates against the SOAP serer using a user name and password. You can define a generic user ID which is used for all Tioli Monitoring resources for which no user ID is specified in the Agentless Adapter policy. You can also define specific user IDs if you want to use different users for Tioli Monitoring resources. In this case, you must specify a user ID for the Tioli Monitoring resource in the Agentless Adapter policy. You must also define the user credentials in the list of specific credentials for accessing the SOAP serer for each user ID that is specified for a Tioli Monitoring resource. Important: All Tioli Monitoring user IDs defined in the Agentless Adapter policy and in the configuration utility must be alid Tioli Monitoring users that can access the Tioli Monitoring SOAP serer. The users are authenticated through the hub monitoring serer. Depending on how the monitoring serer is configured, user IDs can be authenticated either by the local system registry of the system on which the hub monitoring serer runs or by an external LDAP-enabled central registry. In the Tioli Monitoring SOAP serer configuration, you can define users to a SOAP Serer and specify the access priileges for each user: Query or Update. Chapter 4. Integrating 237

256 The access priileges control what methods the user is allowed to use. Update access includes Query access. User IDs used by the Agentless Adapter to connect to the Tioli Monitoring SOAP Serer to start, stop, and monitor remote Tioli Monitoring resources require the Query access. Complete the following steps to define one or more user credentials used by the Agentless Adapter when connecting to the hub Tioli Enterprise Monitoring Serer to control or monitor an Tioli Monitoring resource. Procedure 1. Open the Agentless Adapter configuration as described in Configuring the Agentless Adapter on page Select the Tioli Monitoring tab 3. On the Tioli Monitoring tab, either specify a generic or a specific user ID or both: a. For specific user IDs, click Add and specify a new user ID and password in the dialog that is displayed. Click OK. The new user is displayed in the list of specific credentials. If you want to use a specific ID, you must specify it for a Tioli Monitoring resource in the Agentless Adapter policy. b. For the generic user ID, enter the username in the corresponding entry field and click Change to specify a password for the generic user. This generic user is used for all Tioli Monitoring resources in the Agentless Adapter policy for which no user ID is specified. If you decide to omit the user ID for at least one of the Tioli Monitoring resources in the Agentless Adapter policy, you must define a generic user. c. Click Sae to sae the configuration changes that you applied in the preceding tasks. Actiating the configuration changes: By completing the tasks described in the preceding sections, you modified the configuration of an Agentless Adapter instance and you enabled this adapter to monitor and control Tioli Monitoring resources. You must now actiate the configuration changes by performing these steps: 1. Distribute the changed configuration (only for remote Agentless Adapters) Configurations are generally stored on the system where the SA Application Manager is installed. If you decided to use a remote Agentless Adapter instance for Tioli Monitoring resource automation, you must distribute the configuration from the system where the SA Application Manager is installed to the system where the corresponding Agentless Adapter is installed. Refer to Distributing a remote Agentless Adapter configuration on page 116 for a description of this task. 2. Start/restart the Agentless Adapter All configuration settings are stored in configuration properties files that the Agentless Adapter reads when it is started. If the Agentless Adapter is already running when you modify the configuration, the adapter must be stopped and restarted to load the new settings. Agentless Adapters are controlled by using the eezaladapter command. Use eezaladapter start to start the adapter. If the adapter is you must stop the adapter using eezaladapter stop, then start it. Refer to IBM Tioli System 238 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

257 Automation Application Manager Reference and Problem Determination Guide and Problem Determination Guide for details on the eezaladapter command. Creating a Tioli Monitoring resource in an Agentless Adapter policy To complete the steps to create the Tioli Monitoring resource, retriee information about your managed resources. These steps are described in Retrieing the required information about your Tioli Monitoring managed resources on page 244 and subsequent topics. Creating an Agentless Adapter policy for Tioli Monitoring resources: This topic describes how to create a policy for an Agentless Adapter domain which contains Tioli Monitoring resources. The policy pool directory for the Agentless Adapter contains a template policy file which can be used to create a new Agentless Adapter policy automating Tioli Monitoring resources. The policy template file is named SampleITMResourcePolicy.xml and is located in the Agentless Adapter policy pool directory. XML source of the policy template: <?xml ersion="1.0" encoding="utf-8"?> <AutomationPolicy ersion="1.0" xmlns=" xmlns:xsi=" xsi:schemalocation=" EEZALPolicy.xsd"> <PolicyInformation> <PolicyName>Template For ITM Resource In Agentless Adapter Domain</PolicyName> <!-- Replace domain$ with Agentless Adapter Domain Name --> <AutomationDomainName> domain$</automationdomainname> <PolicyToken> 0.0 </PolicyToken> <PolicyAuthor>Author of this policy</policyauthor> <PolicyDescription>This is a template.</policydescription> </PolicyInformation> <!-- *********************************************************************************** --> <!-- Use this template to create a policy for an agentless adapter domain to use ITM --> <!-- monitored resources in SA management. --> <!-- --> <!-- It is recommended not to mix resources of type IBM.RemoteResource and --> <!-- IBM.ITMResource together in one policy. Policies only defining IBM.RemoteResources --> <!-- can be easier created using the built-in SA Application Manager Policy Editor. --> <!-- --> <!-- Use the following section to copy from. Paste the IBM.ITMResourceAttributes and --> <!-- Resource description fields below and adapt them to your needs. --> <!-- *********************************************************************************** --> <IBM.ITMResourceAttributes name="itmagentresourceattributes" > <Owner>John Doe</Owner> <InfoLink> <Description>Some short description for the operator</description> <!-- Replace user$ with the TEMS user to be used for this resource --> <UserName> user$</username> <StartCommand></StartCommand> <StopCommand></StopCommand> <StartCommandTimeout>30</StartCommandTimeout> <StopCommandTimeout>30</StopCommandTimeout> <!-- Replace group$ with the attribute group used for SA state monitoring --> Chapter 4. Integrating 239

258 <!-- Replace attribute$ with the name of the attribute used for SA state monitoring --> <MonitorAttribute>$group$.$attribute>$</MonitorAttribute> <!-- Replace online$ with the attribute alue that maps to SA state Online --> <MonitorValueOnline> online$</monitorvalueonline> <!-- Replace offline$ with the attribute alue that maps to SA state Offline --> <MonitorValueOffline> offline$</monitorvalueoffline> <MonitorCommandPeriod>10</MonitorCommandPeriod> </IBM.ITMResourceAttributes> <!-- Replace system$ with the ITM Managed System Name --> <Resource name="my SA ITM Resource Name" class="ibm.itmresource" node=" system$"> <ClassAttributesReference> <IBM.ITMResourceAttributes name="itmagentresourceattributes"/> </ClassAttributesReference> </Resource> <!-- *********************************************************************************** --> <!-- Add you resource definitions here. Use sample policy snippets if applicable. --> <!-- *********************************************************************************** --> </AutomationPolicy> Sample policy snippets for commonly used monitoring agents are included in the snippets/itm directory of the System Automation Application Manager policy pool. For example: /etc/opt/ibm/tsamp/eez/policypool/snippets/itm If you want to define a Tioli Monitoring resource for one of these agents, copy the appropriate policy snippet into your Agentless Adapter policy and adjust the resource name and managed system name in order to suite your enironment. Policy snippets of the Agentless Adapter policy pool snippets directory: Snippet_DB2_agent.xml Snippet_WebSphere_agent.xml Snippet_Apache_agent.xml Snippet_custom_agent.xml Snippet_LinuxOS_agent.xml Snippet_UNIXOS_agent.xml Refer to IBM Tioli System Automation Application Manager Reference and Problem Determination Guide, for details about the properties used in the policy snippets. Use an XML editor to modify the proided policy template file and add new Tioli Monitoring resources. Follow these steps: 1. Copy the file SampleITMResourcePolicy.xml. By default, the file is located in the following directory: /etc/opt/ibm/tsamp/eez/aladapterpolicypool. 2. Open the file in an XML editor. 3. Update the PolicyInformation section of the policy. It is required that you specify at least the domain name of the Agentless Adapter domain you hae configured to interact with the TEMS correctly. It is recommended to also change the PolicyName and PolicyDescription of the policy. 4. Create a Tioli Monitoring resource. As you can see in the policy template, you typically hae to create the following for each new Tioli Monitoring Resource: a. One XML fragment of type IBM.ITMResourceAttributes with all the Tioli Monitoring agent specific properties. In this section you specify the Tioli Monitoring agent attributes which are used to determine the obsered state and how to map them to the System Automation Application Manager 240 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

259 obsered state. It also describes which actions are used to start or stop this resource. You can share one set of IBM.ITMResourceAttributes for multiple Tioli Monitoring resources. b. One XML fragment of type Resource with the corresponding instance of the IBM.ITMResourceAttributes as argument. Here you can define the name of your resource and identify which agent instance (managed system name) is used to monitor and control the application that is represented by this resource. The Tioli Monitoring managed system name is specified in the node attribute of the Resource element. Depending on whether a predefined agent policy snippet exists or not, choose one of the following steps: 1) If your Tioli Monitoring resource is monitored by a Tioli Monitoring agent for which a predefined policy snippet exists, create a Tioli Monitoring resource using a predefined template: a) Open one of the Snippet_*_agent.xml files in your editor. b) Copy the Resource and IBM.ITMResourceAttributes elements into your main policy document and adapt the attributes to match your enironment. The resources attributes contain predefined Tioli Monitoring agent specific settings such as the state mappings from the Tioli Monitoring agent state alues to System Automation state alues. The Description attribute proides an oeriew of the properties that you need to adapt to match your enironment. 2) If there is no predefined policy snippet for your Tioli Monitoring resource, copy and modify the XML elements of the generic Tioli Monitoring resource that is contained in the SampleITMResourcePolicy.xml template: Key attributes which hae to be defined for a Tioli Monitoring resource. All attributes are defined within the XML element IBM.ITMResourceAttributes. <StartCommand> and <StopCommand> These alues contain the exact command and arguments run by the Tioli Monitoring agent when the resource receies a start or stop request for the corresponding resource instance. The command can either be a predefined take action command supported by the Tioli Monitoring agent or any remote system command. To use a predefined take action command of a specific Tioli Monitoring agent, specify the name of the command and associated parameters. You do not need to specify a fully qualified file path. If you want to trigger a different command on the system, the fully qualified path to that command needs to be specified. The command is run on the managed system identified by the managed system name of the resource. <UserName> The alue defines a user name which is used to connect to the Tioli Monitoring SOAP serer running on the hub monitoring serer to submit the StartCommand and StopCommand and to query the Tioli Monitoring agent for the attribute specified in the MonitorAttribute element. Specify one of the user IDs configured using cfgeezdmn as specific Tioli Monitoring users. For more information, refer to Configuring user credentials to access the Chapter 4. Integrating 241

260 monitored resources on page 237. If you want to use the generic Tioli Monitoring user configured in cfgeezdmn, leae this attribute blank. <MonitorAttribute> The alue specifies the Tioli Monitoring agent attribute that is queried to determine the obsered state of the resource. The attribute consists of an attribute group and an attribute name within that group. The alue of the specified agent attribute is queried periodically to determine or update the obsered state of the resource. The attribute is specified as AttributeGroup.AttributeName. <MonitorValueOnline> and <MonitorValueOffline> Use these elements to specify which alue of the Tioli Monitoring attribute defined as MonitorAttribute is to be mapped to which System Automation obsered state. A MonitorValue<obsered_state_alue> element exists for eery aailable System Automation obsered state. Specify the monitor attribute alue which is mapped to this obsered state as alue of the XML element. You can map multiple Tioli Monitoring States to the same System Automation obsered state. If the monitor attribute has a alue for which no mapping to a System Automation obsered state exists, this alue is ignored and the obsered state of the Tioli Monitoring resource remains unchanged. If you are unsure about which alues to specify, refer to Retrieing the required information about your Tioli Monitoring managed resources on page 244 to obtain the correct ones. For a full description of all properties aailable for Tioli Monitoring resources, refer to IBM Tioli System Automation Application Manager Administrator's and User's Guide. In addition, refer to IBM Tioli System Automation Application Manager Reference and Problem Determination Guide for details about XML elements. 5. Sae the policy file in the Agentless Adapter policy pool. Using attribute filters in a monitor query: The Tioli Monitoring agent attribute group that was specified as part of the MonitorAttribute of the Tioli Monitoring resource is queried periodically. The query is performed to determine or update the obsered state of the resource. Agent attribute groups are returned as tables. For some agent attribute groups, more than one row of alues can be returned. For example, when a table of running processes is displayed, or if the agent monitors multiple application instances. If you want to use an attribute of such an attribute group as monitor attribute, you must specify a filter to locate the row in the table which contains the state of your Tioli Monitoring Resource. You use the MonitorQueryAttrFilter property to specify such a filter. You can specify the following filters: MonitorQueryAttrFilter This XML element is an optional element within the IBM.ITMResourceAttributes element. When querying the monitor attribute, this filter is applied to reduce the amount of returned data based on the filter criteria. In the filter, you can specify which attribute must meet which 242 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

261 filter criteria. Only the matching rows of the attribute group that contain the attribute are returned. A filter criteria has the three components Attribute Name, Operator, and Attribute Value. Attribute Name Is the name of the attribute on which the filter is applied. It must exist in the attribute group specified in the monitor attribute. Operator Can be: EQ, NE, GE, GT, LE, LT, or LIKE. You can select one of them from the list, where: EQ is equals NE is not equal GE is greater than or equal to LE is less than or equal to LT is less than LIKE can be used if pattern matching is required. Aailable pattern characters when using LIKE are: '%' matches any single character. ' * ' matches one to many characters. LIKE is only supported for character attributes. Attribute Value Is the alue on which the operator is applied. The filter alue is specified as follows attribute_name;operator;alue. You can specify multiple filter criteria. Multiple filters are applied using a logical AND operation. Note: Filter criteria are optional. Howeer, you must make sure that the query result of the monitor attribute does not return more than one row. If the monitor query returns an empty result set, the resource assumes Offline as obsered state. This filter criteria is required if process monitoring ia an OS agent is used, because the process table does not list the monitored process if the process is not running. Specifying additional properties for a Tioli Monitoring resource: You can add multiple Tioli Monitoring attributes with their current alues to the list of additional properties of the corresponding Tioli Monitoring resource. The attributes and alues are then shown in the Additional tab of the Properties dialog of the selected Tioli Monitoring resource in the System Automation operations console. Use the Property XML element that can be specified within the IBM.ITMResourceAttributes element to define the additional attributes which should be added to a resource. Additional Attributes specified as Property element. The attributes that you add as Property element must be part of the attribute group that is specified in the MonitorAttribute element. The attribute alue is Chapter 4. Integrating 243

262 queried periodically with eery monitor call. Do not specify attributes with frequently changing alues, for example CPU utilization, because a resource modified eent is triggered each time the attribute alue changes. You can specify multiple Property elements if more than one agent attribute alue should be added to the additional properties of a resource. The following screen capture shows parts of an attribute group as displayed in the Tioli Enterprise Portal: Figure 30. Agent attributes which can be added as additional attributes If in this attribute group there is also the attribute chosen as monitor attribute, you can use the other attributes as additional properties for the resource. In this example, Status was chosen as monitor attribute. Good examples for attributes to be added as additional attributes are Version or Process ID. Since JVM Memory Free (bytes) is an attribute that changes frequently, it is not a good candidate to be added to the list of additional properties. Example: <IBM.ITMResourceAttributes>... <MonitorAttribute>Application_Serer.Status</MonitorAttribute> <MonitorValueOnline>Connected</MonitorValueOnline> <MonitorValueOffline>Disconnected</MonitorValueOffline> <MonitorCommandPeriod>10</MonitorCommandPeriod> <Property>Version</Property> <Property>Process_ID</Property> </IBM.ITMResourceAttributes> Retrieing the required information about your Tioli Monitoring managed resources Specify attributes in the XML elements IBM.ITMResourceAttributes and Resource to create a Tioli Monitoring resource in an Agentless Adapter policy. This section describes the steps that you must perform to find the required information. Use the Tioli Enterprise Portal (TEP) connected to an Tioli Monitoring enironment to perform the following steps: Procedure 1. Step 1: Find the correct Managed System Name that must be specified as node attribute of the Resource XML element. 2. Step 2: Find suitable take action commands proided by the Tioli Monitoring agent to start and stop the Tioli Monitoring managed application and specify them as StartCommand and StopCommand within the IBM.ITMResourceAttributes XML element. 3. Step 3: Find the aailable attribute and corresponding attribute alues that can be used for determining the obsered state. Specify the attribute as MonitorAttribute XML element for the Tioli Monitoring resource and define 244 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

263 state mappings for the attribute alues using the corresponding MonitorValue XML elements. For example MonitorValueOnline or MonitorValueOffline. The following tasks guide you through the process. Step 1: Managed system name: The managed system name identifies an Tioli Monitoring agent on a specific remote endpoint that is used to monitor and control the application that you add to the Agentless Adapter policy. This managed system name must be specified in the ITM Resource section for an Tioli Monitoring resource. Perform the following steps to determine the managed system name: Procedure 1. Use the Tioli Enterprise Portal Naigator to naigate to the managed system for which you want to determine the managed system name. Right-click on the naigator item and select Properties 2. The managed system name in the Assigned list must be specified as node attribute of the Resource XML element as shown in the following example: <Resource name=... class= IBM.ITMResource node= serer1:saxb32e:kyns Step 2: Take action commands: In the StartCommand and StopCommand properties you can either specify any remote command aailable on the remote endpoint or a predefined "Take Action" command which is proided by the Tioli Monitoring agent. Use the following methods to display the aailable "Take Action" commands for an ITM agent. This information must be specified on the Start / Stop Properties notebook page for the Tioli Monitoring resource. Perform the following steps to determine the "Take Action" commands: Procedure 1. Use the Tioli Enterprise Portal Naigator to naigate to the managed system for which you want to determine the aailable take action commands. 2. Right-click on the naigator item and select Take Action > Select. 3. A list box containing all aailable Take Action commands for the currently selected managed system is displayed. Select the appropriate command to start or stop the monitored application. If you are prompted to specify required parameter alues, specify the correct alues in that dialog. 4. The Take Action dialog now displays the completed Take Action details. Specify the alue in the Command box in the StartCommand or StopCommand properties of the Tioli Monitoring resource. The start and stop commands must be specified in the StartCommand and StopCommand XML elements within the IBM.ITMResourceAttributes XML element as shown in the following example: <StartCommand>YN:StartAppSr wasadmin waspassword </StartCommand> Chapter 4. Integrating 245

264 Step 3: Monitor attribute and alid attribute alues: In this step, retriee aailable attributes and attribute alues that you need to specify in the MonitorAttribute element and the corresponding state mapping elements. A typical Tioli Enterprise Portal workspace contains multiple iews where each iew displays data from an agent attribute group. If you want to use an attribute that is displayed in a workspace iew as MonitorAttribute for System Automation, you first need to determine the corresponding attribute group name. Procedure 1. Use the Tioli Enterprise Portal Naigator to naigate to the managed system for which you want to determine the name of an attribute group corresponding to a workspace iew. Open the workspace that contains the workspace iew. 2. Select the workspace iew that displays the status information that you want to use to define the aailability state of the Tioli Monitoring resource. right-click in this workspace iew and select Properties. 3. In the "Properties" dialog, find the required Attribute Group by selecting Click here to assign a query. 4. In the Query Editor" dialog, find the matching Attribute Group in the tree on the left: 5. In this example, the matching Attribute Group is Application_Serer. Ifthe displayed name contains any spaces, replace them with the underscore character. Important: Application_Serer is the displayed name of the attribute group name. Replacing spaces with underscore characters is an attempt to create the internal name of the attribute group as it is known to the Tioli Monitoring agent. This internal name is also the name that must be specified in the policy. Neertheless, in some cases the internal name is still different (for example, the DB2 agent uses different internal names). To ensure the right names for attribute group and attribute name, erify that the name exists in the agent's.atr file. For more information, see Determine attributes and attribute alues from Tioli Monitoring agent attribute files on page 248. The User's Guides of the corresponding Tioli Monitoring agents, contain a detailed reference of all agent attributes. Refer to these documents to find a description of the attributes and their alues. 6. Click Cancel close the Query Editor" dialog and return to the Properties dialog. 7. Select the Filters tab and find the attribute which you want to use for mapping as SA obsered state. In the example below the attribute name is Status. As described for the attribute group in the preious steps, you may hae to specify an internal attribute name which is different from the displayed name. When you click into an empty cell of this attribute row, a list which shows you all defined attribute alues for this attribute is displayed. For each listed attribute alue, decide to which SA obsered state alue it is mapped. This mapping is defined using the MonitorValueOnline, MonitorValueOffline, and other elements. 246 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

265 You now determined all required alues for monitoring the aailability state of the resource: The attribute group name (in this example: Application_Serer), The attribute name (in this example: Status) The attribute alue mappings. 8. In the IBM.ITMResourceAttributes XML element, specify the attribute group name and the attribute name in the MonitorAttribute XML element as shown in the following example:<monitorattribute>application_serer.status</ MonitorAttribute> 9. Define state mappings for the attribute alues as shown in the following example: <MonitorValueOnline>Connected</MonitorValueOnline> <MonitorValueOffline>Disconnected</MonitorValueOffline> Alternatie ways to retriee information for Tioli Monitoring Resource policy alues This section describes how you can use the Tioli Enterprise Portal (TEP) or command line commands as an alternate source to retriee managed system names, "Take Action" commands, and resource attributes. These alues are required to create an Agentless Adapter policy to monitor and control Tioli Monitoring resources. Also refer to the preious topics for a description of the preferred way to gather this information. Displaying a list of all Managed Systems: To open the Managed System Status workspace, perform these steps: Procedure 1. Click the Enterprise Naigator item to open its default workspace. 2. Either right-click the Enterprise Naigator or open the View menu, then select Workspace > Managed System Status The Managed System Status table iew with a list of the monitoring agents in your managed network is displayed. Look for the agent which is used to monitor the application that you want to integrate in an Agentless Adapter policy. The Name column shows the managed system name that must be specified in the node attribute of the resource element. Using the Command Line To display a list of all aailable managed systems, run the following command on the hub Tioli Enterprise Monitoring Serer: tacmd listsystems Take Action commands: Procedure 1. Enter the following command to list all aailable Take Action commands for a specific agent product code: tacmd listaction t <pc> Chapter 4. Integrating 247

266 To list, for example, all actions for the Web Serer Agent which has the product code HT, use the command: tacmd listaction t HT The output contains a NAME column which lists the names of the aailable Take Action commands. 2. Enter the following command to display the details for a selected Take Action command: tacmd iewaction -n <action_name> -t <pc> To iew, for example, the details for the Start DB2 command: tacmd iewaction -n "Start DB2" -t UD The output contains the Command alue that must be specified in the StartCommand and StopCommand properties for an Tioli Monitoring resource. Determine attributes and attribute alues from Tioli Monitoring agent attribute files: The aailable attribute groups, attributes, and alues for an Tioli Monitoring agent can be determined from the *.atr file of the respectie agent. Attribute files are aailable for eery agent type and are on the hub Tioli Enterprise Monitoring Serer in the <ITM_Root>/tables/<TEMS_Name>/ATTRLIB directory. The file name for an attribute file is:k<pc>,atr, where pc is the two letter product code of an Tioli Monitoring agent. For example, klz.atr is the attribute file for the Linux OS agent. Here is an example of an entry in such an attribute file: entr ATTR name Apache_Web_Serer.Status affi G0000## colu STATUS type 4 mini maxi msid KHT0714 opgr 2048 atid ale Stopped ali 0 ale Running ali 1 ale Error ali 2 ale N/A ali -1 The highlighted lines are in particular of interest if you want to integrate a resource that is monitored by the respectie Tioli Monitoring agent into an Agentless Adapter policy. name ale Specifies the attribute group ( Apache_Web_Serer ) and attribute name ( Status ) separated by a dot. You must specify this alue for the MonitorAttribute XML policy element. These entries specify the alue set for the Apache_Web_Serer.Status attribute. You can use them to define state mappings for Tioli Monitoring resources in the Agentless Adapter policy. For example, you could define 248 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

267 for a resource that is monitored by this agent type that the alue Running is mapped to an SA Obsered State Online. Actiate and test the Agentless Adapter policy Actiating the Agentless Adapter policy: After you created the Agentless Adapter domain policy as described in the preious sections and stored it in the Agentless Adapter policy pool, you can now actiate it from the Operations Console. Open the Actiate Automation Policies dashboard and select the Tioli Monitoring domain. The aailable policies for the selected domain are listed. Select the new policy and click Actiate. After the policy is actiated, the Agentless Adapter connects to the configured Tioli Enterprise Monitoring Serer and attempts to retriee the agent attributes which were specified as monitor attribute in the policy for all defined Tioli Monitoring resources. After a few seconds, the resources displayed in the Operations Console change their obsered state from Unknown into either Online or Offline. If the status does not change, you must check the log of this specific Tioli Monitoring domain. You can iew the log by selecting the Tioli Monitoring domain and clicking View log in the context menu of the domain. This problem could occur if you did not specify the correct user credentials for accessing the Tioli Enterprise Monitoring Serer. In this case, you must now specify the credentials as described in Configuring user credentials to access the monitored resources on page 237 and restart the Agentless Adapter. Note: The last actie policy of the Tioli Monitoring domain is automatically reactiated only if you also configured alid First-leel automation credentials for your Tioli Monitoring domain using the cfgeezdmn configuration utility. Displaying Tioli Monitoring resources in the Operations Console: After policy actiation, you can open the domain page from the context menu of the Tioli Monitoring domain in order to iew the defined Tioli Monitoring resources and corresponding nodes. In the Properties dialog of a Tioli Monitoring resource you see the new resource class IBM.ITMResource together with the information about on which endpoint this resource is located. This information is also displayed in the Relationships graph. On the Additional tab of the resource's Properties dialog, you find the Tioli Monitoring specific start/stop actions and also which attribute is being used to determine the aailability state and the current alue of this attribute. Chapter 4. Integrating 249

268 Start/Stop a Tioli Monitoring Resource using the Operations Console: An Tioli Monitoring resource offers the same start/stop behaior as standard remote resources of class IBM.RemoteResource which are also managed by the Agentless Adapter. Depending on the current obsered state, an operator can either issue a Bring Online / Bring Offline or Restart command. The resource itself is in Starting state while the start action is running. The maximum time that the resource is allowed to be in the "Starting" state is defined for each start/stop action in the policy. After this action is performed, the obsered state is set according to the aailability state attribute of the Tioli Monitoring resource. Since the Agentless Adapter offers no automation capabilities, there is no desired state and therefore also no indication that the current state does not reflect the desired state. Managing Tioli Monitoring resources as part of a composite business application Create an end-to-end automation policy for Tioli Monitoring resources: This section describes how to add Tioli Monitoring resources as referenced resources of the end-to-end automation domain to achiee the following: Define an automated startup or shutdown sequence of different Tioli Monitoring monitored resources, hosted on different Tioli Monitoring endpoints. An integrated startup or shutdown sequence can be defined for Tioli Monitoring monitored resources and other automated resources that are controlled by another automation domain such as SA for Multiplatforms, SA z/os, or HACMP. Tioli Monitoring resources in an Agentless Adapter domain hae no desired aailability state. By integrating them into the end-to-end automation domain it is possible to automatically react when undesired outages of these Tioli Monitoring Resources occur. The grouping concepts in the end-to-end automation policy allow you to create composite application groups of Tioli Monitoring resources. These composite application groups can be managed as one entity in the SA Operations Console and proide an aggregated aailability state. Create ResourceReferences referring to the Tioli Monitoring resources as you would for any other first leel resources. You can collect the required attributes, like resource name and resource class from the resource's Properties dialog. What to do next After haing created the desired resource references to Tioli Monitoring resources, your policy already seres one purpose: When it is actiated on the end-to-end domain, the System Automation Application Manager ensures the defined desired state and restarts eery Tioli Monitoring resource if it is failing. Next, you can define a group in the end-to-end automation policy and add the resource references as group members. Gie your new group a meaningful name, for example PortalGroup. With this configuration you can manage multiple Tioli Monitoring resources as one composite group. 250 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

269 You can also create relationships between the resource references thereby controlling the startup behaior of the Tioli Monitoring resources. After you finished creating this first end-to-end policy, you must sae it into the policy pool directory of the System Automation Application Manager. Actiate the end-to-end automation policy: Open the Actiate Automation Policies dashboard and select the end-to-end automation domain. The aailable policies for the end-to-end automation domain are listed. Select the new policy and click Actiate. Control a composite business application consisting of multiple Tioli Monitoring and other clustered resources: This section describes how a Tioli Monitoring resources defined in an actie Agentless Adapter domain can be automated and controlled in the context of an end-to-end composite business application. After the end-to-end policy is actiated, as described in the preious section, the composite application group PortalGroup is shown in the Resources widget on the domain page of the end-to-end automation domain. As displayed in the Relationships graph of a selected resource reference, the end-to-end automation domain now controls starting and stopping the indiidual referenced resource that is defined in the ITM domain. A composite business application, such as the PortalGroup, can be started by an operator start request that results in start commands being sent to all referenced Tioli Monitoring resources. If you specified startafter relationships between the resource references, they are honored as well. In addition, the SA Application Manager enforces the defined desired state and restarts eery Tioli Monitoring resource in case it is failing. You can also use forceddownby relationships in order to automatically restart related components if a Tioli Monitoring resource fails. Creating a Tioli Monitoring situation to trigger an automated restart So far you learned how to instrument Tioli Monitoring resources to be managed by the Agentless Adapter of SA Application Manager. You also know how you can create composite business applications by using the Tioli Monitoring resources. The SA Application Manager takes oer the responsibility to start these composite applications in a coordinated sequence on request by an operator. SA Application Chapter 4. Integrating 251

270 Manager can also restart the Tioli Monitoring resources in unexpected outage situations. These integration scenarios are defined by using the instrumentation functions proided by Tioli Monitoring. In this section, you find an example of how to trigger an automated SA action based on a defined Tioli Monitoring situation. This scenario can be used, for example, to restart a WebSphere Application Serer when a specific Tioli Monitoring situation, such as aerage heap size too high, becomes true. All operator actions against SA Application Manager resources from the Operations Console can also be triggered by using the SA Application Manager command shell (eezcs command). You can issue such a command as System Command from the Tioli Enterprise Monitoring Serer as an Action that is defined for a situation. If the Tioli Enterprise Monitoring Serer and SA Application Manager are installed on different serers, you must run this command remotely on the SA Application Manager serer using the ssh command. The following figure shows an example of how to define such a command. Figure 31. Perform an SA Application Manager command shell command as action for an Tioli Monitoring situation Any SA resource (not only Tioli Monitoring resources) can be the target of such a start/stop/restart request action. You can start resources which are, for example, automated by an SA for Multiplatforms, SA for z/os or HACMP domain. zenterprise Hardware Management Console This topic describes how to set up the zenterprise Hardware Management console (HMC) to use with System Automation Application Manager. 252 Tioli System Automation Application Manager V4.1: Installation and Configuration Guide

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

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

More information

IBM Operational Decision Manager Version 8 Release 5. Installation Guide

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

More information

Tivoli 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

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

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

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

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

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

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

More information

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

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

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

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

IBM Agent Builder Version User's Guide IBM SC

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

More information

IBM. IBM Service Management Unite V Installation and Configuration Guide

IBM. IBM Service Management Unite V Installation and Configuration Guide IBM IBM Service Management Unite V1.1.1 - Installation and Configuration Guide ii IBM Service Management Unite V1.1.1 - Installation and Configuration Guide Contents Chapter 1. Overview and planning...

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

Managing Server Installation and Customization Guide

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

More information

IBM 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 Unix GC32-1615-00 Tioli Tioli Proisioning Manager Version 2.1 Installation Guide for Unix GC32-1615-00 Note: Before using this information

More information

Tivoli 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

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

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

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

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

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

License Administrator s Guide

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

More information

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

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

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

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

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

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

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

More information

IBM 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

IBM Security Identity Manager Version 6.0. Installation Guide GC

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

More information

IBM Director Virtual Machine Manager 1.0 Installation and User s Guide

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

More information

IBM. IBM Service Management Unite V Installation and Configuration Guide

IBM. IBM Service Management Unite V Installation and Configuration Guide IBM IBM Service Management Unite V1.1.2 - Installation and Configuration Guide ii IBM Service Management Unite V1.1.2 - Installation and Configuration Guide Contents Chapter 1. Overview and planning...

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

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

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

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

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

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

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

Installation and Configuration Guide

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

More information

IBM 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

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

Reference and Problem Determination Guide

Reference and Problem Determination Guide System Automation Application Manager Version 4.1 Reference and Problem Determination Guide SC34-2703-00 System Automation Application Manager Version 4.1 Reference and Problem Determination Guide SC34-2703-00

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

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

Live Partition Mobility ESCALA REFERENCE 86 A1 85FA 01

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

More information

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

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

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

More information

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

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

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

Tivoli IBM Tivoli Advanced Catalog Management for z/os

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

More information

IBM 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

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

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

More information

IBM Tivoli Asset Discovery for Distributed Version 7.2. Installation Guide GI

IBM Tivoli Asset Discovery for Distributed Version 7.2. Installation Guide GI Tivoli IBM Tivoli Asset Discovery for Distributed Version 7.2 Installation Guide GI11-8749-00 Tivoli IBM Tivoli Asset Discovery for Distributed Version 7.2 Installation Guide GI11-8749-00 Installation

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

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

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

Upward Integration Modules Installation Guide

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

More information

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

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

IBM Tivoli Federated Identity Manager Version Installation Guide GC

IBM Tivoli Federated Identity Manager Version Installation Guide GC IBM Tivoli Federated Identity Manager Version 6.2.2 Installation Guide GC27-2718-01 IBM Tivoli Federated Identity Manager Version 6.2.2 Installation Guide GC27-2718-01 Note Before using this information

More information

WebSphere MQ. Clients GC

WebSphere MQ. Clients GC WebSphere MQ Clients GC34-6058-01 Note! Before using this information and the product it supports, be sure to read the general information under Notices on page 179. Second edition (October 2002) This

More information

Managed System Infrastructure for Setup User s Guide

Managed System Infrastructure for Setup User s Guide z/os Managed System Infrastructure for Setup User s Guide Version1Release4 SC33-7985-03 z/os Managed System Infrastructure for Setup User s Guide Version1Release4 SC33-7985-03 Note! Before using this

More information

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

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

More information

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 Business Systems Manager

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

More information

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

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

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

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

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

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

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

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

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

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

Troubleshooting Guide

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

More information

IBM 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 i Version 7.2. Security Service Tools IBM

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

More information

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

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

More information

IBM Geographically Dispersed Resiliency for Power Systems. Version Deployment Guide IBM

IBM Geographically Dispersed Resiliency for Power Systems. Version Deployment Guide IBM IBM Geographically Dispersed Resiliency for Power Systems Version 1.2.0.0 Deployment Guide IBM IBM Geographically Dispersed Resiliency for Power Systems Version 1.2.0.0 Deployment Guide IBM Note Before

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 Systems Director for Windows Planning, Installation, and Configuration Guide

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

More information

Administrator's and User's Guide

Administrator's and User's Guide Tioli System Automation for Multiplatforms Version 3.2.2 Administrator's and User's Guide SC34-2583-03 Tioli System Automation for Multiplatforms Version 3.2.2 Administrator's and User's Guide SC34-2583-03

More information

WebSphere Message Broker. Installation GC

WebSphere Message Broker. Installation GC WebSphere Message Broker Installation Guide Version 6.0 GC34-6621-00 WebSphere Message Broker Installation Guide Version 6.0 GC34-6621-00 Note! Before using this information and the product it supports,

More information

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

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

More information

Tivoli Security Compliance Manager

Tivoli Security Compliance Manager Tioli Security Compliance Manager Version 5.1 Collector Deelopment Guide SC32-1595-00 Tioli Security Compliance Manager Version 5.1 Collector Deelopment Guide SC32-1595-00 Note Before using this information

More information