Before you create an object store, consider where you will locate
the object store database, what database server to use, what users
will have access to the object store, and other configuration issues.
Consider the following questions before running this wizard:
- Whether to collocate the object store database with the global
configuration database. Although collocation is not recommended for
production systems, you can locate an object store database in the
same physical database as the global configuration database that is
created during Content Platform Engine installation.
For non-production situations such as development environments, test
configurations, or systems with small data requirements, collocating
an object store with the global configuration database can simplify
system management or reduce the costs that are associated with requiring
another database.
- Whether to create a file storage area or use the database storage
area for content storage.
- Which database type you are using. All the object stores that
you create must be based on the same database type. For example, you
cannot create an object store that is based on IBM®
DB2® for Linux, UNIX and Windows and another object store
that is based on IBM
DB2 for z/OS® or Microsoft SQL Server.
- Which users and groups work with the object store, and what access
rights the users and groups need. Object stores do not all need to
have the same initial set of users and groups. You can grant users
access to an object store when you create the object store. However,
adding users and groups after you create an object store is difficult
and time-consuming. To add a user or group to an existing object store,
you must manually add the user or group to all objects in the object
store and assign security settings as needed.
Tip: Before
creating an object store, create one or more generic access users
with the correct administrative rights to the database. When you run
the Create Object Store wizard, add the generic user to the object
store. For more information, see
Object
store access rights.
- Whether to create additional database connections. For more information,
see Sharing data sources.
- Which add-on features to install on the object store.
Choose only those add-on features that are supported by your product
or application. Each add-on user-defined property reduces the row
size from what already is reserved by the current system and add-on
properties. If you are in doubt about whether you need an add-on,
wait to install it until you can confirm that the add-on is necessary.