What do i like Most in 11g - Default JMS/AQ Delivery channel

On AS11, we have an option of going with either AQ or JMS as the default messaging layer for B2B (Internal Queues). This would enable an enterprise to go with DB backed messaging as in our earlier versions or more fashionable middleware backed messaging using JMS.

The internal queues AQ (IP Queues) and JMS (B2B Queues) shipped along with the product and based on the configuration either one can be active at any given point in time. To retain the behavior, as in earlier version 10.1.2, AQ would be a default messaging channel.

One may change the default messaging channel to JMS by enabling (providing value true) "System Parameter, Use JMS Queue" on B2B Console Configuration Tab.

The above are just the default channels, users can configure any custom listening or delivery channels using all supported transport protocols.


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 2014
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