| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuring FAT Client : Client on NT and Server is on AIX |
« View previous topic :: View next topic » |
| Author |
Message
|
| anuppc |
 Posted: Fri Apr 04, 2003 12:19 pm Post subject: Configuring FAT Client : Client on NT and Server is on AIX |
 |
|
Voyager
Joined: 22 Oct 2002
Posts: 93
Location: Montreal
|
1. We are trying to configure a Fat Client on NT to connect to WF Server running on AIX. We seem to have a communication trouble with MQ Series. We did copy the tab file in binary format from AIX, on to the NT machine and tried to reconfigure the fat client using this tab file. We also pointed to the AIX host in the configuration..
The listener and the WFServer is up and running on AIX. The fat client seem to have difficulty in terms of finding the remote QueueManager. Looks like its trying to search for the local QManager.
2. Meanwhile we have an application(WebClient) which runs perfectly on NT. we are trying to port it on AIX.. Thats the basic idea of this whole exerscise. We have an error while running our application directly on AIX m/c. It says "Communication Error FMC00013E. Failing Object FMCQM"
On AIX
The MQWFlow version is 3.3.2 and MQSeries version is 5.2.1, Websphere 4.0
On NT
MQWFlow version 3.3.0 (currently we r not using this but using just the FAT client)
Please note that this NT box has everything, Websphere, MQSeries 5.2.1 and workflow.... I just modified the existing client configuration to point to the remote WFServer on AIX...
Please let me know if there are some documents regarding configuring the FAT client. If you know of some utilities to check if my installation of MQ WorkFlow on AIX. Im sure it is running correctly as evrything starts up normally and im ale to port my models using fmcibie .....
_________________
BlowFish |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Apr 04, 2003 12:53 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Anup:
On the NT box I would suggest you to do this.
Use fmczutil instead of the configuration utility (GUI) and do this.
Select the "client with QMGR" option. For this configuration just select option c.
Create the new configuration with a local qmgr on the box and when asked for the info about the first qmgr give the details of the qmgr on AIX box where the mqwf server is running.
If I beleive my memory I think if you have both MQ Client and MQ Server on the Windows box then if you are trying to create a workflow configuration, there is some setting to be done and I don't remember what it was.
Try what I have said above and see how it goes.
| Quote: |
2. Meanwhile we have an application(WebClient) which runs perfectly on NT. we are trying to port it on AIX.. Thats the basic idea of this whole exerscise. We have an error while running our application directly on AIX m/c. It says "Communication Error FMC00013E. Failing Object FMCQM"
|
See the error logs in /var/mqm/errors and see what it says (or post it here).
-------
Venny |
|
| Back to top |
|
|
| manoj |
| Posted: Sat Apr 05, 2003 7:06 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
are u configuring the FAT client as a "client with queue manager" ? . i guess u r configurring just a client bcos u r copying the channeltabs.
check the connect name u gave while configuring the client..this is a very common mistake people do.
if u want to configure a client with queue manager and if u still get the problem then first make sure that u r local queue manager can communicate with the queue manager of workflow server on the AIX box.
_________________
-manoj |
|
| Back to top |
|
|
| clindsey |
| Posted: Sat Apr 05, 2003 8:16 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
If you are trying to connect as a client to a remote qm and you have a local queue manager installed, there is a config change that is necessary, just as Venny says.
MQWF has 2 copies of a file named fmccfmlc.dll. The 2 copies are identical in function but one is linked with MQ server libraries and is located in <mqwf>\bin\mqserver. The other is linked with MQ client libraries and is located in <mqwf>\bin\mqclient. Which ever one is first in your PATH is the one that determines the mode you are running.
You must have <mqwf>\bin\mqserver currently in your path. You can verify this by running 'fmczccd'. The official way to change this to be a remote client is to change the path to <mqwf>\bin\mqclient.
I switch back and forth frequently in my development environment on W2K so to keep from constantly changing the path, I only put <mqwf>\bin
in the path. Then I have bat files called setserver.bat and setclient.bat that copies the respective fmccfmlc.dll into mqwf\bin. This works for me.
For unix guys, workflow also has 2 shared libs as well. But unix gives you the utility to switch modes (fmczinsx -o mqserver | mqclient).
By the way, fmczccd (Windows only) is a nice utility to validate your channel table as well. If you have multiple configs, run it as 'fmczccd -y <cfgid>' otherwise just 'fmczccd'. First, if you are running in server mode it will tell you this. Make the path change as described above. Then run it again. I will tell you your connection names for the current config and then it will use your channel tab to connect to the queue manager. If this test is successful, you should be able to bring up the client with no problems.
Sorry for the long post. I hope this helps,
Charlie |
|
| 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
|
|
|
|
