MQSeries.net :: View topic

hagai2003 · Posted: Sun Jun 15, 2003 5:53 am Post subject: JNDI and JMS

Hi,
i have a few questions regarding using JMS in WSAD.
As i understand, in order to define an object - like a WASQueue - i need to make 2 definitions :

1) after defining the queue in MQ (on PC) for example, i use jmsadmin in order to write a reference to the object to the jndi server (inside wsad).

2) there is the WASQueue definition inside WSAD -> server -> JMS
where i have some (i think) server control parameter like Persistence, Priority , Expiry and so on ... see the following like to see my screen (sorry, no attachments on this forum)

http://community.webshots.com/user/hagai2003

it doesn't have some parameters like queue name or qmanager name so why is this definition nessecery ?

the jndi name on both these places should be identical, right ?
is this the normal procedure ? defining the object at these 2 places ?
the first one maps the reall MQ queue to some JNDI virtual name,
and the second step ... just defines that JNDI name inside WSAD so programs can access it ?
if so - why isn't the first definition enough ?
just add the object to JNDI and access it directly ? why should i define it inside the wsad also ?

when i'm using the internal JMS server on the other hand, i noticed that i only need to make the second definition, it's like the internal queue is mapped to the JNDI name : /jms/Qname automatically, and i only make the second definition (the one like the screen snapshot i attached earlier) is it true ? that internal JMS server objects are always JNDI named :
/jms/..object name.. ??

thanks,
Hagai.

i'm using 2 scenarios :
1) using the internal JMS provider :
i noticed that when i use the internal JMS i only define