| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Server inside WebSphere Application Server |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bharat |
 Posted: Wed Apr 28, 2004 12:08 pm Post subject: MQ Server inside WebSphere Application Server |
 |
|
Acolyte
Joined: 14 May 2002
Posts: 61
Location: Reston, VA, USA
|
Hi,
I worked with regular WebSphereMQ Server and know all the concepts. I would like to use the internal MQ Server provided with WebSphereMQ Application Server 5.1. What is the difference between this internal MQ Server and regular MQ Server?
I just need to create a Queue and post messages onto that with in WebSphere Appserver and create Message Driven Beans to pick them and process.
Can anyone explain how this internal MQ Server works?
I saw crtmmqm.exe command in the bin directory which helps to create a Queue Manager, but I didn't see runmqm to run on it for creating Queues.
Thanks,
Bharat |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Apr 28, 2004 12:23 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
The embedded JMS is a stripped down version of the full MQ product. Some of the utilities that you would use to administer full MQ aren't shipped since you are supposed to be using WAS to administer it. When the AppServer starts up, if you have your JMSServer set to started, you'll get your qmgr (and broker) started. You'll see entries for both in your SystemOut.log.
In order to define queues, you use the list box that is under your server's JMS Server component. You put the name in the box and WAS sees to it that the queues are created.
As far as MDBs are concerned, you'll need to define WebSphere JMS resources for your QCF/Q or TCF/Topic. You then create a listener port that points to these, and deploy your MDB against this port.
Hope this helps. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Apr 28, 2004 12:25 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Also, never, never, never use the crtmqm or dltmqm command to create and delete the qmgr that is associated with WAS. There is more to it. There are a couple of scripts (createmq, deletemq) that are supplied that can be used. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Sun May 02, 2004 4:16 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| WSAD 5.1 adds a third option, the 'MQ simulator', this is a pure java JMS implementation with no persistence, remote queuing or clients. It runs in the WAS JVM, and can only be accessed within the WAS JVM. It was desgined to be lightweight for unit testing purposes, and cannot be used within WAS (only available within WSAD test environments). |
|
| 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
|
|
|
|
