Monitoring Application Deployments

As an Operator, you use the Executions view to see the list of general and deployment workflow executions that have been triggered. From this view, you can open the Workflow Monitor to monitor the execution process and ensure that the Application is being properly deployed. You also use dashboards and widgets to keep track of application deployments and key performance indicators.

This page includes the following:

Viewing Application Deployments

To View the Application Deployments

  1. Open the Process Monitoring perspective.
  2. Navigate to Release Automation > Executions. The list of Workflow Executions is displayed. The following information is shown by default:
    • ID
    • Application
    • Environment
    • Workflow
    • Package
    • Profile
    • Click Evaluate Properties to check if the dynamic properties are defined correctly and avoid errors that could arise during the deployment. For more information, see Evaluation Settings
    • Status

      • Waiting statuses

        • Waiting for approval

          The Workflow has been executed, but there are approvals pending, so the execution cannot run.

        • Waiting for start

          The Workflow has been executed, potential approvals have been made, but the planned start time has not passed yet.

        • Waiting for manual confirmation

          The Workflow has been executed with the option 'Manual confirmation required' - approvals have been made, the start time window is open but the execution has to be confirmed by a specified user or group.

      • Active status

        • Active

          The execution is actively running.

      • Blocked status

        • Blocked

          The execution is blocked (for example, due to a problem in an action).

      • Final statuses

        • Finished

          The execution has ended successfully.

        • Canceled

          The execution has been canceled.

        • Failed

          The execution has failed.

    • Planned Start
    • User

    Tip: Click the downward arrow next to the last column to the right to select and display additional columns.

    Notes:

    • By default, you can filter the list by Application, Package, and Profile. Click Add Filter Criteria to show additional fields.
    • Saved filters are private (they are not available for other users).
    • From this view, you can archive and restore one or more executions in bulk. For more information, see Archiving Entities
    • You can also export the list of executions to a csv file. For more information, see Exporting Tables to CSV
    • The maximum number of executions displayed is defined in the COMBINED_ACTIVITIES_LIMIT variable. For more information, see: ACTIVITIES_LIMIT Parameters.

Custom Views

You can save your preferred table structure using Custom Views. For more information, see Working with Custom Views.

Audit with Execution Reports

CDA provides a central view and enables to audit the complete process history for retrospective analysis and audits.

A history is automatically tracked for all workflow executions and on changes of properties of CDA objects. These include creation, property changes or status changes and attempted runs for the executions. Details of each history record include updated components and variable values.

Viewing and Downloading an Execution Report

You can download and view reports for workflow executions in a final state:

  1. Open the Process Assembly perspective.
  2. Select the Executions tab.
  3. Double-click an execution.
  4. Navigate to History > History Records.
  5. Click Show details to view the report or Download Reports to download it. For more information, see Statistics & History

Execution Report File Structure

The report file includes the following sections:

Header

The header section provides general information for the execution.

--- HEADER --------------------------------------------------------

Workflow: <Workflowname>

Application: <Applicationname>

Package: <Packagename>

Profile: <Profilename>

Environment: <Environmentname>

Start time: <Starttime>

End time: <Endtime>

Requested by: <User name>

Status: <Status>

-------------------------------------------------------------------

Example:

--- HEADER --------------------------------------------------------
Workflow: AraDeploy
Application: ARA51
Package: Load_c53502ac-93c2-453a-a457-19ddecc96825
Profile: QAtest1
Environment: QAtest1
Start time: 2018-06-02T13:31:39Z
End time: 2018-06-02T13:32:29Z
Requested by: 4/ARA/ARA
Status: Finished
--------------------------------------------------------------------

Approvals

This section lists all approval requests of the respective execution.

 --- APPROVALS -----------------------------------------------------

<all approval requests on this execution, sorted by date ascending>

-------------------------------------------------------------------

Example:

--- APPROVALS -----------------------------------------------------
2018-06-02T10:09:32Z    Approved by 4/ARA1/ARA
-------------------------------------------------------------------

History

The execution history section consists of all history records on the execution.

--- HISTORY -------------------------------------------------------

<all history records on this execution, sorted by date ascending>

-------------------------------------------------------------------

Example:

--- HISTORY --------------------------------------------------------
2018-06-02T13:31:33Z     Execution "AraDeploy" was created by 4/ARA/ARA.
2018-06-02T13:31:33Z     The workflow execution "AraDeploy"
			  was scheduled for "2018-06-02 13 by 4/ARA/ARA.
2018-06-02T13:31:33Z     The status of execution "AraDeploy" 
			  was changed to "Active".
2018-06-02T13:31:43Z     The workflow "AraDeploy" was executed 
			  by 4/ARA/ARA with run ID 137376276.
2018-06-02T13:34:01Z     The status of execution "AraDeploy" 
			  was changed to "Finished".
--------------------------------------------------------------------

(line breaks for formatting purposes only)

Deployment XML

The deployment XML section consists of the plain XML data related to the deployment.

--- DEPLOYMENT XML ------------------------------------------------

<deployment XML>

-------------------------------------------------------------------

Note: Password variables are displayed as ****

Overview

The overview section consists of workflow or action name, run id and the state of the workflow/action.

Important! Run id and execution id refer to different concepts. The run id is generated by the Automation Engine when the execution starts. The execution id is the key that uniquely identifies a deployment in CDA.

--- OVERVIEW ------------------------------------------------------

<NAME> | <RUNID> | <STATUS>

...

-------------------------------------------------------------------

Reports

The reports section consists of all detail reports for each workflow or action of this workflow.

--- REPORTS ------------------------------------------------------

RunID: <RUNID> (<NAME>)

Type: <WORKFLOW> or <ACTION>

Status: <STATUS>

Started: <STARTTIME>

Ended: <ENDTIME>

 

<REPORTTYPE>:

<FULLREPORT>

------------------

...

-------------------------------------------------------------------

Example:

--- REPORTS --------------------------------------------------------
RunID: 137376276 (RM.AUTOMIC.ARADEPLOY.DEPLOY1)
Type: WORKFLOW
Runbook: RM.AUTOMIC.ARADEPLOY.DEPLOY1
Status: ENDED_OK - ended typically
Started: 2018-06-02T11:32:00Z
Ended: 2018-06-02T11:33:00Z
--------------------------------------------------------------------
RunID: 137376395 (IIS_TO_IISTARGET14)
Type: WORKFLOW
Runbook: IIS_TO_IISTARGET14
Status: ENDED_OK - ended typically
Started: 2018-06-02T11:32:00Z
Ended: 2018-06-02T11:32:00Z
--------------------------------------------------------------------

See also: