Fix (APAR):  PM05969

Status:  Fix

Release:  6.1.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  PK99568;PK97324;PK98103;PK96841;PK96414;PK96120

CMVC Defect:  PM05969

Byte size of APAR:  998692

Date: 2010-03-11

Abstract:  There is no mechanism for serving static file content from the local file system of the on demand router (ODR).

Description/symptom of problem:  
PM05969 resolves the following problem:

ERROR DESCRIPTION:                                              

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Virtual Enterprise Version 6.1.1.0

PROBLEM DESCRIPTION:
There is no mechanism for serving static file content from the local file system of the on demand router (ODR).

RECOMMENDATION:
None

The ODR in WebSphere Virtual Enterprise Version 6.1.1.0 cannot be enabled to serve static content from its local file system
even though proxy servers in WebSphere Application Server Network Deployment Version 7.0.0.x are enabled to serve static content.

PROBLEM CONCLUSION:                                             
The addRoutingRule command has been updated to support a local resource action type.                                     


Directions to apply fix:  
Install Fix to:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
XX Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must have administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files.

Customers must be at V6.1.0.17 or newer of the Update Installer.  This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy PM05969.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PM05969.pak file which was copied in the maintenance directory).  The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:  The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.

NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
DO NOT REMOVE A FIX UNLESS
ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PM05969.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown the WebSphere On-Demand Router

2) Follow the Fix instructions to apply the fix.

3) Restart the WebSphere On-Demand Router

Additional Information: