Administrator Guide

Integrating Collaboration

This chapter describes the features that let you use Collaboration with the Microsoft Windows desktop, back-end groupware server, and Microsoft Project. This helps users work more efficiently by integrating Collaboration into a single work environment. It includes the following sections:

Integrating Collaboration and the Desktop

This section describes the configuration and administration of Collaboration features that provide integration with the Microsoft Windows desktop. It includes the following sections:

Overview of WebDAV Protocol

Collaboration’s desktop integration features require the Web-Based Document Authoring and Versioning (WebDAV) protocol. WebDAV is an extension to the HTTP protocol. During installation, the Collaboration installer lets you install and configure a WebDAV service.

Configuring Web Folders

Collaboration lets users manage Collaboration documents directly from their desktop using Microsoft Windows Explorer. After mapping a Web folder, users can access, edit, and share documents in an Collaboration project or create new Collaboration projects. The Web Folder Settings page in Collaboration Settings lets users select the projects whose documents they want to access with Microsoft Windows Explorer.

Documents opened through Windows Explorer are automatically opened in edit mode and checked out in Collaboration. This helps users work more efficiently by removing the need to check out and download the document. All security and version control operations are performed by Collaboration.

Adding Activity Rights

To map a Web folder to Collaboration, users must belong to a group that is granted the Bulk Upload to Collaboration activity right. This activity right also lets users employ the Bulk Upload feature.

To add this activity right to a group:

Click the Administration tab.
Select the Activity Manager utility.
Click Bulk Upload to Collaboration.
Click Add Group.
Select the groups you want to have this activity right.
Click OK.
Click Finish.

For more information on managing activity rights, see the Administrator Guide for BEA AquaLogic Interaction.

Using IIS with Web Folders

If you are using the Map a Web Folder feature when the portal is deployed on IIS, you must ensure that the Front Page server extensions are disabled on the IIS Web site where the portal is deployed.

Choose Start | Programs | Administrative Tools | Internet Service Manager.
Right-click on the Web site used by the portal.
Select Properties.
Select the Server Extensions tab.

If you receive a message stating that the server has not been configured to use server extensions, then IIS is configured correctly.

If the Enable authoring checkbox exists, ensure that it is not selected.

Making the Collaboration Office Tools Add-In Installer Available to End Users

The Collaboration Office Tools Add-In lets end users choose from several check-in options and type additional check-in comments. The Add-In dialog appears after users edit and close a document either from WebEdit or within the Web folder on their personal computer.

The Collaboration Office Tools Add-In must be installed on the machine of each user who may want to use the Add-In. WebEdit, however, still functions correctly without the installation of the Add-In. You can either push out the Add-In’s installer to your users or have them download it.

To push out the installer to end users, use the file appropriate to your language:

ALICollaborationOfficeTools.exe (English and other European languages)
ALICollaborationOfficeTools_ja (Japanese)
ALICollaborationOfficeTools_ko (Korean)
ALICollaborationOfficeTools_zh (Chinese)
ALICollaborationOfficeTools_zh-tw (Traditional Chinese)

All .exe files are located in:

install_dir\ptimages\imageserver\plumtree\collab\private\applets

To make the installer available to be downloaded by end users, set the
installOfficeToolsPopUp enabled parameter in config.xml to yes.

Mapping Web Folders

This section describes how to map a Web folder. You should test these procedures before rolling out a production version of Collaboration.

The Map a Web Folder feature allows a user to map a Network Place on their personal computer running Microsoft Windows to the document hierarchy in Collaboration. This allows the user to view the document hierarchy using Windows Explorer. Folders and files on Collaboration appear as directories and files in Explorer.

Note:

Mapped Web folders should not contain Windows folders whose names include the # or : characters. Windows folder names that include these characters appear incorrectly within Collaboration projects.

Note:

When you move a Windows folder within a project subfolder, a Windows dialog prompts you to confirm whether you want to delete the folder. Click Yes. The folder is moved to the desired location, even though a message appears that Windows is unable to delete the folder. This is expected Windows behavior.

To map a Web folder in Windows XP or Windows 2003:

In the portal, click My Account.
Click Collaboration Settings.
Under Settings on the left, click Web Folders.
Copy the URL in the Web Folder Location box.
Open My Network Places on your desktop.
Double-click Add Network Place.

The Add Network Place Wizard appears.

Click Next.
Select Choose another network location.
In the Internet or network address box, paste the URL, then click Next.
If prompted, enter your name and password, then click OK.
In the Type a name for this network place box, type a name, then click Finish.

A new network place is created and Collaboration is mapped on Windows Explorer.

To map a Web Folder in Microsoft Vista:

In the portal, click My Account.
Click Collaboration Settings.
Under Settings on the left, click Web Folders.
Copy the URL in the Web Folder Location box.
Open Map Network Drive on your desktop.
Click Connect to a Web site that you can use to store your documents and pictures.
Click Next.
Select Choose a custom network location, then click Next.
In the Internet or network address box, paste the URL; then click Next.
If prompted, enter your name and password, then click Next.
In the Type a name for this network place box, type a name, then click Next.
Click Finish.

A new network place is created and your Collaboration is mapped on Windows Explorer.

Working with Web Folder Configuration File Settings

This section explains the configuration file settings for the Web Folder feature.

Table 6-1 config.xml Nodes for Web Folder Feature

Node

Description

fullWebDAVAccessToThisServer

Enables or disables the use of WebDAV. Valid values are:

yes: Causes Collaboration to accept WebDAV requests. This is the default.
no: Causes Collaboration to reject WebDAV requests.

requestsAreGatewayed

Enables or disables WebDAV communication between Windows Explorer and Collaboration. Valid values are true and false.

uiDisplaysServerConfigInfo

Controls how Collaboration displays the New | Web Folder dialog in the Documents tab. Valid values are:

yes: Displays the Web Folder dialog box. This is the default.
no: Does not display the Web Folder dialog box.

useNonGatewayedURL

Determines whether the Web Folder dialog box displays instructions for mapping a gatewayed network drive.

Valid values are:

no: Cause the Web Folder dialog to display information for mapping between Windows Explorer and Collaboration through the gateway. This is the default.

yes: Causes the Web Folder dialog to display information for mapping directly between Windows Explorer and Collaboration.

Note:

If the connection between Windows Explorer and Collaboration is gatewayed, this instance of Collaboration continues to function as the WebDAV service. Therefore, this instance of config.xml must have fullWebDAVAccessToThisServer.enabled set to true and fullWebDAVAccessToThisServer.requestsAreGatewayed set to true.

serverURL

Provides the base URL to Collaboration that acts as the WebDAV service if Collaboration is configured to communicate directly with Windows Explorer.

Following is an example of the Web Folder section of config.xml:

<webDAV>

  <fullWebDAVAccessToThisServer enabled="yes">

    <requestsAreGatewayed>false</requestsAreGatewayed>

  </fullWebDAVAccessToThisServer>

  <uiDisplaysServerConfigInfo enabled="yes">

    <useNonGatewayedURL enabled="yes">

      <serverURL>http://server.yourco.com:8080/collabserver</serverURL>

    </useNonGatewayedURL>

  </uiDisplaysServerConfigInfo>

</webDAV>

Configuring WebEdit

WebEdit lets Collaboration users directly edit Microsoft Office documents on their desktop. Users can edit a document directly without having to explicitly check out and download the document to their machine. Collaboration handles the process of checkouts and security.

Users must be running Microsoft Internet Explorer 6.0 or later. The following types of documents are supported by WebEdit:

Microsoft Word
Microsoft Excel
Microsoft Office
Microsoft PowerPoint

Using IIS with WebEdit

If you are using the WebEdit feature when the portal is deployed on IIS, you must ensure the Front Page server extensions are disabled on the IIS Web site where the portal is deployed.

Choose Start | Programs | Administrative Tools | Internet Service Manager.
Right-click on the Web site used by the portal.
Select Properties.
Select the Server Extensions tab.

If you receive a message stating that the server has not been configured to use server extensions, then IIS is configured correctly.

If the Enable authoring checkbox exists, ensure that it is not checked.

Working with WebEdit Configuration File Settings

This section explains the configuration file settings for the WebEdit feature.

config.xml

The following nodes and attributes are located in config.xml.

Table 6-2 config.xml Nodes for WebEdit Feature

Node or Attribute

Description

webEdit

Enables or disables WebEdit. Valid values are yes and no.

nonGatewayedAccess

Determines if HTTP communication between Microsoft Office and Collaboration is gatewayed through the portal. Valid values are:

yes: HTTP communication is gatewayed through the portal. This is the default.

no: HTTP communication is not gatewayed through the portal.

serverURL

The base URL Microsoft Word uses to communicate with Collaboration. This attribute is used if enable is set to true.

Example: http://collab.myco.com:8080/collabserver

tokenBasedAuthentication

Determines if token-based authentication is used. In a normal Collaboration implementation, there is no need to change these values. Valid values are:

true: Enables token-based authentication. This is the default.

false: Disables token-based authentication. This setting can only be used when HTTP communication is gatewayed and some other authentication method is being used.

useClustering

Controls the use of message clustering (also known as load balancing) with token-based authentication. Valid values are:

yes: Enables message clustering. This is the default.

no: Disables message clustering. This setting should only be used when message clustering is not required and would degrade performance.

Note:

This setting has no effect if general clustering functionality has been disabled for Collaboration. Therefore we recommend that you enable useClustering at all times.

maxWaitSeconds

Determines how long Collaboration waits for a response from other servers in the cluster. This setting is applicable only if token-based authentication and message clustering/load balancing are enabled.

Default: 30

truncateFileNames

The number of characters that are allowed in the file name displayed in WebDAV before the characters are truncated.

clsid

Specifies the class ID of the COM object.

Note:

This value should not be modified.

fileSpec

Specifies the name of the distribution file and information about the component.

Note:

This value should not be modified unless a more recent version of the object needs to be deployed.

installOfficeToolsPopUp enabled

Enables or disables the Collaboration Office Tools Add-In installer. Valid values are yes and no.

Following is an example of the WebEdit section of config.xml:

<webEdit enabled="yes">

  <nonGatewayedAccess enabled="no">

    <serverURL>@WEB_EDIT_COLLAB_SERVER_BASE_URL@</serverURL>

  </nonGatewayedAccess>

  <tokenBasedAuthentication enabled="true">

    <useClustering enabled="yes">

      <MaxWaitSeconds>30</maxWaitSeconds>

    </useClustering>

  </tokenBasedAuthentication>

  <truncateFileNames>75</truncateFileNames>

  <clientControl>

    <clsid>68473829-414C-A45B-ABEE249E704A</clsid>

    <fileSpec>PTCollabWebEditControl.CAB#version=1,0,0,0</fileSpec>

  <clientControl>

<installOfficeToolsPopUp enabled="yes" />

</webEdit>

filetypes.xml

The following configuration nodes and attributes are located in filetypes.xml:

Table 6-3 filetypes.xml Nodes
Node or Attribute	Description
webEdit	Specifies whether this type of file is WebEditable. Unless serious modifications are made to the code, only Microsoft Office applications are WebEditable. Valid values are yes and no.
appCode	Represents the application that opens the document in a WebEdit session. Valid values are: 1 (for Microsoft Word) 2 (for Micrsoft Excel) 3 (for Micrsoft PowerPoint)

Following is an example of the WebEdit section of filetypes.xml:

<webEdit enabled="yes">

  <appCode>1</appCode>

</webEdit>

Integrating Collaboration and Groupware

Collaboration lets you integrate back-end groupware servers. The Groupware Integration feature lets users:

Access items on a groupware calendar using the My Calendar portlet.
Create appointments and meeting requests.
Synchronize a Collaboration calendar with a groupware calendar.

Note:

Groupware Integration is not necessary for users to employ the Email a Project feature. For more information about the Email a Project feature, see Configuring Email a Project. Additionally, the AquaLogic Notification Service, which is used to generate and send email notifications from projects to users, is not required to employ Groupware Integration capabilities (however, if the AquaLogic Notification Service is not running the Email a Project feature is less useful).

Back-end groupware connections are configured by Collaboration administrators. If no groupware server is configured, no Groupware Integration functionality is available to end users.

The following groupware servers are supported:

Microsoft Exchange 2000 SP3 and above
Microsoft Exchange 2003
Lotus Domino 5.0.11

Performing Basic Groupware Integration Tasks

This section describes the basic configuration required for enabling groupware integration. Groupware integration tasks include the following procedures:

This section describes how to enable groupware integration and set up user accounts. See Configuring Groupware Servers for details on configuring groupware servers.

Enabling Groupware Integration

This section describes how to use the Configuration Manager to enable groupware integration.

Note:

Groupware integration is disabled by default. Do not enable groupware integration until you have configured your back-end servers. This prevents the integration-related graphical user interface elements from appearing to end users.

To enable groupware integration:

Launch the Configuration Manager.
In the application list on the left, under Collaboration, click Groupware.
Under Enable Groupware with Collaboration, select Enabled.
Under General Groupware, select the type of groupware server you are using.
In the Server URL box, type the SOAP Server URL of the groupware server.
Click SAVE.

For more information on these fields and config.xml, see Working With Auto-Synchronization.

Setting Up User Accounts for Groupware Integration

In order to use groupware integration, each user must perform the following steps to configure their account:

Log in to the portal.
Click My Account.
Click Collaboration Settings.
Click Calendar Synchronization.
Enter the required account information.
Click Finish.

Working With Auto-Synchronization

Collaboration can perform automatic synchronization between groupware and Collaboration calendars for individual users. When groupware appointments are imported or calendar items are exported, Collaboration creates a link between them and updates the entries on the groupware server if they are different from the Collaboration calendar entries.

Users can manually synchronize the groupware and calendar entries using the Synchronize button on the calendar toolbar. Collaboration administrators can also enable automatic synchronization by setting the calendarAutoSynch element to yes. After this feature is enabled, users can specify which calendar items are auto-synchronized from the My Account page.

When automatic synchronization is enabled, Collaboration runs a nightly process to update the specified entries for each user.

Note:

For Microsoft Exchange, the speed at which users’ free/busy information is updated to the groupware server and made available to the Collaboration calendars is dependent on the interval that the user sets in their Microsoft Exchange calendar’s free/busy options.

Limiting Attachment Size

Collaboration administrators can set a size limit on the attachments each appointment or meeting request can have. This limit applies to the total size of all attachments, not individual attachments. When the total size of the attachments exceeds the size limit, a warning is displayed and the upload process is canceled.

Working with Groupware Integration Configuration File Settings

This section describes the settings for groupware integration contained in config.xml. Enable or disable groupware integration and configure groupware server settings using the Configuration Manager.

Table 6-4 config.xml Nodes for Groupware Integration

Node or Attribute

Description

timeoutInMilliSecond

Specifies the amount of time, in milliseconds, that Collaboration waits for responses from the SOAP server. If the SOAP server does not respond in this amount of time, the current operation is aborted and an exception is returned.

Note:

Due to the performance constraints and the fact that large attachments might be transferred between Collaboration via Exchange, the attribute should be set to a value greater than 10000 (10 seconds).

calendarCachePeriod

Specifies the cache time-out period, in seconds, for groupware items on the My Calendar portlet. When the My Calendar portlet is refreshed, Collaboration checks if the current items have timed out. If they have, Collaboration retrieves the entries from the back-end server. Otherwise, the entries are retrieved from memory.

addressBookReturn

The maximum number of returned addresses from the address search operation.

maxAttachmentSizeinKB

The maximum attachment file size, in kilobytes, that a meeting request or appointment can contain.

Note:

This limit is the total file size of all attachments an item can have.

calendarAutoSynch

The following values are supported:

yes: Enables automatic synchronization between a user’s project calendar and their Exchange or Notes calendar.

no: Disables automatic synchronization between a user’s project calendar and their Exchange or Notes calendar.

month.Range

The range of months auto-synchronization covers, starting from the current month.

This node is used to configure settings to let users send an email directly to a project from their groupware.

Following is an example of the groupware integration section of config.xml:

<groupware enabled="yes" type="exchange">

  <soapServerURL timeoutInMiliSecond="10000">http://server. mycompany.com/GroupwareService/GroupwareService.asmx</soapServerURL>

  <calendarCachePeriod>600</calendarCachePeriod>

  <addressBookReturn>50</addressBookReturn>

  <maxAttachmentSizeinKB>2048</maxAttachmentSizeinKB>

  <calendarAutoSynch enabled="yes">

    <monthRange>2</monthRange>

Integrating Collaboration and Instant Messaging

The Instant Messaging feature allows users who have been assigned the Ability to View Instant Messaging Presence activity right to see which project collaborators are currently logged in to their Yahoo! Instant Messaging client. For details on assigning activity rights to users, see Granting Activity Rights to Users.

To integrate Yahoo! Instant Messaging with Collaboration complete the following procedures:

Enabling Instant Messaging Integration

This section describes how to use the Configuration Manager to enable instant messaging integration.

To enable instant messenger integration:

Launch the Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under Enable Instant Messaging, select Enabled.
Click SAVE.

Configuring Instant Messaging in config.xml

This section describes the configuration file settings for instant messaging integration in config.xml.

Table 6-5 config.xml Nodes for Instant Messaging Integration
Node or Attribute	Description
presence-url	This node returns an image to indicate whether the user is online or not.
send-url	This node includes the URL from which messages are sent. The $user variable includes the email address of the individual user.
contact-url	This node includes the URL at which messages can be received. The $user variable includes the email address of the individual user.
presence-poll-interval	This node includes the number of seconds between presence polls.

Setting Up the IM Handle Property

If your users are required to have an IM handle value that is different than their email address, follow this procedure to create the IM Handle property and add the property to the portal’s General Information page for each user profile. After you have added this property, you can add each user’s IM handle to their user profile; you can also have each user perform this task on their own.

Log in to the portal as the Administrator.
Navigate to Administration | Administrative Resources Folder. Then, from the Create Object drop-down list, choose Property.
On the Main Settings page, leave the default values and selections.
Click Finish.

The Save Object dialog box appears.

Make sure that the Administrative Resources folder is selected and name the object IM Handle.
Click Save.
Click Close.
You are returned to the Administrative Resources folder.
From the Select Utility drop-down list, choose Global Object Property Map.
On the Main Page, click Edit for the User object.
In the Choose Property dialog box, select the IM Handle property, then click OK.

You are returned to the Main Page.

Click Finish.
From the Select Utility drop-down list, choose User Profile Manager.
Under Edit Object Settings, click the User Information - Property Map link.
If the IMUser user information attribute is assigned to the Email Address property, perform the following in sequence:

Click Edit for the property.
Delete IMUser, along with the comma that precedes it.

Do not delete any other user information attributes that are assigned to the Email Address property.

Click Edit for the Email Address property to return it to a non-editable state.

Click Add.
In the Choose Property dialog box, select the IM Handle property, then click OK.

You are returned to the User Information - Property Map page.

Click Edit for the IM Handle property.
Delete IMHandle, then replace it with IMUser.
Click Edit for the IM Handle property to return it to a non-editable state.
Click Finish.
Navigate to Administration | Portal Resources Folder.
Click the Portlet link.
Click the General Information portlet link.
In the Edit Portlet: General Information page, click Edit.

The User Profile Portlet Configuration dialog box appears.

Click Add Property.
Select the IM Handle property name, then click OK.

You are returned to the User Profile Portlet Configuration dialog box.

Click Finish.

You are returned to the Edit Portlet: General Information page.

Click Finish.

You are returned to the Portal Resources Folder. The IM Handle property is added to the portal’s user profile, General Information page.

Integrating Collaboration and AquaLogic BPM

Collaboration can be integrated with AquaLogic BPM, allowing users to attach a Collaboration document to a WorkSpace process instance and then initiate the process from the document in the Collaboration UI.

To enable AquaLogic BPM integration:

Launch the AquaLogic Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under Enable ALBPM Integration, select Enabled.
Click SAVE.

The following table describes the nodes in config.xml that are used to enable integration with AquaLogic BPM:

Table 6-6 config.xml nodes for AquaLogic BPM Workspace Extensions integration
Node or Attribute	Description
ALIPIntegration enabled	This node is used to enable integration with AquaLogic BPM. Valid values are yes and no.
processPortletUUID	The UUID for the Process - Application portlet. By default, the value is E1F1B56E-0563-4397-9544-223AD1885C16. You do not need to change this value. Only users with access to the Process - Application portlet are able to use the Initiate Process feature in Collaboration.
requestTimeoutInMilliSecond	Specifies the amount of time, in milliseconds, that Collaboration waits to receive the names of available processes from AquaLogic BPM. If Collaboration does not receive these names in the specified amount of time, Collaboration stops waiting for process names. By default, the value is 60000 (60 seconds).

Integrating Collaboration and AquaLogic Pathways

Collaboration can be integrated with AquaLogic Pathways, allowing users with the Access Pathways activity right to apply Pathways tags to Collaboration objects so that they can be searched on and accessed from within the Pathways UI.

To enable Pathways integration:

Launch the AquaLogic Configuration Manager.
In the application list on the left, under Collaboration, click Pathways.
Under Enable Pathways, select Enabled.
Under Pathways Communication, type the URL to Pathways in the Pathways URL text box:

From the Pathways Items or Pathways Users portlet click Display in Pathways.
Copy URL from the Address field of the browser.
Paste the URL in the Pathways URL text box.

Click SAVE.

Integrating Collaboration and AquaLogic Interaction Analytics

Collaboration can be integrated with AquaLogic Interaction Analytics to send events to Analytics as a user is browsing and using Collaboration. This allows Analytics to have an accurate event data collection at any given time.

To enable Analytics integration:

Launch the AquaLogic Configuration Manager.
In the application list on the left, under Collaboration, click Analytics.
Under Enable Analytics, select Enabled.
Click SAVE.

For instructions on using the OpenUsage API to send Collaboration events to Analytics, see Using the AquaLogic Interaction Analytics 2.0 OpenUsage API on the BEA dev2dev site.

Configuring Microsoft Project Import

The following configuration parameters can be set to customize Microsoft Project imports:

Table 6-7 Configuration Parameters for Customizing Microsoft Project Imports
Node or Attribute	Description
project-import	Contains parameters that are specific to Microsoft Project import.
number-of-tasks-limit	The total number of tasks allowed in an import. The default is 1000.

Configuring Email a Project

This section describes how to configure the Email a Project feature. The Email a Project feature lets users:

Email a message to a discussion within a project.
Email a document to a folder within a project.
Reply to a message post notification.

This section discusses the following:

The “Relaying Email to Collaboration” section provides an example of configuring sendmail on a Linux machine that is also running Collaboration. You can use this example as a guideline for configuring your mail host if it is running on the same machine as Collaboration.

Note:

Groupware Integration is not necessary for users to employ the Email a Project feature. Groupware Integration is only necessary if users want to employ the capabilities that are described in Integrating Collaboration and Groupware. Additionally, the Notification Service -- which is used to generate and send email notifications from projects to users -- is not required to employ the Email a Project feature. However the Email a Project feature is less useful if the Notification Service is not running.

Performing a Basic Configuration

This section discusses how to configure Email a Project if you are running your mail host and Collaboration on separate machines.

To configure Collaboration to use the Email a Project feature:

An IT or network operations employee at your organization needs to add a DNS MX (mail exchange) record that points to Collaboration.
The users’ email address must be registered in their portal user profile.

Either the administrator or user can perform this task. The email address in the portal user profile must exactly match the user’s email address; this is case-sensitive.

(Optional) If you do not want to use the default values, you can configure the following nodes in the email section of config.xml:

Table 6-8 config.xml Nodes for Email a Project Configuration
Node	Description
domain	The email domain. For example: mail.buttercut.plumimap.com Most likely, you configured this node when you ran the Collaboration Installer.
connection-pool	The number of socket handlers for incoming connections. The default value is 10.
mail-processors	The number of threads devoted to processing incoming emails. The default value is 5.
maximum-message-size	The maximum size of incoming emails. -1 indicates that Collaboration does not perform size checks. When this is the case, the Collaboration API enforces size limits for message bodies and files. The default value is -1.
authorized-connections	The names or IP addresses of hosts, in a comma-delimited format, that are allowed to connect to the SMTP handler. We recommend creating this list of names to enforce security. See the config.xml file for an example of this list. The default value is *, which indicates no limit.
idle-timeout	The time (in minutes) that an incoming connection can remain idle. The default value is 20.

Following is an example of the email section in config.xml:

- <email enabled="@EMAIL_ENABLED@" port="25">

<domain>@EMAIL_DOMAIN@</domain>

<connection-pool>10</connection-pool>

<mail-processors>5</mail-processors>

<maximum-message-size>-1</maximum-message-size>

  <authorized-connections>*</authorized-connections>

<idle-timeout>20</idle-timeout>

Example: Relaying Email to Collaboration

If you are running your email host on the same machine as Collaboration, you need to configure your email host to relay email to Collaboration. This section provides an example of configuring sendmail to relay email to Collaboration, which you can use as a guideline for configuring your own email host.

In this example, Collaboration uses port 2525 (by default, Collaboration uses port 25, which is the same port that sendmail uses. For this reason, Collaboration’s port must be changed.)

Note:

The steps that are required for you to set up your email host to relay mail to Collaboration may differ than the example, depending on your production environment.

Prerequisites

These prerequisites provide an example of the tasks that should be completed before configuring sendmail.

The sendmail-cf rpm package must be installed. To determine if it is installed, run the following as root:

rpm -qa | grep sendmail

The return should appear as follows:

sendmail-8.12.11-4.RHEL3.1

sendmail-cf-8.12.11-4.RHEL3.1

Create a subzone/subdomain under your current domain. For example, collabmail.yourcompany.com.
Create a host entry that points to your Collaboration server.

MX    10    mail.collabmail.yourcompany.com

Create a MX (mail exchange) record so that anything that gets sent to *@collabmail.yourcompany.com goes to the host record that you just created:

MX    10    mail.collabmail.yourcompany.com

The value 10 in the above example represents the priority that allows you to have more MX records. It assures that emails go to the higher priority first.

Note:

An alternative to Step 2 (above) is to specify mx 10 X.X.X.X under your subzone.

Configuring Sendmail

These instructions provide an example for configuring sendmail to relay incoming mail to Collaboration:

Log in as root.
Stop the sendmail processes:

/etc/rc.d/init.d/kudzu stop

/etc/rc.d/init.d/sendmail stop

/etc/rc.d/init.d/apmd stop

Verify file “relay-domains” is in etc/mail.

Add your domain:

[machine].[yourimap].com

For example, collab-x5.plumimap.com.

Edit the etc/mail/access file.

Add the following to the access file:

To: [machine].[yourimap].com    RELAY

To: collab-x5.plumimap.com       RELAY

From your terminal, rehash to update the access.db file:

/usr/sbin/makemap hash /etc/mail/access.db < /etc/mail/access

Edit the sendmail.mc file to relay emails to Collaboration using a different port.

/etc/mail/sendmail.mc

Add the following before the MAILER lines at end of the file:

FEATURE(`mailertable')

define(`confRELAY_MAILER', `esmtp')

define(`RELAY_MAILER_ARGS', `TCP $h 2525')

Look for the following line in the file:

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Comment the above line out so that it appears as follows:

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

In your terminal, type the following:

m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf

Edit the mailertable file as follows.

/etc/mail/mailertable

Add the following to the mailertable file:

[machine].[yourimap].com    relay:mail.[machine].[yourimap].com

For example:

Collab-x5.plumimap.com  relay:mail.[machine].plumimap.com

Then rehash to update the mailertable.db file by typing the following in your terminal:

/usr/sbin/makemap hash /etc/mail/mailertable.db < /etc/mail/mailertable

Start sendmail as follows:

/etc/rc.d/init.d/apmd start

/etc/rc.d/init.d/sendmail start

/etc/rc.d/init.d/kudzu start

Edit the Collaboration config.xml file to enable email and to use port 2525:

email enabled="yes" port="2525”

Restart Collaboration.

The collaboration.log file should show the Email Service has started on port 2525 with no errors.

A Telnet to the machine port should return something similar to the following:

220 Collaboration 4.5 Build:198844.20050824 0720.0 SMTP Server (Messaging Server) ready Wed, 24 Aug 2005 14:50:36 -0700 (PDT)

Working With Collaboration Email Errors

If an error occurs when a user sends an email to a Collaboration project:

Collaboration rejects the email and does not reply with an error notification if it cannot verify:

The identification of the user who sent the email.
The format of the email address.

Collaboration replies with an error notification if it is able to verify:

The identification of the user who sent the email.
The format of the email address.

If Collaboration is down, the mail server queues the email and attempts redelivery a few times before quitting. Collaboration sends an error email to the user who sent the email, then redelivers the email when Collaboration is back up.