|
Abstract |
Contains the readme documentation for WebSphere
Application Server V5.0.2.12 Base, Network Deployment and Express
Editions. Includes install related instructions, prerequisites, highlights
of changes and known issues, if any. |
|
|
|
|
Content |
IBM WebSphere Application Server, Version 5.0.2 Cumulative Fix 12
IBM WebSphere Application Server Network Deployment, Version 5.0.2
Cumulative Fix 12
IBM WebSphere Application Server Express, Version 5.0.2 Cumulative Fix 12
Table of Contents
Compilation date: 2005/07/15
© 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.
About Cumulative Fix 12
There are several platform-specific cumulative fixes that are each
referred to as Cumulative Fix 12 for their respective product and
platform. The complete list of fixes appears in a series of tables in the
Retrieving Cumulative Fix
12 section, which is organized by product:
- WebSphere Application Server, Version 5.0.2, including its
features and the embedded messaging feature, which is based on WebSphere
MQ technology.
- WebSphere Application Server Network Deployment, Version
5.0.2
- WebSphere Application Server Express Edition
This document also describes prerequisites, space requirements, download
instructions, locations of detailed installation instructions, and more
information about the update installer application.
Back to top
Additional information
You can find additional information in the Version 5.0 information center.
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 updates and related documentation is available from the WebSphere Application Server V5.0.2 Cumulative Fix 12
download page.
Back to top
Prerequisites
Install the appropriate Cumulative Fix 12 on top of WebSphere Application
Server Base, Network Deployment, or Express Edition.
A Java Runtime Environment must be available, even if the Java
installation is not being updated.
Download Cumulative Fix 12 to a read/write directory as described in Installing Cumulative Fix 12.
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.
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 cumulative fix, have
approximately 400 MB of free space in the /tmp directory and another 400
MB in the file system that hosts the WebSphere Application Server image
(typically /usr) on a UNIX-based platform, or approximately 800 MB 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. After unpacking the ZIP file, you can delete the ZIP file to
free space if necessary. After the code is installed, the Cumulative Fix
12 code increases the IBM WebSphere Application Server installation and
run-time footprints by a small amount.
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 12.
When installing Cumulative Fix 12, 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.
Back to top
Retrieving Cumulative Fix 12
Cumulative Fix 12 platform-specific files for the base WebSphere
Application Server product:
Operating system platform
|
Cumulative Fix 12 ZIP file
|
Cumulative Fix 12 ID
|
AIX
|
was502_cf12_aix.zip
|
was502_cf12_aix
|
HP-UX
|
was502_cf12_hpux.zip
|
was502_cf12_hpux
|
Linux
|
was502_cf12_linux.zip
|
was502_cf12_linux
|
Linux for Power PC
|
was502_cf12_linuxppc32.zip
|
was502_cf12_linuxppc32
|
Linux for S/390
|
was502_cf12_linux390.zip
|
was502_cf12_linux390
|
Solaris
|
was502_cf12_solaris.zip
|
was50_cf12_solaris
|
Windows NT and Windows 2000
|
was502_cf12_win.zip
|
was502_cf12_win
|
Cumulative Fix 12 platform-specific files for the base WebSphere
Application Server Express product:
Operating system platform
|
Cumulative Fix 12 ZIP file
|
Cumulative Fix 12 ID
|
AIX
|
was502_express_cf12_aix.zip
|
was502_express_cf12_aix
|
HP-UX
|
was502_express_cf12_hpux.zip
|
was502_express_cf12_hpux
|
Linux
|
was502_express_cf12_linux.zip
|
was502_express_cf12_linux
|
Solaris
|
was502_express_cf12_solaris.zip
|
was50_express_cf12_solaris
|
Windows NT and Windows 2000
|
was502_express_cf12_win.zip
|
was502_express_cf12_win
|
Cumulative Fix 12 platform-specific files for the Network Deployment
product:
Operating system platform
|
Cumulative Fix 12 ZIP file
|
Cumulative Fix 12 ID
|
AIX
|
was502_nd_cf12_aix.zip
|
was502_nd_cf12_aix
|
HP-UX
|
was502_nd_cf12_hpux.zip
|
was502_nd_cf12_hpux
|
Linux
|
was502_nd_cf12_linux.zip
|
was502_nd_cf12_linux
|
Linux for Power PC
|
was502_nd_cf12_linuxppc32.zip
|
was502_nd_cf12_linuxppc32
|
Linux for S/390
|
was502_nd_cf12_linux390.zip
|
was502_nd_cf12_linux390
|
Solaris
|
was502_nd_cf12_solaris.zip
|
was502_nd_cf12_solaris
|
Windows NT and Windows 2000
|
was502_nd_cf12_win.zip
|
was502_nd_cf12_win
|
Back to top
Steps for installing Cumulative Fix
12
- Backup any interim fixes you might have installed, as you will need to
re-install them after the V.5.0.2 Cumulative Fix 12 is installed on your
machine if these fixes are not included in the V.5.0.2 Cumulative Fix 12.
- Run the backupConfig command to back up configuration files.
See Backing up and restoring administrative
configurations in the online information center.
- Verify required disk space.
- After backing up the configuration and before installing Cumulative
Fix 12, stop all Java processes that use the IBM Developer Kit that
WebSphere Application Server provides to support the Java 2 SDK on your
operating system platform, such as the IBM Developer Kit for AIX, Java
Technology Edition.
Stop all application server processes, the nodeagent process, the
deployment manager process, and all server processes, such as the
jmsserver process, that belong to serviceable features. Features with
server processes include the IBM HTTP Server and the embedded messaging
feature. Stop all Java processes. The product might not continue to run
successfully, or without error if you do install a fix pack while a
WebSphere Application Server-related Java process is running.
- Obtain the fixes you need from the WebSphere Application Server V5.0.2 Cumulative Fix 12
download page. Download the files into the install_root/update
directory, which you can create.
- At a system command prompt, change the directory to where you
downloaded the file, for example:
# cd /usr/WebSphere/DeploymentManager/update (Linux® or UNIX®)
> cd \WebSphere\update (Windows® platforms)
- Unzip the file.
Note: On Windows platforms, the pkunzip utility might not
decompress the download image correctly. Use another utility (such as
WinZip) to unzip the image.
- (Optional) Delete the ZIP file if you need more space.
- At a system command prompt, call the updateWizard.sh or the
updateWizard.bat script to begin the installation. Refer to the
readme_updateinstaller.html (or PDF) file for detailed information about
using the updateWizard script.
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.
- Re-install any Temporary Fixes you may have uninstalled at step
1.
Known problems
After upgrading to cumulative fix WebSphere Application Server V5.1.1.6,
V5.0.2.12, or V5.0.2.13, a memory leak has been found in Invocation Cache
which leads to an OutOfMemory situation. To resolve the problem, apply PK12027.
Back to top
Highlights of changes
- PQ90177: Save Conflict
When a save conflict occurs in the admin console, the default option
is to overwrite the conflicting files. This is not a well chosen default
option, because overwriting file changes could lead to repository
corruption.
The default option upon a save conflict has been changed from overwrite to
discard. This will help preserving the integrity of the repository. The
overwrite option is meant for advanced users. This will also line up
administrative console behavior with 'wsadmin', where the default is not
to overwrite conflicting files.
- PQ93396: Disk Cache
If your server is configured to use disk cache function, you must
delete previous disk cache files after installing the Service Pack. For
more details on this, see Troubleshooting tips for the dynamic cache service in
the information center.
- Java virtual machine custom properties for tuning the
disk cache
Use this page to set Java virtual machine (JVM) custom properties to
maintain cache entries that are saved to disk.
Steps for this task
To set any of these JVM custom properties, perform the following steps:
- In the administrative console, click Servers > Application
servers > server_name > Process definition > Java virtual
machine > Custom properties > New
- Type the name of the custom property (for example,
com.ibm.ws.cache.CacheConfig.htodCleanupFrequency) in the Name
field.
- Type a valid value for the property in the Value field.
- Save the property and restart WebSphere Application Server.
- com.ibm.ws.cache.CacheConfig.htodCleanupFrequency
Use this property to change the amount of time between disk cache
cleanup.
By default, the disk cache cleanup is scheduled to run at midnight to
remove expired cache entries and cache entries that have not been accessed
in the past 24 hours. However, if you have thousands of cache entries that
might expire within one or two hours, the files that are in the disk cache
can grow large and become unmanageable. Use the
com.ibm.ws.cache.CacheConfig.htodCleanupFrequency custom property
to change the time interval between disk cache cleanup.
Units |
Minutes
For example, a value of 60 means 60 minutes between each disk cache
cleanup |
Default |
0
The disk cache cleanup occurs at midnight every 24 hours |
Back to top
Finding the readme_updateinstaller.txt,
readme_updateinstaller.html and readme_updateinstaller.pdf files
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. It is useful for installing a fix pack
in an environment that does not provide a graphical user interface, for
example.
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.
Back to top
Trademarks and service marks
The following terms are trademarks of IBM Corporation in the United
States, other countries, or both:
- Everyplace
- iSeries
- IBM
- Redbooks
- ViaVoice
- WebSphere
- zSeries
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.
Back to top
More information
For more information, refer to the recommended updates and IBM
cumulative fix strategy documents. |
|
|
|
|
|
Original publication
date |
2005/7/15 |
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Application Server - Express |
General |
AIX, HP-UX, Linux, Solaris, Windows |
5.0.2.9, 5.0.2.8, 5.0.2.7, 5.0.2.6, 5.0.2.5, 5.0.2.4, 5.0.2.3,
5.0.2.2, 5.0.2.12, 5.0.2.11, 5.0.2.10, 5.0.2.1, 5.0.2, 5.0 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|