IBM Support

IT29826: CANNOT RESOLVE XSDS FOR SAP OPERATIONS IN THE SAME RESOURCE GROUP BUT DIFFERENT NAMESPACES

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

  • It is possible during discovery of SAP objects to specify the
    namespace that schema files are generated in to allow
    interacting with multiple SAP system that may have different
    definitions of the same object.
    
    If the same operation is discovered on 2 different adapters and
    the schema files are placed within the same container
    (application or library) but in separate sub directories then
    the following error is generated when the schemas are first
    accessed by SAP Adapter code:
    
    
    Jul 24 15:59:34 karnivool ACE[21780]: IBM App Connect
    Enterprise v11004 (ACESAP1WAY.default)
    
    [Thread 27970] (Msg 5/5) BIP3424E: Message type
    'SapBapiCustomerGetdetail' is not present in message set ''.
    Message types contained in the message set are:
    
    <list of deployed types>
    
    
    The problem is caused by the import resolution process in ACE
    v11, in this code if 2 or more candidate matches are found for
    a specific xsd name (which amtches the SAP operation name) then
    the code does not know which one is the correct copy and fails
    to resolve the schema.
    
    The code should check the namespaces of each file to determine
    if there is a unique match which is in the correct namespace.
    
    
    Additional Symptom(s) Search Keyword(s):SAP namespaces, xsds,
    BIP3424E
    

Local fix

  • Best practice would be to create artifacts for different SAP
    systems in separate static libraries., in this case the code
    searches in its own container first and therefore does not hit
    the problem.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise v11 using SAP adapters with
    custom namespaces.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">It is possible
    during discovery of SAP objects to specify the </span><span
    style="background-color:rgb(255, 255, 255)">namespace that
    schema files are generated in to allow </span><span
    style="background-color:rgb(255, 255, 255)">interacting with
    multiple SAP system that may have different </span><span
    style="background-color:rgb(255, 255, 255)">definitions of the
    same object.                                </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">If the same
    operation is discovered on 2 different adapters and </span><span
    style="background-color:rgb(255, 255, 255)">the schema files are
    placed within the same container </span><span
    style="background-color:rgb(255, 255, 255)">(application or
    library) but in separate sub directories then  </span><span
    style="background-color:rgb(255, 255, 255)">the following error
    is generated when the schemas are first </span><span
    style="background-color:rgb(255, 255, 255)">accessed by SAP
    Adapter code:                                  </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span><span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">Jul 24
    15:59:34 karnivool ACE[21780]: IBM App Connect </span><span
    style="background-color:rgb(255, 255, 255)">Enterprise v11004
    (ACESAP1WAY.default)                         </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">[Thread 27970]
    (Msg 5/5) BIP3424E: Message type </span><span
    style="background-color:rgb(255, 255,
    255)">'SapBapiCustomerGetdetail' is not present in message set
    ''.   </span><span style="background-color:rgb(255, 255,
    255)">Message types contained in the message set are:
                   </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)"><list of
    deployed types>                                       </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span><span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">The problem is
    caused by the import resolution process in ACE  </span><span
    style="background-color:rgb(255, 255, 255)">v11, in this code if
    2 or more candidate matches are found for </span><span
    style="background-color:rgb(255, 255, 255)">a specific xsd name
    (which matches the SAP operation name) then </span><span
    style="background-color:rgb(255, 255, 255)">the code is unable
    to determine which the correct copy to use and fails
    </span><span style="background-color:rgb(255, 255, 255)">to
    resolve the schema.
    </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span><span style="background-color:rgb(255, 255, 255)">
    
    </span><span style="background-color:rgb(255, 255, 255)">
    
    </span>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT29826

  • 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-07-24

  • Closed date

    2019-12-18

  • Last modified date

    2019-12-18

  • 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:
18 December 2019