| Author |
Message
|
| cyberimp |
 Posted: Fri Aug 13, 2004 4:25 am Post subject: Problem of create Runtime and client configuration.(AIX/Win) |
 |
|
Newbie
Joined: 09 Aug 2004
Posts: 9
|
Platform: AIX + MQ series + Workflow 3.5
in summary: The Runtime Queue manager won't have the related cluster sender channel while the client configuration completed and the client queue manager was added to the same Clusters with Runtime QM.
Steps:
After I created a run time configuration, verify the configuration by
fmczchk -y FMC
It report one error, but I can't find out it in log file.
Then:
strmqm FMCQM
runmqsc FMCQM
display channel(%ANY CHANNEL NAME%)
it will report an error like:
'can't find /var/mqm/qmgrs/FMCQM/@ipcc/AMQCLCHL.TAB...'
If I cp a AMQCLCHL.TAB from other queue manager directory, those channel can be shown.
Then I create a runtime client on Windows. After the configuration finished, the runtime queue manager FMCQM1 was created and joined to cluster FMCGRP. But the FMCQM (QM of runtime on AIX) has not the related cluster sender channel: TO.FMCQM1.TCP, just has a cluster receiver channel: TO.FMCQM.TCP.
The client QM FMCQM1 have two channel TO.FMCQM.TCP(cluster sender) and TO.FMCQM1.TCP(cluster receiver)
If login from client, it will fail with FMC_API_ERROR_COMMUNICATION.
What's the reason? and how to resolve these?
Thanks a lot!!!! |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Aug 13, 2004 7:54 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
cyberimp
I am not sure what you are trying to accomplish:
But after you created a runtime configuration you need to do the following:
1. Make sure database is started
2. Start the QMGR using strmqm
3. Start the trigger monitor: runmqtrm -m QMGRNAME -q FMCTRIGGER &
4. Start the workflow server: fmcamain &
After that you should see a fmcamain process and two fmcemain processes.
| Quote: |
| 'can't find /var/mqm/qmgrs/FMCQM/@ipcc/AMQCLCHL.TAB...' |
This is normal for a workflow QMGR. This is because workflow creates a channel table (in /var/fmc/chltabs) instead of the above directory where MQ ususally creates. To get rid of this error there are a couple of env variables that you need to set.
Look at this thread for what env variables and how to set them
http://www.mqseries.net/phpBB2/viewtopic.php?t=8160&highlight=fmcqm+channel+table |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Aug 13, 2004 7:58 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
If you only one repository QM (WF runtime QM), you will have only cluster reciever channel on it. A repository QM doesnot need a cluster send channel unless it is talking to another repository.
Are that your channels in active state on both ends and make sure u r client QMs can communicate with the server Qm.
_________________
-Ratan |
|
| Back to top |
|
|
| cyberimp |
| Posted: Mon Aug 16, 2004 12:06 am Post subject: |
|
|
Newbie
Joined: 09 Aug 2004
Posts: 9
|
My platform configuration
PC1: Windows XP + MQServer&Client + Workflow Client.
PC2: AIX + MQServer&Client + Workflow Runtime server.
Now, all the problems above have been resolved by changing the method of creating Client configuration.
During creating the Client configuration:
1. I updated the system variable Path: change the ...;<WFDIR>\MQServer;... to ...;<WFDIR>\MQClient;...
2. download the MQWFCHL.TAB from Unix.
3. Run the WF Configuration Utility(fmczacfg), create an client configuration. There just have two tabs: Client connection, Runtime client.
3. Launch the WF Client to connect to Server on Unix.
It works.
In these main steps above:
If I didn't update the Path, keep the MQServer, there will have more tabs while creating client configuration, like 'Queue Manager', 'Cluster'.
After the configuration finished. When I try to logon from the client on windows. there will has an error message: FMC_API_ERROR_COMMUNICATION ...
So, my questions are:
1. Is it possible to connect the Windows Client to Unix server by MQServer API? Is that the Client Concentrator? I searched several posts about the Client configuration here, but it seems that everyone use the MQClient API.
2. If it is possible. So, I should create a local QM and join it into the Cluster, which also include Runtime QM as repository QM. Should I upload the MQWFCHL.TAB from Windows to Unix? This file on windows has been changed after the Client configuration created.
3. If the MQWFCHL.TAB is not the reason for the FMC_API_ERROR_COMMUNICATION error, what's the possible reason for this error?
4. While I am trying to create Client config. on windows by using fmczutil, as Vennela recommended in other posts. It won't work. There won't have any command list or error messages on console window. The logined User is a memmber of Administrators and mqm groups. Why?
Thanks! |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Aug 16, 2004 6:22 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
1. Is it possible to connect the Windows Client to Unix server by MQServer API? Is that the Client Concentrator? I searched several posts about the Client configuration here, but it seems that everyone use the MQClient API.
|
YES, YES
| Quote: |
| 2. If it is possible. So, I should create a local QM and join it into the Cluster, which also include Runtime QM as repository QM. |
Instead of you creating and joing the QMGR to the cluster, allow the workflow config utility to create the QMGR and add to the workflow cluster
| Quote: |
| Should I upload the MQWFCHL.TAB from Windows to Unix? |
NO, you don't have to do that. channel tabs are only for client server communication and not for QMGR QMGR communication
| Quote: |
3. If the MQWFCHL.TAB is not the reason for the FMC_API_ERROR_COMMUNICATION error, what's the possible reason for this error?
|
Because the two QMGRs are not talking to each other
You should observer that the ckuster channels beween these two QMGRs will not be running. If not let us kno and we will try to trouble shoot
| Quote: |
4. While I am trying to create Client config. on windows by using fmczutil, as Vennela recommended in other posts. It won't work. There won't have any command list or error messages on console window. The logined User is a memmber of Administrators and mqm groups. Why?
|
With 3.4 using the GUI is better than using fmczutil. |
|
| Back to top |
|
|
| cyberimp |
| Posted: Mon Aug 16, 2004 4:48 pm Post subject: |
|
|
Newbie
Joined: 09 Aug 2004
Posts: 9
|
| vennela wrote: |
Because the two QMGRs are not talking to each other
You should observer that the ckuster channels beween these two QMGRs will not be running. If not let us kno and we will try to trouble shoot
. |
After the workflow configure utility created the client QM(FMCQM1 on win) and joined them into the Cluster with the Runtime QM(FMCQM on unix), the FMCQM1 have two channel TO.FMCQM.TCP(cluster sender) and TO.FMCQM1.TCP(cluster receiver).
But the FMCQM just have one cluster receiver channel: TO.FMCQM.TCP.
I had noticed that at the begin of this post, but I don't know why.
Is that the reason for the FMC_API_ERROR_COMMUNICATION?
If it is, should I add the cluster sender channel in runtime QM(FMCQM)?
I think the configure utility should do this while add the client QM into the Cluster. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Aug 17, 2004 12:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Maybe not
What do you get when you do
dis clusqmgr(*) on both the QMGRs
What do you get when you do
dis qc(*) on Windows box
What do you have in the MQ error logs on both sides |
|
| Back to top |
|
|
| cyberimp |
| Posted: Fri Sep 03, 2004 1:36 am Post subject: |
|
|
Newbie
Joined: 09 Aug 2004
Posts: 9
|
I try that again.
Before that, I changed the MQClient to MQServer and delete all in chltabs dir on windows box. (I created a fat Client by using MQClient API before.)
All are ok. The connection is successful.
But there has one thing, while I try the fmczccd -y FMC2 to check my client configuration on windows box, the message as below:
-------------------------------------------------------------------------------
The channel table in the profile is: e:\program files\ibm websphere mq workflow\
chltabs\mqwfchl.tab
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQMC
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQMC
Protocol : TCP/IP
Connection name : 172.16.1.133(5011)
TCP/IP-addr : 172.16.1.133
TCP-Port : 5011
Status : ok
---------------
You are using the MQSeries Server API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQMC .
Connecting to the queue manager FMCQMC was successful.
There are no checks with this utility to verify that the MQSeries Workflow Serve
r is running on your server.
-------------------------------------------------------------
note: FMCQMC(5011) is the QM on windows box. the runtime server is on Unix box, and its QM is FMCQM(5010).
Is that right? In my memory, there should have two QM info while using client concentrate mode. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Sep 03, 2004 5:53 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| fmczccd will not be of much use if you are using MQ Server on the workflow client side |
|
| Back to top |
|
|
|
|
