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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Cluster Configuration

Post new topic  Reply to topic
 Cluster Configuration « View previous topic :: View next topic » 
Author Message
koko
PostPosted: Mon Sep 12, 2005 7:37 am    Post subject: Cluster Configuration Reply with quote

Master

Joined: 26 Sep 2003
Posts: 206

Hi,

I would like to know whats happening here with my set up.

Config Id - FMC - FMCQM, FMCSYS, FMCGRP ( on AIX )
Config Id - FMCWAS - FMCQMWAS, FMCSYS, FMCGRP ( on same box - Client with QM )

Now I added

Config Id - FMCNEW - FMCQMNEW, FMCSYS1, FMCGRP ( on same box )

Once I defined this, the Webclient config FMCWAS stopped working. I was getting a time out error. I figured out that even though FMCQM and WF were running (FMCSYS), it was not connecting to the WF.

Once I started WF on FMCNEW configuration (FMCSYS1), webclient started working fine.

I guess this means that Webclient started connecting to FMCSYS1 rather than FMCSYS.

Can some one explain me why this happened? Does this mean that I need to have both the QManagers FMCQM and FMCQMNEW ( ofcourse apart from FMCWAS) to have my webclient running??
_________________
Thanks

Koko
Back to top
View user's profile Send private message
Ratan
PostPosted: Tue Sep 13, 2005 11:55 am    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

I saw this behavior before.

If one of the WF Systems is down, you have to take the QM also down for webclient to connect to the running system.

This is because Webclient does not just do a Login request. It does a login followed by Query lists. So if one of your WF Systems (say SYS1) is down, WebClient Login request will be succesfull (if it goes to SYS) and query list will fail, because it will go to SYS1 (Standard MQ round robin for load balancing in a cluster). From WebClient UI you will get a time out because you did not get the response for query lists.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
koko
PostPosted: Wed Sep 14, 2005 10:57 am    Post subject: Reply with quote

Master

Joined: 26 Sep 2003
Posts: 206

Thanks Ratan for trying to reply.

I tried shutting off both WF and the QM on the new system. But still the WebClient did not go to Default system. It was still getting timed out.

I did the same set up on another environment and found that there is no such problem there.

your comment regarding RoundRobin brings something else into my concern.

The reason we added another system is to run *only* cleanup and scheduling servers on it NOT the execution servers on the new system. In other words I dont want any sort of load balancing or anything here between two systems. I want all my workflow processing on FMCSYS and only scheluder, cleanup activities on the FMCSYS1.

Can the experts jump in and their valued expertise please.....
_________________
Thanks

Koko
Back to top
View user's profile Send private message
Ratan
PostPosted: Thu Sep 15, 2005 9:32 am    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

If you do not want to process anything on FMCSYS1 then I think you should put disable the EXEXMLINPUTQ in that QM.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
karthik
PostPosted: Thu Sep 15, 2005 9:56 pm    Post subject: Reply with quote

Centurion

Joined: 17 Oct 2003
Posts: 114

Hi Koko,

Based on ratan's reply .. i have tested the following scenario actually with RunTime client rather than the WebClient.

So, when i created the new system to the system group , i went on to add the connect names of the primary system to the new configuration i have made.

Then i stopped my primary system , my primary Queue manager , and tried to logon to the client for the secondary system.
Here the only difference is , when i try to login is, i have to specify the system group and the system i want to logon to.

As ratan said , everything works fine for me here. I can't tell what you are missing in your environment. And i am positive if you create a webclient with the connect names for both the systems , it should work for you too. ( you might check the system, system group names when logging in).

So, i would think that MQ Workflow is working as designed. And experimenting to run cleanup server and scheduling server on other system might be something good you can try and let us know. We wanted to experiment that here on our MQ Workflow environment also

Thanks
Karthik
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 » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Cluster Configuration
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.