|Oracle® Fusion Middleware Managing Oracle WebCenter Content
11g Release 1 (11.1.1)
Part Number E26693-01
|PDF · Mobi · ePub|
This chapter provides information on managing Oracle WebCenter Content: Desktop, which provides a set of embedded applications that help to seamlessly integrate users' desktop experience with Oracle WebCenter Content, Oracle WebCenter Content Server, Oracle Content Database, or other WebDAV-based content repositories.
For information about using Desktop, see Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.
This chapter covers these topics:
The Desktop client software installers support a number of custom installation options that can help system administrators roll out the software:
Command-line operation: You can use a number of command-line parameters to automate (part of) the installation process.
Disabling integrations: The Desktop installers provide a number of command-line options that enable you to disable specific software integrations.
Silent roll-outs: The MSI installer enables the system administrator to roll out the Desktop client software to multiple client machines with the help of third-party tools such as SMS or netOctopus, which are capable of executing one executable on many machines.
Configuring Content Server connections through the Windows registry: Desktop Integration Suite supports the configuration of servers and settings by executing a registry file named defaults.reg in the installation program's directory. The file is not included as part of the standard installation files; you must create it.
For information on using these options, see "Using Custom Installation Options for the Client Software" in Oracle WebCenter Content Installation Guide.
Desktop provides plug-ins for various popular web browsers which enable users to search for content on a Content Server instance directly from the search field in their web browser. For more information about the search provider web browser plug-in, see "Integration into Web Browsers" in Using Oracle WebCenter Content: Desktop.
The default search provider name for a Content Server instance is
Oracle WebCenter Content Search, but this can be modified to a more meaningful name for the server.
To modify the default search provider name:
Log in to Content Server as an administrator.
Open the Administration tray or menu and choose Configuration for SERVER.
On the Configuration Information for SERVER page, under Features And Components, click Enabled Component Details.
In the list of all installed components, find DesktopIntegrationSuite and click its Configure link.
On the Update Component Information page, make sure the Enable web browser search plug-in check box is selected.
Enter the search provider name for the server in the Web browser search plug-in title field.
Make sure to choose a search provider name that is unique across your organization. You cannot have two servers with the same search provider name.
When you are done, click Update to enable the new settings, Reset to cancel any modifications, or Revert To Install Settings to return to all default settings.
Restart the Content Server instance.
If a Content Server 11gR1 instance is using Framework Folders as the content hierarchy component, then you can enable subfolder searching. This allows users to specify whether a content search should apply to the current folder only or whether it should include all subfolders of that folder.
To enable subfolder searching, the Content Server instance must be configured to use the Oracle Text Search engine and some elements must be added to the search form.
To enable subfolder searching:
Log in to the Administration Server of the Content Server instance.
Choose General Configuration in the menu.
On the General Configuration page, make sure the Additional Configuration Values section includes the following entries:
Restart the Content Server instance.
Rebuild the search collection index using the Repository Manager utility.
The content search form now includes a Parent Folder field as well as an 'Include Subfolders' check box, which allows users to limit a search query to just the current content folder or expand it to include all subfolders.
System administrators can map e-mail header fields to metadata fields for e-mail messages that are checked in to the Content Server. This is done on the Map MSG Metadata and Map EML Metadata pages, which are available in the Content Server web interface. MSG metadata mapping is used for the Microsoft Outlook message format and EML metadata mapping for Internet mail message format.
Please note that you cannot override the six standard e-mail metadata mappings; you can only create additional mappings. (See "E-mail Specific Metadata on Oracle Content Server" in Oracle Fusion Middleware Using Oracle WebCenter Content: Desktop.)
To map e-mail metadata:
Log in to Content Server as an administrator.
Open the Administration tray or menu and choose Configure Email Metadata and then Map MSG Metadata or Map EML Metadata.
The Email Metadata Mappings page opens (MSG or EML) (Figure 43-1).
The e-mail header fields listed under Available Fields are not mapped to Content Server metadata fields. The fields listed under Mapped Fields are mapped to metadata. Use the right and left arrows to select a field and move it from one group to the other. Use the up and down arrows to sort the fields within each grouping.
As fields are added to or removed from Mapped Fields, a dropdown list appears for that field under Mapped Values. For each mapped e-mail header field, select a value for the metadata field from the dropdown list.
Once all fields have been updated with metadata values, click Save.
Figure 43-1 Email Metadata Mappings (MSG) Page
The e-mail header fields in this list can be mapped to Content Server metadata fields. Use the up and down arrows to sort the fields as desired, and once a field is selected, use the right arrow to move it into the Mapped Fields box.
The e-mail header fields in this list are mapped to Content Server metadata fields. Use the up and down arrows to sort the fields as desired, and once a field is selected, use the left arrow to move it into the Available Fields box (and unmap the field).
Each e-mail header field in the Mapped Fields list is included in this area. Select a Content Server metadata field in the dropdown list to map the e-mail header field to.
Saves the e-mail mapping information on the server.
Resets all fields to their values when the screen was opened in this session.
Your organization may use separate identity and access management software that provides secure, form-based login screens to authenticate users and control what they have access to on the network. Desktop is compatible with form-based logins. To set this up, system administrators need to add a comment to the login page so that Desktop identifies an HTML response as the forms-based login page. Users, as a result, will see the form-based login instead of the standard Content Server login.
To configure form-based login:
Locate the login form on the file system (for example,
login.fcc for Netegrity SiteMinder). The location of this form depends on how the authentication system was set up in your organization.
Open the form in a text editor.
Add the following comment (with no spaces) to the HEAD section of the form:
<!--IdcClientLoginForm=1--> token (using a strict string search) and route through the prompting code if it is found. It is encoded as an HTML comment so that regular browsers do not show the token when they attempt to log in. (If it is Idoc Script, then the parser removes that bit of code from the delivered page, and the client-side browser will not see anything in the page.)
Save and close the form.
The next time users connect to a Content Server instance using Desktop, they will see a login form, where they can provide their user name and password to log on.
By default, Desktop 11g uses the following regular expression to identify a form-based login:
<!--IdcClientLoginForm=1-->| <form .*sso.* name=\"LoginForm\"| <form *name=\"loginForm\"
This regular expression is configurable in the Windows Registry. The code first looks in the following place:
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\SERVER_NAME] "Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
[HKEY_CURRENT_USER\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\SERVER_NAME] "Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV] "Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
And finally in:
[HKEY_CURRENT_USER\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV] "Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
If no custom regular expression is defined in any of these Windows Registry locations, the default one is used.