Server Readiness | |
---|---|
Base hardware and operating system requirements. |
|
Intel/AMD 64-bit platform (minimum 2 dual-core CPUs). |
|
Network 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 Linux 64-bit or RedHat Enterprise Linux 64-bit 5.x or 6.x. Oracle Database 11g or 12c Enterprise Edition. The The EBS, JD Edwards, FLEXCUBE, and PeopleSoft configuration zip files are available. |
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:
|
|
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:
|
|
Cookie technology. |
|
Page-labelling technology. |
|
Blind POST field names (such as |
|
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: |
||
Text message: |
Text message: |
Alerting via SNMP (Optional)(1) | |
---|---|
SNMP management server. |
|
SNMP community name. |
|
SNMP version. |
Footnote 1 RUEI provides a standard MIB to be imported into the SNMP manager.