essbase guide

Oracle® Essbase

Database Administrator’s Guide

RELEASE 11.1.2.1

content

1. Introduction to Essbase2. Essbase Architecture3. Essbase Product Components4. Understanding Mutidimensional Databases5. Running Essbase server, Application and databases

1. Essbase Executable Files2. Understanding the Agent3. Starting Essbase Server in foreground4. Starting Essbase server as background Process5. Changing the Essbase server system password6. stopping Essbase server7. Starting and Application8. Stoping and Application9. Stopping an Application Improperly10. Staring a Database11. Stopping a Database12. Essbase Logs

6. Managing Applications and Databases1. Copying or Migrating an Application2. Reanaming an Application3. Deleting an Application4. Copying Databases5. Reanming Databases6. Deleting Databases

7. Starting and Stopping Essbase Products8. Launching client

Introducing Essbase

Essbase is a multidimensional database management system (MDBMS) that provides a

multidimensional database platform upon which to build analytic applications.

With Essbase, companies quickly leverage and integrate data from multiple existing data sources

and distribute filtered information to end-user communities in the format that best meets the users’

needs.Essbase is the business analysis server technology that provides an environment for rapid

development of custom analytic and enterprise performance management applications. For

example, Essbase enables line-of-business personnel to develop and manage analytic applications

that model complex scenarios, forecast business trends, and perform “what-if” analyses.

Essbase supports extremely fast query response times for vast numbers of users, for large data sets,

and for complex business models. It is hot-pluggable across any data source.

Essbase Architecture

Essbase products incorporate powerful architectural features to handle a wide range of analytic

applications across large multiuser environments. Figure 1 provides a high-level view of the

information flow between the three tiers of the Essbase architecture. The client tier (on the left)

includes Essbase Server clients, such as Oracle Hyperion Smart View for Office, Fusion Edition

and Administration Services Console. The middle tier (in the center) includes services, such as

Oracle Hyperion Provider Services and Oracle Essbase Administration Services. The database

tier (on the right) is made up of Essbase Servers. Communication between the client and middle

tiers, and the middle and database tiers, is through HTTP. Communication between the client

and database tiers is through TCP/IP or HTTP. Communication between data sources and the

metadata catalog with the middle and database tiers is through ODBC and JDBC drivers.

Figure 1 High-level Information Flow Between Product Components

Essbase Product Components

Administration ServicesAdministration Services—the database and system administrators’ interface to Essbase—

provides a single-point-of-access console to multiple Essbase Servers. Using Administration

Services, you can design, develop, maintain, and manage multiple Essbase Servers, applications,

and databases. You can preview data from within the console without having to open a client

application, such as Spreadsheet Add-in. You can also use custom Java plug-ins to leverage and

extend key functionality.

Essbase StudioOracle Essbase Studio simplifies cube construction by delivering a single environment for

performing tasks related to data modeling, cube designing, and analytic application

construction. With a wizard-driven user interface, Essbase Studio supports modeling of the

various data source types from which Essbase applications are typically built.

A single common metadata repository, or catalog, captures all metadata related to all Essbase

applications built in the enterprise and allows the reuse of metadata at the lowest level of

granularity. The catalog makes Essbase Studio inherently aware of the common metadata that

is shared across the various applications enterprise wide.

Essbase Studio supports several drill-through options: relational databases, custom SQL, URLs

(including Oracle Business Intelligence Enterprise Edition and Oracle Hyperion Financial Data

Quality Management, Fusion Edition URLs), and Java methods. Essbase Studio also supports

lineage tracking through a rich graphical view of metadata relationships, allowing users to follow

application lineages to their metadata components and through to the data sources from which

they were sourced.

Spreadsheet Add-inSpreadsheet Add-in integrates Essbase with Microsoft Excel. Spreadsheet Add-in adds the

Essbase menu to Excel, which provides enhanced commands such as Connect, Pivot, Drilldown,

and Calculate. Users can access and analyze data on Essbase Server with mouse clicks and

dragging operations. Spreadsheet Add-in enables multiple users to access and update data on

an Essbase Server simultaneously.

Visual ExplorerOracle Essbase Visual Explorer provides a query and analysis interface for creating interactive

summaries and reports about the data in an Essbase database. You can choose to visualize data

in various graphical formats, including bars, lines, Gantt bars, shapes, colors, and tables.

Visual Explorer is installed with and accessed from Spreadsheet Add-in.

Data MiningData Mining reveals hidden relationships and patterns in your data, enabling you to make better

business decisions. Using Data Mining, you can plug in various data mining algorithms, build

models, and apply them to existing Essbase applications and databases.

Integration ServicesOracle Essbase Integration Services—an optional product component—provides a metadatadriven

environment to bridge the gap between data stored in Essbase databases and detailed data

stored in relational databases. The Hybrid Analysis feature gives business users more detail for

decision-making and IT managers more modularity in designing and maintaining large-scale

analytic applications. Hybrid Analysis allows portions of Essbase databases to be stored in a

relational database. This relational-stored data is mapped to the appropriate Essbase hierarchies.

Provider ServicesProvider Services is a middle-tier data-source provider to Essbase for Java API, Smart View, and

XMLA clients. Provider Services supports highly concurrent analytical scenarios and provides

scalability and reliability in a distributed Web-enabled enterprise environment.

Smart ViewSmart View provides a common Microsoft Office interface for Essbase, Oracle Hyperion

Financial Management, Fusion Edition, Oracle Hyperion Planning, Fusion Edition, and Oracle

Enterprise Performance Management Workspace, Fusion Edition data. Using Smart View, you

can view, import, manipulate, distribute, and share data in Microsoft Excel, Word, and

PowerPoint interfaces.

Application Programming Interface (API)Essbase API—the developers’ interface to Essbase—enables you to create customized

applications. The Oracle Essbase API Reference provides a complete listing of API functions.

Developer ProductsEssbase developer products enable the rapid creation, management, and deployment of tailored

enterprise analytic applications, whether or not users have programming knowledge.

The products (for example, Application Builder and Oracle's Hyperion® Application Builder

for .NET) provide a comprehensive set of application programming interfaces, drag-and-drop

components, and services.

Smart Search Command Line UtilityOracle Hyperion Smart Search Command Line Utility integrates with leading enterprise search

solutions such as Google Search Appliance and Oracle Secure Enterprise Search to provide a

familiar search interface. Using simple business terminology, users can obtain structured

information from Essbase applications and databases. Information that has been filtered

