Lotus Quickr Connectors

First Edition

Published June 2010

About this edition

In keeping with IBM's commitment to accessibility, this edition of the product documentation is accessible.

Printing

When you print this document some of the style elements are removed to create a better print output. Here are a few tips about printing:
  • The document length may exceed the browser's print capability. Microsoft Internet Explorer has demonstrated the ability to print large files successfully.
  • This document is long. Use print preview to determine the printed page length.
  • You can highlight section of the document and then choose to only print the selected content

Working offline

You can save a local copy of this document from your browser. Each browser has different menus and menu options. Consult the browser help if you need assistance saving the document locally.

Submitting feedback

Submit feedback about this HTML edition. To submit feedback about the product documentation in the wiki, use the commenting or editing feature.

Product overview

Learn about new features in this version and accessibility features.

What's new in the Lotus Quickr Connectors

Many new features and functionality are available in Lotus® Quickr™ Connectors.

The latest updates to the Lotus Quickr Connectors are as follows:

  • Across all connectors users can take advantage of the following new features and functionality:
    • Send folders, documents, and pages to Trash and restore them as needed. For example, after deleting a document within Lotus Symphony™, a user can navigate to the place connector for Microsoft® Explorer to open the place's Trash bin either to permanently delete or to restore the document.
      Note: The Trash view does not refresh automatically so users should make sure to refresh the Trash view manually (press F5) after restoring content to verify that the restored items have been returned to their original locations. This feature is not available currently on the Lotus Quickr 8.5 for Portal server.
    • Work with an existing place library page and any attachments from a connector just as you would if you had accessed the page within the place's library itself. Pages appear in a connector's place list alphabetically as typical documents and are listed under folders. You see all the library's pages except for comments.
      Note: This feature is not available currently on the Lotus Quickr 8.5 for Portal server.
    • Launch a search of a place by clicking Search in Browser.
    • Require that users specify certain properties when creating documents in places and ECM repositories.
    • Override the default preference to upload drafts automatically whenever changes are made and saved to a local draft and instead to upload drafts on an as-needed basis. In certain environments an automatic upload could increase server load to an unacceptable level so the option is available to give place members the ability to decide when to upload.
    • Integrated Windows Authentication (SPNEGO) enabled out of the box so that end users can use their Windows® login credentials to access the Lotus Quickr server.
  • Using the place connector for Microsoft Office, users can exploit the updated Lotus Quickr Ribbon Tab Add-in for Microsoft Office 2007 if they use the Add-in tab. All activities that users can perform from this connector are available on the Places tab in the Office ribbon, which appears next to the Add-In tab. The Ribbon is an enhancement of the previous toolbar and menu options that were available for earlier versions of Microsoft Office as well as previous versions of the connectors installed in Microsoft Office 2007.  The toolbar also exists for versions of Microsoft Office prior to 2007.
  • Using the place connector for Lotus Notes®, users can save all attachments in a single action when sending or receiving an e-mail with several attachments. A user can open the e-mail, right-click one of the file attachments, and then click Save All to a Place. There is an improved link format in Lotus Notes and users can copy and paste documents as attachments
    Note: This feature requires a Lotus Notes client version of 8.5 or higher.
  • Using the place connector for Lotus Symphony, users can exploit the following additional features and functionality:
    • The connector executable (qkrconn.exe) now includes the place connector for Lotus Symphony.
    • Users can double-click a document from the place connector for Windows Explorer and have it open in Lotus Symphony. The file will be recognized successfully as a Lotus Quickr-managed document.
    • Security facilities are improved to integrate with the latest authentication modules, Basic, SiteMinder, Windows SSO, inheriting from previous releases of Lotus Quickr, and also provide extension point to be extended to integrate customized authentication module.
    • More than 30 legacy defect fixes are integrated.
    • Improved performance and user interface responsiveness because of threading technology that detaches almost all the network-centric operations into separated threads.

Accessibility features

Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully.

