test

Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide

Preface

The Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide provides planning and deployment solutions for Sun JavaTM System Access Manager based on the solution life cycle.

Access Manager is a component of the Sun JavaTM 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 deployment architects and business planners responsible for the planning, analysis, and design of an Access Manager deployment. This book might also be useful for system integrators who are responsible for the design and implementation of the specific aspects of an Access Manager deployment.

Before You Read This Book

Readers should be familiar with the following components and concepts:

How This Book Is Organized

This book is organized as follows:

Chapter 1, Introduction to Deployment Planning for Access Manager introduces Sun Java System Access Manager.

Chapter 2, Business Analysis for Access Manager describes the business analysis phase of the solution life cycle, when you define business goals by analyzing a business problem and identifying the business requirements and business constraints to meet that goal.

Chapter 3, Technical Requirements describes the technical requirements phase of the solution life cycle, when you perform a usage analysis, identify use cases, and determine quality of service requirements for the proposed deployment solution.

Chapter 4, Logical Design with Access Manager describes the logical design phase of the solution life cycle, when you design a logical architecture showing the interrelationships of the logical components of the solution.

Chapter 5, Deployment Design with Access Manager describes the deployment design phase of the solution life cycle, when you design a high-level deployment architecture and a low-level implementation specification, and prepare a series of plans and specifications necessary to implement the solution.

Chapter 6, Implementation of an Access Manager Design describes the implementation phase of the solution life cycle. For example, deploying Access Manager on multiple servers or installing and configuring Access Manager session failover.

Appendix A, Installed Product Layout describes the directory layout after you install Access Manager.

Appendix B, Changing the Password Encryption Key describes the password encryption key and how to change it after installation.

Related Books

Related documentation is available as follows:

Access Manager Core Documentation

The Access Manager core documentation set contains the following titles:

Updates to the Access Manager Release Notes and links to modifications of the core documentation can be found on the Access Manager documentation web site (http://docs.sun.com/app/docs/coll/1292.1).

Sun Java Enterprise System Product Documentation

For useful information for related products, see the following documentation collections on the Sun Java Enterprise System documentation web site (http://docs.sun.com/prod/entsys.05q4):

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

Sun Function 

URL 

Description 

Documentation 

http://www.sun.com/documentation/

Download PDF and HTML documents, and order printed documents 

Support and Training 

http://www.sun.com/support/

Obtain technical support, download patches, and learn about Sun courses 

Typographic Conventions

The following table describes the typographic changes that are used in this book.

Table P–1 Typographic Conventions

Typeface or Symbol 

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.

Perform a patch analysis.

Do not save the file.

[Note that some emphasized items appear bold online.] 

Shell Prompts in Command Examples

The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.

Table P–2 Shell Prompts

Shell 

Prompt 

C shell prompt 

machine_name%

C shell superuser prompt 

machine_name#

Bourne shell and Korn shell prompt 

$

Bourne shell and Korn shell superuser prompt 

#

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 Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide, and the part number is 819-2136.