A fix is available
APAR status
Closed as program error.
Error description
In most of our business processes we have to invoke rules which have String arrays as outputs. However, whenever BPM is parsing the WODM response (which is correct) all other parts of the response (e.g. booleans) are added to the list of Strings in PD (see bpm_result.txt for details). Attached you'll find a sample WODM response (and the corresponding WSDL) and the result after parsing in PD. I will upload the TWX as soon as the PMR is created. In that toolkit you'll find the Decision Service "Aufbereitung Emailadressen AD" that uses a String list in the output parameter mapping. bpm_result.txt versionInfo.txt wodm_response.txt TWX file will be sent ASAP by Michael. bpm_result shows: **************************************************************** ******** Actual result in PD: ==================== <object type="String[]"> <arrayElement size="4"> <item type="String">1</item> <item type="String">vermittlerinfo@dmarco@vkb.de</item> <item type="String">vermittlerinfo@dmischa@vkb.de</item> <item type="String">true</item> </arrayElement> <metadata> <property name="dirty" type="Boolean">true</property> <property name="shared" type="Boolean">false</property> <property name="key" /> <property name="version" /> </metadata> </object> You'll find the decision ID as first element and the flagEmailOk as last element of the array. Expected result in PD: ====================== <object type="String[]"> <arrayElement size="2"> <item type="String">vermittlerinfo@dmarco@vkb.de</item> <item type="String">vermittlerinfo@dmischa@vkb.de</item> </arrayElement> <metadata> <property name="dirty" type="Boolean">true</property> <property name="shared" type="Boolean">false</property> <property name="key" /> <property name="version" /> </metadata> </object> **************************************************************** ******** wodm_response.txt **************************************************************** ******** <?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ds="http://www.ibm.com/rules/decisionservice/AllRuleSetsRu leApp/Au fbereitungEmailadressenAD"> <soapenv:Body> <AufbereitungEmailadressenADResponse xmlns="http://www.ibm.com/rules/decisionservice/AllRuleSetsRuleA pp/Aufbe reitungEmailadressenAD"> <DecisionID xmlns="http://www.ibm.com/rules/decisionservice/AllRuleSetsRuleA pp/Aufbe reitungEmailadressenAD">1</DecisionID> <eMail>vermittlerinfo@dmarco@vkb.de</eMail> <eMail>vermittlerinfo@dmischa@vkb.de</eMail> <flagEmailOK xmlns="http://www.ibm.com/rules/decisionservice/AllRuleSetsRuleA pp/Aufbe reitungEmailadressenAD">true</flagEmailOK> </AufbereitungEmailadressenADResponse> </soapenv:Body> </soapenv:Envelope> **************************************************************** ********
Local fix
na
Problem summary
**************************************************************** * USERS AFFECTED: Applications using simple type String * * array in their web services call. * **************************************************************** * PROBLEM DESCRIPTION: Extra elements are added when parsing * * the web services response. * **************************************************************** * RECOMMENDATION: * **************************************************************** When parsing a response of simple type String array, other parts of the schema are being appended to the final result. During serialization BPM does not have knowledge of the child element names when obtained from the root element. Therefore, all elements are retrieved and processed.
Problem conclusion
Code changes have been made to properly obtain the child element names and process only the necessary elements of the response. An interim ifix will be available on BPM V8.0.1.0 and will be integrated into the next fix pack. 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
JR45001
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-04
Closed date
2013-03-03
Last modified date
2013-03-03
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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 October 2021