This chapter describes how to perform advanced customizations. It also provides HTML files, their location, and details on features that are fully customizable for Communications Express user interface.
This chapter contains the following sections:
In addition to the features mentioned in Chapter 5, Customizing User Interface Features in Mail, many other features are fully customizable. However, to take advantage of these features, an in-depth knowledge of JavaScript is required. You might also face migration problems when attempting to reconfigure JavaScript files.
This chapter does not provide code samples for advanced customizations. Also, an advanced knowledge of JavaScript and HTML is assumed.
Table 6–1 lists the UI related FrameSet files of Communications Express user interface that are fully customizable.
Table 6–1 Communications Express User Interface Customizable Features
Features |
Files |
---|---|
Adds attachment for upload (popup window) | |
Collects pop email (popup window) | |
New message composition | |
Folder viewing and management | |
Message listing for a selected folder | |
Message viewing | |
Receipt notification (popup window) | |
Search message (popup window) | |
Sets folder sharing permission (popup window) | |
Search Results |
srchresults_fs_lr.html |
Subscribe to |
subscribe_fs_lr.html |
You can modify the following attachments options in mail.
The HTML file that controls the attachment related features is attach_fs_lr.html.
You can modify the following labels that appear when collecting mail from another server:
Password (text field)
Delete messages from server (select button)
Save to folder (list box)
The HTML file that controls the mail collection feature is collect_fs_lr.html.
The message composition feature enables basic mail functions. You can modify the following message composition options:
Compose new message
Reply to the sender
Reply to all recipients of the message including the sender
Forward message to others
Move message to folder
Delete message
Navigate through messages using Prev or Next icon
The HTML file that controls the message composition feature is msg_fs_lr.html.
The mailbox management tab enables access to a mailbox. You can modify the following mailbox management tab options:
Get new message
Compose new message
Search for message
Move message to selected folder
Delete message
Undelete message
Select message
Select all messages
Collect external messages
The HTML file that controls the mailbox management tab feature is mbox_fs_lr.html.
The HTML file that controls the options tab features is opts_fs_lr.html.
The return receipt feature enables the management of return receipts.
The file that controls the return receipt feature is receipt_fs_lr.html.
A shared folder is a folder in which you can store messages that can be accessed by other users. Communications Express manages access to the shared folders by granting others access to the shared folders.
Sharing folders is a two-step process that involves sharing and subscribing:
A user shares a folder, specifying who has permissions to the folder.
The users who were given permissions to that folder then subscribe to it.
For more information on Shared Folders, see Sun Java System Communications Express Online Help, that can be accessed by clicking the Help on Sun Java System Communications Express.
The Communications Express Server loads a default set of LDAP attributes for a user at the start of a session. These attributes are provided in Example 6–1.
cn givenName mail mailAlternateAddress mailAutoReplyMode mailAutoReplySubject mailAutoReplyText mailAutoReplyTextInternal mailAutoReplyTimeout mailDeliveryOption mailForwardingAddress mailQuota,mailMsgQuota preferredLanguage sn uid vacationEndDate vacationStartDate |
For more information on the attributes required or allowed by LDAP object classes for Communications Express, see Chapter 3 Attributes in the Sun One Messaging and Collaboration Schema Reference Manual at:
http://docs.sun.com/db/prod/s1msgsrv#hic
You might want to obtain other customized LDAP attributes from the server. For example, an ISP might have a custom LDAP attribute assigned to all users called myuserclass. This attribute could denote different types of users that access services, including Communications Express. Possible values for this attribute are “regular” and “vip.”
Before adding custom attributes to the directory, ensure that the directory schema supports these new attributes. The global set of schema for Directory Server can be found in the entry named cn=schema.
For more information on extending directory schema, see Sun ONE Directory Server Deployment Guide at:
http://docs.sun.com/db/prod/s1dirsrv#hic
After extending the directory schema, you can add the new attribute to a User or a group entry. To add custom attribute to as User entry you need to modify the entry in servletsconf section using the ldapmodify command. For more information on ldapmodify command, see Sun ONE Directory Server Configuration, Command, and File Reference at:
http://docs.sun.com/db/prod/s1dirsrv#hic
Depending on the type of user (that is, the value of the myuserclass LDAP attribute), different advertisements are presented to the user when they log into Communications Express (Communications Express is customized to display banner advertisement). If the customized client has access to the myuserclass LDAP attribute, the type of user can be determined and the relevant banner advertisement for that user type is displayed.
To obtain other customized LDAP attributes from the server, use configutil to modify the service.http.extrauserldapattrs configuration parameter. The attributes are read-only by default. If the user wants to modify an attribute using the Communications Express code, the attribute needs to be marked read-write by appending the suffix.
The following example assumes the user wants to display banner advertisements depending on the class of the user and that the client program allows the user to edit a link to a home page:
configutil -l -o service.http.extrauserldapattrs -v “myuserclass,homepage:w “ |