Installing OpenAM Core Services

Deploy the .war file on your container.

$ cp OpenAM-13.5.2.war /path/to/tomcat/webapps/openam.war

Browse to the initial configuration screen, for example at http://openam.example.com:8080/openam.

In the initial configuration screen, click Create Default Configuration under Default Configuration.

Review the software license agreement. If you agree to the license, click "I accept the license agreement", and then click Continue.

Provide different passwords for the default OpenAM administrator, amadmin, and default Policy Agent users.

When the configuration completes, click Proceed to Login, and then login as the OpenAM administrator with the first of the two passwords you provided.

Stop the OpenAM web application to clear the configuration held in memory.

$ /path/to/tomcat/bin/shutdown.sh
Password:
Using CATALINA_BASE:   /path/to/tomcat
Using CATALINA_HOME:   /path/to/tomcat
Using CATALINA_TMPDIR: /path/to/tomcat/temp
Using JRE_HOME:        /path/to/jdk/jre
Using CLASSPATH:
       /path/to/tomcat/bin/bootstrap.jar:/path/to/tomcat/bin/tomcat-juli.jar

Delete OpenAM configuration files, by default under the $HOME of the user running the web application container.

$ rm -rf $HOME/openam $HOME/.openamcfg

Restart the OpenAM web application.

$ /path/to/tomcat/bin/startup.sh
Password:
Using CATALINA_BASE:   /path/to/tomcat
Using CATALINA_HOME:   /path/to/tomcat
Using CATALINA_TMPDIR: /path/to/tomcat/temp
Using JRE_HOME:        /path/to/jdk/jre
Using CLASSPATH:
       /path/to/tomcat/bin/bootstrap.jar:/path/to/tomcat/bin/tomcat-juli.jar

In the initial configuration screen, click Create New Configuration under Custom Configuration.

Read the license agreement. If you agree to the license, click "I agree to the license agreement", and then click Continue.

On the Default User Password page, provide a password with at least eight characters for the OpenAM Administrator, amadmin.

Verify that the server settings are valid for your configuration.

In the Configuration Store screen, you can accept the defaults to allow OpenAM to store configuration data in an embedded directory. The embedded directory can be configured separately to replicate data for high availability if necessary.

In the User Store screen, you configure where OpenAM looks for user identities.

In the Site Configuration screen, you can set up OpenAM as part of a site where the load is balanced across multiple OpenAM servers.

In the Agent Information screen, provide a password with at least eight characters to be used by policy agents to connect to OpenAM.

Check the summary screen, and if necessary, click Previous to return to earlier screens to fix any configuration errors as needed.

When the configuration completes, click Proceed to Login, and then login as the OpenAM administrator, amadmin.

Restrict permissions to the configuration directory (by default, $HOME/openam, where $HOME corresponds to the user who runs the web container). Prevent other users from accessing files in the configuration directory.

If you specified the Other User Data Store option in the User Data Store Settings screen, you must index several attributes in your external identity repository. See "To Index External Identity Repository Attributes" for more information.

In the initial configuration screen, under Custom Configuration, click Create New Configuration.

In the first screen, enter the same password entered for the OpenAM Administrator, amadmin, when you configured the first server in the site.

Configure server settings as required.

In the configuration store screen, select Add to Existing Deployment, and enter the URL of the first OpenAM server in the site.

In the site configuration screen, select Yes and enter the same site configuration details as for the first server in the site.

In the summary screen, verify the settings you chose, and then click Create Configuration.

When the configuration process finishes, click Proceed to Login, and then login as the OpenAM administrator to access OpenAM Console.

If Tomcat is already started, stop it.

Specify the -Dcom.iplanet.services.debug.level=message option in the CATALINA_OPTS environment variable:

$ export CATALINA_OPTS=-Dcom.iplanet.services.debug.level=message

Run the OpenAM installation. Debug log files containing troubleshooting information appear in the /path/to/openam/openam/debug directory.

When you have completed OpenAM installation and no longer need to capture debug logs, stop Tomcat, revert the debug logging options, and restart Tomcat.