Readme for IBM WebSphere Application Server
Compilation date: 2004/06/29
© Copyright International Business Machines Corporation 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Abstract: Documentation for Cumulative Fix 6 of Version 5.0.2 of the WebSphere Application Server product family.
WSADIE customers running on Windows NT, Windows 2000, and Windows 2003 may experience configuration issues when installing WebSphere Application Server from WSADIE if they have installed WSADIE in the default path. This is due to an install path length limitation on the operating systems listed above. We are researching a solution, and any additional information learned will be posted to Technote 1173022, it may be referenced from the WebSphere Application Server Support page at http://www-306.ibm.com/software/main/img/titles/products/appserv-was-title.gif using keyword Readme1173022.
There are several platform-specific cumulative fixes that are each referred to as Cumulative Fix 6 for their respective product and platform. The complete list of fixes appears in a series of tables in the Retrieving Cumulative Fix 6 section, which is organized by product:
You can find additional information in the Version 5 information center: http://publib7b.boulder.ibm.com/webapp/wasinfo1/index.jsp?deployment=ApplicationServer.
The readme_updateinstaller.html file in the cumulative fix contains more detailed information about applying fix packs to more than one product on a machine. It also has detailed information about each of the two interfaces to the update installer application, which are the updateSilent and updateWizard interfaces.
The list of fixes and the Release Notes for Cumulative Fix 6 are on the product support Web site at http://www.ibm.com/software/webservers/appserv/support.html.
Install the appropriate Cumulative Fix 6 on top of the base WebSphere Application Server product, the Network Deployment product, or on top of the Enterprise product that extends the base product or the Network Deployment product.
A Java Runtime Environment must be available, even if the Java installation is not being updated.
Download Cumulative Fix 6 to a read/write directory as described in Installing Cumulative Fix 6. Installing from a read-only drive is not supported.
All required hardware and software prerequisites are described in the Supported hardware and software Web site at http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html.
Space requirements vary depending on what you are installing. The size of each download is available on the Support site. The platform-specific space requirements for a cumulative fix are as follows:
Unix-based platform
Approximately
400 MB of free space in the /tmp directory
400 MB in
the file system that hosts the WebSphere Application Server image (typically
/usr).
Windows platform
Approximately 800 MB of free space
on the disk drive.
Verify that the free space is available before beginning the installation. After unpacking the ZIP file, you can delete it to free space if necessary. After the code is installed, the Cumulative Fix 6 code increases the IBM WebSphere Application Server installation and run-time footprints slightly.
Space is also required for the /update directory of the product installation root. The space required is about the same as the size of the cumulative fix, typically somewhere between 50 MB to 250 MB.
Space is also required for backup files in the /properties/version/backup directory of the product installation root. The space required is about the same as the size of the cumulative fix, somewhere between 50 MB to 250 MB, varying by product and platform.
The update installer checks for required space before it installs the cumulative fix. However, a bug exists in the space checker when installing Cumulative Fix 6.
When installing Cumulative Fix 6, the update installer checks for required disk space in the /tmp directory and in the backup directory. If the /tmp directory or the backup directory have insufficient space, the update installer issues a warning message.
Cumulative Fix 6 platform-specific files for the Enterprise / Enterprise ND WebSphere Application Server product:
Operating system platform | Cumulative Fix 6 ZIP file | Cumulative Fix 6 ID |
---|---|---|
AIX | was502_pme_cf6_aix.zip | was502_pme_cf6_aix |
HP-UX | was502_pme_cf6_hpux.zip | was502_pme_cf6_hpux |
Linux | was502_pme_cf6_linux.zip | was502_pme_cf6_linux |
Linux for Power PC | was502_pme_cf6_linuxppc32.zip | was502_pme_cf6_linuxppc32 |
Linux for S/390 | was502_pme_cf6_linux390.zip | was502_pme_cf6_linux390 |
Solaris | was502_pme_cf6_solaris.zip | was502_pme_cf6_solaris |
Windows NT and Windows 2000 | was502_pme_cf6_win.zip | was502_pme_cf6_win |
Note: The above download file contains jars for both Enterprise/ Enterprise ND.
# cd /usr/WebSphere/DeploymentManager/update (Linux or UNIX) > cd \WebSphere\update (Windows platforms)
Note: On Windows platforms, the pkunzip utility might not decompress the download image correctly. Use another utility (such as WinZip) to unzip the image.
On some platforms, the updateWizard interface to the update installer program does not recognize the existing WebSphere Application Server product. This problem is caused by a limitation in the InstallShield for MultiPlatforms (ISMP) program that the update installer program uses.
The ISMP program does not recognize previous installations of WebSphere Application Server on some operating platforms.
To work around the problem, click Specify product information and type the fully qualified installation root directory for the existing product in the Installation directory field of the updateWizard panel.
The following problem has been identified with custom defined access intent policies:
Custom defined access intent policies created with access type = pessimistic update are treated just
like the access type pessimistic update - weakest lock at load.
Transactions that load entity beans using defined access intent policies with access type =
pessimistic update will acquire shared locks rather than exclusive locks on databases other than Oracle.
Concurrent transactions that attempt to update data using locks shared by other transactions may cause deadlocks.
This error will not be experienced by applications deployed against Oracle databases.
Solution: This problem is fixed in WebSphere Application Server
v5.1. Applications that will be deployed on WebSphere Application Server version v5.0.2 and require the locking
behavior associated with access type = pessimistic update should not use custom defined
access intent policies. These applications should instead specify custom attributes
when applying a standard WebSphere access intent policy to an entity bean or an entity bean method.
Open the readme_updateinstaller file in the format of your choice for more information about using the updateWizard.sh or the updateWizard.bat scripts, and for information about using the updateSilent.sh or updateSilent.bat scripts. The updateSilent scripts let you install a fix pack silently without interaction. For example, it is useful for installing a fix pack in an environment that does not provide a graphical user interface.
The readme_updateinstaller file describes an overall procedure for installing multiple fix packs on machines with multiple products, including how to install an Enterprise product fix pack, and how to install fix packs on nodes in a deployment manager cell.
The readme_updateinstaller file describes how to verify that you have successfully installed the fix pack.
The readme_updateinstaller file also describes how to uninstall a fix pack.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
LINUX is a trademark of Linus Torvalds in the U.S., other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.