Creating users for Oracle databases

You can create the users for Oracle databases either before or after you run the BPMConfig command with the -create -de parameters to create the stand-alone profile. Create the deployment environment-level user, the Process Server user, and the Performance Data Warehouse user.

The BPMConfig command requires input from a properties file that contains configuration settings for the profile and database users to be created. In this file, the bpm.de.deferSchemaCreation property determines when the database users can be created:

If the property is set to false, database tables are automatically created when you run the BPMConfig command to create the stand-alone profile. Therefore, the database users must exist before you run the BPMConfig command.
If the property is set to true, database table creation is deferred when you run the BPMConfig command to create the stand-alone profile. Therefore, you can create the database users either before or after running the command. You might find it useful to create the database users after running the BPMConfig command because you can use the set of populated scripts, which the command generates, to create the database users and database tables at a time that you choose.

Before you begin

Before you install your system in Oracle database, ensure that the minimum initial settings in the following table are met for IBM BPM database schema users:

Table 1. Minimum initial settings for BPM database schema users
Tuning item	Minimum memory for initial settings (MB)
Buffer cache	2048
Shared pool size	1024

Note: You might want to enlarge the memory for the preceding settings depending on the capacity of your BPM system. For more tuning details, consult your database administrator.

Recommendations for database tablespace settings:

On Oracle, IBM® Business Process Manager stores large objects (LOBs) with the SECUREFILE option. For SECUREFILE, it is recommended to use a tablespace with the AUTOALLOCATE option. If you use UNIFORM SIZE extents, ensure that the UNIFORM SIZE is big enough. Given the default block size of 8K, specify a UNIFORM SIZE of at least 120K. IBM BPM does not explicitly prescribe the tablespace options; it relies on the default Oracle settings (such as AUTOALLOCATE) to automatically manage extents.

For new IBM BPM installations, create tablespaces with the AUTOALLOCATE option.

For migrations, if you use tablespaces with a UNIFORM SIZE less than 120K, create new tablespaces with the AUTOALLOCATE option and make it the default tablespace for IBM BPM database schema users.

You can use a single instance of Oracle for configuring IBM Business Process Manager. The Oracle instance must exist and be available for access. Consult the Oracle documentation to create an Oracle instance. If you use a single Oracle instance, make sure that you use different user IDs for the three different IBM Business Process Manager databases.

About this task

The default database names are BPMDB for the Process database, PDWDB for the Performance Data Warehouse database, and CMNDB for the Common database.

For more information about creating databases, see the following sections:

Creating users for the databases before creating the stand-alone profile and database tables
Creating users for the databases after creating the stand-alone profile

Creating users for the databases before creating the stand-alone profile and database tables

To generate the database scripts that can be used by the BPMConfig command to create the users and configure your databases, you can run BPMConfig with the -create -sqlfiles parameters, and additionally include the -outputDir parameter to specify a location for the generated scripts. When you run the BPMConfig command with these parameters, it generates the database scripts without configuring your environment.

Before you begin

Prepare the following information:

Information about the database configuration that you are designing. This might be a document that describes the general purpose of the database configuration supplied by the database administrator or solution architect. Alternatively, it might be a description of required parameters and properties. This information must include:
- The location of the databases
- The user ID and password for authenticating to the database
Information about how IBM Business Process Manager and its components have been installed, the database software used, and the properties required by that type of database.
An understanding of the profiles that you plan to create, specifically, the functional relationship between the profile types and the databases.
Information about the topology pattern to be implemented, and an understanding of how the database design fits into the pattern that you plan to use.

Important: If you are using an Oracle database, you must include the database user name and password for all databases, including the optional ones.

Procedure

