| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere & client transport ConnectionFactory |
« View previous topic :: View next topic » |
| Author |
Message
|
| kergadic |
 Posted: Thu Jan 25, 2007 10:45 am Post subject: Websphere & client transport ConnectionFactory |
 |
|
Newbie
Joined: 25 Jan 2007
Posts: 2
|
Hi,
In websphere administration console, you can define the default JMS provider (specific, embedded or MQ).
in MQ provider configuration (Resources > JMS MQ provider), you can define a connectionfactory with client tranport (calling a remote MQ server) : in this case, the local MQ server is not part of the connectionfactory.
Am I right ? If yes, why the connection factory configuration is defined in the default provider configuration : isn't it independent for a client transport (i'm not talking of the binding transport ) ?
thank you & bye
Greg |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jan 25, 2007 3:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You have to differentiate in WAS 6 the java JMS Engine which lives on the SI BUS (WAS6) and the WebSphere MQ JMS implementation...
They are 2 completely different things.
The preferred Data Store for the JMS Engine is a DB. Websphere MQ uses a file system....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kergadic |
| Posted: Fri Jan 26, 2007 1:40 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2007
Posts: 2
|
in fact I'm running on Websphere 5.1.
My question is in fact:
I have a Websphere AS on Machine 1
I have a Websphere MQ on Machine 2
Where do I bind my connectionfactory in WAS administration console ? In Resources > MQ JMS provider (there is no local provider local) ?
I'm new in MQ, so sorry if my questions are weird  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 26, 2007 2:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The connection factory definition needs to be bound using the correct provider.
This is because the connection factory definition needs provider specific information. In the case of MQ, it can either be a queue mananger name or a hostname and channel and port.
Inside your code, and from the point of view of your code, the connection factory OBJECT is completely provider neutral, as nothing in your code needs to know any of the provider specific information.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
