1. Using B2B for Oracle Integration 3
  2. Use B2B for Oracle Integration in Standalone Mode
  3. Standalone Mode Concepts

Standalone Mode Concepts

B2B for Oracle Integration provides several components that enable you to design integrations to handle B2B messages. This includes the AS2 Adapter and the B2B action for EDI translation. Use these components to create integrations to receive and send messages from (or to) your external trading partners. In this mode, the external trading partner is not defined explicitly as you do in B2B trading partner mode. Standalone mode ignores any trading partner definitions.

Standalone mode supports the following:
  • Interfacing with external trading partners using any adapter provided in Oracle Integration: AS2, FTP, REST, SOAP, AQ, and more.
  • Handling any data formats that Oracle Integration supports: EDI, CSV, XML, JSON, and more.
In contrast, B2B trading partner mode currently supports a limited set of adapters (AS2 and FTP) and only EDI data formats.

B2B Action

The B2B action was previously called EDI Translate. This action was renamed because it now provides additional operations besides EDI translation. However, those operations are only available in B2B trading partner mode. When using the B2B action in standalone mode, it provides the two key operations, inbound and outbound EDI translation, just as it did before. Any existing integration you created using the EDI Translate action works the same as before.

Support for the EDIFACT, X12, X12 HIPAA, OAG, custom, fixed length, and delimiter document standards is available in standalone mode.

Details about how to use the B2B action in your integrations are provided. See Design a B2B Standalone Mode Integration.

Adapters for Communication

You can design your B2B integrations with any adapter as a trigger or invoke connection for receiving or sending messages from (or to) a trading partner. This section provides pointers for using the popular communication protocols in conjunction with B2B processing below:
  • AS2

    You can design an integration to receive or send EDI or another type of payload over the AS2 protocol.

  • FTP

    You can design an integration to poll for files or send files with EDI or another type of payload. A stage file action is typically used with the FTP Adapter.

  • REST, plain HTTP

    You can design an integration to receive an EDI or another type of payload over REST or plain HTTP using the REST Adapter. For EDI processing, you can configure the REST Adapter trigger to accept a binary payload and process it using the B2B action.

  • SOAP

    You can design an integration to receive or send a SOAP message from (or to) a trading partner, typically with an XML payload to cover any of the XML-based B2B standards. In this pattern, you bring the XSD schemas and upload them into the SOAP Adapter trigger or invoke adapter configuration.