Environments
Tufts' Denodo architecture has the following environments:
Development: All development takes place here. All other environments are read-only and only have their code updated through deployments.
Stage: Used for testing code before deploying to Production.
Production: Stable, high-performance environment for end users.
Data Catalog
Development: https://denodo-dev.it.tufts.edu:9443/denodo-data-catalog
Stage: https://denodo-stage.it.tufts.edu:9443/denodo-data-catalog/#/
Production: https://denodo-prod.it.tufts.edu:9443/denodo-data-catalog/#/
The Data Catalog is an interactive tool that allows end users to explore all of the data available in Denodo and see relevant meta data (which we don’t have much of yet.) Querying directly on the data in a specific view is possible within the catalog:
Design Studio
This is the “IDE” (Integrated Development Environment) where Denodo development happens, including updates to descriptions and other meta data.
In order to log in, hit this link: https://denodo-solution-manager.it.tufts.edu:19443/denodo-design-studio/#/
and in that window, put in the dev address:
And you end up here:
You can use Design Studio to connect to the Stage and Production VDP’s, access will be read-only. You can only make edits in the Development VDP.
Data Catalog:
Development: https://denodo-dev.it.tufts.edu:9443/denodo-data-catalog
Stage: https://denodo-stage.it.tufts.edu:9443/denodo-data-catalog/#/
Production: https://denodo-prod.it.tufts.edu:9443/denodo-data-catalog/#/
The Data Catalog is an interactive tool that allows end users to explore all of the data available in Denodo and see relevant meta data (which we don’t have much of yet.) Querying directly on the data in a specific view is possible within the catalog:
https://tufts.app.box.com/s/wkbsud6m6qfv6hoqbcsxjn3p6wp02bcs is a field showing the json that is actually flowing from Slate to Denodo.
0 Comments