Sending Outbound Messages

Adapter for X.400 provides a set of services to send IP messages (messages with the Trading Networks document type of ipMessageOut) and X.400 EDI messages (messages with the Trading Networks document type of ediMessageOut). Before you can send X.400 IP or X.400 EDI messages, fulfill the following prerequisites:

• Create a scheduled task that runs the sendAndFetch or send 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 outbound messages:

1. To send IP/EDI messages, you have to invoke the delivery service wm.X400for1N.wm.x400.tn.rec:deliverX.400. The deliverX400 service:
   • Converts the bizdoc/ContentParts into X.400 bodyparts
   • Determines the receiver by matching X.400 address information from the document to the corresponding Trading Networks partner profile
   • Creates an IP/EDI message by mapping the X.400 bodyparts into an X.400 IP/EDI message (depending on the X.400 extended field, contentType, of the Trading Networks partner profile)
   • Invokes the X400for1N.wm.x400.tn.rec:putToQueue service to send the message to your X.400 partner via the webMethods X.400 Gateway
2. The putToQueue service stores the IP/EDI messages into an Outbound Queue (a particular folder per receiving partner) in the webMethods X.400 Gateway.
3. The wm.x400.gateway.Gw:sendAndFetch or wm.x400.gateway.Gw:send services retrieve the messages from the Outbound Queues and send them to the X.400 Server as separate mail messages to the recipients via the ADDONMAIL-UAFI (third party product). If the extended field batchlpm is set to Yes, the messages are combined into one X.400 mail message with multiple content pairs (up to 999 content pairs) called X.400 bodyparts. For more information about the batchlpm extended field, see Defining the Receiver Profile.