|Oracle® Real User Experience Insight Installation Guide
Release 6.5.0 for Linux x86-64
Part Number E17370-02
This chapter describes the procedure for installing the Apache Web server and RUEI software. The procedure for upgrading an existing RUEI 5.x installation to release 6.5 is described in Chapter 5, "Upgrading to RUEI 6.5". The post-installation configuration procedure is described in Chapter 6, "Configuring RUEI".
The RUEI software is available from the Oracle E-Delivery Web site (
http://edelivery.oracle.com). Select the following media pack criteria:
Oracle Enterprise Manager
Copy the downloaded RUEI zip file to
/root directory on the server, and unzip it. Use the following commands:
cd /root unzip package_name.zip
The following directories are created which contain the software needed to complete the RUEI installation:
All steps described in this section must be performed regardless of your planned installation (that is, a Reporter with local database, a Reporter with remote database, or a Collector).
/etc/ruei.conf file specifies the settings used within your installation. Note that all components in your RUEI environment (such as the remote database and Collectors) require the same global
/etc/ruei.conf configuration file. The settings shown in Table 4-1 are defined.
Table 4-1 RUEI Settings.
Home directory of the RUEI software.
Directory for RUEI data files.
The RUEI operating system user.
The RUEI operating system group.
The database instance name.
The database user name.
The database connect string.
Footnote 1 Be aware that all variables specified in this table are the values used throughout this guide, and can be modified as required.
Footnote 2 The directory name cannot exceed 50 characters in length.
Footnote 3 The database instance name cannot exceed 8 characters in length.
Footnote 4 The database user name cannot exceed 30 characters in length.
Footnote 5 The alias name cannot exceed 255 characters in length.
There is no need to change the settings for JAVA_HOME and INSTANTCLIENT_DIR if you intend to use the software contained on the RUEI distribution pack.
moniforce group and 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
An example of the configuration file is included in the RUEI distribution pack. Ensure the file is readable by the RUEI_USER user by issuing the following commands:
cp /root/RUEI/extra/ruei.conf /etc/ chmod 644 /etc/ruei.conf chown moniforce:moniforce /etc/ruei.conf
In case of a remote database installation, the
ruei.conf file needs to be identical with that of the Reporter system.
For both Reporter and Collector systems you need to install the Java Runtime Environment (JRE). Java is bundled within the RUEI distribution pack.
Issue the following commands:
cd /root/RUEI/Java chmod +x ./jre-1_5_0_21-linux-amd64-rpm.bin ./jre-1_5_0_21-linux-amd64-rpm.bin
Note you are prompted to accept the Java licence agreement. You cannot continue until you have done so.
This installs the necessary Java software in the directory
/usr/java/jre1.5.0_21. To make the install directory version independent, create a more generic symlink using the following command:
ln -s /usr/java/jre1.5.0_21 /usr/java/jre
This section can be skipped for Reporter or remote database servers.
Logon to the Collector system as the
root user, and do the following:
The RUEI file and directory locations are fixed. Therefore, it is necessary to use the exact directory name described below. Create the RUEI application root directory using the following command:
mkdir -p /opt/ruei chmod 750 /opt/ruei
Change to the RUEI root directory and run the
ruei-install.sh script using the following commands:
cd /root/RUEI/65 chmod +x ruei-install.sh ruei-check.sh ./ruei-install.sh collector
In addition to the actions described above, you need to configure the network interfaces. This is fully described in Configuring the Network Interface. Moreover, you also need to setup a password-less remote login from the Reporter system to the newly created Collector system. The necessary configuration steps are described in Configuring Reporter Communication (Split-Server Setup Only).
This section describes the procedure for installing the required components for a Reporter system. These include the Apache Web server, the Oracle database Instant Client, and the Zend Optimizer.
This section describes the installation and configuration of the Apache Web server, and the components that use it.
Ensure that the Web server starts automatically after re-boot by issuing the following command:
/sbin/chkconfig httpd on
/etc/sysconfig/httpd file to include the following line at the bottom of the file:
Create the following settings in the
session.gc_maxlifetime = 14400 memory_limit = 96M upload_max_filesize = 128M post_max_size = 128M
Install the Oracle database Instant Client and SQLplus extension with the following commands as the
cd /root/RUEI/IC rpm -Uhv oracle-instantclient11.1-basic-*.rpm rpm -Uhv oracle-instantclient11.1-sqlplus-*.rpm
php-oci8 module (this is part of the RUEI distribution set) using the following commands:
cd /root/RUEI/PHP rpm -Uhv php-oci8-11gR1-*
Go to the directory containing the Zend Optimizer code, unpack the tar file, and run the Zend optimizer installer. Read the license agreement. You will not be able to proceed until you have accepted the license terms. Accept all default settings, and allow the installer to restart the Apache Web server. Issue the following commands:
cd /root/RUEI/ZendOptimizer tar zxvf ZendOptimizer-3.3.3-linux-glibc23-x86_64.tar.gz cd ZendOptimizer-3.3.3-linux-glibc23-x86_64 ./install
Note:If you upgrade your system packages (for example, using Yum), this can overwrite changes you previously made to the
/etc/php.inifile. Therefore, you should be prepared to re-install the Zend Optimizer. When doing so, ensure the Zend Optimizer installer indicates the location of the
It is recommended you move the Zend configuration lines created in the
/etc/php.ini file to the RUEI-specific PHP configuration file
/etc/php.d/ruei.ini to prevent upgrade issues. If you performed a default installation of the Zend Optimizer, this involves moving the following lines:
[Zend] zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-3.3.3 zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-3.3.3 zend_optimizer.version=3.3.3 zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so
The RUEI 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.
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.
ruei-check.sh: 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. A complete description of the script, refer to Appendix A, "The ruei-check.sh Script".
The four "connection data" files created during the procedure described in this section are as follows:
The RUEI configuration file (
/etc/ruei.conf) also needs to be present on the database server and configured as described in The RUEI Configuration File.
Do the following:
ruei-check.sh scripts to the server on which you intend to run the database instance, and make them executable for the
oracle user. These scripts can be found in the RUEI distribution zip (
Review the settings in the
/etc/ruei.conf file to match your needs as described in The RUEI Configuration File.
Logon 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 RUEI database user passwordFoot 1 . This enables the RUEI application to login to the database automatically. The script also creates the "connection data" files for you now.
If you run the
ruei-prepare-db.sh script for a combined Reporter/Database server, all files are placed automatically in the correct locationFoot 2 . In case of a remote database, a separate .
tar file is generated, and you will need to perform the extra step 4.
Issue the following commands:
chmod +x ruei-prepare-db.sh ruei-check.sh export ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1 ./ruei-prepare-db.sh
If you ran the above commands on a combined Reporter/Database server you can skip step 4 and proceed to step 5.
This step only applies when using a remote database.
In the 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 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. Logon 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
Because logging of the database can consume a large amount of disk space, it is recommended 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 via
cron using 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'
The RUEI directory locations are flexible. Therefore, it is necessary to use the exact directory name described as configured in the
/etc/ruei.conf file. Create the RUEI application root directory using the following command:
mkdir -p /opt/ruei chmod 750 /opt/ruei
Note:The specified RUEI_HOME and RUEI_DATA directories must have 750 permissions defined for them.
moniforce members of two additional groups using the following commands:
/usr/sbin/usermod -aG moniforce apache /usr/sbin/usermod -aG uucp apache /usr/sbin/usermod -aG uucp moniforce
Go to the directory which holds the RUEI software, and install the RUEI packages. You can specify
collector to the
ruei-install.sh script depending on the required installation:
cd /root/RUEI/65 chmod +x ruei-install.sh ./ruei-install.sh reporter
Re-start the Apache Web server using the following command:
/sbin/service httpd restart
Verify that the RUEI software was correctly installed by issuing the following command:
su - moniforce set-admin-password
You are prompted to enter and confirm the password.
Note:When defining the
adminuser password, bear the following in mind:
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.
This section is only relevant to Reporter and Collector systems.
Make the monitoring network interface up status permanent (after a reboot) by setting the ONBOOT parameter of the capturing interfaces to yes in the interface configuration files. The network interfaces configuration can be found in
X represents the necessary network interface). Alternatively, use the graphical utility system-config-network to set the appropriate interfaces to "activate device when computer starts".
This section is only relevant to the Reporter system.
For PDF generation with multibyte character content, additional fonts need to be enabled. These fonts need to be made available to Java. Use the following command to copy (or move) the RUEI-installed fonts to the appropriate Java directory:
cp /opt/ruei/gui/include/bi_publisher/fonts/* \ /usr/java/jre/lib/fonts/
This section is only relevant to the Reporter system.
RUEI assumes a working local MTA for sending PDF reports and E-mail alerts. By default, Enterprise Linux uses the Sendmail MTA. By default, Sendmail will deliver the E-mail directly to the destination MTA. If this behavior is not according to your needs or policies, sending mail via a SmartHost (relay) might be an alternative. To configure a SmartHost in Sendmail, do the following:
Install the Sendmail configuration utility by issuing the following command:
rpm -Uhv sendmail-cf-8.13.8-*.el5.x86_64.rpm
Find the line which contains the Smart Host setting in
/etc/mail/sendmail.mc. Modify the SMART_HOST setting to your needs. For example:
Generate the new configuration into a new
sendmail.cf by executing the following command:
make -C /etc/mail
Restart Sendmail. For example:
Note:Extensive information about the configuration of the Sendmail MTA is available at
You can download the RUEI MIB definition file through the Reporter interface. This definition file can be added to the SNMP manager. The procedure for downloading the MIB file is described in the Oracle Real User Experience Insight User's Guide.
This section is only relevant to Reporter systems.
To have the browser automatically redirected to the correct RUEI path, create the file
/var/www/html/index.html with the following content:
<head> <meta http-equiv="REFRESH" content="0;URL=/ruei/"> </head>
This section is only relevant to a Reporter system with remote Collector(s).
A password-less SSH connection must be setup between the
Moniforce user from the Reporter system to each Collector system. Do the following:
Logon to the Reporter server as root. Issue the following commands:
su - moniforcessh-keygen -P ""
Press Enter to accept the defaults.
root on each of the Collector systems. Issue the following commands:
su - moniforcecd ~/.sshssh root@Reporter cat /var/opt/ruei/.ssh/id_rsa.pub >> authorized_keys
(you will need to specify the Reporter system root password)
chmod 600 authorized_keys
Check that it is now possible to execute a remote command (as
moniforce user) on the Reporter system without using a password. For example:
root on the Reporter server.
su - moniforce.
Execute a remote pwd command:
Enter yes to the question "Are you sure you want to continue connecting (yes/no)?".
The command should return
The above steps must be performed for each Collector!
Note:If the connection between the Reporter and the Collector(s) has not been correctly configured, you will receive an authorization error when you try to register the remote Collector.
On completion of the Initial Setup Wizard (described in Performing Initial RUEI Configuration), you can verify your installation by selecting System, the Status. All system indicators should report OK. Note Status notification will indicate "Unknown" because no system alerts have yet been configured. This is fully described in the Oracle Real User Experience Insight User's Guide.
Footnote LegendFootnote 1: The database password is also used as the Oracle wallet password. Both passwords must be between 8 and 30 characters in length, and contain both numbers and letters. For information on changing the Oracle wallet password, please consult the appropriate Oracle documentation.