2.1 Requirements

Use the information in the following table to verify that you meet the requirements for SocialAccess before deploying the appliance.

Table 2-1 SocialAccess Requirements

Components

Requirements

VMware

One of the following versions of VMware:

  • ESXi 5.5

  • ESXi 5.1

  • ESXi 5.0 (U2 or later)

Node

Minimum hardware requirements for each appliance node in the cluster:

  • 60 GB disk space

  • 2 Cores

  • 4 GB RAM

NOTE:The default memory allocation is 8 GB, but you can change the memory allocation as needed before powering on the appliance.

The appliance can be a heavy consumer of CPU, disk I/O, and network bandwidth. Performance can be adversely affected by other virtual machines with similar operational requirements deployed on the same VMware host server.

As a best practice, ensure that you group or separate virtual machines on hosts and data stores to avoid resource conflicts for CPU, disk I/O, and network bandwidth. You can do this manually as you deploy virtual machines, or use affinity and anti-affinity rules if they are available in your VMware environment.

Browsers

Administration: Supported browsers for administration tasks:

  • Firefox (latest version) on Windows 7 or 8.1

  • Google Chrome (latest version) on Windows 7 or 8.1

  • Internet Explorer (latest version) on Windows 7 or 8.1

  • Safari (latest version) on OS X Mavericks or later

Users: Supported browsers for users:

  • Firefox (latest version) on Windows 7 or 8.1

  • Google Chrome (latest version) on Windows 7 or 8.1

  • Internet Explorer (latest version) on Windows 7 or 8.1

  • Safari (latest version) on OS X Mavericks or later

NOTE:You must disable pop-up blockers to access the administration console. If you experience any issues with a supported browser, ensure that you have the latest version of the browser installed, or try another supported browser. Administering the appliance with Internet Explorer may be slower than with other supported browsers.

Cluster

Supported cluster configuration:

  • Up to a five-node cluster

  • For optimal performance, each node should reside in the same IP subnet

DNS

SocialAccess requires that all appliance nodes, administration workstations, end user workstations, and identity sources be able to resolve the public DNS name of the appliance.