none
Receive EDI via WCF (WCF Services Publishing Wizard) Question RRS feed

  • Question

  • I'm trying to create a WCF service to process an EDI message via a WcfHttp receive location. Being new to WCF Services in BizTalk Server, I'm wondering if the only way I can retrieve an EDI message is through elements.
    Pardon my naivete, but isn't there a way to create a service that takes the entire document and gives it to BizTalk Server to process...using something like:


    wcfServiceClient.ReceiveMessage(EDIDocument ediMessage);--EDI Document is a parameter

    Saturday, August 20, 2011 5:46 AM

Answers

All replies

  • Hi,

    Take a look at this blog post/video and you will get a better picture of processing a EDI Message via WCF.

    Cheers,

    Bali


    --------------------------------------
    Mark As Answer or Vote As Helpful if this helps.
    Saturday, August 20, 2011 5:52 AM
  • The problem I'm having is that the video shows a service reference that has a Request class with a Value property (as a string). This property allows you to send the entire EDI message. When I created my WCF Service, the Request Class splits the EDI Message into the different loops etc.

     

    Is there no easy way to take the entire x12_873 EDI message as a string and send it to BizTalk to process rather than creating each individual segment of the message first?

    Sunday, August 21, 2011 5:09 AM
  • Hi,

    Didnt get exactly what you need, but will still try to answer this. The video is what your requirement is, I would say construct your WCF Service as per the video and that will be it. 

    Timothy : When I created my WCF Service, the Request Class splits the EDI Message into the different loops etc.

    You will have to recreate your service class as per the video.

    Is there no easy way to take the entire x12_873 EDI message as a string and send it to BizTalk to process rather than creating each individual segment of the message first?

    I think the video shows you the way of taking the entire EDI message. 

     

    Cheers,

    Bali


    --------------------------------------
    Mark As Answer or Vote As Helpful if this helps.
    Sunday, August 21, 2011 6:19 AM
  • Yes, the video does. Here is the problem:

     

    On the WCF Client form, the author sends the EDI message as a string. When I try to create the same WCF client, I do not have the same Request.Value that takes the EDI message as a string, I have a Request.X12_5020_873 which requires me to specify what the segments of the EDI message are.

    Sunday, August 21, 2011 6:29 AM
  • Can you share the request message that you are getting when you are creating the proxy?


    --------------------------------------
    Mark As Answer or Vote As Helpful if this helps.
    Sunday, August 21, 2011 6:41 AM
  • Here is the message...I can also send the solution as well if you have an email address to send to:

     

    ISA*00*          *00*          *ZZ*VWX            *ZZ*AX2009         *991221*1226*U*00502*000000025*0*T*>
    GS*NMQR*VWX*AX2009*19991221*1226*1*X*00502
    ST*873*123456789
    BGN*00*1*19960123****G1
    DTM*102****DT*199601230945
    N1*SJ**1*357961038
    N1*78**1*478935021
    DTM*007****RDT*199602010900-199602020900
    CS*K1234***NMT*P
    SLN*N001**I
    LQ*QT*R
    LQ*TT*01
    N1*US**1*123456789
    LCD*1*M2***DR*R11111111
    QTY*38*100*BZ
    N1*DW**1*987654321
    LCD*1*MQ***DR*D11111111
    SLN*N002**I
    LQ*QT*R
    LQ*TT*01
    N1*US**1*123456780
    LCD*1*M2***DR*R11111111
    QTY*38*25*BZ
    N1*DW**1*987654320
    LCD*1*MQ***DR*D22222222
    SLN*N003**I
    LQ*QT*R
    LQ*TT*01
    N1*US**1*123456780
    LCD*1*M2***DR*R11111111
    QTY*38*25*BZ
    N1*DW**1*987654321
    LCD*1*MQ***DR*D11111111
    SE*32*123456789
    GE*1*1
    IEA*1*000000025

    Sunday, August 21, 2011 6:46 AM
  • You can send it to <<removed email>> if you want to. 

     


    --------------------------------------
    Mark As Answer or Vote As Helpful if this helps.
    • Edited by DPS Bali Monday, September 12, 2011 10:32 AM removed email
    Sunday, August 21, 2011 6:49 AM
  • Thanks for the help with this. I finally got it running and it looks thlike the problem was with the EDI receive pipeline.
    Tuesday, August 23, 2011 5:57 PM