Install the Server in Non-interactive Mode on a Linux-based Operating System

Update the Default Parameters to Use for Non-interactive Mode

A non-interactive installation uses a set of default installation settings to silently install the server. If you want to run a non-interactive installation, you might want to update the default installation settings first. To create a parameters file that the installation process will use, run the installer script with the option -d.This file is the equivalent of an "answer file" in a non-interactive Windows installation.

Using the -d option lets you create a parameters file without going through the full installation process.

To update the default parameters to use for non-interactive mode, follow these steps:

  1. Run the Acrolinx installer script with the -d option.



    $ cd <INSTALL_DIR> $ bash ./ -d

    The script will try to determine the appropriate settings for your environment and create a parameters file in your installation directory.

  2. Change the installation parameters by following these steps:

    1. Open the installer parameters file.

    2. Update the relevant installation parameters and save the file.

When you run the installer script in non-interactive mode, the server is installed according to your updated parameters.

Running the Installer Script in Non-interactive Mode

You can use the -batch option to start the server installation in non-interactive mode. When the installation runs in non-interactive mode, you won't be prompted to confirm any installation actions. The installer script uses the default installation parameters instead. If you want to fully automate the server installation, you might find non-interactive mode useful.

To run the installer script in non-interactive mode, follow these steps:

In a command shell, navigate to the installation directory and run the installation script with the -batch option.



$ cd <INSTALL_DIR> $ bash ./ -batch
Remember: The installer script runs silently except when an unsupported Java version is detected. In this case, it will wait for you to confirm that it should continue anyway. To ensure that the installation process silently continues even when an unsupported Java version is detected, run the installer script with the -force option like this:
$ bash ./ -batch -force

Before the server is operational, you'll still need to install the guidance package files to your new installation.

If you're upgrading your server, you'll need to copy your updated guidance package files to your new installation. Use the installation update checklist as guide on what files to copy and follow the guidance package update procedure.