- BPMDB - The Process Centre / Process Server databases
- PDWDB - The Performance Data Warehouse Database
- BSPDB - The Business Space Database (New in version 8, Business Space used to only be part of Advanced in v 7.x)
- MEDB - The Messaging Engine Database (In v7.x the ME tables were schema's under PDWDB and BPMDB
For some reason the documentation states that the Common Database is needed, but as far as I can tell it's not. There are no datasources configured for it during any part of the installation.
Example DB2 commands for creating the databases are as follows:
db2 create database <Database Name> automatic storage yes using codeset UTF-8 territory GB pagesize 32768;
db2 connect to <Database Name>;
db2 grant dbadm on database to user <user name>;
db2 UPDATE DB CFG FOR <Database Name> USING LOGFILSIZ 4096 DEFERRED;
db2 UPDATE DB CFG FOR <Database Name> USING LOGSECOND 64 DEFERRED;
db2 connect reset;
Once the databases have been created, you can create the tables and stored procedures within by using the scripts generated when you imported and generated the deployment environment:
(Note - create database scripts are provided for all but MEDB, however in most cases your DBA's will want to create the databases, apply any table space settings specific their standards (as above) and set you up with a user with rights for you to create the tables etc. (Not sure why none were provided for MEDB by the way. I guess somebody just forgot ;) )
BPMDB <dmgr profile>/dbScripts/PerformanceDW/DB2/BPMDB
Once the databases have been created, you can create the tables and stored procedures within by using the scripts generated when you imported and generated the deployment environment:
(Note - create database scripts are provided for all but MEDB, however in most cases your DBA's will want to create the databases, apply any table space settings specific their standards (as above) and set you up with a user with rights for you to create the tables etc. (Not sure why none were provided for MEDB by the way. I guess somebody just forgot ;) )
BPMDB <dmgr profile>/dbScripts/PerformanceDW/DB2/BPMDB
- db2 connect to BPMDB
- db2 -tvf createTable_ProcessServer.sql
- db2 -tvf createProcedure_ProcessServer.sql
- db2 terminate
PDWDB <dmgr profile>/dbScripts/PerformanceDW/DB2/PDWDB
- db2 connect to PDWDB
- db2 -tvf createTable_PerformanceDW.sql
- db2 terminate
BSPDB <dmgr profile>/dbScripts/PerformanceDW/DB2/BSPDB
A wrapper script is provided, however I've forgotten it's name...
Will follow
MEDB
The MEDB DDL needs to be generated by the SIBDDLGenerator.sh script as follows
sibDDLGenerator [ -systemDBMS name ][ -versionDBMS version ][ -platformDBMS platform ][ -schemaschema name ][ -useruser name ][{ -create -drop }][ -databasedatabase ][ -storagegroupstorage group ][ -cataloghigh level qualifier ][ -bufferpoolbuffer pool ][ -statementendstatement end ][ -nolinebreaks ][ -noblanklines ][ -firstlinefirst line ][ -lastlinelast line ][ -permanentnumber ][ -temporarynumber ]
You'll need 2 sets of DDL, one for the Process Server ME's and one for the PDW ME's.
I usually create a directory alongside the ones generated for the other databases (e.g. <dmgr profile>/dbScripts/PerformanceDW/DB2/MEDB) and then run the above command twice substituting the schema names each time to match the ones you specified in your Deployment Environment, and redirecting to a suitably named file each time
No comments:
Post a Comment