Fix (APAR):  JR26462

Status:  Fix

Release:  6.0.2.1

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

Supersedes Fixes:  

CMVC Defect:  JR26462

Byte size of APAR:  66219

Date: 2007-09-18

Abstract:  When the user modifies the BO definition at runtime and try to test the scenario using BPCExplorer find the BO definition is not modified, the BO definition is loaded from the cach

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

ERROR DESCRIPTION:                                              
.                                                               
Short description                                               
ESR: Problems making change to POJO: have to restart server;    
JAXRPCException when send req after POJO change. Also server has
to be                                                           
restarted in order to pickup changes to MFC or XML Maps/XSLT.   
This                                                            
happens when performance patch is applied to WID UTE server.    

LOCAL FIX:                                                      
WPS 6.0.2                                                       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 602.x Users who
make BO or workspace changes at runtime.

PROBLEM DESCRIPTION:
When the user modifies the BO
definition at runtime and try to test
the scenario using BPCExplorer find
the BO definition is not modified,
the BO definition is loaded from the
cache. This fix enables on demand
loading of BO and as well workspace
changes, so appropriately reflects
the changes at runtime without server
restart.

RECOMMENDATION:
Restarting the server is a workaround for
this problem, user might want to apply
this iFix instead of restarting the server.

At runtime if BO definition changes, doesn't get reflected
when the user want to use modified definitions.

PROBLEM CONCLUSION:                                             
This iFix enables user to modify the workspace at runtime       
without restarting the server.                                  


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also 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

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

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: