Configure/Access remote Message Queue (Open MQ)

Question

Hi,
I am new to JMS and Message Queue. I have installed Sun's Open Message Queue on my system.I have created ObjectStore and Destination(Queue) and using java program to insert and fetch messages.
Following are the details:
1. Created ObjectStore MyObjectStore with following properties:-
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:///c:/tmp
2. Created ConnectionFactory MyConnectionFactory and Destination MyQueue
3. Code to access above queue:
Hashtable env;
    Context     ctx = null;
    env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory");
    env.put(Context.PROVIDER_URL, "file:///c:/tmp");
    ConnectionFactory cf=(javax.jms.ConnectionFactory) ctx.lookup("MyConnectionFactory");
    Queue queue=(javax.jms.Queue)ctx.lookup("MyQueue");
    Connection connection = cf.createConnection();
    Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
    MessageProducer msgProducer = session.createProducer(queue);
    MessageConsumer msgConsumer = session.createConsumer(queue);
    ....................My problem is that I am able to access Message Queue on local machine only. I don't know how i can configure my MQ to be accessed on network or/and how to look up for MQ from a remote machine in network.
Can anybody help me on this.
Regards
Edited by: Arpit.Purohit on Apr 8, 2009 4:49 AM
Edited by: Arpit.Purohit on Apr 8, 2009 4:49 AM

Answer 1

Arpit,
Yes, this is because you have chosen to use com.sun.jndi.fscontext.RefFSContextFactory as the JNDI provider in which to store your destination and connection factory objects.
The Sun Java System Message Queue 4.3 Administration Guide has a section [File-System Object Stores|http://docs.sun.com/app/docs/doc/820-6740/aeogx?a=view] about this:
+"Message Queue ... supports the use of a directory in the local file system as an object store for administered objects. While this approach is not recommended for production systems, it has the advantage of being very easy to use in development environments. Note, however, that for a directory to be used as a centralized object store for clients deployed across multiple computer nodes, all of those clients must have access to the directory. In addition, any user with access to the directory can use Message Queue administration tools to create and manage administered objects"+
So if you place your JNDI store in a shared directory visible to other machines rather than C:/tmp you will be able to access it from other machines.
The ideal solution is to use an LDAP JNDI provider. See the section [LDAP Server Object Stores|http://docs.sun.com/app/docs/doc/820-6740/aeogw?a=view] in the Administration Guide.
Note that this issue relates to the administered objects used by MQ only. The MQ broker itself will be available from anywhere on the network and the messages themselves will stored in the broker's own message store.
Nigel