Fix (APAR):  PK85526

Status:  Fix

Release:  6.1.0.5,6.1.0.4,6.1.0.3,6.1.0.2,6.1.0.1

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

Supersedes Fixes:  PK47074;PK48624;PK52224;PK52782;PK55419;PK56306;PK56591;PK56949;PK57460;PK61565;PK61892;PK61940;PK63947;PK64364;PK64765;PK66516;PK66529;PK67616;PK67969;PK68690;PK68789;PK69283;PK69789;PK70075;PK71581;PK73339;PK73812;PK74146;PK75496;PK76144;PK76249;PK77669;PK81357;PK83680;PK84324

CMVC Defect:  PK85526

Byte size of APAR:  455482

Date: 2009-05-28

Abstract:  On demand routers (ODR) that are in the running state are not included in the generated plugin-cfg.xml file.

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

ERROR DESCRIPTION:                                              
On demand routers (ODR) receive an invalid state information    
set, which causes the ODRs to not be included in the            
plugin-cfg generation.                                          

LOCAL FIX:                                                      
1) We will provide the ability to include the ODRs regardless of
state                                                           
2) We will force the ODRs to ignore bad state information about 
themselves while printing a warning about where that invalid    
state information came from.                                    

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Virtual Enterprise
Version 6.1.0.x

PROBLEM DESCRIPTION:
 On demand routers (ODR) that are in
the running state are not included in
the generated plugin-cfg.xml file.

RECOMMENDATION:
None

The ODRs runtime weights are erroneously being set to zero,
which causes the ODRs to not be displayed in the generated
plugin-cfg.xml file.

PROBLEM CONCLUSION:                                             
To prevent this problem from occurring, any attempt by a        
remote process to set the runtime weight of the ODR to zero is  
ignored.                                                        


Directions to apply fix:  
Install Fix to:
__ Application Server Nodes
__ 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.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 6.1.0.1-WS-WXD-IFPK85526.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 (6.1.0.1-WS-WXD-IFPK85526.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 (6.1.0.1-WS-WXD-IFPK85526.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: