Fixes are available
APAR status
Closed as fixed if next.
Error description
The Webservices component cannot properly consume messages with the following aspects: -rpc encoded -uses an array where each entry is a multiref reference. -uses lazy parsing. For example: <ns1:getBasicBillingInfoResponse <getBasicBillingInfoReturn arrayType="ns2:BasicBillingInfo[3]" xsi:type="soapenc:Array"> <getBasicBillingInfoReturn href="#id0"/> <getBasicBillingInfoReturn href="#id1"/> <getBasicBillingInfoReturn href="#id2"/> </getBasicBillingInfoReturn> <the referenced array entries follow> In this example there are supposed to be 3 entries in the array. However, when this message is processed, only the first entry that uses reference #id0 is propogated into the DataObject/BO. The subsequent entries, #id1 and #id2, of the array are discarded. This APAR will resolve the issue and the correct number of entries in the array will be populated.
Local fix
If the service cannot be adjusted to avoid either RPC encoded or multiple multiref arrays,a valid workaroud is to use Eager Parsing. The Eager Parsing mode will correctly populate all the entries in the array.
Problem summary
**************************************************************** * USERS AFFECTED: Business Process Management users * **************************************************************** * PROBLEM DESCRIPTION: JAX-RPC binding wrongly ignores the * * following message aspects: * * -rpc encoded * * -uses an array where each entry is a * * multiref reference. * * -uses lazy parsing. * **************************************************************** * RECOMMENDATION: * **************************************************************** When encountering a schema such as the one below, the BO Parser only handles the first reference and erroneously ignores subsequent ones. <ns1:getBasicBillingInfoResponse <getBasicBillingInfoReturn arrayType="ns2:BasicBillingInfo[3]" xsi:type="soapenc:Array"> <getBasicBillingInfoReturn href="#id0"/> <getBasicBillingInfoReturn href="#id1"/> <getBasicBillingInfoReturn href="#id2"/> </getBasicBillingInfoReturn> The issue is fixed in Business Process Manager Version 8.0.1 Fix Pack 1 (8.0.1.1).
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR44078
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-12
Closed date
2012-12-13
Last modified date
2013-10-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 October 2013