Skip Headers
Oracle® WebCenter Content User's Guide for Desktop
11g Release 1 (11.1.1)

Part Number E10624-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

D Desktop Administration

This section covers these topics:

Note:

See the Oracle WebCenter Content System Administrator's Guide for Content Server for information on configuring the Desktop components on Oracle WebCenter Content Server.

D.1 Custom Installation Options for the Client Software

The Desktop client software installers support a number of custom installation options that can help system administrators roll out the software:

D.1.1 Command-Line Operation

You can use a number of command-line parameters to automate (part of) the installation process.

MSI Installer

You can use command-line parameters for the MSI installer as follows:

msiexec /q /i "DIS-11.1.x.yy-Setup.msi" OUTLOOK=0 INSTALLDIR="C:\Desktop"

Note:

Use "DIS-11.1.x.yy-x64-Setup.msi" for 64-bit Windows.

The /i switch provides the name of the MSI package to be installed, and INSTALLDIR is the installation directory of the Desktop software. The double quotes are required only if the parameter value has spaces in them (for example "C:\Program Files\Desktop" as the installation directory), but using them for values without spaces will not hurt anything.

See Section D.1.2, "Disabling Integrations" for more information about the OUTLOOK parameter.

Exe Installer

The .exe installer can be invoked from the command line as follows:

DIS-11.1.x.yy-Setup.exe /v"WORD=0 EXCEL=0 INSTALLDIR=\"C:\Program Files\Desktop\""

Note:

Use DIS-11.1.x.yy-x64-Setup.exe for 64-bit Windows.

The /v switch passes parameters to the installer. Please note the placement of the double quotes around the entire /v switch section. If any command-line argument has spaces in it, then it must be embedded in double quotes, as in the INSTALLDIR property above. Please note the backslash (\) in front of the double quotes (as they are embedded within the double quotes for the /v switch).

D.1.2 Disabling Integrations

The Desktop installers provide a number of command-line options that enable you to disable specific software integrations. Normally, if the installer detects that an integration can be applied to existing software on the computer (Microsoft Word, PowerPoint, Excel, etc.), it will automatically attempt to install an integration. If you do not want an integration installed for a specific software product, you can disable that integration using these command-line switches:

  • EXPLORER=0

  • WORD=0

  • POWERPOINT=0

  • EXCEL=0

  • OUTLOOK=0

  • NOTES=0

Make sure that you use capital letters for the switch names. See Section D.1.1, "Command-Line Operation" for examples of how to use these switches on the command line.

Note:

Switches are only used to disable software integrations; you do not need to use any switches to enable software integrations for applications that are found on client computers.

D.1.3 Silent Roll-outs

The MSI installer enables 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. The MSI installer for the Desktop client software supports a silent installation option that can easily be configured with SMS.

The command to install the Desktop software silently is as follows:

msiexec /q /i "DIS-11.1.x.yy-Setup.msi" OUTLOOK=0 INSTALLDIR="C:\Desktop"

Note:

Use 'DIS-11.1.x.yy-x64-Setup.msi' for 64-bit Windows.

D.2 Setting the Web Browser Search Provider Name for an Oracle WebCenter Content Server Instance

Desktop provides plug-ins for various popular web browsers which enable users to search for content on an Oracle WebCenter Content Server instance directly from the search field in their web browser. See Chapter 6, "Integration into Web Browsers" for more information about the search provider web browser plug-in.

The default search provider name for an Oracle WebCenter 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:

  1. Log in to Oracle WebCenter Content Server as an administrator.

  2. Open the Administration tray or menu and choose Configuration for SERVER.

    The Configuration Information for SERVER page opens.

  3. Under Features And Components, click Enabled Component Details.

    A list of all installed components opens.

  4. Find DesktopIntegrationSuite in the list, and click its Configure link.

    The Update Component Information page opens for the component.

  5. Make sure the 'Enable web browser search plug-in' check box is selected.

  6. Enter the search provider name for the server in the 'Web browser search plug-in title' field.

    Note:

    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.

  7. 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.

  8. Restart the content server.

D.3 Enabling Subfolder Searching

If an Oracle WebCenter 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 must be configured to use the Oracle Text Search engine and some elements must be added to the search form.

To enable subfolder searching:

  1. Log in to the Administration Server of the content server.

  2. Click General Configuration in the menu on the left.

    The General Configuration page opens.

  3. Make sure the Additional Configuration Values section includes the following entries:

    SearchIndexerEngineName=OracleTextSearch
    FoldersIndexParentFolderValues=true
    
  4. Click Save.

  5. Restart the content server.

  6. 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.

D.4 Mapping E-mail Metadata

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 Oracle WebCenter 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 (see Section 12.2, "E-mail Specific Metadata on Oracle WebCenter Content Server"); you can only create additional mappings.

To map e-mail metadata:

  1. Log in to Oracle WebCenter Content Server as an administrator.

  2. 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 D-1).

  3. 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.

  4. 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.

  5. Once all fields have been updated with metadata values, click Save.

Figure D-1 Email Metadata Mappings (MSG) page

Description of Figure D-1 follows
Description of "Figure D-1 Email Metadata Mappings (MSG) page"

Element Description

Available Fields

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.

Mapped Fields

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).

Mapped Values

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.

Save

Saves the e-mail mapping information on the server.

Reset

Resets all fields to their values when the screen was opened in this session.


D.5 Configuring Form-Based Login

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. Oracle WebCenter Content: 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:

  1. 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.

  2. Open the form in a text editor.

  3. Add the following comment (with no spaces) to the HEAD section of the form:

    <!--IdcClientLoginForm=1-->
    

    Important:

    The form's HEAD section may contain a lot of code; for example, many META tags or JavaScript code. The delivered page must have that HTML comment (or token) in the first 5,000 characters of the response, otherwise the server connection may fail. The software on the client computer sniffs the response for the <!--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.)

  4. Save and close the form.

The next time users connect to a content server using Oracle WebCenter Content: Desktop, they will see a login form, where they can provide their user name and password to log on.

D.6 Customizing the Form-Based Login Regular Expression

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"

Then in:

[HKEY_CURRENT_USER\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\SERVER_NAME]
"Form Based Logins Reg Exp"="REGULAR_EXPRESSION"

Then in:

[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.