according to user privileges is delivered in data grids and live links in Smart View. Oracle

Hyperion Smart Search Command Line Utility greatly enhances the way in which users can

quickly get to information contained within Oracle applications.

Lifecycle ManagementOracle Hyperion Enterprise Performance Management System Lifecycle Management provides

a consistent way for Oracle Hyperion Enterprise Performance Management System products to

migrate an application, a repository, or individual artifacts across product environments and

operating systems. Generally, the Lifecycle Management interface in Oracle's Hyperion® Shared

Services Console is consistent for all EPM System products that support Lifecycle Management.

However, EPM System products display different artifact listings and export and import options

in the Lifecycle Management interface.

Lifecycle Management features:

• Viewing applications and folders

• Searching for artifacts

• Migrating directly from one application to another

• Migrating to and from the file system

• Saving and loading migration definition files

• Viewing selected artifacts

• Auditing migrations

• Viewing the status of migrations

• Importing and exporting individual artifacts for quick changes on the file system

Understanding Multidimensional Databases

OLAP and Multidimensional DatabasesOnline analytical processing (OLAP) is a multidimensional, multiuser, client-server computing

environment for users who need to analyze enterprise data.

It has the ability to provide managers the information that they need to make effective decisions

about an organization's strategic directions. A successful OLAP application provides information as

needed; that is, it provides “just-in-time” information for effective decision-making.

Key to OLAP systems are multidimensional databases, which not only consolidate and calculate

data; but also provide retrieval and calculation of a variety of data subsets. A multidimensional

database supports multiple views of data sets for users who need to analyze the relationships

between data categories.

In multidimensional databases, the number of data views is limited only by the database outline,

the structure that defines all elements of the database. Users can pivot the data to see information

from a different viewpoint, drill down to find more detailed information, or drill up to see an

overview.

Dimensions and MembersA dimension represents the highest consolidation level in the database outline. The database

outline presents dimensions and members in a tree structure to indicate a consolidation

relationship. For example, in figure 2,Year is a dimension (of type Time) and Qtr1

is a member. Figure 2 Hierarchical Structure

Essbase has standard dimensions and attribute dimensions.

Standard dimensions represent the core components of a business plan and often relate to

departmental functions. Typical standard dimensions: Time, Accounts, Product Line, Market,

and Division. Dimensions change less frequently than members.

Attribute dimensions are associated with standard dimensions. Through attribute dimensions,

you group and analyze members of standard dimensions based on the member attributes

(characteristics). For example, you can compare the profitability of noncaffeinated products

that are packaged in glass to the profitability of noncaffeinated products packaged in cans.

Members are the individual components of a dimension. For example, Product A, Product B,

and Product C might be members of the Product dimension. Each member has a unique name.

Essbase can store the data associated with a member (referred to as a stored member in this

chapter), or it can dynamically calculate the data when a user retrieves it.

Outline HierarchiesAll Essbase database development begins with creating a database outline, which accomplishes

the following:

• Defines the structural relationships between members in an Essbase database

• Organizes data in the database

• Defines the consolidations and mathematical relationships between items

Essbase uses the concept of members to represent data hierarchies. Each dimension consists of

one or more members. The members, in turn, may consist of other members. When you create

a dimension, you tell Essbase how to consolidate the values of its individual members. Within

the tree structure of the database outline, a consolidation is a group of members in a branch of

the tree.

For example, many businesses summarize their data monthly, rolling up monthly data to obtain

quarterly figures and rolling up quarterly data to obtain annual figures. Businesses may also

summarize data by zip code, city, state, and country. Any dimension can be used to consolidate

data for reporting purposes.

In the Sample.Basic database included with Essbase Server, for example, the Year dimension

comprises five members: Qtr1, Qtr2, Qtr3, and Qtr4, each storing data for an individual quarter,

plus Year, storing summary data for the year. Qtr1 comprises four members: Jan, Feb, and Mar,

each storing data for a month, plus Qtr1, storing summary data for the quarter. Similarly, Qtr2,

Qtr3, and Qtr4 comprise the members that represent the individual months plus the member

that stores the quarterly totals.

The database outline in Figure 2 uses a hierarchical structure to represent the data consolidations

and relationships in Qtr, as described in the previous paragraph.

Some dimensions consist of relatively few members, while others may have hundreds or even

thousands of members. Essbase does not limit the number of members within a dimension and

enables the addition of new members as needed.

Dimension and Member RelationshipsEssbase uses hierarchical (generations and level; and roots and leaves) and family history

(parents, children, and siblings; and descendants and ancestors) terms to describe the roles and

relationships of the members in a database outline. The subtopics in this section reference the

outline show in Figure 3 in describing the position of the members.

Figure 3 Member Generation and Level Numbers

Parents, Children, and SiblingsFigure 3 illustrates the following parent, child, and sibling relationships:

• A parent is a member that has a branch below it. For example, Margin is a parent member

for Sales and Cost of Goods Sold.

• A child is a member that has a parent above it. For example, Sales and Cost of Goods Sold

are children of the parent Margin.

• Siblings are child members of the same immediate parent, at the same generation. For

example, Sales and Cost of Goods Sold are siblings (they both have the parent Margin), but

Marketing (at the same branch level) is not a sibling, because its parent is Total Expenses.

Descendants and AncestorsFigure 3 on page 60 illustrates the following descendant and ancestral relationships:

• Descendants are members in branches below a parent. For example, Profit, Inventory, and

Ratios are descendants of Measures. The children of Profit, Inventory, and Ratios are also

descendants of Measures.

• Ancestors are members in branches above a member. For example, Margin, Profit, and

Measures are ancestors of Sales.

Roots and LeavesFigure 3 on page 60 illustrates the following root and leaf member relationships:

• The root is the top member in a branch. Measures is the root for Profit, Inventory, Ratios,

and the children of Profit, Inventory, and Ratios.

• Leaf members have no children. They are also referred to as level 0 members. For example,

Opening Inventory, Additions, and Ending Inventory are leaf members.

Generations and LevelsFigure 3 on page 60 illustrates the following generations levels:

• Generation refers to a consolidation level within a dimension. A root branch of the tree is

generation 1. Generation numbers increase as you count from the root toward the leaf

member. In Figure 3, Measures is generation 1, Profit is generation 2, and Margin is

generation 3. All siblings of each level belong to the same generation; for example, both

Inventory and Ratios are generation 2. Figure 4 shows part of the Product dimension with its

