You must set environment variables to identify the location of the JVM environment and the library path. You can set environment variables using any of the following methods:
On Windows, set a system or user variable, or edit the application server’s startup environment script.
If you set a user variable, ensure that you set it for the user account that will run the application server, or administration console.
On UNIX and Linux, set an environment variable in the user profile, or edit the application server’s startup or environment script.
For information about editing an application server’s startup script, see Change the Application Server Startup Script.
Tip: Most application server versions ship with a script specifically intended for setting environment variables. For example, some WebSphere versions ship with setupCmdLine.bat or setupCmdLine.sh, WebLogic ships with setEnv.cmd or setEnv.sh, and Oracle ships with iasenv.bat or iasenv.sh. These scripts can be modified to set appropriate values for use with Cognos components. Most of these scripts set the JAVA_HOME environment variable by default.
Set the JAVA_HOME environment variable to point to the JVM used by the application server.
Tip: If the application server ships with a JVM, then the JAVA_HOME environment variable must be set to reference it.
Cognos Configuration uses this variable to create encryption keys for Cognos components that are compatible with the JVM used by the application server.
For example, for WebLogic under Windows, the JVM used by the application server is specified as:
drive:/WebLogic_location/jdk142_04
Append c8_location/bin to the appropriate environment variable.
This variable is used to locate the Cognos library files.
Operating system | Environment variable |
Windows | PATH |
AIX | LIBPATH |
Solaris and Linux | LD_LIBRARY_PATH |
HP-UX | SHLIB_PATH |
Tip: To install multiple instances of Cognos 8 on a single server, set the PATH, LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH variable within the application server instance scope and not as a global variable to ensure that each instance has a unique value.
Note: The CRN_ROOT and COG_ROOT variables are no longer required in a non-clustered environment and should be removed if they were used in a previous installation.