| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WAS EE 5.x built in JMS provider Vs. WMQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| sumeet |
 Posted: Sun Jul 25, 2004 10:50 pm Post subject: WAS EE 5.x built in JMS provider Vs. WMQ |
 |
|
Novice
Joined: 16 Mar 2004
Posts: 16
|
Dear all,
We are using WAS 5.x EE for our project and it would involve messaging. We are trying to find out the differences between the embedded messaging support that comes with WAS and WMQ. Are the features supported different? Any advantages / disadvantages of one over the other.
Any inputs / pointers to any documentation would be highly appreciated.
Thanks & Regards,
S |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jul 26, 2004 9:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The was documentation specifies that any communication outside the scope of the embedded mq (node/../server) is not possible.
This will be your biggest hurdle. I believe as well (but could be wrong here) that messages will not be persistent. Once you shutdown was you might loose all messages in the was queues.
Enjoy  |
|
| Back to top |
|
|
| kman |
| Posted: Mon Jul 26, 2004 11:26 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Sumeet,
As I recollect, WAS EE comes packaged with WMQ. There is no added cost there. I would recommend using WMQ then as the provider.
In the meantime, the difference between the two, for the major parts are;
1. Embedded Messaging (EMPS) is intended for development not prod.
2. EMPS cannot communicate outside of cell.
3. EMPS is a stripped down version of WMQ. No channelling, toolings.
4. EMPS has a broker component, installed in directory WebSphere MQ/WEMPS/
5. WMQ does not have the broker component, so must install separate MA0C supportpac (can't remember exactly this), or WBIMB.
6. The broker component is used for pub/sub work.
7. EMPS does not require to define the queues to use. WAS Admin Console definition would create this.
8. WMQ requires manual definition of this queues using the runmqsc or WMQ Explorer tool.
etc., etc.,
 |
|
| Back to top |
|
|
| OmPat |
| Posted: Tue Jul 27, 2004 6:02 am Post subject: |
|
|
Apprentice
Joined: 20 Jul 2004
Posts: 33
Location: Charlotte
|
sumeet,
If you doin development you could use Embedded MQ but I would recommend using WMQ instead of Embedded MQ in Websphere because of the Obvious Production benefits pointed out in the earlier post.
Njoy...
_________________
IBM Certified WMQ V5.3 System Administrator
IBM Certified WMQ V5.3 Solutions Designer
Brainbench Certified MQ Expert
IBM Certified WMQI V2.1 Solutions Expert
IBM Certified WMQI V2.1 Specialist |
|
| Back to top |
|
|
| Javax |
| Posted: Thu Apr 27, 2006 5:27 am Post subject: |
|
|
Newbie
Joined: 13 Dec 2004
Posts: 5
|
| but what are the steps to install them, first de WAS or the MQ, now i am having a problem, i installed first the WAS, then tried to uninstall the WAS version of MQ but it have a reference with WEPMS if I uninstall it, now i'm able to install MQ but the WAS need WEPMS components |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Apr 27, 2006 6:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I used to install MQ first and then WAS. That will not give me any problems.
I haven't figured out other ways of doing though |
|
| Back to top |
|
|
| kman |
| Posted: Thu Apr 27, 2006 4:30 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
You can install either one first.
Steps to install MQ first. Well as Vennela found out, it was really easy and straight forward.
Steps to install WAS first. You can't uninstall EMPS, as that is needed to connect to WMQ. So go ahead and install WMQ on top of what is already there from WAS. The infocenter has some discussion on co-existence. One thing to note is the environment variable, as set in the Admin Console, pointing to where WMQ is installed. Obviously, it will install in its own location (not WEMPS).
WAS require at least Embedded Messaging Client to be installed, in order to use WMQ. The client will create the connection to the MQ Server. Point to note, that does not mean connection is CLIENT in your QCF definition. That CLIENT definition is for connection to remote MQ Server on other platform, if not installed on the same machine.
Have fun... |
|
| 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
|
|
|
|
