| Author |
Message
|
| avish |
 Posted: Thu Apr 17, 2003 9:35 am Post subject: Webshphere MQ & WSAD |
 |
|
Newbie
Joined: 08 Apr 2003
Posts: 2
|
I had MQ server already installed on my workstation and then I installed
WSAD and both are working fine.
In one incident when I tried to install MQ server on a workstation that had
WSAD (Websphere Studio Application Developer) already installed, I got
a different dialog to remove or modify the MQ.
All the mq processes were running and even WSAD had its own queue manager . However I need the MQ explorer on the machine and
having MQ processes is not enough.
Is the order important in installing MQ and WSAD? Is there any way I can
install MQ or MQ explorer on the top of WSAD? |
|
| Back to top |
|
 |
| tlinus2 |
| Posted: Wed Aug 20, 2003 12:07 pm Post subject: mq wsad - install order important |
|
|
Novice
Joined: 20 Aug 2003
Posts: 12
Location: Wash DC
|
Yeah, so wsad 5 comes with an embedded JMS server (per the j2ee spec).
You partly noticed something. The embedded JMS server runs inside wsad. So even when you have a full MQ running, you see that JMS server instantiated; but when wsad server isn't running, the embedded QM shuts down too.
To answer you more specifically, only full MQ gives you the explorer and tools. You can install MQ over the default embedded "mq-lite" jms server. But in the end you will only have one mq running. (With full MQ, you can as many QMs as you like, but with embedded version, wsad/wsas controls the QM.) Order isn't important; it will use the higher version. But also, you can't install a lower version. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Mon Oct 04, 2004 8:25 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
| so we have just installed WAS on a win2k3 machine and now we are going to install websphere 5.3 server. I would basically like to be using the mq queues so correct me if Im wrong but I will need to go in admin console and set up 'mirrors' of the real queue (MQ) and the 'ghost' queue(JMS WAS)? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 04, 2004 8:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you want to use "real" MQ with WAS, then you do not need to set up a mirror between the Embedded JMS Provider in WAS and the "real" MQ.
You merely need to inform WAS of the location of MQSeries, and then use the WebSphere MQ JMS Provider to create your JMS objects.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Tue Oct 05, 2004 10:00 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
Jeff,
which redbook should I use (WAS 5.1)?
I am installing the WMQ 5.3 server on the windows box with WAS5.1 already installed and being new I need some docs on 'How' to set up WAS to see my WMQ queues etc through the admin console and ensure my MQ mgr runs at startup etc.
is there anything else I need to do when installing the WMQ etc? I am installing the JMS provider while also.
thank you |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 05, 2004 10:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm sure there are a number of different redbooks that will tell you to set MQ_INSTALL_ROOT in the WAS variables.
There's really not much after that. Try it and see what happens.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Oct 05, 2004 10:05 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| bamboozled_by_MQ wrote: |
| and being new I need some docs on 'How' to set up WAS to see my WMQ queues etc through the admin console |
If I understand what you are asking, you don't see your WMQ queues through the admin console. You define your queues using WMQ utilities (ie, runmqsc). You use the admin console to define a WebSphere MQ JMS resource so that it can be looked up via JNDI by your program. When you define the WebSphere MQ JMS resource, you have to specify the name of the underlying WMQ queue.
As far as how/what to install, this is the approach that I took:
- install WMQ 5.3
- install WMQ 5.3 fp 7
- install WAS 5.1 and select embedded JMS server and client
This gives me the ability to use WMQ as the full-product. It also allows me to treat WMQ as embedded when running from WAS. If you look at the mq_install.log in this scenario, you'll see that it recognizes that you have the WMQ code installed and will only install the embedded broker.
Hope this helps and doesn't confuse. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Tue Oct 05, 2004 11:16 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
ouch.
the person told me they finised installing WAS and did not use the embedded message, in the script it was set to FALSE.
so if now go install WMQ5.3 I will have problems even though I want to use the full product of WMQ as my jms provider etv?
I was told by someone else not use embedded messaging becuase we want to use the full WMQ...
***also,
if I am installing WMQ 5.3 server I don't need to install MA88 classes do I?
thanks |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue Oct 05, 2004 12:13 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| bamboozled_by_MQ wrote: |
| ouch. |
I wouldn't go quite this far. I wanted my machine setup so that I could use it as either a full WMQ machine or treat it as embedded. Your scenario sounds like you need a full WMQ machine. If you installed WAS without embedded JMS, you need to simply install WMQ and you'll be good to go. Make sure that you do a custom install so that you can select the java/jms component. These are not part of the typical install (and they replace the old MA88).
So, I believe that you are in good shape. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 05, 2004 12:27 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The difference between embedded JMS and WebSphere MQ JMS is transparent to the applications (assuming your applications use JNDI)
The difference to the JNDI administrator is not, quite. You have to use the screens for the WebSphere MQ JMS Provider, instead of the screens for the regular JMS Provider to create your JMS Objects.
And you have to set MQ_INSTALL_ROOT, and restart your WAS instance.
That's it, really!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Tue Oct 05, 2004 12:57 pm Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
you guys are awesome!
I'll let you know how it goes |
|
| Back to top |
|
|
|
|
