Skip Headers

Oracle® Real User Experience Insight Installation Guide Release 5.0 for Linux x86-64 Part Number E12487-08 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| View PDF

# B Instal lation Checklist

This appendix provides a checklist of actions that should be complete, and information gathered, before starting to install the RUEI software. These include server and infrastructure readiness and configuration, as well as HTTPS encrypted traffic and alerting issues.

Server readiness |
--- | ---
Base hardware and operating system requirements. |
Intel/AMD 64-bit platform (minimum 2 dual-core CPUs). |
Network connectivity: 10/100 MB NIC for office network connectivity. 10/100/1000 MB NIC for data collection connectivity. |
Disk space: at least 400 GB (on high-performance RAID-5, RAID-10, or similar). |
Memory: at least 16 GB RAM for single server. |
OS: Oracle Enterprise Linux 64-bit or RedHat Enterprise Linux 64-bit 5.x. The `ruei-check.sh` script reports no errors. The EBS and PeopleSoft configuration zip files are available (only applicable if the EBS and/or PeopleSoft accelerators are to be installed). |

Infrastructure readiness |
--- | ---
Ensure easy placement and accessibility of the system. |
Prepare rackspace in the Data Center cabinet with power sockets. |
The server is accessible through remote ports: Port 80/443 for HTTP(S) traffic to the RUEI Web server. Port 22 for remote management over SSH/SCP. Port 25 (SMTP). Port 123 (NTP). Port 161/162 (SNMP). |
Access to the Data Center on the appropriate day and time is arranged. |
Network preparation for TAP/copy port is done and cables available in cabinet. |
Server configuration completed (see below). |
Main topology with proxies, load balancers, routers, switches, and so on, is known. |
Main traffic flows throughout the infrastructure are known. |
VLAN topology, VLAD IDs, and IP addresses are known. |
The monitoring position for the RUEI server is located as close as possible to the firewall. |
The domains, applications, server farm(s), and/or VLANs to be monitored are identified. |

Server configuration
Complete the details below to for reference during server configuration.
Host name and domain name (optional). |
Data Center name. |
Placement date and time. |
Server IP, netmask, and default gateway. |
Server type (Collector/Reporter). |
NTP server IP and backup. |
DNS server IP and backup. |
Mail server and sender mail. |
Socket 0: collection port to TAP/switch name. |
Socket 1: collection port to TAP/switch name. |
Socket 2: rescue/maintenance interface. | <reserved>
Socket 3: Office network to switch name. |
Socket 4: collection port to TAP/switch name. |
Socket 5: collection port to TAP/switch name. |

Data collection configuration
Once in place, the server will start collecting data. Specify how much data is expected, and the technologies used.
HTTP traffic (in MB, pageviews, or hits per hour). |
Base technology for Web applications. |
Limits on amount of traffic to be captured: HTTP and HTTPS ports (if other than 80/443 HTTP/HTTPS). VLAN traffic and VLAN IDs (optional). |
Cookie technology. |
Page-labelling technology. |
Blind POST field names (such as `passwd`). |
User identification in URL (if other than login). |
Web service domains or networks. |
XML/SOAP envelopes (max 10). |
Chronos/EUM URL (for EBS and Forms). |

HTTPS enablement
Specify the contact(s) for the required SSL keys to monitor encrypted traffic.
Name: |  | Name: |
Function: |  | Function: |
E-mail: |  | E-mail: |
Phone/Mobile: |  | Phone/Mobile: |
Keys (if not all): |  | Keys (if not all): |

System health notifications
The system can trigger and send alerts for various components. Specify the users, notification methods, and details for each component.
Name: |  | Name: |
Function: |  | Function: |
E-mail: |  | E-mail: |
Mobile: |  | Mobile: |
SMS: |  | SMS: |

Alerting via SNMP (optional)Foot 1 |
--- | ---
SNMP management server. |
SNMP community name. |
SNMP version. |

Footnote 1 RUEI provides a standard MIB to be imported into the SNMP manager.