generations numbered. Product is generation 1, 100 is generation 2, 100-10 is generation 3,

and 100-10-12 and 100-10-16 are generation 4.

Figure 4 Generations

• Level also refers to a branch within a dimension; levels reverse the numerical ordering used

for generations. Levels count up from the leaf member toward the root. The root level

number varies depending on the depth of the branch. In Figure 3, Sales and Cost of Goods

Sold are level 0. All other leaf members are also level 0. Margin is level 1, and Profit is level

2. Notice that the level number of Measures varies depending on the branch. For the Ratios

branch, Measures is level 2. For the Total Expenses branch, Measures is level 3. Figure 5

shows part of the Product dimension with its levels numbered. 100 is level 2, 100-10 is level

1, and 100-10-12 and 100-10-16 are level 0.

Figure 5 Levels

Generation and Level NamesTo ease report maintenance, you can assign a name to a generation or level and then use the

name as a shorthand for all members in that generation or level. Because changes to an outline

are automatically reflected in a report, when you use generation and level names, you do not

need to change the report if a member name is changed or deleted from the database outline.

Standard Dimensions and Attribute Dimensions

Essbase has standard dimensions and attribute dimensions. This chapter focuses on standard

dimensions, because Essbase does not allocate storage for attribute dimension members. Instead,

it dynamically calculates the members when the user requests data associated with them.

An attribute dimension is a special type of dimension that is associated with a standard

dimension.

Sparse and Dense Dimensions

Most data sets of multidimensional databases have two characteristics:

• Data is not smoothly and uniformly distributed.

• Data does not exist for the majority of member combinations. For example, all products may

not be sold in all areas of the country.

Essbase maximizes performance by dividing the standard dimensions of an application into two

types: dense dimensions and sparse dimensions. This division allows Essbase to cope with data

that is not smoothly distributed, without losing the advantages of matrix-style access to the data.

Essbase speeds data retrieval while minimizing memory and disk requirements.

Most multidimensional databases are inherently sparse; they lack data values for the majority

of member combinations. A sparse dimension is one with a low percentage of available data

positions filled.

For example, the outline of the Sample.Basic database in Figure 6 includes the Year, Product,

Market, Measures, and Scenario dimensions. Product represents the product units, Market

represents the geographical regions in which the products are sold, and Measures represents the

accounts data. Because not every product is sold in every market, Market and Product are chosen

as sparse dimensions.

Most multidimensional databases also contain dense dimensions. A dense dimension has a high

probability that one or more cells is occupied in every combination of dimensions. For example,

in the Sample.Basic database, accounts data exists for almost all products in all markets, so

Measures is chosen as a dense dimension. Year and Scenario are also chosen as dense dimensions.

Year represents time in months, and Scenario represents whether the accounts values are budget

or actual values. Figure 6 Sample.Basic Database Outline

Data StorageEach data value in a multidimensional database is stored in one cell. A particular data value is

referenced by specifying its coordinates along each standard dimension.

Consider the simplified database shown in Figure 4. This database has three dimensions:

Accounts, Time, and Scenario:

• The Accounts dimension has four members: Sales, COGS, Margin, and Margin%.

• The Time dimension has four quarter members, and Qtr1 has three month members

• The Scenario dimension has two child members: Budget for budget values and Actual for

actual values.

Figure 4 A Multidimensional Database Outline

Data ValuesThe intersection of one member from one dimension with one member from each of the other

dimensions represents a data value. The example in Figure 16 has three dimensions (Accounts,

Time, and Scenario); therefore, the dimensions and data values in the database can be

represented as a cube.

Figure 5 Three-Dimensional Database

As illustrated in Figure 6, when you specify Sales, you are specifying the slice of the database

that contains eight Sales values, where Sales intersect with Actual and Budget.

Figure 6 Sales Slice of the Database

Slicing a database amounts to fixing one or more dimensions at a constant value while allowing

the other dimensions to vary.

As illustrated in Figure 7, when you specify Actual Sales, you are specifying the slice of the

database that contains four Sales values, where Actual and Sales intersect.

Figure 7 Actual, Sales Slice of the Database

A data value is stored in one cell in the database. To refer to a specific data value in a

multidimensional database, you specify its member on each dimension. In Figure 8, the cell

containing the data value for Sales, Jan, Actual is shaded. The data value can also be expressed

using the cross-dimensional operator (->) as Sales -> Actual -> Jan.

Figure 8 Sales->Jan->Actual Slice of the Database

Data Blocks and the Index SystemEssbase uses two types of internal structures to store and access data: data blocks and the index

system.

Essbase creates a data block for each unique combination of sparse standard dimension members

(providing that at least one data value exists for the sparse dimension member combination).

The data block represents all the dense dimension members for its combination of sparse

dimension members.

Essbase creates an index entry for each data block. The index represents the combinations of

sparse standard dimension members. It contains an entry for each unique combination of sparse

standard dimension members for which at least one data value exists.

Each unique data value can be considered to exist in a cell in a data block. When Essbase searches

for a data value, it uses the index to locate the appropriate data block. Then, within the data

block, it locates the cell containing the data value. The index entry provides a pointer to the data

block. The index handles sparse data efficiently because it includes only pointers to existing data

blocks.

By carefully selecting dense and sparse standard dimensions, you can ensure that data blocks do

not contain many empty cells, minimizing disk storage requirements and improving

performance. In Essbase, empty cells are known as #MISSING data.

Multiple Data ViewsA multidimensional database supports multiple views of data sets for users who need to analyze

the relationships between data categories. Slicing the database in different ways gives you

different perspectives of the data. For example, in Figure 9, the slice for Jan examines all data

values for which the Year dimension is fixed at Jan.

Figure 9 Data for January

The slice in Figure 10 shows data for the month of Feb:

Figure 10 Data for February

The slice in Figure 11 shows data for profit margin

Figure 11 Data for Profit Margin

Running Essbase Server, Applications and databases

Essbase Executable Files

Executable File Describtion Locationessbase.exe Essbase Server Agent

process

ESSBASEPATH/bin

esssvr.exe Application server process ESSBASEPATH/binessmsh.exe MaxL Shell ESSBASEPATH/binesscmd.exe ESSCMD command-line

client interface

ESSBASEPATH/bin

adminsvr.exe or

startEAS.exe

Essbase Administration

Server executable

EPM_ORACLE_HOME/

products/Essbase/eas/

server/binadmincon.exe Administration Services

