Advanced Queuing - Oracle

JMS Propagation
oe_ws from database db1, the order entry database, to the western shipping
database db2. The WS_bookedorders_topic at db2 is a remote subscriber to the
OE_bookedorders_topic in db1.
Example Scenario for Case 2
Assume the order entry application and Western region shipping application are on
different databases, db1 and db2. Further assume that there is a dblink dblink_
oe_ws from the local order entry database db1 to the western shipping database
db2. The agent "Priority" at WS_bookedorders_topic in db2 is a remote
subscriber to the OE_bookedorders_topic in db1. Messages propagated to the
WS_bookedorders_topic are for "Priority" only.
public void remote_subscriber(TopicSession jms_session)
{
Topic topic;
ObjectMessage obj_message;
AQjmsAgent remote_sub;
try
{
/* get a handle to the OE_bookedorders_topic */
topic = ((AQjmsSession)jms_session).getTopic("OE",
"OE_bookedorders_topic");
/* create the remote subscriber, name unspecified and address
* the topic WS_booked_orders_topic at db2
*/
remote_sub = new AQjmsAgent(null, "WS.WS_bookedorders_topic@dblink_oe_
ws");
/* subscribe for western region orders */
((AQjmsSession)jms_session).createRemoteSubscriber(topic, remote_sub,
"Region = ’Western’ ");
}
catch (JMSException ex)
{ System.out.println("Exception :" + ex); }
catch (java.sql.SQLException ex1)
{System.out.println("SQL Exception :" + ex1); }
}
Database db2 - shipping database: The WS_booked_orders_topic has two
subscribers, one for priority shipping and the other normal. The messages from the
Order Entry database are propagated to the Shipping database and delivered to the
correct subscriber. Priority orders have a message priority of 1.
Creating Applications Using JMS 12-85