Fix (APAR): JR25528 Status: Fix Release: 6.0.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 9755 Date: 2006-12-28 Abstract: During deployment of a BPEL application, build completes successfully, but many errors are seen. Description/symptom of problem: JR25528 resolves the following problem: ERROR DESCRIPTION: While deploying a BPEL process to the WPS server, the build completes successfully and the suddenly during the deployment, there are many errors like the following: [11/28/06 16:07:29:632 EST] 0000009a TraceBPE < com.ibm.bpe.validation.BPELValidation.validateExecutableBPELExte nsionsProcess(BPELValidation.java:330) RETURN [11/28/06 16:07:29:632 EST] 0000009a TraceBPE 3 com.ibm.bpe.deployment.BPELDeployer.installBPEL(BPELDeployer.jav a:587) CWWBV0003E: Validated process model 'DeleteProcess' with findings: 128 errors, 0 warnings, 0 information: CWWBV3186E: The parameter 'item' must be removed or mapped to an element or part (activity 'DeleteAccount', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAccount'). CWWBV3186E: The parameter 'removeAccountReturn' must be removed or mapped to an element or part (activity 'DeleteAccount', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAccount'). CWWBV3186E: The parameter 'item' must be removed or mapped to an element or part (activity 'DeleteAddress', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAddress'). CWWBV3186E: The parameter 'removeAddressReturn' must be removed or mapped to an element or part (activity 'DeleteAddress', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAddress'). .... This problem occurs when: For bpel applications that have a) multiple wsdls sharing a same namespace b) multiple of them have inline schemas sharing a same namespace c) these share a same namespace wsdls import/include each other d) those types defined in inline schema are used by wsdl porttype/message/part, during application installation, there MAY be bpel validation errors and application install could fail. This APAR fixes these problems. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server, WebSphere Enterprise Service Bus 6.0.1 users. PROBLEM DESCRIPTION: During deployment of a BPEL application, build completes successfully, but many errors are seen. RECOMMENDATION: None While deploying a BPEL process to the WPS server, the build completes successfully and then suddenly during the deployment, there are many errors like the following: [11/28/06 16:07:29:632 EST] 0000009a TraceBPE < com.ibm.bpe.validation.BPELValidation.validateExecutable BPELExtensionsProcess(BPELValidation.java:330) RETURN [11/28/06 16:07:29:632 EST] 0000009a TraceBPE 3 com.ibm.bpe.deployment.BPELDeployer.installBPEL(BPEL Deployer.java:587) CWWBV0003E: Validated process model 'DeleteProcess' with findings: 128 errors, 0 warnings, 0 information: CWWBV3186E: The parameter 'item' must be removed or mapped to an element or part (activity 'DeleteAccount', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAccount'). CWWBV3186E: The parameter 'removeAccountReturn' must be removed or mapped to an element or part (activity 'Delete Account',parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAccount'). CWWBV3186E: The parameter 'item' must be removed or mapped to an element or part (activity 'DeleteAddress', parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAddress'). CWWBV3186E: The parameter 'removeAddressReturn' must be removed or mapped to an element or part (activity 'Delete Address',parameter 1). CWWBV3192E: The message-part 'parameters' is not mapped to a parameter (activity 'DeleteAddress') This problem occurs when: For bpel applications that have a) multiple wsdls sharing a same names pace b) multiple of them have inline schemas sharing a same namespace c) these share a same namespace wsdls import/include each other d) those types defined in inline schema are used by wsdl porttype/message/part, during application installation, there MAY be bpel validation errors and application install could fail. PROBLEM CONCLUSION: This ifix will fix these errors. 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: