Determine whether IBM®
DB2® for Linux, UNIX and Windows database
components will be dedicated to individual FileNet® P8 components or shared and
review other IBM
DB2 for Linux, UNIX and Windows database
requirements.
In a shared configuration, multiple
FileNet P8 components can store their
data in a single database. Most components allow for data to be collocated.
However, the best practice is to keep some in dedicated databases:
- The global configuration database: it is best practice to not
share this database.
- Object stores and their workflow system data although those part
of a single application family can be collocated given the factors
listed below. If you configure object stores in separate databases,
you have more flexibility and control with security access, backup
scheduling and execution, updates, and scheduled outages.
- Rendition Engine data
- IBM Content Navigator configuration
data: sharing the IBM Content Navigator database
with the global configuration database is not supported.
When you make the decision about whether to share a database for
multiple components, consider the following factors:
- Database backup/recovery requirements should allow for the data
that resides in a single database to be backed up and recovered together.
- Database security should allow for collocation of data.
- Sharing of a database might allow for more efficient usage of
database resources like database connections.
DB2 for Linux, UNIX and Windows version 9.7
is required for workflow system data to support GB18030 character
sets.
IBM
FileNet P8 does not support
partitioned DB2 databases
or databases created with the RESTRICTIVE clause (or, from the Control
Center, with Restrict access to system catalogs selected
in the Create Database Wizard).
Plan to use automatic storage for table spaces. For performance
reasons, IBM recommends that
you create table spaces using automatic storage, rather than database
managed or system managed table spaces.
Plan to use SERVER authentication.
Set the DB2 codeset to UTF-8.
Set the page size to 32 KB.
Determine the maximum size of the content elements your users store.
The size affects setting up database storage areas or file storage
areas. When you create an object store, a database storage area is
provided by default, allowing you to store content as database BLOBs.
You can also create one or more file storage areas to store content
on local or remote file systems. If your users store large individual
documents or other content elements, use only file storage areas.
Otherwise, users can encounter memory-related errors when retrieving
or indexing the large content.
Important: Controlled tests with limited concurrency exhibited
errors when run with files that were 300 MB or larger. Factors affecting
this file-size limitation include driver and application server memory
demands, other activity such as concurrent retrieval or indexing of
large content, and JVM memory allocations.