Tivoli System Automation Application Manager

Transcription

1 Tivoli System Automation Application Manager Version 3.1 Release Notes (December 2009) SC

2

3 Tivoli System Automation Application Manager Version 3.1 Release Notes (December 2009) SC

4 Note! Before using this information and the product it supports, read the information in Notices on page 23. This edition of the IBM Tivoli System Automation Application Manager Release Notes applies to IBM Tivoli System Automation Application Manager Version 3.1, program number 5724-S92, and to all subsequent releases of this product until otherwise indicated in new editions. This edition replaces SC IBM welcomes your comments. A form for readers comments may be provided at the back of this publication, or you may address your comments to the following address: IBM Deutschland Research & Development GmbH Department 3248 Schoenaicher Strasse Boeblingen Germany FAX (Germany): FAX (Other Countries): Internet eservdoc@de.ibm.com If you would like a reply, be sure to include your name, address, telephone number, or FAX number. Make sure to include the following in your comment or note: Title and order number of this book Page number or topic related to your comment When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Read this before installation Where to find IBM Tivoli System Automation Application Manager documentation Chapter 2. Required hardware and software Supported operating systems Installation prerequisites for all systems Middleware software requirements DB2 software prerequisites Software prerequisites for a local DB2 setup Software prerequisites for a remote DB2 setup Supported Web browsers Hardware requirements Memory TCP/IP connectivity Disk space requirements Service Fixes and problem-solving databases Installing fix packs to obtain level Installing fix packs to obtain level Installing fix packs to obtain level Installing fix packs to obtain level Installing fix packs to obtain level Chapter 3. Known problems and limitations Documentation update Notices Trademarks Copyright IBM Corp iii

6 iv IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

7 Chapter 1. Read this before installation This software may contain errors that could result in critical business impact. It is highly recommended that you install the latest available fixes before using this software. Fixes can be obtained from IBM Tivoli System Automation Application Manager support at the following Web site: The Release Notes document for IBM Tivoli System Automation Application Manager, Version 3.1, includes information that helps you install this software. Always view the most current version of the release notes before installing and using the product. The most current version of the release notes is available at the following Web site: The release notes document contains the latest updates for the product IBM Tivoli System Automation Application Manager. Changes since the last edition of this document are marked with a vertical bar ( ) in the left margin. Where to find IBM Tivoli System Automation Application Manager documentation Additional documentation about this software can be found either on the product CD, or on the product Web site at: Copyright IBM Corp

8 2 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

9 Chapter 2. Required hardware and software Supported operating systems The following table lists the operating systems that are supported for System Automation Application Manager: Table 1. Supported operating systems Operating system IBM System x 1,7 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 2003 R2 Standard Edition (32 bit) X Windows Server 2003 R2 Enterprise Edition (32 bit) X Windows Server Standard Edition X Windows Server , 8 Standard x64 Edition X Windows Server Enterprise Edition X Windows Server , 8 Enterprise x64 Edition X AIX (AIX 5L Version 5.3) ML 4 X AIX X SUSE SLES 9 (32-bit) 5 X SUSE SLES 9 (64-bit) 6 X X X SUSE SLES 10 (32-bit) 5 X SUSE SLES 10 (64-bit) 6 X X X SUSE SLES 11 (32-bit) 5, 8 X SUSE SLES 11 (64-bit) 6, 8 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 AS (32-bit) 5 X Red Hat RHEL 5 AS (64-bit) 6 X X X z/os 1.7 or higher X All SP levels of the listed supported SuSE versions and all update levels higher than the listed supported Red Hat versions are also supported, unless a more specific minimum version requirement is indicated in one of the following notes. Notes: 1. IBM System x with IA32, EM64T, or AMD64 architecture. Any other systems with IA32, EM64T, or AMD64 architecture are also supported. Systems with IA64 architecture are not supported. 2. Windows Server 2008 installed as Server Core or under Hyper-V is not supported. 3. APAR IY65979 must be installed. 4. AIX 6.1 supports Workload Partition (WPAR) mobility or relocation. In the V3.1 release, System Automation Application Manager do not support domains with nodes that are System WPARs. 5. The following Linux kernel architectures are supported for running with 32 bit: Copyright IBM Corp

10 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 p v s390x on IBM System z is supported for some distributions 7. All supported operating systems are also supported when running under VMware. 8. Requires IBM Tivoli System Automation Application Manager V3.1 with fix pack 5 or higher. 4 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

11 Installation prerequisites for all systems Prerequisites for all systems that are accessed with browsers that are configured to display multibyte-character languages Affected System Automation Application Manager version: z/os only, version Problem: Installation prerequisites for all systems that are accessed with browsers that are configured to display multibyte-character languages Solution: Before installing SA Application Manager on a system that will be accessed with internet browsers that have their preferred language set to a multibyte-character language, be sure to copy the following fonts in binary mode into the Java fonts subdirectory of the WebSphere Application Server installation directory: mtsansdj.ttf (you can download this font from ftp://submit.boulder.ibm.com/download/typography/ fonts/worldtype/archive/wtsd/ / ) tnrwt_j.ttf (you can download this font from ftp://submit.boulder.ibm.com/download/typography/ fonts/worldtype/archive/wt / / ) For the z/os operating system, the WebSphere Java fonts directory is "<WAS_HOME>/java/lib/fonts". For other operating systems, the WebSphere Java fonts directory is "<WAS_HOME>/java/jre/lib/fonts". In addition, create a subdirectory "fallback" of the WebSphere Java fonts directory and make the font files listed above also available from this directory, either by copying the files into the "fallback" directory as well or by creating symbolic links. Ensure that all users have read access to these font files, both for the files located in the WebSphere Java fonts directory and for the files located in the "fallback" subdirectory. Restart the WebSphere Application Server after the fonts have been installed. If the fonts are not installed, multibyte characters are not displayed correctly on the pages of the following dialogs: v SA Application Manager policy editor, v SA Application Manager measurement and reporting. Chapter 2. Required hardware and software 5

12 Middleware software requirements The following middleware software must be installed on the system on which System Automation Application Manager will run, before the component itself can be installed: v DB2: A DB2 server for a local DB2 setup or a DB2 JDBC driver for a remote DB2 setup v WebSphere Application Server (32-bit version) DB2 software prerequisites Before you can install System Automation Application Manager, one of the following IBM DB2 UDB versions must be installed on the system on which System Automation Application Manager will run: v IBM DB2 Version 9.5, which is bundled with System Automation Application Manager, Version 3.1 v IBM DB2 UDB Enterprise Server Edition, Version or higher v For System Automation Application Manager on z/os: IBM DB2 UDB Version 8 or later Software prerequisites for a local DB2 setup If you are using a local DB2 setup, the end-to-end automation management database and the database tables are created by the installation program during the installation of System Automation Application Manager. Software prerequisites for a remote DB2 setup Before you can install the automation manager and the operations console, the following software prerequisites must be manually installed: 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 and the System Automation Application Manager installation program. 6 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

13 Supported Web browsers The operations console is the user interface of System Automation Application Manager. It is displayed in a Web browser that connects to the WebSphere Application Server on which the operations console is running. The Web browser can run on an arbitrary system. The following versions of Web browsers are supported: v Microsoft Internet Explorer V6.0 Service Pack 1 v Microsoft Internet Explorer V7.0 v Firefox 2.0.x v Firefox 3.0.x Web browsers other than Firefox and Internet Explorer are not supported. Other versions of Firefox and Internet Explorer than the versions listed above may work, but they are not supported. In particular there are known problems with Microsoft Internet Explorer V8.0. To generate and view reports using Tivoli Common Reporting, Mozilla or Firefox may give better results. For information about how the Web browser must be configured, see the IBM Tivoli System Automation Application Manager Administrator s and User s Guide, section Configuring your Web browser. Chapter 2. Required hardware and software 7

14 Hardware requirements The following sections describe the hardware requirements for System Automation Application Manager. Memory 1.5 GB is required on the server on which System Automation Application Manager is installed (for WebSphere Application Server and System Automation Application Manager). TCP/IP connectivity System Automation Application Manager consists of various components that can run on one or several systems, for example: v v When you use a local DB2 setup without WebSphere Application Server the automation manager, the operations console, and the DB2 server run on the same system (single-node setup). When you use a remote DB2 setup, or a local DB2 setup with WebSphere Application Server, System Automation Application Manager and the DB2 server run on separate systems (multi-node setup). Be sure that TCP/IP connections can be established between the following components: v the WebSphere Application Server that is running the automation J2EE framework, the resource adapters, and the operations console v the DB2 server Disk space requirements Disk space requirements on Windows systems The following table lists the disk space requirements for System Automation Application Manager on Windows systems. The table does not include the disk space that is required for the installation of the middleware software. Table 2. Disk space requirements on Windows systems Description Default directory Disk space System Automation Application Manager installation directory Automation manager and operations console deployed in WebSphere Application Server C:\Program Files\IBM\tsamp\eez C:\Program Files\IBM\WebSphere\AppServer 300 MB 50 MB DB2 database C:\DB2 120 MB Temporary disk space needed for installation and installation log and response files Configuration file directory and policy pool directory of System Automation Application Manager Tivoli Common Directory The value of the system variable %TEMP% Typically, this is: C:\Documents and Settings\Administrator\Local Settings\Temp C:\Program Files\IBM\tsamp\eez\cfg C:\Program Files\IBM\tsamp\eez\policyPool C:\Program Files\IBM\tivoli\common\eez 125 MB 1MB 250 MB 8 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

15 Table 2. Disk space requirements on Windows systems (continued) Description Default directory Disk space 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 disk space requirements for System Automation Application Manager on AIX and Linux systems.the table does not include the disk space that is required for the installation of the middleware software. Table 3. Disk space requirements on AIX and Linux systems Description Default directory Disk space Installation directory of System /opt/ibm/tsamp/eez 205 MB Automation Application Manager Automation manager and operations console deployed in WebSphere Application Server AIX: /usr/ibm/websphere/appserver Linux: /opt/ibm/websphere/appserver 30 MB DB2 database ~db2inst1 120 MB Temporary disk space needed for installation and installation log and response files /tmp 125 MB Configuration file directory and policy pool directory of System Automation Application Manager /etc/opt/ibm/tsamp/eez/cfg /etc/opt/ibm/tsamp/eez/policypool Tivoli Common Directory /var/ibm/tivoli/common/ 250 MB Installer registry /var/.com.zerog.registry.xml 5KB 1MB Chapter 2. Required hardware and software 9

16 Service See the IBM Tivoli System Automation Application Manager Installation and Configuration Guide for information about installing service for System Automation Application Manager. Fixes and problem-solving databases Information about fixes and service updates for this software can be found at the following Web site: Installing fix packs to obtain level To update System Automation Application Manager to level , you need to install WebSphere Application Server fixes and a product fix pack. Table 4 lists the archives you use for installing the WebSphere Application Server fixes. Table 4. WebSphere Application Server fixes archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAMW-WIN-FP0001.exe TIV-SAAMW-AIX-FP0001.bin TIV-SAAMW-I386-FP0001.tar TIV-SAAMW-PPC-FP0001.tar TIV-SAAMW-S390-FP0001.tar To install the WebSphere Application Server fixes, download and extract the archive for your platform. The extracted archive contains two directories Upgrade and Fixes. Use the UpdateInstaller located in the directory Upgrade to install all the fixes for the WebSphere Application Server, which are contained in the Fixes directory. If you are running System Automation Application Manager for z/os, then download and install the WebSphere Application Server fixes, which are in particular a new fix pack for the Integrated Solutions Console (ISC). Download the ISC fix pack from the following Web site: You upgrade the System Automation Application Manager to level by installing Fix Pack 1 on top of IBM Tivoli System Automation Application Manager The archives you use to install the fix pack are listed in Table 5. For a description of how to install fix packs, refer to the IBM Tivoli System Automation Application Manager Installation and Configuration Guide Before you start the installation, perform the following actions: 1. Make sure the WebSphere Application Server server1 has been stopped. 2. Make sure the Integrated Solutions Console server (ISC_Portal) has been stopped. 3. Stop the automation manager daemon by typing the following command: eezdmn -shutd. 4. On AIX, type the following command: /usr/sbin/slibclean. Table 5. System Automation Application Manager fix pack archives Platform Windows AIX Linux on System x Archive name TIV-SAAM-WIN-FP0001.exe TIV-SAAM-AIX-FP0001.bin TIV-SAAM-I386-FP0001.tar 10 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

17 Table 5. System Automation Application Manager fix pack archives (continued) Platform Linux on Power Systems Servers Linux on System z Archive name TIV-SAAM-PPC-FP0001.tar TIV-SAAM-S390-FP0001.tar When the installation of the fix pack has been finished, start the automation manager daemon by typing the following command: eezdmn -start Table 6. Automation adapter fix pack archives Platform AIX (HACMP adapter) Archive name TIV-SAAMA-AIX-FP0001.bin Installing fix packs to obtain level To update System Automation Application Manager to level , you need to install WebSphere Application Server fixes and a product fix pack. If you already installed level of System Automation Application Manager on the system, then the WebSphere Application Server fixes have already been installed with service for level If, however, the installed level of System Automation Application Manager is , then the WebSphere Application Server fixes need to be installed. Table 7 lists the archives you use for installing the WebSphere Application Server fixes. Table 7. WebSphere Application Server fixes archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAMW-WIN-FP0001.exe TIV-SAAMW-AIX-FP0001.bin TIV-SAAMW-I386-FP0001.tar TIV-SAAMW-PPC-FP0001.tar TIV-SAAMW-S390-FP0001.tar To install the WebSphere Application Server fixes, download and extract the archive for your platform. The extracted archive contains two directories Upgrade and Fixes. Use the UpdateInstaller located in the directory Upgrade to install all the fixes for the WebSphere Application Server, which are contained in the Fixes directory. If you are running System Automation Application Manager for z/os, then download and install the WebSphere Application Server fixes, which are in particular a new fix pack for the Integrated Solutions Console (ISC). Download the ISC fix pack from the following Web site: You upgrade the System Automation Application Manager to level by installing Fix Pack 2 on top of IBM Tivoli System Automation Application Manager or The archives you use to install the fix pack are listed in Table 8 on page 12. For a description of how to install fix packs, refer to the IBM Tivoli System Automation Application Manager Installation and Configuration Guide Before you start the installation, perform the following actions: 1. Make sure the WebSphere Application Server server1 has been stopped. 2. Make sure the Integrated Solutions Console server (ISC_Portal) has been stopped. 3. Stop the automation manager daemon by typing the following command: eezdmn -shutd. Chapter 2. Required hardware and software 11

18 4. On AIX, type the following command: /usr/sbin/slibclean. Table 8. System Automation Application Manager fix pack archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAM-WIN-FP0002.exe TIV-SAAM-AIX-FP0002.bin TIV-SAAM-I386-FP0002.tar TIV-SAAM-PPC-FP0002.tar TIV-SAAM-S390-FP0002.tar When the installation of the fix pack has been finished, start the automation manager daemon by typing the following command: eezdmn -start Table 9. Automation adapter fix pack archives Platform AIX (HACMP adapter) Archive name TIV-SAAMA-AIX-FP0002.bin Installing fix packs to obtain level Updating to System Automation Application Manager level requires the installation of WebSphere Application Server fixes and a product fix pack. Table 10 lists the archives you use for installing the WebSphere Application Server fixes. Table 10. WebSphere Application Server fixes archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAMW-WIN-FP0003.exe TIV-SAAMW-AIX-FP0003.bin TIV-SAAMW-I386-FP0003.tar TIV-SAAMW-PPC-FP0003.tar TIV-SAAMW-S390-FP0003.tar To install the WebSphere Application Server fixes, download and extract the archive for your platform. The extracted archive contains two directories Upgrade and Fixes. Use the UpdateInstaller located in the directory Upgrade to install all the fixes for the WebSphere Application Server, which are contained in the Fixes directory. If you are running System Automation Application Manager for z/os, then download and install the WebSphere Application Server fixes, which are in particular a new fix pack for the Integrated Solutions Console (ISC). Download the ISC fix pack from the following Web site: v v You upgrade the System Automation Application Manager to level by installing Fix Pack 3 on top of IBM Tivoli System Automation Application Manager , , or The archives you use to install the fix pack are listed in Table 11 on page 13. For a description of how to install fix packs, refer to the IBM Tivoli System Automation Application Manager Installation and Configuration Guide Before you start the installation, perform the following actions: 12 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

19 1. Make sure the WebSphere Application Server server1 has been stopped. 2. Make sure the Integrated Solutions Console server (ISC_Portal) has been stopped. 3. Stop the automation manager daemon by typing the following command: eezdmn -shutd. 4. On AIX, type the following command: /usr/sbin/slibclean. Table 11. System Automation Application Manager fix pack archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAM-WIN-FP0003.exe TIV-SAAM-AIX-FP0003.bin TIV-SAAM-I386-FP0003.tar TIV-SAAM-PPC-FP0003.tar TIV-SAAM-S390-FP0003.tar When the installation of the fix pack has been finished, start the automation manager daemon by typing the following command: eezdmn -start Table 12. Automation adapter fix pack archives Platform AIX (HACMP adapter) Archive name TIV-SAAMA-AIX-FP0003.bin Installing fix packs to obtain level Updating to System Automation Application Manager level requires the installation of WebSphere Application Server fixes and a product fix pack. Table 13 lists the archives you use for installing the WebSphere Application Server fixes. Table 13. WebSphere Application Server fixes archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAMW-WIN-FP0004.exe TIV-SAAMW-AIX-FP0004.bin TIV-SAAMW-I386-FP0004.tar TIV-SAAMW-PPC-FP0004.tar TIV-SAAMW-S390-FP0004.tar Do not install WebSphere Application Server 6.1 fix pack 25, because this makes SA AM unusable. To install the WebSphere Application Server fixes, download and extract the archive for your platform. The extracted archive contains the two directories Upgrade and Fixes. Use the UpdateInstaller in the directory Upgrade to install all the fixes for the WebSphere Application Server, which are contained in the Fixes directory. Installation of the ISC AE pak file ( WS-WASFeature-FEISCAE7105.pak) is only supported using the WebSphere Application Server Update Installer , which is included in the System Automation Application Manager deliverables. In particular, newer versions of the WebSphere Application Server Update Installer might not be able to successfully install the ISC AE update. If you are running System Automation Application Manager for z/os, you need to download and install the WebSphere Application Server fixes, which in particular is a new fix pack for the Integrated Solutions Console (ISC) from one the following Web sites: Chapter 2. Required hardware and software 13

20 v v You upgrade the System Automation Application Manager to level by installing Fix Pack 4 on top of IBM Tivoli System Automation Application Manager , , or The archives that you use to install the fix pack are listed in Table 14. For a description of how to install fix packs, refer to the IBM Tivoli System Automation Application Manager Installation and Configuration Guide Before you start the installation, perform the following actions: 1. Make sure that the WebSphere Application Server server1 and the Integrated Solutions Console server (ISC_Portal) have been stopped. 2. Stop the automation manager daemon using the following command: # eezdmn -shutd 3. On AIX, the following command needs to be executed after the automation manager daemon has been stopped and before the installation is started: # /usr/sbin/slibclean Table 14. System Automation Application Manager fix pack archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAM-WIN-FP0004.exe TIV-SAAM-AIX-FP0004.bin TIV-SAAM-I386-FP0004.tar TIV-SAAM-PPC-FP0004.tar TIV-SAAM-S390-FP0004.tar There are two new panels that are displayed during the installation of the SA AM fix pack that are not mentioned in the IBM Tivoli System Automation Application Manager Installation and Configuration Guide: User and group administration panel This panel allows you to manage whether your WebSphere installation allows user and group administration with its administrative interface, as follows: No Select No if user management is based on a read-only third-party repository, such as LDAP, and all the users have already been created as described in the IBM Tivoli System Automation Application Manager Installation and Configuration Guide. In this case, you must specify the Primary administrative user name that you created as the Was Admin User ID in the repository in step 18 of the installation sequence in the section Installing System Automation Application Manager using the installation wizard. Yes Select Yes if the users and groups are created using the WebSphere administrative interface. High Availability panel No Select No if the SA AM is not running in an HA environment. Yes Select Yes if the SA AM installation is for a node in an HA environment to skip the database-related update steps and proceed as described in the section Installing service in a setup for high availability of the IBM Tivoli System Automation Application Manager Installation and Configuration Guide. 14 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

21 After the installation of the fix pack has finished, start the automation manager daemon using the following command: # eezdmn -start Table 15. Automation adapter fix pack archives Platform AIX (HACMP adapter) Archive name TIV-SAAMA-AIX-FP0004.bin Installing fix packs to obtain level Updating to System Automation Application Manager level requires the installation of WebSphere Application server fixes and a product fix pack. The following table lists the archives you use for installing the WebSphere Application server fixes. Table 16. WebSphere Application Server fixes archives Platform Windows AIX Linux on System x Linux on Power Systems Servers Linux on System z Archive name TIV-SAAMW-WIN-FP0005.exe TIV-SAAMW-AIX-FP0005.bin TIV-SAAMW-I386-FP0005.tar TIV-SAAMW-PPC-FP0005.tar TIV-SAAMW-S390-FP0005.tar To install the WebSphere Application Server fixes, download and extract the archive for your platform. The extracted archive contains the two directories Upgrade and Fixes. Use the UpdateInstaller in the directory Upgrade to install all the fixes for the WebSphere Application server, which are contained in the Fixes directory. If you are running System Automation Application Manager for z/os you need to download and install the WebSphere Application server fixes, which is in particular a new fix pack for the Integrated Solutions Console (ISC) from one the following Web sites: v v You upgrade the System Automation Application Manager to level by installing Fix Pack 5 on top of IBM Tivoli System Automation Application Manager , , , or The archives you use to install the fix pack are listed in Table 17 on page 16. For a description of how to install fix packs, refer to the IBM Tivoli System Automation Application Manager Installation and Configuration Guide Before you start the installation, perform the following actions: 1. Make sure that the WebSphere Application Server server1 and the Integrated Solutions Console server (ISC_Portal) have been stopped. 2. Stop the automation manager daemon using the following command: # eezdmn -shutd 3. On AIX, the following command needs to be executed after the automation manager daemon has been stopped and before the installation is started: # /usr/sbin/slibclean Chapter 2. Required hardware and software 15

22 Table 17. System Automation Application Manager fix pack archives Platform Archive name Windows TIV-SAAM-WIN-FP0005.exe AIX TIV-SAAM-AIX-FP0005.bin Linux on System x TIV-SAAM-I386-FP0005.tar Linux on Power Systems Servers TIV-SAAM-PPC-FP0005.tar Linux on System z TIV-SAAM-S390-FP0005.tar After the installation of the fix pack has finished, start the automation manager daemon using the following command: # eezdmn -start Table 18. Automation adapter fix pack archives Platform AIX (HACMP adapter) Windows (MSCS adapter) Archive name TIV-SAAMA-AIX-FP0005.bin TIV-SAAMA-WIN-FP0005.bin 16 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

23 Chapter 3. Known problems and limitations HACMP adapter (hac.adapter) requires cluster.es.server.rte Affected System Automation Application Manager version: all versions Problem: The HACMP adapter (hac.adapter) can be installed even if cluster.es.server.rte, which is an optional HACMP file set, is not installed. This prerequisite is not enforced by the installation of the hac.adapter file set, and is not described in the installation chapter of the HACMP adapter. Solution: Ensure that cluster.es.server.rte is installed before installing the HACMP adapter. Activation of a new SA for Multiplatforms policy without resources for samadapter removes the policy for the samadapter and leaves the SA for Multiplatforms domain disconnected Affected System Automation version: All versions, all platforms Problem: Activating a new SA for Multiplatforms policy from the SA Application Manager Operations console that does not contain resources for the samadapter results in removing the resources for the samadapter and leaving the SA for Multiplatforms domain disconnected from the SA Application Manager Operations console. Solution: All SA for Multiplatforms policies that are activated from the SA Application Manager Operations console must have resources for the samadapter. When you create an SA for Multiplatforms policy with the policy editor, start with a policy that already contains the resources for the samadapter to ensure that those resources are already part of the SA for Multiplatforms policy. Distributed Disaster Recovery - Feature: HACMP policy may not have Failback option defined Affected System Automation version: n/a Problem: Discretionary workload in stretched HACMP clusters may not be defined with the Failback option in the HACMP policy. HACMP attempts to restart resources with the Failback option whenever a node is included, and ignores the desired state of the workloads. Solution: Do not define the Failback option in stretched HACMP clusters for Distributed Disaster Recovery. ISC cannot run with WebSphere Application Server or higher Affected System Automation version: , all platforms Problem: The ISC version , which is delivered with SA AM , does not work with WebSphere Application Server (SA AM is delivered with WAS ). Solution: Install SA AM 3.1 fix pack 1, which contains ISC , when installing a WebSphere Application Server fix pack higher than Installing WebSphere Application Server makes SA Application Manager unusable Affected System Automation version: All versions, all platforms Problem: The installation of fix pack 25 for WebSphere Application Server ( ) makes SA Application Manager unusable. Solution: System Automation Application Manager 3.1 fix pack 5 contains the fixes for this problem. Install the fix pack. Limitation: The box Event recording unavailable is not displayed if data of a SA z/os domain was selected for a report Affected System Automation version: z/os only, version 3.1 Limitation: The box Event recording unavailable is not displayed if data of a SA z/os domain was selected for a report. In SA z/os, event recording is dependent on whether the NetView Copyright IBM Corp

24 process is running. For this process no offline are recorded, only online events are, therefore no Event recording unavailable periods can be reported. Errors are reported for the report Startup and shutdown times for a selected resource Affected System Automation version: All 3.1 Problem: The Startup and shutdown times for a selected resource report shows: v Internal Server Error v No data available for the selected timespan, although data is available in the database This problem is caused by a combination of the following two circumstances: v The trace level for EEZReportingLogger is set to finest. v The database does not contain any recorded events for the selected resource itself or for one of the resources in the start/stop dependency tree of the selected resource. Solution: Set the trace level for EEZReportingLogger to INFO and rerun the report. If you need to enable tracing for this report, contact IBM support. Invalid exception shown in WebSphere FFDC files, indicating that file <EEZ_INSTALL_ROOT>/tcr/ lib/eezflaacb.jar does not exist Affected System Automation version: All 3.1 Problem: In the WebSphere FFDC log file directory, there may exist files with the following content: key = java.util.zip.zipexception com.ibm.ws.classloader.classloaderutils.adddependents 238 java.util.zip.zipexception: EDC5129I No such file or directory. (errno2=0x ) /SYSTEM/local/eez/tcr/lib/EEZFLAACB.jar Solution: This exception may be ignored. Known incompatibilities between WebSphere Portal 6.1 and ISC AE 7.1 used for SA Operations Console Affected System Automation version: All 3.1 Problem: Some functions of the SA Operations Console no longer work if WebSphere Portal 6.1 is installed into the same WebSphere Application Server that hosts the SA Operations Console. Solution: Contact IBM support if you plan to have such an environment to receive further instructions on required fix pack levels. Base Operations Console & Policy Editor The Desired State NoChange not available with System Automation Application Manager V3.1 Affected System Automation version: All 3.1 Problem: The online help of the Operations Console and the Policy Editor describes the new desired state with the value NoChange, but this is not available with SA Application Manager V3.1. Solution: The value cannot be specified and the description should be ignored. Common Event Infrastructure is not deployed on z/os Affected System Automation Application Manager version: z/os only, version Problem: With the upgrade of WebSphere to level the Common Event Infrastructure is not listed as a service in the WebSphere Administrator console. This is caused by a missing entry in the <WAS_HOME>/profiles/default/config/cells/csamX/nodes/nsamX/node-metadata.properties file. Solution: Locate the following entry in the <WAS_HOME>/profiles/default/config/cells/csamX/ nodes/nsamx/node-metadata.properties file: 18 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

25 com.ibm.websphere.deployed.features= com.ibm.ws.base_ , com.ibm.ws.express_ , com.ibm.ws.j2ee_ , com.ibm.ws.uddi_ , com.ibm.ws.wsgateway_ Change it to: com.ibm.websphere.deployed.features= com.ibm.ws.base_ , com.ibm.ws.express_ , com.ibm.ws.j2ee_ , com.ibm.ws.uddi_ , com.ibm.ws.wsgateway_ ,com.ibm.events.service_ Restart WebSphere Application Server. The end-to-end configuration tool (cfgeezdmn) supports only English when invoked in UI mode on z/os Affected System Automation Application Manager version: z/os only, version Problem: The end-to-end configuration tool (cfgeezdmn) supports only English when invoked in UI mode on z/os Solution: Ensure that the login shell is set to an English locale before starting the end-to-end configuration tool (cfgeezdmn) in UI mode on z/os. When using a non-english locale, the content of the title bar or the content of the various panels of the end-to-end configuration tool may show corrupted characters, or boxes instead of characters. In the Policy Editor, the fly-over helps are not translated but are only available in English Affected System Automation Application Manager version: z/os only, version Problem: In the Policy Editor, the fly-over helps are not translated but are only available in English. Solution: None. Report parameter headers are not displayed in browser locale Affected System Automation Application Manager version: All, version Problem: In the Tivoli Common Reporting dialogs, the report parameter headers are not displayed in the browser locale, but in the server locale of the WebSphere Application Server installation. Solution: None. CTGRW1000E An error occurred during a TCR data store request Affected System Automation Application Manager version: All, version Problem: After opening the Tivoli Common Reporting (TCR) UI for the first time after a WebSphere restart, a red error message box appears with the following text: CTGRW1000E An error occured during a TCR data store request Solution: Click Ok on the error message, close the TCR UI and open it again. Note: During the closing procedure the following Javascript error message might appear: "RPC Error: XMLHttpTransport Error: 0" You can ignore this and simply close it. These error messages do not affect the behavior of the TCR UI after it has been closed and reopened. SA Application Manager discovery library adapter may fail to create a discovery book after the end-to-end automation domain has been renamed Chapter 3. Known problems and limitations 19

26 Affected System Automation version: All Problem: When you choose to change the name of the end-to-end automation domain, both the new domain name and the previous domain name remain visible in the end-to-end automation domain topology as a domain with the status domain offline (a gray icon in the operations console). This previous domain remains until it is removed automatically. By default, the cleanup interval is 48 hours. When there are two end-to-end domains in the domain topology tree, the discovery library adapter fails to create a discovery book because it tries to contact both end-to-end domains and receives an exception for the domain that is offline (message EEZJ0019E). This exception causes the discovery library adapter to stop altogether. Solution: To recover from this situation, modify the domain removal interval as described in the IBM Tivoli System Automation Application Manager Administrator s and User s Guide, Appendix D: Troubleshooting, Section Resolving timeout problems, subsections Database clean-up timeout for automation domains and Modifying the environment variables for the automation J2EE framework. For example, set the variable com.ibm.eez.aab.domain-removal-hours to 1 hour and restart WebSphere Application Server. After a short time, the domain that is offline is removed from the domain topology tree and the discovery library adapter can be used again. Installer cannot detect non-default SOAP port Affected System Automation version: All Problem: If the default SOAP port settings are changed in the WebSphere Administrator Console, the installer cannot detect this, causing an error panel to be displayed with the message that the cell could not be retrieved. Changing the SOAP port using the WebSphere Administrator Console does not update the SOAP port for the wsadmin.sh command. This causes all commands that use wsadmin.sh and a SOAP connection to fail. Solution: A workaround for this problem is to manually edit the file /opt/ibm/websphere/ AppServer/profiles/AppSrv01/properties/wsadmin.properties and change the value of com.ibm.ws.scripting.port=. However, there is an official way to properly change the default ports of WebSphere using an Ant script. See the official WebSphere manual or information center for further information. In the information center, search for the item Updating ports in an existing profile. Using the Ant script does not have this limitation because it correctly updates the SOAP port for wsadmin.sh. Resetting a resource reference from a unrecoverable error fails with a NullPointerException Affected System Automation version: All Problem: Resetting a resource reference that is in the operational state NonRecoverableError fails. When a reset is triggered either by pressing the button in the Operations Console or by the Command Shell command resetres, a NullpointerExecption occurs in the Automation Engine and the reset is not performed. Solution: Reset the referenced resource rather than the resource reference. In the Operations Console, navigate to the referenced resource and use the reset button that is provided there. In the Command Shell, reset the referenced resource by the resetres command. Only the first 20 files are displayed in policy editor policy pool Affected System Automation Application Manager version: All versions on all platforms Problem: The policy editor only displays 20 files when exploring the policy pool, even if there are more then 20 policy files in that directory. Solution: Manually check the policy pool directory and delete any policy files that you no longer need from the directory or move older policy files to another directory for archiving. Potential WebSphere Application Server security risk Affected System Automation Application Manager version: All versions on all platforms using WebSphere Application Server 6.1 with FP lower than IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

27 Problem: See &dc=d600&uid=swg &loc=en_us&cs=utf-8&lang=en Solution: Download and install either the interim fix or the WebSphere Application Server 6.1 FP23 (recommended) as advised in the above document. System Automation Application Manager does not start in a high availability setup Affected System Automation version: All versions, Linux only Problem: The setup of the System Automation Application Manager high availability solution with System Automation for Multiplatforms may fail, because the script eezwasctrl-as sets an ulimit value for the number of open files that is too high. Since the script is used to control start and stop of WebSphere Application Server, System Automation Application Manager cannot be started. Solution: Modify the script on all nodes of the System Automation Application Manager high availability cluster. Change the line ulimit -n 9999 to ulimit -n Documentation update The following text describes how to navigate to the manage users task in the navigation tree. It is to be added at the start of the subsection Creating and authorizing users from the Integrated Solutions Console on AIX, Linux and Windows, in Creating and authorizing users to work with Tivoli System Automation in the chapter Managing users in IBM Tivoli System Automation Application Manager Administrator s and User s Guide. The task for creating and modifying users for the Integrated Solutions Console that hosts the Operations Console, the Policy Editor and the Tivoli Common Reporting UI is a management task that is provided by the WebSphere administrative console. To manage users perform the following steps: 1. Log on to the system that you installed the System Automation Application Manager on. 2. Ensure that the WebSphere Application Server instance that is hosting the Automation J2EE framework is running. 3. Open your Web browser and connect to the Websphere Administrative Console that is hosted by the Integrated Solutions Console. 4. On the Login panel of Integrated Solutions Console, enter any administrative WebSphere User ID and password (for example, wasadmin). 5. In the navigation tree in the left view, All tasks, click Users and Groups > Manage Users. Note: The first administrative user ID that is created during installation of SA Application Manager (the default is eezadmin ) is a special user ID that should be handled very carefully. Apart from any additional user ID that you create as required for operators and administrators in your environment, this eezadmin user ID is also a technical user ID that is used to start various components of the SA J2EE Framework. If you change this ID or its password here, some internal components of the SA J2EE framework might fail to start. For more information about how to work with these dialogs see the WebSphere Application Server documentation. Chapter 3. Known problems and limitations 21

28 22 IBM Tivoli System Automation Application Manager 3.1 Release Notes (December 2009)

29 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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user s responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement 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 be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department LJEB/P South Road Road Poughkeepsie, New York U.S.A. Copyright IBM Corp