Installation Instructions

Table of Contents

• About V6.0.1 Fix Pack 3
• Change History
• Problems addressed in this fix pack
• Fix Pack prerequisites
• Space requirements
• Steps for installing V6.0.1 Fix Pack 3
• Business Process Choreographer configuration
• Known issues
• Additional information
• Finding the Readme file for the Update Installer
• Trademarks and service marks

Change History
Release date: 30 September 2006
30 September 2006: Published

Back to top

Problems Addressed in this fix pack
In addition to the fixes contained in the previous fix packs, V6.0.1 Fix Pack 1 and V6.0.1 Fix Pack 2, (fix packs are cumulative), the fixes addressed in V6.0.1 Fix Pack 3 are detailed in the V6.0.1 Fix Pack 3 Content document at the following link: ftp://ftp.software.ibm.com/software/ts/cw/servers/wps/r601/FP/3/6013DefectList.html.

Back to top

Fix Pack prerequisites
To use this fix pack, you must have one of the following versions of WebSphere Enterprise Service Bus or WebSphere Process Server installed: 6.0.1.0, 6.0.1.1 or 6.0.1.2.

All hardware and software prerequisites are described in the Supported Hardware and Software web pages for WebSphere Enterprise Service Bus and WebSphere Process Server.

Ensure that the required disk space is available prior to installation of the fix pack. See the Space requirements section for details.

Back to top

Space requirements
Space requirements vary depending on your platform. The size of each download is available on the product support and download sites, WebSphere Enterprise Service Bus product support and WebSphere Process Server product support. A fix pack requires approximately 600 MB of free space in the system temporary directory (typically /tmp on a Linux(r) or UNIX(r) system) and another 600 MB in the file system that hosts the WebSphere Enterprise Service Bus or 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 installation disk on a Windows platform.

Space is also required in the "<install_root>/updateinstaller" and "<install_root>/properties/version/update/backup" directories. The space required for each of these directories is equal to the size of the fix pack package, typically from 25 MB to 750 MB.

Back to top

Steps for installing V6.0.1 Fix Pack 3

1. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations in the online information center for more information about the backing up of configuration files.
   Note: Backup of existing profiles in WebSphere Enterprise Service Bus or WebSphere Process Server.
   In addition to service to the core product files, some fix packs provide required service for existing profiles. The Update Installer will prompt you to back up your configuration when installing a fix pack that has required maintenance for profiles.
   Use the backupConfig command to back up the configuration of each profile that the fix pack can update. Or archive the "<install_root>/profiles" directory to back up all of the profiles at once. If you uninstall a fix pack, the Update Installer does not uninstall fix pack updates from profiles. The reason for not removing this maintenance is that you might have configured the profile after installing the maintenance. To restore an original profile, use the restoreConfig command or copy the profile from the archived profiles directory to replace the changed profile.
   
   
2. If you have already installed a previous maintenance package over your installation, you should complete the following additional step:
   Before extracting the contents of the fix pack, back up and delete any previous maintenance installation files. Delete the contents of:
   "<install_root>/updateinstaller/maintenance"
   where "<install_root>" refers to the directory name of the root of the WebSphere Enterprise Service Bus or WebSphere Process Server installation. For example, if your target platform is Linux(x86), and WebSphere Enterprise Service Bus is installed in the default location, then substitute <install_root> with the string "/opt/ibm/WebSphere/ESB".
   IMPORTANT: If you need to use a newer version of the Update Installer than you currently have installed, then back up and delete the entire "<install_root>/updateinstaller" directory, and all of its subdirectories. If you are unsure whether you need a new Update Installer, then back up and delete the entire updateinstaller directory. The new fix pack package contains a suitable replacement Update Installer.
   
   
3. Verify that the required disk space is available, as described in the Update Installer readme file located in the following path: <install_root>/updateinstaller/docs/readme_updateinstaller.html.
   
   
4. After backing up the configuration files and before installing the fix pack, stop all Java processes that are running within the IBM Java 2 Runtime provided by the WebSphere Enterprise Service Bus or WebSphere Process Server product.
   Stop all WebSphere Enterprise Service Bus or WebSphere 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.
   If you install V6.0.1 Fix Pack 3 while a WebSphere Enterprise Service Bus or WebSphere Process Server related process is running, then the installed WebSphere Enterprise Service Bus or WebSphere Process Server product might not continue to run successfully.
   IMPORTANT: For instructions on installing the fix pack in a Network Deployment environment where minimal downtime is required, refer to the update instructions in Section D, "For clusters in a Network Deployment environment where minimum downtime during upgrade is required."
   
   
