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.  Problem in Pipeline Variables

    Posted Sat December 21, 2002 01:38 AM

    Hi Experts,

    I’m Using Webmethod 4.6, Developer 4.6, Trading Network 4.6, TN Console 4.5.1, EDI 4.6 and EDIforTN 4.6 in my system

    When I’m sending a EDI document using EDIforTN i’m not getting the following pipeline variables
    Values, editn_grp, editn_xtn. I’m getting the rest of the information.

    I had followed the Steps as specified in EDIforTN User guide chapert 4.

    Any help on this will be highly appriciated.

    Thanks in Advance


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 2.  RE: Problem in Pipeline Variables

    Posted Mon December 23, 2002 04:13 PM

    I believe you are using builtin services to post the edi document to TN with passing $edidata variable.

    wm.tn.doc.xml:routeXML
    wm.tn:receive.

    IF you have used any of the above servicesthat post edi document(edidata) to TN, you will be definetely see all variables in Pipeline including Envelope,group,transaction set (edi_xtn).

    Just make sure again that you are sending $edidata to TN.


    #Adapters-and-E-Standards
    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: Problem in Pipeline Variables

    Posted Tue December 24, 2002 12:22 AM

    Hi Rama,

    I’m using wm.tn.receive service to send the EDI data. I had tried from Developer and aslo from WmEDIforTN homepage(selecting Submit a Sample). But still i’m not getting the Values, Group and Transaction set output variables in pipeline.

    Uday


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 4.  RE: Problem in Pipeline Variables

    Posted Tue December 24, 2002 11:04 AM

    That means i believe your Group Envelope section(GCEnvelope) and Transaction set might be having some compliance errors(means not in the format according to the used edi template).

    So my suggesion is pls make a compliance check using built in service (processEnvelope)in edi package, before you sending the edi document to TN (wm.tn:receive or wm.tn.doc.xml:routeXML).

    With this builtin service you can validate the final edi document with Error True or False.

    If Errors is false then your edi document is formatted well according to delimiters and segments.

    After you tested the edi document you disable the service processEnvelope.

    Thanks.


    #webMethods
    #Adapters-and-E-Standards
    #Integration-Server-and-ESB