*************************************************************** (c) Copyright 2000, 2002 International Business Machines Corp. All rights reserved. *************************************************************** Welcome to IBM WebSphere Application Server Version 4.0 FixPak 5. Use this FixPak to upgrade the WebSphere Application Server, the J2EE Client, the J2EE Thin Client, the J2C (Connector Architecture for WebSphere Application Server), and the IBM HTTP Server. This readme file covers the FixPak install and uninstall for both Advanced Edition and Advanced Single Server Edition products on AIX, HP-UX, Linux, Solaris, Windows NT, and Windows 2000. This README contains information about: * Finding additional information * Prerequisites * Space requirements * Retrieving FixPak 5 * Installing FixPak 5 * Uninstalling FixPak 5 FINDING ADDITIONAL INFORMATION ------------------------------ In addition to this README file, see the Version 4.0 InfoCenter: http://www.ibm.com/software/webservers/appserv/infocenter.html See the InfoCenter for: * Release Notes for Version 4.0.5 * Release Notes for Version 4.0.4 * Release Notes for Version 4.0.3 * Release Notes for Version 4.0.2 * Release Notes for Version 4.0.1 * README for Version 4.0.1 base The above documents are also available from the InfoCenter site map. Please note particular issues in regard to the security file 'java.policy', and, for a Single Server Edition product, in regard to the handling of server configuration files ('server-cfg.xml', 'template-server-cfg.xml' and 'admin-server-cfg.xml'. PREREQUISITES ------------- FixPax 5 is cumulative containing all the updates/fixes since 4.0.1. Install this FixPak on top of the IBM WebSphere Application Server Version 4.0.1 base or on top of the IBM WebSphere Application Server Version 4.0.2 or 4.0.3 or 4.0.4. FixPak 5 expands the list of supported product prerequisites. See the following Web site for details: http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html A java runtime environment must be available both for an installation operation and for a restoration operation, even if the java installation is not being updated. SPACE REQUIREMENTS ------------------ The FixPak installation program requires some temporary space, approximately 110 MB. After it is installed, the FixPak 5 code increases the IBM WebSphere Application Server installation and runtime footprints by a small amount. RETRIEVING FixPak 5 FOR AIX, HP-UX, LINUX, AND SOLARIS (ADVANCED EDITION) ----------------------------------------------------------------------- 1. Obtain the tar was40_ae_ptf_5_(Platform) from the product Web site: http://www.ibm.com/software/webservers/appserv/support.html Download the file into an empty directory on the machine on which you plan to install the FixPak. For example, download the file to /tmp directory. 2. At a system command prompt, change the directory to where you downloaded the file, for example: # cd /tmp 3. Untar or unzip the file. For untarring: # tar -xvf was40_ae_ptf_5_(Platform).tar RETRIEVING FixPak 5 FOR AIX, HP-UX, LINUX, AND SOLARIS (SINGLE SERVER EDITION) ----------------------------------------------------------------------------- 1. Obtain the tar was40_aes_ptf_5_(Platform) from the product Web site: http://www.ibm.com/software/webservers/appserv/support.html Download the file into an empty directory on the machine on which you plan to install the FixPak. For example, download the file to /tmp directory. 2. At a system command prompt, change the directory to where you downloaded the file, for example: # cd /tmp 3. Untar or unzip the file. For untarring: # tar -xvf was40_aes_ptf_5_(Platform).tar RETRIEVING FixPak 5 FOR WINDOWS NT AND WINDOWS 2000 (ADVANCED EDITION) -------------------------------------------------------------------- 1. Obtain was40_ae_ptf_5.zip from the product Web site: http://www.ibm.com/software/webservers/appserv/support.html Download the file into an empty directory on the machine on which you plan to install the FixPak. 2. At a system command line, change directory (cd) to where you downloaded the file. 3. Unzip the file. RETRIEVING FixPak 5 FOR WINDOWS NT AND WINDOWS 2000 (SINGLE SERVER EDITION) ------------------------------------------------------------------------- 1. Obtain was40_aes_ptf_5.zip from the product Web site: http://www.ibm.com/software/webservers/appserv/support.html Download the file into an empty directory on the machine on which you plan to install the FixPak. 2. At a system command line, change directory (cd) to where you downloaded the file. 3. Unzip the file. USING THE INSTALLATION SCRIPT (ALL PLATFORMS) --------------------------------------------- * Before installation, remove any previously installed e-fixes from the machine. 1. Install the FixPak using the installation script install.sh for UNIX platforms and install.bat for Windows platforms. 2. For a typical, interactive install, you do not need to specify any command line options or environment variables. Environment variables must be specified when performing a silent install. You can find detailed option and environment variable information for the install scripts by specifying either of the -Help or -Usage options, for example: For AIX, HP-UX, Linux, and Solaris ---------------------------------- ./install.sh -usage ./install.sh -help For Windows NT and Windows 2000 ------------------------------- install.bat -usage install.bat -help Valid command line options include: -Help [ Show help text ] -Usage [ Show usage text ] -Silent [ Enable silent mode ] -Connector [ Force the installation of J2C Connector Technology ] A number of options are available through environment variables, as follows: SKIP_WAS = [ true | FALSE ] [ Skip Application Server Update ] WAS_UPDATE_HOME = [ path ] [ Application Server Home ] SKIP_JDK = [ true | FALSE ] [ Skip JDK Update ] JDK_UPDATE_HOME = [ path ] [ JDK Home ] INSTALL_IHS = [ true | FALSE ] [ Perform IHS Update ] IHS_UPDATE_HOME = [ path ] [ IHS Home ] FORCEJ2C = [ true | FALSE ] [ Force J2C Installation ] BACKUP_DIR = [ path ] [ Alternate Location for Backups ] LOGS_DIR = [ path ] [ Alternate Location for Logs ] TMP = [ path ] [ Location for Temporary Files ] IPLANET_HOME = [ path ] [ If using iPlanet Web Server (ie: /usr/iplanet/servers/https-/config) ] IPLANET_VERSION = [ 4 | 6 ] [ iPlanet Web Server Version ] INSTALL_APACHE = [ true | FALSE ] [ Perform Apache Update for EAPI Support ] APACHE_UPDATE_HOME = [ path ] [ Apache Home ] Silent mode defaults are shown in uppercase. In silent mode, by default, the Application Server update will be performed, the JDK update will be performed, the IHS update will not be performed, the iPlanet update will not be performed, the Apache update will not be performed, and the J2C installation will not be forced. In silent mode, by default, 'WAS_UPDATE_HOME' must be set. A java home must be available, either, beneath 'WAS_UPDATE_HOME', or, in an alternate location as specified using 'JDK_UPDATE_HOME'. In silent mode, if 'SKIP_WAS' is true, then 'JDK_UPDATE_HOME' must be specified. In silent mode, if 'INSTALL_IHS' is true, then 'IHS_UPDATE_HOME' must be specified. In silent mode, if 'IPLANET_HOME' is specified, then 'IPLANET_VERSION' must be specified. In silent mode, if 'INSTALL_APACHE' is true, then 'APACHE_UPDATE_HOME' must be specified. 3. Determine if silent mode is to be used. If used, particular values must be set through environment variables, according to the install options which are set. 4. Determine the particular updates which are to be performed: * IBM WebSphere Application Server * Java Development Kit * iPlanet Web Server * IBM HTTP Server * Apache Web Server (add support for Apache EAPI) * J2C Connector Technology [Advanced Edition Only] If one of the Application Server and Java Development Kit are being updated then the other should also be updated. If the FixPak is to be installed on a component-only installation such as plugin-only, admin console-only, tools-only, etc... the Application Server must be updated. The\ reason for this is the FixPak install considers all files under the 'WAS_UPDATE_HOME' directory (except those in 'WAS_UPDATE_HOME/java' directory) to be part of the Application Server. Therefore, in order to update the plugin files the Application Server must be updated. 5. When updating the IBM WebSphere Application Server, determine the IBM WebSphere Application Server installation root for the respective operating system. By default, these locations are: AIX /usr/WebSphere/AppServer HP-UX /opt/WebSphere/AppServer Linux /opt/WebSphere/AppServer Solaris /opt/WebSphere/AppServer Windows c:\WebSphere\AppServer For the most updated information, consult: http://www.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/root.html ** In silent mode, to skip the Application Server update set 'SKIP_WAS' to 'true'. ** Otherwise, 'WAS_UPDATE_HOME' must be set to the Application Server home. 6. If necessary, determine the location for the java installation. This is usually 'WebSphere/AppServer/java'. The installation script will automatically detect java in the default location. However, a different location may be specified to the install script. Note that a java installation must be available regardless of whether or not the java installation is being updated. ** In silent mode, the java home is automatically located relative to the Application ** Server home, and is automatically updated. To skip the JDK update set 'SKIP_JDK' ** to 'true'. Use 'JDK_UPDATE_HOME' to specify a alternate JDK location. 7. If the iPlanet web server is to be updated, determine the iPlanet web server configuration directory root. The directory location typically is: AIX /usr/iplanet/servers/https-/config HP-UX /opt/iplanet/servers/https-/config Linux /opt/iplanet/servers/https-/config Solaris /opt/iplanet/servers/https-/config Windows C:\iPlanet\servers\https-\config Also, the iPlanet version must be specified. Either '4' for iPlanet 4.x or '6' for iPlanet 6.x. ** In silent mode, by default, the iPlanet web server is not updated. To cause ** iPlanet to be updated, set 'IPLANET_HOME' to the configuration directory and set ** 'IPLANET_VERSION' to either 4 or 6. ** For this update to occur the user must agree to update the Application Server. 8. If the IBM HTTP Server is to be updated, determine the IBM HTTP Server installation root. By default the IBM HTTP Server location is: AIX /usr/HTTPServer HP-UX /opt/HTTPServer Linux /opt/IBMHTTPServer Solaris /opt/IBMHTTPD Windows C:\IBM HTTP SERVER ** In silent mode, by default, the IBM HTTP Server (IHS) is not updated. To cause ** IHS to be updated, set 'INSTALL_IHS' to 'true' and set 'IHS_UPDATE_HOME' to the ** IHS home directory. 9. If the Apache web server is to be updated to add support for Apache EAPI, the EAPI patch must already be installed with Apache in order for the web server to work properly. The Apache web server root installation directory must be determined. Typically, the Apache web server location is: AIX /usr/apache HP-UX /opt/apache Linux /opt/apache Solaris /opt/apache Windows C:\Apache Groups\Apache ** In silent mode, by default, the Apache web server is not updated. To cause ** Apache to be updated to support EAPI, set 'INSTALL_APACHE' to 'true' and set ** 'APACHE_UPDATE_HOME' to the Apache home directory. ** For this update to occur the user must agree to update the Application Server. 10. [Advanced Edition Only] Determine if the J2C Connector is to be installed. When present, the J2C Connector installation will automatically be updated. When absent, the installation of the J2C connector may be specified to the install script. ** In silent mode, the J2C Connector is updated. Set 'FORCEJ2C' to true to cause ** the J2C connector to be installed even if it is not already present. 11. Determine a location for temporary files. If set, the install scripts will use the value specified by environment variable 'TMP'. However, a different location may be specified to the install script. ** In silent mode, make sure that 'TMP' is correctly set. When unset the install ** script defaults 'TMP' to the current directory. The 'TMP' must be writable -- ** the installation script will halt if the 'TMP' directory is not writable. 12. Determine a location for log files. By default, logs are placed beneath the Application Server 'logs directory, 'WebSphere/AppServer/logs', however, a different location may be specified to the install script. Note that a location for logs must be specified if the IBM WebSphere Application Server is not being updated. ** In silent mode, 'LOGS_DIR' defaults as described above. An alternate logs ** directory may be specified through an environment variable. 13. Determine a location for backup jar files. By default, backup jar files are placed beneath the Application Server directory. However, a different location may be specified to the install script. A location must be specified if the IBM WebSphere Application Server is not being updated. ** In silent mode, 'BACKUP_DIR' defaults as described above. An alternate backup ** directory may be specified through an environment variable. 14. Stop the running processes as needed: 15a. Stop any processes of a Web Server which is being used with the Application Server. When stopping the IBM HTTP Server, make sure that the IBM HTTP Administration Service is stopped as well. On some UNIX platforms, the IBM HTTP Server is started automatically at the conclusion of the full product install. If you are installing the full product and then intend on installing the FixPak immediately thereafter, please ensure that the IBM HTTP Server is shut down before proceeding with the FixPak installation. 15b. Stop any Application Server processes that are running. 15c. Stop any java process that are running out of the IBM WebSphere Application java installation. For instance, The Application Assembly Tool (AAT) and third-party applications that use WebSphere JRE (e.g. Tivoli Manager for WebSphere). Due to garbage collection all java processes may not terminate for some time. Use the command ps -ef | grep java to verify that there are no java processes running. 16. Run the FixPak installation script: ./install.sh ./install.bat 17. If silent installation is not to be performed, follow the instructions provided during the installation program. A sequence of prompts will be provided guiding the user through the installation process. 18. At the conclusion of the installation, a summary log file will be created. Additional logs files will be created for the particular updates which were selected. Depending on the particular options used during the installation, the summary log file will be left in the temporary directory or will be copied into the specified logs directory. Additional log files are created in the specified logs directory. The summary log file is named 'Summary_ptf_5_.log', where is the SQL timestamp of starting time of running the install script. 19. [UNIX] Note the location of the backup jar files. Along with the backup jar files will be the two scripts 'uninstall_ptf_5.sh' and 'LogEvent.sh'. [WINDOWS] Note the location of the backup jar files. Along with the backup jar files will be the two scripts 'uninstall_ptf_5.bat' and 'LogEvent.bat', and the utility program 'GetInput.exe'. UNINSTALLING FixPak 5 (ALL PLATFORMS) ---------------------------------- 1. The uninstall scripts are located in the same directory as the backup jar files from the installation. [UNIX] The uninstall script is: ./uninstall_ptf_5.sh [WINDOWS] The uninstall script is: .\uninstall_ptf_5.bat 2. For a typical, interactive restoration, you do not need to specify any command line options and particular environment variables. Environment variables must be specified when performing a silent restoration. Detailed options and environment variable information may be found by specifying either of the options -Help or -Usage. In brief: Valid options for the uninstall script are the following: -Usage [ Show this usage information ] -Help [ Show comprehensive help ] -Silent [ Enable silent mode ] The uninstall script respects the following environment variables: SILENT = [ true | FALSE ] [ Specify silent mode ] TMP = [ path ] [ Temporary Directory ] LOGS_DIR = [ path ] [ Logs Directory ] JAVA_UPDATE_HOME = [ path ] [ Directory containing the JDK ] SKIP_RESTORE_WAS = [ true | FALSE ] [ Skip the Application Server restoration ] SKIP_RESTORE_JDK = [ true | FALSE ] [ Skip the JDK restoration ] SKIP_RESTORE_IHS = [ true | FALSE ] [ Skip the IBM HTTP Server restoration ] SKIP_RESTORE_J2C = [ true | FALSE ] [ Skip the J2C Connector restoration ] On all platforms the backup jar files and the uninstall script are in the same directory. [UNIX] On unix platforms, regardless of the directory from which the uninstall script is run, the backup jar files can be correctly located. [WINDOWS] On windows, when the uninstall script and the backup jar files are outside of the current directory, use the following environment variable to specify the location of the backup jar files: BACKUP_DIR = [ path ] [ Directory containing backup jar files ] See item 7 below. 3. Determine if a silent uninstall is to be performed. When performing a silent uninstall, uninstall options are selected using environment variables. 4. Determine the particular restores which are to be performed: * IBM WebSphere Application Server * Java Development Kit * IBM HTTP Server * J2C Connector Technology [ADVANCED EDITION ONLY] If one of the Application Server and Java Development Kit are being restored then the other should also be restored. The script will only perform restorations as backup jars are available. Each of the four 'SKIP_RESTORE' environment variables is meaningful only if the corresponding backup jar file is available. ** In silent mode, use 'SKIP_RESTORE_WAS', 'SKIP_RESTORE_JDK', 'SKIP_RESTORE_IHS', ** and 'SKIP_RESTORE_J2C' to cause particular restore operation to be skipped. ** ** In silent mode, by default, a java home is located relative to the directory ** containing the backup jar files. In certain cases, an alternate java home ** must be specified. In these cases, use 'JAVA_UPDATE_HOME' to specify ** the java home. 5. Determine the location for temporary files. By default, the value of the environment variable 'TMP' is used. If unset, temporary files are placed in the current directory. 6. Determine the location for log files. By default, logs are placed in the 'logs' directory beneath the directory containing the backup jar files. ** In silent mode, if the default logs directory cannot be used, or is not ** to be used, set 'LOGS_DIR' to specify an alternate location for log files. 7. [WINDOWS ONLY] The uninstall script is present in the directory which contains the backup jar files. Usually, the uninstall script is run from this directory. In this case, a backup directory ('BACKUP_DIR') does not need to be specified. However, the uninstall script may be executed from any directory, in which case the directory containing backup jars must be specified. (On UNIX platforms, the backup jar files are located relative to the uninstall script, so that a backup directory need not be specified.) 8. Stop the running processes as needed: 9a. Stop any processes of a Web Server which is being used with the Application Server. When stopping the IBM HTTP Server, make sure that the IBM HTTP Administration Service is stopped as well. 9b. Stop any Application Server processes that are running. 9c. Stop any java processes that are running out of the IBM WebSphere Application java installation. The Application Assembly Tool (AAT) is one such process. Due to garbage collection all java processes may not terminate for some time. Use the command ps -ef | grep java to verify that there are no java processes running. 10. Run the appropriate FixPak uninstall script: [UNIX] ./uninstall_ptf_5.sh [WINDOWS] .\uninstall_ptf_5.bat [UNIX] The uninstall script need not be run from the current directory. [WINDOWS] The uninstall script is usually run from the current directory. However, by specifying 'BACKUP_DIR', the uninstall script may be executed from another directory. 11. If silent uninstall is not to be performed, follow the instructions provided during the uninstall program. 12. Start IBM WebSphere Application Server. 13. This step is not required if you are going from 4.0.X to any release other than 4.0.1. Run the WSCP script which will convert 4.0.X DataSources to the 4.0.1 configuration; failure to do this will cause the 4.0.1 Administrator's Console to fail to start: [UNIX] wscp.sh -f ds_fix_post_uninstall.tcl [WINDOWS] wscp -f ds_fix_post_uninstall.tcl If the datasource is remote, property values wscp.hostName and wscp.hostPort can be modified to connect to remote node. These and other wscp properties can be specified either with -p option or in the property file .wscprc. Please refer to WebSphere InfoCenter section 6.6.0.2.2.2.2: Invoking and terminating wscp for more information.