Using the Orchestration Console in System Center 2012 R2 Orchestrator

Size: px

Start display at page:

Download "Using the Orchestration Console in System Center 2012 R2 Orchestrator"

Janis Smith
5 years ago
Views:

1 Using the Orchestration Console in System Center 2012 R2 Orchestrator Microsoft Corporation Published: November 1, 2013 Applies To System Center Orchestrator Orchestrator in System Center 2012 SP1 System Center 2012 R2 Orchestrator Feedback Send suggestions and comments about this document to sc2012docs@microsoft.com.

2 Copyright Information This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes Microsoft Corporation. All rights reserved. Microsoft, Access, Active Directory, ActiveSync, ActiveX, Authenticode, Bing, BitLocker, Excel, Forefront, Hyper-V, Internet Explorer, JScript, Microsoft Press, MSDN, Outlook, SharePoint, Silverlight, SoftGrid, SQL Server, Visio, Visual Basic, Visual C++, Visual Studio, Win32, Windows, Windows Intune, Windows Mobile, Windows PowerShell, Windows Server, Windows Server System, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners. Revision History Release Date October 17, 2013 November 1, 2013 Changes Original release of this guide. Minor updates for this guide.

3 Contents Using the Orchestration Console in System Center Orchestrator... 4 Overview of Orchestration Console How to Start the Orchestration Console... 8 How to Work With Runbooks in the Orchestration Console... 9

4 Using the Orchestration Console in System Center Orchestrator The Orchestration console is a web-based tool with which an operator can perform the following functions in System Center Orchestrator: View a list of runbooks and runbook servers. View the current running status and history of runbooks. View high-level definition of runbooks. Start and stop runbooks. View events that runbook servers and the management server create. The functions that you can perform in the Orchestration console is a subset of the functions in the Runbook Designer, but you can run the Orchestration console from any computer with a browser without requiring installation of a separate tool. It is intended for users who are required to manage the operation of runbooks but are not required to modify them. To provide users with this access, you have to give them permission to specific runbooks or folders. This process is described in Runbook Permissions. Orchestration console topics Overview of Orchestration Console Describes the basic features of the Orchestration console. Describes the minimum browser requirements for using the Orchestration console. How to Start the Orchestration Console Describes how to start the Orchestration console. How to Work With Runbooks in the Orchestration Console Describes how to start, stop, and manage runbooks from the Orchestration console. Other resources for this product TechNet Library main page for System Center Orchestrator 2012 Getting Started with System Center Orchestrator Release Candidate Deploying System Center Orchestrator Release Candidate Administering System Center Orchestrator Release Candidate Integration Packs for System Center Orchestrator Release Candidate Using Runbooks in System Center Orchestrator Release Candidate Runbook Activity Reference for System Center Orchestrator Release Candidate 4

5 Overview of Orchestration Console The Orchestration console is comprised of a single webpage with multiple panes that are described in the following sections. Navigation pane The navigation pane is the left pane in the Orchestration console where you can click the workspace that you want to use. Depending on the workspace you click, you can view specific data and use specific options. The following workspaces are available in the navigation pane. Runbooks workspace The Runbooks workspace lets you start and stop runbooks. You can also view information such as the jobs and instances created for each runbook and their definition. Summary The Summary tab is displayed for any folder or runbook selected in the Runbooks workspace. This tab displays summary information for the jobs and instances of the selected runbook or for all of the runbooks in the selected folder. The statistics that are displayed are updated every 10 minutes so that activity performed within that time might not be reflected in the numbers until they are updated. Each column in the Summary displays the number of jobs and instances that finished with a particular status (Succeeded, Warning, or Failed) within the last hour, the last day, and the last week. For instances, the number of instances that are currently in progress are also displayed. For jobs, the number of jobs that have been created and that are currently queued are also displayed. Runbooks The Runbooks tab is displayed when you select a folder in the Runbooks workspace. It lists the runbooks contained in the selected folder and specifies the status of any running jobs and instances from each. To select one of these runbooks and control their actions, click an option in the Actions pane. If you have a large number of runbooks, you can refine the list by specifying a filter. Jobs The Jobs tab is displayed when you select a folder or runbook in the Runbooks workspace. This tab lists the jobs created for a given runbook and the completion status. For a folder, it lists the jobs created for all runbooks in the folder and their completion status. A job is a request for a runbook server to run a runbook and is created every time a runbook receives a request to run. If a runbook starts with a monitor, it creates a job that runs continuously until the runbook is stopped. In this case, the status of the job shows an hourglass that indicates it is currently running. 5

