movetask command
The movetask command moves a task to a different position in the list of tasks. The task position determines the order that the tasks are run when you run all the tasks at the same time. You use the listtask command to display the task order. The command names are not case sensitive.
movetask 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 movetask -task task_type | -taskfile task_file_name
-position new_position -profile myprofile [-silent][-force][-help]movetask command parameters
- -task task_type
- The -task task_type parameter
indicates which task to move. This parameter must be included if the -taskfile task_file_name parameter
is omitted. 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 Platform Engine settings affected by
the task.
Table 1. task_type values Option Configuration files Description configurejdbcgcd configurejdbcgcd.xml
Moves the task for configuring the settings for the JDBC connections to the global configuration database database used by Content Platform Engine.
configurejdbcos configurejdbcos.xml
configurejdbcos.n.xml, where n is an integer greater than or equal to 2
Moves the task for configuring the settings for the JDBC connections to a single object store database used by Content Platform Engine.
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.
configureldap configureldap.xml
configureldap.n.xml, where n is an integer greater than or equal to 2
Moves the task for configuring the connection to the directory server for authenticating Content Platform Engine users.
(WebSphere® Application Server or Oracle WebLogic Server only) When you generate a second LDAP configuration file, it is named configureldap.2.xml. The filename increments for each new file you generate.
When you generate a second LDAP configuration file, it is named configureldap.2.xml. The filename increments for each new file you generate.
deployapplication deployapplication.xml Moves the task for deploying the Content Platform Engine application on the application server. - -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.
- -positionnew_position
- The -positionnew_position parameter specifies the new position in the list for the item. You can run the listtasks to view the list of tasks in the profile and their position before you run the movetask command.
- -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 Platform 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.cfgp" or /opt/IBM/FileNet/ContentEngine/tools/configure/profiles/ce_was_tiv_db2/ce_was_tiv_db2.cfgp.
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.cfgp". - -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.
movetask command examples
- Move the task for the configurejdbcos.3.xml file in a profile with more than one configurejdbcos task.
- The following command moves the task for the configurejdbcos.3.xml file
for the wstdb2 profile located in the ce_install_path/tools/configure/profiles/wstdb2 directory
to position 1:
configmgr_cl movetask -taskfile configurejdbcos.3.xml -position 1 -profile wstdb2 - Move the configureldap task.
- The following command moves the configureldap task from the default position of
task 3 to task 5 in the wstdb2 profile located in the
ce_install_path/tools/configure/profiles/wstdb2
directory:
configmgr_cl movetask -task configureldap -position 2 -profile wstdb2 - Display the help for the movetask command.
- The following command displays the help for the movetask command:
configmgr_cl movetask -help