The listtasks command displays a list of the tasks and the task files in the configuration profile. The command name is not case sensitive.
configmgr_cl listtasks [-task task_type] -profile myprofile [-help]
Option | Configuration files | 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, then all the configuration tasks and the associated task files for the profile are listed. |
configurebootstrap | configurebootstrap.xml configurebootstrap.n.xml, where n is an integer starting with 2 |
Lists 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 |
Lists 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 |
Lists the task for configuring the settings for the JDBC connections to a single object store database used by Content Engine. You must 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. |
configureldap | configureldap.xml configureldap.n.xml, where n is an integer starting with 2 |
Lists the tasks 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. You cannot change the filename, but you can edit the value in the file for the name of the task. JBoss Application Server does not support multiple LDAP tasks. |
configureloginmodules | configureloginmodules.xml | (WebSphere Application Server or JBoss Application Server only.) Lists the task for configuring the login modules for the Content Engine application. |
deployapplication | deployapplication.xml | Lists the task for deploying the Content Engine application on the application server. |
configmgr_cl listtasks -profile wstdb2
All tasks in profile wstdb2. The tasks will be executed in the positions indicated when executing all tasks: Task 1: Name: Configure GCD JDBC Data Sources Type: configurejdbcgcd File: configurejdbcgcd.xml Task 2: Name: Configure Object Store JDBC Data Sources Type: configurejdbcos File: configurejdbcos.xml Task 3: Name: Configure Login Modules Type: configureloginmodules File: configureloginmodules.xml Task 4: Name: Configure LDAP Type: configureldap File: configureldap.xml Task 5: Name: Configure Bootstrap Properties Type: configurebootstrap File: configurebootstrap.xml Task 6: Name: Deploy Application Type: deployapplication File: deployapplication.xml
configmgr_cl listtasks -task configurejdbcos -profile wstdb2
Tasks in profile wstdb2 of the task type configurejdbcos: Task name: Configure Object Store JDBC Data Sources File: configurejdbcos.xml
configmgr_cl listtasks -help