JR44613: WEB SERVICE ADBEXCEPTION ISSUE

Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• BPMV8 webservice failed to be invoked, ADB exception thrown out
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  User who builds Web Integration Service on  *
  *                  BPM.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: BPM V8 Webservice failed to be          *
  *                      invoked, ADB exception thrown out.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer has developed a Web integration service on BPM.
  Customer find out the message from BPM v8 is not able to be
  recognized by the Web service provider, complained that
  namespace was not identified.
  They see the messages as below:
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <soapenv:Body>
  <ns1:InvokeBOPSENQServiceByRemote
  xmlns:ns1="http://service.bo.avivacofco.com">
  <ns1:mBOParaSchema>
  <ns0:BOPSENQ_AL_FIELDS_BGEN_ZBINSTPREM_SFL_BGEN_ZBINSTPREM_SIGN
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns0:BOPSENQ_AL_FIELDS_BGEN_ZLINSTPREM_SFL_BGEN_ZLINSTPREM_SIGN
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns0:BOPSENQ_AO_REC_MESSAGE_DATA_ADDITIONAL_FIELDS_BGEN_ACCRCCY
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns1:BOPSENQ_AO_REC_MESSAGE_DATA_ADDITIONAL_FIELDS_BGEN_AGNTNUM
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns0:BOPSENQ_AO_REC_MESSAGE_DATA_ADDITIONAL_FIELDS_BGEN_BANKKEY
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns1:BOPSENQ_AO_REC_MESSAGE_DATA_ADDITIONAL_FIELDS_BGEN_BROKNUM
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  <ns1:BOPSENQ_AO_REC_MESSAGE_DATA_ADDITIONAL_FIELDS_BGEN_CHDRCOY
  xmlns:ns0="http://schema.bo.avivacofco.com/xsd"/>
  

Problem conclusion

• The fix was to properly serialize XML string and append it to
  the SOAP request.
  
  For details of install/uninstall instructions, please download
  the README file along with the ifix file from Fix Central.
  

Temporary fix

Comments

APAR Information

• 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