Accessibility features

The following list includes the major accessibility features in Lotus Quickr Connectors:
  • Keyboard-only operation
  • Interfaces that are commonly used by screen readers
  • Keys that are discernible by touch but do not activate just by touching them
  • Industry-standard devices for ports and connectors
  • The attachment of alternative input and output devices

The Lotus Quickr wiki, and its related publications, are accessibility-enabled.

Keyboard navigation

This product uses standard Microsoft Windows navigation keys.

Vendor software

Lotus Quickr Connectors include certain vendor software that is not covered under the IBM license agreement. IBM makes no representation about the accessibility features of these products. Contact the vendor for the accessibility information about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility:

Planning

Learn about system requirements and international considerations.

System requirements

Before installing the IBM® Lotus® Quickr™ Connectors, review the hardware and software requirements.

See the detailed system requirements document at the following URL: http://www.ibm.com/support/docview.wss?rs=3264&uid=swg27009740

Authentication options

Users of IBM® Lotus Quickr Connectors can choose between Basic and Integrated Windows authentication types.

The IBM Lotus Quickr Connectors can support the following types of authentication for users:
  • Basic
  • Integrated Windows Authentication
  • Basic Authentication over HTTPS can be provided by Siteminder.

Using Basic authentication

If you intend for your Connectors implementation to use Basic authentication, it must protect the /dm context root. It is highly recommended that the /dm context root be further protected by https. Not doing so might expose the credentials to any kind of network sniffing attack. In addition, the connectors do not support http redirects (permanent or temporary).
  • Connector users simply select Basic in the Authentication Type field the first time they attempt to connect to a place.

Using Integrated Windows authentication

Connector users can also use Integrated Windows Authentication, which allows them to login to Lotus Quickr using their Windows® login credentials.
  • It is enabled as an authentication type by default with this registry setting: [HKEY_LOCAL_MACHINE\Software\IBM\Lotus Quickr\Desktop Integration\Settings]"EnableSSO"="1" A value of 0 (zero) disables it.
  • Custom authentications can also be created using APIs.
  • Users can select Integrated Windows Authentication in the Authentication Type field the first time they attempt to connect to a place.

Administrators can enable the Domino Web SSO option on the Lotus Quickr for Domino server to allow Integrated Windows Authentication for connector users.

Installing and upgrading

There are two ways to install or upgrade the IBM Lotus Quickr Connectors. A user can install and upgrade connectors through the server, or an administrator can perform a silent installation or upgrade for all connector users.

User installation

Users can install connectors for IBM Lotus Notes, IBM Lotus Sametime®, Lotus Symphony, Microsoft Windows Explorer, Microsoft Outlook, and Microsoft Office applications.

Users can install connectors from the server by clicking Lotus Quickr Connectors from the footer and downloading the qkrconn.exe file that runs in the installation. Administrators can silently install connectors or control which servers are available for collaborative connector installations.
Note: When downloading the latest versions of the connectors, users now have the explicit option to install the place connector for Microsoft Outlook independently of the place connector for Microsoft Office option.
Note: Once the proxy server has been configured, the browser settings on any clients using the connectors must be modified. Connector users need to:
  1. Select the Windows proxy setting Internet Options > Lan Settings.
  2. Select the Use a proxy server option and enter the proxy Address and the Port number into the appropriate fields so be sure your users have the correct information.

Silent installation

