X.400 trading configuration

A community can use the X.400 subsystem to exchange messages with partners. The following related topics describe the fields in the delivery exchange wizard for adding an X.400 delivery exchange and embedded servers for a community and a partner.

To launch the wizard, open the summary page for a community or partner. Click Trading pickup or Partner delivery in the navigation graphic at the top of the summary page. On the page that opens, click Add a delivery.

Community X.400 pickup

The following describes the fields in the exchange wizard for adding an X.400 pickup for a community. The fields are the same for X.420 and X.435.

Enter X.400 settings

  • Name – The name for the X.400 subsystem. This can be any name you want.

Subsystem ports

  • External (RFC1006) – The X.400 subsystem listens on this port for connections from other (most likely external) subsystems. Exchange of data between subsystems is accomplished over this port.
  • Interchange communication is done using the User Agent API port.
  • This port must be 102 or greater than 1023. Click inside the field to display a list of ports in use by Interchange. If 102 is in use, type a port number greater than 1023, but not a port already used.
  • System starter – The port used by Interchange and the X.400 subsystem to monitor the status of each other. If Interchange loses the connection on this port, it tries to restart the X.400 subsystem. If the X.400 subsystem loses the connection, it assumes Interchange has shut down and shuts itself down as well.
  • OSITP – The listening port for the lower layer OSI stack process within the X.400 subsystem.
  • User agent API – The API port used by Interchange and the X.400 subsystem user agent. All messages exchanged between Interchange and the UA go through this port.

Local configuration

  • MTA name – The name of the message transfer agent in the X.400 subsystem.
  • Alias/Routing ID – Depending on whether the delivery is associated with a community or partner, the routing ID of the community or partner in Interchange, selected from a drop-down list of the profile’s available routing IDs.
  • Country name – The two-character ISO country code. For a community delivery exchange, this should be the code of the community’s country. If a partner delivery exchange, this should be the code of the partner’s country.
  • For a list of codes see the International Organization for Standardization (ISO): http://www.iso.org/iso/home.html.
  • Connect to an Administration Management Domain (ADMD) – When selected, the following field displays.
  • Administration domain name – Identifies an administrative domain name (ADMD).
  • This is the name of an ADMD service provider for client organizations (PRMDs) that subscribe to an ADMD provider for X.400 message routing and related services. For clients who connect directly to other PRMDs, bypassing an ADMD, set the name to a single space character.
  • For a community delivery exchange, this should be the code of the community’s ADMD. If a partner delivery exchange, this should be the code of the partner’s ADMD.

Enter X.400 subsystem settings URL

  • External hostname – computer a partner’s remote X.400 system connects to when sending messages to your community. The host name can be an IP address or a fully qualified domain name.
  • The default value can be used only if your instance of Interchange runs on a single computer with a single processing node. That is, the instance does not run in a clustered environment of multiple processing nodes (multiple nodes on the same or different computers).
  • If you run Interchange in a cluster, change the value to your external load balancer. You must do this to make sure inbound messages can be delivered to your community.
  • While multiple processing nodes are the norm in a clustered environment of Interchange, only one instance of an X.400 system can exist per cluster. There can be multiple X.400 systems within a cluster, but only a single instance of each system on a single machine. This is why the load balancer, not the host of a single processing node, must be specified as the host.
  • When you export your community profile as a partner profile for your partners to import on their instances of Interchange, the partners send messages to the host specified in this field.
  • External port – The port a partner’s remote X.400 system connects to when sending messages to your community. Just as with the external hostname field, the default port value can be used only if your instance of Interchange runs on a single computer with a single processing node. If you run Interchange in a cluster, specify the port of your external load balancer.
  • When you export your community profile as a partner profile for your partners to import on their instances of Interchange, the partners will send messages to the port specified in this field.

Click Next if you want to name the exchange. Otherwise, click Finish.

The X.400 subsystem is started upon adding the delivery exchange. You can check the log files for the status. The log files are at:

<install directory>/<common directory>/subsystems/X400/<subsystem name>/runtime/log

Partner X.400 delivery

The following describes the fields in the exchange wizard for adding an X.400 delivery to a partner. The fields are the same for X.420 and X.435.

Note   If you and your trading partner both use Interchange, you do not have to manually add the partner’s X.400 exchange and other data to the partner. Instead, export your community profile as a partner profile and have your partner import the profile file. Have the partner do the same. Exchanging profiles is the norm when both parties use Interchange.

Choose subsystem

  • Subsystem – The name of the X.400 subsystem, selected from a drop-down list, your community uses to send messages to the partner.

Remote configuration

  • Alias/Routing ID – Depending on whether the delivery is associated with a community or partner, the routing ID of the community or partner in Interchange selected from a drop-down list of the available routing IDs.
  • Country name – The two-character ISO country code. For a community delivery exchange, this should be the code of the community’s country. If a partner delivery exchange, this should be the code of the partner’s country.
  • For a list of codes see the International Organization for Standardization (ISO): http://www.iso.org/iso/home.html.
  • Connect to an Administration Management Domain (ADMD) – When selected, the following field displays:
    • Administration domain name – Identifies an administrative domain name (ADMD). – This is the name of an ADMD service provider for client organizations (PRMDs) that subscribe to an ADMD provider for X.400 message routing and related services. For clients who connect directly to other PRMDs, bypassing an ADMD, set the name to a single space character. For a community delivery exchange, this should be the code of the community’s ADMD. If a partner delivery exchange, this should be the code of the partner’s ADMD.

Choose remote MTA type

On this wizard page select whether to use an existing remote message transfer agent or to add one.

Select the use existing option and click Next to select an existing remote MTA from a drop-down list.

If there are not any existing MTAs or you want a new one, select the new option and click Next.

Enter remote MTA settings

  • Name – Name of the remote MTA.
  • Remote MTA password – Password the local MTA uses to access the remote MTA.
  • Local MTA password – Password the remote MTA uses to access the local MTA.
  • TCP host – The fully qualified domain name or IP address of the remote message transfer agent.
  • TCP port – The port the remote message transfer agent listens for connections.
  • TCP address – If a TCP address, the fully qualified domain name or IP address of the host and the listening port number.
  • X25 address – If an X.25 address, the fully qualified domain name or IP address of the host.
  • TSAP – The transport services access point.

Click Next if you want to name the exchange. Otherwise, click Finish.

Related topics

Related Links