Preface

The Sun Java^TM System Portal Server Configuration Guide explains in detail how to install or upgrade to this version of the software and post installation configuration, discusses the new psadmin command line utilities that can be used to perform the basic duties of administrating the Portal Server software, describes the new inter-portlet feature, and includes reference material for the administration tag library.

Who Should Use This Book

This book includes information including new features and enhancements in the Portal Server software. This guide is meant for administrators and other individuals installing and using this version of the product.

Before You Read This Book

Before you read this book, see the Sun Java System Portal Server 7 Release Notes.

How This Book Is Organized

Chapter 1, Enabling Access to the Portal Server Through the Gateway, provides instructions on how you can enable access to thePortal Server through the Gateway.

Chapter 2, Enabling User Behavior Tracking, provides instructions for enabling User Behavior Tracking.

Chapter 3, Setting up Federated Search, provides instructions on how to set up Federated Search which enables users to submit a search query to multiple search engines concurrently and have the search results displayed in a unified format.

Chapter 4, Establishing Trust Between Two Cacao Agents, provides instructions for establishing trust between two cacao agents.

Chapter 5, Setting Up Registry Support for WSRP, provides instructions for setting up registry support for WSRP.

Chapter 6, Modifying Proxylet Rules, provides instructions on how to modify Proxylet Rules. These rules help the browser to identify the domains that needs to be routed through Proxylet.

Chapter 7, Creating a New Portal, provides instructions for creating a new empty portal and deploying sample content into an empty portal.

Chapter 8, Deploying Struts Application as a Portlet in Portal Server, provides instructions on how to deploy any existing struts application as a JSR168 portlet in Portal Server.

Chapter 9, Deploying JSF Application as a Portlet in Portal Server, provides instructions on how to deploy any existing JSF application as a JSR168 portlet in Portal Server.

Default Paths and File Names

The following table describes the default paths and file names used in this Configuration Guide.

Table P–1 Default Paths and File Names

Term	Description
PortalServer-base	Represents the base installation directory for a previous version of Portal Server. The software default base installation and product directory depends on your specific platform:  SolarisTM systems /opt
PortalServer7–base	Represents the base installation directory for this version of Portal Server. The software default base installation and product directory depends on your specific platform:  SolarisTM systems /opt
AccessManager-base	Represents the base installation directory for Sun Java System Access Manager. The Access Manager default base installation and product directory depends on your specific platform:  Solaris systems: /opt/SUNWam
DirectoryServer-base	Represents the base installation directory for Sun Java System Directory Server. Refer to the product documentation for the specific path name.
ApplicationServer-base	Represents the base installation directory for Sun Java System Application Server. Refer to the product documentation for the specific path name.
WebServer-base	Represents the base installation directory for Sun Java System Web Server. Refer to the product documentation for the specific path name.

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:

• Documentation

• Support

• Training

Typographic Conventions

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

Table P–2 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–3 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	#