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.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
Expand all | Collapse all

Pipeline Matching Variable in TN Document

  • 1.  Pipeline Matching Variable in TN Document

    Posted 05/11/11 07:25 PM

    Hi,

    Does any one knows or have worked with Pipeline Matching Variables that can be defined while defining TN document?

    Please let me know how to use that feature?
    I want to set SenderID and ReceiverID with constant value for that particular document type.

    Any suggestions would be appreciated.

    Thanks,
    Shweta


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


  • 2.  RE: Pipeline Matching Variable in TN Document

    Posted 05/11/11 10:15 PM

    What exactly you want to send in the document? you want to pass the params in the TN_params?

    Are you creating some document type that sender/receiver identifiers and use for extract and recognize?

    HTH,
    RMG


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


  • 3.  RE: Pipeline Matching Variable in TN Document

    Posted 05/12/11 07:14 PM

    I want to pass SenderID and ReceiverID in that document. I tried to pass it through TN_Params, but not sure how to extract from it.

    Please advice.


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


  • 4.  RE: Pipeline Matching Variable in TN Document

    Posted 05/13/11 03:38 PM

    In which service you are tried passing params? Is it routeXML or tn:receive or routeFlatfile?

    TN will automatically extract and recognize…but this only works when you route flat files note it:

    [url]wmusers.com

    HTH
    RMG


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


  • 5.  RE: Pipeline Matching Variable in TN Document

    Posted 05/13/11 03:40 PM


  • 6.  RE: Pipeline Matching Variable in TN Document

    Posted 05/13/11 04:43 PM

    Refer to the TN documentation. It describes how to do this.


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


  • 7.  RE: Pipeline Matching Variable in TN Document

    Posted 05/13/11 10:04 PM

    TN_parms → Document (optional) An IS document (IData object) that holds ʺhintsʺ that Trading Networks uses when performing document recognition for a flat file document. See information about document gateway services in the webMethods Trading Networks Administrator’s Guide for details on providing recognition hints.


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


  • 8.  RE: Pipeline Matching Variable in TN Document

    Posted 05/25/11 10:35 AM

    sender id and receiver id should match in the TN while tranfering the document.


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


  • 9.  RE: Pipeline Matching Variable in TN Document

    Posted 05/26/11 10:27 AM

    Hi Shweta,

    Please refer TN Documentation …
    It has been desribed there with ease … just follow the documentation …

    Cheers !!!


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


  • 10.  RE: Pipeline Matching Variable in TN Document

    Posted 07/14/11 04:11 PM

    In your TN doctype you set a pipeline matching variable, you can use whatever you want say the name is ‘Transaction Type’. Then you set a variable under the TN_parms to match eg. Transaction Type and set the value to match what you put in TN doctype. Then you route it to TN (such as via recognize and routeBizdoc)


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