13.3 Installing Sentinel as a Non-root User

If your organizational policy does not allow you to run the full installation of Sentinel as root, you can install Sentinel as a non-root user; that is, as the novell user. In this installation, a few steps are performed as a root user, then you proceed to install Sentinel as the novell user created by the root user. Finally, the root user completes the installation.

When installing Sentinel as a non-root user, you should install Sentinel as the novell user. Non-root installations other than the novell user is not supported, although the installation proceeds successfully.

Download the installation files from the Downloads website.
Specify the following command at the command line to extract the install files from the tar file:
```
tar -zxvf <install_filename>
```
Replace <install_filename> with the actual name of the install file.
Log in as root to the server where you want to install Sentinel as root.
Go to the directory where you have extracted the installer:
```
cd <directory_name>
```
Specify the following command:
```
./bin/root_install_prepare
```
A list of commands to be executed with root privileges is displayed. If you want the non-root user to install Sentinel in non-default location, specify the --location option along with the command. For example:
```
./bin/root_install_prepare --location=/foo
```
The value that you pass to the --location option foo is prepended to the directory paths.

This also creates a novell group and a novell user, if they do not already exist.
Accept the command list.

The displayed commands are executed.
(Conditional) If the given non-default directory location is already existing prior to Step 5, ensure that the novell user has ownership permissions to the directory. Run the following command to assign ownership permissions:
```
chown novell:novell <non-default installation directory>
```
Specify the following command to change to the newly created non-root user; that is, novell:

su novell

(Conditional) To do an interactive installation:

Specify the appropriate command depending on the component you are installing:

Component	Command
Sentinel server	Default location: ./install-sentinel Non-default location: ./install-sentinel --location=/foo
Collector Manager	Default location: ./install-cm Non-default location: ./install-cm --location=/foo
Correlation Engine	Default location: ./install-ce Non-default location: ./install-ce --location=/foo

Continue with Step 12.

(Conditional) To perform silent installation of Sentinel Server, ensure that you have recorded the installation parameters to a file. For information on creating the response file, see Sentinel Server Standard Installation or Sentinel Server Custom Installation.
1. To install, specify the following command:
  
  Default location: ./install-sentinel -u <response_filename>
  
  Non-default location: ./install-sentinel --location=/foo -u <response_filename>
2. Continue with Step 15.

(Conditional) To perform silent installation of Collector Manager or Correlation Engine, ensure that you have recorded the installation parameters to a file.

NOTE:Use the configuration file to connect Collector Manager and Correlation Engine to a different Sentinel server than the one recorded in the response file. Update this file with the relevant Sentinel server details and use it along with the response file during unattended installation.

For information on creating the response file or the configuration file, see Collector Manager and Correlation Engine Installation.

Specify the appropriate command depending on the component you are installing:

Component	Command
Collector Manager	To use the response file: Default location: ./install-cm -u <response_filename> Non-default location: ./install-cm --location=/foo -u <response_filename> To use the response file and the configuration file: Default location: ./install-cm -u <response_filename> -i <configuration_filename> Non-default location: ./install-cm --location=/foo -u <response_filename> -i <configuration_filename> The installation proceeds with the Sentinel server values from the configuration file and the other installation parameter values stored in the response file.
Correlation Engine	To use the response file: Default location: ./install-ce -u <response_filename> Non-default location: ./install-ce --location=/foo -u <response_filename> To use the response file and the configuration file: Default location: ./install-ce -u <response_filename> -i <configuration_filename> Non-default location: ./install-ce --location=/foo -u <response_filename> -i <configuration_filename> The installation proceeds with the Sentinel server values from the configuration file and the other installation parameter values stored in the response file.

Component

Command

Collector Manager

To use the response file:
- Default location: ./install-cm -u <response_filename>
- Non-default location: ./install-cm --location=/foo -u <response_filename>
To use the response file and the configuration file:
- Default location:
  
  ./install-cm -u <response_filename> -i <configuration_filename>
- Non-default location:
  
  ./install-cm --location=/foo -u <response_filename> -i <configuration_filename>
The installation proceeds with the Sentinel server values from the configuration file and the other installation parameter values stored in the response file.

Correlation Engine

To use the response file:
- Default location: ./install-ce -u <response_filename>
- Non-default location: ./install-ce --location=/foo -u <response_filename>
To use the response file and the configuration file:
- Default location:
  
  ./install-ce -u <response_filename> -i <configuration_filename>
- Non-default location:
  
  ./install-ce --location=/foo -u <response_filename> -i <configuration_filename>
The installation proceeds with the Sentinel server values from the configuration file and the other installation parameter values stored in the response file.

Continue with Step 15.

Specify the number for the language you want to use for the installation.

The end user license agreement is displayed in the selected language.
Read the end user license and enter yes or y to accept the license and continue with the installation.

The installation starts installing all RPM packages. This installation might take a few seconds to complete.
You are prompted to specify the mode of installation.
- If you select to proceed with the standard configuration, continue with Step 8 through Step 10 in Sentinel Server Standard Installation.
- If you select to proceed with the custom configuration, continue with Step 7 through Step 14 in Sentinel Server Custom Installation.
Log in as a root user and specify the following command to finish installation:
```
./bin/root_install_finish
```
The Sentinel installation finishes and the server starts. It might take few minutes for all services to start after installation because the system performs a one-time initialization. Wait until the installation finishes before you log in to the server.

To access the Sentinel Main interface, specify the following URL in your web browser:

https://IP_AddressOrDNS_Sentinel_server:8443/sentinel/views/main.html

Where IP_AddressOrDNS_Sentinel_server is the IP address or DNS name of the Sentinel server and 8443 is the default port for the Sentinel server.