Content and Design Implementation
124 Portal Server 6 2005Q1 •Deployment Planning Guide
See the Portal Server 6 Developer’s Guide and Portal Server 6 Desktop Customization
Guide for more information.

Placement of Static Portal Content

Place your static portal content in the web-container-install-root/SUNWam/public_html
directory or in a subdirectory under the
web-container-install-root/SUNWam/public_html directory (the document root for the
web container). Do not place your content in the
web-container-install-root/SUNWps/web-apps/https-server/portal/ directory, as this
is a private directory. Any content here is subject to deletion when the Portal Server
web application is redeployed during a patch or other update.
Integration Design
This section provides information on integration areas that you need to account for
in your low-level design.

Creating a Custom Access Manager Service

Service Management in Access Manager provides a mechanism for you to define,
integrate, and manage groups of attributes as an Access Manager serv ice. Readying
a service for management involves:
1. Creating an XML service file
2. Configuring an LDIF file with any new object classes and importing both the
XML service file and the new LDIF schema into Directory Service
3. Registering multiple services to organizations or sub-organizations using the
Access Manager administration console
4. Managing and customizing the attributes (once registered) on a per
organization basis
See the Access Manager documentation for more information.

Integrating Applications

Integrating and deploying applications with Portal Server is one of your most
important deployment tasks. The application types include:
•Channel. Provides limited content options; is not a “mini-browser”.