| Author |
Message
|
| tdwells |
 Posted: Wed Jul 16, 2003 6:05 am Post subject: Workflow Process Monitoring/testing |
 |
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
Does anyone have any suggestions on a way to monitor/test a Workflow process that is running on AIX. The installation of Workflow 3.4 is the basic install (ie, no holosofx or no web server).
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Jul 16, 2003 8:07 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Can you be a little more specific about what you are wanting to do. I do not understand.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| tdwells |
| Posted: Wed Jul 16, 2003 8:34 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
I currently have a process designed on a laptop. When I test the process, I use MQSeries Workflow Client to monitor what activity in the process is being executed, as well as whether the process is being started when XML input is placed in the XML input queue.
I am now moving the workflow process to a runtime environment on AIX and am not quite sure how to perform the same process monitoring as described above.
Hope this helps.
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Jul 16, 2003 8:38 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
You can still use the same MQ Workflow Runtime Client to monitor ans test your process.
Just configure a client for your workflow server (AIX) on your laptop(workstation).
_________________
-Ratan |
|
| Back to top |
|
|
| tdwells |
| Posted: Wed Jul 16, 2003 9:17 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
So, in the Workflow Configuration utility on my workstation, I should add a new Workflow Configuration, selecting 'Client' as the components (correct?).
Then, should I choose 'No' for the message that prompts me whether I should use the 'already configured MQ Series Workflow' queue manager since it is probably referring to the Workflow queue manager on my workstation? I guess at that point, I could get the mqwfchl.tab from the server and use it for my client connection table?
Does this sound like the correct approach?
These are the steps I followed and it seemed that the Workflow Client was still connecting to my local Workflow configuration.
Does this sound like the correct approach?
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Jul 16, 2003 9:26 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I would use an MQSeries client to connect my workflow client to the server, but you should also be able to use an MQServer to connect.
I have never configured an WF Client with MQServer to connect to workflow server, but this how you should be configuring.
use a new QM and set the first QM in the cluster to the WF Server QM name. You will not need to copy the channel table if you are using an MQServer at your client machine.
If you want to use a MQClient, install MQClient on your workstation and change the environment variable to use MQClient. then configure a WF client. Here you will have to copy over the channel table.
_________________
-Ratan |
|
| Back to top |
|
|
| tdwells |
| Posted: Fri Jul 25, 2003 7:10 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2002
Posts: 42
|
I just wanted to post a step-by-step configuration for client connections to AIX workflow server. The reason is that I encountered a wierd situation that others may also run into and the solution below may help.
1. Get the MQWFCHL.TAB file from your AIX server. Should be in /var/fmc/chltabs and put in some location on your workstation.
2. On your workstation, use Workflow Configuration Utility.
a. Choose New
b. Choose 'Client' components
c. Under the Client Connections Tab
1. Select the MQWFCHL.TAB file on your workstation that
you pulled in step 1.
2. Add 'Connect names' for your workflow configuration.
** I had a problem here that I will explain below.
d. Select 'Next' or 'Done'. (Nothing you really have to do for the
'Client' tab.
3. Choose Start|Programs|IBM MQSeries Workflow|MQSeries Workflow
Client - {ConfigID}. ConfigID is whatever you named it during steps
above.
** My initial problem was that both the full install of Workflow (Server) on my workstation and the connect names on the AIX were the same
(default)
System Group: FMCGRP
System: FMCSYS
Queue Prefix: FMC
Queue Manager: FMCQM
What was happening to me was that no matter which Workflow client I used, it would try to connect to my local workstation Workflow configuration.
So, if you have the same situation, you have 2 options:
1. Change the Connect names information on either your workstation or your unix platform to something different.
2. On your workstation *before* you configure the client for AIX, change the PATH environment variable on your workstation:
From: C:\Program Files\MQSeries Workflow\bin\MQServer
To: C:\Program Files\MQSeries Workflow\bin\MQClient
and then begin with step 1 of creating and Workflow client configuration.
If you use option 2 above, any time you switch back and forth between your local Workflow Server testing/monitoring configuration and the unix configuration, you must also switch this PATH variable before invoking Workflow client.
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
|
|
