EMC SourceOne Email Management Version 7.1 Installation Guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

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

EMC® SourceOne™Email Management

Version 7.1

Installation Guide302-000-174

REV 02

EMC SourceOne Email Management Version 7.1 Installation Guide2

Copyright © 2006 - 2013 EMC Corporation. All rights reserved. Published in the USA.

Published October 2013

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.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

http://support.emc.com


EMC SourceOne Email Management Version 7.1 Installation Guide 1

Contents

Preface.............................................................................................................................. 7

Chapter 1 IntroductionProduct overview.............................................................................. 12

EMC SourceOne Email Management ......................................12Related products .........................................................................14

System architecture........................................................................... 18System components .......................................................................... 19

Processing services .................................................................... 19Databases .................................................................................... 20Archives ...................................................................................... 21Storage......................................................................................... 22Applications ............................................................................... 22

Chapter 2 Planning the InstallationPre-deployment planning................................................................ 26

Customer engagement ...............................................................26Roles and resources ....................................................................27Analysis and design ...................................................................28

Example configurations ................................................................... 29Information resources ................................................................29Blueprints.....................................................................................29EMC SourceOne example configurations ...............................30Small-to-medium business configuration example ...............31Enterprise configuration example............................................35Sizing and scalability..................................................................38Performance metrics...................................................................39High-availability .........................................................................40


Contents

Backup and restore..................................................................... 40Disaster recovery ........................................................................ 40

Chapter 3 Pre-installationPre-installation checklist overview ................................................ 42Creating accounts in Active Directory........................................... 43Assigning permissions..................................................................... 47

Common permissions assignment........................................... 48Email Management permissions assignment......................... 52

Establishing system requirements.................................................. 58Common computer requirements............................................ 59Email Management computer requirements.......................... 70

Chapter 4 Important ConsiderationsCommon considerations (all products) ......................................... 74

Native Archive Index Work directory considerations.......... 74Hardware repurposing considerations ................................... 75Important SQL Server considerations ..................................... 75Additional service accounts to support least privileges....... 81Service account passwords ....................................................... 82Regional and language options to support indexing............ 82

Email Management considerations................................................ 84Compatibility with EMC EmailXtender.................................. 84Service account mailbox restrictions and workaround ........ 84Indexing support for embedded Exchange messages .......... 85Search service startup ................................................................ 85Modifying the EMC SourceOne Notes user account ............ 86

Chapter 5 Installing Common EMC SourceOne ComponentsPre-installation checklist.................................................................. 88Installation overview........................................................................ 89Installing common EMC SourceOne components ....................... 90

Installing databases using scripts............................................. 91Installing databases using the MSI installer ........................... 94Configure SQL permissions ...................................................... 98Installing Master Services software ....................................... 103Installing the EMC SourceOne Console application ........... 111Installing Worker Services software ...................................... 115Installing Web Services software ........................................... 121Installing the EMC SourceOne Search application.............. 128Installing Mobile Services software ....................................... 135

3EMC SourceOne Email Management Version 7.1 Installation Guide

Contents

Installing Native Archive Services software.........................141Maintaining the installation........................................................... 149

Upgrade......................................................................................149Remove a component ...............................................................149Repair a component..................................................................149

Chapter 6 Installing Email Management SupportPre-installation checklist ................................................................ 152Installation overview ...................................................................... 153Installing Email Management components for Exchange ........ 154

Installing Extensions for OWA 2003 Support.......................154Installing Extensions for OWA 2007 or 2010 Support .........160Installing Extensions for OWA 2013 Support.......................166

Installing Email Management components for Domino ........... 172IBM Lotus Domino support overview...................................172Configure administrator access to journaling databases ... 175Installing Extensions for IBM Lotus Domino .......................176Installing the ONM Viewer software.....................................200

Maintaining the installation........................................................... 204Upgrade......................................................................................204Remove a component ...............................................................204Repair a component..................................................................204

Appendix A Domino Configuration and AdministrationJournaling configuration and administration ............................. 208

Journaling administration....................................................... 208EMC SourceOne journaling considerations ......................... 212Native Domino journaling considerations........................... 214

Shortcutting configuration and administration.......................... 217Shortcutting administration ................................................... 217Shortcutting considerations.................................................... 220

Historical archiving configuration and administration............. 221

Appendix B Single Sign-on Support Example (Windows)Overview .......................................................................................... 224

Example details ........................................................................ 224EMC SourceOne eDiscovery - Kazeon considerations....... 225

Example: Single sign-on in Windows Server 2003 ..................... 227Configure Web Services site (SearchWS).............................. 227Configure the Search site (Search) ......................................... 230Configure Universal URL site (ExShortcut) ......................... 231


Contents

Restart IIS.................................................................................. 233Configure IIS 6.0 authentication............................................ 233Configure a User Principal Name for the service account 235Configure Internet Explorer................................................... 235

Example: Single sign-on in Windows Server 2008 R2 ............... 236Configure Web Services site (SearchWS) ............................. 236Configure the Search site (Search)......................................... 240Configure Mobile Services site (ExShortcut) ....................... 241Restart IIS.................................................................................. 242Configure IIS 7.5 authentication............................................ 242Configure Internet Explorer................................................... 246

Appendix C Single Sign-on Support Example (Domino)Overview.......................................................................................... 250

IBM SSO solution..................................................................... 250EMC SourceOne eDiscovery - Kazeon considerations ...... 250

Example: Single sign-on in Windows 2003 ................................. 252Enable the DIIOP task on the Domino server ..................... 252Install the ExValidateLTPA web service............................... 253Configure IIS Web sites in Windows 2003 ........................... 258Configure IIS authentication.................................................. 264

Appendix D Shortcut and UDA Icon Support for OutlookOverview.......................................................................................... 266Publishing Custom Exchange forms............................................ 267

Create an Exchange Public Organizational Forms library 267Configure permissions for the library .................................. 268Replicate the forms library to other Exchange servers ...... 268Review the forms you can publish........................................ 268Publishing forms to the library.............................................. 269

Appendix E Installing EMC SourceOne ReportingPlanning and installation checklist .............................................. 274Pre-deployment planning.............................................................. 275

SQL Server 2008 or 2008 R2 Reporting Services requirement.. 275..............................................Considerations and limitations 276High availability of SQL Server Reporting Services .......... 276

Hardware and software requirements......................................... 277Requirements for the report server....................................... 277Requirements for the report client ........................................ 278


Contents

Installing SQL Server 2008/2008 R2 Reporting Services........... 279Configuring SQL Server Report Server ....................................... 288

Step 1: Connect to the Report Server instance ..................... 289Step 2: Specify the service account ........................................ 290Step 3: Specify the Web Service URL..................................... 290Step 4: Specify information about the Reporting Server database..................................................................................... 292Step 5: Specify the Report Manager URL ............................. 297Step 6: Use defaults for Email Settings ................................. 299Step 7: Use defaults for Execution Account ......................... 299Step 8: Specify backup information for the encryption key ..... 300Step 9: Use defaults for Scale-out Deployment ................... 301

Verifying installation of SQL Server Report Server.................... 303Installing EMC SourceOne reports ............................................... 304

Prerequisites.............................................................................. 304Procedure .................................................................................. 304Verify report installation ......................................................... 306

Controlling access to EMC SourceOne reports ........................... 308Roles in Reporting Services .................................................... 308Requirements for users and groups ...................................... 308Assigning users to roles .......................................................... 309

Authenticating with the EMC SourceOne Activity database ... 311Configuring Internet Explorer for EMC SourceOne reports..... 313Maintaining the installation........................................................... 314

Upgrade..................................................................................... 314Uninstall reports....................................................................... 314

Index .............................................................................................................................. 315


Contents


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properly or does not function as described in this document.

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

Audience This document is part of the EMC® SourceOne™ documentation set, and is intended for use by installers of the product, EMC SourceOne system administrators, and mail server administrators.

Relateddocumentation

Related documents include:

◆ EMC SourceOne Email Management Installation Guide

◆ EMC SourceOne Email Management Administration Guide

◆ EMC SourceOne Search User Guide

◆ EMC SourceOne Products Compatibility Guide

◆ EMC SourceOne Email Management Release Notes

◆ EMC SourceOne Discovery Manager Installation and Administration Guide

◆ EMC SourceOne Discovery Manager User Guide

◆ EMC SourceOne Discovery Manager Release Notes

https://support.emc.com

8 EMC SourceOne Email Management Version 7.1 Installation Guide

Preface

Conventions used inthis document

EMC uses the following conventions for special notices.

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

CAUTION!A caution notice contains information essential to avoid data loss or damage to the system or equipment.

IMPORTANT!An important notice contains information essential to operation of the software.

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, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, 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 call, man pages

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)


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC Online Support website (registration required) at:

http://Support.EMC.com

Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Online communities — Visit EMC Community Network at https://community.EMC.com for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professions for all EMC products.

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

| 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


http://Support.EMC.com


Preface

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

Please include the following information:

◆ Product name and version

◆ Document name, part number, and revision (for example, 01)

◆ Page numbers

◆ Other details that will help us address the documentation issue

Introduction 11

1

EMC SourceOne is a comprehensive, policy-based system that automatically collects, organizes, indexes and retains email, Microsoft SharePoint, and file system content and stores it in designated archives connected to shared storage.

This chapter is organized as follows:

◆ Product overview............................................................................... 12◆ System architecture............................................................................ 18◆ System components ........................................................................... 19

Introduction


Introduction

Product overviewEMC SourceOne products comprise an enterprise solution which you can use to reduce the space required for your email, file and Microsoft SharePoint environments and to aid in complying with legal requirements for archiving content.

EMC SourceOne products archive, retain and organize content from Microsoft Exchange, IBM Lotus Domino, SMTP mail servers, Microsoft SharePoint and network file servers. Archived content is stored in the EMC SourceOne Native Archive, and can be searched by administrators and end users with appropriate permissions.

EMC SourceOne Email ManagementEMC SourceOne Email Management is the base application, or platform, required for other EMC SourceOne products including:

◆ EMC SourceOne for Microsoft SharePoint

◆ EMC SourceOne for Microsoft SharePoint Storage Management

◆ EMC SourceOne for File Systems

◆ EMC SourceOne Discovery Manager

◆ EMC SourceOne Offline Access

◆ EMC SourceOne Email Supervisor

Provides core architectureThe Email Management product provides the core architecture to support other SourceOne products. This architecture includes the components to support the core processing services, databases, archives, storage and applications needed for both the Email Management product and other SourceOne products.

Email management featuresEmail Management supports the archiving of messaging content to enable companies to meet storage management, compliance, and legal discovery requirements, enabling companies to:

◆ Reduce the storage load on messaging servers while still providing users with seamless, efficient access to messages stored on lower-cost storage.

Product overview 13

Introduction

◆ Retain messages for a specified period of time to meet mandated requirements such as the U.S. Securities and Exchange Commission (SEC) 17a-4 regulations, or to meet company-defined compliance requirements.

◆ Preserve messages that may be required for litigation to satisfy legal discovery requirements.

◆ Provide advanced search capabilities designed for the discovery and management of messages for the purposes of complying with email regulations and policies.

◆ Enable role-based searches of messaging archives to support administrative and end-user requirements.

◆ Enable administrators to search for email and export it to PST or NSF format using Discovery Manager express edition.

For information about using the Email Management product, refer to the EMC SourceOne Email Management Administration Guide.

Archiving messagesEmail Management performs the following types of email archiving:

◆ Journaling (archiving messages in real time)

◆ Historical archiving

◆ User-directed archiving

Real-time archivingEmail Management performs real-time archiving (also referred to as journaling) of messages from the following data sources:

◆ Microsoft® Exchange mail servers

◆ IBM® Lotus Domino® mail servers

◆ Drop directories into which SMTP mail is placed

Historical archivingEmail Management performs historical archiving of messages from the following data sources:

◆ Microsoft Exchange mailboxes and PST files

◆ Lotus Domino mailboxes and NSF files

User-directed ArchivingEmail Management enables a mail user or mail application to direct messages to a specific folder in EMC SourceOne Email Management for archiving.


Introduction

Searching messagesEMC SourceOne Email Management enables the following types of searches:

◆ Using the SourceOne Search web-based application:

• Administrator searches - Administrators can perform search and restore operations on archived messages for other users in the company.

• End user searches - End users can perform searches for archived messages with which they are associated.

◆ Using Discovery Manager express edition, administrators can search for email and export it to PST or NSF format.

Related productsThis section provides a brief description of additional EMC SourceOne products. Specific information about how each product integrates with EMC SourceOne Email Management is provided in the documentation set which accompanies each product.

EMC SourceOne for Microsoft SharePointEMC SourceOne for Microsoft SharePoint is an add-on product to EMC SourceOne Email Management that addresses long-term or specialized content archiving strategies. The product leverages the EMC SourceOne Email Management architecture to provide access to archived content using search user interfaces.

EMC SourceOne for Microsoft SharePoint requires that the EMC SourceOne Email Management software be installed, regardless of whether you are using the email management features.

ArchivingEMC SourceOne for Microsoft SharePoint supports the policy-based archiving of SharePoint content in the EMC SourceOne archive to provide efficient storage of SharePoint content.

Product overview 15

Introduction

SearchEMC SourceOne for Microsoft SharePoint provides the following options for searching for archived SharePoint content:

◆ End users can search for archived content using an Archive Search site integrated into SharePoint.

◆ Administrative users can use the EMC SourceOne Search application to search for archived SharePoint content.

External BLOB StorageEMC SourceOne for Microsoft SharePoint provides the ability to offload the storing of binary large objects (BLOBs) from SharePoint SQL Server to external storage.

More informationFor more information on installing, configuring and using EMC SourceOne for Microsoft SharePoint, refer to the EMC SourceOne for Microsoft SharePoint documentation set.

EMC SourceOne for Microsoft SharePoint Storage ManagementEMC SourceOne for Microsoft SharePoint Storage Management provides support for Remote BLOB Storage (RBS) which is used specifically with Microsoft SharePoint Foundation 2010/2013 and Microsoft SharePoint Server 2010/2013.

Remote BLOB StorageThis product provides:

◆ The ability to externalize the storage of BLOBs outside of the SharePoint SQL Server and on remote storage.

◆ BLOBs are stored directly on the selected storage.

◆ BLOB storage is configured at the content database level.

More informationFor more information on installing, configuring and using EMC SourceOne for Microsoft SharePoint Storage Management, refer to the EMC SourceOne for Microsoft SharePoint Storage Management documentation set.

EMC SourceOne for File SystemsEMC SourceOne for File Systems is an add-on component to EMC SourceOne Email Management that enables your organization to gain control over unmanaged information residing on file share systems. By archiving content from file servers across the organization,


Introduction

administrators and end users can leverage content indexing and search capabilities provided by EMC SourceOne to support information governance, compliance discovery and data protection.

EMC SourceOne for File Systems requires the EMC SourceOne Email Management software be installed, regardless of whether you are using the email management features.

For more information on installing, configuring and using EMC SourceOne for File Systems, refer to the EMC SourceOne for File Systems documentation set.

EMC SourceOne Discovery ManagerStarting with version 6.8 of EMC SourceOne, there are two editions of Discovery Manager:

◆ The full edition of Discovery Manager is an add-on component to EMC SourceOne Email Management that offers advanced search capabilities designed for the discovery and collection of archived content for the purposes of litigation support and compliance with organizational or industry-driven regulations and policies.

◆ The express edition of Discovery Manager is included with SourceOne Email Management. Use the express edition for quick search and export of archived email to PST or NSF files.

Note: You cannot install the express edition of Discovery Manager over the full edition.

For more information on installing, configuring and using EMC SourceOne Discovery Manager, refer to the EMC SourceOne Discovery Manager documentation set.

EMC SourceOne Offline AccessEMC SourceOne Email Management can remove messages and attachments from the mail server and replace them with space-efficient stubs (shortcuts) which point to copies of the messages stored in the archive. EMC SourceOne Offline Access supports:

◆ Resolution of shortcut messages using Microsoft Outlook.

◆ The creation and maintenance of a local cache of messages and attachments which the Outlook user can access offline.

For more information on installing, configuring and using EMC SourceOne Offline Access, refer to the EMC SourceOne Offline Access documentation set.

Product overview 17

Introduction

EMC SourceOne Email SupervisorEMC SourceOne Email Supervisor is an add-on component to EMC SourceOne Email Management that offers additional advanced surveillance capabilities designed specifically for compliance with email regulations and policies, including message sampling, customizable automated procedures, intelligent cross-mailbox searching, and purging.

For more information on installing, configuring and using EMC SourceOne Supervisor, refer to the EMC SourceOne Supervisor documentation set.

EMC SourceOne eDiscovery - KazeonEMC SourceOne eDiscovery - Kazeon is an EMC product that enables organizations to efficiently and cost effectively classify, manage, and retrieve data.

For more information on installing, configuring and using EMC SourceOne eDiscovery - Kazeon, refer to the EMC SourceOne for eDiscovery - Kazeon documentation set.


Introduction

System architectureFigure 1 depicts a sample EMC SourceOne system architecture.

Figure 1 EMC SourceOne architecture

System components 19

Introduction

System componentsThe following sections describe the components of the system architecture provided by EMC SourceOne Email Management and depicted in Figure 1:

◆ “Processing services” on page 19

◆ “Databases” on page 20

◆ “Archives” on page 21

◆ “Storage” on page 22

◆ “Applications” on page 22

Processing services The EMC SourceOne processing services include Master Services software, Worker Services software, Web Services software, Mobile Services software, and a database server hosting the EMC SourceOne databases.

The EMC SourceOne processing services architecture is scalable, supporting the installation of all components on a single host computer or allowing you to distribute them across multiple host computers depending on the requirements of your environment.

Master Services softwareMaster Services software schedules and distributes jobs that are processed by Worker Services software installed on the same computer or on multiple computers, depending on the size and processing requirements of the environment.

Worker Services softwareWorker Services software performs archiving activities from various data sources. Worker Services software can be installed on the same computer on which the Master Services software is installed, or you can install Worker Services software on additional computers as needed. Each Worker Services computer can be configured to process only specific activities. Worker Services computers assume control of jobs based on the type of tasks the Worker Services computer is configured to process.

Note: The Discovery Manager Worker Services software is now installed as part of the Email Management Worker Services software.


Introduction

Web Services software Web Services software processes search requests from administrators and end users and performs shortcut resolution for Email Management users. The Web Services software is installed on one or more computers on which Worker Services software is installed.

Mobile Services softwareMobile Services software works in conjunction with Web Services software to support the resolution of shortcuts for Email Management and File System users accessing them using a URL. This includes:

◆ Mobile users

◆ Outlook Web Access users

◆ Outlook users who do not have the EMC SourceOne Offline Access installed.

For EMC SourceOne for File Systems users, the Universal URL also provides support for resolution of links to files in the Native Archive which were archived from a file server.

Installing Mobile Services software creates an IIS Web site (ExShortcut).

Databases The following core Microsoft SQL Server databases are installed with EMC SourceOne Email Management:

◆ Activity database – The activity database maintains data associated with EMC SourceOne system processing.

◆ Native Archive database – The archive database manages data associated with the EMC SourceOne Native Archive, a role-based architecture that manages the archiving, indexing, searching, and retrieving of content.

◆ Search database – The search database maintains data associated with the EMC SourceOne Search application.

Note: Additional databases may be required for other EMC SourceOne products. Refer to the product’s documentation for details.


Introduction

Archives EMC SourceOne supports the following types of archives:

◆ EMC SourceOne Native Archive

◆ EmailXtender 4.8 SP1 email archive (read-only)

Each archive can be connected to one or more storage environments, as described in “Storage” on page 22.

EMC SourceOne Native Archive softwareThe Native Archive software uses an architecture which can be configured to perform the following roles:

◆ Archive

◆ Index

◆ Search

◆ Retrieve

The Native Archive software can be installed on a single host computer or multiple host computers, enabling you to dedicate hardware to specific roles (archive, index, search, and retrieve) to match your organization’s archiving policies. For example, in small-to-medium business environments, the Native Archive software can perform all roles using one physical host computer. In enterprise environments, the Native Archive software can be installed and configured on multiple physical host computers that act as a single virtual computer.

EmailXtender 4.8 SP1 email archiveYou can configure read-only access from EMC SourceOne Email Management to support searches and shortcut resolution for email messages archived by EmailXtender 4.8 SP1.


Introduction

Storage A storage environment is required to house the large amount of data archived by EMC SourceOne as well as databases, program disk data, and other configuration data. SAN storage can consist of a Storage Area Network (SAN) or Network Attached Storage (NAS), or a combination of both depending on the size and throughput requirements of the specific environment. For details on the available storage options, refer to the EMC SourceOne Email Management Administration Guide.

Connectivity to the storage devices can be provided using current device connectivity methods such as Fibre Channel, or iSCSI over Ethernet, depending on the type of storage environment being used.

This document describes the requirements and procedures for a configuration consisting of several servers, databases, and software applications. The implementation of an appropriate storage environment to support the configuration is beyond the scope of this document. EMC Professional Services is expected to leverage information and best practices on configuring a storage environment to support the requirements for EMC SourceOne by using the EMC documentation set for applicable products, and other available information, resources, and expertise.

Applications EMC SourceOne applications provide administrators with the ability to manage the EMC SourceOne system and search the archives. End user applications allow users to search for and retrieve archived content.

This section includes:

◆ EMC SourceOne common applications.......................................... 22◆ Related applications .......................................................................... 23

EMC SourceOne common applicationsThis section describes the common applications which are packaged with the EMC SourceOne Email Management product. These common applications are used with:

◆ EMC SourceOne Email Management

◆ EMC SourceOne for Microsoft SharePoint

◆ EMC SourceOne for File Systems


Introduction

EMC SourceOne ConsoleThe EMC SourceOne Console is a Microsoft Management Console snap-in that can be run from an administrator’s desktop or other system that meets the system requirements. Administrators can use the EMC SourceOne Console to configure and manage:

◆ Archives, archive folders, and mapped folders

◆ Organizational policies

◆ Activities

◆ Filtering rules

◆ Job processing

◆ Applications and Web services

For more information about EMC SourceOne Console features and capabilities, refer to the administration guide for your product. In addition, the EMC SourceOne Console includes a single online help system which supports all applicable SourceOne products.

EMC SourceOne SearchThe EMC SourceOne Search application is typically installed on a Web server and securely communicates with Web Services software installed on one or more Worker Services computers behind the firewall. You can alternatively install the Search application on a Worker Services computer.

EMC SourceOne Search supports administrative searches for archived email, SharePoint, and file system content in the same user interface.

This section describes applications specifically used with EMC SourceOne Email Management.

Related applications “Related products” on page 14 provides a brief description of related EMC SourceOne products.

Refer to the documentation set which accompanies your product for details about the specific applications used with each product.


Introduction

Planning the Installation 25

2

EMC SourceOne products comprise a comprehensive system that integrates with your company’s technology infrastructure and requires careful planning as part of the deployment process. Planning services are offered by EMC Professional Services to assist organizations in deploying the solution. EMC’s deployment services include, but are not limited to, organizational planning, configuration design, environment sizing, and ensuring that the necessary hardware and software is in place and configured to support the environment.


◆ Pre-deployment planning ................................................................. 26◆ Example configurations .................................................................... 29

Planning theInstallation


Planning the Installation

Pre-deployment planningThis section describes the planning activities that take place when deploying EMC SourceOne products within the context of an EMC Professional Services engagement. In cases where Professional Services is not used, similar planning activities are required.

Customer engagementWhen EMC Professional Services is engaged to plan and deploy one or more EMC SourceOne products, the engagement is driven using a detailed customer engagement model. Resources from various EMC organizations including Professional Services work with your organization’s internal IT organizations to plan and execute the deployment.

The timeline for customer engagement spans pre-sale activities, deployment planning, deployment and production. Activities which take place prior to deployment include the following:

◆ Solution requirements definition — This activity typically takes place during the pre-sale phase. The activity involves gathering customer requirements, and determining initial license counts, service deliverables and deployment timeline.

◆ Business requirements definition — This activity involves collecting and analyzing customer business requirements, metrics and processes.

◆ Solution design — This activity involves translating business requirements into technical requirements, including license counts, hardware and storage requirements and services estimate.

Pre-deployment planning 27


Roles and resourcesBefore installing EMC SourceOne products, EMC Professional Services works with your organization to define archiving and computer use policies which protect business interests. This policy should define the rights and obligations of employees regarding the use of company systems. It should also clearly define restrictions.

Once this policy is defined, it should be clearly communicated to all employees in the organization. Your organization should conduct employee training and awareness sessions to ensure that employees understand each policy and its purpose.

The personnel that can be involved in an installation of EMC SourceOne products include:

◆ EMC Professional Services and authorized partners — Trained to scope, install and configure EMC SourceOne components.

◆ Compliance officer — Defines and enforces company-wide compliance policies. Involved prior to, during, and post installation as a consulting entity to enable administrators to configure the system to support compliance policies.

◆ Email administrator — Implements appropriate policies related to the organization’s messaging environment.

◆ Network administrator — Ensures the deployment team has the appropriate network environment configured to support the EMC SourceOne system.

◆ Database administrator — Ensure the deployment team has the appropriate database environment to support the EMC SourceOne system.

◆ Storage administrator — Ensure the deployment team has the appropriate storage environment and resources to support the EMC SourceOne system.

◆ Backup administrator — Ensure the deployment team understands the requirements to backup the EMC SourceOne system.



Analysis and designThe analysis and design effort includes the following environmental elements:

◆ Data infrastructure

◆ Network and storage environment

◆ Hardware and software requirements

◆ Impact of implementation to infrastructure

◆ Software configuration parameters

◆ Hardware and storage sizing

Once these factors are understood, the Professional Services team can create a project plan which defines the solution and a plan for enterprise rollout.

Example configurations 29


Example configurationsThe configuration examples described in this section provide a basic deployment example designed to support high availability and can be scaled as the organization’s requirements grow and change.

Information resourcesYour account team can provide configuration options and details based on the size and scope of your EMC SourceOne deployment. In addition, several customer-facing white papers are available on the EMC Online Support site.

BlueprintsEMC Professional Services can provide assistance in sizing your environment, recommending a configuration and deploying the configuration. EMC SourceOne blueprints are available to assist with this process.



EMC SourceOne example configurationsThis section describes two example configurations: one used by a small-to-medium business customer, and one used by an enterprise customer. This information is intended only to provide examples of typical configurations.

EMC SourceOne deployment details can vary greatly depending on the size of your environment and specific product features. This can include considerations for EMC SourceOne Email Management, EMC SourceOne for Microsoft SharePoint, EMC SourceOne for File Systems, and other products as described in “Applications” on page 22.

The examples depicted in this section include EMC SourceOne Email Management, EMC SourceOne for Microsoft SharePoint, and EMC SourceOne for File Systems.

Small-to-medium business example configuration – This configuration (Figure 2) can support your site using an architecture that distributes processing and archiving functionality across a minimal number of physical computers and storage.

Enterprise configuration example – This configuration (Figure 4) can support large sites using an architecture which distributes processing and archiving functions across hardware and storage.



Small-to-medium business configuration example

Figure 2 EMC SourceOne SMB configuration example



Basic configuration EMC SourceOne supports the installation of the following software on a single computer:

◆ Master Services software

◆ Worker Services software

◆ Web Services software

◆ Native Archive Services software

◆ Console application (can be installed on this computer and/or one or more client computers)

◆ EMC SourceOne for Microsoft SharePoint Business Components Extensions

◆ EMC SourceOne for File Systems Business Component Extensions

◆ Search application (can alternatively be installed on a Web server)

◆ Discovery Manager Server, express edition

◆ Mobile Services software

◆ DiskXtender (if used)

Native Archive disk configuration and storage Figure 3 depicts a disk configuration and storage example for the EMC SourceOne Native Archive.

Figure 3 Native Archive SMB disk/storage configuration example



Sizing detailsThe configuration described in this section is an example. The EMC SourceOne Sizing Calculator and other EMC resources can provide details on storage capacity, server configuration, and disk layout recommendations based on an analysis of your requirements. Contact your EMC representative for details.

Disk configurationIn this example, the drives are configured as follows:

◆ C: - Operating system

◆ E: - Program files and trace log files

◆ F: - Work directories for temporary processing:

• EMC SourceOne Work directory

– Temporary area required for EMC SourceOne processing (excluding indexing)

– Created during Master software installation (subsequent Worker and Native Archive software installations confirm that this directory exists)

– Requires a minimum of 1 GB of free space• EMC SourceOne Index Work directory

– Temporary area required for Native Archive computers performing the index role

– Created during Native Archive software installation– Requires a minimum of 20 GB of free space– Must be located on a local drive– Cannot be located on the operating system drive



StorageIn this example, shares on configured on a separate file server as follows:

◆ Message Center folder configured as a share and sized using the EMC SourceOne Sizing Calculator

◆ Index folder configured as a share and sized using the EMC SourceOne Sizing Calculator

◆ Container folder configured as a share and sized using the EMC SourceOne Sizing Calculator. Direct storage is also supported on EMC Centera, EMC Celerra, EMC Data Domain and NetApp

Note: Specific permissions for each share are configured as described in “Assigning permissions” on page 47.



Enterprise configuration example

Figure 4 EMC SourceOne enterprise configuration example



Basic configuration EMC SourceOne software can be distributed across several computers. For example, you can configure separate computers as follows:

◆ Dedicated SQL Server database host computer

◆ Master Services software installed on two computers which are clustered using Microsoft Clustering

◆ Two or more Worker Services computers with the following software installed:

• Worker Services

• Web Services (on at least one Worker Services computer)

• Mobile Services

• Discovery Manager Server, express edition

• EMC SourceOne for Microsoft SharePoint Business Component Extensions

• EMC SourceOne for File Systems Business Component Extensions

◆ One or more computers (Master Services computer or a client computer) with the following software installed:

• EMC SourceOne Console application

• EMC SourceOne for Microsoft SharePoint Business Component Extensions

• EMC SourceOne for File Systems Business Component Extensions

◆ The EMC SourceOne Search application:

• Installed on one or more Worker Services computers and configured to communicate with Web Services.

• Installed on an IIS Web server and configured to communicate with Web Services on one or more Worker Services computers.

◆ One or more computers with Native Archive Services software installed. Disk configuration and storage configured as described in “Native Archive disk configuration and storage” on page 37.

◆ The Discovery Manager client application:

• Installed on one or more client computers and configured to communicate with the Discovery Manager Server, express edition.



Native Archive disk configuration and storage Figure 5 depicts a disk configuration and storage example for the EMC SourceOne Native Archive.

Figure 5 Native Archive enterprise disk/storage configuration example

Sizing detailsThe configuration described in this section is an example. The EMC SourceOne Sizing Calculator and other EMC resources can provide details on storage capacity, server configuration, and disk layout recommendations based on an analysis of your requirements. Contact your EMC representative for details.

Disk configurationIn this example, each Native Archive computer has the following disk configuration:

◆ C: - Operating system

◆ E: - Program files and trace log files

◆ F: - Work directories for temporary processing:

• EMC SourceOne Work directory

– Temporary area required for EMC SourceOne processing (excluding indexing)

– Created during Native Archive software installation– Requires a minimum of 1 GB of free space



• EMC SourceOne Index Work directory

– Temporary area required for Native Archive computers performing the index role

– Created during Native Archive software installation– Requires a minimum of 20 GB of free space– Must be located on a local drive– Cannot be located on the operating system drive

Storage configurationIn this example, the two Native Archive computers can share the following storage configuration:

◆ Message Center stored on a separate file share, SAN or NAS device

◆ Indexes stored on a separate file share, SAN or NAS device

◆ Containers stored on a separate file share, SAN or NAS device. Direct storage is also supported on EMC Centera, EMC Celerra, EMC Data Domain and NetApp

Note: Specific permissions for each share are configured as described in “Assigning permissions” on page 47.

Sizing and scalabilityUnderstanding specific information about the environment into which EMC SourceOne is deployed is key to determining the hardware, software and storage resources required. Although EMC SourceOne example configurations provide base guidelines for these required resources, certain aspects can be adjusted to meet the specific needs of the environment.

EMC utilizes various tools to gather key information by working with the customer prior to a deployment in order to scope the environment. These tools include the EMC SourceOne Sizing Calculator. The resulting information is then applied to the framework of the configuration where components of the configuration can be scaled or extended.

For example, when sizing an Email Management environment, some of the factors examined include:

◆ Total number of users

◆ Number of messages per day



◆ Percentage of messages with attachments

◆ Average size of attachments

◆ Average size without attachments

◆ Average number of recipients per message

◆ Message de-duplication percentage

◆ Annual email usage growth

◆ Typical business processing requirements

The information provided by the EMC SourceOne Sizing Calculator includes:

◆ Archive storage capacity

◆ Additional storage considerations

◆ Server and processing requirements

◆ Standard server configurations (disk layout, spindle speeds and other information)

For more information about the EMC SourceOne Sizing Calculator, contact your EMC account team.

Performance metricsProfessional Services utilizes information resulting from performance testing to establish a performance baseline for a base configuration. EMC SourceOne components can then be adjusted to achieve an expected level of performance.



High-availabilityAs an enterprise-class solution, EMC SourceOne components must be configured to support high availability and minimize system downtime. High availability is a combination of data protection, failover, and appropriate planning to eliminate both planned and unplanned downtime.

EMC SourceOne is designed to support high availability by forming an infrastructure which includes hardware and software redundancy for all system components.

In addition, it is important for the organization to have policies and procedures in place to support business continuity objectives. These objectives are defined and documented as part of the engagement between EMC and key personnel representing the organization.

Backup and restoreInformation and procedures for performing backups of the EMC SourceOne system is described in the EMC SourceOne Email Management Administration Guide.

For backup and restore information for other EMC SourceOne products, refer to the documentation set that accompanies each product.

Disaster recoveryThe EMC SourceOne Disaster Recovery Solution Guide provides configuration, failover and failback information for supported EMC SourceOne configurations.

Pre-installation 41

3

This chapter provides details on implementing the accounts, permissions and system requirements required before installing EMC SourceOne software. Important considerations are also provided.


◆ Pre-installation checklist overview.................................................. 42◆ Creating accounts in Active Directory ............................................ 43◆ Assigning permissions ...................................................................... 47◆ Establishing system requirements ................................................... 58

Pre-installation


Pre-installation

Pre-installation checklist overviewThe following pre-installation checklists are provided in this chapter.

Specific permissions, system requirements and considerations for all products (common) and EMC SourceOne Email Management are provided as subsections.

As you complete the tasks in each checklist, you can indicate it using the checklist provided in Table 1.

IMPORTANT!Before you begin implementing the accounts, permissions, and system requirements, review “Important Considerations” on page 73 for information that may be relevant to your environment.

Table 1 Checklist overview

Done Checklist

“Creating accounts in Active Directory” on page 43

“Assigning permissions” on page 47• “Common permissions assignment” on page 48• “Email Management permissions assignment” on page 52

“Establishing system requirements” on page 58• “Common computer requirements” on page 59• “Email Management computer requirements” on page 70

“Important Considerations” on page 73• “Common considerations (all products)” on page 74• “Email Management considerations” on page 84

Creating accounts in Active Directory 43

Pre-installation

Creating accounts in Active DirectoryThis section provides a checklist for the tasks required to configure groups and accounts in Active Directory.

Figure 6 Active Directory groups and accounts

IMPORTANT!Users who will be using Discovery Manager (express edition or full edition) must be in Active Directory. Email users whose email will be searched do not need to be in Active Directory.


Pre-installation

Table 2 Accounts and permissions checklist - Active Directory (1 of 3)

Done Task Details Validation

Create the primary service account

All environmentsThe EMC SourceOne primary service account is required in all environments to process EMC SourceOne activities. Details:• Password does not need to be changed at next login• Account does not expire• Password does not expire. See “Service account passwords” on

page 82 for considerations.• Must be in the same domain as the SourceOne servers

Account name:___________________________________

Email Management environments onlyIn Exchange environments, you can optionally create an Exchange mailbox for the primary service account. If your site disallows creating a mailbox for a service account, see “Service account mailbox restrictions and workaround” on page 84.

Ensure account successfully created.

Create Master Services service account (optional)

All environmentsThe optional EMC SourceOne Master Services service account is specified during Master Services installation. You can alternatively use the primary service account. See “Additional service accounts to support least privileges” on page 81 for considerations.Details:• Password does not need to be changed at next login• Account does not expire• Password does not expire. See “Service account passwords” on


Account name:___________________________________


Creating accounts in Active Directory 45

Pre-installation

Identify or create OWA service account (optional)

Email Management environments onlyThe EMC SourceOne OWA service account is specified during Extensions for OWA installation on Exchange. You can alternatively use the primary service account. See “Additional service accounts to support least privileges” on page 81 for considerations.Details:• Password does not need to be changed at next login• Account does not expire. • Password does not expire. See “Service account passwords” on


Account name:___________________________________


Create security group

All environmentsCreate the EMC SourceOne security group. This group houses the service accounts used with EMC SourceOne. Details:• Created in a domain that is fully trusted by the domains EMC

SourceOne applications are running• Group scope is Universal (or Global if Universal is not available in the

environment)• Group type is Security• Group name does not contain special characters

Group name:___________________________________

Ensure group successfully created.

Add service accounts to security group

All environmentsAdd the following accounts: • EMC SourceOne primary service account• EMC SourceOne Master Services service account (if used)• EMC SourceOne OWA service account (if used)

Ensure accounts successfully added.




Pre-installation

Create Admins group

All environmentsCreate the EMC SourceOne Admins group. This group houses the accounts for designated administrators who will use the EMC SourceOne Console application. Details:• Created in a domain that is fully trusted by the domains EMC

SourceOne applications are running• Group scope is Universal (or Global if Universal is not available in the

environment)• Group type is Security• Optionally create an Exchange email address

Group name:___________________________________

Ensure group successfully created.

Identify or create administrative accounts

All environmentsIdentify or create one or more administrative user accounts used to run the EMC SourceOne Console.

Account name(s):_________________________________________________________________________________________________________

Ensure account exists or is successfully created.

Add administrative accounts to Admins Group

All environmentsAdd administrative accounts to the EMC SourceOne Admins Group.


Identify or create installation account

All environmentsIdentify or create one or more installation user accounts used to install EMC SourceOne software.

Account name(s):_________________________________________________________________________________________________________




Assigning permissions 47

Pre-installation

Assigning permissionsThis section provides a checklist for the tasks required to assign permissions to SQL Server, computers, share locations, and data source environments, and is organized as follows:

◆ Common permissions assignment ................................................... 48◆ Email Management permissions assignment................................. 52

Note: For information about permissions required for Discovery Manager (express edition or full edition), refer to the EMC SourceOne Discovery Manager Installation and Administration Guide.


Pre-installation

Common permissions assignment

Task overview


Pre-installation

Task checklistThis checklist describes how to assign permissions common to all EMC SourceOne environments.

Table 3 Accounts and permissions - permissions assignment (1 of 3)

DoneEnvironment/System Task Details Validation

SQL Server Configure SQL database install permissions and Security Logins

Ensure that the installation account is a local administrator and has the SQL sysadmin role.

Note: For important details about database installation permissions, see “SQL database installation permissions” on page 78.

Configure the following groups and accounts as Security Logins in SQL Server:• EMC SourceOne security group• EMC SourceOne Admins group• EMC SourceOne installation account(s)You will later assign individual database privileges to these logins after EMC SourceOne databases are installed.

After EMC SourceOne is installed, use the ODBC Test Connection function to confirm the connection.

Master computer(s)

Add service account to local administrators group

Add one of the following service accounts as a member of the local administrators group for this computer:• Primary service account, or• Master Services service account (if used)This account is required to be a member of this group to run the EMC SourceOne Job Scheduler service.

Ensure account(s) added

Master computer(s)

Add installation account to local administrators group

Add the EMC SourceOne installation account as a member of the local administrators group for this computer.You can remove this user from the group once installation is completed.

Note: Alternatively you can use an existing account that is a member of the local administrators group to install the software.

Ensure you can log in using this account


Pre-installation

Worker computer(s)





Native Archive computer(s)





Console client computers








Pre-installation

Storage Configure storage location permissions

Configure EMC SourceOne Security Group with permissions for the following storage locations:• Message Center location• Archive location• Index location• Job detail log file locationConfigure the following permissions for each location:• Sharing tab - Configure the security group with Full

Control permissions to the share • Security tab - Configure the security group with Full

Control permissions to the share

1. Log in to a system as the primary service account.

2. Access the share and create a text file.

3. Delete the text file.

DiskXtender Add security group to DX administrators group

If using DiskXtender, add the EMC SourceOne Security Group to the DxAdministrators group on the DiskXtender server.

Ensure the group is added

EmailXtender Provide access to EmailXtender database

To use an EMC SourceOne archive connection to an EmailXtender 4.x read-only archive, the EMC SourceOne service account must have db_datareader access to the EmailXtender database. This access is created using Microsoft SQL Server Management Studio.

Ensure the service account can access the database




Pre-installation

Email Management permissions assignmentThis section provides a task overview and checklists for the tasks required to assign permissions specific to your email environment. This section includes:

◆ Task overview..................................................................................... 53◆ General permissions .......................................................................... 54◆ Microsoft Exchange permissions..................................................... 55◆ IBM Lotus Domino permissions...................................................... 57


Pre-installation

Task overview


Pre-installation

General permissionsThis section describes general permissions associated with EMC SourceOne Email Management.

Table 4 Accounts and permissions - permissions assignment


MIME drop directories

Configure drop directory permissions for MIME management

For drop directories into which you place MIME messages to be archived by EMC SourceOne:• Sharing tab - Configure the security group with Full






NSF drop directories

Configure drop directory permissions for NSF management

For drop directories into which you place NSF files to be archived by EMC SourceOne:• Sharing tab - Configure the security group with Full






PST drop directories

Configure drop directory permissions for PST management

For drop directories into which you place PST files to be archived by EMC SourceOne in a single Exchange forest configuration:• Sharing tab - Configure the security group with Full



Note: See the EMC SourceOne Email Management Administration Guide for considerations in a Exchange resource forest configuration.

1. Log in to a system as the EMC SourceOne primary service account.



Network computers

Configure PST discovery permissions

To support PST discovery and management on network computers in a single Exchange forest configuration, add the EMC SourceOne security group as member of local Administrators group for these computers.

Note: See the EMC SourceOne Email Management Administration Guide for considerations in a Exchange resource forest configuration.

Network computers:1. Log in to a system

as the EMC SourceOne primary service account.

2. Access a computer from My Network Places.

3. Access C$ drive.


Pre-installation

Microsoft Exchange permissionsThis section provides a checklist for the tasks required to configure permissions in Microsoft Exchange.

Table 5 Accounts and permissions - Microsoft Exchange (1 of 3)


Create Exchange journaling mailboxes

Create one or more Exchange journaling mailboxes. A journaling user account is associated with an Exchange journaling mailbox that collects messages generated on a mailbox store. Most configurations will consist of several journaling users and mailboxes.

Note: Envelope journaling is required for EMC SourceOne. See “Microsoft Exchange environment requirements” on page 70 for details.

A journaling user account is created in Active Directory and must have the following characteristics:• Member of Domain Users group• Password does not need to be changed at next login• Password does not expire• Account does not expire

Journaling users/mailboxes_________________________________________________________________________________________________________

Ensure mailboxes created.

Configure general Exchange permissions

Grant the EMC SourceOne primary service account and the EMC SourceOne Admins group the following permissions:

- Exchange View-Only Administrator (at the Organization level)

Note: If using Exchange 2010 in a mixed environment (which includes both Exchange 2010 and a previous Exchange version), you must explicitly configure these permissions in Exchange 2010, as they do not automatically propagate over from previous Exchange versions.

1. Start the EMC SourceOne Console.

2. Check that the administrator can view the mail server hierarchy from the EMC SourceOne Console.


Pre-installation

Configure permissions for journaling mailboxes

Grant the EMC SourceOne primary service account access rights to each journaling mailbox. Exchange 2010 Server• Full mailbox accessExchange 2007 Server• Full mailbox accessExchange 2003 Server• Delete mailbox storage• Read permissions• Change permissions• Full mailbox access

Test journaling mailbox access:1. Open Outlook as the

primary service account.

2. Open the journal mailbox Inbox folder.

3. Add and delete a message.

Configure permissions for user mailboxes

To support storage management (which requires a higher level of permissions to access and manipulate mailbox contents), configure the following permissions (depending on Exchange version).Exchange 2010Grant the EMC SourceOne primary service account the following extended permissions:• Receive As

Note: In a mixed environment (Exchange 2010 and a previous version of Exchange), grant these permissions at the mailbox database level, targeting only the mailboxes on Exchange 2010. You can then use the permissions described in the following section for mailboxes hosted on previous Exchange versions.

Exchange 2003 or 2007Grant the EMC SourceOne primary service account the following extended permissions:• Receive As • Send As

Note: These permissions can be granted at the Organization level (highest) to the individual mailbox level (lowest).

Storage management:1. Open Outlook as the

primary service account.

2. Open a test user mailbox Inbox folder.

3. Add and delete a message.




Pre-installation

IBM Lotus Domino permissionsThis section provides a checklist for the tasks required to configure permissions in IBM Lotus Domino.

Review Exchange 2010 considerations

Review the following considerations if using EMC SourceOne in an environment that includes Microsoft Exchange 2010:• Exchange 2010 replaced the permissions model used in Exchange

2007 with a Role Based Access Control (RBAC) permissions model. Refer to the Microsoft Exchange 2010 documentation set for more information.

• Exchange 2010 takes two hours to update the permissions cache. Restart the Microsoft Exchange Information Store after applying permissions to activate the changes.

None.



Table 6 Accounts and permissions - IBM Lotus Domino


Create EMC SourceOne Lotus Notes account

This account will later be specified on EMC SourceOne host computers to support message processing in a Domino environment.To support all EMC SourceOne activities, configure the account with:• Manager privileges for all users mail files• Delete access to all mailboxes To support all EMC SourceOne activities except archiving messages based on read or unread status, restoring messages from EMC SourceOne Search, and user-directed archiving:• Editor privileges for all users mail files• Delete access to all mailboxes Account name:___________________________________

1. Open a user NSF file for test purposes as the EMC SourceOne Notes user.

2. Add data.3. Delete the data.

Configure Internet address and password for Lotus Notes users

Ensure Lotus Notes users have an Internet address and password configured. This is required for Notes users to use EMC SourceOne Search.

After EMC SourceOne is installed, confirm that a Notes user can log in to EMC SourceOne Search.


Pre-installation

Establishing system requirementsThis section provides minimum hardware, operating system, network connectivity, and prerequisite software requirements for components comprising a typical EMC SourceOne system configuration.

IMPORTANT!Before you begin implementing the system requirements, review “Important Considerations” on page 73 for information that may be relevant to your environment.

This section describes the system requirements for computers used with EMC SourceOne and is organized as follows:

◆ Common computer requirements ................................................... 59◆ Email Management computer requirements ................................. 70For information about requirements for Discovery Manager (express edition or full edition), refer to the EMC SourceOne Discovery Manager Installation and Administration Guide.

Establishing system requirements 59

Pre-installation

Common computer requirementsThis section describes system requirements for host computers common to all EMC SourceOne environments, including:

◆ Database host computer requirements............................................ 60◆ Master Services host computer requirements ................................ 61◆ Worker Services host computer requirements................................ 63◆ Native Archive Services host computer requirements.................. 65◆ Storage environment requirements.................................................. 67◆ IIS Web Server requirements............................................................. 68◆ EMC SourceOne Console client computer requirements ............. 69


Pre-installation

Database host computer requirementsThis table describes the requirements for a dedicated Microsoft SQL Server database host computer.

Table 7 Database host computer base requirements

Hardware The EMC SourceOne Sizing Calculator provides recommendations based on your environment. Important guidelines for your database administrator are also provided in “Important SQL Server considerations” on page 75.

OS Refer to the EMC SourceOne Products Compatibility Guide for detailed operating system requirements.

Disk configuration

The EMC SourceOne Sizing Calculator provides recommendations based on your environment. General guidelines for your database administrator are also provided in “Important SQL Server considerations” on page 75.

Network High-speed connection to all components and systems in the configuration with sufficient bandwidth to process the expected workload.

Software Refer to the EMC SourceOne Products Compatibility Guide for more detailed information on supported versions of the software described in this section.

Microsoft SQL Server • Enterprise Edition (recommended) or Standard Edition• General guidelines for your database administrator are also

provided in “Important SQL Server considerations” on page 75.

Windows Server 2008 only - configure firewall rules

If using Windows Server 2008, configure the SQL Server executable (Sqlservr.exe) as an exception to the blocked programs list.Refer to the following Microsoft article for details on configuring firewall rules using Windows Firewall with Advanced Security in Windows Server 2008:http://msdn.microsoft.com/en-us/library/cc646023.aspx

Important Considerations

Ensure that you review the important information in “Important SQL Server considerations” on page 75. Topics include:• Database installation permissions• SQL Server disk configuration• Database partitioning• Database installation options• Collation settings• Disaster recovery configuration

http://msdn.microsoft.com/en-us/library/cc646023.aspx


Pre-installation

Master Services host computer requirementsThis table describes the requirements for the host computers on which Master Services software is installed.

Table 8 Master Services host computer base requirements (1 of 2)

Hardware The EMC SourceOne Sizing Calculator provides detailed recommendations based on your environment.


Disk configuration

The EMC SourceOne Sizing Calculator provides detailed recommendations based on your environment.



Email software (Exchange) • No client software required

Email software (Domino) • Install Notes client• Configure the Notes ID as the EMC SourceOne Notes user account• Validate by ensuring the client can access the mail server• Notes 8.5 Shared Login feature is not supported• Do not update or change the version of Lotus Notes client software

after EMC SourceOne components are installed.

Email software (general) Mixed-mail environments (Exchange and Domino):• Ensure Outlook is the default mail clientSMTP mail environment:• No email client is requiredValidation:• Validated by EMC SourceOne software installation that email client

version is supported

Microsoft .NET Framework Redistributable Package

• Manually install• Validated by EMC SourceOne software installation

Microsoft Management Console 3.0 • Manually install if planning to install EMC SourceOne Console on this computer

• Validated by EMC SourceOne Console software installation


Pre-installation

Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)

• English, French, Italian, German and Spanish language systems - Automatically installed with EMC SourceOne software if not present

• Chinese, Japanese, and Korean language systems - Manually or silently install the redistributable package specific to the supported language.

Microsoft SQL Server Native Client Redistributable Package

• Automatically installed with EMC SourceOne software if not present

Core XML Services (MSXML) 6.0 • Manually install (Windows 2003 only)• Not validated by EMC SourceOne software installation.

Table 8 Master Services host computer base requirements (2 of 2)


Pre-installation

Worker Services host computer requirementsThis table describes the requirements for the host computers which may be running the following EMC SourceOne software:

◆ Worker Services

Note: The Discovery Manager Worker Services software is now installed as part of the Email Management Worker Services software.

◆ Web Services

◆ Mobile Services

◆ EMC SourceOne Search

◆ EMC SourceOne for Microsoft SharePoint Business Components Extensions

◆ EMC SourceOne for File Systems Business Component Extensions

Table 9 EMC SourceOne Worker Services host computer base requirements (1 of 2)



Disk configuration

The EMC SourceOne Sizing Calculator provides detailed recommendations based on your environment.



Email software (Exchange) • Install Outlook 2007 (ensure Cached Exchange Mode is disabled)

• Log in using the service account and ensure the MAPI profile named EMCSourceOne is configured for the mailbox associated with the service account.

Note: See “Service account mailbox restrictions and workaround” on page 84 for details on service account mailbox configuration.

• Validate by using Control Panel > Mail > Show Profiles to ensure profile name is EMCSourceOne


Pre-installation

Email software (Domino) • Install Notes client• Configure the Notes ID as the EMC SourceOne Notes user

account• Validate by ensuring the client can access the mail server• Notes 8.5 Shared Login feature is not supported• Do not update or change the version of Lotus Notes client

software after EMC SourceOne components are installed

Email software (general) Mixed-mail environments (Exchange and Domino):• Ensure Outlook is the default mail clientSMTP mail environment:• No email client is requiredValidation:• Validated by EMC SourceOne software installation that email

client version is supported

Core XML Services (MSXML) 6.0 • Manually install (Windows 2003 only)• Not validated by EMC SourceOne software installation



Microsoft Internet Information Services (IIS) • Manually install if installing Web Services on this computer• Ensure .NET is installed prior to IIS• Ensure ASP.NET option selected• Validated by EMC SourceOne Web Services software

installation

Microsoft ASP.NET • Manually install if installing Web Services on this computer• Inherited authorization rules are set to Allow• Validated by EMC SourceOne software installation



• Chinese, Japanese, and Korean language systems - Manually or silently install the redistributable package specific to the supported language



Microsoft ASP.NET AJAX Extensions Redistributable Package


Table 9 EMC SourceOne Worker Services host computer base requirements (2 of 2)


Pre-installation

Native Archive Services host computer requirementsThis table describes the requirements for the host computers on which Native Archive Services software is installed.

Table 10 Native Archive Services computer base requirements (1 of 2)


Operating system A supported version of Microsoft Windows 2003 Server. Refer to the EMC SourceOne Products Compatibility Guide for more detailed information on operating system requirements.

Disk configuration Refer to the guidelines described in “Example configurations” on page 29 for the recommended disk con-figuration and storage options.

Network connectivity High-speed connection to all components and systems in the configuration with sufficient bandwidth to process the expected workload.


Email client software • Install Outlook 2007. See “Indexing support for embedded Exchange messages” on page 85 for considerations.

Core XML Services (MSXML) 6.0 • Manually install (Windows 2003 only)• Not validated by EMC SourceOne software

installation.


• Manually install• Validated by EMC SourceOne software

installation.





Pre-installation



Internet Control Message Protocol (ICMP). Utilized by EMC SourceOne software to manage network connection issues.

• Ensure ICMP is enabled and functioning.

Operating system language support (for indexing)

• For all languages for which you intend to index messages and files, install code page conversion tables

• For East Asian languages, install files for East Asian languages

• See “Regional and language options to support indexing” on page 82 for considerations.

Table 10 Native Archive Services computer base requirements (2 of 2)


Pre-installation

Storage environment requirementsA storage environment is required to house the large amount of data archived by EMC SourceOne as well as databases, logs, program disk data and other configuration data. SAN storage can consist of a Storage Area Network (SAN) or Network Attached Storage (NAS), or a combination of both depending on the size and throughput requirements of the specific environment.

Connectivity to the storage devices can be provided using current device connectivity methods such as Fibre Channel, or iSCSI over Ethernet, depending on the type of storage environment being used.

This document describes the requirements and procedures for a configuration consisting of several servers, databases and software applications (see “Example configurations” on page 29). The implementation of an appropriate storage environment to support the configuration is beyond the scope of this document.


Pre-installation

IIS Web Server requirementsYou can install the following EMC SourceOne applications on a separate IIS Web server:

◆ EMC SourceOne Search software

◆ EMC SourceOne Mobile Services software.

Note: Be sure to apply all current Windows updates before installing SourceOne components that require IIS.

Ensure the Web server meets the following requirements.

Table 11 IIS Web Server host computer base requirements

OS Must meet the same operating system requirements as a Worker Services computer. Refer to the EMC SourceOne Products Compatibility Guide for detailed operating system requirements.





Microsoft Internet Information Services (IIS) • Manually install if installing Web Services on this computer• Ensure .NET is installed prior to IIS• Ensure ASP.NET option selected• Validated by EMC SourceOne Web Services software

installation

Microsoft ASP.NET • Manually install if installing Web Services on this computer• Inherited authorization rules are set to Allow• Validated by EMC SourceOne software installation

Microsoft ASP.NET AJAX Extensions Redistributable Package



Pre-installation

EMC SourceOne Console client computer requirementsThis table describes the requirements for client computers running the EMC SourceOne Console software.

Table 12 EMC SourceOne Console client computer base requirements

Hardware Standard desktop or laptop used in a corporate environment.


Network Standard connection to the corporate network.


Email software (Exchange) • Ensure Microsoft Outlook installed

Email software (Domino) • Ensure IBM Lotus Notes installed• If this computer is also an EMC SourceOne Master or Worker, the Notes 8.5

Shared Login feature is not supported• Do not update or change the version of Lotus Notes client software after EMC

SourceOne components are installed.

Email software (general) SMTP mail environment:• No email client is requiredValidation:• Supported email client software versions validated if present

Core XML Services (MSXML) 6.0

• Manually install (Windows 2003 only)• Not validated by EMC SourceOne software installation


• Manually or silently install• Validated by EMC SourceOne software installation

Microsoft Management Console • Manually or silently install• Validated by EMC SourceOne software installation

Microsoft Windows Installer • Automatically installed with EMC SourceOne software if not present.



• Chinese, Japanese, and Korean language systems - Manually or silently install the redistributable package specific to the supported language




Pre-installation

Email Management computer requirementsThis section describes system requirements for host computers in an EMC SourceOne Email Management environment, including:

◆ Microsoft Exchange environment requirements ........................... 70◆ IBM Lotus Domino environment requirements ............................ 71◆ ONM Viewer client computer requirements ................................. 72◆ Mobile device requirements ............................................................. 72

Microsoft Exchange environment requirementsThis table describes the prerequisite software and configuration required on each Exchange Server on which you also plan to install the EMC SourceOne Extensions for Outlook Web Access software.

Table 13 Microsoft Exchange Server software prerequisites


Microsoft .NET Framework Redistributable Package • Manually install• Validated by EMC SourceOne software installation




Configuration Configuration specifics.

Exchange 2010 envelope journaling • For Exchange 2010, envelope journaling is not optional and is enabled by default.

Exchange 2007 envelope journaling • For Exchange 2007, envelope journaling is not optional and is enabled by default.

Exchange 2003 envelope journaling • For Exchange 2003, ensure that envelope journaling is enabled. This feature is required for EMC SourceOne.


Pre-installation

IBM Lotus Domino environment requirementsThis table describes the prerequisite software required on each Domino server on which you also plan to install the EMC SourceOne Extensions for Domino software.

Table 14 IBM Lotus Domino server software prerequisites





(Red Hat Enterprise Linux only) Required compatibility GCC package. Refer to the EMC SourceOne Products Compatibility Guide for the specific version

• Manually install


Pre-installation

ONM Viewer client computer requirementsThis table describes the requirements for client computers running the EMC SourceOne ONM Viewer software.

Table 15 EMC SourceOne ONM Viewer client computer base requirements

Mobile device requirementsRefer to the EMC SourceOne Products Compatibility Guide for more detailed information on mobile device support. For information on how to configure mobile device support, see the EMC SourceOne Administration Guide.

Hardware Standard desktop or laptop used in a corporate environment.

OS Refer to the EMC SourceOne Products Compatibility Guide for more detailed information on operating system requirements.

Network Standard connection to the corporate network.


Email software (Domino) • Ensure IBM Lotus Notes installed• Validated by EMC SourceOne software installation that email

client version is supported


• Manually or silently install• Validated by EMC SourceOne software installation




Important Considerations 73

4

This chapter provides important considerations to review when preparing to install EMC SourceOne products.


◆ Common considerations (all products) .......................................... 74◆ Email Management considerations ................................................. 84

ImportantConsiderations



Common considerations (all products)This section describes considerations for all EMC SourceOne products.

◆ Native Archive Index Work directory considerations.................. 74◆ Hardware repurposing considerations........................................... 75◆ Important SQL Server considerations............................................. 75◆ Additional service accounts to support least privileges .............. 81◆ Service account passwords............................................................... 82◆ Regional and language options to support indexing ................... 82

Native Archive Index Work directory considerationsEMC SourceOne performs all indexing locally on the Native Archive computer. To support this requirement, you must allocate a local directory (referred to as the Index Work directory) with at least 20 GB of space on all Native Archive indexing computers to serve as a temporary space for indexing. This directory:

◆ Must be regarded as a local drive by the operating system.

◆ Can not be the operating system drive (e.g., C:).

◆ Can be on local disk or SAN storage, as long as it is regarded as a local drive by the Native Archive server. For best performance, this should be on a dedicated physical disk.

◆ Requires a minimum of 20 GB of free disk space be available.

Ideally you should allocate the required space prior to installing Native Archive software on your indexing servers (Native Archive disk configuration and storage information in “Example configurations” on page 29). Then, when installing the Native Archive software, simply select a destination folder on this drive.

Although you are required to specify this location when installing the Native Archive software, you can bypass the 20 GB requirement during the installation (the installer will provide a warning). This is necessary when installing Native Archive software on a server which is not designated for indexing. If you later decide to enable indexing, you will need to either:

◆ Free up space on the current Index Work directory drive.

◆ Move the Index Work directory to another drive which has enough space.

Common considerations (all products) 75


Example You install Native Archive software on a computer not originally intended to perform indexing, but you later decide to enable the indexing role. The current Index Work directory that you established when you installed the Native Archive software is on a 30 GB drive, but has only 5 GB of free disk space. In this case, you can either:

◆ Move or delete files to free up 20 GB space, and then enable the indexing role on this server.

◆ Use a utility (provided in the EMC SourceOne Email Management 6.6 SP1 software kit) to move the Index Work directory to another drive with at least 20 GB of free space. You can then enable the indexing role.

Details about both of these options are provided in the "Maintaining EMC SourceOne" chapter in the EMC SourceOne Administration Guide.

Hardware repurposing considerationsWhen procuring systems on which you will install EMC SourceOne server components (e.g., Master Services, Worker Services, Web Services, Native Archive Services) you should utilize "clean" systems to avoid issues resulting from conflicts with previously installed software. If you must repurpose a computer for use with EMC SourceOne, you should reformat the system and re-install the operating system.

Important SQL Server considerationsThis section applies to the SQL Server used to host the EMC SourceOne databases.

For information about the SQL Server used to host EMC SourceOne reports, refer to “Installing EMC SourceOne Reporting” on page 273.

Review the important considerations provided in this section.

◆ Enterprise Edition vs. Standard Edition.......................................... 76◆ SQL Server disk configuration.......................................................... 76◆ Database partitioning......................................................................... 77◆ Disk partition alignment best practices........................................... 77◆ Memory allocation in 64-bit SQL Server ......................................... 78◆ Page file size ........................................................................................ 78◆ General SQL Server information ...................................................... 78◆ SQL database installation permissions............................................ 78



◆ EMC SourceOne database installation methods ........................... 79◆ Alias configuration for SQL Server host computer ...................... 79◆ Recovery model considerations....................................................... 80◆ SQL Server collation settings ........................................................... 80◆ Storage best practices ........................................................................ 81

Enterprise Edition vs. Standard EditionSQL Server Enterprise Edition is recommended, as it supports database partitioning, online index maintenance, and provides data management and performance benefits for the Native Archive and Activity databases.

You should review considerations with your EMC representative to determine the advantages or disadvantages of selecting Enterprise or Standard Edition for your deployment.

For additional information about comparing Standard and Enterprise edition features, refer to the following resource:

http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx

For information on configuring partitioning using the EMC SourceOne console, refer to the EMC SourceOne Administration Guide.