Administrators can silently upgrade or install the Lotus Quickr Connectors from the command prompt. Installing the connectors silently bypasses user involvement in the process other than to ensure that the applications that the connectors work with are the proper versions.

  1. Click Download from the IBM Lotus Quickr connectors section of the footer.
  2. Save the install file qkrconn.exe to your computer.
  3. Open a command prompt and navigate to the directory where you saved qkrconn.exe.
  4. Make sure all applications such as Lotus Notes, Lotus Sametime, Microsoft Office/Outlook and Lotus Symphony are closed before performing the following silent commands.
  5. Type qkrconn.exe /Options(s) [Property settings] The optional parameters and public property settings are listed in the following tables:
    Table 1. Optional parameters
    Optional parameters Description
    /install Installs connectors.
    /uninstall Uninstalls connectors.
    /quiet Establishes Silent mode requiring no user interaction.
    /norestart Prevents restart after the installation is complete.
    /promptrestart Prompts the user for restart if necessary.
    /forcerestart Always restarts the computer after installation.
    Table 2. Public properties
    Public property [PROPERTY=PropertyValue] Description
    INSTALLDIR Directory that connectors will be installed in. For example, INSTALLDIR=C:\Progra~1\IBM\QuickrConnectors.
    ADDLOCAL Specify which connector to install. By default, if you do not specify the ADDLOCAL property, all connectors are installed except for the place connector for Notes Embedded Symphony. For example, ADDLOCAL=WindowsExplorer,MicrosoftOffice will install the place connector for Windows Explorer and the place connector for Microsoft Office. ADDLOCAL=ALL installs all connectors.

    WindowsExplorer (required)

    MicrosoftOffice (place connector for Microsoft Office)

    MicrosoftOutlook (place connector for Microsoft Outlook)

    LotusSametime (place connector for Lotus Sametime Standalone Edition. For Lotus Sametime embedded in Lotus Notes, use the place connector for Lotus Notes.)

    LotusNotes (place connector for Lotus Notes)

    LotusSymphonyStandalone (place connector for Lotus Symphony connector Standalone Edition)

    LotusSymphonyEmbedded (place connector for Lotus Symphony embedded in Lotus Notes)

    QC_NOTES_TARGET_FOLDER When installing the place connector for Lotus Notes, specifies where Lotus Notes is installed. This property is optional. For example, QC_NOTES_TARGET_FOLDER=C:\Notes.
    QC_NOTES_NOTES_INI_PATH When installing the place connector for Lotus Notes Single User Install (SUI), specifies where notes.ini is placed. This property is optional. For example, QC_NOTES_NOTES_INI_PATH=C:\Notes\notes.ini.
    QC_SAMETIME_TARGET_FOLDER When installing connector for Lotus Sametime, specifies where Lotus Sametime is installed. This property is optional. For example, QC_SAMETIME_TARGET_FOLDER=C:\progra~1\IBM\Sametime.
    QC_SYMPHONY_TARGET_FOLDER When installing connector for Lotus Symphony Standalone Edition, specifies where Lotus Symphony Standalone Edition is installed. This property is optional. For example, QC_SYMPHONY_TARGET_FOLDER=C:\progra~1\IBM\Lotus\Symphony.
    Table 3. Samples of silent install commands
    Description Code sample
    Silent uninstall with no restart qkrconn.exe /uninstall /quiet /norestart
    Silent install with no restart and settings for Lotus Notes and Lotus Sametime. qkrconn.exe /install /quiet /norestart QC_NOTES_TARGET_FOLDER=C:\notes QC_SAMETIME_TARGET_FOLDER=C:\progra~1\IBM\Sametime The QC_ properties are required due to the user interface providing the option for changing any registry-discovered values first.
    Silent install with restart and only installing place connectors for Windows Explorer and Microsoft Office. qkrconn.exe /install /quiet /forcerestart INSTALLDIR=C:\Progra~1\IBM\QuickrSample ADDLOCAL=WindowsExplorer,MicrosoftOffice
  6. Consider the following deployment options:
    Table 4. Connector deployment options
    Deployment option Condition to use Command sample
    Install Fresh install, no old driver exists. To perform a fresh installation, adding place connectors for Explorer and Office: qkrconn.exe /install /quiet ADDLOCAL=WindowsExplorer,MicrosoftOffice
    Upgrade Upgrade from Lotus Quickr 8.1/8.2 drivers to 8.5, all connectors on old driver will be removed first and then install the Lotus Quickr 8.5 connectors. To upgrade an existing Lotus Quickr 8.1 or 8.2 driver, adding place connectors for Explorer, Office, and Notes®: qkrconn.exe /install /quiet /forcerestart ADDLOCAL=WindowsExplorer,MicrosoftOffice,LotusNotes
    Uninstall Uninstall current installed driver, the installed driver version should be same as the version of qkrconn.exe you are invoking. To uninstall an existing 8.5 driver:qkrconn.exe /uninstall /quiet /norestart
    Patch Patch existing 8.5 driver with a newer 8.5 iFix driver. To patch all installed connectors: qkrconn.exe /install /quiet /forcerestart REINSTALL=ALL To patch the place connectors for Explorer and Notes: qkrconn.exe /install /quiet /forcerestart REINSTALL=WindowsExplorer,LotusNotes
  7. Reboot the machine.
