Execution Data Overview

With the execution data lists comprehensive historical data is provided to help you monitoring your processes and troubleshooting when something goes wrong.

Every run performed in your system is recorded and stored in the form of historical data presented in lists that centralize the access to the key information on the tasks. These lists are available in the Process Monitoring perspective, but you can also access them from the Process Assembly.

The data is presented in lists where each row is an execution of the selected task. It is displayed in chronological order; by default, the latest one is displayed at the top.

Example

A job fails repeatedly and you want to find out why. You right-click on it and open the Executions list displaying the history of previous runs. If, for instance, it is included in another object (its parent), you can also access the history of the parent object. Use these lists to analyze what might have gone wrong.

You have access to the execution data of an object or task if your user definition contains the necessary privileges.

Execution data is available for the following:

ClosedUsers

Recording the execution data of a user is triggered as soon as the user logs on into the system and ends with his/her logging off.

It is called Session log and provides information on all the sessions of a user in chronological order. Any failed logon attempt and the reason for the failure is provided too.

To Open the User Execution Data

  1. Switch to the Administration Perspective if you are not already there.
  2. Click User Management on the left navigation pane.
  3. Select Users.

  4. In case of large installations, the resulting list can be very long. Click the links below for a description of the search options that can help you:

  5. Right-click on the required user and select Session Log.

  6. The Session Log list provides information on the following:

    Column Description
    User name Name of the user
    Session Start Date/time on which the user logged on into the system.
    Session end Date/time on which the user logged off.
    Status Status icon and status of the session.
    Message Additional information that describes the reason for the error.

ClosedClients

Recording the client execution data begins as soon as it starts and ends when it terminates.

Client execution data provide information on the status of your client sessions.

To Open the Client Execution Data

  1. Switch to the Administration Perspective if you are not already there.
  2. Click Clients on the left navigation pane.

  3. In case of large installations, the resulting list can be very long. Click the links below for a description of the search options that can help you:

  4. Select the required client and right-click to select Executions.

  5. The list provides key historical data on the client such as:

    Column Description
    Name Name of the client. This is a number between 0 and 9999 assigned by the system upon client creation that you can change to suit your needs.
    Type

    Type of object, in this case CLNT (Client).
    RunID  
    Status Status icon and client status.
    Runtime Logon time period
    Activation Time Date/time on which the client was activated.
    Start Time Date/time on which the client was started.
    End Time Date/time on which the client terminated, regardless of its status.
    Return Code Code provided by the application when the Client ended.

ClosedAgents

Recording the agent execution data begins as soon as it starts and ends when it terminates. Additionally, a new record is created when the log file changes.

It is critical that the agents are up and running for your workflows and processes to run smoothly. If an agent has connection problems, you can start searching for the reason in the Executions list. In addition, more detailed information on each record is also available from this list via the details and reports.

Note that, since it is possible to perform multiple logins on an agent, each modification of the login information results in a new record in the Executions list.

The Agent execution data is available in client 0 only.

To Open the Agent Execution Data

  1. Switch to the Administration Perspective if you are not already there.
  2. Click Agents & Groups on the left navigation pane.
  3. Select Agents.

  4. In case of large installations, the resulting list can be very long. Click the links below for a description of the search options that can help you:

  5. Right-click on the required agent and select Executions.

  6. The list provides information on the following:

    Column Description
    Name Name of the agent as defined in the ini file.
    Type Type of object: HOST
    Start Time Date/time on which the agent was started.
    End Time Date/time on which the agent terminated, regardless of its status.
    Status Status icon and current status of the Agent.
    Message  Additional information that describes the reason for the error.

ClosedServer

The server statistics are available from the Processes and Usage list and provide details on the status of the connection.

To Open the Server Execution Data

  1. Switch to the Administration Perspective if you are not already there.
  2. expand the Automation Engine Management on the left navigation pane.
  3. Select Processes and Usage.

  4. In case of large installations, the resulting list can be very long. Click the links below for a description of the search options that can help you:

  5. Right-click on the required server and select Executions.

  6. The list provides information on the following:

Column Description
Name

Name of the server process with the following format:

SSSSSSS#TTNNN

where

  • SSSSSSS is the system name
  • TT is the process type
  • NNN is a serial number for the process type
Type

Server
Start Time Date/time on which the server was started.
End Time Date/time on which the server terminated.
Status Status icon and server status that indicate whether a server process is active or not.
Message Additional information that describes the reason for the error.

ClosedExecutable Objects

Please see Execution Data of Executable Objects for details.

Storing Execution Data Permanently

The execution data of servers, agents and executable objects is constantly recorded and archived. It is not possible to disable this function.

You can specify that the collected data should be stored permanently. The administrator can use the UC_STATISTIC_OPTIONS variable to determine whether execution data should be kept after a user has logged off correctly. All security-relevant data (e.g. attempts to log on with an invalid password) is stored. By default, the execution data of user sessions are also stored.

See also: