Create an object store

The Create an Object Store wizard steps you through creating an object store. After successfully completing the wizard, the newly-created object store appears in the Enterprise Manager tree when you expand the Object Stores node. Additionally, if you expand the target Object Store node, the default object store objects, such as document class, property template, and choice lists, display.

You can access the Create an Object Store wizard several ways: from the Content Engine Getting Started page, from a context menu accessed from the Enterprise Manager tree, or from the Action menu.

NOTE  Prior to running this wizard, you must first create a target database and database user for the object store, and you must also create the necessary Connection Pools and Data Sources in your application server to access the database. For more information, see the FileNet P8 Platform Installation and Upgrade Guide.

From the Content Engine Getting Started page

  1. Click Enterprise Manager [domain] in the Enterprise Manager tree. In the right pane, the Getting Started with Content Engine page is displayed.
  2. Click the Create an Object Store link.
  3. Click on Start in Start the Create an Object Store wizard.
  4. Complete the wizard, referring to the help text provided.

From a context menu

  1. In Enterprise Manager tree, right-click Object Stores and click New Object Store.
  2. Complete the wizard, referring to the help text provided.

From the Action menu

  1. Select Object Stores in the Enterprise Manager tree.
  2. In the toolbar, click Action > New Object Store.
  3. Complete the wizard, referring to the help text provided.

NOTE  If enabling content-based retrieval (CBR), be sure to refer to the FileNet P8 Platform Installation and Upgrade Guide topic "Configure the Content Engine for Content-Based Retrieval."

Row Size Limit with DB2

Creating an object store in the Content Engine allows you to also create custom properties. Each property becomes a column in a property description table. The more properties you create, the more columns are created, and the rows containing the property descriptions can get very long. DB2 has a default limit of 32,000 bytes for the row length.

If you create an object store and define too many properties for a given object class, you could exceed the 32,000 row size limitation, and receive an error when adding any new property definitions to a class.

There are four components that determine the row size. Run the following SQL queries to determine whether the row size sum is nearing its limit.

NOTE  The following example is for the DocVersion table, which defines the Document class properties. Custom Objects are in the Generic table.

1. For non-UCS-2, non-LOb columns:

SELECT SUM(length) FROM syscat.columns WHERE TABSCHEMA = 'SCHEMANAME' AND tabname = 'DOCVERSION' AND typename != 'BLOB' AND typename != ‘DBCLOB’ AND typename != 'VARGRAPHIC'

2. Add that sum to the UCS-2 column sum (* 2 for double-byte):

SELECT 2 * SUM(length) FROM syscat.columns WHERE TABSCHEMA = 'SCHEMANAME'' AND tabname = 'DOCVERSION' AND typename !=VARGRAPHIC'

3. For the LObs:

A maximum overhead (see below excerpt) for the BLOb descriptors could be:

SELECT SUM(300) FROM syscat.columns WHERE TABSCHEMA = 'SCHEMANAME ' AND tabname = 'DOCVERSION' AND typename != 'BLOB'

4. For DBCLObs:

SELECT SUM(300) FROM syscat.columns WHERE TABSCHEMA = 'SCHEMANAME' AND tabname = 'DOCVERSION' AND typename != ‘DBCLOB’