OLAP Setup and User's Guide

Installing DB2 OLAP Server

You can use DB2 OLAP Server with a new or existing DB2 RDBMS installation, or with a multidimensional storage manager. The Dual Storage Manager component enables you to create applications that use either storage manager, and the ability to switch storage managers for existing applications. See "Selecting a Storage Manager".

If you are installing DB2 OLAP Server and you want to use an RDBMS, you must install the RDBMS separately. DB2 and DB2 Universal Database can be installed either before or after you install DB2 OLAP Server. If you install DB2 Universal Database, make sure that you install the latest DB2 Universal Database fixpack, available from the DB2 Service and Support Web page at http://www.ibm.com/software/data/db2/db2tech/

If you want to install DB2 OLAP Server and Information Catalog Manager on the same system, we recommend that you install both products at the same time.

Information You Need Before You Install

During installation you are asked what edition and options you purchased. This information is used to build a license key for DB2 OLAP Server.

If your installation is new, or if you do not have an existing RDBMS configuration file (rsm.cfg), you will be prompted for information about your relational database name, user ID, and password. You can either add this information during installation, or update the rsm.cfg file after installation is complete.

You need the following information about your RDBMS:

Relational database name: The name of the relational database where you want to store your multidimensional data.
Relational database user ID: The user ID that you want DB2 OLAP Server to use to log on to your relational database.
Relational database password: The password for the user ID that you want DB2 OLAP Server to use to log on to your relational database. This password is stored unencrypted in the relational storage manager configuration file (rsm.cfg). You can choose to leave the user ID and password fields blank. If you do not specify a user ID or password, DB2 OLAP Server will attempt to log on to the relational database using the ID and password you used to log on to your workstation. If this user ID does not have access to the relational database, you will be denied access to the relational database.

DB2 OLAP Server Components and Add-ons

Components of DB2 OLAP Server version 7.1:

Documentation
Information Catalog Manager
Client components:
- Hyperion Essbase Server
- The ESSCMD command line interface
- Multidimensional Storage Manager
- IBM's Relational Storage Manager
- Application Manager
- Spreadsheet Add-ins
- Integration Server Desktop
Server components:
- DB2 OLAP Server
- Sample applications
Add-on components, that you can purchase:
- DB2 OLAP Integration Server, including the Administration Manager
- ODBC drivers for the DB2 OLAP Integration Server
- SQL Interface, including ODBC drivers
- API
- Currency Conversion
- Extended Spreadsheet Toolkit
- Web Gateway
- Objects
- Allocations Manager
- Partitioning

Installation Steps for DB2 OLAP Server

To install DB2 OLAP Server:

Log on to the server as a user ID that has root privileges.
If you are installing on Solaris Operating Environment, set your locale to C. When you have finished installing, make sure the locale is still C when you start the server for the first time. Using the correct locale ensures that the administration user ID will be configured correctly.
If your workstation has a CD-ROM drive, follow these steps:
1. Insert the DB2 OLAP Server CD into your CD-ROM drive.
2. Use the ls command to find olapinst on the CD. The file name is either uppercase or lowercase, depending on your operating system.
3. Enter olapinst to run the setup script from the DB2 OLAP Server CD.
  If a multi-threaded environment is not detected, you will receive an error.
4. Continue at step 5.
If your workstation does not have a CD-ROM drive, follow these steps:
1. Create a temporary directory for use during installation.
2. Use FTP, NFS, or any similar utility to copy the DB2 OLAP Server files into your temporary directory.
3. Change to the temporary directory.
4. Use the ls command to find olapinst in the temporary operating system subdirectory, for example, look in /temp/aix for the AIX installation file. The file name is either uppercase or lowercase, depending on your operating system.
5. Enter olapinst to run the setup script from the temporary directory.
  If a multi-threaded environment is not detected, you will receive an error.
When prompted, specify the directory to which you want to install DB2 OLAP Server. In order to access your current licensing information, you can enter a directory that already exists. If you enter a new directory, you will receive a message asking if you want to enter your existing directory in order to access your current license files. You can either specify a new directory name or use the existing one. DB2 OLAP Server will be installed to whatever directory you specify.
When prompted for licensing information, select the add-on features that you purchased. Information about the add-on features is used to build the license key for DB2 OLAP Server.
You will be presented with a list of components to install. The components in the list are the ones that you are licensed to install. Select the components that you want to install.
Recommendation. If you want to install DB2 OLAP Server and Information Catalog Manager on the same system, we recommend that you install both products at the same time.
Optional. Select the Sample applications.
You can load data into the sample applications using the Application Manager.
If you are installing the server, and the installation program does not detect an existing rsm.cfg file, you will be asked to supply the relational database name, the relational database user ID and password, and the database table space clause. These values are used to update the parameters in the relational configuration file.
If you are installing the SQL Interface, see "Loading and Configuring ODBC for the SQL Interface" to set up ODBC.
For Solaris Operating Environment only: Run the Bourne shell script root.sh from the root account. The script is in the $ARBORPATH/bin directory and performs additional installation tasks, such as setting sticky bits on binaries and shared libraries. For example, to log in as the root user and run root.sh, type the following commands:
```
$ su -
PASSWORD:  (enter your password)
# cd /home/essbase/bin
# sh root.sh
# exit
```
The root.sh script asks whether you installed the SQL Interface module. If you installed it, root.sh prompts you for the full path and file name of the libodbc.so shared library. Enter the full path and the file name, such as /home/essbase/dlls/libodbc.so.
For HP-UX only: Enter the following command in the $ARBORPATH/bin directory:
```
ln -f -s /opt/IBMdb2/V5.0/lib/libdb2.sl libesssql.sl
```
where /opt/IBMdb2/V5.0/ is the installation directory for DB2 UDB.
Use the information in the essbaseenv.doc file to update the environment variables. The essbaseenv.doc file is created by the installation program. See Updating the Environment Variables for more information.

The installation program creates the following directory structure:

<installation directory>
  bin
  app
  locale
  is

The bin directory contains the DB2 OLAP Server program.

The app directory contains a subdirectory for each Essbase application you create. An activity log file, which tracks all user requests made to the application or to databases within the application, is stored in the top directory for each application.

[ Top of Page | Previous Page | Next Page ]