Fix (APAR):  JR28263

Status:  Fix

Release:  6.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9006

Date: 2008-02-21

Abstract:  A runtime exception may result when saving changes to a relationship in WebSphere Integration Developer.

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

ERROR DESCRIPTION:                                              
Cannot publish app after change key attribute in relation       

LOCAL FIX:                                                      
NONE                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1 Users

PROBLEM DESCRIPTION:
A runtime exception may result when
saving changes to a relationship in
WebSphere Integration Developer.

RECOMMENDATION:
None

A runtime exception may result for the following problem
scenario in WebSphere Integration Developer.
1) Start the WebSphere Process Server test environment.
2) Deploy an application containing at least one
relationship to the server.
3) Open the relationship and change the Key Attribute
for one or more roles.
4) Save the changes to the workspace.

The following runtime exception may appear in the console
after saving the changes to the workspace:

E com.ibm.wbiserver.relationshipservice.util.
ArtifactLoaderUtility
createRuntimeSchema(BrokerageModuleApp) CWLAE0005I:
An exception was encountered when the relationship
service code was executing.
com.ibm.wbiserver.relationshipservice.exceptions.
RelationshipServiceException:
table CUST_BROK_RT_354E905481A639C701426D3C9430B2FE
already exist,but the table  schema is different
from current role defintion
at com.ibm.wbiserver.relationshipservice.dblayer.
cloudscape.CloudscapeCreator101.createRoleBaseSchema
(CloudscapeCreator101.java:438)
at com.ibm.wbiserver.relationshipservice.dblayer.
cloudscape.CloudscapeCreator101.createRoleRuntimeSchema
(CloudscapeCreator101.java:154)
at com.ibm.wbiserver.relationshipservice.dblayer.
SchemaCreator.createRuntimeSchema(SchemaCreator.java:139)

PROBLEM CONCLUSION:                                             
The problem has been fixed by changing (correcting) the         
classloader reload settings so an application restart is not    
triggered when saving changes to the  workspace in WebSphere    
Integration Developer.                                          


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: