| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WSAD5 + JMS <--> Remote MQ5.30.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| nyey |
 Posted: Fri Apr 25, 2003 7:15 am Post subject: WSAD5 + JMS <--> Remote MQ5.30.1 |
 |
|
Acolyte
Joined: 13 Mar 2003
Posts: 57
|
Hi. I have made a JMS/Messae driven bean working on my local machine with WSAD 5 and WSAD5's WAS 5 engine. JMS with the test engine, then talking to MQ 5.3 locally.
I need to set up development machine by moving the MQ to another machine so that all developer can share. I don't see any where I can config JMS so that it can communicate with remote MQManager and its Qs.
Any body can help here?
nyey |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Apr 25, 2003 9:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I'm not sure that I understand 100% of what you are trying to do. However, it sounds to me like you have two options:
1) Using WebSphere MQ as the JMS provider, you would create a QCF that would use a client connection (not bindings). You would then specify the channel, hostname, and port that the connection would use.
2) Using remote messaging, you would create a Q that would map to a QREMOTE. This QREMOTE would then map to the qmgr on the other box. This will work for puts, but not for gets. |
|
| Back to top |
|
|
| nyey |
| Posted: Sat Apr 26, 2003 10:16 am Post subject: |
|
|
Acolyte
Joined: 13 Mar 2003
Posts: 57
|
I prefer to use the Option 1. How can I put all the host name, port... info into WSAD 5 Test Environment?
Any details... |
|
| Back to top |
|
|
| tlinus2 |
| Posted: Wed Aug 20, 2003 1:42 pm Post subject: Option 1 not viable in testing (WSAD) |
|
|
Novice
Joined: 20 Aug 2003
Posts: 12
Location: Wash DC
|
When using WSAD, even with a full MQ, if you set a custom parameters, WSAD will create them internally on the MQ. The destinations will go into effect when you rebind them in deployment to the real destinations. In testing, they're created internally (on MQ but you'll see them as something like "WAS_nodename_server1" for the QM).
That was my experience with WSAD and MQ on the same machine. So far, if I wanted to go to another machine, I have to use a direct connect to the Qmgr of another machine.
But looking to use WSAS 5.0 and MQ 5.3 on different machines (using qcf, not direct connect), similar to you.
Linus |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Aug 21, 2003 8:09 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I just saw the phrase "direct connect" in this thread. I'd like to clarify that when using a QCF, you have two options - BINDING and CLIENT. These are the regular MQ bindings/client connections.
However, when you create a TCF, you have three options - BINDING, CLIENT, DIRECT. Binding/client are the regular MQ connections. The DIRECT relates to the WebSphere MQ Event Brokers direct ip connection for publish/subscribe. The embedded pub/sub that ships with WSAD and WAS (WSAS?) is a stripped down version of WMQ EB and allows the direct connection. It is used for performance/scalability and doesn't allow durable subscribers.
Also, the embedded jms that ships with WSAD will use a qmgr that is called WAS_localhost_server1.
I hope this clarifies rather than confuses..... |
|
| 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
|
|
|
|
