IS1200 Lotus Domino Connector User and Configuration Guide · 2020-03-16 · EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 EMC® SourceOne™ EMC

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® SourceOne™

EMC SourceOne eDiscovery-KazeonVersion 4.5.1

IS1200 Lotus Domino ConnectorUser and Configuration Guide

P/N 300-010-776REV A08

Title Page

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1ii

Copyright © 2009 - 2011 EMC Corporation. All rights reserved.

Published February 02, 2011

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

The IS1200 software is based in part on software licenses from the following:

Outside In® Content Access © 1991-2011, Chicago, Inc.

The software is based in part on the work of the Independent JPEG Group.

Code from Inxight Software, Inc. Copyright © 1996-2011. All rights reserved. www.inxight.com.

Certain icons used by the Kazeon Web applications come from the Silk Icon set(http://www.famfamfam.com/lab/icons/silk/)licensed under the Creative Commons Attribution 2.5 license(http://creativecommons.org/licenses/by/2.5/).

Contents iii

Title Page .......................................................................................................................................i

Figures ...........................................................................................................................................v

Tables ...........................................................................................................................................vii

Preface ..........................................................................................................................................ix Audience..................................................................................................................... ix Related Documentation .............................................................................................. ix Conventions used in this document ............................................................................ ix Where to get help........................................................................................................ xi Customer Support ....................................................................................................... xi Your comments ........................................................................................................... xi

Chapter 1: Introduction About the IS1200......................................................................................................... 2

Extending Server Functionality............................................................................. 2Lotus Domino Background ................................................................................... 2

Domino Connector Implementation Overview ........................................................... 3Domino Connector Implementation In New Installations..................................... 3Domino Connector Implementation Overview ..................................................... 3

Chapter 2: Installation and Configuration Basics Steps To Set Up the Domino Agent ................................................................. 6 Detailed Set Up Steps .................................................................................................. 7

Collecting the Agent Setup Information ............................................................... 7Setting Up the Windows Platform......................................................................... 7

Add Microsoft .Net Framework to the Platform ............................................ 8Add Sun Java to the Platform ......................................................................... 8

Installing the Lotus Notes Client........................................................................... 8Installing the Domino Agent ................................................................................. 9

Is This an Upgrade? ........................................................................................ 9Upgrading ....................................................................................................... 9

First Time Installation ........................................................................................... 9Verifying the Deployment of the Domino Agent Service................................... 13Setting JAVA Max Memory for Tomcat Process ............................................... 14

Contents

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1iv

Contents

Install DIIOP: Configuring a Domino Server for IS1200 Access ....................... 15Configuring the Domino Agent Properties .......................................................... 19Configuring the Domino Agent for HTTPS ........................................................ 19Restoring the Properties Backup.......................................................................... 19Adding the Domino Connector License to the IS1200........................................ 19Testing the IS1200 Connection to the Domino agent.......................................... 20Including the All Documents Folder in Domino Classifications......................... 21

Un-installing the Domino Agent................................................................................ 22 Changing the IS1200 Service Account Username or Password ................................ 23

Chapter 3: Registering Domino Repositories Registering Domino Servers ...................................................................................... 26

Updating the Domino Server Database Cache..................................................... 27 Classifying Domino Servers. ..................................................................................... 28 Using Domino Repositories with Collections............................................................ 31 Searching and Reporting on Domino Servers............................................................ 31 Using Actionable Services on Domino Servers ......................................................... 31 Troubleshooting ......................................................................................................... 32

Appendix A: Configuring the Domino Agent to Use HTTPS Background ................................................................................................................ 34 Security Configuration Procedure.............................................................................. 34

Glossary ...................................................................................................................................... 37

Index............................................................................................................................................ 49

Figures v

Figure Title Page

1 How the Domino Connector Works........................................................................................... 62 Microsoft Download Center Page for Net Framework.............................................................. 83 The IS1200 Manager Page....................................................................................................... 104 Verifying the Domino Agent Was Installed Properly.............................................................. 145 Setting JAVA Memory for the Domino Agent ........................................................................ 156 Setting the “Allow HTTP Clients to Browse database” Flag .................................................. 167 Setting the LDAP Server Port .................................................................................................. 168 Access Control List to: kaz’s Directory Dialog ....................................................................... 179 Kaz Domain: Domino Administrator Dialog........................................................................... 1810 The Access Control List to: Dialog.......................................................................................... 1811 The Web-Admin Licenses Page with Add License Dialog ..................................................... 2012 The Web-Admin Add Repository Tab..................................................................................... 2613 Domino Repository Listing with Database Cache Refresh Icon ............................................. 2814 The Web-Admin Deep Crawl Tab ........................................................................................... 2815 Apache Tomcat Properties ....................................................................................................... 35

Figures

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1vi

Figures

Tables vii

Title Page

1 Support Contact Information .................................................................................................... xi2 Information Needed to Install the Domino Agent ..................................................................... 73 Stop Words............................................................................................................................... 46

Tables

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1viii

Tables

Preface ix

Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up‐to‐date information about product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

AudienceThis guide is intended for Administrators, Business Analysts, and Compliance Auditors and describes how to install and configure the EMC Lotus Domino Connector on the EMC SourceOne eDiscovery ‐ Kazeon (IS1200) and then how to use the EMC Lotus Domino Connector to classify, and search or report on Lotus Domino data repositories.

Related DocumentationIS1200 Installation and Quickstart Guide ‐ describes installing and configuring the IS1200 server software.

IS1200 Web‐Admin User and Configuration Guide ‐ describes using Web‐Admin to setup and manage Kazeon clusters.

IS1200 Web‐Search User Guide ‐ describes using Web‐Search to perform basic and advanced search.

IS1200 Web‐Reports User Guide ‐ describes using Web‐Reports to create and use basic and advanced reports.

IS1200 eDiscovery Case Manager Administrators and Supervisors Guide ‐ for legal representatives, a primer of all the web‐based Interfaces above for performing eDiscovery.

IS1200 Command Line Interface Reference Guide ‐ describes the IS1200 Command Line Interface and all it’s commands.

Conventions used in this documentEMC uses the following conventions for special notices.

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1x

Preface

Note: A note presents information that is important, but not hazard‐related.

Contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to software or hardware operation.

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning.

Typographical conventionsEMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows, dialog

boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions, buttons,

DQL statements, keywords, clauses, environment variables, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs, processes,

services, applications, utilities, kernels, notifications, system calls, man pages, bullet titles

Used in procedures for:• Names of interface elements (such as names of windows, dialog

boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier Used for:• System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown

outside of running text

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

Preface xi

Preface

Where to get helpEMC product, and licensing information can be obtained as follows.Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Customer SupportTo obtain customer support, contact EMC Support through Powerlink, EMC’s online support portal, or by telephone using the information below. Powerlink is the preferred method for opening Service Requests. In addition to many other benefits, the ability to attach files, screen shots, and error messages directly to your request allows EMC personnel to provide faster and more effective support.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you wish to address.

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example

Table 1 Support Contact Information

Support Contact Information

Online Support http://powerlink.emc.com

Licensing Key [email protected] Ask for licensing.

Telephone Support

These numbers supersede any previously published support numbers.

United States: 800-782-4362Canada: 800-543-4782Worldwide: +1-508-497-7901

For additional worldwide access numbers, visit:http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf

Email Not available

To resolve site association difficulties

For questions specific to PowerLink registration or access: [email protected] resolve site association issues or for eServices online support tools: [email protected]

http://Powerlink.EMC.com

http://powerlink.emc.com

http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf

[email protected].

[email protected]

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.1xii

Preface

Chapter 1: Introduction 1

This guide is provided as a companion to the IS1200 Web‐Admin User and Configuration Guide which should be read first as it contains most of the basic IS1200 server setup and maintenance information on which this guide builds.

Topics include:

About the IS1200 ................................................................................................. 2Extending Server Functionality ........................................................................ 2Lotus Domino Background ............................................................................... 2Domino Connector Implementation Overview ............................................. 3Domino Connector Implementation In New Installations ........................... 3Domino Connector Implementation Overview ............................................. 3

Chapter 1: Introduction

IS1200 Lotus Domino Connector User and Configuration Guide— v4.5.12


About the IS1200The IS1200s are integrated hardware and software systems that provide information management solutions enabling organizations to efficiently and cost effectively classify, manage, and retrieve data. They provide consistent information visibility and control across distributed files, minimize the risk of un‐managed files, integrate seamlessly with existing infrastructure, and scale to support billions of files for searching, reporting, and backup search and recovery.

Extending Server FunctionalityThe IS1200’s standard functionality can be expanded with optional add‐on modules like the EMC Lotus Domino Connector. The EMC Lotus Domino Connector requires an additional license for the IS1200 and allows the IS1200 to register, classify, search, and report on Lotus Domino Servers.

Lotus Domino BackgroundLotus Domino is an IBM server product that provides enterprise‐grade email and collaboration capabilities. Originally Lotus Notes Server, it is now an application server for Lotus Notes applications as well as a web server.

The core Lotus Domino services include: an email server, an applications server, a web server, a database server, and a directory server (LDAP). With add‐ins it also provides data integration, instant messaging and web conferencing, document management, collaboration spaces, a mobile application server, and mobile ʹPushʹ synchronization to handheld devices for mail, calendar, contacts, and tasks.

Lotus Domino facilitates the development and dissemination of business projects and information but consolidates those resources into a server environment that the standard IS1200 cannot directly access.

To provide a bridge between the IS1200 and the Lotus Domino servers, EMC has designed the Domino Agent, an interface that runs on its own platform and must be setup independently of the IS1200 and Lotus Domino servers. The Domino Agent allows the IS1200 to register, classify, search, and report on Lotus Domino servers. This capabilities also work with “loose” NSF files on file servers, laptops and desktops.

Note: Encrypted NSFs, encrypted email in NSFs, as well as exclusively locked NSF files or emails are reported as processing exceptions.

The processing power required to effectively run the Domino agent requires a dedicated platform.

Chapter 1: Introduction 3


Domino Connector Implementation OverviewIf the EMC Lotus Domino Connector is ordered with the original IS1200 purchase, the appropriate optional module license is automatically included in the server master license and is routinely installed along with the server license.

If the EMC Lotus Domino Connector is purchased after the original installation, the EMC Lotus Domino Connector license key must be added to the installation before EMC Lotus Domino Connector configuration can occur.

Domino Connector Implementation In New InstallationsThe EMC Lotus Domino Connector software is automatically installed on all IS1200s, the EMC Lotus Domino Connector license key simply activates it.

To use the EMC Lotus Domino Connector purchased with a new installation, simply follow the standard IS1200 hardware and software installation and configuration instructions in the IS1200 Installation and Quickstart Guide and then use the rest of this guide to setup and configure the EMC Lotus Domino Connector.

Domino Connector Implementation OverviewUse the following basic steps to implement EMC Lotus Domino Connector capabilities. See “Detailed Set Up Steps” on page 7 for detailed steps.

1. Collect the basic setup information needed to configure the Domino Agent when it is installed. See Table 2 on page 7 for details.

2. Download the Domino Agent installer from the IS1200 Manager page. See step 1 on page 9 for details.

3. Install the Domino Agent on a dedicated Windows server platform as described later in this guide. This includes:

• Preparing a standard Windows server hardware platform• Installing the JDK applications on the Windows server.• Installing Tomcat and Axis‐2 on the Windows server.• Installing the Lotus Notes Client on the Windows server.• Installing the EMC Lotus Domino Connector on the Windows server.

4. If not already running, start a ʺDIIOPʺ process on the Domino Server.

5. Use Web‐Admin to add the EMC Lotus Domino Connector license key to the IS1200, and then quit and relaunch Web‐Admin.

6. Register the Domino Server as a repository on the IS1200.

7. Perform an initial classification of the Domino server.

8. Run searches and reports on the Domino repositories just like other repositories.



Chapter 2: Installation and Configuration 5

This chapter discusses how to install and configure the EMC Lotus Domino Connector on an EMC SourceOne eDiscovery ‐ Kazeon (!S1200).

Topics include:

Basics Steps To Set Up the Domino Agent ...................................................... 6Detailed Set Up Steps ......................................................................................... 7Setting Up the Windows Platform ................................................................... 7Installing the Lotus Notes Client ...................................................................... 8Installing the Domino Agent............................................................................. 9First Time Installation ........................................................................................ 9Verifying the Deployment of the Domino Agent Service ........................... 13Setting JAVA Max Memory for Tomcat Process........................................... 14Install DIIOP: Configuring a Domino Server for IS1200 Access................ 15Configuring the Domino Agent Properties .................................................. 19Configuring the Domino Agent for HTTPS.................................................. 19Restoring the Properties Backup .................................................................... 19Adding the Domino Connector License to the IS1200 ................................ 19Testing the IS1200 Connection to the Domino agent................................... 20Including the All Documents Folder in Domino Classifications............... 21Un‐installing the Domino Agent .................................................................... 22Changing the IS1200 Service Account Username or Password ................. 23

Chapter 2:Installation and Configuration


Chapter 2: Installation and Configuration

The Domino Agent bridges the IS1200 and Lotus Domino Server by presenting a registered Domino server as a standard file system to the IS1200.

Figure 1 How the Domino Connector Works

This enables the IS1200 to handle the Domino Server as a standard directory, and integrates Domino Servers as standard IS1200 data repositories with only minor modifications to the generic IS1200 components.

A standard Windows platform may be used as the Domino Agent, assuming it meets the requirements stated in “Setting Up the Windows Platform” on page 7.

Basics Steps To Set Up the Domino AgentThe Domino Agent runs as an Axis2 web‐service under the Tomcat servlet container on the Domino Agent platform. The following basic steps must occur to prepare an appropriate platform for the Domino Agent:

Note: The Domino Agent platform hardware is not provided as part of the EMC Lotus Domino Connector and must be provided by the user.

1. Collect the basic setup information needed to configure the Domino Agent when it is installed. See Table 2 on page 7 for details.

2. Setup an appropriate hardware platform as a Windows server, including the Microsoft .Net 2.0 Framework and Java. See “Setting Up the Windows Platform” on page 7 for details.

3. Install the Lotus Notes Client on the platform.See “Installing the Lotus Notes Client” on page 8 for details.

Note: The first two steps must be done before the Domino Agent can be installed, because the installer program checks for Server and.Net before installing.

4. Install and verify the Domino Agent and it’s required support programs on the platform. See “Installing the Domino Agent” on page 9 for details.

5. Set the JAVA memory limits for the Domino Agent platform. See “Setting JAVA Max Memory for Tomcat Process” on page 14 for details.

6. Start a DIIOP process on the Domino Server (if its not already running) to allow the Domino Agent to access the platform. See “Install DIIOP: Configuring a Domino Server for IS1200 Access” on page 15 for details.

7. If your Domino server has been configured to require HTTPS, see “Appendix A: Configuring the Domino Agent to Use HTTPS” on page 33.

8. Add the EMC Lotus Domino Connector license to the IS1200. See “Adding the Domino Connector License to the IS1200” on page 19 for details.

IS1200 Domino Agent Domino Server



9. Test the IS1200 Connection to the Domino server. See “Testing the IS1200 Connection to the Domino agent” on page 20 for details.

10. Decide whether to include the “All Documents” folder in Domino repository classifications. See “Including the All Documents Folder in Domino Classifications” on page 21 for details.

Additionally, if the EMC Lotus Domino Connector was not purchased and installed along with the original IS1200 server, the EMC Lotus Domino Connector license must be added to the IS1200 so the IS1200 will recognize the EMC Lotus Domino Connector platform.

Detailed Set Up StepsThe following sections break out each of the “Basics Steps To Set Up the Domino Agent” above in more detail.

Collecting the Agent Setup InformationBefore beginning the installation or upgrade, collect the following information:

Setting Up the Windows PlatformBecause of the processing load on the Domino Agent—when the IS1200 uses the agent to access your Domino Server—a dedicated PC platform is required for the Domino Agent.

The Domino Agent platform must meet all the following requirements:

Pentium 4 running at 3.0 GHz or better1 Gbyte of RAM or better20 Gbyte or better of available hard drive storageLocated in the same domain as the Domino server

Table 2 Information Needed to Install the Domino Agent

Required Information Information Description Enter information needed here:

Domino User ID The fully qualified internet address of a Domino user (possibly the mailbox administrator) that has access privileges to ALL mailboxes on the Domino server. This will be the same user ID recorded in the IS1200 Identity Vault and associated with the Domino server when it is registered as a data repository. This user ID will be used as a proxy user when opening Domino mailboxes for classification.

Domino User Password Enter the internet password of the Domino user described above.

Administrator ID The username of a Domino Directory Administrator. These credentials are used when LDAP calls are made to the Domino server to fetch the list of users using the mailbox filters (for example in the include/exclude filters).

Administrator Password The password of the administrator described above.



Install the following general system software according to Microsoft documentation. Do not substitute other system software.

1. Install a licensed copy of Windows 2003 Server with SP2.

2. Use Windows Administration Tools/Services to disable IIS Admin and all associated services.

Add Microsoft .Net Framework to the PlatformOnce the basic platform is setup, the Microsoft .Net Framework must be added to the platform. Browse to:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

The Microsoft Download Center page for the Net Framework opens:

Figure 2 Microsoft Download Center Page for Net Framework

Follow Microsoft’s instructions to download the installer and install Net Framework on the platform.

Add Sun Java to the PlatformOnce the basic platform is setup, go to the Sun.com web‐site Downloads section and install the latest version of Java.

Installing the Lotus Notes ClientAfter installing JAVA, the Lotus Notes Client must be installed on the platform. The Notes Client must be purchased separately. Purchase the same Notes Client version (or higher) as your Lotus Domino server.

Follow the instructions that come with the Notes Client package to install the Notes Client on the platform. You can simply accept the defaults on the Install Wizard Custom Setup page, and choose whichever options make sense for your installation on the Ready to Install the Program page.

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en



Installing the Domino AgentOnce the platform has been setup, and the Lotus Notes Client has been installed, the Domino Agent may be installed on the platform. The EMC supplied installer will automatically install Tomcat and other required Java support files before installing the agent, as well as make the required changes to registry values and environmental variables.

Is This an Upgrade?If this is the first time the Domino Agent is installed, skip the following section and go straight to the “First Time Installation” on page 9 section. If you are re‐installing an updated version of the Domino Agent, follow the instructions in the “Upgrading” section (immediately following) and then proceed to the First Time Installation section.

UpgradingSuccessfully upgrading a previously installed version of the Domino Agent requires that the previous version be removed first. However, if you have made changes to the default property settings of the Domino Agent since it was first installed, you should first backup those changes before you un‐install the previous version so they can be re‐implemented after the installation.

If a previous version of the Domino Agent was installed, it must be removed using the Uninstaller that came with the previous version. If the previous version did not provide an uninstaller, remove it using Add/Remove Programs Control Panel.

If changes were made to ʺkazdominoservice.propertiesʺ on the Domino Agent since it was first installed, do the following to backup those changes:

1. On the Domino Agent platform, copy the existing file:<tomcat_install_location>\webapps\axis2\WEB-INF\serv

ices\dominoservice\kazdominoservice.properties

for example:C:\Program Files\Apache Software Foundation\Tomcat5.5\

webapps\axis2\WEB-INF\services\dominoservice.properties

to a temporary location like c:\Tempkazdominoservice.properties.bck"

2. Uninstall the current Agent, see “Un‐installing the Domino Agent” on page 22, or simply use: Control Panel-> Add Remove Programs

First Time InstallationThe agent requires some supporting library files first. Do the following:

1. Copy the file, KazeonDomino.zip (which contains the agent installer files) from the IS1200 to the agent platform by doing the following:



• From a browser window on the agent platform go to: http://<your_IS1200_node_name>/manager,the following page appears:

Figure 3 The IS1200 Manager Page

• Click the Kazeon Connectors link circled above.• From the page at (right): Click

the Lotus Domino Agent link.• When the standard Save dialog

appears, save the zip file it specifies to the agent platform, the desktop is a good place.

• Extract the contents of the zip file to the agent platform. There should be four files extracted, Setup.exe, Infrastructure.msi, and Agent.msi and Uninstall.exe.

2. Run the Setup.exe file.The installer dialog opens.

3. Click Next to continue.

The following screens install the various support software required by the Domino Agent.



4. When the Kazeon Domino Setup Configuration dialog appears:

Leave the defaults in the Infrastructure Component Configuration Parameters section.

Make the following entries in the Domino Agent Parameters section, this information should have been collected in Table 2 on page 7.

Domino User ID: Enter the fully qualified internet address of a Domino user (possibly the mailbox administrator) that has access privileges to ALL mailboxes on the Domino server. This is the same user ID that is recorded in the IS1200 Identity Vault and associated with the Domino server when it is registered as a data repository. This user ID will be used as a proxy user when opening Domino mailboxes for classification.

Password and Re‐enter Password: Enter the internet password of the Domino user (the same password used in the Domino Identity) entered in the step above.

Administrator ID: Enter the Domino Directory Administrator username. These credentials are used when LDAP calls are made to the Domino server to fetch the list of users using the mailbox filters (for example in the include/exclude filters).

Password and Re‐enter Password: Enter the password of the user above.

Click OK to continue.

5. After some time, the following screens appear:

Click Next to continue. Click Next to continue.



6. The Select Installation Folder screen appears:

Leave the default installation location,select the Everyone radio button, and click Next to continue.

7. When the screen at right appears:

Click Next to continue.

8. As the following screens appear:

Click Next to continue, Click Close.

When the Domino Agent finishes installing, the screen at right appears.

This screen is immediately overlaid with the dialog shown in the next step.

9. When the dialog below opens:

Click Yes.



10. When the dialog at right opens, locate the NCSO.jar file, and click Open.

The shot at right was taken by mapping a drive on the Domino Server to the platform running the installation. This allowed the administrator to locate the .jar file on the Domino Server.

If you do not know where to find this file, check with your IS1200/Domino‐Server administrator.

The NCSO.jar file must be installed, and Tomcat must be restarted afterwards. While the installer script does both of these automatically, the file does not have to be added during the install script.

However, if the NCSO.jar file is not added during the install script, and is manually added later, Tomcat must ALSO be restarted manually!

11. When the screen at right re‐appears:

Click Exit to close the installer.

Verifying the Deployment of the Domino Agent Service1. Verify that Tomcat has restarted:

a. From the server Start menu, select: Administrative Tools/Services,The Services Window opens:

b. Select the Apache Tomcat listing, is should show “Started” in the Status column. If it does not, right‐click the listing and select Start.



2. Verify the Domino Agent is installed properly by doing the following:

a. In a platform browser window, open: http://localhost:8080/axis2/services/listServices

a. If the following page appears, the Domino Agent is properly installed.

Figure 4 Verifying the Domino Agent Was Installed Properly

Setting JAVA Max Memory for Tomcat ProcessThe JAVA memory limits on the Domino Agent platform must be increased to accommodate the IS1200 access requirements, do the following:

1. From a Windows Explorer window on the Domino Agent platform,go to C:\Program Files\Apache Software Foundation\Tomcat5.5\bin

2. Run the file tomcat5w.exe (see the screenshot below).

3. From the dialog that opens, click the JAVA tab to select it.



4. Make the Java Options field look like the screenshot below:

Figure 5 Setting JAVA Memory for the Domino Agent

Specifically, ensure the first line looks like this: ‐Xmx512m

Note: This assumes the agent platform has at least 1 GIG of RAM, adjust appropriately for lower RAM situations.

5. Click OK and close out of the Domino Agent platform.

6. If the Apache Tomcat Service is running,restart it from Administrative Tools‐>Services.

Install DIIOP: Configuring a Domino Server for IS1200 AccessOnce the Domino Agent platform has been setup and configured, some configuration steps on the Lotus Domino server itself are necessary to allow the Domino Agent to access the Lotus Domino server on behalf of the IS1200. Your Domino Administrator may need to help with these steps.

The Domino Agent runs as an Axis2 web‐service under the Tomcat servlet container on the agent platform. The Domino Agent uses the IBM Java/Corba toolkit API to connect to the Domino Server. To recognize and work with the Java/Corba API, the Domino Server must be running the ndiiop process.

Do the following to start ndiiop on the Domino Server.

1. If the Domino Server is running, use the server ʺload consoleʺ command to start the ndiiop and nhttp process.

If the Domino Server is not running, ensure that the notes.ini file on the server contains ndiiop and http as one of the tasks. If not modify it as follows, ServerTasks=<any other tasks>,http, diiop and then start the Domino server.

2. For the Domino Agent to browse the Domino Server NSF files, the flag ʺAllow HTTP clients to browse databaseʺ must be enabled.



For example, on Domino Server 8.0.1

a. Open the Domino Administrator, and from the menus select Configuration > Server (Current Server Document) > Internet Protocols > HTTP, the following screen appears.

Figure 6 Setting the “Allow HTTP Clients to Browse database” Flag

b. Select the tabs circled above.c. Under the R5 Basics Header,

Set Allow HTTP clients to browse database as shown (circled).3. Check the setting for the LDAP server port.

a. Select the tabs circled in blue below.

Figure 7 Setting the LDAP Server Port



b. Note the LDAP server port number circled above in red.The default value is 389. If LDAP is running on a different port (as above), then the value in the kazdominoservice.properties should be changed as follows. The properties file is located at:

<Tomcat_install_location>\webapps\axis2\WEB-INF\services\dominoservice

Using the example above, make the bolded change shown below:

#Ldap port for connecting to the Domino LDAP server LdapPort = 389

To:

#Ldap port for connecting to the Domino LDAP server LdapPort = 12389

4. Use the Domino Administrator to create user KazAdmin on the Domino Server.

5. Use the Domino Administrator to give KazAdmin the following rights on the following files:

• Reader Access to <Domain>‐>Configuration‐>Current Server DocumentFrom the Domino Administrator menus, select File > Database >Access ControlThe following screen appears:

Figure 8 Access Control List to: kaz’s Directory Dialog



Select KazAdmin, ensure the Access drop‐down is set to Reader,and set all the options as shown above.

• Designer Access for all files in the folder <Domain>->Files->mail.In the KazDomain tab, select the Files tab, and the screen changes to:

Figure 9 Kaz Domain: Domino Administrator Dialog

Right click mail (circled above) and choose Access Control‐>Manage,the following dialog appears:

Figure 10 The Access Control List to: Dialog



Select KazAdmin and set the options as shown.

Configuring the Domino Agent PropertiesIf the DIIOP Port on the Domino server has been changed to something other than the normal default, then the new value should also be specified in kazdominoservice.properties for the property ʺDiiopPortʺ.

In general, make sure all the properties listed in the kazdominoservice.properties file match the values of the same properties on the Domino Server.

Configuring the Domino Agent for HTTPSIf your organization requires secure connections (HTTPS), then the Domino Server may be configured with a certificate and may require the Domino Agent to communicate with it using HTTPS.

This requires additional setup steps. See“Appendix A: Configuring the Domino Agent to Use HTTPS” on page 33 for details.

Restoring the Properties BackupIf you just installed the Domino Agent for the first time, skip this section.

If you are doing an upgrade over a previous version, and you have property changes that you backed up earlier (see “Is This an Upgrade?” on page 9), then restore the properties from the backup files now.

Compare all the properties in your backup file: c:\Temp\kazdominoservice.properties.bck

to the ones under the current

<tomcat_install_location>\webapps\axis2\WEB-INF\services\dominoservice\kazdominoservice.properties

and change all the current settings to reflect the previous backup’s settings.

Adding the Domino Connector License to the IS1200If the EMC Lotus Domino Connector was not purchased with the original IS1200 server, the EMC Lotus Domino Connector license must be added to the IS1200 before using the EMC Lotus Domino Connector. The EMC Lotus Domino Connector license key is provided in the sales confirmation email received from EMC when the connector was purchased.



To install the key:

1. Open Web‐Admin,

Figure 11 The Web-Admin Licenses Page with Add License Dialog

2. Select Licenses under Administration

3. Click Add License in the tool‐bar to open the Add License dialog.

4. Copy the key from the sales confirmation email, and paste it into the dialog.

5. Click the dialog Add button.

See the IS1200 Web‐Admin User and Configuration Guide chapter Installing License Keys for further details.

Testing the IS1200 Connection to the Domino agentOnce all the steps above are completed, run the test program dominotest to verify the configuration and test the connection between the IS1200 and the Domino agent: The command is installed in /opt/openkaz/bin and provides the following help (usage) if specified without options.

dominotest -v -d <domain> -x <domsrv> -i <identity> [-w <websrv> -p <port>] [-m <mailbox> [-f <folder>]]

-d <domain> : specify the domain for the lotus domino server-x <domsrv> : specify the lotus domino server-w <websrv> : specify the webserver hostname, if not specified it is the same as domsrv-p <port> : specify the port to contact the webservice, if not specified the default is 80-m <mailbox> : specify the mailbox to enumerate, if not specified all mailboxes are

enumerated. For e.g if the specific NSF file to be accessed is under the <Domino_server_install>\data\mail\foo.nsf then you need to specify the value as “mail\foo.nsf”

-f <folder> : specify the folder to enumerate, if not specified all folders are enumerated-v : verbose mode for listing messages-i <identity> : specify the identity configured to connect to the lotus domino server



Do the following from a started cluster

1. Login as root

2. Run the domino test command. For example, to access the file mail\achuak4.nsf on the server domino7 using the agent platform vmlotus1

dominotest -d kazeon -x domino7 -w vmlotus1 -p 80 -m "mail\achuak4.nsf" -i kazadminid

The system responds with something similar to:

Pinging Lotus Domino Server (domino7

Ping Lotus Domino Server (domino7).....Successful

Pinging Kazeon Lotus Domino Services Agent host (vmlotus1)

Ping Kazeon Lotus Domino Services Agent host (vmlotus1).....Successful

Connecting to Lotus Domino Connector.....(domain=kazeon, domsrv=domino7, websrv=vmlotus1, port=80, identity=kazadminid)...Successful

Enumerating Folders in mailbox (mail\achuak4.nsf) on Lotus Domino Server (domino7)

Found 8 folders in mailbox (mail\achuak4.nsf) on Lotus Domino server (domino7)

3. Verify that folders and messages are accessible by running the same command with the -m <nsf_file_path> option to enumerate folders in the userʹs mailbox and with the -m <nsf_file_path> -f <foldername> options to enumerate the messages in the userʹs NSF folder <foldername>.

If these tests are successful and the enumerations are completed, the domino repository is ready to be registered and classified.

Including the All Documents Folder in Domino ClassificationsAll files added to a Domino server are added to both the “All Documents” folder as well as to other directories (categorized by owners, department, etc.) as necessary. Even after files are moved or deleted from their owner folders, they may still be available in the All Documents folder. Consequently, when classifying Domino repositories for eDiscovery purposes you may need to include the All Documents folder.

By default, the IS1200 does not include the All Documents folder, however a configuration parameter is available to include the All Documents folder.

To include the All Documents folder, do the following:

On the Domino Agent box go to. <Tomcat_install_location>\webapps\axis2\WEB-INF\services\dominoservice\kazdominoservice.properties



Open the kazdominoservice.properities file and look for the ʺFolderProcessFlagʺ . Set it to either 1, 2, or 3 according to the following comments from the configuration file:

#The following flag specifies which folders/views will#be processed from an NSF file#The valid values are# 1 : Process content from All Documents and all the other# standard and user defined folders like Inbox, Sent etc.# 2 : Process content from standard and user defined folders like Inbox, Sent etc.# and excluding the All Documents# 3 : Process content from All Documents and exclude# other standard and user defined folders like Inbox, Sent etc.FolderProcessFlag = 2

Un-installing the Domino AgentTo uninstall the Domino Agent, locate the uninstaller program downloaded in step 1 of “First Time Installation” on page 9 above.

Do the following:

1. Run the Uninstall.exe program.

The dialog at right opens.

Click Next to continue.

2. When the warning dialog appears, click Yes to continue.

3. The Uninstall Selection dialog opens. Check the boxes of all components you wish to remove and click OK.

You may want to check only the Domino Agent box as the other supporting files may be needed by other servers running on the same platform.



Changing the IS1200 Service Account Username or PasswordSome companies require that passwords must be changed at regular intervals. After the installation is complete and the system is operational, if the username or password of the IS1200 Service account and/or the LDAP account used by the Domino Agent must be changed, do the following on the Domino Agent platform.

1. Open a command prompt.

2. Change the directory to:<Tomcat_installation_path>\webapps\axis2\WEB-INF\services\dominoservice

3. To update the IS1200 service account userName and/or password, run the following: registerDominoAccount.bat <new_user_name> <new_password>

4. To update the LDAP account userName and/or password, run the following: registerLdapAccount.bat <new_user_name> <new_password>



Chapter 3: Registering Domino Repositories 25

This chapter discusses how to register Lotus Domino servers as data repositories on the EMC SourceOne eDiscovery ‐ Kazeon (IS1200) and then classify and search or report on them.

Topics include:

Registering Domino Servers............................................................................ 26Updating the Domino Server Database Cache ............................................. 27Classifying Domino Servers. ........................................................................... 28Using Domino Repositories with Collections............................................... 31Searching and Reporting on Domino Servers .............................................. 31Using Actionable Services on Domino Servers ............................................ 31Troubleshooting ................................................................................................ 32

Chapter 3:Registering Domino Repositories


Chapter 3: Registering Domino Repositories

Registering Domino ServersTo classify files or email on Domino servers, you must first register the Domino server as a data repository on the IS1200. Registering a Domino Server is slightly different than registering NFS or CIFS filers. First, see the Registering and Managing Repositories chapter of the IS1200 Web‐Admin User and Configuration Guide for general information on registering repositories, then return here for details on registering Domino servers.

As with any repository, a metadata file system must first be registered and available before a Domino server can be registered. Because Domino servers can contain large amounts—terabytes—of data, a single dedicated metadata file system should be created for each Domino server that will be registered. Before continuing, create and register a metadata file system for each Domino server that will be registered. See the Registering and Managing Repositories chapter of the IS1200 Web‐Admin User and Configuration Guide for information on registering metadata repositories.

Note: Starting with v4.5.0, all IS1200 versions require specific agent versions to work with optional modules that required agent‐accessed repositories. If the required agent version is not installed when an attempt is made to register, or bring on‐line, a connector‐accessed repository (for instance after an IS1200 upgrade), the repository will not be registered, or will be placed in the “disconnected” state until the agent is updated to the required version.

Use the following procedure to register a Domino server as a data repository.

1. From Web‐Admin, click Lotus Domino Server under Repositories in the left‐navigation pane, The Add Repository tab appears:

Figure 12 The Web-Admin Add Repository Tab

Note: The Lotus Domino Server menu item will not appear unless you have a Lotus Domino license installed. See “Adding the Domino Connector License to the IS1200” on page 19 for details.

2. Ensure that Lotus Domino is selected in the Repository Type drop‐down menu.

3. Fill in the following fields:



Name. Enter a repository reference name (the IS1200 will use this name whenever listing this Domino repository in IS1200 menus). Repository names must be unique.

Metadata Repository. From the drop‐down menu, select the metadata repository created and dedicated to this Domino server, or leave as <auto select> to allow the IS1200 to pick an appropriate metadata directory. This metadata repository is described on the previous page.

Lotus Domino OptionsIdentity. From the drop‐down menu, select an identity containing a username and password that has administrator access rights to the Domino server, or use the Create Identity button to create a new identity with those privileges. An identity containing the same username and password registered for KazAdmin (in step 4 of“Install DIIOP: Configuring a Domino Server for IS1200 Access” on page 15) on the Domino server can be used here. See the IS1200 Web‐Admin User and Configuration Guide chapter The Identity Vault for more information about identities.

Domino Server. Enter the hostname or IP address of the Domino server to register as a repository.

Connector Server. Enter the pathname or IP address of the EMC Lotus Domino Connector (the Domino Agent platform) created and configured in the previous chapter to access your Domino servers.

Connector Port. Leave the default of 80 as is, unless your IS1200 Administrator indicates otherwise.

Specify Use: Leave the Source Repository radio button selected. Domino servers may only be registered as source repositories, they cannot be targets.

4. Click Submit to register the Domino server as a repository.

Updating the Domino Server Database CacheDomino servers may contain many thousands of mailboxes or NSF file paths. The IS1200 maintains a database cache of these to make selecting individual mailboxes or NSF file paths (for instance when setting up classifications or collections) as quick as possible. The database cache is setup and recorded to disk immediately after the Domino server is registered with the IS1200 as a data repository.



If you need to update the cache, simply click the Refresh button (circled below) next to any Domino repository listing in the Web‐Admin Repository View.

Figure 13 Domino Repository Listing with Database Cache Refresh Icon

Clicking the Refresh icon opens the dialog shown above and starts a new Domino Database Cache Update job.

Classifying Domino Servers.To deep classify a Domino server do the following:

1. From any Web‐Admin page, click Deep Crawl under Jobs in the left navigation pane, the Deep Crawl tab opens.

Figure 14 The Web-Admin Deep Crawl Tab

2. Ensure that Lotus Domino is selected in the Show drop‐down menu.

3. Add Source button: If a Domino repository needed does not appear in the Repositories scroll‐box, then click the Add Source button to open a new Add Repository tab where you can add the required new repository.

4. Description. Optional, enter a description for the deep crawl.

5. Repositories. Click‐to‐select any Domino repository in the available listing (the left‐hand scrolling list), and click the Right Arrow ( ) button to add it to the list to classify (the right‐hand scrolling list). Click any listing in the right‐hand list, and click the Left Arrow ( ) to remove



it from the list to be classified. Once a repository is listed in the right‐hand box, the listing may be double‐clicked, or selected and the icon clicked, to edit that line manually.

Most Domino repositories contain large numbers of mailboxes and NSF paths that don’t all need to be classified. These can also be selectively added to the classification list using the Right Arrow as described above.

To select individual mailboxes or NSF paths, click the plus sign preceding any Domino server listing to expand it, as shown at right.

Click the Browse link to open the dialog at right.

Select one of the following radio buttons: By Mailbox Name to show or search for NSF mailboxes, or By NSF File Path to show or search by NSF file paths.

If you don’t see the mailbox or file path you need, click the Refresh icon to update the Domino Server Database Cache,see “Updating the Domino Server Database Cache” on page 27 for details.

Use the Find: field to search for specific mailboxes or NSF paths. The standard wild card (asterisk, “*”) may be used in searches.

When the By NSF File Path radio button is selected, the Find: drop‐down menu displays possible search results as you enter a search path.

Once the Browse Directory dialog displays the listings you need, click any single listing, or use shift‐click or cntrl‐click to make multiple selections, and then click the Add Selected button to add the selected mailboxes or filepaths to your current selection.

Repeat until all desired listings are selected and then click the Close button.



After clicking Close, the Browse Dialog disappears and the Repositories left‐hand scroll‐list reappears with your choices listed as shown at right.

Use the Right Arrow button to move these listing into the right‐hand scroll list.

6. Click the Advanced Options header expander triangle circled below

to open the Repository Filters sections.

Click the Exchange/Domino tab to display Include, Mailbox Filters, Folder Filters, and Date Filters for use with Domino Servers. You may enter Domino mailbox names or NSF file paths in these filters.

When specifying what mailboxes or folder to include or exclude, you can enter strings with wildcards, for example: Include: t* or Exclude: A*

These strings are case sensitive and may not use bracketed RegEx expressions.

7. Fill out all other Job Scheduler pages and fields as described in the IS1200 Web‐Admin User and Configuration Guide manual to finish scheduling the deep crawl. Date filters must be provided.



Using Domino Repositories with CollectionsCollections from Domino servers, both from Web‐Admin or the eDiscovery Case Manager, are done the same as with other repository types, except that when making the Repositories selections, Domino mailboxes or NSF file paths may be selected to collect from in the same manner as described above in step 5 on page 28 .

Searching and Reporting on Domino ServersDomino servers are searched using the Web‐Search interface. See the IS1200 Web‐Search User Guide for general information on using Web‐Search.

Reports are done on Domino servers using the Web‐Reports interface. See the IS1200 Web‐Reports User Guide for general information on using Web‐Reports.

Both searches and reports on Domino servers are created and scheduled the same way as searches and reports on other repositories.

Note: The EMC Lotus Domino Connector indexes only email messages and attachments (or composite objects containing email and attachments) on Domino servers and does not provide classification or indexing services (and hence cannot search or report on) the following information on Domino Servers:

Calendars, Contacts, Notes, Shared/Public folders on Domino servers

Using Actionable Services on Domino ServersAfter using searches or reports on Domino servers, some Actionable Services can be performed on the results. For complete information about using Actionable Services see the Actionable Services chapters of the IS1200 Web‐Search User Guide and the IS1200 Web‐Reports User Guidee.

Generally, Domino servers may not be selected as the targets of Actionable Services, regardless of the result sources. In other words, neither search nor report results from any kind of repository (Domino or otherwise) can be copied or moved TO a Domino server.

When the target for an Actionable Service is not an Domino server (for example an NFS or CIFS repository), the following applies:

From the Actionable Services Manage Files menu:• Result files can NOT be moved from an Domino server to another repository• Result files can be copied from and Domino server to another repository• Result files can NOT be deleted, restored, or locked on Domino serversSearch result files from Domino servers can be Re‐ClassifiedSearch result files from Domino servers can have new Metadata Tags or Policy Groups added to the appropriate metadata repositorySearch result listings from Domino servers can be exported to XML or CSV files



Search result files from Domino servers may be downloaded to other repositories as PST files, but NOT as NSFs!

Note:While some Actionable Services, like Delete and Download to NSF, cannot be applied to search and report results from Domino servers, the services still appear in Actionable services menus to allow services across multiple repositories (which all may, or may not, be Domino servers). If these services are applied to Domino repositories, some results may be skipped, and the job will report failures.

TroubleshootingStarting with v4.5.0, all IS1200 versions require specific agent versions to work with connector‐accessed repositories like the Domino Agent. If the required agent versions is not installed when a connector‐accessed repository is registered, updated or patched, or brought back on‐line for any reason, the repository will not come on‐line until the agent is updated to the required version.

Appendix A: Configuring the Domino Agent to Use HTTPS 33

This appendix discusses how to configure the EMC Lotus Domino Connector to work with security certificates and networks that require secure (HTTPS) connections.

Topics include:

Background........................................................................................................ 34Security Configuration Procedure.................................................................. 34

Appendix A:Configuring the Domino Agent

to Use HTTPS


Appendix A: Configuring the Domino Agent

BackgroundIf your organization requires secure connections (HTTPS), then your Domino Server may be configured with a certificate and may require the Domino Agent to communicate with it using HTTPS. This requires additional setup steps. This appendix describes those steps.

Security Configuration ProcedureThe steps below are necessarily general, as it is not the purpose of this guide to repeat all the detailed instructions of the Domino Server User and Configuration manual. For specific details on how to accomplish the general steps below, see your Domino Server documentation.

To modify the Domino Agent to use HTTPS, do the following:

Note: If Domino Server files “keyfile.kyr” and “keyfile.sth” already exist,skip to step 3.

1. Create a key ring on the Domino Server. Open the Server Certificate Admin (certsrv.nsf) database on a Domino Server and use its forms to create and populate a key ring. See Domino Administrator Help for detailed information.

2. Move the keyring to the server. The keyring consists of a keyring file (KYR file) and a stash file (STH file). These files are generated on the computer used to access the Server Certificate Admin database. Move or copy the two keyring files to the Domino Server, under the data directory. For example, if you create a keyring with a self‐certified certificate using the default names (selfcert.kyr, and selfcert.sth) and copy the files to the Domino Server data directory, then the following two files should be found on the Domino server at:

<domino_server_install_location>\data\selfcert.kyr.

<domino_server_install_location>\data\selfcert.sth.

3. Once the keyring files are on the server, starting or restarting the DIIOP task generates a file called “TrustedCerts.class” in the data directory.

Appendix A: Configuring the Domino Agent to Use HTTPS 35


Copy “TrustedCert.class” to the Domino Agent platform ( <tomcat_install_location>\certs ) and put it in the classpath along with NCSO.jar as follows by running the utility “<tomcat_install>\bin\tomcat5w.exe”.

Go to the Java tab and under the Java Classpath and add the following entries.

<tomcat_install>\ webapps\axis2\WEB‐INF\lib\NCSO.jar;

<tomcat_install>\certs

Be sure the entries for Initial Memory Pool and Maximum Memory Pool are the same as shown above.

4. Verify the SSL configuration for the Domino Server by doing the following:

a. Open the Domino Administrator.b. Under the Current Server document, go to tab Ports‐>Internet Ports.c. Under the SSL settings specify the SSL key file named. (for example “selfcert.kyr”).e. Go to DIIOP tab and check that the SSL port no is correct. Default is

63149. Enable the SSL port.f. Set the Name & Password and Anonymous authentication settings as desired. Based on the settings in step e.) above, indicate the corresponding settings in Domino Agent configuration file “kazdominoservice.properties” by changing the configuration values:

HTTPRedirectToSSLNamePasswordEnforcedAnonymousAccessAllowed.

found at:

<tomcat_installation_folder>\webapps\axis2\WEB-INF\services\dominoservice\kazdominoservice.properties

Use the configuration file comments to decide how to set these values.

Figure 15 Apache Tomcat Properties



Glosssary 37

This glossary contains terms related to disk storage subsystems, networks, file management, and eDiscovery. Many of these terms are used in this manual.

AActive Directory (AD) A technology created by Microsoft that provides a variety of network services,

including: LDAP‐like directory services, Kerberos‐based authentication, and DNS‐based naming and other network information.

Actions,Actionable Services

Services such as copy, move, delete, tagging, etc, that can be applied to search and report results and allow the IS1200 to be an effective file management tool for registered repositories.

Access Control List(ACL)

A file system level data file that specifies how users or groups may access resources on a computer or network, like an application, file or printer, and the rights they have to it, for example read access, write access, and so forth.

Advanced Search A search made from the IS1200 Advanced Search link. Allows searching for extracted metadata by tag‐value pairs, and allows multiple variable and boolean searches.

Assignment Rules An assignment rule is a type of classification rule. It tags files with metadata and assigns files to policy groups. Assignment rules are contained in Assignment Rule Sets (ASRs). See the Policies: Classification, Extraction and Assignment Rules chapter of the IS1200 Web‐Admin User and Configuration Guide for more details.

Auditing A service that allows the IS1200 to record all system events according to who did what, when, and the event result. This data is especially useful to Legal Service Providers when providing an audit trail for responsive data produced during eDiscovery. Complete details are available in the Auditing and Data Verification chapter of the IS1200 Web‐Admin User and Configuration Guide.

Authorization Rule A policy rule that filters search results to ensure that the assigned files can only be viewed by authorized users. IS1200 authorization policies may be used to add additional levels of security to the Access Control Lists (ACLs) for file objects found in registered data repositories. See the Policy Groups: Authorization Policies chapter of the IS1200 Web‐Admin User and Configuration Guide for more details.

Authentication The process of identifying users based on user name and password to ensure that only authorized users can access the IS1200.

Glossary

Glosssary38

Glossary

BBasic Search A search made from the Search page using only the Search field. Searches only the

content found in the fullText field populated during classifications.

CCAS Device EMC’s Content Addressed Storage (CAS) devices are cluster‐able archival devices

that host archival business file content such as email, office productivity files (like word processing and spreadsheet files), images, and other file documents.

CASID A unique IS1200 ID for each classified file that the system generates during basic classification.

Centera Server The EMC Centera server is a networked storage system specifically designed to store and provide fast, easy access to fixed content (information in its final form). It is a CAS device providing long‐term retention and assured integrity designed to store and manage data that require or have legally mandated retention periods, for example medical records and files relevant to legal matters.

Celerra Server An EMC server designed to store and manage archival data. The Celerra File Level Retention (FLR) server also allows enforcing enterprise or governmental retention policies.

checkpoints,checkpointing

Checkpoints and checkpointing allow IS1200 jobs and services to resume more efficiently if the job or service is paused or stopped before it completes. Basically, the IS1200 records “bookmarks” about what file or object was last processed. This allows the IS1200 to skip to the bookmark—the checkpoint—when the job or service is resumed, and avoid reprocessing all the files and objects already processed.

However, checkpoints are not set for every file accessed, instead most jobs divide file processing into “batches” and the checkpoints indicate where batches started. Consequently, when a job restarts at a checkpoint, some objects may be reprocessed again and—in cases such as a ʹCopyʹ service with ʹenable‐versioningʹ option selected—duplicate versioned files will be created on the target repository when those objects are reprocessed.

Classification Rule Rules that the system implements during data classification to extract metadata, tag files, and assign files to policy groups. The two types of classification rules are extraction rules and assignment rules.

Classification Service Sometimes called a “crawl”. An IS1200 service that accesses job‐specified registered repositories and extracts and records their metadata to later facilitate comprehensive and cross‐repository searches. Classifications extract metadata according to extraction rules, compute digests for all objects, and assigns files to policy groups according to assignment rules. See “Assignment Rules” on page 37, “Extraction Rules” on page 42, “Hash Values” on page 42, and “Policy Groups” on page 45 for more details.

Classifications may be “full”, every object in the specified repositories is parsed and it’s metadata repopulated in the indexes and databases, or they may be “differential”, see “Differential Classifications” on page 41 of more details.

Cluster A set of IS1200 appliance nodes working as a unit. A cluster can contain a maximum of four nodes. A cluster can be used to control other clusters, see “Information Center Server” on page 43 for details.

Glosssary 39

Glossary

CASContent Addressable

Storage

Rather than address data objects by a file name, at a physical location, a CAS device uses a content address (hash‐code identifiers) based on file contents to store file objects in a flat file system that maximizes storage efficiency. This returns a unique identifier (Content Address) used to store and retrieve data objects.

CSVComma Separated Values

A file type used to transfer data between applications such as databases and spreadsheets.

CLICommand Line Interface

The CLI is a traditional command line interface that allows direct communications with the IS1200 “backend” using a the set of commands defined in the IS1200 Command Line Interface Reference Guide.

Concepts Search The standard IS1200 software supports keyword exploration. However, in the initial stages of the legal discovery process (often called eDiscovery), keyword search alone may not be as concise or as time‐efficient as required by standard legal timetables.

Concepts augments standard keyword searching by automatically suggesting filters based on the results of a current search. By default it looks for concepts based on persons, countries, noun groups, organizations, company names, and products.

Concepts Search is an optional module that requires an additional license key for each IS1200 cluster node. See the IS1200 Concepts Search User and Configuration Guide for complete details.

conceptfinder Ruleset The conceptfinder ruleset is an assignment ruleset that extracts the concepts listed in the Web‐Search Results Grouping Concepts pane, which is only available when a valid Concepts license is installed on the IS1200. The conceptfinder ruleset must be used in deep classifications to get the best results in Web‐Search from the Concepts heading of the Results Grouping pane.The ConceptFinder_DWF assignment ruleset combines both the conceptfinder ruleset and the DocsWithoutFullText ruleset. See “DocsWithoutFullText Assignment Ruleset” on page 41 for more details.

connectors Connectors are IS1200 optional modules that allow an IS1200 to work with repository types beyond the standard CIFS and NFS repositories. See “optional modules” on page 45 for more details.

Optional module connectors require separate licenses to be purchased and installed on all nodes of an IS1200 cluster. For a complete list of optional modules available, see the Introduction chapter of the IS1200 Web‐Admin User and Configuration Guide. Some connectors, such as the Microsoft Exchange Server Connector, require agents. Agents are additional server platforms, usually Windows servers, that provide the additional CPU cycles and network staging the IS1200 needs to work with the repository types they connect to.

All connectors have their own user guides which can be accessed from the Kazeon Documenation link on the IS1200 Manager page (https://<yourIS1200Name>/manager).

Container file/object A file (object) that contains other files (sub‐objects), such as a ZIP, TAR, JAR, and PST or NSF files. The container file is often called the “parent” and the contained objects are called “children”. Container objects should not be confused with files that have embedded objects, such as Microsoft Word files that have embedded charts or graphics (OLE).

Custodian A legal term used by Legal Service Providers (LSP) and other legal personnel to describe the owners or responsible parties for electronic documents pertinent (responsive) to a legal matter.

Glosssary40

Glossary

DData A file of any type and size such as a short email, a word processor document, or a

large spreadsheet.

Datamap A report that lists the electronic storage locations of all possible sources of relevant ESI. This can include standard file servers, groupware servers, email servers—and their backup and archive systems—as well as custodian’s desktop and laptop computers.

Data-Mount The NFS file system that is accessed by the IS1200 to parse data and extract metadata.

Data Server The file server that exports an NFS or CIFS file system so that the IS1200 can classify data on the file system to create metadata.

Data-Share The CIFS file system to be accessed by the IS1200 to extract metadata.

Data Repository A networked file system registered with the IS1200 so it can be classified, searched, and reported on. Data repositories created on the IS1200 itself (sometimes called localdatafs) are strongly discouraged!

Data Verification Builds on Auditing and is only available when system auditing is enabled. For job services like Actionable Services Copy or Move, Legal Hold Copy, and Single Step Collections, Data Verification generates an audit trail proving that files were not altered during these actions. This is especially valuable in eDiscovery situations.

Complete details are available in the Auditing and Data Verification chapter of the IS1200 Web‐Admin User and Configuration Guide

Deduplication A process that identifies file or email object and sub‐object duplicates based on their digest values. Digests are numerical values that are calculated based on file and email contents and are unique for all unique objects. Digest values allow objects to be compared very quickly. Digests are calculated during basic and deep classifications or during collections when indexing is enabled.

Digests are calculated differently for standard files, emails, and container objects. For standard files, a physical digest is computed for the entire file much like a hash value. For email objects, just the subject, the message content (including attachments), and certain specific addresses are combined and an email digest value is calculated from the combination. Container objects, like ZIP or PST files, and their sub‐objects have digests calculated both as complete objects and as individual sub‐objects.

Note: Calculating email digests requires access to the email object’s fullText and only classifications that include the fullText rule can produce email digests. Emails classified without the fullText rule receive the same physical digest that other files do. Consequently, identical emails on different repositories, one classified with and one without the fullText rule, will not be identified as duplicates!

Deduplication may be applied to export processes (Actionable Services like Download, Legal Export, and Copy) to create only unique copies of file and email objects and sub‐objects to a destination.

When the deduplicate option is used along with the Generate Manifest option, a manifest summary and a detailed list or report may be produced to identify all duplicates that were ignored in the export process, allowing them to be identified later.

Reduplication may also be applied to tagging processes to allow a single file copy to be reviewed, but apply metadata tags to all its copies.

Glosssary 41

Glossary

Domino Sever (Lotus) A Lotus server providing groupware solutions and storage.

Domino XML Language(DXL)

A Lotus version of eXtensible Markup Language (XML) used to import and export Lotus email files.

DocsWithoutFullTextAssignment Ruleset

Some file objects, such as graphics files (examples are.jpeg, .gif, or .bmp files) contain no text, and hence will have no fullText extracted by the FullTextRuleset, see “fullText” on page 42 for more details. In legal cases, these files may still contain responsive information, but not textual information that can be located by text searches. The DocsWithoutFulltext assignment rules identifies these files and adds the metadata tag and value “DocWithoutFulltext=true” to all files that contain no searchable text. This allows these files to be easily searched for later, and inspected for legal responsiveness by non‐search methods.

The ConceptFinder_DWF assignment ruleset combines both the DocsWithoutFullText ruleset with the conceptfinder ruleset. See “conceptfinder Ruleset” on page 39 for more details.

Note: Parent file objects that don’t contain text (such as .zip, .tar, and .pst files) are not tagged with the DocWithoutFulltext tag.

Documentum Sever(EMC)

The EMC Documentum server manages business content including documents, photos, video, medical images, e‐mail, Web pages, fixed content, XML‐tagged documents, etc. The Documentum core is a repository that stores content securely under compliance rules and appears as a unified environment, even though content may reside on multiple servers and physical storage devices within a distributed environment.

DifferentialClassifications

Differential classifications do not re‐classify all file objects in the selected repositories. Instead, they examine the metadata from previous crawls, and if there is no previous metadata (indicating the object is new since the last classification) or has changed (based on atime, or mtime changes), then the object is parsed and it’s metadata re‐populated in the database.

EeDiscovery The process of reviewing electronic files to determine their relevances and

responsiveness to a legal matter or case.

eDiscovery Case Manager A IS1200 web‐application that facilitates eDiscovery for Legal Service Providers.

Electronic DiscoveryReference Model

(EDRM)

The EDRM was a Project created to provide standards and guidelines for the electronic discovery market. The model defines a common, flexible and extensible framework for the development, selection, evaluation and use of electronic discovery products and services.

Enterprise Vault A Symantec networked repository for archived email.

eth1, eth2 Most IS1200 platforms require two ethernet connections for proper deployment. These connections are called eth1 and eth2, must each have unique IP addresses, and must be GigaBit, or 1GB/sec or better, connections. Additionally, all network segments between eth1 and all registered metadata and data repositories must be gigabit! eth1 is used to communicate between the IS1200 and its registered repositories. The IS1200 hostname should be DNS mapped to the eth1 IP address. eth2 must be connected to a private network between the IS1200 nodes and is used to coordinate and balance system wide operations.

Glosssary42

Glossary

Extended Attributes User‐defined keywords that are extracted during data classification.

Extraction Rules Extraction rules are a type of classification rule. They extract user‐defined keywords (custom metadata) to add to the metadata file. Extraction rules are grouped into Extraction Rule Sets (ERSs). See the Policies: Classification, Extraction and Assignment Rules chapter of the IS1200 Web‐Admin User and Configuration Guide for more details.

Exchange Server (Microsoft) A microsoft server designed to store and manage email.

FFederation A defined group of member‐clusters on a Federation server that can be managed,

searched, and reported on as a group. Member‐clusters are referred to as Federated clusters.

Federation Server An single‐node IS1200 server, with a Federation license, that allows consolidated searching and reporting of up to eight Federated member‐clusters of its defined Federation.

Filer A file server that exports its file systems using NFS or CIFS protocol.

fullText fullText is the “content” portion of a file, for example this is the textual content of word processing files and the message body of emails. fulltext is an extraction rule that is used to save file textual content as metadata to the Search Index during classifications. It saves up to 10 megabytes of content by default. This default may be changed, but it is not recommended. Fulltext extraction is required by Web‐Search for the Previewer pane to work and to generate Concepts in the Results Grouping pane.

fulltext, is extracted differently for container objects and sub‐objects, and for files with embedded objects.

Container objects (such as ZIP or PST files) and their sub‐objects are classified individually and the fulltext of the parent container file, and for each child sub‐object, is extracted and added to the relevant metadata repository separately.

Files with embedded objects (such as a Microsoft Word file with and embedded spreadsheet), are classified together. The fulltext of the embedded object is included in the fulltext of it’s parent object and not collected separately.

For more details on fullText, see Chapter 1 of the IS1200 Metadata Reference Guide.

GGroupware Collaborative software designed to help people involved in common tasks achieve

their goals. Incorporates services such as email, calendaring, text chat, wiki, web‐sharing, document control, and advanced search.

HHash Values Hash values are used to compare one file with another for duplicates.

An extremely simplified description of hashing is that the numeric values of all bytes in a file are added into a grand total. The chances of two different files yielding the same result (hash value) are remotely small, so hash values can be used to identify duplicate files, or compare files with the same name to decide if they have been modified.

Glosssary 43

Glossary

Computing hash on an entire file is called a full‐hash, and computing hash on a portion of the file is called a partial‐hash. A “partial hash” may also be used to increase classification speed and “hashing” can be turned on, or off to increase classification speed.

Iidentity A single entry in the Identity Vault database. The identity contains a single username

and password that the IS1200 can retrieve when it needs to access a registered data or metadata repository or other server like and authentication service.

Identity Vault An encrypted database of usernames and passwords the IS1200 uses to store the credentials used to access registered data repositories, send email notifications, and work with authentication services.

Information CenterServer

The standard IS1200 server offers clustering as a scalable solution for classifying, searching, and reporting on registered network repositories. While clustering is ideal for scaling to large numbers of files on a LAN, it is not a viable solution for WANs. Enterprises with multiple IS1200 clusters deployed, or IS1200 clusters deployed in remote offices need the ability to setup and manage unified reports and searches across all their clusters. The IS1200 Information Center server provides this solution.

Each Federation server supports one federation. A Federation may have up to eight clusters (with four nodes each) included in it. Once a federation is establish it becomes a central management point allowing classifications, search, and reports to be setup on managed on all the federations members from the Information Center server. See the IS1200 Information Center User and Configuration Guide for complete details.

Intelligent PlatformManagement Interface

(IPMI)

IS1200 clusters may contain more then one node. Normally each node communicates with the others to share information and workload.

The IS1200 appliance includes an Intelligent Platform Management Interface (IPMI) to shut down nodes when individual nodes or software errors would degrade the overall cluster performance. The IPMI is an autonomous micro‐controller—installed in all cluster nodes—used by the cluster’s “leader” node to power down nodes with errors or performance problems. The IPMI requires its own unique IP address, but communicates over the eth1 port, see “eth1, eth2” on page 41 for more details.

KKazeon EVAgent An IS1200 service, installed on the Enterprise Vault server, that allows the IS1200 to

directly open and access Enterprise Vault email for classification services.

Kaz-mount The NFS file system that is the IS1200 metadata repository. on which the IS1200 stores metadata.

Kazeon Query Language A programming language used in classification and assignment rules to identify files that should received specified metadata tags.

Kaz-server The file server where the metadata repository is located.

Kaz-share The CIFS file system on which the IS1200 stores metadata.

Kaz Schema Defines the set of metadata fields used to build a Search Index for registered data repositories (file systems).

Glosssary44

Glossary

LLegal Hold Files placed on legal hold are either copied to a secure secondary location where they

can preserved for later use, or are locked in their original locations against further change until a legal matter is resolved.

Legal Service Provider (LSP) A lawyer or trained legal professional that provides legal services for a fee.

Local Refers to the local resources (usually the metadata repository) of the Federation server.

localdatafs A data repository created on the IS1200 itself. This practice is not recommended.

localkazfs A metadata repository created on the IS1200 itself. This practice is not recommended.

Logging rule Logging rules audit user actions on files such as file access, creation, modification, and deletion.

MManifest Reports Manifest reports reconcile Actionable Services object‐counts with the search result

object‐counts they are performed on because processes such as deduplication can result in the two counts not matching. The reports details the count differences and the reasons for the differences.

Member-cluster Any of the clusters registered to a particular Federation.

Metadata Data about data. Metadata is used to search for information and to create reports. Metadata can be file system or custom metadata that the IS1200 extracts from files during classification. file system metadata includes file type, and file path extracted during basic classification. Custom metadata is generated during deep classification.

Metadata Repository A registered repository the IS1200 uses exclusively to record the metadata extracted during classification services on the registered data repository the metadata repository is mapped to.

The primary metadata repository is the host of the repository registration database, the report results database, Environment Discovery job results, Auditing and Data Verification databases, and miscellaneous databases the cluster requires for routine operation. Collectively these are called the Cluster Data Base.

Metadata repositories created on the IS1200 itself (sometimes called localkazfs) are strongly discouraged!

NNetwork File System

(NFS)A protocol used primarily by Unix based computers for accessing computer systems and filers over the internet.

Network InformationSystem (NIS)

A network naming, administration, and authentication system for smaller networks that was developed by Sun Microsystems and is used primarily by Unix systems.

Node A single IS1200 appliance.

Notes Storage File(NSF)

A standardized storage file format used by Lotus to store email, attachments, notes, calendars, etc.

Glosssary 45

Glossary

Ooptional modules The standard IS1200 license provides a default set of features that allows the IS1200 to

register, classify, and search and report on CIFS and NFS data repositories. Optional modules are additional software licenses that can add further capabilities, such as being able to work with repository types other than CIFS and NFS, or providing Concepts Search capabilities, or applying legal hold. For a complete list of available optional modules, see the Introduction chapter of the IS1200 Web‐Admin User and Configuration Guide.

PPEA Files A Pool Entry Authorization (PEA) file is generated by the Centera server

administrator. A PEA file defines what applications and users can perform read, write, delete, query, copy, or hold operations for Centera objects.

Policy Groups Associates one or more authorization rule and logging rule with one or more files to protect information and audit user actions on files.

PST Files Personal STorage files are generally used by email programs like Microsoft Outlook to store user email locally. PST files are also called “composite” files, because they are packages meant to efficiently store a number of smaller related files. Another example of a composite file is a ZIP storage file

RRetention The process of enforcing corporate or legal standards for how long certain kinds of

files must be preserved for access. Examples of retained files include files responsive to legal matters and medical records.

Roles All IS1200 users have a role, either admin, auditor, or end-user. If a legal license is installed, there may also be legaladmin, legalsupervisor, legalreviewer, or a custodian. Roles determines what parts of the IS1200 interface may be seen, and how much of search and report results are displayed.

SSearch Index An IS1200 database that stores and indexes the file content metadata (including

extended attributes, and fullText) for standard and custom user‐defined metadata produced by extraction rules during classifications.

SharePoint Sever(Microsoft)

A Microsoft server in the groupware category.

snippets A snippet is a sub‐set of a document’s actual content. After a keyword search completes, result snippets are created as small standard size chunks of data taken from the text surrounding a search query hit. For example, if a search is made for “medicine”, the snippet will contain about 300 bytes of the text surrounding the paragraph where the word “medicine” was found. If multiple search hits are found, the most relevant hit is used to create the snippet. For searches made without keywords, snippets are simply the first 300 bytes of file text.

Snippet size is configurable, see the Configuration Files and Utilities appendix of the IS1200 Web‐Admin User and Configuration Guide for details on setting snippet size.In all cases, snippets are taken from the result file’s fullText.

Glosssary46

Glossary

SourceOne Archive Server(EMC)

The EMC SourceOne server is a comprehensive, policy‐based system that automatically collects, organizes, indexes and retains messages and associated attachments and stores them in designated archives connected to shared storage. EMC SourceOne provides indexed searching that works with both EMC storage and other brands such as IBM or NetApp.

stop words Stop words consist are the most commonly used words in sentences, such as “a”, “an”, “the”, and .”and”. If indexed individually, they would consume excessive amount of metadata storage space, and consequently are not individually indexed.

If stop words are used in a search query, they are ignored unless they are parts of quoted phrases. The table below lists all stop words:

Stemming Stemming is a search technique designed to increase search efficiency and broaden relevant search hits. When stemming is used, fullText indexing first attempts to identify each word’s “stem”, and then indexes words by their stems. For example, the words “connected”, “connecting”, and “connectable” all share the same stem and are indexed under “connect”. Search query criteria are automatically stemmed, and so querying “connected” returns all instances where “connect”, “connected”, and “connecting” are used. Nouns like “connector” are not stemmed. Stemming is ON by default but may be disabled.

sub-objects A file found inside a “container object”, see “Container file/object” on page 39 for more details. A container file is often called the “parent” and the contained sub‐objects are called “children”. Sub‐objects should not be confused with embedded files such as OLE objects, for example spreadsheets or graphics embedded in a Microsoft Word file. Note however, an email message may be a container object, if it “contains” attachments, or a simple non‐container object but still have a graphic embedded in its body.

TTags The names of metadata fields. Tags are always associated with a value. For example,

the metadata tag “filename” for any given file is always followed by a value (a text string) containing the actual filename.

Tokenization Tokenization is an IS1200 classification procedure that breaks word strings into “tokens” for better search results. During classifications, Numbers, AlphaNums, HostNames and EmailAddresses (in fullText) are tokenized similar to alpha only strings. With tokenization, the stings “www.kazeon.com”, “[email protected]”, and “11,22,333,44” are tokenized into separate words yielding; “www”,”kazeon”, and “com”; “fred”, “kazeon”, and “com”; and “11”, “22”, “333”, and “444”. This allows searching for “kazeon” and getting all email addresses that contain the domain name, while.

Table 3 Stop Words

a an and are as at be but

by for if in into is it not

of on or s such t that the

their then there these they this to was

will with

Glosssary 47

Glossary

WWeb-Admin An IS1200 web application used by IT personnel to administer the server itself, and

when the IS1200 is used to help administer other IT resources. Web‐Admin is the preferred interface for administering the server.

Web-Reports An IS1200 web application that provides advanced reporting capabilities based on IS1200 metadata.

Web-Search An IS1200 web application that provides basic, advanced, and specialized email searches against IS1200 metadata.

XXML

eXtensible Markup LanguageA file type that uses the XML language to define and describe data that can be transferred between applications like databases and spreadsheets.

Glosssary48

Glossary

Index 49

AAccess Control List 18Access Control List (ACL) 37Actionable Services 31, 37Actions 37Active Directory (AD) 37Advanced Search 37Assignment Rule 37Auditing 37Authentication 37Authorization Rule 37

BBackup 19Basic Search 38

CCAS 39CAS Device 38Case Manager 41CASID 38Celerra Server 38Centera Server 38checkpointing 38Classification Rule 38Classification Service 38CLI Command Line Interface 39Cluster 38conceptFinder Ruleset 39Concepts Search 39connectors 39Container 39Content Addressable Storage 39CSV Comma Separated Values 39Custodian 39

Ddata 40Data Repository 40Data Server 40Data Verification 40Datamap 40

Data‐Mount 40Data‐Share 40Deduplication 40Differential Classifications 41DocsWithoutFullText 41Documentum Sever 41Domino Agent 6, 9Domino Sever 41Domino XML Language 41DXL 41

EeDiscovery 41eDiscovery Case Manager 41Electronic Discovery Reference Model 41EMC

Celerra Server 38Centera Server 38Documentum Server 41SourceOne Archive Server 46

Enterprise Vault 41eth1 41eth2 41EVAgent 43Exchange Server 42Extended Attributes 42Extraction Rule 42

FFederation 42Federation Server 42Filer 42fullText 42

Ggroups

policy 45Groupware 42GUIs

eDiscovery Case Manager 41Web‐Admin 47Web‐Reports 47

Index


Index

Web‐Search 47

HHash Values 42HTTPS 6, 19

IIdentity 27identity 43Identity Vault 43Intelligent Platform Management Interface 43IPMI 43

JJAVA 6, 8

KKaz Schema 43Kazeon EVAgent 43Kazeon Query Language 43Kaz‐mount 43Kaz‐server 43Kaz‐share 43

LLegal Hold 44Legal Service Provider (LSP) 44Local 44localdatafs 44localkazfs 44Logging rule 44Lotus

Domino 41Lotus Domino 2Lotus Notes Client 3, 6

MManifest Reports 44Member‐cluster 44Metadata 44Metadata Repository 27, 44Microsoft

Active Directory 37Exchange Server 42SharePoint 45

Microsoft .Net 8

NNetwork File System (NFS) 44Network Information System (NIS) 44Node 44Notes Storage File 44NSF 44

Ooptional modules 45

PPEA Files 45Policy Group 45PST 45

RRegistering 26Reporting 31reports

manifest 44Web‐Reports 47

Retention 45Roles 45rules

classification 38extraction 42logging 44

SSearch

advanced 37Basic 38Web‐Search 47

Search Index 45Searching 31SharePoint Sever 45snippets 45SourceOne Archive Server 46SP2 8Stemming 46stop words 46sub‐objects 46Symantec

Enterprise Vault 41

TTags 46Tokenization 46Tomcat 3

WWeb‐Admin 47Web‐Reports 47Web‐Search 47Windows 2003 Server 8Windows Administration Tools/Services 8

XXML eXtensible Markup Language 47