The checkstatus command checks the status of the specified configuration task. The command name is 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 checkstatus [-task task_type | -taskfile task_file_name] -profile myprofile [-help]
Option | Configuration file | 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 the status for all the configuration files in the profile is displayed. |
configurebootstrap | configurebootstrap.xml configurebootstrap.n.xml, where n is an integer starting with 2 |
Checks status for applying 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 check the status for the initial bootstrap task for the new profile and to check the status 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 check. |
configurejdbcgcd | configurejdbcgcd.xml |
Checks the status 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 |
Checks the status 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 cannot change the filename, but you can edit the value in the file for the name of the task. If your profile contains more than one configurejdbcos task, then you must specify the -taskfile task_file_name parameter to identify the task to check. |
configureLDAP | configureldap.xml configureldap.n.xml, where n is an integer starting with 2 |
Checks status for configuring 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 cannot change the filename, but you can edit the value in the file for the name of the task. If your profile contains more than one ConfigureLDAP task, then you must specify the -taskfile task_file_name parameter to identify the task to check. |
configureloginmodules | configureloginmodules.xml | (WebSphere Application Server or JBoss Application Server only.) Checks status for creating the login modules for the Content Engine application. |
deployapplication | deployapplication.xml | Checks status 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.
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.
configmgr_cl checkstatus -task configurejbcos -profile wstdb2jdbc
configmgr_cl checkstatus -taskfile configurejdbcos.2.xml -profile wstdb2jdbc
configmgr_cl checkstatus -task configureloginmodules -profile wstdb2jdbc
configmgr_cl checkstatus -help