What do you mean?
In the trivial case: on your remote machine you
just lookup the connection factory in the jndi
of your jboss server.
thanks for the reply.
I am away from work on vacation for 2 weeks.
The scenario is like this.
The external system does not have any app server. It is a stand alone application running on a seperate box remotely.
But my machine (j2ee server is running on this) is connected to the external system through serial cable.
I need to ensure that the messages in the local queue (p2p) are delivered only when the external system is up and running.
My problem is as to "how to bring the external system within purview of JMS" so that I can monitor the heart beep of external system before delivering message.
The major limitation is that I should communicate my messages only through serial cable.
thanks in advance
JBossMQ doesn't have a work-off-line mode.
If I just copy the client jars on to my remote machine and configure my initial context to point at the remotemachine in jndi.properties, does it address my problem??
If so, please provide me few lines of code how jndi properties are to be configured to look up for remote system.
I, like Adrian I think, am having a difficult time figuring out what in the word your a trying to accomplish. If you just want to talk to the JMS server from a remote machine, yes, all you need to do is set your jndi.properties to include the hostname of the machine you want to talk to. I generally just copy the jndi.properties file from the JBoss server/xxx/config directory and uncomment the line is says not to uncomment (for the client you want to uncomment it, but don't uncomment it in your JBoss distribution). Then get your InitialContext and run with it. Does this address your question?