Console application

EPM_ORACLE_HOME/

products/Essbase/eas/

server/bin

Understanding the Agent

Launching the Agent executable file, essbase.exe, starts the Essbase Server Agent process. The

Agent process starts and stops all applications and acts as the traffic coordinator for Essbase

Server.

On the computer where Essbase Server is installed, the Agent is accessible only from the server

console, which is the primary terminal, or monitor, connected to the server computer.

When you start Essbase Server in the foreground, the Agent becomes active in an operating

system window. In the Agent window, you can view release and license information, enter login

and administrative commands, and monitor the behavior of Essbase Server. On Windows,

Essbase can be accessed only from the server console. On UNIX, a telnet session is used to access

Essbase remotely.

When you start Essbase Server in the background, the terminal becomes free for other input,

and the Agent activities are not visible in the terminal.

The agent log is called the Essbase Server log.

Starting Essbase Server in the Foreground

Starting Essbase Server in the foreground starts the Agent in an operating system window, in

which you can enter commands and monitor Essbase Server activities.

When starting an Essbase Server for the first time (for example, after installing Essbase), the

administrator enters a company name, Essbase Server system administrator user ID, and a system

password. This information is saved in the Essbase security file (essbase.sec). As long as

essbase.sec is present in your Essbase installation, you are not prompted to provide this

information when subsequently starting Essbase Server.

To start Essbase Server in the foreground,

For Windows, choose a method:

• On the Start menu, select Programs, then Oracle EPM System, then Essbase, then Essbase

Server, and then Essbase.

• In the file system, launch the startEssbase.bat file.

Starting Essbase Server as a Background Process

If you start Essbase Server in the background, these conditions apply:

• You do not have access to Agent commands.

• You cannot shut down Essbase Server from the Agent. You must use MaxL or ESSCMD.

• You cannot access the application server window to monitor a running application. You

must access this information from the application log (ARBORPATH/app/appname/

appname.log).

• You cannot monitor Essbase Server activity using the Agent. You must access this

information from the Essbase Server log (EPM_ORACLE_HOME/logs/essbase/

essbase.log).

To start Essbase Server in the background on UNIX or on Windows systems utilizing a UNIXl ike

shell such as MKS, enter the following command at a command prompt:

startEssbase.sh -b &

Using the ampersand (&) at the end of the command is optional; however, if you do not use

“&,” the command prompt is not returned after Essbase Server is started.

Note: On Windows, unless you are using a UNIX-like shell such as MKS, the ampersand (&)

has no effect. Essbase Server starts in the background, but control of the command prompt

is not returned. You may need to press the Enter key twice before the command prompt

returns.

Changing the Essbase Server System PasswordYou can change the password that is required to start Essbase Server.

Note: Changing the system password does not change the connection password for the Essbase

system Administrator.

To change the Essbase Server system password, use a tool:

Tool TopicAgent passwordMaxL alter user system_administrator

set password passwordESSCMD SETPASSWORD

Essbase verifies that the system password has been updated.

Stopping Essbase ServerYou need Administrator permissions to stop or shut down Essbase Server.

To stop Essbase Server and all running applications, use a tool:

Tool TopicAgent quit exitMaxL Alter system shutdownESSCMD SHUTDOWNSERVER

If you stop the Agent by closing the Agent window or by pressing Ctrl + C, the next time you

start the database, Essbase rolls back any transactions that were in progress.

Starting an ApplicationWhen you start an application, the following actions can happen:

• Users can connect to the application.

• The application can respond to commands from the Agent.

• Users can change the settings of the application.

• Data and user security are enabled.

• Each database in the application can start.

To start an application, use a tool:

Tool TopicAgent START appnameMaxL alter system load applicationESSCMD LOADAPP or SELECTAdministration Services Starting Applications

The application starts and, if you are running on Windows, opens the application server window

on the Essbase Server computer.

You can also start an application by completing any of these actions:

• Starting a database within an application.

• Saving an outline to Essbase Server. (Opening an outline does not start an application.).

You can set options that control how applications start:

• startup (Allow user to start application): If an application is stopped, and a user attempts to

retrieve data from any databases within that application, the application starts on the Essbase

Server computer automatically.

• autostartup (Start application when Essbase starts): Users may experience better initial

performance when they make requests of databases in that application, because the

application and databases are already loaded into memory on the Essbase Server computer.

Stopping an Application

Stop applications properly to prevent the databases within them from becoming corrupt. When

you stop an application, transactions may be running. If you stop an application using any of

the proper methods (see the following table), the application does not stop if a calculation or

data load is in progress. Instead, Essbase displays a message in the Agent console.

If you stop the Agent by closing the server console window or by pressing Ctrl+C, the application

stops, and the next time you start the application, Essbase rolls back any transactions that were in

progress.

To properly stop applications, use a tool:

Tool TopicAgent stop appnameMaxL alter system unload applicationESSCMD UNLOADAPPAdministration Services Stopping Applications

Stopping an Application Improperly

Sometimes, stopping the application server process improperly, by closing the application server

window, is necessary; for example, if the application server is corrupted and is not processing

client requests.

äTo stop the application improperly, use a method for the operating system on which Essbase

Server runs:

For UNIX platforms, kill the ESSSVR process.

You can use the ps output to identify individual applications. If an application freezes, you

can stop the application by using this command:

kill -9 <pid>

For Windows, choose a method:

• Perform a Windows operating system End Task.

Windows does not display process IDs for individual Essbase applications—all of the

running Essbase applications are displayed as undifferentiated ESSSVR processes,

preventing you from stopping a single application in the event that the application freezes.

• Click the Close button in the application server window.

• Taskkill the process ID.

You can find the process ID for individual application servers in the

EPM_ORACLE_HOME/logs/essbase/essbase.log file. When the server starts, a line

like the following is displayed in the Essbase Server log:

Application [Sample] started with process id [225]

Starting a Database

When Essbase starts a database and loads it to memory, the entire index cache for that database

is allocated in memory automatically. The data cache and data file cache are allocated as blocks

requested from Essbase clients.

When you start an application, Essbase loads the application and its databases into memory on

the Essbase Server computer. When you start a database from an application that is not started,

the application is loaded into memory along with all its related databases.

To start a database, use a tool:

Tool TopicAgent START appnameMaxL alter application load databaseESSCMD UNLOADAPPAdministration Services LOADDB or SELECT

To configure a database to start automatically when its parent application starts, use a tool:

