Setup Guide

Customizing the Groupware Portlet

This section describes the Customization features associated with the Groupware Portlet. The look and feel of the Groupware Portlet can be customized by modifying the Cascading Style Sheet (CSS) Class properties. The behavior of the Groupware Portlet can be customized by modifying the Groupware Listener classes.

Skins

The Compoze Portlets reference custom CSS Class names that are located in a file named compoze.css. Different versions of this file can exist for each skin in the Portal. Display aspects such as the font, background color, and text position can be easily modified by changing the properties inside the CSS class definitions.

The compoze.css file is organized into eight logical groups:

General CSS resources (used by any portlet utilizing these HTML features)
General Compoze (used by multiple feature groups)
Addressbook Feature Group
Calendar Feature Group
Home Feature Group
Mail Feature Group
Options Feature Group
Tasks Feature Group

Listener Classes

The Listener classes are located user the %PORTAL_PROJECT%/compoze/groupware/c13n/ directory. A default implementation exists for each Listener class. By modifying these classes, or creating your own implementation, you can change the following:

How the portlet obtains provider account information
Where portlet events are logged
How the portlet interacts with the user from page to page.

Account Listener

The AccountListener interface represents an interface for receiving account events. The DefaultAccountListener class represents a default implementation of the AccountListener interface. The DefaultAccountListener uses BEA's User Profile capabilities to retrieve and store provider account information. This class can be extended to:

Configure the type of provider to which new accounts will be bound to
Acquire provider connection parameters to providers from a source other than the BEA's User Profile
Pass additional connection parameters to the provider
Configure whether certain connection parameters are required to be entered during account setup
Configure whether multiple accounts can be added in the portlet
Configure whether users have the ability to add or edit accounts
Automatically create Groupware accounts for users
Configure SSO

To configure the portlets to use the subclass of the DefaultAccountListener which you have created, alter the DefaultAccountListener's getAccountListener method to return a new instance of your custom AccountListener. Various implementations of the AccountListener interface, such as ExchangeAccountListener and DominoAccountListener, ship with the product to aid you in the creation of your own custom AccountListener implementation.

Log Listener

The LogListener interface represents an interface for receiving log events. The DefaultLogListener class represents a default implementation of the LogListener interface. The DefaultLogListener currently does nothing so the log information is sent to the logging mechanism set for the BEA Portal. This messageReceived() method of this class can be altered to (for example):

Log information to additional targets (e.g. a database or file)
Perform logging based on some type of constraints

The portlet logging mechanism is sensitive to the logging level configured on the host WebLogic Portal. Debug and other messages can be output to the logging targets by altering the Logging Severity Threshold on the server to "Info".

View Listener

The ViewListener interface represents an interface for receiving view events. The DefaultViewListener class represents a default implementation of the ViewListener interface. The DefaultViewListener maximizes every view except those originating from the Home feature. By modifying this file, the Groupware Portlet can be displayed in the Normal mode, Maximized mode, or any combination of the two.

Portlet Locales

The LocaleUtility class is located under the %PORTAL_PROJECT%/compoze/groupware/c13n/ directory. The default list of locals can be modified by altering the list of available locales in the s_supportedLocales. If additional locales are added, be sure to add properties files which correspond to the list of new locales which will be available in the portlet. The list of properties files which should be created is:

%PORTAL_PROJECT%/compoze/content/groupware_resources_%JAVA_LOCALE_NAME%.properties
If the domino provider is being used, add a domino_resources_%JAVA_LOCALE_NAME%.properties file in the top-level directory of all harmony_portlets.jar files.
If the exchange provider is being used, add a exchange_resources_%JAVA_LOCALE_NAME%.properties file in the top-level directory of all harmony_portlets.jar files.

Note: If you encounter exceptions that include the following text, the properties files you have created are missing properties and should be altered to contain all properties that the default and unmodified groupware_resources.properties file contains. For example, the error: Error opening /portlets/compoze/content/addressbook/addContact/add_contact.jsp. The source of this error is javax.servlet.ServletException: Can't find resource for bundle com.bea.p13n.taglib.i18n.JspMessageBundle, key contacts.contact_add.button.attach means that the "contacts.contact_add.button.attach" key is missing from the groupware_resources_%JAVA_LOCALE_NAME%.properties file.