dcsimg
JMS persistence using Multiple Database
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Animesh_Srivastava
Posted On:   Sunday, February 17, 2002 10:46 PM

Hi, We have two geographically distant Sybase database (Tokyo and Frankfurt) which are replicated (using Sybase's internal replication mechanism). Is it possible to make an event server (using jms) such that if a message is published on Tokyo JMS (then it is delivered to all the subscribers in Tokyo) and also persisted to the Tokyo database. Since the database are replicated, the JMS running in Frankfurt picks it up and delivers it all the subscribers registered with the Frankfurt JMS. Basically the need is to send messages to all subscribers (Tokyo and Frankfurt) when a message is published from any one of the locations. Can there be some other way of doing it also? Thanks a Lot, Regard   More>>

Hi,

We have two geographically distant Sybase database (Tokyo and Frankfurt) which are replicated (using Sybase's internal replication mechanism).


Is it possible to make an event server (using jms) such that if a message is published on Tokyo JMS (then it is delivered to all the subscribers in Tokyo) and also persisted to the Tokyo database. Since the database are replicated, the JMS running in Frankfurt picks it up and delivers it all the subscribers registered with the Frankfurt JMS. Basically the need is to send messages to all subscribers (Tokyo and Frankfurt) when a message is published from any one of the locations.


Can there be some other way of doing it also?



Thanks a Lot,

Regards.

Animesh.    <<Less

Re: JMS persistence using Multiple Database

Posted By:   Chandra_Patni  
Posted On:   Monday, February 18, 2002 07:18 PM

You can certainly use Pub/Sub model with durable subscriptio, where one Subscriber to Tokyo Messaging server publishes messages to Frankfurt server and a subscriber to Frankfurt messaging server publishes a message to Tokyo messaging server. Of course you have to unwrap the message and republish the message with some application header so that you break the circularity.


Also, check your messaging vendor if they support durable subscription or not.

About | Sitemap | Contact