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

• To Enable Mail Service to the Organization Using Delegated Administration CLI

• To Enable Proxy Authentication in Calendar Server

• To Partition the Proxy Users in a Separate Organization

To Install and Configure the Back-end Services

See detailed documentation for Calendar Server and Delegated Administrator software for instructions on installing and configuring these software.

Documentation for:

• Installing and configuring Calendar Server is available at Part II, Postinstallation Configuration, in Sun Java System Calendar Server 6 2006Q4 Administration Guide.

• Installing and configuring Delegated Administration software is available at Sun Java System Communications Services 6 2006Q4 Delegated Administrator Guide.

To Enable Mail Service to the Organization Using Delegated Administration CLI

See Chapter 5, Command Line Utilities, in Sun Java System Communications Services 6 2006Q4 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

1. 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.

2. 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.

1. Create a new parallel organization with a unique domain name to the organization containing the community users through Delegated Administration.

   For example, create an organization called proxyusers.com.

2. 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 through the Portal Server management console and set the DA_DEFAULT_DOMAIN to the proxy users organization domain name.