Cisco Cisco Process Orchestrator 3.1 User Guide

Page of 786
 
1-9
Cisco Process Orchestrator 3.1 User Guide
 
Chapter 1      Introduction
  Process Orchestrator System Components
  –
All automation running against the TelePresence system. These results are filterable by a time 
range or by a specific process.
6.
When the end user runs a process action, internally the workflow traverses the relationship to find 
the SSH, etc. target required by the action. The user sees this and other automation running against 
the TelePresence system.
Process Orchestrator System Components
The topics in the following sections describe the major architectural elements of the Process 
Orchestrator.
Process Orchestrator Console
The Process Orchestrator console is a Windows form-based UI that is intended for advanced users that 
will be defining processes, target types, activities, and so on.
The console contains the following workspaces, each of which contains a group of objects that perform 
specific actions within the application.
  •
Operations—Use the Operations workspace to monitor the orchestration that is executing or is 
scheduled to execute on various targets. You can also use this workspace to monitor the processes 
that are scheduled to execute, view processes that are currently running, and verify that processes 
have successfully completed.
  •
Definitions—Use the Definitions workspace to view and modify processes and other related 
configurations that are used in executing automation. 
  •
Administration—Use the Administration workspace to perform administrative actions such as 
editing system-wide settings, managing security roles, configuring adapters and automation packs, 
and tuning database grooming and other settings.
Web Console
The Process Orchestrator Web Console provides a web-based UI that is intended for occasional users. 
The vision is that while a broad set of users may be defining processes, pervasively everyone in IT and 
even non-IT individuals may need to interact with those processes. The web console focuses on this 
second group. It does not allow users to define processes but does allow them to start processes, monitor 
processes they started, or interact with human steps in processes called tasks (such as approvals). This 
interface is purposefully simplified to minimize the learning curve of occasional users.
Note
The Web Console is typically not used when Process Orchestrator is used in conjunction with Cisco 
Prime Service Catalog. In these cases, end-user interaction occurs through the catalog rather than 
Process Orchestrator interfaces. The Web Console is typically only used in cases when Process 
Orchestrator is used independently.
The web console runs on a Microsoft IIS web server. Process Orchestrator environments can span 
Process Orchestrator servers, so if a deployment scenario requires breaking up automation for security, 
organizational, geographic, or purpose (such as development or test), the Web Console can provide a 
single point of access for occasional users.