FileNet P8 Content Engine, Version 5.0.+              

Editing the configuration XML files for a Content Engine instance

You must edit each configuration XML file to provide the property values for your environment. You can use any text editor to open and edit the files.

Be sure that you have available the Installation and Upgrade Worksheet that was completed during your planning activities.

To edit values in the configuration XML files:

  1. Open your completed Installation and Upgrade Worksheet file.
    Tip: In the worksheet file, verify that the Data > Filter > AutoFilter command is enabled. To view only Configuration Manager values, in the Installation or Configuration Program column filter by each of the following items, depending on which XML file you are editing:
    • CM: Set Application Server properties
    • CM: Configure GCD JDBC Data Sources
    • CM: Configure LDAP
    • CM: Configure Bootstrap Properties
  2. Use a text editor or XML editor to open one of the following configuration XML files that you generated:
    • applicationserver.xml
    • configurejdbcgcd.xml for the Global Configuration Data (GCD)
    • configureldap.xml
    • configurebootstrap.xml

    Do not edit the configureloginmodules.xml, configurejdbcos.xml, or deployapplication.xml files at this time.

  3. Make the following changes to each XML configuration file:
    1. Replace each occurrence of ****INSERT VALUE**** with a value appropriate for your site. See the descriptions in the file for more information.
      Important: You do not need to supply values for passwords. You can run the storepasswords command later to add encrypted passwords to the file.
    2. Verify that the default values for the remaining properties are correct for your site.
    3. Set the enabled attribute value in the <configuration> tag to true in any configuration XML file you edit if you want to run the configuration task.
  4. (WebSphere® Application Server only) If you created XA and non-XA data sources that you want to use for the Global Configuration Data (GCD) database, make the following edits:
    1. In the configurejdbcgcd.xml file, set the enabled attribute value to false in the <configuration> tag to avoid creating another pair (XA and non-XA) of data sources.
    2. In the configurebootstrap.xml file, set the <JDBCDataSourceXAFileName> and <JDBCDataSourceFileName> values to the XA and non-XA JNDI names, respectively, that are associated with the GCD database.
  5. Save your edits and close the XML file.
  6. Optional: Add encrypted passwords to the XML files by running the storepasswords command.
    Tip: If the storepasswords command prompts you to store passwords in configuration files on disk, you must respond with yes or no (instead of y or n).
    .
    1. Enter the following command on one line:
      configmgr_cl storepasswords [-task task_type | -taskfile task_file_name]
       -profile myprofile

      where:

      -task task_type
      The -task task_type parameter is optional and specifies a task for which to encrypt passwords. The task_type value is not case sensitive. The following table lists each valid task name, its associated configuration XML file, and a description of the Content Engine settings affected by the task.
      Table 1. task_type values
      Task Configuration file Description
      omitted

      applicationserver.xml

      configurebootstrap.xml

      configurejdbc.xml

      configureldap.xml

      deployapplication.xml

      When you omit the -task task_type parameter, you are prompted to enter the passwords for each configuration XML file in the profile. Each password is encrypted before it is added to the XML file.
      configurebootstrap configurebootstrap.xml Encrypts the password for the BootstrapPassword property that is used to create the Global Configuration Data and to start Content Engine.
      configurejdbcgcd

      configurejdbcgcd.xml

      Encrypts the password for the DatabasePassword property that Content Engine uses to access the GCD database.

      configurejdbcos

      configurejdbcos.xml

      configurejdbcos.n.xml, where n is an integer starting with 2

      Encrypts the password for the DatabasePassword property that Content Engine uses to access the object store database.

      If you have more than one configurejdbcos.n.xml file, run the command for each task file.

      configureldap

      configureldap.xml

      configureldap.n.xml, where n is an integer starting with 2

      Encrypts the password for the LDAPBindPassword property that Content Engine uses to connect to the directory server for authenticating Content Engine users.

      If you have more than one configureldap.n.xml file, run the command for each task file.

      -taskfile task_file_name
      The -taskfile task_file_name parameter specifies the configuration XML file to use.

      If only one task file exists for the task_type, then the -taskfile task_file_name parameter is optional.

      If more than one task file for the task_type exists, then you must include the -taskfile task_file_name parameter. You can omit the -task task_type parameter when you specify the -taskfile task_file_name parameter.

      -profile myprofile
      The -profile myprofile parameter specifies the profile to use. The myprofile value can be one of the following items:
      • The name of the profile, such as ce_was_tiv_db2. The profile must be located in the ce_install_path/tools/configure/profiles directory, where ce_install_path is the location where the Content Engine software is installed.
      • The absolute path to the profile directory, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2.
      • The absolute path to the profile input file, such as "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfg" or opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2/ce_was_tiv_db2.cfg.
      Remember: If the path includes a directory name with spaces, enclose the entire path in quotation marks. For example, enter "C:\Program Files\IBM\FileNet\ContentEngine\tools\configure\profiles\ce_was_tiv_db2\ce_was_tiv_db2.cfg".
  7. Repeat this procedure as needed until you edit all the required files.


Feedback

Last updated: November 2010


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