| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Work Item RUNNING state not shown on the Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| muralihegde |
 Posted: Tue Nov 12, 2002 4:12 am Post subject: Work Item RUNNING state not shown on the Client |
 |
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi All,
We have a work flow 3.3.0 server configured on a Windows 2000 PC and the we are using the Windows MQWF Run Time Client on the same PC.
During the development, I had made all the acitivities as Start Manual, in order to test my logic.
When I start the activity manually, (either by the Windows RunTime Client or through my java pgm) and if the activity runs for a longer duration so as to stay in the running condition (An activity implemented as UPES Synchronous), I could see the work item as RUNNING on the Windows Client as well as through my java pgm ( service.queryWorkItem() )
But now, as it should be in production, when I make the activity start as Automatic, they go into running state as earlier.
But I will not see these work items in the Windows Run Time Client Work List or through the java query. I can only know that they are in running state, through the Process Monitor option in the Windows RunTime Client.
Also I tested, it is sufficient if at least either one of the activity start or exit has to be manual in order to show the activity as running when queried.
But if we make the exit as manual, when the activity gets a response back, it goes to Executed State, instead of Finished, so the next activity does not become ready.
Am I missing something in the setting/ process modelling or the activity property set up ?
-Murali |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Nov 12, 2002 5:55 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Murali:
What you are seeing is a feature of V330 and up. There is no workitem created for an automatic activity. This is for performance reasons.
In short what you are seeing is what I would expect to see.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Nov 12, 2002 9:13 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Muralihedge
Jmac is correct, this is by design. Now I have not tried this, but I think you can override ths setting by running the program in "Attended" mode instead of "Unattended". I got the following information from an IBM conference. Please let me know if this works.
Good luck.
Dave
PDF: MQSeries Workflow MQSeries Workflow
Handling of a Handling of a
UPES Program Error UPES Program Error
| Quote: |
If "unattended" and "automatic If "unattended" and "automatic
start", only a program activity start", only a program activity
will be created, will be created,
but no work items. but no work items.
In case of an error In case of an error
(<ActivityImplInvokeResponse> (<ActivityImplInvokeResponse>
with an <Exception>) with an <Exception>)
a work item with the state a work item with the state
InError will be InError will be created. |
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Nov 12, 2002 9:39 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Dave:
I don't think it is possible to have a program activity set to run as a UPES and to not have the program object that is assigned to the activty set to unattended. You will get a failure on BT Export, or Verify. Please let me know if you have done this successfully.
What I think the foil you are referring to is stating is that "In the case of an error", then a Workitem MUST be created and put into the "InError" state.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| muralihegde |
| Posted: Thu Nov 14, 2002 7:22 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi All,
I was earlier using the Work Item related APIS.
IBM support gave the suggestion to use the Process Instance Monitor APIs to access the Activity Instances. These APIs return the states of all the activites (automatic and manual as well) irrespective of whether they are in Running, Expired, Ready, Inactive etc.
With this we are now able to query the status and take action on the activity(force finish etc)..and this has solved our requirement.
Thanks for all the responses.
-Murali. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Nov 14, 2002 7:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ah... But the only way to do this (get the ActivityInstances) is to have access to the appropriate ProcessInstance, or a Workitem (which obviously you do not have).
I have requested from IBM a QueryActivityInstances ExecutionService method, and would suggest that you do the same. This would enable us to more quickly access these "troubled" activities. If enough people ask, we just might get this.
THANKS
_________________
John McDonald
RETIRED |
|
| 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
|
|
|
|
