|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
[Solved]Server switch without client concentrator. |
« View previous topic :: View next topic » |
Author |
Message
|
chintu |
Posted: Tue Mar 11, 2008 6:57 pm Post subject: [Solved]Server switch without client concentrator. |
|
|
 Acolyte
Joined: 27 Dec 2004 Posts: 64
|
Another cluster question:
I have 2 systems in the same group.
Box a: FMC.FMCSYS.FMCGRP.FMCQM
Box b: FMC.FMCSYS1.FMCGRP.FMCQM1.
Both qmgrs are in a cluster and both have full repository.
I am trying to test failover by stoping WF and Qmgr on BoxA and then testing if a user can logon thru webclient or runtime client using just GROUP information. I have created a 4 client configurations on Box A with the following connect names..
1)FMC.DUMMY.FMCGRP.FMCQM & FMC.FMCSYS1.FMCGRP.FMCQM
2)FMC.DUMMY.FMCGRP.FMCQM & FMC.FMCSYS1.FMCGRP.FMCQM1
3)FMC.FMCSYS.FMCGRP.FMCQM & FMC.FMCSYS1.FMCGRP.FMCQM
4)FMC.FMCSYS.FMCGRP.FMCQM & FMC.FMCSYS1.FMCGRP.FMCQM1
I can logon to the runtime clients and webclient of these 4 configuration ...but when I stop FMCSYS and FMCQM, I am not able to logon to any of these configurations. The error I get:FMC00013E Communication error - Failing Action: connect, Reason Code: 2059, Failing Object: FMCQM
fmczccd,fmcautil( -g FMCGRP) do not work for config1 and config2 but work fine for 3 and 4...so client channel table specified in thru fmczutil has been verified.
What am I missing? I see a note in the configuration utility that says that clients using java api connect only to the first connect name. Is this why I am unable to the second system in the same group?
WF 3.6
MQ 6
on WinXP.
Thanks in advance.
Last edited by chintu on Wed Apr 09, 2008 7:56 am; edited 3 times in total |
|
Back to top |
|
 |
chintu |
Posted: Wed Mar 12, 2008 8:38 am Post subject: |
|
|
 Acolyte
Joined: 27 Dec 2004 Posts: 64
|
The configurationID for runtime on boxA is FMC. The second system which is on box B was created with a configID of FMC1. Should both systems have the same configID for runtimes? |
|
Back to top |
|
 |
hos |
Posted: Thu Mar 13, 2008 12:23 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
Hi,
the different configurationIDs on boxA and boxB are not your problem.
The problem is, that MQWF has not implemented a failover function in its logon processing. The first matching connect name is selected for the connect call. In your example the first matching connect name is FMCGRP.FMCQM (for a group logon). If you disable FMCQM there is no way to logon to FMCQM1 because the second connect name is never selected unless you specify a system name (system logon).
If you want to participate from MQ's failover features, you need to setup a concentrator environment (but even in this case MQWF won't be able to recover a broken session on the flight).
Have a look into the Installation Guide for more information about the multi system capabilities of the web client. |
|
Back to top |
|
 |
chintu |
Posted: Mon Mar 17, 2008 5:38 am Post subject: |
|
|
 Acolyte
Joined: 27 Dec 2004 Posts: 64
|
|
Back to top |
|
 |
chintu |
Posted: Thu Mar 20, 2008 1:36 pm Post subject: |
|
|
 Acolyte
Joined: 27 Dec 2004 Posts: 64
|
Has anyone tried setting up a JMS client concentrator inside websphere application server? Is it even possible. From my understanding of a client concentrator setup..I think one can configure the same as a JMS resource.
Currently boxA's WF java client(running on WAS) can only point to WF on boxA(without a client concentrator). I am planning on setting up a 3rd queue manager(inside websphere) and adding it to the qmgrA and qmgrB cluster..and configuring the WASqmgr3 as a client concentrator.
I do not think there is any documentation around doing this in WAS...but if anyone has given this a try or sees any thing wrong with this approach ...please let me know. Any help or suggestions are appreciated. |
|
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
|
|
|
|