Installation locations
The installation directory is the location of product artifacts after a package, product, or component is installed. The following table lists the conventions that are used to refer to the installation location of installed components and products:
If you're using IBM OpenPages for IBM Cloud Pak for Data, see Files and directories in IBM OpenPages for IBM Cloud Pak for Data.
|
Directory |
Description |
|---|---|
|
<installation_server_home> |
The directory where the IBM OpenPages installation server is installed. For example:
|
|
<agent_home> |
The directory where the IBM OpenPages installation agent is installed on a remote server. For example:
|
|
<OP_HOME> |
The directory where OpenPages is installed. For example:
In the installation app, you specify the <OP_HOME> directory in the OP Home Directory field on each Application Server card. |
|
<DB2_HOME> |
The installation location of the IBM® Db2® software. For example:
|
|
<WLP_HOME> |
The installation location of IBM WebSphere® Liberty. For
example:
|
| <WLP_USER_HOME> |
The location of OpenPages application files and server configuration files. For example:
|
|
<COGNOS_HOME> |
The installation location of IBM Cognos® Analytics. For example:
|
|
<JAVA_HOME> |
The installation location of the IBM Semeru Runtimes. IBM Semeru
Runtimes example on an
application server:
JRE example on a reporting server where IBM Cognos
Analytics is installed:
IBM Semeru
Runtimes example on a
search server:
|
|
<CC_HOME> |
The installation location of OpenPages Reporting. For example:
|
| <SEARCH_HOME> |
The installation location of global search. The <SEARCH_HOME> directory contains the opsearchtool.jar, Apache Solr, and other global search files. The global search indexing directory is also stored in the <SEARCH_HOME> directory. For example:
In the installation app, you specify the <SEARCH_HOME> directory in the Search Home Directory field on the Search Server card. |