![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
A Hyperion Essbase application is a container for a database and its related files. In addition to the database, an application can include scripts that are used to load data into the database, calculate derived values, and prepare reports. This chapter explains how to work with Hyperion Essbase applications and databases. For information on copying, renaming and deleting applications, databases and their associated files, see Working with Hyperion Essbase Files and Cross-Platform Environments.
This chapter includes the following sections:
The Hyperion Essbase Application Manager provides a Windows-based environment where you can create and maintain Hyperion Essbase applications. Application development includes building outlines and dimensions, performing data loading and calculations, and defining security access.
A Hyperion Essbase application is a collection of one or more of the following types of files:
The application and its parts usually reside on the server machine, but pieces of it can reside on your client machine. The server machine can store multiple applications. The following diagram shows the relationship between the parts of an application:
Figure 7-1: Parts of a Hyperion Essbase Application
When you start an application, the following actions can happen:
For information on how to start an application, see Starting and Stopping Applications and Databases.
Database outlines define the structure of a multidimensional database, including all the dimensions, members, tags, types, consolidations, and mathematical relationships. Data is stored in the database according to the structure defined in the outline. See Basic Architectural Elements for information on creating database outlines.
Data load rules are sets of operations that Hyperion Essbase performs on data from an external data source file as it is loaded, or copied, into the Hyperion Essbase database. You need to load data into a Hyperion Essbase database because it contains no data when you create a database for the first time. 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 can also load data into the database, and then modify the database outline based on data in the external data source file.
See Introducing Data Loading for information on creating data load rules.
See Introducing Dynamic Dimension Building and Building Dimensions Using a Rules File for information on creating dimension build rules.
Calc scripts are text files that contain instructions to calculate data in the database. Calc (calculation) scripts perform different calculations than the consolidations and mathematical operations that you define in the database outline. Because calc scripts perform specific mathematical operations on members, they are typically associated with a particular database. You can, however, define a calc script for use with multiple databases. See Developing Calc Scripts for information on creating calc 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. See Developing Report Scripts for information on creating report scripts.
With Hyperion Essbase Application Manager, you also maintain user information, security information, application activity logs, and server activity logs. This information is saved on the Hyperion Essbase server. Within your organization, you can have multiple servers, each with its own users, applications, and databases. See Managing Security at Global and User Levels for more information about setting up and maintaining security information.
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 Steps for Implementing Hyperion Essbase.
![]() |
To start or stop an application: |
Figure 7-2: Stop Application Dialog Box
![]() |
You can also use alter system in MaxL, or the LOADAPP and UNLOADAPP commands in ESSCMD, to start and stop an application. See the online Technical Reference in the DOCS directory for information.
|
![]() |
To a start or stop a database: |
Figure 7-3: Stop Database Dialog Box
![]() |
You can also use alter application in MaxL, or the LOADDB and UNLOADDB commands in ESSCMD, to start and stop a database. For more information, see the online Technical Reference in the DOCS directory.
|
When you start the Hyperion Essbase Application Manager, an icon is displayed at the bottom of the window. This is the Application Desktop window for client-based applications. When you connect to a Hyperion Essbase server, a window is displayed that lists all the applications on the server. This is the Application Desktop window for server-based applications.
Figure 7-4: Application Desktop Window
Before you can work with database outlines, calc scripts, report scripts, data loading or dimension building rules, you must select an existing application or create a new one.
Figure 7-5: Application Desktop Window with Database Selected
When you select an application and database from the list boxes, select one of the following buttons to work with outlines, scripts, and rules files.
Before creating an application and database, you should decide:
You can create an application on your client machine, or you can connect to a Hyperion Essbase 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:
You can use either Hyperion Essbase Application Manager or ESSCMD to create an new application or database.
![]() |
To create a new application with Hyperion Essbase Application Manager: |
Figure 7-6: Create New Application Dialog Box
Note: | Depending on your license agreement, you may see a Storage Type list box. |
![]() |
You can also use create application in MaxL or the CREATEAPP command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
![]() |
To create a database using Hyperion Essbase Application Manager: |
The Application Desktop window is displayed:
Figure 7-8: Create New Database Dialog Box
![]() |
You can also use create database in MaxL or the CREATEDB command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When naming applications and databases, follow these rules:
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.
Hyperion Essbase Spreadsheet Add-in users can view the database note from Hyperion Essbase Spreadsheet Add-in. In Excel, for example, the Note button in the Connect dialog box lets you view database information.
![]() |
To annotate a database: |
Figure 7-9: Set Database Note Dialog Box
When designing and creating your Hyperion 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 Hyperion 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 calc scripts, report scripts, or in Hyperion Essbase Spreadsheet Add-in. You cannot use substitution variables in formulas that you apply to the database outline. For information about using substitution variables, refer to the following:
You can set substitution variables on the server using either Hyperion Essbase Application Manager 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 Hyperion Essbase Application Manager: |
Hyperion Essbase displays the Substitution Variables dialog box:
Figure 7-10: Creating a Substitution Variable
![]() |
You can also use MaxL's alter system, alter application, or alter database, or the CREATEVARIABLE command in ESSCMD, to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
You may need to delete a substitution variable that is no longer used.
![]() |
To delete a substitution variable using Hyperion Essbase Application Manager: |
Hyperion Essbase displays the Substitution Variables dialog box:
Figure 7-11: Deleting a Substitution Variable
![]() |
You can also use MaxL's alter system, alter application, or alter database, or the DELETEVARIABLE command in ESSCMD, to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
You can modify or update existing substitution variables.
![]() |
To update a substitution variable using Hyperion Essbase 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.
![]() |
You can also use MaxL's alter system, alter application, or alter database, or the UPDATEVARIABLE command in ESSCMD, to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
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.
You can create a location alias for a particular database.
![]() |
To create a location alias using Hyperion Essbase Application Manager: |
Hyperion Essbase displays the Location Aliases dialog box.
Figure 7-13: Location Aliases Dialog Box
Hyperion Essbase displays the settings in the lower text box.
Figure 7-14: Creating a Location Alias
![]() |
You can also use create location alias in MaxL, or the CREATELOCATION command in ESSCMD, to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
You can edit or delete location aliases that you previously created.
![]() |
To edit or delete a location alias using Hyperion Essbase Application Manager: |
Hyperion Essbase displays the Location Aliases dialog box.
Figure 7-15: Editing or Deleting a Location Alias
![]() |
You can use display location alias in MaxL, or the LISTLOCATIONS command in ESSCMD, to list existing location aliases. You can use drop location alias in MaxL or the DELETELOCATION command in ESSCMD to remove location aliases. For more information, see the online Technical Reference in the DOCS directory.
|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Copyright © 1991-2000 Hyperion Solutions Corporation. All rights reserved.