SQL Server disk configurationReview the recommendations provided in this section.

SQL Server host computer:

◆ Because of the critical nature of the processing performed by EMC SourceOne, you should use a dedicated SQL Server host.

◆ Do not use the same EMC SourceOne SQL Server host for other databases or applications.

EMC SourceOne databases and logs:

◆ When you install EMC SourceOne databases, the databases and log files are created on the default data and log location configured in SQL Server. For best performance, and depending on available disks and storage, you should detach, move and attach the EMC SourceOne databases and logs to separate disks attached to adequate storage:

• Ideally, each EMC SourceOne database (Archive, Activity, Search) should reside on a dedicated drive connected to Tier 1 storage.

http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx



• If this is not feasible, the Archive database should be on a dedicated drive, the Activity and Search databases can be co-located on the same drive.

• The Archive database logs should be on a dedicated drive (separate from the database drives).

SQL Server system databases and logs:

◆ The SQL Server TempDB database should be on a dedicated drive in accordance with Microsoft’s best practices. Refer to the following resource:

http://technet.microsoft.com/en-us/library/cc966534.aspx

◆ SQL Server logs should be on a dedicated drive

Database partitioning Review the recommendations provided in this section.

The EMC SourceOne Administration Guide provides information and recommendations for configuring and managing database partitioning.

Note: EMC SourceOne versions prior to version 6.6 SP1 allowed you to specify the number of files a partition can host equal to one half the number of CPUs on the SQL Server host. When you upgrade to version 6.6 SP1, the number of files per partition is reset to a default of 1. The EMC SourceOne Administration Guide provides information on changing this option.

Disk partition alignment best practicesObserve the following best practices related to disk partition alignment:

◆ Align sectors and tracks on the disk. This can result in significant performance gains for IO intensive system such as EMC SourceOne.

◆ Consult your storage hardware vendor and ask for proof of successful disk partition alignment.

◆ Microsoft recommends stripe size of 128K/256K for SQL Server 2008.

Review the following resource for disk partition alignment best practices:

http://msdn.microsoft.com/en-us/library/dd758814%28SQL.100%29.aspx






Memory allocation in 64-bit SQL ServerTo prevent performance issues with 64-bit versions of SQL Server, lock the memory that is allocated for the buffer pool in physical memory.

Note: This practice applies to physical environments and may not be true in virtualized environments. Consult with your virtualization vendor.

Refer to the following resource for details:

http://support.microsoft.com/kb/918483

Note the following:

◆ This option off by default

◆ For 64-bit SQL Server Standard Edition, this setting may be ignored

Page file sizeMicrosoft recommends the page file to be 1.5 times physical RAM but not more than 3 times. For details:

http://support.microsoft.com/kb/889654/en-us

Note the following:

◆ Data and log files are created on default SQL data and log directory

◆ Data and log files should be moved to appropriate drives

General SQL Server informationThis section provides general information to describe how EMC SourceOne uses Microsoft SQL Server:

◆ EMC SourceOne uses Windows authentication (not SQL authentication).

◆ As a security consideration, do not use IIS on your SQL Server host.

◆ EMC SourceOne does not use hard-coded SQL accounts.

SQL database installation permissionsTo successfully install or update the EMC SourceOne databases, you must ensure that the installation account used to log in to the SQL Server host computer:

◆ Is a member of the local administrators group

�http://support.microsoft.com/kb/918483

http://support.microsoft.com/kb/889654/en-us



◆ Has SQL sysadmin server role privileges

By default in SQL Server the sysadmin role contains all members of the Windows BUILTIN\Administrators group and the local administrator's group. If the default configuration exists, and the installation account is a member of either of these groups, it already has the sysadmin role. In customer scenarios where this is not the case, you must temporarily establish the permissions described above.

The sysadmin role for the installation account is specifically needed to add system-level error codes in the sys.messages table and is not used for any other purpose.

This permissions requirement is temporary, and is only needed until you complete all database installations or updates and verified success by reviewing the database installation log files. For security purposes, you can remove this installation account from the local administrators group and revoke the sysadmin role once installation or update of the databases is complete.

Note: Procedures for updating existing EMC SourceOne databases is provided in the product release notes.

EMC SourceOne database installation methodsYou can install the EMC SourceOne databases using either a MSI installation program or scripts:

◆ Using the installation scripts allows you to inspect the database installation process before running. Installation errors are presented "in stream" during installation

◆ The MSI program installs the three EMC SourceOne databases at once. You must manually review the installation log to check for errors indicating installation success or failure.

Alias configuration for SQL Server host computerTo provide the flexibility to move EMC SourceOne databases from one physical SQL Server host computer to another to support disaster recovery, you should configure a CNAME alias for your SQL Server before installing EMC SourceOne software.

◆ When an EMC SourceOne component installation program asks you to enter your SQL Server host computer, provide the CNAME alias instead of the physical host name.



◆ This is the required configuration to support re-directing EMC SourceOne servers to an alternate database server at the disaster recovery site during failover. For details about this configuration, refer to the EMC SourceOne Disaster Recovery Solution Guide.

Recovery model considerationsSQL Server recovery models are designed to control transaction log maintenance and prepare your environment for disaster recovery. Three recovery models exist: simple, full, and bulk-logged. Each of these models represents a different approach to balance the tradeoff of conserving disk space against providing for more granular disaster recovery options.

Typically a database uses the full or simple recovery model. By default, EMC SourceOne databases are installed in the simple recovery model to conserve log space. This model may not be suitable for all environments depending on the database backup methodology and tools used. If necessary, you can change to a full recovery model if this better suits your environment.

For details on recovery models and their use, refer to the following resource:

http://msdn.microsoft.com/en-us/library/ms189275.aspx

SQL Server collation settingsEMC SourceOne databases are case insensitive, and can be installed in a case insensitive or case sensitive SQL Server environment.

EMC SourceOne requires the default SQL Server collation settings as described in Table 16.

Table 16 SQL Server collation settings

Server collation Operating system

SQL_Latin1_General_CP1_CI_AS English

Latin1_General_CI_AS French

Latin1_General_CI_AS Italian

Latin1_General_CI_AS German

http://msdn.microsoft.com/en-us/library/ms189275.aspx



Storage best practicesReview the following resource for SQL Server storage best practices:


Note: Best practice number 8 in the above link generally applies to the TempDB only, and not necessarily user databases such as SourceOne databases.

Additional service accounts to support least privilegesEMC SourceOne requires at least one primary service account to operate. This service account is placed in the EMC SourceOne security group. You can optionally create additional service accounts (and place them in the security group) in environments which require least possible permissions:

◆ Master Services service account – This optional service account can be specified when installing Master Services software instead of the primary service account. Details:

• This account is associated only with a dedicated Master Services computer, as the Master Services software requires that the service account remain a member of the local administrators group in order to interact with the Windows Job Scheduler service.

• Other computers in the EMC SourceOne configuration do not require the primary service account to be a member of the local administrators group.

• If you are also installing Worker Services software on this computer, you should use the primary service account.

Latin1_General_CI_AS Spanish

Japanese_CI_AS Japanese

Chinese_PRC_CI_AS Simplified Chinese

Table 16 SQL Server collation settings

Server collation Operating system




◆ OWA service account (Email Management environments only) – This optional service account can be specified when installing Extensions for OWA software on Exchange servers to limit the access to Exchange to a dedicated service account rather than using the primary service account.

Service account passwordsTo ensure continuous operation, EMC recommends configuring service accounts used with EMC SourceOne to have passwords which do not expire. If a service account is allowed to expire, this will cause authentication errors to be written to the event logs.

You should be aware of when this password will expire and change it before it expires to avoid interrupting EMC SourceOne processing. After you have changed the password in Active Directory, re-run the installation to access the Repair function.

For more details on resetting service account passwords, see the EMC SourceOne Administration Guide.

Regional and language options to support indexingFor all languages which you expect to encounter when indexing email and files, you must ensure that the following language support is configured on a Native Archive server running Microsoft Windows Server 2003:

◆ Code page conversion tables

◆ East Asian language files

Note: This issue does not exist with Windows Server 2008.

Code page conversion tablesEnable the appropriate code page conversion tables:

1. Click Start > Control Panel > Regional and Language Options.

2. Click the Advanced tab.

3. Select the appropriate languages in the Code page conversion tables section.

4. Click Apply.



East Asian language files1. Install East Asian language files:

2. Click Start > Control Panel > Regional and Language Options.

3. Click the Languages tab.

4. Select Install files for East Asian languages.

5. Click Apply.

6. Click OK.



Email Management considerationsThis section describes considerations for all EMC SourceOne Email Management environments.

◆ Compatibility with EMC EmailXtender ......................................... 84◆ Service account mailbox restrictions and workaround................ 84◆ Indexing support for embedded Exchange messages.................. 85◆ Search service startup........................................................................ 85

Compatibility with EMC EmailXtenderDo not install EMC SourceOne Email Management components on an EmailXtender server. No EMC SourceOne Email Management components are required on the EmailXtender server to communicate with the EmailXtender archive.

Service account mailbox restrictions and workaroundSome sites prohibit the creation of a mailbox for a service account. However, EMC SourceOne requires that the primary service account have full mailbox rights to a mailbox in order to function in an Exchange environment. To address this scenario:

1. Create a separate mailbox not directly associated with the service account (for example, ES1 Mailbox).

2. Grant the primary service account Full Mailbox access to this mailbox.

3. Configure the MAPI profile (called EMCSourceOne) used on the Worker Services computer(s) to point to this mailbox. See “Worker Services host computer requirements” on page 63 for details.

Email Management considerations 85


Indexing support for embedded Exchange messagesTo support full-text indexing of embedded Exchange messages you must install Microsoft Outlook 2007 on all Native Archive computers. Note the following:

◆ This is a new prerequisite not previously required for EMC SourceOne Native Archive computers prior to version 6.6.

◆ This is primarily applicable to Microsoft Exchange environments.

◆ You can choose not to install Microsoft Outlook. For example, if you are installing SourceOne in an IBM Lotus Domino or EMC SourceOne for Microsoft SharePoint environment, Microsoft Outlook is not needed.

However, it may be useful to install Outlook in a Domino environment to support the scenario in which an Exchange message (.msg) is embedded in a Domino message.

◆ Unlike master or worker computers, a MAPI profile is not required.

◆ If running Native Archive Services software on the same computer on which Worker Services is installed, the Outlook client software which must be installed as a prerequisite for the Worker Services software is sufficient.

Search service startupAfter initial installation and system restart, the EMC SourceOne Search Service may not start, and will display a corresponding error message. This message can be safely ignored, as the Search Service will start upon receiving its first search request.



Modifying the EMC SourceOne Notes user accountDo not modify the EMC SourceOne Notes user account. If you modify the Notes user account configured for use by EMC SourceOne services, Domino-related features, including address book synchronization, may not function. Also, Notes users will not be able to log in to the EMC SourceOne Search client and will receive the following error:

Padding is invalid and cannot be removed

If this issue occurs, contact EMC Support.

Installing Common EMC SourceOne Components 87

5

This chapter describes how to install components of EMC SourceOne commonly needed to support all EMC SourceOne products including EMC SourceOne Email Management, EMC SourceOne for Microsoft SharePoint and EMC SourceOne for File Systems. Each section in this chapter is presented in the order in which the components should be installed, as some installed components are dependent on previously installed components.


◆ Pre-installation checklist ................................................................... 88◆ Installation overview......................................................................... 89◆ Installing common EMC SourceOne components ........................ 90◆ Maintaining the installation ........................................................... 149

Installing CommonEMC SourceOne

Components


Installing Common EMC SourceOne Components

Pre-installation checklistBefore beginning the installation procedures detailed in this chapter, ensure that the items in the following checklist are completed.

Table 17 Pre-installation checklist

Activity Description

Review the product overview information

Review the product overview information and under-stand the features and options. See “Product over-view” on page 12 and the EMC SourceOne Administration Guide.

Understand the system ar-chitecture

Review the components which comprise EMC Source-One system. See “System architecture” on page 18 and “System components” on page 19.

Complete analysis activities Compile and analyze the organization’s requirements, metrics and processes. See “Pre-deployment plan-ning” on page 26.

Complete configuration planning activities

Size the environment and adjust variable components of the configuration to support it. See “System archi-tecture” on page 18 and “Example configurations” on page 29.

Configure accounts and per-missions

Establish the accounts and permissions required to support EMC SourceOne. See “Pre-installation” on page 41.

Establish required hardware and network infrastructure

Ensure that the appropriate hardware is available for installation and connected to the network. Hardware specifications, operating system, and network connec-tivity, and software prerequisites are detailed in “Pre-installation” on page 41.

Installation overview 89


Installation overviewTable 18 provides an overview of the EMC SourceOne common installations presented in the order in which you should perform them.

Table 18 Installation procedure overview

Installation/Configuration Details Procedure

Databases Install the EMC SourceOne Activity, Archive and Search databases. You can install the databases using scripts or an MSI installation program.

• “Installing databases using scripts” on page 91

• “Installing databases using the MSI installer” on page 94

Database permissions

Configure SQL security logins and required database permissions.

“Configure SQL permissions” on page 98

Master Services software

Install Master Services software. Optionally install the software on a second computer and cluster them for high availability.

“Installing Master Services software” on page 103

EMC SourceOne Console application

Install the EMC SourceOne Console application on one or more computers to administer EMC SourceOne.

“Installing the EMC SourceOne Console application” on page 111

Worker Services software

Install Worker Services software on one or more computers to process activities.

“Installing Worker Services software” on page 115

Web Services software

Install Web Services software on one or more Worker Services computers to support search and shortcut resolution functionality. Optionally configure network load balancing for Web Services.

“Installing Web Services software” on page 121

Mobile Services software

Install the Mobile Services software on one or more EMC SourceOne Worker Services computers or a separate IIS Web server to support mobile users, Outlook Web Access users, Outlook users who do not have the EMC SourceOne Offline Access installed, and EMC SourceOne for File Systems users to resolve file links to archived files.

“Installing the EMC SourceOne Search application” on page 128

EMC SourceOne Search application

Install the EMC SourceOne Search application to provide a Web interface for search functionality.

“Installing the EMC SourceOne Search application” on page 128

Native Archive Services software

Install the Native Archive Services software on one or more computers to manage archiving, indexing, searching and retrieving.

“Installing Native Archive Services software” on page 141

Discovery Manager express edition

Optionally, install the Discovery Manager express edition server and client software.

Refer to the EMC SourceOne Discovery Manager Installation and Administration Guide.



Installing common EMC SourceOne componentsUse the following procedures to install common components required in all EMC SourceOne environments:

◆ Installing databases using scripts.................................................... 91◆ Installing databases using the MSI installer .................................. 94◆ Configure SQL permissions ............................................................. 98◆ Installing Master Services software............................................... 103◆ Installing the EMC SourceOne Console application ................... 111◆ Installing Worker Services software............................................... 115◆ Installing Web Services software ................................................... 121◆ Installing the EMC SourceOne Search application ..................... 128◆ Installing Mobile Services software .............................................. 135◆ Installing Native Archive Services software................................ 141

Installing common EMC SourceOne components 91


Installing databases using scriptsThis section describes how to use scripts to create the databases required for EMC SourceOne on a Microsoft SQL Server host computer. You can install the databases on the default instance or a named instance of SQL server.

Note: Alternatively, you can use the MSI installer to install the databases as described in “Installing databases using the MSI installer” on page 94.

You can install the following databases using scripts:

◆ Activity database

◆ Search database

◆ Native Archive database

PrerequisitesFor specific hardware, operating system, network connectivity, and prerequisite software requirements, see “Database host computer requirements” on page 60.

Also refer to “Important SQL Server considerations” on page 75.

ProceduresTable 19 provides an overview of the procedures to install the databases on the Microsoft SQL Server host computer using scripts.

Table 19 Procedures

Step Procedure Details

1 “Copy Database folder to the SQL Server host computer” on page 92

Copy the EMC SourceOne installation files from the software kit to the local computer.

2 “Install the Activity database” on page 92

Installs the database used to process EMC SourceOne activities.

3 “Install the Search database” on page 93

Installs the database used to manage EMC SourceOne Search.

4 “Install the Native Archive database” on page 93

Installs the database used to manage EMC SourceOne archiving, indexing, searching and retrieving.

5 “Configure database permissions” on page 94

Configures database security permissions for EMC SourceOne accounts.



Copy Database folder to the SQL Server host computerTo copy the Database folder locally to the SQL Server host computer:

1. Navigate to the \Setup directory on the EMC SourceOne software kit.

2. Copy the Database folder to a temporary location on the SQL Server host computer.

Install the Activity databaseTo install the Activity database:

1. Log in to the SQL Server host computer using an account with local administrator permissions on the SQL Server host computer and the SQL sysadmin role.

IMPORTANT!See “Service account mailbox restrictions and workaround” on page 84 for additional details.

2. Open a command prompt and navigate to the temporary location to which you copied the Database folder.

3. Run the ES1_ActivityDB_Create_mssql.bat file.

4. Enter the following information:

• SQL Server information

– If you are using the default named instance, enter the SQL Server name in the following format:hostname

– If you are using a named instance, enter the SQL Server name and instance in the following format:hostname\instance

• Database name

• Ensure that you select the option to view the log file. Although the database may appear to install correctly, the log file is the only user interface that will provide important information if an installation issue occurs.

5. Press Enter. The script is executed and the database is installed.

6. Ensure that the installation was successful by reviewing the installation log file.



Install the Search databaseTo install the Search database:


2. Run the ES1_SearchDB_Create_mssql.bat file.





• Search database name




Install the Native Archive databaseTo install the Native Archive database:


2. Run the ES1_ArchiveDB_Create_mssql.bat file.







• Native Archive database name




Configure database permissionsRefer to “Configure SQL permissions” on page 98 to configure the appropriate permissions for each database.

Installing databases using the MSI installerThis section describes how to create the databases required for EMC SourceOne on a Microsoft SQL Server host computer using a Microsoft Installation (MSI) program. You can install the databases on the default instance or a named instance of SQL server.

Note: Alternatively, you can use the database installation scripts as described in “Installing databases using scripts” on page 91.

You can install the following databases using the MSI installer:

◆ Activity database

◆ Search database

◆ Native Archive database

The default database locations and log locations configured in SQL Server are used.

PrerequisitesFor specific hardware, operating system, network connectivity, and prerequisite software requirements, see “Database host computer requirements” on page 60.

For important database installation permissions, see “SQL database installation permissions” on page 78.

For important SQL Server considerations, see “Important SQL Server considerations” on page 75.



ProceduresTable 20 provides an overview of the procedures to install and configure the EMC SourceOne databases on the Microsoft SQL Server host computer.

Copy the setup executable locallyTo copy the setup executables for the databases locally to the SQL Server host computer:

1. Log in to the SQL Server host computer using an account with local administrator permissions on the SQL Server host computer and the SQL sysadmin role.

IMPORTANT!See “SQL database installation permissions” on page 78 for additional details.

2. Navigate to the Setup\Windows directory on the EMC SourceOne software kit.

3. Copy the ES1_DatabaseSetup.exe executable to a temporary location on the SQL Server host computer.

Table 20 Procedures


1 “Copy the setup executable locally” on page 95

Copies the installation executable locally to the SQL Server host computer.

2 “Install databases” on page 96 Installs the EMC SourceOne Activity database, Native Archive database and Search database.

3 “Review database logs” on page 98 Review the database installation logs.

4 “Configure database permissions” on page 98

Configures database security permissions for EMC SourceOne accounts.



Install databasesTo install the databases:

1. Navigate to the temporary location to which you copied the setup executable.

2. Double-click the ES1_DatabaseSetup.exe file and click Run. The Welcome page displays.

3. Click Next to display the Database Log Folder page.

Note: This folder contains only the logs detailing the results of the database installation.

4. Specify the destination directory and click Next to display the Database Instance page.

5. Do one of the following:



• If you are installing the database to the default named instance, leave the Specific Instance check box unchecked and enter the Database Server name.

• If you are installing the database to a named instance, select the Specific Instance checkbox and type the name of the instance.

6. Click Next to display the Database Selection page.

7. Accept the default name or enter a name for each of the following databases:

• Activity Database - used to manage EMC SourceOne processing

• Native Archive Database - used to manage EMC SourceOne archiving, indexing, searching and retrieving

• Search Database - used to manage EMC SourceOne Search

8. Click Next to display the Ready for Installation page.

9. Click Install.

Once the installation is complete, the InstallShield Wizard Completed Page displays.

10. Click Finish.



Review database logsReview the database logs created in the folder specified during installation. Although the database may appear to install correctly, the log file is the only user interface that will provide important information if an installation issue occurs.

You can also verify the EMC SourceOne databases were created by navigating to the databases in Microsoft SQL Server Management Studio.

Configure database permissionsRefer to “Configure SQL permissions” on page 98 to configure the appropriate permissions for each database.

Configure SQL permissionsConfigure Microsoft SQL database permissions for the EMC SourceOne security logins you created during the planning process (“Assigning permissions” on page 47):

◆ Security group

◆ Admins group

◆ Installation account

This section includes:

◆ “Security login considerations” on page 98

◆ “Assign security login roles” on page 99

◆ “Configure permissions for each database” on page 101

Security login considerationsEMC SourceOne requires that the default schema for each of its databases be granted access rights to the EMC SourceOne service account. Assigning permissions to the security group (instead of the EMC SourceOne service account) simplifies the configuration for the following reasons:

◆ If you add the service account as a SQL Server login (not recommended), by default it is assigned the dbo schema. For EMC SourceOne to authenticate properly, it requires that the service account’s own schema be associated with its databases, not the default dbo schema, which does not have the required permissions. You must take the extra step to configure each database to use the service account’s schema.



◆ If you add the security group as a SQL Server login (recommended), it is not assigned the default dbo schema. Therefore, when the service account authenticates indirectly through the security group, a schema associated with the service account user is automatically created.

Assign security login rolesUsing Microsoft SQL Server Management Studio, map the EMC SourceOne security logins to the db_datareader and db_datawriter databases roles for each of the EMC SourceOne databases as shown in Table 21.

Table 21 Database roles for security logins

EMC SourceOneSecurity Login

EMC SourceOneDatabase

Database Role Membership

Admins groupSecurity groupInstallation account

Activity db_datareaderdb_datawriterpublic (default)


Native Archive db_datareaderdb_datawriterpublic (default)


Search db_datareaderdb_datawriterpublic (default)



Figure 7 shows an example of the Login Properties dialog box from which you configure the database role membership for each of the EMC SourceOne security logins. Ensure that you click each database and apply the database role membership permissions.

Figure 7 Login Properties dialog box example



Configure permissions for each databaseConfigure explicit permissions for the security logins for each EMC SourceOne database as shown in Table 21.

Table 22 Explicit permissions for EMC SourceOne databases

EMC SourceOneDatabase

EMC SourceOneSecurity Login Explicit Permissions

Activity Security group Alter*Connect (default)Execute

Admins group Alter**Connect (default)Execute

Installation account Connect (default)

Native Archive Security group AlterConnect (default)Execute

Admins group AlterConnect (default)Execute


Search Security group AlterCreate tableConnect (default)Execute

Admins group Connect (default)Execute




Figure 8 shows an example of the Database Properties dialog box from which you configure the explicit permissions. You must configure the permissions for each individual database as described in Table 22 on page 101.

Figure 8 Database Properties dialog box example



Installing Master Services softwareThis section describes the prerequisites, software requirements, and installation procedures for installing Master Services software on a host computer. This section also describes how to configure two host computers running Master Services software for high availability using a Microsoft Clustering active/passive configuration.

PrerequisitesTable 23 provides an overview of the prerequisites you must complete before installing software.

ProceduresTable 24 provides an overview of the procedures to install and configure EMC SourceOne Master Services software on a host computer.

Table 23 Prerequisites

Prerequisite Details

System requirements Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Master Services host computer requirements” on page 61.

Accounts and permissions Ensure that:• Active Directory accounts and groups and other

permissions-related configuration is completed as described in “Pre-installation” on page 41.

• Database permissions are configured as described in “Configure SQL permissions” on page 98.

Table 24 Procedures



Copies the installation executables locally.

2 “Install Master Services software” on page 104

Installs the EMC SourceOne Master Services software.

3 “Cluster EMC SourceOne Master computers” on page 109

Install Master Services software on a second host computer and configure as nodes in a Microsoft Cluster.



Copy the setup executable locallyTo copy the setup executable for the EMC SourceOne Master Services software locally to the host computer:

1. Log in to the host computer using the EMC SourceOne installation account.


3. Copy the ES1_MasterSetup.exe executable to a temporary location on the host computer.

Install Master Services softwareTo install the EMC SourceOne Master Services software:


2. Double-click the ES1_MasterSetup.exe file and click Run. The Welcome page displays.

Note: When the installer is run, it validates the system configuration to ensure that prerequisite components are installed. Depending on your system configuration, the installer may automatically install one or more prerequisite components before displaying the Welcome page. Automatically installed components are listed in “Establishing system requirements” on page 58.

3. Click Next to display the Destination Folder page.



4. Specify the destination directories:

a. The first destination determines where the primary EMC SourceOne Master Services software files are installed. Click Change to specify a different directory, or accept the default directory.

Note: You should choose a local drive other than the operating system drive. If you are installing Master Services software on an active/passive cluster (“Cluster EMC SourceOne Master computers” on page 109), ensure you install the software to a local drive on each node.

b. The second destination identifies the work directory, which is a temporary storage area for message processing. You should specify a directory with at least 1 GB free space.

5. Click Next to display the Logon Information page.

6. Enter the logon information:

a. Type the fully-qualified Domain.

b. Type the Service Account and Service Account Password.

Depending on the Active Directory accounts you created during the planning process, the service account used when installing the Master Services software can be one of the following:

– Primary service account– Master Services service account



For a more detailed discussion, see the following topics:

– “Creating accounts in Active Directory” on page 43– “Additional service accounts to support least privileges”

on page 81c. Type the EMC SourceOne Security Group. The service

account you choose must be a member of this Security Group.

d. The Enable check box is already checked in the Service Logon Policy region. This setting is required to enable services to run without a logged in user.

e. Click Next to validate the credentials and display the Database page.

7. Enter the database information:

a. Type the Activity Database name.

b. Type the Activity Database Server (or IP) host name.





c. Click Next to display the Email Server Platform page.

8. Select one or more of the following email server types that will be used with EMC SourceOne:

• IBM Lotus Domino

• Microsoft Exchange

• Microsoft Office 365

9. Click Next.

10. If you are installing the EMC SourceOne Master Services software on a computer on which Lotus Notes is installed, the Email Environment page displays.



11. Enter the Notes password for the EMC SourceOne Lotus Notes account configured during the planning process (see “IBM Lotus Domino permissions” on page 57). Click Next to validate the password and display the Ready to Install the Program page.

12. Click Install.


13. Click Finish. Do one of the following:

• If you are installing EMC SourceOne Master Services software on a system on which only Microsoft Outlook is installed, go to step 14.

• If you are installing EMC SourceOne Master Services software on a system on which Lotus Notes software is installed, a Lotus Notes configuration wizard is automatically launched.

– Configure the Notes client software to use the EMC SourceOne Lotus Notes account configured during the planning process (see “IBM Lotus Domino permissions” on page 57).

– Ensure that you copy the Notes ID file locally when prompted by the wizard.

– When the configuration is complete, exit the Notes client.

IMPORTANT!In a mixed-mail environment (Microsoft Exchange and IBM Lotus Domino), do not configure the Lotus Notes client as the default mail client. Microsoft Outlook must be the default mail client.

14. A message displays indicating that you must restart the system. Click Yes.



Cluster EMC SourceOne Master computersFor high availability, set up an active/passive Microsoft Clustering configuration for the two computers on which EMC SourceOne Master Services software is installed.

Prerequisites. Repeat the following procedures to install the EMC SourceOne Master Services software on a second host computer:

◆ “Copy the setup executable locally” on page 104

◆ “Install Master Services software” on page 104

Considerations — Configure each host computer as active/passive nodes in a Microsoft Cluster using the following guidelines:

◆ Each computer requires Microsoft Cluster Administrator to support the configuration.

◆ Each computer should be configured with dual Network Interface Cards (NICs) to support a private connection between each node and a public connection to the network.

◆ The shared quorum disk and data resource disk should be configured on a device accessible using the public network connection to both nodes.

◆ For detailed background information and instructions on configuring Microsoft Clustering, refer to the Microsoft documentation set.

Procedure — To create a Group and Resource for EMC SourceOne services:

1. On both nodes, set the following services to Manual:

• EMC SourceOne Address Cache (ExAddressCacheService)

• EMC SourceOne Job Scheduler (ExJobScheduler)

• EMC SourceOne File Mover Agent (ES1MoverAgent)

Note: While the Address Cache and Job Scheduler services are present on all master computers, the EMC SourceOne File Mover Agent service is only installed if you selected Microsoft Office 365 support when installing the Master Services software.

2. On one of the nodes, click Start > Programs > Administrative Tools > Cluster Administrator.

3. Right-click Groups and click New > Group.

4. Enter a name for the group and click Next.

5. Click Finish.



The new group is displayed in the Groups folder.

6. Right-click the new group and select New > Resource.

7. Enter a name for the resource (for example, EMC Master Service) in the Name field and select Generic Services from the Resource type dropdown list.

8. Click Next to display the Possible Owners page.

9. Click Next to display the Dependencies page.

10. Click Next to display the Generic Service Parameters page.

11. In the Service Name field, type ExJobScheduler.

12. Click Next to display the Registry Replication page.

13. Click Finish.

14. Right click the service and select Bring Online. The State field indicates the service is Online.

15. Repeat steps 6 through 14 to create a resource for the ExAddressCacheService service.

16. If Microsoft Office 365 support is installed, repeat steps 6 through 14 to create a resource for the ES1MoverAgent service.

17. Restart the Microsoft Cluster services.

18. Verify that the Group is Online.

19. Verify that the following services are set to Manual and are only running on one node:

• EMC SourceOne Address Cache

• EMC SourceOne Job Scheduler

• ES1MoverAgent (if used)

Note: If the services are running at the same time on each node, this may cause duplicate jobs to be processed. By shutting down the systems after the services are created in the cluster group, the cluster will take control of them and only allow them to run on one node at a time.



Installing the EMC SourceOne Console applicationYou can install the EMC SourceOne Console application on the Master Services host computer or a client computer that meets the system requirements. You can install the EMC SourceOne Console on one or more computers.


ProceduresTable 26 provides an overview of the procedures to install and configure EMC SourceOne Console software on a host computer.



System requirements Hardware, operating system, network connectivity, and prerequisite software requirements for installing the EMC SourceOne Console application on one of the following:• Master Services host computer - described in “Master

Services host computer requirements” on page 61.• Client computer - described in “EMC SourceOne

Console client computer requirements” on page 69.




Table 26 Procedures



Copies the installation executable locally.

2 “Install EMC SourceOne Console software” on page 112

Installs the EMC SourceOne Console software.



Copy the setup executable locallyTo copy the setup executable for the EMC SourceOne Console software locally to the host computer:



3. Copy the ES1_ConsoleSetup.exe executable to a temporary location on the host computer.

Install EMC SourceOne Console softwareTo install the EMC SourceOne Console software:


2. Double-click the ES1_ConsoleSetup.exe file and click Run. The Welcome page displays.




4. Accept the default location and click Next to display the Administrators Group page.

5. Enter the Administrators Group information:

a. Accept the default Domain.

b. Type the Administrators Group.

– If this environment uses a separate EMC SourceOne Admins group to house the console administrator accounts, type the name for this group.

