De Junta particular a cuerpo académico: categorías, cargos y mecanismos de control

Files that are related to databases are called artifacts (or objects). Database artifacts perform actions against one or more Essbase databases, such as defining calculations or reporting against data. By default, artifacts are stored in their associated database folder on the Essbase Server, and can also be saved to a client computer or to other available network directories. You cannot, however, load data or calculate data on a client computer.

Essbase provides the following common types:

• A database outline (a storage structure definition)

• Data sources

• Rules for loading data and building dimensions dynamically (rules files)

• Scripts that define how to calculate data (calculation scripts)

• Scripts that generate reports on data (report scripts)

• Security definitions

• Linked reporting objects (LROs)

• Partition definitions

Some of these artifacts are optional, such as calculation scripts and LROs. See Application and Database File Types.

In Administration Services Console, database artifacts are displayed under their associated applications or database in the Enterprise View tree.

Understanding Database Outlines

Database outlines define the structure of a multidimensional database, including all the dimensions, members, aliases, properties, 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 in the following directory:

ARBORPATH/app/sample/basic/basic.otl

See Creating a Database and Creating and Changing Database Outlines.

Understanding Data Sources

A data source is external data that is loaded into an Essbase database. The common types of data sources include the following:

• ^{Text files}

• Spreadsheet files

• Spreadsheet audit log files

• External databases, such as an SQL database See Supported Data Sources.

Understanding Rules Files for Data Load and Dimension Build

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 the data is loaded, or copied, into the Essbase database. Dimension build rules files create or modify the dimensions and members in an outline dynamically based on data in an external data source. Rules files are typically associated with a particular database, but you can define rules for use with multiple databases. A single rules file can be used for both data loads and dimension builds. Rules files have the .rul extension.

See Rules Files and Creating Rules Files.

Understanding Calculation Scripts

Calculation scripts are text files that contain sets of instructions telling Essbase how to calculate data in the database. 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.

See Developing Calculation Scripts.

Understanding Report 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.

See Developing Report Scripts.

Understanding Security Definitions

Essbase provides a comprehensive system for managing access to applications,

databases, and other artifacts. Each application and database contains its own security definitions that restrict user access.

See User Management and Security.

Understanding LROs

An LRO is an artifact associated with a specific data cell in an Essbase database. LROs can enhance data analysis capabilities by providing additional information on a cell.

An LRO can be any of the following:

• A paragraph of descriptive text (a “cell note”)

• A separate file that contains text, audio, video, or graphics

• A URL for a Web site

• A link to data in another Essbase database See Linking Objects to Essbase Data.

Understanding Spreadsheet Queries

Within Essbase Spreadsheet Add-in for Excel, users can create and save queries using Query Designer (EQD). The queries can be accessed at a later time by any user with access to the query. Query files created using Query Designer have the .eqd extension.

See the Essbase Spreadsheet Add-in for Excel User's Guide.

Understanding Member Select Definitions

Within Essbase Spreadsheet Add-in for Excel, users can define and save member retrievals with the member select feature. Member specification files have the .sel extension.

See the Essbase Spreadsheet Add-in for Excel User's Guide.

Understanding Triggers Definitions

The triggers feature enables efficient monitoring of data changes in a database. Triggers is licensed separately from Essbase. If data breaks rules that you specify in a trigger, Essbase logs relevant information in a file or, for some triggers, sends an email alert; for example, to notify the sales manager if, in the Western region, sales for a month fall below sales for the equivalent month in the previous year.

See Monitoring Data Changes Using Triggers.

Creating Applications and Databases

First create an application and then create its databases. You can annotate the databases.

Creating an Application

When you create an application on the Essbase Server, Essbase creates a subdirectory for the application on the Essbase Server in the ARBORPATH/app directory. The new

subdirectory has the same name as the application; for example,

AnalyticServices/app/app1. In Administration Services Console, applications and databases are displayed in a tree structure in Enterprise View.

Before naming the application, see Naming Restrictions for Applications and Databases.

You can also create an application that is a copy of an existing application. See Copying or Migrating Applications.

To create an application, use a tool:

Tool Topic Location

Administration Services Creating Applications Essbase Administration Services Online Help MaxL create application Essbase Technical Reference

ESSCMD CREATEAPP Essbase Technical Reference

Creating a Database

When you create a database, Essbase creates a subdirectory for the database within the application directory. The new subdirectory has the same name as the database; for example, AnalyticServices/app/app1/dbname1. In Administration Services Console, applications and databases are displayed in a tree structure in Enterprise View.

You can create normal databases or currency databases. See Designing and Building Currency Conversion Applications.

Before naming the database, see Naming Restrictions for Applications and Databases.

To create a database, use a tool:

Tool Topic Location

Administration Services Creating Databases Essbase Administration Services Online Help MaxL create database Essbase Technical Reference

ESSCMD CREATEDB Essbase Technical Reference

Except for databases requiring use of the Currency Conversion option, creating one database per application is recommended.

Annotating a Database

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.

Users can view database notes in Essbase Spreadsheet Add-in for Excel.

To annotate a database, see “Annotating Databases” in the Essbase Administration Services Online Help.