IT13895: INVALID WSDL IN SOAP NODE IS NOT DETECTED AT DEPLOY TIME

APAR status

• Closed as program error.

Error description

• When a SOAP node in a message flow has been configured with an
  invalid WSDL name, the problem is not detected at deploy time if
  the Bar file contains a sub flow with a SOAP node that specifies
  a valid WSDL name.
  
  The error is only detected when the message flow is restarted.
  The following error messages may occur:
  
  BIP3726E: Failed to setup SOAP transport for node SOAP Input.
  
  BIP3732E: The specified WSDL binding <WDSL binding name>  could
  not be found in the supplied WSDL file <WSDL file name>.wsdl.
  

Local fix

• The work around is to correct the invalid WSDL name in the SOAP
  node and redeploy.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10 who deploy a message flow
  containing a SOAP node which has been configured with an invalid
  wsdl file name.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A deployment completes even when it contains a SOAP node
  configured with an invalid wsdl file name.
  
  When the IBM Integration Bus server is restarted the message
  flow that contains the invalid wsdl file name will fail to
  start. The following sequence of messages may be observed in the
  system log.
  
  1/3) BIP2275E: Error loading deployed resource '<resource id>'
  of type '.CMF'.
  2/3) BIP3726E: Failed to setup SOAP transport for node SOAP
  Input.
  3/3) BIP3732E: The specified WSDL binding binding name>
         could not be found in the supplied WSDL file <invalid
  wsdl file name>.
  1/1) BIP2154I: Execution group finished with Configuration
  message.
  
  
  <i>There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm</i>
  

Problem conclusion

• The product now detects an invalid wsdl file name at deploy
  time, and outputs an error message similar to the following:
  
  BIP3838E The specified WSDL binding <binding name>  could not be
  found in the supplied WSDL file <wsdl file name>.
  
  The WSDL binding <binding name> from the target namespace
  <namespace> associated with shared library <library name>  was
  not found in the WSDL file <wsdl file name>. This could be
  because the WSDL file is missing, invalid or corrupt.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.1
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IT04975

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP