Sending to and Fetching Messages from X.400 Server

There are two X.400 message types that you can send or receive:
  • Inter Personal Messages referred to as IP messages or IPMs
  • X.435 EDI messages (PEDI) referred to as EDI messages

For outbound processing, when you want to send an X.400 message (IP or EDI message) to a partner, Adapter for X.400 batches the messages in an Outbound Queue. There is one Outbound Queue for each receiving partner. The Adapter for X.400 provides the wm.x400.gateway.Gw:sendAndFetch and wm.x400.gateway.Gw:send services to retrieve messages from the Outbound Queues and send them to the X.400 Server. To send the messages, the sendAndFetch and send services invoke the ADDONMAIL-UAFI (third party product).

The sendAndFetch and fetch services are used for inbound processing to retrieve the data from your X.400 mailbox on the X.400 Server. In this situation, the sendAndFetch and fetch services invoke the ADDONMAIL-UAFI, which fetches the messages and notifications out of your X.400 mailbox. The sendAndFetch and fetch services then convert the messages and notifications into XML and store them in the inbound folder for further processing.

You should create a scheduled to task to have Integration Server periodically invoke the sendAndFetch service. When you create the scheduled task, you define the time interval when you want outbound messages sent to the X.400 Server and when you want to retrieve the inbound data from your X.400 mailbox. If you want to define different times for sending and fetching, you can create scheduled tasks for the send and fetch services. Use the Scheduler function of the Integration Server Administrator to create a scheduled task. Before using Adapter for X.400r you have to configure the connection to the X.400 mailbox. For information on how to create a scheduled task, refer to the IBM webMethods Integration Server Administrator’s Guide or IBM webMethods Integration Server Online Help.

For more information about configuring the fields in the adapter, see Configuring Communication Parameters.

The following table specifies what input parameters you can provide for the send and fetch services. If you use a combined filter (combination of simple criteria), there is an implicit logical OR between values of the same attribute/criteria type (e.g. the values new/listed/processed for the attribute type entry status), and an implicit AND between values of different attribute/criteria type.

Service name Input parameters for the service
send
  • text_format

    This parameter is used to set the text conversion tables for IA5 and T.61 strings to be used. The tables are specified in files with extension .chs. This parameter specifies which character mapping file to use. The most commonly needed files (ANSI character set and the most common DOS code pages) are installed together with UA-FI. This parameter is seldom needed. It can for instance be used if you want to submit PCASCII text files while using UA-FI for Windows. The default values are ANSI for all operating systems except DOS where it is PCASCII. Possible values: ANSI, PCASCII
fetch
  • text_format

    This parameter is used to set the text conversion tables for IA5 and T.61 strings to be used. The tables are specified in files with extension .chs. This parameter specifies which character mapping file to use. The most commonly needed files (ANSI character set and the most common DOS code pages) are installed together with UA-FI. This parameter is seldom needed. It can for instance be used if you want to submit PCASCII text files while using UA-FI for Windows. The default values are ANSI for all operating systems except DOS where it is PCASCII.

  • deleteMessages

    If set to false, messages will not be deleted from the X.400 mailbox. Default value is true.

  • messageFilter/ms-entry-status
    The ms-entry-status (the status of the message in the MS)
    • new means that no attributes have yet been fetched or listed from this message.
    • listed means that the message has been listed or that parts of it have been fetched.
    • processed means that the entire message with all BodyParts has been fetched from the MS.
  • messageFilter/ms-entry-type
    • delivered_message is used to select e-mail messages (IPM), EDI messages (Pedi), Receipt Notifications (IPN) and Pedi Notifications (EDIN).
    • delivered_report selects Delivery and Non-Delivery Reports.
  • messageFilter/p2-content
    This filter fetches IPM/IPN messages only (P2 or P22). The P2_content can be:
    • IPM (Inter Personal Message)
    • IPN (Receipt Notification)
    This criterion is only valid for the entry type delivered_message. Delivery Reports will NOT be fetched when using this selection criterion.
  • messageFilter/content-type
    The content_type can be:
    • P2
    • P22
    • Pedi
    P2 will select 1PM messages with content according to the 1984 X.400 standard, while P22 will select messages with content according to the 1988 X.400 standard.

    The content_type describes the content of the message. This filter can for example be used to select between EDI and 1PM messages.

  • messageFilter/pedi-content
    This criterion fetches Pedi messages only. Pedi-content can be:
    • EDIM (EDI message)
    • EDIN (EDI Notification)
    Note: This criterion is not always supported by the MS. Check with your service provider.
  • messageFilter/x400-address

    This criterion is used to fetch messages that are sent from a certain originator.

  • messageFilter/ms-sequence-numbers

    The MS sequence numbers is a unique number assigned by the central Message Store to identify a message (range 0-2147483647).

    For MS sequence numbers you can:

    • Specify a list of single MS sequence numbers separated by commas.
    • Specify a range by giving the first and the last number separated by a hyphen.
    • Specify a combination of single MS sequence numbers and ranges separated by commas.