Fix (APAR):  PK56306

Status:  Fix

Release:  6.1

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

Supersedes Fixes:  

CMVC Defect:  PK56306

Byte size of APAR:  333238

Date: 2007-11-15

Abstract:  If the non-WAS server is already running when the XD Agent is started, the On Demand Router may not be able to route to the non-WAS server.

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

ERROR DESCRIPTION:                                              
If the On Demand Configuration is notified of an XDAgent server 
start before ODC has received the server's configuration        
information, it will discard the notification and never mark the
 server as running.                                             

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
All Users of WebSphere Extended Deployment
V6.1 managing non-WAS servers via the XD
Agent component of Websphere Extended
Deployment

PROBLEM DESCRIPTION:
If the non-WAS server is already
running when the XD Agent is started,
the On Demand Router may not be able
to route to the non-WAS server.

RECOMMENDATION:
None

A timing window exists in which the On Demand Configuration
component may discard notification of the startup of a non-WAS
server if the non-WAS server was already running when the XD
Agent and ODC are started.  This will result in the ODR
reporting the non-WAS server as stopped and refusing to route
to it.

PROBLEM CONCLUSION:                                             
Notifications of non-WAS server starts will be queued to        
ensure that they are not discarded if the On Demand             
Configuration component is not ready for them.  This will       
ensure proper server state reporting for non-WAS servers.  An   
ifix will be made available and this fix will be included in    
Websphere Extended Deployment version 6.1.0.1.                  


Directions to apply fix:  
Install Fix to:
_X_ Application Server Nodes
_X_ Deployment Manager Nodes
_X_ Standalone XD Agent Nodes

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 PK56306.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 (PK56306.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 (PK56306.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: