Guidelines for sharing database connections

Database connection sharing enables multiple object stores or isolated regions that reside in a single database to share a single data source. The ability to share a database is achieved by the use of a schema name. At object store creation time, you can specify a schema name and all the tables and indexes are created within that schema.

Database connection sharing provides the following benefits:
  • Reduces the application server administrative overhead of managing the data sources
  • Reduces the database administrator overhead with fewer databases
  • Reduces usage of database connections by the Content Platform Engine server
  • Allows you to create new object stores without the intervention of the database administrator and the application server administrator
  • Object stores and isolated regions that share a database require fewer data sources and database connections.

Restrictions

  • Object stores or isolated regions that must be backed up independently must be stored in separate databases.
  • (Db2® for z/OS® only) Because schema names have global visibility within a Db2 for z/OS server, make sure to use a separate schema name for every object store that is created on your server. This is necessary even when the schemas reside in different databases within a shared Db2 for z/OS server.
  • Object stores and isolated regions that are used for IBM® Case Manager must be stored in the same database and therefore cannot be backed up independently.