| Author |
Message
|
| amittalekar |
 Posted: Thu Aug 22, 2002 6:10 am Post subject: channel table for Client Concentrator |
 |
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
I want to set up a client concentrator which will connect to the two workflow server's which are having their q manager's in the cluster.
For the client concentrator to connect to the two server's, whose (either of the workflow servers) channel defination table should I use?...Or can use the the channel table of the workflow server whose Q manager is selected as the first Q manager in the cluster?
Waiting for ur responses
-- Amit |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Aug 22, 2002 9:44 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You don't use the channel definition table for the client concentrator. Client concentrator is a client with Queue Manager. When the client concentrator is configured, the config utility asks the information of the first queue manager in the cluster. Then, point the first queue manager (or the additional repository QM if you have defined one) info.
Channel definition table comes into picture when you want your Workflow clients connect to the Workflow servers using an MQ Client.
Now if you want your clients to talk to workflow servers via client concentrator, you will have to copy the channel definition table of the CLIENT CONCENTRATOR.
------
Refer: Installation Guide 3.3.2 : Appendix I : Figure 36
Venny |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Sep 24, 2002 7:02 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
You must have channel defination table of the "workflow server which has its QManager as the first Q manager in the cluster" , on the client concentrator machine.
If this table is not used, still cofiguration will be done successfully. But client concentrator wont find which workflow server to connect.
And all workflow clients ,if there any, will use the channel definition table of the CLIENT CONCENTRATOR. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Sep 24, 2002 8:23 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
You must have channel defination table of the "workflow server which has its QManager as the first Q manager in the cluster" , on the client concentrator machine.
|
I dont see any reason to use a channel definition table. All you need is to install a workflow client on the client concentration machine and configure it to be the part of the same cluster ( FMCGRP).
| Quote: |
If this table is not used, still cofiguration will be done successfully. But client concentrator wont find which workflow server to connect.
|
The client concentrator would use a round robin fashion of submitting the requests to all the workflow servers in the cluster.
If have experienced problems without using channel tables, please share it with us.
-Laze |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Sep 24, 2002 2:41 pm Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
I have tried client concentrator set with both the options i.e. with channel defination table and without it. In both the cases configuration was done successfully.
But when I tasted the configuration using fmcautil utility, only the configuration with channel defination table was able to connect to workflow server.
Anyone has tried CONCENTRATOR setup without client channel defination? please share your views. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Sep 24, 2002 7:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I think Your configuration was wrong, because your fmcautil should work.
Let us know how you tried to configure and we can see if any thing is wrong.
-laze |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Sep 24, 2002 9:20 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
That's true. Your admin utility should work either way - whether you have the channel definition table copied or not. So there's something fishy in your configuration.
I don't have a client concentrator but I have a client with QueueManager and I didn't copy the channel definition table. I will test the client concentrator tomorrow and will post whether "copying channel definition table" is a must.
---
Venny |
|
| Back to top |
|
|
| amittalekar |
| Posted: Wed Sep 25, 2002 6:52 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
I have done the exact steps as given in the documentation for client concentrator. I have tried twice. But it does't work without channel defination table.
I have workflow 3.3.0. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 25, 2002 8:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I did this today
1. Workflow server on one box
2. Workflow client with Queue Manager on another box (CLIENT CONCENTRATOR).
3. Fat Client on another box.
I did NOT copy channel table from Workflow server to the client concentrator box.
I copied channel table from CLIENT CONCENTRATOR to the machine where I was unning fat client and I was able to connect to the server and work on work items.
I am having Workflow 3.3.2
Maybe for 3.3 you may have to copy the channel tab but for 3.3.2 you can just do it as per the documentation.
---
Venny |
|
| Back to top |
|
|
| leongor |
| Posted: Sun Sep 29, 2002 4:23 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
First of all, you don't need to copy channel table from WF Server Qmgr
to Client Concentrator Qmgr.
Let's separate the problem to parts.
When you create Client Concentrator configuration
these step are produced :
1. Client Concentrator Qmgr is created and added to the main MQ cluster.
( this is the reason why you don't need WF server's channel table here )
2. All your WF clients need the Client Concentrator Qmgr channel table
instead of the WF server's one.
Possible problems :
1. Before you configure check if your PATH includes
<WF Root>\BIN\MQServer
and not
<WF Root>\BIN\MQClient
2. After configuration check if your Client Concentrator Qmgr can see
the main one in the cluster ( all the shared queues ),
otherwise WF won't be able to connect.
It can happen for example if you work with hostnames, but not all
machines in your MQ cluster can use it.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Oct 01, 2002 9:52 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
Hi
I have installed workflow 3.3.2 and tasted the same CONCENTRATOR configuration. It is working on this version without channel defination table.
The same configuration is not working on workflow 3.3.0 SP3. It may work with higher Service Packs, I have not tried that.
Thanks everyone for your responses... |
|
| Back to top |
|
|
|
|