– If this environment houses console administrators in the EMC SourceOne Security Group (which also houses the service accounts used by EMC SourceOne), type the name for this group.

Note: For details about the Admins and Security Group configuration, see “Creating accounts in Active Directory” on page 43.



6. Click Next to display the Database page.



b. Type the Activity Database Server host name.



c. Click Next to display the Product Shortcuts page.

8. Select the desired options and click Next to display the Ready to Install the Program page.

9. Click Install.





Installing Worker Services softwareThis section describes how to install the EMC SourceOne Worker Services software on a host computer.


ProceduresTable 28 provides an overview of the procedures to install and configure EMC SourceOne Worker Services software on a host computer.

Copy setup executable locallyTo copy the setup executable for the EMC SourceOne Worker Services software locally to the host computer:




System requirements Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Worker Services host computer requirements” on page 63.




Table 28 Procedures


1 “Copy setup executable locally” on page 115

Copies the installation executables locally to the computer.

2 “Install Worker Services software” on page 116

Installs the EMC SourceOne Worker Services software.




3. Copy the ES1_WorkerSetup.exe executable to a temporary location on the host computer.

Install Worker Services softwareTo install the EMC SourceOne Worker Services software:


2. Double-click the ES1_WorkerSetup.exe file and click Run. The Welcome page displays.




a. The first destination determines where the primary EMC SourceOne Worker Services files are installed. Click Change to specify a different directory, or accept the default directory.

Note: You should choose a drive other than the operating system drive.




5. Click Next to display the Job Log Folder page.

Consider the following:

• This location was established during the planning phase with appropriate permissions granted to the EMC SourceOne security group. See “Assigning permissions” on page 47 for details.

• This file share location will contain job detail logs which support the viewing of job details from the EMC SourceOne Console.

• You must configure all Worker Services computers to use the same location.

• If you choose to enable job detail logging in the EMC SourceOne Console, ensure that this location includes sufficient space to allow for log growth or specify a location with expandable storage.

6. Enter a path (\\hostname\share) or click Browse and navigate to the location.





a. Type the fully-qualified Domain.

b. Type the Service Account and Service Account Password. This is the EMC SourceOne primary service account username and password.

c. Type the EMC SourceOne Security Group. The service account must be a member of this Security Group.

d. The Enable checkbox is already checked in the Service Logon Policy region. This setting is required to enable services to run without a logged in user.




9. Enter the database information.

Note: Some of this information may be pre-filled if you have already installed other EMC SourceOne software (such as Master Services software) on this computer. Accept the default values.


b. Type the Activity Database Server host name.



c. Type the Search Database name.

d. Type the Search Database Server host name.



e. Click Next.

10. If you are installing the EMC SourceOne Worker Services software on a computer on which Lotus Notes is installed, the Email Environment page displays.

11. Enter the Notes password for the EMC SourceOne Lotus Notes account configured during the planning process (see “IBM Lotus Domino permissions” on page 57). Click Next to validate the password and display the Ready to Install the Program page.

12. Click Install.


13. Click Finish. Do one of the following:

• If you are installing EMC SourceOne Worker Services software on a system on which only Microsoft Outlook is installed, go to step 14.



• If you already installed Master Services software on this computer (and therefore have already configured the Lotus Notes client software) go to step 14.

• If you are installing EMC SourceOne Worker Services software on a system on which Lotus Notes software is installed, a Lotus Notes configuration wizard is automatically launched.

– Configure the Notes client software to use the EMC SourceOne Lotus Notes account configured during the planning process (see “IBM Lotus Domino permissions” on page 57).

– Ensure that you copy the Notes ID file locally when prompted by the wizard.

– When the configuration is complete, exit the Notes client.

IMPORTANT!In a mixed-mail environment (Microsoft Exchange and IBM Lotus Domino), do not configure the Lotus Notes client as the default mail client. Microsoft Outlook must be the default mail client.


15. If necessary, repeat this procedure on other EMC SourceOne Worker computers.



Installing Web Services software Web Services software can be installed on one or more Worker Services computers to support underlying Web functions such as fielding search requests and performing shortcut resolution. Installing Web Services software creates an IIS Web site (SearchWS).

This section describes how to install the EMC SourceOne Web Services software on a host computer on which EMC SourceOne Worker Services is installed. This section also includes information on implementing load balancing for the Web Services application.

Prerequisites

Table 29 provides an overview of the prerequisites you must complete before installing software.



System requirements Hardware, operating system, network connectivity, and pre-requisite software requirements are described in “Worker Services host computer requirements” on page 63.

Accounts and permissions Ensure that:• Active Directory accounts and groups and other permis-

sions-related configuration is completed as described in “Pre-installation” on page 41.


EMC SourceOne software Install Worker Services software on this computer prior to installing the Web Services software.



ASP.NET considerationsEMC SourceOne uses several Microsoft Internet Information Services (IIS) Web sites to support product functionality. These sites require ASP.NET 2.0 (as described in “Establishing system requirements” on page 58). If the default Web site on the IIS server is configured to use ASP.NET 1.1, the EMC SourceOne installation will change the version to ASP.NET 2.0, resulting in a restart of IIS. An error message similar to the following may be observed as a result of the IIS restart:

Failed while restarting W3SVC. Error code: 0x80070420

You can avoid this error being generated by ensuring that the default Web site on your IIS server is configured to use ASP.NET 2.0 before installing EMC SourceOne software.

ProceduresTable 30 provides an overview of the procedures to install and configure EMC SourceOne Web Services software on a host computer.

Table 30 Procedures


1 “Copy setup executable locally” on page 123

Copies the installation executables locally to the computer.

2 “Install Web Services software” on page 123

Installs the EMC SourceOne Web Services software.

3 “Configuring load balancing” on page 125 Optional. Configure load balancing.

4 “Configure firewall rules (Windows Server 2008 R2 only)” on page 125

Configures rules to allow EMC SourceOne services and system components to communicate with other services on the network.

5 “Configure IIS 7.5 role services (Windows Server 2008 R2 only)” on page 126

If installing on Windows Server 2008 R2, configure required service roles.

6 “Configure single sign-on (SSO)” on page 127

Provides a reference to information on configuring single sign-on.

7 “Review IBM Lotus Domino consideration” on page 127

Review this consideration if installing in an IBM Lotus Domino environment.



Copy setup executable locallyTo copy the setup executable for the EMC SourceOne Web Services software locally to the host computer:



3. Copy the ES1_WebServicesSetup.exe executable to a temporary location on the host computer.

Install Web Services softwareTo install the EMC SourceOne Web Services software:


2. Double-click the ES1_WebServicesSetup.exe file and click Run. The Welcome page displays.




4. Accept the default location and click Next to display the Logon Information page.


a. Type the Domain.

b. Type the Username and Password. This is the EMC SourceOne primary service account username and password.



e. Click Next to validate the credentials and display the Ready for Software Installation page.

6. Click Install.


7. Click Finish.



Configuring load balancingTo support load balancing across two or more Worker Services computers running Web Services software, you can utilize network load balancing using an appliance or software solution such as the Microsoft Network Load Balancing Service (NLBS).

You can install Web Services software on multiple Worker Services computers and configure EMC SourceOne applications that require a Web Services location to access a virtual host name configured using the appropriate load balancing solution. The service then distributes the requests to multiple servers to balance the load.

Once you establish the virtual host name, you can specify this host information when installing EMC SourceOne applications that require you to provide the Web Services location. Several application installations require a Web Services location, depending on the environment.

All environments

◆ EMC SourceOne Search

◆ Mobile Services

Email Management environments

◆ Extensions for OWA 2007 Support

◆ Extension for OWA 2010 Support

◆ Extensions for IBM Lotus Domino Support

◆ Offline Access

SharePoint environments

◆ SharePoint Archive Search

Details for selecting a virtual host name when identifying the Web Services location are provided within the installation procedure for each of these components.

Configure firewall rules (Windows Server 2008 R2 only)If using Windows Server 2008 R2, create new firewall inbound rules to allow connections to the following EMC SourceOne services:

◆ EMC SourceOne Document Management Service (DocManageSvcHost.exe)

◆ EMC SourceOne Offline Access Retrieval Service (DocManageSvcOAHost.exe)



Refer to the following Microsoft article for details on configuring firewall rules using Windows Firewall with Advanced Security in Windows Server 2008 R2:

http://go.microsoft.com/fwlink/?linkid=137808

Configure IIS 7.5 role services (Windows Server 2008 R2 only)For Windows 2008 R2, use Server Manager to configure the role services using the information in Table 31.

Table 31 IIS 7.5 Role Services and EMC SourceOne SearchWS requirements

IIS Role ServiceRequired for EMC SourceOne Web Services (SearchWS)

Common HTTP Features

Static Content Required

Default Document Required

HTTP Errors Required

Application Development Features

ASP.NET Required

.NET Extensibility Required (for ASP.NET)

ISAPI Extensions Required (for ASP.NET)

ISAPI Filters Required (for ASP.NET)

Security Features

Basic Authentication Required

Windows Authentication Required (if using SSO)

Request Filtering Required

Management Tools

IIS Management Console Required

Note: If using SSO, the IIS Management Console is required to perform the SSO configuration. A local instance is required if server is not remotely managed.

IIS Metabase Compatibility Required

http://go.microsoft.com/fwlink/?linkid=137808



Configure single sign-on (SSO)For information on configuring SSO, refer to the following sections:

◆ Single Sign-on Support Example (Windows) ............................... 223◆ Single Sign-on Support Example (Domino) ................................. 249

Note: You can wait until all EMC SourceOne IIS sites (Web Services, Search and Mobile Services) are installed before configuring SSO.

Review IBM Lotus Domino considerationIf you are running EMC SourceOne Web Services in a Domino-only environment, note that the Web Services installation creates a service called EMC SourceOne Offline Access Retrieval Service. This service is configured to start automatically, but is only necessary in an Exchange environment. You can safely configure this service to start manually.



Installing the EMC SourceOne Search applicationThe EMC SourceOne Search application installs an IIS Web site (Search) which supports the Web client interface to end users and passes query and results data to and from the EMC SourceOne Web Services software installed on a Worker Services computer.

Deployment scenariosDepending on the size of your environment, load balancing requirements, and security considerations, you can deploy the EMC SourceOne application in several ways.

Single-box scenarioYou can install the EMC SourceOne Search application on a single EMC SourceOne Web Services computer.

Figure 9 Search deployment - single-box scenario

Load balancing scenarioYou can install the EMC SourceOne Search application on two or more EMC SourceOne Web Services computers and configure network load balancing using an appliance or software solution such as Microsoft Network Load Balancing Service (NLBS).

When using a network load balancer, you must configure server affinity (also referred to as sticky sessions) to ensure that a Web browser’s requests are handled by the same Search server instance throughout the duration of the user’s session.



Figure 10 Search deployment - load balancing scenario

Secure Sockets Layer (SSL) considerationsNote the following considerations for using SSL with EMC SourceOne Search:

◆ During the installation of EMC SourceOne Search, you are presented with the option of enabling SSL. If you select this option and SSL is not enabled for the Web Services, EMC SourceOne Search will not be able to communicate with the Web Services. Ensure that SSL is enabled for Web Services before selecting this option during the install.

◆ Sensitive data is transmitted between EMC SourceOne Search and EMC SourceOne Web Services. If you are installing EMC SourceOne Search on an IIS Web server (e.g., not the same physical computer as the EMC SourceOne Web Services), you should enable SSL when installing EMC SourceOne Search.

◆ If you are installing EMC SourceOne Search on an IIS Web server, you should configure SSL for the Web server itself. Sensitive information such as usernames and passwords are transferred between a user’s Web browser and the Web server. This SSL configuration recommendation is unrelated to the Web Services SSL configuration and enabling SSL during EMC SourceOne Search installation.



User accessUsers can access the application from their browser using a URL and authenticate using their Windows Logon or Lotus Notes credentials as described in the EMC SourceOne Search User Guide.






System requirements Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Worker Services host computer requirements” on page 63 if installing in the one of the following deployment scenarios:• “Single-box scenario” on page 128• “Load balancing scenario” on page 128If installing on an IIS Web server, see “Storage environment requirements” on page 67.

Accounts and permissions Ensure that Active Directory accounts and groups and other permissions-related configuration is completed as described in “Pre-installation” on page 41.

EMC SourceOne software This installation requires that an EMC SourceOne Web Services computer exists and is accessible on the network. You will specify this host name during the EMC SourceOne Search installation. If you have configured two or more Web Services computers in a load balancing cluster, you will instead specify the virtual host name during the EMC SourceOne Search software installation. See “Configuring load balancing” on page 125 for more information.




ProceduresTable 33 provides an overview of the procedures to install and configure EMC SourceOne Search software on a Worker Services host computer or a Web server.

Copy the setup executable locallyTo copy the setup executable for the EMC SourceOne Search software locally to the host computer:

1. If installing the software on an:

• EMC SourceOne Worker Services computer, log in to the host computer using the EMC SourceOne installation account.

• IIS Web server, log in to the host computer using an account which is a member of the local administrators group.


2. Copy the ES1_SearchSetup.exe executable to a temporary location on the host computer.

Table 33 Procedures




2 “Install EMC SourceOne Search software” on page 132

Installs the EMC SourceOne Search software.







Install EMC SourceOne Search softwareTo install the EMC SourceOne Search application software:


2. Double-click the ES1_SearchSetup.exe file and click Run. The Welcome page displays.







a. Type the Domain.




6. Click Next to display the Web Services page.



7. Enter the Server Name for the computer on which Web Services software is installed. If using SSL, enter the server name or alias to which the SSL certificate was issued.

8. Optionally select the Use SSL (Secure Sockets Layer) checkbox to enable EMC SourceOne Search to communicate with Web Services using an SSL connection only if you have already configured SSL for the Web Services. Review the considerations described in “Secure Sockets Layer (SSL) considerations” on page 129 before proceeding.

9. Click Next to display the Product Shortcuts page.

10. Click Next to validate the credentials and display the Ready for Software Installation page.

11. Click Install.


12. Click Finish.

Configure IIS 7.5 role services (Windows Server 2008 R2 only)For Windows 2008 R2, use Server Manager to configure the role services using the information in Table 34.

Table 34 IIS 7.5 Role Services and EMC SourceOne requirements (Search)

IIS Role ServiceRequired for EMC SourceOne Search (Search)






ASP.NET Required




Security Features




◆ Single Sign-on Support Example (Windows) ............................... 223◆ Single Sign-on Support Example (Domino) ................................. 249Note: You can wait until all EMC SourceOne IIS sites (Web Services, Search and Mobile Services) are installed before configuring SSO.

Installing Mobile Services softwareYou can install the Mobile Services software on one or more Worker Services computers or on a separate IIS Web server to provide Universal URL support for EMC SourceOne Email Management users, specifically:

◆ Mobile users

◆ Outlook Web Access users

◆ Outlook users who do not have the EMC SourceOne Offline Access installed

For EMC SourceOne for File Systems users, the Universal URL also provides support for resolution of links to files in the Native Archive which were archived from a file server.

Installing Mobile Services software creates an IIS Web site (ExShortcut).




Management Tools




Table 34 IIS 7.5 Role Services and EMC SourceOne requirements (Search)

IIS Role ServiceRequired for EMC SourceOne Search (Search)




ProceduresTable 36 provides an overview of the procedures to install and configure Mobile Services software on a host computer.



System requirements

Worker Services computer - Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Worker Services host computer requirements” on page 63.IIS Web server - Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Storage environment requirements” on page 67.

Accounts and permissions

Ensure that:• Active Directory accounts and groups and other



EMC SourceOne software

This installation requires that an EMC SourceOne Web Services computer exists and is accessible on the network. You will specify this host name during the EMC SourceOne Mobile Services installation. If you have configured two or more Web Services computers in a load balancing cluster, you will instead specify the virtual host name during the EMC SourceOne Mobile Services software installation. See “Configuring load balancing” on page 125 for more information.

Table 36 Procedures






Copy the setup executable locallyTo copy the setup executable for the Mobile Services software locally to the host computer:



3. Copy the ES1_MobileSetup.exe executable to a temporary location on the host computer.

Install Mobile Services softwareTo install the Mobile Services software:


2. Double-click the ES1_MobileSetup.exe file and click Run. The Welcome page displays.

2 “Install Mobile Services software” on page 137

Installs the EMC SourceOne Mobile Services software.





Table 36 Procedures







a. Type the Domain.






6. Click Next to validate the credentials and display the Web Services page.

7. Enter the Server Name for the computer on which Web Services software is installed. Note the following:

• If using load balancing such as Microsoft NLBS, enter the virtual host name.

• If using SSL, enter the server name or alias to which the SSL certificate was issued.

8. Click next to display the Ready for Installation page.

9. Click Install.


10. Click Finish.



Configure IIS 7.5 role services (Windows Server 2008 R2 only)For Windows 2008 R2, use Server Manager to configure the role services using the information in Table 37..

Table 37 IIS 7.5 Role Services and EMC SourceOne requirements

IIS Role ServiceRequired for EMC SourceOne Mobile Services(ExShortcut)






ASP.NET Required




Security Features




Management Tools







◆ Single Sign-on Support Example (Windows) ............................... 223◆ Single Sign-on Support Example (Domino) ................................. 249

Note: You can wait until all EMC SourceOne IIS sites (Web Services, Search and Mobile Services) are installed before configuring SSO.

Installing Native Archive Services softwareThis section describes how to install the Native Archive Services software on a host computer.




System requirements Hardware, operating system, network connectivity, and prerequisite software requirements are described in “Native Archive Services host computer requirements” on page 65.

Local disk space If the Native Archive server is to be used for indexing, you must have a minimum amount of free disk space available to support local index processing. Refer to the Native Archive disk configuration and storage information in “Example configurations” on page 29.






ProceduresTable 39 provides an overview of the procedures to install and configure EMC SourceOne Native Archive Services software on a host computer.

Copy the setup executable locallyTo copy the setup executable for the Native Archive Services software locally to the host computer:



3. Copy the ES1_ArchiveSetup.exe file to a temporary location on the Native Archive services host computer.

Install Native Archive Services software

IMPORTANT!For multiple Native Archive servers, Archive servers that share the same message center, archive, index, or unpack location must not share the same archive name because this action might result in data loss. However, archive servers can share folder names if they do not share the same storage location.

To install the Native Archive Services software:


Table 39 Procedures



Copies the installation executables locally to the Native Archive Services host computer.

2 “Install Native Archive Services software” on page 142

Installs the EMC SourceOne Native Archive Services software.

3 “Configure firewall rules (Windows Server 2008 only)” on page 148

Configures rules to allow EMC SourceOne services and system components to communicate with other services on the network.



2. Double-click the ES1_ArchiveSetup.exe file and click Run. The Welcome page displays. The installer:

• Validates the system configuration to ensure that prerequisite components are installed. Depending on your system configuration, the installer may automatically install one or more prerequisite components before displaying the Welcome page. Automatically installed components are listed in “Establishing system requirements” on page 58.

• Inspects whether the Microsoft Windows East Asian Language Pack is installed. This language pack is required to support full-text indexing of East Asian content.

If support is not installed, a warning message is displayed. For information on enabling the appropriate support before installing the Native Archive software, refer to “Regional and language options to support indexing” on page 82.

• Inspects the local drives to determine if adequate space (20 GB) is available to support indexing.

– If this Native Archive server is to be used for indexing, you must have a minimum amount of free disk space available. Refer to the Native Archive disk configuration and storage information in “Example configurations” on page 29. Click Yes to cancel the setup and allocate the local space.

– If this server is not used for indexing, click No to ignore the warning and continue with the installation.





a. The first destination determines where the primary Native Archive Services files are installed. Click Change to specify a different directory, or accept the default directory.

Note: Choose a drive other than the operating system drive.



6. Specify a destination folder (i.e., Index Work directory) used to perform Native Archive indexing.

• If this Native Archive server will not perform indexing, select a destination folder on a local drive (other than the operating system drive), ignore any warnings about insufficient disk space, and continue with the installation.

• If this Native Archive server will perform indexing, this location:

– Must be regarded as a local drive by the operating system. – Can not be the operating system drive (e.g., C:).– Can be on local disk or SAN storage, as long as it is

regarded as a local drive by the Native Archive server. For best performance, this should be on a dedicated physical disk.



– Requires a minimum of 20 GB of free disk space be available if this Native Archive Server is to perform indexing.

Note: You can change the index work directory at any time post-installation. Refer to “Native Archive Index Work directory considerations” on page 74 for details.



a. Type the Domain.

b. Type the Service Account and Service Account Password. This is the EMC SourceOne primary service account username and password.






9. Enter the database information:

a. Type the Native Archive Database name.

b. Type the Native Archive Database Server host name.



c. Click Next to display the In Place Migration page.



IMPORTANT!This option is only for customers who are creating a Native Archive instance that will exclusively support in place migration of legacy EmailXtender data to EMC SourceOne.

Note the following:

• The procedures in this guide assume you are installing a standard Native Archive instance for EMC SourceOne. Therefore, you should not select this option.

• If you are installing a Native Archive instance to support in place migration, refer to the EMC SourceOne In Place Migration Administration Guide for a version of this procedure that is focused on enabling in place migration support and other specific requirements.

10. Click Next to display the Ready to Install the Program page.

11. Click Install.


12. Click Finish.




Configure firewall rules (Windows Server 2008 only)If using Windows Server 2008, create inbound firewall rules as follows:

1. Create new firewall inbound rules to allow connections to the following EMC SourceOne services:

• EMC SourceOne Archive (ExAsArchive.exe)

• EMC SourceOne Query (ExAsQuery.exe)

Refer to the following Microsoft article for details on configuring firewall rules using Windows Firewall with Advanced Security in Windows Server 2008:

http://technet.microsoft.com/library/1378db20-de0d-476c-bc62-d6a0fda83984.aspx

2. Configure an inbound ICMP rule for ICMPv4.

Refer to the following Microsoft article:

http://technet.microsoft.com/en-us/library/cc972926(v=WS.10).aspx

3. Enable the firewall exception rule for Enable COM+ Network Access (DCOM-In).

Refer to the following Microsoft article:


http://technet.microsoft.com/library/1378db20-de0d-476c-bc62-d6a0fda83984.aspx



Maintaining the installation 149


Maintaining the installationThis section provides information on maintaining installation of the components described in this chapter.

UpgradeRefer to the product release notes for detailed instructions on upgrading EMC SourceOne product databases and components.

Remove a componentTo remove (uninstall) an EMC SourceOne product component that is installed on a Microsoft Windows system:

1. Using an account that is a member of the local Administrators group, access the Microsoft Windows Add or Remove Programs dialog box.

2. Select the appropriate component and click Remove.

3. Follow the prompts to remove the component.

Repair a componentRepairing a component can fix missing or corrupt files, shortcuts, and registry entries. Due to differences in the permissions model between Windows 2003 and Windows 2008, use the appropriate procedure for your environment as described in the following sections.

Windows 2003 systemsTo repair an EMC SourceOne product component that is installed on a Microsoft Windows 2003 system:


2. Select the appropriate component and click Change.

3. Follow the prompts to repair the component.



Windows 2008 systemsTo repair an EMC SourceOne product component that is installed on a Microsoft Windows 2008 system, do one of the following, depending on the account your are logged in as.

If you are logged in as the local system Administrator (highest permission level)Do the following:

1. Access the Microsoft Windows Program and Features dialog box.



If you are logged in as a member of the local Administrators groupDo the following:

1. Access the original setup executable for the EMC SourceOne component.

2. Run the executable.


Installing Email Management Support 151

6

This chapter describes how to install the required and optional components of EMC SourceOne Email Management. Each section in this chapter is presented in the order in which the components should be installed, as some installed components are dependent on previously installed components.


◆ Pre-installation checklist ................................................................. 152◆ Installing Email Management components for Exchange ......... 154◆ Installing Email Management components for Domino............ 172◆ Maintaining the installation ........................................................... 204

Installing EmailManagement Support


Installing Email Management Support

Pre-installation checklistBefore beginning the installation procedures detailed in this chapter, ensure that the items in the following checklist are completed.

Table 40 Pre-installation checklist


Review the product overview information

Review the product overview information and under-stand the features and options. See “Product over-view” on page 12 and the EMC SourceOne Administration Guide.

Understand the system ar-chitecture

Review the components which comprise EMC Source-One system. See “System architecture” on page 18 and “System components” on page 19.

Complete analysis activities Compile and analyze the organization’s requirements, metrics and processes. See “Pre-deployment plan-ning” on page 26.

Complete configuration planning activities

Size the environment and adjust variable components of the configuration to support it. See “System archi-tecture” on page 18 and “Example configurations” on page 29.

Configure accounts and per-missions

Establish the accounts and permissions required to support EMC SourceOne. See “Pre-installation” on page 41.

Establish required hardware and network infrastructure

Ensure that the appropriate hardware is available for installation and connected to the network. Hardware specifications, operating system, and network connec-tivity, and software prerequisites are detailed in “Pre-installation” on page 41.

Install common EMC SourceOne infrastruc-ture

Establish the EMC SourceOne common infrastructure as described in “Installing Common EMC SourceOne Components” on page 87.

Installation overview 153


Installation overviewTable 41 provides an overview of the EMC SourceOne Email Management installations presented in the order in which you should perform them.

Table 41 Installation procedure overview

Installation/Configuration Details Procedure

Extensions for OWA software

If applicable in your environment, install extensions on Microsoft Exchange to support Outlook Web Access 2003, 2007, 2010, and 2013.

• “Installing Extensions for OWA 2003 Support” on page 154

• “Installing Extensions for OWA 2007 or 2010 Support” on page 160

• “Installing Extensions for OWA 2013 Support” on page 166

Extensions for IBM Lotus Domino

If applicable in your environment, install and configure support for journaling and shortcutting on Lotus Domino servers.

“Domino Configuration and Administration” on page 207

ONM Viewer software Installs the ONM Viewer software on client computers. Enables users to open Lotus Notes messages from EMC SourceOne Search results.

“Installing the ONM Viewer software” on page 200



Installing Email Management components for ExchangeThe EMC SourceOne Extensions for Microsoft Outlook Web Access software is installed on a computer running Microsoft Exchange Server. A separate installation procedure is provided for each of the supported Microsoft Exchange versions.

Topics include:

◆ “Installing Extensions for OWA 2003 Support” on page 154◆ “Installing Extensions for OWA 2007 or 2010 Support” on

page 160◆ “Installing Extensions for OWA 2013 Support” on page 166

Installing Extensions for OWA 2003 SupportThis section describes how to install the EMC SourceOne Extensions for Microsoft Outlook Web Access software on a computer running Microsoft Exchange Server 2003.

Note: To install the Extensions for OWA 2007 or Extensions for OWA 2010 Support software on a computer running Microsoft Exchange Server 2007 or Exchange Server 2010, see “Installing Extensions for OWA 2007 or 2010 Support” on page 160.

PrerequisitesThis table provides an overview of the prerequisites you must complete before installing software.



System requirements This software is installed with Microsoft Exchange Server 2003 versions supported by EMC SourceOne. Refer to the EMC SourceOne Products Compatibility Guide for details.


permissions-related configuration is completed .• Database permissions are configured.

Installing Email Management components for Exchange 155


ConsiderationsReview the following considerations before installing the software.

Server typeYou install this software only on Microsoft Exchange Server 2003 back-end servers. You do not need to install this software on Microsoft Exchange Server 2003 front end servers.




Clustered Exchange considerationsIf installing the Extensions for OWA 2003 Support software in a clustered Exchange Server environment, you should plan appropriately for the installation of this software on each node and against each Exchange Virtual Server in the cluster group. Review these considerations:

◆ The node on which you are installing the software must have an active Exchange Virtual Server, or the installation cannot proceed.

EMC SourceOne software This installation requires that an EMC SourceOne Web Services computer exists and is accessible on the network. You will specify this host name during the EMC SourceOne Extensions for OWA 2003 Support software installation. If you have configured two or more Web Services computers in a load balancing cluster, you will instead specify the virtual host name during the EMC SourceOne Extensions for OWA 2003 Support software installation.





◆ Run the installation on the first active node in the cluster. When prompted for the Exchange server name, enter the name of the Exchange Virtual Server that is active on that node.

◆ Run the installation on the next active node in the cluster. When prompted for the Exchange server name, enter the name of the Exchange Virtual Server that is active on that node. Ensure that this Virtual Server is not the same Virtual Server you specified when installing on the previous node.

Note: Ultimately, you must specify each Exchange Virtual Server in your cluster configuration at least once during the installation of the OWA Extensions.

◆ Before running the installation on a passive node, perform a failover so that an Exchange Virtual Server is running on that node. When prompted by the install for the Exchange server name, enter the name of the Exchange Virtual Server that is active on that node. Ensure that this Virtual Server is not one of the Virtual Servers you specified when installing on previous nodes.

◆ Repeat this process until all Exchange Virtual Servers have been specified at least once during the installation of the Extensions for OWA 2003 Support software.

ProceduresTable 43 provides an overview of the procedures to install and configure EMC SourceOne for OWA 2003 Support software on a computer running Microsoft Exchange Server 2003.

Copy the setup executable locallyTo copy the setup executable for the Extensions for OWA 2003 software locally to the Microsoft Exchange Server 2003 host computer:

1. Navigate to the Setup\Windows directory on the EMC SourceOne Email Management Extensions for OWA software kit.

Table 43 Procedures



Copies the installation executables locally to the Exchange computer.

2 “Install Extensions for OWA 2003 software” on page 157

Installs the EMC SourceOne Extensions for OWA 2003 Support software.



2. Copy the ES1_OWA2003Setup.exe file to a temporary location on the Exchange computer.

Install Extensions for OWA 2003 softwareTo install the EMC SourceOne Extensions for OWA 2003 Support software:


2. Double-click the ES1_OWA2003Setup.exe file and click Run. The Welcome page displays.


4. Specify the destination directory. Click Change to specify a different directory, or accept the default directory.





a. Type the Domain.


Depending on the Active Directory accounts you created during the planning process, the service account used when installing the Extensions for OWA Support software can be one of the following:

– Primary service account– OWA service accountFor a more detailed discussion, see the following topics:



account must be a member of this Security Group.


e. Click Next to validate the credentials and display the Web Services page.






8. Click Next to display the Messaging Server page.



9. Enter the messaging server information:

a. Type the Server Name. If you are using:

– An Exchange Server 2003 cluster configuration, type the Exchange Virtual Server name. Ensure that you review the considerations for a cluster configuration provided in “Clustered Exchange considerations” on page 155.

– A single Exchange server configuration, type the host name of the current Exchange server.

b. Type the SMTP Domain. This information is used for registering OWA 2003 shortcut forms. The SMTP domain name configured for this Exchange server is displayed by default. Accept the default information or type the correct SMTP domain.

c. Type the Server Domain in which the Exchange server (or Exchange Virtual Server) is located.

IMPORTANT!The information on this page is not validated by the installation program. Ensure that you provide accurate information.


11. Click Install. Once the installation is complete, the InstallShield Wizard Completed Page displays.

12. Click Finish.

Installing Extensions for OWA 2007 or 2010 SupportThis section describes how to install the EMC SourceOne Extensions for Microsoft Outlook Web Access software on a computer running one of the following:

◆ Microsoft Exchange Server 2007

◆ Microsoft Exchange Server 2010




ConsiderationsReview these considerations before installing the software.

Server typeYou install this software only on Exchange Server 2007 or Exchange Server 2010 running the Client Access Server role.

You do not need to install this software on Exchange Server 2007 or Exchange Server 2010 running only the Mailbox Server role.