After installing or upgrading connectors, you can disable the connectors download feature from the site.

Upgrading the connectors on client workstations

Users can upgrade their connectors without having uninstall their previous versions.

The Lotus Quickr Connectors work with Lotus Quickr 8.5 for Portal and also for Lotus Domino®, and with ECM QService 1.1. Connectors released with Lotus Quickr 8.2 also can work with Lotus Quickr 8.5 for Portal and for Lotus Domino, and with ECM QService 1.1.

Before upgrading connectors on client workstations, make sure users have the required versions of the applications already installed on the client workstations. The application requirements of the latest Lotus Quickr Connectors are as follows:

  • Place connector for Lotus Notes requires Lotus Notes 8.0.2 (Standard and Basic) or Lotus Notes 8.5.1 (Standard and Basic).
  • Place connector for Lotus Sametime requires Lotus Sametime 8.0.2 or Lotus Sametime 8.5.
  • Place connector for Lotus Symphony requires Lotus Symphony 1.3 and Lotus Notes 8.0.2 embedded or Lotus Notes 8.5.1 embedded.
  • Place connector for Microsoft Office/Outlook requires Microsoft Office XP, 2003, or 2007.

The following upgrade paths have been tested and are supported:

  • From Lotus Quickr Connectors 8.1.1 to Lotus Quickr Connectors 8.5
  • From Lotus Quickr Connectors 8.2 to Lotus Quickr Connectors 8.5
  • From Lotus Quickr Connectors 8.2 interim fixes to Lotus Quickr Connectors 8.5
Note: Upgrading from Lotus Quickr Connectors 8.1 to version 8.5 has not been tested but should work.

Manually upgrading client workstations to the latest Lotus Quickr Connectors

Follow these steps to upgrade the Quickr Connectors from a previous version without having end users uninstall first.
  1. Make the qkrconn.exe available to end users.
  2. User needs to double-click qkrconn.exe to begin installation.
  3. Follow the self-explanatory prompts from the upgrade wizard. You can change the components during the upgrade for previous connectors releases. You can install one or all of them, as long as you have the supported versions of these applications installed on the client workstation already.
  4. Reboot if prompted. If you do not, unexpected behavior may occur.

Silently upgrading client workstations to the latest Lotus Quickr Connectors

Follow these steps to upgrade the connectors from a previous version without having end users uninstall first. A silent installation means the end user does not need to perform the upgrade manually.
  1. Ensure that all applications on the client workstations are shut down before the upgrade is started.
  2. Save qkrconn.exe to the desired location to run the silent upgrading.
  3. Enter the required silent install command qkrconn.exe with switches. For a full list of commands and switches, type qkrconn.exe /? You can install one connector or all of them, as long as you have the supported versions of these applications installed on the client workstation already. For example:
    qkrconn.exe /install /quiet /forcerestart ADDLOCAL=WindowsExplorer,MicrosoftOffice,LotusNotes
  4. Reboot after the upgrade is finished. If you do not, unexpected behavior might occur.

Installing a connectors interim fix

