Use the information in the following table to verify that your environment meets all requirements before you deploy the appliance.
Table 2-2 Product Requirements
Components |
Requirements |
---|---|
Supported Virtual Environments |
The appliance requires one of the following virtual environments:
|
Virtual System Guest Requirements |
Minimum hardware requirements for each appliance node in the cluster:
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 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 virtual environment. |
Cluster |
Supported cluster configuration:
NOTE:The L4 switch must be configured with the publicly resolvable DNS of the cluster before you initialize the appliance. |
Identity Sources |
Supported identity sources for users:
For more information, see Section 5.0, Configuring Identity Sources. |
Client Workstations |
Administration: Supported workstations for administration tasks: NOTE:Administration tasks are not supported on mobile devices.
Users: Supported workstations for users:
|
Mobile Devices |
Administration: Not supported on mobile devices. Users: Supported iOS mobile devices for users:
Supported Android mobile devices for users:
|
Browsers |
Administration: Supported browsers for administration tasks:
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 might be slower than with other supported browsers. Users: Supported browsers for users:
|
Email Clients |
For email proxy, CloudAccess supports IMAP, POP3, and SMTP across a variety of desktop and mobile email clients. For example, Windows Live Mail 2011 and the latest version of the Apple Mail Client on iPad or iPhone with iOS 8.x or later. NOTE:The email ports in the CloudAccess cluster cannot be changed. It might be necessary to adjust the mail protocol or port configuration on the email clients to connect to the email proxy. |
DNS |
CloudAccess requires that all appliance nodes, administration workstations, end-user workstations, mobile devices, and identity sources be able to resolve the public DNS name of the appliance. NOTE:The L4 switch must be configured with the publicly resolvable DNS of the cluster before you initialize the appliance. |
SaaS Application Requirements |
Each SaaS application has different requirements. For more information about the requirements for each SaaS application, see the NetIQ CloudAccess Connectors Guide. |