Deployment Requirements

For initial installation, a few hundred MB is sufficient, not including the downloaded files.

• The AM .war file size varies from release to release, but if your container holds one .war file and one directory with the contents of the .war file, the disk space required is on the order of 300 MB.

  This space requirement remains stable as you use AM.

• The installation of AM with an embedded DS server requires free disk space equal to or greater than 5 GB, plus 5% of the total size of the filesystem on AM's configuration directory.

• This space requirement grows as you use AM.

When using the embedded DS server, take the following into account:

• DS is designed to work with local storage for the database, but not for network file system (NFS) nor network-attached storage (NAS) due to some file system locking functions that DS needs. High performance storage, like solid state drives (SSD), is essential if you need to handle high write throughput.

  By default, AM's configuration directory resides under the $HOME directory of the user running the container. $HOME directories can be mounted over the network.

  This is not an issue if you are using DS mainly for configuration data. It can however be a serious problem when you use DS to back the CTS in a high-volume deployment.

• Embedded DS server log files are stored under /path/to/openam/opends/logs/. As for AM, you can configure DS server log rotation and purging. The default cap for access logs is 2 GB.

• AM stores policy information in the configuration directory. The space this takes up depends on the policies you have.

• By default, AM stores CTS information in the configuration directory. The space this takes up depends on the volume of traffic to the server and whether AM is configured for client-based sessions.

• With the default database implementation, DS database files handling sustained writes can grow to about double their initial size on disk.

• For DS on Linux systems, enable file system write barriers and ensure the file system journaling mode is ordered to avoid directory database file corruption after crashes or power failures. For details on enabling write barriers and setting the journaling mode for data, see the options for your file system in the mount command manual page.

• DS uses file descriptors when handling connections.

  Defaults can be limited to 1024 file descriptors per user on Linux systems. Consider increasing this limit to at least 64K. For details, see "Setting Maximum File Descriptors and Processes Per User".

• Web and Java agents can log audit messages locally to the agent installation or can send them to the AM instances. Refer to the configuration reference of your agent for more information.

• Debug messages are logged to files local to the agent installation, and their volume depends on the debug log level. In production environments, provision additional storage to ensure you can enable higher debug log levels for diagnostic purposes.

• Logs generated using a CaptureFilter

• Log messages created by scriptable filters and handlers

The following are based on the preceding information in this section. When deciding on disk storage, keep the following recommendations in mind:

• Plan enough space and enough disk I/O to comfortably absorb the load for logs.

  Check your assumptions in testing. For example, make sure that logs are cleaned up so that they do not exceed your space threshold even in long-duration testing.

• When using local web or Java agent logs, make sure you have a mechanism in place to clean them up.

• For IG, make sure you turn off CaptureFilter logging, scriptable filter, and handler debug logging before moving to production.