FileNet P8 Content Engine, Version 5.0.+              

Configuring Content Engine

You can configure and deploy all of your Content Engine instances by using Configuration Manager. A single Content Engine application instance equates to one deployed application on your application server.

Important: You must use the LDAP directory that you used in version 3.5.2 of Content Engine. The directory cannot just have the identical users and groups, but must have the original SIDs in their SID History. If the new Content Engine version does not support the version of LDAP directory used in version 3.5.2, you can upgrade the LDAP directory after upgrading Content Engine.

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.

Begin the configuration process by ensuring that you have the necessary operating system permissions to use Configuration Manager.

To grant permissions to the Configuration Manager user:

  1. Log on as ce_install_user to the server where you installed Content Engine.
  2. Grant permissions to the config_mgr_user user for the executable file that you intend to use:
    Option Description
    UNIX® - graphical user interface Grant execute permission to configmgr
    UNIX - command line Grant execute permission to configmgr_cl
    Windows® - graphical user interface Grant read and execute permission to configmgr.exe
    Windows - command line Grant read and execute permission to configmgr_cl.exe
  3. Grant write permission to the directory where you want Configuration Manager to place the configuration XML files that it creates.

    If you do not specify the profile directory when you run Configuration Manager, grant write permission on the default directory ce_install_path/tools/configure and all its files and subdirectories.

  4. Log off the Content Engine server and log on again as config_mgr_user.


Feedback

Last updated: November 2010


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