importSolutionManifest command
The importSolutionManifest command imports a case management solution from a version control system into another environment by using a manifest and a set of files.
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 importSolutionManifest -profile myprofile
-solutionManifest mymanifest
-projectAreaName project_area_name
[-silent] [-force] [-help]Parameters
- -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.
- -solutionManifest mymanifest
- The full path to the solution manifest that you want to import.
If the path includes a directory name with spaces, enclose the path in double quotation marks. For example, enter "C:\Solution Manifests\SOL1_Manifest.json".
Any files that are related to the solution manifest must be in the same folder as the solution manifest.
- -projectAreaName project_area_name
- Specifies the name of the project area for the solution. This option is valid only for importing a solution package to into another development environment.
- -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.
- Import a solution package to a development environment by using a solution manifest.
- The following command imports the solution package that is identified by the SOL1 manifest to
the object store that is used in the MyDevelop1 profile. The solution will be assigned to the Credit
Dispute project area. This command also imports the SOL1 files that were extracted to the same
folder as the SOL1
manifest.
configmgr_cl importSolutionManifest -profile myDevelop1 -solutionManifest "C:\Solution Manifests\SOL1_Manifest.json" -projectArea "Credit Dispute" - Show the help for the importSolutionManifest command.
- The following command shows the help for the importSolutionManifest
command:
configmgr_cl importSolutionManifest -help