User Guide > Objects > Alphabetical Listing > Rollback Tab

Rollback Tab

The Rollback tab is an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task-specific tab that is available in every executable object that can be included in a workflow.

The Rollback tab can be used to define actions that store the taskAn executable object that is running. Tasks are also referred to as activities. (= Backup) and restore it (= Rollback). These settings are only useful when the object runs in a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."] because you can only start a rollback process within a workflow.

The backup and rollback functions are especially designed to undo erroneous installation and deploymentThe deployment of a single application revision to an environment within a single activity. processes that are defined in the Automic Release AutomationAutomic Release Automation (ARA), is an end-to-end solution for planning, coordinating and automating software release processes, including automated deployment of applications across large-scale server environments and covers all mentioned use cases. [Formerly called "Application Release Automation", "Release Manager" and "Deployment Manager"] but processed using the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..

Backup actions will always be processed before the object is processed, and Rollback actions can only be started via workflows. For more information, see the related documentation.

Field/Element Description
Enable Rollback

Use this to activate or deactivate the rollback settings.

When this option is deactivated, all the fields of this tab are disabled.

Custom Rollback

A userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management.-defined rollback actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios. allows you to roll back tasks through user-defined executable objects.

The following object variablesPlaceholder for values that are stored in an object's "Variables & Prompts" tab/section. are available for the processing of backup and rollback tasks:

Note that variables of the same name will be overwritten in the Backup or Rollback object.

Backup

Specify an executable object that is responsible for the backup process.

If you specify a Backup object, it will always automatically run before the task runs, regardless of how the object is activated.

The actions and steps that must be defined in the Backup object depend on the processes and actions of the related task. Note that you must define them manually. For example, if you use an object to update your databaseA database is an organized collection of data including relevant data structures., it is useful to include a database using the Backup object.

After the backup task has successfully ended, the object variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. &RB_CBACKUP_RUNID# will automatically be created within the task that triggers the backup process. This variable stores the RunIDShort for "run number". It is a number that provides unique information about a task's execution. The RunID can include 7 to 10 digits. It is assigned by the Automation Engine component . of the backup task.

Rollback

Specify an executable object that is responsible for the rollback process.

The definition of the Rollback object depends on the current object or the Backup object and must be made manually. The Rollback object's basic task is to undo modifications in the case of an error in order to ensure that a previous working statusThis represents the condition of a task (such as active, blocked, generating). will be restored. For example, if the Backup object creates a database backup, the Rollback object should be able to restore this backup.

The Rollback object will be processed when the task starts in rollback mode which is only possible in a workflow.

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH