Importing Runbooks from System Center Orchestrator 2012
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 - Service Manager
System Center 2012 – Service Manager integrates with System Center 2012 - Orchestrator, providing the capability to synchronously invoke runbooks from within Service Manager through the use of workflows. This capability provides integration between Orchestrator automation capabilities with the Self-Service Portal, as well as business modeling capabilities. When this capability is combined with the Service Manager Service Catalog stack, it is possible to create an end-user-facing request offering with an Orchestrator runbook as part of the fulfillment process.
Activities that make up a service request can be mapped to runbook activities, which in turn are mapped to an Orchestrator runbook. For example, the parameters that are necessary for a custom start activity to invoke a runbook in Orchestrator, such as a computer name, can go into as Service Manager as objects. You start this process by importing runbook objects into the Service Manager database using an Orchestrator connector. After you import runbooks into Service Manager, they appear in the Library node in the Administration workspace.
Note
Make sure that you have installed the ADO.NET Data Services Update for .NET Framework 3.5 Service Pack 1 (SP1), as described in Microsoft Knowledge Base article 976127. For more information, see ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2.
Importing Runbook Topics
How to Create an Orchestrator Connector
Describes how to create an Orchestrator connector.
How to Synchronize an Orchestrator Connector
Describes how to synchronize an Orchestrator connector.
How to Disable and Enable an Orchestrator Connector
Describes how to temporarily disable and then re-enable an Orchestrator connector.
Other Resources for This Component