5. Download the appropriate V6.0.1.3 fix pack package from the product's support Web site, WebSphere Enterprise Service Bus, or WebSphere Process Server. Download the package to a temporary disk location.
   
   
6. Unzip the package directly into the <install_root> directory. This unpacks the fix pack update files and the fix pack Update Installer into the <install_root>/updateinstaller directory, and includes a maintenance subdirectory.
   For example, on Linux (x86), if your installation is located in the default WebSphere ESB installation location of "/opt/ibm/WebSphere/ESB", and the downloaded file has been saved to /tmp, use the following commands to unzip the package:
   
   

   cd /opt/ibm/WebSphere/ESB unzip /tmp/6.0.1-WS-WPS-ESB-LinuxX32-FP0000003.zip

   
   If the unzip command is unavailable, you can substitute the command "jar -xvf" in its place, using the JAR binary file which is located within your WebSphere ESB or WebSphere Process Server supplied Java 2 SDK installation. Note: If you use the jar command to extract the files from the zip archive on a UNIX or Linux platform, you may need to change the file permissions of the "updateinstaller/update" binary file so that it is executable. You can do this by the command "chmod a+x updateinstaller/update".
   
   The V6.0.1.3 downloadable package contains both the Update Installer and the V6.0.1.3 fix pack files. The Update Installer for WebSphere Software is contained within the <install_root>/updateinstaller directory. The fix pack files are located in the <install_root>/updateinstaller/maintenance directory.
   
   Note that once you unpack the downloaded zip file, you might need to delete the zip file to free up space.
   
   
7. From the <install_root>/updateinstaller/ directory, run the update binary file to initiate the graphical installer, and follow the instructions to install the fix pack.
   
   
Important:
The installer installs the packages one at a time. When you are asked to enter the file name of the maintenance package, you must browse to find each package name, in the following order. The package names vary slightly by operating system, as indicated by <platform>



6.0.2-WS-WAS-<platform>-FP0000013.pak 6.0.2-WS-WASJavaSDK-<platform>-FP0000011.pak Note that the installation of this Java SDK package is a two-stage process. Follow the on screen instructions carefully for this package. 6.0.2.12-WS-WAS-IFPK29634.pak WS-WAS-IF353793.pak 6.0.1-WS-WPS-ESB-<platform>-FP0000003.pak


For each file in the list, select the package in the update installer and click "Next" to install it. Relaunch the installer after the installation of each package.

Note: The Java SDK package is not provided for the Solaris x86-64 platform because it was included in the V6.0.1.0 original install package for Solaris x86-64.

When all the installations are complete, click Finish.

Refer to the <install_root>/updateinstaller/docs/readme_updateinstaller.html file for detailed information about using the update command.

Note on installing the Java SDK Update: As mentioned above, installing the Java SDK is a two step process. The first step involves launching the update installer program and choosing 6.0.2-WS-WASJavaSDK-<platform>-FP0000011.pak as the maintenance package to install. Once this is done, shutdown and exit the update installer program completely. Do not choose "Relaunch". Now restart the update installer again and once again choose the same maintenance package to install. Then exit the update installer after successful completion of this package installation and proceed to install other maintenance packages. Installation of the Java SDK update must be done from the UpdateInstaller GUI and not from the command line.

To perform a silent installation using the command prompt:
For each filename in the previous list of package names (in the order shown), use the following commands, substituting <package_name> for the filename in the list:

For Windows platforms:


cd <install_root>\updateinstaller update -silent -W maintenance.package=.\maintenance\<package_name>


For UNIX platforms:


cd <install_root>/updateinstaller ./update -silent -W maintenance.package=./maintenance/<package_name>

Steps for updating the Business Process Choreographer configuration
(WebSphere Process Server only)

During the installation of the fix pack, the parts of the Business Process Choreographer component that are shipped as enterprise archive (EAR) files are updated on the file system. However, these files are not automatically deployed to the runtime configuration of WebSphere Process Server. The procedure to do this for stand-alone servers, for Network Deployment environments and for minimum down-time of clustered environments is described below:

1. For stand-alone profiles
   For each stand-alone profile for which you configured Business Process Choreographer, do the following:
   1. Make sure the application server where Business Process Choreographer is configured is stopped.
   2. Install the V6.0.1 Fix Pack 3 on the stand-alone installation.
   3. Go to the <install_root>/ProcessChoreographer directory.
   4. Depending on your platform, run one of the following commands:
      On Windows:

      ..\bin\wsadmin -conntype NONE -profileName <profileName> -f bpeupgrade.jacl

      On UNIX and Linux:
      

      ../bin/wsadmin.sh -conntype NONE -profileName <profileName> -f bpeupgrade.jacl

      where <profileName> is the name of the profile that contains the Business Process Choreographer configuration.
   5. Restart the application server.


2. For non-clustered servers in an Network Deployment environment
   
   1. Stop the deployment manager.
   2. Install the V6.0.1 Fix Pack 3 on the deployment manager's installation.
   3. Start the deployment manager.
   4. For each node with one or more servers where you configured Business Process Choreographer do the following:
      1. Make sure all servers (application servers and node agents) where Business Process Choreographer is to be upgraded are stopped.
      2. Install the V6.0.1 Fix Pack 3 onto the node's installation.
      3. On the node, go to the <install_root>/ProcessChoreographer directory.
      4. Depending on your platform, run one of the following commands:
         On Windows:

         ..\bin\wsadmin -profileName <profileName> -f bpeupgrade.jacl

         On UNIX and Linux:
         

         ../bin/wsadmin.sh -profileName <profileName> -f bpeupgrade.jacl

         where <profileName> is the name of the node's profile.
      5. Restart all servers of the node.


