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.  Rosetta Net PIP3A4 Outbound Problem

    Posted Thu February 23, 2006 10:32 PM

    I’m trying to send an outbound PIP3A4 as a Buyer. When I submit the document to TN, it is recognized correctly as my Buyer internal document. However, after the document leaves my outbound map step, it’s Document Type in the TN Activity Log becomes a PIP3A4vV02.02 Purchase Order Request Action Seller Document and the Sender and Receiver roles are reversed. Then, when TN attempts to submit the document, I get the following error:

    Preferred protocol not specified.

    However, the partner who I am trying to send to does have a preferred protocol. I’m guessing that TN is actually trying to submit the document back to my profile.

    When I setup the agreement, I copied the PIP3A4vV02.02 Purchase Order Request Action Buyer Internal Document agreement and changed the Sender and Receiver accordingly and set the Agreement ID to the name of the TN Internal Document.


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


  • 2.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Thu February 23, 2006 10:42 PM

    Has anyone ever seen this before?

    Maybe I missed a step somewhere? I disabled all of my PIP3A4 agreements except for the one I modified, but that didn’t help either.

    Thanks
    Marc


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


  • 3.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Thu February 23, 2006 10:50 PM

    Is your PIP internal document for outbound matching with sender/receiver/doctype as per agreement/processingrule/documenttype criteria which are extracting from the 3A4 document? based on TP setup.

    What is your Activitylog shows is it triggering with correct rules/partner recognition etc…?

    HTH,
    RMG


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


  • 4.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Thu February 23, 2006 11:11 PM

    My outbound document is matching the correct receiver / sender / document type in TN. Then, it triggers my outbound mapping service.

    Once it leaves my outbound mapping service, the service that sends the document externally is called. This is where the error happens. When I look at the pipeline for this service in the Monitor, the document content is correct but the Sender and Receiver portions of the TPA are reversed. When I look at this document in TN, the the Document Type is NOT correct (Seller instead of Buyer) and the Sender and Receiver portions are also reversed.

    So to try and put it as simply as possible:

    1. Send document to TN
    2. Document is persisted in TN. Document Type = Custom Outbound Document. Sender = me, Receiver = Cisco
    3. Outbound mapping service is called
    4. Document is persisted in TN. Document Type = PIP3A4vV02.02 Purchase Order Request Action Seller Document. Sender = Cisco, Receiver = me
    5. Document fails on send, with “Preferred Protocol not specified” error

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


  • 5.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Fri February 24, 2006 12:46 AM

    Thanks for details.

    Let me try if i can help on this situation.

    Hope someone will chim lite on this.

    RMG.


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


  • 6.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Wed March 01, 2006 02:55 PM

    The problem was resolved. I did not set the Focal Role to “Buyer” in the Modeler.


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


  • 7.  RE: Rosetta Net PIP3A4 Outbound Problem

    Posted Wed March 01, 2006 04:10 PM

    Glad to know you have resolved the problem its a good catch,Thanks for the update.


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