Plan the DB2® for z/OS® installation
and configuration, install the software, and configure database components.
DB2 for z/OS planning considerations
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.
- 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.
- The database must be remote.
- The DB2 for z/OS database
must be remote from Content Platform Engine.
- Use System Managed Storage (SMS).
- Configure system managed storage for Content Platform Engine databases.
- Use UTF-8 collation
- Use UTF-8 collation settings by configuring CCSID UNICODE.
- Add SDSNLOD2 into the LNKLST.
- The SDSNLOD2 library must be added into the LNKLST.
- Use TCP/IP as the default protocol.
- Set TCP/IP as the default network protocol.
- Determine the maximum size of the content elements your users
store.
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.
- Set CACHE DYNAMIC SQL for Content Platform Engine
- The CACHEDYN subsystem parameter on the DSNTIP8 panel controls
whether prepared, dynamic SQL statements are to be cached. Content Platform Engine requires that this
parameter be set to YES for proper metadata authoring to occur.
- Set performance and optimization parameters for Content Platform Engine
- Set both of the following parameters, also on the DSNTIP8 panel,
to YES: SKIP UNCOMMITTED INSERTS (SKIPUNCI) and EVALUATE UNCOMMITTED
(EVALUNC).
- Features not supported.
- In this regard:
- There is no support for partitioned 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).
- Parallelism is not supported. Set CDSSRDEF=1 to
disable it.
Content Platform Engine, Version 5.2 Database:
DB2 for z/OS
Operating systems:
Linux on System z
