IBM Support

IT30218: BIP3424 EXCEPTION WHEN USING THE DATAOBJECT PARSER AND THE SAP ALE IDOC PHYSICAL FORMAT WITH XSD SCHEMAS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When parsing a SAP IDoc using the the DataObject parser in the
    SAP ALE IDoc physical format and XSD schema files the following
    exception may occur:
    
    BIP3424E RecoverableException createMetaData 'attempted to use
    type which is not in the message set. TypeName:SapMatmas05 Fully
    Qualified
    Name:http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/matmas/sap
    matmas05:SapMatmas05 Application: Valid Types:' ['SapMatmas05',
    '', '']   MbErrorHandler.java:115
    BIP3472E ParserException        parseIdoc 'MbException caught in
    parseIDOC'   MbAdapterDirector.java:601 <Nested: BIP3424E>
    
    Additional Symptom(s) Search Keyword(s): SAP ALE IDoc, BIP3424E,
    BIP3472E
    

Local fix

  • Deploy either an inbound or outbound adapter that is configured
    to process IDocs of the type that is being parsed. This adapter
    does not need to be used in a message flow, it merely needs to
    be deployed in the same application or static library as the XSD
    schemas.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise v11 implementing the SAP
    IDoc gateway pattern with XSD schemas instead of message sets.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When parsing a SAP IDoc using the the DataObject parser in the
    SAP ALE IDoc physical format and XSD schema files the following
    exception may occur:
    
    BIP3424E RecoverableException createMetaData 'attempted to use
    type which is not in the message set. TypeName:SapMatmas05 Fully
    Qualified
    Name:http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/matmas/sap
    matmas05:SapMatmas05 Application: Valid Types:' ['SapMatmas05',
    '', '']   MbErrorHandler.java:115
    BIP3472E ParserException        parseIdoc 'MbException caught in
    parseIDOC'   MbAdapterDirector.java:601 <Nested: BIP3424E>
    
    Additional Symptom(s) Search Keyword(s): SAP ALE IDoc, BIP3424E,
    BIP3472E
    

Problem conclusion

  • A new parameter is available in the server.conf.yaml file under
    the SAPConnectorProvider block named
    enableStandaloneIDocParsing. If this property is set to true
    then XSDs schemas in an application or static library will
    always be loaded by the DataObject parser at deploy time ready
    for use in parsing later in a message flow. The default value
    for this property is false, so affected users must explicitly
    opt into this behaviour as it increases deploy times. It is not
    necessary to set this property to true if there are also
    inadapter on outadapters deployed in the application or its
    static libraries.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.6
    
    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

    IT30218

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-09

  • Closed date

    2020-01-08

  • Last modified date

    2020-01-08

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
08 January 2020