Import¶

Scheduler supports import server configuration, projects, plugins and JDBC adapters from a file containing the metadata of a server.

• ZIP or XML file: enter the path to the Scheduler backup file. That is, the file that contains the elements to recreate the metadata. If you have exported the metadata with the Export environment specific properties option enabled, the backup file generated already contains the properties file inside, so you do not need to provide a single properties file (see next option), unless you want to override the properties inside the backup file with the ones in the file you provide.

• Properties file (optional): if you have exported the metadata with the Export environment specific properties option disabled and the backup file to import does not include the properties (or you want to override them), enter the path to the file with the .properties. Properties in the file selected in this option have priority over the ones contained inside the backup file.

The “Data import” dialog will then show a tree with the projects and its elements included in the file. Use the check boxes to select the individual contents to import. It is possible to configure which kinds of elements (jobs, data sources, plugins and drivers) will be replaced by the ones included in the imported file if they already exist. This is useful for migration and backup purposes. If the metadata was exported with a custom password, select Use custom password to decrypt sensitive data and enter the password. Denodo Scheduler also provides scripts for importing the metadata (see appendix Use of the Import/Export Scripts for Backup (Scheduler)). A password can be set to use by default when exporting/importing metadata, if the user does not specify a custom password (see appendix Use of Configure Scheduler Export Key Script).

Export¶

Scheduler supports export projects (with their data sources and jobs), plugins, JDBC adapters and the server configuration. This is useful for migration and backup purposes. It generates a backup file including all the required information to restore the current server metadata.

There are two different file formats to export a backup: ZIP or XML.

It is possible to choose what elements to export:

• All the projects (with all their elements), choosing the set of resources to export among the server configuration, the plugins and the JDBC adapters used by the elements of the exported projects.

• A single project or a set of projects, also choosing the set of elements (data sources and jobs) of each project and the resources to export among the server configuration, the plugins and the JDBC adapters used by the chosen elements of the exported projects.

• You can include the elements on which the selected items depend by checking the option Export dependencies. For instance, if you select to export a job “Job1” that is configured with a data source “DS1” and you do not select this data source to be exported, by enabling this option it automatically will be included in the export file.

• You can include the permissions assigned for each role by checking the option Export roles and permissions. Note that permissions assigned to not selected (to be exported) projects and jobs will not be included in the export file.

• You can include Scheduler environment settings and metadata by checking the option “Export settings”.

You can export the environment dependent properties (such as the connection data for data sources, etc.) separately in a different properties file by checking the option Export with properties. In this case, a backup file is generated, containing these two pieces of information:

• When exporting to ZIP:

1. The backup (a .zip file). The values of the parameters that depend on the environment are variables instead of the actual values.

2. A file (with the extension .properties) that contains the values of the variables.

• When exporting to XML the backup file also contains the same information than the ZIP but in an unique file.

This option makes exporting and importing metadata across different environments, easier.

If you want to encrypt sensitive data with a custom password, instead of default server password, check button “Use custom password for sensitive data encryption” and enter the password in “Custom password” and “Confirm custom password” fields.

The platform also provides scripts to run automatic backup copies (see appendix Use of the Import/Export Scripts for Backup (Scheduler)). It is important to note that sensitive data (like passwords) are encrypted in the backup file.