Page tree

Versions Compared

Key

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

...

The installation process is divided into various steps:

Step 1Rename and deploy the .WAR file on your application server
Step 2Configure your deployed .WAR file
Step 3Install the license key
Step 4Restart Tomcat and test connection
Step 5Configure user authentication
Step 6

First login and become admin - ≥ 2.1 only

Step 7Configure roles
Step 78Generate snapshot data
Step 89Configure data authorization

...

This step involves configuring how your users will authenticate with the CAST Engineering Dashboard. Most organizations opt for LDAP/Active Directory integration so that users can use their corporate username/password to access the resources they need. The Engineering Dashboard also has a built in username/password authentication mechanism which is enabled "out of the box". See User authentication.

Anchor
become_admin
become_admin
Step 6 - First login and become admin - ≥ 2.1 only

By default, the CAST Dashboard requires that at least one user is granted the ADMIN role following the first login after the User authentication configuration. This ensures that one user can access all data and cofiguration settings. See First login and become admin. This step is not required when using Dashboards 1.x and can be skipped.

Anchor
step6
step6
Step

...

7 - Configure roles

This step involves configuring roles for users and groups that are accessing the CAST Engineering Dashboard. See User roles.

Anchor
step7
step7
Step

...

8 - Generate snapshot data

Before your users can "consume" data via the CAST Engineering Dashboard, you need to generate snapshot data.

Anchor
step8
step8
Step

...

9 - Configure data authorization

An Authorization defines permission to access and "consume the data" in a specific Application or group of Applications via the CAST Engineering Dashboard. If permission is not granted, or a "restriction" is used, then any information related to this Application will be not accessible: application properties such as name, technologies or grades and measures, etc. Therefore, an Authorization must be defined before a user/group of users can access a specific application. See Data authorization.

...