| Author |
Message
|
| ucbus1 |
 Posted: Fri May 23, 2003 7:21 am Post subject: Questions on FAT cleint |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am trying to understand how fat cleint need to be configured. I have the following questions.
1.
If my machine( say NT01) has workflow server and client both installed. I have another machine (say NT02)on which I have only workflow client only and I could configure FAT cleint to monitor transactions my development machine say "node01".
Now, I want to configure FAT client on the machine NT01 which has both server and client to cleint to monitor transactions my development machine "node01" the same way it is on NT02
Is it possible?
2. When I have tried to configure FAT client using "configuration utility" the NT01 which has server and cleint installed, the options I received are quite different from what I had on NT02 which has cleint only.
In both cases I have selected "cleint" check box
For example, when I have entered configuration id , it asked whether it shoud use the "local queue manager" As I want to connect to node01, I have clcked "NO". Then I got two different tabs on the menu "Queue manager" and "cluster" which I have not received while configuring NT02 that has only workflow client.
Could somebody guide me how I can configure FATCLEINT on NT01 that has both client and server installed.
I was told that I could not install FAT client if I have both server and client installed on my machine. If it is not true, I appreciated if somebody can help me in configuring it. Details are very much welcome
Thanks |
|
| Back to top |
|
 |
| Ratan |
| Posted: Fri May 23, 2003 7:30 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
From your post I am assuming the following:
1) you want the client installed on NT01 and NT02 to connect to Node01.
2) you were able to do this from NT02
3) NT02 has only a mqclient installed.
4) NT01 has an mqserver installed and also workflow server.
you have to configure your NT01 as client with QM, as it uses MQServer variable. this should solve your problems.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Fri May 23, 2003 7:35 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I think I sure can answer your question. But can you edit your post and make some things clear like when you say client say whether it is an MQ client or workflow client. The same applies for server, whether its a MQ server(QMGR) or workflow server.
If you have both MQ Client and MQ Server on a box and if you want to use the client libraries for MQ workflow, you need to change the PATH. There are a few posts that dealt with the subject before so a search would help. This is one
http://www.mqseries.net/phpBB2/viewtopic.php?t=8345&highlight=client+path |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Fri May 23, 2003 7:41 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| Quote: |
you have to configure your NT01 as client with QM, as it uses MQServer variable. this should solve your problems.
|
Could you please let me know how I can do this?
Also when I mentioned server and client on NT01. I mean the following
server, runtime databse utilities,build time,client and java cobra agent that are displayed on Configuration utility window. the server and client are related to workflow. ( Are they same as mqclient and mqserver? or are they related to executin server,admin server,cleanup servers?)
Thanks |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri May 23, 2003 8:27 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
As you said you have workflow server on NT01, I am assuming you have an MQServer installed. What I am not sure is if you can change your Path variable to MQClient and still be able to run MQWorkflow Server. You can use the MQServer and configure a new client, javaAgent. This should be able to create a new QM on NT01 and use it. I am not sure though, Venny is the GURU of this stuff.
_________________
-Ratan |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Fri May 23, 2003 11:16 am Post subject: Questions on FAT cleint |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi,
Changing the path comes in to play when one system having server & client and wants to connect to another server as client. This is because while configuring client it checks for local queue manager.
In the above scenario, as per my assumption he is creating the client configuration on the server in the later stage. He can use the same configuration utility and need to connect to the QM to which server is connected.
Hope this should work.
Mahesh
IBM Certified solution expert - MQWorkflow |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri May 23, 2003 12:58 pm Post subject: Re: Questions on FAT cleint |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| MaheshPN wrote: |
Hi,
In the above scenario, as per my assumption he is creating the client configuration on the server in the later stage. He can use the same configuration utility and need to connect to the QM to which server is connected.
|
what do you mean by same config Utility?? can you explain a bit more, it is too confusing to me.
_________________
-Ratan |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Jun 11, 2003 11:45 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Venny,
Could you please let me know what need to be done. The discussion was bit confusing to me. I was talking baout "workflow cleint" and "workflow server only".... Not about MQ Client and MQ Server.
Could you please help |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 11, 2003 11:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
ucbus:
BoxA:
MQServer
MQWF Server
You can install MQWF Client straight away
BoxB
MQServer
MQWF Client
You can install client and create a configuration so that this client can talk to the MQWF Server on BoxA but you will have to add the QMGR on this box to the MQWF CLUSTER on BoxA.
BoxC
MQClient
MQWFClient
You can install client and create a configuration so that this client can talk to the MQWF Server on BoxA but you will have to copy the channel definition table from BoxA and put it on this box.
If you run fmczccd on either BoxB it would say it is using MQServer API
If you run fmczccd on either BoxC it would say it is using MQClient API
Hope this clears things for you. If not post them
-------
Venny |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Jun 11, 2003 12:40 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| Quote: |
If my machine( say NT01) has workflow server and client both installed. I have another machine (say NT02)on which I have only workflow client only and I could configure FAT cleint to monitor transactions my development machine say "node01".
|
I think in my case NT02 falls into category MQCleint,MQWFClient. Because I had to copy the chaltab file from "node01" to make it work
I ran command "fmczccd" on NT01 and I got reply saying that it has server API. but I do have runtime installed and all the workflow servers installed and have a working stand alone configuration. Henc I think my NT01 is what you mentaiond BoxA.
Now you have mentioned that it was straight to get it done for type "boxa"
When I used "fmczutil"
I got a message saying "do you want to use queuemangeer that exists locally. For this I mentiond "NO" as I am trying to access remote aix node "node01" . I have selected the "check box" client. Then I got the following tabs on the GUI:
GENERAL, QUEUE MANGER,CLUSTER, CLIENT CONNECTIONS,CLIENT
Now on queuemanger tab what do I have to give. Do I give my remote machine queuemanger and port number. Some time back when I tried to configure this way it messed up some configurations on remote machine and I was admonished for that. hence I have followed the method as you mentioned in "typeC" way of accessing. however now I would liek to try again. Could you please guide me thru next steps??
Thanks |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 11, 2003 1:12 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| ucbus wrote: |
Now you have mentioned that it was straight to get it done for type "boxa"
When I used "fmczutil"
I got a message saying "do you want to use queuemangeer that exists locally. For this I mentiond "NO" as I am trying to access remote aix node "node01" . I have selected the "check box" client. Then I got the following tabs on the GUI:
|
I though you would have one configuration with both server and client. I shouldn't have jumped to the conclusion.
Now on NT01 box:
Create a new configuration if you select clien, it will ask you whether to use the already running QMGR or to create a new one. I always tell it to create a new one.
When you do that, it will create a new one, but then it will ask for some more information which includes
1. QUEUE MANGER: The name of the new QMGR and the first qmgr name (this is the server QMGR), port and host name etc (of the SERVER QMGR again)
2. Cluster (CLUSTER name of the WF Server QMGR) etc
If you still feel my instructions are not clear I can suggest you another easier way.
In the installation guide, see the client concentrator setup section. A client concentrator is nothing but a client with QMGR, and that is what you are trying to do.
But it should be fairly simple.
If you have a configuration
FMC
FMCGRP
FMCSYS
FMCQM
5010
localhost
then when you do the second configuration with just a client and a new QMGR
the values you may have to supply are
ConfigId= FMC1
QMGR=FMCQM1
QUEUE MANGER
FMCQM1
First Queue Manager
FMCQM
localhost
5010
CLUSTER
FMCGRP
CLIENT CONNECTIONS
FMCGRP
FMCSYS
FMCQM1
FMC
That should mostly take care of it.
| Quote: |
| Do I give my remote machine queuemanger and port number |
Give the QMGR on which the server is running and the correspond port. |
|
| Back to top |
|
|
|
|
