Fix (APAR): JR28799 Status: Fix Release: 6.0.2.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 9453 Date: 2008-04-08 Abstract: BusinessObject CoreFramework is not able to resolve some complex type definitions, hence sets the complex types containment properties to false. Description/symptom of problem: JR28799 resolves the following problem: ERROR DESCRIPTION: Publishing this BPEL_Utilities app to server without any significant error/warning then via BPC Explorer, began to work with process instance. Filled out fields as usual ... Process Template Name BOSerializationTestForSAR Operation startOperation Process Input Message CarrierID 0 DestinationStockerID 0 TransportPriority 0 StringOrStruct 0 - In console - [2/19/08 14:05:12:109 EST] 00000083 SystemOut O Performing String to PptUser_struct-->ObjectIdentifier_struct-->identifier assignment [2/19/08 14:05:12:297 EST] 00000083 SystemOut O Entering SetResponse [2/19/08 14:05:12:297 EST] 00000083 SystemOut O Exiting SetResponse - Exception Stack Trace (snippet) - javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.bpe.api.ProcessError com.ibm.bpe.api.ProcessError: Error during Serialization org.eclipse.emf.ecore.xmi.DanglingHREFException: The object 'BO type = PptUserStruct, userID(containment),password = sbt,newPassword = null (default),functionID = null (default),clientNode = localhost, siInfo(containment),' is not contained in a resource. at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.handleDanglingHREF( XMLHelpe rImpl.java:448) at L3 explanation after investigation - - PPTServiceManagerProxyOtoZmapper.wsdl contains inline schema which imports namespace "http://client.siviewproxy.connector.wor kflow.siview.ibm.com", which will cause coreFramework try to load all schemas belong to "http://client.siviewproxy.connector. workflow.siview.ibm.com", including NotificationManagermapper.ws dl which contribute to this namespace. Unfortunately, the NotificationManagermapper.wsdl also contains an inline schema which imports the namespace "http://client.siviewproxy.connector.workflow.siview.ibm.com", and PPTServiceManagerProxyOtoZmapper.wsdl is contribute to this namespace too. Thus the in-memory Schema instance of inline schema in NotificationManagermapper.wsdl will refer to those schemas defined in PPTServiceManagerProxyOtoZmapper.wsdl. When BO is trying to build the model for those inline schemas in NotificationManagermapper.wsdl, it will also build the model for inline schemas in PPTServiceManagerProxyOtoZmapper.wsdl as well, but those inline schemas in PPTServiceManagerProxyOtoZmapper.wsd l is not resolved at this moment, so those elements defined in PPTServiceManagerProxyOtoZmapper.wsdl will be mapped to non-containment feature in the ecore model. LOCAL FIX: L3 has found root cause and prototyped a fix (3.24.2008) PROBLEM SUMMARY USERS AFFECTED: Websphere Process Server version 6.0.2 users. PROBLEM DESCRIPTION: BusinessObject CoreFramework is not able to resolve some complex type definitions, hence sets the complex types containment properties to false. RECOMMENDATION: None The non-containment problem occurs if the inline schemas in different WSDL definitions import the same namespace and contribute some complex type definitions to the namespace. In such scenarios, BusinessObject CoreFramework is not able to resolve the complex types. PROBLEM CONCLUSION: An interim fix is delivered to modify the BusinessObject CoreFramework behavior to be able to resolve these complex types. 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: