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

The IBM Lotus Principal Resolution Cache has the following settings:

• „IBM Lotus Domino Server Host“: IBM Lotus Domino FQDN of IP address
• „IBM Lotus Domino Server Port“: TCP Port with which one you can reach the DIIOP-file
• „IBM Lotus Domino Login Credential“: username/password credential with read access to the configurated domain catalog and directory databases.
• „Directory Database“: The Directory Database (typically names.nsf where users and groups are saved)
• „Domain Catalog Database“: The IBM Lotus Domain Catalog Datenbase (Default: catalog.nsf)
  Includes the database, ACLs and roles for all available databases in the domain.
• „Database For Role Resolving“: A list of databases its locally defined roles are taken into account.

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