For 2.x JARs or ZIPs on Documentation - V2

Changing the name of the cast_dashboards schema

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

A graphical user interface was implemented in ≥ 2.1 for managing the assignment of role and data authorizations to users and groups of users. This interface replaces the existing mechanism provided by the roles.xml and the authorizations.xml files. You can find out more in:

User roles and User roles - 2.x and above
Data authorization and Data authorization - 2.x and above

This management interface relies on aschema hosted on a PostgreSQL instance to store the roles/data authorizations. This schema is called cast_dashboards by default and will be created on first startup of the web application. This schema is defined using two files:

Configure additional Dashboard schemas for JAR file deployments

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

When deploying a JAR file (available in ≥ 2.5) an installer is provided. This installer will only allow the configuration of one single PostgreSQL instance and one single Dashboard/Central schema as shown in the image below:

If you therefore need to define additional C PostgreSQL instance(e.g. you need to define multiple Dashboard/Central schemas located on multiple PostgreSQL instances) or you need to define additional Dashboard/Central schemas (located on the same PostgreSQL instance), you will need to make a manual change to the Dashboard configuration files as described below.

Deploying multiple 2.x ZIPs or JARs on the same server

Mon, 01 Jan 0001 00:00:00 +0000

Note

This information is only valid for CAST Dashboard**≥ 2.x** when using a ZIP/JARdeployment (i.e. without Apache Tomcat).

Introduction

The following situations require some small changes to the Dashboard deployment process so that each Dashboard deployment does not conflict with another:

when multiple standalone 2.x Dashboards need to be run from the same server
when embedded AIP Console Dashboards (from v. 1.25) need to be run on the same machine as standalone 2.x ZIP/JAR dashboards

Required changes

Step 1 - Change the port on which the Dashboard is running - Linux and Microsoft Windows

By default the ZIP/JAR Dashboards are preconfigured to run on the following ports to accept incoming connections:

Modify the user access port or set up secure HTTPS dashboard access

Mon, 01 Jan 0001 00:00:00 +0000

Info

Summary: this page describes how to change the CAST Dashboard access port, for example to enable HTTPS.

Note

This information is only valid for CAST Dashboard ≥ 2.x when using a ZIP/JAR file deployment (i.e. without Apache Tomcat). If you are deploying WAR files using Apache Tomcat, see **Configuring Apache Tomcat to use secure https protocol**for more information.

Introduction

By default, the CAST Dashboards will listen on an insecure HTTP connection on port 8080 (i.e for user access). This page explains how to change the listening port number, for example to enable a secured connection using HTTPS on port 443 or to change to an alternative HTTP port such as port 80.

Start and stop 2.x JAR or ZIP deployments

Mon, 01 Jan 0001 00:00:00 +0000

Info

Summary: this page describes how to start and stop the 2.x ZIP deployments.

Note

This information is only valid for CAST Dashboard ≥ 2.x when using a ZIP file deployment (i.e. without Apache Tomcat).

Introduction

Out of the box, the 2.x ZIP files are provided with start-up and shut down scripts that are used to start/stop the web applications manually:

Microsoft Windows
<install_folder>\startup.bat
*** there is no shutdown.bat for Microsoft Windows - use the CTRL+C escape key to gracefully stop the server if it has been started with the startup.bat file.
 
Linux
<install_folder>\startup.sh
<install_folder>\shutdown.sh

In addition, for Microsoft Windows deployments, CAST provides scripts to install/uninstall a Microsoft Windows Service. Installation instructions are provided in the relevant dashboard installation guide:

Updating Windows Service Java parameters

Mon, 01 Jan 0001 00:00:00 +0000

When a Dashboard (embedded or standalone) is installed as a Windows Service, it is configured with specific Java parameters, for example initial memory pool and max memory pool amongst others:

--JvmMx 1024 --JvmMs 256

It is sometimes necessary to modify these parameters, however, it is not possible to do so by right clicking the service in the Windows Service snap-in and choosing Properties:

Instead CAST provides a specific tool with the installed Dashboard that allows you to view these Java parameters:

Unlock the persistence schema

Mon, 01 Jan 0001 00:00:00 +0000

Info

Summary: this page describes how to unlock the persistence schema using a SQL query

Note

This information is only valid for CAST Dashboard ≥ 2.x

Introduction

If your CAST Dashboard service is unable to start, it may be due to a “locked” persistence schema (by default the persistence schema is called “cast_dashboards” and stores information about roles and data authorization). Schemas (and other database items) are usually “locked” while they are being updated, but sometimes the lock that is applied fails to be released correctly therefore preventing applications from accessing and updating the schema.