Follow these steps to patch the connectors with an interim fix.
  1. Start the installation qkrconn.exe.
  2. Follow the self-explanatory prompts from the upgrade wizard. You cannot change the components and the connectors install location during the upgrading.
  3. Reboot if prompted. If you do not, unexpected behavior may occur.

Silently installing a connectors interim fix

Follow these steps to install an interim fix silently.
  1. Ensure that all applications on the client workstations are shut down before the upgrade is started.
  2. Save qkrconn.exe to the desired location to run the silent upgrading.
  3. Enter the required silent install command qkrconn.exe with switches. To patch an existing 8.5 driver with a new 8.5 ifix driver silently, using REINSTALL parameter. For example, to patch all installed connectors:
    qkrconn.exe /install /quiet /forcerestart REINSTALL=ALL
    To patch the place connectors for Explorer and Notes only:
    qkrconn.exe /install /quiet REINSTALL=WindowsExplorer,LotusNotes
  4. Reboot after the upgrade is finished. If you do not, unexpected behavior may occur.

Suppressing connector functionality

You can disable the Connector download option and the display of the action for adding a place to a connector.

Disabling the Add place to connectors action

The Add place to your connectors action displays by default under the Actions list for a place whether or not you have deployed connectors in your Lotus Quickr implementation. If you have turned off the Connectors download option for a place, you can prevent the Add place to your connectors action from appearing under the Actions list for a place.

This task assumes you have created and use a qpconfig.xml file derived from the qpconfig_sample.xml file delivered with this version of Lotus Quickr. If you have an existing qpconfig.xml file, copy and paste the <webservices> section from the qpconfig_sample.xml file into your working qpconfig.xml.
  1. Open your qpconfig.xml file in your preferred text editor and locate the <webservices> section.
  2. Set the connectors attribute add_place_action enabled to false.
  3. Be sure to save your changes to qpconfig.xml.
The following example shows the add_place_action disabled:
 	<webservices enabled="true">
		<atomws_response type="get" />
		<connector_install_url>http://server.lotus.com/qkrconn.exe</connector_install_url>
		<connectors>
			<add_place_action enabled="false" />
		</connectors>
	</webservices>

Configuring connectors

As Lotus Quickr administrator, you can pre-configure your users' desktops with various library and server preferences, defaults, and policies. You can also create policies for connectors to override default connector settings, disable users from changing connector settings, and set policies at install time by editing the Microsoft Windows registry.

Pre-configuring users' desktops with connector content

Use the QuickrConfig tool to pre-configure your users' desktops with various library, server, preferences, defaults, and policies, so users just need to enter their credentials once without having to add connector content manually.

Administrators can use the QuickrConfig tool to export and import a place list from one system to another. Either an end user can run the tool or a deployment script can run the tool. The tool can be used optionally to export and import user preferences as well as global defaults and policies so that users can run the tool to backup their configuration in the event that they need to run a clean install of the connectors.
The QuickrConfig tool is installed as part of the core code with the Lotus Quickr Connectors installation. It consists of two files: QuickrCfg.exe and QKRCOM.dll. The QKRCOM.dll is a self-registering .dll file registered by the installer. If the .dll file is not registered, the tool will not work. An administrator can deploy these files to a machine with an older version of the connectors, or without the connectors installed, and then just register QKRCOM.dll (regsvr32 QKRCOM.dll).
Note: If you plan to run the QuickrConfig tool in another directory or on another machine where the connectors are installed, the xerces-c_3_0.dll file is also installed and is used. The xerces-c_3_0.dll file needs to be in the same directory.

When exporting, to run the QuickrConfig tool from a command line:

  1. Access the default location of the Lotus Quickr Connectors, typically, C:\Program Files\IBM\Places Connectors.
  2. To export all servers, places, policies, preferences, and global defaults to a specified file, enter a command similar to the following example:
    QuickrCfg -export myQuickr.xml
    Note: If no file is specified, the default filename QuickrCfg.xml is used. If the file specified already exists, the operation will abort. You can overwrite the file with the -overwrite option.
  3. To perform a full export to myQuickr.xml and overwrite the file (if it exists), enter:

    QuickrCfg -export -overwrite myQuickr.xml
