For an introduction to RUEI data collection, see Data Collection. The following installation data collection options are available:

• Network data collector: This option collects data that passes through the network and was the default option in previous releases and requires either a local or remote collector.

• Tag data collector: This option, also called tag based monitoring, collects data by monitoring the request and processing of a specific web URL (the tag) which is inserted into all pages.

Depending on the installation location of the Reporter database and the RUEI software, the necessary disk space needs to be carefully planned. During operating system installation, you will need this information at hand for the disk partitioning phase.

The following table shows the disk space requirements for the RUEI installation components.

This means that for a stand-alone RUEI server installation, a minimum of 1005 GB is required.

If you want to use network data collection:

1. Ensure that a static IP address is assigned to the interface used to access the RUEI web interface. In addition, the assigned IP address and host name should be configured in the /etc/hosts file. If necessary, ensure that all Reporter and Collector systems are correctly defined in the DNS system.

2. Ensure that the network interface(s) used for network packet monitoring are administratively up, but without an IP address.

   Note:

   Make the network interface up status permanent (after a reboot) by setting the ONBOOT parameter of the capturing interfaces to yes. The network interfaces configuration can be found in the /etc/sysconfig/network-scripts/ifcfg-ethX file (where X represents the necessary network interface). Alternatively, use the graphical utility system-config-network to perform the above actions.

When the system boots for the first time, a post-installation wizard appears, and allows you to finalize the operating system configuration settings.

You must ensure that Security Enhanced Linux (SELinux) is disabled. To disable SELinux set SELINUX=disabled in the /etc/selinux/config file. This is necessary for the correct operation of RUEI. Changing the SELinux setting requires rebooting the system so that the entire system can be re-labelled.

Please configure the operating system's firewall, if enabled, to allow access to the respective services, like (by default) TCP port 1521 for the database listener TCP port 443 for the web interface and TCP port 22 for the SSH server.

For security reasons, it is recommended that you select the Encrypt System check box during operating system installation so that all sensitive data is stored in a secure manner. A passphrase is required during booting the system.

Ensure that the date and time settings are correctly specified. The use of NTP is recommended and is required in a split-server deployment. In addition, all time zones specified for Reporter and Collector systems must be identical.

The procedure described in this section is only required for a Reporter system. The procedure depends on whether you are using RedHat Enterprise/Oracle Linux 7.x, 8.x or 9.x.

Download and install Oracle Database Enterprise Edition from the Oracle database software downloads page at the following location:

https://www.oracle.com/database/technologies/oracle-database-software-downloads.html

The procedure for installing the Oracle database is fully described in the product documentation. It is available from the Oracle Database Documentation Library. The path user and group names used in this guide are based on the Oracle database product documentation.

The /etc/ruei.conf file specifies the settings used within your installation. A template of this file is provided in the /root/ruei/extra directory of the RUEI distribution zip. All components in your RUEI environment (such as the remote database and Collectors) require the same global /etc/ruei.conf configuration file.

RUEI_BASE=/my/ruei/dir
export RUEI_HOME=$RUEI_BASE/home

cp /root/ruei/extra/ruei.conf /etc/

In case of a remote Reporter database installation, the ruei.conf file needs to be identical to that of the Reporter system.

1. Create the moniforce group and RUEI_USER user. The home directory of moniforce should be set to /var/opt/ruei, with read permissions for group members.

   /usr/sbin/groupadd moniforce
   /usr/sbin/useradd moniforce -g moniforce -d /var/opt/ruei
   chmod -R 750 /var/opt/ruei
   chown -R moniforce:moniforce /var/opt/ruei
   

   Note:

   The login shell for the moniforce (RUEI_USER) user must be set to /bin/bash.

2. The RUEI directory locations are flexible, however it is necessary to use the exact directory name described as configured in the /etc/ruei.conf file. Create the RUEI application root directory running the following commands:

   mkdir -p /opt/ruei
   chmod 755 /opt/ruei

   Note:

   The specified $RUEI_HOME and $RUEI_DATA directories must have 755 permissions defined for them. For more information on these directories, see Table 2-3 .

3. Ensure the file is readable by the RUEI_USER user by issuing the following commands:

   chmod 644 /etc/ruei.conf
   chown moniforce:moniforce /etc/ruei.conf
   

For Reporter and Collector systems, you need to install the Java Runtime Environment (JRE) version 8. Please download a 64 bit (x64) Linux version from https://www.java.com/en/download/linux_manual.jsp

The installation instructions below (and default value of JAVA_HOME in /etc/ruei.conf) are based on the non-RPM (.tar.gz) version

1. Run the following commands:

   mkdir -p /usr/java
   chmod 755 /usr/java
   cd /usr/java
   tar xzf <path-of-download>/jre-8u*-linux-x64.tar.gz
   

2. This installs the necessary Java software in the directory/usr/java/jre1.8.0_<version>. To make the install directory version independent, create a more generic symlink running the following command:

   ln -s /usr/java/jre1.8.0_* /usr/java/jre

To verify if the system is ready for RUEI to be installed, it is advised to run the RUEI system check.

