An Essbase application is a container for a database and its related files. This chapter provides an overview of Essbase applications and databases and explains how to create them. For information on everyday management of applications, databases, and their associated files, see Maintaining and Automating Hyperion Essbase.
This chapter includes the following sections:
An Essbase application is a management structure that contains one or more Essbase databases and related files. Essbase applications and databases usually reside on OLAP Server. The server machine can store multiple applications. Applications and databases created on client machines are used only to store database objects, such as outlines and calculation scripts. You cannot load data or calculate data on a client machine.
An Essbase database is a data repository that contains a multidimensional data storage array. A multidimensional database supports multiple views of data so that users can analyze the data and make meaningful business decisions. For more information about how Essbase stores data, see Storage Allocation.
This diagram shows the relationships among the parts of an application:
Figure 43: Parts of an Essbase Application
With Application Manager, you can create and maintain Essbase applications. Application development includes creating databases, building database outlines, loading and calculating data, and defining security access. For information about everyday management of applications and databases, see Maintaining and Automating Hyperion Essbase.
Files that are related to databases are called objects. Database objects perform actions against one or more Essbase databases, such as defining calculations or reporting against data. By default, objects are stored in their associated database folder on the server. They can also be saved to a client machine or to other available network directories.
In Essbase, the common types of objects include the following:
Some objects are optional, such as calculation scripts and linked reporting objects.
For a complete list of application and database file types, see Application and Database File Types.
Database outlines define the structure of a multidimensional database, including all the dimensions, members, aliases, tags, types, consolidations, and mathematical relationships. The structure defined in the outline determines how data is stored in the database.
When a database is created, Essbase creates an outline for that database automatically. The outline has the same name as the database (dbname.OTL). For example, when the Basic database is created within the Sample application, an outline is created within the following directory:
ARBORPATH\APP\SAMPLE\BASIC\BASIC.OTL
For information about creating outlines, see Creating and Changing Database Outlines.
A data source is external data that is loaded into an Essbase database. The common types of data sources include the following:
For complete information about data sources, see Introducing Data Loading.
You can integrate a relational database with a multidimensional database so that much of the data remains in the relational database. For complete information, see Accessing Relational Data with Hybrid Analysis.
An Essbase database contains no data when it is first created. Data load rules files are sets of operations that Essbase performs on data from an external data source file as it is loaded, or copied, into the Essbase database. Specifying data load rules is the most common way to load data into the database. Data load rules files are typically associated with a particular database, but you can define rules for use with multiple databases.
Dimension build rules files create or modify an outline dynamically based on data in an external data source file.
A single rules file can be used for both data loads and dimension builds. Rules files have the .RUL extension.
For information about creating data load rules files, see Introducing Data Loading. For information about creating dimension build rules files, see Building Dimensions Using a Rules File.
Calculation scripts are text files that contain sets of instructions telling Essbase how to calculate data in the database. Calculation scripts, also called calculation scripts, perform different calculations than the consolidations and mathematical operations that are defined in the database outline. Because calculation scripts perform specific mathematical operations on members, they are typically associated with a particular database. You can, however, define a calculation script for use with multiple databases. Calculation scripts files have the .CSC extension.
For information about creating calculation scripts, see Developing Calculation Scripts.
Report scripts are text files that contain data retrieval, formatting, and output instructions to create a report from the database. Report scripts are typically associated with a particular database, but you can define a report script for use with multiple databases. Report scripts have the .REP extension.
For information about creating report scripts, see Developing Report Scripts.
Essbase provides a comprehensive system for managing access to applications, databases, and other objects. Each application and database contains its own security definitions that restrict user access.
For more information about setting up and maintaining security information, see Managing Security for Users and Applications.
A linked reporting object is an object associated with a specific data cell in an Essbase database. Linked reporting objects can enhance data analysis capabilities by providing additional information on a data point.
A linked reporting object can be any of the following:
For more information about using linked reporting objects, see Linking Objects to Essbase Data.
Within Spreadsheet Add-in, users can create queries using Query Designer (EQD). Users can save the reports in the form of queries (.EQD files). The queries can be accessed at a later time by the user who created the report or by other users who have access to the query.
For more information, see the Essbase Spreadsheet Add-in User's Guide.
With Spreadsheet Add-in, users can define member retrievals with the member select feature. If users want to save the member select specification, they can do so with an .SEL file.
For more information, see the Essbase Spreadsheet Add-in User's Guide.
To implement a multidimensional database you need to complete a number of steps, from creating an application through optimizing your database performance. For a complete list of these steps, see Quick Start for Implementing Essbase.
When you start Application Manager, the Desktop opens and a closed window is displayed at the bottom of the Desktop. This is the Application Desktop window for client-based applications. When you connect to OLAP Server, a window is displayed that lists all the applications on the server. This is the Application Desktop window for server-based applications:
Figure 44: Application Desktop Window
To work with database outlines, calculation scripts, report scripts, data loading or dimension building rules using the Application Dekstop, use this procedure:
Figure 45: Application Desktop Window with Database Selected
The Outline button lists all database outlines for the selected database. This button performs no action if (all dbs) is selected.
The Calc Script button lists all calculation scripts available for the selected application or database.
The Report Script button lists all report scripts available for the selected application or database.
The Data Load Rules button lists all rules files available for the selected application or database.
Note: When working on scripts associated with a particular database, make sure the database name is selected in the Databases list box. When working on scripts not associated with any particular database, make sure "(all dbs)" is selected in the Databases list box.
You can also use Administration Services Console to manage applications and databases. The console displays a graphical view of the Essbase environment called Enterprise View as shown in Figure 46.
Figure 46: Administration Services Console Enterprise View
From this view, you can operate directly on applications and databases. For more information, see the Essbase Administration Services Online Help.
Before creating an application and database, you should decide:
You can create an application on your client machine, or you can connect to OLAP Server and build it there. Building an application on the client allows you to develop and test it in an isolated environment. However, it does limit what can be done with the application.
You must build your application on the server if you want to give other users access to the application or start the application automatically when the server starts.
You can use either Application Manager, Essbase Administration Services Console, or ESSCMD to create a new application or database.
The application name will be created exactly as you enter it. If you enter the name as all capital letters, for instance NEWSAMP, Essbase will not automatically convert it to upper and lower case; for instance Newsamp.
To create a new application with Application Manager:
Figure 47: Create New Application Dialog Box
Depending on your license agreement, you may see a Storage Type list box.
Tip: You can also create applications without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
To create a database using Application Manager:
The Application Desktop window is displayed.
Figure 49: Create New Database Dialog Box
Note: The database name will be created exactly as you enter it. If you enter the name as all capital letters, for instance BASIC, Essbase will not automatically convert it to upper and lower case; for instance Basic.
In most cases, the database type is Normal. To create a currency database, select a database type of Currency. For more information on currency databases, see Designing and Building Currency Conversion Applications.
Tip: You can also create databases without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
When naming applications and databases, follow these rules:
* (asterisks) \ (backslashes) [] (brackets) : (colons) , (commas) = (equal signs) > (greater than signs) < (less than signs) . (periods) + (plus signs) ? (question marks) " (double quotation marks) ; (semicolons) ' (single quotation marks) / (forward slashes) tabs | (vertical bars)
When you have created a database, you should annotate it. A database note can provide useful information in situations where you need to broadcast messages to users about the status of a database, deadlines for updates, and so on.
Spreadsheet Add-in users can view the database note from Spreadsheet Add-in. In Excel, for example, the Note button in the Connect dialog box lets you view database information.
To annotate a database using Application Manager:
Figure 50: Set Database Note Dialog Box
You can also use the Set Database Note dialog box in Administration Services to annotate a database. Refer to the Essbase Administration Services Online Help.
When designing and creating your Essbase database, you might want to make use of dynamic calculations. Dynamically calculating some data values in your database can significantly improve the overall calculation performance of your database. For more information, see Dynamically Calculating Data Values and Calculating Time Series Data.
When designing your Essbase application, you may want to make use of substitution variables. Substitution variables act as global placeholders for information that changes regularly; each variable has a value assigned to it. The value can be changed at any time by the database designer; thus, manual changes are reduced.
For example, many reports depend on reporting periods; if you generate a report based on the current month, you have to update the report script manually every month. With a substitution variable, such as CurMnth, set on the server, you can change the assigned value each month to the appropriate time period. When you use the variable name in your report script, the information is dynamically updated when you run the final report.
You can use substitution variables in these components:
You cannot use substitution variables in formulas that you apply to the database outline.
You can set substitution variables on the server using Application Manager, Administration Services, MaxL, or ESSCMD. Set the variable at any of the following levels:
Keep in mind the following guidelines when setting substitution variables:
You can set substitution variables on the server at the server, application, or database level.
To set a substitution variable using Application Manager:
Essbase displays the Substitution Variables dialog box, as shown in Figure 51.
Figure 51: Creating a Substitution Variable
Tip: You can also set substitution variables without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
You may need to delete a substitution variable that is no longer used.
To delete a substitution variable using Application Manager:
Essbase displays the Substitution Variables dialog box:
Figure 52: Deleting a Substitution Variable
Tip: You can also delete substitution variables without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
You can modify or update existing substitution variables.
To update a substitution variable using Application Manager:
The name of the existing variable and its current value are displayed in the list.
In the Value list, the previous value is replaced with the new value:
Tip: You can also update substitution variables without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
A location alias is a descriptor for a data source. A location alias maps an alias name for a database to the location of that database. A location alias is set at the database level and specifies an alias, a server, an application, a database, a username, and a password. You need database designer privileges to set location aliases.
After you create a location alias, you can use the alias to refer to that database. If the location of the database changes, you can edit the location definition accordingly.
Note: You can use location aliases only with the @XREF function. With this function, you can retrieve a data value from another database to include in a calculation on the current database. In this case, the location alias points to the database from which the value is to be retrieved. For more information on @XREF, see the Technical Reference in the docs directory.
You can create a location alias for a particular database.
To create a location alias using Application Manager:
Essbase displays the Location Aliases dialog box.
Figure 54: Location Aliases Dialog Box
Essbase displays the settings in the lower text box.
Figure 55: Creating a Location Alias
Tip: You can also create location aliases without using Application Manager:
Tool |
Instructions |
For more information |
---|---|---|
You can edit or delete location aliases that you previously created.
To edit or delete a location alias using Application Manager:
Essbase displays the Location Aliases dialog box.
Figure 56: Editing or Deleting a Location Alias
Tip: You can also edit or delete location aliases without using Application Manager:
Tool |
Instructions |
For More Information |
---|---|---|
![]() © 2002 Hyperion Solutions Corporation. All rights reserved. http://www.hyperion.com |