IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  checkUser ABORTED

    Posted Mon August 08, 2011 06:31 PM

    The Problem is when the partner submit using wm.tn:receive

    When they submit the document, the document is recognizing and posting in the trading network successfully. But the processing status is changing to “ABORTED” and the error is : The user that posted this document (Default) could not be associated with a partner to check their identity.

    In the activity log, the user is “default”

    The customer is posting thru https,

    Created User on TNPartner group and provided username and passwrd to customer…

    No certificates.


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 2.  RE: checkUser ABORTED

    Posted Tue October 04, 2011 12:41 AM

    Suspect
    According to the error, it looks like “Default” user does not have proper priviledge and most probably is not part of the group TNAdministrator it is failing in TN.

    Findings
    Notice that there is a clause in Trading Network Built-in Reference document. For version 8.0 documentation, you can get it here:
    http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite8_ga/Trading_Networks/8-0-SP1_Trading_Networks_Built-In_Services_Reference.pdf

    wm.tn:receive service:
    This service ensures that the sender of the document matches the current user. If you are
    sending documents from within processing rules or services and this identify check fails,
    see wm.tn.doc.xml:routeXml.

    wm.tn.doc.xml:routeXml
    Recognizes an XML document and submits it for processing.
    This service does not check the identity of the sender against the currently logged in user.
    Only invoke this service from within processing rules or services; do not expose directly
    to trading partners. Trading partners should use wm.tn:receive.

    Possible Solution
    Solution to this could be in 2 option:

    1. Change related service to use wm.tn.doc.xml:routeXml instead of wm.tn:receive

    2. Assign “Default” user to TNAdministrator group. But by adding this, you might need to review if there is any security impact to your system.

    And please check if “Default” user or a proper user has been created in TN - partner ID. If they have, try mapping the partner ID to the IS user by using wm.tn.profile:addUsers and try again.

    Hope this helps.


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


Related Content