3. For clusters in an Network Deployment environment
   Note: For instructions concerning minimum downtime during cluster upgrade, refer to section D below.
   1. Stop the deployment manager.
   2. Apply v6.0.1 Fix Pack 3 on the deployment manager's installation.
   3. Start the deployment manager.
   4. For each cluster where you configured Business Process Choreographer, do the following:
      1. Make sure all cluster members and their node agents are stopped.
      2. Install the V6.0.1 Fix Pack 3 to all installations that host cluster members.
      3. On the deployment manager, go to the <install_root>/ProcessChoreographer directory.
      4. Depending on your platform, run one of the following commands:
         On Windows:

         ..\bin\wsadmin -profileName <profileName> -cluster <clusterName> -f bpeupgrade.jacl

         On UNIX and Linux:
         

         ../bin/wsadmin.sh -profileName <profileName> -cluster <clusterName> -f bpeupgrade.jacl

         where <profileName> is the name of the deployment manager's profile and <clusterName> is the name of the cluster.
      5. Restart all cluster members.


4. For clusters in an Network Deployment environment where minimum downtime during upgrade is required
   The following instructions assume a distributed clustered environment that needs to be updated with minimum downtime of the application servers involved. These instructions assume a sample setup that may need to be adapted to your environment:
   • Deployment manager is on a machine of its own.
   • The cluster includes a minimum of two servers, each on its own workstation.
   • Automatic node synchronization is enabled (this is the default).
   
   To update the Business Process Choreographer configuration, follow these steps:
   
   1. Stop the deployment manager.
   2. Install the V6.0.1 Fix Pack 3 on the deployment manager's installation.
   3. Start the deployment manager.
   4. For each cluster where you configured Business Process Choreographer, do the following:
      
      1. Stop half of cluster members and their node agents (for example, if you have two members, stop one).
      2. Install the V6.0.1 Fix Pack 3 on the corresponding installations. Do not restart the servers yet.
      3. Stop the remaining set of cluster members. There is a short downtime which cannot be avoided.
      4. On the deployment manager, go to the <install_root>/ProcessChoreographer directory.
      5. Depending on your platform, run one of the following commands:
         On Windows:

         ..\bin\wsadmin -profileName <profileName> -cluster <clusterName> -f bpeupgrade.jacl

         On UNIX and Linux:
         

         ../bin/wsadmin.sh -profileName <profileName> -cluster <clusterName> -f bpeupgrade.jacl

         where <profileName> is the name of the deployment manager's profile and <clusterName> is the name of the cluster.
      6. Restart the cluster members of those nodes where V6.0.1 Fix Pack 3 has already been applied.
      7. Install the V6.0.1 Fix Pack 3 on the installations of the remaining cluster members and restart each cluster member after the fix pack has been installed.

Back to top

Known issues:
All WebSphere Application Server related Java processes must be stopped before using the Update Installer for WebSphere Software. Read the technote at the following link for more information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21199141

Problem:
Stock Quote Sample fails after upgrade to new fix pack level.
Solution:
If you have deployed the Stock Quote Sample, you must update it with the new version. From the administrative console:

1. In the administrative console, click Applications > Enterprise Applications.
2. Select StockQuote and click update.
3. In Application update options, select Local file system and browse to <install-root>/samples/lib/ESBStockQuoteSample/StockQuote.ear.
4. Click Next, accept the default bindings and mappings, and click Next again.
5. Accept the default installation options and go to the Summary step.
6. Click Finish.
7. Click Save changes to master configuration.

• The product uninstallation does not remove the product correctly.
• The relaunch action for SDK updates does not launch 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 SDK if there is not enough disk space available for installation.
• Non-root profiles start with an error after WebSphere Application Server V6.0.2 is installed.
• There is a problem in cloning the SDK for updates to the product SDK.
• Profile update and undo scripts are limited to Single Byte Character Sets and to characters without pronunciation keys due to operating system limitations.
• Profiles can exist at the WebSphere Application Server V6.0.2 level after rolling back WebSphere Application Server V6.0.2.

Back to top

Additional information:
You can find additional information on any of these topics in the WebSphere Process Server or the WebSphere Enterprise Service Bus Information Centers.

For further information on the update strategy or obtaining updates to WebSphere Process Server or WebSphere Enterprise Service Bus, see also the Recommended Updates pages for Websphere Process Server and Websphere Enterprise Service Bus, as well as the IBM update strategy for WebSphere Application Server V6.0 release page.

Back to top

Accessing the readme file for the Update Installer:
For more information about the Update Installer, see the online readme file, http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162.

After unpacking V6.0.1.3, the readme file is available as the install_root/updateinstaller/docs/readme_updateinstaller.html. However, the online version is updated periodically while the bundled local copy is not.

Back to top

Trademarks and service marks:
For trademark attribution, visit the IBM Terms of Use Web site.