Trading Partners and Agreements

You can create trading partners and agreements between the partners to exchange business documents. An agreement defines the terms that two trading partners, the host trading partner (the partner where Oracle Integration is installed) and the trading partner agree to follow to exchange business documents. You can create an orchestrated integration (known as the backend integration) that enforces the trading partner and agreement details.


This feature is only available on Oracle Integration Generation 2.
For example, if Acme (the host trading partner) and GlobalChips (the trading partner) want to participate in document exchanges with each other, you first define trading partner profiles for both (specify the contact details and identifiers for each). You then define a minimum of two agreements (for example, specify the document definitions to exchange, the unique identifiers of each partner, the backend integration, and other details) for each of the exchanges.
  • One agreement for the host trading partner to send an outbound message to the trading partner.
  • One agreement for the host trading partner to receive an inbound message from the trading partner.
  • Other agreements, as required by the complexity of your document exchange.

See Manage Trading Partners.

To include your trading partner agreement in an orchestration (backend) integration that processes the document exchanges, you configure adapter connections based on the transport protocol to use. Both the AS2 Adapter and FTP Adapter can be configured to run in trading partner mode on the Basic Info page of the Adapter Endpoint Configuration Wizard. This enables these adapters to enforce the details defined in the trading partner profiles and agreements. The B2B action (formerly known as the EDI Translate action) can also be configured to run in trading partner mode.

During runtime, you can track the status of messages from the Track B2B Messages pages. See Track B2B Messages.