Cube linkage refers to the information stored in Essbase cubes regarding:
The Essbase Studio Server and port used to deploy the cube
The model on which the cube was based
The login information for the data source from which the cube was built
For cubes built using Essbase Studio, you can update cube linkage information to change the Essbase Studio Server, port, and model context.
Examples of using cube linkage:
When drill-through reports are redirected to a new Essbase Studio Server or are based on a different Essbase model. This can be a useful load balancing strategy.
When data source login information changes, updating cube linkage is especially helpful for XOLAP-enabled cubes. By updating the cube linkage, data source login information is updated without recreating the model or redeploying the cube.
To update cube linkage in the types of cases above, complete the procedures in Before Updating Cube Linkage for Individual Cubes and Updating Cube Linkage for Individual Cubes.
When Essbase Studio Server is rehosted on a different machine (for example, after upgrade), the process of updating references to the rehosted Essbase Studio Server is handled using cube linkage.
If you have rehosted Essbase Studio Server, follow the procedure in Updating Cube Linkage After Essbase Studio Rehosting.
Note: | Always perform the rehosting steps for Essbase before performing the steps in Updating Cube Linkage After Essbase Studio Rehosting. See Updating References to a Rehosted Essbase Server for more information. |
See the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for complete information on EPM System product rehosting.