On the computer where you installed IBM Business Process Manager, navigate to the following directory where the sample configuration properties files are stored:
install_root/BPM/samples/config/express
Find the sample properties file that most closely represents your target deployment environment and make a copy of this file. The sample properties files are named according to the following format: de_type[-environment_type]-topology-Oracle, where:
- de_type is set to Express.
- environment_type can be set to PS for Process Server or PC for Process Center. .
- topology is set to Standalone.
For example, the sample configuration properties file for a stand-alone Process Center environment using an Oracle database is named Express-PC-Standalone-Oracle.properties.
Edit the copied properties file and update the values as required to reflect your profile and database configuration. When modifying the sample properties file, use the guidance provided within the file for specifying values.
Tip: You can use this same properties file later when you run the BPMConfig command to create your stand-alone profile.
Additional considerations:
- Your modified properties file must use UTF-8 encoding.
- If you want to automatically create your database tables when you run the BPMConfig command later to create the stand-alone profile, set the bpm.de.deferSchemaCreation property to false.
- Do not add any custom properties to this file when you perform your modifications or the BPMConfig command will fail when it is run.
- If you need to use a backslash character (\) in your properties file, for instance when specifying path names or passwords, you must use an escape backslash before it. For example: bpm.de.node.1.installPath=c:\\IBM\\BPM85.
For more information about the available properties, see the BPMConfig command-line utility topic and the descriptions in the Configuration properties for the BPMConfig command topic.
Run the BPMConfig command on the computer where IBM Business Process Manager is installed, passing it the name of the properties file that you created. For example:
```
install_root/bin/BPMConfig -create -sqlfiles /directory_path/my_environment.properties -outputDir /my_bpmscripts_dir
```
In this syntax, directory_path/my_environment.properties is the location and name of your customized properties file, and my_bpmscripts_dir is the directory where you want to generate the database scripts.
The generated scripts include a set of files named createUser.sql, which can be used to create the users for the databases. The createUser.sql files are generated into the following default locations:
- my_bpmscripts_dir/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/CMN_user
- my_bpmscripts_dir/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/PS_user
- my_bpmscripts_dir/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/PDW_user
The number of subdirectories that are generated is dependent on the number of database users that were defined in the properties file.
Note: These scripts are overwritten if you run the BPMConfig command again.
For each createUser.sql file that was generated, run the following command on your local or remote database server:
```
  sqlplus oracle_user_ID/oracle_password@oracle_instance_name @createUser.sql schema_user_password
```
Note: Although you can specify the schema user password shown in the command syntax, you can alternatively edit the createUser.sql script and replace the parameter &1 with the schema user password and then run the script without specifying any parameter.

Creating users for the databases after creating the stand-alone profile

If you want to use the BPMConfig command to create the stand-alone profile separately from the database tables, you can first run the command with the -create -de parameters to create the profile. Afterwards, you can run the command again with the -create -sqlfiles parameters to generate the database scripts that can be used to create the users for the databases and the database tables. The generated database scripts are populated with the values from the properties file that you specified.

Before you begin

You must have already run the BPMConfig command to create the stand-alone profile.

Procedure

Note the location of the properties file that you specified when you ran the BPMConfig command to create the stand-alone profile.
On the computer where you created the stand-alone profile, run the BPMConfig command to generate the database scripts, passing it the name of the properties file. For example:
```
install_root/bin/BPMConfig -create -sqlfiles /directory_path/my_environment.properties [-outputDir /my_bpmscripts_dir]
```
In this syntax, directory_path/my_environment.properties is the location and name of your customized properties file. (The -outputDir parameter and associated my_bpmscripts_dir value are optional and can be used to specify an alternative directory where you want to generate the database scripts.)
The generated scripts include a set of files named createUser.sql, which can be used to create the users for the databases. The createUser.sql files are generated into the following default locations:
- standalone_profile_root/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/CMN_user
- standalone_profile_root/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/PS_user
- standalone_profile_root/dbscripts/cell_name.deployment_environment_name/Oracle/oracle_instance_name/PDW_user
The number of subdirectories that are generated is dependent on the number of database users that were defined in the properties file.
Note: These scripts are overwritten if you run the BPMConfig command again.
For each createUser.sql file that was generated, run the following command on your local or remote database server:
```
  sqlplus oracle_user_ID/oracle_password@oracle_instance_name @createUser.sql schema_user_password
```
Note: Although you can specify the schema user password shown in the command syntax, you can alternatively edit the createUser.sql script and replace the parameter &1 with the schema user password and then run the script without specifying any parameter.