Hi Jim,
If you're running a GlassFish cluster, something like that should be
possible using node-specific environment variables. I haven't tried that
myself with JMS yet, but if you're running into issues with that, I can try
to do so later this week.
BTW, I'm moving this conversation to the OpenESB users mailing list. It has
a wider audience, and I'm trying to retire the JMSJCA mailing list except
for very JMSJCA specific conversations.
HTH, Frank
_____
From: James.Mittler_at_bmwnaext.com [mailto:James.Mittler_at_bmwnaext.com]
Sent: Sunday, January 18, 2009 19:34
To: users_at_jmsjca.dev.java.net
Subject: server specific URLs in a clustered/load balanced environment
Hi,
I'm trying to simplify our deployment process with JCAPS/JMSJCA and I am
hoping the experts will weigh in.
We have multiple servers in our load balanced production environment, each
running JCAPS and each has its own instance of Websphere MQ server as our
primary JMS provider.
Ideally we would create a single deployment to push to each JCAPS server,
but unfortunately the queue manager name is different on each server and
I've had to create separate deployments so that I can specify a unique
QueueManager property in the wmq: connection URL.
Is there a way I can perform a variable substitution or use a system
property to assign a unique queue manager name to each server?
I explored putting the values into JNDI, however because the JCAPS servers
are all part of the same domain, there is no way that I could see to have a
unique JNDI entry by server using a common JNDI name.
Any suggestions would be most appreciated!
Thanks!
Jim
BMW EAI and Web Services