removetask command
The removetask command removes the specified task from the configuration profile. When you remove the task, the configuration XML file is deleted from the profile directory. The command name is not case sensitive.
removetask 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 removetask -task task_type | -taskfile task_file_name
-profile myprofile [-silent][-force][-help]removetask command parameters
- -task task_type
- The -task task_type parameter
is optional and indicates which task to remove. You can omit the -task task_type parameter
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 Platform Engine settings affected by
the task.
Table 1. task_type values Option Configuration file to remove Description configurejdbcgcd configurejdbcgcd.xml
Settings for configuring the JDBC connections to the Content Platform Engine database used by Content Platform Engine.
configurejdbcos configurejdbcos.xml
configurejdbcos.n.xml, where n is an integer greater than or equal to 2
Settings for configuring JDBC connections to a single object store database used by Content Platform Engine. You need to generate, edit, and apply the configurejdbcos task settings for each object store in your database.
If you generate a second object store JDBC configuration file, then 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
Configures the connection to the directory server for authenticating Content Platform 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.
If your profile contains more than one configureldap task, then you must specify the -taskfile task_file_name parameter to identify the task to remove.
deployapplication deployapplication.xml Deploys 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.
- -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.
removetask command examples
- Remove the configurejdbcos task from a profile with only one configurejdbcos task.
- The following command removes the configurejdbcos task
and the configurejdbcos.xml file from the profile
named wstdb2jdbc_one.
configmgr_cl removetask -task configurejdbcos -profile wstdb2jdbc_one - Remove the configurejdbcos task from a profile with several configurejdbcos tasks.
- The following command removes the configurejdbcos task
and the configurejdbcos.2.xml file from the profile
named wstdb2jdbc_many.
configmgr_cl removetask -taskfile configurejdbcos.2.xml -profile wstdb2jdbc_many - Remove the configurejdbcos task from a profile with several configurejdbcos tasks by using an absolute path to the profile directory.
- The following command removes the configurejdbcos task
and the configurejdbcos.2.xml file from the profile
named wstdb2jdbc_many that is located in the c:\temp\myprofiles\wstdb2jdbc_many directory.
configmgr_cl removetask -taskfile configurejdbcos.2.xml -profile c:\temp\myprofiles\wstdb2jdbc_many - Display the help for the removetask command.
- The following command displays the help for the removetask command:
configmgr_cl removetask -help