Fix (APAR):  JR29110

Status:  Fix

Release:  6.1.0.1

Operating System:  Linux,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  18620

Date: 2008-05-08

Abstract:  WebSphere Process Server V6.1.0.1 fails with an exception when trying to federate a stand alone portal server (i.e. a plain WebSphere Application Server profile) into a Process Ser

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

ERROR DESCRIPTION:                                              
Description: WPS 6101 fails with an exception when trying to    
federate a stand alone portal server (i.e. a plain WAS profile) 
into a Process Server Cell that already contains a process      
server. The exception is "A new instance of the WorkManagerInfo 
object cannot be created because the jndiName attribute of an   
existing WorkManagerInfo object has the same                    
value as wm/AppScheduler." This breaks the main install path for
setting up a single cell process portal. This issue has already 
been discussed with development. The problem appears to be      
caused by the AppScheduler (specifically AppSchedulerImportStepE
xt.java appears to not take the federation of plain WAS profiles
into account).                                                  
                                                                
the scenario used to generate the traces / error:               
1. Installed 6.1.0.1 Process Server DM (Dmgr01)  (Box A)        
2. Created custom profile (custom01) on Dmgr01 (Box A)          
3. Create a Process Server in custom01                          
4. Enabled SCA and process/task containers                      
5. Enabled BPCExplorer                                          
6. Process Server Cell is operating ok.                         
7. Installed portal 6.1. stand alone (portal default install)   
-->                                                             
wp_profile (plain WAS profile) (Box B)                          
8. Tried to federate portal node into Dmgr01 --> Exception.     

LOCAL FIX:                                                      
WPS changeTeam engaged                                          

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server V6.1 customer who
trying to federate a portal node on other
machine to Dmgr.

PROBLEM DESCRIPTION:
WebSphere Process Server V6.1.0.1
fails with an exception when trying to
federate a stand alone portal server
(i.e. a plain WebSphere Application
Server profile) into a Process Server
Cell that already contains a process
server.

RECOMMENDATION:
None

After code changes problem has been resolved.

PROBLEM CONCLUSION:                                             
Apply this interim fix to resolve the issue.                    


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