| Author |
Message
|
| ucbus1 |
 Posted: Mon Nov 10, 2003 7:25 am Post subject: Archietecture question |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
We have a workflow configuration for a business application ( "BAP1") using FMCGRP, FMCSYS and FMC as the configuration. Now we wanted to have different business application ( "BAP2") we came up with new configuration FMCGRP1, FMCSYS1 and FMC1. The reason for having two configuration is to isolate them completely as the users/business entirely different.
Now I am also proposing that the queuemanagers queues need to be different. My point is to isolate the applications completely. There are some 4 queue managers that need to be additonally created. However, our MQ Series admin is hesitant to create NEW queue managers based on business criteria. He says that we should make use of any existing queue managers as it impacts performance of AIX box on which queuemanagers are residing. He also says that we can not have more than limited number of queue managers on AIX.
I would like to know pros and cosn for the approach I am suggesting. Could you please throw some light?
Thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Nov 10, 2003 1:12 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If you have a seperate Queue Manager for a seperate workflow server then:
1. If one Queue Manager goes down, then the other is still up and the second workflow server is not affected.
2. No overlapping cluster problems.
3. Samething applies for the webclient boxes.
4. If the system is made HA, then failover of one QMGR does not cause the failover of two workflow servers but just one.
5. Each QueueManager will have to be a XA resource manager ofr just one DB (I am not sure if this is an advantage or not)
6. If clients are directly connecting to the workflow server, you will not have any problem determining which client connection is to which workflow server |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Nov 10, 2003 1:19 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Is it even possible to have the same QM for 2 different groups? I dont think so.
_________________
-Ratan |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Nov 10, 2003 1:39 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I am also not convinced about having different groups on the same box only because the applications are different. I believe it is easier to have only one group for both your applications.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Nov 11, 2003 1:18 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
Is it even possible to have the same QM for 2 different groups? I dont think so.
|
I did a quick test and found that it is not possible.
The second server started working fine but the first one stopped and failed to start.
Also found this
| Code: |
dis clusqmgr(*)
1 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM) CLUSTER(FMCGRP1)
CHANNEL(TO.FMCQM.TCP)
|
Expected a namelist while the cluster is overwritten.
You should do some tests yourself to prove your MQ admin wrong.
Also get some kind of OK from IBM before you do something like this. |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Nov 11, 2003 5:35 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Ratan,
| Quote: |
| I am also not convinced about having different groups on the same box only because the applications are different. I believe it is easier to have only one group for both your applications. |
In that case for any reason we bring down workflow for first business application then would n't it effect the second business application? I was told that was not acceptable. Hence I came up with two different configurations.May there is an alternative. Could you please tell me how I could have achieved this?
Vennela,
Thanks for the input.
I find that we have to have two seperate queue managers for FMC and FMC1 i.e., FMCQM, FMCQM1. Besides these I have 4 more queue managers running for First application ( with FMC) for carrying out some custom work.I would need 3 new queue managers for the Second(New) workflow application. MQ Administartor says I should be using the existing 4 queue managers. The reason told " there is a restriction on MAX. number of queue managers". My idea for having new queuemangers for the custom work is to sepearate the applications entirely. |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Dec 17, 2003 12:25 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
|
| Back to top |
|
|
| koko |
| Posted: Wed Aug 18, 2004 6:21 pm Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Ucubus
Can you please let us know what you did here. We have a similar situation.
_________________
Thanks
Koko |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Aug 19, 2004 4:49 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Koko,
We ended up creating altogether two configurations under different groups. This completely isolated the applications. though I have to face the grudge of our MQ Admin, I need not face any thing from the users of other application.
Better to face one than facing both. Ain't it?  |
|
| Back to top |
|
|
|
|
