Page tree
Skip to end of metadata
Go to start of metadata

On this page:

Target audience:

CAST AI Administrators

Summary: As described in CAST Application Analytics Dashboard - CAST AAD, CAST is able to export to Excel/CSV file a detailed breakdown of the Enhanced and Automated Function Point data provided "out of the box". However, to do so, a configuration change must be made to the CAST Application Analytics Dashboard. This page explains how to configure the CAST Application Analytics Dashboard to allow the export of Enhance and Automated Function Point (AFP) data to a Microsoft Excel/CSV file.

Note that this configuration change is ONLY applicable when using the standalone CAST-AAD war file (see Installing and configuring the CAST Application Analytics Dashboard) - when using the combined CAST-AAD-AED war file, the export to Microsoft Excel/CSV icons are visible out of the box.

Activating the export icons

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" CAST Application Analytics Dashboard setup when using the standalone CAST-AAD war file (see Installing and configuring the CAST Application Analytics Dashboard):

To enable the icons when using the standalone CAST-AAD war file (see Installing and configuring the CAST Application Analytics Dashboard), a CAST Administrator needs to make a configuration change as follows:

  • First determine which Dashboard Service the snapshot containing the Application has been generated in. You can do so by:
    • first looking at the Application and Snapshot name in the CAST Application Analytics Dashboard:

    • secondly opening the CAST Management Studio and looking at the information in the Execution tab of the Application editor - the Dashboard Service is highlighted below:

  • When you have this information, open the following file with a text editor:
%CATALINA_HOME%\webapps\CAST-AAD\META-INF\context.xml
  • You now need to add an additional resource which points to the Dashboard Service you identified above. The following example shows the resource pointing to the Measurement Service (as defined as part of the initial configuration of the CAST Application Analytics Dashboard - see Installing and configuring the CAST Application Analytics Dashboard) and a second resource pointing to the Dashboard Service:
       <Resource name="jdbc/domains/AAD" url="jdbc:postgresql://nefyn:2280/postgres"
                           initConnectionSqls="SET search_path TO V73_MEASURE;"
                           username="operator" password="CastAIP"
                           
                           auth="Container" type="javax.sql.DataSource" driverClassName="org.postgresql.Driver"
                           validationQuery="select 1"
                           initialSize="5" maxActive="20" maxIdle="10" maxWait="-1"/>
                           
      <Resource name="jdbc/domains/V73_CENTRAL" url="jdbc:postgresql://nefyn:2280/postgres"
                           initConnectionSqls="SET search_path TO V73_CENTRAL;"
                           username="operator" password="CastAIP"
                           
                           auth="Container" type="javax.sql.DataSource" driverClassName="org.postgresql.Driver"
                           validationQuery="select 1"
                           initialSize="5" maxActive="20" maxIdle="10" maxWait="-1"/>    
  • Please ensure that you:
    • Define a unique "name" (unique within the file). In the above example, we have used jdbc/domains/V73_CENTRAL - this is different to the default "name" provided by CAST: jdbc/domains/AAD and reuses the name of the CAST database used for the Dashboard Service (you can use any name you like but please retain the jdbc/domains/ part).
    • Define a "url" that points to the RDBMS or CAST Storage Service on which the Dashboard Service is installed. In the majority of situations, this will be identical to the "url" used for the Measurement Service
    • Define a "initConnectionSqls" that references the name of the CAST database used for the Dashboard Service - V73_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 Automatic Function Point page, the export icon will be visible.

Configuring export to Microsoft Excel or CSV file

By default, the export file format is set to Microsoft Excel (.xlsx). However, it is possible to change this to .csv if you prefer. To do so, open the following file with a text editor:

%CATALINA_HOME%\webapps\CAST-AAD\portal\resources\app.json

Locate the following line in the file:

"exportformat": "xlsx",

Change the line as follows:

"exportformat": "csv",

When complete, save the changes to the app.json file and restart your application server so that changes are taken into account.

  • No labels