Exchange versionA separate EMC SourceOne Extensions for Microsoft Outlook Web Access installer is provided for Exchange Server 2007 and Exchange Server 2010. The installer interface for either version of Exchange is essentially the same, and therefore is documented in this single section (although screenshots are specific to Exchange Server 2007). Differences between Exchange versions are provided in the text where appropriate.



System requirements This software is installed with Microsoft Exchange Server 2007 or Exchange Server 2010 versions supported by EMC SourceOne. Refer to the EMC SourceOne Messaging Compatibility Guide for details.






This installation requires that an EMC SourceOne Web Services computer exists and is accessible on the network. You will specify this host name during the EMC SourceOne Extensions for OWA 2007 Support or EMC SourceOne Extensions for OWA 2010 Support software installation. If you have configured two or more Web Services computers in a load balancing cluster, you will instead specify the virtual host name during this installation. See “Configuring load balancing” on page 125 for more information.






Clustered Exchange considerationsIf installing the Extensions for OWA in a clustered Exchange Server environment, you should plan appropriately for the installation of this software on each node in the cluster group. The node on which you are installing the software must have Exchange services actively running, or the installation cannot proceed. Therefore, you should:

1. Complete the installation on the currently active node.

2. Failover the cluster to the passive node (activating that node) and install the software.

3. Continue this process until the software is installed on all nodes.

ProceduresTable 47 provides an overview of the procedures to install and configure EMC SourceOne for OWA 2007 Support or EMC SourceOne for OWA 2010 Support software on a computer running Microsoft Exchange Server 2007 or Exchange Server 2010.

Table 45 Procedures




2 “Install Extensions for OWA 2007 or 2010 software” on page 163

Installs one of the following (depending on Exchange Server version):• EMC SourceOne Extensions for

OWA 2007 Support software• EMC SourceOne Extensions for

OWA 2010 Support software



Copy the setup executable locallyTo copy the setup executable for the Extensions for OWA 2007 or Extensions for OWA 2010 software locally to the Exchange Server 2007 or Exchange Server 2010 host computer:


2. Copy the ExOWA2007Setup.exe or ExOWA2010Setup.exe file to a temporary location on the Exchange computer.

Install Extensions for OWA 2007 or 2010 softwareTo install the EMC SourceOne Extensions for OWA 2007 Support or Extensions for OWA 2010 Support software:


2. Double-click the appropriate setup executable file for your Exchange Server version (ExOwa2007Setup.exe or ExOWA2010Setup.exe)and click Run. The Welcome page displays.







a. Type the Domain.

Type the Service Account and Service Account Password.




on page 81b. Type the EMC SourceOne Security Group. The service


c. The Enable check box is already checked in the Service Logon Policy region. This setting is required to enable services to run without a logged in user.








10. Click Install


11. Click Finish.



Installing Extensions for OWA 2013 SupportThis section describes how to install the EMC SourceOne Extensions for Microsoft Outlook Web Access software on a computer running Microsoft Exchange Server 2013

PrerequisitesThis table provides an overview of the prerequisites you must complete before installing software.

ConsiderationsReview these considerations before installing the software.

Server typeYou install this software only on Exchange Server 2013 running the Client Access Server role.

You do not need to install this software on Exchange Server 2013 running only the Mailbox Server role.

Exchange versionA separate EMC SourceOne Extensions for Microsoft Outlook Web Access installer is provided for Exchange Server 2013.



System requirements This software is installed with Microsoft Exchange Server 2013 versions supported by EMC SourceOne. Refer to the EMC SourceOne Messaging Compatibility Guide for details.






This installation requires that an EMC SourceOne Web Services computer exists and is accessible on the network. You will specify this host name during the EMC SourceOne Extensions for OWA 2013 Support software installation. If you have configured two or more Web Services computers in a load balancing cluster, you will instead specify the virtual host name during this installation. See “Configuring load balancing” on page 125 for more information.






Clustered Exchange considerationsIf installing the Extensions for OWA in a clustered Exchange Server environment, you should plan appropriately for the installation of this software on each node in the cluster group. The node on which you are installing the software must have Exchange services actively running, or the installation cannot proceed.

When installing the software in a cluster environment:

1. Complete the installation on the currently active node.

2. Failover the cluster to the passive node (activating that node) and install the software.

3. Continue this process until the software is installed on all nodes.

ProceduresThis table provides an overview of the procedures to install and configure EMC SourceOne for OWA 2013 Support software on a computer running Microsoft Exchange Server 2013.

Table 47 Procedures




2 “Install Extensions for OWA 2013 software” on page 168

Installs the EMC SourceOne Extensions for OWA 2013 Support software



Copy the setup executable locallyTo copy the setup executable for the Extensions for OWA 2013 software locally to the Exchange Server 2013 host computer:


2. Copy the ExOWA2013Setup.exe file to a temporary location on the Exchange computer.

Install Extensions for OWA 2013 softwareTo install the EMC SourceOne Extensions for OWA 2013 Support software:


2. Double-click the appropriate setup executable file for your Exchange Server version (ExOwa2013Setup.exe and click Run. The Welcome page displays.







a. Type the Domain.







d. The Enable check box is already checked in the Service Logon Policy region. This setting is required to enable services to run without a logged in user.








10. Click Install. Once the installation is complete, the InstallShield Wizard Completed Page displays.

11. Click Finish.

12. On one Microsoft Exchange 2013 server:

a. Login as Administrator.

b. Open the following files for editing:

C:\Program Files\EMC SourceOne\ES1OWA2013\ES1OWA2013Web\ES1OWA2013.xml

c. Replace the ~remoteAppUrl with the External Exchange OWA URL.

For example:



https://ExternalOWAURL.YourCompany.com/owa/ES1OWA2013Web/Restore.aspx

13. To enable the OWA2013 Mail Application for all users inside the organization, go to:

All Programs > Microsoft Exchange Server 2013 > Exchange Management Shell.

14. Run the following scripts:

$Data = Get-Content -Path "C:\Program Files\EMC SourceOne\ES1OWA2013\ES1OWA2013Web\ES1OWA2013.xml" -Encoding Byte -ReadCount 0

New-App -FileData $Data -OrganizationApp -ProvidedTo Everyone -Enabled:$true -DefaultStateForUser Enabled

Note: The Mail App will fail to launch the first time. This is a known issue of the Microsoft Mail App. For more information about the Add Mail App, refer to the Microsoft documentation site.

Uninstall the OWA 2013 Mail ApplicationTo uninstall the OWA2013 Mail Application:

1. Login to the Exchange admin center.

2. Click organization from the menu on the left.

3. Click apps.

4. Select View original item from the provider EMC.

5. Click Disable from the menu on the right.

6. Click the Delete icon. A message displays confirming that you want to delete the Mail App.

7. Click Yes.



Installing Email Management components for DominoThis section describes how to install the following software to support an IBM Lotus Domino environment:

◆ The EMC SourceOne Extensions for IBM Lotus Domino software is installed on IBM Lotus Domino servers to provide support for journaling and shortcutting on IBM Lotus Domino servers running on Microsoft Windows, Sun Solaris, Red Hat Linux, IBM AIX, or IBM i operating systems.

◆ The ONM Viewer software provides end users on client computers the ability to view Lotus Notes messages from EMC SourceOne Search results in Lotus Notes.

Topics include:

◆ IBM Lotus Domino support overview.......................................... 172◆ Installing Extensions for IBM Lotus Domino .............................. 176◆ Installing the ONM Viewer software............................................ 200

IBM Lotus Domino support overviewEMC SourceOne Email Management provides real-time archiving (also referred to as journaling), shortcutting, and historical archiving support for IBM Lotus Domino mail servers. This section includes the following topics:

◆ Journaling.......................................................................................... 173◆ Shortcutting ...................................................................................... 174◆ Historical archiving ......................................................................... 174◆ Supported Domino platforms........................................................ 174

Installing Email Management components for Domino 173


JournalingJournaling copies messages processed by the Domino server to a designated database from which EMC SourceOne can then archive them.

To support journaling, you have the following options:

◆ Install EMC SourceOne journaling extensions software on your Domino servers. The extensions automatically create and maintain journaling databases from which you can archive messages using the EMC SourceOne console.

◆ Utilize a native Domino journaling database. You can then target journaling activities against the native Domino journaling database using the EMC SourceOne console.

Using EMC SourceOne journalingYou must install the EMC SourceOne journaling extensions to support this journaling option. During message journaling, the EMC SourceOne Journaling Extension Manager copies each message on the Domino server to a journaling database. A journaling database (ExJournal.nsf) is created for the Domino mail.box database on the Domino server. If there is more than one mail.box database (mail2.box, mail3.box etc.), the Domino Extensions installer creates corresponding journaling databases using the same numbering scheme (ExJournal1.nsf, ExJournal2.nsf, etc).

IMPORTANT!Before installing, ensure that you review the considerations for using EMC SourceOne journaling. For details, refer to “EMC SourceOne journaling considerations” on page 212.

Using Native Domino journalingNative Domino mail journaling enables administrators to capture a copy of specified messages that the Router processes by the Domino system. Journaling can capture all messages handled by the Router or only messages that meet specific defined criteria. When mail journaling is enabled, Domino examines messages as they pass through mail.box and saves copies of selected messages to a Domino Mail Journaling database (e.g., mailjrn.nsf).



IMPORTANT!Before installing, ensure that you review the considerations for using native Domino journaling. Included in this information are important settings required for EMC SourceOne to function against a native Domino journaling database. For details, refer to “Native Domino journaling considerations” on page 214.

ShortcuttingShortcutting replaces email messages archived by EMC SourceOne with smaller files called shortcuts on the Domino server. Shortcuts are pointers to email messages archived in the EMC SourceOne repository. Mail users and mobile users can double-click the shortcut to retrieve the full archived message.

To support email shortcutting, you install the optional Shortcut Extension Manager on the Domino server. The Shortcut Extension Manager allows mail users to view the original message in the following ways:

◆ In the preview pane

◆ Opening the full message (double-click)

Shortcut messages are retrieved during replication. The mobile user experience is unchanged.

Historical archivingHistorical archiving support is inherently provided through permissions granted to EMC SourceOne to mail databases on your Domino servers. You do not need to install any EMC SourceOne software to support historical archiving.

Supported Domino platformsYou can archive mail and support shortcutting on Lotus Domino servers running on the Microsoft Windows, Sun Solaris, Red Hat Linux, IBM AIX, or IBM i operating systems.

For specific supported platform information, see the EMC SourceOne Products Compatibility Guide.



Configure administrator access to journaling databasesConfigure access which enables EMC SourceOne administrators to configure Domino-related activities.

Before installing journaling functionality, configure a group in Domino which corresponds to the EMC SourceOne Admins Group created in Active Directory which contains users of the EMC SourceOne console (see “Creating accounts in Active Directory” on page 43 for details on the Admins Group). You then associate the Domino group with each journal database used by EMC SourceOne.

ProcedureTo configure administrator access to the journaling databases:

1. Create a group using Domino Administrator. Use these guidelines:

• Group name - Use a contextual name such as SourceOne Admins.

• Members - Add the same users in the Active Directory Admins Group to the Domino group.

2. Run the Notes client application using the EMC SourceOne Notes User account (typically on the Master Services computer or a Worker Services computer).

3. Configure the access control for each journal database by adding the Domino group with Reader access.

Maintaining the configurationEnsure the following:

◆ As the EMC SourceOne Admins Group in Active Directory changes, ensure that users are added and deleted in the corresponding Domino group.

◆ As mail.box databases are created (and therefore corresponding journal mailboxes), ensure that you repeat this procedure to configure administrative access to the new journaling databases.



Installing Extensions for IBM Lotus DominoThe procedures for installing and configuring the Domino extensions software are different depending on the operating system:

◆ Installing Extensions for Domino on Microsoft Windows ........ 176◆ Installing Extensions for Domino on Solaris, Linux, or AIX ..... 183◆ Installing Extensions for Domino on IBM i.................................. 191

Installing Extensions for Domino on Microsoft WindowsThis section describes how to install extensions for Lotus Domino servers running on Microsoft Windows to support journaling and shortcutting.

IMPORTANT!Before installing EMC SourceOne Extensions for Domino, ensure that you have installed all of the common components as described in “Installing Common EMC SourceOne Components” on page 87.

The EMC SourceOne Extensions for Domino install program allows you install support for journaling by installing the Journaling Extension Manager (optional) and shortcutting by installing the Shortcut Extension Manager.

You optionally can utilize native Domino journaling or EMC SourceOne journaling. Ensure that you review the considerations for each type of journaling support as described in “Journaling” on page 173, as this information may impact your choices when installing the software.

You must run the EMC SourceOne Extensions for Domino on each Domino server from which you want to journal or shortcut messages.

This section includes the following topics:

◆ Copy setup executable to the host computer............................... 177◆ Running the Domino Extensions installer ................................... 177◆ Installation results............................................................................ 181◆ Consideration for 64-bit OS............................................................ 182◆ Configuration and administration ................................................ 182



Copy setup executable to the host computerTo copy the setup executable for the EMC SourceOne Extensions for Domino software locally to the Domino host computer:

1. Navigate to the Setup\Windows directory on the EMC SourceOne Email Management Extensions for IBM Lotus Domino software kit.

2. If you are installing on a:

• 32-bit system – Copy the ES1_DominoExtSetup.exe file to a temporary location on the Domino host computer.

• 64-bit system – Copy the ES1_DominoExtSetupx64.exe file to a temporary location on the Domino host computer.

Running the Domino Extensions installerTo run the EMC SourceOne Extensions for Domino install program:

1. Shut down the Lotus Domino Server application by typing q and pressing Enter in the console window.

2. Double-click the setup file. The Welcome page displays.

3. Click Next to display the Custom Setup page.



4. Enter the custom setup information:

a. Select Shortcut Extensions to install EMC SourceOne shortcutting functionality.

b. Select Journaling Extensions to install journaling functionality. You have the following choices:

– SourceOne Journaling - Use EMC SourceOne journaling functionality

– Native Journaling - Use native Domino journaling functionality and install an agent used to automate the clean up of the Bad Documents Folder.

– De-select the Journaling Extensions check box - No additional journaling software is installed. Choose this option if you want to utilize native Domino journaling, but do not want to install the cleanup agent.

Note: Refer to “Journaling” on page 173 for information about supported types of journaling and specific considerations for each.

c. Click Next to display the Notes Folders page.



5. Validate that the Notes folders that are displayed are accurate and click Next to display the Product Servers page.

6. Type the name of Worker Services host computer on which the EMC SourceOne Web Services software is installed.

• If using load balancing such as Microsoft NLBS, enter the virtual host name. See “Configuring load balancing” on page 125 for more information

• 32-bit systems only – If using SSL, select the Use SSL (Secure Sockets Layer)



7. Click Next to display the Username page.

8. Type the fully-qualified hierarchical name of the Lotus Notes user configured during the planning process (see “IBM Lotus Domino permissions” on page 57).

9. Click Next to validate the account and display the Choose Temporary Folder page.



10. Select a temporary journaling folder and click Next to display the Ready to Install the Program page.

11. Click Install.


12. Click Finish.

13. Start the Lotus Domino Server application.

Installation resultsThe results depend on the type of journaling support you selected during the installation.

EMC SourceOne journaling — If you selected EMC SourceOne journaling, the following occurs:

◆ Installs ExNotesJournal.dll.

◆ Installs the template upon which ExJournal.nsf databases are based. The ExJournal.nsf database(s) are created the first time the Domino server is run after the installation.

Two templates are provided. One template enables transactional logging by default and one does not. You can configure which one to use by editing the notes.ini file. See “Journaling templates” on page 212 for details.

◆ Configures the journaling database and makes necessary changes to the Notes.ini file.

◆ Installs and configures the ExProcBadDocs agent. This cleanup agent processes corrupt and $Readers field messages by placing them in an envelope message that can be archived.

◆ Adds the ExProcBadDocs agent to the ServerTasks= line in the Notes.ini file.

◆ Adds the polling interval (EmailXtenderBadDocsInt=60) for the ExProcBadDocs agent to the Notes.ini file.

Native Domino journaling — If you selected native Domino journaling, the following occurs:

◆ Installs and configures the ExProcBadDocs agent. This agent processes corrupt and $Readers field messages by placing them in an envelope message that can be archived.



◆ Adds the ExProcBadDocs agent to the ServerTasks= line in the Notes.ini file.

◆ Adds the polling interval (EmailXtenderBadDocsInt=60) for the ExProcBadDocs agent to the Notes.ini file.

Shortcutting — For shortcutting, the EMC SourceOne Extensions for Domino installer:

◆ Creates the exshortcut.nsf database.

◆ Creates a user called ES1 Shortcut which is used to restore shortcuts.

Note: In a clustered Domino environment (in which you run the installation on each computer), a duplicate ES1 Shortcut user is created which may cause shortcut problems. Manually delete one of the users.

◆ Updates the Comments field on the Miscellaneous tab for the ES1 Shortcut user to include the name of the Web Services host computer (or virtual host name if using load balancing) that you specified when you installed Domino Extensions.

Consideration for 64-bit OSIf running 32-bit Domino on a 64-bit Microsoft Windows operating system, and then installing the 32-bit version of the EMC SourceOne Extensions for IBM Lotus Domino, an error such as the following occurs:

Error attempting to load or run ExProcBadDocsx64.EXE: Unable to locate program

Edit the notes.ini file to update references to two 64-bit entries:

1. Open the notes.ini file.

2. Locate the ServerTasks line and locate ExProcBadDocsx64 and change it to ExProcBadDocs, removing the x64 from the entry.

3. Locate the EXTMGR_Addins line and locate the ExNotesJournalx64 entry and change it to ExNotesJournal, removing the x64 from the entry.

4. Restart your Domino server.

Configuration and administrationReview the information provided in the “Domino Configuration and Administration” on page 207 and perform any tasks required for your environment.



Installing Extensions for Domino on Solaris, Linux, or AIXThis section describes how to configure extensions to Domino servers running on Sun Solaris, Red Hat Linux, or IBM AIX to support journaling and shortcutting.

◆ For journaling support, you are prompted during the installation to:

• Install the Journaling Extension Manager which supports journaling on each Domino server.

• Use native Domino journaling.

◆ For shortcutting support, you must install the Shortcut Extension Manager.


◆ Running the journaling script on Solaris, Linux, or AIX ............ 183◆ Installation results ............................................................................ 185◆ Running the shortcutting script on Solaris, Linux, and AIX...... 187◆ Installation results ............................................................................ 190◆ Configuration and administration ................................................. 190

Running the journaling script on Solaris, Linux, or AIXTo run the Domino journaling script:

1. Log in as root.

2. Copy the exnotesjournal.tgz file from the Setup/Unix/Notes_Extensions/Journal directory in the EMC SourceOne Email Management Extensions for IBM Lotus Domino installation kit to a local directory.

3. Set the current default directory to the directory to which you are going to extract the installation files.

4. Extract the installation files from the exnotesjournal.tgz file, which was compressed using the tar and gzip utilities, into the current default directory using the following command:

# gunzip -c exnotesjournal.tgz | tar xvf -

The installation kit files are created in the current default directory, and in the newly created Aix, or Linux, or Solaris subdirectory.

5. Execute the install script, install.sh, using the following command:

./install.sh



6. When prompted, type the directory in which Domino is installed. In the following example, the Domino install directory is /opt/lotus.

Specify the Domino Install directory:/opt/lotusInstalling Notes Journal Extension Manager in/opt/lotus/notes/latest/linux

7. When prompted, type the Notes data directory so that the install script can update the Notes.ini file. In the following example, the Notes data directory is /local/notesdata.

Specify the Notes data directory:/local/notesdataUpdating notes/local/notesdata/notes.ini.

8. When prompted, indicate whether you want to use native Domino journaling or EMC SourceOne journaling.

Do you want to install IBM Lotus Domino Native Journaling or EMC SourceOne Domino Journaling Extensions? (N/E)

Type N for native Domino journaling or E for EMC SourceOne journaling.

9. When prompted, type the fully-qualified hierarchical name of the Lotus Notes administrative user configured during the planning process (see “IBM Lotus Domino permissions” on page 57) and the Domino domain for the user. Enter them as NotesUser/NotesDomain, where NotesUser is the canonical name of the Notes user and NotesDomain is the Domino domain for that user. In the following example, the username is NotesAdmin and the Domino domain is CompanyDomain.

Specify the EMC SourceOne user name:[UserName]/[NotesDomain]NotesAdmin/CompanyDomain

10. When prompted, enter a directory where attachments can be temporarily saved. You can enter either an existing directory or a new directory that the install script will create.



In the following example, /local/notesdata/extemp is an existing directory that will be used as the temporary directory for attachments and other EMC SourceOne temporary data.

Specify path of directory where attachments can be saved temporarily:/local/notesdata/extempExisting directory /local/notesdata/extemp

EmailXtenderTempPath=/local/notesdata/extempEmailXtenderUserName=NotesAdmin/CompanyDomain

11. After you enter the temporary directory for attachments, the installation completes and prompts you to stop and then restart the Domino server.

Installation complete.Stop the Lotus Domino server and restart it.

Installation resultsThe results depend on the type of journaling support you select when running the installation script.

EMC SourceOne journaling — If you selected EMC SourceOne journaling when running the journaling script on a Solaris, Linux, or AIX server completes the following:

◆ Installs libexnotesjournal.so in the program folder of the Domino server. The libexnotesjournal.so monitors incoming and outgoing mail and forwards a copy of all mail to the ExJournal.nsf database.

◆ Installs templates upon which ExJournal.nsf databases are based. The ExJournal.nsf database(s) are created the first time the Domino server is run after the installation.

◆ There are two templates provided - one which enables transactional logging by default and one that does not. You can configure which one to use by editing the notes.ini file. See “Journaling templates” on page 212 for details.

Note: When you use antivirus software on the mail server, the antivirus software may remove infected messages in the journaling databases (ExJournal.nsf databases) for that mail server. If infected messages are removed from the journaling database, EMC SourceOne does not archive or index the messages. If you have antivirus software that is causing issues with the EMC SourceOne software, contact EMC Customer Support.



◆ Installs the ExProcBadDocs cleanup agent in the Lotus Domino binary directory and places a template in the Lotus Domino data directory (exbaddocs.ntf)

◆ Installs $Reader field support, which allows EMC SourceOne to access and archive all documents in a journal database, regardless of the value of the $Reader field.

◆ As part of the $Reader field support, ExProcBadDocs cleanup agent creates a EMC SourceOne compound document in the journal database that contains the documents found in the ExBadDocs folder, and then deletes those documents from the journal database. The ExProcBadDocs cleanup agent runs at a default interval of 60 minutes, which you can modify by editing the Notes.ini file for the Domino server.

◆ Makes the following changes to the Notes.ini file:

Table 48 Journaling script changes to Notes.ini File - EMC SourceOne journaling

LINE Change or Addition Description

EXTMGR_ADDINS=libexnotesjournal.so

Supports the EMC SourceOne Notes Journaling Extension Utility.

EmailXtenderUserName= NotesAdministrator/NotesDomain

The canonical name of the Notes user you created for the EMC SourceOne and the Domino domain for that user.

EmailXtenderBadDocsInt=60 The default interval in minutes at which the $Reader field support agent creates a compound document in the journal database that contains documents found in the ExBadDocs folder. (You can modify this value if necessary.)

ServerTasks=exprocbaddocs Adds exprocbaddocs as a server task that is needed for $Reader field support.

EmailXtenderTempPath=temppath Used for $Reader field support.



Native Domino journaling — If you selected native Domino journaling when running the journaling script on a Solaris, Linux, or AIX server completes the following:

◆ Installs the ExProcBadDocs cleanup agent in the Lotus Domino binary directory and places a template in the Lotus Domino data directory (exbaddocs.ntf).

◆ Makes the following changes to the Notes.ini file:

Running the shortcutting script on Solaris, Linux, and AIXIf you plan to use EMC SourceOne to create shortcuts of messages on the Domino server, run the Domino shortcutting script to install the Shortcut Extension Manager. The Shortcut Extension Manager allows mail users to view the original message either in the preview pane or when they double-click the shortcut to open the message. It also allows mobile users to view shortcut messages.

Note: Shortcuts are replicated between server-based mail database replicas, but full messages are replicated to local mail database replicas. The shortcut messages reside on the Domino server, and full messages are in the local mail database for offline use.

You must run the shortcutting script on each Domino server from which you want to shortcut messages.

To run the shortcutting script on Solaris, Linux, or AIX:

1. Log in as root.

2. Copy the exnotesshortcut.tgz file from the Setup/Unix/Notes_Extensions/Shortcut directory on the EMC SourceOne Email Management Extensions for IBM Lotus Domino software kit to a local directory.

Table 49 Journaling script changes to Notes.ini File - native Domino journaling

LINE Change or Addition Description

EmailXtenderBadDocsInt=60 The default interval in minutes at which the $Reader field support agent creates a compound document in the journal database that contains documents found in the ExBadDocs folder. (You can modify this value if necessary).

ServerTasks=exprocbaddocs Adds exprocbaddocs as a server task that is needed for $Reader field support.

EmailXtenderTempPath=temppath Used for $Reader field support.



3. Set the current default directory to the directory where you are going to extract the installation files.

4. Extract the installation files from the exshortcut.tgz file, which was compressed using the tar and gzip utilities, into the current default directory using the following command:

# gunzip -c exnotesshortcut.tgz | tar xvf -

The installation kit files are created in the current default directory, and in the newly created Aix, or Linux, or Solaris subdirectories.

5. Execute the install script, install.sh, using the following command:

./install.sh

6. When prompted, enter the directory in which Domino is installed. (The Shortcut Extension Manager will be installed in this location.) In the following example, the Domino install directory is /opt/lotus:

Specify the Domino Install directory:/opt/lotusInstalling Notes Shortcut Extension Manager in/opt/lotus/notes/latest/linux

The install script automatically identifies the correct operating system and installs the Notes Shortcut Extension Manager accordingly.

7. When prompted, enter the Notes data directory so that the install script can update the Notes.ini file. In the following example, the Notes data directory is /local/notesdata.

Specify the Notes data directory:/local/notesdataUpdating notes/local/notesdata/notes.ini.

8. When prompted, type the fully-qualified hierarchical name of the Lotus Notes administrative user configured during the planning process (see “IBM Lotus Domino permissions” on page 57) and the Domino domain for the user. Enter them as NotesAdmin/CompanyDomain, where NotesAdmin is the canonical name of the Notes user and CompanyDomain is the Domino domain for that user. In the following example, the username is NotesAdmin and the NotesDomain is CompanyDomain.



Specify the EmailXtender user name:[EmailXtenderUserName]/[NotesDomain]NotesAdmin/CompanyDomain

9. When prompted, enter a directory where attachments and other EMC SourceOne temporary data can be temporarily saved. You can enter either an existing directory or a new directory that the install script will create. In the following example, /local/notesdata/extemp is an existing directory that will be used as the temporary attachments directory.

Specify path of directory where attachments can be saved temporarily:/local/notesdata/extempExisting directory /local/notesdata/extemp

EmailXtenderTempPath=/local/notesdata/extempEmailXtenderUserName=NotesAdmin/CompanyDomain

10. After you enter the temporary directory for attachments, the installation completes and prompts you to stop and then restart the Domino server.

Installation complete.Stop the Lotus Domino server and restart it.

11. Add a person record called ES1 Shortcut to the public name and address book.

a. Set the User Name field to ES1 Shortcut.

b. Set the First Name field to ES1.

c. Set the Last Name field to Shortcut.

d. Set the Full Name field to ES1 Shortcut.

e. Edit the Comments field on the Miscellaneous tab to include the EMC SourceOne Worker Services host computer on which EMC SourceOne Web Services is installed:

– If you are using a single Web Services host computer, enter the host name of that computer.

– If you are using a load balancing solution which configures a virtual host name pointing to multiple Web Services computers (see “Configuring load balancing” on page 125), enter the virtual host name.



– If you have installed two or more Web Services host computers but you are not using load balancing, you can enter multiple host names by placing each name on a new line using the ENTER key.

Installation resultsWhen you install the Shortcut Extension Manager on a Solaris, Linux, or AIX server, the install script makes the following changes to the Notes.ini file.

Configuration and administrationReview the information provided in “Domino Configuration and Administration” on page 207 and perform any tasks required for your environment.

Table 50 Shortcut Extension Manager changes to the Notes.ini file

Notes.ini Change or Addition Description

EmailXtenderShortcutDB=ExShortcut

Sets the name of the shortcut database to ExShortcut.nsf.

EXTMGR_ADDINS=libexnotesshortcutext.so

Creates the Shortcut Extension Manager, ExNotesShortcutExt.

ServerTasks=ExNotesShortcutCache Adds ExNotesShortcutCache as a server task and allows EMC SourceOne to manage the shortcut cache.

EmailXtenderShortcutCacheInt=15 Sets how often, in minutes, the shortcut cache should be cleared. The default value is 20, indicating the cache should be cleared every 20 minutes.



Installing Extensions for Domino on IBM iThis section describes how to install and configure extensions to Lotus Domino servers running on IBM i to support journaling and shortcutting.

◆ For journaling support, you have the following options:

• You can install the Journaling Extension Manager which supports journaling on each Domino server.

• You can use native Domino journaling, but choose to install the ExProcBadDocs cleanup agent.

◆ For shortcutting support, you can install the Shortcut Extension Manager.

◆ You can install $Reader field support to allow EMC SourceOne to access and archive all documents in a journal database, regardless of the value of the $Reader field.


◆ Installing journaling support on IBM i.......................................... 191◆ Installing Notes $Reader field support on IBM i ......................... 193◆ Loading and unloading $Reader support on IBM i..................... 196◆ Installing shortcutting support on IBM i....................................... 196◆ Configuration and administration ................................................. 200

Installing journaling support on IBM iTo install the journaling support for EMC SourceOne or native Domino journaling on an IBM i server:

1. On the IBM i computer, do one of the following:

• If this is the first time this software has been installed on this computer, enter the following command to create the save file:

CRTSAVF QGPL/LEGATOJN

• If this software has been installed on this computer before, enter the following command to clear any existing save file named legatojn.savf:

CLRSAVF QGPL/LEGATOJN

2. Copy the installation kit, legatojn.savf, from the Setup\i5_OS\Notes_Extensions\Journal directory on the EMC SourceOne Email Management Extensions for IBM Lotus Domino software kit to a computer running Windows.

3. From the computer running Windows, set the default directory to the directory into which you copied legatojn.savf.



4. Copy the installation kit from the Windows computer to the IBM i computer using the FTP utility. You should use binary mode for the file copy. For example, the following commands would be used to log on to the IBM i computer and copy the file to that computer. In the following example, the IBM i computer is named tbone.

>ftp ftp.tboneConnected to tbone.220 tbone FTP server (Version wu-2.6.2(1) Thu Feb 2117:02:27 PST 2010) ready.User (tbone:(none)): user1Password:230 User ftp logged in. Access restrictions apply.ftp> binary200 Type set to I.ftp> put legatojn.savf QGPL/LEGATOJN

5. Change the default directory to the Domino data directory, and then use the FTP put command to place files in the Domino data directory, depending on the type of journaling you intend to use:

• If you want to use EMC SourceOne journaling, copy the exjournal.ntf and exbaddoc.ntf files to the Domino data directory. In the following example, /domino/boston/data is the Domino data directory on the IBM i computer.

ftp> cd /domino/boston/data250 CWD command successful.ftp> put exjournal.ntfftp> put exbaddoc.ntfftp> quit>

• If you want to use native Domino journaling, but want to take advantage of the ExProcBadDocs cleanup agent, copy the exbaddoc.ntf files to the Domino data directory. In the following example, /domino/boston/data is the Domino data directory on the IBM i computer.

ftp> cd /domino/boston/data250 CWD command successful.ftp> put exbaddoc.ntfftp> quit

6. If you are installing on a Domino partitioned server, you must copy the appropriate .ntf files to each Domino server partition on which you want to install the Journaling Extension Manager.



7. Οn the IBM i computer, enter the following command:

RSTLIB SAVLIB(EXJOURNAL) DEV(*SAVF) SAVF(QGPL/LEGATOJN)

8. Create a symbolic link using the ADDLNK command.

Note: The ADDLNK command creates a new symbolic link named LIBEXADD.PGM in the /QIBM/UserData/LOTUS/NOTES directory. This symbolic link resides in the Integrated File System (IFS) and points to the LIBEXADD service program in the QSYS (legacy) file system.

Note: If you previously installed EMC SourceOne Extensions for Domino (or EmailXtender Notes Listener support) on this computer, the symbolic link already exists. Skip to Step 9.

On the IBM i computer, enter the following commands:

ADDLNK OBJ(‘/QSYS.LIB/EXJOURNAL.LIB/LIBEXADD.PGM’)NEWLNK(‘/QIBM/USERDATA/LOTUS/NOTES/LIBEXADD.PGM’)

9. Stop the Domino server (or servers, if you are installing on a Domino partitioned server).

10. Add the following lines to the Domino server’s Notes.ini file:

EXTMGR_ADDINS=EXADDEmailXtenderUserName=ExUser/NotesDomain

where ExUser is the canonical name of the Lotus Notes administrative user configured during the planning process (see “IBM Lotus Domino permissions” on page 57) and NotesDomain is the Notes domain for that user.

Note: If you are installing the Journaling Extension Manager on a Domino partitioned server, you must modify the Notes.ini file for each Domino server partition on which you want to install the Journaling Extension Manager.

11. Restart the Domino server (or servers, if you are installing on a Domino partitioned server).

Installing Notes $Reader field support on IBM iAfter you restart the Domino server, install $Reader field support. When Domino is running on an IBM i server, you must install $Reader field support, which allows EMC SourceOne to access and archive all documents in a journal database, regardless of the value of the $Reader field.

As part of the $Reader support, the ExProcBadDocs cleanup agent creates a EMC SourceOne compound document in the journal



database that contains the documents found in the ExBadDocs folder, and then deletes those documents from the journal database. You can set the default interval at which ExProcBadDocs cleanup agent runs when you edit the Notes.ini file for the Domino server.

You must install $Reader field support on each Domino server from which you want to archive messages.

To install $Reader field support for Lotus Domino on an IBM i server:

1. On the IBM i computer, enter the following command to clear any existing file named legatobd.savf.

CLRSAVF QGPL/LEGATOBD

2. Copy the installation kit, legatobd.savf from the Setup\i5_OS\Notes_Extensions\Journal directory on the EMC SourceOne installation CD to a computer running Windows.

3. From the Windows computer, set the default directory to the directory into which you copied legatobd.savf.

4. Copy the installation kit from the Windows computer to the IBM i computer using the FTP utility. You should use binary mode for the file copy.

For example, the following commands would be used to log on to the IBM i computer and copy the file to that computer.

In the following example, the IBM i computer is named tbone.



>ftp ftp.tboneConnected to tbone.220 tbone FTP server (Version wu-2.6.2(1) Thu Feb 2117:02:27 PST 2010) ready.User (tbone:(none)): user1Password:230 User ftp logged in. Access restrictions apply.ftp> binary200 Type set to I.ftp> put legatobd.savf QGPL/LEGATOBDftp>quit

5. Οn the IBM i computer, enter the following command:

RSTLIB SAVLIB(EXBADDOC) DEV(*SAVF) SAVF(QGPL/LEGATOBD)

6. Create a symbolic link using the ADDLNK command.

Note: The ADDLNK command creates a new symbolic link named LIBEXBD.PGM in the /QIBM/UserData/LOTUS/NOTES directory.

Note: If you previously installed EMC SourceOne Extensions for Domino (or EmailXtender $Reader support) on this computer, the symbolic link already exists. Skip to Step 7.

On the IBM i computer, enter the following commands:

ADDLNK OBJ(‘/QSYS.LIB/EXBADDOC.LIB/LIBEXBD.PGM’)NEWLNK(‘/QIBM/USERDATA/LOTUS/NOTES/LIBEXBD.PGM’)

7. On the IBM i computer, create a temporary directory, such as /temp.


ServerTasks=libexbdEmailXtenderTempPath=tempdirEmailXtenderBadDocsInt=60

where tempdir is the name of the temporary directory you created in step 7 and 60 is the interval in minutes at which the $Reader field support agent creates a compound document in the journal database that contains documents found in the ExBadDocs folder.

You can append libexbd to the existing ServerTasks entry rather than creating a new entry.



If you are installing $Reader Journaling support on a Domino partitioned server, you must modify the Notes.ini file for each Domino server partition on which you want to install $Reader Journaling support.

9. Stop and then restart the Domino server on the IBM i computer (or servers, if you are installing on a Domino partitioned server).

Loading and unloading $Reader support on IBM iOnce you install $Reader field support, you can load or unload it.

IMPORTANT!If you loaded this support by adding it to the serverTasks line in the Notes.ini file, do not load it using the Domino LOAD command from the console unless you have first unloaded it using the TELL command as described below.

To load LIBEXBD, enter the following command in the Domino server console:

LOAD LIBEXBD

To unload and stop LIBEXBD, enter the following command in the Domino server console:

TELL LIBEXBD QUIT

Installing shortcutting support on IBM iIf you plan to use EMC SourceOne to create shortcuts of messages on the Domino server, you must install the Shortcut Extension Manager.

The Shortcut Extension Manager allows mail users to view the original message either in the preview pane or when they double-click the shortcut to open the message. It also allows mobile users to view shortcut messages. Shortcuts are replicated between server-based mail database replicas, but full messages are replicated to local mail database replicas. The shortcut messages reside on the Domino server, and full messages are in the local mail database for offline use.

You must install the Shortcut Extension Manager on each Domino server from which you want to shortcut messages.



To install shortcutting support on IBM i:

1. On the IBM i computer, enter the following to clear any existing files named legatosh.savf or legatoca.savf:

CLRSAVF QGPL/LEGATOSHCLRSAVF QGPL/LEGATOCA

2. Copy the installation kit files, legatosh.savf,legatoca.savf and exshortcut.ntf, from the Setup\i5_OS\Notes_Extensions\Shortcut directory on the EMC SourceOne installation CD to a computer running Windows.

3. From the Windows computer, set the default directory to the directory into which you copied legatosh.savf, legatoca.savf and exshortcut.ntf.

4. Copy the installation kit from the Windows computer to the IBM i computer using the FTP utility. Use binary mode for the file copy. For example, the following commands would be used to log on to the IBM i computer and copy the file to that computer. In the following example, the IBM i computer is named tbone.

>ftp ftp.tboneConnected to tbone.220 tbone FTP server (Version wu-2.6.2(1) Thu Feb 2117:02:27 PST 2010) ready.User (tbone:(none)): user1Password:230 User ftp logged in. Access restrictions apply.ftp> binary200 Type set to I.ftp> put legatosh.savf QGPL/LEGATOSHftp> put legatoca.savf QGPL/LEGATOCA

5. Change the default directory to the Domino data directory, and then use the FTP put command to copy the exshortcut.ntf file to the Domino data directory. In the following example, /domino/boston/data is the Domino data directory on the IBM i computer.

ftp> cd /domino/boston/data250 CWD command successful.ftp> put exshortcut.ntfftp> quit>



If you are installing the Shortcut Extension Manager on a Domino partitioned server, you must copy the exshortcut.ntf file to each Domino server partition on which you want to install the Shortcut Extension Manager.

6. Οn the IBM i computer, enter the following commands:

RSTLIB SAVLIB(EXSHTCUT) DEV(*SAVF) SAVF(QGPL/LEGATOSH)RSTLIB SAVLIB(EXCACHE) DEV(*SAVF) SAVF(QGPL/LEGATOCA)

7. Use the ADDLNK and NEWLNK commands to create a new symbolic link named LIBEXCUT.PGM in the /QIBM/UserData/LOTUS/NOTES directory.

Note: If you previously installed EMC SourceOne Extensions for Domino (or EmailXtender Shortcut Extension Manager support) on this computer, the symbolic link already exists. Skip to Step 9.

Οn the IBM i computer, enter the following commands:

ADDLNK OBJ(‘/QSYS.LIB/EXSHTCUT.LIB/LIBEXCUT.PGM’)NEWLNK(‘/QIBM/USERDATA/LOTUS/NOTES/LIBEXCUT.PGM’)

8. Use the ADDLNK and NEWLNK commands to create a new symbolic link named LIBEXCA.PGM in the /QIBM/UserData/LOTUS/NOTES directory.

Note: If you previously installed EMC SourceOne Extensions for Domino on this computer, the symbolic link already exists. Skip to Step 9.

Οn the IBM i computer, enter the following commands:

ADDLNK OBJ(‘/QSYS.LIB/EXCACHE.LIB/LIBEXCA.PGM’)NEWLNK(‘/QIBM/USERDATA/LOTUS/NOTES/LIBEXCA.PGM’)

9. On the IBM i computer, create a temporary directory, such as /temp. (This could be the same directory as the one you created for use with $Reader field support, if applicable.)


EmailXtenderTempPath=tempdirEXTMGR_ADDINS=excutEmailXtenderShortcutDb=ExShortCut.nsfEmailXtenderUserName=ExUser/NotesDomainServerTasks=LibexcaEmailXtenderShortcutCacheInt=20

In the previous example of the Notes.ini file:



• tempdir is the name of the temporary directory that was created.

• ExUser is the canonical name of the Lotus Notes administrative user configured during the planning process (see “IBM Lotus Domino permissions” on page 57).

• NotesDomain is the name of the Notes domain for the Notes user for EMC SourceOne.

Note the following:

◆ The EmailXtenderTempPath=tempdir line may already exist in the Notes.ini file if you installed $Reader field support, and the EmailXtenderUserName=ExUser/NotesDomain line should already exist in the Notes.ini file from the Journaling Extension Manager installation.

◆ You can append excut to the existing EXTMGR_ADDINS entry rather than creating a new entry.

◆ You can append ExNotesShortcutCache to the existing ServerTasks entry rather than creating a new entry.

◆ If you are installing the Shortcut Extension Manager on a Domino partitioned server, you must modify the Notes.ini file for each Domino server partition on which you want to install the Shortcut Extension Manager.

11. Add a person record called ES1 Shortcut to the public name and address book.

a. Set the User Name field to ES1 Shortcut.

b. Set the First Name field to ES1.

c. Set the Last Name field to Shortcut.

d. Set the Full Name field to ES1 Shortcut.

e. Edit the Comments field on the Miscellaneous tab to include the EMC SourceOne Worker Services host computer on which EMC SourceOne Web Services is installed:

– If you are using a single Web Services host computer, enter the host name of that computer.

– If you are using a load balancing solution which configures a virtual host name pointing to multiple Web Services computers (see “Configuring load balancing” on page 125), enter the virtual host name.



– If you have installed two or more Web Services host computers but you are not using load balancing, you can enter multiple host names by placing each name on a new line using the ENTER key.

12. Stop and then restart the Domino server on the IBM i computer (or servers, if you are installing on a Domino partitioned server).

Configuration and administrationReview the information provided in “Domino Configuration and Administration” on page 207 and perform any tasks required for your environment.

Installing the ONM Viewer softwareThe ONM Viewer software provides end users on client computers the ability to view Lotus Notes messages from EMC SourceOne Search results in Lotus Notes.

This section includes procedures for installing this software manually using the MSI installation, or silently using a distribution package such as Microsoft SMS. It also includes information on allowing end users to install the software dynamically from the EMC SourceOne Search application.




System requirements Hardware, operating system, network connectivity, and prerequisite software requirements are described in “ONM Viewer client computer requirements” on page 72.






ConsiderationsIf installing the ONM Viewer software on a system on which you intend to also install the EMC SourceOne Console software, ensure that you install the Console software first.

ProceduresTable 52 provides an overview of the procedures to install and configure ONM Viewer software on a host computer.

Install the ONM Viewer software manuallyTo install the ONM Viewer software manually:

1. Log in to the host computer using an account with local administrator privileges.


3. Copy the ES1_ONMViewerSetup.exe executable to a temporary location on the host computer.


5. Double-click the ES1_ONMViewerSetup.exe file and click Run. The Welcome page displays.

Note: When the installer is run, it validates the system configuration to ensure that prerequisite components are installed. Depending on your system configuration, the installer may automatically install one or more prerequisite components before displaying the Welcome page. Automatically

Table 52 Procedures


1a “Install the ONM Viewer software manually” on page 201

Option. Installs the ONM Viewer software manually.

1b “Install the ONM Viewer software silently” on page 202

Option. Installs the ONM Viewer software silently.

1c “Allow users to install the ONM software” on page 203

Option. Allows the end user to install the ONM Viewer software from the EMC SourceOne Search application.

2 “Disabling end user prompt for install” on page 203

Option. Allows the administrator to disable end user prompt for install.



installed components are listed in “Establishing system requirements” on page 58.



8. Click Install.


9. Click Finish.

10. If manually installing the ONM Viewer for all users, you can disable the prompt to the end users to automatically install the ONM Viewer software. See “Allow users to install the ONM software” on page 203.

Install the ONM Viewer software silentlyYou can silently install the ONM Viewer software. This method can be used in environments in which:

◆ Users are not granted local administrator rights on their computers. Local administrator rights are required to install this software.

◆ Users have local administrator rights, but the administrator prefers to distribute the software using silent installation.



Note: If your organization provides local administrator rights to users, you can alternatively allow users to install the software from the EMC SourceOne Search application. See “Allow users to install the ONM software” on page 203 for more information.

The ES1_ONMViewerSetup.exe program confirms that the appropriate version of the Microsoft Installer (MSI) is on the system and it launches the MSI with the applicable parameters.

For more information on standard command line parameters, refer to the Microsoft Installer documentation.

Use the following syntax to silently install the ONM Viewer:

ES1_ONMViewerSetup.exe /s /v"/qn REBOOT=ReallySuppress "

You should disable the prompt to the end users to automatically install the ONM Viewer software. See “Allow users to install the ONM software” on page 203.

Allow users to install the ONM softwareYou can allow end users to install the ONM Viewer software in environments in which users have local administrator rights, and the administrator prefers to let users control the installation.

EMC SourceOne Search users are presented with the option to dynamically install the ONM Viewer software the first time they attempt to view a Lotus Notes message. The user can choose to install the software immediately or postpone the installation. The user can also choose to suppress the installation message. For more information, refer to the EMC SourceOne Search User Guide.

Note: If your organization does not provide local administrator rights to users, you can alternatively use a silent installation method to install the software. See “Install the ONM Viewer software silently” on page 202 for more information.

Disabling end user prompt for installIf you choose to manually or silently install the ONM Viewer software, you can use the EMC SourceOne console to disable the prompt to EMC SourceOne Search end users to install the ONM Viewer software. Refer to the EMC SourceOne Administration Guide for more information.




UpgradeRefer to the product release notes for detailed instructions on upgrading EMC SourceOne product databases and components.

Remove a componentTo remove (uninstall) an EMC SourceOne product component that is installed on a Microsoft Windows system:


2. Select the appropriate component and click Remove.

3. Follow the prompts to remove the component.

Repair a componentRepairing a component can fix missing or corrupt files, shortcuts, and registry entries. Due to differences in the permissions model between Windows 2003 and Windows 2008, use the appropriate procedure for your environment as described in the following sections.

Windows 2003 systemsTo repair an EMC SourceOne product component that is installed on a Microsoft Windows 2003 system:




Maintaining the installation 205


Windows 2008 systemsTo repair an EMC SourceOne product component that is installed on a Microsoft Windows 2008 system, do one of the following, depending on the account your are logged in as.

If you are logged in as the local system Administrator (highest permission level)Do the following:

1. Access the Microsoft Windows Program and Features dialog box.



If you are logged in as a member of the local Administrators groupDo the following:

1. Access the original setup executable for the EMC SourceOne component.

2. Run the executable.




Domino Configuration and Administration 207

A

This appendix provides important information related to configuration and administration of IBM Lotus Domino journaling and shortcutting functionality used with EMC SourceOne Email Management, and includes the following topics:

◆ Journaling configuration and administration.............................. 208◆ Shortcutting configuration and administration........................... 217◆ Historical archiving configuration and administration ............. 221

Domino Configurationand Administration


Domino Configuration and Administration

Journaling configuration and administrationThis section provides information related to configuration and administration of journaling functionality and includes the following topics:

◆ Journaling administration .............................................................. 208◆ EMC SourceOne journaling considerations................................. 212

Journaling administrationThis section includes the following topics:

◆ Configure administrator access to journaling databases ........... 208◆ Starting and stopping EMC SourceOne journaling .................... 209◆ Managing the native Domino journaling environment .............. 211◆ Configuring journaling activities ................................................... 211

Configure administrator access to journaling databasesYou must configure a group in Domino which corresponds to the EMC SourceOne Admins Group created in Active Directory which contains users of the EMC SourceOne console (see “Creating accounts in Active Directory” on page 43 for details). You then associate the Domino group with each journal database used by EMC SourceOne.

Procedure1. Create a group using Domino Administrator. Use the following

guidelines:

• Group name - Use a contextual name such as SourceOne Admins

• Members - Add the same users in the Active Directory Admins Group to the Domino group.

2. Run the Notes client application using the EMC SourceOne Notes User account (typically on the Master Services computer or a Worker Services computer).

3. Configure the access control for each journal database by adding the Domino group with Reader access.

Journaling configuration and administration 209


Maintaining the configurationEnsure the following:

◆ As the EMC SourceOne Admins Group in Active Directory changes, ensure that users are added and deleted in the corresponding Domino group.

◆ As mail.box databases are created (and therefore corresponding journal mailboxes), ensure that you repeat this procedure to configure administrative access to the new journaling databases.

Starting and stopping EMC SourceOne journalingEMC SourceOne journaling provides utilities to start and stop journaling for the supported platforms. Topics include:

◆ Microsoft Windows platforms ........................................................ 209◆ Solaris, Linux, or AIX platforms..................................................... 210◆ IBM i platform................................................................................... 211◆ Starting and stopping journaling on partitioned Domino.......... 211

Microsoft Windows platformsThe EMC SourceOne Extensions for Domino install program installs the ExNotesCfg.exe utility in the Domino program folder. This utility allows you to stop and start journaling without affecting the state of the Lotus Domino server.

When you run the utility, it creates an entry in the Notes.ini file. The command syntax depends on the relative location of the Notes.ini file and the ExNotesCfg.exe file as described in Table 53 on page 210.

To stop or start journaling on the Domino server:

1. Verify that the Domino server is running.

2. Verify the location of the Notes.ini file. This is likely the Domino program folder (c:\Notes\Domino).

3. Verify that the ExNotesCfg.exe file is in the Domino program folder.

4. Open a command prompt and run ExNotesCfg.exe in the directory where Notes.ini resides.

5. Enter the command to enable or disable journaling (Table 53).



Solaris, Linux, or AIX platformsThe Journaling Extension Manager includes a Notes Add-in task (exnotescfg) that allows you to stop or start journaling from the Domino server console without affecting the state of the Domino server.

To start the Journaling Extension Manager, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg journal_enable

To stop the Journaling Extension Manager, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg journal_disable

To list the current setting for the Journaling Extension Manager, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg 3

Table 53 Commands to start or stop Domino journaling

File location Command Result

Notes.ini and ExNotesCfg.exe files are both in the c:\Notes\Domino directory

c:\notes\domino>ExNotesCfg journal_enable

Enable journaling

Notes.ini file is located in c:\notes\data and ExNotesCfg.exe is located in c:\Notes\Domino

c:\notes\data>c:\notes\domino\ExNotesCfg journal_enable

Enable journaling


c:\notes\domino>ExNotesCfg journal_disable

Disable journaling


c:\notes\data>c:\notes\domino\ExNotesCfg journal_disable

Disable journaling



IBM i platformThe capability to start and stop journaling is not available in an IBM i installation of the Journaling Extension Manager.

Starting and stopping journaling on partitioned Domino Disabling EMC SourceOne journaling on one partition of a Domino partitioned server disables all Domino servers on that computer.

When EMC SourceOne journaling is started with two or more Domino partitioned servers on a computer, the messages that indicate journaling is starting are only displayed at the console for the first server journaled. Initialization messages for the journaling of the other servers are not displayed at the console. However, those message are available in the \Data\log.nsf file for each server.

Managing the native Domino journaling environmentRefer to the IBM Lotus Domino documentation for information on configuring and managing the native Domino journaling environment.

Configuring journaling activitiesRefer to the EMC SourceOne Administration Guide for details and procedures for configuring Domino journaling activities against EMC SourceOne or native Domino journaling databases.



EMC SourceOne journaling considerationsThis section describes journaling considerations when using EMC SourceOne journaling extensions. Topics include:

◆ Additional journaling databases ................................................... 213◆ Cleaning up the Bad Documents Folder ...................................... 213◆ ExFailover.nsf database................................................................... 213◆ Multiple Domino servers................................................................ 213◆ Managing high-volume journaling databases............................. 214◆ Information resources ..................................................................... 216

Journaling databasesJournaling databases are a holding place for messages before they are archived by EMC SourceOne. The Journaling Extension Manager creates ExJournal.nsf using a template which is installed with the Journaling Extension Manager. A task running on a EMC SourceOne Worker Services computer then archives messages from the journaling database to an EMC SourceOne archive.

Journaling templatesTwo templates are included with EMC SourceOne journaling from which journaling databases (ExJournal.nsf) can be created.

◆ ExJournal.ntf – The base template used to create the journaling mailbox databases.

◆ ExJournal_ntl.ntf – This alternative template is the same as ExJournal.ntf, but does note have transactional logging enabled.

You can control which template is used as follows:

◆ To use the ExJournal_ntl.ntf template (transaction logging disabled), add the following line to the notes.ini file:

ExDisableJournalTXNLogging=1

◆ To use the ExJournal.ntf template (transaction logging enabled), do not edit the notes.ini file.



Additional journaling databasesIf the Domino administrator configures additional mail.box databases on the Domino server after you have installed the Journaling Extension Manager, the Journaling Extension Manager will create additional Notes databases and name them incrementally (such as ExJournal1.nsf, ExJournal2.nsf, and so on). There must be a one-to-one relationship between the mail.box files for the journaling databases and the Notes databases for each journaling database.

Cleaning up the Bad Documents FolderMessages that could not be transferred from a Domino mail server are moved to the Bad Documents Folder of the Domino journaling database. Installing EMC SourceOne journaling also installs a "cleanup" agent (ExProcBadDocs) which takes messages from the Bad Documents Folder, places them in an NSF file and then places the NSF file into a message as an attachment. It then puts that message back in the All Documents view of the journaling database for processing.

ExFailover.nsf databaseIn the event of a failure to copy mail to one of the ExJournal.nsf databases, an ExFailover.nsf database is created. A corresponding message will be written to the Domino console. If this occurs, you must configure an EMC SourceOne activity to archive mail from this database.

Multiple Domino serversWhen journaling messages in an environment in which there are multiple Domino servers sending email messages, with some Domino servers routing those messages, you should install EMC SourceOne Journaling Extension Manager on all Domino servers (e.g., ones which are sending messages ones which are routing those messages). Capturing messages at the source prevents recipient information in the message from being lost during the routing process.



Managing high-volume journaling databasesIf you have corruption issues with high volume journaling databases, turn off Transactional Logging on all Notes databases created for EMC SourceOne and then compact the databases. For instructions, refer to the Lotus Domino documentation. You can also control whether the template used to create EMC SourceOne journaling databases enables or disables transactional logging when it creates new journaling databases. Refer to “Journaling templates” on page 212.

Native Domino journaling considerationsThis section describes journaling considerations when using native Domino journaling.

Note: For EMC SourceOne journaling considerations, refer to “Native Domino journaling considerations” on page 214.

Journaling database configurationTo support native Domino journaling, you must install EMC SourceOne Extnesions for Native Journaling. “Installing Extensions for IBM Lotus Domino” on page 176 provides complete details.

EMC SourceOne requires that the native Domino journaling database have the following minimum settings:

◆ Journaling – Specify Enabled.

◆ Field encryption exclusion list – Do not change the default fields (Form; From; Principal; PostedDate).

◆ Encrypt on behalf of user – Specify the EMC SourceOne Lotus Notes user account (“IBM Lotus Domino permissions” on page 57).



Cleaning up the Bad Documents FolderMessages that could not be transferred from a Domino mail server are moved to the Bad Documents Folder of the Domino journaling database. The following options are available, depending on your environment.

When you select the native Domino journaling options when installing EMC SourceOne Extensions, the ExProcBadDocs agent is installed. This "cleanup" agent (ExProcBadDocs) takes messages from the Bad Documents Folder, places them in an NSF file and then places the NSF file into a message as an attachment. It then puts that message back in the All Documents view of the journaling database for processing.

To take advantage of this functionality, you must rename your native Domino journaling database from the Domino default name (e.g., mailjrn.nsf) to the same name used with EMC SourceOne journaling (ExJournal.nsf). This is required to enable the ExProcBadDocs agent to interact with the journaling database.

If you choose not to use ExProcBadDocs, the mail administrator is responsible for manually monitoring and cleaning up this folder.



Information resourcesFor information on enabling native Domino mail journaling and setting up the mail journaling database, refer to the IBM Lotus Domino documentation set for the version of Domino you are using.

Shortcutting configuration and administration 217


Shortcutting configuration and administrationThis section provides information related to configuration and administration of shortcutting functionality and includes the following topics:

◆ Shortcutting administration............................................................ 217◆ Shortcutting considerations ............................................................ 220

Shortcutting administrationThis section includes the following topics:

◆ Configuring antivirus software on the Domino server............... 217◆ Starting and stopping shortcutting ................................................ 218◆ Configuring shortcutting activities ................................................ 219

Configuring antivirus software on the Domino serverWhen EMC SourceOne creates a shortcut, it modifies the message by removing attachments from the message. If you have configured antivirus software on the Lotus Domino server to rescan email that is modified in a Notes user's mailbox, the antivirus software detects the modified message and rescans the message. This results in the Domino server attempting to retrieve the shortcut message from the EMC SourceOne archive using an HTTP call. Because EMC SourceOne can quickly create thousands of shortcut messages, this can result in the Domino server being flooded with HTTP calls until it eventually crashes. When this occurs, the EMC SourceOne Shortcut Extension Manager signals multiple errors to the Domino console.

There are a number of steps you can take to avoid this problem:

1. If the antivirus software rescans modified messages, disable that option on Domino servers that contain EMC SourceOne shortcuts.

If you must run a full virus scan of user mail databases that contain shortcuts, disable the Shortcut Extension Manager before running the scan by running the exnotescfg utility.

2. Reload the Shortcut Extension Manager by replacing the appropriate filename in the Notes.ini file on the Domino server, saving the file, and then stopping and restarting the Domino server.



Starting and stopping shortcuttingEMC SourceOne journaling provides utilities to start and stop shortcutting for the supported platforms:

Microsoft Windows platformsThe EMC SourceOne Extensions for Domino install program installs the ExNotesCfg.exe utility in the Domino program folder. This utility allows you to stop and start shortcutting without affecting the state of the Lotus Domino server.

When you run the utility, it creates an entry in the Notes.ini file. The command syntax depends on the relative location of the Notes.ini file and the ExNotesCfg.exe file as described in Table 53 on page 210.

To stop or start shortcutting on the Domino server:

1. Verify that the Domino server is running.

2. Verify the location of the Notes.ini file. This is likely the Domino program folder (c:\Notes\Domino).

3. Verify that the ExNotesCfg.exe file is in the Domino program folder.

4. Open a command prompt and run ExNotesCfg.exe in the directory where Notes.ini resides.

5. Enter the command to enable or disable shortcutting (Table 54).

Table 54 Commands to start or stop Domino shortcutting



c:\notes\domino>ExNotesCfg shortcut_enable

Enable shortcutting

Shortcutting configuration and administration 219


Solaris, Linux, or AIX platformsThe exnotescfg utility allows you to stop or start shortcutting from the Domino server console without affecting the state of the Domino server.

To enable shortcutting, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg shortcut_enable

To stop shortcutting, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg shortcut_disable

To list the current setting for EMC SourceOne shortcutting, verify that the Domino server is running and then enter the following command in the Domino server console:

load exnotescfg 3

IBM i platformThe capability to start and stop shortcutting is not available in an IBM i installation of the Journaling Extension Manager.

Configuring shortcutting activitiesRefer to the EMC SourceOne Administration Guide for details and procedures for configuring Domino shortcutting activities.


c:\notes\data>c:\notes\domino\ExNotesCfg shortcut_enable

Enable shortcutting


c:\notes\domino>ExNotesCfg shortcut_disable

Disable shortcutting


c:\notes\data>c:\notes\domino\ExNotesCfg shortcut_disable

Disable shortcutting

Table 54 Commands to start or stop Domino shortcutting




Shortcutting considerationsThis section describes shortcutting considerations. Topics include:

◆ EMC SourceOne and SSL connections.......................................... 220◆ Agent issues...................................................................................... 220◆ Domino local replicas and shortcuts............................................. 220◆ Domino compact operation and shortcut activity timing.......... 220

EMC SourceOne and SSL connectionsIf the EMC SourceOne Worker Services computer (with Web Services installed) has been configured to only allow SSL connections, shortcuts cannot be retrieved in Notes using the Shortcut Extension Manager installed on the Domino server.

Agent issuesAgents such as the Out of Office agent can cause potential performance problems (for example, causing large scale restoration of shortcut messages), the Domino agent manager does not restore shortcuts.

Domino local replicas and shortcuts

ProblemIf using Domino local replicas and shortcuts exist in a user’s mail database, Domino will temporarily restore attachments to the mail database hosted on the Domino server until a compact is run again.

WorkaroundDomino administrators should be aware of this issue and monitor server space and user mail database size limits.

Domino compact operation and shortcut activity timing

ProblemIf a shortcut activity is launched while Domino is compacting databases, an error similar to the following is generated:

Failed to open note. [ExShortcutJBC.exe, ExNotesUtils.cpp(3683).CExNotesUtils::OpenNote]

WorkaroundReview the nightly compact schedule and adjust the timing of shortcut activities. You can also re-run activities against mail databases that failed to be shortcut.

Historical archiving configuration and administration 221


Historical archiving configuration and administrationHistorical archiving support is inherently provided through permissions granted to EMC SourceOne to mail databases on your Domino servers. You do not need to install any EMC SourceOne software to support historical archiving.

Refer to the EMC SourceOne Administration Guide for details and procedures for configuring Domino historical archiving activities.



Single Sign-on Support Example (Windows) 223

B

This chapter describes an example of configuring support for single sign-on authentication for EMC SourceOne Search and shortcut resolution in a Microsoft Windows environment.

IMPORTANT!This appendix is provided as an example configuration which includes specific environment components. Your environment may require different or additional components and configuration steps. Services are offered by EMC Professional Services to assist your organization in deploying a single sign-on support solution.

This appendix is organized as follows:

◆ Overview........................................................................................... 224◆ Example: Single sign-on in Windows Server 2003 ...................... 227◆ Example: Single sign-on in Windows Server 2008 R2 ................ 236

Single Sign-on SupportExample (Windows)


Single Sign-on Support Example (Windows)

OverviewEMC SourceOne web applications can use the Microsoft trusted subsystem design in which the Web service acts as a trusted subsystem to access additional resources.

This example configuration uses credentials provided in the configuration instead of the user's credentials to access the resource. For more details on this design, refer to:

http://msdn.microsoft.com/en-us/library/aa480587.aspx


◆ Example details ................................................................................ 224◆ EMC SourceOne eDiscovery - Kazeon considerations............... 225

Example detailsThis example will allow a user to access EMC SourceOne web applications and resolve shortcuts using the built-in Windows Integrated authentication mechanism of an IIS 7.5 server and a properly-configured Internet Explorer web browser.

The goal of this example is that when an authenticated Windows user accesses the URL for the EMC SourceOne web applications (e.g., EMC SourceOne Search and EMC SourceOne SharePoint Archive Search), the user will not be prompted for credentials. Instead the user is automatically logged in to the application and it will work normally based on the user’s permissions. Likewise, when a user attempts to resolve an email or file shortcut, the user is not prompted for credentials, and the message or file is restored.

Overview 225


EMC SourceOne eDiscovery - Kazeon considerationsEMC SourceOne eDiscovery - Kazeon is an EMC product that enables organizations to efficiently and cost effectively classify, manage, and retrieve data.

To integrate with the EMC SourceOne core product, EMC SourceOne eDiscovery - Kazeon communicates with an EMC SourceOne Web Services IIS Web site using the Basic authentication method, while the single sign-on example detailed in this chapter is based on Windows Integrated authentication.

Review the following options when implementing single sign-on support in an environment which includes EMC SourceOne eDiscovery - Kazeon:

◆ Mixed authentication

◆ Single sign-on for Universal URL only

Mixed authenticationYou can provide a mixed authentication environment which simultaneously supports:

◆ EMC SourceOne Search, EMC SourceOne for Microsoft SharePoint Archive Search, and Universal URL authentication using Windows Integrated authentication.

◆ EMC SourceOne eDiscovery - Kazeon authentication using Basic authentication.

To support this configuration:

◆ Install Web Services software on separate workers to provide separate instances of a Web Services IIS site (SearchWS) for Kazeon and Search.

• Configure the first Web Services site (SearchWS) which supports Kazeon to use Basic authentication (e.g., retain the default configuration). When you install Kazeon software, configure it to utilize this Web Services site.



• Configure the second Web Services site (SearchWS) which supports Search to use Windows Integrated authentication as described in this chapter. When you install other EMC SourceOne components, configure them to utilize this Web Services site.

◆ Configure the Search site (Search) and Universal URL site (ExShortcut) to use Windows Integrated authentication as described in this chapter.

Single sign-on for Universal URL onlyIf single sign-on is needed only to support the Universal URL (ExShortcut) site:

◆ Configure the Universal URL site (ExShortcut) site to use Windows Integrated authentication.

◆ Configure the Web Services and Search sites (SearchWS and Search) to use Basic authentication.

Example: Single sign-on in Windows Server 2003 227


Example: Single sign-on in Windows Server 2003The topics in this section provide an example of how to configure single sign-on for the EMC SourceOne Search and shortcut Web applications in a Microsoft Windows Server 2003 environment:

◆ Configure Web Services site (SearchWS)....................................... 227◆ Configure the Search site (Search).................................................. 230◆ Configure Universal URL site (ExShortcut).................................. 231◆ Restart IIS........................................................................................... 233◆ Configure IIS 6.0 authentication..................................................... 233◆ Configure a User Principal Name for the service account ......... 235◆ Configure Internet Explorer ............................................................ 235

IMPORTANT!This section describes an example configuration which includes specific environment components. Your environment may require different or additional components and configuration steps. Services are offered by EMC Professional Services to assist organizations in deploying a single sign-on support solution.

Configure Web Services site (SearchWS)Do the following to configure the EMC SourceOne Web Services (SearchWS) site:

1. Open the computer on which Web Services is installed, open IIS Manager and navigate to the SearchWS virtual directory.

2. Right-click SearchWS and select Properties.



3. Click the Directory Security tab.

a. In the Authentication and access control section, click Edit to display the Authentication Methods page.

b. Ensure that the Anonymous access check box is not selected and that Integrated Windows authentication check box is the only check box selected.

4. Click OK to return to the SearchWS Properties page and select the ASP.NET tab.

5. Click Edit Configuration.

6. Click the Authentication tab

7. Change Authentication mode from None to Windows.

8. Select the Authorization tab.



9. Change the Local authorization rules section (bottom pane) to deny access to all users but the EMC SourceOne service account or security group.

a. Configure the first entry:

a. Rule type: Allow

b. Verbs: All verbs

c. Users: DOMAIN\serviceAccountUser

d. Alternatively, you can enter the EMC SourceOne security group in the Role field.

Note: Ensure that the Users field is blank if specifying the security group in the Roles field.

b. Configure the second entry:



a. Rule type: Deny

b. Verbs: All verbs

c. Users and roles: select All Users (*)

10. Click OK on the dialogs to save all changes and close the properties dialog.

Configure the Search site (Search)Do the following to configure the Search site:

1. Open the computer on which EMC SourceOne Search is installed, open IIS Manager and navigate to the Search virtual directory.

2. Right-click Search and select Properties.






4. Click OK to return to the Search Properties page and select the ASP.NET tab.



7. Change Authentication mode from Forms to Windows.


Configure Universal URL site (ExShortcut)Do the following to configure the Universal URL (ExShortcut) site:

1. Open the computer on which Web Services is installed, open IIS Manager and navigate to the ExShortcut virtual directory.

2. Right-click ExShortcut and select Properties.






4. Click OK to return to the ExShortcut Properties page and select the ASP.NET tab.


6. Click the Authentication tab.

7. Change Authentication mode from Forms to Windows.



Restart IISTo ensure the configuration changes take effect, use the iisreset command to restart IIS.

1. From the Start menu, click Run.

2. In the Open box, type cmd, and then click OK.

3. At the command prompt, type the following:

iisreset

See the following Microsoft article for details:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/95826e7a-bac4-4e1f-bcb6-c52d49c9d7f4.mspx?mfr=true

Configure IIS 6.0 authenticationFor Windows Server 2003 environments which use IIS 6.0, you must configure a Service Principle Name (SPN) for the EMC SourceOne service account(s) used to run ASP.NET applications, specifically to support Kerberos authentication, the default authentication method used by Windows Integrated authentication.

Note: The information in this section does not apply to Windows Server 2008 R2 environments which use IIS 7.5. Refer to “Example: Single sign-on in Windows Server 2008 R2” on page 236 for details on configuring authentication in that environment.

General informationYou configure the SPN by running the Setspn utility on a domain controller. This command-line tool allows you to read, modify, and delete the Service Principal Names (SPN) directory property for an Active Directory service account. SPNs are used to locate a target principal name for running a service. You can use Setspn to view the current SPNs, reset the account's default SPNs, and add or delete supplemental SPNs.

For details on the Setspn utility:

http://support.microsoft.com/?id=929650


http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/95826e7a-bac4-4e1f-bcb6-c52d49c9d7f4.mspx?mfr=true

http://support.microsoft.com/?id=929650




The Setspn utility is provided in the Windows Server 2003 Support Tools that are included on your Windows Server 2003 CD. To install the tools, double-click the Suptools.msi file in the Support/Tools folder.

ProcedureUse the following procedure to configure the SPN for the EMC SourceOne service account(s).

IMPORTANT!You must run the command twice for every EMC SourceOne worker host computer on which Web Services software is installed.

1. Register an SPN using the Setspn utility by running the following commands from a command prompt:

a. Using the NetBIOS name of the EMC SourceOne Web Services host computer. For example:

setspn -A HTTP/webservername domain\serviceAccountUser

b. Using the fully-qualified domain name (FQDN) of the EMC SourceOne Web Services host computer. For example:

setspn -A HTTP/webservername.fullyqualifieddomainname domain\serviceAccountUser

2. Repeat this procedure for the remaining Web Services and host computers.



Configure a User Principal Name for the service accountThe service account under which the EMC SourceOne Web service is running must have a User Principal Name (UPN).

Note: This configuration is in addition to the Service Principal Name (SPN) you configure as described in “Configure IIS 6.0 authentication” on page 233.

The UPN is composed of the user logon name and the UPN suffix joined by the @ sign. Ensure the service account has a UPN by modifying the properties for the service account using Active Directory Users and Computers. For details, see the following Microsoft KB article:

http://technet.microsoft.com/en-us/library/cc756018%28WS.10%29.aspx

Configure Internet ExplorerTo configure Internet Explorer settings for client computers accessing the EMC SourceOne Search, SharePoint Archive Search, and shortcut URLs:

1. Open Internet Explorer.

2. Select Tools > Internet Options and select the Security tab.

3. Click Local intranet and select Custom Level.

4. Scroll to the bottom of the Settings pane.

5. In the User Authentication > Logon section, ensure that Automatic logon only in Intranet zone is selected.

6. Click OK to return to the Security tab.

7. Click Sites.

8. Click Advanced.

9. Add the URLs for the Search, SharePoint Archive Search, and ExShortcut web sites.

When this configuration is complete, the Internet Security Properties icon displayed in the lower right side of the browser should indicate that the site is in the local intranet.

http://technet.microsoft.com/en-us/library/cc756018%28WS.10%29.aspx



Example: Single sign-on in Windows Server 2008 R2The topics in this section provide an example of how to configure single sign-on for the EMC SourceOne Search and shortcut Web applications in a Microsoft Windows Server 2008 R2 environment:

◆ Configure Web Services site (SearchWS)...................................... 236◆ Configure the Search site (Search)................................................. 240◆ Configure Mobile Services site (ExShortcut) ............................... 241◆ Restart IIS .......................................................................................... 242◆ Configure IIS 7.5 authentication .................................................... 242◆ Configure Internet Explorer ........................................................... 246


Configure Web Services site (SearchWS)This section describes how to configure the Web Service site (SearchWS).

Before you beginEnsure that the required role services (including the ones required to support SSO) are installed as described in “Configure IIS 7.5 role services (Windows Server 2008 R2 only)” on page 126.

Configure the siteConfigure the EMC SourceOne Web Services (SearchWS) site:

1. Open the computer on which Web Services is installed, open Internet Information Services (IIS) Manager.

Example: Single sign-on in Windows Server 2008 R2 237


2. Navigate to SearchWS in the Connections pane.

3. Click SearchWS. The configuration options for SearchWS are displayed in the center pane.

4. In the IIS section, double-click the Authentication icon.



5. Configure the following settings:

• Disable Anonymous Authentication

• Disable Forms Authentication

• Enable Windows Authentication

6. Click SearchWS in the location bar to return to /SearchWS Home.

7. Scroll to the Management section in the center pane.

8. Double-click the Configuration Editor icon.

a. From the Section drop-down list, select system.web/authentication.

b. Set the mode to Windows.




10. Scroll to the ASP.NET section in the center pane.

11. Double-click the .NET Authorization icon.

12. Remove any existing rules.

Note: You cannot remove the Inherited rule, Allow > All Users

13. Create the following rules:

a. Create an Allow rule for either:

– The EMC SourceOne security group role (using the Specified roles or user groups entry field).or

– The EMC SourceOne service account user (using the Specified users entry field).

b. Add a Deny rule for All Users.

IMPORTANT!The Allow rule must precede the Deny rule in the .NET Authorization Rules section.




15. Exit the Internet Information Services (IIS) Manager application.

Configure the Search site (Search)This section describes how to configure the Search site (Search).


Configure the siteConfigure the EMC SourceOne Search (Search) site:


2. Navigate to Search in the Connections pane.

3. Click Search. The configuration options for Search are displayed in the center pane.








6. Click Search in the location bar to return to /Search Home.


Configure Mobile Services site (ExShortcut)This section describes how to configure the Mobile Services site (ExShortcut).


Configure the siteConfigure the EMC SourceOne Mobile Services (ExShortcut) site:


2. Navigate to ExShortcut in the Connections pane.

3. Click ExShortcut. The configuration options for ExShortcut are displayed in the center pane.








6. Click ExShortcut in the location bar to return to /ExShortcut Home.


Restart IISTo ensure the configuration changes take effect, use the iisreset command to restart IIS.

Configure IIS 7.5 authenticationBy default, Windows Server 2008 R2/IIS 7.5 uses Windows Authentication with Kernel-mode authentication enabled, resulting in improved performance.

Unlike Windows Server 2003/IIS 6.0, which required that you use the Setspn utility to configure an application pool identity for the EMC SourceOne service account, the IIS 7.5 configuration instead uses the IIS server’s machine account to decrypt single sign-on Kerberos tickets for the requested service.



Typical scenarioIn most cases, you do not need to perform any further configuration for Windows Authentication, assuming that you are accessing the server by the NetBIOS or fully-qualified domain name (e.g., MyIISServerName or MyIISServerName.Domain.com.) If this is not the case in your environment, refer to “Alternate scenarios” on page 243.

Alternate scenariosThere may be alternate scenarios, depending on your environment:

◆ “Custom host name or host header names” on page 243

◆ “Web farm” on page 243

Custom host name or host header namesIf your environment uses a custom host or host header names (e.g., www.MySite.com), an SPN must be added only for the IIS server’s machine account (and not for the Domain\Username account). The Setspn utility is run on the domain controller. For example:

setspn -A HTTP/site_custom_name netbios_name

Web farmIf you are running the IIS 7.5 server in a Web farm, the Kerberos Ticket Granting Server (KDC) cannot predict which individual server the request may go to decrypt tickets. In this scenario, instead of registering SPNs under a specific machine account, use a domain account.

Scenario A (recommended) — Retain Kernel-mode authentication, configure SPNs for the EMC SourceOne service account, and configure the ApplicationHost.config file to use the application pool credentials.

Configure the SPNs:

Note the following differences when using the Setspn utility in Microsoft Windows Server 2008 R2 environment:

◆ Microsoft Windows Server 2008 R2 includes an updated version of the Setspn utility as part of the operating system. You must use this version of the utility if running Windows Server 2008 R2.

◆ The utility includes an additional parameter switch used when configuring the SPN (-u). This switch indicates that the SPN is for a user instead of a computer.



◆ You must run the command twice for every EMC SourceOne worker host computer on which Web Services software is installed.



setspn -U -A http/webservername domain\serviceAccountUser


setspn -U -A http/webservername.fqdn domain\serviceAccountUser


3. Configure a User Principal Name (UPN) for the service account as described in “Configure a User Principal Name for the service account” on page 235.

Configure ApplicationHost.config file to use the application pool credentials:

1. Ensure the application pool is run under the EMC SourceOne service account (this should already be configured).

2. Locate the ApplicationHost.config file on the IIS server. Typically:

<system_drive>/Windows/System32/inetsrv/config

3. Add the useAppPoolCredentials attribute to the file:

<system.webServer><security> <authentication> <windowsAuthentication enabled="false" useKernelMode="true" useAppPoolCredentials="true" /> </authentication> </security> </system.webServer>



Scenario B (not recommended) — You can disable Kernel-mode authentication and configure SPNs for the EMC SourceOne service account. You forfeit the performance benefits provided using Kernel-mode authentication.

Disable Kernel-mode authentication for EMC SourceOne sites:


2. Navigate to SearchWS in the Connections pane.

3. Click SearchWS. The configuration options for Search are displayed in the center pane.


5. Select Windows Authentication.

6. In the right pane, select Advanced Settings.

7. Uncheck Kernel-mode Authentication.

8. Repeat this procedure for the Search (Search) and Mobile Services (ExShortcut) site.

Configure the SPNs:

Note the following differences when using the Setspn utility in Microsoft Windows Server 2008 R2 environment:

◆ Microsoft Windows Server 2008 R2 includes an updated version of the Setspn utility as part of the operating system. You must use this version of the utility if running Windows Server 2008 R2.

◆ The utility includes an additional parameter switch used when configuring the SPN (-u). This switch indicates that the SPN is for a user instead of a computer.

◆ You must run the command twice for every EMC SourceOne worker host computer on which Web Services software is installed.





setspn -U -A http/webservername domain\serviceAccountUser


setspn -U -A http/webservername.fqdn domain\serviceAccountUser


3. Configure a User Principal Name (UPN) for the service account as described in “Configure a User Principal Name for the service account” on page 235.

Configure Internet ExplorerTo configure Internet Explorer settings for client computers accessing the EMC SourceOne Search, SharePoint Archive Search, and shortcut URLs:







7. Click Sites.

8. Click Advanced.

9. Add the URLs for the Search, SharePoint Archive Search, and ExShortcut web sites.






Single Sign-on Support Example (Domino) 249

This chapter describes an example of configuring support for single sign-on authentication for EMC SourceOne Search in an IBM Lotus Domino environment.

IMPORTANT!This appendix is provided as an example configuration which includes specific environment components. Your environment may require different or additional components and configuration steps. Services are offered by EMC Professional Services to assist your organization in deploying a single sign-on support solution.


◆ Overview........................................................................................... 250◆ Example: Single sign-on in Windows 2003 .................................. 252

Single Sign-on SupportExample (Domino)


Single Sign-on Support Example (Domino)

OverviewThis example of a single sign-on solution for EMC SourceOne Search and shortcut resolution functionality requires the single sign-on solution published by IBM as a foundation.

IBM SSO solutionThe IBM single sign-on (SSO) solution is based on a configuration between IBM Websphere Portal and IBM Lotus Domino. Once this configuration is established, you perform some additional configuration steps specific to EMC SourceOne to complete the configuration.

For white papers detailing the concepts, implementation details and troubleshooting information, refer to the following IBM web site, "Understanding single sign-on (SSO) between IBM WebSphere Portal and IBM Lotus Domino":

http://www.ibm.com/developerworks/websphere/zones/portal/proddoc/dw-w-sso-portal-domino/index.html

EMC SourceOne eDiscovery - Kazeon considerationsEMC SourceOne eDiscovery - Kazeon is an EMC product that enables organizations to efficiently and cost effectively classify, manage, and retrieve data.

To integrate with the EMC SourceOne core product, EMC SourceOne eDiscovery - Kazeon communicates with an EMC SourceOne Web Services IIS Web site using the Basic authentication method, while the single sign-on configuration example detailed in this chapter is based on Windows Integrated authentication. You must review the following considerations before implementing single sign-on support if implementing EMC SourceOne eDiscovery - Kazeon with the EMC SourceOne core product:

http://www.ibm.com/developerworks/websphere/zones/portal/proddoc/dw-w-sso-portal-domino/index.html

Overview 251


Mixed authenticationYou can provide a mixed authentication environment which simultaneously supports:

◆ EMC SourceOne Search and Universal URL authentication using Windows Integrated authentication.

◆ EMC SourceOne eDiscovery - Kazeon authentication using Basic authentication.

To support this configuration:

◆ Install Web Services software on separate workers to provide separate instances of a Web Services IIS site (SearchWS) for Kazeon and Search.

• Configure the first Web Services site (SearchWS) which supports Kazeon to use Basic authentication (e.g., retain the default configuration). When you install Kazeon software, configure it to point to this Web Services site.

• Configure the second Web Services site (SearchWS) which supports Search to use Windows Integrated authentication as described in this chapter. When you install other EMC SourceOne components, configure them to point to this Web Services site.

◆ Configure the Search site (Search) and Universal URL site (ExShortcut) to use Windows Integrated authentication as described in this chapter.

Single sign-on for Universal URL onlyIf single sign-on is needed only to support the Universal URL (ExShortcut) site, you can:

◆ Configure the Universal URL site (ExShortcut) site to use Windows Integrated authentication.

◆ Configure the Web Services and Search sites (SearchWS and Search) to use Basic authentication.



Example: Single sign-on in Windows 2003Assuming the IBM single-sign on configuration between IBM WebSphere Portal and IBM Lotus Domino has been established, the following sections provide an example of the additional configuration steps required to complete the single sign-on configuration. This section includes the following topics:

◆ Enable the DIIOP task on the Domino server.............................. 252◆ Install the ExValidateLTPA web service ....................................... 253◆ Configure IIS Web sites in Windows 2003.................................... 258◆ Configure IIS authentication .......................................................... 264


Enable the DIIOP task on the Domino serverThe Domino Internet Inter-ORB Protocol ( DIIOP) enables EMC SourceOne to attach to and manipulate Domino databases.

You can enable the DIIOP task by typing the load diiop command on the Domino server, or you can enable the DIIOP task to load automatically every time the Domino server starts by editing the notes.ini file in the Domino Program directory.

For details, refer to the IBM Lotus Domino documentation set. The following link provides relevant information:

http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.zos.doc/collab/ksa_cfg_dommailptl.html



Example: Single sign-on in Windows 2003 253


Install the ExValidateLTPA web serviceDeploy the ExValidateLTPA web service in WebSphere using the ExValidateLPTA_WS.war file which is packaged in a hot fix available on the EMC Online Support site (SourceOne for IBM Lotus Domino SSO Hotfix 1).

To install the ExValidateLPTA web service on WebSphere:

1. Unzip the hotfix package and copy the ExValidateLPTA_WS.war file to an appropriate location on the WebSphere server.

2. Log in to the WebSphere Integrated Solutions Console as a WebSphere administrator.

3. Expand the Applications node in the Tasks tree and select Install New Application. The Preparing for application installation page displays.



4. In the Path to new application section, select Local file system and browse to the path to which you copied the ExValidateLTPA_WS.war file.

5. In the Context root text box, type ExValidateLTPA_WS.

6. Click Next. The Select installation options page displays.

7. In the Application name text box:

a. Remove the "_war" from the displayed text.

b. Click Next. The Map modules to servers page displays.

8. Select the ExValidateLTPA_WS module and click Next. The Map virtual hosts for Web modules page displays.



9. Select the ExValidateLTPA_WS module and click Next. An installation summary page displays.

10. Click Finish.

11. An installation progress page displays.

12. After installation completes, click Save.

13. Expand the Applications node in the Tasks tree and select Enterprise Applications. The Enterprise Applications page displays.



14. Select the ExValidateLTPA_WS application and click Start. The web service is now started.

15. Copy the .mar files from the installation directory to the lib directory, for example:

The default installation directory location is:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\win2003r2se32Node01Cell\ExValidateLTPA_WS.ear\ExValidateLTPA_WS.war\WEB-INF\modules

The lib directory location is:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\win2003r2se32Node01Cell\ExValidateLTPA_WS.ear\ExValidateLTPA_WS.war\WEB-INF\lib.

16. For the copied files, rename the extensions from .mar to .jar.

17. Change the "Class Loader Order" to show "Class loaded with local class loader first (parent last)":

a. Navigate to the following:

Enterprise Applications > ExValidateLTPA_WS > Manage Modules > ExValidateLTPA_WS.war.



18. Expand Applications > Application Types in the menu tree on the left of the admin tool and then click WebSphere enterprise applications. The Enterprise Applications pane on the right appears.

19. Click ExValidateLTPA_WS.

20. In the Modules section, click Manage Modules. The Manage Modules page appears.

21. Click the ExValidateLTPA_WS module.

22. In the Configuration tab of the page that you navigated to, choose Class loader order > Classes loaded with local class loader first (parent last).

23. Click OK and save the changes to the Master Configuration.

24. Start a browser and go to URL to start the wsdl for the web service:

http://ServerName:9080/ES1Test/services/ExValidateLTPAToken?wsdl

Note: The port number for your installation may differ.



Configure IIS Web sites in Windows 2003This section describes how to configure the EMC SourceOne Search and Web Services IIS Web sites for single sign-on:

◆ “Configure the Search Web site” on page 258

◆ “Enable Windows Authentication for the Web Services site” on page 260

Configure the Search Web siteDo the following to configure the Search (Search) site:

1. Open the computer on which EMC SourceOne Search is installed, open IIS Manager and navigate to the Search virtual directory.

2. Right-click Search and select Properties.

3. Click the ASP.NET tab.

4. Click Edit Configuration. The ASP.NET Configuration Settings page (General tab) displays.



5. In the Application settings section, do the following:

a. Click the LTPAAuthEnabled key and click Edit.

b. In the Value text box, type true.

c. Click OK.

d. Click the LTPAAuthFailURL key and click Edit.

e. In the Value text box, type the URL for the IBM Portal. For example:

http://servername.domain.com:10040/wps/portal/

f. Click OK.

g. Click the ExValidateLTPAURL key and click Edit.

h. In the Value text box, type the URL for the ExValidateLTPA Web service. For example:

http://servername.domain.com:10000/ExValidateLTPA_WS/services/ExValidateLTPAToken.ExValidateLTPATokenHttpSoap11Endpoint

i. Click OK.

j. Click the DominoServer key and click Edit.

k. In the Value text box, type the fully-qualified domain name of the Domino server. For example:

servername.domain.com

l. Click OK.

6. Click the Autentication tab.

7. In the Authentication settings section, select None in the Authentication mode dropdown list.



Enable Windows Authentication for the Web Services siteDo the following to configure the EMC SourceOne Web Services (SearchWS) site:

1. Open the computer on which Web Services is installed, open IIS Manager and navigate to the SearchWS virtual directory.

2. Right-click SearchWS and select Properties.






4. Click OK to return to the SearchWS Properties page and select the ASP.NET tab.



7. Change Authentication mode from None to Windows.

8. Select the Authorization tab.



9. Change the Local authorization rules section (bottom pane) to deny access to all users but the EMC SourceOne service account or security group.

a. Configure the first entry:

a. Rule type: Allow

b. Verbs: All verbs

c. Users: DOMAIN\serviceAccountUser

d. Alternatively, you can enter the EMC SourceOne security group in the Role field.

Note: Ensure that the Users field is blank if specifying the security group in the Roles field.



b. Configure the second entry:

a. Rule type: Deny

b. Verbs: All verbs

c. Users and roles: select All Users (*)




Configure IIS authenticationDepending on your IIS server environment, refer to the following sections for information about configuring IIS authentication:

Windows Server 2003/IIS 6.0:

◆ “Configure IIS 6.0 authentication” on page 233

◆ “Configure a User Principal Name for the service account” on page 235

◆ “Configure Internet Explorer” on page 235

Windows Server 2008 R2/IIS 7.5:

◆ “Configure IIS 7.5 authentication” on page 242

◆ “Configure Internet Explorer” on page 246

Shortcut and UDA Icon Support for Outlook 265

D

To support the display of icons in Outlook which indicate the status of email messages which have been shortcut or placed in a user-directed archive (UDA), you must publish Custom Exchange forms containing these icons to an Exchange Public Organizational Forms library.


◆ Overview........................................................................................... 266◆ Publishing Custom Exchange forms ............................................. 267

Shortcut and UDA IconSupport for Outlook


Shortcut and UDA Icon Support for Outlook

OverviewEMC SourceOne uses custom icons to display message status information to Outlook users. The custom icons indicates the type of processing that occurred for the message, and whether it was successfully processed.

If your site has not configured user-directed archiving, then the icons shown in Table 55 are used.

If your site has configured user-directed archiving, then additional icons shown in Table 56 are used.

Table 55 Shortcut icons

Icon Description

Normal

Shortcut

Table 56 User-directed archive icons

Success Failed Type of processing and item

Archive message

Shortcut message

Archive posted message

Shortcut posted message

Archive meeting request

Archive task request

Publishing Custom Exchange forms 267


Publishing Custom Exchange forms To support the display of shortcut and user-directed icons, you create an Exchange Public Organizational Forms library and publish the EMC SourceOne Custom Exchange forms (.fdm files) to the library in Exchange 2003, 2007 or 2010.

Create an Exchange Public Organizational Forms libraryMicrosoft Exchange 2003, 2007 or 2010 does not create a default Public Organizational Forms library. You may have created a Public Organizational Forms library if you are using Exchange with other software, such as virus scanning software. If a library does exist, proceed to “Configure permissions for the library” on page 268.

If you do not already have a Public Organizational Forms library in place on the Microsoft Exchange 2003, 2007 or 2010 server, you must create one so that you can install the EMC SourceOne forms used to display shortcut and user-directed archive icons.

Refer to the appropriate Microsoft documentation for your version of Exchange to create an Organizational Forms library. The following Microsoft links include relevant information:

◆ How to Create an Organizational Forms Library in Exchange 2003

• http://support.microsoft.com/kb/821922/

◆ How to Create an Organizational Forms Library in Exchange 2007

• http://support.microsoft.com/kb/933358

• http://technet.microsoft.com/en-us/library/cc540468(EXCHG.80).aspx

◆ Understanding Public Folders (Exchange 2010)

• http://technet.microsoft.com/en-us/library/bb397221(EXCHG.140).aspx



Configure permissions for the libraryVerify the following:

◆ You have an account configured with Owner permissions to the new library. You will log in to Outlook using the MAPI profile for this account to publish the forms.

◆ Client computers have permission to access the forms.

Refer to the appropriate Microsoft documentation for your version of Exchange to configure permissions for the library.

Replicate the forms library to other Exchange serversConfigure the forms library to replicate to any remaining Exchange servers on which you plan to create shortcuts or use user-directed archiving. Refer to the appropriate Microsoft documentation for the version of Exchange you are using.

Review the forms you can publishThe Exchange forms used by EMC SourceOne are provided in the product software kit in the Setup\Windows\Forms directory.

Table 57 lists the forms you add to the Organization Form Public Folder to display shortcut icons correctly, and their corresponding message classes. The forms with "Archived" or "Failed" in their names (indicated by gray shading) are used for user-directed archiving.

Table 57 EMC SourceOne Exchange Forms and Message Classes

Outlook Template File Message Class Form Name Indicates

ExMeetingRequestArchived.fdm IPM.Schedule.Meeting.Request EXArchived User-directed archiving of meeting request was successful.

ExMeetingRequestFailed.fdm IPM.Schedule.Meeting.Request EXFailed User-directed archiving of meeting request failed.

ExNoteArchived.fdm IPM.Note EXArchived User-directed archiving of message was successful.

ExNoteFailed.fdm IPM.Note EXFailed User-directed archiving of message failed.



Publishing forms to the libraryAfter you create a Public Organizational Forms library on the Microsoft Exchange server, install the EMC SourceOne forms into the library.

To install forms using Outlook 2003, 2007 or 2010:

1. Open Microsoft Outlook.

2. In the Choose Profile dialog box, select a MAPI profile that has:

• Access to the Microsoft Exchange server that owns the Public Organizational Forms library

• Owner permissions for the Public Organizational Forms library

• Access to all address books and distribution lists that are supported by EMC SourceOne

ExPostArchived.fdm IPM.Post EXArchived User-directed archiving of posted message was successful.

ExPostFailed.fdm IPM.Post EXFailed User-directed archiving of message failed.

ExPostShortcutArchived.fdm IPM.Post ExShortcut.EXArchived User-directed archiving of shortcut posted message was successful.

ExPostShortcutFailed.fdm IPM.Post ExShortcut.EXFailed User-directed archiving of message failed.

ExShortcut.fdm IPM.Note ExShortcut Shortcut message

ExShortcutArchived.fdm IPM.Note ExShortcut.EXArchived User-directed archiving of shortcut message was successful.

ExShortcutFailed.fdm IPM.Note ExShortcut.EXFailed User-directed archiving of shortcut message failed.

ExShortcutPost.fdm IPM.Post ExShortcut Shortcut posted message

ExTaskRequestArchived.fdm IPM.TaskRequest EXArchived User-directed archiving of task request was successful.

ExTaskRequestFailed.fdm IPM.TaskRequest EXFailed User-directed archiving of task request failed.

Table 57 EMC SourceOne Exchange Forms and Message Classes (continued)

Outlook Template File Message Class Form Name Indicates



To change the profile that is used by Microsoft Outlook, from the Tools menu select Options. Select the Mail Services tab and then select a different profile.

3. From the Tools menu, select Options. The Options dialog box opens.

4. Select the Other tab.

5. Click Advanced Options. The Advanced Options dialog box opens.

6. Click Custom Forms to display the Custom Forms page.

7. Click Manage Forms. The Forms Manager dialog box opens.

8. Verify that both sides of the dialog box are set to Organization Forms (or the name of the Public Organizational Forms library you created in “Create an Exchange Public Organizational Forms library” on page 267). If they are not, click the Set button next to the Organization Forms fields. When the Set Library To dialog box opens, choose the Public Organizational Forms library you created from the drop-down list and then click OK.

If Personal Forms is the only option that appears in the Public Organizational Forms library list, make sure that you created a Public Organizational Forms library as described in “Create an Exchange Public Organizational Forms library” on page 267, and that the profile you used to open Microsoft Outlook has owner privileges within that library.

9. Click Install.

10. In the Open dialog box:

a. Locate the .fdm files provided with EMC SourceOne product software kit (Setup\Windows\Forms).

b. In the Files of Type field, select the Form Message (.fdm) file type.

c. Double-click the ExShortcut.fdm form.



11. In the Form Properties dialog box, click OK.

If you are replacing an existing Email Message Shortcut form after updating from a previous release of EmailXtender, a message appears asking if you want to replace the existing form. Click Yes.

The form installs.

12. Repeat step 9 - step 11 for the remaining .fdm files you want to install. Refer to “Review the forms you can publish” on page 268 for a list of the .fdm files used by EMC SourceOne.

13. Save all changes and close all dialog boxes.



Installing EMC SourceOne Reporting 273

E

EMC SourceOne Reporting is an optional feature in EMC SourceOne Email Management. This appendix describes how to install components of EMC SourceOne Reporting and is organized as follows:

◆ Pre-deployment planning ............................................................... 275◆ Hardware and software requirements .......................................... 277◆ Installing SQL Server 2008/2008 R2 Reporting Services ........... 279◆ Configuring SQL Server Report Server ........................................ 288◆ Verifying installation of SQL Server Report Server .................... 303◆ Installing EMC SourceOne reports................................................ 304◆ Controlling access to EMC SourceOne reports............................ 308◆ Authenticating with the EMC SourceOne Activity database.... 311◆ Configuring Internet Explorer for EMC SourceOne reports ..... 313◆ Maintaining the installation ........................................................... 314

Installing EMCSourceOne Reporting


Installing EMC SourceOne Reporting

Planning and installation checklistUse the following checklist to plan and install EMC SourceOne Reporting.

Table 58 Checklist: Planning and installing EMC SourceOne Reporting


Perform pre-deployment planning. Review SQL Server requirements, considerations and limitations and high availability requirements. See “Considerations and limitations” on page 276.

Review hardware and software requirements for the report server and client host computers.

Review hardware and software requirements for Microsoft SQL Server 2008/2008 R2 Reporting Services. See “Requirements for the report server” on page 277.Review software requirements for the EMC SourceOne Reporting client computer. See “Requirements for the report client” on page 278

Install Reporting Services. Install SQL Server 2008/2008 R2 Reporting Services. See “Installing SQL Server Reporting Services” on page 83.

Configure Report Server. Configure SQL Server 2008/2008 R2 Report Server.See “Configuring SQL Server Report Server” on page 92.

Verify the installation. Verify the installation of SQL Server 2008/2008 R2 Report Server. See “Verifying installation of SQL Server Report Server” on page 107.

Install the EMC SourceOne Reports on the Report Server. Install the Source One reports on the SQL Server 2008/2008 R2 Report Server. “Installing EMC SourceOne reports” on page 108.

8 Set access permissions for EMC SourceOne reports. Configure the access control permissions for the reports. See “Controlling access to EMC SourceOne reports” on page 112.

Configure Internet Explorer. Configure Internet Explorer on client computers. See “Configuring Internet Explorer for EMC SourceOne reports” on page 117.

Configure EMC SourceOne auditing. Perform administrative configuration of auditing. Refer to "Configuring Applications and Web Services" > "Auditing search operations" in the EMC SourceOne Email Administration Guide.

Pre-deployment planning 275


Pre-deployment planningBefore you install EMC SourceOne Reporting, review the following sections:

◆ “SQL Server 2008 or 2008 R2 Reporting Services requirement” on page 275

◆ “Considerations and limitations” on page 276

◆ “High availability of SQL Server Reporting Services” on page 276

SQL Server 2008 or 2008 R2 Reporting Services requirementEMC SourceOne Reporting requires SQL Server 2008 or 2008 R2 Reporting Services. Refer to Microsoft for information about license costs.

OverviewIf your EMC SourceOne production databases are on SQL Server 2008/2008 R2, then the SQL Server 2008/2008 R2 Report Server can be installed on the same computer, as indicated by the dotted line in Figure 11.

Figure 11 Server and client configuration for EMC SourceOne Reporting

The following table lists the SQL Server version and edition supported for EMC SourceOne components.

Table 59 Supported SQL Server editions for EMC SourceOne

EMC SourceOne functionalitySQL Server 2008

(Standard/Enterprise)SQL Server 2008 R2

(Standard/Enterprise)

EMC SourceOne databases Yes Yes

EMC SourceOne Reporting(Requires SQL Server Reports Server)

Yes Yes



Considerations and limitationsReview the following considerations and limitations.

PerformanceThe EMC SourceOne Activity production database is also used for reporting. Performance is affected by the increased number of database calls and increased disk space usage due to additional auditing. System reports require increased I/O operation.

ScalabilityIf the EMC SourceOne Activity database is hosted on the Enterprise edition of SQL Server, then some of the database tables that store auditing information are partitioned automatically to improve the scalability of auditing. No action is required by the SQL Server database administrator.

LanguagesInternet Explorer (7.0 or higher) language settings will affect the text generated by SQL Server Reporting Server. However, the text in EMC SourceOne reports is displayed in English only in this release.

High availability of SQL Server Reporting ServicesSQL Server Reporting Services cannot be clustered. You can install a separate instance of Reporting Services, as described in Microsoft documentation for scale-out deployment.

Hardware and software requirements 277


Hardware and software requirementsThis section includes the following topics:

◆ “Requirements for the report server” on page 277

◆ “Requirements for the report client” on page 278

Note: Refer to Microsoft SQL Server 2008/2008 R2 Reporting Services documentation for additional requirements.

Requirements for the report serverEMC SourceOne reports are produced using Microsoft SQL Server 2008 or 2008 R2 Reporting Services (SSRS 2008/2008 R2).

If your EMC SourceOne databases are running on SQL Server 2008 or 2008 R2, then you can install Microsoft SQL Server 2008/2008 R2 Reporting Services on the same computer, as long as all hardware and software requirements for Reporting Services are met.

However, running reports against a large data set (such as the EMC SourceOne database) takes processor time away from the operation of EMC SourceOne. The ingestion rate or the performance of other EMC SourceOne operations may be affected when the databases and Microsoft Report Server are on the same computer.

For performance reasons, you may want to install Microsoft Report Server on a separate computer.

Refer to the following topics:

◆ “Hardware requirements for the report server” on page 277

◆ “Software requirements for the report server” on page 278

◆ “Login requirements for installation of the report server” on page 278

Hardware requirements for the report serverThe server on which you plan to install Microsoft SQL Server 2008/2008 R2 for use with EMC SourceOne tracking reports must meet Microsoft’s minimum or recommended hardware requirements. Refer to Microsoft documentation.



Software requirements for the report serverThe SQL Server 2008/2008 R2 server used for EMC SourceOne Reporting requires the following software:

◆ Windows Server 2003 or Windows Server 2008

◆ SQL Server 2008 or 2008 R2, Standard or Enterprise License

◆ .NET Framework (installed as part of the SQL Server 2008/2008 R2 Reporting Server)

Login requirements for installation of the report serverYou must install SQL Server Reporting Services using an account with local administrator privileges on the computer.

Requirements for the report clientThe client computer used to access EMC SourceOne reports requires:

◆ Internet Explorer 7.0 or higher to access EMC SourceOne reports over the intranet through a browser. Optional: Enable tabbed viewing for better browsing experience.

Note: After installing EMC SourceOne reports, add the Report Manager URL to Internet Explorer’s Local Intranet zone, as described in “Configuring Internet Explorer for EMC SourceOne reports” on page 313.

◆ Adobe Acrobat Reader to view and print EMC SourceOne reports in PDF format.

◆ Minimum screen resolution of 1024x768 for standard size monitors, or the equivalent for wide-screen monitors.

Installing SQL Server 2008/2008 R2 Reporting Services 279


Installing SQL Server 2008/2008 R2 Reporting ServicesThis section describes a single-server, default instance deployment of SQL Server Reporting Services. The Report Server and the Report Server database are installed on the same computer.

For information on planning, installing, and configuring Reporting Services for a scale-out deployment, refer to Microsoft documentation.

This procedure assumes that you are adding the Reporting Services feature to an existing instance of SQL Server with the Database Engine already installed, as shown in Figure 14.

To install SQL Server 2008/2008 R2 Reporting Services, on the SQL Server that will be used for EMC SourceOne reports:

1. Log in using an account with local administrator privileges on the computer.

2. Run the SQL Server setup program.

3. In the SQL Server Installation Center, click New installation or add features to an existing installation.

Figure 12 SQL Server Installation Center

The Setup Support Rules page displays information about your system.

4. Click Next.

5. On the Installation Type page, select Add features to an existing instance of SQL Server 2008/2008 R2, then select the name of the instance from the dropdown list.



Figure 13 Installation Type

6. Click Next.

7. On the Feature Selection page, select following features:

• Reporting Services

• Management Tools - Complete

Note: The check boxes for features that were installed previously are selected by default and are grayed out.



Figure 14 Feature Selection - SQL Server 2008

8. Click Next.

9. The Disk Space Requirements page reports the total disk space available and the total disk space required. Verify that you have enough disk space for the installation.

Figure 15 Disk Space Requirements

10. Click Next.



11. On the Server Configuration page, specify the service accounts (names and passwords) for the Reporting Services and any other SQL Server services you installed. Microsoft recommends using the Network Service account.

Figure 16 Server Configuration

12. Click Next.



13. On the Reporting Services Configuration page, select the Install, but do not configure the report server option for both existing and new installations.

Figure 17 Reporting Services Configuration

14. Click Next.



15. On the Error and Usage Reporting page, leave the default settings.

Figure 18 Error and Usage Reporting - SQL Server 2008

Figure 19 Error and Usage Reporting - SQL Server 2008 R2



16. Click Next.

17. The Installation Rules page (SQL Server 2008) or the Installation Configuration Rules page (SQL Server 2008 R2) indicates whether or not the installation is ready to proceed. The status of all items should be Passed or Not Applicable.

Figure 20 Installation Rules - SQL Server 2008



Figure 21 Installation Configuration Rules - SQL Server 2008 R2

18. Click Next.



19. The Ready To Install page lists the installation information that you supplied. Verify that the information is correct. If it is not correct, edit the information on the appropriate page of the installation wizard.

Figure 22 Ready To Install

20. When you are ready to proceed with the installation, click Install.

The Installation Progress page indicates the progress of the installation.

The Complete page indicates that the installation completed successfully.

21. Click Close.



Configuring SQL Server Report Server

IMPORTANT!Configure the options in the Reporting Services Configuration Manager window in the sequence shown in the left pane. Doing so ensures that each configuration screen is populated correctly.

To configure SQL Server 2008/2008 R2 Report Server:

1. On the Start menu, select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > Reporting Services Configuration Manager.

2. Continue to each of the following steps, in the order given:

• “Step 1: Connect to the Report Server instance” on page 289

• “Step 2: Specify the service account” on page 290

• “Step 3: Specify the Web Service URL” on page 290

• “Step 4: Specify information about the Reporting Server database” on page 292

• “Step 5: Specify the Report Manager URL” on page 297

• “Step 6: Use defaults for Email Settings” on page 299

• “Step 7: Use defaults for Execution Account” on page 299

• “Step 8: Specify backup information for the encryption key” on page 300

• “Step 9: Use defaults for Scale-out Deployment” on page 301

Configuring SQL Server Report Server 289


Step 1: Connect to the Report Server instanceThe Reporting Services Configuration Connection dialog box displays the name of the server running Report Server and the name of the instance of Report Server.

1. You can edit the information.

2. Click Connect to connect to the specified Report Server instance.

Figure 23 Reporting Services Configuration Connection - SQL Server 2008

Figure 24 Reporting Services Configuration Connection - SQL Server 2008 R2



Step 2: Specify the service accountMicrosoft recommends changing the Reporting Services service account through SQL Server Reporting Services Configuration Manager, not through the service console.

To specify the service account:

1. In the left pane of the Reporting Services Configuration Manager window, click Service Account.

2. Select the Use built-in account option.

3. Select Network Service from the dropdown list.

Figure 25 Service Account - Use built-in account

4. Click Apply.

Step 3: Specify the Web Service URLTo specify the Web Service URL:

1. In the left pane of the Reporting Services Configuration Manager window, click Web Service URL.

2. The right pane displays the default values for the Report Server Web Service. Leave the default settings.



Figure 26 Web Service URL

3. Click Apply.

The Results pane indicates the progress of URL creation.

IMPORTANT!Make a note of the Report Server Web Service URL shown at the bottom of the right pane. You need this URL when you install EMC SourceOne reports later.



Step 4: Specify information about the Reporting Server databaseSQL Server Reporting Server uses its own report database for internal processing of reports and other catalog information. This is not a EMC SourceOne database.

To specify information about the Reporting Server database:

1. In the left pane, click Database.

2. In the right pane, click Change Database.

Figure 27 Report Server Database

The Change Database dialog box opens.

3. Continue to each of the following steps, in the order given:

• “Step 4A: Change Database - Action page” on page 293

• “Step 4B: Change Database - Database Server page” on page 293

• “Step 4C: Change Database - Database page” on page 294

• “Step 4D: Change Database - Credentials page” on page 295

• “Step 4E: Change Database - Summary page” on page 296

• “Step 4F: Change Database - Progress and Finish page” on page 297



Step 4A: Change Database - Action page1. On the Action page of the Change Database dialog box, select the

Create a new report server database option.

Figure 28 Change Database - Action

2. Click Next.

Step 4B: Change Database - Database Server pageOn the Database Server page of the Change Database dialog box:

1. In the Server Name field, specify the name of the server running SQL Server 2008 Database Engine.

2. In the Authentication Type field, select Current user - Integrated Security.

The Username field displays the name of the account that has permission to connect to the SQL Server 2008 Database Engine. You specified this account when you installed the Database Engine.

3. Click Test Connection to verify that the specified account can connect to the Database Engine.



Figure 29 Change Database - Database Server

4. Click Next.

Step 4C: Change Database - Database pageOn the Database page of the Change Database dialog box:

1. Specify the name of the Report Server database. The default is ReportServer.

2. The language you specify for the reports database affects the names of roles and other internal features that an administrator sees when managing the database. It does not affect EMC SourceOne reports. In the Language field, select the appropriate language.

3. For Report Server Mode, select the Native Mode option.



Figure 30 Change Database - Database

4. Click Next.

Step 4D: Change Database - Credentials page1. On the Credentials page of the Change Database dialog box, in

the Authentication Type field, select Service Credentials (default). This is the account that the Report Server will use to connect to the Report Server database, using the same credentials as the Reporting Service.

The User name and Password fields display the credentials of the service account for Reporting Services that you specified during installation.

Note: The Windows Credentials option connects using the specified credentials for a particular Windows user. Select this option if the default Service Credentials option is not appropriate. The SQL Server Credentials option is not recommended.



Figure 31 Change Database - Credentials

2. Click Next.

Step 4E: Change Database - Summary pageThe Summary page of the Change Database dialog box lists the configuration information that you supplied.

1. Verify that the information is correct.

2. If it is not correct, edit the information on the appropriate page of the Change Database wizard and then click Next.

Figure 32 Change Database - Summary



Step 4F: Change Database - Progress and Finish pageThe Progress and Finish page of the Change Database dialog box indicates the progress of the configuration, and then indicates that the installation completed successfully.

Click Complete.

Step 5: Specify the Report Manager URLThe Report Manager URL will be used to access the EMC SourceOne reports.

To specify the Report Manager URL:

1. In the left pane of the Reporting Services Configuration Manager window, click Report Manager URL.

2. The right panel displays the URL to access Report Manager, based on information you supplied. You can edit the default value for the virtual directory. To edit other parameters, click Advanced.

3. Click Apply.

The Results pane indicates the progress of URL creation.



Figure 33 Report Manager URL

IMPORTANT!Make a note of the URL shown in the right pane. This is the URL that you will use to access EMC SourceOne reports.

4. Click the URL to verify that you can access the Report Manager home page.

Figure 34 Report Manager home page



Step 6: Use defaults for Email SettingsUse the defaults for email settings:

1. In the left pane of the Reporting Services Configuration Manager window, click Email Settings.

2. In the right pane, leave the default settings for email.

Figure 35 Email Settings

Step 7: Use defaults for Execution AccountTo use the defaults for Execution Account:

1. In the left pane of the Reporting Services Configuration Manager window, click Execution Account.

2. In the right pane, leave the default settings for the execution account.



Figure 36 Execution Account

Step 8: Specify backup information for the encryption keyTo specify backup information for Reporting Services encryption key:

1. In the left pane of the Reporting Services Configuration Manager window, click Encryption Keys.

2. In the right pane, click Backup.

Figure 37 Encryption Keys



3. In the Backup Encryption Key dialog box, specify the security password and file to backup your Report Server encryption key.

a. In the File Location field, either type a new pathname or click the browse button and select an existing encryption key file.

b. In the Password field, type the password for the encryption key.

c. In the Confirm Password field, retype the password.

The encryption file and password are used to save the encrypted information (such as credentials) stored in Report Server. This information is required in case Report Server becomes corrupt and needs to be restored with a re-install.

Figure 38 Backup Encryption Key

4. Click OK to close the Backup Encryption Key dialog box.

Step 9: Use defaults for Scale-out DeploymentUse the defaults for Scale-out Deployment:

1. In the left pane of the Reporting Services Configuration Manager window, click Scale-out Deployment.

2. The right pane displays information about the Report Server.



Figure 39 Scale-out Deployment

3. Click Exit to close the Reporting Services Configuration Manager window.

Verifying installation of SQL Server Report Server 303


Verifying installation of SQL Server Report ServerUse one of the following methods to verify the installation of SQL Server 2008/2008 R2 Report Server:

◆ In Reporting Services Configuration Manager, click the URL link described in “Step 5: Specify the Report Manager URL” on page 297.

◆ Outside of Reporting Services Configuration Manager, follow these steps on the Report Server. Repeat the procedure on a client computer.

1. Start Internet Explorer.

2. Enter the Report Manager URL. (This is the URL shown on the Report Manager URL page of SQL Server Reporting Services Configuration Manager).

Note: It may take a few minutes to access the URL, and it may appear that the access operation has hung. SQL Server Reporting Services flushes its cache if it is inactive for 20 minutes.

3. Verify that you see the SQL Server Reporting Services Home page.

You have completed installing and configuring SQL Server 2008/2008 R2 Reporting Services.



Installing EMC SourceOne reportsThis section describes the prerequisites and procedures for installing EMC SourceOne reports.

PrerequisitesEnsure the following prerequisites are completed:

◆ Install and configure SQL Server 2008/2008 R2 Reporting Services, as described earlier in this chapter.

◆ Verify that the SQL Server Reporting Services web service is ready by browsing to the Web Service URL. (This is the URL shown on the Web Service URL page of SQL Server Reporting Services Configuration Manager).If you attempt to install EMC SourceOne reports before this web service is ready, then the installation may time out.

ProcedureTo install EMC SourceOne reports, on the SQL Server 2008/2008 R2 Report Server:

1. Log on with local administrator privileges on the computer.

2. Open a command window.

3. Run ES1_Reports_Setup.bat.

4. At the following prompt, specify the SQL Server that hosts the EMC SourceOne Activity database. Specify the IP address or the server name, or press Enter to accept the default (localhost).

Specify SQL Server for Activity database <default:localhost>:

5. At the following prompt, specify the name of the EMC SourceOne Activity database.

Specify Activity Database Name:

6. At the following prompt, specify the URL of the Report Server Web Service. It is not necessary to include the port number.

Specify Report Server Web Service URL:

Installing EMC SourceOne reports 305


This URL must be the same one that you configured on the Web Service URL page in Reporting Services Configuration Manager.

Figure 40 Example - Web Service URL

Note: Do not specify the Report Manager URL.

7. At the View log file? <Y/N default:N> prompt, do one of the following steps:

• If you want to view the log file, press Y.

• If you do not want to view the log file, press N, or press Enter to accept the default (N).

Figure 41 Running ES1_Reports_Setup.bat

If the installation is successful, then you see messages confirming the installation of each report.

If an error occurs during installation, then you see an error message. The following example shows the error message displayed when you enter an incorrect URL.



Figure 42 404 error due to incorrect URL

Verify report installationTo verify that the reports were installed:

1. Start Internet Explorer.

2. Enter the Report Manager URL. (This is the URL shown on the Report Manager URL page of SQL Server Reporting Services Configuration Manager).

Note: It may take a few minutes to access the URL, and it may appear that the access operation has hung. SQL Server Reporting Services flushes its cache if it is inactive for 20 minutes.

3. Verify that the SQL Server Reporting Services home page displays the EMC SourceOne folder.

Figure 43 EMC SourceOne folder

Installing EMC SourceOne reports 307


4. Click the EMC SourceOne folder to open it, and verify that it contains the following subfolders:

• Configuration Reports

• Search Audit Reports

• System Reports

Figure 44 EMC SourceOne reports subfolders



Controlling access to EMC SourceOne reportsAfter you install EMC SourceOne reports, you must set permissions for users to access EMC SourceOne reports.

The examples in this section describe common scenarios, and assume:

◆ EMC SourceOne Email Management and EMC SourceOne reports are installed.

◆ SQL Server 2008/2008 R2 Reporting Services are installed on the same computer that hosts the EMC SourceOne Activity database.

Roles in Reporting ServicesIn SQL Server Reporting Services you can assign groups or users to different roles to control access to reports. For example, the Content Manager role could include administrator users who are able to view and customize reports, and the Browser role could include additional users who can only view reports.

The Content Manager role and the Browser role have pre-defined permissions in Reporting Services. If these built-in roles are not appropriate, then you can create custom roles in SQL Server Management Studio. For example, if you want administrators to set up reports without being able to view them, then you could create a role that grants all permissions except for View Report.

To customize roles further, refer to Microsoft documentation.

Requirements for users and groupsIf you create new groups, you must give them Connect and Execute permissions to the EMC SourceOne Activity database so they can view reports.

For Content Manager roleAssigning the EMC SourceOne security group to the Content Manager role bypasses the need to set up additional permissions in Active Directory and SQL for report administration.

Controlling access to EMC SourceOne reports 309


For Browser roleFor users who will have read-only access to reports:

1. Create a group in Active Directory (for example EMC SourceOne Report Users), and add appropriate users to the group.

2. To view reports, members of this new group also need access to the EMC SourceOne Activity database. Using SQL Server Management Studio:

a. Add the group as a login.

b. Under permissions for the EMC SourceOne Activity database, grant both Connect and Execute permissions.

Assigning users to rolesYou can specify security settings for all EMC SourceOne reports, for all reports in a folder, or for individual reports.

To do so, you must be logged in as administrator, or you must be a user who already has the Content Manager role.

To navigate to security settings and assign users to roles:

1. Using Internet Explorer, navigate to the SQL Server Reporting Services Home page. (Use the URL shown on the Report Manager URL page of SQL Server Reporting Services Configuration Manager).

2. Navigate to the Security tab of the folder or report for which you want to set access. For example, to specify security settings for all EMC SourceOne reports, do one of the following steps:

• In SQL Server 2008, open the EMC SourceOne folder, click the Properties tab, then click Security.

• In SQL Server 2008 R2, select Manage from the EMC SourceOne folder’s dropdown menu, then click Security.

3. On the Security tab, click New Role Assignment.



4. Do one of the following steps:

• To specify users who can view and manage reports:

a. In the Group or user name field, specify your EMC SourceOne security group.

b. Select the Content Manager role.

• To specify users who have read-only access to reports:

a. In the Group or user name field, specify the name of the report users group that you created in Active Directory.

b. Select the Browser role.

5. Click OK.

Authenticating with the EMC SourceOne Activity database 311


Authenticating with the EMC SourceOne Activity databaseIf your Reporting Services are on a different computer than the one that hosts EMC SourceOne Activity database, when you view reports, you may experience errors relating to authentication with the Activity data source. This is the result of Windows Integrated Security, which can only pass credentials across one computer unless Kerberos is enabled. If this problem occurs, then do one of the following steps:

◆ Configure your network to use Kerberos.

◆ Configure the Activity data source to use Credentials supplied by the user running the report instead of Windows Authentication. When running reports, users will be prompted for valid credentials to connect to the SQL database.

To change connection credentials for the Activity data source:

1. On the Home page of SQL Server Reporting Services, open the EMC SourceOne folder.

2. Click Show Details (SQL Server 2008) or Detail View (SQL Server 2008 R2).

Figure 45 EMC SourceOne folder - Details view

3. Open the Data Sources folder.

4. Click the dsES1Activity link.



Figure 46 Data Sources folder

5. On the Properties page:

a. Select Credentials supplied by the user running the report.

b. Select the Use as Windows credentials when connecting to the data source checkbox.

Figure 47 Properties page - dsES1Activity data source

6. Click Apply.

Configuring Internet Explorer for EMC SourceOne reports 313


Configuring Internet Explorer for EMC SourceOne reportsAfter installing EMC SourceOne reports, add the URL of the SQL Server Reporting Services web site to the Local Intranet Zone in Internet Explorer. (This URL is shown on the Report Manager URL page of SQL Server Reporting Services Configuration Manager.)

To configure Internet Explorer settings for client computers accessing the EMC SourceOne Reports URL:







7. Click Sites.

8. Click Advanced.

9. Add the URL of the SQL Server Reporting Services web site.





UpgradeRefer to the product release notes for detailed instructions on upgrading EMC SourceOne reports.

Uninstall reportsTo uninstall EMC SourceOne reports, including all customizations:

1. You must have System Administrator privileges for SQL Server 2008/2008 R2 Reporting Services.

2. In Internet Explorer, enter the Report Manager URL for your SQL Server 2008/2008 R2 Reporting Services.

The SQL Server Reporting Services home page opens.

3. Click Show Details on the right side of the toolbar.

The home page lists the Data Sources and EMC SourceOne folders.

4. Select the checkbox es for both the Data Sources and the EMC SourceOne folders.

5. Click Delete on the toolbar.


Aaccounts 43

Active Directory 43administrative 46Admins group 46installation 46Lotus Notes user 57Master Services service account 44OWA service account 45security group 45service account 44

Active Directory accounts and groups 43Administration Console

installing 111administrative accounts 46Admins group 46antivirus software

considerations for Domino 217applications overview 22architecture 18

applications 22enterprise configuration example 35example configurations 29high-availability 40message archives 21processing services 19sizing 38storage 22, 32, 37

archivinghistorical 13real-time 13supported types 13user-directed 13

Cclustering Master Services 109Console

installation 111permissions 47, 52

Ddatabase

installation 91security access 98

database host computer requirements 60Discovery Manager

full edition and express edition 16worker services 19

Discovery Manager express editionpermissions 47requirements 58

Dominoantivirus software 217installing ONM Viewer software 200permissions 57system requirements 71

Domino Extensionsinstalling on AIX 183installing on IBM i 191installing on Linux 183installing on Microsoft Windows 176overview 172shortcutting considerations 220supported platforms 174

Index


Index

Eenterprise configuration example 35example configuration 31example configurations 29Exchange

journaling mailboxes 55permissions 55supporting Outlook icon display 267system requirements 70

Extensions for IBM Lotus Domino Support software

installing 223, 249Extensions for OWA 2003 Support software

installing 154Extensions for OWA 2007 or 2010 Support

softwareinstalling 160, 166

FFile Systems

overview 15

Hhigh-availability 40historical archiving 13http

//Support.EMC.com 9

IIBM Lotus Domino

anitvirus software 217installing ONM Viewer software 200permissions 57system requirements 71

IBM Lotus Domino Extensionsinstalling on AIX 183installing on IBM i 191installing on Linux 183installing on Microsoft Windows 176overview 172shortcutting considerations 220supported platforms 174

iconssupporting shortcut and UDA icons 265, 267

IIS Web server

system requirements 68installation

Administration Console 111clustering Master Services 109configuring load balancing 125databases 91EMC SourceOne reports 273Extensions for IBM Lotus Domino Support

software 223, 249Extensions for OWA 2003 Support software

154Extensions for OWA 2007 or 2010 Support

software 160, 166maintaining 149, 204Master Services software 103Mobile Services software 135Native Archive Services software 141ONM Viewer software 200overview 89, 153pre-installation checklist 88, 152Search deployment scenarios 128Search software 128Web Services software 121Worker Services software 115

installation account 46

Jjournaling 13journaling databases

additional mail.box databases 213console administrator access 175, 208ExFailover.nsf 213multiple Domino servers 213

journaling mailboxes 55

LLotus Notes user 57

Mmailbox permissions 56Master Services

clustering 109installing 103permissions 47, 52service account 44


Index

system requirements 61message archive types 21Microsoft Exchange

permissions 55supporting Outlook icon display 267system requirements 70

Microsoft SharePointoverview 14

MIME drop directory permissions 54mobile devices

system requirements 72Mobile Services software

installing 135

NNative Archive

installing 141permissions 47, 52system requirements 65

OONM Viewer software

installing 200Outlook icon support

installing 267overview 265

OWA service account 45

Pperformance metrics 39permissions 43

Active Directory 43Console 47, 52Discovery Manager 47IBM Lotus Domino 57Master Services 47, 52Microsoft Exchange 55MIME drop directory 54Native Archive 47, 52PST discovery 54PST drop directory 54SQL Server 49storage 51Web Services 47, 52Worker Services 47, 52

processing services 19product overview 12PST discovery permissions 54PST drop directory permissions 54

Rreal-time archiving 13reports

authenticating with the Activity database 311

configuring Internet Explorer to support 313configuring SQL Server Report Server 288controlling access to 308hardware and software requirements 277high availability options 276installing EMC SourceOne Reporting 273installing EMC SourceOne reports 304installing SQL Server Reporting Services 279maintaining the installation 314planning checklist 274pre-deployment planning 275SQL Server requirements 275verifying installation of SQL Server Report

Server 303requirements

database host computers 60Discovery Manager 58EMC SourceOne reports 273IIS Web server 68Master Services computer 61messaging environments 70, 71mobile devices 72Native Archive Services computer 65storage 67system 58Worker Services computer 63

SSearch

deployment scenarios 128installing 128installing ONM Viewer software 200

searchessupported types 14

security group 45service account


Index

creating 44SharePoint

overview 14shortcut and UDA icon support

installing 267overview 265

single sign-onconfiguring (Domino) 249configuring (Windows) 223

sizing and scalability 38small-to-medium business 31small-to-medium business configuration 31SQL Server

EMC SourceOne Reporting 273host computer requirements 60important considerations 75installing databases 91permissions 49

storageNative Archive 32, 37overview 22permissions 51system requirements 67

system architecture 18system requirements 58

database host computer 60Discovery Manager 58EMC SourceOne reports 273IBM Lotus Domino 71IIS Web server 68Master Services computer 61Microsoft Exchange 70mobile devices 72Native Archive Services computer 65storage 67Worker Services computer 63

Uuser-directed archiving 13

WWeb Services

installing 121load balancing 125permissions 47, 52

Worker Services

installing 115permissions 47, 52system requirements 63

Date post:	04-Jan-2017
Category:	Documents
Upload:	phamtuyen
View:	235 times
Download:	5 times