ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » MQ component in Websphere Application Server

Post new topic  Reply to topic
 MQ component in Websphere Application Server « View previous topic :: View next topic » 
Author Message
whizkid_va
PostPosted: Wed May 11, 2005 5:05 pm    Post subject: MQ component in Websphere Application Server Reply with quote

Newbie

Joined: 11 May 2005
Posts: 3

Hi,
Websphere application server (WAS 5.0) comes with embedded MQ component, has anyone of you made use of it.
In our scenario, we have an application that needs to be deployed on WAS and this application sends messages to MQ server, I am sure that I can make use of MQ component in WAS but before going with it I would like to ensure that I would not be runing into any problems as it is very critical application.

I would really appreciate your help. Thanks
Back to top
View user's profile Send private message
malammik
PostPosted: Wed May 11, 2005 5:08 pm    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA

Before you can know whether you can utilize was 5.0 embedded messaging, you need to answer AT LEAST these 3 questions that come to mind.

Will your queue manager need to talk to other queue managers?
Will clients other than JMS clients need to connect to the queue manager?
What are your availability, reliability requirement?
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex
Back to top
View user's profile Send private message Visit poster's website AIM Address
whizkid_va
PostPosted: Wed May 11, 2005 5:33 pm    Post subject: Reply with quote

Newbie

Joined: 11 May 2005
Posts: 3

Will your queue manager need to talk to other queue managers?
>> No, Message is delivered to MQ server from WAS and there ends the MQ role

Will clients other than JMS clients need to connect to the queue manager?
>> No

What are your availability, reliability requirement?
>> It is moderate, I am mainly concerned with question: WILL I HAVE ANY ADVANTAGES IF INSTALL MQ CLIENT ON TOP OF WAS 5.0 (OR) CAN I LIVE WITH MQ COMPONENT IN WAS

Regards
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed May 11, 2005 5:54 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

whizkid_va wrote:
Will your queue manager need to talk to other queue managers?
>> No, Message is delivered to MQ server from WAS and there ends the MQ role
And what happens then. Does the message stay indefinitely in MQ ?? This is not a valid response...

Quote:
Will clients other than JMS clients need to connect to the queue manager?
>> No

I believe the better question here would be does any client outside WAS need to connect to the queue manager and how do you plan to do it ??

Quote:
What are your availability, reliability requirement?
>> It is moderate, I am mainly concerned with question: WILL I HAVE ANY ADVANTAGES IF INSTALL MQ CLIENT ON TOP OF WAS 5.0 (OR) CAN I LIVE WITH MQ COMPONENT IN WAS

Regards


It really depends on what you need the qmgr for. If it is just for asynchronous decoupling inside WAS -- go for it.
If it is to move stuff from and to WAS you might seriously want to consider a "real" MQ manager. Depending on need for 2 phase commit you will have some choices and $$ to face.

Enjoy
Back to top
View user's profile Send private message Send e-mail
malammik
PostPosted: Wed May 11, 2005 6:07 pm    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA

Bottom line is that if you need messaging for some peripheral was to was messaging, go with embedded messaging. I personally, always recommend clients going with external jms provider such as full blown mq deployment because I most of them grow out of embedded messaging very quickly. Once again, this is my preference, not necessarily a correct way to do it.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex
Back to top
View user's profile Send private message Visit poster's website AIM Address
bower5932
PostPosted: Thu May 12, 2005 6:12 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

Of course, if you are just now getting started on WAS 5.0, you can consider starting with WAS 6.0. It has its own messaging engine (different from WMQ) and an MQLink component to get out of WAS and into WMQ. You'd then need to get the full WMQ product which you may have been doing anyhow.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
whizkid_va
PostPosted: Thu May 12, 2005 6:56 am    Post subject: Reply with quote

Newbie

Joined: 11 May 2005
Posts: 3

Thanks guys for all your replies

Regards
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » MQ component in Websphere Application Server
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.