Finding the Dirt: tricks for rapid Prototyping with Essbase Studio - Developing Essbase Applications - page 101

Figure 3.36 Default Load Binding.

An example might be an application with dimensionality from a development envi-
ronment, but data sourced from a staging or production system for more robust testing.
This is accomplished using the alternate data source bindings capability that overrides
the fact table and pushes the data load to whichever additional source specified.
to use alternate data source bindings:

1. on the cube schema properties select Override default data load bindings
(Figure 3.36) and click Next .

2. on the Define Data Load mappings screen go to the base members of the
accounts dimension and double-click the empty Data Load Binding field
(Figure 3.37). Then click on the ellipses in the field.

3. using the data sources in the formula area, browse to the desired alternate data
source binding and double-click it to add it to the Expression area.

4. Click OK and repeat for the additional measures.

5. Deploy the model and load data as normal.

Note: This example shows alternate data source bindings for a relational source. When
working with a relational source, this is an option. When using a text data source, you
need use the alternate data source bindings to have Studio process the data load.

3.6.5 Generating Load Rules and Integrating with MaxL Automation
A common complaint about Essbase Studio is that there is no built in scheduling mech-
anism. The lack of a built in scheduler is an overt omission by the development team
because Studio does not need one . Essbase Studio is a graphical Load rule generator.
The final output of all of your work in Studio is a set of Load rules that can either be
used to deploy a cube from the Studio uI or to build a cube based on your current
Essbase automation processes.
If you are simply prototyping with Studio, then you can deploy from the Studio uI.
however, if you use Studio in a production environment, there are two capabilities to let
you dovetail the Studio output directly into maxL:

1. generate and leverage Load rules from Studio

2. generate a maxL script from the deployment process