Exporting and Importing Dynamic Runbooks

Beginning with Oracle Enterprise Manager 13c Release 5 Update 11 (13.5.0.11), you can export and import published Runbook definitions, thus significantly enhancing Runbook reuse and sparing administrators from having to develop Runbooks from scratch.

Note:

You can only export/import published Runbooks. Runbook drafts and Runbook sessions cannot be used as they have contextual properties that are specific to the Enterprise Manager system in which they are authored. They will not be portable across Enterprise Manager installations.

Usage Guidelines

Exporting/importing published Runbooks across Enterprise Manager versions:

  • Export from an older Enterprise Manager version and import to a newer Enterprise Manager version will always work.
  • Export from a newer Enterprise Manager version and import to an older Enterprise Manager version will only work if step types are compatible (supported in both versions).

The following table lists the currently available step types and the corresponding minimum compatible Enterprise Manager release.

Step Type Applies to EM release
Note Enterprise Manager 13c Release 5 Update 7 and later
Target SQL Enterprise Manager 13c Release 5 Update 7 and later
Repository SQL Enterprise Manager 13c Release 5 Update 7 and later
Metric Enterprise Manager 13c Release 5 Update 7 and later

Republish Runbooks authored before Enterprise Manager 13c Release 5 Update 11

For published Runbooks created using Enterprise Manager 13c Release 5 Update 7 thru 10, you must republish the Runbooks you plan on exporting/importing. This ensures that Runbook properties are up-to-date and compatible across Enterprise Manager deployments.

Note:

To republish a Runbook, simply create a new draft from an existing published Runbook, optionally edit the draft, and then publish Runbook.

Required User Privileges

In order to export or import a published Runbook, you must have at least one of the following privileges:

  • CREATE_RUNBOOK—Allows you to create and publish Runbooks.
  • MANAGE_RUNBOOK—Allows you to perform administrative operations, such as deleting/showing/hiding Runbooks, or viewing Runbook session data.

For more information, see Types of Dynamic Runbook Users.

Export a Published Runbook

  1. Navigate to the Published page. From the Enterprise menu, select Monitoring and then Runbooks.
  2. Select Export from the Actions menu for the Runbook you want to export. An Export dialog displays with the default Export Filename. By default, the name of the currently published Runbook is used, however, you can enter a new filename.
  3. Click OK. A Runbook definition JSON file is saved to your local file system.

Import a Published Runbook

  1. Navigate to the Published page. From the Enterprise menu, select Monitoring and then Runbooks.
  2. Click Import. The Import a Published Runbook dialog displays
  3. Either drag and drop a Runbook definition file directly into the dialog, or click the Drag and Drop region to open a file browser to select a file. The imported definition file will immediately appear in the Published Runbook table.
  4. Click Close.

Note:

The user importing a Runbook definition becomes the new owner of that Runbook.