6 Instances The Instances tab is displayed when if you select a folder or runbook in the Runbooks workspace. For a runbook, this tab lists the instances that have been created for the runbook and their completion status. For a folder, it lists the instances that have been created for all runbooks in the folder and their completion status. An instance is a running copy of a runbook and is created each time that a runbook runs. If a runbook starts with a monitor, it creates an instance that continues to run until the monitor condition is met. In this case, the status for the instance shows an hourglass. When the monitor condition is met, the instance continues with the subsequent activities and then shows a completion status. The runbook then creates a new instance that also runs until the monitor condition is met. Runbook Servers workspace The Runbook Servers workspace lets you view the status of current and completed jobs and instances for each runbook server. Jobs The Jobs tab lists the jobs that have been run on the runbook server and their completion status. A job is a request for a runbook server to run a runbook and is created every time a runbook receives a request to run. If a runbook starts with a monitor, it creates a job that runs continuously until the runbook is stopped. In this case, the status of the job shows an hourglass, which means that it is currently running. Instances The Instances tab lists the instances that have been created on the runbook server and their completion status. An instance is a running copy of a runbook and is created each time that a runbook runs. If a runbook starts with a monitor, it creates an instance that continues to run until the monitor condition is met. In this case, the status for the instance shows an hourglass. When the monitor condition is met, the instance continues with the subsequent activities, and then shows a completion status. The runbook then creates a new instance that also runs until the monitor condition is met. Events workspace The Events workspace lets you view log events. By default, log events include all events for the management server and all runbook servers. To limit the events, click Filter and provide criteria to limit the events displayed. If an event is specific to a runbook server, it includes the name of the server in the Source box. In this case, you can select the event, and then click View Runbook Server in the Actions pane. Clicking View Runbook Server opens the Jobs tab in the Runbook Servers workspace for that runbook server. 6

7 Starting and stopping runbooks In addition to viewing the current status of a runbook, you can also start and stop a runbook from the Orchestration console. When you start a runbook, a job is created and waits for an available runbook server to process the runbook. If the first action in a runbook is a monitor, the job runs continuously, potentially producing multiple instances of a runbook, until the runbook or job is stopped. When a runbook server is available, the job provides an instance of the runbook to the runbook server to process. A running runbook has at least one job and one or more instances associated with it. When you stop a runbook, the runbook, all jobs, and all instances associated with the runbook are stopped. Stopping jobs A job is a request for a runbook to run. A job is created only when you request a runbook to run. If the first action in a runbook is a monitor, the job runs continuously until the runbook or job is stopped. An hourglass indicates the status of a running job. An instance is a running copy of a runbook. You cannot start a job; you can only start a runbook. When you view an instance, you can choose to stop the associated job. Stopping the job stops the instance, the job, any other associated instances, and the runbook. See Also How to Start the Orchestration Console How to Work With Runbooks in the Orchestration Console The Orchestration console can be accessed from any browser that supports Microsoft Silverlight 4. To access the system requirements for Silverlight, see Get Microsoft Silverlight. Authentication The Orchestration console requires authentication by using your domain credentials so that it can identify the runbooks and folders that you should have permission to access. If your browser is configured for automatic logon, you are not prompted for a name and password. Your browser supplies this information automatically each time you connect to the Orchestration console. If you are using a browser that does not support automatic logon or if your browser is configured to not perform automatic logon, you are prompted for a name and password each time that you connect to the Orchestration console. You can continue to type your name and password each time, or you can configure your browser to perform automatic logon. 7

