O Running Oracle B2B as a Hub
Oracle B2B provides an out-of-box solution that allows Oracle B2B to run as a hub.
The appendix includes the following sections:
Introduction
To run Oracle B2B as a hub, you need to configure three trading partners.
For example:
-
OracleServices: The host trading partner that acts as a hub.
-
MarketInc: The trading partner that sends CUSTOM PurchaseOrder_A01 documents to another trading partner, RetailInc by using OracleServices.
-
RetailInc: The trading partner that receives the CUSTOM PurchaseOrder_A01 documents sent by MarketInc through OracleServices.
So, the message flow as per the preceding example will be:
MarketInc <--- PurchaseOrder_A01 ----> OracleServices (HUB) <--- PurchaseOrder_A01 ----> RetailInc
The preceding flow demonstrates that MarketInc is sending the PurchaseOrder_A01 messages to OracleServices, but actually in the technical implementation, MarketInc assumes the following flow:
MarketInc <----------------> RetailInc
So, at the Oracle B2B server of MarketInc, the agreement(s) are configured between MarketInc and RetailInc, but the channel location is the one on which OracleServices' Oracle B2B server listens for messages from partners.
Configuring Oracle B2B as a Hub
The overall steps to configure Oracle B2B hub are as shown below.
To configure Oracle B2B as a hub:
Testing the Configuration
To start and test the message flow, place a PurchaseOrder_A01 message in the external listening channel directory of OracleServices.
Once the message gets removed from the directory, navigate to Oracle B2B reports and verify:
-
The incoming PurchaseOrder from MarketInc has been processed successfully.
-
An ACK for incoming PurchaseOrder has been sent to MarketInc.
-
The same PurchaseOrder has been passed to RetailInc.