| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Application Architecture |
« View previous topic :: View next topic » |
| Author |
Message
|
| jason_e |
 Posted: Tue May 11, 2004 9:54 am Post subject: Application Architecture |
 |
|
Apprentice
Joined: 19 Aug 2003
Posts: 33
|
I would like a web application to put a message onto a WebSphere MQ queue. The web server and the MQ server are physically different boxes.
The messages need to be put on the queue (remote) so that they can be sent to an external partner.
What is the best practice and recommended architecture for setup. I'm guessing that it would probably be best if the MQ server is on the same box as the web server? (eliminate the network as a single point of failure)
The MQ client would definitely need to be installed on the web server if a mq server is not local. Do people actually do this in practice and what is the overall opinion?
How about hosting a web service on the MQ box that can be used to put messages onto any queue specified when invoking the service?
Is it considered bad to have a web server running on the MQ server?
(I would need to web server to host a web service on he MQ box?)
Any other ways of doing this? What is your option of hosting a generic web service on the MQ box to put messages onto a queue a specified? This would probably make it easier for future application as well since they can now just use the web service and not worry about any MQ detail?
Please let me have you opinions.. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 11, 2004 12:10 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MQSeries provides robust, mangeable, asynchronous, stateful, transactional communications.
Take advantage of it, don't abstract that power behind a light-weight, synchronous, stateless protocal.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jason_e |
| Posted: Wed May 12, 2004 4:53 am Post subject: |
|
|
Apprentice
Joined: 19 Aug 2003
Posts: 33
|
Point taken. If my web application needs to put messages onto a queue is it better to have the MQ server on the sample box as the web application for is it acceptable to use the MQ client on the web box for communication with the MQ server?
How is this usually done? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 12, 2004 5:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's usually done as cheaply as possible. 
Generally, if you aren't doing two-phase commit, webservers will use clients rather than servers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed May 12, 2004 8:57 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Here is a quick snapshot of what we have setup at a client site:
- WebLogic v7.x - installed on Box A
- MQ Client 5.3 & CSD03 - installed on Box A
- MQ Transactional Client - installed on Box A
- MQ Server 5.3 - CSD03 - installed on Box B
- Oracle 8 - installed on Box C
The web apps are wrritten in Java and use JMS. Probably 30% of them do 2-phase commits between MQ (using XAQCF) & Oracle. We have been running this setup since last fall and it is working well.
As soon as we get a fix for Netegrity, we will migrate more applications to WebLogic v8.1 .
Hope that helps.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
