Direct links to fixes
APAR status
Closed as program error.
Error description
Environment: BPM 8.5.7 CF 2016_12 Scenario: Deployment of an application created on an earlier BPM version to BPM 8.5.7 CF 2016_12 Observation: Deployment fails. Sample exception: [1/12/17 13:03:32:999 CET] 000002cc BPELValidatio E CWWBV3136E: The messageType is not set in the output element of the operation 'getArchiveConfig' (activity 'InvokegetArchiveConfig'). [1/12/17 13:03:33:113 CET] 000002cc FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/WebSphere/Proc/DeploymentManager/profiles/TestDmgr/logs/f fdc/dmgr_c1234567_17.01.10_10.00.00.0265528918110449939867.txt com.ibm.ws.management.application.SchedulerImpl.run 328 [1/12/17 13:03:33:323 CET] 000002cc InstallSchedu I ADMA5014E: The installation of application XYZ123App failed. [1/12/17 13:03:33:027 CET] FFDC Exception:com.ibm.websphere.management.exception. AdminException SourceId:com.ibm.ws.management.application.SchedulerImpl.run ProbeId:328 Reporter:java.lang.Class@b43fce0f com.ibm.websphere.management.exception.AdminException: CWWBF0029E: Process components of XYZ123App cannot be configured in WebSphere configuration repository. at com.ibm.bpe.management.application.AbstractDeploymentTask. throwAdminException(AbstractDeploymentTask.java:158) at com.ibm.bpe.management.application.process.NativeBFM ApplicationConfigureTask.configureComponents(Native BFMApplicationConfigureTask.java:168) at com.ibm.bpe.management.application.AbstractDeploymentTask. performTask(AbstractDeploymentTask.java:99) at com.ibm.ws.management.application.SchedulerImpl.run (SchedulerImpl.java:315) at java.lang.Thread.run(Thread.java:809) Caused by: com.ibm.websphere.management.exception.AdminException: CWWBF0110E: The following unexpected error occurred during validation of the ABCArchive.bpel process: {1} at com.ibm.bpe.management.application.AbstractDeploymentTask. throwAdminException(AbstractDeploymentTask.java:158) at com.ibm.bpe.management.application.process.ProcessSCA Archive.loadBPELResource(ProcessSCAArchive.java:1279) at com.ibm.bpe.management.application.process.ProcessSCA Archive.createBPELContext(ProcessSCAArchive.java:615) at com.ibm.bpe.management.application.process.ProcessSCA Archive.initBPELProcessContexts(ProcessSCAArchive.java:359) at com.ibm.bpe.management.application.process.ProcessSCA Archive.<init>(ProcessSCAArchive.java:191) at com.ibm.bpe.management.application.process.ProcessSCA Archive.<init>(ProcessSCAArchive.java:257) at com.ibm.bpe.management.application.process.ProcessSCA Archive.<init>(ProcessSCAArchive.java:218) at com.ibm.bpe.management.application.process.NativeBFM ApplicationConfigureTask.configureComponents(NativeBFM ApplicationConfigureTask.java:114) ... 3 more Caused by: com.ibm.bpe.plugins.BPELValidationException: CWWBV0003E: Validated process model 'ABCArchive' with findings: 2 errors, 0 warnings, 0 information: CWWBV3135E: The messageType is not set in the input element of the operation 'getArchiveConfig' (activity 'InvokegetArchiveConfig'). CWWBV3136E: The messageType is not set in the output element of the operation 'getArchiveConfig' (activity 'InvokegetArchiveConfig').
Local fix
n/a
Problem summary
When the definition of an interface in a process model contains multiple WSDL files, and the WSDL files contain duplicate prefix for same namespace, for example WSDL 1 contains xmlns:bons1="http://example.com/request" WSDL 2 contains xmlns:bons1="http://example.com/request" these WSDL files merge at run time for validation. In some situations, the duplicate prefix is defined in <wsdl:definitions> and <xsd:schema> elements respectively; therefore, this prefix should be defined in <wsdl:definitions> in the merged WSDL, otherwise it could cause the validation of the process model to fail during the installation.
Problem conclusion
A fix is available for the IBM BPM V8.5.7.0 2016.12 that corrects the prefix merging algorithm to make sure the duplicate prefix defined at <wsdl:definitions>.
Temporary fix
Comments
APAR Information
APAR number
JR57414
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-13
Closed date
2017-02-21
Last modified date
2017-02-21
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
[{"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":"857","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 September 2023