Fix (APAR):  PK63947

Status:  Fix

Release:  6.1.0.1,6.1

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

Supersedes Fixes:  

CMVC Defect:   PK63947

Byte size of APAR:  387818

Date: 2008-04-21

Abstract:  The autogenerated plugin-cfg.xml contains incorrect /* URIs which prevent the webserver from serving any local content.  All requests are routed to the On Demand Router.

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

ERROR DESCRIPTION:                                              
The generated plugin-cfg.xml file contains /* URIs for the      
GenericApplication when it should not, causing the plugin to    
route all traffic to the ODR instead of serving any local/static
 content itself.                                                

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Users of WebSphere Extended Deployment
6.1.0 using the autogenerated
plugin-cfg.xml file.

PROBLEM DESCRIPTION:
The autogenerated plugin-cfg.xml
contains incorrect /* URIs which
prevent the webserver from serving
any local content.  All requests are
routed to the On Demand Router.

RECOMMENDATION:
None

The plugin-cfg.xml file contains a /* URI for the
GenericApplication definition.  This URI should not be present
in the plugin-cfg.xml file.

PROBLEM CONCLUSION:                                             
The plugin-cfg generator code will be fixed to not introduce the
 /* URI in the output file.  An ifix will be made available and 
the fix will be included in the Websphere Extended Deployment Re
lease 6.1.0.2.                                                  


Directions to apply fix:  
Install Fix to:
_X_ Application Server Nodes
_X_ Deployment Manager Nodes
_X_ 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.0.2.2 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  PK63947.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 ( PK63947.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 ( PK63947.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere

Additional Information: