Hi,

I am using WAS 5.1 as a JNDI name server for a client app. The client commun
icates with other system components through Websphere MQ, and it retrieves t
he administerd components through the WAS 5.1 JNDI name server.

To make that possible, I registered the connection factory and several queue
s in the Websphere MQ JMS provider panel, during which I also specified the 
JNDI name. However, when the client does a lookup of these components, they 
can not be found. The excep
tion that is thrown states that the first component of the jndi name is not 
found.

I also bound several strings in the environment > Naming > Name space bindin
gs panel, and these bindings *can* be found. So I assume the name server is 
properly set up.

All bindings are in the server context. I used dumpnamespace, and found that
 strings can be found, but the MQ objects do not appear in the dump.

I did a similar set up in WAS 5.0, not so long ago, and this worked fine fro
m the start.

I would appreciate any information and tips to help me get on with this.

Thanks in advance,
Huub

[ Post a follow-up to this message ]

Hi,

I solved the problem: the configuration of my WAS installation was not corre
ct. The WebSphere variable MQ_INSTALL_ROOT should point to the installation 
directory of MQ. When it does not (and in my installation it indeed did not)
, no MQ administered object
s can be created, and hence no name bindings can be added to the naming prov
ider.

Unfortunately, WAS is not very specific about this, and attempts to create m
anaged objects without a known MQ are not clearly indicated. This took me ho
urs...

Huub

[ Post a follow-up to this message ]