Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

To use this feature, the user logged into the source Controller must have the ops_promotion_admin role, or be granted permission to the Promote command and execute permission to one or more promotion targets.

The Promotion Read Permission Required Universal Controller system property specifies whether or not the ops_promotion_admin role additionally requires Read permission, on the source Universal Controller, for any record type being promoted.

Also, the user ID and password specified for the Promotion Target must be for a valid user on the target Controller with the ops_promotion_admin or ops_promotion_accept_bundle role.

The Promotion Accept Bundle Create/Update Permission Required Universal Controller system property specifies whether the ops_promotion_admin role additionally requires Create (or Update) permission, on the target Universal Controller, for any record type being promoted.

Overview

Promoting a Bundle means copying all of the records in a Bundle from a source Controller to a target Controller.

You also can promote one or more individual records without bundling them.

For every record in a bundle being promoted, and every record being promoted individually, the following associated data is always included in the promotion.

  • If you promote a workflow, all of the tasks in the workflow are also promoted.
  • If you promote a task (including a workflow), all variables, virtual resource dependencies, actions, notes, etc. are included in the promotion.
  • If you promote an application, its associated start, stop, and query tasks are included in the promotion.
  • If you promote a calendar, its associated custom days are included in the promotion.
     

Note

If you promote a trigger whose Forecast field has been checked so that the Controller calculates the date and time when this trigger will be satisfied for the next number of days, the Forecast field will not be checked for that trigger on the target system.

Promoting a Bundle

Step 1

From the Bundles & Promotion navigation pane, select Bundles. The Bundles list displays.
 

Step 2

Locate the Bundle that you want to promote and either:Action menuAction menuThe Promote Bundle pop-up dialog displays.
 

Step 3

If the selected Bundle record specifies a Default Promotion Target, the name of that Target displays in the Promotion Target field.

You can change, or select, the Promotion Target by selecting any Target from the drop-down list.

Step 4

The default login User and Password are provided from the selected Promotion Target record. If you want to override the defaults, click Override User/Password and type in the new information.

Step 5

If the promotion contains new or modified Universal Templates, click Allow Universal Template Changes; otherwise, the promotion will not succeed. See Diagnosing Promotion Failures for details.

Step 6

If you want to schedule the promotion of the bundle at a later time, click Schedule.

Step 7

Click Submit.
 
The Controller logs in to the target machine specified in the URI field of the Promotion Target record and copies the bundled records to the target Controller. Based on the specified Agent mapping, the target Agent replaces the source Agent where required.
 
If you scheduled the promotion to be run at a later time, a record of the promotion is created in the Promotion Schedules list.
 

Note

The promotion process creates audit records on the source and target machine. On the target machine, the Controller also creates a Promotion History record. For details, see Promotion History and the Restore Option.

Scheduling a Bundle Promotion

You can create a promotion schedule for a Bundle so that it will automatically be promoted at a specified date and time.
 

Step 1

From the Bundles & Promotion navigation pane, select Bundles. The Bundles list displays.
 

Step 2

Locate the Bundle that you want to promote and either:Action menuAction menuThe Promote Bundle pop-up dialog displays.
 

Step 3

The default login ID and password are provided from the Promotion Target record, if specified. If you want to override the default, click Override User/Password and type in the new information.

Step 4

If the promotion contains new or modified Universal Templates, click Allow Universal Template Changes; otherwise, the promotion will not succeed. See Diagnosing Promotion Failures for details.

Step 5

Click Schedule. Additional fields display on the Promote Bundle pop-up dialog that let you create a promotion schedule.
 

Step 6

Select a Date and Time when you want the bundle to be promoted.

Step 7

If you want to schedule the promotion using the current Bundle records, select Create Snapshot. When you submit the schedule, the current Bundle records are collected immediately and promoted at the scheduled time. Any changes to Bundle records between the time that the promotion was scheduled and the time that the promotion was performed are not promoted.
 
If you want to schedule the promotion using the Bundle records collected dynamically at the time of the scheduled promotion, do not select Create Snapshot.

Step 8

If you want to send a System Notification on the success and/or failure of the promotion, select one of the following from the System Notification drop-down list:

  • Operation Failure (default)
  • Operation Success/Failure
  • Operation Success

If you do not want to send a System Notification, select – None --.
 

Note

Promotions without a specified Schedule will run immediately. Real-time notifications will be displayed in the Universal Automation Center Console, rather than through System Notifications.

Step 9

Click Submit. A record of the promotion schedule is listed in the Promotion Schedules list.
 
After a scheduled promotion has completed, it will remain on the list (where it can be rescheduled to run again) for the number of days specified by the Promotion Schedule Retention Period In Days Universal Controller system property.

Promoting One or More Individual Records

The Controller also allows you to promote records of the same type to a target machine without going through the process of creating a Bundle.

Note

