Sunday Aug 28, 2011

Controlling the dequeuing of messages

A new feature has been introduced in B2B 11g with which the messages from JMS can be dequeued in a controlled fashion.

The use case is to achieve the outbound message throttling. For example, if there is an outage and for some reason the JMS queue is holding a big volume of messages, then there needs a way to process these messages in a controlled way rather than bombarding the B2B infrastructure with a huge pileup.

This feature enables users to configure the # of messages to be picked per poll and a polling interval and as of now this feature is available for JMS transports only.

Configuration details:

Go to "Transport Protocol Parameters" for JMS transport protocol and set the following parameters:

- Message Count
- Polling Interval

If Message Count is 100 and polling interval is 10, then B2B picks 100 messages, sleeps for 10 milliseconds and picks the next 100 messages so on and so forth.

With this feature, you can ensure the controlled processing of high volume messages in B2B.

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
« August 2011 »
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
29
30
31
   
       
Today