Configuring an AS2 inbound exchange profile

An exchange profile defines the configuration that is required to exchange documents with a trading partner. It also defines how the message or document that is sent or received must be processed in B2B Advanced Communications.

1. Click Exchanges > Exchange Profiles.
2. On the Exchange Profiles page, click New > AS2 Inbound.
3. In the New Exchange Profile dialog box, specify values for the following fields and click Save.

   Field	Description
   Profile name	Required. Specify a unique name for the exchange profile.
   Exchange pattern	Required. Select AS2 Inbound.

   The Exchange Identification page is displayed.
4. In the Basic Properties section, click Edit to update or specify the values for the following fields, and then click Save.

   Field	Description
   Name	Name of the exchange profile. The name entered in the Profile name field is populated here.
   Description	Optional. Provide a description for the exchange profile.

5. In the Participating Organizations section, specify values for the following fields.
   Note: When configuring the exchange profile, do not assign the value Any to the following fields:

   • Receiver ID
   • Sender ID

   Any is a reserved value. It is used for exchange profile look up when the any of the preceding fields do not have a user assigned value.

   Field	Description
   Owner Organization	Click Select and select the owner organization. In an inbound exchange profile, the owner organization is the receiver.
   Receiver ID	Optional: Click New and type a receiver ID. The receiver ID is the unique business identifier that is used to identify your organization. The ID can be mutually agreed on or assigned by an international code designator. For example, a DUNS ID.
   Trading Partner Organization	Click Select and select the trading partner organization. In an inbound exchange profile, the trading partner is the sender. Alternatively, you can select Use Anonymous Partner for authentication and authorization, instead of configuring a partner organization in the system. The anonymous partner allows you to represent more than one partner through the Anonymous Partner mechanism. This mechanism supports many trading partners (or individual users) without needing to configure an organization (identity representation in the system), specific certificates, and exchange details for each one.
   Sender ID	Optional: Click New and type a sender ID. The sender ID is the unique business identifier that is used to identify the trading partner. The ID can be mutually agreed on or assigned by an international code designator. For example, a DUNS ID.

6. In the Trigger: Receive AS2 Messages from Trading Partners section, specify the AS2 receiver, connection settings, security policy, and security settings for the message exchange.

   Field	Description
   Select Receiver	Click Select and select the required AS2 receiver. After receiving the message, the AS2 receiver sends the message to the messaging destination that is specified in the AS2 receiver configuration. A messaging receiver (associated with the same message queue definition as the messaging destination) picks the message and sends it to the AS2 engine.
   Configure connection	Click Configure and specify values for the following fields: Duplicate messages - To allow duplicate messages, select the Allow duplicate messages check box. In B2B Advanced Communications, duplicate messages are detected and eliminated by default. Select the check box to allow duplicate messages. Asynchronous MDN destination - Select an asynchronous message disposition notification (MDN) destination. An asynchronous MDN destination is mandatory for the following reasons: Currently, in B2B Advanced Communications, it cannot be determined whether synchronous or asynchronous MDN is specified in the incoming message until the message reaches the AS2 runtime. To process the MDN requirements of the incoming request, SSL connection options, connection timeout, thread pool, and retry policy settings are required. If Override the receipt URL from the incoming messages is selected in the MDN configuration, the URL specified in the MDN destination configuration overrides the URL in the header of the incoming request. However, to process the MDN, other destination settings (SSL connection options, connection timeout, thread pool, and retry policy) are used from the MDN destination that is configured for the inbound exchange profile. If the configuration of the MDN destination is to Use the receipt URL from the incoming message, the MDN is sent to the destination (URL) specified in the incoming message. If the configuration of the MDN destination is to Override the receipt URL from the incoming message, the MDN is sent to the destination (URL) specified for the MDN destination that you have selected.
   Select Security Policy	Click Select to select a security policy that can be used for the exchange. To create a new security policy, click New Security Policy.
   Configure security	For information about configuring security settings for an AS2 inbound exchange profile, see Configuring security settings for AS2 inbound exchange profile.

7. In the Action: Deliver Message Data section, define the action after the inbound flow is triggered.

   Field	Description
   Message Destination	To select an existing destination, click Select and select the required destination. To create a new destination, click New Destination. B2B Advanced Communications sends the inbound message that is processed (BDO, payload and attachments) to the messaging destination.

8. In the Deploy Exchange Profile section, click Deploy to deploy the exchange profile.
   Note: The Deploy button is enabled only when all the sections of the exchange profile are in Complete status.
9. Optional: Click Information to exchange with the trading partner to view authentication and certificate-related information specific to the owner organization and the trading partner.