Tool TopicMaxL alter database enable autostartupAdministration Services Configuring Databases to Start

Automatically

Stopping a Database

Stopping a database unloads all data from memory and commits any updated data to disk. If a

database is stopped and a user attempts to retrieve data from it, the database starts on Essbase

Server automatically, without any explicit commands issued.

When you stop a database, transactions may be currently running. If you stop a database using

any of the proper methods (see the following table), the database does not stop if a calculation

or data load is in progress. Instead, Essbase displays a message in the server console window.

If you stop the Agent by closing the server console window or by pressing Ctrl+C, the database

stops, and the next time you start the database, Essbase rolls back any transactions that were in

progress.

To stop a database, use a tool:

Tool TopicAgent STOP appnameMaxL alter application unload

databaseESSCMD UNLOADDBAdministration Services Stopping Databases

Essbase LogsThis topic describes the logs that Essbase Server creates to record information about server, application, and database activities..Note:Log files (except for Essbase Server log files) may be located under ARBORPATH/app/appname, depending on the value of the DEFAULTLOGLOCATION configuration parameter.

Summary of Logs

Type of Log Location of Log Information Included

Essbase Server log

HYPERION_HOME/logs/essbase/ESSBASE.LOGNote:If your installation contains multiple instances of Essbase Server, each instance has its own log file directory, as controlled by the InstanceID configuration setting. For example: if InstanceID is set to inst1, the logging directory for that instance is HYPERION_HOME/logs/essbase_inst1.

Server activities and errors

Application log HYPERION_HOME/logs/essbase/app/appname/appname.LOG

Application activities and errors

Query log HYPERION_HOME/logs/essbase/app/appname/dbname/dbname00001.qlg

Query patterns of Essbase database retrievals

Outline change log

HYPERION_HOME/logs/essbase/app/appname/dbname/dbname.olg

Changes to the outline

Exception log

One of these locations:ARBORPATH/log00001.xcpHYPERION_HOME/logs/essbase/app/log00001.xcpHYPERION_HOME/logs/essbase/app/appname/log00001.xcpHYPERION_HOME/logs/essbase/app/appname/dbname/log00001.xcp

Errors that result when Essbase Server stops abnormally

Dimension build and data load error logs

One of these locationsARBORPATH/client/dataload.errHYPERION_HOME/logs/essbase/app/appname/appname.log

Errors from a dimension build or a data load

EPM System Configurator and System Log FilesLog Type Log Location Name and ContentsEPM SystemConfigurator logs

EPM_ORACLE_INSTANCE/diagnostics/logs/config

cmconfig.log—Trace info generated during Reporting and Analysisconfiguration from Reporting and Analysis (CMC) APIs called● configtool.log—Configuration task output and warning messages● configtool-http-ant.log—Trace from ant code executed duringWeb server setup● ConfigTool-stdout.log—Console output● Configtool-appdeployment.log—Trace of deployment steps● configtool_summary.log—Summary status about pass/fail tasks● EssbaseExternalizationTask.log—Trace information for theEssbase externalization process executed during Essbase customconfiguration● SharedServices_CMSClient.log—Shared Services CMS clienttrace, generated during configuration when CMS calls are made● ocm-config.log—Oracle Configuration Manager configuration log● registry.log—Trace of Oracle Hyperion Shared Services Registry callsmade during configuration● SharedServices_Security.log—Shared Services Registryregistration log

EPM System Diagnosticslogs

EPM_ORACLE_INSTANCE/diagnostics/logs/validation/

validation.log—Trace information generated during diagnostic utilityexecutionNote: A file name validation-n.log indicates that the log has rolledover because of size limits● validationTool-stderr.log—Error information generated duringdiagnostic utility execution● validationTool-stdout.log—Trace information generated duringdiagnostic utility execution● velocity.log—Diagnostic utility trace generated by velocitycomponent calls

EPM System Diagnosticsreports

EPM_ORACLE_INSTANCE/diagnostics/reports

instance_report_20110305_121855.html—Validation tool report

Application Server logs—For Oracle WebLogicServer installed withEPM System Installer.For WebLogic Serverinstalled outside EPMSystem Installer, see theWebLogic Serverdocumentation forinformation about logs

WebLogic Server service,error, and console logs: EPM_ORACLE_INSTANCE/diagnostics/logs/PRODUCT

See the product folders for the specific logs.

Web server logs—ForOracle HTTP Serverinstalled with EPMSystem Installer. ForWeb servers installedoutside EPM SystemInstaller, see vendordocumentation forinformation about logs.

EPM_ORACLE_INSTANCE/httpConfig/ohs/diagnostics/logs/OHS/ohs_component

● access_log and access_log.number—WebLogic-generated log filefor a managed server● console~OHS~1.log—Oracle HTTP Server-generated log file, consoleoutput● ohs_component.logOracle HTTP Server-generated log file

Start and stop logs EPM_ORACLE_INSTANCE/diagnostics/logs/starter (UNIX)

PRODUCT.log—Start and stop logs for each EPM System product

Services startup logs EPM_ORACLE_INSTANCE/diagnostics/logs/services (Windows)

PRODUCT-syserr.log and PRODUCT-out.log—Windows servicestartup logs; trace of messages through startup

Shared Services Registrylogs

MIDDLEWARE_HOME/user_projects/domains/domain name/servers/managed server name/logs

registry.log—Registry activity

Security logs CSS and Shared ServicesRegistry product activity:MIDDLEWARE_HOME/user_projects/domains/domain

SharedServices_SecurityClient.log—Native Directoryinitialization, CSS initialization

name/servers/managed server name/logs

WebLogic logs MIDDLEWARE_HOME/user_projects/domains/domain name/servers/managed server name/logs

access.log—WebLogic activity needed when contacting Oracle SupportServices.

Foundation Services Logs

Log Location Log Name and DescriptionFoundation Services:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

FoundationServices0.log—Server and security activity

Shared Services:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/

● SharedServices_Admin.log—Applications Groups management activity● SharedServices_Audit.log—Audit server errors while reading/writing auditinformation to the database or while configuring auditing● SharedServices_Audit_Client.log—Information about the audit client● SharedServices_CMSClient.log—Metadata Service client activity● SharedServices_Hub.log—Shared Services context listener and initialization activity● SharedServices_LCM.log—Lifecycle Management activity● SharedServices_Registry.log—Shared Services Registry activity● SharedServices_Security.log—User management, provisioning, authentication,and single sign-on activity● SharedServices_TaskFlow.log—Information about Taskflows

