Sun Java System Access Manager 7.1 Postinstallation Guide

Revision History

Table P–5 Revision History

Date and Part Number 

Description of Change 

February 14, 2007 (819–5899–10) 

Initial release. 

May 18, 2007 (819–5899–11) 

In Chapter 12, Deploying Access Manager as a Single WAR File, revised the information about the deploying an Access Manager 7.1 WAR file (amserver.war) and a Distributed Authentication UI server WAR file (amauthdistui.war).

June 7, 2007 (819–5899–12) 

In Chapter 12, Deploying Access Manager as a Single WAR File, added the requirement that to run the Configurator, the code set in the LANG environment variable must be set to ISO8859-1.

January 31, 2008 (819–5899–13) 

Added Chapter 14, Removing Access to the Access Manager Console.

In Appendix A, Directory Server Considerations:

February 19, 2008 (819–5899–14) 

In Chapter 6, Implementing Session Failover, added the Removing the Session Failover Configuration section.

In Appendix A, Directory Server Considerations, added the Changing the Naming Attribute After Installation section.

March 4, 2008 (819–5899–15) 

Added Appendix C, Using Active Directory as the User Data Store.

May 5, 2008 (819–5899–16) 

Clarified the Configuring Different Root Suffixes for the Access Manager Information Tree and User Directory Nodes section, because Active Directory cannot be used as the configuration data store.

May 30, 2008 (819–5899–17) 

Clarified the required LDIF file in Appendix C, Using Active Directory as the User Data Store.

October 2, 2009 (819–5899–18) 

Added a note that the Client Detection service is disabled for a WAR file deployment in Considerations for an Access Manager WAR File Deployment.

Updated the permissions for a for a WAR file deployment in Adding Access Manager Permissions to the Server Policy File.