Fixes are available
APAR status
Closed as program error.
Error description
When installing a Process App or Ear file with BPEL processes, it might fail with a message similar to this: CWWBV0002E: Validated process model 'MyBPELProcess' with findings: 2 errors, 0 warnings, 0 information. CWWBV3187E: The XSD type definition 'MyInputBO' was not found (activity 'Receive', parameter number 1, matching part or element 'MyInputType'). This is also a behavioral change in BPM 8.0.1. You would not have the same validation errors for your application prior to that version. That error is pretty generic and means that the xsd type definition for the named element could not be found in the application. For this issue the element would be defined in the application but issues with the WSDLMerger function used in validation which causes the WSDL interface definition to be incorrectly read. This will occur when you have multiple WSDL files defined with the same targetNamespace but different namespaces(xmlns) defined for the schema. These will be merged during the validation but the xmlns values might become incorrect. For example you might see the issue if you have two WSDLs with a schema tag similar to this pattern. Interface1.wsdl <xsd:schema xmlns:NS1="http://namespace1" xmlns:NS3="http://namespace3" targetNamespace="http://namespace4" > Interface2.wsdl <xsd:schema xmlns:NS2="http://namespace2" xmlns:NS3="http://namespace3" targetNamespace="http://namespace4" > In the artifact loader trace you might see a message similar to this which has an incorrect namespace: [7/2/13 10:15:48:467 CDT] 00000034 ArtifactLoade 2 com.ibm.ws.ar.WSDLMerger mergeAttributes(Element, Element, URI) Added attribute: xmlns:NS2="http://namespace4"
Local fix
Manually modify the WSDL files in your application which uses the same targetNamespace. Ensure each WSDL file uses the same xmlns definitions.
Problem summary
**************************************************************** * USERS AFFECTED: Business Process Manager Advanced users * **************************************************************** * PROBLEM DESCRIPTION: Application install failed due to * * BPEL validation errors when install * * EAR contains BPC into BPM advanced * * server. * **************************************************************** * RECOMMENDATION: * **************************************************************** Starting from BPM Advanced V8. Business Process Choreographer (BPC) had made some update in BPEL validation which used some unimplemented functions for artifact loader which results some BPEL validation error. The error related to some XSD cannot be found caused by incorrect behavior by the WSDL merger which is in turn used by the validator. The net effect is that the namespace and prefix may not match after merge.
Problem conclusion
This iFix implements the functions for the WSDL merger and correctly merges the namespace and prefixes used in the WSDL. Install/Dependency information is available in the readme.txt on FixCentral. When the user goes to the download files page in FixCentral, the readme will be available with the fix package as a separate download.
Temporary fix
Comments
APAR Information
APAR number
JR47245
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-16
Closed date
2013-09-25
Last modified date
2013-09-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022