This section describes the installation and configuration of the Apache web server, and the components that use it.

Download the Oracle Database Instant Client (Basic) and SQL*Plus (version 19.x and above) package from Oracle Instant Client Downloads for Linux x86-64 (64-bit), and install by running the following commands as the root user:

cd /root/ruei/ic
rpm -Uhv oracle-instantclient*-basic-*.rpm
rpm -Uhv oracle-instantclient*-sqlplus-*.rpm

As a prerequisite download and install the Oracle database Instant Client SDK (devel) package for your version of PHP, based on your yum, for your version of Instant Client from Oracle Instant Client Downloads for Linux x86-64 (64-bit).

You can find detailed installation instructions for the php-oci8 module at https://www.php.net/manual/en/oci8.installation.php

Example commands:

1. Install the Oracle database Instant Client SDK (devel) package:

   yum install php-pear php-devel 
   yum install <path-of-download>/oracle-instantclient-devel-*.x86_64.rpm

2. pear config-set http_proxy <url_of_proxy>:<port> 

   Note:

   This step is optional, if a proxy is needed for internet access.

3. pecl install oci8-<version>

   Note:

   When prompted for a path to the library, you can choose the default of autodetect.

4. Create a file named /etc/php.d/oci8.ini and add the following to it:

   #enable oci8 extension module
   extension=oci8.so

5. Restart httpd:

   systemctl restart httpd

   Note:

   If your OS is RedHat Enterprise / Oracle version 9.x, also restart php-fpm:

   systemctl restart php-fpm

The procedure described in this section should be skipped if you are installing a secondary (failover) Reporter system (see Configuring a Failover Reporter System), and you should continue at Installing the Reporter Software.

The Reporter database can reside either locally (that is, on the Reporter server) or on a remote database server. In this section you will create the database instance required for RUEI, and generate the "connection data" required for the Reporter to connect to this database instance. As an alternative for the database setup described in this chapter, you can follow the procedure described in Generic Database Instance Setup.

If you are using a remote database and you do not have command-line access to the remote database server because, for example, you want to configure RUEI using a “Pluggable Database", see Setting up RUEI Against a Remote Database Service.

You will need the following scripts to be present on the system where the database instance (RUEI_DB_INST) will be created:

• ruei-prepare-db.sh: creates the database instance, Oracle wallet, and database connect files. This script will only run on Linux. If you are installing the Oracle database on a different operating system, see Generic Database Instance Setup.

• sql_scripts: this directory contains a number of SQL scripts that are called by the ruei-prepare-db.sh script.

• db_templates: this directory contains templates for the RUEI database instance that is created by the ruei-prepare-db.sh script.

• ruei-check.sh: this is a hardware and environment check utility, and is automatically invoked by ruei-prepare-db.sh. The script can also be used as a stand-alone troubleshooting utility. For a complete description of the script, refer to RUEI System Check Tool.

For creating the database autologin wallet in this section and, optionally, for the integration with Enterprise Manager later on, a specific version of the "mkstore" utility is needed. You can set up this utility as follows. This needs to be done on the system where the database instance (RUEI_DB_INST) will be created as well as the reporter if those are separate systems.

• Run the following commands:

  cd /usr/local
  tar xzf /root/ruei/mkstore/mkstore-11.2.0.4.0.tar.gz

• This installs the mkstore utility to /usr/local/mkstore-11.2.0.4.0. To make the install directory version independent, create a more generic symlink using the following command:

  ln -s /usr/local/mkstore-11.2.0.4.0 /usr/local/mkstore

• Make the following change to /etc/ruei.conf:

  * export MKSTORE_BIN=/usr/local/mkstore/mkstore

• If you are executing these steps on a database server separate from the reporter system, make the following change to /etc/ruei.conf:

  * export JAVA_HOME=$ORACLE_HOME/jdk/jre

The four connection data files created during the procedure described in this section are as follows:

• cwallet.sso

• ewallet.p12

• sqlnet.ora

• tnsnames.ora

The RUEI configuration file (/etc/ruei.conf) also needs to be present on the database server and configured as described in Check The RUEI Configuration File and the instructions for setting up mkstore, given earlier in this section.

Do the following:

1. Copy the ruei-prepare-db.sh and ruei-check.sh scripts, and the sql_scripts and db_templates directories to the server on which you intend to run the database instance, and make them executable for the oracle user. These scripts and directories can be found in the RUEI distribution zip (/root/ruei/).

2. Review the settings in the /etc/ruei.conf file to match your needs as described in Check The RUEI Configuration File. If you want to use different names for the configuration and statistics tablespaces make sure these names are set before continuing. The same tablespace names must be used on the RUEI reporter and on the remote database.

