This chapter describes how to view and monitor business processes. It contains the following topics:
The [Ensemble] > [Business Process List]
page displays any current instances of a business process in the currently running production. If a business process has completed its work, there is no entry for it on this page.
The following topics provide details.
The left area of the [Ensemble] > [Business Process List]
page provides the following options that you can use to filter the list of business process instances displayed on this page:
After you have edited these fields, you can click one of the commands at the top of the page:
to sort the list of entries in the top display using the criteria shown in the bottom display.
to redisplay the entries in their default order and return the fields in the bottom display to their default values.
Ensemble then redisplays the page.
The middle area of the [Ensemble] > [Business Process List]
page displays the following information for each business process instance:
The unique identifier for the instantiated business process.
The value 1 means that the primary request that initiated this business process has been completed. The value means that the primary request has not yet been completed.
When this is underlined, it means that the host class is a BPL business process. You can click on the underlined name to display the BPL diagram for the host class.
One or more business processes may be instantiated within Ensemble during the session, in order to fulfill the primary request. All of these business processes share the same SessionId
, but business process has a different ID
The message ID number of the request that caused this business process to be instantiated. The PrimaryRequest
number is distinct from the object ID
number of the business process. The PrimaryRequest
may or may not be the same as the SessionId
. If the numbers are different, it means that the request message that started the session triggered subsequent requests within Ensemble, and one of these later messages is the one that actually instantiated the business process.
When the PrimaryRequest
number is underlined, it means that the primary request message can be displayed as a set of properties in XML format. You can click on the underlined PrimaryRequest
number to display the message properties in colorized XML format in the right area of the page. For example:
The date and time when this business process was instantiated.
The date and time when this business process completed the primary request that instantiated it. If this request has not been completed, this field is blank.
The unique identifier for the general-purpose, persistent variable context
, which is defined using the <context> and <property> elements in BPL to hold persistent properties for this business process instance. This column is available for BPL business processes only.
is underlined to indicate that you can click on it to display the context
properties in colorized XML format in the right area of the page. For example:
Click this command to display the business rule log
for this business process instance.
In each row, background color indicates the status of the business process instance:
White These items are in progress.
You can purge outdated records from the Ensemble business process archives by clicking the
command at the bottom left of the [Ensemble] > [Business Process List]
The fields in this dialog allow to you purge business process instance data as follows:
The number in this column reflects the total number of instances that are now in the persistent store for this production. Use the Current Count
to decide whether or not it is worthwhile to purge these records at this time.
Do not purge most recent
Specifies the number of days’ worth of records to keep. The number can be 0 (zero), which keeps nothing and deletes all business process instance records that exist at the time of the purge operation. The default value for Do not purge most recent
is 7, which keeps records for the last seven days.
The count of days includes today
, so keeping messages for 1 day keeps the messages generated on the current day, according to local server time.
To purge the data, click
. Ensemble immediately starts to purge instances according to the parameters you have entered in the dialog box.
You cannot undo the