BPMConfig properties for creating a target IBM Business Process Manager for z/OS V8.5 deployment environment for migration

Use this information to complete the BPMConfig properties file that is referenced by the BPMConfig.sh script when creating your target deployment environments and generating database scripts. These properties relate to a single cluster topology and DB2® for z/OS®.

The properties can be grouped into the following categories:

Deployment environment properties:: Deployment environment definitions; Process Center definitions

Security and role properties:: Security and role definitions

Topology properties:: Cell definitions; Deployment manager definitions; Cluster definitions; Node and cluster member definitions

Database configuration properties:: Database definitions

If you are editing a properties file for an Advanced-only Process Server deployment environment, a fewer collection of properties is shown than for an Advanced Process Server deployment environment. It is also worth noting that passwords are shown in clear text in the properties files, so consider whether you require password protection, or encryption, to restrict read/write access to the file that you are customizing. If your environment contains multiple deployment targets, each deployment environment requires its own properties file with a unique name.

You typically require two physical databases, which are scoped at the cell level and cluster level, to support your deployment environment in the z/OS system. If you are migrating, you might have a larger number of schema qualifiers set up in the databases in your source environment, than is required in the target environment. Because your source databases will be used in the target environment, it is useful to determine how to map the components in the source environment to those in the target environment. For more information, see:

Deployment environment definitions

Table 1. Entries for defining the deployment environment
Property	Description
bpm.de.name	Specify a unique name for the deployment environment to be created. Each properties file defines one deployment environment.
bpm.de.type	The `Advanced` or `AdvancedOnly` value identifies the type of deployment environment being created. Do not change this value.
bpm.de.environment	Do not change the `Process Server` default value, which is the correct setting for the IBM Business Process Manager for z/OS deployment environment to be created.
bpm.de.deferSchemaCreation	Retain the `true` default value. This setting stops new database objects from being created at the same time that you create the deployment environment and generate the database scripts.
bpm.de.contextRootPrefix	Set the context root prefix at the deployment environment level. This value requires a leading forward slash (/). If set, the default context roots for all the product components are customized with this prefix after you run the BPMConfig.sh script to create the deployment environment. Leave this value blank if you do not want to set a context root prefix. Important: The following conditions apply when you customize the context roots with a prefix: You must change any hard-coded URLs in your existing applications. In URLs, the specified context root prefix, including the leading forward slash (/), is added in front of the default context root. If you intend to connect the Process Server to a Process Center repository to deploy applications, the Process Center must at least be at the V8.5.0.1 level. Tip: You can also customize the context roots in an existing deployment environment by running the BPMConfig.sh script, as described in Customizing context roots for the components in a deployment environment.
bpm.de.psServerName	Specify a unique name by which the Process Server can be identified.
bpm.de.psPurpose	Do not change the `Production` default value, which is the correct setting for the IBM Business Process Manager for z/OS deployment environment to be created. This property applies to an Advanced deployment environment only.

Process Center definitions

These properties apply to an Advanced deployment environment only.

Table 2. Entries for setting up a connection to a Process Center
Property	Description
bpm.de.psOffline	Set this value to `false` to indicate that the Process Server is online and can be connected to a Process Center repository that is installed and configured on Linux, Windows, or UNIX. Set this value to `true` to indicate that the Process Server is an offline server that is not connected to the Process Center. The Process Center serves as a central repository for all processes, services, and other assets that are created in the IBM Business Process Manager authoring environments (Process Designer and Integration Designer).
bpm.de.psProcessCenterTransportProtocol bpm.de.psProcessCenterHostname bpm.de.psProcessCenterPort	If you set bpm.de.psOffline to `false`, you must use these properties to specify a valid transport protocol (`http` or `https`), a fully qualified host name, and a port number for the Process Center. The Process Server uses these values to connect to the Process Center. If you set bpm.de.psOffline to `true`, leave these values blank.
bpm.de.psProcessCenterContextRootPrefix	If the default context root for the Process Center is customized with a prefix, specify the prefix here. This value requires a leading forward slash (/). Leave this value blank if no context root prefix is set for the Process Center. Tip: In URLs, the context root prefix, including the leading forward slash (/), is added in front of the default context root.

