Trading Partner Management is the process by which customers and users are set up to use the service.

OmPrompt supports two classes of users:

> Subscribers, who control and authorise for their unique community of Trading Partners. Generally, a Subscriber will be an organisation that drives and supports a Trading Community and contracts with OmPrompt for the provision of the service.

> Trading Partners, who will send and receive messages with varying formats and devices. The OmPrompt Transaction service will translate the messages from sender format to required receiver format and deliver the message to the specified receiver(s) Subscribers use the Registration component of Trading Partner management to:

Define the Subscribers relationship with OmPrompt - names, address, contacts, authorised system controllers etc.

Define and allocate authorisation codes to all Senders and Receivers in the Trading Community Define Trading Partner relationships.

Specify the connectivity required, including security, certification etc Trading Partners use the same Registration facility to:

Define inbound/outbound message formats

Define connectivity protocols

Provide inbound/outbound message samples for use by OmPrompt in automated mapping.

Define, with OmPrompt, any code conversion/table lookup functions and business logic required to successfully execute message translation.

Test and confirm with OmPrompt successful message translation and transaction execution through the Transaction layer of the service.