Is ActiveMQ suitable for this Store-And-Forward scenario?

[azbel <az...@msn.com>]

Good afternoon.
I'm currently evaluating existing JMS Servers in order to fulfill the
following requirement:

A Java client application must send XML messages to JMS on the application
server, but the network is not available most of the time. XML messages must
be persisted in the local client machine and be forwarded when the
connection is available. I suppose that configuring an embedded broker with
ActiveMQ would be the solution since it will persist the messages, but only
if it provides the required funcionality of sending the message when the
network is available again.

Are my assumptions correct? Does ActiveMQ fulfill the requirement?
Thanks in advance.

-- 
View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13416012
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Is ActiveMQ suitable for this Store-And-Forward scenario?

[azbel <az...@msn.com>]

Thanks for clarifying! :-D
-- 
View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13427709
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Is ActiveMQ suitable for this Store-And-Forward scenario?

[ttmdev <jo...@ttmsolutions.com>]

There are two basic deployment configurations for ActiveMQ brokers: embedded
and standalone. 

An embedded broker executes within the same JVM process as the client(s)
that is using its services. The client communicates with the embedded broker
via direct method invocation. 

Standalone brokers do not have any client applications that co-reside within
its JVM. Clients communicate with standalone brokers through TCP/IP network
connections. 

You will need a bridge in order to have ActiveMQ interoperate with BEA's
implementation of JMS. Or you could 'embed' ActiveMQ within the WebLogic
server  d:-)

Joe  





azbel wrote:
> 
> Thanks for replying, Joe.
> The client application won't be transitory, but I wonder what you mean by
> standalone broker. Do you mean developing it from scratch? That would
> require to implement all the polling to the server and the persistance
> feature among other things. My idea is to leverage existing projects, but
> I'm open to develop something from scratch if it's the only option.
> 
> By the way, the JMS server is WebLogic. Won't there be a problem?
> Greetings.
> 

-- 
View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13419222
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Is ActiveMQ suitable for this Store-And-Forward scenario?

[azbel <az...@msn.com>]

Thanks for replying, Joe.
The client application won't be transitory, but I wonder what you mean by
standalone broker. Do you mean developing it from scratch? That would
require to implement all the polling to the server and the persistance
feature among other things. My idea is to leverage existing projects, but
I'm open to develop something from scratch if it's the only option.

By the way, the JMS server is WebLogic. Won't there be a problem?
Greetings.
-- 
View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13418678
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Is ActiveMQ suitable for this Store-And-Forward scenario?

[ttmdev <jo...@ttmsolutions.com>]

Yes, ActiveMQ will meet your requirements. You can have the ActiveMQ message
broker, on your local client machine, persist the XML messages so that when
the network is available it can forward the messages on to the ActiveMQ
broker that you have deployed on the server machine. 

If your client application is somewhat transitory, then you may want to
elect not to use an embedded broker and instead deploy a standalone or
daemon-like broker on your client machine. Thus you are assured that the
persisted messages are forwarded immediately upon the network becoming
available.    

Joe


azbel wrote:
> 
> Good afternoon.
> I'm currently evaluating existing JMS Servers in order to fulfill the
> following requirement:
> 
> A Java client application must send XML messages to JMS on the application
> server, but the network is not available most of the time. XML messages
> must be persisted in the local client machine and be forwarded when the
> connection is available. I suppose that configuring an embedded broker
> with ActiveMQ would be the solution since it will persist the messages,
> but only if it provides the required funcionality of sending the message
> when the network is available again.
> 
> Are my assumptions correct? Does ActiveMQ fulfill the requirement?
> Thanks in advance.
> 
> 

-- 
View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13416441
Sent from the ActiveMQ - User mailing list archive at Nabble.com.