To better understand Orchestrator, we need to know the basics of it. We can start off with the fact that it has seven components. The automated workflow is called a Runbook. The seven components are as follows:
Management Server: This component coordinates the communication in the Orchestrator architecture between all the other components and it cannot be redundant as there can be only one Management Server per Orchestrator deployment.
Orchestrator Database: As the name suggests, this is composed of a database that will be stored in a Microsoft SQL Server, and it will keep all the Runbooks in it, the status of those Runbooks, and keep the security delegation in place.
Runbook Server: This is the component responsible for executing the Runbooks instances. When a Runbook is invoked, a copy of it is transmitted from the database into the Runbook Server, and then it's executed. The first Runbook Server to get installed gets the primary role.
Runbook Designer: This component is the interface between you and the Orchestrator engine for creating the Runbooks. It has a subcomponent called Runbook Tester for you to use in order to validate the Runbooks you create.
Orchestrator Console: This is a console that runs on Silverlight that uses the Orchestrator Web Service to communicate with Orchestrator.
Orchestrator Web Service: This is the interface that allows applications to connect with Orchestrator and allows them to perform tasks through it, such as starting and stopping Runbooks, or viewing the status.
Orchestrator Deployment Manager: The Deployment Manager is a tool used to deploy Integration Packs (IPs), Runbook servers, and Runbook Designers. This is a subcomponent of the Management Server.