IBM Support

IC98259: MAPPING NODE REPORTS ERROR UNABLE TO RESOLVE SOAP_DOMAIN_MSG SCHEMA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The problem affects users of IIB who have a Map that is
    mapping a SOAP Domain message and the IBM Defined SOAP Domain
    Message schema "IBMDefined/soap.xsd" has been imported into more
    than one Library that is deployed along with the Mapping node.
    If the fixpack function level is set to 9001 or above the
    following error occurs on deployment, otherwise it occurs on the
    first message in the flow:
    
    BIP3944E: The map script generation for QName
    '{www.example.org}:ST_CTMapping_ESQL_Mapping' has failed, with
    the following details: Location: 'Unsupported, or unresolved
    schema model for map output:
    mb:msg(SOAP_Domain_Msg,assembly,SOAP,Properties)
    

Local fix

  • The Maps can be updated to reference the inbuilt SOAP domain
    message schema, or the duplicated IBMdefined/soap.xsd can be
    removed from one of the Libraries.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus who use the Mapping node to
    transform messages in the SOAP domain using the IBM defined
    schema.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The Mapping node might fail with error message BIP3944E
    reporting that the schema "IBMDefined/soap.xsd" for the
    message SOAP_Domain_Msg cannot be resolved.
    
    This will only occur when the IBM defined SOAP domain message
    schema has been imported into more than one Library that is
    included in the deployed Application and the Map was created
    with reference to one of these schema, rather than the built
    in SOAP domain message.
    
    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
    

Problem conclusion

  • The product is corrected and maps referencing the IBM defined
    SOAP domain schema "IBMDefined/soap.xsd" deploy successfully.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.2
    
    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 number

    IC98259

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-12-11

  • Closed date

    2014-02-03

  • Last modified date

    2014-02-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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 February 2014