Migrate resources in Denodo at IU

On this page:


Overview

In Denodo at Indiana University, developers can migrate their own resources from DEV to STG to PRD.

Development occurs in the IU Denodo Dev environments at the following URI:

  • DEV: //ebidvt-dev.uits.iu.edu:9999/<your_VDB_name>

After migration, you can access Denodo views in Stage and Production at the following URIs:

  • STG: //ebidvt-stg.uits.iu.edu:9999/<your_VDB_name>
  • PRD: //ebidvt.uits.iu.edu:9999/<your_VDB_name>

You can read, write, and create new objects only in the DEV environment. You can view objects in STG and PRD, but you cannot alter them in those environments. The only way to get objects into STG and PRD is through the migration process.

The only way to get objects into STG and PRD is through the full VDB migration process or the selected items migration process.

This document describes full VDB process migration process. For a description of the selected items migration process, see Migrate selected objects in Denodo at IU.

STG access is for testers, and PRD access is for consumers. To request access for additional users or groups to STG and/or PRD, see Use Data Delivery Apply Security to assign security to Denodo views.

Migrate resources

  1. Prepare to migrate: Before migrating your resources, prepare all of your data sources and views in the virtual database (VDB) without the _dev suffix (this is the VDB that will migrate). All the objects in this VDB will be migrated, except the data sources. To migrate data sources, fill out the EDSD Support Form ; under "Application", select Denodo, and under "Question Type", select Request datasource migration. Include proof of data manager approval for all data sources that contain any enterprise data; for details about data manager approval, see Data Manager approval for Denodo and Tableau. Migrate any new data sources before running the migration script in step 3 below. Until the data sources are migrated, all objects that rely on those data sources will fail due to a missing dependency.

    If you have a significant amount of work in progress, you should keep that in your other VDB. If you have work in progress that only you need to access, you may request a personal VDB.

  2. Access the scheduler: Navigate to the appropriate version of the scheduler:
    1. Go to https://denodo-dev.dvt.iu.edu/solution-manager-web-tool/.
    2. Log in with your IU username and passphrase, and then confirm your identity with Two-Step Login (Duo).

    3. Use the "Environment" drop-down to select Stg for the Stage scheduler.
    4. On the Scheduler tile, select Open.
  3. Migrate your resources to STG: In the Stage scheduler:
    1. Select Jobs in the navigation bar at the top of the display. Use the “Job” and/or “Project name” filters to find the import <your_vdb> Dev to Stage job. Use one of the following methods to start the job:
      • Select the checkbox next to the name of the job, and then select a start option from the Start drop-down menu in the line of icons above the results grid.
      • Hover at the extreme right of the row containing the name of the job (in the "Processed (Tuples/Errors)" column) until the vertical ellipses appear. Select the ellipses and choose a start option.

      Migrate to stage

      You should see your changes in the STG VDB within minutes.

      Note:
      Your job may be named Migrate <your_vdb> Dev to Stage, or Migrate <your_vdb> Stage to Prod.
  4. Migrate to PRD: Make sure to test everything thoroughly on STG before migrating your VDB to PRD. When you're ready, access the stage scheduler (using the instructions from step 2, above), and then:
    1. Select Job in the navigation bar at the top of the display.
    2. In the list of jobs, find your import <your_vdb> Stage to Prod job, and start it as described in step 3.
Important:
Consumer access privileges do not migrate between environments. If consumers need access to views in STG and/or PRD, see Use Data Delivery Apply Security to assign security to Denodo views.

Handle environment-specific settings

In some cases, you may need to have different data source connections in different environments (for example, you may want the STG Denodo VDB to point to DSS1STG and PRD point to DSS1PRD).

If environment-specific settings are part of your requirements, and you need to migrate data sources, make note of the environment-specific settings in the "Comments" section when you complete the EDSD Support Form . Also include proof of data manager approval for all data sources that contain any enterprise data; for details about data manager approval, see Data Manager approval for Denodo and Tableau. Any subsequent modification of data sources in STG and PRD will also be handled via the EDSD Support Form .

Note:
Currently, Excel data sources and custom data sources cannot be managed with environment-specific configurations.

Migrate web services

If you migrate web services to production or staging and the web service needs to be deployed, create a request using the EDSD Support Form .

Get help

If you need help or have questions about the migration process, fill out the EDSD Support Form .

This is document altb in the Knowledge Base.
Last modified on 2024-04-10 08:56:39.