EDI Message – Input Parameters for the deliverX400 Service

The following table specifies the input parameters for the deliverX400service if you want to send an EDI message:

Type of X.400 message Input parameters for the deliverX400 service
EDI messages
  • Bizdoc (BizDocEnvelope) with one content part and address information out of Trading Networks Profiles. This is the EDI message you want the Adapter for X.400 to send and it cannot have more than one content part.
  • ediMessageOut with additional parameters for an X.400 IEDI message to be set by the user (e.g.,subject).
  • Alias Name of the remote Integration Server, if the X.400 Gateway does not reside on the local machine.

The deliverX.400 service automatically sets the following parts of the ediMessageOut structure:

  • contentType (PEDI)
  • locallD (unique Trading Networks document ID)
  • from
  • primary
  • p7recipient
  • bodypart(s) ( one or more message content parts, Base64 encoded)

The BizDocEnvelope provides the information for all these. For the bodypart, Adapter for X.400 pulls the first content with PartName edidata from the BizDocEnvelope structure. If no content with the name edidata is present, Adapter for X.400 uses the first content part.

For more information about the structure of an EDI message, see the chapter on submitting and receiving EDI messages in the UA-FI Programmer’s Guide.

If an EDI message was sent via service deliverX400, Adapter for X.400 sets the Trading Networkss user status to X400queued. After receiving an inbound notification, Adapter for X.400 then sets the actual value of the user status of the document to: X400submitted/X400non-subrnitted, X400delivered/X400non-delivered, or X400positiveEDI/X400negativeEDI/X400forwardedEDI