jndiContext.lookup

Hi,

It seems from your description that you are trying to use the default file store that comes with the broker

for your administered objects repository. Please let us know if you are trying to use LDAP.

One thing that is not clear though is how you are creating the jndicontext. The following code will be helpful

This is for the filestore.

Hashtable env = new Hashtable();

env.put (Context.INITIAL_CONTEXT_FACTORY,

"com.sun.jndi.fscontext.RefFSContextFactory");

env.put (Context.PROVIDER_URL,

"file:///c:/imq_admin_objects");

Context ctx = new InitialContext(env);QueueConnectionFactory myQConnFactory = (QueueConnectionFactory)

ctx.lookup("MyQueueConnectionFactory");

If you are a subscriber tyring to get a handle to the filestore on the other machine. Then you'll have to make sure that filestore is accessible on the network.

In case of solaris/linux the ProviderURl will change to

file:///imq_admin_objects

assuming imq_admin_objects is the filestore folder.

The preffered way to register the administered objects in the production environment is in a LDAP. If you are using LDAP then the code will change to

Hashtable env = new Hashtable();

env.put (Context.INITIAL_CONTEXT_FACTORY,

"com.sun.jndi.fscontext.com.sun.jndi.ldap.LdapCtxFactory");

env.put (Context.PROVIDER_URL,

"domain name and the port on which the LDAP provider is listening");

Context ctx = new InitialContext(env);QueueConnectionFactory myQConnFactory = (QueueConnectionFactory)

ctx.lookup("MyQueueConnectionFactory");

Please have a look at http://docs.sun.com/source/817-3727/adminobj.html

to get more understanding on managing administerd objects.

thx

Vibhor

Vibhor_Sharma at 2007-7-3 0:14:17 >

On windows if you share a folder and then map that shared folder on to a drive of your local machine. That shared file can be accessed in a manner similar to a file existing on your local machine.

For example you have a machine1 where your broker resides. If you have configured a folder called c:\temp

for the file store,you can make that folder shareable and give permissions to people to use it. Now assume that machine2 has your subscribers. You can map the shared folder on machine1 to a drive g:

When you use this shared folder for creating the ProviderURL you'll use

file:\\\g:\temp

i hope this helps

Vibhor_Sharma at 2007-7-3 0:14:17 >

yes that is correct you can expose the service port on the firewall that you want and then access the broker.

It's always a good idea to expose a particular port of the service desired than to expose all the ports.

Are you trying the firewall setup to access your broker?

can you ping your broker from the remote machine where you intend to create the subscriber?

If you are using MQ3.5 then then you'll need to set up

imqaddresslist attribute in the connectionfactory object with the address syntax.

Refer table 4.3 on

http://docs.sun.com/source/817-3728/runtime.html#wp26987

have you done that ?

when you use the following as the address syntax

mq://host name:7676/jms

you are accessing the port mapper and then the port mapper will allocate the port dynamically for the service that you want in your case it is jms service.

The service port that you want can be found out by performing telnet to the broker host and it will give you all the dynamically allocated ports for all the supported service.

If you just want to access a particular port get the corresponding port number from the above mentioned step and then use

mqtcp://hostname and port number/jms

in the imqaddesslist of the connection factory object.

Vibhor_Sharma at 2007-7-3 0:14:18 >

While creating the Administrator Object, what attribute value did you

give for "java.naming.provider.url" ?

Following is an example I executed on my system. Let me know if this help ?

Creating the queue connection factory object:

imqobjmgr add -t qf -l "cn=testQCF" -o "imqBrokerHostName=aparna" -o "imqBrokerHostPort=7676" -j "java.naming.factory.initial=

com.sun.jndi.fscontext.RefFSContextFactory" -j "java.naming.provider.url=file:///space/temp/fsc"

Code :

Hashtable env = new Hashtable();

env.put (Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.fscontext.RefFSContextFactory");

env.put (Context.PROVIDER_URL,"file:///space/temp/fsc");

Context ctx = new InitialContext(env);

queueConnectionFactory = (QueueConnectionFactory)ctx.lookup("cn=testQCF");

queueConnection = queueConnectionFactory.createQueueConnection();

Aparna at 2007-7-3 0:14:18 >

couple of things first

a)When you say that you have added the connection factory it seems that you have added the object store. The values that you have provided appear to be those of object store. Please remember that the default object store is a filestore.

While adding the object store you are supposed to use the correct protocol since we support file store and ldap the valid protocols should start with either file: or ldap and not mq. Hence it gives you a malformed URL exception because mq is not a supported protocol for the providerURL for the object stores.

please check

http://docs.sun.com/source/817-6024/tutorial.html

b)Once you have added the object store now add the connection factory object. If you are using imqadmin GUI to add the CF, then right click on the connectionfactories option(underneath the object store you created) and select addconnectionfactoryobject. There specify the connection handling details in your case it is

mq://rumbleRTE:7676/jms and this will be added to the mqaddresslist. Please also add the lookup name for this connection factory object for example myCF.

c)In case you are using filestore which you are and if you want to enable the filestore to be accessed remotely then you'll have to map the filestore and make it accesible or rather shared. From your code it appears that the file store has been created at c:\temp. Can you share this location and map this file on your remote subscriber machine. In case you map this c:\temp to a g: drive on your remote subscriber then the providerURL will become file:///g:/temp.

d)Finally telnet on your broker(running state) machine and you'll come to know the services running on your broker. It will also give the port number. So once you know the port number of your desired service(jms) expose that port also on the firewall. So now you'll not only expose 7676 but also the desired service port .

thanks

Vibhor

Vibhor_Sharma at 2007-7-3 0:14:18 >

> couple of things first

> c)In case you are using filestore which you are and

> if you want to enable the filestore to be accessed

> remotely then you'll have to map the filestore and

> make it accesible or rather shared. From your code it

> appears that the file store has been created at

> c:\temp. Can you share this location and map this

> file on your remote subscriber machine. In case you

> map this c:\temp to a g: drive on your remote

> subscriber then the providerURL will become

> file:///g:/temp.

>

I am currently trying to enable JMS through the HttpTunnel capabilities of the Enterprise Trial version of IMQ. From this statement, it appears as though I can only use the File Object Store if I enable filesharing through my firewall. Otherwise, the remote subscriber has no way of locating the broker's managed administration objects. Is this correct?

Carl

Carl.Hume at 2007-7-3 0:14:19 >