Configuration
is a multiple step process. You must provide information about your Content Engine application environment,
then you apply the settings by running the configuration tasks, and
then you deploy the application. You can configure multiple instances
before you deploy any of them, or you can configure and deploy one
instance at a time.
You use
Configuration Manager to
define the following information for the
Content Engine instance:
- Application server properties
- Java™ Database Connectivity
(JDBC) data source properties for the Global Configuration Data (GCD) database
- Java Database Connectivity
(JDBC) data source properties for each object store database
- Directory service (LDAP) provider properties
- Content Engine application
login modules
- Content Engine bootstrap
properties
Remember the following
points when you prepare to configure
Content Engine:
- (WebSphere® Application
Server only)
For best results, configure no more than one Content Engine instance in a WebSphere profile.
- If you need an accessible software version of Configuration Manager for people with
disabilities, use the command-line version of Configuration Manager.
- If your system is HP-RISC, use the command-line
version of Configuration Manager.
- If your system is Novell SUSE Linux® Enterprise 9, use the command-line
version of Configuration Manager.
- If your FileNet® P8 domain
uses multiple non-managed application servers, then use a copy of
a single EAR file with the bootstrap settings on all the servers.
After you complete the tasks on the initial server, copy the EAR file
with the bootstrap settings to the additional servers.
Important: If you specified
an incorrect value for the .NET API COM Compatibility Layer (CCL)
server URL during Content Engine installation,
you cannot correct the URL by using Configuration Manager to edit
the dotnetclient configuration profile. Instead, correct the value
by completing the following steps: