Cisco Cisco Process Orchestrator 3.1 User Guide

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

For more information about the dependencies on Process Orchestrator and Process Orchestrator's 
dependencies on other services, see the Cisco Process Orchestrator Compatibility Matrix. 

Ensuring operational continuity of your Process Orchestrator environment includes these actions:

In a disaster recovery situation, you will need copies of the following information, so be sure to 
regularly: 

Back up your database. Follow the standard database backup procedures for data recovery and the 
best practice database resiliency strategies of your database vendors, which should be provided in 
the documentation for the applicable database platform.

Save the Windows security credentials encryption key for the Process Orchestrator environment. 
This only needs to be done once; this key is shared by all servers in a single Process Orchestrator 
environment. For information about how to save the key, see 

. 

Save the Process Orchestrator server configuration file. For more information about this file, see 

.

Take snapshots of the Process Orchestrator server VMs and save them at an alternate site (see 

Save any customizations to the Web.config file in the Web Console server.

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 that Process Orchestrator relies on.

Downstream

The IT services that rely on Process Orchestrator.