RapidIdentity Product Guide

Minimum Requirements

Most of the RapidIdentity implementations run on the minimum requirements. One current implementation environment with over 130,000 users runs on the minimum requirements. Most of the time performance issues are not related to the appliances but rather due to lack of directory indexing. Be sure to index attributes that are being queried in both the RapidIdentity Connect Action Sets as well as the RapidIdentity Portal modules, especially the Delegation Definitions.

Appliance Minimum Hardware Requirements

  1. 2 Processors

  2. 4GB RAM

  3. 40GB Disk Space

  4. Audit database appliance requires at least 120GB Disk Space

Appliance Hardware Platform Options

  • Physical server installation

  • VMWare

  • Microsoft HyperV

Java 8

Java 8 is required for all on-premises, cloud, and virtual machine environments.

Disk Space

Disk space is typically unimportant to a RapidIdentity Portal or RapidIdentity Connect appliance. Typically, only log files and database entries for workflow (RapidIdentity Portal) and audit are stored. It is rare to go beyond the 40GB minimum in a virtual environment, and the minimum disk available on a physical machine (with mirrored drives at a minimum) is typically implemented. Currently, the only databases supported for configuration and audit are MySQL, PostgreSQL, and MS SQL 2012 and later.

RAM

Since RapidIdentity is a 64-bit operating system and application it can capitalize on 4GB of RAM or more. However, it is very unusual to need more than 4GB. The underlying application server (Tomcat) is configured to only use 2GB of RAM. This is the recommendation for machines with 4GB total RAM. If more RAM is added, please contact Identity Automation Support to configure Tomcat to use more memory. The recommendation is to have 2GB of RAM available to the operating system at all times.

Processors

The multi-threaded appliance capitalizes on multiple processors. For RapidIdentity Connect, each Action Set runs on separate processors, as available. Thus, multiple Action Sets running simultaneously could use different processors for each to maximize performance. There are numerous processes in RapidIdentity Portal that will take advantage of multiple processors so, again, the more you have the better the performance.