Preface
The Sun Java System Access Manager 7.1 Postinstallation Guide provides information about configuring Sun JavaTM System Access Manager after installation. Usually, you perform postinstallation tasks only a few times. For example, you might want to deploy an additional instance of Access Manager or configure Access Manager for session failover.
Access Manager is a component of the Sun Java Enterprise System (Java ES), a set of software components that provide services needed to support enterprise applications distributed across a network or Internet environment.
Who Should Use This Book
This book is intended for system administrators and system integrators who are responsible for installing and configuring Access Manager.
Before You Read This Book
Readers should be familiar with the following components and concepts:
-
Access Manager technical concepts, as described in the Sun Java System Access Manager 7.1 Technical Overview.
-
Deployment platform: SolarisTM, Linux, HP-UX, or Windows operating system
-
Web container that will run Access Manager: Sun Java System Application Server, Sun Java System Web Server, BEA WebLogic, or IBM WebSphere Application Server
-
Technical concepts: Lightweight Directory Access Protocol (LDAP), Java technology, JavaServer PagesTM (JSPTM) technology, HyperText Transfer Protocol (HTTP), HyperText Markup Language (HTML), and eXtensible Markup Language (XML)
How This Book Is Organized
This book is organized by common configuration tasks, as outlined in the Contents.
Related Books
Related documentation is available as follows:
Access Manager 7.1 Documentation Set
The following table describes the Access Manager documentation set, which is available on the following Web site:
http://docs.sun.com/coll/1292.2
Table P–1 Access Manager 7.1 Documentation Set|
Title |
Description |
|---|---|
|
Sun Java System Access Manager 7.1 Documentation Center |
Contains links to commonly referenced information in the Access Manager documentation collection. |
|
Describes new features, problems fixed, installation notes, and known issues and limitations. The Release Notes are updated periodically after the initial release to describe any new features or problems. |
|
|
Provides an overview of how Access Manager components work together to consolidate access control functions, and to protect enterprise assets and web-based applications. It also explains basic Access Manager concepts and terminology. |
|
|
Sun Java System Access Manager 7.1 Deployment Planning Guide |
Provides planning and deployment solutions for Access Manager based on the solution life cycle. |
|
Sun Java System Access Manager 7.1 Postinstallation Guide (this guide) |
Provides information about configuring Access Manager after installation. Usually, you perform postinstallation tasks only a few times. For example, you might want to deploy an additional instance of Access Manager or configure Access Manager for session failover. |
|
Describes how to use the Access Manager console as well as manage user and service data via the command line interface. |
|
|
Provides reference information for the Access Manager command-line interface (CLI), configuration attributes, AMConfig.properties attributes, serverconfig.xml file attributes, log files, and error codes. |
|
|
Sun Java System Access Manager 7.1 Federation and SAML Administration Guide |
Provides information about the Federation module based on the Liberty Alliance Project specifications. It includes information on the integrated services based on these specifications, instructions for enabling a Liberty-based environment, and summaries of the application programming interface (API) for extending the framework. |
|
Provides information about customizing Access Manager and integrating its functionality into an organization’s current technical infrastructure. It also contains details about the programmatic aspects of the product and its API. |
|
|
Provides summaries of data types, structures, and functions that make up the public Access Manager C APIs. |
|
|
Provides information about the implementation of Java packages in Access Manager. |
|
|
Sun Java System Access Manager 7.1 Performance Tuning and Troubleshooting Guide |
Provides information about how to tune Access Manager and its related components for optimal performance. |
|
Sun Java System Access Manager Policy Agent 2.2 User’s Guide |
Provides an overview of Policy Agent software, including the web agents and J2EE agents that are currently available. To view the Access Manager Policy Agent 2.2 documentation collection, see: |
Sun Java Enterprise System 5 Documentation
The following table provides links to documentation collections for related Java ES products.
Table P–2 Related Sun Java Enterprise System 5 Documentation|
Product |
Link |
|---|---|
|
Sun Java Enterprise System 5 | |
|
Sun Java System Directory Server Enterprise Edition 6 | |
|
Sun Java System Web Server 7 | |
|
Sun Java System Application Server Enterprise Edition 8.2 | |
|
Sun Java System Message Queue 3.7 UR1 | |
|
Sun Java System Web Proxy Server 4.0.4 | |
|
Sun Java System Identity Manager 7 |
Searching Sun Product Documentation
Besides searching Sun product documentation from the docs.sun.comSM web site, you can use a search engine by typing the following syntax in the search field:
search-term site:docs.sun.com |
For example, to search for “broker,” type the following:
broker site:docs.sun.com |
To include other Sun web sites in your search (for example, java.sun.com, www.sun.com, and developers.sun.com), use sun.com in place of docs.sun.com in the search field.
Related Third-Party Web Site References
Third-party URLs are referenced in this document and provide additional, related information.
Note –
Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.
Documentation, Support, and Training
The Sun web site provides information about the following additional resources:
Typographic Conventions
The following table describes the typographic conventions that are used in this book.
Table P–3 Typographic Conventions|
Typeface |
Meaning |
Example |
|---|---|---|
|
AaBbCc123 |
The names of commands, files, and directories, and onscreen computer output |
Edit your .login file. Use ls -a to list all files. machine_name% you have mail. |
|
AaBbCc123 |
What you type, contrasted with onscreen computer output |
machine_name% su Password: |
|
aabbcc123 |
Placeholder: replace with a real name or value |
The command to remove a file is rm filename. |
|
AaBbCc123 |
Book titles, new terms, and terms to be emphasized |
Read Chapter 6 in the User's Guide. A cache is a copy that is stored locally. Do not save the file. Note: Some emphasized items appear bold online. |
Shell Prompts in Command Examples
The following table shows the default UNIX® system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.
Table P–4 Shell Prompts|
Shell |
Prompt |
|---|---|
|
C shell |
machine_name% |
|
C shell for superuser |
machine_name# |
|
Bourne shell and Korn shell |
$ |
|
Bourne shell and Korn shell for superuser |
# |
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. |
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document.
For example, the title of this book is the Sun Java System Access Manager 7.1 Postinstallation Guide, and the part number is 819–5899.
- © 2010, Oracle Corporation and/or its affiliates