Fix (APAR):  PK16490

Status:  Fix

Release:  5.1.1.8

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

Supersedes Fixes:  

CMVC Defect:  PK16490

Byte size of APAR:  9525

Date: 2006-02-14

Abstract:  The nodename may be ignored while deploying an application in a Network Deployment environment.

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

ERROR DESCRIPTION:                                              
After applying cumulative Fix 8 node validation is ignored.     
Deploy DefaultApplication to test_server on node node2.         
The deployment finishes without errors. Now look in the         
adminconsole                                                    
under applications to our installed DefaultApplication.         
Under <Map modules to Application server> we see the            
DefaultApplication is mapped to test_server on node node01:     
<WebSphere:cell=CellNameNetwork,node=node01,server=test_se      
rver>                                                           
                                                                
WebSphere Application Server 5.1.1.8                            

LOCAL FIX:                                                      
NA                                                              

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server users of
version 5.1.1.8 and 5.1.1.9.

PROBLEM DESCRIPTION:
The nodename may be ignored while
deploying an application in a Network
Deployment environment.

RECOMMENDATION:
None


This problem occurs while deploying an application in a
Network Deployment configuration, which has multiple nodes
each containing an AppServer of the same name, for example,
server1.  When the application is being deployed
to any of the identically named servers, the application will
only be deployed on the server in the first node, even if you
select the server another node.

While retrieving the serverContext, to which the application
needs to deployed, the nodename validation is being ignored,
so that the serverContext which finds a server match  first
will be returned, which is not necessarily the correct one.

PROBLEM CONCLUSION:                                             
The root cause of the problem was identified.  This is that     
node name validation is being ignored. The corresponding        
changes were made to validate node name and server name, in     
order to select the appropriate serverContext instead.          
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 5.1.1.10.  Please refer to the recommended updates      
page for delivery information:                                  
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
Fix applies to Editions:
Release:
5.1
_y__ Application Server (Express or BASE)
_y__ Network Deployment (ND)

Install Fix to:
Method:
_y_ Application Server Nodes
_y_ Deployment Manager Nodes
_y_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update 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.

1) Copy PKxxxxx.jar 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 (PKxxxxx.jar 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.
* 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 (PKxxxxx.jar).

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: