FileNet P8 Content Engine, Version 5.0.+              

Configuring upgraded instances by using the command line

You can configure an upgraded Content Engine instance on a web application server by using the command-line version of Configuration Manager.

Ensure that you have the required accounts and appropriate permissions before you begin.

To configure the upgraded Content Engine instance:

  1. Log on to the machine where Content Engine is installed as config_mgr_user, which is the Configuration Manager user.
  2. Change the current directory to ce_install_path/tools/configure, where ce_install_path is the path where you installed Content Engine.

    As an example, ce_install_path might be /opt/FileNet/ContentEngine.

  3. At a command prompt, run the generateupgrade command to generate the upgrade profile. Enter the command on one line without line breaks.
    configmgr_cl generateupgrade [-appserver app_server_type] -server server_name
     [-deploy deploy_type] -profile myprofile [-silent] [-force] [-help]

    Where:

    -appserver appserver_type
    The -appserver appserver_type parameter is required only if the ce_install_path/Servers.xml file does not exist or does not contain any servers. This parameter specifies the type of application server and must be one of the following values: WebSphere, WebLogic, or JBoss.
    -server server_name
    The -server server_name parameter indicates the server to create the upgrade profile for. Use the listservers command to display a list of valid server_name values before you run the generateupgrade command.
    -deploy deploy_type
    The -deploy deploy_type parameter is required only if the ce_install_path/Servers.xml file does not exist or does not contain the deployment type for the selected server. This parameter specifies the type of Content Engine deployment. If a value for the deployment type exists in the Servers.xml file for the selected server, then the value from the Servers.xml file is used instead the value you specify on the command line.

    Select one of the following values: standard, cluster, or netdeploy (network deployment).

    Specify standard if you are deploying Content Engine to a stand-alone (that is, a server that is neither managed nor clustered) WebSphere® Application Server, Oracle WebLogic Server, or JBoss Application Server.

    Specify cluster if you are deploying Content Engine to a WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server cluster

    Specify netdeploy if you are deploying Content Engine to a managedWebSphere Application Server instance. That is, you are using Network Deployment to manage individual servers that are not necessarily in a cluster.

    -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".
    -silent
    The -silent parameter is optional. When -silent is specified, then no prompts or informational messages are displayed in the console, but the errors are written to the log. Failure messages and validation error messages are displayed as needed, such as messages about missing passwords or invalid port numbers. If you run the execute command to run all the tasks in a profile, and you specify the -silent parameter, you must also specify the -force parameter.
    -help
    The -help parameter is optional and displays a brief message on the command syntax instead of running the command.

    The upgrade.xml file and one directory named for each existing Content Engine instance is created in the profile directory.

    Important: If the generateupgrade command returns a message saying that an upgrade profile already exists, skip to 4.
  4. (IBM® WebSphere Application Server or Oracle WebLogic Server only) Set the application server administrator properties:
    1. Navigate to the myprofile/mycontent_engine_instance directory.
    2. Open the applicationserver.xml file in a text editor.
    3. Set the value for the ApplicationServerAdminUsername property.
      <propertyname="ApplicationServerAdminUsername">
      	<value>administrator_user_name </value>
      </property>
    4. Save your changes and close the file.
    5. Run the storepasswords command, which prompts you (respond with yes or no) to choose whether to encrypt and store the web application server administrator password to the applicationserver.xml file. If you choose to not save the password, you will need to edit applicationserver.xml by specifying the clear text of the password for the ApplicationServerAdminPassword property.
      configmgr_cl storepasswords -profile myprofile
      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).
    6. Repeat this step as needed to edit the application server properties for each Content Engine instance directory that was created.
  5. (WebSphere only) If you are upgrading Content Engine from version 4.0.1 or 4.5.0, at a command prompt run the execute command to configure the login modules:
    configmgr_cl generateconfig -appserver app_server_type
     -repositorytype  ldap_repository_type -task configureloginmodules
     -profile myprofile

    Where:

    -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.
  6. (JBoss only) If you are upgrading Content Engine from version 4.0.1, 4.5.0, or 4.5.1 at a command prompt run the execute command to configure the login modules:
    configmgr_cl execute -task configureloginmodules -profile myprofile
  7. At a command prompt, run the execute command to configure the bootstrap properties.
    configmgr_cl execute -task configurebootstrap -profile myprofile
    Status messages are displayed in the console.
  8. Optional: At a command prompt, check the completion status of the task by running the checkStatus command.
    configmgr checkStatus -task configurebootstrap -profile myprofile


Feedback

Last updated: November 2010


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