System Center Orchestrator 2012: Product architecture

The goal of this post is to explain what are the components that make up the architecture of System Center Orchestrator 2012.

Starting from the following picture you can see how the architecture of Orchestrator is characterized by the presence of several components in relation to each other:

Figure 1 – Product architecture

We carry over the main features of each of these components:

Orchestration database – The database, based on Microsoft SQL Server, contains all configurations of Orchestrator, runbook data and log files.

Runbook Server – A Runbook Server is where a ’ instance of a runbook is performed. Runbooks servers communicate directly with the Orchestrator database and you can deploy multiple Runbook Server for each implementation of Orchestrator in order to increase the processing capacity and have a redundancy mechanism.

Management server – The Management server is the layer of communication between the Runbook Designer and database.

Runbook Designer – The Designer Runbook is the tool used to build, Edit and manage runbook.

Runbook Tester – Using the Runbook testers can test runbooks that were developed using the Runbook Designer.

Orchestration console – The web console allows you to manage runbook execution status and view their status in real time using a web browser.

Web service Orchestrator – The web service Orchestrator allows other applications to connect to Orchestrator. In this way, ad hoc applications can interact with Orchestrator managing runbook status and retrieving information about operations performed. Even the Orchestration console uses this web service.

Deployment Manager – The Deployment Manager is the tool that is used to deploy the Integration Pack (IP), runbooks Server and runbooks Designer.

All of these roles can be hosted by a single server, or they can be distributed in a timely manner on multiple systems.


Please follow and like us: