Overview of Managing B2B Configuration
When you use B2B Adapter as a delivery method for message exchange, Oracle Fusion Collaboration Messaging Framework routes messages through Oracle B2B, and you need to do additional set up in Setup and Maintenance using the Manage B2B Configuration task.
You need to create trading partners and trading partner agreements in Oracle B2B, for every trading partner that doesn't use a service provider and for each service provider with whom you want to exchange messages. You also have to configure the delivery channel to be used to deliver messages.
The Trading Partners that need to be set up in B2B Configuration correlate to the trading partners and service providers in Collaboration Messaging Framework:
-
If a service provider is being used, then the trading partner name set up in B2B configuration needs to be the same as the service provider name in Manage Collaboration Messaging Service Providers.
-
If no service provider is used, the trading partner name set up in Manage B2B Configuration has to be the same as the name of the trading partner in Manage B2B Trading Partners (which is to say, the trading partner in Manage B2B Trading Partners must be set up with an ID type of Name).
For outbound messages, all delivery related information such as URL, user name, and password are set up in Oracle B2B. You have to define the Sender ID and Sender ID type using the Manage Collaboration Configuration task so that they're included as HTTP headers.
If you use predefined collaboration message definitions for exchanging messages with trading partners or service providers, there is no need to create any new document-related artifacts in Oracle B2B. You can use predefined document definitions to create trading partner agreements. However, if you create a new external message definition in Collaboration Messaging Framework, you need to create a new document type in Oracle B2B. The document type must match the message type of the external message definition.
Your B2B setup and the corresponding setup in Collaboration Messaging Framework must have this correlation:
|
B2B Artifact |
Collaboration Messaging Artifact |
|---|---|
|
Document Protocol |
External Message Definition-Messaging Standard |
|
Document Protocol Version |
External Message Definition-Standard Version |
|
Document Type |
External Message Definition-Message Type |
|
Trading Partner Name |
Note: If the trading partner uses a service provider, then
the trading partner set up in B2B Configuration has to have the same
name as the service provider. If there is no service provider being
used, then the trading partner set up in B2B configuration needs to
have the same name as the trading partner in Manage B2B Trading Partners.
|
Within Collaboration Messaging Framework, the setup for exchanging messages through Oracle B2B requires that the delivery method type B2B Adapter is used for the service provider or the trading partner if no service provider is being used, and the delivery method name that has B2B Adapter as the delivery method type must be associated with all inbound and outbound messages.
Refer to the Oracle Fusion Middleware User's Guide for Oracle B2B for details of the B2B functionality.