Fix (APAR): JR26704 Status: Fix Release: 6.0.2.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 26346 Date: 2007-07-06 Abstract: setWithCreate API in the migration code throws an exception when mapping an attribute from a source BO to a destination attribute that is an attribute in a child object that is few Description/symptom of problem: JR26704 resolves the following problem: ERROR DESCRIPTION: setWithCreate API in the migration code throws an exception when mapping an attribute from a source BO to a destination attribute that is an attribute in a child object that is few levels down in the hierarchy. The exception thrown appears somewhat as follows: This mapping transformation fails with the following exception: 5/8/07 18:06:24:875 PDT] 00000073 BaseMAP E submap_call_2() CWLAS0015E: Submap transformation #2 in Map failed with exception CWLAS0015E: Custom transformation #2 in Map failed with exception Error 11030 Attribute does not exist in business object . Error11030..[5/8/07 18:06:25:000 PDT] 00000073 ParameterMedi E com.ibm.wbiserver.mediation.ifm.ParameterMediationHelper doParameterMediation CWLAU0005E: Interface mapping Component1 with source operation operation1 and target operation operation1 experienced an unexpected error com.ibm.wbiserver.map.exceptions.WBIMapFailureException: CWLAS0015E: Submap transformation #2 in Map failed with exception CWLAS0015E: Custom transformation #2 in Map failed with exception Error 11030 Attribute does not exist in business object . Error11030.. when invoking map . The calling context is SERVICE_CALL_REQUEST. This is due to an error in the manner in which the multiple cardinality child objects are handled in the Heritage API. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2.x users trying to use the setWithCreate API in the migration code. PROBLEM DESCRIPTION: setWithCreate API in the migration code throws an exception when mapping an attribute from a source BO to a destination attribute that is an attribute in a child object that is few levels down in the hierarchy. RECOMMENDATION: None setWithCreate API in the migration code throws an exception when mapping an attribute from a source BO to a destination attribute that is an attribute in a child object that is few levels down in the hierarchy. The exception thrown appears somewhat as follows: This mapping transformation fails with the following exception: 5/8/07 18:06:24:875 PDT] 00000073 BaseMAP E submap_call_2() CWLAS0015E: Submap transformation #2 in Map failed with exception CWLAS0015E: Custom transformation #2 in Map failed with exception Error 11030 Attribute does not exist in business object . Error11030..[5/8/07 18:06:25:000 PDT] 00000073 ParameterMedi E com.ibm.wbiserver.mediation.ifm.ParameterMediationHelper doParameterMediation CWLAU0005E: Interface mapping Component1 with source operation operation1 and target operation operation1 experienced an unexpected error com.ibm.wbiserver.map.exceptions.WBIMapFailureException: CWLAS0015E: Submap transformation #2 in Map failed with exception CWLAS0015E: Custom transformation #2 in Map failed with exception Error 11030 Attribute does not exist in business object . Error11030.. when invoking map . The calling context is SERVICE_CALL_REQUEST. PROBLEM CONCLUSION: This APAR is a runtime fix that is addressed to fix the above problem. This is a runtime fix. 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. Please install the prereq JR25922 using the updateInstaller. 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: