After installing DB2 OLAP Server and DB2 OLAP Integration Server on Linux, AIX, Solaris, or HP-UX, you must update the environment variables on your system. The installation program creates scripts you can use to apply the environment variables, and stores them in the $ARBORPATH or $ISHOME directory. The scripts are listed in Table 17.
Product | Shell | Script | Sets environment variables for: |
---|---|---|---|
DB2 OLAP Server | Korn or Bourne | essbaseenv.sh | DB2 OLAP Server; ODBC |
CShell | essbaseenv.csh | DB2 OLAP Server; ODBC | |
Korn or Bourne | essjava.sh | Java | |
CShell | essjava.csh | Java | |
DB2 OLAP Integration Server | Korn or Bourne | hisjava.sh | DB2 OLAP Server; ODBC; Java |
CShell | hisjava.csh | DB2 OLAP Server; ODBC; Java |
If you run both DB2 OLAP Server and DB2 OLAP Integration Server on the same UNIX system, IBM recommends that you set the environment variables for each server component separately, in separate UNIX sessions. For example, you can take the following steps:
For example, in the .profile file, you can add the following command for each script:
. /full path/script name
where full path is the path where the script file is stored, and script name is the name of the script for the UNIX shell you use. After entering the statement, you must log out and then log back in to enable the new settings to take effect.
Alternatively, instead of updating the .cshrc or .profile files, you can manually invoke the essbaseenv.sh and essjava.sh scripts each time you start a session to run DB2 OLAP Server, and in the session running DB2 OLAP Integration Server, invoke only the hisjava.sh script.
The $ARBORPATH/essbaseenv.doc file contains additional information about setting environment variables in your environment.
Optionally, you might need to take these additional steps:
The hisjava.csh and hisjava.sh scripts provided with DB2 OLAP Integration Server set the library path to access the DataDirect ODBC drivers provided with the product. If you use these drivers, include either hisjava.csh or hisjava.sh in the login script for the user who runs DB2 OLAP Integration Server to set the required variables.
If you use ODBC drivers other than DataDirect, the provider typically provides a shell script to set the library path to access the driver. Add this shell script to the login script for the user who runs the DB2 OLAP Integration Server software.
An example of a shell script that sets the library path to access ODBC libraries on Solaris follows:
if env | grep LD_LIBRARY_PATH" > $ISHOME/esslib:$HYPERION_HOME/common /ODBC/Merant/4.2/lib:$LD_LIBRARY_PATH else LD_LIBRARY_PATH= $ISHOME/esslib:$HYPERION_HOME/ODBC/Merant/4.2/lib
For DB2 OLAP Integration Server, set the environment variables required for database client software in the login script of the user who runs DB2 OLAP Integration Server. These environment settings are required for ODBC access to the databases in the RDBMS that you are using. The database vendor typically supplies a shell script to set any environment variables required by the database client. Add this shell script to the login script for the user who runs the DB2 OLAP Integration Server software. For more information about how to set environment variables for the database client, see the database client installation documentation.
To verify that the database client software is set up correctly, log on as the user who runs DB2 OLAP Integration Server, and use a database utility to connect to the databases that you use with DB2 OLAP Integration Server.
If you are running Analytic Server on a Solaris system and you plan to use the Cache Memory Locking database setting, you must run the Bourne shell script root.sh.
It is not necessary to run root.sh unless you plan to use the Cache Memory Locking database setting on a Solaris system.
CAUTION: Using root.sh may interfere with SQL Interface. You may need to choose between SQL Interface and cache memory locking.
After you install Analytic Server, run root.sh from the root account. The script, located in ARBORPATH/bin, performs post-installation tasks. To run root.sh, log on as user root, and type the following commands:
$ su - Password: # cd /home/hyperion/essbase/bin # sh ./root.sh # exit
The script directs the following actions:
On Solaris:
libesssd.so.1 libessapi.so.1 libessnetu.so.1 libessotl.so.1 libessshr.so.1 libesssql.so.1 libessutl.so.1 libesssvrd.so.1 libesssm.so.1 libessdvrq.so.1 libglobalc.so:
DB2 OLAP Integration Server uses the cron scheduling daemon to perform scheduled member and data loads. This daemon must be started on the computer that runs DB2 OLAP Integration Server and the user who starts the program must be authorized to schedule cron jobs. For more information, see the documentation for the UNIX system you are using.
In order to schedule jobs for DB2 OLAP Integration Server, the crontab file must exist. You can check whether this file exists by running the following command in your environment:
crontab -l
If this file does not exist in your environment, you can create it manually by using the following command:
crontab -e
At this point, the file is open for editing. You can quit the file without saving it. For details on crontab settings, refer to the help for the UNIX operating system you are using.