Fix (APAR):  JR28631

Status:  Fix

Release:  6.0.2.3,6.0.2.2

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR28631

Byte size of APAR:  44614

Date: 2008-03-13

Abstract:  Federation of multiple standalone WebSphere Process Server node to deployment manager fails in 6.0.2.2.

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

ERROR DESCRIPTION:                                              
Federation of multiple standalone WPS profiles was allowed in   
6.0.2.0 release of WPS. In 6.0.2.2, there were restriction put  
in WPS to disallow this, as it leads to corruption of resources 
like bus and databases been used by applications in the         
standalone server.                                              
                                                                
Following exception is seen-                                    
                                                                
AddNode cannot continue because the DMgr is not empty.          
 at                                                             
com.ibm.ws.management.tools.SOACoreExtensionChecker.checkExtensi
on(SOACoreExtensionChecker.java:144)                            
 at                                                             
com.ibm.ws.management.tools.DefaultWPSExtensionChecker.checkExte
nsion(DefaultWPSExtensionChecker.java:120)                      
 at                                                             
com.ibm.ws.management.tools.AbstractNodeConfigUtility.checkProdu
ctExtensions(AbstractNodeConfigUtility.java:684)                
 at                                                             
com.ibm.ws.management.tools.NodeFederationUtility.doCheckIfAddNo
deIsOkToRun(NodeFederationUtility.java:1081)                    
 at                                                             
com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFe
derationUtility.java:438)                                       
                                                                
                                                                
                                                                
However WebSphere Business Monitor install and config needs     
this feature and depends on it for 6.0.2.2 release.             
http://www.ibm.com/developerworks/library/ar-bam3/              
                                                                
                                                                
The restriction in WPS needs to be relaxed, ie. if the          
federated profile does not have buses to be merged.             
                                                                
                                                                
Note- Monitor config design is changed in 6.1 and               
federation of multiple standalone WPS profile is NOT needed.    

LOCAL FIX:                                                      
Interim fix will be developed                                   

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.2 and above.
WebSphere Enterprise Service Bus 6.0.2.2
and above.

PROBLEM DESCRIPTION:
Federation of multiple standalone
WebSphere Process Server node to
deployment manager fails in 6.0.2.2.

RECOMMENDATION:
None

Federation of multiple standalone WPS profiles was allowed in
6.0.2.0 release of WPS. In 6.0.2.2, there were restriction put
in WPS to disallow this, as it leads to corruption of resources
like bus and databases been used by applications in the
standalone server.

Following exception is seen-

AddNode cannot continue because the DMgr is not empty.

PROBLEM CONCLUSION:                                             
Apply the interim fix that relaxes the restriction in           
WebSphere Process Server (WPS), ie. if the standalone profile   
does not have buses to be merged, they can be federated to a    
non empty DMgr.                                                 


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: