Usage and Accounting Manager (TUAM) UNIX/Linux and Windows Installation Readme © Copyright International Business Machines Corporation 2008. All rights reserved. Note: The full set of documentation including installation documentation can be found at the IBM(R) Tivoli Usage and Accounting Manager Information Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/welcome.htm Contents 1.0 Upgrading Tivoli Usage and Accounting Manager Enterprise Edition or Tivoli Usage and Accounting Manager Virtualization Edition to Fixpack 1 (7.1.0.8) 1.1 Upgrade Files 1.2 Upgrade Notes 1.3 Running the Upgrade 1.4 Upgrade Problems 2.0 Upgrading Tivoli Usage and Accounting Manager Enterprise Collector Pack to Fixpack 1 (7.1.0.8) 2.1 Upgrade Files 2.2 Upgrade Notes 2.3 Running the Upgrade 2.4 Upgrade Problems 3.0 DB2 JDBC driver information for Tivoli Usage and Accounting Manager Fixpack 1 (7.1.0.8) 3.1 Minimum requirements for DB2 JDBC driver have changed 3.2 Where to get an updated DB2 JDBC driver 4.0 Tivoli Usage and Accounting Manager Fixpack 1 (7.1.0.8) data source schema changes 4.1 Tivoli Usage and Accounting Manager now requires the Object Prefix value to be specified on the Data Source Maintenance page for DB2 and Oracle. 5.0 Tivoli Usage and Accounting Manager Fixpack 1 (7.1.0.8) database upgrade 5.1 The Tivoli Usage and Accounting Manager database version should be upgraded before you start using Usage and Accounting Manager Fixpack 1 (7.1.0.8). 6.0 Notices and Trademarks 1.0 Upgrading Tivoli Usage and Accounting Manager Enterprise Edition or Tivoli Usage and Accounting Manager Virtualization Edition to Fixpack 1 (7.1.0.8) 1.1 Upgrade Files The Enterprise Edition (EE) installation archive includes the following files: Windows: setup-tuam-ee-7-1-0-8-fp1-{platform}.exe v9fp2_ALL_LANG_setup_{bits}.exe, where {bits} is either 32 or 64 setup-tuam-wpc-7-1-0-8-fp1-windows_32_64.exe tuam_win.rsp readme.txt Non-Windows: setup-tuam-ee-7-1-0-8-fp1-{platform}.bin setup-tuam-wpc-7-1-0-8-fp1-windows_32_64.exe tuam_unix.rsp readme.txt For a Virtualization Edition (VE) install, the list is the same, except that the executable is "-ve-" instead of "-ee-". 1.2 Upgrade Notes 1.2.1 The "General Availability/Base" version (GA: 7.1.0.7) of the Tivoli Usage and Accounting Manager (VE, EE, and/or ECP) products must be installed before an upgrade of the products can be done. If the "Base" or "GA" version of the product is not installed, the upgrade will display a message that it cannot continue. 1.2.2 For a Windows upgrade, if Windows Web Reporting is selected, the following prerequisite is required: Microsoft IIS The installer will not proceed unless this prereq is installed. The necessary prereq installer can be found on the Windows Operating System CD. 1.2.3 Linux upgrades will not start if Security Enhanced (SE) is enabled. Choose one of these two workarounds to get past this issue: Workaround A: Disable SE while upgrading Tivoli Usage and Accounting Manager 1. Disable SE 2. Reboot 3. Upgrade Tivoli Usage and Accounting Manager 4. Enable SE 5. Reboot Workaround B: Install the IBM 1.5 JVM before upgrading Tivoli Usage and Accounting Manager 1. Download the IBM 1.5 JVM RPM image from IBM: http://www.ibm.com/developerworks/java/jdk/index.html 2. Install the Java Virtual Machine (JVM) rpm -i ibm-java2-i386-jre-5.0-5.1.i386.rpm (this is the Intel 32-bit image name) 3. Upgrade Tivoli Usage and Accounting Manager 4. Optionally, uninstall the IBM 1.5 JVM if you do not want the virtual machine on your system. 1.2.4 The file setup-tuam-wpc-7-1-0-8-fp1-windows_32_64.exe contains the Tivoli Usage and Accounting Manager Windows Process Collector installer. It is not run as part of the EE upgrade, but rather it is copied to the Tivoli Usage and Accounting Manager install directory (TUAM_HOME) so that it can be deployed to Windows-based systems and run later. For this reason, it is included in both Windows and non-Windows archives. 1.3 Running the Upgrade Launch the installer by invoking the executable: setup-tuam-ee-7-1-0-8-fp1-{platform}.exe on Windows setup-tuam-ee-7-1-0-8-fp1-{platform}.bin on non-Windows Response files (tuam_win.rsp and tuam_unix.rsp) for the installers are located in the same directories as their respective upgrade executables. Each parameter is thoroughly documented in the response file. The response files can be used for GUI, console, and silent upgrades. To use the options file with the installer, specify -options as a command argument to the upgrade executable, where is the name of this options file and "executable" is the name of the Tivoli Usage and Accounting Manager installer's executable file. Examples: To load the GUI based upgrade with response file options: executable -options To run the console upgrade with these response file options: executable -options -console To run the silent upgrade with these response file options: executable -options -silent -V licenseAccepted=true Note: The ISMP "-options-record" and "-options-template" parameters are not valid for the Tivoli Usage and Accounting Manager installers and will not create valid response files. 1.4 Upgrade Problems Problems encountered during the upgrade are documented in the install log files, located in the Tivoli Common Directory: Windows: C:\Program Files\ibm\tivoli\common\AUC\logs\install Non-Windows: /opt/ibm/tivoli/common/AUC/logs/install 2.0 Upgrading Tivoli Usage and Accounting Manager Enterprise Collector Pack to Fixpack 1 (7.1.0.8) 2.1 Upgrade Files The Enterprise Collector Pack (ECP) installation archive includes the following files: Windows: setup-tuam-ecp-7-1-0-8-fp1-{platform}.exe readme.txt Non-Windows: setup-tuam-ecp-7-1-0-8-fp1-{platform}.bin readme.txt 2.2 Upgrade Notes There are currently no special notes for the ECP upgrade. 2.3 Running the Upgrade Launch the upgrade by invoking the executable: setup-tuam-ecp-7-1-0-8-fp1-{platform}.exe on Windows setup-tuam-ecp-7-1-0-8-fp1-{platform}.bin on non-Windows There are no response file options for the ECP upgrade. The upgrade can be run in GUI, console, or silent mode. Examples: To run the GUI based upgrade: executable To run the console based upgrade: executable -console To run the silent upgrade: executable -silent 2.4 Upgrade Problems Problems encountered during the ECP upgrade are documented in the install log files, which are in the Tivoli Common Directory: Windows: C:\Program Files\ibm\tivoli\common\AUC\logs\install Non-Windows: /opt/ibm/tivoli/common/AUC/logs/install 3.0 DB2 JDBC driver information for Tivoli Usage and Accounting Manager Fixpack 1 (7.1.0.8) 3.1 Minimum requirements for DB2 JDBC driver have changed The minimum DB2 JDBC driver (db2jcc.jar) version is now 2.8.46. If your current version of the DB2 JDBC driver is below the 2.8.46 version, the Tivoli Usage and Accounting Manager Administration console will display a message that shows the current version of the DB2 JDBC driver, as well as the required minimum version of the driver. The Tivoli Usage and Accounting Manager trace.log file (in your /logs/server directory) will also log a "JDBC driver version" message. You will not be able to connect to the Tivoli Usage and Accounting Manager DB2 database until the DB2 JDBC driver is upgraded. 3.2 Where to get an updated DB2 JDBC driver 3.2.1 Download the driver from the IBM DB2 Express-C Site. An updated DB2 JDBC driver can be downloaded from the following site: http://www-306.ibm.com/software/data/db2/express/download.html You must log in to this site using your IBM user ID and password, or you can register for an IBM User ID and password if you do not currently have one. 3.2.2 Locate the file to download. Once you are logged in to the above site, search for "JDBC", then download and unzip the IBM Data Server Driver for JDBC and SQLJ zip file. 3.2.3 File replacement options: You can either back up your original db2jcc.jar file and use the unzipped db2jcc.jar file in its place (that is, put the updated db2jcc.jar file in the same directory as the original db2jcc.jar file) or you can configure Tivoli Usage and Accounting Manager and your system's CLASSPATH environment variable to point to the new location of the db2jcc.jar file you just unzipped. 1. If you choose to put the new db2jcc.jar file in the same location as the old: a. Back up your original db2jcc.jar file and use the unzipped db2jcc.jar file in its place. b. Stop and restart the Tivoli Usage and Accounting Manager server so that it begins using the new db2jcc.jar file. 2. If you choose to put the new db2jcc.jar file in a different location from the old: Configure Tivoli Usage and Accounting Manager and your system's CLASSPATH to point to the (new) location of the updated db2jcc.jar file: a. Remove the db2jcc.jar file path from the Tivoli Usage and Accounting Manager Configuration--Drivers page: Usage and Accounting Manager -> System Maintenance -> Configuration -> Drivers b. Stop the Tivoli Usage and Accounting Manager Server. One way to do this is to change to the Tivoli Usage and Accounting Manager install directory (TUAM_HOME). Then change to the \ewas\bin directory and run the following command: Linux and UNIX: ./stopServer.sh server1 Windows: stopServer.bat server1 c. Update your system's "CLASSPATH" environment variable. Update the CLASSPATH environment variable so that the path to the new db2jcc.jar file is in front of any other db2jcc.jar file. For example, if the new db2jcc.jar file is in your C:\db2JDBC directory (on Windows), you should add the following information to the front of your system's CLASSPATH: C:\db2JDBC\db2jcc.jar Similarly, if your Linux or UNIX system has a CLASSPATH environment variable set, and you put the new db2jcc.jar file in a directory named "/data/db2JDBC", you should add the following information to the front of your system's CLASSPATH: /data/db2JDBC/db2jcc.jar d. Start the Tivoli Usage and Accounting Manager server. One way to do this is to change to the Tivoli Usage and Accounting Manager install directory (TUAM_HOME). Then change to the \ewas\bin directory and run the following command: Linux and UNIX: ./startServer.sh server1 Windows: startServer.bat server1 e. Configure Tivoli Usage and Accounting Manager to use the new db2jcc.jar file. Log back on to the Tivoli Usage and Accounting Manager Administration console and add the path of the new db2jcc.jar file to the Configuration--Drivers page. 4.0 Tivoli Usage and Accounting Manager Fixpack 1 (7.1.0.8) data source schema changes 4.1 Tivoli Usage and Accounting Manager now requires the Object Prefix value to be specified on the Data Source Maintenance page before Usage and Accounting Manager can successfully connect to a DB2 or Oracle database. When you upgrade Tivoli Usage and Accounting Manager and select to view the Configuration panel Usage and Accounting Manager -> System Maintenance -> Configuration a message similar to the following might be displayed: The data source Object Prefix and the current schema reported by the database do not match. The data source Object Prefix is set to ' ' while the current database schema is 'DB2ADMIN. '. The data source Object Prefix and the database schema must match exactly... " This can occur if you originally configured your Tivoli Usage and Accounting Manager data source without specifying a value in the Object Prefix field. To fix this problem: 1. View your Tivoli Usage and Accounting Manager database and its tables. 2. Find the schema name listed next to the database tables that have names starting with "CIMS". 3. Open the Tivoli Usage and Accounting Manager Data Source Maintenance page: Usage and Accounting Manager -> System Maintenance -> Data Sources ->