How can I connect to JMS Queue in WebSphere App Server v6? If I enable the g
lobal security on the app server and secure the bus and added the user group
 to connect to bus as well as JMS destination, then I have to pass the user 
id and password in the JMS
connection code.
Is there any way by which I do not have to pass the user id and password to 
connect the destination from Application Client?

Thanks, Bill

[ Post a follow-up to this message ]

Hi Bill,

You don't say where you are getting your connection factory from. The
current recommended solution would be to define the connection factory
within the EAR file itself using the Application Client Resource
Configuration Tool (clientConfig). See:

http://publib.boulder.ibm.com/infoc...ucli_tjmcr.html

Regards,
David

[ Post a follow-up to this message ]

> Hi Bill,
>
> You don't say where you are getting your connection
> factory from. The
> current recommended solution would be to define the
> connection factory
> within the EAR file itself using the Application
> Client Resource
> Configuration Tool (clientConfig). See:
>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/
> topic/com.ibm.websphere.base.doc/info/aes/ae/ucli_tjmc
> r.html
>
> Regards,
> David

Hi David:

Thanks a lot for your reply. Actually I am getting the connection factory fr
om application server. I have defined the ResourceRef for connection factory
 and queue and under WebSphere Binding panel given the name of JNDI name on 
the server.
For ConnectionFactory ResourceRef, I have provided the Authentication Alias 
for connection. This alias is defined in the server under J2C authentication
 data entries.

In the production environment we do no use clientConfig.sh to configure the 
Application Client EAR file as we do not know the user's password in this en
vironment. To over come this problem, I am using properties file and keep th
e user id and password ther
e. In the prod environment administrator supplies the password and we access
 it programtically.

Is it the right soultion? I am sure that this might not be best practice.
Thanks a lot once again.

Regards,
Bill

[ Post a follow-up to this message ]

I'll put it this way: given your circumstances, I don't know of a better
solution.

Regards,
David

[ Post a follow-up to this message ]