Monitoring Tab
Taleo Connect Client enables end users to track the progress and inspect the final status of workflow executions by using the monitoring feature. The feature is based on the workflow result information that is updated at each step of the workflow execution. This information can be saved to disk in its original XML format, in a text or HTML formatted version, or in a custom format using an XSL transformation.
Monitoring
The Enable Monitoring check box determines if monitoring is active or not. It is highly recommended to always have at least one type of monitoring active as this is the principal source of information about workflow executions.
Monitoring Location
Folder identifies the folder where all monitoring files are stored. This value can be modified from its default value; however, when using the HTML monitoring type, the web subfolder is required for the images and style sheets.
A specific monitoring file is generated for each workflow execution and updated after each step. The Reuse the workflow identifier as the file name setting will use the workflow identifier as defined in for the monitoring file name. The Use a custom identifier setting allows you to specify the monitoring file name instead of using reusing the workflow identifier as the file name. In addition, the monitoring file name can use either a static or a unique identifier:
Use a static identifier. A static or constant identifier for the monitoring file name gives you easy access to the result of a given integration process over time. Each workflow execution would overwrite the previous one, but a simple shortcut could be added to an Internet browser to quickly access the current result.
By default, the monitoring file name is static.
Use a unique identifier. A unique identifier creates a different monitoring file name for each workflow execution. This ensures that the monitoring information is always available and easily retrievable for a particular execution.
A unique identifier can be used either when the file name reuses the workflow identifier or when the file name uses a custom identifier.
There are two ways to add a unique identifier to a monitoring file name:
Append a token (UUID, time stamp) to the file name.
Add a system property named "com.taleo.integration.client.uniquemonitoringid=true" to the command line or set "-Dcom.taleo.integration.client.uniquemonitoringid=true" in the ini file.
Monitoring Type
The Monitoring Type section determines what information is stored and how it is presented.
The XML monitoring file contains all the information produced by the workflow execution. It is not easily readable and is more suited for automated system treatment.
The HTML monitoring file offers a styled view of the main monitoring information that is easy to read and interpret.
The TEXT monitoring file contains the minimal subset of monitoring information and is mostly used in a production environment where an HTML file cannot be accessed.
The Custom monitoring file allows a personalized view of the monitoring information. The custom file is generated by applying an XSL transformation to the XML monitoring file. The file extension determines what is appended to the file location set in the previous location to create the actual file on disk.