0.

yum -y install bc binutils elfutils-libelf elfutils-libelf-devel glibc glibc-

devel ksh libaio libaio-devel libXrender libX11 libXau libXi libXtst libgcc libnsl
librdmacm libstdc++ libstdc++-devel libxcb libibverbs make policycoreutils
policycoreutils-python-utils smartmontools sysstat

yum -y install ipmiutil libnsl2 libnsl2-devel net-tools nfs-utils

1. DB creation

2. configure XA transactions
ORACLE_HOME/javavm/install/initxa.sql

su - oracle
sqlpus oracle_user_id/oracle_password@oracle_instance_name @initxa.sql ili
sqlplus / as sysdba , pa onda
@/u01/app/oracle/product/19.0.0/dbhome_1/javavm/install/initxa.sql

/u01/app/oracle/product/19.0.0/dbhome_1/javavm/install/initxa.sql

3. If you have not already done so, create custom directories for your Oracle Java
Database Connectivity (JDBC) driver. In the IBM® BPM installation root on the IBM
BPM deployment manager and every managed node machine, create a custom directory
for your JDBC driver and copy the required JDBC driver JAR file into it. For
example, you could create the following custom directory:

install_root/ojdbc

- If you previously ran the BPMConfig command with the -create -sqlfiles -outputDir
parameters to generate the database scripts that are used to create your database
users, you should already have a properties file. Verify that the value of the
bpm.de.deferSchemaCreation property has been set, and then go to step 5 and
complete the remaining steps.

However, if you do not yet have a customized properties file that contains the
configuration settings for your profiles, deployment environment, and databases,
complete all of the following steps.

- On the computer where you want to create the deployment environment, locate the
appropriate sample properties file: BPM_Home\BPM\samples\config.

- Find the sample properties file that most closely represents your target
deployment environment and make a copy of this file. For each of the different
product configurations, there is a different folder containing sample configuration
files. For example, for configuring an Advanced, AdvancedOnly, or Standard
deployment environment, there is an advanced, advancedonly, or standard folder
containing a set of sample configuration properties files. Within each folder,
there is a set of files that are specific to the different database types and
configuration environments. The sample files are named according to the following
format: de_type[-environment_type]-topology-database_type[-suffix], where:

* de_type can be set to Advanced, AdvancedOnly, or Standard .

 * environment_type can be set to PS for Process Server or PC for Process
Center. This variable is not used if de_type is AdvancedOnly.
* topology can be set to SingleCluster or ThreeClusters.
* database_type can be set to DB2, DB2zOS, Oracle, or SQLServer.
* suffix can be set to -WinAuth for an SQL Server database.

For example, the sample configuration properties file for configuring Advanced
deployment environments with Process Server in a single cluster topology using an
Oracle database is called Advanced-PS-SingleCluster-Oracle.properties.

- Modify your version of the properties file so that the values correspond to your
own configuration. When modifying the sample properties file, use the guidance
provided within the file for specifying values.

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

When you are configuring a Process Server environment to use Process Center
remotely, you must change the default value for the psProcessCenterHostname
property from local host to a valid host name. If you are configuring an offline
Process Server and the value for bpm.de.psOffline is set to true, then you do not
need to specify a value for the psProcessCenterHostname property.

Note: Your modified properties file must use UTF-8 encoding.

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 are configuring a three-cluster setup that is based on the Advanced or

AdvancedOnly template, and you want your deployment environment to include the
optional Business Process Archive Manager, include the properties file entries that
are described in Configuring Business Process Archive Manager.

Set the bpm.dmgr.jdbcDriverPath property to point to the custom JDBC driver path
where your JDBC driver is installed. For Oracle databases, there is no default
value and you must specify the path, for example, install_root/myjdbc.

For more information about the available properties, read the comments in the
sample files, or see the BPMConfig command-line utility and the sample property
file descriptions in Configuration properties for the BPMConfig command.

- Run the BPMConfig command on the computer that has the deployment manager,
passing it the name of the properties file you created.

BPM_home\bin\BPMConfig -create -de my_environment.properties

- Start the deployment manager. Run the BPMConfig command on each computer that has
one or more managed nodes, passing it the name of the same properties file. The
managed node profiles are created and federated into the deployment manager cell.

- Optional: If you plan to use applications with advanced content or that have been
imported into IBM Integration Designer and you are adding more than one deployment
environments to the cell, provide a way to distinguish between the advanced content
in these business level applications across the deployment environments. For
information, see the step that describes how to set the AdvancedDeploymentDEScoped
property in Isolating deployment environments.
4. On the computer where you created the deployment manager profile, navigate to
one or more of the following default subdirectories where the SQL database scripts
were generated:

