The SharedEvents and SharedTasks 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 JavaTM System Calendar Server and Sun Delegated Administration software. You can use an existing deployment or, choose to perform a fresh installation and configuration of these services. This section provides instructions for configuring the back-end services for these 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.
This section contains the following:
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, Post Installation Configuration for Calendar Server 6.3 Software, in Sun Java System Calendar Server 6.3 Administration Guide.
Installing and configuring Delegated Administration software is available at Sun Java System Delegated Administrator 6.5 Administration Guide.
See Chapter 5, Command Line Utilities, in Sun Java System Delegated Administrator 6.5 Administration Guide and run the commadmin command.
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.
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.
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.
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.
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.