Security and role definitions

These properties define the user credentials and role assignments that can be applied to the deployment environment, network deployment cell, databases, and Process Center.

Table 3. Entries for defining user credentials and access privileges for the deployment environment
Property	Description
bpm.de.authenticationAlias.1.name bpm.de.authenticationAlias.1.user bpm.de.authenticationAlias.1.password	Use these properties to assign an authentication alias to an administrator ID and password that can be used to access the deployment environment. You can retain the default alias name, but must specify a valid user ID and password. If you change the bpm.de.authenticationAlias.1.name value, you must replace all other instances of this value with the new value. See Table 5 for considerations relating to cell administrator, deployment administrator, and database user IDs.
bpm.de.roleMapping.1.name bpm.de.roleMapping.1.alias	Use these properties to assign a role to the authentication alias that is defined for the deployment environment. Do not change the `DeAdmin` role name value. For information about this role, see IBM Business Process Manager security roles. Only change the default `DeAdminAlias` alias value if you changed the value for bpm.de.authenticationAlias.1.name. If this is the case, ensure that the values match.

Table 4. Entries for defining user credentials and access privileges for the network deployment cell
Property	Description
bpm.cell.authenticationAlias.1.name bpm.cell.authenticationAlias.1.user bpm.cell.authenticationAlias.1.password	Use these properties to assign an authentication alias to an administrator ID and password that can be used to access the network deployment cell. You can retain the default alias name, but must specify a valid user ID and password. If you change the bpm.cell.authenticationAlias.1.name value (default `CellAdminAlias`), you must replace all other instances of this value with the new value. See Table 5 for considerations relating to cell administrator, deployment administrator, and database user IDs.
bpm.cell.roleMapping.1.name bpm.cell.roleMapping.1.alias	Use these properties to assign a role to the authentication alias that is defined for the cell. Do not change the `CellAdmin` role name value. For information about this role, see IBM Business Process Manager security roles. Only change the default `CellAdminAlias` alias value if you changed the value for bpm.cell.authenticationAlias.1.name. If this is the case, ensure that the values match.

In the following table, the hash character (#) depicts a sequence number (1, 2, 3, or 4) that is included in the property names for the database role mapping properties.

Table 5. Entries for defining user credentials and access privileges for the product databases
Property	Description
bpm.de.authenticationAlias.2.name bpm.de.authenticationAlias.2.user bpm.de.authenticationAlias.2.password	These properties map an alias to the user credentials that can be used to access the product databases with a set of predefined privileges. Considerations for cell administrator, deployment administrator, and database user IDs: If you want to assign administrator privileges for the deployment environment and cell to the same user, and the cell administrator has database access privileges, you can specify the same ID for the bpm.de.authenticationAlias.1.user and bpm.cell.authenticationAlias.1.user properties, and then leave the bpm.de.authenticationAlias.2.* properties commented out. This user ID will be assigned the requisite DeAdmin and CellAdmin roles. This definition is useful if your DB2 and IBM Business Process Manager for z/OS installations are on the same sysplex and you want to use a single, existing user ID in RACF®. If you want to assign administrator privileges for the deployment environment and cell to the same user, but the cell administrator does not have database access privileges, you can specify the same ID for the bpm.de.authenticationAlias.1.user and bpm.cell.authenticationAlias.1.user properties. Then uncomment the bpm.de.authenticationAlias.2.* properties and use them to assign an authentication alias (for example, `BPM_DB_ALIAS`) to a user ID and password for the databases. You must also update the bpm.de.db.#.roleMapping.#.alias values (that are located further down in the file) to match the bpm.de.authenticationAlias.2.name value. For example, your DB2 installation might be on a different sysplex from your IBM Business Process Manager for z/OS installation. If you want to assign different user IDs for the deployment environment administrator, cell administrator, and the product databases, you can specify different IDs for the bpm.de.authenticationAlias.1.user and bpm.cell.authenticationAlias.1.user properties. Then uncomment the bpm.de.authenticationAlias.2.* properties and use them to assign an authentication alias (for example, `BPM_DB_ALIAS`) to a user ID and password for the databases. You must also update the bpm.de.db.#.roleMapping.#.alias values (that are located further down in the file) to match the bpm.de.authenticationAlias.2.name value. For example, you might want to define separate IDs per cluster, and the databases might be on a different sysplex from the product installation. Migration consideration: The source environment databases will be upgraded as required, and used in the target environment after migration. So you will need to check which user credentials are currently used to access to the databases in the source environment, to determine whether these credentials need to be mapped to an authentication alias.
bpm.de.db.#.roleMapping.1.name bpm.de.db.#.roleMapping.1.alias bpm.de.db.#.roleMapping.2.name bpm.de.db.#.roleMapping.2.alias These role mapping properties are defined once within each collection of database properties that is shown further down in the file.	Use these properties to assign the `DbUser` and `DbUserXAR` roles to the authentication alias that is associated with the product databases: Do not change the `DbUser` role name value, which grants access to the databases. Do not change the `DbUserXAR` role name value, which grants authority for XA recovery on data sources and Java™ Message Service (JMS). For more information about these roles, see IBM Business Process Manager security roles.

Table 6. Entries for defining user credentials and access privileges for the Process Center
Property	Description
bpm.de.authenticationAlias.3.name bpm.de.authenticationAlias.3.user bpm.de.authenticationAlias.3.password	These properties apply to an Advanced deployment environment only. Use these properties to assign an authentication alias to a user ID and password that the Process Server can use to connect to the Process Center. You can retain the default alias name, but must specify a valid user ID and password. If you change the bpm.de.authenticationAlias.3.name value, you must replace all other instances of this value with the new value. If you set bpm.de.psOffline to `true`, you can ignore these settings.
bpm.de.roleMapping.2.name bpm.de.roleMapping.2.alias	These properties apply to an Advanced deployment environment only. Use these properties to assign a role to the authentication alias that is used to connect to the Process Center. Do not change the `ProcessCenterUser` role name value. For information about this role, see IBM Business Process Manager security roles. Only change the default `ProcessCenterUserAlias` alias value if you changed the value for bpm.de.authenticationAlias.3.name. If this is the case, ensure that the values match. If you set bpm.de.psOffline to `true`, you can ignore these settings.

Cell definitions

Table 7. Entries for defining the network deployment cell
Property	Description
bpm.cell.name	Specify a name that identifies the cell. Cell names must be unique across the same z/OS sysplex. This value must correspond to the long name specified in zPMT.
bpm.cell.db	Specify a keyword that is used to identify the collection of database properties that you need to configure for the cell-scoped database. Retain the `CellOnlyDb` default value.

Deployment manager definitions

Table 8. Entries for defining the deployment manager
Property	Description
bpm.dmgr.nodeName	Set this value to the deployment manager node name. This value must correspond to the long name specified in zPMT.
bpm.dmgr.hostname	Replace the default `localhost` value with the fully qualified host name of the deployment manager server, to enable remote connections where necessary.
bpm.dmgr.installPath	Set this value to the WAS_HOME directory that will be created for the deployment manager node in the configuration file system; for example, /wasv85config/bbocell/bbodmgr/DeploymentManager.
bpm.dmgr.profileName	The default value of `default` is always the profile name on IBM Business Process Manager for z/OS.
bpm.dmgr.initialPortAssignment	Leave this value blank. The port numbers are set in zPMT.
bpm.dmgr.soapPort	Set this value to the deployment manager SOAP port number. This value must correspond to the Java Management Extensions (JMX) SOAP connector port number that is specified in zPMT.
bpm.dmgr.jdbcClassPath	Specify the directory path of the DB2 for z/OS JDBC driver files.
bpm.dmgr.jccOptionsFilePath	Set this value to the location of the DB2JccConfiguration.properties file that defines the subsystem ID of the DB2 for z/OS system. If the file does not yet exist, you can specify a fully qualified path (for example, /etc/db2cfg/directory) and later create the file in this path, as described in Creating a DB2JccConfiguration.properties file.

Cluster definitions

In the following table, the hash character (#) depicts a sequence number (1 or 3) that is included in the property names for the cluster properties.

Table 9. Entries for defining the cluster
Property	Description
bpm.de.cluster.1.name	Specify a unique name that identifies the cluster.
bpm.de.cluster.1.shortName	Specify a short name for the cluster.
bpm.de.cluster.1.capabilities	Do not change the `Application,Support,Messaging` value that is specified for this single cluster.
bpm.de.cluster.1.db	Specify the keyword value that is used to represent the individual collections of database properties that are defined for the cluster-scoped database. For an Advanced deployment environment, this value must correspond to the values that are collectively specified for the bpm.de.db.1.name, bpm.de.db.2.name, bpm.de.db.3.name, and bpm.de.db.4.name properties in the database configuration section of the properties file. Retain the default value of `SharedDb,ProcessServerDB,PerformanceDB,CommonDB`. For an Advanced-only deployment environment, this value must correspond to the value that is specified for the bpm.de.db.1.name and bpm.de.db.2.name properties in the database configuration section of the properties file. Retain the default value of `SharedDb,CommonDB`.
bpm.de.cluster.1.capability.1.component.#.name	Specify a component for which a context root prefix can be set. The only valid value is `ProcessPortal`, which provides the option to customize the Process Portal context root. Use this property in conjunction with the bpm.de.cluster.1.capability.1.component.#.contextRootPrefix property. Leave this value blank if you do not want to set a context root prefix at the component level. This property applies to an Advanced deployment environment only.
bpm.de.cluster.1.capability.1.component.#.contextRootPrefix	Set a context root prefix that is specific to Process Portal only. This value requires a leading forward slash (/). Use this property in conjunction with the bpm.de.cluster.1.capability.1.component.#.name property. When you customize the Process Portal context root with a prefix, the Process Portal URL is configured to include the specified context root prefix, including the leading forward slash (/), in front of the default context root. Leave this value blank if you do not want to set a context root prefix for Process Portal. If you set a context root prefix at the deployment environment level (with the bpm.de.contextRootPrefix property) and also set a prefix for Process Portal, all components will use the same prefix except for Process Portal, which will have its own unique prefix. This property applies to an Advanced deployment environment only. Tip: You can also customize the context roots in an existing deployment environment by running the BPMConfig.sh script, as described in Customizing context roots for the components in a deployment environment.

Node and cluster member definitions

The default configuration defines two managed nodes, for which you can configure one cluster member each. In the following table, the hash character (#) depicts a sequence number (1 or 2) that is included in the property names for each set of node and cluster member properties.

Table 10. Entries for defining managed nodes and associated cluster members
Property	Description
bpm.de.node.#.name	Set this value to a unique node name. This value must correspond to the long name specified in zPMT.
bpm.de.node.#.hostname	Replace the default `localhost` value with the fully qualified host name of the managed node, to enable remote connections where necessary.
bpm.de.node.#.installPath	Set this value to the WAS_HOME directory that will be created for the unmanaged node in the configuration file system; for example, /wasv85config/bbocell/bbonode/AppServer.
bpm.de.node.#.profileName	Do not change the default value of `default`.
bpm.de.node.#.initialPortAssignment	Leave this value blank. (You can use the bpm.de.node.#.clusterMember.1.initialPortAssignment property to specify an initial port.)
bpm.de.node.#.jdbcClassPath	Set this value to the bpm.dmgr.jdbcClassPath value.
bpm.de.node.#.jccOptionsFilePath	Set this value to the bpm.dmgr.jccOptionsFilePath value.
bpm.de.node.#.clusterMember.1.name	Specify a name for the application server that you are defining as a cluster member. The name must be unique within the node.
bpm.de.node.#.clusterMember.1.shortName	Specify a short name for the cluster member.
bpm.de.node.#.clusterMember.1.weight	Specify the proportionate workload to be directed to this cluster member. For more information, see Clusters and workload management. You can retain the default value.
bpm.de.node.#.clusterMember.1.initialPortAssignment	Specify a starting value for the range of ports to be assigned to the cluster member. Use the same value for the bpm.de.node.1.clusterMember.1.initialPortAssignment and bpm.de.node.2.clusterMember.1.initialPortAssignment properties.
bpm.de.node.#.clusterMember.1.cluster	Specify the name of the cluster to which this cluster member belongs. This value must match the bpm.de.cluster.1.name value (shown in Table 9).

Additional notes for adding nodes: If you want to add another node to the default configuration, you must use zPMT to create a customization definition for the node, and then update this file to add the required properties for the node and its associated cluster member. For example, to add a third node, replicate a set of node and cluster member properties and then increment the sequence number to 3, as follows:

bpm.de.node.3.name=Node3
bpm.de.node.3.hostname=localhost
bpm.de.node.3.installPath=WAS_HOME_path
bpm.de.node.3.profileName=default
bpm.de.node.3.initialPortAssignment=
bpm.de.node.3.jdbcClassPath=dir_path
bpm.de.node.3.jccOptionsFilePath=dir_path
bpm.de.node.3.clusterMember.1.name=SingleClusterMember3
bpm.de.node.3.clusterMember.1.shortName=short_name
bpm.de.node.3.clusterMember.1.weight=2
bpm.de.node.3.clusterMember.1.initialPortAssignment=1234
bpm.de.node.3.clusterMember.1.cluster=SingleClusterMember

Database definitions

You can use the database configuration properties to define the contents of the cell-scoped and cluster-scoped databases, based on the mapping from the source environment.

Take note of the following considerations:

In the properties file, a set of properties is required for each physical database and schema combination that is being defined.
For an Advanced deployment environment, five sets of database properties are provided in the sample file, for you to configure the IBM Business Process Manager for z/OS databases.
For an Advanced-only deployment environment, three sets of database properties are provided. You can use the database configuration properties, which are described in Table 11, Table 14, and Table 15, to define two databases that are scoped at the cell level and cluster level. (Note that the properties are prefixed bpm.de.db.1., bpm.de.db.2., and bpm.de.db.3. for an Advanced-only configuration.)
For an Advanced deployment environment, the Process Server and Performance Data Warehouse require different schema qualifiers, so you must ensure that Process Server and Performance Data Warehouse are not specified within the same bpm.de.db.*.dbCapabilities definition. For migration purposes, the new CommonDB component, which is scoped at the cluster level, can optionally be assigned a unique schema qualifier.
For an Advanced-only deployment environment, the Process Server and Performance Data Warehouse components are not required, and so must not be specified within the bpm.de.db.*.dbCapabilities properties. For migration purposes, the new CommonDB component, which is scoped at the cluster level, can optionally be assigned a unique schema qualifier.

Cluster-scoped configuration

Table 11. Entries for defining the cluster-scoped database (1 of 4)
Property	Description
bpm.de.db.1.name	Specify a keyword that represents this collection of bpm.de.db.1.* database properties. Set this value to `SharedDb`.
bpm.de.db.1.dbCapabilities	Specify the product components to configure on the database identified by the bpm.de.db.1.databaseName property. The database tables for these components will exist in this database, and share the same schema qualifier. Set this value to `Messaging,BusinessSpace,BPC`.
bpm.de.db.1.databaseName	Specify the name of the physical cluster-scoped database. This should match the database name in your source environment.
bpm.de.db.1.connectionLocation	Specify the DB2 location name.
bpm.de.db.1.type	Do not change the `DB2zOS` value.
bpm.de.db.1.hostname	Replace the default `localhost` value with the fully qualified host name of the DB2 for z/OS server, to enable remote connections where necessary.
bpm.de.db.1.portNumber	Specify the port on which the server listens.
bpm.de.db.1.sqlServerWinAuth	Ignore this setting if shown.
bpm.de.db.1.roleMapping.1.name bpm.de.db.1.roleMapping.1.alias bpm.de.db.1.roleMapping.2.name bpm.de.db.1.roleMapping.2.alias	See Table 5.
bpm.de.db.1.schema	Specify a unique schema qualifier.
bpm.de.db.1.volumes bpm.de.db.1.vcat bpm.de.db.1.bptable4k bpm.de.db.1.bptable8k bpm.de.db.1.bptable16k bpm.de.db.1.bptable32k bpm.de.db.1.bpindex bpm.de.db.1.bplob4k bpm.de.db.1.stogrp	Specify the volume for storing data, Virtual Storage Access Method (VSAM) catalog, buffer pools for tables, indexes, and LOB data, and the storage group name. Use the same values for each set of database properties that is defined in the properties file.
bpm.de.db.1.tspre	Specify a table space prefix for Business Space. The maximum length allowed for this string is 3 characters. The default value is `BSP`. This property affects only the generated SQL files. A database administrator needs to create the specified table spaces explicitly before the generated files can be run to create the database tables.

Table 12. Entries for defining the cluster-scoped database (2 of 4): Advanced deployment environment only
Property	Description
bpm.de.db.2.name	Specify a keyword that represents this collection of bpm.de.db.2.* database properties. Set this value to `ProcessServerDB`.
bpm.de.db.2.dbCapabilities	Specify the product components to configure on the database identified by the bpm.de.db.2.databaseName property. Set this value to `ProcessServer`.
bpm.de.db.2.databaseName	Specify the name of the physical cluster-scoped database. This name must match the value that you specified for the bpm.de.db.1.databaseName property.
bpm.de.db.2.connectionLocation	Specify the DB2 location name. This name must match the bpm.de.db.1.connectionLocation value.
bpm.de.db.2.type	Do not change the `DB2zOS` value.
bpm.de.db.2.hostname	Replace the default `localhost` value with the fully qualified host name of the DB2 for z/OS server, to enable remote connections where necessary. This value must match the bpm.de.db.1.hostname value.
bpm.de.db.2.portNumber	Specify the port on which the server listens. This value must match the bpm.de.db.1.portNumber value.
bpm.de.db.2.sqlServerWinAuth	Ignore this setting if shown.
bpm.de.db.2.roleMapping.1.name bpm.de.db.2.roleMapping.1.alias bpm.de.db.2.roleMapping.2.name bpm.de.db.2.roleMapping.2.alias	See Table 5.
bpm.de.db.2.schema	Specify a unique schema qualifier.
bpm.de.db.2.volumes bpm.de.db.2.vcat bpm.de.db.2.bptable4k bpm.de.db.2.bptable8k bpm.de.db.2.bptable16k bpm.de.db.2.bptable32k bpm.de.db.2.bpindex bpm.de.db.2.bplob4k bpm.de.db.2.stogrp	Specify the volume for storing data, Virtual Storage Access Method (VSAM) catalog, buffer pools for tables, indexes, and LOB data, and the storage group name. Use the same values for each set of database properties that is defined in the properties file.

Table 13. Entries for defining the cluster-scoped database (3 of 4): Advanced deployment environment only
Property	Description
bpm.de.db.3.name	Specify a keyword that represents this collection of bpm.de.db.3.* database properties. Set this value to `PerformanceDB`.
bpm.de.db.3.dbCapabilities	Specify the product components to configure on the database identified by the bpm.de.db.3.databaseName property. Set this value to `PDW`.
bpm.de.db.3.databaseName	Specify the name of the physical cluster-scoped database. This name must match the value that you specified for the bpm.de.db.1.databaseName property.
bpm.de.db.3.connectionLocation	Specify the DB2 location name. This name must match the bpm.de.db.1.connectionLocation value.
bpm.de.db.3.type	Do not change the `DB2zOS` value.
bpm.de.db.3.hostname	Replace the default `localhost` value with the fully qualified host name of the DB2 for z/OS server, to enable remote connections where necessary. This value must match the bpm.de.db.1.hostname value.
bpm.de.db.3.portNumber	Specify the port on which the server listens. This value must match the bpm.de.db.1.portNumber value.
bpm.de.db.3.sqlServerWinAuth	Ignore this setting if shown.
bpm.de.db.3.roleMapping.1.name bpm.de.db.3.roleMapping.1.alias bpm.de.db.3.roleMapping.2.name bpm.de.db.3.roleMapping.2.alias	See Table 5.
bpm.de.db.3.schema	Specify a unique schema qualifier.
bpm.de.db.3.volumes bpm.de.db.3.vcat bpm.de.db.3.bptable4k bpm.de.db.3.bptable8k bpm.de.db.3.bptable16k bpm.de.db.3.bptable32k bpm.de.db.3.bpindex bpm.de.db.3.bplob4k bpm.de.db.3.stogrp	Specify the volume for storing data, Virtual Storage Access Method (VSAM) catalog, buffer pools for tables, indexes, and LOB data, and the storage group name. Use the same values for each set of database properties that is defined in the properties file.

Table 14. Entries for defining the cluster-scoped database (4 of 4)
Property	Description
bpm.de.db.4.name	Specify a keyword that represents this collection of bpm.de.db.4.* database properties. Set this value to `CommonDB`.
bpm.de.db.4.dbCapabilities	Specify the product components to configure on the database identified by the bpm.de.db.4.databaseName property. Set this value to `CommonDB`.
bpm.de.db.4.databaseName	Specify the name of the physical cluster-scoped database. This name must match the value that you specified for the bpm.de.db.1.databaseName property.
bpm.de.db.4.connectionLocation	Specify the DB2 location name. This name must match the bpm.de.db.1.connectionLocation value.
bpm.de.db.4.type	Do not change the `DB2zOS` value.
bpm.de.db.4.hostname	Replace the default `localhost` value with the fully qualified host name of the DB2 for z/OS server, to enable remote connections where necessary. This value must match the bpm.de.db.1.hostname value.
bpm.de.db.4.portNumber	Specify the port on which the server listens. This value must match the bpm.de.db.1.portNumber value.
bpm.de.db.4.sqlServerWinAuth	Ignore this setting if shown.
bpm.de.db.4.roleMapping.1.name bpm.de.db.4.roleMapping.1.alias bpm.de.db.4.roleMapping.2.name bpm.de.db.4.roleMapping.2.alias	See Table 5.
bpm.de.db.4.schema	If you want the `CommonDB` component to share the same schema qualifier as `Messaging`, `BusinessSpace`, and `BPC`, this value must match the bpm.de.db.1.schema value. If you want to define a different schema qualifier for `CommonDB`, specify a unique schema qualifier.
bpm.de.db.4.volumes bpm.de.db.4.vcat bpm.de.db.4.bptable4k bpm.de.db.4.bptable8k bpm.de.db.4.bptable16k bpm.de.db.4.bptable32k bpm.de.db.4.bpindex bpm.de.db.4.bplob4k bpm.de.db.4.stogrp	Specify the volume for storing data, Virtual Storage Access Method (VSAM) catalog, buffer pools for tables, indexes, and LOB data, and the storage group name. Use the same values for each set of database properties that is defined in the properties file.

Cell-scoped configuration

Table 15. Entries for defining the cell-scoped database
Property	Description
bpm.de.db.5.name	Specify a keyword that represents this collection of bpm.de.db.5.* database properties. Set this value to `CellOnlyDb`.
bpm.de.db.5.dbCapabilities	Specify the product components to configure on the database identified by the bpm.de.db.5.databaseName property. Set this value to `CellScopedDB`.
bpm.de.db.5.databaseName	Specify the name of the physical cell-scoped database. This should match the database name in your source environment.
bpm.de.db.5.connectionLocation	Specify the DB2 location name. This name must match the bpm.de.db.1.connectionLocation value.
bpm.de.db.5.type	Do not change the `DB2zOS` value.
bpm.de.db.5.hostname	Replace the default `localhost` value with the fully qualified host name of the DB2 for z/OS server, to enable remote connections where necessary. This value must match the bpm.de.db.1.hostname value.
bpm.de.db.5.portNumber	Specify the port on which the server listens. This value must match the bpm.de.db.1.portNumber value.
bpm.de.db.5.sqlServerWinAuth	Ignore this setting if shown.
bpm.de.db.5.roleMapping.1.name bpm.de.db.5.roleMapping.1.alias bpm.de.db.5.roleMapping.2.name bpm.de.db.5.roleMapping.2.alias	See Table 5.
bpm.de.db.5.schema	Specify a unique schema qualifier.
bpm.de.db.5.volumes bpm.de.db.5.vcat bpm.de.db.5.bptable4k bpm.de.db.5.bptable8k bpm.de.db.5.bptable16k bpm.de.db.5.bptable32k bpm.de.db.5.bpindex bpm.de.db.5.bplob4k bpm.de.db.5.stogrp	Specify the volume for storing data, Virtual Storage Access Method (VSAM) catalog, buffer pools for tables, indexes, and LOB data, and the storage group name. Use the same values for each set of database properties that is defined in the properties file.