Installation locations

Applies to: On premises

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:

Important: Directory locations that contain spaces are not supported. IBM OpenPages® or any software that is used by it must not be installed into a directory with spaces. For example, do not install database server, database client, or application server software into the Program Files directory.

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.

Table 1. Variable notations for installation directories

Directory

Description

<installation_server_home>

The directory where the IBM OpenPages installation server is installed.

For example:
  • On Windows: C:\IBM\OPInstall\OP_<version>_Installer.
  • On Linux®: /home/opuser/IBM/OPInstall/OP_<version>_Installer.

<agent_home>

The directory where the IBM OpenPages installation agent is installed on a remote server.

For example:
  • On Windows: C:\IBM\OPAgent.
  • On Linux: /home/opuser/IBM/OPAgent.

<OP_HOME>

The directory where OpenPages is installed.

For example:
  • On Windows: C:\IBM\OpenPages.
  • On Linux: /opt/opuser/IBM/OpenPages.

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:
  • On Windows: C:\IBM\SQLLIB.
  • On Linux: /home/db2inst1/sqllib.

<WLP_HOME>

The installation location of IBM WebSphere® Liberty.

For example:
  • On Windows: <OP_HOME>\wlp.
  • On Linux: <OP_HOME>/wlp.
<WLP_USER_HOME>

The location of OpenPages application files and server configuration files.

For example:
  • On Windows: <OP_HOME>\wlp-usr.
  • On Linux: <OP_HOME>/wlp-usr.

<COGNOS_HOME>

The installation location of IBM Cognos® Analytics.

For example:
  • On Windows: C:\IBM\cognos\analytics.
  • On Linux: /usr/IBM/cognos/analytics.

<JAVA_HOME>

The installation location of the IBM Semeru Runtimes.

IBM Semeru Runtimes example on an application server:
  • On Windows: C:\IBM\semeru_21_0_64.
  • On Linux: /opt/ibm/ibm-semeru_21_0_64.
JRE example on a reporting server where IBM Cognos Analytics is installed:
  • On Windows: C:\IBM\cognos\analytics\ibm-jre\jre .
  • On Linux: /usr/IBM/cognos/analytics/ibm-jre/jre.
IBM Semeru Runtimes example on a search server:
  • On Windows: C:\IBM\semeru_21_0_64.
  • On Linux: /opt/ibm/ibm-semeru_21_0_64.

<CC_HOME>

The installation location of OpenPages Reporting.

For example:
  • On Windows: C:\IBM\OpenPages\Reporting.
  • On Linux: /opt/IBM/OpenPages/Reporting.
<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:
  • On Windows: C:\IBM\OpenPages\OPSearch.
  • On Linux: /opt/IBM/OpenPages/OPSearch.

In the installation app, you specify the <SEARCH_HOME> directory in the Search Home Directory field on the Search Server card.