| Author |
Message
|
| praveenchhangani |
 Posted: Tue Jan 07, 2003 8:15 am Post subject: Workflow Audit Trail Question |
 |
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Hi All,
Does anyone know what happens to the workflow audit-trail information, if for some reason it Workflow is unable to store it in the audit trail database tb.
Does it store the audit trail somewhere else if the above scenario was present?
Any input is appreciated!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
 |
| Ratan |
| Posted: Tue Jan 07, 2003 11:16 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Praveen,
I have no Idea what happens, but my guess.
If workflow is unable to access the audit trail DB table, I guess that means workflow is unable to access the runtime Database. This would mean workflow is down. I believe as long as workflow server is up it will access the audit trail DB table.
I can be completely wrong.
-Laze |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 07, 2003 11:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
What Laze says makes sense to me, although, I guess it would be possible for the Audit_Table (or any table for that matter) to reside on a disk that runs out of space, while other tables still have room to grow.
One thing for sure... Clean out your Audit table periodically.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Tue Jan 07, 2003 12:09 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Thanks.
This is interesting to know, because if a company was making use a of a lot of their audit trail data and very much dependant on it for performance and other audit trail related reasons; What would happen if, for even 15-20 minutes the audit trail data could not be written to the audit trail table?
This is possible in a situation where the size limit for the audit trail (for a particular process) has NOT been specified and at the same time the process requires FULL AUDIT TO DB.
The moment the runtime db maxes out, workflow goes down. Now, let's say Janice the workflow admin, brings workflow back up in about 15 minutes. After 15 minutes, when workflow is back up, she tells Jane the audit trail analyzing expert that workflow is up. Jane now examines the audit trail data and wants to know how long a particular process took(from start to finish).
Let's say that process 'BANKING' started at 1:00pm.
Workflow went down at 1:15pm
Janice brought workflow back up at 1:30pm
Janice restarts 'BANKING' at 1:30pm
Process 'BANKING' completes at 2:00pm
Jane looks at audit trail data and what does she see?
Process 'BANKING':
Start time: 1:00pm
End time: 2:00pm
or
Process 'BANKING'
Start time: 1:30pm
End time: 2:00pm
No wonder it is said that curiosity killed the cat!!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Jan 07, 2003 12:15 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I believe the 'Banking' Process would show up as 1pm - 2pm. we cant rely on the duration of the process by examining just one instance. If you have 'n' instances of Process B1..Bn. Then you can take the average of duration of the Process instances to arrive at a conclusion of the duration each Process Instance would take. 
-Laze. |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Tue Jan 07, 2003 12:26 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
That makes sense.....I agree.
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 07, 2003 12:31 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Praveen:
The problem you are describing as I see it is that we do not know when workflow starts and stops based on the audit trail. This makes it difficult to calculate the length of time for an Instance. I guess if you average over a day, assuming that workflow was not down for a long period of time it should be moot. Best would be if there were an Audit Record cut when message FMC1000I (System Ready) is put in the system log.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Tue Jan 07, 2003 12:40 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
John,
That would be ideal to have, yes ...in that, with functionality on hand like that; Now you can
1) Have more accurate calculations on situations described in the upper posts and..
2) Can mathematically tell system down time for workflow over a period of time eg. months, years.
Oh well, something to add to my workflow wish list!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 07, 2003 12:47 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Praveen:
Please make your wish list known to IBM. The listen more closely when issues like this are requested by customers.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