You can only create a Promotion Schedule for a Bundle of records, not one or more individual records.

Step 1

Display the records list for the type of record that you want to promote.

Step 2

Select the record(s) that you want to promote.
 
To promote a single record, either:Action menuAction menuThe Promote dialog displays, prompting you to select the Promotion Target from a drop-down list. Select the target.
 

 
To promote multiple records, either:
 
Ctrl-click the records you want to promote, right-click any of the selected records to display an Action menu, and then click Promote. The Promote dialog displays, prompting you to select the Promotion Target from a drop-down list. Select the target.
 

 
OR
 
From any tasks list, right-click any column header for the list, display the Action menu, and select Run Command On Filtered > Promote.... The Promote dialog displays, prompting you to select the Promotion Target from a drop-down list. Select the target.
 

Step 4

The default login ID and password will be provided from the Promotion Target record. If you want to override the default, click Override User/Password and type in the new information.

Step 5

Select Exclude on Existence if you want to specify record types in the promotion payload that will not be updated if they exist on the target payload. You can:The Bundle Exclude On Existence Picker Default Universal Controller system property specifies which record types, if any, will be selected by default in the drop-down list.

Step 6

Select Follow References if you want to dynamically include records that are referenced by these records. (See Records Promoted When Follow References is Selected or Not Selected.)

Step 7

If the promotion contains new or modified Universal Templates, click Allow Universal Template Changes; otherwise, the promotion will not succeed. See Diagnosing Promotion Failures for details.

Step 8

Click Submit. The Controller logs in to the target machine specified in the URI field of the Promotion Target Record and copies the selected records to the target machine.

This process creates audit records on the source and target machines. On the target machine, the Controller also creates a Promotion History record.

Promoting Universal Tasks and Universal Templates

The following conditions apply for the promotion of Universal Tasks and Universal Templates:

Subject

Condition

Universal Template

For any Universal Task included in a promotion, its corresponding Universal Template automatically will be included in the promotion.

Universal Template Changes

In order to promote a new Universal Template or a Universal Template change, the promotion must be performed with the Allow Universal Template Changes field enabled on the Promote Bundle... dialog or the Promote... dialog; otherwise, the promotion will fail. See Diagnosing Promotion Failuress for details.
 
The Allow Universal Template Changes field is visible on each dialog only if the user has the ops_admin role role or the ops_universal_template_admin role, and at least one Universal Template is configured within the source system.

Universal Template Changes

Universal Template changes will be listed under under Non-Restorable Items in the Promotion History Report.

Change Restrictions

All Restrictions on Universal Template Changes apply to any change(s) being applied on a target system with a promotion.

Promotion Failure

Any promotion that includes a Universal Task and/or a Universal Template will fail if the target system is not Universal Controller 6.4.0.0 or later.

Promotion Restore

Any promotion that includes Universal Template changes cannot be restored using the Restore Unchanged or Restore All operations of Promotion History.

  • Promotion History for the promotion will be flagged as not restorable; the Can Restore field in the Promotion History Details for the promotion will not be selected.
  • Any Universal Template change will be recorded as a Promotion History Item, where the New Version, Previous Version, and Source Version fields are blank.

Follow References

If the Follow References field is enabled for a promotion, the following references are followed for Universal Templates: Agent Cluster (or Broadcast Cluster), Credentials, and Credential Field Type (if a default value has been defined). See Records Promoted When Follow References is Selected or Not Selected.

Follow References

If the Follow References field is enabled for a promotion, the following references are followed for Universal Tasks: Agent Cluster (or Broadcast Cluster), Credentials, and any fields that match a Universal Template Credential Field Type, in additional to the references inherited by all Task Types. See Records Promoted When Follow References is Selected or Not Selected.

Child Audit

For any promoted Universal Template change, a child audit captures the Universal Template Properties, Fields, and Field Choices in the Before, After, and Difference fields.

Child Audit

For any promoted Universal Task, a child audit captures the Before, After, and Difference fields based on the original, incoming, and combination of original and incoming Universal Templates, respectively.

Diagnosing Promotion Failures

Unable to render {include} The included page could not be found.

Promotion Audit Records

Whenever a Bundle or an individual record is promoted to a target machine, the Controller creates audit records on both the source and target machines.

On the source machine, each time you promote a record or a Bundle, the Controller creates a single audit record for that event. If you promoted a Bundle, the audit description is PROMOTE BUNDLE; if you promoted a single record or multiple records, the audit description is PROMOTE.

On the target machine, the Controller creates an ACCEPT BUNDLE audit record, along with child audit records associated with that promotion (either record[s] or a Bundle). These may include UPDATE commands for records that existed on the target already and CREATE commands for records that did not previously exist.

The following examples show an ACCEPT BUNDLE record on a target machine and a Child Audit record for a task included in the Bundle promotion.
 


 


 

For detailed information on audit record, see Audits.

  • No labels