Object
stores are used to store documents, workflows and other objects. The New Object Store wizard leads
you through the steps required to create an object store.
Before you begin
When creating an object store, you either reuse an existing database connection or, if your
object store must have its own database, you must follow the same procedures required for creating
the initial object store. If you are reusing an existing database connection, you can run the New
Object Store wizard without any further preparations.
When creating an object store you have these choices:
- reuse an existing database connection. In this case you can run the New Object Store wizard,
explained below, without further preparation.
- put your object store into its own database. In this case you must first follow the database
creation and preparation instructions explained in Database administrator
installation tasks. Then run the database connection wizard, explained in Creating a database
connection. Then run the New Object Store wizard, explained below. Use your new database
connection while running the wizard.
Note: A single database and database connection can serve more than one object store. If you
are using database sharing, you can use the database connection for more than one object store,
provided you assign a unique schema name to each object store. However, if an object store must have
its own database, you cannot reuse the database connection. Do these prerequisite steps once for
each nonshared object store.
About this task
The New Object Store wizard fails to
complete if you try to assign the new object store to a database connection and schema name that has
already been used.
If
you encounter timeout errors when you create an object store or when you subsequently import add-on
features, the transaction timeout value setting might be too low. To modify the transaction timeout
value, see the appropriate topic for your application server:
Procedure
To create an object store:
- Start Administration Console for Content Platform Engine if you did not already
do so:
-
On any computer, open a browser and navigate to the Administration Console for Content Platform Engine logon page:
- In
a standard availability environment, the logon page is at
http://CPE_Server:port/acce
. CPE_Server is
the name of the system where Content Platform Engine is
deployed. port is the HTTP port that is used by
the application server where Content Platform Engine is
deployed.
- In a high availability environment, the logon page is at
http://virtual_server:port/acce
. virtual_server is
the name of the load balancer or proxy server where the clusters of Content Platform Engine is deployed. port is
the port number of the load balancer or proxy server.
- Log on as the gcd_admin user.
- In the tree view, right-click the Object Stores container and
choose New Object Store to start the wizard.
- Complete the wizard screens by using the values in your worksheet.
Important: Db2® for Linux®, UNIX and Windows
V10.1 or earlier and
Db2 for z/OS®:
The maximum row size of the
underlying DB2® database tables is 32 KB. Therefore, choose a
minimal set of add-on features before creating an object store. After the object store exists, be
aware that each user property reduces the row size from what already is reserved by the current
system and add-on properties. For more information about minimizing database row sizes, see Minimize database row sizes.
Tip: If the storage area creation fails when you run the New
Object Store wizard, the object store is still created. After the object store is
created, you can try again to create the storage area by running the appropriate storage area
wizard.
What to do next
After an object store is created, you can define its document classes, folders, security
policies, and other features required by your system design.
To enable content-based retrieval, see Finding objects with content-based retrieval.
Set up a file storage area or install a fixed content device, depending on where the object store
will store content.