BPM v75* database set-up procedure

Implementing the BPM databases is divided into sections as follows:

Steps 1 through 3 would typically be carried out by the database administrators, steps 4 and 5 are carried out by the engineer building the BPM system.

1. Creating the database - In Oracle, this is effectively the SID (Note: I'm assuming we'll do all this on one database - or SID - and we'll seperate everything using schemas - I've seen it done this way, bit of a pain really and I wouldn't choose this approach normally - will document the multiple database / SID approach another time)
2. Creating the tablespaces - This is the act of creating some space on the file system (or on a raw device directly)
3. Creating the schemas - Technically, this step is actually creating the users. In Oracle, when you create a user Oracle creates the SCHEMA object as part of the CREATE USER statement and the SCHEMA has the same name as the USER. Here's the difference for reference purposes ... USER is the account name, SCHEMA is the set of objects owned by that user.
4. Create the tables - In this step we connect as the user created above in the Create Schema step and create all of the required tables within that schema
5. Populate the Lombardi tables - i.e. run the bootstrap 

In order to carry out steps 2 and 3, the database admins require schema names and passwords for the following schemas:

In order to carry out steps 2 and 3, the database admins require schema names and passwords for the following schemas:

• Common
• Process Server / Centre - The Process Centre and the Process Server DDL's are identical - the difference is what they are populated with via the bootstrap process (and of course the WAS profile tempaltes are different)
• Performance Data Warehouse
• Business Space
• Process Choreographer
• Messaging - There are six messaging schemas for BPM 75* Advanced, one for each messaging engine - SYS, APP and BPC (for WPS), PS/PC and PDW (for Lombardi) and CEI (or the Common Event Infrastructure)