JR41732: NEED TO COMPLETELY REMOVE OR HAVE AN OPTION TO REMOVE XSI:TYPE FROM THE SOAP REQUEST THAT IS FORMED BY BPM

APAR status

• Closed as program error.

Error description

• SOAP request is being created with an xsi:type attribute.  Other
  systems do not use this and it causes the Web Service provider
  to not accept the response.
  

Local fix

• change the message after its created or adjust Web Service
  provider.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, Standard and          *
  *                  Advanced 7.5.1                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: SOAP request is being created with an   *
  *                      xsi:type attribute.  Other              *
  *                      systems do not use this and it causes   *
  *                      the Web Service provider                *
  *                      to not accept the response.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SOAP request is being created with an
  xsi:type attribute.  Other
  systems do not use this and it causes
  the Web Service provider
  to not accept the response.
  

Problem conclusion

• The problem was fixed by moving to a new JAX-WS Based
  implementation.
  A JAX-WS API based implementation for
  outbound BPM Web Services was introduced.  The existing
  outbound BPM Web Service implementation is the default.
   To enable the JAX-WS implementation (after installing
  JR42012) the 99Local.xml file must be modified to include a
  child element to the <common> element with a value of
  <use-jaxws>true</use-jaxws> .
  
  Also note that the following known issues are also fixed by
  moving to the new JAX-WS based implementation:
  1. Outbound SOAP request contains xsi:type when not necessary
  2. Error when using Custom SOAP Headers in Web Service
  Integration
  3. "Basic" HTTP authorization mode is not supported by Web
  Service Integration
  4. When calling a Web Service, the results cannot be put into
  a generic Record object
  5. Outbound SOAP Request Missing Elements When WSDL/Schema
  Elements Contain Hyphens
  6. WS-Addressing Header Is Always Present in the Outbound SOAP
  Request When Username Token Digest or Plaintext Enabled
  
  
  ***It is important to note that if the JAX-WS implementation is
  enabled that WSDLs containing a style of "rpc" and use of
  "encoded" are no longer supported and will cause an
  exception.***
  
  This fix is available in the JR42012 package for 7.5.1.
  
  More details on installing JR42012 can be found at:
  http://www-01.ibm.com/support/docview.wss?uid=swg1JR42012
  

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 STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R750 PSY

     UP