Cisco Cisco Process Orchestrator 3.0 Guida Utente

Pagina di 242
 
5-8
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 5      Managing High Availability and Resiliency
  Ensuring Operational Continuity
  •
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.
Saving the Process Orchestrator Server Data in Preparation for a Disaster
When making preparations for a disaster, the most important piece of information to save is the security 
key that a Process Orchestrator server uses to encrypt sensitive data before storing it to the database. This 
environment-specific key is stored in the Windows security system of each Process Orchestrator server.
Note
In a disaster recovery situation, the Process Orchestrator database is useless without the 
corresponding and separately stored encryption key for the Process Orchestrator environment.
Another important piece of data is the Process Orchestrator server configuration file. For more 
information about this file, see 
.
To save this information:
Step 1
Once for the Process Orchestrator environment:
a.
Export the security credentials encryption key to a file:
aspnet_regiis –px “Tidal Intelligent Automation Server” Keys.xml -pri
Aspnet_regiis.exe is a Microsoft.NET framework utility that resides in the .Net Framework folder. 
This folder is typically located at this location:
C:\Windows\Microsoft.Net\Framework64\{Version}\aspnet_regiis.exe
You might need to specify the full path to this utility if you have not defined the path in your Path 
environment variable
b.
Save the Keys.xml file, then move it to a secure location (typically a standby or backup server) 
separate from the Process Orchestrator server.
Step 2
For each Process Orchestrator server, copy the server configuration file to a standby or backup server. 
You can find this file in the installation folder.
%INSTALLDIR%\Tidal.Automation.Server.exe.config
Monitoring Processes and Events
Each server in a Process Orchestrator environment publishes performance and events. A Process 
Orchestrator server can also provide data about its own health to operational support systems, and can 
interact with operational support systems with regard to the health of services for which it provides 
automation.
If you want to monitor the entire high availability environment, however, you must monitor all of the 
servers. Most application management systems include the ability to monitor the data that Process 
Orchestrator publishes, such as Windows event logs and performance counters.