Command syntax is as follows:
QuickrCfg [COMMAND] [OPTION] <filename>
Where [COMMAND] can be any of the following:
Table 5. Quickr/Config tool commands
Command Description
-backup Create a backup of the current configuration.
-deletebackup Delete any backup configuration.
-export Exports configuration to <filename>.
-format Print xml syntax/format.
-import Imports configuration from <filename>.
-help / -? Print cmd syntax.
-restore Restore a previous backup.
-sample Print out sample xml.
-validate Validates xml format in <filename>.

where [OPTION] can be any of the following:

Table 6. Quickr/Config tool options
Option Description
-noplaces (used for both export and import) Do not import or export places, but do export servers.
-noservers (used for both export and import) Do not import or export servers or places.
-noprefs (used for both export and import) Do not import or export user preferences.
-nopolicy (used for both export and import) Do not import or export policy settings.
-nodefaults (used for both export and import) Do not import or export global defaults.
-nouser (export only) Do not include user information in export list.
-overwrite (export only) Replaces existing output file if exists.
-merge (import only) Merges server/places into existing configuration.
-replace (import only) Replaces existing configuration.
-suppress Suppress any user warning prompts.
-verbose Print out more status messages while running action.
<filename> The default filename, if not specified, is QuickrCfg.xml .

When importing, the default is to import everything in the specified file. Server and place list entries will be added into the existing configuration. If duplicate servers/places exists, they will not be merged.

  1. Access the default location of the Lotus Quickr Connectors, typically, C:\Program Files\IBM\Places Connectors.
  2. To import everything in the specified file, enter a command similar to the following example:
    QuickrCfg -import myQuickr.xml
    Note: To merge servers/places, the -merge option needs to be specified. This will cause the information from the configuration file to replace any information in the registry if the servers match.
  3. To import servers and places from a preexisting configuration file and merge the information into the existing configuration, as well as to have the tool provide full output, enter:
    QuickrCfg -import -noprefs -nopolicies -nodefaults -merge -verbose myQuickr.xml 

To see a sample of the import/export format, enter QuickrCfg -sample. The following sample of the import/export format is not an exhaustive list of all the key/values that would be exported. The tool will iterate over the HKCU and HKLM Desktop Integration registry keys and export the appropriate keys and values.

<?xml version="1.0" encoding="UTF-8"?>
<qkr:config xmlns:qkr="http://quickr.connectors.acme.com">
<!-- servers and places -->
   <qkr:servers>
      <qkr:server name="server1">
         <qkr:val name="AnonymousBinaryUrl" value="/dm.anonymous/atom"/>
         <qkr:val name="AuthExt" value="1"/>
         <qkr:val name="BinaryUrl" value="/dm/atom"/>
         <qkr:val name="CommonName" value="uid=quikradm,o=default organization"/>
         <qkr:val name="InstallURL" value="http://server1.acme.com/qkrconn.exe"/>
         <qkr:val name="DisplayName" value="Server One"/>
         <qkr:val name="LocalDir" value="c:\Users\user1\server1"/>
         <qkr:val name="Name" value="server1"/>
         <qkr:val name="Version" value="8.5.0"/>
         <qkr:places>
            <qkr:place name="User1's Place">
               <qkr:val name="AddDoc" value="2"/>
               <qkr:val name="Description" value="This place is owned by user 1"/>
               <qkr:val name="DisplayName" value="User1's Place on Server1"/>
               <qkr:val name="DoubleClick" value="2"/>
               <qkr:val name="LocalDir" value="c:\Users\user1\server1\user1splace"/>
               <qkr:val name="Name" value="47c4c9004706e8b784a3d7e73568607e"/>
               <qkr:val name="Path" value="/contentRoot/icm:libraries[7]/clb:libraries/clb:libraries"/>
               <qkr:val name="Title" value="User1's Place"/>
               <qkr:val name="Type" value="1"/>
            </qkr:place>
         </qkr:places>
      </qkr:server>
   </qkr:servers>
