Orchestrator is composed of three distinct layers: an orchestration platform that provides the common features required for an orchestration tool, a plug-in architecture to integrate control of subsystems, and a library of workflows. Orchestrator is an open platform that can be extended with new plug-ins and libraries, and can be integrated into larger architectures through a REST API.

The following list presents the key Orchestrator features.

Persistence

Production grade databases are used to store relevant information, such as processes, workflow states, and configuration information.

Central management

Orchestrator provides a central way to manage your processes. The application server-based platform, with full version history, can store scripts and process-related primitives in the same storage location. . This way, you can avoid scripts without versioning and proper change control on your servers.

Check-pointing

Every step of a workflow is saved in the database, which prevents data-loss if you must restart the server. This feature is especially useful for long-running processes.

Control Center

The Control Center interface increases the administrative efficiency of vRealize Orchestrator instances by providing a centralized administrative interface for runtime operations, workflow monitoring, unified log access and configurations, and correlation between the workflow runs and system resources. The vRealize Orchestrator logging mechanism is optimized with an additional log file that gathers various performance metrics for vRealize Orchestrator engine throughput.

Versioning

All Orchestrator Platform objects have an associated version history. Version history is useful for basic change management when distributing processes to project stages or locations.

Scripting engine

The Mozilla Rhino JavaScript engine provides a way to create building blocks for Orchestrator Platform. The scripting engine is enhanced with basic version control, variable type checking, name space management, and exception handling. The engine can be used in the following building blocks:

  • Actions

  • Workflows

  • Policies

Workflow engine

The workflow engine allows you to automate business processes. It uses the following objects to create a step-by-step process automation in workflows:

  • Workflows and actions that Orchestrator provides

  • Custom building blocks created by the customer

  • Objects that plug-ins add to Orchestrator

Users, other workflows, schedules or policies can start workflows.

Policy engine

You can use the policy engine to monitor and generate events to react to changing conditions in the Orchestrator server or plugged-in technology. Policies can aggregate events from the platform or any of the plug-ins, which helps you to handle changing conditions on any of the integrated technologies.

Security

Orchestrator provides the following advanced security functions:

  • Public Key Infrastructure (PKI) to sign and encrypt content imported and exported between servers.

  • Digital Rights Management (DRM) to control how exported content can be viewed, edited, and redistributed.

  • Secure Sockets Layer (SSL) to provide encrypted communications between the desktop client and the server and HTTPS access to the Web front end.

  • Advanced access rights management to provide control over access to processes and the objects manipulated by these processes.

Encryption

vRealize Orchestrator uses a FIPS-compliant Advanced Encryption Standard (AES) with a 256-bit cipher key for encryption of strings. The cipher key is randomly generated and is unique across appliances that are not part of a cluster. All nodes in a cluster share the same cipher key.