Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle B2B
11g Release 1 (11.1.1)

Part Number E10229-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

1 Introduction to Oracle B2B

Oracle B2B is an e-commerce gateway that enables the secure and reliable exchange of business documents between an enterprise and its trading partners. Oracle B2B supports business-to-business document standards, security, transports, messaging services, and trading partner management. The Oracle SOA Suite platform, of which Oracle B2B is a binding component, enables the implementation of e-commerce business processes. Oracle B2B also supports Health Level 7, which enables health care systems to communicate with each other.

For more information about Oracle SOA Suite, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

This chapter contains the following topics:

1.1 Oracle B2B and Business-to-Business E-Commerce

E-commerce is the buying and selling of products or services over the Internet, including business-to-business (B2B). In B2B e-commerce, an enterprise extends its business processes over the Internet to reach trading partners. B2B e-commerce represents classic business processes, mature business documents, and industry-tempered messaging services. It requires a unified business process platform, end-to-end instance tracking, visibility and auditing, integrated process intelligence, process and service governance, and centralized security.

You can think of an e-commerce transaction between businesses as analogous to a mail or express carrier (shipping) transaction. In both kinds of transactions, the sender must consider the details required for packaging and sending an item, and the receiver's requirements. Table 1-1 provides an example that compares the two kinds of transactions.

Table 1-1 Comparing Traditional and E-Commerce Transactions: An Example

Traditional Shipping Transaction E-Commerce Transaction

What is the item to be shipped, that is, the transaction item?

Cell phone

Electronic document

Document protocols: Custom, EDI EDIFACT, EDI X12, HL7, OAG, positional flat file, RosettaNet, UCCnet, and more

How is the item packaged?

Box, bubble wrap

Packaging protocols: MIME, SMIME, SOAP, XMLDSig, XMLEncrypt

How is the item sent and received?

Truck, ship, airplane

Transport protocols: HTTP, File, FTP, SFTP (SSH FTP), TCP/IP, SMTP, MLLP

Who is the carrier?


Message exchange protocols: RNIF, AS1, AS2, ebMS

What carrier services are required?


  • Signed receipt

  • Overnight/next day

  • Delivery attempts


  • Nonrepudiation

  • Time to acknowledge/respond

  • Retry counts

This guide describes how to use Oracle B2B to define the document, the packaging, and the delivery, in addition to configuring trading partners, creating and deploying agreements, and monitoring a deployment.

1.2 Protocols Supported in Oracle B2B

Oracle B2B supports numerous industry-standard e-commerce protocols, as defined for a range of industries, including health care, retail, IT, telecom, electronics, manufacturing, the food industry, and more. Table 1-2 lists the protocols supported in Oracle B2B. Protocols marked with an asterisk (*) are in preview mode in this release.

Table 1-2 Protocols Supported in Oracle B2B

Protocol Type Protocol

Document protocol

  • Custom (user-defined)

  • EDI EDIFACT, all versions

  • EDI X12, all versions

  • HL7, all versions

  • RosettaNet PIP business documents

  • OAG*

  • Positional flat file (includes SAP iDoc)*

  • UCCnet*

  • Custom (non-XML)*

  • NCPDP Telecom*

  • EDIEL*

Packaging protocol

  • MIME 1.0

  • S/MIME 2.0, S/MIME 3.0

  • SOAP

  • XML digital signature (XMLDSig)

  • XML encryption (XMLEncrypt)

Transport protocol

  • AQ

  • Email (SMTP 1.0, IMAP 1.0, POP3)

  • File

  • FTP and SFTP (SSH FTP)

  • HTTP (HTTP 1.0, HTTP 1.1) and HTTPS (HTTPS 1.0, HTTPS 1.1)

  • JMS

  • TCP/IP

Message exchange protocol

  • AS1-1.0*, AS2-1.1

  • MLLP-1.0

  • ebMS-1.0, ebMS-2.0 (ebXML Messaging Service)

  • RosettaNet-01.10, RosettaNet-V02.00

  • Generic File-1.0

  • Generic AQ-1.0

  • Generic FTP-1.0

  • Generic SFTP-1.0

  • Generic JMS-1.0

  • Generic HTTP-1.0

  • Generic Email-1.0

About Document Types:

Using the Custom and positional flat file document protocols, you can use many other document types, including W3CXML Schema (OAGIS, xCBL, UBL, ebXML, and more). Use Oracle B2B Document Editor to create the guideline documents.

1.3 Features in Preview Mode

The following document protocols are in preview mode for this release:

The following message exchange protocols are in preview mode for this release:

Command-line tools for the following operations are in preview mode for this release:

The following B2B integration type is in preview mode for this release:

Scripts for archiving and restoring data are in preview mode for this release. See Chapter 19, "Scripts for Archiving and Restoring Data," for more information.


