Receiving Inbound Messages

The Adapter for X.400 provides a set of services for receiving inbound IP messages (messages with the Trading Networks document type of ipMessageln) and EDI messages (messages with the Trading Networks document type of ediMessageln).

Before you can receive X.400 IP or X.400 EDI messages, fulfill the following prerequisites:

• Create a scheduled task that runs the sendAndFetch or fetch service. For more information, see Sending to and Fetching Messages from X.400 Server.
• Configure the profiles for the sender and receiver of the message. For more information, see Manage Partner Profiles for the Adapter.

The following list illustrates how Adapter for X.400 processes both IP and EDI inbound messages:

1. The scheduled wm.x400gateway.Gw:sendAndFetch or wm.x400gateway.Gw:fetch services invoke the ADDONMAIL-UAFI (third party product),which fetches the messages and notifications out of your X.400 mailbox. The sendAndFetch and fetch services convert the messages and notifications into XML and store them in the Inbound folder for further processing.
2. You should create a client that invokes the wm.X400forTN.wm.x400.tn.rec:receiveX400 service to retrieve the messages from the Inbound folder.
   Note: You can also create a scheduled task to periodically invoke the receiveX400 service.

   The receiveX400 service stores the mail message in the Trading Networks database. The receiveX400 service automatically pulls the sender/receiver information for Trading Networks out of the message header.

   Next, the receiveX400 service parses the message for the content. Each content part (X.400 bodypart) is checked for its format.

   • Known format. Adapter for X.400 routes content parts of a known format (e.g.,ANSI X.12, EDIFACT, EANCOM, IDOC, XML, HTML) to the wm.tn:receive service.
   • Unknown format. Adapter for X.400 stores content parts of an unknown format as the Trading Networks document type of X400payload. The X400payload document contains the Sender/Receiver X.400 address, a format description (e.g.,UNKNOWN, ODETTE,VOA), and the content (Base64 encoded).
3. Adapter for X.400 creates a Transactions relationship between the original message retrieved from the Inbound folder and each extracted content part(s), whether the content part is of known or unknown format.

   To see relationships go to IBM My webMethods Server > Monitoring> Integration > B2B > Transactions, search for a transaction and click on the icon in the column Related Documents.

4. Adapter for X.400 sets the Transactions user status of the original message retrieved from the Inbound folder and each extracted content part(s) to X.400 received.