Prior to release 11.1.1, users could create links to transactional data in relational datawarehouse by using a suite of tools called Essbase - Integration Services (EIS).
Release 11.1.1 introduces Essbase Studio.
Combining into a single workbench much of the functionality of :
Essbase Studio is the next-generation environment for the development, deployment, and maintenance of enterprise-scale application
Essbase Studio simplifies cube construction by delivering a single environment for performing tasks related to data modeling, cube designing, and analytic application construction.
The graphical front-end features of Essbase Studio enable you to build Essbase Cubes from snowflake and star schema relational data source and flat files.
Lineage tracking functionality in Essbase Studio provides full upstream and downstream metadata visibility for your Essbase - Data Source. Additionally, it provides enhanced drill-through to multiple targets including :
- Relational databases,
- Essbase applications (drill across),
- OBIEE, BI+ reports,
- Reporting and Analysis repositories,
- custom SQL,
A single common metadata repository, or catalog, captures all metadata related to all Essbase applications built in the enterprise and allows the reuse of metadata at the lowest level of granularity. The catalog makes Essbase Studio inherently aware of the common metadata that is shared across the various applications enterprise wide.
Essbase Studio also supports lineage tracking through a rich graphical view of metadata relationships, allowing users to follow application lineages to their metadata components and through to the data sources from which they were sourced.
How to schedule cube deployment
There are two ways to schedule cube deployment outside of Essbase Studio:
- You may create a deployment script that uses the MaxL “deploy” command. Then, use a scheduling tool of your choice to schedule the script to run.
- Alternatively, you can create rules files using the Essbase Studio Console or the MaxL “deploy” command with the rules files only option. Then, create a deployment script that uses the MaxL “import data” command using the pre-created rules to automate cube construction. Again, use a scheduling tool of your choice to schedule the script to run.