FileNet P8 Content Engine, Version 5.0.+              

execute command

The execute command applies the settings from a configuration XML file for the specified configuration task. The command name is not case sensitive.

execute command syntax

The following syntax includes line breaks to format the command for reading. Enter the command and options on a single line, without any line breaks.

configmgr_cl execute [-task task_type | -taskfile task_file_name]
 -profile myprofile [-silent] [-force] [-help]

execute command parameters

-task task_type
The -task task_type parameter is indicates which task to run. You can omit the -task task_type parameter if you want to run all of the tasks or if you specify the -taskfile task_file_name parameter. The task_type value is not case sensitive. The following table lists the valid task names, the associated configuration XML file, and a description of the Content Engine settings affected by the task.
Table 1. task_name values
Option Configuration file to execute Description
omitted

configurebootstrap.xml

configurebootstrap.n.xml

configurejdbcgcd.xml

configurejdbcos.xml

configurejdbcos.n.xml

configureldap.xml

configureldap.n.xml

configureloginmodules.xml

deployapplication.xml

where n is an integer starting with 2

If you omit the -task task_type parameter and the -taskfile task_file_name parameter, then all the configuration files in the path are run. Any configuration XML file that has the enabled attribute value in the <configuration> tag set to false is skipped.
configurebootstrap

configurebootstrap.xml

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

Applies the settings for the Content Engine bootstrap on the application server. The bootstrap information is needed for creating the Global Configuration Data and for starting Content Engine

When you generate a second bootstrap configuration file, it is named configurebootstrap.2.xml. The filename increments for each new file you generate. You cannot change the filename, but you can edit the value in the file for the name of the task. For example, you might must run the initial bootstrap task for the new profile and then later run another task for modifying the EAR file to apply a fix pack.

If your profile contains more than one configurebootstrap task, then you must specify the -taskfile task_file_name parameter to identify the task to run.

configurejdbcgcd

configurejdbcgcd.xml

Applies the settings for configuring the JDBC connections to the Global Configuration Data (GCD) database used by Content Engine.

configurejdbcos

configurejdbcos.xml

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

Applies the settings for configuring JDBC connections to a single object store database used by Content Engine. You need to generate, edit, and apply the configurejdbcos task settings for each object store in your database.

When you generate a second object store JDBC configuration file, it is named configurejdbcos.2.xml. The filename increments for each new file you generate. You can edit the file name as needed.

If your profile contains more than one configurejdbcos task, then you must specify the -taskfile task_file_name parameter to identify the task to run.

configureldap

configureldap.xml

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

Configures the connection to the directory server for authenticating Content Engine users.

WebSphere® Application Server or Oracle WebLogic Server only.) If you generate a second LDAP configuration file, then it is named configureldap.2.xml. The filename increments for each new file you generate. You can rename the file as needed.

JBoss does not support multiple LDAP tasks.

If your profile contains more than one configureldap task, then you must specify the -taskfile task_file_name parameter to identify the task to run.

Oracle WebLogic Server only. When you run configureldap option, the
weblogic.security.
providers.authentication.
DefaultAuthenticator.
ControlFlag
value is set to SUFFICIENT for authenticating users.
configureloginmodules configureloginmodules.xml (WebSphere Application Server or JBoss Application Server only.) Creates the login modules for the Content Engine application.
deployapplication deployapplication.xml Deploys the Content Engine application on the application server.
registerem registerem.xml Windows® only. Registers or unregistersEnterprise Manager from the Windows Registry.
-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".
-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.
-force
The -force parameter is optional and only applies when the -silent parameter is used. When -force is specified, then the task is run without pausing for required responses to validation error messages, such as messages about missing passwords or invalid port numbers.
-help
The -help parameter is optional and displays a brief message on the command syntax instead of running the command.

execute command examples

The following examples include line breaks to format the command for reading. Enter the command and options on a single line, without any line breaks.

Run all the tasks in a profile.
The following command runs all the tasks in the wstdb2jdbc profile, which is located in the ce_install_path/tools/configure/profiles/wstdb2jdbc directory. If you include the -silent parameter in the command, you must also include the -force parameter.
 configmgr_cl execute -profile wstdb2jdbc
Run the configurejdbcos task in a profile with one configurejdbcos task.
The following command runs the configurejdbc task in the ce_install_path/tools/configure/profiles/wstdb2jdbc directory:
 configmgr_cl execute -task configurejdbcos -profile wstdb2jdbc
Run a single configurejdbcos task in a profile with multiple configurejdbcos tasks:
The following command runs the configurejdbcos.2.xml task file in the ce_install_path/tools/configure/profiles/wstdb2jdbc directory:
 configmgr_cl execute -taskfile configurejdbc.2.xml -profile wstdb2jdbc
Display the help for the execute command.
The following command displays the help for the execute command:
configmgr_cl execute -help


Feedback

Last updated: November 2010


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