TPI Server overview

This section provides a brief overview of the TPI Server functionality. The connector functionality is described in following sections.

The TPI Server enables the secure exchange of documents among trading partners over the Internet. The application packages documents in secure envelopes that are transmitted among trading partners according to user-configured schedules. The TPI Server supports XML, EDI, and binary data formats.

TPI supports FTP, SMTP, and WebSphere MQ for transporting documents among trading partners. The TPI Server uses a system of directories for delivery and retrieval of documents. The TPI Server maintains six document directories for each trading partner -- three for inbound and three for outbound. Each of the directories holds incoming or outgoing documents of a specific format--XML, EDI, or binary.

Sending documents

When a document is placed in one of the outbound directories, the TPI Server packages the document by first creating a digest, which includes the sender and receiver identification. The TPI Server then encrypts the document and digest in a single message. Once the document is packaged, TPI sends the message to the specified trading partner. The trading partner profile in the TPI repository determines which transport method is used to send the message.

Receiving documents

When the TPI Server receives a message from a trading partner, it decrypts the message, verifies the digital signature, and writes the document to the appropriate inbound directory. Once the message is unpacked, the TPI Server returns a Message Disposition Notification (MDN) to the message sender. The MDN verifies only that the message was received and properly unpacked. It does not indicate whether the document was fully processed by the trading partner.

Copyright IBM Corp. 1997, 2003