EPM Workspace:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

● Workspace.log–EPM Workspace error and informational messages● Framework.log:❍ EPM System common user interface framework error and informational messages❍ Miscellaneous messages; for example, locale detection

❍ Messages regarding BPMUI configuration files or registry settings❍ Any errors due to invalid configuration files; for example: corrupt BpmServer.properties or registry.❍ BPMUI security messages, including CSS initialization, logon/logout logs from the Webapplication, and CSS authentication error messages

Smart View Smart View is a client-side application. The name and location of the file where it logs events,errors, and other information are specified as options in Smart View. For more informationabout Smart View logging options, see the Oracle Hyperion Smart View for Office User'sGuide.

Performance Management ArchitectDimension Server logs:EPM_ORACLE_INSTANCE/diagnostics/logs/epma

● DimensionServer.log—Activities from Performance Management Architect DimensionServer; for example, all export activities and dimension manipulation

Performance Management Architect:Data Sync Web application server logs:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

● datasync.log—Logging information from Data synchronization activities; for example,validation and execution errors from connectors● EpmaDataSync0.log—Performance Management Architect Web- tier activities; forexample, deployment activities, LCM activities, and product interaction activities

Performance Management Architect:Web application server logs:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

● epma.log—Logging information from Web reports● EpmaWebReports0.log—Performance Management Architect Web-tier activities

Calculation Manager:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

● apsserver.log—Generates communication logs between Calculation Manager andEssbase servers● CalcManager.log—Generates all Calculation Manager Web tier activities● CalcMgr0.log—Generates all Calculation Manager activities

Essbase Logs

The following table contains information about Essbase product family logs that use ODL

format:

• Essbase

• Administration Services

• Essbase Studio

• Provider Services

Log Location Log Name and DescriptionEssbase:EPM_ORACLE_INSTANCE/diagnostics/logs/essbase/essbase_0

● Essbase Server log:ESSBASE_ODL.logEssbase Server activities and errors● Essbase application log:/app/APPLICATION_NAME_ODL.logEssbase application activities and errors● Data load log:dataload_ODL.errData load and dimension build errors● SSAUDIT log files:dbname_ODL.atx and dbname_ODL.algSuccessfully completed spreadsheet update transactions. These are SSAUDIT log files; file name and locationare specified through an essbase.cfg setting. See “Monitoring Data, Applications, and Databases” in theOracle Essbase Database Administrator's Guide and the Essbase Technical Reference.● Exception log:log0000x.xcpErrors that result when Essbase Server stops abnormally● Essbase Server Lease Manager log:leasemanager_server_HOSTNAME.logEssbase Server Lease Manager information● Essbase Agent Lease Manager log:leasemanager_essbase_HOSTNAME.logAgent Lease Manager information

Essbase Studioupgrade log: EPM_ORACLE_INSTANCE/diagnostics/logs/upgrades

EssbaseStudioServer.log–Essbase Studio upgrade activity

Essbase staging tool:The working directory