8 To configure Internet Explorer for automatic logon 1. In Internet Explorer, click Tools, and then click Internet Options. The Internet Options dialog box opens. 2. On the Security tab, select Local intranet, and then click Custom Level. 3. Scroll down to User Authentication, and under Logon, select Automatic logon only in Intranet zone. Click OK. 4. In the Internet Options dialog box on the Security Settings tab, with Local intranet still selected, click Sites. 5. Click Advanced. 6. Type the URL of the Orchestration console server (for example, in the Add this Web site to the zone box, and then click Add. Note If the Require server verification ( for all sites in this zone is selected, you have to specify https for the address, and your web server has to be configured to support Secure Sockets Layer (SSL). 7. Click OK for this and the remaining dialog boxes. See Also Overview of Orchestration Console How to Start the Orchestration Console How to Work With Runbooks in the Orchestration Console How to Start the Orchestration Console The Orchestration console is a web-based tool and is accessed through your web browser. In addition to starting it on the Start menu on the computer where the web service is installed, there are two methods for starting the Orchestration console as described in the following procedures. To start the Orchestration console in a browser 1. Open your browser. 2. In the address bar, type name>:<port number> where computer name is the name of the server where the web service is installed, and port is the port number selected during configuration of the web service. By default, the port is 82. To start the Orchestration console in the Runbook Designer 1. Click the Orchestration Console button on the toolbar. Note 8

9 If the URL has not been set for the Orchestration console, you will receive an error message. Use the following procedure to set the URL. To set the Orchestration console URL in the Runbook Designer 1. Select Options, and then select Orchestration Console. 2. In the URL box, type name>:<port number> where computer name is the name of the server where the web service is installed, and port is the port number selected during configuration of the web service. By default, the port is Click Finish. See Also Overview of Orchestration Console How to Work With Runbooks in the Orchestration Console How to Work With Runbooks in the Orchestration Console Use the following steps to run a runbook, to view the status of the jobs and instances of a runbook, and to stop a job in the Orchestration console. To run a runbook in the Orchestration console 1. Click Runbooks to open the Runbooks workspace. 2. If the runbook is located in a folder, select the folder in the Runbooks pane. 3. Click the Runbooks tab in the results pane. 4. Select the runbook, and then in the Actions pane, click Start Runbook. 5. If the runbook requires parameters, they are listed in the Runbook Parameters pane. Click the Value column for each runbook and type a value for the runbook to use. 6. If you want to run the runbook on a server other than its default, click a server in the Available Runbook Server(s) pane, and then click the right arrow to add the server to the Selected Runbook Server(s) pane. 7. Click Start. Note If you add multiple servers to the Selected Runbook Server(s) pane, the runbook runs only on the first server if it is available. The other servers are backup servers where the runbook runs only if the primary server is not available. To view the status of a runbook in the Orchestration console 9

10 1. Click Runbooks to open the Runbooks workspace. 2. If the runbook is located in a folder, select the folder in the Runbooks pane. 3. Select the Runbooks tab in the results pane. 4. Select the runbook. 5. To view all jobs that the runbook created, in the Actions pane, select View Jobs. 6. To view all instances that the runbook created, in the Actions pane, select View Instances. To stop a runbook in the Orchestration console 1. Click Runbooks to open the Runbooks workspace. 2. If the runbook is located in a folder, select the folder in the Runbooks pane. 3. Click the Runbooks tab in the results pane. 4. Select the runbook, and then in the Actions pane, click Stop Runbook. 5. Click OK to the message to confirm that you want to stop the jobs. 6. If the runbook was started successfully, you receive a confirmation message that the job was stopped. If the runbook has no running jobs, you receive a message that no job was running. See Also Overview of Orchestration Console 10

Getting Started With System Center 2012 R2 Orchestrator

Getting Started With System Center 2012 R2 Orchestrator Microsoft Corporation Published: November 1, 2013 Applies To System Center 2012 Service Pack 1 (SP1) System Center 2012 R2 Orchestrator Feedback