IBM Lotus Connector
Installation and Configuration

Infrastructure preparations

The IBM Domino server must run a service that provides the DIIOP file for external applications.

IBM Documentation: https://www-10.lotus.com/ldd/dominowiki.nsf/dx/DIIOP_Usage_and_Troubleshooting_Guide

Installation

Before installing the IBM Lotus Connector ensure that the Mindbreeze Server is already installed and this connector is also included in the Mindbreeze license.

Configuration of Mindbreeze

Configuration of IBM Lotus Data Source

To connect to the Lotus Domino server and crawl the data source, the following information must be provided:

After configuring the Lotus Domino Server connection, the next step is to specify the databases to be crawled. This can be done by:

1. Searching databases through address books, or
2. Providing database names directly

Both databases and address books through which databases are found can be configured.

For configuring databases and address books check the setting “Advanced Setting” on top-right corner of the “Indices” tab.

Configuration of Address Books

Click on Add Property on the bottom right to add a new address book.

For configuring an address book, provide the following information:

Configuration of Databases

Click on Add Property on the bottom right to add a new database and configure it as follows.

By clicking the Save-button on the top right the settings will be persisted.

Databases and Metadata

By default, only a small amount of metadata is taken from the user-specific databases. A mapping file must be created in order to transfer all required metadata.

With the option "Custom Form Configuration File Path" you can configure a file path that contains a form configuration file.

There are two ways to edit the forms.xml file:

• Automatically Generating the Mapping File
• Manually Creating the Mapping File

Automatically Generating the Mapping File

Use the tool (forms_tool.zip) from the directory:  IBM Lotus as follows:

java -jar ibm-domino-dbinfo.jar <servername[:port]> <username> <password> <database.nsf> [form regex] [field regex]

• If Regex is empty, all forms and their metadata are taken, otherwise only those forms that match the forms regex and those fields/metadata that match the field regex are taken.
• The alias can be viewed in IBM Domino/Lotus as shown in the screenshot below.

Then copy the output into the forms.xml file.

Manually Creating the Mapping File

Open the forms.xml file and add your own mapping.

Example:

  <Form lotusName="content" categoryclass="blog">

                  <Title>$TITLE</Title>

                  <Metadatum lotusName="technorati" name="breadcrumbs"/>

                  <Metadatum lotusName="$UpdatedBy" name="updatedby">

                                               <PostProcessing type="CNExtract" />

   <!--CNExtract ==> CN properties are removed, so that e.g. username remains</!--CNExtract>-->

                               </Metadatum>

                <Metadatum lotusName="OriginalModTime" name="mes:date">

                               <PostProcessing type="ParseDateTime" format="dd.MM.yyyy HH:mm:ss z" locale="en"/>

   <!--So that Mindbreeze can interpret the date-->

                </Metadatum>

                <Metadatum lotusName="safesubject" name="content" fulltext="true" />

                </Form>

...

This configuration means that all objects with the name content are crawled, stored in the database blog and their metadata is mapped as in the example.

Example:

<Metadatum lotusName="technorati" name="breadcrumbs"/>

The lotus metadatum technorati is mapped to the metadata breadcrumbs in Mindbreeze.

To find out the lotusName of the form, you can use the IBM Domino Administrator:

With default settings, Lotus documents index only those attachments embedded in rich text fields.

If the "Index Not Embedded Attachments" option is enabled, all attachments are extracted and indexed.

Document Selection Patterns

It is possible to narrow sources to be crawled. In the following example, only mailboxes of users whose names begin with john are crawled.

Configuring User Mapping

By selecting Map Users via Address Book the ShortName property of the special address book “names.nsf” will be used to transform the identity (the ShortName) of the user to a IBM Lotus account (the FullName).

If you want to provide your own user account to username mapping, enter a file in the “Map Users via File” field.

The file is constructed like a Java-Properties file.

<sso username (SAML,Kerberos,..)> = <Lotus username/FullName aus names.nsf>

Example:

Lotus username==Im names.nsf im Feld/Spalte “FullName“

Configuration IBM Lotus Principal Resolution Cache

In the new or existing service, select the CachingIBMLotusNotesPrincipalResolutionService option in the Service setting. For more information about additional configuration options and how to create a cache and how to do the basic configuration of a cache for a Principal Resolution Service, see Installation & Configuration - Caching Principal Resolution Service.

The IBM Lotus Principal Resolution Cache has the following specific settings:

The other parameters usually do not need to be changed.

Troubleshooting and Recovery

If no data can be found, there are different possible reasons:

• The crawler cannot connect to the Lotus Domino Server or the authentication collapses.
  • Log-File log-ibmlotuscrawler_*.txt gives information about possible problems. Typically the log file resides in this directory:
    • C:\Windows\TEMP\ log-ibmlotuscrawler_*.txt.
    • On Linux you can find the file in /var/opt/mindbreeze/log/log-ibmlotuscrawler_*.txt.
  • Tracing can be activated in the Fabasoft Mindbreeze Enterprise Configuration. You can find more details regarding the configuration of the log level in the Whitepaper for Fabasoft Mindbreeze Enterprise.

• Problems during Filtering/Indexing of data.
  • Warnings and errors can be found in the Applications event log (eventvwr.exe) on Windows systems or in the syslog on Linux systems.