webMethods

webMethods

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
Expand all | Collapse all

diff. between resubmit and reprocess

webMethods Community Member

webMethods Community MemberThu November 03, 2011 05:25 AM

  • 1.  diff. between resubmit and reprocess

    Posted Wed November 02, 2011 10:26 AM

    in wM trading networks console, in transaction analysis, if we right click on any failed transaction there r two options resubmit and reprocess…plz any one explain the difference between resubmit and reprocess…

    Advanced Thanks…:slight_smile:


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


  • 2.  RE: diff. between resubmit and reprocess

    Posted Wed November 02, 2011 04:25 PM

    From TN User Guide 8.0 SP1

    When you reprocess a document, Trading Networks performs the following:

    • Performs a processing rule lookup to determine the processing rule to use
    • Performs the processing actions identified in the matching processing rule

    Note: When reprocessing a saved document, Trading Networks does not perform pre-processing actions—verify, validate, check uniqueness, or save the document.

    When you resubmit a document, Trading Networks adds a new instance of the document. The original document remains unchanged. Trading Networks performs the following for the new instance of the document

    When you resubmit a document, Trading Networks performs the following processing:

    • Relates the resubmitted document to the original document
    • Uses the TN document type definitions to recognize the document
    • Performs a processing rule lookup to determine the processing rule to use
    • Performs the pre-processing and processing actions identified in the matching processing rule

    Hope this helps…

    S.


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


  • 3.  RE: diff. between resubmit and reprocess

    Posted Wed November 02, 2011 04:26 PM

    From TN User Guide 8.0 SP1

    When you reprocess a document, Trading Networks performs the following:

    • Performs a processing rule lookup to determine the processing rule to use
    • Performs the processing actions identified in the matching processing rule

    Note: When reprocessing a saved document, Trading Networks does not perform pre-processing actions—verify, validate, check uniqueness, or save the document.

    When you resubmit a document, Trading Networks adds a new instance of the document. The original document remains unchanged. Trading Networks performs the following for the new instance of the document

    When you resubmit a document, Trading Networks performs the following processing:

    • Relates the resubmitted document to the original document
    • Uses the TN document type definitions to recognize the document
    • Performs a processing rule lookup to determine the processing rule to use
    • Performs the pre-processing and processing actions identified in the matching processing rule

    Hope this helps…

    S.


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


  • 4.  RE: diff. between resubmit and reprocess

    Posted Thu November 03, 2011 05:25 AM


  • 5.  RE: diff. between resubmit and reprocess

    Posted Sat November 05, 2011 06:18 PM

    One more point to be noted

    From TN Admin Guide:

    You might get different or unexpected results when you reprocess a document. Because the attributes are not saved when you reprocess the document, Trading Networks will not match processing rules that use extended criteria. Instead, Trading Networks will match to another processing rule, for example the default processing rule, and perform the process actions identified in that matching rule. Trading Networks does not perform document recognition again and therefore does not re-extract the attributes

    For example, if you use extended criteria to select a processing rule when the value of the custom attribute Total Amount is greater than 10000, Trading Networks would not select that processing rule when reprocessing a document because the value of the Total Amount attribute would not be available and therefore would not match the extended criteria.

    HTH
    Senthil


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


  • 6.  RE: diff. between resubmit and reprocess

    Posted Wed December 07, 2011 07:28 AM

    My 2 cents here

    1. As reprocessing uses the same bizdoc created, the processing logic may fail in case content parts are used with static/fixed names
    2. When you resubmit, it copies only the primary content part (xmldata/EDIdata/ffdata) to the new bizdoc and whatever was done in the gateway service (setting values to extended fields, adding extra content parts etc) will not be done again.

    So choose the action carefully.

    Cheers
    Guna


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


  • 7.  RE: diff. between resubmit and reprocess

    Posted Mon August 10, 2015 11:17 AM

    @Gunsekhar, @Senthil : Good point :slight_smile: Was unable to re-submit flat files. Re-processing was working fine. Your inputs helped to understand the same :slight_smile: I couldn’t find this info on 9x guides though :roll:


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


  • 8.  RE: diff. between resubmit and reprocess

    Posted Mon August 10, 2015 02:10 PM

    Vimal,

    What is the error when trying to resubmit for flat files via MWS B2B–>Transactions view?

    I believe you can only reprocess FF’s not resubmit as it works differrently then standard XML or EDI submit wise.

    HTH,
    RMG


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


  • 9.  RE: diff. between resubmit and reprocess

    Posted Mon August 10, 2015 08:54 PM

    There is no error. Just that Doctype, Sender and Receiver comes down as unknown and its gets processed via defaulr processing rule. And Gunasekhar’s explaination makes sense here. All the extended which i was using to mark the same are lost while re-submitting. Reprocessing works though as it uses the same BizDoc :slight_smile:


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


  • 10.  RE: diff. between resubmit and reprocess

    Posted Tue August 11, 2015 05:25 PM

    Yes that is how it works for flat file routing!

    HTH,
    RMG


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


  • 11.  RE: diff. between resubmit and reprocess

    Posted Mon September 28, 2015 06:05 PM

    Resubmission of flat files also works as long as you code your gateway service correctly. By that I mean that when calling wm.tn.doc.ff:routeFlatFile, you need to pass the name of your gateway service inside a variable named TN_parms/$receiveSvc. This will cause TN to call that service when resubmitting the document.

    Percio


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