Restrictions

Clustering

Adapter for X.400 isn’t usable in a clustered webMethods environments.

It isn’t possible to run the Adapter parallel on two or more Integration Servers in a load balanced scenario.

Adapter for X.400 only supports fail-over configurations.

In these configurations the adapter is installed on two Integration Servers (production and fail over system), but there is only one running instance on the active Integration Server.

Standards Conformance

P7 (X.413) protocol operations with X.400 server (MS), P2, P22, PEDI.

Common Restrictions

Common restrictions for Adapter for X.400 include the following:

• X.25 is unsupported (but might be possible by TCP/IP over X.25)
• Maximum 999 bodyparts per message
• P772 (military messaging protocol) is unsupported
• X.420 (P22) is partially supported
• X.400 1988 address parameter DN is not supported
• Outbound: content type is set to P2/P22/PEDI. FTAM bodyparts are unsupported.
• Inbound: Adapter for X.400 processes FTAM bodyparts by sending the content to Trading Networks and discarding the FTAM file name parameters.
• Transaction protection will be provided between the Adapter for X.400 Gateway Inbound /Outbound folders and the X.400 message store.
• Large document handling is only supported within Trading Networks for received IP and EDI messages. During the transport from the mailbox to Trading Networks via X.400 Gateway Service a large document will be held in memory. Therefore sufficient memory has to be provided by the hardware.

Special Features

• Switch-off the Trading Networks user status update. Adapter for X.400 allows you to switch-off the user status. To do this, set parameter noUserStatus=true in the configuration file Integration Server_directory\packages\X400forTN\config\x400Cfg.properties. The default value is false.