2.1. Java Requirements
This release of OpenAM requires Java Development Kit 1.6, at least 1.6.0_10. ForgeRock recommends the most recent release of Java 6 to ensure you have the latest security fixes.
ForgeRock has tested this release of OpenAM primarily with Oracle Java SE JDK.
OpenAM Java SDK requires Java Development Kit 1.5 or 1.6.
2.2. Web Application Container Requirements
This release of OpenAM runs in the following web application containers.
- Apache Tomcat 6.0.x, 7.0.x
- GlassFish v2
- IBM WebSphere 8, 8.5
- JBoss Enterprise Application Platform 4.x, 5.xJBoss Application Server 7.x
- Oracle WebLogic Server 11gOracle WebLogic Server 12c
If running as a non-root user, the web application container must be able to write to its own home directory, where OpenAM stores configuration files.
2.3. Data Store Requirements
This release of OpenAM works with the following configuration data stores.
- Embedded (using ForgeRock OpenDJ for the data store)When using the embedded configuration store, you must deploy OpenAM on a local file system and not on an NFS-mounted file system.
- External ForgeRock OpenDJ data store
- External Sun OpenDS data store
- External Oracle Directory Server Enterprise Edition data store
This release of OpenAM works with the following user profile data stores.
- ForgeRock OpenDJ
- Microsoft Active Directory
- IBM Tivoli Directory Server
- Oracle Directory Server Enterprise Edition
OpenAM also works with OpenLDAP and other LDAPv3 compliant directory servers. Some features of OpenAM depend on features supported by your directory service, such as the following:
- Extensible LDAP schema, required to extend the schema for OpenAM. First, install OpenAM to use a fresh instance of OpenDJ, such as the embedded OpenDJ server. After installation, study the custom schema definitions from the OpenDJ file,
config/schema/99-user.ldif, to see what schema definitions you must add to your directory. You might need to adapt the schema definition format before adding the definitions to your directory.
- The persistent search request control (OID:
- The Behera Internet-Draft Password Policy for LDAP Directories (for OpenAM password reset, for example)
If you plan to deploy with OpenLDAP or other LDAPv3 directory for user data, make sure you test your solution before you deploy to ensure all OpenAM features that you use work as expected.
2.4. Browsers Tested
ForgeRock has tested many browsers with OpenAM console and end user pages, including the following browsers.
- Chrome and Chromium 16 and later
- Firefox 3.6 and later
- Internet Explorer 7 and later
- Safari 5 and later
2.5. Platform Requirements
ForgeRock has tested this release of OpenAM on the following platforms.
- Linux 2.6, 3.0
- Microsoft Windows Server 2003, 2008
- Oracle Solaris 10
2.6. Hardware Requirements
You can deploy OpenAM on any hardware supported for the combination of software required. Deploying OpenAM requires a minimum of 1 GB free RAM over and above the RAM used by all other software on the system.
ForgeRock has tested this release of OpenAM primarily on x86 and x64 based systems.