Use preview mode features with caution, particularly in production environments.

1.4 Oracle B2B Metadata

Oracle B2B instance data is stored and managed within the SOAINFRA schema of your database. Oracle B2B metadata for design-time and configuration is stored and managed through Metadata Services (MDS), available in Oracle Fusion Middleware. See Oracle Fusion Middleware Administrator's Guide for more information about MDS.

1.5 Security Features of Oracle B2B

Oracle B2B leverages the security features of Oracle Platform Security Services, a comprehensive security platform framework. Oracle Platform Security Service supports:

The default administrator user created during Oracle SOA Suite installation is assigned the Administrator role, which has access to all Oracle B2B functionality. When logged in as the default administrator user, you can create additional users and assign the following roles:

See "Adding Trading Partner Users" for instructions on how to assign roles.

The partner data you design, deploy, and manage with the Oracle B2B user interface is secured by its centralized storage in the Metadata Service (MDS) repository.

Other security features include:


Oracle B2B does not support the CLIENT-CERT authentication method. Therefore, B2B is not able to post to OAM-SSO protected URLs.

See the following for more information about security:

1.6 How Does Oracle B2B Fit into a SOA Implementation?

As a business-to-business gateway, Oracle B2B is used to extend business processes to trading partners. When Oracle B2B is used in a SOA composite application, you can model an end-to-end business process integration.

Oracle SOA Suite provides a complete set of service infrastructure components for designing, deploying, and managing composite applications. The multiple technology components of a composite application share common capabilities, including a single deployment and management model and tooling, end-to-end security, and unified metadata management. See Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite for more information.

In a SOA implementation, Oracle B2B functions as a binding component, with network protocols and services that enable message sending and receiving:

In addition to messages, Oracle B2B can also send attachments and large payloads in a SOA implementation. See Appendix A, "Performance Tuning and Large Payloads," for information about handling large payloads.


With the integration of the B2B, Mediator, and BPEL components within Oracle SOA Suite, the XML Gateway Internal Delivery channels are not needed in Oracle B2B 11g to communicate with Oracle E-Business Suite. This can be achieved by using the Oracle Application Adapter available in Oracle SOA Suite.

1.7 Sending a Purchase Order: An Example of a SOA Implementation

The following example describes how the components of a SOA composite application are used to send a purchase order that originates from Oracle E-Business Suite, as shown in Figure 1-1.

Figure 1-1 An Outbound Purchase Order in a SOA Composite Application

Outbound purchase order
Description of "Figure 1-1 An Outbound Purchase Order in a SOA Composite Application"

The outbound purchase order (P. O.) is an XML document that participates in an end-to-end business process as follows:

  1. An application, for example, Oracle E-Business Suite, initiates the P. O. process. The P. O. document uses the application-generated XML.

  2. Oracle Mediator receives the P. O. from Oracle E-Business Suite. The P. O. is translated to canonical XML through XSLT Mapper, and is validated by using the schema obtained when the composite application was validated. Oracle Mediator routes the message to Oracle BPEL Process Manager.

  3. Oracle BPEL Process Manager receives the P. O. from Oracle Mediator. Business processes such as human workflow, business rules, and error handling can apply before Oracle BPEL Process Manager sends the P. O. back to Oracle Mediator.

  4. Oracle Mediator receives the P. O. from Oracle BPEL Process Manager. The P. O. is transformed from canonical XML to the target XML through XSLT Mapper and then routed to Oracle B2B.

  5. Oracle B2B receives the P. O. from Mediator, translates the P. O. to EDI native format, for example, and manages the interaction with the trading partner.

  6. Oracle Business Activity Monitoring (BAM) monitors the end-to-end process.

See the following for more information:

1.8 Oracle B2B Samples

The B2B samples guide you through the steps to create guideline files, design B2B transactions, deploy and monitor trading partner agreements, and create and deploy SOA composite applications. The composite applications include a B2B binding component and use the document definitions that you create in Oracle B2B.

Samples are available for the following document types:

These end-to-end samples are based on a scenario in which two trading partners, Acme and GlobalChips, participate in a transaction. Acme is the initiator (the buyer, in the case of a purchase order scenario) and GlobalChips is the responder (the seller in a purchase order scenario). In the HL7 sample, Acme (initiator) sends an ADT_A01 admit patient message and receives an ACK_A01 acknowledgment from GlobalChips.

The samples include instructions and sample document definition files for you to create all the documents, agreements, and SOA composites you need to run the samples. The completed SOA composite application is also provided for each sample.

To download the samples, go to

See "What You Need to Get Started with Oracle B2B" for the components required to use the samples.

1.9 Administering Oracle B2B in the Oracle Fusion Middleware Environment

The following components provide monitoring, configuration, and performance tuning capabilities for Oracle B2B:

Within the Oracle B2B interface, use the following for monitoring and configuration: