Cisco Cisco Process Orchestrator 3.0 Guida Informativa

Legend

Component and version is supported in the release

—

Component, device, or application is not supported in the release

High Availability and Resiliency

Dependency

Description

Hard

A component or service is required by the dependent service to be fully operational.

Soft

A component or service is not required by the dependent service to be fully operational, but
functionality directly involving the component might be degraded or broken.

Upstream

The IT services Process Orchestrator relies on.

Downstream

The IT services that rely on Process Orchestrator.

Process Orchestrator interacts with many different IT technologies and processes (see Process Orchestrator
Dependencies, page 16‐17). It is critically dependent on some technologies, such as its backend database on an
Oracle or SQL Server (a hard upstream dependency), and on other technologies such as a DB2 database or
VMware vCenter connection (soft upstream dependencies), only to the extent that processes interact with
those technologies.
Similarly, other IT services might rely on Process Orchestrator. For example, an IaaS private cloud service built
on Cisco Intelligent Automation for Cloud (that includes Process Orchestrator) will be non‐operational or will
have to revert to all‐manual workarounds without a functioning Process Orchestrator.

Other IT services could operate in various degraded states without Process Orchestrator. For example, Incident
Management in Remedy will still function as IT's Incident Management without a functional Process
Orchestrator, but capabilities such as automated troubleshooting (a hard downstream dependency) and ticket
enrichment (a soft downstream dependency) will not be available.

To summarize, when you are planning your Process Orchestrator environment, take into consideration all of
these types of dependencies:

Process Orchestrator Compatibility Matrix