Fixes are available
APAR status
Closed as fixed if next.
Error description
USER AFFECTED: Users who create PropertyAlias objects in different files from the Property objects, either by hand or from a different BPEL tool. PROBLEM SUMMARY: The problems view will show errors relating to correlation sets not being found. PROBLEM DETAILED DESCRIPTION: These BPEL extensions in the WSDL file are physically located above the WSDL imports, when the model is being read in the PropertyAlias objects don't resolve the Property objects as the model doesn't know about the imports at this point. TEST CASE: 1. Import PI provided by customer. 2. Do a clean/buildthe errors Result: The errors.
Local fix
Manually put the Property and PropertyAlias objects in the same file.
Problem summary
************************************************************** * Maintenance stream beyond BPM Adv. 7.5.0 Fixpack 1 will be * * 7.5.1. APAR has been fixed with 7.5.1 GA. * ************************************************************** When using the BPEL import from developerworks to import a WS-BPEL 2.0 busines process into WebSphere Integration Developer the structure of the imported WSDL files with respect to property and propery alias can lead to validation errors like this: - A matching correlation property entry was not found for the callerIdProperty correlation property and the CirpackBasicChangeResponseMessage message type (ReceiveCirpackBasicChange activity, CallerIdCorrelationSet correlation set). - A matching propertyAlias definition was not found for the property 'callerIdProperty' and messageType 'traiterB2eCreationAlerteMessage' (receive choice activity 'PickAlerteDecision', receive element number 1, correlation set 'CallerIdCorrelationSet'). when property and property alias are located in different WSDL files.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR40662
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
750
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-19
Closed date
2011-11-11
Last modified date
2011-11-11
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
R751 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021