Readme for IBM WebSphere Application Server version 6.1.0.3

Content

WebSphere Application Server 6.1.0 Fix Pack 3 (6.1.0.3)
WebSphere Application Server Network Deployment version 6.1.0 Fix Pack 3 (6.1.0.3)

Table of Contents

• What is new with Fix Pack 3
• About Fix Pack 3
• Prerequisites
• Space requirements
• Steps for installing Fix Pack 3
• Known issues
• Change History
• Additional information
• Trademarks and service marks

Compilation date: 2006/09/18

© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

---

What is new with Fix Pack 3
One installation of Version 6.1 Update Installer can be used to update all WebSphere Version 6.1 products installed on the entire machine. There is no longer a need to install one copy for each product install location.

The Update Installer is no longer bundled with version 6.1 fix packs. It is available on the Version 6.1 product compact disc or as a download from IBM support site. See section on Prerequisites for installing Fix Pack 3 for more details.


Back to top

---

About Fix Pack 3
Several cumulative fixes are bundled into a single maintenance package for a specific combination of product and platform. Each maintenance package is referred to as version 6.1.0.3.

Installing Fix Pack 3 with version 6.1 Update Installer raises the fix level of your product to version 6.1.0.3.

See the installation instructions in the Steps for installing Fix Pack 3 section for more information.

Fix packs can be downloaded from the version 6.1.0.3 download page.

Note: If a remote Web server plug-in or IBM HTTP Server is installed alongside WebSphere Application Server, you will need to download a separate fix pack in order to update the plug-in or HTTP Server to the most current level (if an update is available). All fix packs can be found on the version 6.1.0.3 download page.


Back to top

---

Prerequisites

1. Install the version 6.1 product from the appropriate compact disc or distribution media.
   
   
2. If not already installed on your machine, install the version 6.1 Update Installer from the 6.1 product compact disc or alternatively download and install the latest available from the Update Installer version 6.1 download page.
   
   You very likely already have one installed, it is recommended only one copy of the Update Installer be installed to support all of version 6.1 WebSphere products on the entire machine.
   
   The installation directory will be referred to as updi_install_root in this document.

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 Application Server image (typically /usr or /opt on a Linux® or UNIX® 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 backup files in the WebSphere Product's 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.


Back to top

---

Steps for installing 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.
   
   
2. Verify required disk space, as described in the readme file for the maintenance package.
   
   
3. After backing up the configuration and before installing fix pack 6.1.0.3, stop all Java processes associated with Java™ SDK shipped with WebSphere Application Server to support Java 1.5 SDK.
   
   
4. Stop all application 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 operate successfully if attempts to install fix pack 6.1.0.3 while a WebSphere Application Server-related Java processes is still running.
   
   
5. Obtain downloadable maintenance packages from the version 6.1.0.3 download page.
   
   Download the packages into the update installer maintenance directory:
   
   

updi_install_root/maintenance

6. To install downloaded maintenance packages, refer to instructions found in the Update Installer installation documentation directory:
   
   

updi_install_root/docs/readme_updateinstaller.html

Additional instructions can be found in the Information Center, Installing Maintenance Packages. Installation instructions are summarized and repeated here for convenience only, refer to the preceding official published sources. Open a command shell window and change directories to the updi_install_root install location of the V6.1 Update Installer.

cd updi_install_root

Use the update command to install the maintenance package that you downloaded into updi_install_root/maintenance directory: The Update Installer wizard can run in silent mode without graphical user interface and responsefile can be configured for automatical installation. For Windows®: update –silent –options  responsefile For Linux® or UNIX® platforms: ./update.sh –silent –options  responsefile And, graphical user interface mode is available by update command without any parameter: For Windows®: update.bat For Linux® or UNIX® platforms: ./update.sh Refer to the following file for detailed information about using the update command: updi_install_root/docs/readme_updateinstaller.html

Back to top

---

Known side-effects
An HTTP error code 404 is received when attempting to access precompiled JSP pages that use SDK 1.5 language features, such as enums. JSP precompilation completes successfully, however the JSP pages cannot be loaded because their associated JSP classes cannot be found when attempting to load the page; this should not occur. Replacement is recommended and correcting interim fixes for this error are available in this Link.

Back to top

---

Change History
7 Dec 2006	Updated Known side-effects section
18 Sept 2006	Initial publication

Back to top

---

Additional information
You can find additional information in the WebSphere Application Server Version 6.1 Information Center.

For additional information, refer to Recommended fixes for WebSphere Application Server.

Back to top

---

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

Back to top

---