IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Generate monitor models > Generate from applications in the workspace

Common monitoring templates for IBM BPM Advanced and WebSphere Enterprise Service Bus

When you are generating or working with a monitor model based on a Integration Designer application, you can choose to apply one or more predefined common monitoring templates. These templates are collections of predefined monitoring constructs.

For example, you can select a template to capture the elapsed duration of a Business Process Execution Language (BPEL) process. After you select a template, the generated monitor model is automatically set up with the constructs that are required to capture the information, in this example the elapsed duration.

KPI templates

The KPI templates produce metric-based key performance indicators (KPIs). These KPIs do not include targets, ranges, or metric filters, but you can add those later in the Monitor Model editor. The following KPI templates are available:

• Average elapsed duration:

  • The average elapsed duration template measures the time difference between the end event and the start event for an event source. The KPI calculates the average of these times for all monitoring context instances.

  • When you apply this template, an inbound event is created for each event that can create a monitoring context and for each event that can terminate a monitoring context. A single stopwatch is created that references all the inbound events. A KPI is created that is based on the stopwatch and calculates the average elapsed duration.

• Average working duration:

  • The average working duration template measures the time difference between the end event and the start event for an event source, not counting the time taken out by pause or suspend events. The KPI calculates the average of these times for all monitoring context instances.

  • When you apply this template, an inbound event is created for each event that can create or terminate a monitoring context, as well as for each suspend or resume event. A single stopwatch is created that references all the inbound events. A KPI is created that is based on the stopwatch and calculates the average working duration.

Metric templates

The metric templates produce instance metrics. The following metric templates are available:

• Start time:

  • The start time template captures the time at which the start event arrives for the event source.

  • When you apply this template, a Start Time metric is created to store the start time of the event source. An inbound event is created for each event that can create a monitoring context. A metric value expression is added to the Start Time metric for each of these inbound events. The Start Time metric is set only when the first of these events arrives.

• Completion time:

  • The completion time template captures the time at which the end event arrives for the event source.

  • When you apply this template, an End Time metric is created to store the completion time of the event source. An inbound event is created for each event that can terminate a monitoring context. A metric value expression is added to the End Time metric for each of these inbound events. The End Time metric is set only when the first of these events arrives.

• Assigned user:

  • The assigned user template stores the name of the user who has claimed the task.

  • When you apply this template, an Assigned User metric is created to store the name of the assigned user. An inbound event is created for each event that can assign a user. A metric value expression is added to the Assigned User metric for each of these inbound events. The Assigned User metric is updated each time one of these events arrives.

• State:

  • The state template tracks the state of an event source.

  • When you apply this template, a metric is created to store the state of the event source. An inbound event is created for each event that can change the state. Depending on the event source, either a metric value expression is added to the State metric or a trigger is created for each of these inbound events. The State metric is updated each time one of these events arrives.

  • For information about the state values for process, activity, and activity scope events, see "Business process events."

• Elapsed duration:

  • The elapsed duration template measures the time difference between the end event and the start event for an event source.

  • When you apply this template, an inbound event is created for each event that can create a monitoring context and for each event that can terminate a monitoring context. A single stopwatch is created that references all the inbound events.

• Working duration:

  • The working duration template measures the time difference between the end event and the start event for an event source, not counting the time taken out by pause or suspend events.

  • When you apply this template, an inbound event is created for each event that can create or terminate a monitoring context, as well as for each suspend or resume event. A single stopwatch is created that references all the inbound events.

Inbound events are created only once. If you apply both a start time and a completion time template, you will have only one set of inbound events. All generated template elements will refer to this one set of inbound events.

Measure templates

The measure templates produce measures and stopwatches. The following measure templates are available:

• Average elapsed duration:

  • The elapsed duration template measures the time difference between the end event and the start event for an event source.

  • When you apply this template, an inbound event is created for each event that can create a monitoring context and for each event that can terminate a monitoring context. A single stopwatch is created that references all the inbound events. A measure is created that is based on the stopwatch and calculates the average elapsed duration.

• Average working duration:

  • The working duration template measures the time difference between the end event and the start event for an event source, not counting the time taken out by pause or suspend events.

  • When you apply this template, an inbound event is created for each event that can create or terminate a monitoring context, as well as for each suspend or resume event. A single stopwatch is created that references all the inbound events. A measure is created that is based on the stopwatch and calculates the average working duration.

Templates available for each application element type

The following templates are available for each application element type:

Event Source	Elapsed duration	Work duration	Start time	Completion time	Assigned user	State
SCA	Interface Operation	X		X	X		X
BPEL	Process	X	X	X	X		X
Assign	X		X	X		X
Compensate	X		X	X		X
Empty	X		X	X		X
Flow
ForEach	X		X	X		X
Invoke	X	X	X	X		X
Link
Pick	X		X	X		X
Receive	X		X	X		X
Reply	X		X	X		X
Rethrow	X		X	X		X
Scope	X		X	X		X
Script	X		X	X		X
Sequence
Staff	X	X	X	X	X	X
Switch						X
Terminate	X		X	X		X
Throw	X		X	X		X
Variable
Wait	X		X	X		X
While	X		X	X		X
Business state machine	BSM definition			X	X		X
State	X		X	X		X
Transition	X		X	X		X
Guard	X		X	X		X
Action	X		X	X		X
State entry action	X		X	X		X
State exit action	X		X	X		X
Timer	X		X	X		X
Business object map	Map	X		X	X		X
Transformation	X		X	X		X
Interface map	Operation binding	X		X	X		X
Parameter mediation	X		X	X		X
Business rules	Operation	X		X	X		X
Selector	Operation	X		X	X		X

Generate monitor models from applications located in the workspace