Cisco Cisco Process Orchestrator 3.0 User Guide

The Process Orchestrator server logs errors that can be useful when you need to diagnose failures to 
the Windows Event Logs. For example, if there is an error connecting to a database, this will be 
logged as an event. 

These logs can also be picked up by most enterprise systems management tools if you want a view 
of Process Orchestrator health within your systems or application management console.

For more information about viewing system events, see 

.

Windows performance counters

The Process Orchestrator server publishes a number of Windows performance counters concerning 
its operations. For a list of Windows performance counters, see 

.

Be sure to monitor the system event logs and Windows performance counters from all 
Process Orchestrator servers in an environment. Monitoring one server is not sufficient to 
monitor the health of all servers.

This section discusses how to maintain the availability of the servers in the Process Orchestrator 
environment during routine maintenance:

To maintain availability of the overall high availability environment during routine outages, such as 
Microsoft security patches and minor Process Orchestrator upgrades that do not affect the database 
schema:

Shut down one Process Orchestrator service (while keeping the others running). Wait for the Process 
Orchestrator service to completely stop via a friendly shutdown.

Install the Microsoft patches or Process Orchestrator patches on that server.

Reboot as necessary, then restart the Process Orchestrator service.

Repeat steps 1-3 on all Process Orchestrator servers, one at a time, to maintain availability of the overall 
high availability environment.

For more information about shutting down and restarting Process Orchestrator, see the Cisco Process 
Orchestrator Installation Guide.