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.
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]
Option | Configuration files | Description |
---|---|---|
configurebootstrap | configurebootstrap.xml configurebootstrap.n.xml, where n is an integer starting with 2 |
Moves the task for configuring 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. |
configurejdbcgcd | configurejdbcgcd.xml |
Moves the task for configuring the settings for the JDBC connections to the Global Configuration Data (CGD) database used by Content Engine. |
configurejdbcos | configurejdbcos.xml configurejdbcos.n.xml, where n is an integer starting with 2 |
Moves the task for configuring the settings for the JDBC connections to a single object store database used by Content 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 starting with 2 |
Moves the task for configuring the connection to the directory server for authenticating Content 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. JBoss Application Server does not support multiple LDAP tasks. |
configureloginmodules | configureloginmodules.xml | Moves the task for configuring the login modules for the Content Engine application. |
deployapplication | deployapplication.xml | Moves the task for deploying the Content Engine application on the application server. |
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.
configmgr_cl movetask -taskfile configurejdbcos.3.xml -position 1 -profile wstdb2
configmgr_cl movetask -task configureoginmodules -position 5 -profile wstdb2
configmgr_cl movetask -help