In this section of the tutorial we are going to see another useful feature included in Denodo Solution Manager, the promotion of changes between all your Denodo environments.

A promotion migrates all Denodo objects that need to be part of the migration in the server's metadata from one environment to the other. Also, it takes into account all the tasks that you should perform to migrate changes to the target environment. All the changes to be promoted are represented by what we call a revision.

Let's see a diagram of the promotion process:

This tutorial will show you a how to perform the most basic tasks of a promotion:

• How to Create Revision in Solution Manager (selecting the elements to promote).
• How to Validate a Revision
• And finally, How to Deploy a Revision into another Denodo environment.

It is strongly advised to complete the Data Services tutorial before starting this one, as we are going to be using the resources (data source, base views and integrations) created on it.

If you have already completed it, please proceed to the next section. Otherwise, follow the subsequent instructions:

1. Launch the resources needed (check how in the Installation & Bootstrapping tutorial).
2. Log in Denodo Design Studio (user/password: admin/admin)
3. Import this VQL to Denodo by clicking into File > Import. Drag ‘n' drop the file, select Use custom password for sensitive data decryption, and enter denodo in the Password field.

If all steps have been executed correctly, you should observe the following in the Design Studio's elements tree:

Great! Now it's time to start the tutorial and learn how to create revisions!

A revision is a list of Virtual DataPort catalog elements (data sources, views, etc.) and Scheduler jobs created over a Denodo environment (for example, the list of views and jobs created in the Development environment of Denodo).

The Solution Manager Administration Tool is able to connect to that source Denodo environment, so users can select those elements from the UI for creating the revision. Let's see how.

The below steps have to be followed to create a revision:

1. Click on the source environment (let's assume Development in this case, which includes a Virtual DataPort server).
2. Select New Revision

3. Provide the details of the new revision in the General section of the revision window (check the documentation for more information):

4. Change to Revision Elements in order to select the required elements to be promoted. In our example, the tree of elements created in our Development server will be displayed.

5. Select the element/s you want to include in the revision. If the element has some dependencies, they will be visible in the Dependencies tree panel. You can also select the dependencies of the elements for the promotion that you also want to include in the revision.
6. Click on the Save button on the top right corner to save the revision.

Done! You have created your first revision!

Finally, find below the list of elements which can be part of a revision in Denodo Solution Manager:

• Virtual DataPort databases (data sources, views, Web services operations, etc.)
• Associations
• Scheduler jobs
• Users (default users are ignored)
• Roles (default roles are ignored)
• Tags
• Global Security Policies (to use this feature Denodo Enterprise Plus License is needed)

Once the revision is created, the next step is to validate it. Let's see how to do that.

Once the revision has been created in Solution Manager, before promoting it to another environment, it must be validated!

The validation consists in a full check that all the required properties are defined in the target environment. For example, a revision could depend on a set of properties which includes data source configurations, users passwords, etc.

So, for a successful deployment, the target environment has to include every property used by the promoted VQL. In our example let's suppose we are promoting the revision created from our

Development environment to a

Test environment.

For checking that all the required properties are defined in the target environment, users must click on the validation icon in the revisions section and select the target environment (

Test in our example):

The first time you validate a revision including new data sources you will get an error because the configuration of those data sources is not present in the target environment. You will be able to create these new properties from that dialog:

After filling the values of the new properties into the target environment, the revision will be automatically validated again. This time it is a successful validation!!

The Revisions table also indicates that the revision has been validated successfully in the target environment (Test in our case):

Up next we will see how to Deploy a Revision.

Now let's learn how to deploy the revision validated in the previous section of the tutorial by following the steps below:

1. In the Revisions table, select the validated revision and deploy it by clicking on the symbol :

2. Select the target environment (in our case, Test) and click on Deploy button:

3. Configuring Deployments

The common options that you can configure for standard mode environments are:

• Enable deployments: Only environments with this option enabled admit working as the target of a deployment. The deployment will fail otherwise.
• Save backup in VCS when the deployment finishes: If selected, a backup of the deployment will be saved in the Version Control System you have configured. The backup will be performed both for successful and unsuccessful deployments, using the metadata of the first enabled server in the first enabled cluster.
• Execute rollback when the deployment fails in the first server: The first enabled server of the first enabled cluster of the environment works as a test base for the deployment. If this option is selected and the deployment fails there, the Solution Manager will restore its previous state by executing the backup saved during the latest successful deployment, in the Version Control System.

It is also possible to configure Solution Manager to synchronize Data Catalog servers for all environment types. The options that you can configure for Data Catalog Synchronization are:

• Enable Data Catalog synchronization: Select Views, Web services and option ALL(includes views and web services)
• Data Catalog synchronize priority
• Data Catalog servers to synchronize
• Server name to synchronize

If you have registered Data Catalog as a server in Solution manager you will see this option in the Deployments section.

4. Now you have enabled the deployments, validated and deployed the revision. That's all! The revision has been deployed! For seeing the historical information of deployments you can go to the Deployments section:

5. The successful deployments will be marked as and the failed one will be marked as .

6. Of course, you can check the errors in order to get the reason for the failure by clicking on the status icon of the failed deployment and navigating to Output > Execution Errors:

Congratulations! You have deployed your first revision into a different Denodo environment. Now you have two environments, one for developing and another one for testing a specific version of your virtual model.

Up Next, it's time to see another useful feature of Solution Manager: Monitoring all your environments.

With the help of this tutorial, we have understood the importance of Solution Manager and its advantages with respect to its following functionalities:

• How to manage promotion of Denodo elements between environments.

Congratulations! You have finished the Denodo Solution Manager tutorial. Take a look at the official reference manuals of Denodo Platform 9.0 and play with your own use cases.