t l systemautomationapplication...

Tivoli® System Automation Application Manager

Installation and Configuration Guide

Version 3.1

SC33-8420-01

��

Note!Before using this information and the product it supports, read the information in “Notices” on page 217.

This edition of the IBM Tivoli System Automation Application Manager Installation and Configuration Guide applies toVersion 3, Release 1, Modification 0 of IBM Tivoli System Automation Application Manager, program number5724-S92, and to all subsequent releases and modifications of this product until otherwise indicated in new editions.IBM Tivoli System Automation Application Manager is the successor to the End-to-End Automation Managementcomponent of IBM Tivoli System Automation for Multiplatforms V2.3.

This edition replaces SC33-8420-00.

IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, oryou may address your comments to the following address:

IBM Deutschland Research and Development GmbHDepartment 3248Schoenaicher Str. 22071032 BoeblingenGermany

FAX (Germany): 07031 16-3456FAX (Other Countries): (+49) 7031 16-3456

Internet e-mail: [email protected]

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:v Title and order number of this bookv Page number or topic related to your comment

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 2006, 2009.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

|

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . ixWho should read this guide . . . . . . . . . ixHow to use this guide . . . . . . . . . . . ixWhere to find more information . . . . . . . ixConventions used in this guide . . . . . . . . xRelated information . . . . . . . . . . . . x

Summary of changes . . . . . . . . xiiiWhat's new for System Automation ApplicationManager 3.1 . . . . . . . . . . . . . . xiii

Part 1. System AutomationApplication Manager . . . . . . . . 1

Chapter 1. Overview of SystemAutomation Product Family . . . . . . 3

Chapter 2. Installing System AutomationApplication Manager . . . . . . . . . 5Product components . . . . . . . . . . . . 5Installing System Automation Application Manageron AIX, Linux or Windows . . . . . . . . . 5Installing System Automation Application Manageron z/OS . . . . . . . . . . . . . . . 38Verifying the installation . . . . . . . . . . 63Post-installation tasks . . . . . . . . . . . 66

Chapter 3. Upgrading from IBM TivoliSystem Automation release 2.x . . . . 71Upgrading the MSCS adapter . . . . . . . . 72

Chapter 4. Configuring the end-to-endautomation manager . . . . . . . . . 73Invoking the end-to-end automation managerconfiguration dialog . . . . . . . . . . . 73End-to-end automation manager basic configuration 75Configuring the end-to-end hardware adapter . . . 84Configuring high availability for the end-to-endautomation manager . . . . . . . . . . . 89Replicating the configuration files . . . . . . . 96Setting up the domain . . . . . . . . . . . 96Removing the domain . . . . . . . . . . . 97Validating and storing the automation policy for theend-to-end automation manager . . . . . . . 97Defining the automation policy for the end-to-endautomation manager . . . . . . . . . . . 98Removing the automation policy for the end-to-endautomation manager . . . . . . . . . . . 100

Chapter 5. Silent configuration . . . . 101Overview. . . . . . . . . . . . . . . 101Invoking silent configuration . . . . . . . . 103Silent mode input properties file . . . . . . . 104Output in silent mode . . . . . . . . . . 106

Chapter 6. Installing and uninstallingservice . . . . . . . . . . . . . . 109Installing service . . . . . . . . . . . . 109Installing service in a setup for high availability 113Uninstalling service . . . . . . . . . . . 113Updating the installation on z/OS . . . . . . 114

Chapter 7. Uninstalling SystemAutomation Application Manager . . . 115Launching the graphical uninstallation program onWindows . . . . . . . . . . . . . . . 115Launching the graphical uninstallation program onAIX and Linux . . . . . . . . . . . . . 115Using the uninstallation program . . . . . . . 115Uninstalling System Automation ApplicationManager from z/OS . . . . . . . . . . . 118

Chapter 8. Installing and configuringthe Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . 119Installing the Distributed Disaster Recovery feature 119Configuring the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 121Activating the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 124Uninstalling the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 125

Part 2. Enabling launch-in-contextsupport . . . . . . . . . . . . . 127

Chapter 9. Installing and configuringthe IBM TEC extension for the SystemAutomation Application Manager . . . 129Overview. . . . . . . . . . . . . . . 129Prerequisites. . . . . . . . . . . . . . 129Installing the IBM TEC extension . . . . . . . 130Configuring the TEC extension for SystemAutomation Application Manager . . . . . . 130

Chapter 10. Setting up TivoliEnterprise Portal launch-in-contextsupport . . . . . . . . . . . . . . 133

© Copyright IBM Corp. 2006, 2009 iii

||

Part 3. Installing and configuringthe end-to-end automationadapters . . . . . . . . . . . . . 135

Chapter 11. Overview . . . . . . . . 137

Chapter 12. Installing and configuringthe HACMP adapter. . . . . . . . . 139Installing the HACMP adapter . . . . . . . 139Automating the HACMP adapter. . . . . . . 140Configuring the HACMP adapter . . . . . . 140Verifying the HACMP adapter configuration . . . 152Controlling the HACMP adapter . . . . . . . 153

Chapter 13. Installing and configuringthe MSCS adapter . . . . . . . . . 155Installation and configuration roadmaps . . . . 155Planning and preparing for the MSCS adapter . . 156Installing the MSCS adapter . . . . . . . . 158Upgrading the MSCS adapter . . . . . . . . 160Configuring the MSCS adapter . . . . . . . 160Windows Firewall on Windows Server 2008 . . . 169Providing high availability for the MSCS adapter 170Verifying the installation and configuration . . . 176Uninstalling the MSCS adapter . . . . . . . 176

Chapter 14. Installing and configuringthe VERITAS Cluster Server adapter . 177Installing the VCS adapter . . . . . . . . . 177Automating the VCS adapter . . . . . . . . 178Configuring the VCS adapter . . . . . . . . 178Verifying the VCS adapter configuration . . . . 191Controlling the VCS adapter . . . . . . . . 192

Part 4. Appendixes . . . . . . . . 193

Appendix A. Default directories . . . 195

Appendix B. Preserving user dataduring the upgrade from IBM TivoliSystem Automation for Multiplatforms2.x to System Automation ApplicationManager 3.1 . . . . . . . . . . . . 197

Appendix C. Troubleshooting theinstallation of System AutomationApplication Manager . . . . . . . . 199

Installation wizard cannot find WebSphereApplication Server on the system. . . . . . . 199Determining the correct DB2 port number . . . . 199DB2 access test hangs . . . . . . . . . . 200DB2 message SQL1035N The database is currentlyin use. SQLSTATE=57019 . . . . . . . . . 200Installer cannot detect non-default SOAP port . . 200Exceptions appear in file eezinstall.log . . . . . 200Cleaning up from a failed installation . . . . . 201Procedures for troubleshooting an installation . . 201Using the log file collector utility . . . . . . . 202Gathering information for IBM Support . . . . 202

Appendix D. Troubleshooting theinstallation of the HACMP adapter . . 203HACMP adapter does not start . . . . . . . 203HACMP adapter terminates . . . . . . . . 203Adapter does not connect to the host . . . . . 203HACMP adapter log files . . . . . . . . . 204

Appendix E. Troubleshooting theinstallation of the MSCS adapter . . . 205MSCS adapter log files . . . . . . . . . . 205MSCS adapter installation fails . . . . . . . 205MSCS Adapter configuration dialog problemsoccur . . . . . . . . . . . . . . . . 205MSCS adapter start problems . . . . . . . . 206MSCS adapter terminates . . . . . . . . . 206Domain does not join. . . . . . . . . . . 207MSCS adapter uninstallation fails . . . . . . 208Uninstalling the MSCS adapter manually . . . . 208

Appendix F. Changing the companylogos on the top of a report . . . . . 211

Appendix G. Considerations aboutuser and group management inWebSphere Application Server . . . . 213

Appendix H. Using IBM SupportAssistant . . . . . . . . . . . . . 215Installing IBM Support Assistant and the SystemAutomation Application Manager plug-in . . . . 215

Notices . . . . . . . . . . . . . . 217Trademarks . . . . . . . . . . . . . . 218

Index . . . . . . . . . . . . . . . 219

iv System Automation Application Manager: Installation and Configuration Guide

||||

Figures

1. Overview of System Automation product family . . . . . . . . . . . . . . . . . . . . . 32. Components of System Automation Application Manager . . . . . . . . . . . . . . . . . . 53. WebSphere scenario - base . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394. WebSphere scenario - HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405. Configuration of the HACMP adapter . . . . . . . . . . . . . . . . . . . . . . . . 1416. Configuration of the VCS adapter. . . . . . . . . . . . . . . . . . . . . . . . . . 179

© Copyright IBM Corp. 2006, 2009 v

vi System Automation Application Manager: Installation and Configuration Guide

Tables

1. Product CD versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62. WebSphere Application Server upgrade CDs . . . . . . . . . . . . . . . . . . . . . . . 63. Archives for Windows platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. Archives for AIX platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75. Archives for Linux on System x . . . . . . . . . . . . . . . . . . . . . . . . . . . 76. Archives for Linux on POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . 77. Archives for Linux on System z . . . . . . . . . . . . . . . . . . . . . . . . . . . 88. Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89. Disk space requirements on Windows systems . . . . . . . . . . . . . . . . . . . . . . 10

10. Disk space requirements on AIX and Linux systems . . . . . . . . . . . . . . . . . . . . 1111. Database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512. Contents of the WebSphere Application Server 6.1.0 upgrade CD or electronic deliverable . . . . . . . 1713. Installation directory and Tivoli Common Directory . . . . . . . . . . . . . . . . . . . . 1814. DB2 data for local and remote DB2 setup . . . . . . . . . . . . . . . . . . . . . . . 2015. WebSphere Application Server installation parameters . . . . . . . . . . . . . . . . . . . 2116. Installation parameters for IBM Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . 2217. End-to-end automation domain name . . . . . . . . . . . . . . . . . . . . . . . . . 2218. WebSphere Application Server user ID . . . . . . . . . . . . . . . . . . . . . . . . 2219. System Automation Administrator user ID . . . . . . . . . . . . . . . . . . . . . . . 2320. Directories on the product CD . . . . . . . . . . . . . . . . . . . . . . . . . . . 2321. Additional disk space requirements on z/OS systems . . . . . . . . . . . . . . . . . . . 4122. Installation directory and Tivoli Common Directory . . . . . . . . . . . . . . . . . . . . 4323. General installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 4424. DB2 data for local and remote DB2 setup . . . . . . . . . . . . . . . . . . . . . . . 4425. WebSphere Application Server (WAS) installation parameters . . . . . . . . . . . . . . . . . 4926. Installation parameters for RACF user and groups . . . . . . . . . . . . . . . . . . . . 5027. Installation parameters for IBM Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . 5228. Installation parameters for IBM Tivoli Common Reporting . . . . . . . . . . . . . . . . . . 5329. Installation parameters for GDPS interaction . . . . . . . . . . . . . . . . . . . . . . 5330. End-to-end automation domain name . . . . . . . . . . . . . . . . . . . . . . . . . 5431. WebSphere Application Server user ID . . . . . . . . . . . . . . . . . . . . . . . . 5432. System Automation administrator user ID . . . . . . . . . . . . . . . . . . . . . . . 5533. Job control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5634. Inbound TCP ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6835. Resources in the automation policy for the end-to-end automation manager. . . . . . . . . . . . . 9936. Generated input properties files . . . . . . . . . . . . . . . . . . . . . . . . . . 10537. Archives for Windows platforms . . . . . . . . . . . . . . . . . . . . . . . . . . 11138. Archives for AIX platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11139. Archives for Linux on System x . . . . . . . . . . . . . . . . . . . . . . . . . . 11140. Archives for Linux on POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . 11141. Archives for Linux on System z . . . . . . . . . . . . . . . . . . . . . . . . . . 11242. Supported platforms for server clusters to be managed by SA AM Distributed Disaster Recovery . . . . 11943. Context used to find a Tivoli Enterprise Portal workspace . . . . . . . . . . . . . . . . . 13344. Resources in the HACMP adapter automation policy . . . . . . . . . . . . . . . . . . . 15145. HACMP adapter command options . . . . . . . . . . . . . . . . . . . . . . . . . 15346. Microsoft Failover Cluster default ports . . . . . . . . . . . . . . . . . . . . . . . . 17047. Resources in the VCS adapter automation policy. . . . . . . . . . . . . . . . . . . . . 19148. VCS adapter control command options . . . . . . . . . . . . . . . . . . . . . . . . 19249. Default directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

© Copyright IBM Corp. 2006, 2009 vii

viii System Automation Application Manager: Installation and Configuration Guide

About this guide

This guide provides information needed to plan, install, configure, and upgradeIBM Tivoli System Automation Application Manager (hereafter System AutomationApplication Manager).

Who should read this guideThis guide is for planners, installers, and administrators who plan to install andconfigure System Automation Application Manager.

How to use this guideThis guide is divided into the following parts:v Part 1, “System Automation Application Manager,” on page 1 describes how to

install, uninstall, service, and configure System Automation ApplicationManager.

v Part 2, “Enabling launch-in-context support,” on page 127 describes how youinstall and configure the IBM TEC extension for System Automation ApplicationManager. which enables users to navigate from an event displayed in the EventConsole of Tivoli Enterprise Console to the corresponding resource or domain inthe System Automation operations console, and describes how to set uplaunch-in-context support for Tivoli Enterprise Portal (TEP), which enables usersto launch TEP workspaces from the System Automation operations console witha single mouse click.

v Part 3, “Installing and configuring the end-to-end automation adapters,” on page135 describes how to install and configure the HACMP™, MSCS, and VCSadapters.

v The Appendixes provide troubleshooting information.

Where to find more informationIn addition to this manual, the IBM Tivoli System Automation library contains thefollowing books related to the System Automation Application Manager:v IBM Tivoli System Automation Application Manager Release Notes, SC33–8422v IBM Tivoli System Automation Application Manager Administrator’s and User’s

Guide, SC33-8419v IBM Tivoli System Automation Application Manager Reference, SC33-8421

You can download the books at:http://publib.boulder.ibm.com/tividd/td/IBMTivoliSystemAutomationforApplicationManager3.1.html

More information about IBM Tivoli System Automation for Multiplatforms can befound in the following books:v IBM Tivoli System Automation for Multiplatforms Release Notes, SC33–8418v IBM Tivoli System Automation for Multiplatforms Installation and Configuration

Guide, SC33-8416v IBM Tivoli System Automation for Multiplatforms Administrator’s and User’s Guide,

SC33-8415v IBM Tivoli System Automation for Multiplatforms Reference, SC33-8417

© Copyright IBM Corp. 2006, 2009 ix

http://publib.boulder.ibm.com/tividd/td/IBMTivoliSystemAutomationforApplicationManager3.1.html

You can download the books at:http://publib.boulder.ibm.com/tividd/td/IBMTivoliSystemAutomationforMultiplatforms3.1.html

The IBM Tivoli System Automation home page contains useful up-to-dateinformation, including support links and downloads for maintenance packages.

The IBM Tivoli System Automation Application Manager home page is:

http://www.ibm.com/software/tivoli/products/sys-auto-app-mgr

The IBM Tivoli System Automation for Multiplatforms home page is:

http://www.ibm.com/software/tivoli/products/sys-auto-multi

Conventions used in this guideThis guide uses several conventions for special terms and actions and operatingsystem commands and paths.

Typeface conventionsThis guide uses the following conventions:v Typically, file names, directories, and commands appear in a different font. For

example:– File name: setup.jar– Directory: /etc/hosts– Command: eezdmn -reconfig

v Variables are either italicized, enclosed in brackets, or both. For example:– http://<hostname.yourco.com>/index.html

v Frequently, variables 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 Server root installation directory: <was_root> or

was_root– Runtime root directory of Integrated Solutions Console: <isc_runtime_root> or

isc_runtime_rootv Directories are shown with forward slashes (/), unless operating-system specific

information is provided. On Windows® systems, you should use backwardslashes (\) when typing at a command line, unless otherwise noted.

v Operating-system specific information is provided. For example:– AIX, Linux: /opt/IBM/tsamp/eez

– Windows: C:\Program Files\IBM\tsamp\eez

– z/OS: /local/eez

Related informationThis topic provides information about publications and Web sites related to IBMTivoli System Automation:

WebSphere Application Server publications:

The latest versions of all WebSphere Application Server publications can befound on the WebSphere Application Server library Web site at

x System Automation Application Manager: Installation and Configuration Guide

http://publib.boulder.ibm.com/tividd/td/IBMTivoliSystemAutomationforMultiplatforms3.1.html

http://www.ibm.com/software/tivoli/products/sys-auto-app-mgr


http://www.ibm.com/software/webservers/appserv/was/library/

IBM DB2 publications:DB2 publications can be found on the IBM DB2 UDB Web site at

http://www.ibm.com/software/data/db2/udb/support/

The link to the PDF manuals is available in the Other resources section onthe Web page.

IBM GDPS publications:GDPS publications can be found in the Resources section on the IBMGDPS Web site at:http://www.ibm.com/systems/z/advantages/gdps/

IBM Redbooks publications:The following publications are available at:http://www.redbooks.ibm.com/

v End-to-End Automation with IBM Tivoli System Automation forMultiplatforms (SG24-7117-00)

v GDPS Family – An Introduction to Concepts and Facilities

About this guide xi

http://www.ibm.com/software/webservers/appserv/was/library

http://www.ibm.com/software/data/db2/udb/support

http://www.ibm.com/systems/z/advantages/gdps/

http://www.redbooks.ibm.com/

xii System Automation Application Manager: Installation and Configuration Guide

Summary of changes

What's new for System Automation Application Manager 3.1The following enhancements and changes are provided in Version 3 Release 1:v System Automation Application Manager, formerly the End-to-End Management

component of Tivoli System Automation for Multiplatforms, is now anindependent product.

v System Automation Application Manager can now be installed on– AIX 6.1– Windows Server 2008– z/OS

v The minimum Red Hat RHEL version is now 4.5.v The HACMP, MSCS, and VCS adapters can no longer be configured to use the

IBM Tivoli System Automation operations console in direct access mode. Theymust now be configured to use System Automation Application Manager.

v There is a new Distributed Disaster Recovery feature of the System AutomationApplication Manager, which can be enabled with an additionally priced featurelicense.

v A graphical user interface to the Policy Editor has been added.v Reports can be produced using the Tivoli Common Reporting feature.v A silent configuration feature has been added to allow configuration without a

GUI.v You can now use the SA operations console to move resources from one node to

another.

© Copyright IBM Corp. 2006, 2009 xiii

||

xiv System Automation Application Manager: Installation and Configuration Guide

Part 1. System Automation Application Manager

Chapter 1. Overview of System AutomationProduct Family . . . . . . . . . . . . . 3

Chapter 2. Installing System AutomationApplication Manager . . . . . . . . . . . 5Product components . . . . . . . . . . . . 5Installing System Automation Application Manageron AIX, Linux or Windows . . . . . . . . . 5

Planning for installation . . . . . . . . . 5Installing the middleware software . . . . . 12Preparing for the installation of SystemAutomation Application Manager . . . . . . 18Installing System Automation ApplicationManager using the installation wizard . . . . 25Installing System Automation ApplicationManager in silent mode . . . . . . . . . 38

Installing System Automation Application Manageron z/OS . . . . . . . . . . . . . . . 38

Planning for installation . . . . . . . . . 38Preparing for the installation of SystemAutomation Application Manager . . . . . . 43Installing System Automation ApplicationManager on z/OS . . . . . . . . . . . 59

Verifying the installation . . . . . . . . . . 63Verify the automation manager . . . . . . . 63Verify the automation engine . . . . . . . 64Verify the operations console . . . . . . . 64

Post-installation tasks . . . . . . . . . . . 66Modify the Lightweight Third PartyAuthentication (LTPA) settings . . . . . . . 66Modify the HTTP session timeout . . . . . . 66Configure the number of users who can connectto the automation manager using the operationsconsole . . . . . . . . . . . . . . . 67Modify the Windows Firewall Security Rules . . 67

Chapter 3. Upgrading from IBM Tivoli SystemAutomation release 2.x . . . . . . . . . . 71Upgrading the MSCS adapter . . . . . . . . 72

Chapter 4. Configuring the end-to-endautomation manager . . . . . . . . . . . 73Invoking the end-to-end automation managerconfiguration dialog . . . . . . . . . . . 73

Using the task launcher . . . . . . . . . 73Displaying online help . . . . . . . . . 74

End-to-end automation manager basic configuration 75Domain tab . . . . . . . . . . . . . 76Command shell tab. . . . . . . . . . . 78Discovery library adapter tab . . . . . . . 78User credentials tab . . . . . . . . . . 79Security tab . . . . . . . . . . . . . 81Logger tab. . . . . . . . . . . . . . 81Saving the basic configuration . . . . . . . 84

Configuring the end-to-end hardware adapter . . . 84

Adapter tab . . . . . . . . . . . . . 85Credentials tab . . . . . . . . . . . . 85Saving the hardware adapter configuration . . . 89

Configuring high availability for the end-to-endautomation manager . . . . . . . . . . . 89

Domain setup tab . . . . . . . . . . . 89Automation manager tab . . . . . . . . . 91Policy pool tab . . . . . . . . . . . . 92WebSphere tab . . . . . . . . . . . . 92DB2 tab . . . . . . . . . . . . . . 94Hardware adapter tab . . . . . . . . . . 94Saving the high-availability configuration . . . 95Restoring an existing high-availabilityconfiguration . . . . . . . . . . . . . 95

Replicating the configuration files . . . . . . . 96Setting up the domain . . . . . . . . . . . 96Removing the domain . . . . . . . . . . . 97Validating and storing the automation policy for theend-to-end automation manager . . . . . . . 97Defining the automation policy for the end-to-endautomation manager . . . . . . . . . . . 98Removing the automation policy for the end-to-endautomation manager . . . . . . . . . . . 100

Chapter 5. Silent configuration . . . . . . . 101Overview. . . . . . . . . . . . . . . 101

Working in silent mode . . . . . . . . . 101Tasks to be performed manually . . . . . . 102

Invoking silent configuration . . . . . . . . 103Configuring MSCS on Windows Server 2008 104

Silent mode input properties file . . . . . . . 104Editing the input properties file . . . . . . 105

Output in silent mode . . . . . . . . . . 106

Chapter 6. Installing and uninstalling service 109Installing service . . . . . . . . . . . . 109

Where to obtain fix packs . . . . . . . . 109Archive naming conventions . . . . . . . 109Naming conventions of the update installerlocation . . . . . . . . . . . . . . 110Installation scenarios . . . . . . . . . . 110Usage instructions for the platform-specificarchives . . . . . . . . . . . . . . 110Steps for installing a product fix pack . . . . 112

Installing service in a setup for high availability 113Uninstalling service . . . . . . . . . . . 113Updating the installation on z/OS . . . . . . 114

Chapter 7. Uninstalling System AutomationApplication Manager . . . . . . . . . . 115Launching the graphical uninstallation program onWindows . . . . . . . . . . . . . . . 115Launching the graphical uninstallation program onAIX and Linux . . . . . . . . . . . . . 115Using the uninstallation program . . . . . . . 115

© Copyright IBM Corp. 2006, 2009 1

||

||

Uninstalling System Automation ApplicationManager from z/OS . . . . . . . . . . . 118

Chapter 8. Installing and configuring theDistributed Disaster Recovery feature . . . . 119Installing the Distributed Disaster Recovery feature 119

Installation prerequisites . . . . . . . . . 119Supported hardware and operating systems . . 119Packaging . . . . . . . . . . . . . 120Installing the feature license . . . . . . . 120

Configuring the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 121

Configuring the JMS destination for GDPSevents . . . . . . . . . . . . . . . 121Configuring the hardware adapter . . . . . 124

Activating the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 124Uninstalling the Distributed Disaster Recoveryfeature . . . . . . . . . . . . . . . 125

2 System Automation Application Manager: Installation and Configuration Guide

Chapter 1. Overview of System Automation Product Family

The IBM Tivoli System Automation Application Manager works together withother IBM Tivoli System Automation products as shown in Figure 1.

System Automation Application Manager manages the system as a whole throughconnections to these other products. The products are linked together byautomation adapters. The adapters for IBM Tivoli System Automation forMultiplatforms and IBM Tivoli System Automation for z/OS are packaged withthose products. All other automation adapters are packaged with SystemAutomation Application Manager.

Figure 1. Overview of System Automation product family


Chapter 2. Installing System Automation Application Manager

Product componentsThese components are common to System Automation Application Manager on allsupported platforms as shown in Figure 2.

The installation procedure on the z/OS platform is significantly different toinstallation on the other platforms and is therefore described separately in thesection “Installing System Automation Application Manager on z/OS” on page 59

For information about the components of System Automation Application Managerplease refer to the IBM Tivoli System Automation Application Manager Administrator’sand User’s Guide.

Installing System Automation Application Manager on AIX, Linux orWindows

Planning for installationThis section contains the information you need to prepare for the installation ofSystem Automation Application Manager on AIX, Linux or Windows systems.

PackagingSystem Automation Application Manager can be ordered from IBM as a mediapack or downloaded from an IBM software distribution download site.

Automation J2EE Framework

Automation Engine

Resource Adapter

First Level Automation

Manager Resource Adapter

Integrated

Solution

Console

Operations

Console

Operations

Console

Policy

Editor

Policy

Editor

TCR UI

DLA

Command

Shell

Browser

Client

GDPS

Agent(*)

Automation

Engine

Auto-

mation

Policy

Automation

Database

DB2

FS

Policy PoolSA Application Manager

SDKSDK

Node

Automation

Adapter

Automation

Adapter

First Level

Automation

Manager

Node

Node

First-Level

Automation Domain

Hardware

Adapter(*)

SA Operator

SA Administrator

(*) with Feature: Distributed Disaster Recovery

FS

Policy Pool

WebSphere Application Server

End-to-End Automation Manager

SA Application

Manager

Node

GDPS

TCR Application

Figure 2. Components of System Automation Application Manager


Product CD and WebSphere Application Server upgrade CD: When you orderSystem Automation Application Manager on CD you receive the following CDs:v One product CD for each operating system on which the product can be

installed. You use the product CD to install System Automation ApplicationManager.

v One WebSphere Application Server upgrade CD for each operating system onwhich the product can be installed. You use the upgrade CD to bring WebSphereApplication Server to the version level required for System AutomationApplication Manager.

For information about the middleware software CDs that are shipped with SystemAutomation Application Manager, refer to “Contents of the middleware softwareCDs” on page 12.

Product CD: The following table lists the versions of the product CDs that areavailable for System Automation Application Manager. To install the product, youuse the installation wizard file listed in the right column of the table.

Table 1. Product CD versions

Operatingsystem Product CD label Installation wizard file

Windows IBM Tivoli System Automation ApplicationManager V3.1.0 for Windows

EEZ3100Windows\Windows\setup.exe

AIX IBM Tivoli System Automation ApplicationManager V3.1.0 for AIX

EEZ3100AIX/AIX/setup.bin

Linux onSystem x

IBM Tivoli System Automation ApplicationManager V3.1.0 for Linux on System x

EEZ3100I386/i386/setup.bin

Linux onPOWER

IBM Tivoli System Automation ApplicationManager V3.1.0 for Linux on POWER

EEZ3100PPC/ppc/setup.bin

Linux onSystem z

IBM Tivoli System Automation ApplicationManager V3.1.0 for Linux on System z

EEZ3100S390/s390/setup.bin

WebSphere Application Server upgrade CDs: The following table lists the availableversions of the WebSphere Application Server upgrade CDs.

Table 2. WebSphere Application Server upgrade CDs

Operating system CD label

Windows IBM Tivoli System Automation Application Manager V3.1.0WAS V6.1 upgrade for Windows

AIX IBM Tivoli System Automation Application Manager V3.1.0WAS V6.1 upgrade for AIX

Linux on System x IBM Tivoli System Automation Application Manager V3.1.0WAS V6.1 upgrade for Linux on System x

Linux on POWER IBM Tivoli System Automation Application Manager V3.1.0WAS V6.1 upgrade for Linux on POWER

Linux on System z IBM Tivoli System Automation Application Manager V3.1.0WAS V6.1 upgrade for Linux on System z

Electronic distribution: You can also obtain System Automation ApplicationManager and WebSphere Application Server through electronic distribution. In thiscase, you can download the deliverables from a URL you receive after purchasingthe product.


Archives: The following tables list the archives that you need for installing theWebSphere Application Server upgrade and the product itself.

Windows:

Table 3. Archives for Windows platforms

Archive name Description

C1A1XML.exe This is the archive you use to install the product. The archive is self-extracting.After extraction, the directory structure is identical to that on the correspondingCD.

C1A24ML.exe The self-extracting archive contains the files that you need for installing theWebSphere Application Server upgrade. After extraction, the directory structureis identical to that on the corresponding CD.

AIX:

Table 4. Archives for AIX platforms


C1A1YML.bin This is the archive you use to install the product. The archive is self-extracting.After extraction, the directory structure is identical to that on the correspondingCD.

C1A25ML.bin The self-extracting archive contains the files that you need for installing theWebSphere Application Server upgrade. After extraction, the directory structureis identical to that on the corresponding CD.

Linux on System x:

Table 5. Archives for Linux on System x


C1A2SML.tar This is the archive you use to install the product. To extract the archive GNUtar 1.13 or later is required. Use the tar -xf command to extract the files to atemporary directory. After extraction, the directory structure is identical to thaton the corresponding CD.

C1A26ML.tar The archive contains the files that you need for installing the WebSphereApplication Server upgrade. After extraction, the directory structure is identicalto that on the corresponding CD.

Linux on POWER:

Table 6. Archives for Linux on POWER


C1A1ZML.tar This is the archive you use to install the product. To extract the archive GNUtar 1.13 or later is required. Use the tar -xf command to extract the files to atemporary directory. After extraction, the directory structure is identical to thaton the corresponding CD.


Linux on System z:

Chapter 2. Installing System Automation Application Manager 7

Table 7. Archives for Linux on System z


C1A20ML.tar This is the archive you use to install the product. For extracting the archive,GNU tar 1.13 or later is required. Use the tar -xf command to extract the filesto a temporary directory. After extraction, the directory structure is identical tothat on the corresponding CD.


DB2 setup optionsWhen 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 forSystem Automation Application Manager. You have the following options:

Local DB2 setupThe DB2 server is installed and runs on the same node on which SystemAutomation Application Manager is installed.

Remote DB2 setupThe DB2 server is installed and runs on a node other than that on whichSystem Automation Application Manager is installed. In this case, youneed to install a DB2 JDBC driver on the System Automation ApplicationManager node.

Product requirementsThe following sections list the software and hardware requirements for SystemAutomation Application Manager.

Supported operating systems: The following table lists the operating systems thatare supported for System Automation Application Manager:

Table 8. Supported operating systems

Operating system IBM System x1 IBM System i IBM System p IBM System z

Windows Server 2003 Standard Edition(32-bit)

x

Windows Server 2003 Enterprise Edition(32-bit)

x

Windows Server 20082 Standard Edition(32-bit)

x

Windows Server 20082 Enterprise Edition(32-bit)

x

AIX 5.33 (AIX 5L Version 5.3) ML 4 x

AIX 6.14 x

SUSE SLES 9 (32-bit)5 x

SUSE SLES 9 (64-bit)6 x x x

SUSE SLES 10 (32-bit)5 x

SUSE SLES 10 (64-bit)6 x x x

Red Hat RHEL 4.5 AS (32-bit)5 x

Red Hat RHEL 4.5 AS (64-bit)6 x x x

Red Hat RHEL 5.0 AS (32-bit)5 x


Table 8. Supported operating systems (continued)

Operating system IBM System x1 IBM System i IBM System p IBM System z

Red Hat RHEL 5.0 AS (64-bit)6 x x x

Notes:1. IBM System x with IA32, EM64T, or AMD64 architecture.

Any other systems with IA32, EM64T, or AMD64 architecture are alsosupported.Systems with IA64 architecture are not supported.All supported operating systems are also supported when running underVMWare.

2. Windows Server 2008 installed as Server Core or under Hyper-V is notsupported.

3. APAR IY65979 must be installed.4. AIX 6.1 supports Workload Partition (WPAR) mobility or relocation. In the V3.1

release, System Automation Application Manager do not support domains withnodes that are System WPARs.

5. The following Linux kernel architectures are supported for running with 32-bit:v x86 on IBM System x

6. The following Linux kernel architectures are supported for running with 64-bit:v ppc64 on IBM System i and IBM System pv s390x on IBM System z is supported for some distributions

Middleware software requirements: The following middleware software must beinstalled on the system on which System Automation Application Manager willrun, before the component itself can be installed:v DB2: A DB2 server for a local DB2 setup or a DB2 JDBC driver for a remote DB2

setupv WebSphere Application Server (32-bit version)

DB2 software prerequisites: Before you can install System Automation ApplicationManager, one of the following IBM DB2 UDB versions must be installed on thesystem on which System Automation Application Manager will run:v IBM DB2 Version 9.5, which is bundled with System Automation Application

Manager, Version 3.1v IBM DB2 UDB Enterprise Server Edition, Version 8.2.3 or higher

Software prerequisites for a local DB2 setup: If you are using a local DB2 setup, theend-to-end automation management database and the database tables are createdby the installation program during the installation of System AutomationApplication Manager.

Software prerequisites for a remote DB2 setup: Before you can install the automationmanager and the operations console, the following software prerequisites must bemanually installed:v A DB2 JDBC driver must be installed on the System Automation Application

Manager node:1. Copy the DB2 JDBC driver files from the Java directory of your DB2 server

to the system where you install System Automation Application Manager.The name of the location/directory is at your discretion.

2. Make the location/directory accessible to WebSphere Application Server andthe System Automation Application Manager installation program.


||

Supported Web browsers: The operations console is the user interface of SystemAutomation Application Manager. It is displayed in a Web browser that connectsto the WebSphere Application Server on which the operations console is running.The Web browser may run on an arbitrary system.

The following minimum levels of Web browsers are supported:v Microsoft Internet Explorer V6.0 SP1v Mozilla V1.7.8v Firefox V1.5

For information on how the Web browser must be configured, refer to the IBMTivoli System Automation Application Manager Administrator’s and User’s Guide,section "Configuring your Web browser".

Hardware requirements: The following sections describe the hardwarerequirements for System Automation Application Manager. The description doesnot cover the hardware requirements that need to be satisfied for installing andrunning the required middleware software. For more information on hardwarerequirements for the required middleware software, refer to “Installing themiddleware software” on page 12.

Memory: 1.5 GB is required on the server on which System AutomationApplication Manager is installed (for WebSphere Application Server and SystemAutomation Application Manager).

TCP/IP connectivity: System Automation Application Manager consists of variouscomponents that may run on one or several systems. For example:v When you use a local DB2 setup without Websphere Application Server the

automation manager, the operations console, and the DB2 server run on thesame system (single-node setup).

v When you use a remote DB2 setup, or a local DB2 setup with WebsphereApplication Server, System Automation Application Manager and the DB2 serverrun on separate systems (multi-node setup).

Be sure that TCP/IP connections can be established between the followingcomponents:v the WebSphere Application Server that is running the automation J2EE

framework, the resource adapters, and the operations consolev the DB2 server

Disk space requirements:

Disk space requirements on Windows systems: The following table lists the disk spacerequirements for System Automation Application Manager on Windows systems.Note that the table does not include the space required for the installation of themiddleware software.

Table 9. Disk space requirements on Windows systems

Description Default directory Disk space

System AutomationApplication Managerinstallation directory

C:\Program Files\IBM\tsamp\eez 100 MB


Table 9. Disk space requirements on Windows systems (continued)


Automation managerand operationsconsole deployed inWebSphereApplication Server

C:\Program Files\IBM\WebSphere\AppServer 50 MB

DB2 database C:\DB2 120 MB

Temporary diskspace needed forinstallation andinstallation log andresponse files

The value of the system variable %TEMP%

Typically, this is:

C:\Documents and Settings\Administrator\Local Settings\Temp

125 MB

Configuration filedirectory and policypool directory ofSystem AutomationApplication Manager

C:\Program Files\IBM\tsamp\eez\cfg

C:\Program Files\IBM\tsamp\eez\policyPool

1 MB

Tivoli CommonDirectory

C:\Program Files\IBM\tivoli\common\eez 250 MB

Installer registry The Zero G Registry resides in the hidden directory:

C:\Program Files\Zero G Registry\.com.zerog.registry.xml

10 KB

Disk space requirements on AIX and Linux systems: The following table lists the diskspace requirements for System Automation Application Manager on AIX and Linuxsystems. Note that the table does not include the space required for the installationof the middleware software.

Table 10. Disk space requirements on AIX and Linux systems


Installation directory of SystemAutomation Application Manager

/opt/IBM/tsamp/eez 205 MB

Automation manager and operationsconsole deployed in WebSphereApplication Server

AIX: /usr/IBM/WebSphere/AppServer

Linux: /opt/IBM/WebSphere/AppServer

30 MB

DB2 database ∼db2inst1 120 MB

Temporary disk space needed forinstallation and installation log andresponse files

