Cisco Cisco Process Orchestrator 3.0 Guida Utente
5-7
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 5 Managing High Availability and Resiliency
Ensuring Operational Continuity
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.
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.
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:
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.
dependencies on other services, see the Cisco Process Orchestrator Compatibility Matrix.
Ensuring Operational Continuity
Ensuring operational continuity of your Process Orchestrator environment includes these actions:
•
•
•
Backing Up Your Data
In a disaster recovery situation, you will need copies of the following information, so be sure to
regularly:
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.
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
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
.
Table 5-2
Dependency Types
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.
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.