By Juergenkress-Oracle on Jun 04, 2015
First of all, season's greetings to everyone!
Then, let me introduce this post saying that, already in the version 11g, a generic HTTP listening channel for message posting to B2B using the HTTP protocol was available. Any configured trading partner could use this generic channel to post messages to B2B.
A single common URL was available by default:
In this way, a single listening channel is able to serve multiple trading partners for every HTTP communications with B2B.
When this channel is used, the process follows the default steps for message processing, namely:
Sender identification (i.e. using HTTP Header);
Document protocol/version/type identification ;
Message processing (parsing and validation);
Synchronous delivery to a back-end application.
The only differentiation factor is: since this channel is generic and not configurable or even available on the list of listening channels in B2B console, make it unavailable for channel callout configuration.
This has now changed with the 12c version.
With the version 12c of B2B is now possible to define a generic HTTP transport callout and associate it with a specific transport level callout.
As of now, this is driven by an B2B configuration Fusion Middleware property that needs to be added on Oracle Enterprise Manager Fusion Middleware Control