/tmp 125 MB

Configuration file directory and policypool directory of System AutomationApplication Manager

/etc/opt/IBM/tsamp/eez/cfg

/etc/opt/IBM/tsamp/eez/policyPool

1 MB

Tivoli Common Directory /var/ibm/tivoli/common/ 250 MB

Installer registry /var/.com.zerog.registry.xml 5 KB

Security conceptsThe following sections describe the security concepts for System AutomationApplication Manager.

Security considerations: In a local DB2 setup, in which System AutomationApplication Manager and the external components needed for running (WebSphere


Application Server and DB2) are installed on the same system, you do not need tosecure the connections between these components over SSL.

The external connections that will be established between the components listedbelow, however, should be secured over SSL, especially if the external componentsare running in different security domains that are separated by firewalls.

External connections will be established between the following components (thedefault port numbers are given in brackets):v The connection from the automation engine to the automation adapters (port

2001).v The connection from the automation adapters to the automation engine(port

2002). Note that SSL is not supported for this connection.v The connection between the Web browsers in which the operations console is

displayed and Integrated Solutions Console (HTTP port 9060, HTTPS port 9043).

User management: For information on how user IDs and passwords forend-to-end automation management are managed, refer to the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide, chapter "Managingusers".

Installing the middleware softwareDepending on the setup type you choose, middleware software has to be installedon one or more systems before System Automation Application Manager can beinstalled.v For information on possible setup types, refer to “DB2 setup options” on page 8v For information on the required middleware software for each system, refer to

“Middleware software requirements” on page 9

Contents of the middleware software CDsThe middleware software CDs that are shipped with the System AutomationApplication Manager product CDs contain the following software products:v IBM DB2 UDB Version 9.1 Enterprise Server Edition (DB2 server)v The 32-bit version of IBM WebSphere Application Server Base Version 6.1

Notes:

1. IBM Tivoli System Automation Application Manager only supports the 32-bitversion of WebSphere Application Server.

2. In addition to a WebSphere Application Server 6.1 CD for every supportedplatform, a WebSphere Application Server 6.1.0 upgrade CD is available foreach supported platform. The upgrade CD is needed for bringing WebSphereApplication Server to the required product level.

3. Websphere Application Server 6.1 Network Deployment is not supported.4. Please note that the IBM Tivoli Directory Server is not contained on the

middleware software CDs.

Installing a DB2 server

DB2 server requirements: Use the following publications to find out whichrequirements need to be met for installing and running a DB2 server:v IBM DB2 UDB - Quick Beginnings for DB2 Servers (GC09-4836)v IBM DB2 UDB - Release Notes - Version 9


The latest versions of these publications are available on the IBM DB2 UDB Website:

www.ibm.com/software/data/db2/udb/support/

You will find the link to the PDF manuals in the Other resources section on theWeb page.

In addition, check for the latest system requirements at

www.ibm.com/software/data/db2/udb/sysreqs.html

The DB2 release notes can also be found on the CD labeled IBM DB2 UDBEnterprise Server Edition Version 9.1 for your platform. Make sure that allrequirements for installing and running a DB2 server are met. Otherwise, SystemAutomation Application Manager may not install or work properly.

DB2 server installation: You can use the DB2 Setup wizard to install the DB2server. You will find the DB2 Setup wizard on the CD labeled IBM DB2 UDBEnterprise Server Edition Version 9.1 for your platform.

The typical installation of a single-partition database environment is recommended.

On a Windows system, the following users must be local users:v the DB2 administration server userv the fenced userv the instance owner user

You must create a DB2 instance before you install System Automation ApplicationManager.

Make sure that the DB2 server has the required version level (see “Middlewaresoftware requirements” on page 9).

Make a note of the following information for future reference:v The host name of the system where the DB2 server is installed.v The port number of the DB2 instance

The port number is displayed on the summary panel of the DB2 Setup wizard.The summary panel appears immediately before the wizard copies the programfiles.

v The name of the directory to which the DB2 server is installed if a local DB2setup is used

v The name and password of the instance owner user or of a different user who isauthorized to drop and create databases and database tables, and to select,insert, delete, and update table rows.

Note: See Chapter 7. ″Controlling database access″ in IBM DB2 UDB AdministrationGuide: Implementation, Version 9.1 (SC09-4820) for information about DB2server security concepts and on how to authorize users to perform certaintasks.

Post-installation tasks for remote DB2 setup: The following tasks must becompleted on the DB2 server system:


http://www.ibm.com/software/data/db2/udb/support

http://www.ibm.com/software/data/db2/udb/sysreqs.html

v Identify the DB2 instance that will hold the databases. Identify the instanceowner user ID and password. Identify the host name of the DB2 server system.Identify the TCP/IP port of the DB2 instance.

v Create the automation manager database (for information on how to do this, seebelow).

v Create the automation manager tables in the database (for information on howto do this, see below).

Note: If the database has already been created and tables already exist, youmust drop the existing tables before creating the tables.

v To use a remote database setup, the following JDBC driver files must be copiedfrom the remote database to a directory on the local system where SystemAutomation Application Manager will be installed:– db2jcc.jar– db2jcc_license_cu.jar

The CD IBM Tivoli System Automation Application Manager V3.1.0 for your platformcontains scripts for creating the required databases and tables.

Creating the automation manager database and the database tables:

On Windows: Perform the following steps if your DB2 server runs on a Windowssystem:1. Log in with a user ID that has SYSADM privileges on the DB2 instance.2. On the CD labeled IBM Tivoli System Automation Application Manager V3.1.0 for

Windows, change the directory to DDL\Script

3. From this directory, run the following two batch files:db2_create_automgr_db.bat <db_name> <instance_owner> <instance_pw>db2_create_reporting_tables.bat <db_name> <instance_owner> <instance_pw>

wherev <db_name> is the desired name of the automation manager database

(Example: EAUTODB)v <instance_owner> is the instance owner user ID of the DB2 instance

(Example: db2admin)v <instance_pw> is the password of the instance owner user ID

On AIX or Linux: Perform the following steps if your DB2 server runs underLinux or AIX:1. Log in as root.2. On the CD labeled IBM Tivoli System Automation Application Manager V3.1.0 for

your operating system, change the directory to DDL/Script.3. From this directory, run the following two shell scripts:

db2_create_automgr_db.sh <db_name> <instance_owner> <instance_pwd> <script_directory>db2_create_reporting_tables.sh <db_name> <instance_owner> <instance_pwd> <script_directory>

wherev <db_name> is the desired name of the automation manager database

(Example: EAUTODB)v <instance_owner> is the instance owner user ID of the DB2 instance

(Example: db2inst1)


v <instance_pwd> is the password of the instance owner user IDv <script_directory> directory where the DB2 scripts for Tivoli System

Automation are located on the CD, which you changed to in step 2(DDL/Script)

Verifying the creation of the remote database: After running the scripts as described in“Creating the automation manager database and the database tables” on page 14,issue the following commands to verify that the remote database was createdcorrectly:1. su - db2inst1

2. db2 connect to <db_name>

3. db2 list tables for schema eautousr

4. db2 disconnect <db_name>

The output of the list tables command should display the following table names:

Table 11. Database tables

EEZAUTOMATIONACCESS

EEZAUTOMATIONRELATION

EEZCOMMONEVENTS

EEZDOMAINSUBSCRIPTION

EEZOPERATORDOMAINFILTER

EEZOPERATORDOMAINPREFERENCES

EEZOPERATORHIDDENDOMAIN

EEZRESOURCESUBSCRIPTION

EEZSAFOSEVENTS

Installing WebSphere Application ServerBefore you begin:

v IBM Tivoli System Automation Application Manager only supports the 32-bitversion of WebSphere Application Server.

v WebSphere Application Server 6.1 Network Deployment is not supported.v Installing WebSphere Application Server from the CD "IBM WebSphere

Application Server Base Version 6.1" does not result in the required versionlevel. To obtain the required version level 6.1.0.15, you must perform thefollowing steps:1. Install WebSphere Application Server from the CD "IBM WebSphere

Application Server Base Version 6.1" or from the electronic delivery pathfrom IBM.

2. Install the WebSphere Application Server 6.1.0 UpdateInstaller.3. Use the UpdateInstaller to install the required fixes into WebSphere

Application Server 6.1.4. Augment the application server of your WebSphere Application Server

installation, or, preferably, augment every server profile into which you wantto install System Automation Application Manager.

These steps are described in the subsequent sections.


WebSphere Application Server 6.1.0.15 requirements: Check the followingpublication to find out which requirements need to be met for installing andrunning WebSphere Application Server Base:v The ReadMe file, which is available on the product CD "IBM WebSphere

Application Server Base Version 6.1".v The "Getting started" topics in the Information Center for IBM WebSphere

Application Server, Version 6.1.v An IBM WebSphere Application Server Getting started document is also available

on the product CD for your platform, where it is also referred to as InstallationGuide. Make sure that all requirements for installing and running WebSphereApplication Server are met. Otherwise, System Automation Application Managermay not work properly.

The latest versions of all WebSphere Application Server publications can be foundat

www.ibm.com/software/webservers/appserv/was/library/

In addition, check for the latest system requirements at

www.ibm.com/software/webservers/appserv/was/requirements/

Installing WebSphere Application Server 6.1.0.15: You can use the WebSphereApplication Server installation wizard to install WebSphere Application Server. TheWebSphere Application Server installation wizard can be started from theWebSphere Application Server LaunchPad. You will find the LaunchPad on the CDlabeled IBM WebSphere Application Server Version 6.1 for your platform or from theelectronic deliverable for your platform (see “Product CD and WebSphereApplication Server upgrade CD” on page 6).

The typical installation is recommended.

Upgrading WebSphere Application Server 6.1: Before you can install SystemAutomation Application Manager version 3.1, you must upgrade WebSphereApplication Server 6.1 to level 6.1.0.15, upgrade the WebSphere Java version toJava 5 Service Release 6 and install the Advanced Edition of Integrated SolutionsConsole 7.1.

To do so, you use the WebSphere Application Server 6.1.0 upgrade CD for yourplatform or from the electronic deliverable for your platform (see “Product CD andWebSphere Application Server upgrade CD” on page 6). The contents of the CD orthe electronic deliverable are listed in the following table.

To install the packages from the CD or the electronic deliverable, you first installthe UpdateInstaller (see “Installing the UpdateInstaller” on page 17) and use it toinstall the remaining packages (see “Installing the updates” on page 17).


http://www.ibm.com/software/webservers/appserv/was/library

http://www.ibm.com/software/webservers/appserv/was/requirements

Table 12. Contents of the WebSphere Application Server 6.1.0 upgrade CD or electronicdeliverable

Directory Contents

Fixes The following update packages:

v 6.1.0-WS-WAS-<your_platform>-FP0000015.pak

Upgrades WebSphere Application Server 6.1.0 to level 6.1.0.15.

v 6.1.0-WS-WASSDK-<your_platform>-FP0000015.pak

Upgrades the Java version of WebSphere Application Server toJava 5 Service Release 6

v 7.1.0.2-WS-WASFeature-FEISCAE7100.pak

Installs the Advanced Edition of Integrated Solutions Console 7.1

README The readme file README.txt.

Upgrade The UpdateInstaller zip file for your platform.

Installing the UpdateInstaller: To install the UpdateInstaller perform these steps:1. Unpack the update installer zip file for your platform to a temporary directory.

Unzipping creates the directories JDK and UpdateInstaller.2. Change to the UpdateInstaller directory.3. On Linux and AIX use the command ls -al to check that the file install has

execute permission. If the execute permission is not correctly set use thecommand chmod +x install to set it.

4. Invoke the file install to install the UpdateInstaller. When installed, theUpdateInstaller is located in the following directory by default:v AIX: /usr/IBM/WebSphere/UpdateInstaller/update.sh

v Linux::/opt/IBM/WebSphere/UpdateInstaller/update.shv Windows: C:\Program Files\IBM\WebSphere\UpdateInstaller\update.bat

5. Optional: Delete the temporary directory.

Installing the updates: You can install all updates with one invocation of theUpdateInstaller. If for any reason the UpdateInstaller does not install Fix Pack 15first, remove the installed packages and install Fix Pack 15 first.

Augmenting the application server of your WebSphere Application Server installation:You need to augment the application server of your WebSphere Application Serverinstallation, or, preferably, augment every server profile into which you want toinstall System Automation Application Manager.

To do so, issue the following command (the example assumes that the profile nameis AppSrv01 and the server name is server1):<was_home>/bin/manageprofiles.sh

-augment -templatePath <was_home>/profileTemplates/iscae71-profileName AppSrv01 -serverName server1

If the default path is used, <was_home> stands for:v AIX: /usr/IBM/WebSphere/AppServer/binv Linux: /opt/IBM/WebSphere/AppServerv Windows: C:\Program Files\IBM\WebSphere\AppServer

Considerations about user and group management: If you intend to configureWebSphere Application Server to use a security product in read-only mode so that


||

the WebSphere administrative interfaces to manage users and groups cannot beused, see Appendix G, “Considerations about user and group management inWebSphere Application Server,” on page 213 for more information.

Preparing for the installation of System AutomationApplication Manager

Collecting the information you need to provide duringinstallationOn AIX, Linux and Windows systems the installation of System AutomationApplication Manager is wizard-driven. The wizard guides you through theinstallation and prompts you for installation and configuration parameters. Thefollowing tables list the parameters you need to specify on the installation wizardpanels, in the order in which they must be specified.

Make sure that you specify all required parameters on the installation wizardpanels and that your entries are correct. The installation wizard does not verifythat your entries are correct and complete during the installation.

Installation directory and Tivoli Common Directory: The parameters listed in thefollowing table must always be specified.

Table 13. Installation directory and Tivoli Common Directory

Parameter Description Default

Installation directory name The directory to which the installablefeatures are installed.

In this guide, this directory is referred toas EEZ_INSTALL_ROOT.

When specifying a directory other than thedefault, observe the following restrictions:

Windows:

v The directory name has to consist of theplatform-specific path separatorcharacter and alphanumeric characters(A..Z, a..z, 0..9).

v The colon character is allowed onlyonce, immediately following the driveletter. For example, C:\<directory_name>is allowed, butC:\<directory_name>:<directory_name>is not allowed.

v The space character and the underscorecharacter (_) are allowed.

Windows:

C:\Program Files\IBM\tsamp\eez

AIX, Linux:


v The underscore character (_) is allowed.

v The space and colon characters are notallowed.

AIX, Linux:

/opt/IBM/tsamp/eez


|||

Table 13. Installation directory and Tivoli Common Directory (continued)


Tivoli Common Directory The Tivoli directory for storingserviceability information.

During installation, you are only promptedfor input when no Tivoli CommonDirectory is found on the system.

In the Tivoli Common Directory, thesubdirectory eez is created for storingproduct-specific data.

In this guide, this directory is referred toas Tivoli_Common_Directory.

When specifying a directory other than thedefault, observe the following restrictions:

Windows:


v The colon character is allowed onlyonce, immediately following the driveletter. For example, C:\<directory_name>is allowed, butC:\<directory_name>:<directory_name>is not allowed.

v The space character and the underscorecharacter (_) are allowed.

Windows:

C:\Program Files\IBM\tivoli\common

AIX, Linux:


v The underscore character (_) is allowed.

v The space and colon characters are notallowed.

AIX, Linux:

/var/ibm/tivoli/common

Installation parameters for DB2:

Note:

When you have a local DB2 setup but do not want the installation wizard tocreate the end-to-end automation management database and the databasetables, just select the radio button for remote DB2 setup (IBM DB2 UDB ondifferent system (remote)) on the Database Server window of theinstallation wizard. If you make this selection, the installation wizard willneither create the database nor any tables and you are free to set up thedatabase manually as you would for remote setup.

The parameters listed in the following table must be specified.


Table 14. DB2 data for local and remote DB2 setup


DB2 UDB directory The installation location of the DB2 clientdirectory.

If you are using a local DB2 setup, youuse the DB2 client that is part of the DB2server installation. In this case, you needto specify the DB2 server directory.

The location is detected on your systemand displayed as the default directory.

DB2 instance host name Remote DB2 setup: The host name of theDB2 instance in which the automationmanager and operations consoledatabases are located.

DB2 instance port number The port number of the DB2 instance inwhich the automation manager andoperations console databases are located.Note: When you install SystemAutomation Application Manager on AIXor Linux systems the installation wizardcan retrieve the valid DB2 instance portnumber automatically. If you choose notto use this function, or are installing onWindows systems, the port number 50000will be displayed in the entry field on thecorresponding installation wizard panel.This is the default port number that isassigned to DB2 during the installation ofDB2. However, if this port is not free, adifferent port number is assignedautomatically, which is why you need tocheck if the default port number iscorrect.

How you determine the correct portnumber is described in “Determining thecorrect DB2 port number” on page 199.

50000

Database instance ownername

The instance owner user ID of the DB2instance in which the automationmanager and operations consoledatabases are located.

In a local DB2 setup, this user ID will beused for creating the databases and tables.

In a remote DB2 setup, the database andthe tables must have already beencreated. The installation program does nochange to DB2 and neither creates a DBnor tables.

The user ID will be used by WebSphereApplication Server to connect to theautomation manager and operationsconsole databases and to select, insert,delete, and update rows in tables.

Windows: db2admin

AIX, Linux: db2inst1


Table 14. DB2 data for local and remote DB2 setup (continued)


Database instance ownerpassword

The password for the instance owner userID of the DB2 instance in which theautomation manager and operationsconsole databases are located.

No default value is provided

DB2 UDB JDBC driver pathon local system

For remote DB2 setup only: Path to thedirectory where the files DB2 JDBC arelocated.

Automation managerdatabase

Automation manager database for use byWebSphere Application Server.

In a local DB2 setup, a database with thisname will be created in the DB2 instancerelated to the specified instance owner.

In a remote DB2 setup, a database withthis name must already exist in theremote DB2 instance.

EAUTODB

If an automation manager database(EAUTODB) from an earlier installationalready exists, the database will bedropped without warning during theinstallation of System AutomationApplication Manager. To preserve thedata from the earlier installation, you canexport the data before starting theinstallation and import it during theinstallation. For information on exportingthe data from the database, seeAppendix B, “Preserving user data duringthe upgrade from IBM Tivoli SystemAutomation for Multiplatforms 2.x toSystem Automation Application Manager3.1,” on page 197.

Backend version Version of the back end DB2:

v ZOSUDB81: DB2 UDB V8.1 - running onz/OS

v ZOSUDB91: DB2 UDB V9.1 - running onz/OS

v DIST: DB2 UDB - running ondistributed system

DB2_OPTN_UDB

WebSphere Application Server installation parameters: The parameters listed inthe following table are detected during the installation of System AutomationApplication Manager.

Note that WebSphere Application Server administrative security must be enabledbefore you install System Automation Application Manager.

Table 15. WebSphere Application Server installation parameters


WebSphere Application Serverdirectory

The installation location ofWebSphere Application Server. Theremust be exactly one installation ofWebSphere Application Server onyour system.

The location is detected on yoursystem and displayed as the defaultdirectory.

WebSphere Application Server (WAS)profile name

The WebSphere Application Serverprofile to be used for the automationmanager and the operations console.

All existing profiles are detected onyour system and displayed in asingle-choice list.

WebSphere Application Server (WAS)server name

The server to be used for theautomation manager.

The server name is detected on yoursystem and displayed as defaultvalue.


Table 15. WebSphere Application Server installation parameters (continued)


WAS Admin User ID The user ID of the WebSphereApplication Server administrator.

No default value is provided.

WAS Admin User Password The password of WebSphereApplication Server administrator userID.

No default value is provided.

IBM Tivoli Enterprise Console connection configuration data: Optionally, youcan use Tivoli Enterprise Console for monitoring end-to-end automationmanagement events. The parameters listed in the following table are only requiredif you will be utilizing Tivoli Enterprise Console for end-to-end automationmanagement.

Table 16. Installation parameters for IBM Tivoli Enterprise Console


TEC host name The name of the host where the Tivoli Enterprise Console serveris installed.

localhost

TEC server port number The port number for the Tivoli Enterprise Console server 5529

For more information about utilizing Tivoli Enterprise Console for end-to-endautomation management, refer to the IBM Tivoli System Automation ApplicationManager Administrator’s and User’s Guide, chapter "Using Tivoli Enterprise Consolewith System Automation Application Manager"

Name of the end-to-end automation domain:

Table 17. End-to-end automation domain name


Automation domainname

The name of the end-to-end automation domain represented bythis instance of the automation engine. The domain name must beunique and may not be used for any other automation domain.

The characters used for the domain name are limited to thefollowing ASCII characters: A–Z, a–z, 0–9, . (period), and _(underscore).

FriendlyE2E

WebSphere Application Server user ID for the end-to-endautomation engineThe end-to-end automation engine requires a WebSphere Application Server userID to access the J2EE framework. The user ID is created during the installation ofSystem Automation Application Manager.

In the installation wizard on AIX, Linux and Windows systems you need to specifythe user ID and the password.

Table 18. WebSphere Application Server user ID


User ID WebSphere Application Server user ID for the end-to-endautomation engine.

eezdmn

Password Password of the user ID


System Automation Administrator user IDDuring the installation of System Automation Application Manager, the initialTivoli System Automation administrator user is created in WebSphere ApplicationServer and authorized for all tasks and actions that can be performed from theSystem Automation operations console. In the installation wizard you need tospecify the data listed in the following table:

Table 19. System Automation Administrator user ID


User ID User ID of the System Automation operations consoleadministrator

eezadmin

Password Password of the user ID none

First and last name ofthe user

User name none

What the installation media containsSystem Automation Application Manager can be ordered from IBM as a mediapack or downloaded as an Electronic Software Distribution (ESD) image from anIBM software distribution download site.

There are multiple CDs for each supported platform.

This is what the CD labeled IBM Tivoli System Automation Application ManagerV3.1.0 for <operating_system_name> contains:v The files for launching the installation wizardv The readme filev Directories containing the files required to install components that are embedded

into the System Automation Application Manager installation. These are:

Table 20. Directories on the product CD

Directory Content

README For example, copyright notices and license agreements

license License key

DDL Scripts for creating DB2 databases and tables when remote DB2 setup is used

ECExtension setup.jar

<PLATFORM>¹ Product installer and files needed for installing the product

DOCS Documentation

Note:

1. <PLATFORM> is one of the following:

v AIX

v PPC (Linux on POWER)

v Windows

v i386 (Linux on System x)

v S390 (Linux on System z)

Languages supported by System Automation ApplicationManagerIn addition to English, System Automation Application Manager supports thefollowing languages:


v Germanv Spanishv Frenchv Italianv Japanesev Koreanv Brazilian Portuguesev Simplified Chinesev Traditional Chinese

Installation prerequisitesThe following prerequisites must be satisfied before you can start the installationwizard for System Automation Application Manager:v The 32-bit version of WebSphere Application Server must be installed as

described in “Installing WebSphere Application Server” on page 15. No otherWebSphere Application Server product installation must exist on the system.

v A DB2 server must be installed as described in “Installing a DB2 server” on page12. The DB2 server instance must be running and accepting client connections.For more information on setting up the DB2 environment refer to IBM DB2 UDBAdministration Guide: Implementation.

v If an automation manager database (EAUTODB) from an earlier installationalready exists, for example, if you are upgrading from IBM Tivoli SystemAutomation 2.2 to 3.1, in which case you need to uninstall the older versionbefore installing the new, the database will be dropped without warning duringthe installation of System Automation Application Manager. To preserve the datafrom the earlier installation, you can export the data before starting theuninstallation, and import it during the installation. For information onexporting the data before uninstalling, see Appendix B, “Preserving user dataduring the upgrade from IBM Tivoli System Automation for Multiplatforms 2.xto System Automation Application Manager 3.1,” on page 197.

v In the current Red Hat 5 distributions, the SElinux environment is switched onby default. It must be switched off for System Automation Application Managerto work properly.

v The user ID that is used to run the installer for System Automation ApplicationManager must have administrator authority.On Linux and AIX, this user ID is typically ″root″.On Windows this is the built-in local Administrator user account of the system.

v When installing System Automation Application Manager to an AIX or Linuxsystem, you must ensure that an X Window session is available for displayingthe graphical installation wizard panels.

v On Windows Server 2008 you must install, configure, run and use the operationsconsole with the built-in local Administrator user account of the system. If UserAccount Control (UAC) is active on the system (this is the default value) youmust keep the default settings:– ″User Account Control: Admin Approval Mode for the Built-in Administrator

account″ disabled– ″User Account Control: Detect application installations and prompt for

elevation″ enabled.


Installing System Automation Application Manager using theinstallation wizard

This section describes how to install System Automation Application Manager. Forthe installation, you use a graphical installation program, the so-called installationwizard. The required steps are described below.

On the panels of the installation wizard, enter the data you have collected usingthe lists in section “Collecting the information you need to provide duringinstallation” on page 18. Make sure that you specify all required parameters on theinstallation wizard panels and that your entries are correct. The installation wizarddoes not verify that your entries are correct and complete during the installation.

Notes:

1. The installation wizard panels in this section show an installation on an AIXsystem. The wizard panels that are displayed during the installation on otheroperating systems are very similar. Make sure to conform to the conventions ofyour platform when specifying directory locations and file names.

2. In this section, only those panels are depicted on which user actions arerequired.

3. The installation comprises these phases:a. In the pre-installation phase, you specify the installation parameters.b. The installation phase begins when you click the Install button on the last

pre-installation panel. In this phase, all files are installed to the disk.c. The configuration step, in which the necessary WebSphere Application

Server and DB2 configuration is performed. The configuration step can becanceled at any time. The installation can be resumed by simply calling theinstaller again.

To install System Automation Application Manager, perform these steps:1. Make sure that all installation prerequisites are met (refer to “Installation

prerequisites” on page 24)._________________________________________________________________

2. Insert the following CD into the CD drive:IBM Tivoli System Automation Application Manager V3.1.0

There are multiple CDs. Be sure to use the one for your platform.If you are using electronic distribution switch to the appropriate archive._________________________________________________________________

3. Change to the directory that contains the installation program. For the locationof the directory, refer to “Packaging” on page 5._________________________________________________________________

4. Launch the installation wizard by starting the following program from thecurrent working directory:v Windows: setup.exe

To generate a response file for use in a silent installation, use the followingcommand to launch the wizard:setup.exe -Dpreparesilent=true

v AIX, Linux: setup.binTo generate a response file for use in a silent installation, use the followingcommand to launch the wizard:setup.bin -Dpreparesilent=true


When the installation wizard is ready, the initial wizard window appears:

_________________________________________________________________5. Select the language in which the text on the wizard panels is to appear and

click OK. The language in which System Automation Application Manager isinstalled is derived from the system's locale setting._________________________________________________________________

6. The next panel displayed is the Introduction panel. Read the information onthis panel and click Next to proceed.

_________________________________________________________________7. The Software License Agreement follows. Carefully read the terms of the

license agreement, and also make sure to read the non-IBM terms by clickingthe Read non-IBM terms button.


To accept the terms of the license agreement, select I accept both the IBM andthe non-IBM terms and click Next._________________________________________________________________

8. Specify the directory where you want to install System AutomationApplication Manager or accept the default location.Click Next.

_________________________________________________________________9. If the installation program detected a Tivoli Common Directory on your

system, for example, because a Tivoli product is already installed, thedirectory must also be used for System Automation Application Manager. Inthis case, the entry field on the panel is write-protected.If the installation program did not detect a Tivoli Common Directory on yoursystem, accept the default location or specify the directory to which the Tivolilog files are to be written.Click Next.


_________________________________________________________________10. Select the DB2 setup type you are using and click Next.

Which panel appears next, depends on the type of DB2 setup you selected:v Local DB2 setup: Proceed with step 11.v Remote DB2 setup: Proceed with step 14 on page 30._________________________________________________________________

11. This panel only appears when you are using a local DB2 setup.

Specify the database name or accept the default name and click Next. Notethat an existing EAUTODB will be dropped automatically without warning(for information on preserving existing data, see Appendix B, “Preserving userdata during the upgrade from IBM Tivoli System Automation forMultiplatforms 2.x to System Automation Application Manager 3.1,” on page197).


_________________________________________________________________12. This panel only appears when you are using a local DB2 setup.

Specify the name and password of the DB2 instance owner and click Next.

_________________________________________________________________13. This panel only appears when you are using a local DB2 setup.

In the field DB2 instance port number, the valid port number must bespecified:v If the DB2 port number was retrieved automatically, the valid port number

is displayed in the field.v If the DB2 port number was not retrieved automatically, the default port

number (50000) is displayed. The actual DB2 port number may differ fromthe default, because a different port number is assigned automaticallyduring DB2 installation if the default port is not free. Before you accept thedefault value, ensure that it is correct, or specify the valid port number.


Click Next and proceed with step 16 on page 31.

Note: After you click Next, the installation program checks whether thedatabase can be accessed with the values you specified on the panel. Ifyou want to skip the check, select the check box on the panel.

_________________________________________________________________14. This panel only appears when you are using a remote DB2 setup.

Specify the database name (see “Post-installation tasks for remote DB2 setup”on page 13), select the DB2 Backend ID type that matches the remote DB2database platform and version that has to be used by this installation of SAApplication Manager, and click Next.

_________________________________________________________________15. This panel only appears when you are using a remote DB2 setup.


Specify the path to the DB2 UDB JDBC driver or click Choose to select thedirectory (see “Post-installation tasks for remote DB2 setup” on page 13), andspecify the name and password of the database instance owner. Click Next.

_________________________________________________________________16. If you want to import existing data into the new end-to-end automation

database, select the Import data check box and specify the fully qualifieddirectory name in which the exported data is located.For information on how to export data from an existing end-to-endautomation database in such a way that it is ready for import, seeAppendix B, “Preserving user data during the upgrade from IBM TivoliSystem Automation for Multiplatforms 2.x to System Automation ApplicationManager 3.1,” on page 197.

_________________________________________________________________17. The installation directory of WebSphere Application Server is detected on your

system and displayed. Click Next.


_________________________________________________________________18. The existing WebSphere Application Server profiles are detected on your

system and displayed. Select the profile you want to use and click Next.

_________________________________________________________________19. Specify the end-to-end automation domain name you want to use or accept

the default name and click Next.

Note: Accept the default domain name (“FriendlyE2E”) if you want to use thesample System Automation Application Manager environment tofamiliarize yourself with end-to-end automation management and theoperations console. For more information, refer to the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide, section"Getting started".


_________________________________________________________________20. If you want to use Tivoli Enterprise Console to display end-to-end

automation management events:v Select Enable TEC server connection

v In the field TEC host name, specify the host name of the console server.v In the field TEC server port number, specify the port number of the

console server:– Windows: Accept the default value that is displayed in the field (5529)– AIX/Linux: Set the value to 0

Click Next.

Note: You can also enable the connection from the WebSphere ApplicationServer administrative console after the installation of SystemAutomation Application Manager is complete. This is described in theIBM Tivoli System Automation Application Manager Administrator’s andUser’s Guide, in the section "Using Tivoli Enterprise Console withSystem Automation Application Manager".


_________________________________________________________________21. To enable report data collection tick the box in the next panel.

_________________________________________________________________22. If the System Automation Application Manager Distributed Disaster Recovery

feature is supported on this platform this panel appears.


If you want to connect the Automation Manager to GDPS:v Select Enable GDPS server connection

v In the field GDPS server host name, specify the TCP/IP host name of theGDPS controlling system (also known as the ″K system″).

v In the field GDPS server port number, specify the TCP port numberconfigured for the NetView Event/Automation Service (E/AS) addressspace that is running on the GDPS controlling system.

If you want to enable a connection to a backup GDPS controlling system:v Select Enable GDPS backup server connection

v In the field GDPS server host name, specify the TCP/IP host name of yourbackup GDPS controlling system.

v In the field GDPS server port number, specify the TCP port numberconfigured for the NetView Event/Automation Service (E/AS) addressspace that is running on the backup GDPS controlling system.

Click Next.

Note: You can also enable or modify the GDPS connection from theWebSphere Application Server administrative console after theinstallation of System Automation Application Manager is complete.This is described in the IBM Tivoli System Automation ApplicationManager Administrator’s and User’s Guide, in the section "Configuring theJMS destination for GDPS events after installation".

_________________________________________________________________23. Specify the WebSphere Application Server user ID and password for the

end-to-end automation engine. The automation engine will use the credentialsfor accessing the J2EE framework that runs in WebSphere Application Server.


_________________________________________________________________24. Specify the user ID, password, and the first and last name of the System

Automation administrator. Do not use cut-and-paste to enter the passwordand the password confirmation, rather, directly type in the password and thepassword confirmation.

Note: You are recommended not to choose the same name for both theSystem Automation administrator user ID and the WAS administratoruser ID, as this will lead to problems if you later uninstall IBM TivoliSystem Automation Application Manager. For example, specifyingeezadmin or wasadmin for both users is not recommended.

Click Next.

_________________________________________________________________


25. When you have specified all the required information on the wizard panels, asummary panel appears. As the installation wizard will not check theavailable space, be sure to verify that sufficient space is available in the filesystem.Click Install to start the installation. The installation can take one or twohours to complete.

_________________________________________________________________26. While the component is being installed and configured, a number of

information panels inform you of the progress._________________________________________________________________

27. When the installation of System Automation Application Manager is complete,the Installation Complete panel appears. Click Done to close the installationwizard. For information on verifying the installation, refer to “Verifying theinstallation” on page 63.

_________________________________________________________________


Installing System Automation Application Manager in silentmode

