none
Can the processed EDI file to be saved to a specify folder? RRS feed

  • Question

  • Hi guys,

    As we know, when the edi file be send to the reccive location then it will be processed by Biztalk mapping application or else, after processing, the file will be removed or deleted from the folder.

    My question is, can we configure the Biztalk server to save the processed file, for example, save the processed file to a achieve folder?

    If it can be configured, please advice how to configure, Thanks.
    Tuesday, April 28, 2009 10:28 AM

Answers

  • Hi,

    Sometimes you have a client who does not want the transactions stored in the database but wants them stored in archive folders.

    You can do this by adding a pipeline component that saves a copy of the transaction to a folder to a custom pipeline that includes the EDIReceive component.  You can do the same thing for outbound files by adding a similar component to a custom pipeline that includes the EDISend component.

    A simple, effective method is to use an extra receive/send port step in the processing flow.  Using AS2 for example, you would receive the EDI file using the AS2Receive pipeline.  A group send port would take the received EDI file from that receive port and store it into two folders:  an archive folder and a processing folder.  A second receive port, using the EDIReceive pipeline, would pick up the saved file from the processing folder and process it.  This would leave a copy of the original X12 interchange in the archive folder.

    You can use the same method for outbound files, using a group send port to route one copy of an EDI transaction to an archive folder and another copy to the actual send port that communicates with the trading partner.

    The question with BizTalk is often whether or not to use the assets available such as orchestrations, custom pipelines, and so forth, or to elect to implement a simple method that avoids these more complex assets.  This choice not only depends on your skill set but also on the capability of the client to maintain the system once you are gone.

    Hope this helps,

    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by Sinosky_Lin Thursday, April 30, 2009 3:10 AM
    Tuesday, April 28, 2009 2:50 PM

All replies

  • Hi,
        There is a setting in the EDI party properties in general tab there is a option "Activate EDI reporting " and "store transaction set payload for reporting". If you will select these option then Biztalk will store all messages in Biztalkdatabase(BizTalkDTADb ) in table "EdiMessageContent" . You can also see it from Biztalk console. After activating this option send a message and go to group hub page and click the option "Edi interchange and correlated ACK status" . Then right click on one query and choose "Transaction set details" then choose one query at new page and select "transaction set content". Then it will show the content of the message you sent.


    Thanks
    Gyan
    Tuesday, April 28, 2009 11:04 AM
  • Hi,

    Sometimes you have a client who does not want the transactions stored in the database but wants them stored in archive folders.

    You can do this by adding a pipeline component that saves a copy of the transaction to a folder to a custom pipeline that includes the EDIReceive component.  You can do the same thing for outbound files by adding a similar component to a custom pipeline that includes the EDISend component.

    A simple, effective method is to use an extra receive/send port step in the processing flow.  Using AS2 for example, you would receive the EDI file using the AS2Receive pipeline.  A group send port would take the received EDI file from that receive port and store it into two folders:  an archive folder and a processing folder.  A second receive port, using the EDIReceive pipeline, would pick up the saved file from the processing folder and process it.  This would leave a copy of the original X12 interchange in the archive folder.

    You can use the same method for outbound files, using a group send port to route one copy of an EDI transaction to an archive folder and another copy to the actual send port that communicates with the trading partner.

    The question with BizTalk is often whether or not to use the assets available such as orchestrations, custom pipelines, and so forth, or to elect to implement a simple method that avoids these more complex assets.  This choice not only depends on your skill set but also on the capability of the client to maintain the system once you are gone.

    Hope this helps,

    Jim -- Pro Mapping in BizTalk 2009, Apress Books, March 23, 2009
    • Marked as answer by Sinosky_Lin Thursday, April 30, 2009 3:10 AM
    Tuesday, April 28, 2009 2:50 PM
  • Thanks Gyan & Jim
    Thursday, April 30, 2009 3:10 AM