Readme for IBM WebSphere Process Server Fix Pack V6.0.1.1 Product readme Abstract Readme documentation for V6.0.1.1 WebSphere Process Server product, including installation-related instructions, prerequisites, highlights, and known issues. Content IBM WebSphere Process Server, Version 6.0.1 Fix Pack 1 (V6.0.1.1) Table of Contents About Fix Pack 1 Change History Fixes Prerequisites Space requirements Steps for installing Fix Pack 1 Known issues Additional information Finding the Readme file for the Update Installer Trademarks and service marks Compilation date: 2006/03/20 Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. About Fix Pack 1 There are several cumulative fixes that are bundled into a single maintenance package for a specific combination of product and platform. Each maintenance package is referred to as V6.0.1. Installing Fix Pack 1 with the Update Installer raises the fix level of your product to V6.0.1.1. See the installation instructions in the Steps for installing Fix Pack 1 section for more information. Fix packs can be downloaded from the V6.0.1 download page. Back to top Change History Release date: 30 March 2006 30 March 2006: Published Back to top WebSphere Process Server and WebSphere Enterprise Service Bus Fixes: JR22713 WAS Common DB install problem with Oracle JR22950 Validator gives error using inherited attr as keys JR22954 Business Process export using SOAP JMS export causes exception JR23057 Cannot modify failed event before resubmitting to a BPEL JR23059 Build time errors with WebServices binding JR23154 WPS wizards needed for dynamic clusters JR22957 NullPointerException during multiple access IY79366 Using Oracle 10g with the OCE driver for BPEDB IY80287 SQL Activity does not support JDBC syntax IY81140 ClassCastException occurs during inter module test IY80791 Processing tel URL in reference in task Included WebSphere Application Server Fixes: PK18885 Backport 313498 and 313498.1 to WAS602.SERV1 PK17894 CTS:MarshallComplexTypesTests failing with faultcode exp PK19782 NotSerializableException: WebServicesFaultAlternateContent PK19923 ConcurrentModificationException in WLM PK20484 WESB server, in a cluster, fails to recover from failure PK19905 PROBLEM WITH JDBC MEDIATOR IN WAS 6.0.2.1: DBEXCEPTION PK16700 Got exception when start adapter module PK19617 Def.getServices doesn't return imported services. Back to top Prerequisites Install the fix pack V6.0.1.1 on top of WebSphere Process Server version 6.0.1. All required hardware and software prerequisites are described in the Supported hardware and software Web site. Back to top Space requirements Space requirements vary depending on what you are installing. The size of each download is available on the Support site. For a fix pack, you need approximately 600 MB of free space in the system temporary directory (typically /tmp on a Linux or UNIX system) and another 600 MB in the file system that hosts the WebSphere Process Server image (typically /usr or /opt on a Linux or UNIX-based platform), or approximately 1.2 GB of free space on the disk drive where you are installing on a Windows platform. Verify that the free space is available before beginning the installation. Space is also required for the install_root/updateinstaller directory. The space required is about the same as the size of the fix pack and other included fixes, typically somewhere between 25 MB to 750 MB. Space is also required for backup files in the install_root/properties/version/update/backup directory. The space required is about the same as the size of the fix pack, somewhere between 25 MB to 750 MB, varying by product and platform. For more information, see the disk space requirements for the Update Installer. Back to top Steps for installing Fix Pack 1 1. Install the V6.0.1 product from the appropriate compact disc or distribution media. You most likely already have installed the product and are updating an existing system. 2. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations in the online information center. 3. IMPORTANT: Back up and delete any older copy of the Update Installer before downloading the current Update Installer. To use a newer version of the Update Installer, you must first remove the older version. a. Back up any files and subdirectories in the install_root/updateinstaller/maintenance directory, if necessary. b. Delete the install_root/updateinstaller/maintenance directory and all of its subdirectories. 4. Verify required disk space, as described in the readme file for the maintenance package. 5. After backing up the configuration and before installing V6.0.1, stop all Java processes that use the IBM Developer Kit that WebSphere Process Server provides to support the Java 2 SDK that IBM provides for WebSphere Process Server products. 6. Stop all process server processes, the nodeagent process, the deployment manager process, and all server processes that belong to serviceable products, such as the IBM HTTP Server. Stop all Java processes, if necessary. The product might not continue to run successfully if you install V6.0.1 while a WebSphere Process Server-related Java process is running. 7. Obtain the V6.0.1.1 downloadable package that you need from the product support Web site. Download the package into a temporary disk location. 8. Unzip the package into the install_root directory. This process unpacks the downloaded package automatically into the install_root/updateinstaller directory and several subdirectories, including the maintenance subdirectory. For example, unzip a maintenance package with the following command: cd /opt/IBM/WebSphere/ProcServer unzip /tmp/downloads/6.0.1-WS-WPS-ESB-AixPPC32-FP0000001.zip The V6.0.1.1 downloadable package contains both the Update Installer and the actual V6.0.1.1 maintenance package, and a number of required WebSphere Application Server maintenance packages. The V6.0.2.6 Update Installer for WebSphere Software is in the install_root/updateinstaller directory. The maintenance package is in the install_root/updateinstaller/maintenance directory. 9. Check the Recommended updates page to see if the Update Installer has been updated since the V6.0.1 file was created. If so, download and unpack the new Update Installer into the installation root directory to replace the Update Installer files that are in V6.0.1. 10. (Optional) Delete the ZIP file if you need more space. 11. Open a command shell window and change directories to the install_root/updateinstaller directory of the product that you are updating. cd install_root/updateinstaller Use the following command to clone the Java 2 Software Development Kit (SDK) that the product uses, so that you can update the original SDK when you install the maintenance package: Note: This step can be omitted if you have previously performed it. To check if you have performed this step before, look for the existence of the java directory inside the updateinstaller directory. For Windows: update -silent -W maintenance.package=\maintenance\6.0.2-WS-WAS-WinX32-FP0000007.pak relaunch.active=false For UNIX platforms, for example for AIX: ./update -silent -W maintenance.package=\maintenance\6.0.2-WS-WAS-AixPPC32-FP0000007.pak relaunch.active=false 12. Using the same command shell, begin the update. Use the update command to install the maintenance packages that you downloaded and unpacked: Here is the order in which the maintenance packages should be installed (these will vary by OS): 6.0.2-WS-WAS-WinX32-FP0000007.pak (WebSphere Application Server V6.02 Fix Pack 7) The 8 included WebSphere Application Server iFixes: 6.0.2.7-WS-WAS-IFPK18885.pak PK17894_6027.pak 6.0.2.7-WS-WAS-IFPK19782.pak 6.0.2.7-WS-WASND-IFPK19923.pak 6.0.2.7-WS-WAS-IFPK20484.pak 6.0.2.7-WS-WAS-IFPK19905.pak 6.0.2.7-WS-WAS-IFPK16700.pak 6.0.2.7-WS-WAS-IFPK19617.pak 6.0.1-WS-WPS-ESB-WinX32-FP0000001.pak (WebSphere Process Server V6.0.1 Fix Pack 1) For each maintenance package do the following: For Windows: update -silent -W maintenance.package=\maintenance\6.0.2-WS-WAS-WinX32-FP0000007.pak For UNIX platforms, for example for AIX: ./update -silent -W \ maintenance.package=./maintenance/6.0.2-WS-WAS-AixPPC32-FP0000007.pak Or, issue the update command without a parameter to start the graphical user interface: For Windows: update For UNIX platforms: ./update Refer to the install_root/updateinstaller/docs/readme_updateinstaller.html file for detailed information about using the update command. Back to top Known issues Stop all WebSphere Application Server-related Java processes before using the Update Installer for WebSphere Software Read the following technote for more information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21199141 Refer to the Readme file for the Update Installer for workarounds to the following known problems: Problem Product uninstall does not remove the updated product correctly Relaunch action for SDK updates does not relaunch the update installer This is a known problem on some HP-UX systems. Always use the most current version of the Update Installer for WebSphere Software to install maintenance packages Control returns prematurely to the command line when the Update Installer rolls back an updated IBM Software Development Kit (SDK). The Update Installer fails to relaunch after copying the IBM Software Development Kit (SDK) if not enough disk space is available for installation Non-root profiles start with an error after installing V6.0.2 Problem in cloning the SDK for updates to the product SDK Profile update and undo scripts are limited to SBCS and to characters without pronunciation keys due to operating system limitations Profiles can exist at the V6.0.2 level after rolling back V6.0.2 Back to top Additional information You can find additional information in the WebSphere Process Server Information Center. For additional information, see also the Recommended Updates page and the IBM update strategy for WebSphere Application Server V6.0 release page. Back to top Finding the Readme file for the Update Installer See the online Readme file for the Update Installer for more information. After unpacking V6.0.1.1, a copy of the readme file is available as the install_root/updateinstaller/docs/readme_updateinstaller.html file. However, the online version is updated periodically while the bundled local copy is not. The information in the readme file is also available in the WebSphere Process Server Information Center. The information center version and the online techdoc are synchronized periodically. Back to top Trademarks and service marks For trademark attribution, visit the IBM Terms of Use Web site.