Page tree

Skip to end of metadata
Go to start of metadata

This topic explains how you can preconfigure Parasoft Test products during installation to streamline consistent installation across multiple team machines. This process applies to all supported platforms and IDEs.

Sections include:

Preconfiguring the Installation

To preconfigure Parasoft Test during installation:

  1. Create a localsettings file that includes the options you want to preconfigure the installation with. An example is provided below. For more details, see Configuring Localsettings.
  2. Pass that localsettings file to the installer using the /configure or --configure parameter. For example:
    • Windows: /configure=<path-to-localsettings-file>
    • Unix: --configure <path-to-localsettings-file>

The localsettings file will be copied into the root directory of Parasoft Test as parasofttest.ini. Settings from that file are used to initialize a clean workspace during startup in UI mode.

Tip - Other Ways to Configure Licenses

You can also configure licensing upon command line startup using -localsettings. For details, see Licensing.

If you want to apply settings to an existing workspace, you need to add an additional property to the localsettings file: enforce.configure=true. This overrides existing settings during the first startup after the installation/reinstallation.

Note that with the Windows installer:

  • If the same version (or a newer version) of Parasoft Test is installed on the machine, the localsettings file won't be copied during installation or reinstallation.
  • If the location passed in /ParasoftTestDir is different than the location of an existing Parasoft Test installation, the localsettings file won't be copied during reinstallation.

Windows Options

OptionDescription

/SILENT
/VERYSILENT

Run installer in silent mode. The wizard and the background window are not displayed.
/DIR=<location>Destination location for installed product's files.
/EclipseDir=<location>Location of target platform.
/Configure=<localsettings file>Pre-configure product during installation step.
/ParasoftTestDir=<location>Destination location for Parasoft Test's files (Use this option if Parasoft Test is not already installed). 

 

See http://www.jrsoftware.org/ishelp/index.php?topic=setupcmdline for additional options and help.

UNIX Options (for Linux, Solaris, or Mac)

OptionDescription
--non-interactiveRun installer in non interactive mode.
--install-dir <location>Destination location for installed product's files.
--target-location <location>Location of target platform (e.g., Eclipse). 
--configure <localsettings file>Pre-configure product during installation step.
--parasofttest-install-dir <location>Destination location for Parasoft Test's files. 
--helpPrints the available command line options

Installation Examples

Windows

parasoft_jtest_9.2_win32.exe /SILENT /DIR=<jtest dir> /ParasoftTestDir=<parasofttest dir> /configure=<localsettings file>
parasoft_jtest_9.2_win32_eclipse_plugin.exe /SILENT /DIR=<jtest dir> /ParasoftTestDir=<para-softtest dir> /EclipseDir=<eclipse dir> /configure=<localsettings file>

Unix

parasoft_jtest_9.2_linux.sh --non-interactive --install-dir <jtest dir> --parasofttest
-install-dir <parasofttest dir> --configure=<localsettings file>
parasoft_jtest_9.2_linux_eclipse_plugin.sh --non-interactive --install-dir <jtest dir> 
--parasofttest-install-dir <parasofttest dir> --target-location <eclipse dir> --configure=<localsettings file>

Sample localsettings File

Here is a sample localsettings file that configures Team Server and License for Jtest:

jtest.license.use_network=true
jtest.license.network.host=main1.parasoft.com.pl jtest.license.network.port=2222
jtest.license.network.edition=server_edition tcm.server.accountLogin=true
tcm.server.enabled=true
tcm.server.name=main1.parasoft.com.pl
tcm.server.password=test
tcm.server.port=18888
tcm.server.username=test
enforce.configure=true
  • No labels