In this post series I will go through Microsoft System Center Orchestrator 2012 Deployment and Configuration in Step by Step format with screenshots, and will go into details of the product to help you better understand how you can get benefits from this powerful product.
In this post I will go through Orchestrator System Requirements based on RC version that can be subject to change in future version.
Orchestrator Deployment Basics
A basic deployment of Orchestrator consists of the following features:
The Management server is the communication layer between the Runbook Designer and the database.
|A Runbook Server is where an instance of a runbook runs. Runbook Servers communicate directly with the Orchestrator database. You can deploy multiple runbook servers per Orchestrator installation for capacity and redundancy|
|The database is a Microsoft SQL Server database that contains all of the deployed runbooks, status of running runbooks, log files, and configuration data for Orchestrator|
The Runbook Designer is the tool used to build, edit, and manage Orchestrator runbooks. For more information on the Runbook Designer, see Using Runbooks in System Center 2012 – Orchestrator Release Candidate.
The Runbook Tester is a runtime tool used to test runbooks developed in the Runbook Designer. For more information on the Runbook Tester, see How to Test a Runbook in Using Runbooks in System Center 2012 – Orchestrator Release Candidate.
The Orchestration console enables you to start or stop runbooks and view real-time status from a web browser. For more information on using the Orchestration console, see the Using the Orchestration Console in System Center 2012 – Orchestrator Release Candidate
|Orchestrator web service||
The Orchestrator web service is a REST-based service that enables custom applications to connect to Orchestrator to start and stop runbooks, and retrieve information about operations using custom applications or scripts. The Orchestration console uses this web service to interact with Orchestrator.
The Deployment manager is a tool used to deploy integration packs (IPs), Runbook servers, and Runbook Designers. For more information on this tool, see the Deploying System Center 2012 – Orchestrator Release Candidate.
For System Requirements we have two scenarios, Single Server hold all Orchestrator Roles and individual features distributed on different Servers,I will focus on this port on first scenario for Single Server,
Single Server Hardware Requirements:
The following minimum hardware configuration is required for a full installation of Orchestrator:
- Minimum 1 gigabyte (GB) of RAM, 2 GB or more recommended (4 GB recommended)
- 200 megabyte (MB) of available hard disk space (1 GB disk space recommended)
- Dual Core Intel 2.1GHz+ or better
Single Server Operating System Requirements:
Windows 2008 R2 is the supported Operating System for Management Server, Orchestrator web Service, Runbook Designer, and Runbook Sever.
Single Server Software Requirements:
The following software is required for a full installation of Orchestrator on a single computer:
- Microsoft SQL Server 2008 R2 – Orchestrator requires only the basic SQL Server features found in the Database Engine Service. No additional features are required.
- Microsoft Internet Information Services (IIS) – Orchestrator Setup enables IIS if it is not enabled.
- Microsoft .NET Framework 3.5 SP1 – Orchestrator Setup installs and enables .NET Framework 3.5 SP1 if it is not installed and enabled.
- Microsoft .NET Framework 4.
- Management servers and Runbook servers installed on the same computer must use the same database. The Management server must run as a 32-bit application.
- It is recommended to have Orchestrator Server Joined to Active Directory Domain.
- On first use of Orchestrator console, you are prompted to install Microsoft Silverlight 4 on the computer if it is not already installed.
In the coming post I will go through Orchestrator 2010 Step by Step in details with screenshots.
- Orchestrator 2012 Deployment & Configuration Step by Step – Part 1 “Overview and Architecture” can be found here: http://blogs.technet.com/b/meamcs/archive/2011/11/02/orchestrator-2012-deployment-amp-configuration-step-by-step-part-1-overview-and-architecture.aspx
- Orchestrator 2012 Deployment & Configuration Step by Step – Part 2 “System Requirements” can be found here: http://blogs.technet.com/b/meamcs/archive/2011/11/02/orchestrator-2012-deployment-amp-configuration-step-by-step-part-2-system-requirements.aspx
- Orchestrator 2012 Deployment & Configuration Step by Step – Part 3 “Installation” can be found here: http://blogs.technet.com/b/meamcs/archive/2011/11/05/orchestrator-2012-deployment-amp-configuration-step-by-step-part-3-installation.aspx
- Orchestrator 2012 Deployment & Configuration Step by Step – Part 4 “Build, Testing and Monitoring a Runbook” can be found here: http://blogs.technet.com/b/meamcs/archive/2011/11/06/orchestrator-2012-deployment-amp-configuration-step-by-step-part-4-build-testing-and-monitoring-a-runbook.aspx
- Orchestrator 2012 Deployment & Configuration Step by Step – Part 5 “Integration Pack” can be found here http://blogs.technet.com/b/meamcs/archive/2011/11/19/orchestrator-2012-deployment-amp-configuration-step-by-step-part-5-integration-pack.aspx?wa=wsignin1.0