Use Cases: Exchanging EDI documents with an AS2 Channel

The following use cases address the runtime aspects of using various combinations of AS2 channel configurations for partners to exchange documents with each other.

These use cases assume that webMethods.io B2B sends a functional acknowledgment when one partner receives a document from another.

webMethods.io B2B automatically detects the exchange documents between partners and generates the functional acknowledgment for each of the inbound documents of partners while processing them. After the functional acknowledgment is generated, webMethods.io B2B sends it to the intended partner using the AS2 out the channel. The use cases utilize plain content. Plain EDI content means document content that is not signed, encrypted, or verified.

Ensure to complete the prerequisites mentioned below before you allow partners to exchange EDI documents.

Pre-requisites:

Ensure to set the AS2 out the channel as the preferred outbound channel of each of the transacting partners.

To start exchanging EDI documents with an AS2 inbound channel

  1. Create the AS2 inbound and AS2 outbound channels for each of the partners.
  2. Create profiles for partners for whom you want to facilitate document exchange.
  3. Ensure that you have created an EDIINT AS2 identity type and set the identity value in the partner profile of business partners for whom you want to facilitate the document exchange over an AS2 channel. The EDIINT AS2 identity type is required in addition to the existing identity type to facilitate the recognition of business partners.
  4. Associate the AS2 inbound and AS2 outbound channels with the newly created partners.
  5. Create a partner user each and associate the partner users with the newly created partner profiles.
  6. Inform the partners to share their AS2 inbound channel endpoint URLs along with partner user credentials with the business partners with whom they want to exchange business documents.

A Business Partner Sends Plain EDI content to Another Partner Through webMethods.io B2B

Use case 1: When a partner (For example, TrinityMetalCorp) sends plain EDI content by using an AS2 inbound channel to another partner (Bridgestone), webMethods.io B2B recognizes the document, identifies, and splits the EDI document into Envelope, Group, and Transaction.

webMethods.io B2B also ensures that it sends the corresponding Functional Acknowledgment to the partner(TrinityMetalCorp) using the partner's preferred outbound channel.

If you have configured a specific processing rule to process specific types of EDI content, webMethods.io B2B applies that processing rule and completes the processing of the document.

A Business Partner Sends EDI Content and Requests a SYNC MDN from Another Partner Through webMethods.io B2B.

Use case 2: When a partner (For example, TrinityMetalCorp) sends EDI content by using an AS2 inbound channel requesting for a SYNC MDN from another partner (Bridgestone), the document passes through webMethods.io B2B. webMethods.io B2B recognizes the document, identifies, and splits the EDI document into Envelope, Group, and Transaction.

webMethods.io B2B also ensures that it sends the corresponding EDIINT SYNC MDN and Functional Acknowledgment to the partner using the partner's preferred outbound channel.

If you have configured a specific processing rule to process specific types of EDI content, webMethods.io B2B applies that processing rule. It routes the document from the sender to the receiver and during this process, webMethods.io B2B creates an SYNC MDN and sends it to the receiver.

A Business Partner Sends EDI Content and Requests an Asynchronous MDN from Another Partner Through webMethods.io B2B

Use case 3: When a partner (for example, TrinityMetalCorp) sends EDI content by using an AS2 inbound channel requesting for a SYNC MDN from another partner (Bridgestone), the document passes through webMethods.io B2B. webMethods.io B2B recognizes the document, identifies, and splits the EDI document into Envelope, Group, and Transaction.

webMethods.io B2B also ensures that it sends the corresponding EDIINT ASYNC MDN by using the Asynchronous MDN URL that is set in AS2 outbound channel of the partner. Functional Acknowledgment is also sent to the partner using the partner's preferred outbound channel.

If you have configured a specific processing rule to process specific types of EDI content, webMethods.io B2B applies that processing rule. It routes the document from the sender to the receiver and during this process, webMethods.io B2B creates an ASYNC MDN and sends it to the receiver.