Sun Java System Portal Server 7 Community Sample Guide

Chapter 2 Configuring Back-end Services

Certain service portlets in the Community Sample require certain back-end services to be setup and configured prior to installing and configuring the portlet. These back-end services are Sun Java^TM System Calendar Server and Sun Delegated Administration software. You can use an existing deployment or, choose to perform a fresh install and configuration of these services. This chapter provides instructions for configuring the back-end services for the Community Sample portlets.

This chapter contains the following:

Configuring Back-end Services for Portlets

The Calendar Server, Delegated Administration software, and Sun Java System Portal Server software must use the same Sun Java System Directory Server. Mail service should be enabled for the organization.

To Install and Configure the Back-end Services

Step

See detailed documentation for:

Installing Calendar Server at Configuring Calendar Server at Part II, Postinstallation Configuration, in Sun Java System Calendar Server 6 2005Q4 Administration Guide in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
Installing Delegated Administration software at Configuring Delegated Administration software at Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

To Enable Mail Service to the Organization Using Delegated Administration CLI

Step

See Chapter 5, Command Line Utilities, in Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

For example, type /opt/SUNWcomm/bin/commadmin domain modify -D admin -n domain -w passwd -S mail -H preferred-mailhost -d domain to add mail LDAP attribute to the user.

To Enable Proxy Authentication in Calendar Server

Steps

Edit CS-config-directory/ics.conf file (where CS-config-file is by default /etc/opt/SUNWics5/config/ directory) and change the value of service.http.allowadminproxy property to yes.

Restart the Calendar Server.

To Partition the Proxy Users in a Separate Organization

A proxy user is created for each community to manage that community's shared calendar. Follow the instructions in this section to avoid populating the manually created Portal Server users' organization.

Steps

Create a new parallel organization with a unique domain name to the organization containing the community users via Delegated Administrator.

For example, create an organization called proxyusers.com.

Set the DA_DEFAULT_DOMAIN to the proxy user's newly created organization domain name.

For example, set the DA_DEFAULT_DOMAIN to proxyusers.com. If the portlets have already been deployed, update the relevant SSO adapters via the Portal Server administration console and set the DA_DEFAULT_DOMAIN to the proxy users organization domain name.

Gathering Information for the Portlets

Before deploying the portlets, gather the following information:

UGRoot Suffix: This is the server/Group Root suffix of the Directory Server. This information is provided while running the commds_setup.pl script.
CSUGRoot Suffix: This is the UGRoot suffix under which the calendar users are created by default. It is under this suffix, the calendar admin user (calmaster) is created. It is important to choose this suffix appropriately such that the calendar admin user is able to proxy-authenticate other calendar users in other organizations. It is recommended that this suffix be the same as UGRoot Suffix. For the portlets, this specifies the value of Base Distinguished Node configuration input while configuring Calendar Server.
DA Default Domain: This is the DNS domain name of the default organization used by Delegated Administration software (for provisioning users by default). For the portlets, this specifies the value of Default Domain configuration input while configuring Delegated Administration software.
DA Default Organization DN: The Organization distinguished node will be the LDAP subtree under which all the users and groups that belong to the Delegated Administration software Default Domain are located. Note that the distinguished node must be located under the UGRoot Suffix. For the portlets, this specifies the value of Organization Distinguished Node for the Default domain configuration input while configuring Delegated Administration software.