| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ High Availability with Oracle RAC on AIX |
« View previous topic :: View next topic » |
| Author |
Message
|
| jsware |
 Posted: Tue Jul 04, 2006 7:52 am Post subject: MQ High Availability with Oracle RAC on AIX |
 |
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
We are looking at using Oracle RAC to provice "continuous availability" for a database server instead of high availability using HACMP on AIX.
Normally we would install MQ on the DB server and have it fail over to the standby node using HACMP.
Multiple application servers could then either access MQ on the DB server using MQ client, or we can setup MQ on the app servers in a cluster with the DB server, having the DB server's MQ act as a gateway qmgr in/out of the cluster and load balance the traffic between the two app servers.
However, now we have Oracle RAC running on "both" DB servers and Oracle handles the failover. This is to eliminate the HACMP configurations/licenses and improve availability (apparently if one of the DB servers fails, the other takes over without DB clients having to reconnect).
Anybody had experience of implementing MQ in an Oracle RAC environment on AIX to provide some kind of "high/continuous availability" without using HACMP?
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 04, 2006 9:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Generally, I prefer to put a queue manager tied to each application server. This queue manager then is part of the same failure unit as the app server. Particularly in a J2EE application server environment, application designers and architects think that they need full two-phase commit everywhere. And generally with MQ you can't do that without a local queue manager.
Generally, I don't put queue managers on database servers. I believe that they should be devoted machines to just serving database work - and everything uses database clients to access them.
If I want to separate/isolate the parts of my applications that access the database from the application servers (which can make sense), then I will put up a separate machine or machines that have queue managers on it, and database clients.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jsware |
| Posted: Wed Jul 12, 2006 7:25 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| jefflowrey wrote: |
| Generally, I prefer to put a queue manager tied to each application server. This queue manager then is part of the same failure unit as the app server. Particularly in a J2EE application server environment, application designers and architects think that they need full two-phase commit everywhere. And generally with MQ you can't do that without a local queue manager. |
We would also put MQ on the application servers (as I mentioned) and have them accessed by a local application. We put MQ on the DB server as a gateway qmgr into an MQ cluster of application servers all performing the same function.
In Oracle RAC, the "RAC" bit as I understand it decides where an Oracle database and also the applications (running on Oracle Application Server) run. It could be any one of a number of hosts in the RAC, or a combination of them.
So my original question remains...
Anybody had experience of running MQ in an Oracle RAC environment?
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| 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
|
|
|
|
