1. Using B2B for Oracle Integration Generation 2
  2. Use B2B for Oracle Integration in Trading Partner Mode
  3. Create B2B Integrations for Receiving and Sending

Create B2B Integrations for Receiving and Sending

When you add a transport to a trading partner, two integrations are automatically created for you: the B2B integration for receiving and the B2B integration for sending (these are not their exact names, but rather indicative of the concept).

Both integrations are front-end integrations because they directly interface with the external trading partner. These integrations are at the heart of the transport for its runtime functioning.

These integrations are automatically created when you define a transport. Two master template integrations are cloned internally to create these two integrations for the transport. The names of these master template integrations are as follows:
  • B2B Integration template FTP Receive and B2B Integration template FTP Send: Used as the master template for the FTP transport.
  • B2B Integration template AS2 Receive and B2B Integration template AS2 Send: Used as the master template for the AS2 transport.

The master template integrations are included with B2B for Oracle Integration. They are not initially present in your Oracle Integration instance, but created on-demand when you create your first transport.

When you create a transport, you have some control over the actual names of these B2B integrations. In the transport settings, you are prompted for an integration name prefix and an integration identifier prefix. These prefixes are used to generate the actual names and identifiers for the B2B integrations.

For example, the automatically created B2B integrations look as follows when the name prefix entered is Ext TP.
A table is displayed with columns for Name, Version, Style, Last Updated, and Status. To the left of the Name column are icons depicting the type of adapters used in the integration, including an icon for scheduled integrations.

In general, you don't need to edit or manage the B2B integrations directly because most functionality is driven through lifecycle actions on the transport.

Note:

You may customize the B2B integrations. However, in future versions, Oracle may provide enhancements to the master template integrations and a way to upgrade a transport, which overwrite the B2B integrations so as to leverage new features. You may have to add any customizations again into the integrations.

There are a few cases where you may need to do some management directly on the B2B integrations, specifically for the FTP transport.

  1. View Past and Future Scheduled Runs for an FTP Receive Integration - refer to various other functions you can perform. See Create Scheduled Integrations in Using Integrations in Oracle Integration Generation 2.
  2. Use submit now to trigger ad-hoc runs and make the FTP Receive integration execute immediately to poll for files.
  3. Change the default behavior for what should happen to files, in case of FTP Receive, after the inbound processing is completed. See FTP Receive Integration Postprocessing Behavior.