Eksporter (0) Skriv ut
Vis alt
EN
Dette innholdet er ikke tilgjengelig på ditt språk, men her er den engelske versjonen.

Step 5: Create and Deploy the EDI Receive Pipeline

Updated: November 21, 2013

In this topic, you configure the EDI Receive bridge that receives an X12 850 PO message from an FTP server, processes it, transforms it to an ORDERS05 IDOC, and then routes it to the XML One-Way Bridge that you deployed in the last step.

To configure an EDI Receive pipeline

  1. Log into the BizTalk Services Portal. You can get the URL for the BizTalk Services Portal from your BizTalk Services subscription. For more information about logging into the portal, see http://go.microsoft.com/fwlink/?LinkId=317714.

  2. Create a partner for Fabrikam and Contoso. On the left pane, click Partners, and then from the Partners page, click Add Partner.

  3. Create an agreement between the two partners. On the Agreements page, click the X12 tab if you are not already on that tab. Then click Add.

  4. Set the following values for the General Settings tab.

     

    Field

    Description

    Name

    Enter a name for the agreement. For this tutorial, specify the name as SAPIntegration.

    noteNote
    This is a mandatory field. The name for the agreement must be unique.

    Description

    Enter notes or a description for the agreement.

    Hosted Partner

    Select the hosted partner for the agreement. A hosted partner is a partner managed by the service provider and the pipelines are deployed for that partner during agreement deployment. Typically partners managed by service provider are configured as a hosted partner while the enterprise partners are guest partners.

    For this tutorial, the hosted partner is Fabrikam. The default profile for Fabrikam is displayed in the Profile field.

    Guest Partner

    Select the partner for the agreement (who is not a hosted partner). For this tutorial, select Contoso. The default profile for Contoso is displayed in the Profile field.

    Identities

    Hosted Partner ID Qualifier

    Select an authenticating qualifier that provides unique business identities to the trading partners. For this tutorial, select ZZ-Mutually Defined.

    Value

    Enter FABRIKAM.

    Guest Partner ID Qualifier

    Select an authenticating qualifier that provides unique business identities to the trading partners. For this tutorial, select ZZ-Mutually Defined.

    Value

    Enter CONTOSO.

    Tracking

    Track Send side message properties

    Check this to store the message properties when the EDI message is sent to the partner. Once stored, you can query this data by clicking Tracking on the BizTalk Services Portal home page.

    When enabled, you can also store the message body by checking Archive Send side message.

    Track Receive side message properties

    Check this to store the message properties when the EDI message is received from a partner. Once stored, you can query this data by clicking Tracking on the BizTalk Services Portal home page.

    When enabled, you can also store the message body by checking Archive Receive side message.

  5. Click Continue.

    Clicking Continue adds two new tabs, one for receive settings and the other for send settings. Each tab is for a one-way agreement between the two partners, one for receiving messages and the other for sending messages. The properties in the Receive Settings tab define how the EDI receive bridge is configured. This bridge receives incoming EDI messages that are sent to Fabrikam. Similarly, the properties in the Send Settings tab define how the EDI send bridge is configured. This bridge sends EDI messages from Fabrikam to its trading partners like Contoso.

To specify the receive settings

  1. From the agreements page, click the Receive Settings tab.

  2. Specify the following values for the Transport section.

    • For Transport Type, select FTP. In the scenario used in this tutorial, Contoso sends the X12 850 message using an FTP location.

    • Provide the name of the FTP Server from where the messages are picked.

    • Specify the username and password to connect to the FTP Server.

    • Specify the relative path on the server from where to pick the X12 850 message.

    Specify the FTP Server details
  3. Specify the following values for the Protocol section.

    • Specify whether you want to receive technical (TA1) and functional acknowledgements (997).

    • Under Schemas, click the plus sign and specify the following values.

       

      For this Specify this

      For Version

      Specify 00401.

      For Transaction Type (ST1)

      Specify 850 – Purchase Order.

      For Sender Application (GS02)

      Specify CONTOSO.

      For Schema

      From the drop-down list, select the schema (X12_00401_850.xsd). This schema was uploaded to your BizTalk Services when you deployed the BizTalk Service project in the last step.

      Specify the Receive-side Protocol settings
  4. In the Transform section, click the plus sign to add a transform to the agreement. From the drop-down list, select the X12_00401_850.xsd schema and the transform you created earlier (AzureTransformations.trfm). The schema as well as the transform is deployed to the BizTalk Services subscription when you deployed the BizTalk Service project in the last step.

    Specify the Receive-side Transform
  5. On the Route page, under Route Settings, click Add to add a route destination.

    1. Set the Rule Name to SendToBridge.

    2. Under Route rule, select the Use advanced definitions option and specify the following expression in the text box:

      1=1
      

      This expression always resolves to true, which means that all the messages are routed to the bridge.

      noteNote
      Even if you do not select the Use advanced definitions option and do not provide any route rule, by default this option is selected and its value is set to 1=1. This means that the default behavior is to route all the messages to the route destination.

    3. Under Route action, click the plus sign to add a new row and set the following values:

      • Set Target Type to Http Header

      • Set Header Name to Content-Type

      • Set Value Type to Constant

      • Set Constant Value to application/xml

      noteNote
      This ensures that all the messages that are routed to the bridge include a content-type header with its value set to application/xml. Without this header, the bridge receiving the message treats it as a flat-file message and might result in validation errors.

    4. Under Route destination, set Transport type to Azure BizTalk Bridge and in the text box enter the entity name of the bridge on the message flow surface. For this tutorial, you specified the bridge name as B2BConnector. Using this name the bridge deployment endpoint is built, which is http://<mybiztalkservicename>.biztalk.windows.net/default/B2BConnector. With this configuration, all the messages processed by the agreement are routed to the XML One-Way Bridge bridge you deployed earlier.

      Specify route action in EDI agreement

      Click Save.

    5. On the Route page, under Message Suspension Settings, specify the Transport Type as Azure Service Bus, and then specify the following values:

      • Set the route destination type to BasicHttpRelay.

      • Specify the Service Bus namespace, issuer name, and issuer key.

      • Specify the endpoint URL where a relay receiver service is already running. For this tutorial, specify this as Suspend. So, the complete URL where a failed message is sent is http://<servicebus_namespace>.servicebus.windows.net/Suspend.

To specify the send settings

  1. From the agreements page, click the Send Settings tab.

    noteNote
    Even though this tutorial does not cover the send side of the agreement, you must specify the minimum default values to successfully deploy the agreement.

  2. Retain the default values Inbound URL, Transform, and Batching tabs.

  3. In the Protocol tab, under Schemas, specify the following values:

     

    Property Description

    For Version

    Set this to 00401

    For Transaction Type (ST01)

    Set this to 850 – Purchase Order

    For Schema

    Set this to X12_00401_850.

  4. In the Transport section, under Transport Settings, specify the following values.

    • Set the Transport Type to FTP/S.

    • Specify the required values for the FTP transport.

  5. In the Transport section, under Message Suspension Settings, specify the following values.

    • Set the Transport Type to Azure Service Bus.

    • Set the route destination type to BasicHttpRelay.

    • Specify the Service Bus namespace, issuer name, and issuer key.

    • Specify the endpoint URL where a relay receiver service is already running. For this tutorial, specify this as Suspend. So, the complete URL where a failed message is sent is http://<servicebus_namespace>.servicebus.windows.net/Send_Failure.

  6. Click Deploy Agreement to deploy the agreement.

    Once the agreement is deployed, to test the solution, you can go ahead and drop a test PO 850 message in the folder on the FTP server that you specified as part of the agreement. More details on how to test the solution are provided in the next topic, Step 6: Test the Solution.

See Also

Fellesskapsinnhold

Vis:
© 2014 Microsoft