IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Install IBM BPM Advanced for z/OS: Process Server
IBM BPM file system directories
After installation, the IBM BPM for z/OS product code is stored in z/OS partitioned data sets and z/OS UNIX System Services file systems.
IBM BPM product file system
All IBM BPM product files are stored in the product file system, together with the WebSphere Application Server product files.
The product file system is defined when you use System Modification Program/Extended (SMP/E) to load WebSphere Application Server from the installation media, and then use Installation Manager to install the WebSphere Application Server product code. The product file system is typically mounted read-only.
In the examples in the documentation, the path /usr/lpp/zWebSphere/V8R0 is generally used as the location of the product file system.
The installation jobs assume that a unique data set is allocated to be used for IBM BPM. The sample job to create a zFS product file system is identified in the WebSphere Application Server Program Directory, which is provided with your order. The system programmer can run this job during the installation process.
Configuration file system
Each IBM BPM application-serving environment (stand-alone application server node or ND cell) has configuration files in one or more WebSphere Application Server configuration directories. These configuration directories are created during the configuration process, and they contain symbolic links to files in the product file system.
The default location of the configuration directories varies by node type, and can be denoted by the WAS_HOME variable, where WAS_HOME is the top directory for the WebSphere Application Server node.
WAS_HOME represents the configuration_root/ nodetype_directory location, where:
- configuration_root refers to the mount point for the configuration file system in WebSphere Application Server.
For example, /wasv8config/ cell_name/ node_name, for a read/write file system that was created at /wasv8config.
- nodetype_directory refers to a unique directory for the application server, dmgr, or unmanaged node in the configuration file system.
For example, DeploymentManager for the dmgr, or AppServer for each stand-alone application server or unmanaged server node.
Sample values for the WAS_HOME variable are as follows:
- /wasv8config/bbobase/bbonode/AppServer
- /wasv8config/bbocell/bbodmgr/DeploymentManager
- /WebSphere/V8T3Z1/AppServer
- /WebSphere/V8T8DM/DeploymentManager
Configure with symbolic links
In the runtime environment, the configuration file system uses symbolic links to access the product code in the product file system. When you define the customization values for WebSphere Application Server and IBM BPM, you can define a directory path for an intermediate symbolic link that can be used in place of a direct symbolic link between the configuration and product file systems. As a result, the configuration file system will point to the intermediate symbolic link, which in turn will point to the product file system. This level of indirection makes it possible to switch to a new or different server level of IBM BPM by changing the single intermediate symbolic link. You can stop the servers that use a particular intermediate symbolic link, change the link to point to the new product directory, and then restart the affected servers.
During the configuration process, the symbolic links are automatically created in the configuration file system for most of the directories that are stored in the root directory of the product file system. These symbolic links are defined at the directory level because all of the files contained in a given directory are stored in the same product file system. IBM BPM itself does not provide symbolic link scripts because it shares the product file system with WebSphere Application Server.