This chapter introduces the file types that Hyperion Essbase uses, describes operations that you can perform on Hyperion Essbase files, and discusses some of the issues that you face when working with Hyperion Essbase files on different platforms.
This chapter contains the following sections:
The following table lists the file types that Hyperion Essbase uses to store applications and databases:
The following table lists the types of Hyperion Essbase files that are stored in the \ESSBASE\BIN
directory:
The following table lists the types of Hyperion Essbase files that are stored in the \ESSBASE\API
sub-directories:
You can use Hyperion Essbase Application Manager to copy, rename, delete, and lock each of the following:
Hyperion Essbase stores each application as a collection of files in the Hyperion Essbase application directory (for example,\ESSBASE\APP\
appname)
on the server. Hyperion Essbase stores each database as a collection of files on the database directory of the server (for example,\ESSBASE\APP\
appname\
dbname).
Files that are related to applications and databases are called objects. The common types of objects are outlines, calc scripts, report scripts, rules files, and data sources. You typically store objects on the server in the appname or dbname directory or on the client machine under the \ESSBASE\CLIENT\
appname or dbname directory.
In addition to the standard object types, Hyperion Essbase also supports the following objects:
.OCX
) for creating OLAP-aware modules. This feature is available with Hyperion Objects, licensed separately.
When you copy an application, Hyperion Essbase copies all files associated with the application to the destination application. Before copying, make sure that you have enough disk space to contain a full copy of the application, databases, and related files.
Figure 49-1: Application Copy Dialog Box
\ESSBASE\APP
directory.
You can also use create application in MaxL or the COPYAPP command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When you rename an application, the application and the application directory (ESSBASE\APP\
appname) are renamed. All objects within the application (for example databases or calc scripts) with the same name as the application are not renamed.
Figure 49-2: Rename Application Dialog Box
\ESSBASE\APP
directory.
You can also use alter application in MaxL or the RENAMEAPP command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When you delete an application, all objects within the application are also deleted. The\ESSBASE\APP\
appname directory and all files located in the directory are deleted.
Figure 49-3: Confirm Delete Dialog Box for Applications
You can also use drop application in MaxL or the DELETEAPP command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When you copy a database, all files associated with the database are also copied to the destination application. Before copying, make sure you have enough disk space to contain a full copy of the databases and of the related files.
Figure 49-4: Database Copy Dialog Box
You can also use create database in MaxL or the COPYDB command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When you rename a database, the database, the database directory (ESSBASE\APP\
appname\dbname), and the outline file (.OTL
) are renamed. All other objects in the database (for example, calc scripts) with the same name as the database are not renamed.
Figure 49-5: Rename Database Dialog Box
\ESSBASE\APP\
appname directory.
You can also use alter database in MaxL or the RENAMEDB command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
When you delete a database, all objects within the database are also deleted. The \ESSBASE\APP\
appname\
dbname directory and all files located in the directory are deleted.
Figure 49-6: Confirm Delete Dialog Box for Databases
You can also use drop database in MaxL or the DELETEDB command in ESSCMD to perform this task. For more information, see the online Technical Reference in the DOCS directory.
|
Objects related to databases or applications are outlines, calc scripts, report scripts, rules files, and data sources. You can copy any of these objects, except outlines, to another application, database, server, or client location.
Figure 49-7: Copy to Server Object Dialog Box
You can rename any object, except outlines. An outline always has the same name as the database, so you need to rename the database to rename the outline.
Figure 49-8: Rename Object Dialog Box
You can delete any object, except an outline. An outlines is a required part of a database, so you need to delete the database to delete the outline.
Figure 49-9: Confirm Delete Dialog Box for Objects
Hyperion Essbase uses a check-out facility for server-based objects to ensure that no more than one user attempts to modify an object at one time. This section describes how to lock and unlock objects.
Note: | Locking objects is not the same as locking data blocks. The Hyperion Essbase Kernel handles locking for data blocks, but not for objects. See Ensuring Data Integrity for information about locking data blocks. |
By default, whenever a user opens a server-based object, Hyperion Essbase locks the object. If a second user attempts to open the same object, a message is displayed. The message indicates that the object is locked and tells the user who locked it.
You can avoid the lock error by unchecking "Lock file" in the Application Desktop window before attempting to open an object. This action essentially opens the file in read-only mode, and you cannot save any changes you make.
There are two ways to unlock a previously locked object:
Note: | Users can unlock only objects that they have locked themselves. A user with supervisor privileges can unlock any object. |
The Hyperion Essbase OLAP Server runs on multiple platforms, including Windows platforms and UNIX platforms. For a list of supported platforms and information on how to install and configure the Hyperion Essbase server on each platform, see the Hyperion Essbase Installation Guide.
After you install an application, you may want to port the application to a server that may be running a different operating system. This section describes how to port an installed Hyperion Essbase application to another Hyperion Essbase server machine.
Porting Hyperion Essbase applications across servers involves these steps:
If you are porting a Hyperion Essbase application to a server running a different operating system, you need to identify which Hyperion Essbase files are compatible with the new operating system.
The following file types are compatible between operating systems:
.csc
) and report scripts (.rep
). Also, data files can be ASCII text files.
.rul
.
.otl
.
The following file types are incompatible between operating systems and need to be redefined or reloaded on the new server:
.db
and.dbb
.pag
.ind
.sec
.app
and.apb
.esm
Note: | If you are using the Linked Reporting Objects feature, you need to relink any files or cell notes on the new server. For more information, see Linking Objects to Hyperion Essbase Data. |
When transferring files to a UNIX system, you need to be aware of the case of file names. UNIX is a case-sensitive operating system, and files are recognized only if they have the correct case. For example, in certain MaxL or ESSCMD operations, you need to specify a file name, and the file name must be entered with the correct case.
The Hyperion Essbase system files use the following naming conventions on UNIX systems:
ESSBASE
, ESSCMD
).
.a
and are in lowercase (libessnet.a
).
.sl
on HP-UX,.so
on Solaris, and.a
on AIX. These file names are in lowercase (for example, libesscur.sl
).
.sec
and are in lowercase (essbase.sec
).
.mdb
and are in lowercase (essbase.mdb
).
.hlp
and are in lowercase (esscmd.hlp
).
Hyperion Essbase files on UNIX systems are capitalized with proper case: the first letter is uppercase, and the remaining letters are lowercase. The following table gives examples of names for different file types:
Note: | The application name is an exception to the above rule. The application name can be in lower case. |
Table 49-5 lists several examples of valid and invalid file names on UNIX systems:
Valid File Names | Invalid File Names |
Model.csc
| MODEL.CSC
|
Monthly.rep
| Monthly.Rep
|
Forecast.otl
| forecast.otl
|
Actuals.rul
| AcTuAlS.rUl |
My_File.txt
| My_File.Txt
|
If two servers are connected, you can create the application and database directories on the new server and use either FTP (File Transfer Protocol) or Hyperion Essbase Application Manager to transfer the compatible application files. If the servers are not connected, you need to redefine server information on the new server before reloading the database.
Using FTP, you can transfer files directly between operating systems. You should transfer only the files compatible between operating systems, and you should transfer the files in binary mode.
If you have files with the wrong case on a UNIX server, Hyperion Essbase Application Manager can see these files but cannot open them. After you use FTP to transfer files, you should rename the files on the server to ensure that they are capitalized with proper case. Alternatively, you can use FTP to rename the file when you transfer the file:
ftp>put oldfile Newfile
Using Hyperion Essbase Application Manager, you can transfer files from the client machine to the server by using File > Save As. For example, you can connect to a Windows NT server, open an outline, and then save it to a UNIX server. The file types you can transfer from Hyperion Essbase Application Manager are outline files, report scripts, calc scripts, and rules files.
When you save a file from Hyperion Essbase Application Manager to a UNIX server, proper case is applied automatically regardless of what case you type.
If the server you are porting to is not connected to the existing server, you need to redefine some Hyperion Essbase server information on the new server.
.otl
) for the databases that you want to port from the old server to the same directory location on the new server. Make sure the application is not running while you copy these files.
Database files, such as.db
, .pag
, .esm
, and.ind
, are not compatible between operating systems. If you port an application to a server on a different operating system, you need to repopulate the database by reloading the data from a data file and a data load rules file (if applicable). One way you can reload is to export the data to an ASCII text file, transfer the text file to the new server, and then use the text file to load data.
Copyright © 1991-2000 Hyperion Solutions Corporation. All rights reserved.