essStaging.log–Errors that result when the staging tool (essStage.bat | sh prepares configuration andsecurity information, data, and applications for file transfer during an upgrade.For more information about the stating tool, see “Preparing Essbase Data for Upgrading” in Chapter 5, “UpgradingEPM System Products,” in the Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Guide.

Essbase Serverrehosting log:EPM_ORACLE_INSTANCE/diagnostics/logs/essbase

EssbaseRehost.log–Errors recorded by the Essbase rehosting tool when it rehosts Essbase connections duringan upgrade.For more information about Essbase Server rehosting, see “Rehosting Essbase Server” in Appendix B, “RehostingFoundation Services Web Application and Essbase Server,” of

the Oracle Hyperion Enterprise PerformanceManagement System Installation and Configuration Guide.

Essbase SecurityClient log:EPM_ORACLE_INSTANCE/diagnostics/logs/essbase

Security_client.log—Tracking of EPM System component and CSS communications with native provider.Also records the JDBC configuration from registry in this log file for any binds with native providers.

Oracle ProcessManager andNotification Serverlogs: EPM_ORACLE_INSTANCE/diagnostics/logs

● OPMN server log:/OPMN/opmn/opmn.logDiagnostic information that the OPMN server prints for various operations performed against a managedcomponent (Essbase). This log contains information about when Essbase starts, stops, and how many retryattempts are made to start and stop.● Essbase console log:/OPMN/opmn/console~ESSBASE_CLUSTER_NAME~ESSBASE_PROCESS_TYPE~AGENT~1.LOGAll console messages are directed to a file that is called the "console" output file for a managed process, inthis case, Essbase. Essbase often writes the same log file entries to Essbase.log and stdout; thereforethere might be duplicate entries in Essbase.log and this console log file.● OPMN Forward Ping log:/OPMN/opmn/EssbasePing.logOPMN Forward Ping information

Essbase Plugin logs:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs/essbase/lcm

essbaseplugin_ODL.log—Log statements related to the LCM artifact listing

AdministrationServices:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logsNote: To enableconsole logging, inadmincon.lax, setthe Java optionparameter –DEAS_CONSOLE_LOG. toTrue.

● easserver.log—Administration Services Server activity● EssbaseAdminServices0.log—Web application activity

Essbase Studio: server.log—Essbase Studio server activity

EPM_ORACLE_INSTANCE/diagnostics/logs/esbstudio

Provider Services:MIDDLEWARE_HOME/user_projects/domains/domainname/servers/managed servername/logs

● AnalyticProviderServices0.log—Web application activity● apsserver.log—Provider Services activity

Essbase Failover Logs

OPMN manages Essbase; therefore, the first set of logs to consult are the OPMN log files for

Essbase. However, a failure reported in these log files may point to activity in the back-end

Essbase log files that will help diagnose the problem.

To properly diagnose error conditions, use the Essbase and OPMN log files listed in above Table

and chain the log entries, known as log chaining, across the various processes according to the

time line in which they occurred. There are many possible scenarios of issues involving runtime

failures that affect failover.

The following files are key log files when Essbase runs in failover mode. See above Table for the

location and description of these logs.

• Essbase Server log

• Essbase Server Lease Manager log

• Essbase Agent Lease Manager log

• OPMN server log

• Essbase console log

• OPMN Forward Ping log

Managing Applications, Databases, and Database Artifacts

Copying or Migrating Applications

You can copy an application to any Essbase Server to which you have appropriate access. You

can copy (migrate) an entire application to another Essbase Server, or you can copy an

application on the same Essbase Server. For example, you may need to migrate an entire

application from a development server to a production server. Or, you may want to copy an

application on the same server for testing or for backup purposes.

Essbase copies applications differently, depending on whether you are copying to the same

Essbase Server or to a different Essbase Server. When you migrate applications, you can select

the artifacts to migrate, such as calculation scripts, report scripts, rules files, custom-defined

macros and functions, substitution variables, and filters. You can also specify how user and group

security is migrated.

To copy an application, use a tool:

Tool TopicMaxL create application asESSCMD COPYAPPAdministration Services Copying Applications

Renaming Applications

When you rename an application, the application and its associated directory (ARBORPATH/

app/appname) are renamed. All artifacts within the application (for example, databases or

calculation scripts) with the same name as the application are not renamed

Tool TopicMaxL alter applicationESSCMD RENAMEAPPAdministration Services Renaming Applications

Deleting ApplicationsWhen you delete an application, all artifacts within the application also are deleted. The

ARBORPATH/app/appname directory and all files in the directory are deleted.

Tool TopicMaxL drop applicationESSCMD DELETEAPPAdministration Services Deleting Applications

Copying Databases

You can copy a database in an application to any Essbase Server and application to which you

have appropriate access. You can copy (migrate) an entire database to another Essbase Server,

or you can copy a database on the same Essbase Server. For example, you may need to migrate

an entire database from a development server to a production server. Or, you may want to copy

a database on the same server for testing or for backup purposes. Essbase copies databases

differently depending on whether you are copying to the same Essbase Server or to a different

Essbase Server. See “Copying Databases” in Oracle Essbase Administration Services Online Help.

Administration Services provides a Migration Wizard that helps you migrate applications and

databases. See “Migration Wizard” in Oracle Essbase Administration Services Online Help.

When you copy a database, all files associated with the database, except data files (.pag

and .ind), are copied to the destination application. Before copying, make sure you have enough

disk space to contain a full copy of the database and its related files.

Tool TopicMaxL create database asESSCMD Copying DatabasesAdministration Services Copying Databases

Renaming Databases

When you rename a database, the database and its associated directory (ARBORPATH/app/

appname/dbname), and the outline file (.otl) are renamed. All other artifacts in the database

(for example, calculation scripts) with the same name as the database are not renamed.

Tool TopicMaxL alter databaseESSCMD RENAMEDB

Administration Services Renaming Databases

Deleting Databases

When you delete a database, all artifacts within it are also deleted. The ARBORPATH/app/

appname/dbname directory and all files located in the directory are deleted.

Tool TopicMaxL drop databaseESSCMD DELETEDBAdministration Services Deleting Databases

Starting and stopping Essbase Products

Foundation Services Managed Server Application Server

The following table describes the services and processes for the Foundation Services Managed

Server application server, which includes Shared Services, and EPM Workspace Web

applications.

Information Type DetailsWindows Start Menu

Command

Select Start, then Programs, then Oracle EPM System, then

Foundation Services, and then Start Foundation

ServicesRegistered Service Name HyS9Foundation ServicesDisplay Name in Windows

Services Control Panel

Hyperion Foundation Services - Managed Server

Description Hyperion Foundation Services support Hyperion applications,

including authentication, user provisioning, task

flow management, data and metadata synchronizationWindows Startup Script EPM_ORACLE_INSTANCE/bin/startFoundationServices.batUNIX Startup Script EPM_ORACLE_INSTANCE/bin/startFoundationServices.shWindows Stop Script EPM_ORACLE_INSTANCE/bin/stopFoundationServices.batUNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopFoundationServices.sh

Web Server

The following table describes the services and processes for the Web server. EPM System Installer

installs Oracle HTTP Server.

The Oracle HTTP Server service is managed with OPMN.

Information type DetailsDisplay Name in Windows


Oracle Process Manager (ohsInstanceInstanceNumber)

Note that this menu command directs to the start script,

which redirects Oracle HTTP Server to start using OPMN.

The OPMN start script opmnctl.bat is located in

EPM_ORACLE_INSTANCE/httpConfig/ohs/bin.

IIS: IIS Admin ServiceDescription IIS: Enables this server to administer Web and FTP

services. If this service is stopped, the server will be

unable to run Web, FTP, NNTP, or SMTP sites or

configure IIS. If this service is disabled, any services that

explicitly depend on it will fail to start.Windows Startup Script (For Oracle

HTTP Server installed by EPM System

Installer only)

EPM_ORACLE_INSTANCE/bin/startOHS.bat

Note that this start script redirects Oracle HTTP Server to

start using OPMN. The OPMN start script opmnctl.bat is

located in

EPM_ORACLE_INSTANCE/httpConfig/ohs/bin.Unix Startup Script (For Oracle


Installer only)

EPM_ORACLE_INSTANCE/bin/startOHS.sh

Note that this start script redirects Oracle HTTP Server to

start using OPMN. The OPMN start script opmnctl is

located

in EPM_ORACLE_INSTANCE/httpConfig/ohs/binWindows Stop Script (For Oracle


Installer only)

EPM_ORACLE_INSTANCE/bin/stopOHS.bat

Unix Stop Script (For Oracle


Installer only)

EPM_ORACLE_INSTANCE/bin/stopOHS.sh

Essbase Server

During installation, EPM System Installer installs OPMN and registers Essbase Server for

OPMN. OPMN manages the Essbase Agent, which manages the Essbase Server.

In a Windows environment, before you launch Essbase, change the OPMN service (Oracle

Process Manager (instanceName)) to start as a named user so that the shared network files are

accessible.

Navigate to EPM_ORACLE_INSTANCE/bin and use the following commands to start and stop

Essbase Server:

• opmnctl startproc ias-component=EssbaseInstanceName or ./opmnctl startall

• opmnctl restartproc ias-component=EssbaseInstanceName

• opmnctl stopproc ias-component=EssbaseInstanceName

• opmnctl status

where EssbaseInstanceName is one of the following:

• If you have not implemented clustering, EssbaseInstanceName is the name of the Essbase

instance that you entered on the “Essbase Server Configuration” page during configuration

with EPM System Configurator.

• If you have implemented clustering, EssbaseInstanceName is the name of the Essbase

cluster that you entered on the “Set up Essbase Clusters” page during configuration with

EPM System Configurator.

If you are using Essbase in a clustered environment, there are additional steps required to set up

Essbase failover on both nodes of the cluster.

The following table describes additional methods for starting and stopping Essbase Server. Note

that the Essbase Server start and stop scripts redirect to OPMN.


Command

Select Start, then Programs, then Oracle EPM System, then Essbase,

then Essbase Server, and then Start Essbase

This command launches startEssbase.bat (and redirects to OPMN)Registered Service Name Oracle Process Manager (instanceName)Display Name in Windows


Oracle Process Manager (instanceName)

Windows Startup Script Essbase Server —

EPM_ORACLE_INSTANCE/bin/startEssbase.bat (redirects to

OPMN)

Each instance of Essbase Server has its own startup script. If you

configured an additional instance of Essbase,

startEssbase.bat|sh is located in additionalInstanceLocation/bin.

Launch the start script from this

location to launch this instance of Essbase.

ESSCMD —

EPM_ORACLE_INSTANCE/EssbaseServer/EssbaseServerInstance

Name/bin/startEsscmd.bat (also available in the /EssbaseClient

directory)

essmsh —


Name/bin/startMaxl.bat (also available in the /EssbaseClient

directory)

All the scripts call setEssbaseEnv.bat to set up ESSBASEPATH,

ARBORPATH, and PATH before startingUNIX Startup Script Essbase Server —

EPM_ORACLE_INSTANCE/bin/startEssbase.sh (redirects to

OPMN)

Each instance of Essbase Server has its own startup script. If you

configured an additional instance of Essbase,

startEssbase.bat|sh is located in additionalInstanceLocation/bin.

Launch the start script from this

location to launch this instance of Essbase.

ESSCMD —


Name/bin/startEsscmd.sh (also available in the /EssbaseClient

directory)

essmsh —


Name/bin/startMaxl.sh (also available in the /EssbaseClient

directory)

All the scripts call hyperionenv.doc to set up ESSBASEPATH,

ARBORPATH, and PATH before starting.

When running Essbase manually from a console, the console cannot

be set to UTF-8 encoding.Windows Stop Script Essbase Server — EPM_ORACLE_INSTANCE/bin/stopEssbase.bat

(redirects to OPMN)UNIX Stop Script Essbase Server — EPM_ORACLE_INSTANCE/bin/stopEssbase.sh

(redirects to OPMN)

Stopping Essbase Server can take some time, depending on how many Essbase applications are

running on the server. To stop Essbase Server, you need Administrator permissions.

Administration Services Server

The following table describes the services and processes for the Administration Services server.


Command


Essbase, then Essbase Administration Services,

and then Start Administration ServicesRegistered Service Name Hys9easDisplay Name in Windows


Hyperion Administration Services - Web Application

Description HyS9eas - Controls the running of an Applications ServerWindows Startup Script EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.batUNIX Startup Script EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.shWindows Stop Script EPM_ORACLE_INSTANCE/bin/stopEssbaseAdminServices.batUNIX Stop Script EPM_ORACLE_INSTANCE/bin/startEssbaseAdminServices.sh

Integration Services Server

The following table describes the services and processes for the Integration Services server.


Command


Essbase, then Integration Services, and then ServerRegistered Service Name Hyperion Integration ServicesDisplay Name in Windows


Hyperion Integration Services

Windows Startup Script EPM_ORACLE_INSTANCE/bin/startEisServer.batUNIX Startup Script EPM_ORACLE_INSTANCE/bin/startEisServer.shWindows Stop Script EPM_ORACLE_INSTANCE/bin/stopEisServer.bat

Note that you must manually stop the Integration Services service

manually using the Task ManagerUNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopEisServer.sh

Note that you must manually stop the Integration Services service

by stopping the process.

Essbase Studio ServerThe following table describes the services and processes for the Essbase Studio server.


Command


Essbase, then Essbase Studio, and then Start

ServerRegistered Service Name Hyperion Studio Service BPMS bpms1Display Name in Windows


Hyperion Studio Service BPMS bpms1

Windows Startup Script EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.batUNIX Startup Script EPM_ORACLE_INSTANCE/bin/startBPMS_bpms1_Server.shWindows Stop Script EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.batUNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopBPMS_bpms1_Server.sh

Provider Services Application Server

The following table describes the services and processes for the Provider Services application

server.


Command

Select Start, then Programs, then Oracle EPM System, then Essbase,

then Provider Services, and then Start

Analytic Provider ServicesRegistered Service Name HyS9apsDisplay Name in Windows


Hyperion Provider Services - Web Application

Description Provide access service to Hyperion Provider ServicesWindows Startup Script EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.batUNIX Startup Script EPM_ORACLE_INSTANCE/bin/startAnalyticProviderServices.shWindows Stop Script EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.batUNIX Stop Script EPM_ORACLE_INSTANCE/bin/stopAnalyticProviderServices.sh

Launching Clients

This section describes how to launch EPM System clients. It lists default URLs and script names

as appropriate. Most clients can also be started using the Windows Start menu.

The following table describes the URLs and scripts for launching EPM System clients.

Client URL Script or Other Launch MethodOracle Hyperion Shared

Services Console

http://dba1.appsahyd.com:19

000/interop/

From the Start menu, select Programs,

then Oracle EPM System, then

Foundation Services, and then Shared

Services URL.

Note: The Start menu item is available

only on the machine on which you

installed the Web server.EPM Workspace http://dba1.appsahyd.com:19

000/workspace/


then Oracle EPM System, then

Workspace, and then Workspace URL.

Note: The Start menu item is available

only on the machine on which you

installed the Web server.Smart View NA Use the Smart View menu or Smart View

ribbon in Microsoft Excel, Microsoft

Word, or Microsoft PowerPointAdministration

Services Console

http://dba1.appsahyd.com:19

000/easconsole/console.html


then Oracle EPM System, then Essbase,

then Essbase Administration Services, and

then Start Administration Services

Console.Oracle Essbase

Integration Services

Console

NA From the Start menu, select Programs,


then Integration Services, and then

Console.

Or

EPM_ORACLE_HOME/products/Essbas

e/eis/console/bin/startOlapbldr.batEssbase Studio Console NA From the Start menu, select Programs,


then Essbase Studio, and then Essbase

Studio Console.

Or

EPM_ORACLE_HOME/products/Essbas

e/EssbaseStudio/Console/startStudio.batOracle Essbase

Spreadsheet

Add-in

From the Excel menu bar, select Essbase

to display the Essbase menu.

essbase guide

Documents