| Oracle® Real User Experience Insight Installation Guide 11g Release 1 for Linux x86-64 Part Number E22308-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Real User Experience Insight Installation Guide 11g Release 1 for Linux x86-64 Part Number E22308-03 |
|
|
PDF · Mobi · ePub |
This chapter describes the procedure and prerequisites for installing the Apache Web server and RUEI software. The procedure for upgrading an existing RUEI 6.x installation to release 11.1 is described in Chapter 3, "Upgrading to RUEI 11.1". The post-installation configuration procedure is described in Chapter 4, "Configuring RUEI".
This section describes the steps that should be taken before starting to install the RUEI software. Ensure that all preconditions described in this section should be meet before proceeding with the installation process.
Depending on installation location of the 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 during the disk partitioning phase.
Table 2-1 shows the disk space requirements for the RUEI installation components.
Table 2-1 Required Disk Space Specifications
| Partition | Minimum Required Disk Space (GB) | Component |
|---|---|---|
|
ORACLE_BASE (default |
300 |
Database server |
|
RUEI_HOME (default |
1 |
Reporter, Collector |
|
RUEI_DATA (default |
100 |
Reporter, Collector |
Footnote 1 This is the example location of the database used throughout this guide.
This means that for a stand-alone RUEI server installation, a minimum of 400 GB is required. In the case of a high-traffic implementation, involving a dedicated remote Collector, a minimum of 200 GB of disk space is recommended for /var/opt/ruei (RUEI_DATA).
Important:
The Reporter and database servers require high performance data storage. RAID-10 or RAID-5 (or equivalent) storage configurations with high performance disks are strongly recommended.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.
Ensure that the network interface(s) used for network packet monitoring are administratively up, but without an IP address.
Important:
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
/etc/sysconfig/networking/devices/ifcfg-ethX (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. Ensure that:
Ensure that the RUEI firewall rules shown in Table 1-7 are correctly configured.
Security Enhanced Linux (SELinux) is disabled. This is necessary for the correct operation of RUEI. Note that changing the SELinux setting requires rebooting the system so that the entire system can be relabeled.
For security reasons, it is strongly recommended you check the Encrypt System check box during operating system installation so that all sensitive data is stored in a secure manner. A passphase is required during booting the system.
Ensure that the date and time settings are correctly specified. The use of NTP is strongly recommended, and is required in a split-server deployment. In addition, all time zones specified for Reporter and Collector systems must be identical.
Because the NTP daemon is a critical component of RUEI, especially in a split Reporter-Collector configuration, it is recommended that you verify that it is activated in at least run level 5 during boot. Use the following commands:
chkconfig --list | grep ntp ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off chkconfig ntpd on chkconfig --list | grep ntp ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off /etc/init.d/ntpd start Starting ntpd: [ OK ]
Note that if the NTP daemon is not already running, you can start it with the command
/etc/init.d/ntpd restart
The following sample output show when the NTP daemon is synchronized (indicated by an "*").
ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
*194.171.167.130 .PPS. 1 u 994 1024 377 6.429 0.041 0.093
+80.85.129.25 130.235.20.3 3 u 725 1024 377 4.435 0.673 0.129
+82.94.235.106 135.81.191.59 2 u 678 1024 377 1.709 1.774 0.020
127.127.1.0 .LOCL. 10 l 8 64 377 0.000 0.000 0.001
Important:
In distributed environments, all time zones specified for Reporter and Collector systems must be identical.Note that the procedure described in this section is only required for a Reporter system.
The required packages are available from the Oracle Linux or RedHat Enterprise Linux distribution sets. Issue the following command to install all prerequisites for the Reporter:
rpm -Uhv httpd-2.2.3-*.el5.x86_64.rpm \ apr-1.2.7-11.*.x86_64.rpm \ apr-util-1.2.7-*.x86_64.rpm \ php-5.1.6-*.x86_64.rpm \ mod_ssl-2.2.3-*.el5.x86_64.rpm \ distcache-1.4.5-*.x86_64.rpm \ php-common-5.1.6-*.x86_64.rpm \ php-cli-5.1.6-*.x86_64.rpm \ php-mbstring-5.1.6-*.x86_64.rpm \ php-ldap-5.1.6-*.x86_64.rpm \ gmp-4.1.4-*.el5.x86_64.rpm \ postgresql-libs-8.1.11-*.el5_1.1.x86_64.rpm \ lm_sensors-2.10.7-*.el5.x86_64.rpm \ net-snmp-5.3.2.2-*.el5.x86_64.rpm \ net-snmp-utils-5.3.2.2-*.el5.x86_64.rpm \ perl-XML-Twig-3.26-*.fc6.noarch.rpm \ perl-XML-Parser-2.34-*.x86_64.rpm
Issue the following the commands to install all optional fonts. Alternatively, install the multi-byte character sets necessary to meet your NLS requirements.
rpm -Uhv fonts-*
As an alternative to manual installation, you can use a Yum repository to install the required RPMs. This requires a working Yum repository. For information on Yum repositories, see http://linux.duke.edu/projects/yum/. Install the necessary Oracle database packages using the following commands:
yum -y install gcc yum -y install gcc-c++ yum -y install compat-libstdc++-33 yum -y install libstdc++-devel yum -y install elfutils-libelf-devel yum -y install glibc-devel yum -y install libaio-devel yum -y install sysstat
Install the necessary Reporter packages using the following commands:
yum -y install perl-URI yum -y install perl-XML-Twig yum -y install net-snmp-utils yum -y install sendmail-cf yum -y install httpd yum -y install mod_ssl yum -y install php yum -y install php-mbstring yum -y install php-ldap yum -y install bitstream-vera-fonts yum -y install librsvg2 yum -y install xorg-x11-xinit yum -y install fonts-*
Download and install Oracle Database 11g EnterpriseF Edition from the Oracle database home page at the following location:
http://www.oracle.com/technology/software/products/database/index.html
The procedure for installing the Oracle database is fully described in the product documentation. It is strongly recommended that you download and review the appropriate Oracle Database 11g Quick Installation Guide. It is available from the Oracle Database Documentation Library.
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
Linux x86-64
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:
/root/RUEI/111
/root/RUEI/ZendOptimizer
/root/RUEI/IC
/root/RUEI/PHP
/root/RUEI/Java
/root/RUEI/extra
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).
The /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 2-2 are defined.
Table 2-2 RUEI Configuration Settings
| Setting | Description | ValueFoot 1 |
|---|---|---|
|
RUEI_HOMEFootref 2 |
Home directory of the RUEI software. |
|
|
RUEI_DATAFoot 2 |
Directory for RUEI data files. |
|
|
RUEI_USER |
The RUEI operating system user. |
|
|
RUEI_GROUP |
The RUEI operating system group. |
|
|
RUEI_DB_INSTFoot 3 |
The database instance name. |
|
|
RUEI_DB_USERFoot 4 |
The database user name. |
|
|
RUEI_DB_TNSNAMEFoot 5 |
The database connect string. |
|
|
RUEI_DB_TNSNAME_BIFootref 4 |
The export 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.
Failover Reporter Configuration Settings
Table 2-3 shows the settings that are used to configure a failover Reporter, and are only relevant to Reporter systems. See Chapter 7, "Configuring a Failover Reporter System" for information on the configuration procedure.
Table 2-3 RUEI Failover Reporter Configuration Settings
| Setting | Description |
|---|---|
|
RUEI_REP_FAILOVER_PRIMARY_IP |
The primary Reporter IP address. |
|
RUEI_REP_FAILOVER_STANDBY_IP |
The secondary Reporter IP address. |
|
RUEI_REP_FAILOVER_VIRTUAL_IP |
The virtual Reporter IP address. |
|
RUEI_REP_FAILOVER_VIRTUAL_DEV |
The network interface used to connect to the virtual Reporter IP address. |
|
RUEI_REP_FAILOVER_VIRUAL_MASK |
The network mask of the virtual Reporter IP address. |
Failover Collector Configuration Settings
Table 2-4 shows the settings that are used to configure a failover Collector, and are only relevant to Collector systems. See Chapter 8, "Configuring a Failover Collector System" for information on the configuration procedure.
Table 2-4 RUEI Failover Collector Configuration Settings
| Settings | Description |
|---|---|
|
RUEI_COL_FAILOVER_PRIMARY_IP |
The primary Collector IP address. |
|
RUEI_COL_FAILOVER_STANDBY_IP |
The secondary Collector IP address. |
|
RUEI_COL_FAILOVER_VIRTUAL_IP |
The virtual Collector IP address. |
|
RUEI_COL_FAILOVER_VIRTUAL_DEV |
The network interface used to connect to the virtual Collector IP address. |
|
RUEI_COL_FAILOVER_VIRTUAL_MASK |
The network mask of the virtual Reporter IP address. |
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.
Create the 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_22-linux-amd64-rpm.bin ./jre-1_5_0_22-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_22. To make the install directory version independent, create a more generic symlink using the following command:
ln -s /usr/java/jre1.5.0_22 /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/11.1 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
Edit the /etc/sysconfig/httpd file to include the following line at the bottom of the file:
source /etc/ruei.conf
Create the following settings in the /etc/php.d/ruei.ini file:
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 root user:
cd /root/RUEI/IC rpm -Uhv oracle-instantclient11.2-basic-*.rpm rpm -Uhv oracle-instantclient11.2-sqlplus-*.rpm
Install the php-oci8 module (this is part of the RUEI distribution set) using the following commands:
cd /root/RUEI/PHP rpm -Uhv php-oci8-11gR2-*
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.ini file. Therefore, you should be prepared to re-install the Zend Optimizer. When doing so, ensure the Zend Optimizer installer indicates the location of the php.ini file as /etc/php.ini and not /usr/local/Zend/etc/php.ini.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 PHP 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 procedure described in this section should be skipped if you are installing a secondary (failover) Reporter system (see Chapter 7, "Configuring a Failover Reporter System"), and you should continue at Installation of the Reporter Software.
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. As an alternative for the database setup described in this chapter, you can follow the procedure described in Appendix A, "Generic Database Instance Setup".
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: 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 Appendix C, "The ruei-check.sh Script".
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 The RUEI Configuration File.
Do the following:
Copy the ruei-prepare-db.sh and 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 (/root/RUEI/111).
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_1Foot 3 ./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 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. 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 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 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.Make the apache and 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 reporter or collector to the ruei-install.sh script depending on the required installation:
cd /root/RUEI/111 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:
./ruei-check.sh postinstall
This step should not be performed if you are installing a secondary (failover) Reporter system (see Chapter 7, "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 with the following commands:
su - moniforce set-admin-password
You are prompted to enter and confirm the password.
Note:
When defining theadmin user 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 /etc/sysconfig/network-scripts/ifcfg-ethX (where 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 RUEI_HOME/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, 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 going to the directory containing the uploaded RPM and 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:
define('SMART_HOST', 'my.example')dnl
Generate the new configuration into a new sendmail.cf by executing the following command:
make -C /etc/mail
Restart Sendmail. For example:
/etc/init.d/sendmail restart
Note:
Extensive information about the configuration of the Sendmail MTA is available athttp://www.sendmail.org.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.
Logon as root to each of the Collector systems and become the moniforce user by issuing the following command:
su - moniforce
Create the .ssh directory (if it does not already exist) for the moniforce user on each Collector system by issuing the following commands:
mkdir ~/.ssh chmod 700 ~/.ssh
Copy the SSH key on the Reporter system to the required location on the Collector system by issuing the following commands:
cd ~/.ssh
ssh 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:
Logon as root on the Reporter server.
Logon as moniforce user: su - moniforce.
Execute a remote pwd command: ssh Collector pwd.
Enter yes to the question "Are you sure you want to continue connecting (yes/no)?".
The command should return /var/opt/ruei.
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 Legend
Footnote 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.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|