Solution Manager Administrator¶

The administrators of the Solution Manager are “normal users” - not administrators - that have the role solution_manager_admin.

The goal of these users is to administer the Solution Manager and manage the Denodo licenses of the organization. Specifically, these users can:

Create, edit and remove environments, clusters and servers.

Set the Version Control System configuration.

Set the Solution Manager Database configuration.

Set the Informative Message configuration.

Manage licenses.

but cannot:

Manage deployment configurations.

Manage load balancing variables.

Set Virtual DataPort nor Scheduler properties in environments and clusters.

Access revisions nor deployments.

Execute monitoring operations.

Promotion Administrator¶

Promotion administrators are “normal users” - not administrators - that have the role solution_manager_promotion_admin.

The goal of these users is to create revisions and promote them from the development environment to testing, from testing to production, etc. Specifically, these users can:

Access the main information of the elements of the catalog in read only mode.

Manage deployment configurations.

Manage load balancing variables.

Set Virtual DataPort and Scheduler properties in environments and clusters.

Create, edit and remove her own revisions.

Access the revisions from other users in read only mode.

Validate and deploy any revision in environments.

but cannot:

Create, edit nor remove environments, clusters and servers.

Set the Version Control System configuration.

Set the Informative Message configuration.

Manage licenses.

Edit nor remove revisions from other users.

Execute monitoring operations.

Promotion Administrator for Certain Environments¶

Promotion administrators for certain environments are “normal users” - not administrators - that have one or more of these roles:

• solution_manager_promotion_admin_development

• solution_manager_promotion_admin_production

• solution_manager_promotion_admin_staging

The goal of these users is the same as the promotion administrators, but limited to deploying revisions on specific target environments. For example, the users with the role solution_manager_promotion_admin_staging can only validate and deploy revisions on the staging environments but not the other environments.

The table Solution manager promotion roles shows an overview of the different Solution Manager promotion administrator roles with their privileges to promote revisions created by users to different environment types.

Promotion¶

Promotion users are “normal users” - not administrators - that have the role solution_manager_promotion.

This user is intended to create revisions, validate and deploy them in environments. More in detail, this kind of user can:

Access the main information of the elements of the catalog in read only mode.

Create, edit and remove her own revisions.

Validate her own revisions in environments.

Deploy her own revisions.

but cannot:

Create, edit nor remove environments, clusters and servers.

Create revisions loading a VQL file.

Manage deployment configurations.

Manage load balancing variables.

Set Virtual DataPort nor Scheduler properties in environments and clusters.

Set the Version Control System configuration.

Set the Informative Message configuration.

Manage licenses.

Access revisions from other users.

Execute monitoring operations.

Promotion for Specific Environments¶

Promotion users for certain environments are “normal users” - not administrators - that have one or more of these roles:

• solution_manager_promotion_development

• solution_manager_promotion_production

• solution_manager_promotion_staging

This user is interpreted from the Solution Manager point of view as a promotion user with the difference that she can only validate and deploy her own revisions in the target environments that have the specific scenario assigned. For example, a user with role solution_manager_promotion_staging can only validate and deploy any of her revisions in any staging environment.

Overview of the Promotion Roles¶

The following table shows an overview of the different Solution Manager promotion roles with their privileges to promote revisions created by users to different environment types:

For example, a user with role solution_manager_promotion_deployment can only promote revisions created by herself in any deployment environment. A user with role solution_manager_promotion_admin_production can only promote revisions created by the own user and other users in any production environment.

JMX Administrators¶

JMX administrators users are “normal users” - not administrators - that have the role jmxadmin.

The goal of these users is to monitor the Denodo servers and diagnostic issues in them. Specifically, these users can:

Access the main information of the elements of the catalog in read only mode.

Change logging level of Virtual DataPort servers.

Execute Denodo Monitor to gather the execution logs of the Virtual DataPort servers.

but cannot:

Create, edit nor remove environments, clusters and servers.

Manage deployment configurations.

Manage load balancing variables.

Set Virtual DataPort nor Scheduler properties in environments and clusters.

Set the Version Control System configuration.

Set the Informative Message configuration.

Manage licenses.

Access revisions nor deployments.

Global Administrator¶

Global administrators are “normal users” with the role serveradmin or administrators.

These users can do any operation on the Solution Manager

Developer¶

Users that do not have any of the roles mentioned above are considered developers. These users can create revisions. Specifically, these users can:

Access the main information of the elements of the catalog in read only mode.

Create, edit and remove her own revisions.

Validate her own revisions in environments.

but cannot:

Create, edit nor remove environments, clusters and servers.

Create revisions loading a VQL file.

Manage deployment configurations.

Manage load balancing variables.

Set Virtual DataPort nor Scheduler properties in environments and clusters.

Set the Version Control System configuration.

Set the Informative Message configuration.

Manage licenses.

Access revisions from other users.

Deploy any revision.

Execute monitoring operations.