################################################################## Copyright (C) 2005 IBM Corp. - All Rights Reserved. IBM makes no representations or warranties about the suitability of this program, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. ################################################################## WEBSPHERE PRODUCT CENTER INTERIM FIX 5.2.0-IF003 ======================== 1. ABOUT THIS INTERIM FIX 2. INTERIM FIX REQUIREMENTS 3. LIST OF INTERIM FIXES 4. INSTALLATION ======================== 1. ABOUT THIS INTERIM FIX ========================= This document provides details on Interim Fix 5.2.0-IF003 on the following platform: WebSphere Application Server / DB2 2. INTERIM FIX REQUIREMENTS ========================== Websphere Product Center 5.2.0 must be installed prior to the application of Interim Fix 5.2.0-IF003: It is recommended to apply the Interim Fix to a test system to identify any issues. 3. LIST OF INTERIM FIXES ======================== This Interim fix includes the fixes for: - the APAR JR21580 (PMR 88443,49R,000 : WPC00018395 - MF - Unpredictable Workflow Behavior). - the APAR JR21770 (PMR 01488,49R,000 : WPC00018419 - Scheduler: minute time becomes corrupted for "At minute intervals" schedules). 4. INSTALLATION ================== This section provides general guidelines to apply a Fix Pack to WebSphere Product Center. Some information may differ depending on the methods used for previous installations. Contact your support representative for WebSphere Product Center with any installation issues. 4.1 Preparation Before attempting to apply the latest Fix Pack to WebSphere Product Center, the following preparation is recommended: 4.1.1 Stopping the whole application on the local machine Complete the following steps to stop the WebSphere Product Center instance: a) Check the scheduler to make sure there are no critical jobs that need to be completed. If the queue is clear, kill the scheduler manually by running the following script: $TOP/bin/go/stop/stop_scheduler.sh b) Abort the entire application by running the following script: $TOP/bin/go/abort_local.sh All services running on the local machine is aborted. The RMI registry is aborted. Note: Check to make sure all processes have stopped using the 'ps' command. Kill off any rogue "java" or "rmiregistry" processes that remain after shutting down the instance. Occasionally, it may take several attempts to kill off all java processes. Continue killing all java processes until they are all dead. 4.1.2 Backup a) Create a full backup of the current WebSphere Product Center directories before applying the Fix Pack. The Fix Pack will overwrite files that have changed. If any issues occur, the backup will allow a rollback to a previous version b) It is recommended to apply the Fix Pack to a test system to identify any issues before applying the Fix Pack to a production system c) Perform a full backup of the database before applying the Fix Pack to a production system Note: Do not delete the old WebSphere Product Center version until performing thorough testing with the new installation. 4.1.3 Delete Tomcat working directory For configurations using Tomcat, delete the Tomcat working directory using the following command: rm -rf $TOP/etc/default/tomcat33/webapps/ccd Once the working directory has been deleted, restart the application server and apply the Fix Pack. 4.2 Apply Fix Pack To apply the Fix Pack to WebSphere Product Center, complete the following tasks: a) Unpack tar file b) Run WebSphere Application Server script c) Update configuration files d) Test installation 4.2.1 Unpack tar file Purpose: To extract and update any new installation files into the current working directory Note: GNU tar is needed to untar the WebSphere Product Center files. 1. Copy the WebSphere Product Center tar file to the user or temporary directory. Example: {HOME_OF_WPC}/tarballs 2. CD to $TOP, the current working directory, and unpack the tar file: Example: Using GNU tar, the following command extracts and unzips the tar file using an absolute path: tar zxvf /home/WPC/tarballs/wpc_5001_03_fixpak_from_5000_15_was5_db2.tgz 4.2.2 Run WebSphere Application Server script After unpacking the tar file in the previous section, ensure that the default server (server1) is running and run the following WebSphere Application script: $TOP/bin/websphere/install_war.sh Note: Ensure that the default server (server1) is running, as it is required for the WebSphere Application Server script to work. If needed, start the WAS default server by issuing the following command as root: ${WAS_HOME}/bin/startServer.sh server1 4.2.3 Verify configuration files Verify all configuration files required by the new installation and make any updates as needed. Refer to the backup copy of the configuration files for the previous installation if needed. * common.properties * admin_properties.xml * init_ccd_vars.sh common.properties On startup, the system will use this file to read in all system level parameters. This file includes settings for the database layer (connection parameters), directory settings, default character sets, thread-pooling parameters, and other settings, which are documented in the file. File location: $TOP/etc/default admin_properties.xml This file is used by the administrative utilities to configure clusters of the application. File location: $TOP/etc/default init_ccd_vars.sh The initialization file is the shell script that initializes the shell variables used by the system. File location: $TOP/setup 4.3 Test installation 4.3.1 Start WebSphere Product Center To start the WebSphere Product Center, execute the following script: $TOP/bin/go/start_local.sh The script starts all the services needed to run WebSphere Product Center. Note: This process should take approximately 30-40 seconds, depending on the speed of the processor. 4.3.2 Check status Run the $TOP/bin/go/rmi_status.sh script that was provided by WebSphere Product Center and verify the following services have started correctly. * admin_ * appsvr_ * eventprocessor * queuemanager * scheduler * workflow YOU HAVE SUCCESSFULLY APPLIED THE INTERIM FIX FOR WEBSPHERE PRODUCT CENTER!