im installsolution
installs a solution template
Synopsis
im installsolution [--[no]confirmPartial] [--conflictPrefix=value] [--[no]createData] [--groupMap=value] [--prefix=value] [--siProjectDir=value] [--solutionFile=value] [--userMap=value] [--user=name] [--hostname=server] [--password=password] [--port=number] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--quiet] [--cwd=directory] [--forceConfirm=[yes|no]] [-g|--gui] [--settingsUI=[gui|default]] [--status=[none|gui|default]]
Description
im installsolution runs the installer that sets up a solution. For example:
im installsolution --createAdmins --prefix=RM_ --solutionFile=C:/MKS/rm2007.imt --groupMap=Administrators=everyone,Analysts=everyone,Integrations=everyone,Manager=everyone,Testers=everyone --userMap=administrator=guest,analyst=guest,developer=guest,integration=guest,manager=guest,tester=guest --siProjectDir=C:/RM_repo7
|
|
To successfully install a solution, you must specify the hidden option --createAdmins. If you do not specify this option, the installation fails and does not display an error message.
|
Options
This command takes the universal options available to all
im commands, as well as some general options. See the
options reference page for descriptions.
• --[no]confirmPartial
specifies whether to be prompted to confirm the partial installation of the solution template when no prefix is specified.
• --conflictPrefix=value
specifies a conflict prefix to prepend to projects, states, fields, types, triggers, and other object names that may conflict with existing object names. This is most likely to occur if you are installing the solution without a prefix. Specifying a conflict prefix is optional.
• --[no]createData
specifies whether to create sample data when installing the solution. Sample data populates certain pre-defined configuration management projects. The sample data can be helpful if you intend to use the installation for evaluation and training; however, if you plan to use this installation for production work, PTC recommends that you clear the option and install without the sample data. Sample data is not easily deleted after installation.
• --groupMap=value
specifies the mapping of the solution to local groups on the system in the format solutionGroup=localGroup[,...].
• --prefix=value
specifies the prefix to apply to projects, states, fields, types, triggers, and other objects set up by the installer. To distinguish the new objects from your existing ones, a prefix is applied to the newly created objects. For example, if you accept the default prefix of RM_, then states such as Reject and Defer are named instead RM_Reject and RM_Defer. If your current database is not already configured, then you may also choose to set a blank prefix; however, if you set a blank prefix, subsequent templates will require a prefix upon installation.
• --siProjectDir=value
specifies the name of the target directory where the installer places sample data on the configuration management system.
• --solutionFile=value
specifies the name of the .imt file containing the solution. For example, for MKS Requirements the file name is rm_2007.imt.
• --userMap=value
specifies the mapping of the solution to the local user on the system in the form solutionUser=localUser[,...].
See Also
