|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
The format of the Monitor Event Request (MER) message must conform to the SWMonitorList.xsd schema. When generating a MER message, you can specify the following:
• names of the fields whose data you want to output. You can specify all fields for all activities or you can specify a particular field for a particular activity, depending on your requirements.
• activities you want to monitor or you may specify that you want to monitor all activities. When specifying the activities that you want to monitor you must also specify the steps on which the activity will be monitored. However, you may specify that you want to monitor an activity on all steps in that procedure. For an explanation of the activities that you can monitor, see "Understanding Audit Trails" in TIBCO iProcess Engine Administrator’s Guide.The MER message detailed below shows activity monitoring information for a procedure called CARPOOL. The table below describes:
<ProcedureMonitor xmlns="http://bpm.tibco.com/2004/IAP/1.0/MER" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://bpm.tibco.com/2004/IAP/1.0/MER SWMonitorList.xsd">The XML below demonstrates some output MED messages that have been generated from the MER message.<AuditEvent xmlns="http://bpm.tibco.com/2004/IAP/1.0/MED" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://bpm.tibco.com/2004/IAP/1.0/MED SWAuditMessage.xsd"><TimeStarted Microseconds="674419">2005-07-26T15:59:22</TimeStarted><AuditEvent xmlns="http://bpm.tibco.com/2004/IAP/1.0/MED" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://bpm.tibco.com/2004/IAP/1.0/MED SWAuditMessage.xsd"><TimeStarted Microseconds="674419">2005-07-26T15:59:22</TimeStarted><AuditMessage>"REQUEST" released by swadmin@vora677</AuditMessage><AuditDate Microseconds="429174">2005-07-26T15:59:54</AuditDate>
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |