Information Technology Reference
In-Depth Information
An Orchestrator deployment consists of the following parts:
■
Management server
This server manages the runbook servers. You use the man-
agement server to distribute integration packs to runbook servers and runbook de-
signers. The management server also manages communication between the runbook
designers, runbook servers, and the orchestration database. There is only one manage-
ment server in an Orchestrator deployment
■
Runbook server
This server runs Orchestrator runbooks. Each runbook server can
run up to 50 runbooks concurrently. You can alter this number using the Runbook
Server Runbook Throttling tools, but should monitor the runbook server's resource
requirements. You can have multiple runbook servers in an Orchestrator deployment,
with no maximum limit to the number of runbook servers specified in the Orchestrator
documentation.
■
Runbook Designer
This designer allows you to build and test runbooks. The inter-
face allows you to build runbooks by dragging and connecting activities that are avail-
able in integration packs. The Runbook Designer is shown in Figure 1-2.
FIGURE 1-2
Runbook Designer
■
Orchestration database
Hosted on a Microsoft SQL Server instance, the orchestra-
tion database stores configuration data, policies, and log information.
■
Orchestration console
A web interface that users can use to list, control, and view
runbooks.
