FileNet P8 Content Engine, Version 5.0.+       Application server:  WebSphere Application Server     

Generating one configuration XML file at a time (WebSphere)

From the command line, you can generate each of the required configuration XML files for Content Engine one file at a time.

You must generate the configuration XML files for each of these required configuration tasks:
  • Create the XML file for the bootstrap properties file by using the configurebootstrap option.
  • Create the XML file for configuring the JDBC Data Sources for the Global Configuration Data (GCD) database by using the configurejdbcgcd option.
  • Create the XML file for configuring the JDBC Data Sources for a single object store database by using the configurejdbcos option.
  • Create the XML file for configuring the LDAP provider by using the configureldap option.
  • WebSphere® Application Server and JBoss Application Server only. Create the XML file for configuring the login modules by using the configureloginmodules option.

To generate a single configuration XML file:

  1. Log on to the application server as config_mgr_user, which is the user who will run Configuration Manager.
  2. Change the current directory to ce_install_path/tools/configure.
  3. Run the appropriate command for the task you need. Do not type any line breaks when you enter the command.
    WebSphere Application Server only. Generate the configurebootstrap.xml file for the configurebootstrap task:
    configmgr_cl generateconfig -appserver app_server_type
     -repositorytype  ldap_repository_type
     -task configurebootstrap -bootstrap bootstrap_operation
     -profile myprofile
    Generate the configurejdbcgcd.xml file for the configurejdbcgcd task for the GCD data sources:
    configmgr_cl generateconfig -appserver app_server_type
     -repositorytype ldap_repository_type -db db_type
     -task configurejdbcgcd -profile myprofile
    Generate the configureldap.xml file for the configureldap task:
    configmgr_cl generateconfig -appserver app_server_type
     -repositorytype  ldap_repository_type -ldap ldap_type
     -task configureldap -profile myprofile
    Generate the configureloginmodules.xml file for the configureloginmodules task:
    configmgr_cl generateconfig -appserver app_server_type
     -repositorytype  ldap_repository_type -task configureloginmodules
     -profile myprofile
    where:
    -appserver appserver_name
    -appserver appserver_type specifies the type of application server and must be WebSphere.
    -repositorytype ldap_repository_type
    WebSphere Application Server only. The -repositorytype ldap_repository_type parameter specifies the type of LDAP repository to use and must be standalone or federated.
    -db database_type
    The -db database_type parameter is required only when you are generating files by using the configurejdbcgcd or configurejdbcos option. This parameter specifies the type of database to be used by Content Engine and must be mssql, oracle, oracle_rac, db2, or db2zos.
    -ldap ldap_type
    The -ldap ldap_type parameter is required only when you are generating all the files at the same time or when you are generating a single file by using the configureldap option. This parameter specifies the type of directory service repository that Content Engine uses for authenticating users and must be activedirectory, adam, edirectory, oid, sunjava, or tivoli. The adam value applies to both Microsoft® ADAM and AD LDS.
    -bootstrap bootstrap_operation
    The -bootstrap bootstrap_operation parameter is required only when you are generating all the files at the same time or when you are generating a single file by using the configurebootstrap option. This parameter specifies the bootstrap operation for the profile and must be new, modify, or upgrade.
    - 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 fully qualified 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".
  4. Repeat as needed to generate all the required XML configuration files.


Feedback

Last updated: November 2010


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