3. Log in to the database server as the oracle user on the database server, and set the ORACLE_HOME environment variable. You need to run the ruei-prepare-db.sh script as the oracle user. This script creates the $RUEI_DB_INST database, but only after a number of hardware and software environment checks have been performed. The actual checks performed depend on the system type you are currently installing.

   The script prompts you for the Reporter database user password.

   Note:

   The database password is also used as the Oracle wallet password. Both passwords must be 8-30 characters in length, and contain both numbers and letters. For information on changing the Oracle wallet password, please consult the appropriate Oracle documentation.

   . This enables the RUEI application to login to the database automatically. The script also creates the "connection data" files for you now.

   The script also prompts you for a default tablespace name to be used for this installation, and then creates the connection data files.

   Run the following commands:

   chmod +x ruei-prepare-db.sh ruei-check.sh
   chmod -R +r /home/oracle/sql_scripts/
   chmod -R +r /home/oracle/db_templates/
   export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
        Note: This line requires customization based on your database version and installation path.
   ./ruei-prepare-db.sh create
   

   You are prompted whether you want the installation script to check your system. It is recommended that you do so. The checks performed are fully described in RUEI System Check Tool.

   If you ran the above commands on a combined Reporter/Database server, you can skip step 4 and proceed to step 5.

4. This step only applies when using a remote database.

   In case of a Reporter system using a remote database, you will need to copy the generated /tmp/ruei-database-configuration.tar file in step 3 from the database server to the Reporter system. The /tmp/ruei-database-configuration.tar file must be extracted on the Reporter server in the directory /var/opt/ruei (RUEI_DATA). The permissions of the files need to be set so that the specified RUEI_USER (moniforce) can use them.

   Copy the generated .tar file, which holds connection data files to the Reporter system. Log in to the Reporter server and extract the .tar file using the following commands:

   cd /var/opt/ruei
   tar xvf path-to-tar-file/ruei/database-configuration.tar
   chown moniforce:moniforce cwallet.sso ewallet.p12 sqlnet.ora tnsnames.ora
   

5. Because logging of the database can consume a large amount of disk space, it is recommended that you install a clean-up script to avoid the usage of unnecessary disk space. Copy the (example) script to the oracle user directory and activate it through cron running the following commands:

   mkdir -p /home/oracle/bin
   cp /root/ruei/extra/ruei-clean.sh /home/oracle/bin
   chmod +x /home/oracle/bin/ruei-clean.sh
   su - oracle -c 'echo "10 0 * * * /home/oracle/bin/ruei-clean.sh" | crontab'

To validate the Database Instance creation, run the RUEI post-installation check using the following commands:

For Reporter with local Database or a Single Server system:

cd /root/ruei/
 ./ruei-check.sh database post-install --role reporter

For a Database server system:

cd /root/ruei/
./ruei-check.sh database post-install --role database

The procedure described in this section is relevant to all configurations described in Scaling Scenarios and Planning the Software Installation. Installing the reporter software also installs the collector and processor software.

1. Make the apache and moniforce members of two additional groups running the following commands:

   /usr/sbin/usermod -aG moniforce apache
   /usr/sbin/usermod -aG dialout apache
   /usr/sbin/usermod -aG dialout moniforce

2. Go to the directory that holds the RUEI software, and run the following commands:

   cd /root/ruei
   chmod +x ruei-install.sh
   

3. Use one of the following options to run the pre installation check and install the reporter software:

   • If you are installing a reporter in a split server configuration or you want to use only network based data collection as described in Planning the Software Installation:

     ./ruei-check.sh reporter pre-install
     ./ruei-install.sh reporter
     

     Note:

     Investigate and fix any issues reported by the per installation check, before continuing with the RUEI reporter software installation.

   • If you are installing on a single server and you want to use tag based data collection as described in Planning the Software Installation (This option also supports network based data collection):

     ./ruei-check.sh reporter,tag-server pre-install
     ./ruei-install.sh reporter-tag
     

     Note:

     Investigate and fix any issues reported by the per installation check, before continuing with the RUEI reporter software installation.

   For information on monitoring an application based on tagging, see Defining Applications in the Identifying and Reporting Web Pages chapter of the RUEI Users Guide.

4. Re-start the Apache web server running the following command:

   For Linux 7.x/8.x

   /bin/systemctl restart httpd.service

5. As the root user, add the following lines to the .bash_profile file of the RUEI_USER (RUEI_DATA/.bash_profile):

   source /etc/ruei.conf
   source $RUEI_HOME/bin/env.sh
   

6. Verify that the RUEI software was correctly installed:

   • If you are installing a reporter in a split server configuration or you want to use only network based data collection as described in Planning the Software Installation:

     ./ruei-check.sh reporter post-install

   • If you are installing a reporter in a split server configuration or you want to use only tag based data collection as described in Planning the Software Installation:

     ./ruei-check.sh reporter,tag-server post-install

7. This step should not be performed if you are installing a secondary (failover) Reporter system (see Configuring a Failover Reporter System). You should continue at Configuring the Network Interface.

   As the moniforce user, set the RUEI admin user password to enable logging onto the RUEI interface running the following commands:

   su - moniforce
   set-admin-password
   

   You are prompted to enter and confirm the password.

• The password must have at least eight characters, and contain at least one non-alphanumeric character (such as $, @, &, and !).

• The initial password must be changed within seven days.

• The user name and password are case sensitive.