You can install System Automation Application Manager in silent mode, using aresponse file you generated in a wizard-driven installation (see “Installing SystemAutomation Application Manager using the installation wizard” on page 25.

After the wizard-driven installation is complete, you will find the response fileinstall.properties in the following directory:<EEZ_INSTALL_ROOT>/install

Note that this file is always generated, even if you did not specify the option-Dpreparesilent=true when you invoked the installation wizard. However,install.properties files created without the -Dpreparesilent=true option cannotbe used for silent installation.

To perform a silent installation, perform these steps:1. Copy the response file install.properties file to the system on which you

want to perform the silent installation.2. To start the installation, issue this command:

Windows:setup.exe -i silent -f <fully_qualified_properties_file_name>

AIX, Linux:setup.bin -i silent -f <fully_qualified_properties_file_name>

Installing System Automation Application Manager on z/OS

Planning for installationThis chapter contains the information you need to prepare for the installation ofSystem Automation Application Manager on z/OS.

System Automation Application Manager for z/OS is distributed via tape and isinstalled using SMP/E. The prerequisite list and the detailed installationinstructions can be found in the Program Directory shipped with the tape.

Product componentsThe component structure of System Automation Application Manager on z/OS isthe same as on other platforms and is described in “Product components” on page5.

Product requirementsThe following sections list the software and hardware requirements for SystemAutomation Application Manager for z/OS.

Supported operating systems: z/OS 1.7 or later is required.

Middleware software requirements: The following middleware software must beinstalled on the system on which System Automation Application Manager forz/OS will run, before the component itself can be installed:v DB2: A DB2 server for a local DB2 setup or a DB2 JDBC driver for a remote DB2

setupv WebSphere Application Serverv ISC AE 7.1. This component can be downloaded from URL


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-iscae.

Supported Websphere Topologies on z/OS: This section describes possibletopologies of the installation of System Automation Application Manager on z/OS.

System Automation Application Manager running in base WebSphere setup: Thisscenario describes one way of configuring WebSphere Application Server for z/OSin a similar manner to WebSphere Base on distributed platforms. One applicationserver instance is setup on one z/OS System Image as an 'unmanaged server', inwhich the System Automation Application Manager is installed together with theoperations console policy editor and the reporting feature.

The Automation Engine (eezdmn), Hardware Adapter and End-to-End commandshell are installed on the same z/OS system, together with some required TCRcomponents. In this scenario the Browser Client is connecting to the ApplicationServer instance to open the operations console or to edit policies. The ApplicationServer is not managed by any deployment manager.

z/OS System Image

MQ

CICS

Db2Automation

engineTCR

Cell

CR SR

App server

Daemon

CR

Node

Commandshell

End-to-end Automation Manager

Hardwareadapter

Browserclient

HFS

Figure 3. WebSphere scenario - base


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-iscae

https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-iscae

You can install the System Automation Application Manager in this way bychoosing the setup option BASE in the ATVDOPTS member controlling thegeneration of the post installation jobs.

System Automation Application Manager running as highly available in a mixedWebSphere setup: This scenario describes how to install the System AutomationApplication Manager on more than one z/OS system image, for example to makeit highly available with the help of System Automation for z/OS. The SystemAutomation Application Manager does not support WebSphere clustering, so ifyou want to keep high availability and install the System Automation ApplicationManager on more than one z/OS system image you must choose the baseWebSphere setup and install the System Automation Application Manager on eachsystem image. A deployment manager cannot be used to administer theseunmanaged servers. Administration must be performed separately on each z/OSsystem image.

On each system you must define a cell to host one application server for theApplication Manager. In this scenario the browser client connects to the applicationserver, and not to the deployment manager, in order to open the SA operationsconsole.

Although the System Automation Application Manager only supports a baseWebSphere setup, if you choose to make it highly available it is still possible tohave an ND setup for other managed application servers running other JEEworkload on different system images, as shown in Figure 4.

Supported Web browsers: The operations console is the user interface of SystemAutomation Application Manager. It is displayed in a Web browser that connectsto the WebSphere Application Server on which the operations console is running.The Web browser may run on an arbitrary system.

Figure 4. WebSphere scenario - HA


The following minimum levels of Web browsers are supported:v Microsoft Internet Explorer V6.0 SP1v Mozilla V1.7.8v Firefox V1.5

For information on how the Web browser must be configured, refer to the IBMTivoli System Automation Application Manager Administrator’s and User’s Guide,section "Configuring your Web browser".

Hardware requirements: The following sections describe the hardwarerequirements for System Automation Application Manager for z/OS. Thedescription does not cover the hardware requirements that need to be satisfied forinstalling and running the required middleware software.

TCP/IP connectivity: System Automation Application Manager consists of variouscomponents that may run on one or several systems. For example:v When you use a local DB2 setup without Websphere Application Server the

automation manager, the operations console, and the DB2 server run on thesame system (single-node setup).

v When you use a remote DB2 setup, or a local DB2 setup with WebsphereApplication Server, System Automation Application Manager and the DB2 serverrun on separate systems (multi-node setup).

Be sure that TCP/IP connections can be established between the followingcomponents:v the WebSphere Application Server that is running the automation J2EE

framework, the resource adapters, and the operations consolev the DB2 server

Maximum number of server instances:: For System Automation Application Manageryou cannot run multiple WebSphere Application Server instances in parallel. Toverify the configuration, open the WebSphere administrative console and navigateto Servers > Application servers > server1. On the Configuration tab go to theServer Infrastructure area and select Java and Process Management > ServerInstance. Ensure that the checkbox ″Multiple Instances Enabled″ is not selected,and that the values for both ″Minimum Number of Instances″ and ″MaximumNumber of Instances″ are set to 1.

Disk space requirements: The installation disk space requirements for SystemAutomation Application Manager on z/OS systems are listed in the ProgramDirectory supplied with the installation tape. In addition several directories arecreated post-installation. The following table lists the disk space requirements forthese directories.

Table 21. Additional disk space requirements on z/OS systems


Installation directory of SystemAutomation Application Manager

/local/eezNote: This directory name can be chosen duringinstallation.

10 MB

Tivoli Common Directory /var/ibm/tivoli/common/ 300 MB

Configuration file directory of SystemAutomation Application Manager

/etc/eezNote: This directory name can be chosen duringinstallation.

10 MB


DB2 setup optionsWhen 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 forSystem Automation Application Manager. You have the following options:

Local DB2 setupThe DB2 server is installed and runs on the same node on which SystemAutomation Application Manager is installed.

Remote DB2 setupThe DB2 server is installed and runs on a node other than that on whichSystem Automation Application Manager is installed. In this case, youneed to install a DB2 JDBC driver on the System Automation ApplicationManager node.

Regardless of the DB2 setup option you use, perform the following actions:1. Make sure all stored procedures and tables for JDBC support are installed to

DB2 as described in the DB2 for z/OS Installation Guide. These stored proceduresand tables are usually installed during DB2 installation. If you have omitted toinstall them, you need to customize and run the DB2 installation JobDSNTIJMS.

2. Bind the DB2 packages that are used at the database server and grantEXECUTE authority on the packages to PUBLIC by using the DB2Binder utilityas described in the DB2 for z/OS Installation Guide.

Security conceptsThe following sections describe the security concepts for System AutomationApplication Manager.

Security considerations: In a local DB2 setup, in which System AutomationApplication Manager and the external components needed for running (WebSphereApplication Server and DB2) are installed on the same system, you do not need tosecure the connections between these components over SSL.

The external connections that will be established between the components listedbelow, however, should be secured over SSL, especially if the external componentsare running in different security domains that are separated by firewalls.

External connections will be established between the following components (thedefault port numbers are given in brackets):v The connection from the automation engine to the automation adapters (port

2001).v The connection from the automation adapters to the automation engine (port

2002). Note that SSL is not supported for this connection.v The connection between the Web browsers in which the operations console is

displayed and Integrated Solutions Console (HTTP port 9060, HTTPS port 9043).

User management: For information on how user IDs and passwords forend-to-end automation management are managed, refer to the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide, chapter "Managingusers".


Preparing for the installation of System AutomationApplication Manager

Collecting the information you need to provide duringinstallationOn z/OS the installation of System Automation Application Manager is driven byan Install Options file. You must add the installation and configuration parametersto the Install Options file using an editor. This file is then used by the installationprocess to propagate the parameters to the installation jobs. You are recommendedto save the original file.

The following tables list the parameters you can specify in the Install Options file.Parameters marked with ″Y″ in the column ″Req″ are required; the others areoptional. ″CR″ in this table means that this parameter is conditionally required ifsome other parameter is set to a specific value.

Installation directory: The parameters listed in the following table must alwaysbe specified.

Table 22. Installation directory and Tivoli Common Directory

Parameter Req Name Description Default

Installationdirectory prefix

EEZ_PREFIX_RUNTIME The high level qualifier of thedirectory to which the installablefeatures are installed. Theinstallation directory path(runtime path) will be generatedby using the contents of thisoption appended by a fixedproduct section ″/eez″.

This generated path name willbe used as the mount point foryour runtime HFS specified inthe optionJCL_NAME_RUNTIME_HFS. Usingthe default value will generate adefault runtime path of/local/eez.

In this guide, this directory isreferred to as EEZ_INSTALL_ROOT.

/local

SMP/EInstallationdirectory prefix

EEZ_PREFIX_SMPE Specify with this option theprefix which was used duringthe SMP/E installation of theproduct.

The SMP/E installation pathwill be generated by appendinga fixed product section″/usr/lpp/eez″ to the value ofthis option.

/

Target directory oflinks toapplicationmanagercommands

Y EEZ_PATH_BIN Location for symbolic links to allbinaries required by theApplication Manager. This mustbe a directory in the user's path.Example: /local/bin

none


Table 22. Installation directory and Tivoli Common Directory (continued)


Directory ofapplicationmanagerconfiguration files

EEZ_PREFIX_CONFIG Specify with this option theprefix used to create theconfiguration path structure ofthe product. The Configurationpath name will be generated byusing the contents of this optionEEZ_PREFIX_CONFIG appended bya fixed product section″/etc/eez″. This is the locationof product configuration andproperties files. Using thedefault value of optionEEZ_PREFIX_CONFIG will generatea default configuration path of/etc/eez.

/

AutomationManager HostName

Y EEZ_NAME_HOST Specify with this option thename of the system hosting theapplication manager.

Example:"tstsaam.boeblingen.de.ibm.com"

none

General installation parameters: These parameters can be used to tailor theinstallation on z/OS.

Table 23. General installation parameters


SBPXEXEC Prefix JCL_PREFIX_SBPXEXEC Use this option to specify theinstallation prefix of the z/OSsystem data set SBPXEXEC.

SYS1

Installation parameters for DB2: The parameters listed in the following tablemust be specified.

Table 24. DB2 data for local and remote DB2 setup


DB2 database name Y DB2_NAME_DATABASE Name of the database in the DB2universal data source profile. Usingthe DB2 administration utility this isthe value you find under thedescription ″DB2 location″

none




DB2 program name DB2_NAME_PROGRAM Name of the DB2 program toexecute SQL statements. DB2provides sample programs thatmany users find helpful asproductivity aids. These programsare shipped as source code, so youcan modify them to meet yourneeds. DSNTIAD is a sample dynamicSQL program that is written inassembler language. With thisprogram, you can execute any SQLstatement that can be executeddynamically except a SELECTstatement. For more information seeDB2 Universal Database for z/OSUtility Guide and Reference.

DSNTIAD

DB2 plan name CR DB2_NAME_PLAN Name of the DB2 plan. Thisparameter is required ifDB2_OPTN_UDB=ZOSUDBxx

none

DB2 storage groupname

DB2_NAME_STOGROUP Name of a storage group on thecurrent server to allocate tablespaces and index spaces fromidentified volumes.

EEZGROUP

DB2 dataset qualifier CR DB2_NAME_VCAT Identifies the integrated catalogfacility catalog for the storage group.You must define an alias if the nameof the integrated catalog facilitycatalog is longer than 8 characters.Select a value forDB2_NAME_VCAT that is not usedby other DB2 subsystems. Using theDB2 administrative Utility you canfind a list of VCAT values if youselect option DB2 system catalog,then option Storage groups. Thisparameter is required ifDB2_OPTN_UDB=ZOSUDBxx.

Example: "DSN821"

none

DB2 volume name DB2_NAME_VOLUMES Defines the volumes to create a DB2storage group.

(’*’)

DB2 buffer poolname

CR DB2_NAME_BUFFERPOOL This parameter is required ifDB2_OPTN_UDB=ZOSUDBxx.

Example: "BP2"

none




DB2 steplib CR DB2_DSN_STEPLIB Use this option to specify the MVSload library of the DB2 SQLinterface program DSNTIAD. Thisparameter is only required if yourDB2 is running on a z/OS System(Option DB2_OPTN_UDB=ZOSUDBxx),and the program could not befetched from the LINKLISTconcatenation. Specify either thedata set name of the steplib or thekeyword LLA.

Example: "SYS1.V810.SDSNLOAD"

none

DB2 UDB directory Y DB2_PATH_INSTALL The installation location of the DB2client directory.

If you are using a local DB2 setup,use the DB2 client that is part of theDB2 server installation. In this caseyou must specify the DB2 serverdirectory.

Example: "/local/db2/db2v8/jcc/classes"

none

DB2 instance hostname

Y DB2_NAME_HOST The host name of the DB2 instancein which the automation managerand operations console databases arelocated.

Example:"tstsaam.boeblingen.de.ibm.com"

none

DB2 instance portnumber

Y DB2_PORT_NUMBER The port number of the DB2instance in which the automationmanager and operations consoledatabases are located. Using the DB2administrative utility this is thevalue you find with description″IP-Port″.

Example: "5130"

none




Database instanceowner name

Y DB2_USER_INSTANCE The instance owner user ID of theDB2 instance in which theautomation manager and operationsconsole databases are located.

In a local DB2 setup, this user IDwill be used for creating thedatabases and tables.

In a remote DB2 setup, the databaseand the tables must have alreadybeen created. The installationprogram makes no change to DB2and creates neither a database nortables.

This user ID will be used byWebSphere Application Server toconnect to the automation managerand operations console databasesand to select, insert, delete andupdate rows in tables.

none

Database instanceowner password

Y DB2_PWRD_INSTANCE The password for the instanceowner user ID of the DB2 instancein which the automation managerand operations console databases arelocated.

none

DB2 Subsystem ID CR DB2_NAME_DSN_SYSTEM Using the DB2 administrative utilitythis is the value of your chosen DB2subsystem ID (SSID).

The parameter is required ifDB2_OPTN_UDB=ZOSUDBxx.

Example: "SDT1"




Automation managerdatabase

DB2_NAME_EAUTODB Automation manager database foruse by WebSphere ApplicationServer.

In a local DB2 setup, a databasewith this name will be created in theDB2 instance related to the specifiedinstance owner.

In a remote DB2 setup, a databasewith this name must already exist inthe remote DB2 instance.

EAUTODB

If an automationmanager database(EAUTODB) froman earlierinstallationalready exists, thedatabase will bedropped withoutwarning duringthe installation ofSystemAutomationApplicationManager. Topreserve the datafrom the earlierinstallation, youcan export thedata beforestarting theinstallation andimport it duringthe installation.For informationon exporting thedata from thedatabase, seeAppendix B,“Preserving userdata during theupgrade fromIBM Tivoli SystemAutomation forMultiplatforms2.x to SystemAutomationApplicationManager 3.1,” onpage 197.

Backend version Y DB2_OPTN_UDB Version of the back end DB2:

v ZOSUDB81: DB2 UDB V8.1 -running on z/OS

v ZOSUDB91: DB2 UDB V9.1 -running on z/OS

v DIST: DB2 UDB - running ondistributed system

none

WebSphere Application Server installation parameters: Note that WebSphereApplication Server security must be enabled before you install System AutomationApplication Manager.


Table 25. WebSphere Application Server (WAS) installation parameters


WAS topology Y WAS_TYPE_SETUP Specify the WAS topology you have choosen toinstall the automation manager. Use the keywordBASE for an unmanaged application server setup.Note: Only BASE is supported in the currentrelease.

none

WAS securitysetup

Y WAS_TYPE_SECURITY Specify the current realm definition of the WASUser account repository. You can specify eitherLOCAL, LDAP, FEDERATED or CUSTOM. It ispossible to check the current setting by using theWebSphere Administrative Console andnavigating to Security -> Securityadministration, application andinfrastructure -> current realm definition.

Example: "LOCAL"

none

WASconfigurationgroup

Y WAS_GROUP_CONFIG Specify the RACF group name of your WebSphereconfiguration group.

Example: "WSCFG1"

none

WASadministrationwith surrogate

Y WAS_OPTN_SURROGAT This option specifies how to run the SystemAutomation Application Manager installationjobs. Most of these jobs use the wsadmin.sh script.Depending on your WebSphere environment, youmay prefer to run the installation jobs using userwsadmin granted with SAF Class SURROGATauthorization (BPX.SRV.user). With WAS 6.1 orlater there is no longer a need for the userWSADMIN. You can install the product from auser ID which has accepted the CA Certificate ora user ID within the WAS Key Ring. Specify thevalue ″true″ to use SAF SURROGAT authorizationto use switch user (su), or ″false″ not to use the sucommand.

none

Cell name Y WAS_NAME_CELL The WAS cell to be used for the automationmanager.

Example: "csaam"

none

Certificatename

Y WAS_NAME_CERTIFICATE Specify the name of the WebSphere self-signedCA certificate. This name was specified duringthe WebSphere configuration.

Example: "WebSphereCA"

none

Keyring Y WAS_NAME_KEYRING The name of the WAS keyring as defined duringinstallation

Example: "WASKeyring.NSAAM"

none

Node name Y WAS_NAME_NODE_E2E The WAS node to be used for the automationmanager.

Example: "nsaam"

none

Profile name WAS_NAME_PROFILE The WAS profile to be used for the automationmanager and the operations console.

default

Server name WAS_NAME_SERVER The WAS server to be used for the automationmanager.

server1


Table 25. WebSphere Application Server (WAS) installation parameters (continued)


Installationdirectory

Y WAS_PATH_INSTALL The installation location of WAS.

Example: "/local/WebSphere/V6R1/AP/AppServer"

none

Bootstrap port WAS_PORT_BOOTSTRAP The port of the WAS server to be used asbootstrap for the automation manager.

2809

Administratoruser ID

Y WAS_USER_ADMIN The user ID of the WAS administrator. none

Administratoruser password

Y WAS_PWRD_ADMIN The password of the WAS administrator user ID. none

RACF user ID creation data: The parameters listed in following table are requiredto create various user IDs and groups with RACF. You can specify new or existinguser and group IDs here. Later on you will create sample jobs you can submit tocreate the new user and group IDs as well as other related security attributes. Ifthe job contains definition which are already known to RACF (like users orgroups) then these statements must be removed from the job in order to avoiderrors. In any case you need to verify the RACF definitions that are generatedbefore submitting the job.

The specification of existing user and group IDs is required because thisinformation is referenced by various other jobs.

The following RACF parameters correspond to the groups that are listed, asdescribed in the chapter “Managing users” in IBM Tivoli System AutomationApplication Manager Administrator’s and User’s Guide.

RACF parameter Group

RACF_GROUP_ADMIN EEZAdministratorGroup

RACF_GROUP_CONFIG EEZConfiguratorGroup

RACF_GROUP_OPERATOR EEZOperatorGroup

RACF_GROUP_MONITOR EEZMonitorGroupand

RACF_GROUP_ACCESS EEZEndToEndAccessGroup

Table 26. Installation parameters for RACF user and groups


RACF owner ofresources

Y RACF_OWNER_RESOURCES RACF group name or user name which will beused as resource Owner of resources belongingto System Automation Application Manager.This name could be any existing RACF groupor RACF user defined in your securityenvironment.

Example: GEEZ

none


Table 26. Installation parameters for RACF user and groups (continued)


RACF owner ofgroups

Y RACF_OWNER_GROUPS RACF group name or user name which will beused as the owner of groups belonging toSystem Automation Application Manager. Thisname could be any existing RACF group orRACF user defined in your securityenvironment.

Example: GEEZ

none

RACF superiorgroup name

Y RACF_GROUP_SUPERIOR RACF group name which will be used assuperior group defining the required RACFgroups of System Automation ApplicationManager. This group name must be an existingRACF group defined in your securityenvironment.

Example: GEEZ

none

RACF SAApplicationManager admingroup

Y RACF_GROUP_ADMIN RACF group name of System AutomationApplication Manager ADMINISTRATOR group.

Example: "GEEZADM"

none

RACF SAApplicationManager admingroup OGID

Y RACF_GROUP_ADMIN_OGID RACF group name of System AutomationApplication Manager ADMINISTRATOR groupunique OMVS group ID.

Example: "9501"

none

RACF SAApplicationManagerconfiguratorgroup

Y RACF_GROUP_CONFIG RACF group name of System AutomationApplication Manager CONFIGURATOR group.

Example: "GEEZCONF"

none

RACF SAApplicationManagerconfiguratorgroup OGID

Y RACF_GROUP_CONFIG_OGID RACF group name of System AutomationApplication Manager CONFIGURATOR groupunique OMVS group ID.

Example: "9502"

none

RACF SAApplicationManageroperator group

Y RACF_GROUP_OPERATOR RACF group name of System AutomationApplication Manager OPERATOR group.

Example: "GEEZOPER"

none

RACF SAApplicationManageroperator groupOGID

Y RACF_GROUP_OPERATOR_OGID RACF group name of System AutomationApplication Manager OPERATOR group uniqueOMVS group ID.

Example: "9503"

none

RACF SAApplicationManagermonitor group

Y RACF_GROUP_MONITOR RACF group name of System AutomationApplication Manager MONITOR group.

Example: "GEEZMON"

none

RACF SAApplicationManagermonitor groupOGID

Y RACF_GROUP_MONITOR_OGID RACF group name of System AutomationApplication Manager MONITOR group uniqueOMVS group ID.

Example: "9504"

none


Table 26. Installation parameters for RACF user and groups (continued)


RACF SAApplicationManager accessgroup

Y RACF_GROUP_ACCESS RACF group name of System AutomationApplication Manager ACCESS group.

Example: "GEEZE2E"

none

RACF SAApplicationManager accessgroup OGID

Y RACF_GROUP_ACCESS_OGID RACF group name of System AutomationApplication Manager ACCESS group uniqueOMVS group ID.

Example: "9505"

none

RACF SAApplicationManager usergroup

Y RACF_GROUP_USERS RACF group name of System AutomationApplication Manager USERS group.

Example: "GEEZUSER"

none

RACF SAApplicationManager usergroup OGID

Y RACF_GROUP_USERS_OGID RACF group name of System AutomationApplication Manager USERS group uniqueOMVS group ID.

Example: "9510"

none

RACF groupname of productSystemAutomationApplicationManager

Y EEZ_OWNER_GROUP This group will be used during the installationof System Automation Application Manager asthe group owner of all created paths and files.

Example: "GEEZOWN"

none

RACF groupname of productSystemAutomationApplicationManager OGID

Y EEZ_OWNER_GROUP_OGID OGID to be used for EEZ_OWNER_GROUP.

Example: "9500"

none

RACFinstallation ID

Y RACF_USER_INSTALL Name of a RACF user ID or a RACF group.The product will be installed under the controlof this installation ID. Normally this is yourown user ID, an installation user ID for thisproduct or a function group you are connectedto.

none

IBM Tivoli Enterprise Console connection configuration data: Optionally, youcan use Tivoli Enterprise Console for monitoring end-to-end automationmanagement events. The parameters listed in the following table are only requiredif you will use Tivoli Enterprise Console for end-to-end automation management.

Table 27. Installation parameters for IBM Tivoli Enterprise Console


TEC enableconnection

Y TEC_OPTN_ACTIVATE Specify the option for the TEC Server Connection.Specify ″true″ to enable this option or ″false″ todisable it.

none

TEC host name CR TEC_NAME_HOST The name of the host where the Tivoli EnterpriseConsole server is installed. This parameter isrequired when setting TEC_OPTN_ACTIVATE to "true".

Example: "tecsrv1"

none


Table 27. Installation parameters for IBM Tivoli Enterprise Console (continued)


TEC server portnumber

TEC_PORT_NUMBER The port number for the Tivoli Enterprise Consoleserver.

5529

For more information about utilizing Tivoli Enterprise Console for end-to-endautomation management, refer to the IBM Tivoli System Automation ApplicationManager Administrator’s and User’s Guide, chapter "Using Tivoli Enterprise Consolewith System Automation Application Manager"

IBM Tivoli Common Reporting configuration data: Tivoli Common Reporting isused by the SA Application Manager to create and visualize reporting data ofautomation actions.

Table 28. Installation parameters for IBM Tivoli Common Reporting


Tivoli CommonReportinginstallationoption

Y TCR_OPTN_INSTALL Specify this option to create the TCRinstallation jobs.Note: Only true is supported in the currentrelease.

none

Tivoli CommonReportingadmin group

Y TCR_GROUP_ADMIN Specify the group name of the reportingadministrator group. If your WAS user accountrepository is set to LOCAL this group is aRACF group.

Example: "GTCRADM"

none

Tivoli CommonReportingadmin groupOGID

Y TCR_GROUP_ADMIN_OGID Specify here the unique OMVS group ID forTCR_GROUP_ADMIN.

Example: "9520"

none

Tivoli CommonReportingviewer group

Y TCR_GROUP_VIEWER Specify the group name of the reportingviewer group. If your WAS user accountrepository is set to LOCAL this group is aRACF group.

Example: "GTCRVIEW"

none

Tivoli CommonReportingviewer groupOGID

Y TCR_GROUP_VIEWER_OGID Specify here the OGID for TCR_GROUP_VIEWER.

Example: "9521"

none

Configuration data for enabling communication with GDPS: Parameters in thissection are only required if you choose to install the Distributed Disaster Recoveryfeature. Even after specifying these options and running the generated jobs you arestill required to purchase and enroll the license to enable the Distributed DisasterRecovery feature.

Table 29. Installation parameters for GDPS interaction


GDPS installationoption

GDPS_OPTN_ACTIVATE Specify the option for the GDPS ServerConnection interaction. Use the value ’true’ toenable a GDPS connection; use ’false’ todisable it.

false


Table 29. Installation parameters for GDPS interaction (continued)


GDPS serverconnection

CR GDPS_NAME_HOST Specify the hostname for the GDPS K-Systemconnection. This is only required if youspecified GDPS_OPTN_ACTIVATE=true

Example: "boexdr1"

none

GDPS serverconnection port

GDPS_PORT_NUMBER Specify the port for connection to the GDPSK-System.

5529

GDPS backupserver connection

CR GDPS_OPTN_BKUP Specify the option for the backup GDPSserver connection. Use the value ″true″ toenable a GDPS backup connection; use ″false″to disable.

false

GDPS backupserver hostname

CR GDPS_NAME_HOST_BKUP Specify the hostname for the backup GDPSK-System connection. This is only required ifyou specified GDPS_OPTN_BKUP=true

none

GDPS backupserver connectionport

GDPS_PORT_NUMBER_BKUP Specify the port for connection to the GDPSBackup K-System.

5529

Name of the end-to-end automation domain:

Table 30. End-to-end automation domain name


Automationdomain name

E2E_NAME_DOMAIN The name of the end-to-end automation domainrepresented by this instance of the automationengine. The domain name must be unique and maynot be used for any other automation domain.

The characters used for the domain name arelimited to the following ASCII characters: A–Z, a–z,0–9, . (period), and _ (underscore).

FriendlyE2E

WebSphere Application Server user ID for the end-to-endautomation engineThe end-to-end automation engine requires a WebSphere Application Server userID to access the J2EE framework. The user ID is created during the installation ofSystem Automation Application Manager.

In the Install Options file you need to specify the user ID, the password, and theOMVS UID for this user.

Table 31. WebSphere Application Server user ID


User ID EEZ_USER_DAEMON WebSphere Application Server user ID for theend-to-end automation engine.

The automation engine will use the credentials foraccessing the J2EE framework that runs inWebSphere Application Server.

EEZDMN

Password Y EEZ_PWRD_DAEMON Password of the user ID none

OMVS UID Y EEZ_USER_DAEMON_OUID OMVS UID for this user ID 9402


System Automation administrator user IDDuring the installation of System Automation Application Manager, the initialTivoli System Automation administrator user is created in WebSphere ApplicationServer and authorized for all tasks and actions that can be performed from theSystem Automation operations console. In the Install Options file you need tospecify the data listed in the following table:

Table 32. System Automation administrator user ID


User ID EEZ_USER_ADMIN User ID of the System Automation operationsconsole administrator

EEZADMIN

Password Y EEZ_PWRD_ADMIN Password of the user ID none

OMVS UID Y EEZ_USER_ADMIN_OUID OMVS UID for this user ID 9401

Job control statementsSpecify the job control statements to run the post installation jobs.

The options JCL_JOBCARD_1, JCL_JOBCARD_2 and JCL_JOBCARD_3 are used tocreate a job card valid for execution on your post installation driving system. Theother options control job processing. The values entered for all options mustadhere to MVS JCL conventions.


Table 33. Job control statements


Job Card no.1

Y JCL_JOBCARD_1 Use this option to define thefirst line of the job cardincluding the required JCL JOBstatement. Within this line youcan specify a valid jobname andaccounting information.

If you want to define a staticjob card for each of theinstallation jobs use syntax 1below. If you want to define avariable jobcard containingparts of the submitted membername in the jobname you canuse syntax 2.

Syntax 1:

//job_name JOB 'account_info',

Example:

//SAAMINST JOB 'SAAM-Inst.',

Syntax 2://prefix<#s:e> JOB 'account_info',

where:

//prefix jobname prefix

<# starts the convention

s: starting offset ofsubmitted membername

e> ending offset ofsubmitted membername

Example:

//SAAM<#5:8> JOB 'SAAM-INST.',

if used with member ATVEI110would generate job nameSAAMI110.

none

Job Card no.2

JCL_JOBCARD_2 Use this option to define thesecond line of the job cardincluding the CLASS,MSGCLASS, and MSGLEVELparameters.

// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)


Table 33. Job control statements (continued)


Job Card no.3

JCL_JOBCARD_3 Use this option to define thethird line of the job cardincluding the NOTIFY andREGION parameters.Note: Most of the installationprograms require a region sizegreater than 128 MB. For thisreason the job region sizeshould always be defined withREGION=0M. Do not changethis value, as otherwise theprograms will end withunpredictable results.

// REGION=0M,NOTIFY=&SYSUID

JES controlstatement

JCL_JES_1 This parameter can be used tospecify JES2 or JES3 controlstatements.

Examples:

JES2: /*JOBPARM SYSAFF=xxxx

JES3: //*MAIN SYSTEM=xxxx

//*

JES node ofDB2 location

JCL_XEQ_DB2 This parameter can be used toidentify the network nodewhere the installation jobs forthe DB2 setup should be run.

Example: /*ROUTE XEQ=TSTSAAM

//*

Job commentline no. 1

JCL_COMMENT_1 Free for customer use.

Example://*-------------------------

//*



Example://* - Install SAAMz/OS V3.1 Date yy.mm.dd

//*



Example://*-------------------------

//*

Prefix ofSMPE datasets

Y JCL_PREFIX_SMPE Specify the prefix of the targetSMPE data sets used whilerunning the SMPE installationjobs.

Example:SAAM.V310

none


Table 33. Job control statements (continued)


Prefix ofSAAM workdata sets

Y JCL_PREFIX_WORK Specify a prefix which will beused to create temporary workdata sets required only duringthe installation process.

You are recommended to use adifferent value to that used inoption JCL_PREFIX_SMPE and thename of the runtime HFSspecified in optionJCL_NAME_RUNTIME_HFS.

Example:SAAM.WORK

none

Name ofSAAMruntime HFSdata set

Y JCL_NAME_RUNTIME_HFS Specify the name of the SAAMruntime HFS data set. This willbe allocated and mounted whenthe post installation jobs arerun.

This HFS data set is requiredfor the execution of SAAM. Youare recommended to updateyour parmlib member BPXPRMyyto automatically mount thisHFS during IPL. The mountpoint of this HFS will begenerated by appending a fixedproduct section to the value ofoption EEZ_PREFIX_RUNTIME and.

Example:SAAM.RUNTIME.HFS

none

Storage classname

Y JCL_STORCLAS_RUNTIME Specify the SMS storage classwhich will be used to createruntime data sets required forthe execution of the product.

Check this option with yourSMS storage administrator.

Example:SC#SAAM

none

ProclibName

Y JCL_PROCLIB_STC Specify a proclib in your proclibconcatenation to hold thesample started tasks.

Example:USER.PROCLIB

none

What the installation media containsSystem Automation Application Manager for z/OS is distributed on tape. Thecontents of the tape are listed in the Program Directory distributed with the tape.

Languages supported by System Automation ApplicationManagerIn addition to English, System Automation Application Manager supports thefollowing languages:v German


v Spanishv Frenchv Italianv Japanesev Koreanv Brazilian Portuguesev Simplified Chinesev Traditional Chinese

Installing System Automation Application Manager on z/OSThe preparation consists of the following steps:1. Create a work copy of the Install Options file.2. Edit the work copy of the Install Options file that defines the various

installation and customization settings. These settings are then used to updatethe installation jobs so that you do not need to modify these jobs yourself.

3. Create a work copy of sample job ATVEI100.4. Edit and submit the work copy of sample job ATVEI100. This job allocates the

INSTJCL data set and customizes the rest of the installation jobs.5. Submit the installation jobs created in step 4, in the order given in “Submit the

installation jobs” on page 60.

Note: The user ID under which these jobs are submitted must have UID 0.

Create a work copy of the Install Options fileThe Install Options file is supplied as member ATVDOPTS in the sample data setshipped with SMP/E DDDEF name TATVSAMP.

Create a work copy of Member ATVDOPTS into a data set that meets yourrequirements. For example, you can use the work data set created to run theSMP/E installation jobs. Do not change the SMP/E managed Member ATVDOPTSin the data set that belongs to the SMP/E DDDEF TATVSAMP.

Edit the work copy of the Install Options fileYou define various settings that vary from installation to installation in the InstallOptions file. Typical examples are ports used to communicate with the SAApplication manager, user IDs and passwords, installation path settings, DB2settings and so on. These settings are then propagated into the sample JCL streamsby the ATVRPREP REXX script. The Install Options file contains comprehensivedocumentation on the purpose of the parameters, their syntax and value range.

Note: The Install Options file contains the passwords in readable format. Thereforeaccess to this file should be restricted.

The following rules apply when coding the Install Options File.v An asterisk (*) or hash character (#) indicates a comment line.v Each install option is defined as a keyword=value pair. No comment can be

specified on the keyword=value line. There may be one or more blank charactersbefore and/or after the equals sign (=). Leading and trailing blanks will beremoved from the specified value, but embedded blanks will be preserved.

v If an option is specified more than once the first occurrence is the one used.v Continuation lines must be marked by blank and plus characters ( +) at the end

of the line. For example:


EEZ_PATH_PE=/local/WebSphere/V6R2/AP/AppServer +/systemApps/isclite.ear

As well as the install options described in “Collecting the information you need toprovide during installation” on page 18, some options exclusive to z/OS arerequired. Check the comments in the delivered Install Options file for details andfurther instructions.

Create a work copy of sample job ATVEI100Create a work copy of sample job ATVEI100 into a data set that meets yourrequirements. For example, you can use the work data set created to run theSMP/E installation jobs. Do not change the SMP/E managed Member ATVEI100 inthe data set that belongs to the SMP/E DDDEF TATVSAMP.

Edit and submit the work copy of sample job ATVEI100Edit the work copy of sample job ATVEI100 to update the job statements, andsubmit it. This job allocates the INSTJCL partitioned dataset to contain the JCLused for the various customization activities. It then copies the sample jobs intothis dataset and invokes the ATVRPREP script (via TSO batch invocation) toupdate the jobs with the specified installation options. The script validates thevarious parameters specified in the Install Options file and propagates the installoptions into the JCL, shell scripts and property files, preparing jobs to carry out thevarious customization steps.

Notes:

1. This job and all other jobs submitted during the installation should completewith a return code of 0 (zero). If any job completes with a return code otherthan 0 examine the output of the job for details. Jobs can generally beresubmitted after the error is corrected. Some jobs, however, cannot beresubmitted directly as changes made by them must be undone first. In thesecases auxilliary jobs are provided to back out the changes.

2. As well as the installation jobs, the INSTJCL library also contains jobs forapplying service and uninstalling the product, and should be retained for thesepurposes.

Edit and copy the sample procedures ATVEZDMN, ATVEZGPAand ATVEZHWACheck the comments in the headings of these procedures for any required changes.

These procedure must then be copied from the INSTJCL PDS into the PROCLIBconcatenation chain. Sample job ATVEH160 is provided for this purpose.

Submit the installation jobsThe generated jobs can be submitted without change. You may edit them ifrequired, for example to give them unique job names and to enable job chaining.

They should be submitted in the following order:1. ATVER100

This job sets up the necessary security definitions.

Notes:

a. Before rerunning this job run sample job ATVER10C to undo thedefinitions set up in the previous job.

b. The user ID this job is submitted under requires special RACF securityauthority. This job executes the security commands required for SystemAutomation Application Manager.


c. Review this job with your security administrator and, where required,modify the job before submitting. For example, if you have specified userIDs that are already authorized, remove the ADDUSER commands for theseusers from the job.

d. The commands in this job are written for RACF. If you use anothersecurity product these commands must be translated into the appropriatesyntax for your product before submitting.

2. ATVER110

This job sets up the necessary security definitions.It is intended to define function groups, connect users to the function groups,and define EJBROLE resources in the IBM Security Server RACF.

Notes:

a. This job is only required to run if your WAS user account repository is setto the local operating system. Otherwise the first step will end with areturn code of 04 and all the following steps will be flushed.

b. Before rerunning this job run sample job ATVER11C to undo thedefinitions set up in the previous job.

c. The user ID this job is submitted under requires special security authority.This job executes the security commands required for System AutomationApplication Manager.

d. Review this job with your security administrator and, where required,modify the job before submitting. For example, if you have specified userIDs that are already authorized, remove the ADDUSER commands for theseusers from the job.

e. The commands in this job are written for RACF. If you use anothersecurity product these commands must be translated into the appropriatesyntax for your product before submitting.

f. To activate the new defined EJBROLE resources WebSphere ApplicationServer must be recycled.

3. ATVED100

This creates the necessary DB2 table space and associated tables. The jobcreates the tables listed in Table 11 on page 15, and the associated indexentries.

Notes:

a. This step is not required if you are using a remote DB2.b. Make sure that DB2 is active before submitting the job ATVED100c. Before rerunning this job run job ATVED10C to cleanup the table space

and tables defined by the previous run.d. The user ID under which this job is submitted must have DB2 SYSADM

authority.4. ATVEH160

This copies the PROCLIB members into the installation PROCLIB.5. ATVEI110

This job:v creates the various configuration directories,v creates runtime HFS and customized script files,v creates the symbolic links,v sets the file owner, group owner and permission flags, andv creates the TIVOLI_COMMON_DIRECTORY if this does not already exist.


6. ATVEH180

This checks that WebSphere is properly set up and that the ISC component isinstalled.

7. ATVEW100

This deploys and configures the Common Event Infrastructure (CEI).

Note: If the CEI is already deployed, do not deploy it again. Furthermore, donot disable event persistence in this case.

8. ATVEW120

This installs the JMS provider.9. ATVEW130

This sets up the SA Application Manager .baroc and –load_classes files.10. ATVEW140

This configures the JDBC.11. ATVEW150

This sets up the default messaging.12. ATVEW160

This sets up Naming and WAS configuration.13. ATVEW170

This sets up the J2C connections and connection factories.

Note: Before the next step the server on which End-to-End Automation is tobe installed must be started. (In a Network Deployment environmentthis is not the same as the WebSphere Application Server administrationserver.)

14. ATVEA100

This job:v deploys the System Automation Application Manager EJBs,v deploys the System Automation Application Manager Operations Console,v deploys the Policy editor,v defines the System Automation Application Manager role mappings, andv sets the group ownership of files.

Note: Use sample job ATVEH120 to check if the System AutomationApplication Manager was successfully deployed. Then log on to theWAS administrative UI to verify the status. If the application EEZEARhas started successfully there is a green arrow at the right of the entrywhich corresponds to the application. If there is a red 'X' behind theapplication EEZEAR the application has not yet started.

Check that the System Automation Application Manager IntegrationModule was successfully deployed by starting application EEZIMEAR.Use sample job "ATVEH170" to do this. Then go to the administrativeUI to verify the status. If the application EEZIMEAR has startedsuccessfully there is a green arrow at the right of the entry whichcorresponds to the application. If there is a red 'X' behind theapplication EEZIMEAR the application has not yet started.

15. ATVEA140

This installs the System Automation Application Manager licenses.16. ATVEA150


This deploys System Automation Application Manager for DistributedDisaster Recovery.

17. ATVET100

This job:v prepares the TCR installation,v creates the TCR directories, andv sets the file owner, group owner, and other attributes.

18. ATVET110

This job:v deploys the TCR application in WebSphere,v creates the required shared libraries for TCR,v starts the TCR application,v sets up the TCR internal JNDI datasource for the TCR cloudscape database,

andv adds the TCR install location as a WebSphere JVM property.

Note: After this step WebSphere Application Server must be recycled.19. ATVET140

This imports the System Automation Application Manager reports.

Verifying the installation

Verify the automation managerTo verify that the automation manager was installed successfully, complete thetasks described in the following sections.

Verify the end-to-end automation databasePerform these steps to verify that the end-to-end automation database and thedatabase tables were created successfully on AIX, Linux or Windows:1. Ensure that DB2 is running.2. Open the DB2 Control Center.3. Navigate to Databases and expand the folder.4. Expand EAUTODB.5. Click Tables. The tables listed in Table 11 on page 15 should be shown.

Perform these steps to verify that the end-to-end automation database and thedatabase tables were created successfully on z/OS:1. Ensure that DB2 is running.2. Invoke the DB2 Administration Tool from within TSO.3. Select the DB2 that is hosting the SA Application Manager tables.4. Invoke the DB2 System Catalog function (option 1)5. Navigate to Databases (option D).6. Select EAUTODB (or whatever name you have chosen) and specify option T.7. The tables listed in Table 11 on page 15 should be shown.

Verify the automation J2EE FrameworkPerform these steps to verify that the automation J2EE framework was installedsuccessfully on AIX, Linux, Windows or z/OS:


1. In a Web browser window, specify the following address to display the Loginpanel of Integrated Solutions Console:http://<your_host_name>:<your_isc_port>/ibm/console

The default ISC port is 9060.2. On the login panel, enter the user ID and password of the WebSphere

Application Server administrator user.3. Navigate to Applications > Enterprise Applications. The list of installed

applications must contain the entry EEZEAR.

Verify that DB2 accepts WebSphere Application Server requestsPerform the following task to verify that DB2 accepts WebSphere ApplicationServer requests:1. In a Web browser window, specify the following address to display the Login

panel of Integrated Solutions Console:http://<your_host_name>:<your_isc_port>/ibm/console

The default port is 9060.2. On the login panel, enter the user ID and password of the WebSphere

Application Server administrator user.3. Navigate to Resources > JDBC > Data sources > EAUTODBDS. Click Test

connection to verify that DB2 accepts WebSphere Application Server 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 iscorrect (for more information, refer to the "Troubleshooting" appendix in theIBM Tivoli System Automation Application Manager Administrator’s and User’sGuide, section ″WebSphere Application Server cannot connect to DB2″.

Verify the automation enginePerform these steps to verify that the automation engine was installed successfully:1. If you are using a z/OS system, log in to USS on the system on which the

automation manager is installed with the user ID authorized for this purpose(the default is eezdmn).

2. Issue the command eezdmn -help. If the installation of the automation enginehas been successful the list of available command options is displayed.

Note: You can also use any of the other eezdmn command options to verifythe installation of the automation engine. As long as you do not receivean exception, any message you receive verifies that the automationengine is installed correctly. For a complete list of the eezdmn commandoptions, refer to the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide, chapter "Using the command-lineinterface of the automation engine".

Verify the operations consolePerform the following steps to verify that the operations console was installedsuccessfully:1. In a Web browser window, specify the following address to display the Login

panel of the Integrated Solutions Console:http://<your_host_name>:<your_isc_port>/ibm/console


The default ISC port is 9060.2. On this panel enter the System Automation administrator user ID. The default

user ID is eezadmin. Click Log in.

3. On the Welcome page of Integrated Solutions Console, click the entry for TivoliSystem Automation Application Manager.

4. When the Welcome page of System Automation Application Manager isdisplayed, the installation was successful.

5. Open the operations console.


Post-installation tasksWhen you have verified the installation of System Automation ApplicationManager, you need to perform a number of post-installation tasks:v You should create and authorize additional users as described in the IBM Tivoli

System Automation Application Manager Administrator’s and User’s Guide.v To get System Automation Application Manager operational, you must create

and activate an automation policy. This is described in the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide.– You must enable the end-to-end automation manager to access the first-level

automation domains referenced in the automation policy.To do this, you must specify the user credentials for the first-level domains onthe User credentials tab of the configuration dialog.“Invoking the end-to-end automation manager configuration dialog” on page73 describes how you launch the configuration dialog. For detailedinformation about the User credentials tab, refer to the online help of theconfiguration dialog.

Modify the Lightweight Third Party Authentication (LTPA)settings

After the installation of System Automation Application Manager, you shouldcheck whether the LTPA settings are appropriate for your environment.

During installation, the following LTPA parameters are automatically set inWebSphere Application Server:v LTPA Password is set to the password of the Integrated Solutions Console

administrator user IDv LTPA Timeout for forwarded credentials between servers is set to 120 minutes

LTPA Timeout is a security-related timeout. Because this timeout is absolute, auser will be logged out and forced to log in to Integrated Solutions Consoleagain when the LTPA timeout is reached even if the user is working with theoperations console at the time.

To change the LTPA settings (for example, password and timeout) you use theWebSphere Application Server administrative console. On the administrativeconsole, select Security > Secure administration, applications, and infrastructure> Authentication mechanisms and expiration.

Modify the HTTP session timeoutAfter the installation of System Automation Application Manager, you shouldcheck whether the setting of the HTTP session timeout is appropriate for yourenvironment.

The HTTP session time is an activity timeout. The value to which the HTTPsession timeout is set defines after how many minutes of inactivity a user is loggedout automatically.

During installation, the HTTP session timeout is set to 30 minutes.

To change the value, you use the WebSphere Application Server administrativeconsole.


On the administrative console, select Servers > Application servers > server1 >Container Settings > Session Management:

Configure the number of users who can connect to theautomation manager using the operations console

During the installation of System Automation Application Manager, a default value(30) is set that defines how many users can simultaneously connect to theautomation manager using the System Automation operations console. You canchange the current setting by changing the Maximum connections value for theEEZTopicConnectionFactory from Integrated Solutions Console (Resources >JMS >Topic connection factories > EEZTopicConnectionFactory > Connection pools).

If Maximum connections is set to 0, the number of concurrent connections that canbe established is allowed to grow infinitely. If the specified number of maximumconnections is reached, the next connection attempt using the operation consolewill bring up the following error message:EEZU0011E:Unable to set up the event path between the operations consoleand the management server:CWSIAD005E: The JCA runtime failed to allocate a connection.

Modify the Windows Firewall Security RulesThis task is only necessary when you have installed System AutomationApplication Manager on Windows Server 2008.

After the installation of System Automation Application Manager you must ensurethat inbound and outbound TCP traffic with the different Application Managercomponents is allowed. Ports for communication with the Integrated SolutionConsole, as well as ports to receive status change events from other automationdomains, must be opened in the Windows firewall with advanced security. It isassumed that you do not block the outbound connections to the other automationdomains.


The following ports have to be opened for inbound TCP traffic:

Table 34. Inbound TCP ports

Name Default Description

Event port number 2002 This is the port opened bythe automation engine inorder to receive (EIF-) eventsfrom other automationdomains.

This port is configured withcfgeezdmn.

ISC Port 9060 This is the port to which youdirect your Web browser inorder to open the SAoperations console or theWebSphere Administrativeconsole.

This port can be configuredusing the WebSphereAdministration Console bychanging the value forWC_adminhost.

Secure ISC Port 9043 This is the port which isused to open an httpsconnection to the sameIntegrated Solution Console.

This port can be configuredusing the WebSphereAdministration Console bychanging the value forWC_adminhost_secure.

To correctly set up these firewall rules follow this procedure:v Open "Start -> Administrative Tools -> Windows Firewall with Advanced

Security".v Select "Windows Firewall with Advanced Security" in the tree view. Ensure that

"Outbound connections that do not match a rule are allowed" is set.v In the menu bar open "Action -> New Rule...".v Select "Custom" to create a new Custom rule and press "Next >".v Select "This program path" and browse for the program java.exe of the

WebSphere Application server profile you created for installation of the SAApplication Manager.For example: C:\Program Files\ibm\websphere\appserver1\java\bin\java.exe.

v Select the "Customize..." button and ensure that the radio button "Apply to allprograms and services" is selected. Select "OK" to close this dialog.

v Select "Next >" in the window where you specified the JVM to continue with thewizard.

v Specify "TCP" as protocol type and "Specific Ports" as local ports. In the fieldbelow enter the list of ports in Table 34 separated by commas. For example, ifyou are using the default ports, you must specify ″2002, 9060, 9043″.For "Remote Port" select "All Ports' in order not to block the outbound traffic.


Select "Next >".v Specify "Any IP address" for both local and remote IP addresses. Select "Next >".v Ensure that ″Allow the connection″ is selected on this wizard panel.

Select "Next >".v This rule should apply to all scopes: "Domain", "Private" and "Public".

Select "Next >".v Enter a name such as "SA Application Manager (TCP-In)". The optional

description may be used as an aide-memoire such as ″This allows connection tothe SA Application Manager Java virtual machines. It is required to use the ISCWeb based consoles and allows the automation engine to receive events from theautomation adapters running on other automation domains.″Select "Finish".


Chapter 3. Upgrading from IBM Tivoli System Automationrelease 2.x

To upgrade from release 2.1 or 2.2 of IBM Tivoli System Automation to release 3.1of System Automation Application Manager, release 2.1 or 2.2 must be uninstalledand release 3.1 installed. This implies that in order to preserve data, someadditional steps have to be performed.

Although you do not need to uninstall release 2.3 of IBM Tivoli SystemAutomation before upgrading to release 3.1 of System Automation ApplicationManager, it is still needed to perform some additional steps in order to preservedata.

To preserve the data from the earlier installation, export the data before startingthe update installation, and import it after the installation of release 3.1. Forinformation on exporting the data, see Appendix B, “Preserving user data duringthe upgrade from IBM Tivoli System Automation for Multiplatforms 2.x to SystemAutomation Application Manager 3.1,” on page 197.

If you have configured WebSphere Application Server to use a security product inread-only mode so that the WebSphere administrative interfaces to manage usersand groups cannot be used, perform the following tasks before you upgrade:1. Modify the functional user ID that is used by the end-to-end automation engine

for accessing the WebSphere Application Server (default user ID name: eezdmn )such that it is no longer a member of the user group that is associated with theuser role EEZOperator (default group name: EEZOperatorGroup). Instead, it mustbecome a member of the user group that is associated with the user roleEEZAdministrator (default group name: EEZAdministratorGroup).

2. System Automation Application Manager 3.1 integrates with IBM TivoliCommon Reporting (TCR). The TCR component defines two user roles andcreates by default two associated user groups during installation. Create usergroups that are associated with the following roles, and include user IDs tothose groups as needed:a. User role reportAdministrator (by default, TCR maps this role to user

group reportAdministrator)b. User role reportViewer (by default, TCR maps this role to user group

reportViewer)3. Before you start the upgrade installation to System Automation Application

Manager 3.1, temporarily enable the WebSphere administrative interfaces tomanage users and groups. Refer to “Appendix: Considerations about user andgroup management in WebSphere Application Server” for more information.Once the upgrade installation has been completed, you may again disable theWebSphere administrative interfaces to manage users and groups.

If you configured the end-to-end component of SA for Multiplatforms 2.3 to sendend-to-end automation events to the Tivoli Enterprise Console (TEC), then start theend-to-end automation configuration tool (cfgeezdmn) and enable the checkboxEnable TEC event generation after you upgraded to System AutomationApplication Manager 3.1.


||||

||||

|||||

|||

||||||

|||||

||

||

||||||

Upgrading the MSCS adapterTo upgrade an installation including highly available MSCS adapter resources fromrelease 2.3 to release 3.1, you must reconfigure these in the Cluster Administratoras this service has been renamed from ″SA MP MSCS Adapter″ to ″SA AM MSCSAdapter″ in version 3.1.


Chapter 4. Configuring the end-to-end automation manager

This chapter provides an overview of how you use the end-to-end automationmanager configuration dialog to perform the following tasks:v Change the basic configuration of the end-to-end automation manager (see

“End-to-end automation manager basic configuration” on page 75).v Configure high availability for the end-to-end automation manager (see

“Configuring high availability for the end-to-end automation manager” on page89).

Note: You need an X11 server to use the end-to-end automation managerconfiguration dialog. You can also configure the end-to-end automationmanager in silent mode using an input properties file. The configurationdialog is not available on z/OS so the silent configuration is the onlysupported method on this system. See “Invoking silent configuration” onpage 103 for more details.

Invoking the end-to-end automation manager configuration dialogBefore you begin:

The user ID you use to invoke the dialog must meet the following requirements:v The user ID must be in same group as the user ID you used for installing

System Automation Application Manager. On z/OS this is user eezadmin.Thegroup permissions for the cfgeezdmn script must be set to EXECUTE.

v The user ID must have write access to the following directory:– Windows: <EEZ_INSTALL_ROOT>/cfg– AIX, Linux, z/OS: /etc/<EEZ_INSTALL_ROOT>/cfg

Perform the following step to invoke the configuration dialog:1. Log in on the system where System Automation Application Manager is

installed._________________________________________________________________

2. Enter the following command:cfgeezdmn

The configuration dialog task launcher is displayed (see “Using the tasklauncher”)._________________________________________________________________

Using the task launcherThe task launcher appears when you invoke the configuration dialog as describedin “Invoking the end-to-end automation manager configuration dialog.”


�1� Basic configurationClick Configure to open the end-to-end automation manager configurationdialog. On the dialog tabs, you specify basic configuration parameters. Formore information, see “End-to-end automation manager basicconfiguration” on page 75.

�2� Hardware adapter configurationClick Configure to open the System Automation Application Managerhardware adapter configuration dialog. Use this dialog to configure thehardware adapter host and the hardware access credentials that thehardware adapter uses. For more information, see “Configuring theend-to-end hardware adapter” on page 84.

Note: This option is only enabled if the Distributed Disaster Recoveryfeature is installed on supported platforms.

�3� High-availability configurationYou perform the tasks in this section to provide high availability for theend-to-end automation manager. You activate the task buttons by selectingEnable the high availability configuration tasks.

Note that on Windows and z/OS operating systems, high-availabilityconfiguration is not supported and all tasks are disabled.

For more information, see “Configuring high availability for the end-to-endautomation manager” on page 89.

Displaying online helpThe following sections provide an overview of the end-to-end automation managerconfiguration tasks. More detailed information is available in the online help. Tolaunch the online help, click Help on a dialog tab:


End-to-end automation manager basic configurationThe initial configuration of the end-to-end automation manager is performedduring the installation of System Automation Application Manager. To browse orchange the properties you can use the end-to-end automation managerconfiguration dialog or silent configuration. You should never manually edit theconfiguration properties files in which the configuration parameters are stored.

The following sections describe the basic configuration tabs of the end-to-endautomation manager configuration dialog. To open the configuration dialog,perform these steps:1. Invoke the configuration dialog (see “Invoking the end-to-end automation

manager configuration dialog” on page 73).2. On the task launcher, click Configure in the "End-to-end automation manager

basic configuration" area. The basic configuration notebook appears (see“Domain tab” on page 76). The tabs of the notebook are described in thefollowing sections.

Post-configuration tasks:

After changing any of the configuration properties, you must perform thefollowing tasks:v Activate the new settings by reconfiguring the automation engine. To do so,

invoke the command eezdmn with the option -reconfig.For command details, see the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide, section "Using the command line interface of theautomation engine".

Chapter 4. Configuring the end-to-end automation manager 75

v If your end-to-end automation manager is configured for high availability, youmust replicate the configuration files to the other nodes of the IBM Tivoli SystemAutomation domain that provides the high availability.

v If you changed the hardware adapter configuration, you need to activate thenew settings by reconfiguring the hardware adapter. To do so, invoke thecommand eezhwadapter with the option -reconfig. For command details see theIBM Tivoli System Automation Application Manager Administrator’s and User’sGuide section ″Using the command-line interface of the hardware adapter″.

For a change in the domain name, host name, port numbers, or policy poollocation on the Domain tab to become effective, the automation engine must berestarted using the commands eezdmn -shutdown and eezdmn -start. If you areusing the Distributed Disaster Recovery feature, the hardware adapter must also berestarted using the commands eezhwadapter -stop and eezhwadapter -start.

Domain tabUse the tab to browse or change the configuration properties of the end-to-endautomation domain.

Use the following to configure the settings of the end-to-end automation domainand the host where the end-to-end automation manager is running:

Domain nameThe name of the end-to-end automation domain. The name in this fieldmust be the same as the XML element <AutomationDomainName> in each ofthe domain's automation policy files. Only the following ASCII characterscan be used for the domain name: A–Z, a–z, 0–9, . (period), and _(underscore).

Host name or IP addressName or IP address of the system that hosts the end-to-end automationmanager.


WAS bootstrap port numberThe bootstrap port of the WebSphere Application Server instance that hoststhe end-to-end automation manager.

Command line request port numberThe port on which the automation engine receives command-line interfacerequests.

Event port numberThe port on which the EIF message converter listens for events from thefirst-level automation domains. The port number specified here mustmatch the port number specified as event port number for the end-to-endautomation manager host when configuring automation adapters onfirst-level automation domains.

For SA for z/OS, this is the event port specified in the adapterconfiguration parameter eif-send-to-port in the adapter plug-inproperties file.

Enable report data collectionSelect this checkbox if you want to collect reporting data in the SystemAutomation Application Manager’s DB2 database.

Enable TEC event generationSelect this checkbox if you want the end-to-end-automation manager tosend events for the end-to-end automation domain to the Tivoli EnterpriseConsole.

Policy poolThe fully qualified name of the directory that contains the XMLautomation policy files for the end-to-end automation domain. Onlyautomation policy files that are available in this directory can be activated.

Note: For a change in the policy pool location to become effective, theautomation engine must be restarted using eezdmn -shutdown andeezdmn -start.


Command shell tab

The end-to-end automation manager requires authentication when a user invokesthe end-to-end automation manager command shell by entering the eezcscommand. By default, users are always prompted for their user credentials. On theCommand shell tab you have the choice between these authentication modes:

Read user credentials from stdinIn this mode, users must always specify their user credentials in the shellwindow.

Prompt for user authenticationIn this mode, users are always prompted for their credentials by an X11dialogue unless they specify them when they invoke the command shell.

Use specified user credentialsIn this mode, a shared user ID is used for authentication, which preventsusers from being prompted for their credentials when they invoke thecommand shell.

You specify the shared user ID and the corresponding password in thefields User ID and Password. Note that only the following ASCIIcharacters can be used for the user ID: A–Z, a–z, 0–9, and _ (underscore).

To change the password, click Change.

Discovery library adapter tabSystem Automation Application Manager provides a Discovery Library Adapter(DLA) to export the currently active System Automation Application Managerresource topology to an Identity Markup Lanugage (IdML) discovery book. Usethe tab to configure the location where the DLA stores IdML books.


IdML book directoryThe absolute path to the directory where the DLA should store IdMLbooks.

Local/remote directorySelect whether the IdML book directory is located on the computer wherethe DLA is running or on a remote system.

Local IdML book directoryThe IdML book directory is located on the computer where theDLA is running.

Remote IdML book directoryThe IdML book directory is located on a remote system.

HostnameThe hostname of the remote system where the IdML book directory islocated. This field is only enabled if you select the remote IdML bookdirectory radio button.

User IDThe logon user ID that is used by the DLA to store IdML books on theremote system. This field is only enabled if you select the remote IdMLbook directory radio button.

PasswordThe logon password that is used by the DLA to store IdML books on theremote system. This field and the Change button are only enabled if youselect the remote IdML book directory radio button.

Use the Change button to display a dialog that prompts you to specify andconfirm the password.

User credentials tabUse the User credentials tab to browse or change the user credentials of theend-to-end automation manager. The automation manager uses these credentials to


authenticate itself. The characters used for all credentials entered on this tab arelimited to the following ASCII characters: A–Z, a–z, 0–9, and _ (underscore).

Fields on the User credentials tab:

WAS access user IDThe user ID that is used to access the WebSphere Application Serverinstance that hosts the end-to-end automation manager.

WAS access user passwordThe password for the WAS access user ID. Click Change to change thepassword.

Generic user IDThe user ID the automation manager uses to authenticate itself to afirst-level automation domain when no credentials are specified for thedomain in Credentials for accessing specific first-level automationdomains.

Generic passwordThe password for the generic user ID. Click Change to change thepassword.

Credentials for accessing specific first-level automation domainsClick Add to specify a user ID that is valid for the domain. The user IDneed not be root but it should be authorized to perform operations onresources in the first-level automation domain that the end-to-endautomation manager supports, for example, bringing an automatedresource online. The Remove and Change buttons let you create andmodify the credentials for a first-level automation domain.

For more details, refer to the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide, section "How requests against resource referencesare processed".


Security tabUse the Security tab to browse and change the configuration properties for the SSLconnection to the first-level automation domains.

Fields on the Security tab:

TruststoreThe fully qualified file name of the truststore file that is used for SSL. Thetruststore path name must follow the same naming rules as the InstallationDirectory Name (see Table 22 on page 43). The file name may containmultiple period characters. Click Browse to select a file.

KeystoreThe fully qualified file name of the keystore file that is used for SSL. Thekeystore path name must follow the same naming rules as the InstallationDirectory Name (see Table 22 on page 43). The file name may containmultiple period characters. Click Browse to select a file.

Keystore passwordThe password of the keystore file. The password is required if a keystorefile was specified. Click Change to change the password.

Note: If the truststore is in a different file than the keystore, the passwordsfor the files must be identical.

Certificate aliasThe alias name of the certificate to be used by the server. The charactersused for the certificate alias are limited to the following ASCII characters:A–Z, a–z, 0–9, and _ (underscore).

Logger tabUse the Logger tab to specify the settings for logging, tracing, and First FailureData Capture. You can change the settings permanently or temporarily.


On the Logger tab, you can perform the following tasks:

Change the settings temporarilyPerform 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 theproperties file. If the automation engine is not running, you receive anerror message.

Note: Temporary changes are not supported in z/OS.

Change the settings permanentlyPerform these steps:1. Make the required changes on the tab.2. Click Save.

Results:

The settings in the properties file are updated. To change the settingsimmediately Click Apply and then Save

Revert to the permanent settingsIf you changed the settings temporarily, perform the following steps torevert to the permanent settings defined in the properties file, or when youare unsure which settings are currently active:1. Invoke the configuration dialog and open the Logger tab. The Logger

tab displays the values that are currently set in the properties file.2. Click Apply to activate the settings.


Results:The settings take effect immediately.

Controls and fields on the Logger tab:

Maximum log/trace file sizeThe file size in kilobytes.

Note: On z/OS only the trace file size is configurable. Themessage log file size is 1024 KB and can not be changed.

Message logging level:

Error Logs messages on the error level.

Warning Logs messages on the error and warning levels.

Information Logs messages on the error, warning and informational levels.

Trace logging level:

Off Collects no trace information.

Minimum Collects trace information on the error level.

Medium Collects trace information on the error and warning levels.

Maximum Provides the message and trace logs and collects additionalinformation on the error, warning, and informational level.

First failure data capture (FFDC) settings:v Recording level:

Off Collects no FFDC information.

Minimum Provides the message and trace logs and collects additionalinformation on the error level.

Medium Provides the message and trace logs and collects additionalinformation on the error and warning level.


v Disk space:

Maximum disk spaceSpecifies the maximum disk space in bytes used by FFDC traceswhich are written into the FFDC trace directory. The defaultspace is 10485760 byte (10MB).

Space exceeded policySelect what to do if the maximum disk space is exceeded.

v Message IDs:

Filter mode Initiates the tracing of FFDC data depending on the message IDslisted in Message ID list.

Message ID list:Specifies the message IDs which trigger the tracing of the FFDCdata. Wildcard characters can be used (for example, *E fortracing all error messages).


Saving the basic configurationTo save your changes to the end-to-end automation manager properties files, clickSave on the configuration dialog. Upon completion, the Configuration UpdateStatus window appears, showing the list of configuration files that were updated:

If you have configured high availability for the end-to-end automation manager,you must replicate the properties files to the other nodes in the IBM Tivoli SystemAutomation domain (see “Replicating the configuration files” on page 96).

Configuring the end-to-end hardware adapterNotes:

1. Configuration of the hardware adapter is only enabled if you have installed theDistributed Disaster Recovery feature of System Automation ApplicationManager, because this feature is a prerequisite for using the hardware adapter.

2. The Distributed Disaster Recovery feature (and thus also configuring it) isavailable only on z/OS and Linux on System z.

3. For more details see the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide.

Configuring the System Automation Application Manager hardware adapterconsists of the following:1. Configuring the hardware adapter host using the Adapter tab2. Configuring the hardware access credentials that are used by the hardware

adapter using the Credentials tab

After changing any of the configuration properties, you must perform thefollowing tasks:v Activate the new settings by reconfiguring the hardware adapter. To do so,

invoke the command eezhwadapter -reconfig. For command details, see theIBM Tivoli System Automation Application Manager Administrator’s and User’sGuide, section "Using the command line interface of the hardware adapter″.


v If your end-to-end automation manager is configured for high availability, youmust replicate the configuration files to the other nodes of the IBM Tivoli SystemAutomation domain that provides the high availability.

v For a change in the request port number on the Adapter tab to become effective,the hardware adapter must be restarted with commands eezhwadapter -stopand eezhwadapter -start.

Adapter tabUse this tab to configure the settings of the host where the hardware adapter isrunning. This is the same host system on which the Websphere Application Serverthat hosts the end-to-end automation manager is located. Thus you do not need toexplicitly specify a host name or IP address on this tab.

Field on the Adapter tab:

Request port numberThe number of the port to which the hardware adapter listens for requestsfrom the end-to-end management host. The default port is 2003.

Credentials tabUse this tab to configure the hardware access credentials that are used by theSystem Automation Application Manager hardware adapter.

The Credentials tab displays the following lists:

Hardware defined in disaster recovery policiesThis list shows all the hardware entities that are currently defined in thedisaster recovery policies that are stored in the policy pool.


Compare the hardware units in this list with the hardware units in thehardware access credentials list on the right of the tab. Make sure that thecredentials list contains at least one entry for each defined hardware unitin the list on the left.

Use the Refresh button to refresh the content of the list. If disasterrecovery policies have been added, removed or modified while you havebeen using the configuration dialog, the refresh action updates the recoverypolicy hardware list to its current status.

Configured hardware access credentialsThis list shows all the hardware entities for which you have currentlydefined credentials that are used by the hardware adapter to access thosehardware units.

A dash (″-″) in the Slot column indicates the hardware box itself.

Each hardware unit that is defined in a disaster recovery policy must alsobe specified in the credentials list. However, you may decide to explicitlyomit the actual credentials for selected hardware units. In this case theUser ID column remains empty.

Use the Add missing button to update the hardware access credentials listby adding entries for all hardware units that are defined in disasterrecovery policies, but do not yet have credentials defined for them.

Use the Add button to display the Add Hardware Access Credentialsdialog that lets you add a hardware unit with its credentials to the list ofhardware access credentials. For more details, see “Adding credentials.”

Use the Remove button to remove the selected hardware unit from the listof hardware access credentials. You should only remove hardware unitsthat are not defined in any disaster recovery policy.

Use the Change button to display the Change Hardware AccessCredentials dialog that lets you change the user ID and password for theselected hardware unit. For more details, see “Changing credentials” onpage 88.

Adding credentialsUse this dialog to define access credentials for hardware units that have not yetbeen defined in a disaster recovery 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.

Slot The name of the slot in the hardware box for which you want to definecredentials. If the hardware box does not contain any slots or you want todefine credentials just to access the box itself, leave this field empty.

User IDThe user ID that is used by the end-to-end hardware adapter to access thespecified hardware unit.

PasswordThe password that is used by the end-to-end hardware adapter to accessthe specified hardware unit.

Password confirmationIdentical to the value specified in the Password field. Used to confirmpassword correctness.

SNMP Privacy passwordIf the hardware adapter uses SNMP to communicate to a hardware box,you need to add a privacy password to the credentials for that hardwarebox if SNMP is set up with encrypted communication.

Do not specify an SNMP privacy password if you are defining credentialsfor a slot in a hardware box.

Privacy password confirmationIdentical to the value specified in the SNMP Privacy password field. Usedto confirm password correctness.

Because the definition of access credentials for hardware units is optional, you canleave the user ID and password fields empty. Even if you define access credentialsfor a hardware box that is accessed by the hardware adapter via SNMP, you canstill choose to omit the SNMP privacy password.


Clicking the OK button adds the hardware unit and the credentials that you havespecified to the hardware access credentials list on the Hardware AdapterConfiguration tab and closes this dialog.

Clicking the Cancel button closes this dialog without adding the specifiedhardware unit and credentials.

Changing credentialsUse this dialog to change the user ID and password for a selected hardware unit.The entry fields in this dialog are primed with the values of the selected hardwareunit. The name of the box and slot of the selected hardware unit are displayed inthe corresponding output fields.

Fields on the Change Hardware Access Credentials dialog that you can update:

User IDThe user ID that is used by the end-to-end hardware adapter to access theselected hardware unit.

PasswordThe password that is used by the end-to-end hardware adapter to accessthe selected hardware unit.

Password confirmationIdentical to the value specified in the Password field. Used to confirmpassword correctness.

SNMP Privacy passwordIf the hardware adapter uses SNMP to communicate to a hardware box,you need to add a privacy password to the credentials for that hardwarebox if SNMP is set up with encrypted communication.

Privacy password confirmationIdentical to the value specified in the SNMP Privacy password field. Usedto confirm password correctness.

Note: SNMP privacy passwords can only be specified for hardware boxes.Therefore the privacy password fields are not shown on this dialog if youare changing credentials for a slot in a hardware box.


Because the definition of access credentials for hardware units is optional, you canleave the user ID and password fields empty. Even if you define access credentialsfor a hardware box that is accessed by the hardware adapter via SNMP, you canstill choose to omit the SNMP privacy password.

Use the Clear credentials button to easily remove all specified credentials for theselected hardware unit.

Clicking the OK button changes the credentials for the hardware unit that youselected in the hardware access credentials list on the Credentials tab are changedand closes this dialog.

Clicking the Cancel button closes this dialog without changing the selectedhardware unit credentials.

Saving the hardware adapter configurationTo save your changes to the end-to-end automation manager properties files, clickSave on the Hardware Adapter Configuration tab. Upon completion, theConfiguration Update Status window appears, showing the list of configurationfiles that were updated.

If you have configured high availability for the end-to-end automation manager,you must replicate the properties files to the other nodes in the IBM Tivoli SystemAutomation domain (see “Replicating the configuration files” on page 96).

Activate the new settings by reconfiguring the hardware adapter. To do so, invokethe command eezhwadapter with the option -reconfig. For command details seethe IBM Tivoli System Automation Application Manager Administrator’s and User’sGuide, section "Using the command line interface of the hardware adapter″.

For a change in the request port number on the Adapter tab to become effective,the hardware adapter must be restarted with the commands eezhwadapter -stopand eezhwadapter -start.

Configuring high availability for the end-to-end automation managerFor the platforms on which high availability is possible see "High-availabilityconfiguration" under “Using the task launcher” on page 73.

Notes:

1. Requests to the end-to-end automation manager are lost when a failover isperformed, as these requests are not persistent.

2. Configuring high availability uses IBM Tivoli System Automation forMultiplatforms which must be installed on both nodes.

3. For the steps needed see the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide, section "Making System AutomationApplication Manager highly available″.

The following sections describe the high availability configuration tabs of theend-to-end automation manager configuration dialog.

Domain setup tabUse this tab to specify the parameters required for setting up the IBM TivoliSystem Automation domain which you are using to provide high availability forthe end-to-end automation manager. The specified parameters will be used to


create the IBM Tivoli System Automation domain in the Setup domain task.

Fields on the tab:

Domain nameThe name of the IBM Tivoli System Automation domain. To prime the fieldwith the currently defined domain name, click Query domain. The domainstatus (Online or Offline) is displayed to the right of the field.

Network tie breaker IP addressThe IP address that is used to set up a network tie breaker. Leave the fieldempty if you are setting up a three-node IBM Tivoli System Automationdomain or if you want to use a different type of tie breaker for a two-nodedomain. In this case, no network tie breaker will be defined.

To prime the field with the currently defined value, click Query domain.Note that when you use Query domain to fill this field, the first definedtiebreaker of type ″EXEC″ will be chosen

Node listThe table lists the nodes of the IBM Tivoli System Automation domain. Ifthe domain is online, clicking Query domain will populate the table withthe nodes that are online in the domain.

Table columns:

Defined nodeThe name of the node.

Automate on nodeIndicates whether the end-to-end automation manager is to beautomated on the node, in which case it will be included in theautomation policy.

Network interfaceThe name of the network interface on this node.

Possible actions on the tab:


Determining the sequence in which automation selects the node on which theend-to-end automation manager may run

You specify the preferred failover sequence by changing the position of thenodes in the list. To move a node to a different position, select the nodefrom the list and click Up or Down.

Adding, changing, and removing nodesTo change the list of nodes in the automation policy, use the correspondingbuttons:

Add Opens a window for specifying the settings for the node that is tobe added to the automation policy.

ChangeTo modify the settings for a node, select the node, click Change,and modify the settings in the windows that appears.

RemoveTo remove a node from the automation policy, select the node, andclick Remove.

Automation manager tabUse this tab to configure the resources that are used to automate the end-to-endautomation manager.

Fields on the tab:

Automated resources prefixThe prefix that precedes the names of the resources and groups in theend-to-end automation manager automation policy. The prefix is restrictedto ASCII characters.

If you have defined the current automation policy using the old prefixvalue, you must perform the following steps to change the prefix:1. Remove the current automation policy.2. Change the prefix on this tab.3. Define the automation policy again.

IP addressThe virtual IP address that is shared by all nodes in the IBM Tivoli SystemAutomation domain and that is set for the IBM.ServiceIP resource in the


end-to-end automation manager automation policy. The virtual IP addressmust be authorized by your network administrator. To prime the field withthe currently defined value, click Query domain.

NetmaskThe netmask address that is set for the IBM.ServiceIP resource in theend-to-end automation manager automation policy. Request the addressfrom your network administrator. To prime the field with the currentlydefined value, click Query domain.

Policy pool tabUse this tab to specify the parameters required for automating the file system thatholds the policy pool. The data is used to create the corresponding file systemresource in the automation policy. The policy pool must reside on a file system thatis shared by all nodes in the IBM Tivoli System Automation domain. When theautomation policy is active, it will be mounted at the specified mount point on thenode where the end-to-end automation manager is running.

Fields on the Policy pool tab:

File system typeThe type of the policy pool file system to be automated, for example, "jfs","jfsz", "ext2". To prime the field with the currently defined value, clickQuery domain.

Mount pointThe mount point of the policy pool file system. Click Browse to select adirectory. If the domain is online, you can click Query domain to primethe field with the currently defined value.

Device nameThe device name of the policy pool file system. Click Browse to select adevice. If the domain is online, you can click Query domain to prime thefield with the currently defined value.

WebSphere tabThe tab displays the parameters required for automating the instance ofWebSphere Application Server that hosts the end-to-end automation manager. The


data is used to create the corresponding resource in the automation policy. Theparameters are set by the installer at installation time. Usually, you will not have tochange any of the values.

Notes:

1. The installation parameters must be identical on all nodes of the IBM TivoliSystem Automation domain for the automation policy to work. For example,the path to the profile directory, the Application server port, and theApplication server name must be identical on all nodes.

2. To ensure that IBM Tivoli System Automation can stop WebSphere ApplicationServer, you must add the WebSphere administrator user ID and its password tothe WAS SOAP client properties file. The file is located at /<was_home>/profiles/AppSrv01/properties/soap.client.props.The corresponding entries in this file must look like this:com.ibm.SOAP.loginUserid=<WAS-admin>com.ibm.SOAP.loginPassword=<password>

You can encrypt this password within the properties file by using the WASPropFilePasswordEncoder utility. Input parameters for this utility are theproperties file path and the password identifier.Example:

/opt/IBM/WebSphere/AppServer1/profiles/AppSrv01/bin/PropFilePasswordEncoder.sh/opt/IBM/WebSphere/AppServer1/profiles/AppSrv01/properties/soap.client.props com.ibm.SOAP.loginPassword

Fields on the WebSphere tab:

Application server nameThe name of the WebSphere Application Server instance that hosts theend-to-end automation manager.

Application server portThe number of the WebSphere Application Server port that is used by theend-to-end automation manager.

Profile directoryThe directory in which the WebSphere Application Server profile forSystem Automation Application Manager is located. Click Browse tonavigate to the directory. Click Browse to select a directory.


DB2 tabThe tab displays the parameters used for automating the DB2 instance that hoststhe System Automation Application Manager database (EAUTODB). Theparameters are set by the installer at installation time. Usually, you will not have tochange any of the values.

Note that the installation parameters must be identical on all nodes of the IBMTivoli System Automation domain for the automation policy to work. For example,the installation directory, the instance owner user ID, and the instance ownermount point must be identical on all nodes.

Controls on the DB2 tab:

Automate DB2Select the check box to enable the entry fields on the tab.

Installation directorySpecify the DB2 installation directory or click Browse to select a directory.

Instance owner user IDType the user ID of the owner of the DB2 instance that hosts theEAUTODB database.

Instance owner mount pointType the mount point of the DB2 instance that hosts the EAUTODBdatabase or click Browse to select a directory.

Hardware adapter tabThis tab indicates whether a resource for the hardware adapter will be included inthe end-to-end automation manager automation policy that makes the hardwareadapter highly available.

A resource for the hardware adapter will only be included in the automationpolicy if you have installed the Distributed Disaster Recovery feature of SystemAutomation Application Manager, because this feature is a prerequisite for usingthe hardware adapter.


Saving the high-availability configurationTo save your entries, click Save on the configuration dialog. Upon completion, theConfiguration Update Status window appears, showing the list of configurationfiles that were updated.

To ensure that the configuration properties are set correctly on all nodes of thedomain, you must replicate the configuration files as described below.

Restoring an existing high-availability configurationTo restore a domain configuration from a defined end-to-end automation highavailability policy, you can use the Query domain button on the configurationdialog. This retrieves information on most of fields in configuration notebook:v On the Domain tab:

– domain name and status (online/offline)– list of nodes and network interfaces– IP address of the defined network tiebreaker (even it is not the currently

active tie breaker, if more than one EXEC tiebreaker is defined, the address offirst one)

v On the Automation Manager tab:– IP address and netmask of the IBM.ServiceIP resource starting with resource

name prefix (for example, ″eez-″).These values are derived from the currently active policy, because they aredefined only if ″Define policy″ is performed and removed if ″Remove policy″is performed.

v On the Policy Pool tab:– File system type, mount point and device name of the IBM.AgFileSystem

starting with resource name prefix (for example, ″eez-″).These values are derived from the currently active policy, because they aredefined only if ″Define policy″ is performed and removed if ″Remove policy″is performed.


Replicating the configuration filesIf you have configured high availability for the end-to-end automation manager,you must replicate the configuration files to the other nodes in the IBM TivoliSystem Automation domain whenever you have made changes to the basic orhigh-availability configuration. To perform the task, click Replicate on theconfiguration task launcher. The Replicate Configuration Files window isdisplayed.

Use this window to distribute (replicate) the configuration files to the remainingnodes in the IBM Tivoli System Automation domain:1. Select the configuration files you want to replicate or click Select all to select

all configuration files in the list.2. Select the nodes to which the files are to be propagated. If all nodes can be

accessed with the same user credentials, click Select all. This is the easiest wayto ensure that the configuration is identical on all nodes.

3. Under Target node login, type the user ID and password for the replicationtarget nodes.

4. Start the replication by clicking Replicate.

Replication may take a while. While the files are being replicated, the Replicatebutton is indented and grayed-out. When the replication is complete, thereplication status of each configuration file is displayed.

After replication you must ensure that the value specified for the ’Host name or IPaddress’ on the 'Domain' tab of the ’end-to-end automation manager basicconfiguration’ still matches the system on all nodes in the domain. You arerecommended to use the virtual IP address specified in the IP address field of theautomation manager tab of ’Configuring high availability for the end-to-endautomation manager’. You have to adapt the ’Host name or IP address’ on theDomain tab of the ’end-to-end automation manager basic configuration on eachnode in the domain after the replication is completed.

Setting up the domainUse this task to set up the domain in which the end-to-end automation manager isto be automated. If you will be automating the end-to-end automation manager ina new IBM Tivoli System Automation domain, you must perform this task beforeyou invoke the high-availability configuration task Define policy.

To perform the task, click Set up domain on the configuration task launcher. Thefollowing window appears, showing the nodes that will make up the domain (thelocal node and the remote node or nodes, which were specified on the Domainsetup tab).


Two actions are performed to set up the domain:1. Prepare the remote node or nodes for joining the domain

To prepare the nodes, specify the user credentials for accessing the nodes. If allnodes can be accessed with the same user credentials, select Use credentialsalso for remaining nodes. To perform the cluster setup, click Prepare. Uponcompletion, a message box is displayed.

2. Define the domainTo complete the domain setup, the following commands are performed on thelocal node:v preprpnode - prepares the local node for joining the domainv mkrpdomain - creates the domain definition using the domain name and the

nodes that were specified on the Domain setup tabv startrpdomain - brings the domain onlineNote that IBM Tivoli System Automation must be installed on all nodes that areto be included in the new domain. If other IBM Tivoli System Automationdomains currently exist, they should be offline.Upon completion, a message box is displayed.

Removing the domainIn order to be able to remove the peer domain definition from all nodes, thedomain must be online to the local node.

To remove the domain definition from all nodes in the domain, click Removedomain on the task launcher. This invokes the rmrpdomain command.

Validating and storing the automation policy for the end-to-endautomation manager

You can validate the end-to-end automation manager automation policy as youhave configured it in the end-to-end automation manager high-availabilityconfiguration window by clicking Validate&Store policy on the configurationdialog task launcher. This task also stores the automation policy in XML format ina file. Upon completion the result of the validation is displayed, including thename of the file where the XML policy is stored.

Note: This requires IBM Tivoli System Automation for Multiplatforms version 3.1or higher.

This task has the following main purposes:


1. Validating the policy.This allows you to check whether the definitions that you made in the policyconfiguration window are valid and consistent.

2. Inspecting the generated file.This enables you to check which resources will be defined if you use theDefine policy task to activate the configured policy. If you are using IBM TivoliSystem Automation to also automate your own applications, the end-to-endautomation policy elements are added as a delta to your currently active policy.You may therefore want to evaluate whether those additional policy elementsmight have any impact on your active policy.

3. Modifying the stored policy and manually activating it.This allows you to apply modifications to the policy or extend it beyond whatyou can define using the policy configuration task. Note that each invocation ofthe Validate&Store policy or Define policy task will overwrite the XML policyfile. You should therefore copy or rename the file before modifying it.If you want to activate a modified policy, you must use the sampolicycommand. See the IBM Tivoli System Automation for Multiplatforms Referencemanual for details. You are recommended to use the update option -u in thiscase in order not to stop or remove any resource outside of the automationpolicy for the End-to-End Automation manager.The XML policy file contains inclusions of other XML policy files. Theseincluded files are not overwritten by an invocation of the Validate&Storepolicy 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 correspondinginclude-tag to refer to the renamed file.

Note: This function is only supported if IBM Tivoli System Automation forMultiplatforms version 3.1 or higher is used to make the End-to-EndAutomation manager highly available. If earlier versions are used,theValidate&Store policy button is disabled.

Defining the automation policy for the end-to-end automation managerClicking Define policy on the configuration dialog task launcher will create theresources with the resource name as described in the table below. Note that ifautomated resources with the same name exist, they will be changed.

If you specified, for example, the resource-/group prefix name eez on theAutomation manager tab, the resource group eez-srvdb2-rg and the resources andrelationships shown in the following table will be created.

Notes:

1. Be aware that changing one of these policy elements from outside this dialog,for example by using a console command or the sampolicy command, maycause a failure of the remove policy or the define policy task.

2. Activating or deactivating a policy for IBM Tivoli System Automation using thesampolicy command may remove existing definitions for the end-to-endautomation policy. For example, the definition of one of the resources in thetable below may be removed when a new policy for IBM Tivoli SystemAutomation is activated.It is therefore recommended that you first save the currently active policy usingthe sampolicy -s command, edit the XML output file, and finally use thecommand sampolicy -u to update the active policy with the changed XMLoutput file. When editing the policy, you must make sure that all definitions for


end-to-end automation are preserved and that none of your changes has anundesired effect on the currently active end-to-end automation policy. Fordetails, see the description of the sampolicy command in the IBM Tivoli SystemAutomation for Multiplatforms Reference.

Table 35. Resources in the automation policy for the end-to-end automation manager.

Resource name Resource class Description

eez-srvdb2-rg IBM.ResourceGroup The top-level group that comprisesall automated resources

eez-srv-rg IBM.ResourceGroup The group that comprises allresources except of the DB2 relatedresources

eez-db2-rg IBM.ResourceGroup The group that comprises all DB2resources

eez-was-rg IBM.ResourceGroup The group that comprises allWebSphere Application Serverresources

eez-engine-rg IBM.ResourceGroup The group that comprises allautomation manager resources

eez-hwa-rg IBM.ResourceGroup The resource group that comprisesthe hardware adapter resources

eez-gdpsagent-rg IBM.ResourceGroup The resource group that comprisesthe command receiver for DistributedDisaster Recovery resources

eez-ip IBM.ServiceIP The virtual IP address used for theWebSphere Application Server

eez-was-as IBM.Application The WebSphere Application server

eez-engine IBM.Application The end-to-end automation manager

eez-shared-mount IBM.AgFileSystem The policy-pool for the automationmanager; only defined when thepolicy pool is not harvested by theStorageRM

eez-db2-rs IBM.Application The DB2 server

eez-db2-rs_mount IBM.Application The DB2 filesystem

eez-hwa-rs IBM.Application The end-to-end hardware adapter

eez-gdpsagent-rs IBM.Application The command receiver forDistributed Disaster Recovery

db2-rs-dependsOn-db2-rs_mount IBM.ManagedRelationship Dependency from DB2 server on thefilesystem

eez-was-as-dependsOn-db2-rs IBM.ManagedRelationship Dependency from WebSphereApplication Server on DB2

eez-shared-mount-stopsAfter-engine IBM.ManagedRelationship Dependency from the policy pool onthe automation manager, onlydefined if the policy pool is notharvested by the StorageRM

eez-engine-startsAfter-shared-mount IBM.ManagedRelationship Dependency from the automationmanager on the policy pool

eez-engine-startAfter-was-as IBM.ManagedRelationship Dependency from the automationmanager on the WebSphereapplication server


Table 35. Resources in the automation policy for the end-to-end automation manager. (continued)

Resource name Resource class Description

eez-was-as-startsAfter-ip IBM.ManagedRelationship Dependency from the WebSphereapplication server on the virtual IPaddress

eez-ip-dependsOn-niequ IBM.ManagedRelationship Dependency from the virtual IPaddress on the network interface

hwa-startsAfter-eez-engine IBM.ManagedRelationship Dependency from hardware adapteron the automation manager

gdpsagent-dependsOn-eez-was-as IBM.ManagedRelationship Dependency from the commandreceiver on the WebSphereapplication server

eez-niequ IBM.Equivalency The available network interfaces oneach node

nettb IBM.TieBreaker Tie-Breaker defined, if IP address isspecified on the domain setup page

Removing the automation policy for the end-to-end automationmanager

Clicking Remove policy on the configuration dialog task launcher will remove theresources described in the preceding table. All the resources are first stopped andthen removed.

Activating or deactivating a policy for IBM Tivoli System Automation using thesampolicy command may remove existing definitions for the end-to-endautomation policy. For example, the definition of one of the resources listed in thetable above may be removed when a new policy for IBM Tivoli SystemAutomation is activated.

Therefore, it is recommended that you first save the currently active policy usingthe sampolicy -s command, edit the XML output file, and finally use the commandsampolicy -u to update the active policy with the changed XML output file. Whenediting the policy, you must make sure that all definitions for end-to-endautomation are preserved and that none of your changes has an undesired effecton the currently active end-to-end automation policy. For detailed information, seethe description of the sampolicy command in the IBM Tivoli System Automation forMultiplatforms Reference.


Chapter 5. Silent configuration

This chapter provides an overview of the silent mode of the end-to-end automationmanager configuration dialog and the tasks that you can perform in silent mode.

OverviewUsing the configuration tool in silent mode allows you to configure the end-to-endautomation manager and the end-to-end automation adapters without invoking theconfiguration dialog. This means that, for example, when configuring an AIX,Linux, or z/OS system, you do not need to have an X Window session available.

You can use the configuration tool in silent mode to configure the followingcomponents:v The end-to-end automation manager (including the automation policy and

hardware adapter)v The HACMP end-to-end automation adapterv The MSCS end-to-end automation adapterv The VCS end-to-end automation adapter

You configure these components by editing configuration parameter values in anassociated properties file. The parameter values in each properties file corresponddirectly to the values that you enter in the configuration dialog. See the followingfor more details about the configuration parameters:v Chapter 4, “Configuring the end-to-end automation manager,” on page 73v Chapter 12, “Installing and configuring the HACMP adapter,” on page 139v Chapter 13, “Installing and configuring the MSCS adapter,” on page 155v Chapter 14, “Installing and configuring the VERITAS Cluster Server adapter,” on

page 177

You must first invoke the configuration tool to generate silent mode inputproperties files before you actually perform a configuration update.

Working in silent modeTo use the configuration tool in silent mode, you need to follow these steps foreach component that you want to configure:1. Generate or locate the silent mode input properties file, see “Silent mode input

properties file” on page 104.2. Edit the parameter values in the file, see “Editing the input properties file” on

page 105.3. Invoke the configuration tool in silent mode to update the target configuration

files, see “Invoking silent configuration” on page 103.4. If the configuration tool does not complete successfully, deal with any errors

that are reported (see “Output in silent mode” on page 106) and re-invoke theconfiguration tool.


Tasks to be performed manuallyAfter configuration has completed successfully, you might also need to manuallyperform some of the tasks that are invoked in dialog mode by clicking thecorresponding push button in one of the launchpad windows.

If you have configured high availability for the end-to-end automation manager,you might also need to manually perform the following:1. Replicate the configuration files.

You must replicate the configuration files to the other nodes in the IBM TivoliSystem Automation domain whenever you have made changes to theend-to-end automation manager configuration. To do this, you must run theconfiguration tool in silent mode with identical input properties files on eachsystem.

2. One of the tasks that are described in Chapter 4, “Configuring the end-to-endautomation manager,” on page 73. As an alternative to using the dialogfunctions there are scripts available that you can launch to perform those tasks.v Set up the domain.

To perform this tasks, do the following:a. Issue the preprpnode command on all nodes that you specified when

configuring the end-to-end automation manager high-availability, exceptthe node where you ran the configuration tool in silent mode.

b. Invoke the script eezautomate -createDomain <config-dir>/eezautomate.properties on the local node to perform all remainingactions to set up the cluster.

v Remove the domain.Invoke the script eezautomate -deleteDomain <config-dir>/eezautomate.properties to remove the IBM Tivoli System Automation clusterto make the end-to-end automation manager highly available.

v Validate and store the automation policy for the end-to-end automationmanager.Invoke the script eezautomate -V -checkPolicy <config-dir>/eezautomate.properties to validate the end-to-end automation managerautomation policy as you have configured it.

v Define a configured automation policy.Invoke the script eezautomate -activatePolicy <config-dir>/eezautomate.properties to define the end-to-end automation managerresources and related dependent resource according to the values that youspecified when configuring the end-to-end automation managerhigh-availability.

v Remove a configured automation policy.Invoke the script eezautomate -deactivatePolicy <config-dir>/eezautomate.properties to remove the end-to-end automation managerresources and related dependent resource that matches the values that youspecified when configuring the end-to-end automation managerhigh-availability.

3. If you have made one of the end-to-end automation adapters highly availablein an HACMP, MSCS, or VCS cluster, you might also need to replicate thecorresponding adapter configuration files to the other nodes in the HACMP,MSCS, or VCS cluster. To do this, you must run the configuration tool in silentmode for the respective adapter with identical input properties files on eachnode of the cluster.


4. If you have made one of the end-to-end automation adapters highly availablein an HACMP or VCS cluster, you might also need to manually perform one ofthe following:a. Define the automation policy.

Invoke the script mkhacadpter -p for the HACMP adapter and the scriptmkvcsadpter -p for the VCS adapter to define the resources according tothe values that you specified when configuring the adapter automationpolicy.

b. Remove the automation policy.Invoke the script mkhacadpter -r for the HACMP adapter and the scriptmkvcsadpter -r for the VCS adapter to remove the resources that match thevalues that you specified when configuring the adapter automation policy.

Invoking silent configurationBecause silent configuration is simply an alternative to the configuration dialog,silent mode is invoked using the same command. For each component you specifythe option -s after the command to invoke the configuration tool.

You invoke silent configuration for each component as follows:

The end-to-end automation manager

Before you begin:

The user ID you use to invoke the configuration tool in silent mode mustmeet the following requirements:v The user ID must be in same group as the user ID you used for

installing System Automation Application Manager. The grouppermissions for cfgeezdmn.sh must be set to EXECUTE.

v The user ID must have read-write permissions on the followingdirectory:– Windows: <EEZ_INSTALL_ROOT>/cfg– AIX, Linux, and z/OS: /etc/<EEZ_INSTALL_ROOT>/cfg

Perform the following steps to invoke silent configuration:1. Log in on the system where System Automation Application Manager

is installed.2. Enter the following commands:

a. To configure the end-to-end automation manager:v Windows: cfgeezdmn.bat -s

v AIX, Linux, and z/OS: cfgeezdmn -s

b. To configure the end-to-end automation manager hardware adapter:v Windows: cfgeezdmn.bat -s -h

v AIX, Linux, and z/OS: cfgeezdmn -s -h

c. To configure the automation policy to make the end-to-endautomation manager highly available:v Windows: cfgeezdmn.bat -s -a

v AIX, Linux, and z/OS: cfgeezdmn -s -a

The HACMP end-to-end automation adapterTo use the HACMP adapter configuration tool in silent mode you musteither be logged in to the system with the user ID root or you must havewrite access to the directory /etc/opt/IBM/tsamp/eez/hac/cfg.

Chapter 5. Silent configuration 103

Issue the following command to invoke the configuration tool in silentmode:cfghacadapter -s

The MSCS end-to-end automation adapterTo invoke the configuration tool in silent mode, issue the followingcommand:cfgmscsadapter.bat -s

The file is located in the adapter installation directory, in the subdirectorybin. The default directory isC:\Program Files\IBM\tsamp\eez\mscs\bin

Note: There are further considerations on Windows Server 2008. See“Configuring MSCS on Windows Server 2008.”

The VCS end-to-end automation adapterTo use the VCS adapter configuration tool in silent mode, you must eitherbe logged in on the system with the user ID root or have write access tothe directory /etc/opt/IBM/tsamp/eez/vcs/cfg.

Issue the following command to invoke the configuration tool in silentmode:cfgvcsadapter -s

Configuring MSCS on Windows Server 2008All MSCS adapter configuration tasks must be performed with a domain useraccount satisfying these two requirements:1. The domain user account must be member in the local Administrators group

on all systems where the MSCS adapter service is planned to run.2. The domain user account must be granted full control access over the Microsoft

Server Cluster or Failover Cluster.

On Windows Server 2008, the silent configuration program must be started withAdministrator privileges. Otherwise the configuration program is unable to writechanged configuration files to the right location. Use the following procedure toobtain a command prompt with Administrator privileges which can be used to runthe silent configuration program:1. In the Windows Start menu, select ″All Programs″ -> ″Accessories″.2. Right-click the entry named ″Command Prompt″.3. In the context menu for ″Command Prompt″, select the entry ″Run as

administrator″.

Silent mode input properties fileYou generate silent mode input properties files from the values that are currentlydefined in the corresponding target configuration files. The advantages of this are:v It allows you to generate properties files immediately after installation and

before you perform any customizationv 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 modev You can easily recover from the accidental deletion of the silent mode input

properties file


To generate a silent mode input properties file, use one of the following optionswhen you invoke silent configuration:

-g Generate the input properties file only if it does not already exist.

-gr Generate the input properties file and replace it if it already exists.

Depending on the target configuration, Table 36 shows the silent input propertiesfiles that are generated if the -g or -gr option is specified.

Table 36. Generated input properties files

Component Target configuration Silent input properties file

The end-to-end automation manager cfgeezdmn -s -g | -gr <config_dir>/silent.eezengine.properties

The end-to-end automation managerhardware adapter

cfgeezdmn -s -h -g | -gr <config_dir>/silent.eezhwadapt.properties

The end-to-end automation managerautomation policy

cfgeezdmn -s -a -g | -gr <config_dir>/silent.eezauto.properties

HACMP adapter cfghacadapter -s -g | -gr <config_dir>/silent.hacadapter.properties

MSCS adapter cfgmscsadapter -s -g | -gr <config_dir>/silent.mscsadapter.properties

VCS adapter cfgvcsadapter -s -g | -gr <config_dir>/silent.vcsadapter.properties

Editing the input properties fileThe input properties files that are generated for each of the components containconfiguration parameter keyword-value pairs. To make it as easy as possible toswitch between modes and to minimize errors when editing the properties file, thestructure, terminology and wording that is used in the silent mode properties fileis identical to the structure, terminology and wording of the configuration dialog.

The names of tabs (for example, Domain) on the configuration dialog are used asidentifiers in the properties file, for example:# ==============================================================================# ... Domain

Each field name on the configuration dialog (for example, Domain name) iscontained in the properties file, followed by a brief description and the keywordfor 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 activated 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 values you want tochange and overwrite the value.


If you set the value of a keyword to blank or comment out the keyword, the valuethat is currently defined in the target configuration file remains unchanged.

Notes:

1. If a keyword is specified several times, the value of the last occurrence in thefile is used.

2. Each value must be specified on one single line.

Output in silent modeInvoking the configuration tool in silent mode leads to output that closely matchesthe output that is displayed by the configuration dialog and consists of thefollowing:

No updateThis occurs if:v All parameters in all target configuration files already match the

specified silent input parameters

v No errors were detected when checking the silent input parameters

However, if additional information is available or any warning conditionswere detected, the information and warnings are reported.


Successful completionThis indicates that:v At least one of the target configuration files was updated (all

configuration files and their update status are listed)

v No errors were detected when checking the silent input parameters

However, if additional information is available or any warning conditionswere detected, the information and warnings are reported.

Unsuccessful completionThis indicates that:v No target configuration file was updatedv Any errors that were detected when checking the silent input parameters

are reported


Silent input properties file generationThis indicates that:v No target configuration file was updatedv Target configuration values are used to generate the input file


Chapter 6. Installing and uninstalling service

z/OS service

Note: The next two sections describe installing and uninstalling service ondistributed systems. To update the installation on z/OS refer to“Updating the installation on z/OS” on page 114.

Installing serviceInstalling service means applying corrective service fix packs to release 3.1.0 ofIBM Tivoli System Automation Application Manager or upgrading the softwarerelease level from release 3.1.0. In this documentation, the service fix packs thatyou use for updating System Automation Application Manager are referred to asproduct fix packs.

Note: For some product fix packs, specific interim fixes or fix packs for WebSphereApplication Server are required. In such a case, these fixes are available atthe location from which you download the product fix pack. They must beinstalled before the product fix pack is installed. Detailed instructions forinstalling the fixes are provided in the release notes.

Product fix packs and interim fixes are delivered as:v Self-extracting archives for Windows and AIXv Archives in TAR-format for Linux

Where to obtain fix packsRead the release notes to find out which fix packs are required for a releaseupdate. The release notes are available on the IBM Tivoli System Automation homepage at:www.ibm.com/software/tivoli/products/sys-auto-linux/

On the page, click Technical Documentation to display the list of availabledocumentation.

The archives can be downloaded from the IBM Tivoli System Automation supportsite at:www.ibm.com/software/sysmgmt/products/support/IBMTivoliSystemAutomationforLinux.html

Archive naming conventionsNaming convention for product fix pack archives:3.1.0-TIV-SAE2E-<platform>-FP<fix_pack_number>.<archive_type>

Naming convention for WebSphere Application Server interim fix archives:3.1.0-TIV-SAWAS-<platform>-FP<fix_pack_number>.<archive_type>

wherev <platform> represents the platform on which System Automation Application

Manager is installed



http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliSystemAutomationforLinux.html

v <fix_pack_number> represents the fix pack numberv <archive_type> represents the platform-specific file extension of the archive

Example:This is the tar archive that is used to install product fix pack 1 for SystemAutomation Application Manager 3.1 on Linux on POWER platforms:3.1.0-TIV-SAE2E-PPC-FP0001.tar

Naming conventions of the update installer locationThe location at which you find the update wizard program for installing theproduct fix pack after unpacking an archive has the following syntax:EEZ31<mf>E2E<platform>/<platform>/<update_wizard_file>

wherev <mf> represents modification level and fix level. For example, for fix pack 3101,

the directory is named EEZ3101.v <platform> represents the platform on which System Automation Application

Manager is installedv <update_wizard_file> represents the update wizard program you use to install

the product fix pack

Example:This is where you find the update wizard after the Linux on POWER archive forfix pack 1 for System Automation Application Manager 3.1 is unpacked:EEZ3101E2EPPC/ppc/

Installation scenariosStarting with the update installer for System Automation Application Manager3.1.0.1, the installer supports two additional installation scenarios:v Allow System Automation Application Manager to use a WebSphere Application

Server that is set up to use a standalone user registry. This means thatWebSphere uses the user registry product for user authentication and userauthorization only. In this scenario, the interfaces provided by WebSphere to list,create, modify or delete user IDs must not be used by the System AutomationApplication Manager installer. As a consequence, the steps related to user IDmanagement that would otherwise be performed by the System AutomationApplication Manager installer have to be configured manually before the SystemAutomation Application Manager installer is invoked.

v Allow omitting all installer steps that are related to the automation database.This installer feature is required when an installation that is set up for highavailability has to be migrated to System Automation Application Manager3.1.0.1 or higher. As a consequence, the steps required for upgrading theautomation database have to be performed manually before the SA ApplicationManager installer is invoked.

Usage instructions for the platform-specific archivesThese are the archives for applying service to System Automation ApplicationManager.


|

||

|||||||||

||||||

WindowsTable 37. Archives for Windows platforms


3.1.0-TIV-SAE2E-WIN-FP<fix_pack_number>.exe The archive is self-extracting.

This is where you find the update installer program afterunpacking the product fix pack archive:

EEZ31<mf>E2EWindows/Windows/setup.exe

3.1.0-TIV-SAWAS-WIN-FP<fix_pack_number>.exe The archive is self-extracting.

For information about installing WebSphere Application Serverinterim fixes, refer to the release notes.

AIXTable 38. Archives for AIX platforms


3.1.0-TIV-SAE2E-AIX-FP<fix_pack_number>.bin The archive is self-extracting.


EEZ31<mf>E2EAIX/AIX/setup.bin

3.1.0-TIV-SAWAS-AIX-FP<fix_pack_number>.bin The archive is self-extracting.


Linux on System xTable 39. Archives for Linux on System x


3.1.0-TIV-SAE2E-I386-FP<fix_pack_number>.tar For extracting the archive, GNU tar 1.13 or later is required. Usethe tar -xf command to extract the files.


EEZ31<mf>E2EI386/i386/setup.bin

3.1.0-TIV-SAWAS-I386-FP<fix_pack_number>.tar For extracting the archive, GNU tar 1.13 or later is required. Usethe tar -xf command to extract the files.


Linux on POWERTable 40. Archives for Linux on POWER


3.1.0-TIV-SAE2E-PPC-FP<fix_pack_number>.tar For extracting the archive, GNU tar 1.13 or later is required. Usethe tar -xf command to extract the files.


EEZ31<mf>E2EPPC/ppc/setup.bin

Chapter 6. Installing and uninstalling service 111

Table 40. Archives for Linux on POWER (continued)


3.1.0-TIV-SAWAS-PPC-FP<fix_pack_number>.tar For extracting the archive, GNU tar 1.13 or later is required. Usethe tar -xf command to extract the files.


Linux on System zTable 41. Archives for Linux on System z


3.1.0-TIV-SAE2E-S390-FP<fix_pack_number>.tar For extracting the archive, GNU tar 1.13 or later is required. Usethe tar -xf command to extract the files.


EEZ31<mf>E2ES390/s390/setup.bin

3.1.0-TIV-SAWAS-S390-FP<fix_pack_number>.tar For information about installing WebSphere Application Serverinterim fixes, refer to the release notes.

Steps for installing a product fix packBefore you begin:

v Product fix packs are always cumulative.v Release 3.1.0 must be installed before any product fix pack can be installed.v To install a product fix pack, you must have administrator authority on

Windows or root authority on other platforms.

To install a product fix pack, perform the following steps:1. Check the release notes to find out which archives are required.2. Download the archives from the System Automation Application Manager

support site:v Archives for WebSphere Application Server fixes:

Follow the download instructions provided in the release notes.v Archives for product fix packs:

Typically, one archive is provided for each platform. Download the archive toa temporary directory.

3. If fixes for WebSphere Application Server must be installed, unpack and installthe fixes as described in the release notes.

4. Unpack the product fix pack archive to a temporary directory. For informationabout how to unpack the archive for your platform, refer to “Usage instructionsfor the platform-specific archives” on page 110.

5. Before performing the subsequent steps, check the release notes for additionalor deviating installation instructions.

6. Change to the directory in which the update wizard program is located. Forinformation on where to find the update wizard program, refer to “Usageinstructions for the platform-specific archives” on page 110.

7. 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 service in a setup for high availabilityIf you made your installation of System Automation Application Manager highlyavailable by using IBM Tivoli System Automation for Multiplatforms (as describedin the IBM Tivoli System Automation Application Manager Administrator’s and User’sGuide, “Chapter 14: Making System Automation Application Manager highlyavailable”), perform the following steps to install service for System AutomationApplication Manager. The instructions assume that System Automation ApplicationManager is currently running on node 1 but not on node 2.1. Stop node 2 within the SA MP domain (via command stoprpnode). It is

important to stop the node and not just to exclude it (since if you excludenode 2, the resources are still monitored, and if the resources on node 2become online due to the maintenance on node 2 they will be stoppedautomatically on both nodes).

2. Run the System Automation Application Manager 3.1.0.x update installer onnode 2.a. In case of remote DB2 setup, and if no other application uses the JDBC

driver on this node, perform the following step:After you are done with the panel “IBM DB2 Universal Database onremote system” and clicked “Next”, temporarily rename the JDBC driverdirectory on node 2 in the file system, so that the WebSphere ApplicationServer cannot find it. This ensures that there is no way for SystemAutomation Application Manager 3.1 on node 2 to connect to the remotedatabase manager during update installation. Note: You can determine theJDBC driver directory in the WebSphere administrative console. Open“Environment > WebSphere Variables” and inspect the variableDB2_JDBC_DRIVER_PATH.

b. On the panel “High Availability”, select “Yes” in order to skip all stepsrelated to the automation database.

3. In case of remote DB2 setup, perform the following step:Rename the JDBC driver directory back to its original name.

4. To start node 2 type startrpnode.5. Move the end-to-end automation manager to node 2 (either by moving the

application, or by excluding node 1).6. Verify that System Automation Application Manager 3.1.0.x has been properly

installed (for example by inspecting the System Automation ApplicationManager operations console, and in particular the version number on the“Welcome” page).

7. To stop node 1 type stoprpnode.8. Run the System Automation Application Manager 3.1.0.x update installer on

node 1, observing the instructions described in step 2.9. In case of remote DB2 setup perform the following step:

Rename the JDBC driver 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 serviceUninstalling service is only supported by uninstalling the complete SystemAutomation Application Manager as described in Chapter 7, “Uninstalling SystemAutomation Application Manager,” on page 115, and reinstalling to the levelrequired.

Chapter 6. Installing and uninstalling service 113

|

|||||||

|||||

||

|||||||||||

||

||

|

||

||||

|

||

||

|

|

Updating the installation on z/OSAn update to a z/OS installation is supplied as a PTF. This should be appliedusing SMP/E. After it has been applied check the installation notes sent as++HOLD data with the PTF. If a new Install Options file is provided by the PTFthis file must be merged with the file used for the initial installation, and samplejob "ATVEI100" must be resubmitted to update the JCL for the rest of theinstallation jobs.

Any or all of the following jobs must then be run, as specified in the installationnotes. Check the ++HOLD data for the correct sequence to run them in.v ATVEW170

This sets up the J2C connections and connection factories.

Note: This job is only required if new or changed *.RAR files have to beprocessed.

v ATVEM130

This deploys the SA Application Manager EJBs.

Note: This job is only required if there are new or changed EEZEAR parts.v ATVEM120

This deploys the Integration Module.

Note: This job is only required if there are new or changed EEZIMEAR parts.v ATVEM100

This deploys the GUI.

Note: This job is only required if there are new or changed files in theOperations Console.

v ATVEM110

This deploys the Policy Editor.

Note: This job is only required if there are new or changed files in the PolicyEditor.

v ATVEM140

This redeploys the TCR function in Websphere.

Note: This job is only required if service for TCR has to be applied.v ATVEM150

This redeploys the EIF TEC feature option for System Automation ApplicationManager.

v ATVEW130

This sets up the SA Application Manager .baroc and –load_classes files.

Note: This job is only required if new or changed TEC messages are shippedwith the update.


Chapter 7. Uninstalling System Automation ApplicationManager

Uninstalling System Automation Application Manager from z/OS

Note: This section describes uninstalling System Automation ApplicationManager on distributed systems. To uninstall the product from z/OSrefer to “Uninstalling System Automation Application Manager fromz/OS” on page 118.

This section describes how to uninstall System Automation Application Manager.An uninstallation program is provided that removes the components that wereinstalled by the installation wizard.

Note: Uninstall System Automation Application Manager before uninstallingWebSphere Application Server.

Launching the graphical uninstallation program on WindowsTo launch the uninstallation program on Windows, you can either issue thecommand <EEZ_INSTALL_ROOT>/uninstall/uninstall.exe at a command prompt orperform the following steps:1. Open Add or Remove Programs (Start > Control Panel > Add or Remove

Programs)._________________________________________________________________

2. On the Add or Remove Programs panel, select System AutomationApplication Manager and click Change/Remove. This brings up the initialpanel of the uninstallation program._________________________________________________________________

Launching the graphical uninstallation program on AIX and LinuxTo launch the uninstallation program on AIX and Linux, enter the followingcommand in a shell:<EEZ_INSTALL_ROOT>/uninstall/uninstall

This brings up the initial panel of the uninstallation program.

Using the uninstallation programBefore you begin:

v Before starting the uninstallation of System Automation Application Manager,make sure that the automation engine is stopped. Refer to "Using thecommand-line interface of the automation engine in the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide.

v During uninstallation, a number of panels may appear prompting you toconfirm that specific files are to be deleted. Make sure that the files should bedeleted before confirming the deletion.

Perform the following steps to uninstall System Automation Application Manager:


1. Launch the uninstallation program as described in the sections above._________________________________________________________________

2. Read the information on the first wizard panel and click Next.

_________________________________________________________________3. Specify whether Common Event Infrastructure should be deinstalled and click

Next.

_________________________________________________________________4. In the fields on this panel, type the requested information and click Next.


_________________________________________________________________5. The Start Deinstallation panel appears, confirming that the preparations for

uninstalling System Automation Application Manager and, should you haveopted to deinstall it, the Common Event Infrastructure are complete. ClickUninstall to start the uninstallation._________________________________________________________________

6. Some information panels are displayed while the uninstallation program checksyour system for the information it needs for the uninstall. The following figureshows an example.

_________________________________________________________________7. When the uninstallation is complete, a summary window is displayed. To exit

the installation program, click Done.

Chapter 7. Uninstalling System Automation Application Manager 117

Note: If problems were encountered during the unconfiguration step, an errorpanel appears before the actual uninstallation step (in which the files areremoved from the disk). In such a case, do this:a. On the error panel, click Save installation log files.b. Only if you want to remove all installed file, click Next. Otherwise,

click Cancel to be able to perform corrective actions and then rerunthe uninstallation

_________________________________________________________________

Uninstalling System Automation Application Manager from z/OSThe JCL members generated during the installation process include jobs fordeinstallation. These jobs should be submitted in the following order:1. ATVED10C

This job deletes the DB2 tables and table space.2. ATVEU100

This un-deploys the SA Application Manager from Websphere.3. ATVEU110

This removes the various directories used by the SA Application Manager.4. ATVEU120

This unmounts and removes run-time HFS.5. ATVEU130

This deletes previously defined procedures from the PROCLIB.

Note: This job is only required if the procedures have previously been copiedto the Installation PROCLIB by the job ATVEH160.

6. ATVER11C

This job removes the function groups and EJBROLE resource definitions createdby job ATVER110.

7. ATVER10C

This removes the security definitions.


Chapter 8. Installing and configuring the Distributed DisasterRecovery feature

The following topics describe how to install and configure the Distributed DisasterRecovery feature of System Automation Application Manager.

Installing the Distributed Disaster Recovery feature

Installation prerequisitesThe Distributed Disaster Recovery feature is only available on z/OS and Linux onSystem z. Before you can install the Distributed Disaster Recovery feature licenseyou must install the System Automation Application Manager base product.

Supported hardware and operating systemsThe following table shows the distributed server hardware and the operatingsystem release levels that must be in place on server clusters to be managed bySystem Automation Application Manager Distributed Disaster Recovery:

Table 42. Supported platforms for server clusters to be managed by SA AM Distributed Disaster Recovery

Operating system: System x1 System z System p System i

z/OS 1.7 or higher2 X

SUSE SLES 9

(32 bit3)X X4

SUSE SLES 9

(64 bit3)X X4 X X

SUSE SLES 10

(32 bit3)X4

SUSE SLES 10

(64 bit3)X4 X4 X4 X4

Red Hat RHEL 4.5AS

(32 bit3)

X

Red Hat RHEL 4.5AS

(64 bit3)

X X X X

Red Hat RHEL 5.0AS(32 bit3)

X

Red Hat RHEL 5.0AS

(64 bit3)

X X X X

AIX 5.25 X6

AIX 5.33 X6


Table 42. Supported platforms for server clusters to be managed by SA AM Distributed DisasterRecovery (continued)

Operating system: System x1 System z System p System i

z/OS 1.7 or higher2 X

AIX 6.17 X8

Notes:1. xSeries (except Intel IA64 based servers) and any other 32-bit Intel based server,

or AMD Opteron based server (64-bit), or Intel EM64T based server (64 bit).2. With SA z/OS 3.1 or higher.3. With SA MP 2.3 FP4 or higher.4. SP1 must be installed.5. With SA MP 2.3 only, FP4 is required as a minimum.6. Requires C++ Runtime Library for AIX version 7.0.0.1, which is included in

PTFs U800738 and U800739.7. With SA MP 3.1 or higher.8. AIX 6.1 supports Workload Partition (WPAR) mobility or relocation. In SA MP

3.1, RSCT does not support domains with nodes that are System WPARs.

PackagingThe code of the Distributed Disaster Recovery feature is shipped as part of theSystem Automation Application Manager product, but you can not exploit thecorresponding functionality unless you have installed a separate license to enablethis code. You receive the license when you order the Distributed DisasterRecovery feature. The name of the license file is eez31_DDR.lic. This is where youfind the license file:

CD If you install the Distributed Disaster Recovery feature from the CD ″IBMTivoli System Automation Application Manager 3.1.0 – Distributed disasterrecovery″ the license file is available in the directory EEZ3100FeatDDR/license.

Electronic distributionIf you obtain the Distributed Disaster Recovery feature through electronicdistribution you will find the license in the file C1A29ML.txt. Rename orcopy this file to eez31_DDR.lic.

Installing the feature licenseUse the eezdmn command to install the license. The license file must be accessiblefrom the system where the System Automation Application Manager is installed.Transfer the file eez31_DDR.lic in text mode to a location where it will beaccessible when you invoke eezdmn. Use the following command to install thelicense:eezdmn -instcert <license file location>/eez31_DDR.lic

To verify that the feature license has been successfully installed, issue thecommandeezdmn -help

The output should be in the form:


IBM Tivoli System Automation end-to-end automation engineVersion: 3.1.0.0.081402, NO_APARFeatures: SA AM for Distributed Disaster Recovery

Usage:...........................................................

The Distributed Disaster Recovery feature should be listed after ″Features:″ on thethird or subsequent lines of the command output.

For more information on the eezdmn command refer to the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide, chapter "Using thecommand-line interface of the automation engine".

Configuring the Distributed Disaster Recovery featureThe are two steps in the configuration of the Distributed Disaster Recovery feature:1. Configuring the JMS destination for GDPS events2. Configuring the hardware adapter

Configuring the JMS destination for GDPS eventsIf you have not activated or configured a GDPS server connection or a GDPSbackup server connection during the installation of System AutomationApplication Manager, you must do so now by performing the following steps inthe Integrated Solutions Console:1. Activate the Common Event Infrastructure (CEI) service when the application

server is started:a. Click Servers > Application servers > <server_name> > Container

Services > Common Event Infrastructure Service

b. Select the check box Enable service at server startup

c. Save the Master configuration and restart the WebSphere Application Server.2. Configure the GDPS server connection when the application server is started:

a. Click Resources > JMS > Queue connection factories (all scopes) >GDPSQueueConnectionFactory > Custom properties

b. Set ServerLocation to your GDPS server name

Chapter 8. Installing and configuring the Distributed Disaster Recovery feature 121

c. Set ServerPort to the port the GDPS server is listening to. Typically, this isport 5529.

d. Save your changes to the Master configuration.3. Optionally, configure the GDPS backup server connection:

a. Click Resources > JMS > Queue connection factories (all scopes) >GDPSBackupQueueConnectionFactory > Custom properties

b. Set ServerLocation to your GDPS backup server namec. Set ServerPort to the port the GDPS backup server is listening to. Typically,

this is port 5529.d. Save your changes to the Master configuration.

4. Configure the event groups for the GDPS server connection:a. Click Service integration > Common Event Infrastructure > Event

service > Event services > Default Common Event Infrastructure eventserver > Event groups > TEC events for GDPSQueueConnectionFactory

b. Set Event selector string toCommonBaseEvent[sourceComponentId[@subComponent = "IBM Tivoli SystemAutomation Application Manager DR"]]


c. Save your changes to the Master configuration.5. Optionally, configure the event groups for the GDPS backup server connection:

a. Click Service integration > Common Event Infrastructure > Eventservice > Event services > Default Common Event Infrastructure eventserver > Event groups > TEC events forGDPSBackupQueueConnectionFactory

b. Set Event selector string toCommonBaseEvent[sourceComponentId[@subComponent = "IBM Tivoli SystemAutomation Application Manager DR Backup"]]

c. Save your changes to the Master configuration.6. Restart the WebSphere Application Server.

The steps above can also be used to modify the destination for GDPS events.

To disable event forwarding to GDPS, perform the following steps in theIntegrated Solutions Console:1. Disable event forwarding for the GDPS server connection:

a. Click Service integration > Common Event Infrastructure > Eventservice > Event services > Default Common Event Infrastructure eventserver > Event groups > TEC events for GDPSQueueConnectionFactory

b. Set Event selector string to CommonBaseEvent[@rejectAll]

c. Save your changes to the Master configuration.2. Optionally, disable event forwarding for the GDPS backup server connection:

a. Click Service integration > Common Event Infrastructure > Eventservice > Event services > Default Common Event Infrastructure eventserver > Event groups > TEC events forGDPSBackupQueueConnectionFactory

b. Set Event selector string to CommonBaseEvent[@rejectAll]

c. Save your changes to the Master configuration.3. Restart the WebSphere Application Server.

These steps can also be used to selectively disable or enable event forwarding toGDPS or TEC. For example, you can enable event forwarding for the GDPS serverconnection and disable it for the GDPS backup server connection:


Ensure you use the correct Event selector strings:v To disable event forwarding always use CommonBaseEvent[@rejectAll].v To enable event forwarding use:

– for TEC events for TECQueueConnectionFactory:CommonBaseEvent[sourceComponentId[@subComponent = "IBM Tivoli SystemAutomation Application Manager"]]

– for TEC events for GDPSQueueConnectionFactory:CommonBaseEvent[sourceComponentId[@subComponent = "IBM Tivoli SystemAutomation Application Manager DR"]]

– for TEC events for GDPSBackupQueueConnectionFactory:CommonBaseEvent[sourceComponentId[@subComponent = "IBM Tivoli SystemAutomation Application Manager DR Backup"]]

Configuring the hardware adapterUse the end-to-end automation management configuration utility to configure thehardware adapter host and the hardware access credentials which the hardwareadapter uses. For more information see “Configuring the end-to-end hardwareadapter” on page 84.

Activating the Distributed Disaster Recovery featureAfter you have completed all the installation and configuration tasks describedabove you must restart the automation engine to enable usage of the DistributedDisaster Recovery feature functionality. The commands for this are:eezdmn shutdowneezdmn start

For more information on the eezdmn command refer to the IBM Tivoli SystemAutomation Application Manager Administrator’s and User’s Guide, chapter "Using thecommand-line interface of the automation engine".


Uninstalling the Distributed Disaster Recovery featureThere is no specific uninstallation of the Distributed Disaster Recovery feature. It isuninstalled implicitly when the System Automation Application Manager productis uninstalled.


Part 2. Enabling launch-in-context support

Chapter 9. Installing and configuring the IBMTEC extension for the System AutomationApplication Manager . . . . . . . . . . 129Overview. . . . . . . . . . . . . . . 129Prerequisites. . . . . . . . . . . . . . 129Installing the IBM TEC extension . . . . . . . 130Configuring the TEC extension for SystemAutomation Application Manager . . . . . . 130

Adapting the configuration file to yourenvironment. . . . . . . . . . . . . 130Defining a custom button for the Java version ofthe TEC Event Console (Java Swing Client) andthe TEC event viewer embedded in TEP . . . 131Defining a custom button for the Web version ofthe TEC Event Console . . . . . . . . . 131

Chapter 10. Setting up Tivoli Enterprise Portallaunch-in-context support . . . . . . . . 133


Chapter 9. Installing and configuring the IBM TEC extensionfor the System Automation Application Manager

OverviewThe IBM Tivoli Enterprise Console (TEC) extension for System AutomationApplication Manager (IBM TEC Extension) allows navigating from a displayedevent in the Event Console of Tivoli Enterprise Console (TEC Event Console) to thecorresponding resource or domain in the System Automation operations console.

Example usage scenario:

1. An operator sees an event in the TEC Event Console that shows that a TivoliSystem Automation resource failed.

2. The operator selects the event and starts the System Automation operationsconsole for this event.

3. The System Automation operations console automatically navigates to theresource specified in the event.

4. The operator analyzes the error by checking, for example, the resource statusand dependencies.

The IBM TEC Extension can be used for all TEC Event Console setups:v Java version of the TEC Event Consolev TEC Web consolev TEC event viewer embedded in the Tivoli Event Portal (TEP)

– running using the desktop client interface– running using the browser client interface

PrerequisitesTo install and use the IBM TEC Extension for System Automation ApplicationManager, the following prerequisites must be met:

TEC versionTEC 3.8 or later

TEC event forwardingTo exploit launch-in-context support from the TEC to the SystemAutomation operations console, Tivoli System Automation events must besent to the TEC, which is why you must enable TEC event forwarding forSystem Automation Application Manager in your environment:v You can set up TEC event forwarding during the installation of the

component (see “IBM Tivoli Enterprise Console connection configurationdata” on page 22) or at any time after the installation is complete (this isdescribed in the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide, chapter "Using Tivoli Enterprise Consolewith System Automation Application Manager").

Web browser is required for the Java version of the TEC Event ConsoleIf the Java version of the TEC Event Console is to be used to launch to theSA operations console, a Web browser (Mozilla, Firefox, or InternetExplorer) must be installed on the system where the event console runs.


Installing the IBM TEC extensionFor the TEC Web console client, no installation steps are required. You can directlyprogress to the configuration steps described in “Configuring the TEC extensionfor System Automation Application Manager.”

You only need to perform the installation steps described in this chapter if you areusing the Java version of the TEC Event Console or the TEC event viewerembedded in TEP:v When you are using the Java version of the TEC Event Console, the IBM TEC

Extension for System Automation Application Manager needs to be installed onthe system where the TEC Event Console runs.

v When you are using the TEC event viewer embedded in the TEP and the TEP isstarted using the browser client interface, the IBM TEC Extension for SystemAutomation Application Manager needs to be installed on the system where thebrowser runs.

To install the IBM TEC Extension on AIX, Linux or Windows perform these steps:1. Insert the System Automation Application Manager product CD into the CD

drive of the system where the TEC server is running.2. Open a command prompt (Windows) or a command shell (Linux, AIX).3. Change to the directory ecext on the product CD or in the electronic

distribution directory structure.4. Start the installation program, using this command:

java –jar setup.jar

5. Follow the installation instructions.

To install the IBM TEC Extension on z/OS perform these steps:1. Find the installer in SMPE_INSTALL_ROOT/install/tec_ext_installer.2. FTP the installer in binary mode to the location where it will be installed.3. Open a command prompt.4. Change to the directory at the chosen location.5. Start the installation program, using this command:

java –jar setup.jar

6. Follow the installation instructions.

Configuring the TEC extension for System Automation ApplicationManager

To enable the launch-in-context feature, complete the following steps:1. Optional: Adapt the configuration file isc.properties to your environment2. Define a custom button for the TEC Event Console

See the following sections for a more detailed description of these steps.

Adapting the configuration file to your environmentThis is an optional configuration step.

You can use the configuration file isc.properties to configure the host name andport of Integrated Solutions Console. The file is generated by the installer. If you


want to change the values specified at the installation, you can change the contentof the configuration file. Depending on the TEC Event Console setup, this file islocated in the following directory:

TEC Event Console is installed as a Java Swing client or TEC event viewerembedded in TEP

The file resides in the same directory where the IBM TEC Extension forSystem Automation Application Manager is installed.

TEC Web console clientThe file can be found in the directory <was_root>/profiles/<server_name>/Tivoli/EEZ

Example of a configuration file:isc.server = e2eserver1isc.port = 9060

isc.server is the hostname where the ISC runs which hosts the Tivoli SystemAutomation operations console. isc.port is the port that is used to access the ISC.

Defining a custom button for the Java version of the TECEvent Console (Java Swing Client) and the TEC event viewerembedded in TEP

Perform these steps:1. Open the Java version of the TEC Event Console.2. Select Windows > Configuration. Navigate to the console where you want to

define the button. Right click Properties.3. Select the Custom Button entry from the list on the left side of the panel.4. Click Create Button.5. Enter a label for the button, for example, “Launch SA Console”, and the

location of EEZLaunchSA.The syntax of the script is:For Windows:<path>EEZLaunchSA.bat [<java home>]

Example:"C:\Program Files\IBM\TECExtension\EEZLaunchSA.bat" C:\IBM\tec_console\jre\bin\

For AIX and Linux<path>EEZLaunchSA.sh [<java home>]

where <path> is the directory in which the TEC Extension for SystemAutomation was installed and the optional parameter <java home> is the Javahome directory where the file java.exe can be found. This parameter must endwith a / (slash) (Linux and AIX) or with \ (backslash) (Windows).Java 1.3 or higher is required. If the path contains blanks it must be enclosed inquotes (“).

6. Ensure that you have enabled “Event selection required for button action”.

Defining a custom button for the Web version of the TECEvent Console

For the definition of a Web custom button, the Java version of the TEC EventConsole is required.

Chapter 9. Installing and configuring the IBM TEC extension for the System Automation Application Manager 131

To define the button, do this:1. Open the Java version of the TEC Event Console.2. Select Windows > Configuration. Navigate to the console where you want to

define the button. Right click Properties.3. Select the Web Custom Button entry from the list on the left side of the panel.4. Click Create Button.5. Enter a label for the button, for example, “Launch SA Console”, and the URL of

the Servlet:http://<isc_server>:<isc_port>/ibm/EEZUIWebClient/EEZIscUrlBuilderServlet

where <isc_server> is the name of the host where the ISC runs which hosts theTivoli System Automation operations console and <isc_port> is the port that isused to access the ISC.Example:http://e2etest:9060/ibm/EEZUIWebClient/EEZIscUrlBuilderServlet

6. Ensure that you have enabled “Event selection required for button action”.


Chapter 10. Setting up Tivoli Enterprise Portallaunch-in-context support

If you are using both the System Automation operations console and TivoliEnterprise Portal (TEP) for resource monitoring and management, you can set uplaunch-in-context support for Tivoli Enterprise Portal. Launch-in-context supportenables users to launch Tivoli Enterprise Portal workspaces from the SystemAutomation operations console with a single mouse click.

When Tivoli Enterprise Portal launch-in-context support is configured, a hyperlinkbecomes available on the General page for first-level automation domains andnodes on the System Automation operations console, allowing users to open thecorresponding Tivoli Enterprise Portal work spaces with a single mouse click.

For launch-in-context support to work properly, a corresponding workspace mustbe available in Tivoli Enterprise Portal. This also means that the correspondingITM agents for the objects that are displayed in the SA operations console must beinstalled, for example, the operating system agent for a displayed system, or thecluster agent for a MSCS cluster, or the corresponding agent for a z/OS sysplex.

The context that is used to find a Tivoli Enterprise Portal workspace is as follows:

Table 43. Context used to find a Tivoli Enterprise Portal workspace

Selected objectin the SAoperationsconsole

Context passedduring launch Object searched for to find TEP workspace

z/OS domain Sysplex name managed_system_name=sysplex_name:*

non-z/OSfirst-levelautomationdomain

Domain name managed_system_name=domain_name:*

z/OS system Node name smfid=node_name

non-z/OSsystem

Node name hostname=node_name

In particular, you have to ensure the following:v For a non-z/OS domain, the first part of the managed system name as displayed

in the TEP must match the domain name as configured for the automationadapter of this domain

v For a z/OS system, the system name must be identical to the SMFIDv For a non-z/OS system, the host name that is used in the TEP must match the

node name as displayed in the SA operations console.

Here is a description how to change the host name that is used in the TEP:1. Stop the OS Monitoring agent on the managed system.2. When the corresponding entry in the TEP navigator goes offline, select the

entry, right-click and select Clear offline entry from the context menu. Theentry should disappear.


3. Open the configuration file for the monitoring agent, which is located in thefollowing path:install_dir/config/env.config

Add the following line:CTIRA_SYSTEM_NAME=<nodename>

where <nodename> is the node name exactly as it is presented in the SAoperations console.For Windows systems: Add the CTIRA_SYSTEM_NAME variable to the fileKNTENV, which is located in install_dir/TMAITM6.

4. Restart the OS Monitoring agent on the managed system. The system shouldappear in the TEP navigator with the new name.

To set up launch-in-context support for Tivoli Enterprise Portal, complete thefollowing steps in Integrated Solutions console (EEZAdministrator privileges arerequired):1. Open Integrated Solution Console.2. In the navigation tree, click IBM Tivoli System Automation > Settings >

Tivoli Enterprise launch-in-context support.3. In the fields on the page that appears, do this:

Enable launch-in-context support for Tivoli Enterprise PortalSelect to enable launch-in-context support.

Server nameSpecify the name of the server on which Tivoli Enterprise Portal runs.

Port numberSpecify the port number of the server on which Tivoli Enterprise Portalruns. The default port number is 1920.

4. Click OK to save the configuration.

Note: If the operations console is displayed while the TEP configuration ischanged, select "Menu -> Refresh all" to pick up the changed settings in thecurrent instance of the Operations Console.


Part 3. Installing and configuring the end-to-end automationadapters

Chapter 11. Overview . . . . . . . . . . 137

Chapter 12. Installing and configuring theHACMP adapter . . . . . . . . . . . . 139Installing the HACMP adapter . . . . . . . 139

Packaging . . . . . . . . . . . . . 139Installation prerequisites. . . . . . . . . 139Using SMIT to install the adapter . . . . . 139

Automating the HACMP adapter. . . . . . . 140Configuring the HACMP adapter . . . . . . 140

Invoking the HACMP adapter configurationdialog . . . . . . . . . . . . . . . 141Configuring the HACMP adapter . . . . . 142Replicating the HACMP adapter configurationfiles to other nodes in the domain . . . . . 151Defining the HACMP adapter automationpolicy . . . . . . . . . . . . . . . 151Removing the HACMP adapter automationpolicy . . . . . . . . . . . . . . . 152

Verifying the HACMP adapter configuration . . . 152Controlling the HACMP adapter . . . . . . . 153

Chapter 13. Installing and configuring theMSCS adapter. . . . . . . . . . . . . 155Installation and configuration roadmaps . . . . 155

Roadmap for highly available adapters . . . . 155Roadmap for adapters that are not highlyavailable . . . . . . . . . . . . . . 155

Planning and preparing for the MSCS adapter . . 156Packaging . . . . . . . . . . . . . 156Installation prerequisites. . . . . . . . . 156Planning and preparing for high availability . . 156Installation directories . . . . . . . . . 157Preparing the user account . . . . . . . . 157

Installing the MSCS adapter . . . . . . . . 158Using the installation wizard to install theMSCS adapter . . . . . . . . . . . . 159Installing the adapter in silent mode . . . . 160

Upgrading the MSCS adapter . . . . . . . . 160Configuring the MSCS adapter . . . . . . . 160

Invoking the MSCS adapter configuration dialog 160Configuring the MSCS adapter . . . . . . 161Replicating the configuration files to othernodes . . . . . . . . . . . . . . . 168

Windows Firewall on Windows Server 2008 . . . 169Providing high availability for the MSCS adapter 170

MSCS high availability on Windows Server 2003 170MSCS high availability on Windows Server 2008 175

Verifying the installation and configuration . . . 176Uninstalling the MSCS adapter . . . . . . . 176

Chapter 14. Installing and configuring theVERITAS Cluster Server adapter . . . . . . 177Installing the VCS adapter . . . . . . . . . 177

Packaging . . . . . . . . . . . . . 177Installation prerequisites. . . . . . . . . 177Using the installation wizard to install the VCSadapter . . . . . . . . . . . . . . 177

Automating the VCS adapter . . . . . . . . 178Configuring the VCS adapter . . . . . . . . 178

Invoking the VCS adapter configuration dialog 179Configuring the VCS adapter . . . . . . . 180Replicating the VCS adapter configuration filesto other nodes in the domain . . . . . . . 190Defining the VCS adapter automation policy 190Removing the VCS adapter automation policy 191

Verifying the VCS adapter configuration . . . . 191Controlling the VCS adapter . . . . . . . . 192


Chapter 11. Overview

System Automation Application Manager can be used to automate the operation ofresources within heterogeneous environments (called first level automationdomains) that each have a local automation technology of their own. Eachfirst-level domain is connected to the end-to-end automation manager or anoperations console by an end-to-end automation adapter.

The purpose of an automation adapter is tov Monitor resources within its first-level automation domainv Propagate resource attribute changes to the end-to-end automation manager.v Start and stop resources within the first-level automation domain by request of

the end-to-end automation manager or an operator.v Provide information for resources that are available within the first-level

automation domain.

The end-to-end automation adapter uses the Tivoli Event Integration Facility (EIF)to communicate with the end-to-end automation manager.

The following chapters describe how you install and configure the automationadapters that are shipped with System Automation Application Manager:v Chapter 12, “Installing and configuring the HACMP adapter,” on page 139

describes how you install and configure the HACMP adapterv Chapter 13, “Installing and configuring the MSCS adapter,” on page 155

describes how you install and configure the MSCS adapterv Chapter 14, “Installing and configuring the VERITAS Cluster Server adapter,” on

page 177 describes how you install and configure the VCS adapter


Chapter 12. Installing and configuring the HACMP adapter

The following topics describe how to install and configure the HACMP adapter.

Installing the HACMP adapter

PackagingThe HACMP adapter is shipped with System Automation Application Manager.The name of the installp package you use for installing the adapter is hac.adapter.This is where you find the installation package:v CD:

You install the adapter from the CD "Tivoli System Automation ApplicationManager V3.1.0 – Automation Adapters all platforms". The installation packageis available in the installation source directory EEZ3100Adapters/EEZ3100HACMP/AIX.

v Electronic distribution:

If you obtain System Automation Application Manager through electronicdistribution, you use the following archive to install the HACMP adapter:– Deliverable name: C1A21ML.bin– Installation source directory: EEZ3100Adapters/EEZ3100HACMP/AIX

Installation prerequisitesNote that the HACMP adapter can only be connected to System AutomationApplication Manager or the End-to-End Automation Management component ofIBM Tivoli System Automation for Multiplatforms V2.2 or V2.3.

The system on which you are installing the adapter must meet the followinginstallation prerequisites:v Required minimum HACMP release level: 5.3.0.5 (PTF5)v The HACMP adapter must not run on a node in the RSCT peer domain. If the

node on which the adapter is to run previously was an RSCT peer domain node,the following actions must be taken prior to installing the adapter:1. The environment variable 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>.v The 32-bit version of Java 1.4 or Java 5 SR5 must be installed.v SSL/SSH packages must be installed and the sshd subsystem must be running

to be able to complete the Replication task of the adapter configuration

Using SMIT to install the adapterYou will find the package in the directory on the CD or in the electronicdeliverable as described in “Packaging.”

Package name: hac.adapter. Use the SMIT interface to install the adapter.

The HACMP adapter installation directory is /opt/IBM/tsamp/eez/hac


Note: Do not change the installation directory or the configuration directory(/etc/opt/IBM/tsamp/eez/hac/cfg). Otherwise, the HACMP adapter cannotbe run because it relies on fixed paths.

After installing the adapter it must be configured as described in the remainingsections of this chapter.

Automating the HACMP adapterIf the HACMP cluster consists of more than one node, the HACMP adapter mustbe automated for the following reasons:v The host using the adapter must be able to reach the adapter always through the

same service IP without reconfiguration.v If the node on which the adapter runs goes down or the HACMP cluster

services on that node are stopped, the adapter must move to another availablenode in the cluster to resume the connection with the host using the adapter.

For more information about automating HACMP adapters using the adapterconfiguration dialog, see “Automation tab” on page 145.

Configuring the HACMP adapterThe following figure shows in which environments the HACMP adapter can workand what needs to be configured for the adapter.


You must configure the adapter for end-to-end automation management usingSystem Automation Application Manager. For more information on end-to-endautomation management, refer to the IBM Tivoli System Automation ApplicationManager Administrator’s and User’s Guide.

You can also configure the HACMP adapter in silent mode using an inputproperties file. See “Invoking silent configuration” on page 103 for more details.

Invoking the HACMP adapter configuration dialogThe HACMP adapter can be configured with the cfghacadapter utility. Thecfghacadapter utility is an X-Windows application and must be used from aworkstation with X-Windows server capabilities. This could be one of your clusternodes, if the X11 optional feature is installed on that node.

To use the HACMP adapter configuration dialog you, must be logged in to thesystem with the user ID root or you must have write access to the directory/etc/opt/IBM/tsamp/eez/hac/cfg.

Issue the cfghacadapter command to invoke the configuration dialog.

The main panel of the dialog is displayed:

Figure 5. Configuration of the HACMP adapter

Chapter 12. Installing and configuring the HACMP adapter 141

The dialog lets you perform the following tasks:1. Configure the HACMP adapter.2. Replicate the HACMP adapter configuration files to other nodes.3. Define the HACMP adapter automation policy to create the resources required

to automate the adapter.4. Remove the HACMP adapter automation policy.

Configuring the HACMP adapterOn the main panel of the configuration dialog, click Configure to display theconfiguration tabs that are described in the following sections.

In the following description, the term Host using the adapter is used to refer tothe end-to-end automation manager host.


Adapter tabOn the Adapter tab, you can configure the adapter host.

Fields and controls on the Adapter tab:

Automation adapter host:

Host name or IP addressHost name or service IP label of the node where the adapter runs.

On initial invocation, the field contains the value the commandhostname would return.

If you are automating the adapter, leave the value unchanged. Thevalue will be updated automatically with the value you specify inthe field Service IP label on the Automation tab (see “Automationtab” on page 145).

Request port numberThe port on which the adapter listens for requests from the hostusing the adapter. The default port is 2001.

Clicking Advanced lets you specify the adapter runtime behavior:

Adapter stop delayThe number of seconds by which the adapter stop is delayed toallow the adapter to properly deliver the domain leave event. Thedefault value is 5. You may need to increase the value on slowsystems. Valid values are 3 through 60.

Remote contact activity intervalThe time period, in seconds, after which the adapter will stop if itwas not contacted by the host using the adapter, whichperiodically contacts the adapter to check if it is still running. The


default value is 360. If a value other than 0 is specified, the intervalmust be a multiple of the check interval.

When the value is set to 0, the adapter continuously runs andnever stops.

Initial contact retry intervalThe time period, in minutes, within which the adapter will attemptto contact the host using the adapter until it succeeds or thespecified time has elapsed. The default value is 0, which meansthat the adapter will attempt to contact the host using the adapterindefinitely.

EIF reconnect attempt intervalThe time period, in seconds, that the adapter will wait before itattempts to reestablish the connection to the host using theadapter after the connection was interrupted. The default value is30.

Host using adapter tabUse the Host using adapter tab to determine which host the adapter connects toand to specify the required information.

The HACMP adapter must be configured to connect to an end-to-end automationmanager host.

Fields on the Host using adapter tab:

Configure the System Automation Application Manager host:

Host name or IP addressThe name or IP address of the host on which the end-to-end


automation manager runs. The port number specified here mustmatch the port number specified as event port number whenconfiguring the domain of the end-to-end automation manager.

Event port numberThe port to which the end-to-end automation manager listens forevents from the HACMP adapter. The default port is 2002.

Automation tab

This tab lets you configure the adapter automation policy. This allows you to makethe end-to-end automation adapter highly available, meaning that if the node onwhich the adapter runs breaks down, the adapter will be restarted on another nodein the domain.

Note: All nodes where the adapter can run must be accessible using the same userID and password.

Fields and controls on the Automation tab:

Automate adapter in first-level automation domainSelect this check box (see also “Automating the HACMP adapter”on page 140).

Query domain If the configuration dialog runs on a node in the HACMP cluster,click Query domain to query the current automation policy fromthe HACMP cluster. If the automation policy for the adapter is notyet defined but the cluster is up, at least all nodes that are onlineare shown in the Defined nodes table. This table provides thefollowing information:v Defined node

The list of defined nodes.v Automate on node


Indicates if the adapter is automated on this node.

The buttons at the bottom of the table let you perform thefollowing tasks:v Up

Moves the selected node one position up in the node sequence.The position determines the order in which automation selectsthe node on which the adapter may run.

v DownMoves the selected node one position down in the nodesequence. The position determines the order in whichautomation selects the node on which the adapter may run.

v AddDisplays the Add node for adapter automation panel which letsyou define the name of the node to be added and determine ifthe node is to be added to automation of the adapter.

v RemoveRemoves the selected node from the list. This means that theadapter must not be started on that node.

v ChangeDisplays the Change node for adapter automation panel whichlets you change the name of the node and add or remove thenode from automation of the adapter.

HACMP root directoryShows the root directory where HACMP is installed.

Automated resources prefixThe prefix that is used to compose the names of the resourcegroup, application, and application monitor in the automationpolicy.The resource names will appear in the resource table on theoperations console. The prefix can be changed. Use no more than atotal of 28 alphanumeric characters and underscores. Do not use aleading numeric. Reserved words are not allowed (see the "List ofReserved Words" in the HACMP Administration Guide, SC23-4862.).Note that if the HACMP adapter policy has been defined using thecurrent prefix, you must remove this policy before changing theprefix.For more information about defining the adapter automationpolicy, refer to “Defining the HACMP adapter automation policy”on page 151.

Service IP labelThe Service IP label is an entry in /etc/hosts that represents aservice IP label. It must be different from the host name of anynode in the HACMP cluster. It should be requested from thenetwork administrator as a "service IP label" or "alias" for all nodesin the HACMP cluster and must have been created (for example,using the SMIT interface) before you invoke the configurationdialog.

The HACMP adapter will listen on the service IP label for requestsfrom the host using the adapter, regardless on which node it runs.


Security tab

The security tab lets you configure the security for the interface between theHACMP adapter and the System Automation Application Manager host.

Fields and controls on the Security tab:

Select the Enable SSL check box if you want to use the Secure Socket layer (SSL)protocol. If checked, the following entry fields must be completed.

Truststore Name of the truststore file used for SSL. The file name may containmultiple period characters. Click Browse to select a file.

Keystore Name of the keystore file used for SSL. The file name may containmultiple period characters. Click Browse to select a file.

Keystore passwordPassword of the keystore file. The password is required if akeystore file was specified. Click Change to change the password.

Note: If the truststore is in different file than keystore, thepasswords for the files must be identical.

Keystore alias Alias name of the certificate to be used by the server. If notspecified, the keystore file must contain only one entry which isthe one to be used.

The Enforce user authentication check box enables user authentication with thePluggable Access Module (PAM). This check box is selected by default. It shouldonly be deselected for test purposes when user authentication is not required.

PAM Service The name of an entry in file /etc/pam.conf that determines which


check are made to authenticate a user. The default value is su,which checks users as if they were trying to execute the commandsu.


Note that the Logger tab always displays the values that are currently set in theconfiguration file.



Results:The settings in the configuration file are updated. You must restart theadapter for the changes to take effect.

Change the settings temporarilyPerform 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 theconfiguration file. If the adapter is not running, you receive an errormessage.


Revert to the permanent settingsIf you changed the settings temporarily, perform the following steps torevert to the permanent settings defined in the configuration file, or whenyou are unsure which settings are currently active for the adapter:1. Invoke the configuration dialog and open the Logger tab. The Logger

tab displays the values that are currently set in the configuration file.2. Click Apply to activate the settings.

Results:The settings take effect immediately. If the adapter is not running, youreceive an error message.


Maximum log/trace file sizeThe maximum file size in kilobytes that each log file can reachbefore it rolls over.






Off Collects no trace information. (Not recommended.)

Minimum Collects trace information on the error level. Only severe errorsituations are traced. This is the default setting.


Maximum Provides the message and trace logs and collects additionalinformation on the error, warning, and informational level.Required for testing and problem determination.






v Disk space:

Maximum disk spaceSpecifies the maximum disk space in bytes used by FFDC traceswhich are written to the FFDC trace directory. The default spaceis 10485760 byte (10MB).

Space exceeded policySelect what to do if the maximum disk space is exceeded:


Ignore Issue warnings, but do not enforce the FFDC disk spacequota.

Auto-deleteAutomatically delete FFDC files, oldest first, until thedirectory is below the limit. This is the default setting.

SuspendHalt further FFDC actions until the directory is manuallycleaned up.

v Message IDs:


Message ID listSpecifies the message IDs that are to trigger tracing, dependingon the filter mode. Wildcards, for example, *E (for all errormessages), are allowed.

Saving the configurationClick Save on the configuration dialog to save your changes to the adapterconfiguration files. Upon completion, the Configuration update status panelappears, showing the list of configuration files that were updated.

Notes:

1. If the service IP label specified on the Automation tab does not match the hostspecified on the Adapter tab, you are prompted for input. On the panel thatappears, click the button Adapter automation.

2. When entries are missing or a value you have entered is out of range (forexample, a port number), an error message is displayed.

3. If you made changes on the Automation tab, a message appears reminding youto launch the Define automation policy task.

4. If not noted otherwise, you must restart the adapter for the changes to becomeeffective.


Replicating the HACMP adapter configuration files to othernodes in the domain

After configuring an HACMP adapter on a node, you use the Replicate function topropagate the changes to the other nodes in the HACMP cluster. To use theReplicate function, go to the main panel of the configuration dialog and clickReplicate. The Replicate configuration files panel is displayed:

Use this window to distribute (replicate) the HACMP adapter configuration itselfor 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 valid on all nodes, you can click

Select all below the list of replication target nodes. This ensures that theadapter configuration is identical on all nodes.

3. Enter the user ID and password for the target nodes you want to replicate thefiles to.



Defining the HACMP adapter automation policyIf definitions for the automation of the HACMP adapter have been made, clickingDefine on the main panel of the configuration dialog will create the resources withthe resource name (Resource-/group prefix) as described on page 146. Note that ifautomated resources with the same name already exist, they are removed beforethe new resources are created.

If you used the default resource name prefix, the following resources will bedefined or queried:

Table 44. Resources in the HACMP adapter automation policy

Resource class Resource name Description

IBM.HacmpResourceGroup hacadapter_rg The resource group that comprises allautomated resources.

IBM.HacmpApplication hacadapter Commands: hacadapter start,hacadapter stop

IBM.HacmpAppMonitor hacadapter_mon Command: hacstatus


Table 44. Resources in the HACMP adapter automation policy (continued)


IBM.HacmpServiceIP <service_ip_label> value The label of the service IP on whichthe host using the adapter accessesthe adapter.This value is not definedbut just queried and, therefore, notremoved.

When you click Define, the button may stay indented for minutes until theresources have been removed, the cluster is synchronized, the new resources arecreated, and the cluster is synchronized again. The dialog will not repaint after ithas been covered and uncovered. Eventually, the results of the commands aredisplayed in a pop-up window.

Removing the HACMP adapter automation policyYou typically use the Remove function before you change the name prefix of theautomated resources (see page 146). When the adapter is automated and youdeselect the check box Automate adapter in system automation domain on theAutomation tab, you receive a message reminding you to remove the automatedresources for the adapter.

Clicking Remove on the main panel of the configuration dialog will remove theresources shown in Table 44 on page 151. If the HACMP adapter is still running, itis stopped before the automated resources are removed.

When you click Remove, the button may stay indented for minutes until resourceshave been removed and the cluster has been synchronized. Eventually, the resultsof the commands are displayed in a pop-up window.

Verifying the HACMP adapter configurationYou can use the clstat command to verify 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:v Resource Group: hacadapter_rg (if the prefix is ‘hacadapter’) in State: On

line

v Interface: p57067ha (in the example configuration) associated with theservice IP label of the same name in State: UP


clstat - HACMP Cluster Status Monitor-------------------------------------

Cluster: hacp57067 (1137142142)Mon Feb 20 14:15:16 MET 2006

State: UP Nodes: 2SubState: STABLE

Node: p570sa06 State: UPInterface: p570sa06 (0) Address: 9.152.20.176

State: UPInterface: p57067ha (0) Address: 9.152.24.195

State: UPResource Group: hacadapter_rg State: On line

Node: p570sa07 State: UPInterface: p570sa07 (0) Address: 9.152.20.177

State: UP************************ f/forward, b/back, r/refresh, q/quit *********

Controlling the HACMP adapterYou use the hacadapter command to start, stop, and monitor the adapter.

Table 45. HACMP adapter command options

Command Description

hacadapterstatus

Checks if the adapter is running and returns the RSCT return code for its operational state(OpState):

0 Unknown. The adapter status cannot be determined.

1 Online. The adapter is running.

2 Offline. The adapter is not running.

hacadapter start Starts the adapter if it is not running:

v If the adapter is automated, the command requests HACMP cluster services to start theadapter on the preferred node. The command returns when the clRGmove commandcompleted.

v If the adapter is not automated, it is started on the node where the command was issued. Theexit code is 0 if the command was successful.

hacadapter stop Stops the adapter if it is running:

v If the adapter is automated, the command requests HACMP cluster services to stop theadapter on the node where it is currently active. The command returns when the clRGmovecommand completed.

v If the adapter is not automated, it is stopped on the node where the command was issued. Theexit code is 0 if the command was successful.


Chapter 13. Installing and configuring the MSCS adapter

The following topics describe how to install and configure the MSCS adapter.

Installation and configuration roadmapsBefore you install the MSCS adapter, you must decide whether you want to makethe adapter highly available, which is strongly recommended. The roadmapsprovided in this section give an overview of the steps you need to perform toinstall and configure the adapter depending on your high-availability decision.

Roadmap for highly available adaptersIf you are making your adapter highly available, which is highly recommended,perform the following steps:1. Plan and prepare for the installation and configuration of the MSCS adapter

(see “Planning and preparing for the MSCS adapter” on page 156)._________________________________________________________________

2. Use the installation wizard to install the adapter on one node in the cluster andgenerate a response file (see “Using the installation wizard to install the MSCSadapter” on page 159)._________________________________________________________________

3. To ensure that uniform installation parameters are used, use the response file toinstall the adapters on the remaining nodes. Response-file driven installationcan be performed in silent mode (see “Installing the adapter in silent mode” onpage 160) or in interactive mode using the installation wizard (see “Using theinstallation wizard to install the MSCS adapter” on page 159)._________________________________________________________________

4. Configure the adapter on one of the cluster nodes using the adapterconfiguration dialog (see “Configuring the MSCS adapter” on page 160)._________________________________________________________________

5. To ensure that uniform configuration parameters are used, replicate the adapterconfiguration files to the remaining nodes (see “Replicating the configurationfiles to other nodes” on page 168)._________________________________________________________________

6. Create the MSCS resources needed for making the adapter highly available._________________________________________________________________

7. Verify the installation and configuration (see “Verifying the installation andconfiguration” on page 176)._________________________________________________________________

Roadmap for adapters that are not highly availableIf you are not making your adapter highly available, perform the following steps:1. Plan and prepare for the installation and configuration of the MSCS adapter

(see “Planning and preparing for the MSCS adapter” on page 156)._________________________________________________________________

2. Use the installation wizard to install the adapter on a cluster node (see “Usingthe installation wizard to install the MSCS adapter” on page 159).


_________________________________________________________________3. Configure the adapter using the adapter configuration dialog (see “Configuring

the MSCS adapter” on page 160)._________________________________________________________________

4. Verify the installation and configuration (see “Verifying the installation andconfiguration” on page 176)._________________________________________________________________

Planning and preparing for the MSCS adapter

PackagingThe MSCS adapter is shipped with System Automation Application Manager. Thisis where you find the installation file:v CD:

You install the adapter from the CD "Tivoli System Automation ApplicationManager V3.1.0 - Automation Adapters all platforms". This is where you find theinstallation wizard file (setup.exe) on the CD:EEZ3100Adapters\EEZ3100MSCS\Windows\setup.exe


If you obtain System Automation Application Manager through electronicdistribution, you use the following archive to install the MSCS adapter:C1A22ML.exeTo extract the archive, run the executable. The resulting directory structure isidentical to that on the CD. This is where you find the installation wizard file(setup.exe) when you have extracted the archive:EEZ3100Adapters\EEZ3100MSCS\Windows\setup.exe

Installation prerequisitesNote that the MSCS adapter can only be connected to System AutomationApplication Manager or the End-to-End Automation Management component ofIBM Tivoli System Automation for Multiplatforms V2.2 or later.

The system on which you are installing the adapter must meet the followinginstallation prerequisites:v Windows Server 2003 Enterprise Edition (32-bit) with Service Pack 1 or laterv Windows Server 2008 Enterprise Edition (32-bit)v System must be an MSCS nodev 64 MB RAM is required for running the MSCS adapter servicev 40 MB RAM is required for running the adapter configuration dialogv Disk space requirements:

– 140 MB for MSCS adapter installation– Typically, 6 MB is sufficient during normal operation, however, up to 250 MB

may be required for service-related files in the Tivoli Common Directory (logfiles, FFDC files)

Planning and preparing for high availabilityMaking the MSCS adapter highly available using MSCS is highly recommendedbut not required. To prepare for making an adapter highly available, do this:v Obtain a virtual IP address:


– The MSCS adapter will use this IP address for incoming connections– MSCS will make the virtual IP address available on the appropriate MSCS

nodev If desired, obtain a network name:

– If you specify the network name in the MSCS adapter configuration, thename will be published to the System Automation Application Managerserver.

– The System Automation Application Manager server will use this networkname for connecting to the MSCS adapter

– MSCS will associate this network name with the virtual IP address on theDNS server that is configured in the Microsoft Windows domain

Installation directoriesFor the MSCS adapter installation directory and the Tivoli Common Directory, thefollowing restrictions apply:v The MSCS adapter installation directory name must not include the DBCS space

character. The SBCS space character is supported.v Tivoli Common Directory:

When specifying a directory other than the default, observe the followingrestrictions:– 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 drive

letter. For example, C:\<directory_name> is allowed, butC:\<directory_name>:<directory_name> is not allowed.

– The space character and the underscore character (_) are allowed.

Preparing the user accountFor the installation and operation of the MSCS adapter, a special purpose domainuser account with local administrative rights must be defined in the domain. Thisdomain user account must be a member of the local Administrators group on allnodes of the cluster the adapter will manage.

Before you install the MSCS adaptor you must perform the following steps:v Create a special purpose domain user account which will run the MSCS adapter

service later on. This user is referred to as ″SAAMAdapter″ hereon.v Grant ″SAAMAdapter″ full control permission over the Microsoft Server Cluster

/ failover cluster to be managed with the MSCS adapter:– Open ″Cluster Administrator″ / ″Failover Cluster Management″ and navigate

to this server cluster / failover cluster.– Right-click this failover cluster and select the ″Properties″ context menu entry.– In the ″Properties″ window select the ″Security″ / ″Cluster Permissions″ tab.– On the ″Security″ / ″Cluster Permissions″ tab select the ″Add...″ button.– In the ″Select Users, Computer, or Groups″ window specify the

″SAAMAdapter″ user account and select the ″OK″ button.– On the ″Security″ / ″Cluster Permissions″ tab select the added domain user

account in the ″Group or user names″ list. Specify ″Allow″ on the ″FullControl″ entry in the ″Permissions for ...″ list. Select the ″OK″ button.

Chapter 13. Installing and configuring the MSCS adapter 157

v Log into each system where you want to install the MSCS adapter, using anaccount with administrative rights on the system. Use the local group policyeditor to grant the ″SAAMAdapter″ user account the right ″Log on as a service″:– Open the ″Start″ menu and select menu entry ″Run...″.– In the ″Run″ window, specify ″gpedit.msc″ in the ″Open″ input field and

select the ″OK″ button.– In the ″Local Group Policy Editor″ window, select the entry in the tree view:

″Local Computer Policy″ -> ″Computer Configuration″ -> ″Windows Settings″-> ″Security Settings″ -> ″Local Policies″ -> ″User Rights Assignment″.

– In the ″Local Group Policy Editor″ window the list view now shows a list ofuser rights. Double-click the right ″Log on as a service″.

– In the ″Log on as a service Properties″ window select the ″Add User orGroup...″ button.

– In the ″Select Users, Computer, or Groups″ window specify the″SAAMAdapter″ user account. Select the ″OK″ button.

– In the ″Log on as a service Properties″ window select the ″OK″ button.– Close the ″Local Group Policy Editor″ window.

v Log into each system where you want to install the MSCS adapter using anaccount with administrative rights on the system. Use the local users and groupseditor to make the ″SAAMAdapter″ user account a member of the localAdministrators group:– Open the ″Start″ menu and select the menu entry ″Run...″.– In the ″Run″ window specify ″lusrmgr.msc″ in the ″Open″ input field and

select the ″OK″ button.– In the ″Local Users and Groups″ window select the ″Groups″ entry in the tree

view.– In the ″Groups″ window right-click the ″Administrators″ group in the list

view and select the ″Add to Group...″ context menu entry.– In the ″Administrators Properties″ window select the ″Add...″ button.– In the ″Select Users, Computer, or Groups″ window specify the

″SAAMAdapter″ user account. Select the ″OK″ button.– In the ″Administrators Properties″ window select the ″OK″ button.– Close the ″Local Users and Groups″ window.

Installing the MSCS adapterYou have the following options to install an MSCS adapter:v You use the installation wizard to install the adapter.v You generate a response file when you use the installation wizard on a node.

You can then use the response file in one of two ways to install the adapter onother nodes:– You launch the installation wizard using the response file as input. The values

in the response file will appear in the fields on the wizard panels and can bechanged.

– You can install the adapter in silent mode on the remaining nodes of thecluster if you are making the adapter highly available, in which case thevalues in the response file apply to all nodes.


Using the installation wizard to install the MSCS adapterThis section describes how you install the MSCS adapter using the installationwizard. For information on silent mode, see “Installing the adapter in silent mode”on page 160.

Perform the following steps to install the adapter:1. Log in with the domain user account prepared in “Preparing the user account”

on page 157._________________________________________________________________

2. Launch the installation wizard. You have the following options:v To launch the installation wizard without generating a response file, use the

file:setup.exe

When you launch the wizard in this way, the values that are displayed onthe wizard panels are either default values or values that were detected onyour system.

v To launch the installation wizard, generating a response file, use thefollowing command:setup.exe -Dpreparesilent=true

This is the response file that is generated:<install_root>/install/install.properties

When you launch the wizard in this way, the values that are displayed onthe wizard panels are either default values or values that were detected onyour system.

When you have launched the wizard, click Next on the Welcome panel todisplay the license agreement._________________________________________________________________

3. Select I accept both the IBM and the non-IBM terms. to agree to the licenseagreement. Click Next. The Installation directory panel is displayed._________________________________________________________________

4. Specify the directory where you want to install the adapter or accept thedefault location. Click Next to display the Tivoli Common Directory panel._________________________________________________________________

5. If the installation program did not detect a Tivoli Common Directory on yoursystem, accept the default location or specify a different directory. If a TivoliCommon Directory was detected on your system, the directory is displayedand cannot be changed.Click Next to display the Microsoft Cluster Adapter service user panel._________________________________________________________________

6. Specify the domain user account prepared in “Preparing the user account” onpage 157 and the password.Click Next to display the summary panel._________________________________________________________________

7. Check the values on the summary panel and click Install to start theinstallation._________________________________________________________________

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 verify the success of the installation.If problems occur, check the applicable installation log files for moreinformation. Click Finish to close the installation wizard._________________________________________________________________

Installing the adapter in silent modeThis section describes how you install the adapter in silent mode, using a responsefile you generated during wizard-driven installation. For information on how togenerate a response file and how to use it as input for a wizard-driven installation,see “Using the installation wizard to install the MSCS adapter” on page 159.

To install the MSCS adapter in silent mode, use the following command:setup.exe -i silent -f <response_file_name>

Notes:

1. Response files contain password information and should be deleted when theyare no longer needed.

2. The silent installation will only be successful if the wizard-driven installationwhere the response file was generated completed successfully without errors.

Upgrading the MSCS adapterYou can upgrade an already installed MSCS adapter to the current version byrunning the installation as described in “Installing the MSCS adapter” on page 158.

If you upgrade from IBM Tivoli System Automation for Multiplatforms 2.2 or 2.3MSCS adapter to System Automation Application Manager 3.1 or higher, and havemade the MSCS adapter highly available using MSCS, you need to update theMSCS resource of type ″Generic Service″ used for controlling the MSCS adapterWindows service. The new service name to be controlled is ″SA AM MSCSAdapter″.

Configuring the MSCS adapterYou use the adapter configuration dialog to configure your MSCS adapter. If yourMSCS adapter is highly available, you always configure the adapter on one nodeand replicate the configuration file to the remaining cluster nodes as described in“Replicating the configuration files to other nodes” on page 168.

You must configure the adapter for end-to-end automation management using theend-to-end automation manager. For more information on end-to-end automationmanagement, refer to the IBM Tivoli System Automation Application ManagerAdministrator’s and User’s Guide.

You can also configure the MSCS adapter in silent mode using an input propertiesfile. See “Invoking silent configuration” on page 103 for more details.

Invoking the MSCS adapter configuration dialogTo invoke the configuration dialog, issue the following command:cfgmscsadapter

The file is located in the adapter installation directory, in the subdirectory bin. Thedefault directory is


C:\Program Files\IBM\tsamp\eez\mscs\bin

Note: On Windows Server 2008, the configuration dialog must be started withAdministrator privileges. Otherwise the configuration program is unable towrite changed configuration files to the right location. Use the followingprocedure to obtain a command prompt with Administrator privilegeswhich can be used to run the configuration dialog:1. Log on with the domain user account prepared in section “Preparing the

user account” on page 157.2. In the Windows Start menu, select ″All Programs″ -> ″Accessories″.3. Right-click the entry named ″Command Prompt″.4. In the context menu for ″Command Prompt″, select the entry ″Run as

administrator″.

The main panel of the configuration dialog is displayed:

The dialog lets you perform the following tasks:1. Configure the MSCS adapter.2. Replicate the MSCS adapter configuration files to other nodes.3. Define the MSCS adapter automation policy to create the resources required to

automate the adapter.4. Remove the MSCS adapter automation policy.

Configuring the MSCS adapterOn the main panel of the configuration dialog, click Configure to display theconfiguration tabs that are described in the following sections.

In the following description, the term Host using the adapter is used to refer tothe end-to-end automation manager host.


Adapter tabOn the Adapter tab, you can configure the adapter host.



Host name or IP address

v If the MSCS adapter is highly available, specify the network name or IPaddress you obtained as described in “Planning and preparing for highavailability” on page 156.

v If the MSCS adapter is not highly available, specify the IP address orhost name of the system on which the adapter is running.

Request port numberSpecify the number of the port on which the adapter listens for eventsfrom host using the adapter. The default port is 2001.

Automation domain

The domain name is the name by which the Microsoft Server Clustering (MSCS)cluster is known to the host using the adapter. The domain name must be uniquewithin the scope of automation domains that connect to an end-to-end automationmanager or a System Automation operations console.

You have the following options to specify the domain name:v It is recommended that you use the MSCS cluster name as domain name. This

option is selected by default. You must keep this setting if you want to useTivoli Enterprise Portal launch-in-context support, which allows you to launch


Tivoli Enterprise Portal work spaces from the System Automation operationsconsole, because Tivoli Enterprise Portal will not recognize any other domainname.

v If you cannot use the MSCS cluster name as domain name, for example, becauseit would not be unique, you can specify a domain name for the Microsoft ServerClustering (MSCS) cluster.



Remote contact activity intervalThe time period, in seconds, after which the adapter will stop if itwas not contacted by the host using the adapter, whichperiodically contacts the adapter to check if it is still running. Thedefault value is 360. If a value other than 0 is specified, the intervalmust be a multiple of the check interval.


Initial contact retry intervalThe time period, in minutes, within which the adapter will attemptto contact the host using the adapter until it succeeds or thespecified time has elapsed. The default value is 0, which meansthat the adapter will attempt to contact the host using the adapterindefinitely.



The MSCS adapter must be configured to connect to a System AutomationApplication Manager host.



Configure the end-to-end automation manager host:

Host name or IP addressThe name or IP address of the host on which the end-to-endautomation manager runs. The port number specified here mustmatch the port number specified as event port number whenconfiguring the domain of the end-to-end automation manager.

Event port numberThe port on which the end-to-end automation manager listens forevents from the MSCS adapter. The default port is 2002.

Security tabUse the Security tab to configure security for the interface between the MSCSadapter and the System Automation Application Manager host.


Select the Enable SSL check box if you want to use the Secure Socket layer (SSL)protocol. If checked, the following fields must be completed:



Keystore passwordPassword of the keystore file. It is required if a keystore file wasspecified. Click Change to change the password.



User authentication

It is recommended that you select the corresponding check box to enforceauthentication of the user ID on behalf of which the host using the adapterrequests operations from the MSCS adapter.







Change the settings temporarilyPerform 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 theconfiguration file. If the adapter was not running, you receive an errormessage.






Maximum log/trace file sizeThe file size in kilobytes.






Off Collects no trace information.

Minimum Collects trace information on the error level.








v Disk space:

Maximum disk spaceSpecifies the maximum disk space in bytes used by FFDC traceswhich are written into the FFDC trace directory. The defaultspace is 10485760 byte (10MB).

Space exceeded policySelect what to do if the maximum disk space is exceeded.

v Message IDs:


Message ID list:Specifies the message IDs which trigger the tracing of the FFDCdata. Wildcards like *E, meaning all error messages, are allowed.

Saving the configurationClick Save to save your settings to the adapter configuration files. Uponcompletion, the configuration update status panel appears, showing the list ofconfiguration files that were updated.

Notes:




Replicating the configuration files to other nodesIf your MSCS adapter is highly available, you must replicate the configuration filesto the other cluster nodes.

Open the main panel of the adapter configuration dialog and click Replicate. Thefollowing window is displayed:

Use this window to distribute (replicate) the MSCS adapter configuration itself orconfiguration updates to other nodes in the RSCT cluster:1. Select the configuration files you want to replicate, or click Select all below the

configuration file list to select all files in the list.2. Click Select all below the list of replication target nodes. This ensures that the

adapter configuration is identical on all nodes.3. In the Target node login section, specify a local or domain user ID that is valid

on all target nodes. For a local user ID, the specified password must be validon all target nodes. Domain user IDs must be specified in the form<user_ID>@<domain_name>.

4. Click Replicate to start the replication.



Windows Firewall on Windows Server 2008On Windows Server 2008, the Windows Firewall with Advanced Security isenabled by default, so all incoming TCP network communication not explicitlyallowed by rules is blocked. This inhibits the MSCS adapter. Firewall rules must bedefined to allow the TCP network communication required by the MSCS adapter.

To set up the Windows Firewall with Advanced Security, perform these steps oneach node of the Microsoft Failover Cluster:1. Select "Start > Administrative Tools > Windows Firewall with Advanced

Security".2. In the "Windows Firewall with Advanced Security" window, open the item

"Windows Firewall with Advanced Security on Local Computer" in the treeview.

3. Select item ″Inbound Rules″ in the tree view. Define all inbound rules requiredby System Automation Application Manager.

4. Select item ″Outbound Rules″ in the tree view. Define all outbound rulesrequired by System Automation Application Manager.

To define an Inbound Rule in the Windows Firewall with Advanced Security,perform these steps:1. Click ″New Rule...″ from ″Actions″.2. Select ″Custom″ to define a custom rule. Click ″Next″.3. Select ″All Programs″. Click ″Next″.4. Select the desired ″Protocol type″.5. For protocol type ″TCP″, set ″Local port″ to ″Specific Ports″, specify the desired

local port, and keep the setting ″All Ports″ for ″Remote port″. Click ″Next″.6. Click ″Next″.7. Select ″Allow the connection″. Click ″Next″.8. Select all network locations: ″Domain″, ″Private″, and ″Public″. Click ″Next″.9. Specify a name and a description for the rule. Click ″Finish″.

By default, the new rule is automatically enabled.

To define an Outbound Rule in the Windows Firewall with Advanced Security,perform these steps:1. Click ″New Rule...″ from ″Actions″.2. Select ″Custom″ to define a custom rule. Click ″Next″.3. Select ″All Programs″. Click ″Next″.4. Select the desired ″Protocol type″.5. For protocol type ″TCP″, set ″Remote port″ to ″Specific Ports″, specify the

desired remote port, and keep the setting ″All Ports″ for ″Local port″. Click″Next″.

6. Click ″Next″.7. Select ″Allow the connection″. Click ″Next″.8. Select all network locations: ″Domain″, ″Private″, and ″Public″. Click ″Next″.9. Specify a name and a reasonable description for the rule. Click ″Finish″.

By default, the new rule is automatically enabled.


The following rules must be defined and enabled as described above on all nodesof the Microsoft Failover Cluster. The rules contain the default ports afterinstallation. If you change any of the ports, you need to adapt the rules.

Table 46. Microsoft Failover Cluster default ports

Name Direction Default port Protocol

IBM Tivoli SA AM MSCS Adapter (TCP-In) Inbound 2001 TCP

IBM Tivoli SA AM MSCS Adapter (TCP-Out) Outbiund 2002 TCP

Providing high availability for the MSCS adapterThe procedure for this depends on the server operating system in use. ForWindows Server 2008 see “MSCS high availability on Windows Server 2008” onpage 175.

MSCS high availability on Windows Server 2003Perform the following steps:1. Open the Microsoft Cluster Administrator. Launch the Cluster Application

Wizard from the File menu. On the Welcome panel, click Next. The followingpanels are displayed:

_________________________________________________________________2. You are recommended to select Create a new virtual server to create or assign

dedicated resources (for example the virtual IP address) to the MSCS adapterservice resources.Click Next. The following panel is displayed:


_________________________________________________________________3. Define a new group or identify an existing group representing the MSCS

adapter as virtual server. In the following steps, this group is referred to asthe "virtual server group". You should choose the group containing thequorum resource. If you choose a different group, this group should onlycontain resources for making the MSCS adapter service highly available.Click Next. The Resource Group Name panel is displayed:


_________________________________________________________________4. On the Resource Group Name panel, specify a group name and a description.

Click Next. The Virtual Server Access Information panel is displayed:

_________________________________________________________________5. On the Virtual Server Access Information panel, specify a valid new network

name under which the MSCS adapter will be reachable. You must ensure thatthe operations console or automation manager to which the MSCS adapterwill connect is able to resolve this network name.If you do not want to use a network name for the MSCS adapter, specify adummy name here and remove it later.Specify a valid IP address on which the MSCS adapter can be reached. Youmust ensure that the operations console or automation manager to which theMSCS adapter will connect is able to reach the virtual IP address.Do not specify the IP address shown in the screen capture, as it belongs to theprivate IP address space.If the MSCS adapter is highly available, specify the network name or IP addressyou obtained as described in “Planning and preparing for high availability”on page 156.Click Next to display the Advanced Properties panel:


_________________________________________________________________6. Click Advanced Properties to view or modify the properties of the selected

MSCS group or resource. The default settings are appropriate for most cases,but should be checked for correctness and completeness.Click Next to continue._________________________________________________________________

7. On the Create Application Cluster Resource panel specify a cluster resourcefor your application.Click Next to continue._________________________________________________________________

8. On the Application Resource panel select Generic Service from thedrop-down list. An MSCS resource of type Generic Service is used to makethe service highly available as the MSCS adapter runs as a Windows service.Click Next to display the following panel:


_________________________________________________________________9. Specify an adapter name and a description.

_________________________________________________________________10. Click Advanced Properties and open the Dependencies page.


_________________________________________________________________11. On the Dependencies page:

v If you want to define a network name for the MSCS adapter, add adependency on the ″Network Name″ resource.

v If you do not want to define a network name for the MSCS adapter, add adependency on the ″IP Address″ resource.

_________________________________________________________________12. Display the Generic Service Parameters panel and type the service name "SA

AM MSCS Adapter" in the Service name field. Leave the Start parameters fieldempty and click Next._________________________________________________________________

13. The Registry Replication panel is displayed. No entries are required. ClickNext._________________________________________________________________

14. On the completion panel verify that the configuration settings are correct andclick Finish to save the configuration._________________________________________________________________

15. If you do not want to use a network name for the MSCS adapter you candelete it now using the Cluster Administrator:

_________________________________________________________________

MSCS high availability on Windows Server 2008Perform the following steps:1. Open the Microsoft Failover Cluster Management Console. In the tree view

select the failover cluster in which you want the configure high availability ofthe MSCS adapter. Click ″Configure a Service or Application...″ under″Actions″. The ″High Availability Wizard″ opens. Depending on your system’ssettings, the ″Before You Begin″ panel may be displayed. If so click ″Next″.

2. On the ″Select Service or Application″ panel, select the ″Generic Service″resource type and click ″Next″.

3. On the ″Select Service″ panel, select the ″SA AM MSCS Adapter″ service fromthe list of installed services. The MSCS adapter must have been installedsuccessfully on all failover cluster nodes before. Click ″Next″.


4. On the ″Client Access Point″ panel, specify a valid new network name underwhich the MSCS adapter will be reachable. It must be ensured that theautomation manager to which the MSCS adapter will connect is able to resolvethis network name.If you do not want to use a network name for the MSCS adapter, specify adummy name here and remove it later.Specify a valid IP address on which the MSCS adapter can be reached. Youmust ensure that the automation manager to which the MSCS adapter willconnect is able to reach this virtual IP address.Use the network name or IP address you obtained as described in “Planningand preparing for high availability” on page 156. Click ″Next″.

5. On the ″Select Storage″ panel do not select any storage volumes, as the MSCSadapter does not require any. Click ″Next″.

6. On the ″Replicate Registry Settings″ panel do not specify any registry keys, asthe MSCS adapter does not require any. Click ″Next″.

7. On the ″Confirmation″ panel, check that all settings are correct. If so click″Next″. If not click ″Previous″ to correct the settings.

8. On the ″Summary″ panel, click ″Finish″.

Verifying the installation and configurationPerform the following steps to verify that the adapter is installed and configuredcorrectly:

The adapter is highly available:

1. Start the MSCS adapter using MSCS and check if the domain joins.2. Fail the adapter over to all MSCS nodes and check if the domain joins.

The adapter is not highly available:

v Start the MSCS adapter using the Services plug-in from the MicrosoftManagement Console and check if the domain joins.

Uninstalling the MSCS adapterPerform the following steps:1. Make sure that the MSCS adapter service is stopped before starting the

uninstallation.Note that MSCS may try to restart or fail the MSCS adapter service over toanother MSCS node if you stop the service manually.If the MSCS adapter service is highly available, you must take the MSCSadapter group offline._________________________________________________________________

2. Open the Windows Control Panel and use Add or Remove Programs touninstall the adapter._________________________________________________________________


Chapter 14. Installing and configuring the VERITAS ClusterServer adapter

The following topics describe how to install and configure the VERITAS ClusterServer adapter (VCS adapter) on Solaris/SPARC.

Installing the VCS adapter

PackagingThe VCS adapter is shipped with System Automation Application Manager. Thename of the binary file you use for installing the adapter is install.bin. This iswhere you find the installation package:v CD:

You install the adapter from the CD "Tivoli System Automation ApplicationManager V3.1.0 - Automation Adapters all platforms". The installation packageis available in the installation source directory EEZ3100Adapters/EEZEEZ3100VCS/Solaris.


If you obtain System Automation Application Manager through electronicdistribution, you use the following archive to install the VCS adapter:– Deliverable name: C1A23ML.bin– Installation source directory: EEZ3100Adapters/EEZ3100VCS/Solaris

Installation prerequisitesNote that the VCS adapter can only be connected to System AutomationApplication Manager or the End-to-End Automation Management component ofIBM Tivoli System Automation for Multiplatforms V2.3.

The system on which you are installing the adapter must meet the followinginstallation prerequisites:v Solaris 10 on RISC processorsv 64 MB of free RAMv Minimum color depth: 8-bit (256 colors)v Minimum screen resolution: 640 x 480

Using the installation wizard to install the VCS adapterYou use an installation wizard to install the VCS adapter on Solaris/SPARCsystems.

Perform the following steps:1. Log in as root on the system where you want to install the VCS adapter.

_________________________________________________________________2. Launch the installation wizard using the file setup.bin. On the panel that

appears, click OK to display the license agreement. The language is detectedautomatically or you can select it on the first panel._________________________________________________________________


3. Select I accept both the IBM and the non-IBM terms to agree to the licenseagreement. Click Next. The Introduction panel is displayed.

After installing the adapter it must be configured as described in the remainingsections of this chapter.

Automating the VCS adapterIf the VCS Solaris/SPARC cluster consists of more than one node, the VCS adaptermust be automated for the following reasons:v The host using the adapter must be able to reach the adapter always through the

same service IP without reconfiguration.v If the node on which the adapter runs goes down or the VCS cluster services on

that node are stopped, the adapter must move to another available node in thecluster to resume the connection with the host using the adapter.

For more information about automating VCS adapters using the adapterconfiguration dialog, see “Automation tab” on page 183.

Configuring the VCS adapterThe following figure shows in which environments the VCS adapter can work andwhat needs to be configured for the adapter.


You must configure the adapter for end-to-end automation management usingSystem Automation Application Manager. For more information on end-to-endautomation management, refer to the IBM Tivoli System Automation ApplicationManager Administrator’s and User’s Guide.

You can also configure the VCS adapter in silent mode using an input propertiesfile. See “Invoking silent configuration” on page 103 for more details.

Invoking the VCS adapter configuration dialogThe VCS adapter can be configured with the cfgvcsadapter utility.

Notes:

1. The cfgvcsadapter utility is an X-Windows application and must be used from aworkstation with X-Windows server capabilities. This can be one of yourcluster nodes if the X11 optional feature is installed on that node.

2. The 32-bit version of Java 1.4 or Java 5 SR5 must be installed.3. SSL/SSH packages must be installed and the sshd subsystem must be running

to be able to complete the Replication task of the adapter configuration4. To use the VCS adapter configuration dialog, you must either be logged in on

the system with the user ID root or have write access to the directory/etc/opt/IBM/tsamp/eez/vcs/cfg.

Figure 6. Configuration of the VCS adapter

Chapter 14. Installing and configuring the VERITAS Cluster Server adapter 179

To open the configuration dialog, issue the command cfgvcsadapter.

The main panel of the dialog is displayed:

The dialog lets you perform the following tasks:1. Configure the VCS adapter.2. Replicate the VCS adapter configuration files to other nodes.3. Define the VCS adapter automation policy to create the resources required to

automate the adapter.4. Remove the VCS adapter automation policy.

Configuring the VCS adapterOn the main panel of the configuration dialog, click Configure to display theconfiguration tabs that are described in the following sections.In the following description, the term Host using the adapter is used to refer to anend-to-end automation manager host.


Adapter tabSelecting the adapter tab lets you configure the adapter host.



Host name or IP addressHost name or service IP label of the node where the adapter runs.

On initial invocation, the field contains the value the commandhostname would return.

If you are automating the adapter, leave the value unchanged. Thevalue will be updated automatically with the value you specify inthe field Adapter IP address on the Automation tab (see“Automation tab” on page 183).

Request port numberThe port on which the adapter listens for requests from the hostusing the adapter. The default port is 2001.

Automation domain:

The domain name is the name by which the VCS cluster is known to the hostusing the adapter. The domain name must be unique within the scope ofautomation domains that connect to the end-to-end automation manager.

You have the following options to specify the domain name:v It is recommended that you use the VCS cluster name as the domain name. This

option is selected by default. You must keep this setting if you want to use


Tivoli Enterprise Portal launch-in-context support, which allows you to launchTivoli Enterprise Portal work spaces from the System Automation operationsconsole, because Tivoli Enterprise Portal will not recognize any other domainname.

v If you cannot use the VCS cluster name as a domain name, for example, becauseit would not be unique, you can specify a domain name for the VCS cluster.



Remote contact activity intervalThe time period, in seconds, after which the adapter will stop if itwas not contacted by the host using the adapter, whichperiodically contacts the adapter to check if it is still running. Thedefault value is 360. If a value other than 0 is specified, the intervalmust be a multiple of the check interval.


Initial contact retry intervalThe time period, in minutes, during which the adapter will attemptto contact the host using the adapter until it succeeds or thespecified time has elapsed. The default value is 0, which meansthat the adapter will attempt to contact the host using the adapterindefinitely.



The VCS adapter must be configured to connect to an end-to-end automationmanager host.



Configure the System Automation Application Manager host:

Host name or IP addressThe name or IP address of the host on which the end-to-endautomation manager runs. The port number specified here mustmatch the port number specified as event port number whenconfiguring the domain of the end-to-end automation manager.

Event port numberThe port on which the end-to-end automation manager listens forevents from the VCS adapter. The default port is 2002.

Automation tabThis tab lets you configure the adapter automation policy. This allows you to makethe VCS adapter highly available.

Note: All nodes where the adapter can run must be accessible using the same userID and password.


Fields and controls on the Automation tab:

Automate adapter in first-level automation domainSelect this check box ( see also “Automating the VCS adapter” onpage 178).

Query domain If the configuration dialog runs on a node in the VCS cluster, clickQuery domain to query the current automation policy from theVCS cluster. If the automation policy for the adapter is not yetdefined but the cluster is up, at least all nodes that are online areshown in the Defined nodes table. This table provides thefollowing information:v Defined node

The list of defined nodes.v Automate on node

Indicates if the adapter is automated on this node.

The buttons at the bottom of the table let you perform thefollowing tasks:v Up

Moves the selected node one position up in the node sequence.The position determines the order in which automation selectsthe node on which the adapter may run.

v DownMoves the selected node one position down in the nodesequence. The position determines the order in whichautomation selects the node on which the adapter may run.

v Add


Displays the Add node for adapter automation panel which letsyou define the name of the node to be added and determine ifthe node is to be added to automation of the adapter.

v RemoveRemoves the selected node from the list. This means that theadapter must not be started on that node.

v ChangeDisplays the Change node for adapter automation panel whichlets you change the name of the node and add or remove thenode from automation of the adapter.

Automated resources prefixThe prefix that is used to compose the names of the resourcegroup, application, and application monitor in the automationpolicy.The resource names will appear in the resource table on theoperations console. The prefix can be changed. It is restricted toASCII 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 thecurrent prefix, you must remove this policy before changing theprefix.For more information about defining the adapter automationpolicy, refer to “Defining the VCS adapter automation policy” onpage 190.

Adapter IP addressRegardless on which node it runs, the end-to-end automationadapter uses this address to listen for requests and receive requestsfrom the host using the adapter. You must obtain this IP addressfrom your network administrator. The IP address must not be anactual host address or localhost.

Netmask The netmask that is used in the adapter automation policy. Requesta value from your network administrator.

Network interfaceThe network interface that is used in the adapter automationpolicy. The adapter can be reached on this network interfacethrough the specified IP address.

Click Query to display the Select network interface dialog, whichlets you select one of the network interfaces that are currentlydefined on the node where the configuration dialog runs.

Note: When you click Save after specifying an IP address in the field Adapter IPaddress, the following message may be displayed:


The message informs you that the IP addresses on the Adapter andAutomation tabs differ and asks you to confirm that the IP address on theAdapter tab is to be updated with the value you specified on theAutomation tab. Click Yes to confirm the change.

Security tabThe security tab lets you configure the security for the interface between the VCSadapter and the System Automation Application Manager host.

Fields and controls on the Security tab:

Secure Socket Layer (SSL) for transport:

Select the Enable SSL check box if you want to use the Secure Socket layer (SSL)protocol. If checked, the following entry fields must be completed.



Keystore passwordPassword of the keystore file. The password is required if akeystore file was specified. Click Change to change the password.




User authentication:

It is recommended that you select the corresponding check box to enforceauthentication of the user ID on behalf of which the host using the adapterrequests operations from the VCS adapter.

PAM ServiceThe name of an entry in file /etc/pam.conf that determines which checksare made to authenticate a user. The default value is su, which checksusers as if they were trying to execute the command su.







Change the settings temporarilyPerform 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 theconfiguration file. If the adapter is not running, you receive an errormessage.





Maximum log/trace file sizeThe maximum file size in kilobytes that each log file can reachbefore it rolls over.






Off Collects no trace information. (Not recommended.)

Minimum Collects trace information on the error level. Only severe errorsituations are traced. This is the default setting.


Maximum Provides the message and trace logs and collects additionalinformation on the error, warning, and informational level.Required for testing and problem determination.







v Disk space:

Maximum disk spaceSpecifies the maximum disk space in bytes used by FFDC traceswhich are written to the FFDC trace directory. The default spaceis 10485760 byte (10MB).

Space exceeded policySelect what to do if the maximum disk space is exceeded:

Ignore Issue warnings, but do not enforce the FFDC disk spacequota.

Auto-deleteAutomatically delete FFDC files, oldest first, until thedirectory is below the limit. This is the default setting.

SuspendHalt further FFDC actions until the directory is manuallycleaned up.

v Message IDs:


Message ID listSpecifies the message IDs that are to trigger tracing, dependingon the filter mode. Wildcards, for example, *E (for all errormessages), are allowed.

Saving the configurationClick Save on the configuration dialog to save your changes to the adapterconfiguration files. Upon completion, the Configuration update status panelappears, showing the list of configuration files that were updated.

Notes:

1. If the Adapter IP address specified on the Automation tab does not match thehost specified on the Adapter tab, you are prompted for input. On the panelthat appears, click the button Adapter automation.


3. If you made changes on the Automation tab, a message appears reminding youto launch the Define automation policy task.



Replicating the VCS adapter configuration files to other nodesin the domain

After configuring an VCS adapter on a node, you use the Replicate function topropagate the changes to the other nodes in the VCS cluster. To use the Replicatefunction, go to the main panel of the configuration dialog and click Replicate. TheReplicate configuration files panel is displayed:

Use this window to distribute (replicate) the VCS adapter configuration itself orconfiguration 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 valid on all nodes, you can click

Select all below the list of replication target nodes. This ensures that theadapter configuration is identical on all nodes.

3. Enter the user ID and password for the target nodes you want to replicate thefiles to.



Defining the VCS adapter automation policyIf definitions for the automation of the VCS adapter have been made, clickingDefine on the main panel of the configuration dialog will create the resources with


the resource name (Resource-/group prefix) as described on page 185. Note that ifautomated resources with the same name already exist, they are removed beforethe new resources are created.

If you used the default resource name prefix, the following resources will bedefined or queried:

Table 47. Resources in the VCS adapter automation policy


IBM.VCS.ResourceGroup vcsadapter-rg The resource group that comprises allautomated resources

Application vcsadapter-rs Commands: vcsadapter start,vcsadapter stop

IP vcsadapter-ip The virtual IP address on which thehost using the adapter accesses theadapter.

When you click Define, the button may stay indented for minutes until theresources have been removed, the cluster is synchronized, the new resources arecreated, and the cluster is synchronized again. The dialog will not repaint after ithas been covered and uncovered. Eventually, the results of the commands aredisplayed in a pop-up window.

Removing the VCS adapter automation policyYou typically use the Remove function before you change the name prefix of theautomated resources (see page 185). When the adapter is automated and youdeselect the check box Automate adapter in system automation domain on theAutomation tab, you receive a message reminding you to remove the automatedresources for the adapter.

Clicking Remove on the main panel of the configuration dialog will remove theresources shown in Table 47. If the VCS adapter is still running, it is stopped beforethe automated resources are removed.

When you click Remove, the button may stay indented for minutes until resourceshave been removed and the cluster has been synchronized. Eventually, the resultsof the commands are displayed in a pop-up window.

Verifying the VCS adapter configurationYou can use the hastatus command to verify 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 themember resources of the resource group vcsadapter-rg:


sasun01:~ # hastatusattempting to connect....connectedgroup resource system message--------------- -------------------- -------------------- -------vcsadapter-rg sasun01 OFFLINEvcsadapter-rg sasun02 ONLINE----------------------------------------------------------------

vcsadapter-rs sasun01 OFFLINEvcsadapter-rs sasun02 ONLINEvcsadapter-ip sasun01 OFFLINEvcsadapter-ip sasun02 ONLINE

Controlling the VCS adapterYou use the vcsadapter command to start, stop, and monitor the adapter.

Table 48. VCS adapter control command options

Command Description

vcsadapter status Checks if the adapter is running.

Available return codes:

0 Unknown. The adapter status cannot be determined.

1 Online. The adapter is running.

2 Offline. The adapter is not running.

vcsadapter start Starts the adapter if it is not running:

v If the adapter is automated, the command requests VCS to start the adapter on the preferrednode.

v If the adapter is not automated, it is started on the node where the command was issued. Theexit code is 0 if the command was successful.

vcsadapter stop Stops the adapter if it is running:

v If the adapter is automated, the command requests VCS to stop the adapter on the node whereit is currently active.

v If the adapter is not automated, it is stopped on the node where the command was issued. Theexit code is 0 if the command was successful.


Part 4. Appendixes


Appendix A. Default directories

The following table lists the default directory paths for which variables are used inthis guide. The paths in your environment may differ, for example, if you changedthe default path during the installation of the application or component.

Table 49. Default directories

Variable used in this guide Default path

<DB2_install_location> Windows: C:\Program Files\IBM\SQLLIB

AIX: /usr/opt/db2_09_01

Linux: /opt/ibm/db2/V9.1

<EEZ_CONF_ROOT> Windows: C:\Program Files\IBM\tsamp\eez\cfg

AIX, Linux: /etc/opt/IBM/tsamp/eez/cfg

z/OS: /etc/eez/cfg

<EEZ_INSTALL_ROOT> Windows: C:\Program Files\IBM\tsamp\eez

AIX, Linux: /opt/IBM/tsamp/eez

z/OS: /local/eez

The configuration properties files are located in the directory <EEZ_CONF_ROOT>.

<hacmp_adapter_install_root> AIX: /opt/IBM/tsamp/eez/hac

<hacmp_adapter_conf_root> AIX: /etc/opt/IBM/tsamp/eez/hac/cfg

<mscs_adapter_install_root> Windows: C:\Program Files\IBM\tsamp\eez\mscs

<mscs_adapter_conf_root> Windows: C:\Program Files\IBM\tsamp\eez\mscs\cfg

<Tivoli_Common_Directory> Windows: C:\Program Files\IBM\tivoli\common

AIX, Linux, Solaris, z/OS: /var/ibm/tivoli/common

The path to the Tivoli Common Directory is specified in the properties filelog.properties. The file log.properties is located in the following directory:v Windows: C:\Program Files\IBM\tivoli\common\cfgv AIX, Linux, Solaris, z/OS: /etc/ibm/tivoli/common/cfg

<was_root> Windows: C:\Program Files\IBM\WebSphere\AppServer

AIX: /usr/IBM/WebSphere/AppServer

Linux: /opt/IBM/WebSphere/AppServer

<vcs_adapter_install_root> Solaris: /opt/IBM/tsamp/eez/vcs

<vcs_adapter_conf_root> Solaris: etc/opt/IBM/tsamp/eez/vcs/cfg


Appendix B. Preserving user data during the upgrade fromIBM Tivoli System Automation for Multiplatforms 2.x toSystem Automation Application Manager 3.1

The upgrade from IBM Tivoli System Automation for Multiplatforms 2.2.0 toSystem Automation Application Manager 3.1 requires migrating WebSphereApplication Server 6.0.2 to WebSphere Application Server 6.1, and since theinstaller technology has changed from InstallShield to InstallAnywhere, theupgrade effectively means that you need to uninstall IBM Tivoli SystemAutomation for Multiplatforms 2.2 and install System Automation ApplicationManager 3.1 as a new product. The uninstallation step includes the removal of theautomation database (default name: EAUTODB). Among other data, this databasecontains information about the automation domain topology and the operatorpreferences.

To preserve the data, you need to export the data before uninstalling IBM TivoliSystem Automation for Multiplatforms 2.x to be able to import it during theinstallation of System Automation Application Manager. Similarly, you need toexport the data before upgrading from IBM Tivoli System Automation forMultiplatforms 2.x to System Automation Application Manager 3.1.

System Automation Application Manager 3.1 provides scripts that assist you inexporting and importing the data. These scripts are designed for local databases. Ifyou have a remote DB2 setup you must run these scripts directly on the systemwhere the automation database resides.

To export the data, perform the following steps before uninstalling IBM TivoliSystem Automation for Multiplatforms 2.2:1. Stop the WebSphere Application Server to ensure that the automation manager

does not lock any data in the database.2. Change to the “DDL/Script” directory on the product CD and run the

following script to export the data:Windows:db2_export_automgr_from_v2200.bat <db_name> <instance_owner> <instance_pwd> <export_to_dir>

AIX, Linux:./db2_export_automgr_from_v2200.sh <db_name> <instance_owner> <instance_pwd> <export_to_dir>

These are the required parameters:<db_name> - Name of the IBM Tivoli System Automation for Multiplatforms database.

Typically, this is EAUTODB.<instance_owner> - Database instance owner userid.<instance_pwd> - Database instance owner password.<export_to_dir> - Absolute path name of the directory where the exported tables

should be stored.Ensure that the <instance_owner> user ID has write accessto this directory.

All of these parameters are required.3. Then, uninstall IBM Tivoli System Automation for Multiplatforms 2.2 and start

the installation of System Automation Application Manager 3.1. If theautomation database is local, on the Import Data installation wizard panelselect Import data to the automation database and specify the <export_to_dir>directory where the exported tables are stored. If the automation database isremote, complete the System Automation Application Manager 3.1 installation


|||||

and then run the script db2_import_automgr_to_v2300.bat ordb2_import_automgr_to_v2300.sh directly on the remote system to import thepreviously exported data. The use of db2_import_automgr_to_v2300 isanalogous to the usage of db2_export_automgr_from_v2200. Note that this scriptis unchanged from release 2.3 of IBM Tivoli System Automation forMultiplatforms.

Notes:

1. Do not use the backup and restore functionality provided by DB2 to back upand restore the automation database, as this preserves the complete databaselayout.

2. The DB2 export utility that is used by the automation data export script createsseveral warning messages with message ID SQL3100W. This warning messagemay be ignored. For further information about this message, refer to the DB2documentation.

3. Even if the data import step during installation of System AutomationApplication Manager 3.1 fails, the installation completes. After SystemAutomation Application Manager 3.1 has been installed, open the OperationsConsole to check if the data were imported successfully. If the data were notimported successfully, you can check the installation log file, correct the error,and start the import again by using the import scripts provided by SystemAutomation Application Manager in the DDL/Script directory on the productCD. The import scripts have a syntax analogous to the export scripts.


||||||||

Appendix C. Troubleshooting the installation of SystemAutomation Application Manager

Use this section for troubleshooting problems you experience when installing orconfiguring System Automation Application Manager.

Installation wizard cannot find WebSphere Application Server on thesystem

WebSphere Application Server must be installed on the system before SystemAutomation Application Manager can be installed. If the installation wizard ofSystem Automation Application Manager does not detect WebSphere ApplicationServer on the system, although you did install it, the WebSphere ApplicationServer installation may be damaged. You can specify the location manually. IfWebSphere Application Server is found it will be used, if possible.

Determining the correct DB2 port numberWhen you install System Automation Application Manager on AIX or Linuxsystems, the installation wizard can retrieve the valid DB2 instance port numberautomatically. If you opt not to use this function, or on Windows systems, the portnumber 50000 will be displayed in the entry field on the corresponding installationwizard panel, which is the default port number that is assigned to DB2 during theinstallation of DB2. However, if the port is not free, a different port number isassigned automatically, which is why you need to check if the default port numberis correct.

This is how you can determine the correct DB2 port number:v All operating systems:

– The port number is displayed in the summary panel that appears when theDB2 installation is complete.

v You can also determine the port number in this way:1. Log on as the instance user (for example, db2inst1)2. Issue the command db2 get dbm cfg

3. Go to the following line:TCP/IP Service name (SVCENAME) = db2c_DB2

the string after (SCVENAME) = is the DB2 instance port.If the string is numeric, for example, 50000, it is the instance port number. Ifthe string is not numeric, for example, db2c_DB2, look for a string similar todb2c_DB2 50000/tcp in this file:AIX/Linux:/etc/services

Windows:C:\WINDOWS\SYSTEM32\DRIVERS\ETC\SERVICES

z/OS:/etc/services


DB2 access test hangsIf the attempt to access the database does not return (an indeterminate dialog isshown for a very long time), the test may be hung. The DB2 password may beexpired. To resolve the problem, perform these steps:1. End the installer. Because Cancel is not enabled at this point, you must end the

installer using the Task manager (on Windows systems) or the kill command(on UNIX systems). If the installer is killed, files in the system temporarydirectory remain on the system. If desired, you can manually delete the files inthe following way:v AIX/Linux: Delete the directories dirs /tmp/<xxxxxx>.tmp and

/tmp/install.dir.<xxxxxx>> (where <xxxxxx> is an arbitrary number)v Windows: Delete the directory C:\Documents and Settings\Administrator\

Local Settings\temp\Ixxxxxxx (where <xxxxxx> is an arbitrary number)2. Check if the DB2 password is expired.3. Renew the DB2 password.4. Restart the installation.

DB2 message SQL1035N The database is currently in use.SQLSTATE=57019

This message may be received after an error during installation. To correct it yourestart DB2 and drop database EAUTODB manually before resuming theinstallation. It may be necessary to use the force option to close DB2.

Installer cannot detect non-default SOAP portIf the default SOAP port settings are changed in the WebSphere AdministratorConsole, the installer cannot detect these. This causes an error panel to bedisplayed with the message that the cell could not be retrieved.

Changing the SOAP port via the Websphere Administrator Console does notupdate the value used by the wsadmin.sh command. This will cause all commandswhich use wsadmin.sh and a SOAP connection to fail.

A quick workaround for this problem is to manually edit the file/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/wsadmin.properties and change the value com.ibm.ws.scripting.port= by hand.

The recommended solution is to change the default ports of WebSphere using anAnt script. Please refer to the official WebSphere manual or InfoCenter for furtherinformation. In the InfoCenter search for the item ″Updating ports in an existingprofile″. Using the Ant script avoids the problem as it correctly updates the SOAPPort for wsadmin.sh.

Exceptions appear in file eezinstall.logAny NoClassDefFoundError exceptions that appear in the eezinstall.log file afterthe file EEZEAR was deployed can be ignored.

Note: In the last step of the install process the intermediate log is copied to thesubfolder install in the user install directory. This copy omits the messagesfrom the installer finish process ( 3 or 4 lines). If these lines are required the


original install log should be read. This log file can be found in the tmpdirectory with a name of the form: install.dir.xxxxxxxx.

Cleaning up from a failed installationInstallation can be canceled at any time. To recover from this situation, just run theinstaller again.v Installation was canceled or failed before the installation was started: no cleanup

is necessaryv Installation was canceled or failed during the installation phase: Run the

uninstaller to clean up files that were installed on disk.v Installation was canceled during the configuration phase: Installation can be

resumed.If the system has to be cleaned up again, rerun the installer, and then run theuninstaller to undo all configuration steps and to remove all installed files fromdisk.

v Installation failed during the configuration phase: Corrective actions may beneeded before installation can be resumed.You can also perform an uninstallation. If uninstall rather than resume isdesired, the script uninstall.sh can be used to revert the configuration changesthat have already been made. The installation log must be used to determinewhich changes were made and must be reverted. Afterwards, uninstall can becalled to remove the files from the disk. Uninstall can be run with option-Dforce=true to be able to proceed even if errors are reported in thepre-uninstall phase.To just recover the files if the product was uninstalled but the unconfigurationwas not successful and the files are needed to manually perform the remainingunconfiguration steps: Run the installer with the option -Dfilesonly=true in thiscase, only the files are installed; no configuration is performedBe sure to undo the configuration changes that were made during theinstallation before uninstalling. Otherwise, the configuration changes will beretained and the scripts to remove them are already uninstalled.

Procedures for troubleshooting an installationIf the installation fails, the installation wizard displays an error message.

When an error occurs, immediately archive the installation log files (see “Using thelog file collector utility” on page 202). This ensures that the original log files areretained, which is important should you need to contact IBM Support, and you canuse the archive for your own troubleshooting activities.

An error occurred in the pre-installation phaseIf an error occurs in the pre-installation phase, that is, before the Installbutton was clicked, click the button Save installation log files to collect allinstallation log files. The zip file will be created at the location specified.

An error occurred in the installation phaseTypically, errors only occur in the installation phase if insufficient diskspace is available.

An error occurred in the configuration phase:Click Finish to finish the installation, then change to <EEZ_INSTALL_ROOT>/

Appendix C. Troubleshooting the installation of System Automation Application Manager 201

install and run the log file collector utility. The log zip will be created inthe same directory. For details see “Using the log file collector utility.”

Using the log file collector utilityWhen an error occurs, use the log file collector utility to collect the log files thatwere written during the installation. The utility generates an archive that you canuse for your own troubleshooting activities and send to IBM Support if you cannotresolve the error.

Perform these steps to run the log file collector utility:1. Change the directory to <EEZ_INSTALL_ROOT>/install.2. Issue the following command:

Windows: collectinstallerlogs.bat

AIX/Linux: collectinstallerlogs.sh

The command can be invoked with the option -D to copy all logs (in case Javais not available). The directory tree created can then be packed manually.The name of the file that is created by the utility iseezinstallerlogs_<timestamp>.zip.On AIX and Linux you can invoke the command with the option tar to use tarrather than jar for packing.The resulting archive has the following directory structure:- EEZ_logs- cfg: configuration files (for the automation engine, etc.)- logs: eezinstall.log, etc.- sh / bat: scripts used by installer (Linux/AIX: sh; Windows: bat)- WAS_logs- logs: general WAS server logs- <server name>: logs for the selected WebSphere Application Server

Gathering information for IBM SupportIf you cannot resolve an installation problem, send the installation log file archiveto IBM support (see “Using the log file collector utility”).


Appendix D. Troubleshooting the installation of the HACMPadapter

Use this section for troubleshooting problems you experience when installing orconfiguring the HACMP adapter.

HACMP adapter does not startPossible causes:v HACMP level is lower than 5.3.0.5

To check, use: lslpp –l cluster.es.server.utils

v Cluster services have not been startedStart the services using smitty: hacmp —> C-SPOC —> Manage...

HACMP adapter terminatesCluster services terminated while the HACMP adapter was running

If the adapter is automated, it should restart automatically on next prioritynode where cluster services run.

Adapter attempts to start but terminates againThis may indicate that the adapter has not been configured correctly.

Adapter does not connect to the hostMake sure the firewall allows connections in both directions.

Check with netstat:v whether the adapter listens on the request port (default port is 2001):

netstat -an -f inet | grep 2001

Output should be similar to:tcp 0 0 9.152.21.239:2001 :::* LISTEN

v whether the end-to-end automation manager listens on the event port (defaultport is 2002):AIX:netstat -an -f inet | grep 2002

Linux:netstat -ant | grep 2002

and examine the output directly, since there is no grep command.Windows:netstat -an

and examine the output directly, since there is no grep command.z/OS:netstat -an

Output should be similar to:


tcp 0 0 9.152.21.239:2002 :::* LISTEN

However, with netstat you cannot check if tcp session creation is allowed orrejected by a firewall. To check if a tcp session can be created, use theseapproaches:v Try to open a session with telnet to port 2001 from the end-to-end automation

management host using this command:telnet <adapter-address> 2001

v Try to open a session with telnet to port 2002 from the first-level automationdomain to System Automation Application Manager using this command:telnet <e2e-host> 2002

If the connections cannot be set up using telnet a firewall may be blocking thesessions, or other network problems, such as routing problems, may exist.

HACMP adapter log files

Increasing the trace logging levelIf your trace is not detailed enough to analyze a problem and the problem can berecreated, it may be useful to increase the trace logging level:1. Invoke the adapter configuration dialog using cfghacadapter.2. On the main panel of the configuration dialog, click Configure.3. Select the Logger tab.4. Set the Trace logging level to Maximum.5. Click Apply. The new setting takes effect immediately.

For more information about the Logger tab, see “Logger tab” on page 148.

Log file locationsThe HACMP adapter log files are located in the Tivoli Common Directory:v Default location: /var/ibm/tivoli/commonv HACMP adapter-specific subdirectory structure in the Tivoli Common Directory:

– eez/ffdc – Contains the First Failure Data Capture files (if the FFDCrecording level is not set to Off in the adapter configuration dialog)

– eez/logs – Contains the HACMP adapter trace file:- traceFlatAdapter.log


Appendix E. Troubleshooting the installation of the MSCSadapter

Use this section for troubleshooting problems you experience when installing orconfiguring the MSCS adapter.

MSCS adapter log filesThis is where the adapter log files are located:v Tivoli Common Directory

Default location: C:\Program Files\IBM\tivoli\common

MSCS adapter-specific subdirectory structure in Tivoli Common Directory:– eez\ffdc – Contains the First Failure Data Capture files (if the FFDC

recording level is not set to Off in the adapter configuration dialog)– eez\logs – Contains the MSCS adapter log files:

- msgMSCSAdapter.log

- traceMSCSAdapter.log (if trace logging level is not set to Off)- eventMSCSAdapter.log (if trace logging level is not set to Off)

v The default adapter installation directory is C:\Program Files\IBM\tsamp\eez\mscs.Subdirectories and files used for troubleshooting:– The file data\eez.release.information.txt is created in the adapter

installation directory when the MSCS adapter is started. It containsinformation about service applied to the MSCS adapter and about theconfiguration settings used.

– The installation log files are located in the subdirectory /install/logs .

MSCS adapter installation failsIf the installation wizard indicates a problem, check the installer output and thefollowing files for error messages:v The log files in the subdirectory /install/logs.v IBM Tivoli System Automation Application Manager MSCS

Adapter_install_log.log.v mscsinstall_<date_time>.log

MSCS Adapter configuration dialog problems occurA problem occurs using the adapter configuration dialog

Problem determination:v The file cfgmscsadapter.bat contains a command for launching the

configuration dialogv The file contains a duplicate of this command which enables diagnostic

output (option -DEBUG)

The Apply button on the Logger tab cannot be clickedPossible cause: The MSCS adapter is not running.


Configuration files cannot be replicatedPossible causes:v The MSCS cluster is not available.v The cluster contains only a single node.

Replication fails with the message "Login on target node failed"Possible cause: The domain user ID was not specified in the correct format,which is <user_ID>@<domain_name>.

MSCS adapter start problemsMSCS adapter does not start

Problem determination:v The application event log should contain the message ″The service SA

AM MSCS Adapter has been started.″v In the configuration file cfg\mscs.service.properties, uncomment the

property service-log-file, restart the service, and investigate theresulting file.Ensure to comment the property again before returning to normaloperation.

v Make sure that the correct user credentials are used for the SA AMMSCS Adapter Windows service. Re-enter the password for the serviceon the Log On tab of the service properties view, and restart the service.

The SA AM Adapter Service reports the status 'Started' for some seconds andthen stops

v Startup should be completed within 60 seconds.v Refresh the view to see the actual status.

Problem determination:v Investigate the MSCS adapter log file msgMSCSAdapter.log.v If no error messages can be found, increase the trace logging level to

"Maximum" and provide all logs to IBM support.

The file msgMSCSAdapter.log contains the message EEZA0061E, indicating thatthe adapter failed to bind to a socket

Possible reason if the MSCS adapter service is made highly available usingMSCS:v The network name or virtual IP address used for the "Automation

adapter host" is not available during adapter startup

Possible solution:v Check the spelling of the network name or virtual IP address in the

adapter configuration dialog.v Check that there are appropriate "Network Name" and "IP Address"

resources defined in MSCS, and that they are working properly.v Check that the MSCS adapter service resource has a dependency on the

"Network Name" and "IP Address" resources in MSCS.

MSCS adapter terminatesThe MSCS adapter service stops and the log files contain no related errormessages. In particular, message ″EEZA0104I″ does not appear in the MSCSadapter log file msgMSCSAdapter.log. The message indicates that the MSCS adapterwas successfully stopped.


Problem determination:1. Search for javacore.*.txt files in the subdirectory lib.2. Use Windows tool drwtsn32 to configure dump capturing. Use the following

settings:

3. Try to recreate the MSCS adapter termination.4. Provide the data to IBM support.

Domain does not joinThe MSCS domain does not join within two minutes and the MSCS adapterservice is no longer running

Problem determination:v Investigate the MSCS adapter log file msgMSCSAdapter.log.v If no problems can be found, increase the trace logging level to

"Maximum" and provide all logs to IBM support.

The MSCS domain does not join within two minutes but the MSCS adapterservice is running

Problem determination and possible causes:v An invalid host name or IP address is specified for the System

Automation Application Manager server.

Appendix E. Troubleshooting the installation of the MSCS adapter 207

v The System Automation Application Manager server cannot be reachedfrom the system running the MSCS adapter. To check, use ping, telnet,and tracert commands.

v Determine the network name and IP address which the MSCS adaptersends to the System Automation Application Manager server:– Increase the trace logging level at least to "Minimum", restart the

MSCS adapter and investigate the log file eventMSCSAdapter.log.– Locate the latest adapter join event ("EVT_RSN=domainAdapterJoin").

The event contains the required information.v The system running the MSCS adapter cannot be reached from the

System Automation Application Manager server. To check, use ping,telnet, and tracert commands

MSCS adapter uninstallation failsUninstaller indicates an uninstallation problem

This happens if the MSCS adapter service was still running duringuninstallation.

Note: If the MSCS adapter service is made highly available using MSCS,MSCS may restart or fail over the service.

Uninstalling the MSCS adapter manuallyPerform the following steps in sequence:1. Stop the MSCS adapter service and ensure that it is not restarted by MSCS on

the system where the manual uninstallation is performed.2. Manually remove the service by issuing the command:

sc.exe delete "SA AM MSCS Adapter"

3. Manually remove the service JaasLogon by issuing the following commands:cd <adapter_installation_directory>\jre\binJaasLogon.exe –remove

4. Delete the adapter installation directory.5. If no other Tivoli System Automation product is installed on the system you

can delete the eez subdirectories of the Tivoli Common Directory.6. If no other products installed with InstallAnywhere remain on the system, go

to C:\Program Files\Zero G Registry and delete the complete directory. Ifother InstallAnywhere installer products are installed you must remove allentries related to MSCS Adapter from the file .com.zerog.registry.xml.For the following example, all subelements of <products> and <components>must be deletedExample:

<?xml version="1.0" encoding="UTF-8"?><registry install_date="2007-06-19 13:13:59" version="1.1"

last_modified="2007-06-21 16:26:20"><products>

<product name="IBM Tivoli System Automation MSCS Adapter"id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"version="3.1.0.0" copyright="2008" info_url="" support_url=""location="C:\Program Files\IBM\tsamp\eez\mscs"last_modified="2007-06-21 12:35:58">

<vendor name="IBM" id="4b89a1a0-1ee0-11b2-8c02-f523645d652c"home_page="" email=""/>

<feature name="Application" last_modified="2007-06-21 12:35:58">


<![CDATA[This installs the application feature.]]><component ref_id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"

version="3.1.0.0"location="C:\Program Files\IBM\tsamp\eez\mscs\.version"/>

<component ref_id="0df5155e-1ee4-11b2-9b2c-e02fa5b28587"version="1.0.0.0"location="C:\Program Files\IBM\tsamp\eez\mscs\.jre"/>

</feature></product>

</products><components>

<component id="655d44e8-1ee4-11b2-9a39-e02fa5b28587"version="3.1.0.0" name="Common"location="C:\Program Files\IBM\tsamp\eez\mscs\.version"vendor="IBM"/>

<component id="0df5155e-1ee4-11b2-9b2c-e02fa5b28587"version="1.0.0.0"name="InstallAnywhere VM Component"location="C:\Program Files\IBM\tsamp\eez\mscs\.jre"vendor="IBM"/>

</components></registry>

Appendix E. Troubleshooting the installation of the MSCS adapter 209

Appendix F. Changing the company logos on the top of areport

The company logos (by default ″Tivoli″ and ″IBM″) can be changed to customerspecific logos. There are two methods of doing this:1. Go to <tsamp_install_dir>eez\tcr\data\database\resource\eez_resources\

tcr_common\images\

You will find two images: ″tivoli.gif″ (printed on the upper left part of thereports), and ″IBM logo Black.gif″ (on the upper right part of the reports)You can replace these images either with blank ones or with your companylogo.

Notes:

a. The image name must remain the same.b. Some browsers may cache the images, so a restart may be required.

2. Go to <tsamp_install_dir>eez\tcr\data\database\resource\eez_resources\tcr_common\lib\

Backup file TivoliCommonReporting_v1.0.rptlibrary, then open it in a texteditor.Replace the image name in line 636: <expression name="uri">"tcr_common/images/tivoli.gif"</expression> with the name of the image you wantprinted on the upper left part of the reports.Replace the image in line 643: <expression name="uri">"tcr_common/images/IBM logo Black.gif"</expression> with the name of the image you want onthe upper right part of the reports.You will have to store your desired images in <tsamp_install_dir>eez\tcr\data\database\resource\eez_resources\tcr_common\images\


Appendix G. Considerations about user and groupmanagement in WebSphere Application Server

The security infrastructure of the WebSphere Application Server may be set up touse a third-party security product for all user authentication and userauthorization purposes.

Although there are WebSphere administrative interfaces to manage users andgroups, these interfaces may not be usable depending on how the securityprovider is set up and integrated to WebSphere. For example, with a standaloneLDAP server as security provider, the WebSphere Application Server may be set upto be able to bind only (that is, ask if a particular user has particular access rights),but not to give any listings of users or even delete or insert users in the LDAP userregistry.

Starting with System Automation Application Manager 3.1.0.1, the installers fordistributed platforms provide an installation mode that does not create or modifyany user IDs or groups. Instead, the installers expect that all user and grouprelated configuration activities have been performed already within the securityprovider according to the description in the IBM Tivoli System AutomationApplication Manager Administrator’s and User’s Guide, “Chapter 11. Managing users”.

For all earlier versions of the installers of System Automation ApplicationManager, the WebSphere Application Server security infrastructure must be at leasttemporarily set up to allow using the WebSphere administrative interfaces tomanage users and groups. This can be accomplished by configuring WebSpheresecurity to use federated user repositories before you start the installation ofSystem Automation Application Manager. Then install the System AutomationApplication Manager. Before you switch the WebSphere security configuration backto the previous configuration, perform all user and group related configurationactivities within the security provider according to the description in the IBM TivoliSystem Automation Application Manager Administrator’s and User’s Guide, "Chapter 11.Managing users".


|

|

|

|||

|||||||

||||||

|||||||||||

Appendix H. Using IBM Support Assistant

IBM Support Assistant is a free, stand-alone application that you can install on anyworkstation. IBM Support Assistant saves you time searching product, support,and educational resources and helps you gather support information when youneed to open a problem management record (PMR) or Electronic Tracking Record(ETR), which you can then use to track the problem.

You can then enhance the application by installing product-specific plug-inmodules for the IBM products you use. The product-specific plug-in for SystemAutomation Application Manager provides you with the following resources:v Support linksv Education linksv Ability to submit problem management reports

Installing IBM Support Assistant and the System AutomationApplication Manager plug-in

To install the IBM Support Assistant V3.0, complete these steps:v Go to the IBM Support Assistant Web Site:

www.ibm.com/software/support/isa/

v Download the installation package for your platform. Note that you will need tosign in with an IBM user ID and password (for example, a MySupport ordeveloperWorks® user ID). If you do not already have an IBM user ID, you maycomplete the free registration process to obtain one.

v Uncompress the installation package to a temporary directory.v Follow the instructions in the Installation and Troubleshooting Guide, included in

the installation package, to install the IBM Support Assistant.

To install the plug-in for System Automation Application Manager, complete thesesteps:1. Start the IBM Support Assistant application. IBM Support Assistant is a Web

application that is displayed in the default, system configured Web-browser.2. Click the Updater tab within IBM Support Assistant.3. Click the New Products and Tools tab. The plug-in modules are listed by

product family.4. Select Tivoli > Tivoli System Automation Application Manager.5. Select the features you want to install and click Install. Be sure to read the

license information and the usage instructions.6. Restart IBM Support Assistant.


http://www.ibm.com/software/support/isa

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationMail Station P3002455 South RoadPoughkeepsie New York 12601-5400U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″


WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

Trademarksv IBM, the IBM logo, ibm.com, AIX, DB2, developerWorks, HACMP, NetView,

Tivoli, Tivoli Enterprise, Tivoli Enterprise Console, WebSphere, and z/OS aretrademarks of International Business Machines Corporation in the United States,other countries, or both. IBM Redbooks and the IBM Redbooks logo areregistered trademarks of IBM.

v Adobe, Acrobat, Portable Document Format (PDF), and PostScript are eitherregistered trademarks or trademarks of Adobe Systems Incorporated in theUnited States, other countries, or both.

v Microsoft, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

v Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. inthe United States, other countries, or both.

v Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

v Red Hat and all Red Hat-based trademarks are trademarks or registeredtrademarks of Red Hat, Inc., in the United States and other countries.

v UNIX is a registered trademark of The Open Group in the United States andother countries.

v Other company, product, and service names may be trademarks or service marksof others.


Index

Aautomation manager

maximum number of connections 67

Cconfiguration dialog

end-to-end automation manager 73configuration properties

the end-to-end automationmanager 73

DDB2

automation manager databasecreating 14

installation parameters 19, 44server installation 12setup options

local setup 8, 42remote setup 8, 42

software prerequisitesfor remote setup 9local setup 9

WebSphere Application Serverrequests 64

default directories 195directories

default paths 195disk space requirements

AIX 11Linux 11Windows 10z/OS 41

Distributed Disaster Recoverysupported operating systems 119

Ee2einstallerlogs

log file collector utility 202eezinstall.log

NoClassDefFoundError 200electronic distribution 6end-to-end automation domain

name 22, 54end-to-end automation engine

WebSphere Application Server userID 22, 54

end-to-end automation managerconfiguration dialog 73configuring 73silent configuration 101, 103

Ffirst-level automation domain 137

fix packsinstalling 109

GGDPS installation parameters 53

HHACMP adapter

automating 140, 145automation policy

defining 151removing 152

configurationverifying 152

configuration dialogAdapter tab 143Automation tab 145Host using adapter tab 144invoking 141Logger tab 148Security tab 147using 142

configuration directory 139configuring 141installation directory 139installation source directory 139installing 139

prerequisites 139using SMIT 139

log file locations 204packaging 139replicating configuration files 151saving the configuration 150trace logging level

increasing 204troubleshooting 203

high availability setup, installingservice 113

home pageIBM Tivoli System Automation 109

HTTP session timeoutmodifying 66

IIBM Tivoli Common Reporting

installation parameters 53IBM Tivoli Enterprise Console

installation parameters 22, 52installation

planning 5, 38post-installation tasks 66prerequisites 24product CD 5verifying 63

installation directory 18, 43installing

service fix packs 109

installing (continued)service in highly available setup 113service, scenarios 110

Llanguages, supported 23, 58locales, supported 23, 58log file collector utility 202LTPA settings

LTPA password 66LTPA timeout 66

Mmiddleware software CDs

contents 12MSCS adapter

configuring 160high availability

planning 156providing 170, 175

installation directory 205installation log files 205installation wizard 159installing 158log files 205logging 165packaging 156prerequisites 156replicating configuration files 168security 164silent mode installation 160tracing 165troubleshooting 205uninstalling 176verifying the installation 176

NNoClassDefFoundError

eezinstall.log 200

Ppackaging

product CD 5post-installation tasks

modifying the LTPA settings 66overview 66

product CDcontents 23directories 23installation wizard files 6

RRACF

installation parameters 50


release notes 109

Ssecurity concepts

overview 11, 42SSL 11, 42

Server instanceshardware requirements 41

serviceinstallation scenarios 110installing 109installing in highly available

setup 113uninstalling 113

silent configurationend-to-end automation manager 103

SSLsecurity concepts 11, 42

support siteIBM Tivoli System Automation 109

System Automation Application Managersupported operating systems 8troubleshooting 199uninstalling 115

System Automation operations consoleinitial user ID 23, 55

TTCP/IP connectivity

hardware requirements 10, 41testing

connection between WebSphereApplication Server and DB2 64

timeoutsHTTP session timeout 66LTPA timeout 66

Tivoli Common Directory 18, 43Tivoli Event Integration Facility

(EIF) 137trademarks 218troubleshooting

HACMP adapter 203MSCS adapter 205System Automation Application

Manager 199

Uuninstalling

System Automation ApplicationManager 115

VVCS adapter

automating 178, 183automation policy

defining 190removing 191

configurationverifying 191

configuration dialogAdapter tab 181

VCS adapter (continued)configuration dialog (continued)

Automation tab 183Host using adapter tab 182invoking 179Logger tab 187Security tab 186using 180

configuring 179installation source directory 177installation steps 177installing 177

prerequisites 177packaging 177replicating configuration files 190saving the configuration 189

WWeb browsers

requirements 10, 40WebSphere Application Server

connection to DB2test 64

installation parameters 21, 48installing 15

Fix Pack 9 17Version 6.1.0.0 16

interim fixes 109server1 5Upgrade CDs 6


Readers’ Comments — We’d Like to Hear from You

System Automation Application ManagerInstallation and Configuration GuideVersion 3.1

Publication No. SC33-8420-01

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:v Send your comments to the address on the reverse side of this form.v Send a fax to the following number: FAX (Germany): 07031 16-3456

FAX (Other Countries): (+49) 7031 16-3456v Send your comments via e-mail to: [email protected]

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. E-mail address

Readers’ Comments — We’d Like to Hear from YouSC33-8420-01

SC33-8420-01

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Deutschland Research and Development GmbHDepartment 3248Schoenaicher Strasse 22071032 BoeblingenGermany

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Program Number: 5724-S92

Printed in USA

SC33-8420-01