3.3. Installation

3.3.1. Language Selection
3.3.2. Step 1: Welcome
3.3.3. Step 2: Information
3.3.4. Step 3: Licensing Agreements
3.3.5. Step 4: Target Path
3.3.6. Step 5: Select Installation Packages
3.3.7. Step 6: User Data
3.3.8. Step 7: Installation
3.3.9. Step 8: Perform External Processes
3.3.10. Step 9: Setup Shortcuts
3.3.11. Step 10: Installation Finished

Under Microsoft Windows the installer is invoked by running the binary Klaros-Testmanagement-<version>-Setup.exe.

Under Linux the installer can be started by running the binary Klaros-Testmanagement-<version>-Setup.bin in a user shell.

The following screens show each step involved in installing Klaros-Test­management.

3.3.1. Language Selection

Upon startup the installer is requesting the language used throughout the following installation procedure.

Currently both English and German languages are available.

Language Selection

Figure 3.1. Language Selection


3.3.2. Step 1: Welcome

The initial step shows a c to the user ( Figure 3.2).

The “Welcome” Screen

Figure 3.2. The Welcome Screen


The installation may be aborted by clicking the Quit button. Clicking Next proceeds with the installation.

3.3.3. Step 2: Information

The second step shows information about the product and the revision history, listing the fixed issues and the newly added features ( Figure 3.3).

The “Information” Screen

Figure 3.3. The Information Screen


The installation may be aborted by clicking the Quit button. Clicking Previous goes back to the Welcome step and clicking Next proceeds with the installation.

3.3.4. Step 3: Licensing Agreements

The third step shows information about the license agreement for Klaros-Test­management. The license must be accepted to continue the installation. ( Figure 3.4).

The “Licensing Agreement” Screen

Figure 3.4. The Licensing Agreement Screen


The installation may be aborted by clicking the Quit button. Clicking Previous goes back to the Information step and clicking Next proceeds with the installation.

3.3.5. Step 4: Target Path

The fourth step requests the target path where Klaros-Test­management will be installed. The user can use the Browse button to search for the specific path in the local file system ( Figure 3.5).

[Important] Install Folder Location

It is highly recommended using the suggested install location and not the Windows Programs folder. By default, Klaros-Test­management will not be able to start if installed there, as the Tomcat application server requires write access to the installation folder in order to deploy the web application. This is blocked by Microsoft Windows User Account Control (UAC).

If you wish to install Klaros-Test­management in this location, UAC must be disabled.

The “Target Path” Screen

Figure 3.5. The Target Path Screen


The installation may be aborted by clicking the Quit button. Clicking Previous goes back to the Licensing Agreement dialog and clicking Next proceeds with the installation.

3.3.6. Step 5: Select Installation Packages

The fifth step allows selecting optional packages that are installed with Klaros-Test­management.

The “Select Installation Packages” Screen

Figure 3.6. The Select Installation Packages Screen


The installation may be aborted by clicking the Quit button. Clicking Previous goes back to the Target Path dialog, clicking Next proceeds with the installation.

3.3.7. Step 6: User Data

In the sixth step the settings for the installed Tomcat application server can be changed.

The “User Data” Screen

Figure 3.7. The User Data Screen


It is possible to set the ports used by Tomcat (Server-Port and HTTP-Port), the minimum and maximum amount of memory available to the Tomcat process as well as the user name and password of the Tomcat application server administrator.

In addition it is possible to control the startup of the application during the installation. If the Launch Application Server checkmark is set, the application server will be launched automatically during the installation process. If the Launch Browser checkmark is set, a native web browser instance will be redirected to the application login page. Both of these actions will be performed during the Section 3.3.9, “Step 8: Perform External Processes” phase.

The installation may be aborted by clicking the Quit button. Clicking the Previous button goes back to the Select Installation Packages step and clicking Next button proceeds with the installation.

3.3.8. Step 7: Installation

The seventh step starts the installation of Klaros-Test­management and shows the installation progress. The following screenshots show the Installation in Progress Screen and the Installation finished screen ( Figure 3.8).

The “Installation in Progress” Screen

Figure 3.8. The Installation in Progress Screen


The “Installation Finished” Screen

Figure 3.9. The Installation Finished Screen


The installation may be aborted by clicking the Quit button. Clicking Next proceeds with the installation.

3.3.9. Step 8: Perform External Processes

The optional eighth step performs external processes such as setting the environment variables and starting the Tomcat application server.

The “Processes” Screen

Figure 3.10. The Processes Screen


The installation may be aborted by clicking the Quit button. Clicking Next proceeds with the installation.

3.3.10. Step 9: Setup Shortcuts

The ninth step allows to set the options for shortcuts. The installer can create shortcuts in the Start-Menu and on the desktop ( Figure 3.11).

The “Setup Shortcuts” Screen

Figure 3.11. The Setup Shortcuts Screen


This step looks different on Linux installations but has the same functionality.

The installation may be aborted by clicking the Quit button. Clicking Previous goes back to the Perform External Processes step and clicking Next proceeds with the installation.

3.3.11. Step 10: Installation Finished

The last step notifies the user that Klaros-Test­management was installed successfully and shows the path to the to the uninstall program ( Figure 3.12).

The “Installation Finished” Screen

Figure 3.12. The Installation Finished Screen


The Generate an automatic installation script button saves a complete script of the installation with the selected user choices, so that the same installation could be repeated unattended or on other machines.

The installation can be completed by clicking the Done button.