<!-- preferences -->
   <qkr:preferences>
      <qkr:key name="Monitor">
         <qkr:val name="NoShowInfoBubbles" value="1"/>
         <qkr:val name="ScanIgnoreExtentions" value=".xls,.doc,.ppt"/>
      </qkr:key>
      <qkr:key name="Settings">
         <qkr:val name="SendLink MailApp" value="mailto"/>
         <qkr:val name="Default AddDoc" value="2"/>
         <qkr:val name="Default DoubleClick" value="2"/>
      </qkr:key>
   </qkr:preferences>
<!-- policies -->
   <qkr:policies>
      <qkr:key name="Servers">
         <qkr:val name="Disable Password Save Policy" value="1"/>
      </qkr:key>
   </qkr:policies>
<!-- defaults -->
   <qkr:defaults>
      <qkr:key name="Office">
         <qkr:val name="Default CloseOption" value="1"/>
         <qkr:val name="Default CheckinOption" value="0"/>
         <qkr:val name="Default CheckoutOption" value="1"/>
      </qkr:key>
   </qkr:defaults>
</qkr:config>

The following is the valid xml format that will be parsed and understood. This can be seen by entering the command QuickrCfg -format.

<?xml version="1.0" encoding="UTF-8"?>
<qkr:config xmlns:qkr="http://quickr.connectors.acme.com">
<!-- servers and places -->
   <qkr:servers>
      <qkr:server name="serverName">
         <qkr:val name="serverValueName" value="serverValueValue"/>
         <qkr:places>
            <qkr:place name="placeName">
               <qkr:val name="placeValueName" value="placeValueValue"/>
            </qkr:place>
         </qkr:places>
      </qkr:server>
   </qkr:servers>
<!-- preferences -->
   <qkr:preferences>
      <qkr:key name="preferenceScope">
         <qkr:val name="preferenceValueName" value="preferenceValueValue"/>
      </qkr:key>
   </qkr:preferences>
<!-- policies -->
   <qkr:policies>
      <qkr:key name="policyScope">
         <qkr:val name="policyValueName" value="policyValueValue"/>
      </qkr:key>
   </qkr:policies>
<!-- defaults -->
   <qkr:defaults>
      <qkr:key name="defaultScope">
         <qkr:val name="defaultValueName" value="defaultValueValue"/>
      </qkr:key>
   </qkr:defaults>
</qkr:config>

Managing connector policies

Administrators can create policies for connectors to override default connector settings, disable users from changing connector settings, and set policies at install time by editing the Microsoft Windows registry.

In the registry, the policy definitions and system default settings are stored in the HKEY_LOCAL_MACHINE (HKLM) hive. All settings are stored in subkeys under the /Software/IBM/Lotus Quickr/Desktop Integration/ key.

Connector policy definitions and system default settings in the Registry editor

Setting used in various policy scenarios

The following table describes the connector settings used with various combinations of global preference, user preference, and policy settings. A policy setting of 0 means that a setting can be changed by a user. A user preference is used when the policy allows a user to change a setting from their local machine in Preferences. For example, a user can change a setting in IBM Lotus Notes by clicking Tools > Places > Preferences.

A policy setting of 1 means that a setting cannot be changed by users even when a user has changed their preferences.

Table 7. Policy Settings
Policy setting Global preference exists User preference exists Setting used
0 Yes Yes User preference
0 Yes No Default settings (refer to the Setting definitions table)
Note: There is not a default save password value in the registry.
0 No Yes User preference
0 No No Default setting (refer to the Setting definitions table)
1 Yes Yes Global preference
1 Yes No Global preference
1 No Yes Default settings (refer to the Setting definitions table)
1 No No Default settings (refer to the Setting definitions table)

