IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Messaging tuning
Use a single database for all messaging engines
Instead of having a DB2 database per messaging engine, put all messaging engines into the same database using different schemas to separate them.
When you use the database design tool to define the database configuration for each bus, you can specify a prefix for table space names. If you intend to use a single database for all the buses, you must specify a unique table space prefix for each bus to make its table space names unique within the database.
| Schema | Messaging engine |
|---|---|
| V1C1S | v1sr01.000-.SCA.SYSTEM.v1cell.Bus |
| V1C1A | v1sr01.000-SCA.APPLICATION. v1cell.Bus |
| V1C1C | v1sr01.000-CommonEventInfrastructure_Bus |
| V1C1B | v1sr01.000-.BPC.v1cell.Bus |
A sample script is provided on z/OS for creating the SIB schema. This script adopts the above naming conventions. For additional information, see the Redbooks publication
titled z/OS: WebSphere Business Process Management V7 Production Topologies at: 
http://www.redbooks.ibm.com/redpieces/abstracts/sg247831.html.