Creating Oracle databases and validating database connections
If you need new Oracle database users, create
the required users before creating your deployment environment. Even
if you have no new databases, validate that all database connections
are correctly configured before you continue.
Procedure
For each deployment environment that you are creating, complete the following steps:
- Create required databases. If you are migrating to a Standard deployment environment:
- Create a messaging engine database if you want to use a single messaging engine bus in the new environment (recommended). If you want to use multiple buses, you can reuse the previous messaging engine database and schema.
If you are migrating to an Advanced deployment environment:- Create a Business Process Choreographer database.
- Create a messaging engine database if you want to use a single messaging engine bus in the new environment (recommended). If you want to use multiple buses, you can reuse the previous messaging engine database and schema.
For each database, make any required changes and run the following script:install_root/BPM/dbscripts/Oracle/Create/createUser.sql - For case management, you must create three additional users, one for
IBM® Content
Navigator
(ICN), one for the design object store (DOS), and one for the target object store (TOS).
- Find the files to create the databases in install_root\BPM\dbscripts\Oracle\Create.
-
To create the IBM Content
Navigator database,
replace the parameters in the following files:
where:createUser.sql createTablespace_ICN.sql- @DB_NAME@ is the Oracle instance name, for example, orcl.
- @DB_DIR@ is the directory, which you must create before running the SQL files. The DB_DIR directory is the data directory of your database.
- @ECMClient_TBLSPACE@ is the table space used by IBM Content Navigator (ICN). The default value is WFICNTS.
- @ECMClient_SCHEMA@ is the schema used by ICN.
- @DB_USER@ is the ICN user name, for example, icnuser. The schema name and user name are usually the same.
- @DB_PASSWD@ is the password for the user.
-
Run the files to create the IBM Content
Navigator
database.
createUser.sql createTablespace_ICN.sql -
To create the users and table spaces for IBM Enterprise Content Management, using the embedded Content Platform Engine, find the
following database creation SQL file and make a copy of it.
Replace the parameters, where:createUserTablespace_ECM.sql- @ECM_DATA_TS@ is the data table space used by DOS or TOS. The default value for DOS is WFDOSDATATS. The default value for TOS is WFTOSDATATS. You can set these values in the SQL file.
- @DB_NAME@ is the Oracle instance name, for example, orcl.
- @DB_DIR@ is the data directory of your database.Important: Make sure that the @DB_DIR@/@DB_NAME@ path already exists on your database computer. You will use this value when you update the properties file later.
- @DB_USER@ is the DOS user name or TOS user name. for example, dosuser or tosuser.
- @DB_PASSWD@ is the password for the user.
-
Run the file to create the Enterprise Content Management users and table spaces.
createUserTablespace_ECM.sql
- On the target deployment manager computer, validate that all database
connections are correctly configured by running the BPMConfig -validate
command. Use the following syntax:
wheretarget_install_root/bin/BPMConfig -validate -db configuration_properties_file- configuration_properties_file is the full path and name of the properties
file that you copied over to the target environment after you migrated the configuration using the
BPMConfig -migratecommand. TheBPMConfig -validate -dbcommand uses the database properties and the database-related authentication alias properties (including passwords) from the configuration properties file. If necessary, you can update these database properties in the file, such as adding the properties for any new databases that you created.
- configuration_properties_file is the full path and name of the properties
file that you copied over to the target environment after you migrated the configuration using the
Results
After all connections are checked, you see a message that the BPMConfig -validate command completed successfully.
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15