Export and import runbooks
Export and import runbooks by sending requests to the HTTP API. You can use existing tools to send requests, for example cURL, Postman for Chrome, or RESTClient for Firefox.
Before you can send requests, you need to create an API key for authentication. See API Keys for instructions how to create an API key.
In addition, determine the fully qualified domain name and the port where the runbook service is
running (which might be different from the location where the Netcool/OMNIbus DASH UI server is
running). The base URL for sending API requests has the format
https://<fullyQualifiedDomainName>:<rba-rbs-port>, for example,
Export RunbooksThe following two calls create output, which can be imported again.
When enabling the option exportFormat via the query parameter, the usual output of the command is replaced by an array of JSON objects. These JSON objects can be used to create the runbooks by using the import API endpoint. The following call is an example:
Replace <APIKeyUsername> with your username and <APIKeyPassword> with your password.
curl -u <APIKeyUsername>:<APIKeyPassword> https://myhost.mycompany.com:3005/api/v1/rba/runbooks?exportFormat=true
Replace <RunbookId> with the ID of the runbook. You can retrieve this ID, for example, from the Edit Runbook window. The following call is an example:
Replace <APIKeyUsername> with your username and <APIKeyPassword> with your password. Replace <RunbookId> with the ID of the runbook.
curl -u <APIKeyUsername>:<APIKeyPassword> https://myhost.mycompany.com:3005/api/v1/rba/runbooks/<RunbookId>?exportFormat=true > exportedRunbook.json
The following call is an example:
Replace <APIKeyUsername> with your username and <APIKeyPassword> with your password. Note:
curl -H "Expect:" -H "Content-Type: application/json" -u <APIKeyUsername>:<APIKeyPassword> -d@./exportedRunbooks.json https://myhost.mycompany.com:3005/api/v1/rba/runbooks/import
./exportedRunbooks.jsonis the output file that is created from the previous example.
jq, to split the
exportedRunbooks.jsoninto several files named
exportedRunbooks.json.ab, and so on, with 100 runbooks per file. These files can then be imported separately, thereby circumventing the 1 MB limit:
Depending on the size of your runbooks, you might need to split your
cat exportedRunbooks.json | jq . -c | split -l 100 --filter='jq . -cs > $FILE' - exportedRunbooks.json.
exportedRunbooks.jsonfile up into even smaller chunks of runbooks. In this case, simply modify the
-l 100argument of the split command to an even smaller number of runbooks per file.
General Notes on export and import
- Exporting runbooks returns the data of referenced automations inline. These automations are created new when the runbook is imported.
- Import actions do not overwrite existing runbooks, automations, or both.
- Exporting multiple runbooks at once will consolidate automations that are referenced by more than one runbook and only create the minimum necessary number of new automations.
- Imported runbooks are in draft state and do not retain any kind of version or execution. The user performing the import action is visible as the runbook creator.
For more information about creating an API key, see API Keys.
For more information about the API, see https://rba.us-south.cloudeventmanagement.cloud.ibm.com/apidocs-v1.