Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Summary: Instructions for configuring your standalone Health Dashboard to allow export of a detailed breakdown of the AEP/EFP function point data to Excel/CSV. Note that this configuration change is ONLY applicable when using the standalone Health war file (see Standalone Health Dashboard deployment) - when using the combined Health/Engineering war file, the export to Microsoft Excel/CSV icons are visible out of the box.

Introduction

The export to Microsoft Excel/CSV icons (as shown below) are NOT active (they are greyed out) by default in an "out of the box" Health Dashboard setup when using the standalone Health war file (see Standalone Health Dashboard deployment). This is because the information resides in the Dashboard schema (central) and not the Measure schema used by the Health Dashboard. In a combined Health and Engineering Dashboard, the dashboard schema is referenced in the connection property files for the dashboard, so the Health Dashboard already knows where the information is located. To enable these export icons in a standalone Health war file, a configuration change must be made to the Health Dashboard to inform the dashboard where the information is located. This page explains how to make this change.

Options greyed out:

AEP

EFP/AFP

Activating the export icons

To enable the icons when using the standalone Health war file a CAST Administrator needs to make a configuration change as follows:

Determine the Dashboard schema name

First determine which Dashboard schema the snapshot containing the relevant Application has been generated in. You can do so by first looking at the Application and Snapshot name in the Health Dashboard:

...

Info

This information is also located in CAST Management Studio in the Execution tab of the Application editor - the Dashboard Service is highlighted below:

Configure connection properties

WAR 1.x

When you have the name of the Dashboard schema that stores the required information, open the following file with a text editor:

...

You now need to add an additional resource which points to the Dashboard schema you identified above. The following example shows the resource pointing to the Measurement schema (as defined as part of the initial configuration of the Health Dashboard - see Standalone Health Dashboard deployment) and a second resource pointing to the Dashboard schema:

...

  • Define a unique "name" (unique within the file). In the above example, we have used jdbc/domains/uuid_55800ce6_03f7_49d0_971c_eb6f18ff2c94_central- this is different to the default "name" provided by CAST: jdbc/domains/AAD and reuses the name of the Dashboard schema (note that you can use any name you like but please retain the jdbc/domains/ part).
  • Define a "url" that points to the CAST Storage Service/PostgreSQL instance on which the Dashboard schema is installed. In most situations, this will be identical to the "url" used for the Measurement schema
  • Define a "initConnectionSqls" that references the name of the CAST AIP schema used for the Dashboard Service: initConnectionSqls="SET search_path TO uuid_55800ce6_03f7_49d0_971c_eb6f18ff2c94_central;" in the example above.
  • Check that the "username" and "password" entries are correct.
  • Following any changes you make, save the context.xml file and then restart your application server so that the changes are taken into account.
  • Now when you access the relevant pages, the export icons will be visible.

WAR/ZIP ≥ 2.x

When you have the name of the Dashboard schema that stores the required information, you need to modify two files:

...

Code Block
WAR ≥ 2.x
CATALINA_HOME\webapps\<deployed_war>\WEB-INF\classes\application.properties

ZIP ≥ 2.x
<unpacked_zip>\configurations\application.properties

Find the following section in the file:

...

Code Block
WAR ≥ 2.x
CATALINA_HOME\webapps\<deployed_war>\WEB-INF\classes\domains.properties

ZIP ≥ 2.x
<unpacked_zip>\configurations\domains.properties

Add a new line to the file that specifies the Resource2 added in application.properties specific to "AED1" and the Dashboard schema you identified above, ensuring that there are no empty lines:

...