Dashboard configuration checklist
The following checklist provides a detailed overview of all configuration required to use the Health and Value Dashboards and create Value reports. Many of these tasks may already be completed for your environment. The checklist is meant to provide an overview of everything needed to take advantage of the dashboards and Value reports.
The checklist includes references to more information. You can export this page to a file and use the checklist to validate your dashboard configuration.
Step | For more information, see... |
|---|---|
1. Install and configure a database for storing metrics data and set up the drivers for TrueSight Orchestration components, including dashboards. | Configuring-the-metrics-and-audit-records-database Review all information in this page. |
1-a. Review the information about the databases you can install. | |
1-b. Install the database. | Use your database vendor instructions. |
1-c. Create a table space for the metrics tables. | Use your database vendor instructions. |
1-d. Create a database user with permission to create tables, to insert records into those tables, and to select records. | Use your database vendor instructions. |
1-e. If you are not using the Oracle database driver installed by default with TrueSight Orchestration, install the JDBC driver for the database you are using and copy the database driver to the add-on directories for TrueSight Orchestrationcomponents, including the dashboards. | Use your database vendor instructions and |
1-f. Restart the TrueSight Orchestrationservices, including the dashboard service, on each computer on which you installed the driver. | |
2. Ensure that metrics collection is turned on, the connection to the database is configured, and a peer on that grid is designated as a synchronization point (sync point). Optionally, configure peer memory use collection if you want that information included in the Health Dashboard. | |
2-a. Turn on metrics collection. | |
2-b. Turn on process metrics collection. | |
2-c. Ensure that at least one peer on the grid that is connected to the database must be designated as a sync point. | Editing-peers explains how to specify that a peer is a sync point. |
2-d. If you want to collect peer memory usage in the Health Dashboard (Peers memory trending area), set Memory Use for the peer on the Grid Manager's Grid Metrics tab. | Managing-grid-performance-records describes how to add a grid metric configuration. |
3. Configure the following dashboard property files:
Optionally, you can configure currency, Process report minimum and maximum value range, and refresh settings in the hdb.properties file. | |
4. Restart the dashboard service. | |
5. Verify that users have the right permission to access the dashboards. | |
Additional Value Dashboard steps For Value Dashboard use, complete the following steps. | Setting-up-the-Value-Dashboard-and-reports Review Before you begin for requirements. |
6. In Development Studio workflows, set Record Metrics to True for all processes for which you want to collect metrics (process and business). | |
7. In Development Studio workflows, set up Metrics activities for all processes for which you want to collect business metrics. | |
7-a. Workflows must have Metrics activities that are configured to collect business metrics. | |
7-b. Ensure that each Metrics activity is set up to work with Value reports, with the correct property names assigned. | |
8. Export the modules (containing the workflows for which you will collect metrics) to the repository. | |
9. Activate the modules on the grid. | |
10. Assign Default permission to the modules. | |
11. Run the processes. The first process runs generate the additional required tables in the metrics database (if they do not already exist). | |
12. Verify that the metrics tables are created in the database before connecting to the Value Dashboard. | Configuring-the-metrics-and-audit-records-database lists the additional tables used by the Value Dashboard. Use your database vendor instructions to verify that the tables exist in the database. |