• Personal tools
  • 38.107.191.114
  • Talk for this IP
  • Log in
• Navigation
  • Main Page
  • Community portal
  • Current events
  • Recent changes
  • Random page
  • Help
• Toolbox
  • What links here
  • Related changes
  • Upload file
  • Special pages

WebSphere Process Server Databases

From ISSW

WebSphere Process Server requires multiple databases:

Contents 1 The Core 2 Business Process Engine 3 Messaging Engine 4 Common-Event Infrastructure

The Core

Usually called the WPSDB, or WPRCSDB, this is the main Process Server database.

To create the database:

# For Unix and DB2
[db2inst1@DB2Server ~]# db2start;
[db2inst1@DB2Server ~]# db2 create database WPSDB;
DB20000I The CREATE DATABASE command completed successfully
[db2inst1@DB2Server ~]# 

Business Process Engine

The BPEDB contains process-related information.

To create the database, copy the createDatabase.sql script to the database server:

# For Unix and DB2
[root@WPSDMgr ~]# scp /opt/IBM/WebSphere/ProcServer/dbscripts/ProcessChoreographer/DB2/createDatabase.sql db2server:/tmp;

Then execute the script:

# For Unix and DB2
[db2inst1@DB2Server ~]# db2start;
[db2inst1@DB2Server ~]# db2 -tf /tmp/createDatabase.sql;

[db2inst1@DB2Server ~]# 

Note: Completed tasks and processes are not deleted from this database. By default an archiving and deletion strategy should be applied in a production environment and the database should regularly get runstats/reorgs (for DB2), or appropriate maintenance for the specific database type. This is improved in WPS 6.2. Tuning of this database is FUNDAMENTAL to the performance of Process Server.

Messaging Engine

The MEDB is the messaging engine database and acts as a persistent data store for JMS messages sent across the SI Bus.

To create the database:

[db2inst1@DB2Server ~]# db2start;
[db2inst1@DB2Server ~]# db2 create database MEDB;
DB20000I The CREATE DATABASE command completed successfully
[db2inst1@DB2Server ~]# 

The database contains four schemas for each of the messaging engines. The most reliable way to generate them is to run a supplied script:

# For Unix and DB2
[root@WPSDMgr ~]# cd /opt/IBM/WebSphere/ProcServer/bin;
[root@WPSDMgr bin]# ./sibDDLGenerator.sh -system db2 -version 8.1 -platform unix -schema SCASYS -statementend \; -user db2inst1 > /tmp/SCASYS.ddl;
[root@WPSDMgr bin]# ./sibDDLGenerator.sh -system db2 -version 8.1 -platform unix -schema SCAAPP -statementend \; -user db2inst1 > /tmp/SCAAPP.ddl;
[root@WPSDMgr bin]# ./sibDDLGenerator.sh -system db2 -version 8.1 -platform unix -schema BPCMSG -statementend \; -user db2inst1 > /tmp/BPCMSG.ddl;
[root@WPSDMgr bin]# ./sibDDLGenerator.sh -system db2 -version 8.1 -platform unix -schema CEIMSG -statementend \; -user db2inst1 > /tmp/CEIMSG.ddl;

Now the schema definitions must be copied to the database server and run to create the schemas:

# For Unix and DB2
[root@WPSDMgr ~]# scp /tmp/*.ddl db2server:/tmp;

Then run the scripts:

# For Unix and DB2
[db2inst1@DB2Server ~]# db2start;
[db2inst1@DB2Server ~]# db2 -tf /tmp/SCASYS.ddl;
[db2inst1@DB2Server ~]# db2 -tf /tmp/SCAAPP.ddl;
[db2inst1@DB2Server ~]# db2 -tf /tmp/BPCMSG.ddl;
[db2inst1@DB2Server ~]# db2 -tf /tmp/CEIMSG.ddl;

Common-Event Infrastructure

The CEIDB is the datastore for the common-event infrastructure.

To create the database, a set of database schema creation scripts must be run after the main bulk of the infrastructure has been created:

# For Unix and DB2
[root@WPSDMgr ~]# cd /opt/IBM/WebSphere/ProcServer/profiles/DMgr/event/dbconfig;
[root@WPSDMgr dbconfig]# cp DB2ResponseFile.txt NewDB2ResponseFile.txt;

# Edit the response file as appropriate
[root@WPSDMgr ~]# vi NewDB2ResponseFile.txt;

# Once edited, run the configuration script against the response file
[root@WPSDMgr ~]# ./config_event_database.sh NewDB2ResponseFile.txt;

# Then copy the resulting scripts to the database server
[root@WPSDMgr ~]# scp -r /opt/IBM/WebSphere/ProcServer/profiles/DMgr/event/dbscripts/db2 db2inst1@DB2Server:/tmp

# Execute the scripts on the database server
[db2inst1@DB2Server ~]# chmod -R 755 /tmp/db2;
[db2inst1@DB2Server ~]# cd /tmp/db2;
[db2inst1@DB2Server db2]# ./cr_event_db2.sh;

# Execute the cell configuration scripts on the WPS Deployment Manager
# Ensure the Deployment Manager is running
[root@WPSDMgr ~]# /opt/IBM/WebSphere/ProcServer/profiles/DMgr/bin/startManager.sh;
[root@WPSDMgr ~]# cd /opt/IBM/WebSphere/ProcServer/profiles/DMgr/event/dsscripts/db2;
[root@WPSDMgr db2]# ./cr_db2_jdbc_provider.sh cell;