Cisco Cisco Process Orchestrator 3.0 Guida Utente
5-11
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 5 Managing High Availability and Resiliency
Maintaining Availability During Routine Maintenance
Adding More Capacity
To add more capacity to your Process Orchestrator environment, just add another Process Orchestrator
server. Before you can do that, you must:
server. Before you can do that, you must:
•
Be able to connect to an existing Process Orchestrator server
•
Have permission to add a new server
•
Acquire the credentials for connecting to the Process Orchestrator process database
For information about how to add a new server, see the Cisco Process Orchestrator Installation Guide.
Relocating a Process Orchestrator Server
To relocate a Process Orchestrator server:
Step 1
Add a new server to the environment (see
).
Step 2
Uninstall Process Orchestrator from the old server (see the Cisco Process Orchestrator Installation
Guide).
Guide).
Maintaining the Database
The following sections describe how to maintain the Process Orchestrator database:
•
•
Grooming the Database
Process Orchestrator provides settings to control grooming of the following types of objects:
•
Various sections of its Process and Reporting databases.
–
The Process database instances are primarily useful for viewing prior instances in the main
expert UI, understanding the specific activities which were executed, querying the activity
instance inputs, outputs, and other execution details typically useful in troubleshooting and
development scenarios.
expert UI, understanding the specific activities which were executed, querying the activity
instance inputs, outputs, and other execution details typically useful in troubleshooting and
development scenarios.
Grooming the Process database can help optimize performance. Reducing the database size can
improve database insert speeds, but at a cost of being able to view older process instances in the
UI. If you perform complex views including large numbers of historic processes, the database
and UI must deal with the larger data volumes. Larger views might also mean larger data
payloads coming through the server to the UI. This factor therefore not only affects the database
layer, but also the server and UI performance.
improve database insert speeds, but at a cost of being able to view older process instances in the
UI. If you perform complex views including large numbers of historic processes, the database
and UI must deal with the larger data volumes. Larger views might also mean larger data
payloads coming through the server to the UI. This factor therefore not only affects the database
layer, but also the server and UI performance.
Grooming the Process database as tightly as business scenarios allow optimizes performance of
both the Process Orchestrator Server and UIs. For example, if no business requirement exists to
monitor and troubleshoot failed processes past the end of a shift, setting grooming for one day
might be appropriate.
both the Process Orchestrator Server and UIs. For example, if no business requirement exists to
monitor and troubleshoot failed processes past the end of a shift, setting grooming for one day
might be appropriate.