What do i like Most in 11g - B2B Part Of SOA Suite

On AS11, B2B has been made part of Oracle SOA Suite, meaning it runs on the same JVM as the rest of SOA components like BPEL, Mediator and Adapters etc.

Earlier, enterprises have to rely on messaging layer or XML Gateway to integrate B2B with internal applications.

This isn't the case anymore, B2B has been integrated with BPEL, Mediator and/or other SOA components in efficient manner through Oracle Service Infrastructure (SCA - Implementation) for better throughput. And, this offers greater performance and flexibility for an enterprise to integrate their Trading Partners with internal applications using B2B.

Little insight on how an enterprise benefits out of this integration ...



  • Enterprises no longer have to rely only on messaging for B2B integration with internal applications.

  • Enterprise can design SCA composites composed of BPEL/Mediator to handle documents received by B2B. This applies to outbound side as well.


  • SCA Composites can also be deployed to handle exceptions from B2B directly.


  • The internal queue (IP_IN_QUEUE) functionality has been retained, meaning exceptions and inbound business messages can still be delivered to internal queue. This may come handy for an enterprise who already have their infrastructure built around internal queues.

Note: Messages would be delivered to SCA Composites only if there is one deployed to receive messages from B2B. This applies to exception messages as well.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today