This appendix describes the configuration tasks required to enable the use of Oracle WebCenter Content: Desktop.
This appendix includes the following sections:
Section E.1, "Extracting and Running the Installation File for Your Desktop Client Software"
Section E.6, "Customizing the Form-Based Login Regular Expression"
After Oracle WebCenter Content is installed, you can use the desktop_content_setup.exe command with the /export parameter to extract the Desktop installer files:
desktop_content_setup.exe /export [path/existing_extraction_directory/]
You can specify an existing directory to extract the files into. If you omit the directory from the command, it extracts the files into the current directory.
The command extracts three files:
package.ini
contentdesktop.msi
contentdesktop_x64.msi
To install Desktop on a client system, use only one of the MSI files in the Desktop installer command.
The Desktop client software installers support a number of custom installation options that can help system administrators roll out the software:
Section E.1.1, "Using Command-Line Parameters for Automation"
Section E.1.4, "Configuring Content Server Connections Through the Registry on a Windows System"
You can use several command-line parameters to automate part of the installation process. If you need to pass any public property to MSI through desktop_content_setup.exe, you can do that with the following command:
desktop_content_setup.exe /msi ONE_PUBLIC_PROPERTY=public_property_value
The Desktop installer provides a number of command-line options to disable specific software integrations. If the installer detects that an integration can be applied to existing software on the computer (Microsoft Word, PowerPoint, Excel, and so on), it usually will automatically attempt to install an integration. To prevent an integration from being installed for a specific software product, you can disable that integration using one of these command-line switches:
EXPLORER=0
WORD=0
POWERPOINT=0
EXCEL=0
OUTLOOK=0
NOTES=0
Use capital letters for the switch names.
These switches are only for disabling software integrations. They are not necessary to enable software integrations for applications found on client computers.
The Desktop installer enables an 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 installer for the Desktop client software supports a silent installation option that you can configure with SMS.
For silent install, you can use the following command to control the level of user interface displayed.
desktop_content_setup.exe /s UI=user_interface_level
In the command, user_interface_level can be 1, 2, 3, or 4:.
1: No user interface during install.
2: Displays only a progress bar during install.
3: Presents an install screen with different dialog boxes but does not require user input to run.
4: Runs a fully interactive installer requiring user input.
For example, to silently and selectively disable installing Outlook, PowerPoint, and Lotus Notes, the command would be as follows:
desktop_content_setup.exe /s UI=1 /msi OUTLOOK=0 POWERPOINT=0 NOTES=0
You can add Content Server connections by creating a registry file on a Windows system. The file is not included as part of the standard installation files; you must create it.
Adding servers in a registry file automates the setup process by saving your users from setting up connections on their computers. When you add a server connection in this manner, the user cannot delete the server connection from their desktop (Windows Explorer, the email client, or any desktop application).
The following sample registry file entries are examples for Content Servers instances, WebDAV servers, and Content DB servers, with comments below the code lines.
The sample file registry entries are under HKEY_LOCAL_MACHINE. If you would like the user to run the installer, use HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE.
Using HKEY_LOCAL_MACHINE means that users cannot change the ServerAuth or RememberMetaData values because they will not have permission to change HKEY_LOCAL_MACHINE entries (unless a Windows policy is set to allow this, or the user is an administrator).
HKEY_LOCAL_MACHINE values override HKEY_CURRENT_USER values.
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\Corporate] "ServerType"="ucm" "ServerURL"="http://corporate/cs/idcplg/webdav"
(In this registry entry, the server is a Content Server instance, the display name of the server is Corporate, and the server WebDAV URL is http://corporate/cs/idcplg/webdav.)
[HKEY_LOCAL_MACHINE\Software\ORACLE\Universal Content Management\Desktop Integration Suite\Shared\Config\Corporate] "HostCgiUrl"="http://corporate/cs/idcplg" "ServerAuth"=REG_DWORD:0x00000000 (0) "RememberMetaData"=REG_DWORD:0x00000000 (0)
(In this registry entry, the server is a Content Server instance, the name of the server is Corporate, the CGI URL is http://corporate/cs/idcplg, and the user interface URL is http://corporate/wcc/faces. Content DB servers and WebDAV servers do not use these registry entries.)
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\Department] "ServerType"="dav" "ServerURL"="http://corporate/content/app/explorerPage.jspx" "Single Sign-On Url"="http://section/content/app/explorerPage.jspx" "Use Single Sign-On"=REG_DWORD:0x00000001 (1)
(In this registry entry, the server is a WebDAV server, the display name of the server is Department, the server WebDAV URL is http://corporate/content/app/explorerPage.jspx, a single sign-on page has been identified, and single sign-on has been implemented.)
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\Section] "ServerType"="cdb" "ServerURL"="http://section/content/dav" "Single Sign-On Url"="http://section/content/app/explorerPage.jspx" "Use Single Sign-On"=REG_DWORD:0x00000001 (1)
(In this registry entry, the server is a Content DB server, the display name of the server is Section, the server WebDAV URL is http://section/content/dav, a single sign-on page has been identified, and single sign-on has been implemented.)
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.
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:
Log in to Content Server as an administrator.
Choose Administration then Configuration for SERVER.
On the Configuration page, in Features And Components, click Enabled Component Details.
In the list of installed components, find DesktopIntegrationSuite and click its Configure link.
On the Update Component Information page, make sure the Enable web browser search plug-in checkbox is selected.
Enter the search provider name for the server in the Web browser search plug-in title field. Choose a search provider name that is unique across the organization. Two servers with the same search provider name are not allowed.
When 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 Content Server.
If a Content Server instance is using Framework Folders as the content hierarchy component, subfolder searching can be enabled. 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, 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:
Log in to the WebLogic Server Administration Console for Content Server.
Choose General Configuration.
On the General Configuration page, verify that the Additional Configuration Values section includes the following entries:
SearchIndexerEngineName=OracleTextSearch FoldersIndexParentFolderValues=true
Click Save.
Restart Content Server.
Rebuild the search collection index.
The content search form now includes a Parent Folder field as well as an Include Subfolders checkbox, which allows users to limit a search query to just the current content folder or expand it to include all subfolders.
Administrators can map email header fields to metadata fields for messages checked in to Content Server. MSG metadata mapping is used for the Microsoft Outlook message format and EML metadata mapping for Internet mail message format.
The six standard email metadata mappings cannot be overridden. Only additional mappings can be created.
Log in to Content Server as an administrator.
Choose Administration then Configure Email Metadata then Map MSG Metadata or Map EML Metadata.
On the Email Metadata Mappings page, the listed email header fields under Available Fields are not mapped and the fields 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 drop-down list appears for that field under Mapped Values. For each mapped email header field, select a value for the metadata field from the dropdown list.
When all fields are updated with metadata values, click Save.
Your organization may use separate identity and access management software that provides secure, form-based login screens to authenticate users and control access. Desktop is compatible with form-based logins. To enable this, add a comment to the login page so Desktop identifies an HTML response as the forms-based login page. Users 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.
Open the form in a text editor.
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 great deal of code. The delivered page must have that HTML comment (or token) in the first 5,000 characters of the response. If not, the server connection may fail.
The software on the client computer checks 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.
Save and close the form.
By default, Desktop 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 it looks here:
[HKEY_CURRENT_USER\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV\Servers\SERVER_NAME] "Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
Then it looks here:
[HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Universal Content Management\Desktop Integration Suite\WebDAV]
"Form Based Logins Reg Exp"="REGULAR_EXPRESSION"
Finally it looks here:
[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.