Virtual DataPort Databases¶

In the list of candidate elements, the content of Virtual DataPort databases is hidden by default. You have to expand a database, clicking its corresponding arrow, to show all the elements it contains.

Revision database elements example¶

Notice that the Solution Manager Administration Tool does not display all the elements that belong to a database. Currently, the only elements that are supported for revisions are:

• Database configuration: This option allows to include the specific database configuration in the revision VQL. This option is only displayed in CREATE revisions for the databases where the user used to connect to the Virtual DataPort server has dbadmin privileges. If this option is available, it is displayed as the first element inside a database (Include database configuration node).

• Data sources.

• Folders.

• User-defined stored procedures.

• Views.

• Web services. In CREATE revisions, the list of candidate web services only considers those web services that are actually deployed. DROP revisions show all the web services. Moreover, you can select individual operations or resources.

Tags¶

Expand the Tags node to see the available tags. The required permissions for the user to see the tags in the Revision elements tree are:

• For CREATE revisions, the user needs to have the manage_tags role, the assign_tags role or to be admin in at least one database.

• For DROP revisions, the user needs to have the manage_tags role and also to have the assign_tags role or to be admin in at least one database.

The generated VQL will apply the permissions accordingly. In a CREATE revision, the CREATE TAG commands are included in the VQL only if the user is a global administrator or has the manage_tags role.

Users and Roles¶

Expand the nodes Users and Roles to see the available users and roles.

The wizard to create revisions is aimed at creating revisions that promote elements, not to promote privileges. If you want to create a revision that does not create/modify elements and only modifies the privileges of users and roles, it is easier to create a revision from a VQL file with commands like these:

-- Grant the privileges METADATA, EXECUTE and WRITE over the view "customer360"
CREATE ROLE customer_info_read_only
GRANT METADATA, EXECUTE, WRITE ON customer_info.customer360;

Or this:

-- Grant all privileges to the role "denodo_developer" over the
-- database "northwind_db"
CREATE ROLE denodo_developer GRANT ALL PRIVILEGES ON northwind_db;

Or this:

-- Remove all the privileges of the role "denodo_developer" over the
-- database "northwind_db"
ALTER ROLE denodo_developer REVOKE ALL PRIVILEGES ON northWind_db;

When you are creating a revision and in the pill GENERAL, you select Include users and privileges, the revision will select all the users and roles in REVISION ELEMENTS.

When a user or role is selected, the revision will include the VQL statements that do this:

• Create or update these users and roles (not their privileges)

• Grant the privileges to these users and roles over the elements included in the revision. If a revision does not include a VDP element, the revision will create the selected users/roles but it will not include the statements to grant privileges over this VDP element.

  Sample scenario:

  • In the environment “development”, you create the role “customer_info_read_only” and grant the privileges METADATA, EXECUTE and WRITE to this role over the view “customer360”.

  • You create a revision that includes the role “customer_info_read_only” but does not include “customer360”.

  This revision will create the role “customer_info_read_only” but it will not grant the privileges over “customer360”. To grant the new privileges, you have to add the view “customer360” to the revision as well.

Consider this when creating a “DROP” revision:

• The revision will drop the users, roles and VDP elements included in the revision.

• DROP revisions do not revoke the privileges granted to users or roles over VDP elements, unless you drop the user or role as well. To do this, you have to create a revision from a VQL file.

Scheduler Jobs¶

Expand the node Scheduler jobs to see the available jobs. They are organized according to their project and type.

Scheduler jobs example¶

When you add a Scheduler job to a revision of type CREATE, you can choose if you want the Solution Manager to execute this job when it deploys this revision.

To execute a job during the deployment of this revision, right-click the job and click Execute job when revision is deployed.

Option “Execute job when revision is deployed”¶

The jobs that will be executed during the deployment of the revision have a green icon next to them (see below)

Scheduler job marked to execute¶

To not execute a job during the deployment, right-click the job and click Do not execute job when revision is deployed.

By default, VDP, VDP cache and VDP Data Load jobs are not marked to be executed but you can mark them. In case of revisions containing modified summaries, always include the VDP Data Load job to refresh the summary on the target environment and mark “Execute job when revision is deployed”. For more information about summary promotions visit section Summary promotions.

It is not possible to run VDPIndexer jobs during a deployment.

Elements Dependencies Tree¶

The selected elements in the revision may have dependencies with another elements that probably you also want to include. For instance, a view may depend on other views or on a data source. The Solution Manager Administration Tool allows you to check the dependencies for some of the candidate elements. In the Selected elements tree, click the element for which you want to check its dependencies, and they will appear in a hierarchical view under the title Dependencies tree. When you select elements in the Dependencies tree, they are automatically selected in the Selected elements tree. If the selected elements belong to a database whose content was not loaded yet, the database content is loaded and the elements are selected.

It is possible to check the dependencies of the following elements:

• Scheduler jobs. You can see the views for VDP Cache and VDP Data Load jobs.

  

  Scheduler cache jobs dependencies¶

• Views. The dependencies of a view include other views, data sources, stored procedures, the tags associated to the view and those associations where the view participates as an end point. Additionally, if a Scheduler job depends on a view, the dependency tree will also show that job.

  

  View dependencies¶

• Web services operations. The dependencies of a web service operation include another views, data sources, stored procedures and those associations where the published view participates as an end point.

  

  Web service operation dependencies¶

• Associations. The dependencies of an association include the views of the endpoints and the dependencies of those views.

  

  Association dependencies¶

• Users: You can see its roles as dependencies. Note that the predefined roles are ignored.

  

  User dependencies¶