test command

The test command runs the test feature for a task or a profile environment. Some tasks do not have a test function.

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 test -task task_type | -taskfile task_file_name
 -profile myprofile [-silent][-force][-help]

Parameters

-task task_type

Indicates which task to test. This parameter must be included if the -taskfile task_file_name parameter is omitted. The following table describes the valid task names, the associated configuration XML file, and a description of the test performed by the task.

Table 1. task_type values
Option	Configuration file	Description
configibmbpm	configibmbpm.xml	Tests the connection between the Case configuration tool, the IBM® Business Automation Workflow host server, and the Content Platform Engine server.
deployibmbpmis	deployibmbpmis.xml	Tests the connection between the Case configuration tool and the Content Platform Engine server.
deploysolution	deploysolution.xml deploysolution.`n`.xml. `n` is an integer starting with 2.	Opens the role assignment page for you to assign LDAP users to the roles for this solution. You must run the `configmgr_cl execute -taskfile deploysolution.n -profile myprofile` before you assign roles. You can also assign users later in Case Client.
registeradmin	registeradmin.xml	Test the connection between the Case configuration tool and the IBM Content Navigator server and verifies the ID for the selected plug-in.
registercpeapplets	registercpeapplets.xml	This task registers the plug-in for IBM Content Navigator that contains the IBM FileNet® Process Designer applet. Tip: Run this task only if you want to launch the IBM FileNet Process Designer applet from Case Builder. You do not need to run this task to use the standalone IBM FileNet Process Designer.
registerprojectarea	registerprojectarea.xml	Test the connection between the Case configuration tool and the IBM Content Navigator server and verifies the Case Operations user credentials.
registerservices	registerservices.xml	Test the connection between the Case configuration tool and the IBM Content Navigator server and verifies the ID for the selected plug-in.
registertargetenv	registertargetenv.xml	Test the connection between the Case configuration tool and the IBM Content Navigator server and verifies the Case Operations user credentials.

-taskfile activity_file_name

Specifies the configuration.xml file to use.

If only one activity file exists for the activity_type, the -taskfile activity_file_name parameter is optional.

If more than one activity file for the activity_type exists, you must include the -taskfile activity_file_name parameter. The activity_file value is case sensitive if your operating system is case sensitive for file names.

-profile myprofile

Specifies the profile to use. The myprofile value can be one of the following items:

The name of the profile, such as develop1. The profile is located in the install_root/CaseManagement/configure/profiles directory. install_root is the location where IBM Business Automation Workflow is installed.
The full path to the profile directory, such as "install_root\CaseManagement\configure\profiles\develop1" or /install_root/CaseManagement/configure/profiles/develop1.
The full path to the profile input file, such as "install_root\CaseManagement\configure\profiles\develop1\develop1.cfgp" or /install_root/CaseManagement/configure/profiles/develop1/develop1.cfgp.

-silent

Optional: When you specify the -silent parameter, no prompts or informational messages are shown in the console, but the errors are written to the log. Failure messages and validation error messages are shown as needed, such as messages about missing passwords or invalid port numbers. If you run the execute command to run all the activities in a profile and you specify the -silent parameter, you must also specify the -force parameter.

-force

Optional and applies only when the -silent parameter is used. When you specify the -force parameter, the activity is run without pausing for required responses to validation error messages, such as messages about missing passwords or invalid port numbers.

-help

Optional: Shows a brief message on the command syntax instead of running the command.

Sample commands

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.

Test the deploysolution task from a profile with only one deploysolution task.

The following command tests the deploysolution task and the deploysolution.xml file from the profile named deploy_one:

configmgr_cl test -task deploysolution -profile deploy_one

Test the deploysolution task from a profile with several deploysolution tasks.

The following command tests the deploysolution task and the deploysolution.2.xml file from the profile named deploy_many:

configmgr_cl test -taskfile deploysolution.2.xml
 -profile deploy_many

Test the deploysolution task from a profile with several deploysolution tasks by using an absolute path to the profile directory.

The following command tests the deploysolution task and the deploysolution.2.xml file from the profile named deploy_many that is in the c:\temp\myprofiles\deploy_many directory:

configmgr_cl test -taskfile deploysolution.2.xml 
-profile  c:\temp\myprofiles\deploy_many

Show the help for the test command.

The following command shows the help for the test command:

configmgr_cl test -help