Skip Headers
Oracle® Real User Experience Insight Installation Guide
12c Release 2 (12.1.0.3) for Linux x86-64

Part Number E37265-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

E The ruei-check.sh Script

This appendix provides a detailed explanation of the checks performed by the ruei-check.sh script. It is strongly recommended that you use this script to verify successful installation, and to troubleshoot any installation issues.

When started, the script prompts you to specify which role or roles the system is required to perform. For example:

Please specify which role(s) this system will perform.
Use commas to separate multiple roles. For example, 1,2,4

1 - Reporter
2 - Processing Engine
3 - Collector
4 - Database

Enter role(s): 1,2,3,4

The permitted role combinations are shown in Table E-1.

Table E-1 Permitted System Role Combinations

Roles Description

1

Reporter only.

2

Processing Engine only.

3

(Remote) Collector only.

4

(Remote) database only.

1,2

Reporter with Processing Engine.

1,2,3

Reporter with Collector and Processing Engine.

1,2,4

Reporter with Processing Engine and database.

1,2,3,4

Reporter with Processing Engine, Collector, and database.


The checks are performed in the order shown in Table E-2, and are divided into three types: pre-installation, system, and post-installation checks. Whether a specific check is performed depends on the selected role(s).

Table E-2 ruei-check.sh Checks


Role
Check 1 2 3 4 Description

System checks

Architecture

Must be x86_64.

Operating system

Must be Oracle/RedHat Linux 5.x.

Memory

Must be at least 4 GB.

Recommended 16 GB for Reporter installation.

Recommended 8 GB for a Collector only or remote database installation.

Swap space

Must be at least 3/4 of the installed system memoryFoot 1 .

Disk space for RUEI_HOME

 

The disk space for the specified RUEI_HOME location must be at least 512 MB.

Disk space for RUEI_DATA

 

The disk space for the specified RUEI_DATA location must be at least 100 GB.

Disk speed on RUEI_DATA

 

The disk speed of the specified RUEI_DATA location must be at least 40 MB/s (120 MB/s or more is recommended).

SELinux

SELinux must be disabled.

Network interfaces

   

 

Must have at least one interface must be Up without an IP address (as described in ).

Hostname

The system's configured IP address and hostname must be specified in the /etc/hosts file.

DNS

The configured DNS server must resolve the system's configured hostname to its IP address.

HTTPD autostart

     

Must be configured to start automatically.

HTTPD up

     

Must be up.

Database autostart

     

Must be configured to start automatically.

SSHD autostart

Must be configured to start automatically.

SSHD up

Must be up.

SSHD

Attempts to check if the SSH is not firewalled.

NTPD autostart

Must be configured to start automatically.

NTPD up

Must be up.

NTPD

Must be synchronized with a time server.

PHP CLI

     

PHP must be available on the command line.

PHP settings

     

session.gc_maxlifetime should be at least 14400.

memory_limit should be at least 96M.

post_max_size should be at least 128M.

upload_max_filesize should be at least 128M.

Zend Optimizer must be available.

(These appear as individual checks, and are only performed if the above check is passed).

PHP timezone

     

PHP must return the same timezone as the Reporter operating system. See ruei-check.sh Script Reports PHP Timezone Error for additional information.

RSVG

     

The ~apache/.gnome2 directory must exist.

Pre-install checks

Disk space for database data directory

     

Must be 500 GB. (If on the same partition as RUEI_DATA, must be 700 GB).

Disk containing database data directory

     

Should be local. (Remote file systems, such as NFS, are not supported).

Disk speed of database data directory

     

Must be at least 40 MB/s (120 MB/s is recommended).

RUEI_USER user exists

 

The specified RUEI_USER user must exist.

apache user exists

     

User apache must exist.

User apache in group RUEI_GROUP

     

User apache must be a member of the specified group RUEI_GROUP.

User apache in group uucp

     

User apache must be a member of the group uucp.

User RUEI_USER in group uucp

 

The specified RUEI_USER user must be in group uucp.

User root must have umask of 0022

User root must have the umask 0022.

User root can write to /etc/http/conf.d

     

User root must be able to write to the /etc/http/conf.d directory.

User root can write to /etc/init.d

   

User root must be able to write to the /etc/init.d directory.

User root can write to /etc/ld.so.conf.d

   

 

User root must be able to write to the /etc/ld.so.conf.d directory.

User root can write to RUEI_HOME

 

User root must be able to write to the specified RUEI_HOME directory.

User root can write to RUEI_DATA

 

User root must be able to write to the specified RUEI_DATA directory.

User root can write to /tmp

User root must be able to write to the /tmp directory.

/etc/sysconfig/httpd must call /etc/ruei.conf

     

The /etc/sysconfig/httpd script must call the /etc/ruei.conf configuration file.

RUEI_USER user able to contact database

   

The specified RUEI_USER user must be able to connect to the database.

oci8 PHP extension available

     

The oci8 PHP extension must be available.

RUEI_USER user able to contact database via PHP

     

The specified RUEI_USER user must be able to connect to the database via PHP.

RUEI_USER user must have umask 0027

 

The specified RUEI_USER user must have a umask of 0027.

RUEI_USER user able to read RUEI_HOME

 

The specified RUEI_USER user must be able to read the specified RUEI_HOME directory.

RUEI_USER user able to write to RUEI_DATA

 

The specified RUEI_USER user must be able to read the specified RUEI_DATA directory.

Permissions and ownership of RUEI_DATA

 

The Apache user must be able to read from the specified RUEI_DATA directory.

/etc/ruei.conf syntactically correct

 

The /etc/ruei.conf configuration file must be a syntactically correct shell script.

User root able to contact database after loading ruei.conf

   

The root user must be able to connect to the database after the environment specified in the ruei.conf configuration file has been loaded.

wm_concat available

   

The wm_concat database function (used by suites) must be available.

$JAVA_HOME value valid

   

The value specified for $JAVA_HOME in the /etc/ruei.conf configuration file must be valid.

Post-install checks

Reporter RPM check

     

The ux_collector, ux-bi-publisher, ux-core, ux-generic, ux-ipdb, ux-gui, ux-lang-en, ux_lang-fr_fr, ux_lang-de_de, ux_lang-es_es, ux-adf, ux-lang-zh_cn, ux-lang-ko_kr, ux-lang-ja_jp, ux-wlp, ux-suites-ebs, ux-suites-jde, ux-suites-sbl, ux_suites_fus, ux-suites-psft, and ux-suites-flex RPMs must be installed and have the same version (for example, 11.1.0).

Processing Engine check

       

The ux-core, ux-generic, ux-ipdb, ux_suites_fus, ux-adf, ux-wlp, ux-suites-ebs, ux-suites-jde, ux-suites-sbl, ux-suites-psft, and ux-suites-flex RPMs must be installed and have the same version (for example, 11.1.0).

Collector RPM check

   

 

The ux-collector RPM must have been installed.

Java shared objects

   

 

The Java path must have been correctly added to the LD_LIBRARY_PATH (see Generic Installation Tasks).

GUI reachable

     

The Reporter GUI must be reachable via the local hostname on the secure interface (note if a self-signed certificate is found, a warning is generated).

Reporter GUI can reach database

     

The Reporter GUI must be able to contact to the database.

Permissions and ownership of Oracle wallet

   

The Oracle wallet must be readable by the Apache user.

Permissions and ownership of Oracle wallet

 

   

The Oracle wallet must be readable by the RUEI_USER user.

Core binaries in path

   

The specified RUEI_USER user must be able to call the core binaries without specifying a full name.


Footnote 1 If memory is added to meet the memory requirement, this check may start failing.

Re-running the ruei-check.sh Script

Be aware that the role selection you make when running the script is saved to file. Therefore, if you want to re-run the script and be able to specify a different role or roles for the system, you need to delete the file /tmp/ruei-system-type using the following command:

rm /tmp/ruei-system-type