* dmgr_profile_root\dbscripts\cell_name\Oracle\oracle_instance_name\cell_user
* dmgr_profile_root\dbscripts\cell_name.deployment_environment_name\Oracle\
oracle_instance_name\CMN_user
* dmgr_profile_root\dbscripts\cell_name.deployment_environment_name\Oracle\
oracle_instance_name\PS_user
* dmgr_profile_root\dbscripts\cell_name.deployment_environment_name\Oracle\
oracle_instance_name\PDW_user

These directories contain the createUser.sql scripts that you can use to create the
users for the databases.

The number of subdirectories that are generated is dependent on the deployment

environment type and the number of database users that were defined in the
properties file.
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

5. The database SQL scripts are generated in the dmgr_profile_name\dbscripts folder

by default. This folder includes the following sub-folders:

* cell_name - If you are configuring an Advanced deployment environment or

AdvancedOnly deployment environment, this folder contains the SQL files for the
CommonDB database that is configured on the cell.
* cell_name.deployment_environment_name - For each deployment environment, this
folder will contain the SQL files that need to be run.

Locate the generated SQL scripts.

A default configuration for an Advanced deployment environment with Oracle
databases contains the following sub-folders and SQL scripts:

cell_name
Oracle
orcl
celluser
createSchema_Advanced.sql
cell_name.deployment_environment_name
Oracle
orcl
cmnuser
createSchema_Advanced.sql
createSchema_Messaging.sql
psuser
createSchema_Advanced.sql
createProcedure_Advanced.sql
pdwuser
createSchema_Advanced.sql

In the above example, orcl is the Oracle instance, celluser is the cell-scoped
user, cmnuser is the deployment environment-level user, psuser is the Process
Server user, and pdwuser is the Performance Data Warehouse user.
 The BPMDB and PDWDB folders for Process Server and Performance Data Warehouse
databases are not generated for an AdvancedOnly deployment environment.

Run the scripts to apply the schema to the CMNDB.

For example, use the following commands to run the scripts manually for a cell-
scoped Common database configuration:

sqlplus celluser/cellpassword@orcl @BPM_HOME\profiles\DmgrProfile\dbscripts\

cell_name\Oracle\orcl\celluser\createSchema_Advanced.sql

sqlplus cmnuser/cmnpassword@orcl @BPM_HOME\profiles\DmgrProfile\dbscripts\

cell_name.deployment_environment_name\Oracle\orcl\cmnuser\
createSchema_Messaging.sql

Run the scripts to apply the schema to the BPMDB.

For example, use the following commands to run the scripts manually for the Process
database configuration:

sqlplus psuser/pspassword@orcl @BPM_HOME\profiles\DmgrProfile\dbscripts\

cell_name.deployment_environment_name\Oracle\orcl\psuser\createSchema_Advanced.sql

sqlplus psuser/pspassword@orcl @BPM_HOME\profiles\DmgrProfile\dbscripts\

cell_name.deployment_environment_name\Oracle\orcl\psuser\
createProcedure_Advanced.sql

Run the scripts to apply the schema to the PDWDB.

For example, use the following commands to run the scripts manually for the
Performance Data Warehouse database configuration:

sqlplus pdwuser/pdwpassword@orcl @BPM_HOME\profiles\DmgrProfile\dbscripts\

cell_name.deployment_environment_name\Oracle\orcl\pdwuser\createSchema_Advanced.sql

If you created a Standard deployment environment or an Advanced deployment

environment, you must now run the bootstrap utility to load configuration data for
the IBM® Business Process Manager applications into the Process database. This data
is required for the applications to run correctly.

s
- If you ran BPMConfig with the deferSchemaCreation set to true, then you must
create your database tables and if your environment includes the ProcessServer
component, you must also load the Process database. To create the database, run the
SQL scripts that are generated by the BPMConfig command. To load the Process
database, run the bootstrapProcessServerData utility. For more information see the
related task link for running the generated scripts for creating database tables.
After you have created your deployment environment and your database tables, you
can start the deployment manager, node agents, and clusters by running the
BPMconfig command with the -start action from the deployment manager computer. If
you are creating an Advanced or AdvancedOnly deployment environment, the deployment
manager and node agents need to be restarted for the cell scoped configuration to
take affect. This is only required for the first deployment environment with
Advanced or AdvancedOnly capabilities.

#cd Dmgr_profile/bin
#./bootstrapProcessServerData.sh -clusterName AppCluster
#cd Install_root/bin
#./BPMConfig.sh -start -profile PCenterDmgr
- If the new or updated node is on the same computer as the deployment manager
node, then the updated or new node is automatically synchronized with the
deployment manager node. Before you start the node, ensure that this
synchronization has completed by checking the syncNode.log file found in the
profile_root\logs directory. If the new or updated node is on a different computer
than the deployment manager node, you need to run the syncNode.bat or syncNode.sh
command on the new or updated node and wait for the synchronization to complete
before starting the node.