Glossary for Opalis Integration Server 6.3


Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator

The following table lists Opalis Integration Server 6.3 terms and the Orchestrator terms that replace them. A brief definition is included for each term.

Opalis Integration Server 6.3 termSystem Center 2012 - Orchestrator termDefinition
Action serverrunbook serverA runbook server is a computer that receives an instance of a runbook and runs the sequence of activities. Runbook servers communicate directly with the orchestration database; they do not require a management server to run runbooks.
ClientRunbook DesignerSee definition for Opalis client.
custom startinitialize dataThe initial runbook activity defined in a runbook to provide user-defined input parameters for the runbook.
datastoreorchestration databaseThe orchestration database is a SQL Server database containing configuration information, runbooks, and logs for Orchestrator.
foundation objectstandard activityThe set of runbook activities available in a default installation. This includes monitors, tasks, and all runbook controls.
objectactivityThe tasks used to create a runbook.
Object paletteActivities paneThe Activities pane is located in the tasks pane in the Runbook Designer. Collections of activities are grouped by function or integration pack.
Opalis clientRunbook DesignerAn application used to create, modify, and deploy runbooks.
Operator consoleOrchestration consoleThe interface that enables a user to see available runbooks, the real-time status of jobs and running instances, view their status, and start or stop runbooks, jobs, or instances.
PolicyrunbookA runbook is a collection of activities that orchestrates actions, events, and tasks.
Policy folderrunbook folderA folder that contains one or more runbooks.
policy modulejob processA request to run a specific runbook that is waiting for assignment to a runbook server for processing.
Policy Testing ConsoleRunbook TesterThe tool used by Runbook Designers to test policies before deployment.
publish policy dataPublished DataPublished Data is a runbook activity used to publish data from the runbook back to a calling (parent) runbook.
requestjobA job is a request to deploy and run a runbook on a runbook server. Jobs are stored in the orchestration database queue.
trigger policyInvoke RunbookAn Invoke Runbook activity calls another runbook from within a runbook. The Invoke Runbook activity can optionally wait for the called runbook to finish before proceeding. Data is returned from the invoked runbook by using the Returned Data activity. It is equivalent to the function call found in many programming languages.
workflow controlrunbook controlA collection of standard activities that manage how runbook logic behaves.