This topic provides detailed information on installing ReadyAPI on headless machines.
For a typical installation process, see Installation Guide.
To learn how to install VirtServer, see VirtServer Installation.
To run ReadyAPI, your computer must meet certain system requirements.
Also, you will need either a ReadyAPI trial license or a commercial Pro license for one or for all ReadyAPI applications (SoapUI, LoadUI, ServiceV). A Pro license for one of the applications enables basic functionality of the other ones.
Before the first ReadyAPI run, you need to install a license.
For current ReadyAPI users:
If you have an active license of ReadyAPI, you do not need to activate a new license.
VirtServer requires a separate license.
Visit the ReadyAPI Downloads Centerand download the ReadyAPI Linux installer of the desired bitness. This package includes JDK, so you can use it on a machine without installed Java. To install ReadyAPI on a headless machine, follow the instructions below.
To download a package on a headless machine, you can use wget or a similar tool.
The following instruction describes the process of installing ReadyAPI on a headless machine. If you download a tarball archive, just unpack the downloaded file.
Make the downloaded file executable. For example:
chmod +x ./ReadyAPI-x64-3.0.0.sh
Run the installer with the
|Note:||On Windows computers, use the following command:
start /wait ReadyAPI-x64-3.0.0.exe -c
If ReadyAPI is already installed on your computer, you will be asked whether you want to update the current installation or to install the product anew to a different directory:
Enter the number corresponding to the needed option and press Enter.
|Note:||This topic explains how to install the product for the first time. If you update your current installation, the steps may be different.|
On the next page, select the installation mode:
Full installation – installs the default set of ReadyAPI components to the default folder. To choose this option, enter 1.
Custom installation – allows you to select the components you want to install and specify a different installation folder. To choose this option, enter 2.
Enter the needed option and press Enter.
If you select Custom installation, the wizard will contain two additional steps:
The wizard asks you for a folder where you want to install ReadyAPI. Enter the desired path and press Enter.
|Note:||The default path is shown in the square brackets. To use it, leave the input field empty and press Enter.|
Then, the wizard asks you which components should be installed.
ReadyAPI installer includes extra components that you may want to install if you need them. The components can also be added later by running the installer again.
|x: ReadyAPI||ReadyAPI itself.||You do not have to specify this item. It is installed by default.|
|2: Install JDBC Drivers||The JDBC drivers are needed to connect to databases.||If you need some other JDBC drivers, you need to install them manually.|
|3: Postgres JDBC Driver||The Postgres JDBC drivers are needed to connect to PostgreSQL databases.|
|4: Microsoft JDBC Driver for SQL Server||Microsoft JDBC drivers are needed to connect to SQL Server databases.|
|Note:||Enter an asterisk with a corresponding number to get more information about a component.|
Enter the list of numbers (separated with commas) which correspond to the desired components and press Enter.
|Tip:||Not to install additional components, enter a comma (“,”) and press Enter.|
On the next step, you can create symlinks. To skip this step, enter n. To create symlinks, enter y and then specify the desired directory, or leave it blank for the default path.
After the installation is complete, you can run ReadyAPI command-line tools to run tests:
Below is a short list of command-line parameters you can use to install ReadyAPI on a headless machine. For the complete list of parameters, see install4j help.
-h, -help, or /?: Displays the list of available command-line arguments.
-manual: Commands the installer to act as if no JRE has been found and displays the dialog where you can choose a JRE or download one if a JRE has been bundled dynamically. If you locate a JRE, it will be used for the installed application.
|You can apply this parameter to Microsoft Windows only.|
-c: Executes the installer in the console mode, that is, the interaction with the user is performed in the terminal from which the installer was invoked.
-q: Executes the installer in the unattended mode, that is, there is no interaction with the user and the installation is performed automatically with the default values.
-g: Executes the installer in the GUI mode.
|Tip:||Use this parameter if you configured the installer default execution mode as the console or unattended one.|
-console: Displays the installer output, if the installer is executed in the unattended mode and the
-console parameter is passed after the
|Tip:||Use this for debugging.|
-overwrite: Lets the installer overwrite the existing file. Only valid if
-q is set.
-wait [timeout in seconds]: Defines the time to wait before all installed launchers and installer applications, including the updater, shut down. If this does not happen before the timeout expires, the installer exits with an error message. Only valid if
-q is set.
-dir [directory]: Sets a custom installation directory (absolute or relative) for the unattended installation mode. If the directory is relative, it will be resolved relative to the media type. Only valid if
-q is set.
-splash [title]: Specifies the title of the window with a progress bar that will be shown during the installation in the unattended installation mode. Only valid if
-q is set.