Issue: Retrieving Database information from the System Console in Production
Symptom
The System Console provides debugging and analysis tools that are separate from the Process Commander server. The System Console allows you to:
- View the status of your runtime environment
- Retrieve database record counts
- View system usage history
Some tasks require information to be collected from the database. This database retrieval is different from a workflow lookup in a Process Commander application.
Whereas a workflow lookup retrieves a specific subset of data, a request from the System Console may require lengthy, complex join operations s and table scans to retrieve the data. These operations can consume substantial database resources, leading to an unresponsive system for interactive users..
Solution
To avoid this issue you need to identify which tasks require large amounts of database resources. This depends on your organization’s applications and data.
For example, if your system contains a large number of declarative rules, it may take the system a while to return all the data when you select Node Status: Declarative Rules.
To help determine which System Console options may take up database resources, you can run these reports during off-peak hours, or on a development system running on a snapshot of your production database.
Once you have determined which reports may impact performance during normal usage hours, run these reports only during less busy periods, to ensure that production users do not experience unsatisfactory performance or downtime.
Previous topic Issue: Process Commander applications monitored with CA Wily Introscope might experience depleted native memory