This concept does follow the Idea that each user owns a connection. When you are using Servlet you might want that multiple sessions belonging to different users share the same connection.
Do we really need to program a custom solution fo such a scenario?
Regards
Silvano
I'd much rather maintain a small list of application IDs that have authority to MQ than a large list of user IDs that have authority to MQ. _________________ I am *not* the model of the modern major general.
We are running the WAS under a specific ID.
We use an alias to set this ID as container and object alternate authentication. (JAAS) Connecting in bindings mode. This userid has the necessary access to the queues on the qmgr.
Works like a charm... But all users on the Web use the same MQ User Id...
This is not a problem for us...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum