| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration 10g Release 4 (10.3.3.0.0) Part Number E12891-04 |
|
|
View PDF |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration 10g Release 4 (10.3.3.0.0) Part Number E12891-04 |
|
|
View PDF |
This chapter describes the features that let you use Oracle WebCenter Collaboration with other Oracle and third-party products, helping users work more efficiently by integrating these products into a single work environment.
It includes the following sections:
Making the Collaboration Office Tools Add-In Installer Available to End Users
Integrating Oracle WebCenter Collaboration and Instant Messaging
Integrating Oracle WebCenter Collaboration and Oracle WebCenter Analytics
Integrating Oracle WebCenter Collaboration and Oracle Business Process Management
Integrating Oracle WebCenter Collaboration and the Tagging Engine
Integrating Oracle WebCenter Collaboration and Oracle Universal Content Management
This section describes the configuration and administration of Oracle WebCenter Collaboration features that provide integration with the Microsoft Windows desktop. It includes the following sections:
Oracle WebCenter 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 Oracle WebCenter Collaboration installer lets you install and configure a WebDAV service.
Oracle WebCenter Collaboration lets users manage Oracle WebCenter Collaboration documents directly from their desktop using Microsoft Windows Explorer. After mapping a Web folder, users can access, edit, and share documents in an Oracle WebCenter Collaboration project or create new Oracle WebCenter 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 Oracle WebCenter Collaboration. This helps users work more efficiently by removing the must check out and download the document. All security and version control operations are performed by Oracle WebCenter Collaboration.
To configure the Web folders, perform the following steps:
This step is necessary only if you are using IIS.
To map a Web folder to Oracle WebCenter 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.
From the Select Utilities menu, select Activity Manager.
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 Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.
If you are using the Map a Web Folder feature when the portal is deployed on IIS, you must ensure that the FrontPage server extensions are disabled (if they are installed) and that WebDAV is prohibited on the IIS Web site where the portal is deployed.
In Windows, from the Start menu, select All Programs, Administrative Tools, Internet Information Services.
In the navigation tree, display the local computer list, then display the Web sites list.
Right-click the Web site used by the portal.
Select Properties.
If you have installed the FrontPage Server Extensions you see the Server Extensions tab. Click the tab and ensure that the Enable authoring check box is not selected. If it is selected, clear the check box. Click OK to close the properties dialog box.
Note:
If you did not install the optional FrontPage Server Extensions when you installed IIS, the Server Extensions tab does not appear.
In the local computer tree, select Web Service Extensions.
In the Web Service Extensions pane, select WebDAV, then click Prohibit.
When the Office Task Pane feature is enabled, clicking the WebEdit button lets users access key Oracle WebCenter Collaboration project features directly from their Microsoft Office documents. For more detailed end user information, see Oracle WebCenter Collaboration Online Help.
Note:
When the Office task Pane is enabled, some of its features are not functional because they do not serve a purpose in Oracle WebCenter Collaboration. Due to compatibility issues between Oracle and Microsoft products, some non-functioning features are grayed out, while others can be clicked on but serve no purpose.
To configure the Office Task Pane feature, you must perform the following:
Ensuring that the Office Task Pane Feature is Enabled in Oracle WebCenter Configuration Manager
Configuring Your Application Server for Office Task Pane Integration
By default, the Office Task Pane is disabled in Oracle WebCenter Configuration Manager. To ensure that the Office Task Pane feature is enabled, launch Oracle WebCenter Configuration Manager. If you change the setting, restart Collaboration.
Launch Oracle WebCenter Configuration Manager.
Click Collaboration, then Collaboration Settings.
Under Enable Office Task Pane for WebEdit, ensure that Enabled is selected.
Perform the procedure that is appropriate to your application server:
To configure Tomcat to work with the Office Task Pane, you must specify the root web application on Tomcat. To do so:
On the computer on which Oracle WebCenter Interaction is installed, stop Tomcat.
On the computer on which Oracle WebCenter Interaction is installed, navigate to the directory to which Tomcat is installed, then open the webapps directory.
If a directory named ROOT exists in the webapps directory, rename the folder to a different name.
Navigate to:
For Microsoft Windows: install_dir\ptcollab\10.3.3\rootwebapp\java
For UNIX/Linux: install_dir/ptcollab/10.3.3/rootwebapp/java
Copy the root.war file.
On the computer on which Oracle WebCenter Interaction is installed, paste the root.war file into the webapps directory, which is in the same directory into which Tomcat is installed.
Restart Tomcat.
To configure Oracle WebLogic Server to work with the Office Task Pane, you must specify the root web application on Oracle WebLogic Server. To do so:
On the computer on which Oracle WebCenter Collaboration is installed, navigate to:
For Microsoft Windows: install_dir\ptcollab\10.3.3\rootwebapp\java
For UNIX/Linux: install_dir/ptcollab/10.3.3/rootwebapp/java
Copy the root.ear file.
On the computer on which Oracle WebCenter Interaction is installed, paste the root.ear file into the following directory:
For Microsoft Windows: install_dir\ptportal\10.3.3\webapp
For UNIX/Linux: install_dir/ptportal/10.3.3/webapp
This should be the same directory that contains the portal.war file
Deploy the root.ear file.
Restart the portal.
To configure IIS 6 to work with the Office Task Pane feature:
In Windows, from the Start menu, select All Programs, Administrative Tools, Internet Information Services.
In Internet Information Services (IIS) Manager, stop the Web site that contains the portal virtual directory.
Access the Web site's properties and click the Documents tab.
Ensure that the Enable default content page option is selected.
On the Home Directory tab, change the application name to Root.
Click the Configuration button.
The Mappings tab appears.
Click the Insert button.
In the Add/Edit Application Extension Mapping dialog box, click Browse.
Browse to and open the aspnet_isapi.dll file, located at: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
You are returned to the Add/Edit Application Extension Mapping page.
Ensure that the Verify that file exists option is not selected.
Click OK to close the Add/Edit Application Extension Mapping dialog box.
Click OK to close the Application Configuration dialog box.
If the Inheritance Overrides dialog box appears, do not select any options, then click OK.
Click OK to close the Web site properties dialog box.
In Windows Explorer, navigate to install_dir/ptcollab/version/rootwebapp/.net, then copy the following:
Web.config
Default.htm
The bin directory
In IIS, right-click the portal Web site (with the globe and hand icon) and choose Open.
The portal Web site explorer window appears.
Paste the files you copied in Step 14 into the top level of the portal Web site explorer window.
The path should be one of the following, depending on the option that was chosen when Oracle WebCenter Interaction was installed:
If Oracle WebCenter Interaction was installed into the default Web site, the path is C:\inetpub\wwwroot.
If Oracle WebCenter Interaction was installed into a nondefault Web site, the path is install_dir\iisweb\Root.
In IIS, right-click the portal virtual directory (with the gear icon) and choose Open.
In the portal virtual directory explorer window, open the Web.config file in a text editor.
The Web.config file should be located in the following path: install_dir/ptportal/version/webapp/portal/web.
In the <httpHandlers> section of the Web.config file, add the line <clear/> in between the lines <httpHandlers> and <add verb="*" path="*.pt", so that the code appears like the following:
<httpHandlers>
<clear/>
<add verb="*" path="*.pt"
Save and close the Web.config file.
Restart IIS.
After IIS is restarted, ensure that the Web site that contains the portal is started.
Note:
Desktop integration will not work if the Microsoft WebDAV service in IIS has been enabled.
To configure IIS 7 to work with the Office Task Pane feature:
In Windows, from the Start menu, select All Programs, Administrative Tools, Internet Information Services.
In Internet Information Services (IIS) Manager, stop the Web site that contains the portal virtual directory.
In IIS Manager, click the default web site where the portal is installed, then, in the Actions pane, click Explore. Windows Explorer opens, displaying the portal installation directory.
In Windows Explorer, navigate to install_dir/ptcollab/version/rootwebapp/.net, then copy the following:
Web.config
Default.htm
The bin directory
In IIS, right-click the portal Web site (with the globe and hand icon) and choose Open.
The portal Web site explorer window appears.
Paste the files you copied in Step 14 into the top level of the portal Web site explorer window.
The path should be one of the following, depending on the option that was chosen when Oracle WebCenter Interaction was installed:
If Oracle WebCenter Interaction was installed into the default Web site, the path is C:\inetpub\wwwroot.
If Oracle WebCenter Interaction was installed into a nondefault Web site, the path is install_dir\iisweb\Root.
In IIS, right-click the portal virtual directory (with the gear icon) and choose Open.
In the portal virtual directory explorer window, open the Web.config file in a text editor.
The Web.config file should be located in the following path: install_dir/ptportal/version/webapp/portal/web.
In the <httpHandlers> section of the Web.config file, add the line <clear/> in between the lines <httpHandlers> and <add verb="*" path="*.pt", so that the code appears like the following:
<httpHandlers>
<clear/>
<add verb="*" path="*.pt"
Save and close the Web.config file.
Restart IIS.
After IIS is restarted, ensure that the Web site that contains the portal is started.
Note:
Desktop integration will not work if the Microsoft WebDAV service in IIS has been enabled.
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 computer 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:
Microsoft Windows: install_dir\ptimages\imageserver\plumtree\collab\private\applets
UNIX and Linux: 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.
This section describes how to map a Web folder. You should test these procedures before rolling out a production version of Oracle WebCenter 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 Oracle WebCenter Collaboration. This allows the user to view the document hierarchy using Windows Explorer. Folders and files on Oracle WebCenter 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 Oracle WebCenter 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 cannot 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 Oracle WebCenter 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 Oracle WebCenter Collaboration is mapped on Windows Explorer.
Table 5-1 describes the settings for web folder feature contained in config.xml under webDAV.
Table 5-1 Configuration Parameters for Web Folder Feature
| Parameter | Description |
|---|---|
|
fullWebDAVAccessToThisServer |
Enables or disables the use of WebDAV. Valid values are: yes: Causes Oracle WebCenter Collaboration to accept WebDAV requests. This is the default. no: Causes Oracle WebCenter Collaboration to reject WebDAV requests. |
|
requestsAreGatewayed |
Enables or disables WebDAV communication between Windows Explorer and Oracle WebCenter Collaboration. Valid values are true and false. |
|
fuiDisplaysServerConfigInfo |
Controls how Oracle WebCenter Collaboration displays the New, then 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 Oracle WebCenter Collaboration through the gateway. This is the default. yes: Causes the Web Folder dialog to display information for mapping directly between Windows Explorer and Oracle WebCenter Collaboration. Note: If the connection between Windows Explorer and Oracle WebCenter Collaboration is gatewayed, this instance of Oracle WebCenter 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 Oracle WebCenter Collaboration that acts as the WebDAV service if Oracle WebCenter Collaboration is configured to communicate directly with Windows Explorer. |
WebEdit lets Oracle WebCenter 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 computer. Oracle WebCenter Collaboration handles the process of checkouts and security.
Users must be running Microsoft Internet Explorer 6.0 or above.
When the Office Task Pane feature is enabled, clicking the WebEdit button lets users access key Oracle WebCenter Collaboration project features directly from their Microsoft Office documents. For more detailed end user information, see Oracle WebCenter Collaboration Online Help. For configuration information, see Configuring the Office Task Pane Feature.
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.
In Windows, from the Start menu, select All Programs, Administrative Tools, Internet Information Services.
Right-click 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 check box exists, ensure that it is not checked.
Table 5-2 describes the settings for the WebEdit feature contained in config.xml under webEdit.
Table 5-2 Configuration Parameters for the WebEdit Feature in config.xml
| Parameter | Description |
|---|---|
|
webEdit |
Enables or disables WebEdit. Valid values are yes and no. |
|
nonGatewayedAccess |
Determines if HTTP communication between Microsoft Office and Oracle WebCenter 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 Oracle WebCenter 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 Oracle WebCenter Collaboration implementation, there is no must 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 Oracle WebCenter Collaboration. Therefore we recommend that you always enable useClustering. |
|
maxWaitSeconds |
Determines how long Oracle WebCenter 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. |
Table 5-3 describes the settings for the WebEdit feature contained in filetypes.xml under webEdit.
Table 5-3 Configuration Parameters for the WebEdit Feature in filetypes.xml
| Parameter | 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:
|
Oracle WebCenter 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 an Oracle WebCenter Collaboration calendar with a groupware calendar.
Note:
Groupware Integration is not necessary for users to employ the E-mail a Project feature. For more information about the E-mail a Project feature, see Configuring the E-mail a Project Feature. Additionally, the Notification Service, which is used to generate and send e-mail notifications from projects to users, is not required to employ Groupware Integration capabilities (however, if the Notification Service is not running the E-mail a Project feature is less useful).
Back-end groupware connections are configured by Oracle WebCenter 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
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.
This section describes how to use Oracle WebCenter 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 Oracle WebCenter 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.
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.
Oracle WebCenter Collaboration can perform automatic synchronization between groupware and Oracle WebCenter Collaboration calendars for individual users. When groupware appointments are imported or calendar items are exported, Oracle WebCenter Collaboration creates a link between them and updates the entries on the groupware server if they are different from the Oracle WebCenter Collaboration calendar entries.
Users can manually synchronize the groupware and calendar entries using the Synchronize button on the calendar toolbar. Oracle WebCenter 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, Oracle WebCenter 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 Oracle WebCenter Collaboration calendars is dependent on the interval that the user sets in their Microsoft Exchange calendar's free/busy options.
Oracle WebCenter 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.
Table 5-4 describes the settings for groupware integration contained in config.xml under groupware. Enable or disable groupware integration and configure groupware server settings using Oracle WebCenter Configuration Manager.
Table 5-4 Configuration Parameters for Groupware Integration
| Parameter | Description |
|---|---|
|
timeoutInMilliSecond |
The amount of time, in milliseconds, that Oracle WebCenter 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 Oracle WebCenter Collaboration through Exchange, the attribute should be set to a value greater than 10000 (10 seconds). |
|
calendarCachePeriod |
The cache time-out period, in seconds, for groupware items on the My Calendar portlet. When the My Calendar portlet is refreshed, Oracle WebCenter Collaboration checks if the current items have timed out. If they have, Oracle WebCenter 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. |
|
monthRange |
The range of months auto-synchronization covers, starting from the current month. |
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 Oracle WebCenter Collaboration complete the following procedures:
This section describes how to use Oracle WebCenter Configuration Manager to enable instant messaging integration.
To enable instant messenger integration:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under Enable Instant Messaging, select Enabled.
Click Save.
Table 5-5 describes the settings for instant messaging integration contained in config.xml under instant-messaging.
Table 5-5 Configuration Parameters for Instant Messaging Integration
| Parameter | Description |
|---|---|
|
presence-url |
Returns an image to indicate whether the user is online or not. |
|
send-url |
The URL from which messages are sent. The $user variable includes the e-mail address of the individual user. |
|
contact-url |
The URL at which messages can be received. The $user variable includes the e-mail address of the individual user. |
|
presence-poll-interval |
The number of seconds between presence polls. |
If your users are required to have an IM handle value that is different than their e-mail 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.
Click Administration.
Open the Administrative Resources folder.
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.
Ensure 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.
Click Administration, Portal Resources, then 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.
Oracle WebCenter Collaboration comes with portlets and a portlet template that enable you to display a Microsoft Excel file from a Collaboration project in the portal interface:
My Excel: can be added to a My Page
Community Excel: can be added to a community page
Global Excel Portlet Template: can be used to create multiple instances of Excel portlets, so that Excel file can be displayed on a My Page or community page
For information on adding an Excel portlet to a page and configuring the portlet to display an Excel file, see the Oracle WebCenter Collaboration online help.
To configure the maximum size of Excel files that can be displayed in a portlet:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under Excel Portlets, configure the following settings:
Maximum Number of Rows: An Excel file that exceeds the maximum number of rows will produce an error and will not be displayed in the portlets. A value of 0 means there is no restriction on the number of rows.
Maximum Number of Columns: An Excel file that exceeds the maximum number of columns will produce an error and will not be displayed in the portlets. A value of 0 means there is no restriction on the number of columns.
Click Save.
Table 5-6 describes the settings for Microsoft Project import contained in config.xml under project-import.
This section describes how to configure the E-mail a Project feature. The E-mail a Project feature lets users:
E-mail a message to a discussion within a project
E-mail a document to a folder within a project
Reply to a message post notification
This section discusses the following:
Enabling the E-mail a Project Feature and Configuring the SMTP Server
Example: Relaying E-mail to Oracle WebCenter Collaboration
This section provides an example of configuring sendmail on a Linux computer that is also running Oracle WebCenter Collaboration. You can use this example as a guideline for configuring your mail host if it is running on the same computer as Oracle WebCenter Collaboration.
Note:
Groupware Integration is not necessary for users to employ the E-mail a Project feature. Groupware Integration is only necessary if users want to employ the capabilities that are described in Integrating Oracle WebCenter Collaboration and Groupware. Additionally, the Notification Service -- which is used to generate and send e-mail notifications from projects to users -- is not required to employ the E-mail a Project feature. However the E-mail a Project feature is less useful if the Notification Service is not running.
This section describes how to use Oracle WebCenter Configuration Manager to enable the E-mail a Project feature and to configure the SMTP server.
To enable the E-mail a Project feature and configure the SMTP server:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under E-mail a Project Settings, select Enabled.
In the SMTP Server box, type the SMTP server to use for the E-mail a Project feature.
Click Save.
This section discusses how to configure E-mail a Project if you run your mail host and Oracle WebCenter Collaboration on separate computers.
To configure Oracle WebCenter Collaboration to use the E-mail a Project feature:
An IT or network operations employee at your organization needs to add a DNS MX (mail exchange) record that points to Oracle WebCenter Collaboration.
The users' e-mail address must be registered in their portal user profile.
Either the administrator or user can perform this task. The e-mail address in the portal user profile must exactly match the user's e-mail address; this is case-sensitive.
(Optional) If you do not want to use the default values, you can configure the following nodes in the e-mail section of config.xml:
Table 5-7 describes the settings for the E-mail a Project feature contained in config.xml under Email Service Settings.
Table 5-7 Configuration Parameters for E-mail a Project Configuration
| Parameter | Description |
|---|---|
|
domain |
The e-mail domain. For example: mail.buttercut.imap.com Most likely, you configured this node when you ran the Oracle WebCenter Collaboration Installer. This parameter can be set only in the Configuration Manager. |
|
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 e-mails. The default value is 5. |
|
maximum-message-size |
The maximum size of incoming e-mails. |
|
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. |
If you run your e-mail host on the same computer as Oracle WebCenter Collaboration, you must configure your e-mail host to relay e-mail to Oracle WebCenter Collaboration. This section provides an example of configuring sendmail to relay e-mail to Oracle WebCenter Collaboration, which you can use as a guideline for configuring your own e-mail host.
In this example, Oracle WebCenter Collaboration uses port 2525 (by default, Oracle WebCenter Collaboration uses port 25, which is the same port that sendmail uses. For this reason, Oracle WebCenter Collaboration's port must be changed.)
Note:
The steps that are required for you to set up your e-mail host to relay mail to Oracle WebCenter Collaboration may differ than the example, depending on your production environment.
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 Oracle WebCenter 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 enables you to have more MX records. It assures that e-mails 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.
These instructions provide an example for configuring sendmail to relay incoming mail to Oracle WebCenter 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:
computer.yourimap.com
For example, collab-x5.plumimap.com.
Edit the etc/mail/access file.
Add the following to the access file:
To: computer.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 e-mails to Oracle WebCenter 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:
computer.yourimap.com relay:mail.computer.yourimap.com
For example:
Collab-x5.plumimap.com relay:mail.computer.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 Oracle WebCenter Collaboration config.xml file to enable e-mail and to use port 2525:
email enabled="yes" port="2525"
Restart Oracle WebCenter Collaboration.
The collaboration.log file should show the E-mail Service has started on port 2525 with no errors.
A Telnet to the computer port should return something similar to the following:
220 Collaboration 10.3.3 Build:198844.20050824 0720.0 SMTP Server (Messaging Server) ready Wed, 24 Aug 2005 14:50:36 -0700 (PDT)
If an error occurs when a user sends an e-mail to an Oracle WebCenter Collaboration project:
Oracle WebCenter Collaboration rejects the e-mail and does not reply with an error notification if it cannot verify:
The identification of the user who sent the e-mail.
The format of the e-mail address.
Oracle WebCenter Collaboration replies with an error notification if it can verify:
The identification of the user who sent the e-mail.
The format of the e-mail address.
If Oracle WebCenter Collaboration is down, the mail server queues the e-mail and attempts redelivery a few times before quitting. Oracle WebCenter Collaboration sends an error e-mail to the user who sent the e-mail, then redelivers the e-mail when Oracle WebCenter Collaboration is back up.
Oracle WebCenter Collaboration can be integrated with Oracle WebCenter Analytics to send events to Oracle WebCenter Analytics as a user is browsing and using Oracle WebCenter Collaboration. This allows Oracle WebCenter Analytics to have an accurate event data collection at any given time.
To enable Oracle WebCenter Analytics integration:
Launch Oracle WebCenter 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 Oracle WebCenter Collaboration events to Oracle WebCenter Analytics, see the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter Analytics on the Oracle Technology Network in the Oracle WebCenter Analytics 10g Release 4 (10.3.3.0.0) documentation set.
Oracle WebCenter Collaboration can be integrated with Oracle Business Process Management, allowing users to attach an Oracle WebCenter Collaboration document to a WorkSpace process instance and then initiate the process from the document in the Oracle WebCenter Collaboration user interface.
To enable Oracle Business Process Management integration:
Launch Oracle WebCenter 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 parameters in config.xml, under ALIPIntegration, that are used to enable integration with Oracle Business Process Management:
Table 5-8 config.xml Parameters for Oracle Business Process Management integration
| Node or Attribute | Description |
|---|---|
|
processPortletUUID |
The UUID for the Process - Application portlet. By default, the value is E1F1B56E-0563-4397-9544-223AD1885C16. You do not must change this value. Only users with access to the Process - Application portlet are able to use the Initiate Process feature in Oracle WebCenter Collaboration. |
|
requestTimeoutInMilliSecond |
Specifies the amount of time, in milliseconds, that Oracle WebCenter Collaboration waits to receive the names of available processes from Oracle BPM. If Oracle WebCenter Collaboration does not receive these names in the specified amount of time, Oracle WebCenter Collaboration stops waiting for process names. By default, the value is 60000 (60 seconds). |
Oracle WebCenter Collaboration can be integrated with the Tagging Engine, allowing users with the Access Tagging Engine activity right to apply tags to Oracle WebCenter Collaboration objects so that they can be searched on and accessed from within the Tagging Engine user interface.
To enable Tagging Engine integration:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Tagging Engine.
Under Enable Tagging, select Enabled.
Under Tagging Communication, type the URL to the Tagging Engine in the Tagging URL text box:
From the Tagging Engine Items or Tagging Engine Users portlet click Display in Tagging Engine.
Copy URL from the Address field of the browser.
Paste the URL in the Tagging URL text box.
Click Save.
Oracle WebCenter Collaboration can be integrated with Oracle Universal Content Management, allowing users to export Collaboration projects and documents to Oracle Universal Content Management.
To enable Oracle Universal Content Management integration:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Collaboration Settings.
Under Enable Tagging, select Enabled.
Under Project and Document export to UCM, configure the following settings:
Select Enabled.
In the UCM User box, type the name of the Oracle Universal Content Management to use to connect to Oracle Universal Content Management.
In the IDC Url to UCM box, type the URL to connect to Oracle Universal Content Management. The URL must be in the format idc://server:port, where the default port is 4444 for intradoc and 4433 for intradoc over SSL.
In the Project parent folder id box, type the ID of the parent folder (collection) in Oracle Universal Content Management you want to use as the root folder for document export. The folder dialog for document export will display folders underneath this folder. Project export ignores this value.
Click Save.
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|