Setting definitions

It is recommended that when you create a policy key that you also create the corresponding settings. Default settings may change from release to release. An administrator can deploy a policy to managed clients by creating a policy file, installing the connectors on a test machine, editing the registry as appropriate by adding settings and policies, testing their deployment, and exporting the desktop integration key.

Table 8. Setting definitions
Subkey Value Settings User preferences
Office Default CheckoutOption

Default: 0 - Do not check out documents in Open from Place

1 - Default check out documents in Open from Place

Microsoft Office preferences for connectors:

Microsoft Office preferences for connectors
Default CheckinOption

0 - Close document on check in

1 - Leave document open on check in

Default: 2 - Prompt me

Default CloseOption

0 - Check in or Publish document on close

1 - Leave document locked or unpublished on close

Default: 2 - Prompt me

Settings Default AddDoc

0 - Always check in documents

1 - Always add as private drafts

Default: 2 - Prompt me

Places preferences for connectors:

Places preferences for connectors
Default DoubleClick

0 - Always check out

1 - Always open without checking out

Default: 2 - Prompt me

Link Behavior

0 - Always open the document without checking out

Default: 1 - Prompt me to check out the document

General preferences for connectors:

General preferences for connectors

Configuring collaborative installations for Lotus Quickr for Domino only

Users of the place connector for Lotus Sametime and the place connector for Lotus Notes can invite others to download the connectors by sending URL links to the servers to use for the downloads. You can configure which servers to use for these "collaborative" installations.

By default, any IBM Lotus Quickr server can be used for collaborative installations. In this case a server's fully-qualified URL download location is constructed automatically from the server's relative URL. If your environment uses a reverse proxy to handle server requests and you want to allow collaborative installations, you should use this default configuration.

You can change the default behavior and specify that collaborative installations occur from a different server. For example, if you use multiple servers, you might allow collaboration installations from only one of them. You can also disable collaborative installations altogether.

Note: Collaborative installation configuration does not affect the ability to download connectors in the standard way through direct server access.

Perform the following steps:

  1. Open the qpconfig.xml file in the domino_data_root directory, or create the file if it does not exist already.
  2. Perform one of the following steps
    • To use a different server for collaborative installations, specify the following settings:
      <webservices enabled="true">
         <connector_install_url>http://value/qkrconn.exe</connector_install_url>
      </webservices>
      where value is the fully-qualified host name of a Lotus Quickr server to use.
    • To prevent collaborative installations from a particular server, leave the connector_install_url element blank:
      <webservices enabled="true">
         <connector_install_url></connector_install_url>
      </webservices>
  3. Save the modified file.
  4. Enter the following command at the server console to restart the HTTP task:
    restart task http 
For example, to use the server quickr.acme.com for collaborative installations, specify the following settings:
<webservices enabled="true">
   <connector_install_url>http://quickr.acme.com/qkrconn.exe</connector_install_url>
</webservices>
Note: Socks proxies in the place connectors for Lotus Notes or Lotus Sametime are not supported. For more information about configuring a forward proxy, refer to http://www-10.lotus.com/ldd/lqwiki.nsf/dx/7.-enable-a-forward-proxy-server-scenario-2

Terms of use

Understand the terms and conditions before you use this publication.

Personal Use: You may reproduce these publications for your personal, non commercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial Use: You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Notices

Copyright information and a list of trademarks.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Vice President
Intellectual Property & Licensing
North Castle Drive
Armonk, New York 10504

U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information (www.ibm.com/legal/copytrade.shtml).

Adobe® is a registered trademark of Adobe Systems Incorporated in the United States, and/or other countries.

Java™ and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT®, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Linux® is a registered trademark of Torvalds in the United States, other countries, or both.

Intel® is a trademark of Intel Corporation in the United States, other countries, or both.

UNIX® is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

End of document