|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Activity Life Cycle / Audit Trail |
« View previous topic :: View next topic » |
Author |
Message
|
Duschwolf |
Posted: Tue Jul 30, 2002 1:41 am Post subject: Activity Life Cycle / Audit Trail |
|
|
 Novice
Joined: 01 May 2002 Posts: 15
|
Hello!
I have to test a MQSeries Activity Life Cycle by testing the Processes and analyse the Audit Trail.
There are different activity states, listed in Table 6 (IBM MQSeries Workflow Administration Guide), but I'm not able to get states like
- 21203 (CheckedOut)
- 21205 (Terminated)
- 21206 (Suspended)
- 21209 (Skipped)
- 21210 (Deleted)
- 21211 (Suspending)
- 21212 (Terminating)
- 21213 (Expired)
At the moment, I'm working with the simple Processmodell from the Redbook "MQSeries Workflow for WindowsNT for Beginners".
Should I use a less simple Process?
Or can anybody give me another hint how to get this activity states?
Thank U!
Last edited by Duschwolf on Wed Jul 31, 2002 2:21 am; edited 1 time in total |
|
Back to top |
|
 |
fbaril3 |
Posted: Tue Jul 30, 2002 2:04 am Post subject: |
|
|
Acolyte
Joined: 14 Jun 2002 Posts: 53
|
In the BuildTime, check the following :
Go to your process property
Go to the control tab
On the "Keep Finished work items", check if the "Forever" option is positonned. If not, position it on "Forever" (then reimport and restart your MQWF server). |
|
Back to top |
|
 |
jmac |
Posted: Tue Jul 30, 2002 4:57 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
- 21203 (CheckedOut)
Issue a checkout command for the workitem. This state is similar to running, in fact prior to V330 I dont think this state existed
- 21205 (Terminated)
Issue a teminate on the workitem, however you must set your "Keep finished" items as per the previous post
- 21206 (Suspended)
Suspend the process instance.
- 21209 (Skipped)
This is the state that an activity instance is in when it is not run due to Transition conditions, however you must set your "Keep finished" items as per the previous post
- 21210 (Deleted)
Issue a delete on the workitem, however you must set your "Keep finished" items as per the previous post
- 21211 (Suspending)
Suspend the process instance. I have never seen this state, as I believe it is quite fleeting.
- 21212 (Terminating)
Terminate the process instance. I have never seen this state, as I believe it is quite fleeting.
- 21213 (Expired)
Set an expiration time for the activity and let the activity expire, however you must set your "Keep finished" items as per the previous post
One of the things you must remember is that any state that has a workitem completed will never show up unless you set the Keep Finished Workitems as above. The other issue is that the Terminating and Suspending states should only exist for a very short time, I personally have never seen any workitems in either of these states.
GOOD LUCK. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
fbaril3 |
Posted: Wed Jul 31, 2002 1:23 am Post subject: |
|
|
Acolyte
Joined: 14 Jun 2002 Posts: 53
|
Hello,
******
To get the state "Suspending" for a process Instance, you can make it this way :
while a work item is in the state "running" (i.e for example a manual work item yo are filling), you make the action "Suspend" on the process instance which will go on the "Suspending" state until you finish you running work item. (You can easly do that with the flow example you are using)
When you finish your work item, the process instance will go on the state "terminated".
*******
*******
To get the state "Terminating" for your process instance, you can make it this way using a more complex flow than the one from the redbook : you need a process P1 and it subprocess P2.
Use a flow with a "non autonomous control" sub process P2 (non autonomous control is I think put as a default value).
Then, you have to get your subprocess instance of P2 in the "running" state.
If you make a "Terminate" action on the process instance of P1, it will go on the "Terminating" state (as P2 's instance is in the "running" state)
**************
This way, you will be able to see the state "Suspending" and "Terminating" (even using the thick client).
Hope this help |
|
Back to top |
|
 |
Duschwolf |
Posted: Wed Jul 31, 2002 2:18 am Post subject: |
|
|
 Novice
Joined: 01 May 2002 Posts: 15
|
Ok, this helped a lot, thank U!
But even after activating "Forever" for Keep Finished Work Items in my process properties I don't get all the states I like to have.
-21203: How can I checkout any activities?
-21206: When I suspend the Process instance, the activities don't get into this state, although I see that the Process instance is "suspended"
-21209: In which situation do I get a skipped state?
-21210: I'm able to delete Workitems, but how can I delete an activity? |
|
Back to top |
|
 |
jmac |
Posted: Wed Jul 31, 2002 4:41 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
fabril3:
THANKS.... I don't really have a need to see these states, but it certainly helps to know how to produce them.
THANKS AGAIN.
Duschwolf:
21203: How can I checkout any activities?
You cant, from the Fat Client, if you "Start" with the thin client that is actually a CheckOut. If you can write code it's simply
WorkItem::checkout()
21206: When I suspend the Process instance, the activities don't get into this state, although I see that the Process instance is "suspended"
Did you refresh the worklist? Also see what Fabril3 said in the previous post.
-21209: In which situation do I get a skipped state?
You need to have an activity that gets bypassed due to Transition Conditions. However, I generally see this state when looking at ActivityInstances, not WorkItems.
-21210: I'm able to delete Workitems, but how can I delete an activity?
I don't believe there is a method to delete an Activity.
GOOD LUCK _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
Duschwolf |
Posted: Wed Jul 31, 2002 5:29 am Post subject: |
|
|
 Novice
Joined: 01 May 2002 Posts: 15
|
Thanks for the quick answer!
Yes I've refreshed the worklist, but the workitems stay "Ready". May it be that I have to activate the scheduling server so Runtime "switches" the Activity State to "suspended"? |
|
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
|
|
|
|