Installation directories for the product and profiles

The installation directories for IBM® Business Automation Workflow are represented by several variables. The meaning of those variables can differ for a number of factors.

For ease of access, you can use these links to view the tables for the default installation directories in the sections that follow:

install_root default directory
profile_root default directory
Db2® Advanced Workgroup Server Edition default directory
IBM Business Automation Workflow and WebSphere® Application Server default installation directory
Default installation directory for a profile named profile_name
Process Designer default directory
Installation Manager default installation directories
Installation Manager default agent data directories

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 Business Automation Workflow products or components require multiple locations.

Here are the main variables used in the documentation:

install_root: Installation location of IBM Business Automation Workflow. The documentation may show this variable as either install_root or BPM_home. IBM Business Automation Workflow is always installed in the same location as the WebSphere Application Server Network Deployment installation with which it is associated.
profile_root: Location of an IBM Business Automation Workflow 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 Network Deployment. 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.

For AIX operating system For Linux operating system Alternatively, you can use IBM Installation Manager group mode to install Installation Manager and IBM Business Automation Workflow so that a group of nonroot users can install and manage the installation packages. You can install in group mode only with custom command line or response file installation methods, not typical or custom with the graphical interface methods.

Default directories for Typical Installation

The following tables show the default installation locations of the IBM Business Automation Workflow 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 Business Automation Workflow and WebSphere Application Server Network Deployment for both root (Administrator) and nonroot users.

Table 1. install_root default directory
Default `install_root` for root or Administrator users	Default `install_root` for nonroot users
/opt/IBM/Workflow/v18.0/	`user_home`/IBM/Workflow/v18.0/
/opt/ibm/Workflow/v18.0/	`user_home`/ibm/Workflow/v18.0/
C:\IBM\Workflow\v18.0	C:\IBM\Workflow\v18.0

Table 2 shows the default installation directory for a profile named profile_name for both root (Administrator) and nonroot users.

Table 2. `profile_root` default directory
Default `profile_root` for root or Administrator users	Default `profile_root` for nonroot users
/opt/IBM/Workflow/v18.0/profiles/`profile_name`	`user_home`/IBM/Workflow/v18.0/profiles/`profile_name`
/opt/ibm/Workflow/v18.0/profiles/`profile_name`	`user_home`/ibm/Workflow/v18.0/profiles/`profile_name`
C:\IBM\Workflow\v18.0\profiles\`profile_name`	C:\IBM\Workflow\v18.0\profiles\`profile_name`

Table 3 shows the Db2 Advanced Workgroup Server Edition installation location. Db2 AWSE is installed under the same directory as IBM Business Automation Workflow. Nonroot or non-administrator installation of Db2 AWSE is not supported.

Table 3. Db2 AWSE default directory
Default Db2 AWSE binary location	Database Instance location
/opt/ibm/Workflow/v18.0/DB2	Database instance is created under the bpminst user. For example: `user_home`/bpminst
C:\IBM\Workflow\v18.0\DB2	The BPMINST database instance is created under the root (\) of the drive where IBM Business Automation Workflow is installed. For example, if IBM Business Automation Workflow is installed under C:\IBM\BPM\v8.5\ then you will see C:\BPMINST.

Default directories for Custom Installation or existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment

The following tables show the default installation locations of the product and its profiles. If you choose to install IBM Business Automation Workflow on top of an existing supported version of WebSphere Application Server or WebSphere Application Server Network Deployment, IBM Business Automation Workflow is installed into the same location. Table 4 shows the default installation root directory in such a case for root (Administrator) and nonroot (including group where applicable) users.

Table 4. IBM Business Automation Workflow and WebSphere Application Server default installation directory
Default `install_root` for root or Administrator users	Default `install_root` for nonroot and group 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

Table 5. Default installation directory for a profile named `profile_name`
Default `profile_root` for root or Administrator users	Default `profile_root` for nonroot and group 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`

Table 6 shows the Process Designer installation location.

Table 6. Process Designer default directory
Default Process Designer installation location for root or Administrator users	Default Process Designer installation location for nonroot users
C:\IBM\ProcessDesigner\v8.5	C:\IBM\ProcessDesigner\v8.5

Default installation directories for IBM Installation Manager

The following tables show two default directories that are related to the Installation Manager tool. Values are given for root (Administrator), nonroot (non-administrator), and installation group users.

The directories in Table 7 are the defaults (per operating system) into which Installation Manager is installed.
For more information about other defaults for Installation Manager, see Installing as an administrator, nonadministrator, or group in the Installation Manager documentation.
The agent data directories in Table 8 are the defaults (per operating system) used by Installation Manager for data associated with the application, such as the state and history of operations performed by Installation Manager.
For more information about the agent data location, see Agent data location in the Installation Manager documentation.

Installation Manager also uses another directory to store shared program objects and cached files that are generated when you install a product. You can specify this shared resources directory when you install WebSphere Application Server and IBM Business Automation Workflow. This value is set the first time that a product is installed with a particular Installation Manager instance. For further information about the shared resources directory, see Overview of package groups and the shared resources directory. For information about how to locate the shared resources directory, see Backing up and restoring Installation Manager.

Table 7. Installation Manager default installation directories
Defaults for root or Administrator users	Defaults for nonroot or non-administrator users	Defaults for group mode users
/opt/IBM/InstallationManager	/`user_home`/IBM/InstallationManager	/`user_home`/IBM/InstallationManager_Group
/opt/IBM/InstallationManager	/`user_home`/IBM/InstallationManager	/`user_home`/IBM/InstallationManager_Group
Windows 8, Windows Server 2012: C:\Program Files [(x86)]\IBM\Installation Manager	Windows 8, Windows Server 2012: C:\Users\`user`\IBM\Installation Manager	Not available.
(deprecated) Windows Server 2008, Windows 7: C:\Program Files [(x86)]\IBM\Installation Manager	(deprecated) Windows Server 2008, Windows 7: C:\Users\`user`\IBM\Installation Manager	Not available.

Table 8. Installation Manager default agent data directories
Defaults for root or Administrator users	Defaults for nonroot or non-administrator users	Defaults for group mode users
/var/ibm/InstallationManager	/`user_home`/var/ibm/InstallationManager	/`user_home`/var/ibm/InstallationManager_Group
/var/ibm/InstallationManager	/`user_home`/var/ibm/InstallationManager	/`user_home`/var/ibm/InstallationManager_Group
Windows 8, Windows Server 2012: C:\ProgramData\IBM\Installation Manager	Windows 8, Windows Server 2012: C:\Users\`user`\AppData\Roaming\IBM\Installation Manager	Not available.
(deprecated) Windows Server 2008, Windows 7: C:\Program Files [(x86)]\IBM\Installation Manager	(deprecated) Windows Server 2008, Windows 7: C:\Users\`user`\IBM\Installation Manager	Not available.