IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Assess your requirements
Installation directories for the product and profiles
The installation directories for IBM BPM are represented by several variables. The meaning of those variables can differ for a number of factors.
Variables used in the documentation
Several variables representing specific default directories are used throughout the documentation. These file paths are default locations. You can install the product and other components and create profiles in any directory for which you have write access. Multiple installations of IBM BPM products or components require multiple locations.
Here are the main variables used in the documentation:
- INSTALL_ROOT
- Installation location of IBM BPM. IBM BPM is always installed in the same location as the WebSphere Application Server ND installation with which it is associated.
- profile_root
- Location of an IBM BPM profile.
How variable meanings can differ
The meaning of variables used to represent installation directories can differ based on whether you are installing the product on a clean workstation or on a workstation that has an existing installation of WebSphere Application Server or WebSphere Application Server ND. The variables can also differ depending on whether you are performing the installation as a root (Administrator on a Windows system) or nonroot user.
Limitations of nonroot installers
Root, Administrator, and nonroot users can install the product. The default directories the installation program provides differ based on whether the user has root (Administrator) privileges. Root and Administrator users can register shared products and install into system-owned directories (globally shared resources that are available to all users), while nonroot users cannot. Nonroot users can install only into directories they own.
Default directories for Typical Installation
The following tables show the default installation locations of the IBM BPM base installation and its profiles during a typical installation.
Table 1.shows the default installation root directory into which the installation program installs both IBM BPM and WebSphere Application Server ND for both root (Administrator) and nonroot users.
INSTALL_ROOT default directory Default INSTALL_ROOT for root or Administrator users Default INSTALL_ROOT for nonroot users /opt/IBM/BPM/v8.0
user_home/IBM/BPM/v8.0
/opt/ibm/BPM/v8.0
user_home/ibm/BPM/v8.0
C:\IBM\BPM\v8.0
C:\IBM\BPM\v8.0
Table 2.shows the default installation directory for a profile named profile_name for both root (Administrator) and nonroot users.
profile_root default directory Default profile_root for root or Administrator users Default profile_root for nonroot users /opt/IBM/BPM/v8.0/profiles/ profile_name
user_homeIBM/BPM/v8.0/profiles/ profile_name
/opt/ibm/BPM/v8.0/profiles/ profile_name
user_home/ibm/BPM/v8.0/profiles/ profile_name
C:\IBM\BPM\v8.0\profiles\ profile_name
C:\IBM\BPM\v8.0\profiles\ profile_name
Table 3.shows the DB2 Express installation location. DB2 Express is installed under the same directory as IBM BPM.
DB2 Express default directory Default DB2 Express binary location Database Instance location /opt/ibm/BPM/v8.0/DB2
Database instance is created under the bpminst user.
For example: user_home/bpminst
C:\IBM\BPM\v8.0\DB2
The BPMINST database instance is created under the root (\) of the drive where IBM BPM is installed.
For example, if IBM BPM is installed under C:\IBM\BPM\v8.0\ then you will see C:\BPMINST.
Default directories for Custom Installation or existing installation of WebSphere Application Server or WebSphere Application Server ND
The following tables show the default installation locations of the product and its profiles.
If you choose to install IBM BPM on top of an existing supported version of WebSphere Application Server or WebSphere Application Server ND, IBM BPM is installed into the same location. Table 4.shows the default installation root directory in such a case for both root (Administrator) and nonroot users.
shows the default installation root directory into which the installation program installs both IBM BPM and WebSphere Application Server for both root (Administrator) and nonroot users. Default INSTALL_ROOT for root or Administrator users Default INSTALL_ROOT for nonroot users /usr/IBM/WebSphere/AppServer
user_home/IBM/WebSphere/AppServer
/opt/IBM/WebSphere/AppServer
user_home/IBM/WebSphere/AppServer
C:\Program Files\IBM\WebSphere\AppServer
user_home\IBM\WebSphere\AppServer
shows the default installation directory for a profile named profile_name for both root (Administrator) and nonroot users. Default profile_root for root or Administrator users Default profile_root for nonroot users /usr/IBM/WebSphere/AppServer/profiles/ profile_name
user_home/IBM/WebSphere/AppServer/profiles/ profile_name
/opt/IBM/WebSphere/AppServer/profiles/ profile_name
user_home/IBM/WebSphere/AppServer/profiles/ profile_name
C:\Program Files\IBM\WebSphere\AppServer\profiles\ profile_name
user_home\IBM\WebSphere\AppServer\profiles\ profile_name
Default installation directories for IBM Installation Manager
Table 6.shows two default directories related to the Installation Manager tool.
The directories under Installation directory are the defaults (per operating system) into which Installation Manager is installed.
The directories under Agent data location directory are the defaults (per platform) used by Installation Manager for data associated with the application, such as the state and history of operations performed by Installation Manager.
Values are given for both root (Administrator) and nonroot users.
For more information about the Agent data location, see Agent data location in the Installation Manager documentation. For more information on other defaults for Installation Manager, see Installing as an administrator or non-administrator in the Installation Manager documentation.
Installation Manager default installation directories Defaults for root or Administrator users Defaults for nonroot users Installation directory: Installation directory: /opt/IBM/InstallationManager/eclipse
user_home/IBM/InstallationManager/eclipse
/opt/IBM/InstallationManager/eclipse
user_home/IBM/InstallationManager/eclipse
C:\Program Files\IBM\Installation Manager\eclipse
C:\Documents and Settings\ userID\IBM\Installation Manager\eclipse
C:\ProgramData\IBM\Installation Manager
Agent data location directory: Agent data location directory: /var/ibm/InstallationManager
user_home/var/ibm/InstallationManager
/var/ibm/InstallationManager
user_home/var/ibm/InstallationManager
C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
C:\ProgramData\IBM\Installation Manager
C:\Documents and Settings\ userID\Application Data\IBM\Installation Manager
C:\Users\ userID\AppData\Roaming\IBM\Installation Manager
Product locations and default directories for IBM BPM for z/OS
- smpe_root
- Refers to the root directory for the product repository installed with System Modification Program/Extended (SMP/E).
The default location is /usr/lpp/InstallationManagerRepository/ BPM_FMID, where BPM_FMID represents the function modification identifier for IBM BPM for z/OS .
- im_INSTALL_ROOT
- Installation location of the IBM BPM for z/OS product code after it is installed by IBM Installation Manager. The IBM BPM for z/OS product code is always installed in the same product file system as the WebSphere Application Server for z/OS installation with which it is associated.
The default location is /usr/lpp/zWebSphere/V8R0.
- configuration_root
- Refers to the mount point for the configuration file system.
The configuration_root location contains various app_server_root directories and associated symbolic links. Each different node type under configuration_root requires its own cataloged procedures under z/OS.
The default location is /wasv8config/ cell_name/ node_name.
- app_server_root
- Refers to the top directory for a WebSphere Application Server for z/OS node.
The node can be of any type: stand-alone server, dmgr, or unmanaged node. Each node has its own app_server_root directory, which is also referred to as the WAS_HOME directory.
The default location varies by node type. Common defaults are configuration_root/Appserver and configuration_root/DeploymentManager.
- profile_root
- Refers to the home directory for a particular instantiated WebSphere Application Server for z/OS profile.
In general, this is the same as app_server_root/profiles/ profile_name. On z/OS, this value is always app_server_root/profiles/default because only the profile name default is used in WebSphere Application Server for z/OS.
Related concepts:
Process and process application considerations
Resource considerations
Development and deployment version levels
Naming considerations for profiles, nodes, servers, hosts, and cells
Related tasks:
Preparing necessary security authorizations