Information Technology Reference
In-Depth Information
loops, and error handling tasks. Each integration pack that you import into Orchestrator
increases the number of activities that you can include in your runbooks.
Keep the following in mind when creating Orchestrator runbooks:
Provide meaningful names for activities. You can rename activities after you drag them
to the designer workspace. By renaming activities with descriptive names, then you can
quickly understand what tasks a runbook is designed to accomplish. For example, with
the runbook in the example above, you might rename the Monitor Service activity “Is
the VMM Service Stopped” and the Start/Stop Service activity “Start the VMM Service.”
Minimize the number of activities that are performed in a runbook. You can call run-
books from within runbooks. This modular approach to creating runbooks will simplify
the process of troubleshooting them.
Configure runbooks to write logs to external files rather than to the orchestration
database.
Orchestrator runbooks run according to configured schedules. You create each run
separately, and then assign the schedule to the runbook. You create runbook schedules in
the Schedules node, under Global Settings, in the Runbook Designer as shown in Figure 1-4.
Creating a runbook schedule involves assigning a name to the schedule, specifying what days
of the week or days of the month the schedule applies to, and specifying which hours the
schedule applies to.
FIGURE 1-4 Runbook schedule
 
Search WWH ::




Custom Search