FileNet P8 Content Engine, Version 5.0.+              

Configuring Content Engine

You can configure and deploy all of your Content Engine instances with Configuration Manager. Configuration Manager prepares the Content Engine application for deployment on the application server. A single Content Engine application instance equates to one deployed application on your application server.

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:
  1. Open the configmgr.properties file for editing. This file is located in the path ce_install_path/tools/configure/configuration/. Find the line in the file that starts with CCL_URL and replace the URL with the correct value:
  2. Find the line in the file that starts with CCL_URL
    CCL_URL=http\://localhost\:port_number/wsi/FNCEWS40MTOM/
    and replace the URL with the correct value.
  3. Run Configuration Manager to reexecute the dotnetclient profile (which the Content Engine installation program automatically ran when it installed Content Engine). You can reexecute the profile using either the graphical user interface. Or you can reexecute the profile using the command-line interface:
    configmgr_cl execute -task configureDotNetAPI -profile dotnetclient


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)