How to Configure Activity Monitoring Information

Generate your activity monitoring configuration information as XML in the form of a Message Event Request (MER) message. See Understanding Message Event Request (MER) Messages. You can do this using any XML tool, for example, Altova XMLSpy. The MER message should conform to the SWMonitorList.xsd schema. See Understanding the Activity Monitoring Schemas.

Once you have generated a MER message according to your requirements, there are two ways to update or replace the activity monitoring configuration information in the iProcess database with the activity monitoring configuration information in the MER message:

−

by using the SWDIR\bin\swutil IMPMONITOR and EXPMONITOR commands, see "Monitoring Activities" in TIBCO iProcess swutil and swbatch Reference Guide.

When you install the TIBCO iProcess Engine, three schemas are installed which are used to configure the activity monitoring configuration information. The schemas are installed in the SWDIR\schemas directory. The schemas are:

•

SWMonitorList.xsd. The format of the Monitor Event Request (MER) messages must conform to this schema. MER messages request the activities to monitor and are sent to the iProcess database to update the activity monitoring configuration information. See How to Configure Activity Monitoring Information.

•

SWAuditMessage.xsd. The format of the Monitor Event Detail (MED) messages must conform to this schema. These messages can be sent in either a basic format or an extended format conveying additional information. MED messages contain the information about the activities being monitored and are sent from the IAPJMS process to the external application. See "Administering Activity Monitoring" in TIBCO iProcess Engine Administrator’s Guide for more information.

•

SWType.xsd. This defines the iProcess field types that are used in the SWMonitorList.xsd and the SWAuditMessage.xsd schemas.

Every MER message sent to the iProcess database to update the activity monitoring configuration information consists of XML requesting the events to monitor. The MER XML format is defined by the SWMonitorList.xsd schema.

•

You can use an activity ID of -1. Using an activity ID of -1 is the equivalent of using $ALL$ for a step name. It means all activities are monitored. For example:

For an explanation of the activities that you can monitor, see "Understanding Audit Trails" in TIBCO iProcess Engine Administrator’s Guide.

000, 007, 008, 009, 021, 022, 023, 024, 057

You must set the value of <Step Name> to be $ALL$. For example:

If you do not, then no MED message is generated. This is because the schema enforces that a value for the step name element must be defined for these activities. However, because of the way the iProcess Engine works, there is no step name for these activities. For example, for activity ID 000, there is no step name when a case is started because the case has not yet reached its first step. Therefore, to work around this, you should specify a value of $ALL$ in the step name element for these activity IDs.