| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| File Based JNDI tree |
« View previous topic :: View next topic » |
| Author |
Message
|
| neerajairon |
 Posted: Sat Apr 29, 2006 5:16 am Post subject: File Based JNDI tree |
 |
|
Newbie
Joined: 29 Apr 2006
Posts: 1
Location: India
|
I am doing a proof of concept kind of stuff with MQ. I am not using MQ client but I am using IBM implemented JMS libraries to connect to MQSeries. And i am using file based jndi tree for lookup. And JMSSender which is posting the message to MQ queue is running with in bea weblogic.
In upper case if i am running MQ server and JMSSender with in same physical machine. then i am having no issues. and i am using file based jndi tree and successful.
But the problem is if i am running MQ server on some other machine and JMS sender which is posting messages to MQ on different server. and i am using file based jndi tree for lookup. I am not able to do that.
So my query is, If i can run MQ in different m/c and sender(JMS) on different m/c and i am using file based jndi tree. and i am posting message from JMS to MQ. is this scenerio possible?
Neeraj |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Apr 29, 2006 6:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Here is the deal.
MQ has two types of connections it can make - just like databases - a CLIENT connection and a SERVER connection.
You can use a CLIENT connection from *any* machine, including a machine that has an MQ Server on it.
You can only use a SERVER connectoin from the machine that has the MQ Server AND the queue manager you want to connect to, on that same machine.
So if you want to connect to QMGRA, you have two choices. Use a client connection, and run your code anywhere. Use a server connection and only run your code on the same machine as QMGRA.
Now you're going to decide you should just use a client connection always.
BUT, you can't do XA with MQ using a Client Connection - in most cases.
So if you are trying to do XA (two-phase commit, global units of work, it's all the same thing), you have to use a Server connection and so you have to run your code on the same machine as the qmgr you are connecting to.
The extended transactional client can help avoid this - but not with file based JNDI, I think.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Apr 29, 2006 3:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
The extended transactional client can help avoid this - but not with file based JNDI, I think. |
Why not? it should just be a client connection like any other. I believe the difference in java/JMS is that you need one or more additional jars on the classpath.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Apr 29, 2006 5:51 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I remember someone from IBM commenting in a thread here that the ETC was only good for use within an App Server...
Maybe I remember wrong.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Apr 30, 2006 9:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
I remember someone from IBM commenting in a thread here that the ETC was only good for use within an App Server...
Maybe I remember wrong. |
Probably not but you can use file based JNDI in an appserver (external JMS Provider) although we both would not recommend it for WebSphere Application Server... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
