Export (0) Print
Expand All

Configuring a Dynamic Send Port for Messages over AS2

This topic describes how to configure BizTalk Server to send AS2 messages over a dynamic send port. This configuration includes creating the dynamic send port and configuring a backend application to set the appropriate context properties. When you create a dynamic send port to send an AS2 message, you must promote certain properties for the send port to work. For more information, see To configure BizTalk Server to send AS2 messages over a dynamic send port below.

A dynamic send port enables you to send messages to multiple parties without hard-coding the party configuration. The agreement and destination to be used in sending the message are determined dynamically through context properties. You do not have to create a static send port for each individual customer.

To send an AS2 message with an EDI or non-EDI message or an EDI acknowledgment, create a dynamic response HTTP send port with the following configuration:

 

Location Property Setting

Send Port Properties: General

Port Type

  • Dynamic Solicit Response (if Request MDN in Acknowledgements (MDNs) page in the one-way agreement tab is selected)

  • Dynamic One-way Send Port (if Request MDN in Acknowledgements (MDNs) page in the one-way agreement tab is cleared)

Send pipeline

  • AS2EdiSend (for EDI-encoded messages)

  • AS2Send (for non-EDI messages)

Receive pipeline

(if Request MDN in Acknowledgements (MDNs) page in the one-way agreement tab is selected)

AS2Receive (for dynamic solicit response send port)

Send Port Properties: Filters

Property

BTS.MessageType

Operator

==

Value

  • http://schemas.microsoft.com/BizTalk/EDI/X12/2006#<schema name> (for an EDI message)

  • http://schemas.microsoft.com/Edi/X12#X12_<997 or TA1>_Root (for an X12 acknowledgment)

  • http://schemas.microsoft.com/Edi/Efact#Efact_Contrl_Root (for an EDIFACT acknowledgment)

You must be logged on as a member of the BizTalk Server Administrators group.

  1. In the BizTalk Server Administration console, create a dynamic one-way send port (if an MDN is not requested) or a dynamic solicit response send port (if an MDN is requested) with the above configuration.

  2. For the agreement that applies to this message, set the AS2 and EDI properties required.

  3. Promote the following properties to the message context:

    • BTS.MessageType

    • EdiIntAS.MessageID

  4. Add functionality to a backend application to write the following properties to the message context, setting them to the appropriate values:

    • EdiIntAS.AS2To

    • BTS.OutboundTransportLocation

    • HTTP.EnableChunkedEncoding

    • BTS.EncryptionCert

    noteNote
    The AS2To context property and the OutboundTransportLocation context property must be written to the message context for the dynamic send port to function properly. The AS2To property is required for the port to determine the agreement to use in processing the outgoing message and the OutboundTransportLocation property is required for the send port to determine the destination of the message. For more information, see Generating an Outgoing AS2 Message.

The dynamic send port and pipeline does the following to send a synchronous EDI or non-EDI message or acknowledgment over AS2 and process the returned MDN:

  • If sending an EDI message, picks up the EDI message by filtering on the property BTS.MessageType set to the message schema in the http://schemas.microsoft.com/BizTalk/EDI/X12/2006 namespace (for example, X12_00401_864 for an 864 message).

  • If sending an EDI acknowledgment, picks up the acknowledgment by filtering on the property BTS.MessageType set to one of the following control schema:

    • http://schemas.microsoft.com/BizTalk/EDI/X12#X12_997_Root for a 997 acknowledgment

    • http://schemas.microsoft.com/BizTalk/EDI/X12#X12_TA1_Root for a TA1 acknowledgment

    • http://schemas.microsoft.com/BizTalk/EDI/Efact#Efact_Contrl_Root for a CONTRL acknowledgment

  • If sending a non-EDI message, picks up the message using an appropriate filter.

  • Builds an AS2 message. For more information about this process, see Generating an Outgoing AS2 Message.

    noteNote
    BizTalk Server determines the transport type to be used by the dynamic send port from the format of the URL, i.e., http, smtp, ftp, etc.

  • Routes the message or acknowledgment to the destination URL for the send port.

  • Receives the MDN response to the message or acknowledgment, if enabled and if a solicit-response send port. For more information about this process, see Processing an Incoming MDN.

© 2010 Microsoft Corporation. All rights reserved.

Community Additions

ADD
Show:
© 2014 Microsoft